Beruflich Dokumente
Kultur Dokumente
Version 10.0.2
Confidentiality, Copyright Notice & Disclaimer
This document is the property of TEOCO, which owns the sole and full rights including copyright.
TEOCO retains the sole property rights to all information contained in this document, and without
the written consent of TEOCO given by contract or otherwise in writing, the document must not be
copied, reprinted or reproduced in any manner or form, nor transmitted in any form or by any
means: electronic, mechanical, magnetic or otherwise, either wholly or in part.
The information herein is designated highly confidential and is subject to all restrictions in any law
regarding such matters and the relevant confidentiality and non-disclosure clauses or agreements
issued with TEOCO prior to or after the disclosure. All the information in this document is to be
safeguarded and all steps must be taken to prevent it from being disclosed to any person or entity
other than the direct entity that received it directly from TEOCO.
All other company, brand or product names are trademarks or service marks of their respective
holders.
This is a legal notice and may not be removed or altered in any way.
Your feedback is important to us: The TEOCO Documentation team takes many measures in
order to ensure that our work is of the highest quality.
If you find errors or feel that information is missing, please send your Documentation-related
feedback to Documentation@teoco.com
Thank you,
Table of Contents
1 Array and Report Descriptions ...................................................................... 9
GSM (Sim) Arrays.............................................................................................. 9
Pathloss Arrays (GSM Sim) ....................................................................................... 10
Coverage and Data Rate Arrays (GSM Sim)............................................................. 10
All Servers Array (GSM Sim) ..................................................................................... 11
UMTS, CDMA2000 and EV-DO Arrays ............................................................ 12
Pathloss Arrays (UMTS, CDMA, EV-DO) .................................................................. 13
Pilot Coverage Arrays (UMTS, CDMA, EV-DO) ........................................................ 13
Handover Arrays (UMTS, CDMA, EV-DO) ................................................................ 15
Uplink Noise Arrays (UMTS, CDMA, EV-DO) ........................................................... 16
Downlink Noise Arrays (UMTS, CDMA, EV-DO) ....................................................... 16
Uplink Coverage Arrays (UMTS, CDMA, EV-DO) .................................................... 17
Downlink Coverage Arrays (UMTS, CDMA, EV-DO) ............................................... 18
Coverage Balance Arrays (UMTS, CDMA, EV-DO) .................................................. 19
Soft Blocking Arrays (UMTS, CDMA, EV-DO)........................................................... 20
Hard Blocking Arrays (UMTS, CDMA, EV-DO) ......................................................... 20
Throughput Arrays (UMTS, CDMA, EV-DO) ............................................................. 20
HSDPA Arrays ........................................................................................................... 21
HSUPA Arrays ........................................................................................................... 23
All Servers Array (UMTS, CDMA, EV-DO) ................................................................ 24
DVB-H C/I Array ........................................................................................................ 25
LTE Arrays....................................................................................................... 25
Pathloss Arrays (LTE)................................................................................................ 26
Downlink Reference Signal Coverage Arrays (LTE) ................................................. 27
Downlink Noise Arrays (LTE)..................................................................................... 29
Uplink Coverage Arrays (LTE) ................................................................................... 29
Downlink Coverage Arrays (LTE) .............................................................................. 30
Beamforming Gain Arrays (LTE) ............................................................................... 32
Downlink Throughput and Data Rate Arrays (LTE) ................................................... 32
Uplink Throughput and Data Rate Arrays (LTE) ....................................................... 34
General Arrays (LTE)................................................................................................. 36
5G Arrays ........................................................................................................ 38
Pathloss Arrays (5G) ................................................................................................. 39
Downlink Reference Signal Coverage Arrays (5G) ................................................... 39
Downlink Noise Arrays (5G) ...................................................................................... 42
UL Coverage Arrays (5G) .......................................................................................... 42
DL Coverage Arrays (5G) .......................................................................................... 44
Downlink Throughput and Data Rate Arrays (5G) ..................................................... 45
Uplink Throughput and Data Rate Arrays (5G) ......................................................... 46
General Arrays (5G) .................................................................................................. 47
Wi-Fi Arrays ..................................................................................................... 47
Pathloss Arrays (Wi-Fi) .............................................................................................. 48
Downlink Coverage Arrays (Wi-Fi) ............................................................................ 49
Throughput Arrays (Wi-Fi) ......................................................................................... 49
General Arrays (Wi-Fi) ............................................................................................... 50
Composite Tech Arrays (GSM, UMTS, LTE, 5G, Wi-Fi) ................................... 50
Fixed WiMAX Arrays ........................................................................................ 51
General Arrays (Fixed WiMAX) ................................................................................. 51
Thresholded Arrays (Fixed WiMAX) .......................................................................... 52
Mobile WiMAX Arrays ...................................................................................... 52
Pathloss Arrays (Mobile WiMAX) .............................................................................. 53
5
ASSET 10.0.2 Technical Reference Guide
6
Table of Contents
7
ASSET 10.0.2 Technical Reference Guide
8
Array and Report Descriptions
This section describes many of the different types of arrays and reports available in ASSET. The
ranges of outputs available may vary according to which technology you are using, which licences
you have, and which processes you have chosen to run.
For information on creating, managing and displaying arrays, and generating reports, see the
ASSET User Reference Guide.
Note: In addition to this section, there are specialist documents containing a more comprehensive
list of descriptions of all the array outputs and algorithms used in the Simulator. For information on
how you can obtain these documents, please see Static Simulation Algorithms and Outputs on
page 109.
All arrays are produced on a per cell-layer basis. Many arrays depend on whether the terminal is
taken to be indoor or outdoor. Indoor arrays use the in-building parameters for the clutter type at
each pixel (that is, indoor loss and indoor shadow-fading standard deviation).
Coverage arrays can be drawn even if no snapshots have been run, but you should note that the
arrays then refer to coverage in an unloaded system. To obtain coverage arrays for a loaded
system, you must run some snapshots; the key purpose of running snapshots is to provide
measures of traffic load. The arrays change little after a relatively small number of snapshots have
been performed (10s of snapshots in most cases). This is because only a small number of
snapshots are needed to get an idea of the average loading on each sub-cell.
Here is an example of the GSM arrays you can generate on the Map View when using the
Simulator:
Example of the GSM (Sim) arrays appearing in the Map View Data Types
9
ASSET 10.0.2 Technical Reference Guide
These are the downlink losses of the Best Server by RSS and Nth Best Server by RSS,
respectively. They represent average values and are therefore calculated with fades of 0 dB.
This is the sub-cell that provides the highest (and Nth highest) RSS for the terminal.
These are the highest (and Nth highest) RSS levels. They represent average values and are
therefore calculated with fades of 0dB.
Coverage Probability
This is the probability that the Best DL Cell (by RSS) satisfies the RSS requirement specified on the
terminal type. This probability depends on the standard deviation of shadow fading for the clutter
type at the pixel. If this standard deviation has been set to zero, then there are only three possible
coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is satisfied
exactly, and 100% if the requirement is exceeded.
Coverage Probability OK
This is a thresholded version of the RSS Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the RSS Coverage Probability
array. A value of “Yes” means that the coverage probability meets the coverage reliability level
specified in the Sim Display Thresholds tab of the Array Settings dialog box.
CINR (Control)
These are the CINR(Control) values corresponding to the best serving sub-cells, so they are not
necessarily the highest CINR(Control) values.
10
Array and Report Descriptions
These are the CINR (Traffic + Control) values corresponding to the best (and Nth best) serving
sub-cells, so they are not necessarily the highest (and Nth highest) CINR (Traffic + Control) values.
Achievable Bitrate
This is the highest bitrate that can be achieved by the terminal based on CINR regardless of
system loading.
It displays information about which cells are "covering" each pixel. A set of lines is drawn between
all possible serving cells to the simulation pixel where the mouse cursor is located. For pixels with
more than one covering cell, the line thickness increases proportionally.
This array enables you to identify distant servers so that you can optimise your network design by
lowering, moving or reducing the transmit power of problematic sites.
11
ASSET 10.0.2 Technical Reference Guide
Most of them have a dependency on terminal type because body loss and terminal antenna gain
are always included in the link budget.
Many of them depend on whether the terminal is considered to be indoor or outdoor. Indoor arrays
use the in-building parameters for the clutter type at each pixel (that is, indoor loss and indoor
shadow fading standard deviation). Indoor terminals are always taken to be slow moving.
Coverage arrays can be displayed even if no snapshots have been run, but you should note that in
these circumstances the arrays represent coverage in an unloaded network. To obtain coverage
arrays for a loaded network, you must run some snapshots or define the loads manually. The key
purpose of running snapshots is to provide measures of system load.
Arrays for coverage tend to have a weak dependence on the number of snapshots run, and the
arrays change little after a relatively small number of snapshots have been performed (10s of
snapshots in most cases). This is because only a small number of snapshots are needed to get an
idea of the average noise rise and average DL traffic power on each cell.
Arrays for hard or soft blocking probabilities have a strong dependence on the number of snapshots
run. This is because blocking is evaluated by reporting the proportion of snapshots that would block
further connections. For example, if only 1 snapshot has been run, then all blocking probabilities
will be either 0% or 100%. If 5 snapshots have been run then all blocking probabilities will belong to
the set {0%, 20%, 40%, 60%, 80%, 100%}.
Here is an example of the UMTS arrays you can generate on the Map View when using the
Simulator:
Example of the Simulator arrays appearing in the Map View Data Types
12
Array and Report Descriptions
These are the downlink losses of the Best DL Cell by RSCP and the Nth Best DL Cell by RSCP,
respectively. They represent average values and are therefore calculated with fades of 0 dB.
Line of Sight
This is a two-valued array (LOS, non-LOS) for the Best DL Cell by RSCP. The indoor instance is
non-LOS everywhere. The array is available with Enhanced Macrocell, MYRIAD and Volcano
propagation model predictions.
This is the cell that provides the highest (and Nth highest) RSCP for the terminal.
The highest (and Nth highest) RSCP level. Represents average values and is therefore calculated
with fades of 0dB.
This is the probability that the Best DL Cell (by RSCP) satisfies the RSCP requirement specified on
the terminal type. This probability depends on the standard deviation of shadow fading for the
clutter type at the pixel. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is
satisfied exactly, and 100% if the requirement is exceeded.
RSCP Coverage OK
This is a thresholded version of the RSCP Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the RSCP Coverage Probability
array. A value of “Yes” means that the RSCP coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
13
ASSET 10.0.2 Technical Reference Guide
Number of RSCP OK
This is the number of covering cells with a satisfactory RSCP. A cell is counted as having a
satisfactory RSCP if its RSCP coverage probability meets the coverage reliability level specified in
the Sim Display Thresholds tab of the Array Settings dialog box.
These are the highest (and Nth highest) Ec/Io values. They represent average values and are
therefore calculated with fades of 0dB.
This is the probability that the Best DL Cell (by RSCP) satisfies the Ec/Io requirement specified on
the terminal type. This probability depends on the standard deviation of shadow fading for the
clutter type at the pixel. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is
satisfied exactly, and 100% if the requirement is exceeded.
This is a thresholded version of the Pilot Ec/Io Coverage Probability array and has just 2 values
(Yes/No). It has the advantage of being quicker to calculate than the Pilot Ec/Io Coverage
Probability array. A value of “Yes” means that the pilot Ec/Io coverage probability meets the
coverage reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
This is the number of covering cells with a satisfactory pilot Ec/Io. A cell is considered as having a
satisfactory pilot Ec/Io if its pilot Ec/Io coverage probability meets the coverage reliability level
specified in the Sim Display Thresholds tab of the Array Settings dialog box.
Pilot SIR
This is the best Pilot SIR value. It represents an average value and is therefore calculated with
fades of 0dB.
This is the probability that the Best DL Cell (by RSCP) satisfies the pilot SIR requirement specified
on the terminal type. This probability depends on the standard deviation of shadow fading for the
clutter type at the pixel. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is
satisfied exactly, and 100% if the requirement is exceeded.
14
Array and Report Descriptions
This is a thresholded version of the Pilot SIR Coverage Probability array and has just 2 values
(Yes/No). It has the advantage of being quicker to calculate than the Pilot SIR Coverage Probability
array. A value of “Yes” means that the pilot SIR coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
This is the number of covering cells with a satisfactory pilot SIR. A cell is considered as having a
satisfactory pilot SIR if its pilot SIR coverage probability meets the coverage reliability level
specified in the Sim Display Thresholds tab of the Array Settings dialog box.
This is the number of suitable HO candidates for the Best DL Cell (by RSCP). If the Ec/Io level of
the best DL cell is below the Ec/Io requirement on the terminal type, then no result is given.
Otherwise all the other cells are checked to see if their pilot Ec/Io levels make them suitable HO
candidates.
This is the number of suitable soft HO candidates for the Best DL Cell (by RSCP). If the Ec/Io level
of the best DL cell is below the Ec/Io requirement on the terminal type, then no result is given.
Otherwise all the other cells (on different sites to the best cell) are checked to see if their pilot Ec/Io
levels make them suitable HO candidates.
This is the number of suitable softer HO candidates for the Best DL Cell (by RSCP). If the Ec/Io
level of the best DL cell is below the Ec/Io requirement on the terminal type, then no result is given.
Otherwise all the other cells (on the same site as the best cell) are checked to see if their pilot Ec/Io
levels make them suitable HO candidates.
15
ASSET 10.0.2 Technical Reference Guide
This is the potential size of the active set. It is related to the Available Soft/Softer Cells array by:
Active Set Size = min (1 + Available Soft/Softer Cells, Max Active Set Size).
Pilot Polluters
For CDMA2000 and EV-DO, the number of pilot polluters at a location is:
The number of cells that are not in the active set, but provide an Ec/Io level higher than
x dB. Therefore the pilot pollution threshold in CDMA2000 is an absolute quantity.
A typical value for CDMA2000 is -15 dB.
UL Load
Dependencies: Carrier
This is the uplink cell load of the Best DL Cell (by RSCP). Note that for OTSR cells, there can be a
different uplink load on each antenna used by the cell (just as in the uplink simulation reports for
OTSR cells).
UL FRE
Dependencies: Carrier
This is the uplink frequency re-use efficiency of the Best DL Cell (by RSCP). Note that for OTSR
cells, there can be a different uplink FRE on each antenna used by the cell (just as in the uplink
simulation reports for OTSR cells).
DL Total RX Power
This is the total downlink received power. It represents an average value and is therefore calculated
with fades of 0dB.
16
Array and Report Descriptions
DL Io
This is the total downlink power spectral density. It represents an average value and is therefore
calculated with fades of 0dB.
DL Iother/Iown
Dependencies: Carrier
This is the ratio of downlink power received from other cells, to downlink power received from own
cell, where “own cell” is the Best DL Cell (by RSCP).
DL FRE
Dependencies: Carrier
This is the downlink frequency re-use efficiency at a pixel and it is related to DL Iother/Iown as
follows:
DL FRE = 1 / ( 1 + Iother/Iown )
Best UL Cell
This is the cell requiring the minimum uplink transmit power. For UMTS bearers, the only real
dependence is on the carrier used. However, for CDMA2000 bearers, the Best UL Cell must have
an RC type that is supported by the terminal type.
This shows by how much the uplink Eb/No requirement is exceeded on the Best UL Cell, assuming
the terminal transmits at full power.
UL Req TX Power
This is the required UL TX power of the terminal. It is equal to the maximum output power of the
terminal type (dBm) minus the UL Eb/No (or Eb/Nt) margin (dB).
UL Coverage Probability
This is the probability of satisfying the uplink bearer Eb/No (or Eb/Nt) requirement on the Best UL
Cell, assuming the terminal transmits at full power. This probability depends on the standard
deviation of shadow fading for the clutter type at the pixel. If this standard deviation has been set to
zero, then there are only three possible coverage probabilities: 0% if the requirement is not
satisfied, 50% if the requirement is satisfied exactly, and 100% if the requirement is exceeded.
17
ASSET 10.0.2 Technical Reference Guide
UL Coverage Probability OK
This is a thresholded version of the UL Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the UL Coverage Probability
array. A value of “Yes” means that the uplink coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
Achievable UL Bearer
The purpose of this array is to provide a composite coverage plot for the uplink bearers of a
service. The array shows the highest priority uplink bearer with acceptable uplink coverage, that is,
with UL Coverage Probability meeting the coverage reliability level specified in the Sim Display
Thresholds tab of the Array Settings dialog box.
Best DL Cell
This is the cell requiring the minimum downlink transmit power. For UMTS bearers, the only real
dependence is on the carrier used, and so this array is exactly the same as the Best DL cell by
RSCP. However, for CDMA2000 bearers, the Best DL Cell must have an RC type that is supported
by the terminal type.
This is how much the downlink Eb/No (or Eb/Nt) requirement has been exceeded, assuming that
the link powers of cells in the active set are at maximum allowed levels.
DL Coverage Probability
This is the probability of satisfying the downlink bearer Eb/No (or Eb/Nt) requirement, assuming that
the link powers of cells in the active set are at maximum allowed levels. This probability depends on
the standard deviation of shadow fading for the clutter type at the pixel. If this standard deviation
has been set to zero, then there are only three possible coverage probabilities: 0% if the
requirement is not satisfied, 50% if the requirement is satisfied exactly, and 100% if the requirement
is exceeded.
DL Coverage Probability OK
This is a thresholded version of the DL Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the DL Coverage Probability
array. A value of “Yes” means that the downlink coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
18
Array and Report Descriptions
Achievable DL Bearer
The purpose of this array is to provide a composite coverage plot for the downlink bearers of a
service. The array shows the highest priority downlink bearer with acceptable downlink coverage,
that is, with DL Coverage Probability meeting the coverage reliability level specified in the Sim
Display Thresholds tab of the Array Settings dialog box.
This is the Ior/Ioc of the Best DL Cell by RSCP. It represents an average value and is therefore
calculated with fades of 0dB.
This array gives the DL Eb/Nt of the DL bearer with the highest supportable Ior/Ioc requirement.
The purpose of this array is to provide a combined coverage plot for the downlink bearers of a
service. The array shows the bearer with the highest supportable Ior/Ioc requirement.
This is the air-interface bitrate of the DL bearer with the highest supportable Ior/Ioc requirement.
Coverage Balance
The purpose of this array is to provide a composite uplink/downlink coverage plot for a service. The
uplink is deemed to have coverage if any of the uplink bearers on the service have UL Coverage
Probability meeting the coverage reliability level specified in the Sim Display Thresholds tab of the
Array Settings dialog box. Similarly, the downlink is deemed to have coverage if any of the downlink
bearers on the service have DL Coverage Probability meeting the specified coverage reliability
level.
19
ASSET 10.0.2 Technical Reference Guide
This is the probability of uplink soft blocking on the Best UL Cell. Uplink soft blocking occurs if an
additional connection with the uplink bearer would cause the noise rise limit to be exceeded. The
uplink soft blocking probability is determined by examining the proportion of snapshots that would
block a connection with the uplink bearer in this way.
For OTSR cells, the noise rise is measured on a per antenna basis (as in the simulation reports), so
the soft blocking probability depends on the antenna that covers the pixel.
This is the probability of downlink soft blocking on the Best DL Cell. Downlink soft blocking occurs if
an additional connection with the downlink bearer requires more power than is available on the cell.
The downlink soft blocking probability is determined by examining the proportion of snapshots that
would block a connection with the downlink bearer in this way.
This is the probability of hard blocking on the Best DL Cell because of lack of resources. This type
of blocking occurs if an additional connection with the bearer requires more resources than are
available. The blocking probability is determined by examining the proportion of snapshots that
would block a connection with the bearer in this way.
This is the probability of hard blocking on the Best DL Cell because of lack of primary resources.
This type of blocking occurs if an additional connection with the bearer requires more primary
resources than are available. The blocking probability is determined by examining the proportion of
snapshots that would block a connection with the bearer in this way.
UL Throughput (kbps)
Dependencies: Carrier
This is the UL throughput on the Best DL Cell by RSCP. It is the value in the Simulator reports,
rendered over the best server area of the cell.
20
Array and Report Descriptions
DL Throughput (kbps)
Dependencies: Carrier
This is the DL throughput on the Best DL Cell by RSCP. It is the value in the Simulator reports,
rendered over the best server area of the cell.
HSDPA Arrays
Here are brief definitions of the HSDPA-specific arrays:
This is the cell that provides the highest SINR level for the terminal.
HSDPA - SINR
This is the highest SINR level. It represents an average value and is therefore calculated with fades
of 0dB.
This is the extent to which the Eb/No requirement of the HSDPA bearer is exceeded. The cell of
interest is chosen by examining the SINR levels of cells that support the HSDPA bearer, and
choosing the cell with the largest level.
This is the probability of satisfying the Eb/No requirement of the HSDPA bearer. The cell of interest
is chosen by examining the SINR levels of cells that support the HSDPA bearer, and choosing the
cell with the largest level. The probability depends on the standard deviation of shadow fading for
the clutter type at the pixel. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is
satisfied exactly, and 100% if the requirement is exceeded.
This is a thresholded version of the HSDPA - DL Coverage Probability array and has just two
values (Yes/No). It has the advantage of being quicker to calculate than the HSDPA - DL
Coverage Probability array. A value of “Yes” means that the coverage probability satisfies the
downlink coverage reliability level specified in the Sim Display Thresholds tab of the Array Settings
dialog box.
21
ASSET 10.0.2 Technical Reference Guide
The purpose of this array is to provide a composite coverage plot for the HSDPA bearers of a
service. The array shows the highest priority HSDPA bearer with acceptable coverage, that is, with
'HSDPA - DL Coverage Probability' meeting the coverage reliability level specified in the Sim
Display Thresholds tab of the Array Settings dialog box.
This is the user bitrate of the 'HSDPA - Achievable Downlink Bearer'. It is similar to the 'HSDPA -
Achievable Downlink Bearer' array, but instead of giving the bearer name at each location, it gives
the bearer's user rate. Note that for MIMO bearers, the user rate may be adjusted depending on the
number of TX and RX antennas on the cell and terminal respectively.
Dependencies: Carrier
This is the offered HSDPA load on the Best DL Cell by SINR. Note that the offered load is
calculated for each HSDPA resource pool in the network. Therefore, if the HSDPA resources have
been pooled on a site, all HSDPA cells on that site will show the same offered load.
This is the bitrate that the user experiences at a location when there is no queuing delay on the cell.
It is calculated by multiplying the bitrate of the HSDPA - Achievable DL Bearer by its activity factor.
This is the bitrate that the user experiences at a location when there is queuing delay on the cell.
The rate drops to zero as the HSDPA load on the cell approaches 100%.
This is the total amount of data in a service session (bits) divided by the mean service time per user
on the cell (seconds), assuming there is no queuing delay.
This is similar to the HSDPA - Effective Cell Service Rate (Unloaded) array, except that the mean
service time per user on the cell is increased because of queuing delay. As the offered HSDPA
load on the cell approaches 100%, the queuing delay approach infinity and the Effective Cell
Service Rate (Loaded) drops to zero.
22
Array and Report Descriptions
HSUPA Arrays
Here are brief definitions of the HSUPA-specific arrays:
The cell which requires the minimum HSUPA transmit power in order to satisfy the Eb/No
requirement.
For each pixel, this represents the amount by which the target Eb/No is overachieved on the Best
UL Cell, assuming that the terminal is transmitting at full power.
The maximum output power of the terminal minus the Eb/No margin.
This array is dependent on the standard deviations of shadow fading specified for the clutter types.
For each pixel, this array shows the probability of coverage depending on the Eb/No calculated on
the Best UL Cell, assuming that the terminal is transmitting at full power. If the specified standard
deviation is zero, then there are only three probabilities: 0% if the requirement is not satisfied; 50%
if the requirement is satisfied exactly; and 100% if the requirement is exceeded.
This is a thresholded version of the HSUPA-UL Coverage Probability and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the HSDPA - UL Coverage
Probability array. A value of "Yes" means that the uplink coverage probability satisfies the coverage
reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
The purpose of this array is to provide a composite coverage plot for the HSUPA bearers of a
Terminal/ Carrier/ Indoor/ Service/ Speed. The array shows the highest priority HSUPA bearer with
acceptable uplink coverage, that is, with UL Coverage Probability satisfying the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
This array provides additional information about the 'HSUPA Achievable UL Bearer' array (which
shows the achievable bearer at each location), by showing the cell that provides that connection.
23
ASSET 10.0.2 Technical Reference Guide
This is the user bitrate of the 'HSUPA - Achievable UL Bearer'. It is similar to the 'HSUPA -
Achievable UL Bearer' array but instead of giving the bearer name at each location, it gives the
bearer's user rate.
It displays information about which cells are "covering" each pixel. A set of lines is drawn between
all possible serving cells to the simulation pixel where the mouse cursor is located. For pixels with
more than one covering cell, the line thickness increases proportionally.
This array enables you to identify distant servers so that you can optimise your network design by
lowering, moving or reducing the pilot power of problematic sites.
24
Array and Report Descriptions
As with all arrays, you can customise the display properties by double-clicking on the array
heading.
LTE Arrays
This is an overview of some of the LTE arrays generated by the Simulator in ASSET.
Most of them have a dependency on terminal type because body loss and terminal antenna gain
are always included in the link budget.
Many of them depend on whether the terminal is considered to be indoor or outdoor. Indoor arrays
use the in-building parameters for the clutter type at each pixel (that is, indoor loss and indoor
shadow fading standard deviation). Indoor terminals are always taken to be slow moving.
Coverage arrays can be displayed even if no snapshots have been run, but you should note that in
these circumstances the arrays represent coverage in an unloaded network. To obtain coverage
arrays for a loaded network, you must run some snapshots or define the loads manually. The key
purpose of running snapshots is to provide measures of system load.
Arrays for coverage tend to have a weak dependence on the number of snapshots run, and the
arrays change little after a relatively small number of snapshots have been performed (10s of
snapshots in most cases). This is because only a small number of snapshots are needed to get an
idea of the "Mean UL Interference Level (dB)" and "Downlink Load (%)" on each cell.
Here is an example of the LTE arrays you can generate on the Map View when using the
Simulator:
Example of the Simulator LTE arrays appearing in the Map View Data Types
25
ASSET 10.0.2 Technical Reference Guide
The following LTE array descriptions describe the types of array that are available from the
Simulator, and show their dependencies. Most terms (such as 'Indoor') are self-explanatory, but
here are clarifications for some of the terms used:
Term Descriptions
Fading The array depends on the standard deviation of shadow fading for the clutter type.
Reliability The array depends on the coverage reliability threshold specified in the Sim Display
Thresholds tab of the Array Settings dialog box.
Tip: You can try changing this parameter and then redraw the array without running
any more snapshots.
Snapshots/Load Levels The existence, accuracy, and results of the array are dependent on the number of
snapshots done or the load levels defined in the Site Database.
These are the downlink losses of the Best DL Cell by RSRP and the Nth Best DL Cell by RSRP,
respectively. They represent average values and are therefore calculated with fades of 0 dB.
Line of Sight
The Line of Sight array is available for predictions generated by the Enhanced Macrocell model, the
MYRIAD model, or the Volcano model.
This is a two-valued array (LOS, non-LOS) for the Best Server by RSRP. The indoor instance is
non-LOS everywhere. Here is an example:
26
Array and Report Descriptions
This array reports the cell that provides the highest (and Nth highest) RSRP for the terminal, based
on the Best RSRP & Nth Best RSRP arrays.
These arrays take into account the cell-specific Cell Range Extension parameter (RSRP Offset), if it
has been set on the Thresholds subtab of the LTE Params tab for a cell in the Site Database. If it
has ben set, then the determination of the server is based on the Nth Best RSRP adjusted by CRE
arrays.
These are the highest (and Nth highest) RSRP levels. They represent average values and are
therefore calculated with fades of 0dB.
These arrays ignore the cell-specific Cell Range Extension parameter (RSRP Offset).
These are the Nth highest RSRP levels after taking into account the cell-specific Cell Range
Extension parameter (RSRP Offset), which can be set on the Thresholds subtab of the LTE
Params tab for a cell in the Site Database.
They represent average values and are therefore calculated with fades of 0 dB.
CRE Delta
This is the difference in area coverage due to the cell-specific Cell Range Extension parameter
(RSRP Offset).
This is the probability that the Best Server (by RSRP) satisfies the RSRP requirement specified on
the terminal type. This probability depends on the standard deviation of shadow fading for the
clutter type at the pixel. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied; 50% if the requirement is
satisfied exactly; and 100% if the requirement is exceeded.
27
ASSET 10.0.2 Technical Reference Guide
RSRP Coverage OK
This is a thresholded version of the RSRP Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the RSRP Coverage Probability
array. A value of "Yes" means that the RSCP coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
Number of RSRP OK
This is the number of covering cells with a satisfactory RSRP. A cell is counted as having a
satisfactory RSRP if its RSRP coverage probability meets the coverage reliability level specified in
the Sim Display Thresholds tab of the Array Settings dialog box.
These are the highest (and Nth highest) RSRQ values. They represent average values and are
therefore calculated with fades of 0dB.
This is the probability that the Best Server (by RSRP) satisfies the RSRQ requirement specified on
the terminal type. This probability depends on the standard deviation of shadow fading for the
clutter type at the pixel. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied; 50% if the requirement is
satisfied exactly; and 100% if the requirement is exceeded.
RSRQ Coverage OK
This is a thresholded version of the RSRQ Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the RSRQ Coverage Probability
array. A value of "Yes" means that the RSRQ coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
Number of RSRQ OK
This is the number of covering cells with a satisfactory RSRQ. A cell is counted as having a
satisfactory RSRQ if its RSRQ coverage probability meets the coverage reliability level specified in
the Sim Display Thresholds tab of the Array Settings dialog box.
DLRS SNR
This is the highest DLRS SNR level. This does not include the Inter-cell interference (that is, Best
RSRP levels divided by the thermal noise). It represents an average value and is therefore
calculated with fades of 0dB.
28
Array and Report Descriptions
DLRS SINR
This is the highest DLRS SINR level. This includes the Inter-cell interference (that is, Best RSRP
levels divided by the thermal noise plus Inter-cell Interference). it represents an average value and
is therefore calculated with fades of 0dB.
This is the total received noise contributed by all sources, including co-channel serving and non-
serving cells, adjacent channel interference, and thermal noise). It represents average values and
is therefore calculated with fades of 0dB.
This is required for the Achievable UL Bearer array. It is similar to the Best Server (by RSRP) array
but includes all bearers' dependencies and shows the server which provides the connection for an
UL bearer at a given location/pixel.
Achievable UL Bearer
The purpose of this array is to provide a combined coverage plot for the UL bearers of the service.
The array shows the highest priority bearer with acceptable UL coverage, that is, with UL coverage
probability meeting the reliability level specified in the Sim Display Thresholds tab of the Array
Settings dialog box.
This shows the UL TTI Bundling gain for the serving Cell for Achievable UL Bearer.
This is the best UL SINR level assuming that the terminal transmits at the power controlled power
level, that is, the power required to satisfy the UL Bearer SINR requirement. This is in essence a
combined required SINR level (defined on the bearers and modified accordingly if AAS architecture
is employed) plot of UL Bearers.
29
ASSET 10.0.2 Technical Reference Guide
UL Req TX power
This is the required UL TX power of the terminal to serve the achievable UL bearer at a given
pixel/location.
UL Transmission Mode
This shows the achievable UL AAS mode at a given pixel location. The supported UL transmission
modes are Single Antenna, SU-MIMO Diversity, SU-MIMO Multiplexing and MU-MIMO. This array
should be used in conjunction with the Achievable UL Bearer array to determine the achievable UL
bearer and transmission mode at a given pixel/location.
UL MIMO Order
This shows the number of TX and RX antennas for the UL Transmission Mode with the category
“M×N” indicating that there are M transmit elements and N receive elements. Only the most
common values of M and N are reported (1,2,4,8). All other cases are grouped together in the
category “Other”.
This shows the maximum required number of UL Resource Blocks, for the highest achievable UL
bearer, over which the terminal can transmit (spread its power) without losing coverage of the
bearer. The required number of RBs is restricted by the employed carrier bandwidth and the ICIC
settings.
This is required for the Achievable DL Bearer array. It is similar to the Best Server (by RSRP) array,
and shows the server which provides the connection for a given UL bearer at a given location/pixel.
Achievable DL Bearer
The purpose of this array is to provide a combined coverage plot for the UL bearers of the service.
The array shows the highest priority bearer with acceptable UL coverage, that is, with UL coverage
probability meeting the reliability level specified in the Sim Display Thresholds tab of the Array
Settings dialog box.
30
Array and Report Descriptions
This shows the DL TTI Bundling gain for the serving Cell for Achievable DL Bearer.
DL Traffic/Ctrl SINR
This is the highest PDSCH and PDCCH SINR level. This represents an average value and is
therefore calculated with fades of 0dB.
DL Traffic SINR
This is the highest PDSCH SINR level. This represents an average value and is therefore
calculated with fades of 0dB.
DL Ctrl SINR
This is the highest PDCCH SINR level. This represents an average value and is therefore
calculated with fades of 0dB.
DL BCH/SCH SINR
This is the highest P-SCH+S-SCH/PBCH SINR level. This represents an average value and is
therefore calculated with fades of 0dB.
DL MCH SINR
This is the highest PMCCH SINR level. This represents an average value and is therefore
calculated with fades of 0dB.
DL Transmission Mode
This shows the achievable DL AAS mode at a given pixel location. The supported DL transmission
modes are Single Antenna, SU-MIMO Diversity, SU-MIMO Multiplexing and MU-MIMO. This array
should be used in conjunction with the Achievable UL Bearer array to determine the achievable UL
bearer and transmission mode at a given pixel/location.
31
ASSET 10.0.2 Technical Reference Guide
DL MIMO Order
This shows the number of TX and RX antennas for the DL Transmission Mode with the category
“M×N” indicating that there are M transmit elements and N receive elements. Only the most
common values of M and N are reported (1,2,4,8). All other cases are grouped together in the
category “Other”.
This shows the DL Beamforming SINR gain (which is the same as DL Beamforming Signal Gain)
for a terminal that is served by DL beamforming. Assuming that no angular spread values are set
in the clutter categories, then a terminal served by adaptive-beamforming will show a single gain
value across the cell. A terminal served by switched-beamforming will show stronger beamforming
gain in the directions corresponding to the main lobes of the switched-beam patterns.
This shows the UL Beamforming SINR gain for a connection that is served by UL beamforming. A
terminal served by UL adaptive-beamforming will usually have a higher UL SINR gain due to
beamforming when using the Maximise SINR method instead of the Maximise Signal method. If
switched-beamforming is used instead, then the beamforming method has much less of an effect
and plots for the two methods will be almost identical, although the Maximise Signal method will be
faster to evaluate.
This is the application layer data rate that a user can achieve at a location/pixel using the highest
achievable DL bearer and the employed SU\MU-MIMO settings. This also takes into account the
SINR to Error rate mapping defined on the DL bearers as well the reduction in data rate due to
service overheads (accounting for higher layer headers, and so on).
This is the effective data rate that a user can achieve at a location/pixel using the highest
achievable DL bearer and the employed SU\MU-MIMO settings. This also takes into account the
SINR to error rate mapping defined on the DL bearers but not the service overheads.
32
Array and Report Descriptions
This is the peak data rate that a user can achieve at a location/pixel using the highest achievable
DL bearer and the employed SU/MU-MIMO settings without taking into account the SINR to error
rate mapping defined on the DL bearers and service overheads.
This is the application throughput that a user can achieve at a location using the highest achievable
DL bearer and the employed SU/MU-MIMO and ICIC settings. This also takes into account the
SINR to error rate mapping defined on the DL bearers and service overheads. The reported value
is not limited by the service MBR. The DL Achievable Throughput (Application) is achievable over
the available RBs in the present ICIC bandwidth partition (cell centre or cell edge).
This is the effective throughput that a user can achieve at a location using the highest achievable
DL bearer and the employed SU/MU-MIMO and ICIC settings. This also takes into account the
SINR to error rate mapping defined on the DL bearers but not the service overheads. The reported
value is not limited by the service MBR. The DL Achievable Throughput (Effective) is achievable
over the available RBs in the present ICIC bandwidth partition (cell centre or cell edge).
This is the peak throughput that a user can achieve at a location using the highest achievable DL
bearer and the employed SU/MU-MIMO and ICIC settings. The peak throughput is reported without
taking into account the SINR to error rate mapping defined on the DL bearers and service
overheads. The reported value is not limited by the service MBR. The DL Achievable Throughput
(Peak) is achievable over the available RBs in the present ICIC bandwidth partition (cell centre or
cell edge).
This is the application layer DL cell throughput displayed over the Best Server (by RSRP) area. The
presence of this array requires the Simulator to run in the snapshot mode as it requires the cell
throughput results gathered at the end of the snapshots. The effects of SU/MU-MIMO settings as
well as SINR to Error rate mapping and service overheads are taken into consideration.
33
ASSET 10.0.2 Technical Reference Guide
This is the effective DL cell throughput displayed over the Best Server (by RSRP) area. The
presence of this array requires the Simulator to run in the snapshot mode as it requires the cell
throughput results gathered at the end of the snapshots. The effects of SU/MU-MIMO settings and
SINR to Error rate mapping (but not service overheads) are taken into consideration.
This is the peak DL cell throughput displayed over the Best Server (by RSRP) area. The presence
of this array requires the Simulator to run in the snapshot mode as it requires the cell throughput
results gathered at the end of the snapshots. The effects of SU/MU-MIMO settings and SINR to
Error rate mapping (but not service overheads) are taken into consideration.
This is DL Multi User Gain for cells assigned with the Proportional Fair scheduler.
This is the application layer data rate that a user can achieve at a location/pixel using the highest
achievable UL bearer and the employed SU/MU-MIMO settings. This also takes into account the
SINR to Error rate mapping defined on the DL bearers as well the reduction in data rate due to
service overheads (accounting for higher layer headers, and so on).
This is the effective data rate that a user can achieve at a location/pixel using the highest
achievable UL bearer and the employed SU/MU-MIMO settings. This also takes into account the
SINR to error rate mapping defined on the UL bearers but not the service overheads.
This is the peak data rate that a user can achieve at a location/pixel using the highest achievable
UL bearer and the employed SU/MU-MIMO settings without taking into account the SINR to error
rate mapping defined on the UL bearers and service overheads.
34
Array and Report Descriptions
This is the application throughput that a user can achieve at a location using the highest achievable
UL bearer and the employed SU/MU-MIMO and ICIC settings. This also takes into account the
SINR to error rate mapping defined on the UL bearers and service overheads. The reported value
is not limited by the service MBR. The UL Achievable Throughput (Application) is achievable over
the RBs that have been calculated by the UL RBs Required for Coverage array.
This is the effective throughput that a user can achieve at a location using the highest achievable
UL bearer and the employed SU/MU-MIMO and ICIC settings. This also takes into account the
SINR to error rate mapping defined on the UL bearers but not the service overheads. The reported
value is not limited by the service MBR. The UL Achievable Throughput (Effective) is achievable
over the RBs that have been calculated by the UL RBs Required for Coverage array.
This is the peak throughput that a user can achieve at a location using the highest achievable UL
bearer and the employed SU/MU-MIMO and ICIC settings. The peak throughput is reported without
taking into account the SINR to error rate mapping defined on the UL bearers and service
overheads. The reported value is not limited by the service MBR. The UL Achievable Throughput
(Peak) is achievable over the RBs that have been calculated by the UL RBs Required for Coverage
array.
This is the application layer UL cell throughput displayed over the Best Server (by RSRP) area. The
presence of this array requires the Simulator to run in the snapshot mode as it requires the cell
throughput results gathered at the end of the snapshots. The effects of SU/MU-MIMO settings as
well as SINR to Error rate mapping and service overheads are taken into consideration.
This is the effective UL cell throughput displayed over the Best Server (by RSRP) area. The
presence of this array requires the Simulator to run in the snapshot mode as it requires the cell
throughput results gathered at the end of the snapshots. The effects of SU/MU-MIMO settings and
SINR to Error rate mapping (but not service overheads) are taken into consideration.
35
ASSET 10.0.2 Technical Reference Guide
This is the peak UL cell throughput displayed over the Best Server (by RSRP) area. The presence
of this array requires the Simulator to run in the snapshot mode as it requires the cell throughput
results gathered at the end of the snapshots. The effects of SU/MU-MIMO settings and SINR to
Error rate mapping (but not service overheads) are taken into consideration.
This is UL Multi User Gain for cells assigned with the Proportional Fair scheduler.
This shows the time-average number of UL Resource Blocks required by the highest achievable UL
bearer in order to achieve the service GBR. In case of SU-MIMO Spatial Multiplexing the value is
reduced by the UL SM Rate Gain. The UL RBs Used (Time-Average) at a location is always less
than or equal to the UL RBs Required for Coverage.
Coverage Balance
The purpose of this array is to provide a composite uplink/downlink coverage plot for a service. The
uplink is deemed to have coverage if any of the uplink bearers on the service have UL Coverage
Probability meeting the coverage reliability level specified in the Sim Display Thresholds tab of the
Array Settings dialog box. Similarly, the downlink is deemed to have coverage if any of the downlink
bearers on the service have DL Coverage Probability meeting the specified coverage reliability
level.
All Servers
This is not a true array, since it is sensitive to the location of mouse cursor. It displays information
about which cells are "covering" each pixel based on the "All Servers" display properties (either
RSRP or RSRQ). A set of lines is drawn between all possible serving cells to the simulation pixel
where the mouse cursor is located. For pixels with more than one covering cell, the line thickness
increases proportionally.
36
Array and Report Descriptions
This arrays shows the division of the Best Server (by RSRP) area into 'Cell Centre' and 'Cell Edge'
based on the selected Cell Centre - Cell Edge threshold on the Thresholds subtab of the LTE
Params tab. The array as only two values, Cell Centre and Cell Edge, depicting the classification of
service area.
The available Cell Centre - Cell Edge threshold settings are RSRP (dBm) and Relative RSRP (dB).
The latter represents the difference between the RSRP levels of the best and 2nd best server (by
RSRP) at a given location/pixel.
Cell Interferers
DL ABS percentage
This is the DL percentage of Almost Blank Subframes as specified for each cell for Cell Centre and
Cell Edge in LTE Params in the Site Database, for the Best Server by RSRP.
UL ABS percentage
This is the UL percentage of Almost Blank Subframes as specified for each cell for Cell Centre and
Cell Edge in LTE Params in the Site Database, for the Best Server by RSRP.
37
ASSET 10.0.2 Technical Reference Guide
5G Arrays
This is an overview of some of the 5G arrays generated by the Simulator in ASSET.
Most of them have a dependency on terminal type because body loss and terminal antenna gain
are always included in the link budget.
Many of them depend on whether the terminal is considered to be indoor or outdoor. Indoor arrays
use the in-building parameters for the clutter type at each pixel (that is, indoor loss and indoor
shadow fading standard deviation). Indoor terminals are always taken to be slow moving.
Coverage arrays can be displayed even if no snapshots have been run, but you should note that in
these circumstances the arrays represent coverage in an unloaded network. To obtain coverage
arrays for a loaded network, you must run some snapshots or define the loads manually. The key
purpose of running snapshots is to provide measures of system load.
Arrays for coverage tend to have a weak dependence on the number of snapshots run, and the
arrays change little after a relatively small number of snapshots have been performed (10s of
snapshots in most cases). This is because only a small number of snapshots are needed to get an
idea of the "Mean UL Interference Level (dB)" and "Downlink Load (%)" on each cell.
Here is an example of the 5G arrays you can generate on the Map View when using the Simulator:
Example of the Simulator 5G arrays appearing in the Map View Data Types
38
Array and Report Descriptions
The following array descriptions describe the types of array that are available from the Simulator,
and show their dependencies. Most terms (such as 'Indoor') are self-explanatory, but here are
clarifications for some of the terms used:
Term Descriptions
Fading The array depends on the standard deviation of shadow fading for the clutter type.
Reliability The array depends on the coverage reliability threshold specified in the Sim Display
Thresholds tab of the Array Settings dialog box.
Tip: You can try changing this parameter and then redraw the array without running
any more snapshots.
Snapshots/Load Levels The existence, accuracy, and results of the array are dependent on the number of
snapshots done or the load levels defined in the Site Database.
These are the downlink losses for the best control beam of the Best Server and the Nth Best Server
by SS-RSRP They represent average values and are therefore calculated with fades of 0 dB.
These are the downlink losses for the best traffic beam of the Best Server and the Nth Best Server
by SS-RSRP. They represent average values and are therefore calculated with fades of 0 dB.
Line of Sight
This is a two-valued array (LOS, non-LOS) for the Best Server by SS-RSRP. The indoor instance is
non-LOS everywhere. The array is available with Enhanced Macrocell, MYRIAD and Volcano
propagation model predictions.
This array reports the cell that provides the highest (and Nth highest) SS-RSRP for the terminal,
based on the Best SS-RSRP & Nth Best SS-RSRP arrays. If Cell Range Extension cell-specific SS-
RSRP offsets have been set in the Site DB, then the determination of the server is based on the
Nth Best SS-RSRP adjusted by CRE arrays.
39
ASSET 10.0.2 Technical Reference Guide
These are the highest (and Nth highest) SS-RSRP levels. They represent average values and are
therefore calculated with fades of 0 dB.
These are Nth highest SS-RSRP levels after accounting for the Cell Range Extension cell-specific
SS-RSRP offset. They represent average values and are therefore calculated with fades of 0 dB.
CRE Delta
This is the difference in area coverage due to the Cell Range Extension cell-specific SS-RSRP
offset. This difference is the result of the comparison of the Best Server by SS-RSRP with and
without the effect of the Cell Range Extension cell-specific SS-RSRP offset.
This is the probability that the Best Server by SS-RSRP satisfies the SS-RSRP requirement
specified on the terminal type. This probability depends on the standard deviation of shadow fading
for the clutter type at the location. If this standard deviation has been set to zero, then there are
only three possible coverage probabilities: 0% if the requirement is not satisfied; 50% if the
requirement is satisfied exactly; and 100% if the requirement is exceeded.
SS-RSRP Coverage OK
This is a thresholded version of the SS-RSRP Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the SS-RSRP Coverage
Probability array. A value of ‘Yes’ means that the SS-RSRP coverage probability meets the
coverage reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
Number of SS-RSRP OK
This is the number of covering cells with a satisfactory SS-RSRP. A cell is counted as having a
satisfactory SS-RSRP if its SS-RSRP coverage probability meets the coverage reliability level
specified in the Sim Display Thresholds tab of the Array Settings dialog box.
Cell Interferers
This is the number of Cell Interferers. That is the number of cells, excluding the serving cell,
providing an SS-RSRP value within x dB of the SS-RSRP value of the serving cell or higher than
the SS-RSRP value of the serving cell. The x dB threshold is relative and specified at the Simulator
Wizard.
40
Array and Report Descriptions
SS-RSRQ
This is the SS-RSRQ value for the Best Server by SS-RSRP. It represents an average value and is
therefore calculated with fades of 0 dB.
This is the SS-RSRQ value for the Nth Best Server by SS-RSRP. It represents an average value
and is therefore calculated with fades of 0 dB.
This is the probability that the Best Server by SS-RSRP satisfies the SS-RSRQ requirement
specified on the terminal type. This probability depends on the standard deviation of shadow fading
for the clutter type at the location. If this standard deviation has been set to zero, then there are
only three possible coverage probabilities: 0% if the requirement is not satisfied; 50% if the
requirement is satisfied exactly; and 100% if the requirement is exceeded.
SS-RSRQ Coverage OK
This is a thresholded version of the SS-RSRQ Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the SS-RSRQ Coverage
Probability array. A value of ‘Yes’ means that the SS-RSRQ coverage probability meets the
coverage reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
Number of SS-RSRQ OK
This is the number of covering cells with a satisfactory SS-RSRQ. A cell is counted as having a
satisfactory SS-RSRQ if its SS-RSRQ coverage probability meets the coverage reliability level
specified in the Sim Display Thresholds tab of the Array Settings dialog box.
SS-SNR
This is the SS-SNR level as calculated by (94) for the Best Server by SS-RSRP. This does not
include the interference (i.e. Best SS-RSRP levels divided by the thermal noise). It represents an
average value and is therefore calculated with fades of 0 dB.
SS-SINR
This is the SS-SINR level as calculated by (96) for the Best Server by SS-RSRP. This includes the
Inter-cell interference (i.e. Best SS-RSRP levels divided by the thermal noise plus Inter-cell
Interference). It represents an average value and is therefore calculated with fades of 0 dB.
41
ASSET 10.0.2 Technical Reference Guide
CSI-RSRP
This is the CSI-RSRP level for the Best Server by SS-RSRP. It represents an average value and is
therefore calculated with fades of 0 dB.
This is the received signal strength of the PDSCH for the Nth Best Server by SS-RSRP.
This is the beam index of the best SSB beam of the Best Server by SS-RSRP.
This is the beam index of the best traffic beam of the Best Server by SS-RSRP.
This represents average values and is therefore calculated with fades of 0 dB.
This is required for the Achievable UL Bearer array. It is similar to Best Server by SS-RSRP array
but includes all bearers’ dependencies and shows the server which provides the connection for the
UL bearer at a given location.
Achievable UL Bearer
The purpose of this array is to provide a combined coverage plot for the UL bearers of the service.
The array shows the best bearer with acceptable UL coverage, i.e. with UL coverage probability
meeting the reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
42
Array and Report Descriptions
This is the achieved UL SINR level assuming that the terminal transmits at the power controlled
power level, i.e. when the terminal is using the Achievable UL Bearer. Uplink is powered controlled
and the terminal transmits just at the level required to meet the SINR of the bearer. The achieved
SINR is equal to the bearer SINR requirement after all MIMO adjustments.
This shows how much the maximum UL TX power of the terminal exceeds the UL Req TX power at
a given location.
UL Req TX Power
This is the required UL TX power of the terminal to serve the achievable UL bearer at a given
location.
UL Transmission Mode
This shows the achievable UL Advanced Antenna Systems (AAS) mode at a given location. The
supported UL transmission modes are ‘Single Antenna’, ‘SU-MIMO Diversity’, ‘SU-MIMO
Multiplexing’ and ‘MU-MIMO’. This array can be used in conjunction with the Achievable UL Bearer
array to determine the achievable UL bearer and transmission mode at a given location.
UL MIMO Order
This shows the number of TX and RX antennas for the UL Transmission Mode with the category
“MxN” indicating there are M transmit elements and N receive elements. Only the most common
values of M and N are reported (i.e. 1,2,4,8). All other cases are grouped together in the category
“Other”.
This shows the maximum required number of UL Resource Blocks, for the highest achievable UL
bearer, over which the terminal can transmit (spread its power) without losing coverage of the
bearer. The required number of RBs is restricted by the carrier bandwidth and the ICIC settings.
43
ASSET 10.0.2 Technical Reference Guide
This is required for the Achievable DL Bearer array. It is similar to Best Server by SS-RSRP array
and shows the server which provides the connection for the DL bearer at a given location.
Achievable DL Bearer
The purpose of this array is to provide a combined coverage plot for the DL bearers of the service.
The array shows the best bearer with acceptable DL coverage, i.e. with DL coverage probability
meeting the reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
PDSCH SINR
This is the highest PDSCH SINR level. This represents an average value and is therefore
calculated with fades of 0 dB.
PDCCH SINR
This is the highest PDCCH SINR level. This represents an average value and is therefore
calculated with fades of 0 dB.
DL Transmission Mode
This shows the achievable DL Advanced Antenna Systems (AAS) mode at a given location. The
supported DL transmission modes are ‘Single Antenna’, ‘SU-MIMO Diversity’, ‘SU-MIMO
Multiplexing’ and ‘MU-MIMO’. This array can be used in conjunction with the Achievable DL Bearer
array to determine the achievable DL bearer and transmission mode at a given location.
DL MIMO Order
This shows the number of TX and RX antennas for the DL Transmission Mode with the category
“MxN” indicating there are M transmit elements and N receive elements. Only the most common
values of M and N are reported (i.e. 1,2,4,8). All other cases are grouped together in the category
“Other”.
44
Array and Report Descriptions
This is the application throughput that a user can achieve at a location using the highest achievable
DL bearer and the employed SU/MU-MIMO and ICIC settings. This also takes into account the
SINR to Error Rate mapping defined on the DL bearers and service overheads. The reported value
is not limited by the service MBR.
This is the effective throughput that a user can achieve at a location using the highest achievable
DL bearer and the employed SU/MU-MIMO and ICIC settings. This also takes into account the
SINR to Error Rate mapping defined on the DL bearers but not the service overheads. The reported
value is not limited by the service MBR.
This is the peak throughput, at physical layer, that a user can achieve at a location using the
highest achievable DL bearer and the employed SU/MU-MIMO and ICIC settings. The peak
throughput is reported without taking into account the SINR to Error Rate mapping defined on the
DL bearers and service overheads. The reported value is not limited by the service MBR.
This is DL Multi User Gain for cells with Proportional Fair scheduler.
45
ASSET 10.0.2 Technical Reference Guide
This is the application throughput that a user can achieve at a location using the highest achievable
UL bearer and the employed SU/MU-MIMO settings. This also takes into account the SINR to Error
Rate mapping defined on the UL bearers and service overheads. The reported value is not limited
by the service MBR. The UL Achievable Throughput (Application) is achievable over the RBs that
have been calculated by the UL RBs Required for Coverage array.
This is the effective throughput that a user can achieve at a location using the highest achievable
UL bearer and the employed SU/MU-MIMO settings. This also takes into account the SINR to Error
Rate mapping defined on the UL bearers but not the service overheads. The reported value is not
limited by the service MBR. The UL Achievable Throughput (Effective) is achievable over the RBs
that have been calculated by the UL RBs Required for Coverage array.
This is the peak throughput, at physical layer, that a user can achieve at a location using the
highest achievable UL bearer and the employed SU/MU-MIMO settings. The peak throughput is
reported without taking into account the SINR to Error Rate mapping defined on the UL bearers and
service overheads. The reported value is not limited by the service MBR. The UL Achievable
Throughput (Peak) is achievable over the RBs that have been calculated by the UL RBs Required
for Coverage array.
This is UL Multi User Gain for cells with Proportional Fair scheduler.
This shows the time-average number of UL Resource Blocks required by the highest achievable UL
bearer in order to achieve the service GBR. In case of SU-MIMO Spatial Multiplexing the value is
reduced by the UL SM Rate Gain. The UL RBs Used (Time-Average) at a location is always less
than or equal to the UL RBs Required for Coverage.
46
Array and Report Descriptions
Coverage Balance
The purpose of this array is to provide a composite uplink/downlink coverage plot for a service.
The uplink is deemed to have coverage if any of the uplink bearers on the service have UL
Coverage Probability meeting the coverage reliability level specified in the Sim Display Thresholds
tab of the Array Settings dialog box. Similarly, the downlink is deemed to have coverage if any of
the downlink bearers on the service have DL Coverage Probability meeting the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
All Servers
This is not a true array, since it is sensitive to the location of mouse cursor. It displays information
about which cells are ‘covering’ each pixel based on the ‘All Servers’ display properties (either
RSRP or RSRQ). A set of lines is drawn between all possible serving cells to the simulation pixel
where the mouse cursor is located. For pixels with more than one covering cell, the line thickness
increases proportionally.
Wi-Fi Arrays
This is an overview of some of the Wi-Fi arrays generated by the Simulator in ASSET.
Most of them have a dependency on terminal type because body loss and terminal antenna gain
are always included in the link budget.
Many of them depend on whether the terminal is considered to be indoor or outdoor. Indoor arrays
use the in-building parameters for the clutter type at each pixel (that is, indoor loss and indoor
shadow fading standard deviation). Indoor terminals are always taken to be slow moving.
Coverage arrays can be displayed even if no snapshots have been run, but you should note that in
these circumstances the arrays represent coverage in an unloaded network. To obtain coverage
arrays for a loaded network, you must run some snapshots or define the loads manually. The key
purpose of running snapshots is to provide measures of system load.
Arrays for coverage tend to have a weak dependence on the number of snapshots run, and the
arrays change little after a relatively small number of snapshots have been performed (10s of
snapshots in most cases). This is because only a small number of snapshots are needed to get an
idea of the "Mean UL Interference Level (dB)" and "Downlink Load (%)" on each cell.
47
ASSET 10.0.2 Technical Reference Guide
Here is an example of the Wi-Fi arrays you can generate on the Map View when using the
Simulator:
Example of the Simulator Wi-Fi arrays appearing in the Map View Data Types
The following array descriptions describe the types of array that are available from the Simulator,
and show their dependencies. Most terms (such as Indoor) are self-explanatory. Here are some
clarifications for some of the terms:
Term Descriptions
Fading The array depends on the standard deviation of shadow fading for the clutter type.
Reliability The array depends on the coverage reliability threshold specified in the Sim
Display Settings tab of the Array Settings dialog box.
Important: You can try changing this parameter and then redraw the array
without running any more snapshots.
Snapshots/Load Levels The existence, accuracy, and results of the array are dependent on the number of
snapshots done or the load levels defined in the Site Database.
These are the downlink losses of the Best Server and the Nth Best Server. They represent average
values and are therefore calculated with fades of 0 dB.
This is a two-valued array (LOS, non-LOS). The indoor instance is non-LOS everywhere. The array
is available for predictions from the Enhanced Macrocell, MYRIAD and Volcano propagation
models.
48
Array and Report Descriptions
This is the cell that provides the (highest and Nth highest) DL RSS for the terminal.
These are the highest (and Nth highest) DL RSS levels. They represent average values and are
therefore calculated with fades of 0 dB.
This is the probability that the Best Server (by DL RSS) satisfies the RSS requirement specified on
the terminal type. This probability depends on the standard deviation of shadow fading for the
clutter type at the location. If this standard deviation has been set to zero, then there are only three
possible coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is
satisfied exactly, and 100% if the requirement is exceeded.
Wi-Fi: DL RSS OK
This is a thresholded version of the DL RSS Coverage Probability array and has just two values
(Yes/No). It has the advantage of being quicker to calculate than the DL RSS Coverage Probability
array. A value of “Yes” means that the DL RSS coverage probability meets the coverage reliability
level specified in the Sim Display Thresholds tab of the Array Settings dialog box.
This is the number of covering cells with a satisfactory DL RSS. A cell is counted as having a
satisfactory RSS if its DL RSS coverage probability meets the coverage reliability level specified in
the Sim Display Thresholds tab of the Array Settings dialog box.
This is the application layer DL cell throughput, displayed over the Best Server (by DL RSS) area.
The presence of this array requires the Simulator to run in the snapshot mode, as it requires the
cell throughput results gathered at the end of snapshots.
49
ASSET 10.0.2 Technical Reference Guide
This is the application layer UL cell throughput, displayed over the Best Server (by DL RSS) area.
The presence of this array requires the Simulator to run in the snapshot mode, as it requires the
cell throughput results gathered at the end of snapshots.
All Servers
This is not a true array, since it is sensitive to the location of mouse cursor. It displays information
about which cells are "covering" each pixel based on the "All Servers" display properties). A set of
lines is drawn between all possible serving cells to the simulation pixel where the mouse cursor is
located. For pixels with more than one covering cell, the line thickness increases proportionally.
This is the serving cell identity. Primarily, cell ranking is based on the carrier/cell layer priorities
which are specified on the Service. Secondarily, cells of a specific technology type are ordered by
Signal Strength (GSM: RSS; UMTS: RSCP; LTE: RSRP; 5G: SS-RSRP; Wi-Fi: DL RSS). The
terminal’s requirements must be met for the respective technology (GSM: Receiver RSS Sensitivity;
UMTS: Required RSCP, Ec/Io and Pilot SIR; LTE: Required RSRP, RSRQ and BCH/SCH SINR;
5G: Required SS-RSRP, SS-RSRQ and SS-SINR; Wi-Fi: Required Signal Strength). The array has
a dependency on Cell Load Levels, due to the interference-related terminal requirements.
The display thresholds can be specified for each technology type individually in the Sim Display
Thresholds tab of the Array Settings dialog box.
This is the technology type of the serving cell as determined in the Composite: Tech Type array.
The display thresholds can be specified for each technology type individually in the Sim Display
Thresholds tab of the Array Settings dialog box.
This is the combination (not ordered list) of achieved technology types. It is a superset of the
Composite: Tech Type array.
This is the carrier (UMTS, LTE, 5G or Wi-Fi), or the cell layer (GSM) of the serving cell, as
determined in the Composite: Best Server array.
50
Array and Report Descriptions
Most arrays have a dependency on the terminal type because terminal antenna gain is always
included in the linkloss.
Many arrays depend on whether the terminal is taken to be indoor or outdoor. Indoor arrays use in-
building parameters for the clutter type at the given pixel.
Here is an example of the Fixed WiMAX arrays you can generate on the Map View when using the
Simulator:
Example of the Fixed WiMAX arrays appearing in the Map View Data Types
Achievable UL Bearer
This array shows the highest priority UL bearer with acceptable UL coverage. The array is based
on the UL CINR value.
Achievable DL Bearer
This array shows the highest priority DL bearer with acceptable DL coverage (based on the CINR).
DL RSS
This array represents the DL RSS at a given point. Calculated with fades of 0dB as it represents an
average value.
51
ASSET 10.0.2 Technical Reference Guide
This array represents the service area of each WiMAX sector based on DL RSS.
CPE Azimuth
This array displays the CPE azimuth required in order to connect to the best server (server with the
highest signal strength).
DL Loss
This array represents the lowest DL losses. Calculated with fades of 0dB as it represents an
average value.
DL CINR
This is the best C/(I+N) in the DL. The C/(I+N) is calculated by taking into account the signal
strength from the reference base station and signal strength from all interfering base stations.
UL Required TX Power
This array displays the UL required TX power for a given receiver sensitivity (specified in the Site
Database).
UL CINR
These are thresholded versions of their corresponding arrays. They have just two values (Yes/No),
and have the advantage of being quicker to calculate than their corresponding arrays.
A value of “Yes” means that the probability meets the reliability level specified in the Sim Display
Thresholds tab of the Array Settings dialog box.
Most arrays have a dependency on terminal-type because body loss and terminal antenna gain are
always included in the linkloss.
Many arrays depend on whether the terminal is considered to be indoor or outdoor. Indoor arrays
use the in-building parameters for the clutter type at each pixel (that is, indoor loss and indoor
shadow-fading standard deviation). Indoor terminals are always assumed to be slow moving.
Coverage arrays can be drawn even if no snapshots have been run, but the user should note that
the arrays then refer to coverage in an unloaded system. To obtain coverage arrays for a loaded
system the user must run some snapshots. Remember that the key purpose of running snapshots
is to provide measures of system load.
52
Array and Report Descriptions
Arrays for coverage tend to have a weak dependence on the number of snapshots run, and the
arrays change little after a relatively small number of snapshots have been performed (10s of
snapshots in most cases). This is because only a small number of snapshots are needed to get an
idea of the average noise rise and average DL traffic power on each cell.
Here is an example of the Mobile WiMAX arrays you can generate on the Map View when using the
Simulator:
Example of the Mobile WiMAX arrays appearing in the Map View Data Types
DL Loss
The downlink losses of the Best Server by Preamble RSS. They represent average values and are
therefore calculated with fades of 0 dB.
This is the cell that provides the highest Preamble RSS for the terminal.
Preamble CINR
This is the best preamble CINR. It represents an average value and hence is calculated using
fades of 0dB.
Sectors on the same site are not considered as interferers because such sectors will be allocated
different segments.
53
ASSET 10.0.2 Technical Reference Guide
These arrays display the highest (and Nth highest) Preamble RSS levels. They represent average
values and are therefore calculated with fades of 0dB.
Note: The preamble power is the TX power for the cell boosted by the preamble boosting factor.
Both these parameters are specified in the Site Database.
Preamble RSS OK
This array has two values (Yes/No). A value of “Yes” means that the RSCP coverage probability
(the probability that the Preamble RSS satisfies the RSS requirement in the Terminal type dialog
box) meets the coverage reliability criteria specified in the Sim Display Thresholds tab of the Array
Settings dialog box. The coverage probability depends on the standard deviation of shadow fading
for the clutter type at the pixel.
This array displays the cell with the highest UL AMC CINR.
This array displays the cell with the highest UL OPUSC CINR.
This is the cell that provides the highest CINR at a given pixel.
UL Achievable Bearer
This array shows the combined coverage plot for the UL bearers of the service. The array shows
the highest priority bearer with acceptable UL coverage, that is, where the UL coverage probability
meets the reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
54
Array and Report Descriptions
UL AMC CINR
This array displays the UL CINR in the AMC zone. For the uplink CINR analysis, the signal from the
connected terminal is the server signal and the signal from all other terminals are the interferers.
The power transmitted by the terminal can be assumed to be the power specified in the terminal
type dialog. The UL CINR represents an average value (with fades set to 0dB).
UL OPUSC CINR
This array displays the UL CINR in the OPUSC zone. For the uplink CINR analysis, the signal from
the connected terminal is the server signal and the signal from all other terminals are the
interferers. The power transmitted by the terminal can be assumed to be the power specified in the
terminal type dialog. The UL CINR represents an average value (with fades set to 0dB).
UL PUSC CINR
The calculation of the UL PUSC CINR assumes that the terminal is transmitting over all available
data subcarriers.
This is the cell that provides the highest CINR at a given pixel, for the AMC zone.
This is the cell that provides the highest CINR at a given pixel, for the FUSC zone.
This is the cell that provides the highest CINR at a given pixel, for the OPUSC zone.
This is the cell that provides the highest CINR at a given pixel, for the PUSC zone.
55
ASSET 10.0.2 Technical Reference Guide
DL Achievable Bearer
This array shows the combined coverage plot for the DL bearers of the service. The array shows
the highest priority bearer with acceptable DL coverage, that is, where the DL coverage probability
meets the reliability level specified in the Sim Display Thresholds tab of the Array Settings dialog
box.
DL AMC CINR
This array displays the DL CINR in the AMC zone. For the downlink CINR analysis, the CINR is
calculated by taking into account the level from the connected BS (reference base station) as
server and the level from all other sites as interferers. The CINR represents an average value (with
fades set to 0dB).
DL FUSC CINR
DL OPUSC CINR
This array displays the DL CINR in the OPUSC zone. For the downlink CINR analysis, the CINR is
calculated by taking into account the level from the connected BS (reference base station) as
server and the level from all other sites as interferers. The CINR represents an average value (with
fades set to 0dB).
DL PUSC CINR
This array displays the worst interferer at each pixel. The pixel ownership is determined by the Best
Server by DL AMC CINR array.
This array displays the worst interferer at each pixel. The pixel ownership is determined by the Best
Server by DL FUSC CINR array.
56
Array and Report Descriptions
This array displays the worst interferer at each pixel. The pixel ownership is determined by the Best
Server by DL OPUSC CINR array.
This array displays the worst interferer at each pixel. The pixel ownership is determined by the Best
Server by DL PUSC CINR array.
Dependencies: Carrier
This array displays the azimuth that the directional CPE should point to in order to connect to the
best server.
UL Required TX Power
This array displays the minimum UL required TX power for a given receiver sensitivity (specified in
the Site Database).
The throughput arrays display the information displayed in the Simulator throughput report in a
graphical format. The throughput for a given sector is presented within the region specified by the
Best Server by Preamble RSS array. The throughput is summed for all services.
57
ASSET 10.0.2 Technical Reference Guide
In each pixel, the failure rate is the proportion of attempted terminals that failed to make a
connection. It is calculated as a percentage as follows:
Failure Rate (%) = 100 * (Failed Terminals) / (Attempted Terminals)
The accuracy of the result at a pixel is limited by the number of overall attempts made at the pixel.
For example, if only one attempt has been made, the result will either be 0% or 100%. The Failure
Rate array therefore provides a rough visualisation of the problem areas of the network.
This array shows connection successes and failures in a single plot. The value shown at a pixel is
determined by the last terminal that was attempted there, regardless of which snapshot it related to.
So if the last terminal that was attempted at a pixel succeeded, then the pixel will be shown as a
success, regardless of how many terminals may have failed there in previous snapshots. Likewise,
if the last terminal at a pixel failed, then the pixel will be shown as a failure, regardless of how many
terminals succeeded there in previous snapshots. So in theory, locations that are more likely to
serve terminals in a snapshot rather than fail them are more likely to appear as successes than
failures, and vice versa.
A terminal can fail for multiple reasons. When this occurs, only a single reason is reported when
writing a value at the pixel. This will be the most dominant reason based on a hard-coded ranked
list of the failure reasons for the terminal. For example, coverage failures rank more highly than
capacity failures, since there is no purpose in indicating a capacity failure for a terminal if it does not
have coverage. For more detailed information, see the specialist document mentioned in Array and
Report Descriptions on page 9.
This array shows the speed of the terminal in the corresponding Failure Reason array. This array
can be useful because some failure reasons are affected by the speed of the mobile (for example,
bearers have speed-dependent signal to noise requirements). It is available for all technologies
except GSM and Fixed WiMAX and Wi-Fi (these do not have speed-dependent bearer
requirements).
The value shown at a pixel is determined by the last terminal that was attempted there, regardless
of the snapshot in which it was attempted.
58
Array and Report Descriptions
Simulation Reports
This section provides descriptions of some of the network performance reports that can be
generated from the Simulator (when it is run in the snapshot mode).
Note: In addition to this section, there are specialist documents containing more detailed
descriptions of the outputs and algorithms used in the Simulator. For information on how you can
obtain these documents, please see Static Simulation Algorithms and Outputs on page 109.
Note: Probability percentages can add up to more than 100%. This is because a connection can
fail for multiple reasons simultaneously.
59
ASSET 10.0.2 Technical Reference Guide
For UMTS networks there are potentially 36 different resource types but only those that have been
defined will be displayed.
60
Array and Report Descriptions
Pilot Power (dBm) This value shows the downlink pilot power that you have set per cell.
Sync Channel Power (dBm) This is the total time-averaged synchronisation channel power. The
primary and secondary synchronisation channel powers that the user
specifies in the site dialog are peak powers.
The total time-averaged sync channel power is given by:
Total_Sync_Power = 0.1 x Peak_Primary_Sync_Power + 0.1 x
Peak_Secondary_Sync_Power
Note: All powers in this formula are in Watts.
For UMTS networks there are 36 different resource types but only those that have been defined will
be displayed.
61
ASSET 10.0.2 Technical Reference Guide
Percentage of Blocks Due to DL The percentage of the blocks that were due, in part, to Downlink
Resource Channel Limit Reached. Resource Channel Limit Reached.
Percentage of Blocks Due to The percentage of the blocks that were due, in part, to Downlink Eb/No
Downlink Eb/No (Capacity) Capacity.
Percentage of Blocks Due to Noise The percentage of the blocks that were due, in part, to Noise Rise.
Rise
Notes:
The blocking reports are only available if the corresponding checkbox is selected in the
Simulator Wizard.
The statistics given are the reasons for failure to the ’best’ server.
For UMTS networks there are potentially 36 different resource types but only those that
have been defined will be displayed.
Note: Probability percentages can add up to more than 100%. This is because a connection can
fail for multiple reasons simultaneously.
62
Array and Report Descriptions
63
ASSET 10.0.2 Technical Reference Guide
Note: Probability percentages can add up to more than 100%. This is because a connection can
fail for multiple reasons simultaneously.
64
Array and Report Descriptions
Notes:
The blocking reports are only available if the corresponding checkbox is selected in the
Simulator Wizard
The statistics given are the reasons for failure to the ’best’ server.
65
ASSET 10.0.2 Technical Reference Guide
Mean IP Packet Queuing Average time a packet waits (in seconds) in a queue before being transmitted.
Delay (s)
Mean Total IP Packet The total IP packet transmission delay in seconds is:
Transmission Delay (s)
Mean IP packet transmit time + Mean IP packet queuing delay
Mean Gross User This is defined by the following equation:
Throughput (kbit/s)
Mean gross user throughput =
Physical layer packet available bits X No. physical layer packets / IP packet
transmit time
Mean Gross Sector This is defined by the following equation:
Throughput (kbit/s)
Mean gross sector throughput =
Physical layer packet available bits X No. physical layer packets / (no. slots
used X slot time)
Mean Net Sector This is defined by the following equation:
Throughput (kbits/s)
Mean net sector throughput =
(IP packet arrival rate X (1 - %timed out packets/100) X mean packet size
(bits)
Mean Packets Timed Out This is the percentage of packets that are not transmitted due to queuing
delays that exceeded the maximum allowed value.
Throughput Reports
The Throughput Report contains the following information:
66
Array and Report Descriptions
LTE Reports
Here is the list of LTE reports you can generate when using the Simulator:
Note: In addition to this section, there are specialist documents containing more detailed
descriptions of the outputs and algorithms used in the Simulator. For information on how you can
obtain these documents, please see Static Simulation Algorithms and Outputs on page 109.
Composite Report
Dependencies: Service
This report provides a summary of each service in terms of 'Mean Attempted', 'Mean Served' and
'Mean Failed' terminals. The 'Contributions to Failure' section lists the possible reasons with their
percentages that contribute to terminals not being served.
Terminals can fail to connect for multiple reasons so the failure reason percentages can sum to
more than 100%.
Dependencies: Service
This provides a breakdown of the 'Composite Report' and lists the per cell failure reasons for 'Mean
Failed' terminals. Failure reasons and their respective percentages that contribute to terminals not
been served are logged against each cell and per service. For more detailed descriptions, see LTE
Cell Failure Report on page 70.
67
ASSET 10.0.2 Technical Reference Guide
Dependencies: Carrier
This report provides the per carrier DL power/resource consumption information for each cell.
The breakdown of each cell 'Max Power' is given in terms of 'Fixed Channels Power' and 'Traffic &
Control Power'. 'Fixed Channels Power' includes the power consumed by DL Signals and Control
channels (DLRS, SCH, BCH, and PMCCH). 'Traffic & Control Power' includes the power consumed
by the PDSCH and PDCCH. In addition, the resource consumption is logged individually for Cell
Centre (CC) and Cell Edge (CE) bandwidth partitions (that is, 'CC Load (%)' and 'CE Load (%)').
Two extra columns show how much of the load is using beamforming: CC Load (Beamforming) (%)
and CE Load (Beamforming) (%). These beamforming load values are a subset of the existing load
values. For example, is a cell is serving all CC users using beamforming, then "CC Load" will equal
the "CC Load (Beamforming)". The beamforming load is summed over all the beamforming
antennas on the cell.
These loads represent the respective resource consumption from the total/available CC and CE
resources and can be applied to the Site Database to be used further in creating arrays by running
the Simulator in the 'Use levels specified in Site Database' mode. It is important to remember that
CE loads are only applicable for the Soft Frequency Reuse and Reuse Partitioning ICIC schemes.
When '***' appears in the report columns, this indicates cells not employing the ICIC schemes or
configured in a way that results in either a zero CC or CE bandwidth.
Dependencies: Carrier
This report provides the per carrier UL interference level and resource consumption information for
each cell. UL Interference levels and resource consumptions are logged individually for CC and CE
bandwidth partitions, that is, 'CC Interference Level (dB)', 'CE Interference Level (dB)', 'CC Load
(%)' and 'CE Load (%)', respectively. The interference levels can be applied to the Site Database
and further used in creating arrays by running the Simulator in the 'Use levels specified in Site
Database' mode. It is important to remember that CE loads and interference levels are only
applicable for the Soft Frequency Reuse and Reuse Partitioning ICIC schemes.
When '***' appears in the report columns, this indicates cells not employing the ICIC schemes or
configured in a way that results in either a zero CC or CE bandwidth.
Dependencies: Service
These two reports provide the summary of per cell offered and served throughput for a given
service. Offered throughput of a cell is independent of service type (RT/NRT) and always calculated
as the 'Maximum-MBR' rate of the service multiplied by 'Mean number of Attempts' whereas the
served throughput depends on service type (RT/NRT) as well as the employed scheduling
schemes. First the 'Minimum-GBR' demands of terminals are fulfilled, and if resources are still
available to allocate, RT terminals are upgraded to serve their 'Maximum-MBR' demand. Hence,
the served throughput for terminal configured with an RT service can be anything between the
'Minimum-GBR' and the 'Maximum-MBR' demand.
A summary of offered and served throughputs are presented for 'Peak' 'Application' and 'Effective'
throughputs. In addition, these three offered and served throughputs are reported for the CC and
CE areas of the cells which are governed by the 'Cell Centre - Cell Edge threshold' settings in the
Site Database.
68
Array and Report Descriptions
These two reports provide the breakdown of per cell served peak throughputs for each service. The
breakdown is given in terms of service area (CC/CE) as well as the served peak throughput by
each bearer in the respective CC and CE regions.
Dependencies: Service
These two reports provide the breakdown of per cell served effective throughputs for each service.
The breakdown is given in terms of service area (CC/CE) as well as the served effective throughput
by each bearer in the respective CC and CE regions.
These two reports provide the breakdown of per cell served application throughputs for each
service. The breakdown is given in terms of service area (CC/CE) as well as the served application
throughput by each bearer in the respective CC and CE regions.
UL Beamformer Report
This report gives the angular distribution of UL SINR beamforming gain for all the beamformers in
the simulation. Note that if a cell has multiple antennas, or is using an ICIC scheme where the
carrier bandwidth has been split into cell-centre and cell-edge partitions, then this simulator will
have a beamformer for each combination of antenna and carrier partition. Values for the UL SINR
beamforming gain are reported at a predetermined set of azimuthal angles with respect to the
serving antenna, with the angles measured clockwise from North and incremented in 5 degree
steps. By selecting a row of these values, Excel can be used to produce a radar plot (i.e. polar plot)
of the UL SINR beamforming gain.
DL Beamformer Report
This report gives the angular distribution of DL interfering traffic power gain for all the beamformers
in the simulation. Note that if a cell has multiple antennas, or is using an ICIC scheme where the
carrier bandwidth has been split into cell-centre and cell-edge partitions, then this simulator will
have a beamformer for each combination of antenna and partition. The values in the report take
into account the proportion of DL load due to users served by DL beamforming. As the proportion
of beamformed load decreases to zero, the overall power gain approaches unity. The values are
reported at a predetermined set of azimuthal angles with respect to the serving antenna, with the
angles measured clockwise from North and incremented in 5 degree steps. By selecting a row of
these values, Excel can be used to produce a radar plot (i.e. polar plot) of the overall DL interfering
traffic power gain.
69
ASSET 10.0.2 Technical Reference Guide
DL RSRP The RSRP requirement specified on the terminal type is not satisfied.
DL RSRQ The RSRQ requirement specified on the terminal type is not satisfied.
DL BCH/SCH SINR The BCH/SCH SINR requirement specified on the terminal type is not
satisfied.
UL SINR The terminal cannot meet the SINR requirement of the UL bearer,
even if the terminal transmits at maximum power.
DL SINR The terminal cannot meet the SINR requirement of the DL bearer.
DL Capacity The cells have insufficient DL available resources (power/RBs) to
meet the SINR requirement of the DL bearer.
UL Capacity The cells have insufficient UL available resources (power/RBs) to
meet the SINR requirement of the UL bearer.
User Limit The cell has reached the limit specified by its '# of Scheduled Users'
parameter.
No Valid Connection Scenarios An incorrect or conflicting network set-up has resulted in terminals not
being served. For example, this may happen if a modulation scheme
on the cell is not supported by the terminal, or carriers and antennas
are not assigned to the cells.
No Pathloss Data No pathloss data is available for the pixels/region.
70
Array and Report Descriptions
5G Reports
Here is the list of 5G reports you can generate when using the Simulator:
Note: In addition to this section, there are specialist documents containing more detailed
descriptions of the outputs and algorithms used in the Simulator. For information on how you can
obtain these documents, please see Static Simulation Algorithms and Outputs on page 109.
5G - Composite Report
Dependencies: Service
This report provides the summary of each service in terms of ‘Mean Attempted’, ‘Mean Served’ and
‘Mean Failed’, terminals. The ‘Contributions to Failure’ section lists the possible reasons, as
explained in section 4.2, and their percentages that contribute to terminals not being served.
Terminals can fail to connect for multiple reasons so the failure reason percentages can sum to
more than 100%.
Dependencies: Service
This provides a breakdown of the ‘Composite Report’ and lists the per cell failure reasons for ‘Mean
Failed’ terminals. Failure reasons and their respective percentages that contribute to terminals not
being served are logged against each cell and per service.
This report provides the UL noise rise level and UL load information for each traffic beam on each
cell. The UL load summed over all beams on a cell will not exceed 100%. For each cell, the highest
per-beam noise rise can be applied to the Site Database (since there is only a single noise rise
value stored for each cell in the database).
71
ASSET 10.0.2 Technical Reference Guide
This report provides the DL load level and DL traffic (PDCCH and PDSCH) power for each traffic
beam on each cell. The DL load summed over all beams on a cell will not exceed 100%. For each
cell, the total DL load (summed over all traffic beams) can be applied to the Site Database.
Throughput Reports
The available throughput reports are tiered at Peak, Effective and Application level, and the generic
relation between the levels is given by:
Dependencies: Service
These reports provide the per cell average user throughputs for each service. The peak, effective
and application user throughputs are reported.
Dependencies: Service
These composite reports provide the summary of per cell offered and served throughput for a given
service. Offered throughput of a cell is calculated as the MBR rate of the service increased by the
service overhead and multiplied by ‘Mean number of Attempts’. First the GBR demands of
terminals are attempted and if resources are still available to allocate, terminals are upgraded to
serve potentially up to their MBR demands. Summary of throughputs are presented for ‘Peak’ (at
physical layer), ‘Effective’ and ‘Application’ levels.
These CA reports provide the summary of served throughput for a given service processed at the
logical Intra-gNodeB CA-group level, for carrier-aggregated cells belonging to the same gNodeB.
These throughputs are reported separately for SC (Single Carrier) connections and CA (Carrier
Aggregation) connections.
These CA reports provide the summary of served throughput for a given service processed at the
logical Inter-gNodeB CA-group level, for carrier-aggregated cells belonging to multiple gNodeBs.
These CA reports provide the summary of served throughput per cell for a given service. The Total
cell throughputs are separated for SC (Single Carrier) connections, CA Intra (Intra-gNodeB Carrier
Aggregation) connections and CA Inter (Inter-gNodeB Carrier Aggregation) connections. Summary
of throughputs are presented for ‘Peak’ (at physical layer), ‘Effective’ and ‘Application’ levels.
72
Array and Report Descriptions
These reports provide the breakdown of per cell served peak, at physical layer, throughputs for
each service. The breakdown is given in terms of served peak throughput by each bearer.
These reports provide the breakdown of per cell served effective throughputs for each service. The
breakdown is given in terms of served effective throughput by each bearer.
These reports provide the breakdown of per cell served application throughputs for each service.
The breakdown is given in terms of served application throughput by each bearer.
Wi-Fi Reports
Here is a summary of the reports specific to Wi-Fi that you can generate when using the Simulator:
Dependencies: Service
This report provides the summary of each service in terms of Offered, Attempted, Served and
Failed, terminals. The Contribution to Failure section lists the possible reasons, and their
percentages that contribute to terminals not being served. Terminals can fail to connect for multiple
reasons so the failure reason percentages can sum to more than 100%.
Dependencies: Service
This provides a breakdown of the Wi-Fi - Composite Report and lists the per cell failure reasons for
Failed terminals. Failure reasons and their respective percentages that contribute to terminals not
being served are logged against each cell and per service.
Dependencies: Service
These reports provide the breakdown of per cell served throughputs for each service.
73
ASSET 10.0.2 Technical Reference Guide
74
Prediction and Array File Management System
Files relating to created predictions and arrays contain data that can be freshly regenerated at any
time, but, as this process takes time, it is more efficient to store the files on the disk every time they
are created, and manage them as a cache of precalculated data.
Therefore, in ENTERPRISE, the concept behind the storage of these files is that they are stored on
disk and remain stored, even if they become 'invalid' due to changes to the cell parameters or
locations. The major benefit of this is that they can be reused whenever they become 'valid' again.
It is evident from the above approach that, on some occasions, the disk might become full and
consist of many unwanted files.
For this reason, these files are automatically managed within ENTERPRISE by a caching
algorithm, which can dispose of unwanted files on the basis of specific criteria, such as the elapsed
time since the file was last loaded.
As a vital input to this algorithm, you must set the maximum disk space for the storage of these
files, for the prediction folder and output array folder, which are specified on the Shared Data
Directories tab of the Project Settings dialog box.
Overview of Algorithm
The 'maximum disk space' settings, as described above, are stored in configuration files in the root
of the Prediction folder and the Output Array folder.
The file management algorithm is designed to manage the files as a cache, using a ‘weighting’
function to determine which files are to be removed whenever the cache exceeds its maximum
space. In order to monitor this, a statistics file is updated at the end of every prediction/array file
creation session.
The weighting function takes the following factors into consideration for each file (most important
first) :
The elapsed time since the file was last used
The amount of time that was needed to perform the calculation
The number of times the file has been loaded
If a "disk full" error occurs during file creation, then the file management system may be
automatically invoked early to try to provide some space for the file that has just been calculated. If
this fails to provide enough space then a "disk full" error is written to the message log.
Note: The file management algorithm only monitors files generated by ENTERPRISE, and ignores
any other files.
There is some separate information regarding third party integration/interaction with ENTERPRISE.
For information on this, see ENTERPRISE Interfaces on page 111.
75
ASSET 10.0.2 Technical Reference Guide
To determine a file’s position in this prioritised list, the following formula is used:
Position = ( Now – Last Loaded Time ) × modifier
A file with a large 'position' has more chance of being deleted than one with a small 'position'.
Modifier Calculation
1. The time taken to create the file is recorded and will result in an initial modifier as follows:
0-10s 1.2
10s-20s 1.15
20s-40s 1.1
40s-1.5m 1.05
1.5m-2.5m 1
2.5m-5m 0.95
5m-10m 0.9
10m-20m 0.85
20m-40m 0.8
40m+ 0.75
2. The number of times a file has been loaded is recorded and then used to adjust the
modifier, as follows:
0 +0.05
1-5 0
5-10 -0.03
10-20 -0.06
20-40 -0.09
40-80 -0.12
80-160 -0.15
160-320 -0.18
76
Prediction and Array File Management System
320-640 -0.21
640+ -0.24
Note: All the above values are stored in the configuration file in the root of the Prediction folder and
the Output Array folder, and can be modified by your administrator if necessary.
77
ASSET 10.0.2 Technical Reference Guide
78
2g and 2.5g Algorithms
This section contains information about the algorithms and calculations that ASSET uses in relation
to 2g and 2.5g network planning.
For information on the GSM Simulator algorithms and outputs, please see Static Simulation
Algorithms and Outputs on page 109.
The table can store the following four values for any pair of cells A and B (relating to regions where
A is the best server):
Co-channel Area The area* served by cell A that would be affected by interference if A
and B were assigned the same carrier.
Adjacent Channel Area The area* served by cell A that would be affected by interference if A
and B were assigned adjacent carriers.
Co-channel Traffic The amount of traffic* served by cell A that would be affected by
interference if A and B were assigned the same carrier.
Adjacent Channel Traffic The amount of traffic* served by cell A that would be affected by
interference if A and B were assigned adjacent carriers.
The values for area (in km 2) are obtained by averaging the probability of interference over the
region where A is the best server. The average is taken over all pixels in the appropriate coverage
array.
For traffic, the value to be averaged is the probability of interference × the traffic (in mE) at that
pixel. Thus it is necessary to have a traffic array available to make this calculation.
The probability of interference at a given pixel is calculated using a standard statistical technique
based on a C/I signal threshold value and a standard deviation. The assumption is that a difference
in signal level between server and interferer exactly equal to the threshold value would give rise to
a 50% chance of co-channel interference.
By default, a -18dB offset is used for the adjacent channel interference, relative to the co-channel
interference. This means that if, for example, the co-channel C/I threshold value is set at 9dB, a
signal difference of -9dB between server and adjacent channel interferer would give rise to a 50%
chance of adjacent channel interference. The C/A offset can be modified in the Array Settings
dialog box.
79
ASSET 10.0.2 Technical Reference Guide
All signal differences are converted into probabilities of interference. The following graph displays
the spread of probabilities for both C/I and C/A based on the default Interference Weights. Here,
the C/I signal threshold value is 9dB, using a standard deviation of 7.78dB.
C/I C/A
100%
Interference (%)
Proportion of
75%
50%
25%
0%
-20 -10 0 10 20 30 40
Signal Difference (dB)
Examples of Interference Table files can be found, along with a description of the file format, in the
ENTERPRISE Technical Reference Guide.
Worst Connection C/Ic Determines the co-channel C/I levels for all of the possible interfering
frequencies that may be used by the MS-BTS connection.
Each pixel presents the worst C/Ic level and frequency.
Worst Connection C/Ia Determines the adjacent channel C/I levels for all of the possible
interfering frequencies that may be used by the MS-BTS connection.
Each pixel presents the worst C/Ia level and frequency.
Worst Connection C/(Ic+Ia) Determines the combined co-channel/adjacent channel C/I levels for
all of the possible interfering frequencies that may be used by the MS-
BTS connection.
Each pixel presents the worst C/I level and frequency.
Average Interference C/Ic Sums the co-channel C/I levels for all possible interfering frequencies
and presents the average C/Ic level.
Average Interference C/Ia Sums the adjacent channel C/I levels for all possible interfering
frequencies and presents the average C/Ia level.
Average Interference C/(Ic_Ia) Sums the combined co-channel and adjacent C/I levels for all possible
interfering frequencies and presents the average C/(Ic_Ia) level.
Worst Interference C/Ic For non-frequency hopping networks sums all of the co-channel C/I
levels for an interfering frequency.
Each pixel presents the total C/I level, server and interfering sub-cells
and interfering frequency.
80
2g and 2.5g Algorithms
Worst Interference C/Ia For non-frequency hopping networks sums all of the adjacent channel
C/I levels for an interfering frequency.
Each pixel presents the total C/I level, server and interfering sub-cells
and interfering frequency.
Note: The worst connection and the worst interferer calculations are the same in the case of a non-
frequency hopping network.
The Worst Connection Array calculates the C/I per connection, summing over all interferers, and
then selects the connection with the lowest C/I.
For: f 0
C / IW minC / I ( FH ) GFDIV ( n ), minC / I ( f i )
fi
For: f 0
C / IW minC / I ( fi )
fi
Where:
For the hopping frequency group in the serving sub-cell, a single C/I(FH) is calculated.
n
m * f * BER (C / I ( FH ) GFDIV (m)) BER (C / I ( fri ))
C / I AV BER 1 i 1
m* f n
81
ASSET 10.0.2 Technical Reference Guide
Where:
TRX FH
f
m , where TRX FH is the number of hopping TRX.
For the hopping frequency group in the serving sub-cell, a single C/I(FH) is calculated.
f
Note: The denominator in the equation above can never be zero ( and n cannot both be zero at
the same time). This is because ASSET does not allow you to set the total number of TRX
allocated to a sub-cell to zero, if at least one carrier layer is allocated.
The worst interfering frequency and its corresponding C/I are calculated as follows:
maxS IC ( K , f sw ).U ( K , f sw )
K
Where:
f
For each (non-hopping) carrier f1 in the serving sub-cell, C/I( i ) is calculated.
Where:
f
For each (non-hopping) carrier fi in the serving sub-cell, C/I( i ) is calculated.
82
2g and 2.5g Algorithms
-10 0.5000000000
-9 0.4880000000
-8 0.4650000000
-7 0.4300000000
-6 0.3880000000
-5 0.3500000000
-4 0.3200000000
-3 0.3000000000
-2 0.2700000000
-1 0.2500000000
0 0.2200000000
1 0.2000000000
2 0.1700000000
3 0.1500000000
4 0.1200000000
5 0.1000000000
6 0.0900000000
7 0.0780000000
8 0.0660000000
9 0.0550000000
10 0.0450000000
11 0.0370000000
12 0.0300000000
13 0.0260000000
14 0.0200000000
15 0.0150000000
16 0.0120000000
17 0.0080000000
18 0.0060000000
19 0.0040000000
20 0.0020000000
21 0.0007000000
22 0.0001000000
23 0.0000070000
24 0.0000004000
25 0.0000000100
26 0.0000000001
83
ASSET 10.0.2 Technical Reference Guide
27-45 0.0000000000
S SC
C / I (i ) N
S
K 1
IC ( K , i ).U ( K , i )
m
U ( K , i ) u (i, j ).L( K , j ).V ( K , j ). f (i )
j 1
1
u (i, j )
0
fi f j 0 fi f j 0
1 is used if , α is used if , and 0 is used otherwise.
Where:
C/I(i) = C/I ratio for frequency i
SSC(i) = Signal strength from frequency i for serving cell
i,j = A particular frequency
N = Number of interfering cells
n = Number of frequencies in serving cell
m = Number of frequencies in interfering cell K
SIC(K,i) = Signal strength from frequency i for interfering cell K
K = Interfering cell
L(K,j) = Load in interfering cell K on frequency j
V(K,j) = DTX factor in interfering cell K on frequency j
f (i) = Fractional loading for frequency i for interfering cell
α = Adjacent interference factor
84
2g and 2.5g Algorithms
The following graph shows the relationship between the Probability of Bit Error and the C/I:
1.0000000000
0 -2 6 14 22 30 38
-1
0.1000000000
0.0100000000
0.0010000000
Probability of Bit Error
0.0001000000
0.0000100000
0.0000010000
0.0000001000
0.0000000100
0.0000000010
0.0000000001
C/I (dB)
Bit Error Probability
BERAV(serving cell) is calculated as the average BER(i) for all frequencies in the cell:
m FH
BER(i)
BER AV (serving cell) i 1
m.x
m FH
x
nTRX
Where:
Note: If frequency diversity gain GFDIV(m) is enabled, you also need to add a given gain figure to the
hopping C/I. For more information on this, see the ASSET User Reference Guide.
85
ASSET 10.0.2 Technical Reference Guide
TRX FH
f
m
Where:
S SC
C / I (i ) N
S
K 1
IC ( K , i ).U ( K , i )
m
U ( K , i) u (i, j ).L( K , j ).V ( K , j )
j 1
1
u (i, j )
0
fi f j 0 fi f j 0
1 is used if , α is used if , and 0 is used otherwise.
P(i) = f(C/I(i))
P(i) is the Probability of interference, and is calculated from the cumulative normal distribution of
combined standard deviation of serving and interfering cell models.
C / I C2 I2
and
86
2g and 2.5g Algorithms
Interference Weights
100.00
Probabilit y %(C/ I)
90.00
Probabilit y %(C/ A)
80.00
70.00
Probabilty (%)
60.00
50.00
40.00
30.00
20.00
10.00
0.00
-20 -15 -10 -5 0 5 10 15 20 25 30 35 40
C/I (dB)
Search algorithms specialise in looking for solutions to problems that have too many possible
solutions to allow a simple solution. Advanced heuristic search algorithms use the algorithmic
equivalent of taking the path that “looks like the best one”. These algorithms use a 'cost' function to
determine the most desirable next state, which typically will be the state with the lowest cost.
ILSA initialises with a random frequency plan (unless the option is chosen to load the current plan
from the database). This means that for any two runs of ILSA, the results may not be the same.
Moreover, certain starting frequency plans can allow ILSA to make either more rapid initial
improvement or allow a much better plan to be found within a reasonable period of time.
ILSA (as its 'Local Search' name implies) reduces the number of options it has for new states
derived from a current state. ILSA can give special attention to areas of high cost within the network
(analogous to areas of high interference), temporarily ignoring lower cost areas. This allows ILSA to
make very rapid initial progress. For example, if ILSA is attempting to plan for a network requiring
60 carrier allocations, with 20 available carriers, and identifies a subset of 10 high cost carrier
allocations, then the maximum number of new states that ILSA needs to consider has been
reduced from 3.8*1025 to 6.1*1012.
Random changes can be made by ILSA if only low improvement rates are being achieved, or if a
dead end is reached. The algorithm monitors its own progress and will behave differently
depending on how quickly the cost is decreasing at a given time. This intelligent behaviour enables
it to continue finding improvements over long periods of time.
The principle behind ILSA's algorithm is that a single number (the cost) measures the effectiveness
of any particular frequency plan. The algorithm then tries to minimise the cost over the set of all
possible plans. The cost function measures how much interference exists in the network, and what
separations have been broken, while taking account of any user-specified 'importance' weightings
for different sub-cells.
87
ASSET 10.0.2 Technical Reference Guide
For a given frequency plan the value of the cost function is given by the formula:
Cost wi cij aij sij r i d i hi
i
f f j f f 1
j
j
j
i i j
Where:
hi = The handover count and intermodulation interference costs associated with allocation i
w(c ) w(c , c
1 1 2 )# TRX(c1 , c 2 )
Where:
c1 , c2
are sub-cells
TRAFFIC and
AREA are traffic and area percentages
88
2g and 2.5g Algorithms
T (c) and A(c) are traffic and area associated with sub-cell c
# TRX(c1 , c2 ) is the C/I or C/A separation count for all TRX combinations on sub-cells c1 , c2
NREQ
The total number of TS required for CS and GPRS traffic ( ) can then be determined using the
NCS( AV )
average Circuit Switched TS requirement and the channel occupation efficiency (e) as
follows:
NCS( AV ) is average (long term) number of TS required for Circuit Switched traffic (=
L CS )
N
The number of TRX required and GPRS are determined using the channel to transceiver map by
increasing the number of TRX from the result of the previous section until the number of available
N REQ
TS for traffic (NCS allocation) is equal to or greater than .
This section presents the calculation for the blocking for the current allocation of TRX for CS. It has
been assumed throughout that CS traffic will take precedence over GPRS traffic and therefore the
Grade of Service for CS will not be affected by the GPRS load.
89
ASSET 10.0.2 Technical Reference Guide
L
Calculate the blocking for the CS traffic given the traffic load ( CS ) for the current allocation of
TRX, using the selected Erlang table.
The GPRS data rate DR AV for the current allocation of TRX is determined by first calculating the
number of TS required for CS. The remaining TS are available for GPRS. That is:
DR AV L GPRS /(N.e)
Where:
e is the efficiency from the Channel Occupation table determined from N
Ncs ,NGPRS is the number of TS from the Channel Carrier Map for the current allocation of TRX
The table is stored in the database and you can edit the occupancy values.
100%
90%
80%
70%
TSL Occupancy (%)
60%
50%
40%
30%
20%
10%
0%
0
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
50
52
54
56
TSL
90
2g and 2.5g Algorithms
FCC Calculations
This section describes the algorithms used to calculate the data provided in the FCC report.
The Radial average terrain elevation is the average ground height mapped along a radial of
between 3 km and 16 km from the site. If the mapping data prevent this then it will not be calculated
and this will be flagged in the FCC report.
Note: Feature height data and clutter heights are ignored in the calculation.
The best available resolution of the map data is used for this calculation. If the best map data is
1000 m resolution then you will receive a warning noting that the map data is of insufficient
resolution for the FCC form.
The Used Antenna Height AAT (metre) is subject to some minimum values according to the FCC
category and, the ERP:
You will receive a warning if the Average Radial distance exceeds 40.2 km (79.1 km for Gulf of
Mexico cells).
The transmitting ERP for a cardinal radial is the radiated power in Watts taking into account the
antenna gain for the azimuth, the downtilt and the base station powers/losses.
Used ERPS
This is the value of the transmitting ERP which is used in the calculations, it is the Transmitting
ERP subject to certain minima.
91
ASSET 10.0.2 Technical Reference Guide
This will be calculated by finding the distance to the SAB for each degree by linear interpolation of
distance as a function of angle, hence dividing the area into triangular sectors, joining at the site.
The total area is then calculated by adding up the areas of each of the triangles.
32dBu Served D = 2.531 x Used Antenna Height(m) ^ 0.34 x Used ERP for Radial in Watts ^ 0.17
and
Subject to a minimum distance of 5.4 km
32dBu Unserved
Gulf of Mexico D = 6.895 x Used Antenna Height(m) ^ 0.30 x Used ERP for Radial (W) ^ 0.15
There is no minimum distance for this SAB
Frequency Calculations
Two frequency calculations are used when you create a Frequency Plan report.
The effective frequency re-use is an approximate indication of the quality of the hopping network.
It can be calculated for each sub-cell and also the average of these calculated to give a figure for
the network as a whole.
NF
REFF
N TRXH
Where:
NF is the total number of carriers available to hopping TRX on the sub-cell (note: this is not the MA
list length)
92
2g and 2.5g Algorithms
Frequency Load
The average frequency load is another approximate indication of the quality of the hopping network.
It can be calculated for each sub-cell and also the average of these calculated to give a figure for
the network as a whole.
N TRX
LFRACTION
N MA
E
LHW
N CSTS
Where:
NMA is the MA list length (that is, all carriers assigned to hopping carrier layers on the sub-cell)
E is the traffic that could be carried by the timeslots of hopping TRX on the sub-cell, at a user
E ErlangB (GoS, N CSTS )
specified Grade of Service (GoS), that is:
NCSTS is the total number of timeslots installed – this value is derived from the Carrier to Timeslot
map using NTRX.
93
ASSET 10.0.2 Technical Reference Guide
94
Packet Quality of Service Algorithms
This section details the Packet Quality of Service algorithms used in ASSET, and therefore explains
the associated reports generated by the QoS analysis.
The packet QoS analysis feature is a downlink cell level simulation, with 10 ms (single radio frame)
resolution. It is a trace-driven queuing simulation, the packet transmission delays through a cell are
modelled by a queuing system, which has a time-series of packet traffic offered to it. It is based on
the 'WWW Traffic Model' (see WWW Traffic Model on page 98) and multiple, prioritised services
can be specified.
The simulation is run for a calculated period of time, then the results are presented on the summary
page of the QoS Analysis wizard as a spread sheet and graphs. The results can be saved as an
Excel workbook containing graphs and spreadsheets, or the raw the raw data saved in text or
comma separated variable (csv) format. The graphs include the cumulative delay distributions of
the packet services on each cell, enabling you to view percentile delays.
The Excel workbook contains the following data per service, per carrier and, per cell:
Mean and standard deviations of the queuing delays
95th percentile delay
Confidence interval half width
Mean transmission time
Mean retransmission delay
Total transmission delay ( mean queuing delay+mean transmission time+mean
retransmission delay
Graphs for each cell and carrier giving the cumulative queuing delay probability
distributions
95
ASSET 10.0.2 Technical Reference Guide
You then need to run at least two snapshots of the simulation, although at least 100 snapshots are
recommended to produce statistically valid inputs to the QoS analysis. The simulation calculates
the mean blocking probability for each packet service type, on each carrier, on each cell in the
simulation in the simulation and the mean number of terminals connected to each cell, per carrier,
per service, and per bitrate. The mean blocking probability and mean number of terminals are then
used as inputs to the QoS analysis.
Preliminary Tests
Some conclusions can be deduced from the input data without running the simulation at all. These
are:
100% blocking on any service will result in delays building up to infinity
Zero traffic on all services will result in zero delays
Zero blocking on all services will result in zero delays
These results are immediately updated on the summary page of the QoS Analysis dialog box.
96
Packet Quality of Service Algorithms
The red line represents the mean number of users input from the simulation. The orange blocks
represent the number of users varying over time. The blue blocks represent the holding times of the
packet sessions produced by the traffic generator.
Little’s theorem gives us the relation between the arrival rate of packet sessions, the mean number
of users in the cell and their mean session holding time. Let:
The traffic generator therefore generates sessions with mean arrival rate calculated from the mean
number of users in the cell, and the mean session holding time, which is determined using the
WWW traffic model.
97
ASSET 10.0.2 Technical Reference Guide
This diagram shows packets from a source, which may be at either end of the link, but not both
ends simultaneously.
The session holding time is modelled implicitly by the number of events during the session.
Using the WWW traffic model, the mean holding time of a packet session is given by:
98
Packet Quality of Service Algorithms
Packet Model
The traffic generator uses the session arrival and WWW models to produce a list of packets for
each service type, for each cell, for each carrier, lasting the duration of the simulation. Each packet
is stamped with its arrival time at the cell, and also keeps a record of when it gets transmitted (its
departure time), and its randomly generated size. The packet service type lists are then merged
and sorted in arrival time order, to produce a single list of packets offered to the cell carrier:
In the diagram, the data contained in the packet boxes is the arrival time, the departure time and
the packet size. Initially, the packet’s departure time is set to be the same as its arrival time. The
departure time is updated each time step the packet is queued, until it is successfully transmitted.
A histogram of the generated traffic is displayed for each service on each cell and carrier in the
graphs tab of the QoS Analysis dialog box.
99
ASSET 10.0.2 Technical Reference Guide
To calculate the block size, the coding scheme allocated to each connection needs to be input from
the simulation (a mean number of MS connections per coding scheme, per bearer, per service
type, per sub-cell array will be required as input).
The block size can be inferred directly from the GPRS coding schemes, however, the following
mapping is used to calculate the block size for the first transmission attempt for the link adaptation
families:
A – 592 bits
B – 448 bits
C – 352 bits
There are no default BLER versus C/I curves for MCS – 7, 8 and 9. In the retransmission model,
the lower bitrates of the link adaptation families are used.
Precedence Class
Traffic is given a precedence of 1 (premium), 2 (standard) or 3 (best effort), with a precedence of 1
being highest. This precedence is similar to the service type priorities set in the QoS Analysis
wizard in ASSET, however the number of priorities needs to be restricted to three and different
service types can have equal priorities. The precedence class is used to prioritise the queues. For
more information, see Simulation Model for QoS Analysis on page 102.
Delay Class
GPRS has four different traffic classes. The following table shows the parameters that specify the
related QoS requirements:
100
Packet Quality of Service Algorithms
3g service types have traffic classes and are used in the packet service types dialog box in 3g to
set default www parameters and delay targets. In the ASSET QoS Analysis, the achieved 95th
percentile delay per service type, per carrier, per cell is compared with the target 95th percentile
delay.
Traffic class is used to prioritise the queues. For more information, see Simulation Model for QoS
Analysis on page 102.
Reliability Class
Applications can request different reliability classes, depending on their ability to handle corrupt and
duplicated blocks. The following table shows the reliability classes that can be selected:
1 10
2 10
3 10
Reliability is only considered in terms of the retransmission delay formula used in ASSET. This
uses the block error rate (BLER) to analytically calculate the retransmission delay for packet
services. A different approach is proposed for GPRS. The BLER can be calculated using the
Average Data Throughput per Timeslot vs Average Connection C/I curves. The formula is:
Throughput(C / I )
BLER(C / I ) 1
PeakDataRatePerSlot
Where:
BLER(C/I) = block error rate for the C/I achieved by the link.
Throughput(C/I) = throughput in kb/s read off the throughput per timeslot graph for the C/I
achieved by the link.
PeakDataRatePerSlot = peak rate per slot for the given coding scheme (the asymptote of
the throughput per timeslot graph).
The mean BLER over all the connections made per service type, per sub-cell is required as an
input from the simulation, and is reported in the QoS Analysis spreadsheet. Block errors also have
implications for the retransmission model. For more information, see Mean Retransmission Delay
on page 107.
Throughput Class
Applications can request different mean and peak throughputs, in order to request the desired
throughput for bursty IP traffic. Peak throughput applies to short intervals where the transfer rate is
at a maximum. Mean throughput describes the data transfer rate over an extended period of time,
which could involve many idle periods.
1 8 1 100
2 16 2 200
3 32 3 500
4 64 4 1 000
5 128 5 2 000
6 256 6 5 000
101
ASSET 10.0.2 Technical Reference Guide
7 512* - -
8 1024* 17 20 000 000
9 2048* 18 50 000 000
*Data rate only reachable 31 Best Effort
with UMTS or EDGE
In GPRS, the peak throughput is determined by the peak data rate per slot achievable by the
coding scheme, and the number of timeslots for which the MS is enabled. The peak throughput is
calculated as follows:
The coding scheme is identified by the bearer allocated to the connection during the simulation and
the maximum number of timeslots enabled on the MS will be a parameter set on the terminal type.
It is therefore possible to do a preliminary check prior to running the GPRS QoS analysis to
determine the peak throughput achievable for each service type on each sub-cell. The peak
throughput is reported in the QoS Analysis spreadsheet.
The mean throughput is logged as successful transmissions are made from the queue in the QoS
analysis, and are reported in the QoS Analysis spreadsheet.
102
Packet Quality of Service Algorithms
The cell capacity for each service is determined in each frame by generating a uniformly distributed
random number for each packet held in a queue. If the random number is greater than the blocking
probability, the packet starts transmission in that frame. If the random number is less than of equal
to the blocking probability, the packet is delayed in the queue until the next frame.
If the packet call mode is selected instead of the packet mode, connection admission decisions are
taken on a packet call, instead of an individual packet basis.
The service prioritisation is modelled in the simulator. All the packets awaiting transmission through
a cell are stored in a set of queues, one for each service type. A diagram of the queuing model
which would be used for three packet services being transmitted through a cell is shown here:
The rule is then applied that if admissions for each service are considered in priority order, and that
if any higher priority packets remain queued, no lower priority packets are admitted.
By the end of the simulation, the simulator will have produced a list of transmitted packets, each
stamped with its arrival and departure times from the cell.
A histogram of the queue length throughout the simulation is displayed for each service on each
cell and carrier in the graphs tab of the QoS Analysis dialog box.
When a terminal is connected and active, and there is no data to transmit, it uses a fundamental
and supplemental channel. For example, in between packets it uses a 1/8th rate fundamental
channel. This means that a terminal is still consuming transmit power between packet calls. The
session timeout parameter was added to prevent all the available power being consumed by
terminals transmitting at 1/8th rate, which would mean that no packet data could be transmitted.
The session timeout parameter is employed to kill any sessions which have been active for longer
than the session timeout, thus freeing up transmit power and allowing packets or packet calls to be
transmitted.
103
ASSET 10.0.2 Technical Reference Guide
1. Set the basic run length to ensure at least 1000 or 2000 packet admission requests are
made to the cell for each service.
2. Repeat the run (replicate) 5 times and calculate the confidence interval half width H5.
3. If the confidence interval is less than 10% of the mean delay, the desired accuracy has
been obtained.
The confidence interval half width H5 is calculated by repeating runs, using a different random
number stream for each run. Suppose we make k runs (replications), each generating m sample
values of the packet delay, Y.
Let Y1, Y2, Y3,…, Yk be the mean values of the k runs. The mean values are independent, since a
different random number stream was used for each run and, for a sufficiently large m, it will be
approximately normally distributed. The confidence interval half width Hi is then calculated from the
sample mean Y , and variance .
104
Packet Quality of Service Algorithms
Simulation Duration
This is calculated for each cell and carrier. The value depends on the parameters that you have set
for the services supported by that cell, and carrier, and the mean number of users of those services
input from the simulation. Using the same notation as the www traffic model section, plus the
following definitions:
(1)
The session arrivals are modelled as a Poisson process, and so the expected time until the
session arrives is:
(2)
Adding the duration of the session itself, the simulation duration is:
The data for these graphs will be collected by maintaining counts during the simulation. For
example, when a packet which has been queued for 4 frames is finally transmitted, the count in the
4 frame bin will be incremented. If there are N bins, each bin represents a delay of F frames, and c
is the count in a bin at the end of the simulation.
105
ASSET 10.0.2 Technical Reference Guide
0 0.F C0
1 1.F C1
2 2.F C2
... ... ...
N n.F Cn
... ... ...
N N.F CN
Mean delay
Standard
deviation
106
Packet Quality of Service Algorithms
Transmission time:
In order to calculate the average retransmission delay, the block error rate (BLER) at which the
system will operate is required as an input. A typical value of 10% is set as the default. You also
need to set the re-transmission timeout rt in units of radio frames. The BLER can then be used to
calculate the increase in traffic through the link caused by retransmission, and the mean or median
retransmission delay:
BLER
Percentage increase in traffic caused by retransmissions .100
1 BLER
107
ASSET 10.0.2 Technical Reference Guide
References
The following are documents that have been referred to throughout this chapter:
“Selection procedures for the choice of radio transmission technologies of the UMTS” TR
101 112 v3.2.0, p.34
“Quality of Service for Multimedia CDMA”, N. Dimitriou, R. Tafazolli, G. Sfikas, IEEE
Communications Magazine, July 2000
“Simulating Computer Systems”, M.H. MacDougall, MIT Press, p.114
“Introduction to Mathematical Statistics”, R.V. Hogg and A.T. Craig, Collier-Macmillan Ltd,
p.193
108
Static Simulation Algorithms and Outputs
The Simulator in ASSET enables you to perform static simulations for your network (depending on
your licence). The following technologies are supported:
GSM
UMTS (FDD)
CDMA2000
EV-DO
Fixed WiMAX
Mobile WiMAX
LTE
5G (NR)
Wi-Fi
Note: Technology-specific documents are available, containing comprehensive details of all the
algorithms and outputs related to the Simulator. If your company is registered to use the TEOCO
Resource Center (part of the Support area), and you know the login password, you can download
these specialist documents. After logging in, click the Reference Guides link (under Product
Documentation), select the relevant Version from the drop-down box, then select 'Static Simulation
Guide' from the Document Type drop-down box, and then click the Download link for the
appropriate technology.
109
ASSET 10.0.2 Technical Reference Guide
110
ENTERPRISE Interfaces
6 ENTERPRISE Interfaces
Along with the main ENTERPRISE tools, a number of COM interfaces have been developed to
provide a level of third-party integration with the ENTERPRISE suite. These interfaces cover a
number of key areas of functionality, including:
Propagation models (to enable third parties to create new models using the model SDK)
Prediction Access Module (to provide third parties an opportunity to extract existing
prediction data and install prediction pathloss correction data (PLC files)
Loaders (for the Interference Matrix, Measurements and Revenue Maps components)
ENTERPRISE now also includes a number of web services, which form part of the ENTERPRISE
Service Oriented Architecture (SOA) and provide public access to selected areas of the
ENTERPRISE logic. These include:
Prediction service (to enable third parties to create pathloss predictions outside of the
ENTERPRISE environment)
ARRAYWIZARD service (to allow third parties to create predictions, coverage arrays,
interference matrices, LACs and RACs, cell-polygon assignments and Location Based
Services outside of the ENTERPRISE environment)
Documents explaining these APIs and interfaces are available on request from Product Support.
111
ASSET 10.0.2 Technical Reference Guide
112
Index
PMR
algorithms • 79
Index Prediction file management (caching system) • 75
Predictions
file caching system • 75
file management algorithm • 75
A Q
Algorithms
QoS
FCC calculations • 91
algorithms • 95
Frequency hopping • 84
Frequency Re-use and Load • 92
GPRS capacity • 89 R
ILSA cost function • 88
Interference arrays • 80 Reports
Interference Tables • 79 descriptions • 9, 59
MAIO planning cost function • 88 types available • 9, 59
Non-Frequency hopping • 86
Packet QoS • 95
Prediction file caching algorithm • 75
All Servers array • 11, 24
Arrays
2g (GSM Sim) • 9
3g (UMTS and CDMA2000) • 12
All Servers array • 11, 24
CDMA2000 • 12
descriptions • 9
GSM (Sim) • 9
HSPA • 21, 23
LTE • 25
pilot coverage • 13
types available • 9
UMTS • 12
WiMAX (Fixed) • 51
WiMAX (Mobile) • 52
C
Caching algorithm for predictions • 75
Coverage
probability arrays • 10, 13, 18, 27, 52, 53
Coverage Probability arrays • 10, 13, 18, 27, 52, 53
F
Frequency Planning
automatically using ILSA • 87
G
GPRS
algorithms • 79
GSM
algorithms • 79
I
iDEN
algorithms • 79
ILSA
about • 87
cost function • 88
P
Packet Quality of Service algorithms • 95
Planning
frequency • 87
113
ASSET 10.0.2 Technical Reference Guide
114