Escolar Documentos
Profissional Documentos
Cultura Documentos
Date
Reason
15 September 2010
CommercialRelease.
Explanation of Symbols
Throughout this guide, where appropriate, some symbols are used to highlight
particular pieces of text. Three different symbols are in use, and are explained as
follows:
Symbol
Brief Description
Full Description
Note
Tip
Warning or Important
Contents
Appendix A: Array and Report Descriptions
11
12
22
Pathloss Arrays
Coverage Arrays
22
23
LTE Arrays
Pathloss Arrays
Downlink Reference Signal Coverage Arrays
Downlink Noise Arrays
Uplink Coverage Arrays
Downink Coverage Arrays
Downlink Throughput and Data rate Arrays
Uplink Throughput and Data rate Arrays
Miscellaneous Arrays
24
25
25
28
29
30
31
32
34
34
35
35
36
38
39
40
41
42
42
45
45
46
47
49
50
51
General Arrays
Thresholded Arrays
51
52
Simulation Reports
UMTS Composite Reports
UMTS Cell Failure Report
UMTS Downlink Performance Reports
UMTS Cell Handover Reports
UMTS Cell Blocking Reports
Joint GSM-UMTS Composite Reports
Joint GSM-UMTS Cell Failure Report
CDMA2000 Composite Reports
CDMA2000 Failure Report
ASSET 7.0 Technical Reference Guide
Contents
12
53
54
54
55
56
58
58
58
59
60
60
61
62
63
64
65
Page 7
65
66
66
67
68
68
69
69
70
73
75
77
79
79
81
82
82
83
83
84
85
87
87
88
89
90
90
90
91
92
FCC Calculations
92
Frequency Calculations
94
97
98
Preliminary Tests
98
98
106
106
106
99
100
101
102
103
108
ASSET 7.0 Technical Reference Guide
Contents
References
112
113
115
108
109
110
111
111
111
112
Page 9
Page 10
APPENDIX A
Page 11
Example of the 2g/2.5g Arrays under the Coverage heading in the Data Types list
Page 12
Page 13
Interference Arrays
When creating one of the Interference arrays, ASSET requires a Best Server array
in memory. If this is not the case, a Best Server array will be automatically created.
However, if you later create subsequent Interference arrays after making changes to
the network, ASSET does not automatically create a fresh Best Server array.
Therefore, in cases where you suspect the Best Server array in memory has become
out of date for any reason, you should explicitly create both the Best Server array and
the required Interference array when running the Array Creation wizard. For
example:
Example of creating Best Server array and required Interference array in the Coverage/Interference wizard
Page 14
Page 15
Page 16
Page 17
Page 18
To display this on the map, ensure Average Data Rate per Timeslot (GPRS) is selected
in the list of data types to display. The area covered by each GPRS sub-cell is
displayed on the map in the colour corresponding to its average data rate per
timeslot.
When displayed on the map, the array has different colours representing the different
service levels in a kb/s/timeslot. For example:
High (Multimedia)
>12kb/s (Red)
7-12kb/s (Green)
Low (e-mail)
2-7kb/s (Blue)
As with other arrays, you can double-click the item from the Data Types list on the
Map View to change the displayed colours and categories for the array.
Page 19
When the average C/I value for each pixel has been determined, the array converts it
from a signal to noise ratio to a data rate per timeslot by referring to the Coding
Scheme. For details, see the ASSET User Reference Guide.
It works out two of these data rates, one for the best GMSK available, and one for the
best 8-PSK available, and then chooses the one that gives the best overall data rate to
store.
You can specify the cell layer/carrier layer combinations to be considered when
calculating the EGPRS data rate array by selecting the appropriate combinations in
the Interference tab of the Array Settings dialog box.
As with other arrays, you can double-click the item from the Data Types list on the
Map View to change the displayed colours and categories for the array.
High (Multimedia)
>12kb/s (Red)
7-12kb/s (Green)
Low (e-mail)
2-7kb/s (Blue)
As with other arrays, you can double-click the item from the Data Types list on the
Map View to change the displayed colours and categories for the array.
Page 20
Page 21
Example of the GSM (Sim) arrays appearing in the Map View Data Types
Pathloss Arrays
DL Loss & Nth DL Loss
Dependencies: Terminal, Cell layer, Indoor
These are the lowest (and Nth lowest) downlink losses. They represent average values
and are therefore calculated with fades of 0dB.
Page 22
Coverage Arrays
These arrays all provide information on coverage levels and coverage probabilities.
Best DL Cell by RSS
Dependencies: Cell Layer
This is the sub-cell that provides the highest RSS for the terminal.
Best RSS & Nth Best RSS
Dependencies: Terminal, Cell Layer, Indoor
These are the highest (and Nth highest) RSS levels. They represent average values and
are therefore calculated with fades of 0dB.
RSS Coverage Probability
Dependencies: Terminal, Cell Layer, Indoor, Fading
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.
CINR (Control)
Dependencies: Terminal, Cell Layer, Indoor
These are the CINR(Control) values corresponding to the best serving sub-cells, so
they are not necessarily the highest CINR(Control) values.
CINR (Traffic + Control) & Nth CINR (Traffic + Control)
Dependencies: Terminal, Cell Layer, Indoor
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
Dependencies: Terminal, Cell Layer, Service, Indoor
This is the highest bitrate that can be achieved by the terminal based on CINR
regardless of system loading.
Page 23
Example of the Simulator 3g arrays appearing in the Map View Data Types
Page 24
Pathloss Arrays
DL Loss
Dependencies: Terminal, Carrier, Indoor
The lowest downlink loss. Represents average values and is therefore calculated with
fades of 0dB.
Nth DL Loss
Dependencies: Terminal, Carrier, Indoor
The Nth lowest downlink loss. Represents average values and is therefore calculated
with fades of 0dB.
Page 25
RSCP Coverage OK
Dependencies: Terminal, Carrier, Indoor
This is a thresholded version of the RSCP Coverage Probability array and has just 2
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 Settings
tab of the Array Settings dialog box.
Number of RSCP OK
Dependencies: Terminal, Carrier, Indoor
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 Settings tab of the Array Settings dialog
box.
Pilot Ec/Io and Nth Best Pilot Ec/Io
Dependencies: Terminal, Carrier, Indoor
These are the highest (and Nth highest) Ec/Io values. They represent average values
and are therefore calculated with fades of 0dB.
Pilot Ec/Io Coverage Probability
Dependencies: Terminal, Carrier, Indoor
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.
Pilot Ec/Io Coverage OK
Dependencies: Terminal, Carrier, Indoor
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
Settings tab of the Array Settings dialog box.
Page 26
Page 27
Handover Arrays
The aim of the following arrays is to provide the planner with an idea of potential
handover areas, and to indicate areas of pilot pollution. All arrays are based on mean
Pilot Ec/Io levels calculated with fades of 0dB.
Available Soft/Softer Cells
Dependencies: Terminal, Carrier, Indoor
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.
Available Soft Cells
Dependencies: Terminal, Carrier, Indoor
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.
Available Softer Cells
Dependencies: Terminal, Carrier, Indoor
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.
Active Set Size
Dependencies: Terminal, Carrier, Indoor
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).
Page 28
Pilot Polluters
Dependencies: Terminal, Carrier, Indoor
If the Pilot Pollution Threshold specified in the Simulation Wizard is XdB then:
For UMTS, 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 within
XdB of the best Ec/Io in the active set. Therefore the pilot pollution threshold in
UMTS is a relative quantity.
A typical value for UMTS is 6dB.
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 XdB. Therefore the pilot pollution threshold in CDMA2000 is an absolute
quantity.
A typical value for CDMA2000 is -15dB.
Page 29
Page 30
Page 31
Achievable UL Bearer
Dependencies: Terminal, Carrier, Indoor, Service, Speed
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 Settings tab of the Array
Settings dialog box.
Page 32
Achievable DL Bearer
Dependencies: Terminal, Carrier, Indoor, Service, Speed
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 Settings tab of the Array
Settings dialog box.
Downlink coverage arrays are available for each bearer at different speeds. These are
the arrays available for EV-DO:
Ior/Ioc
Dependencies: Terminal, Carrier, Indoor
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.
Achievable DL Bitrate
Dependencies: Terminal, Carrier, Indoor, Service
This is the air-interface bitrate of the DL bearer with the highest supportable Ior/Ioc
requirement.
Page 33
Page 34
Throughput Arrays
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.
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.
Page 35
HSDPA Arrays
Here are brief definitions of the HSDPA-specific arrays:
HSDPA - Best DL Cell by SINR
Dependencies: Carrier
This is the cell that provides the highest SINR level for the terminal.
HSDPA - SINR
Dependencies: Terminal, Carrier, Indoor
This is the highest SINR level. It represents an average value and is therefore
calculated with fades of 0dB.
HSDPA - DL Eb/No Margin
Dependencies: Terminal, Carrier, Indoor, Service, HSDPA Bearer, Speed
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.
HSDPA - DL Coverage Probability
Dependencies: Terminal, Carrier, Indoor, Service, HSDPA Bearer, Speed
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.
HSDPA - DL Coverage Probability OK
Dependencies: Terminal, Carrier, Indoor, Service, HSDPA Bearer, Speed
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 Settings tab of the Array Settings dialog box.
Page 36
Page 37
HSUPA Arrays
Here are brief definitions of the HSUPA-specific arrays:
HSUPA - Best UL Cell
Dependencies: Terminal, Carrier, Indoor, Service, HSUPA Bearer, Speed
The cell which requires the minimum HSUPA transmit power in order to satisfy the
Eb/No requirement.
HSUPA - UL Eb/No Margin
Dependencies: Terminal, Carrier, Indoor, Service, HSUPA Bearer, Speed
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.
HSUPA - UL Req TX Power
Dependencies: Terminal, Carrier, Indoor
The maximum output power of the terminal minus the Eb/No margin.
HSUPA - UL Coverage Probability
Dependencies: Terminal, Carrier, Indoor, Service, HSUPA Bearer, Speed
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.
HSUPA - UL Coverage Probability OK
Dependencies: Terminal, Carrier, Indoor, Service, HSUPA Bearer, Speed
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 Settings
tab of the Array Settings dialog box.
Page 38
Page 39
Page 40
LTE Arrays
This is an overview of the LTE arrays generated by the Simulator in ASSET.
All these arrays are produced on a per carrier basis.
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
Page 41
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. 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.
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.
Pathloss Arrays
DL Loss
Dependencies: Terminal, Carrier, Indoor
The lowest downlink loss. Represents average values and is therefore calculated with
fades of 0dB.
Nth DL Loss
Dependencies: Terminal, Carrier, Indoor
The Nth lowest downlink loss. Represents average values and is therefore calculated
with fades of 0dB.
Page 42
Page 43
RSRQ Coverage OK
Dependencies: Terminal, Carrier, Indoor, Fading, Reliability, Snapshots/Load levels
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 Settings
tab of the Array Settings dialog box.
Number of RSRQ OK
Dependencies: Terminal, Carrier, Indoor, Fading, Reliability, Snapshots/Load levels
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 Settings tab of the Array Settings dialog
box.
DLRS SNR
Dependencies: Terminal, Carrier, Indoor, Snapshots/Load levels
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.
DLRS SINR
Dependencies: Terminal, Carrier, Indoor, Snapshots\Load levels
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.
Page 44
Page 45
UL Transmission Mode
Dependencies: Terminal, Carrier, Service, Indoor, Speed, Fading, Reliability,
Snapshots/Load levels
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.
Page 46
DL BCH/SCH SINR
Dependencies: Terminal, Carrier, Indoor,
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
Dependencies: Terminal, Carrier, Indoor,
This is the highest PMCCH SINR level. This represents an average value and is
therefore calculated with fades of 0dB.
DL Transmission Mode
Dependencies: Terminal, Carrier, Service, Indoor, Speed, Fading, Reliability,
Snapshots/Load levels
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.
Page 47
Page 48
Page 49
Miscellaneous Arrays
Coverage Balance
Dependencies: Terminal, Carrier, Service, Indoor, Speed, Fading, Reliability,
Snapshots/Load levels
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 Settings 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 Settings tab of the Array Settings dialog box.
All Servers
Dependencies: Terminal, Carrier, Indoor
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.
Cell Centre/Cell Edge
Dependencies: Terminal, Carrier, Indoor
This arrays shows the division of the Best Server (by RSRP) area into 'Cell Centre' and
'Cell Edge' based on the selected Cell Edge Threshold setting 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 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.
Page 50
Example of the Fixed WiMAX arrays appearing in the Map View Data Types
General Arrays
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.
Page 51
Thresholded Arrays
DL CINR OK, DL RSS OK, UL CINR OK, UL RSS OK
These are thresholded versions of their corresponding arrays. They have just 2 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 Settings tab of the Array Settings dialog box.
Page 52
Example of the Mobile WiMAX arrays appearing in the Map View Data Types
Page 53
Pathloss Arrays
DL Loss
Dependencies: Terminal, Carrier, Indoor
These are the lowest downlink losses. They represent average values and are
therefore calculated with fades of 0dB.
Preamble Arrays
Best Server by Preamble RSS
Dependencies: Carrier
This is the cell that provides the highest Preamble RSS for the terminal.
Preamble CINR
Dependencies: Terminal, Carrier, Indoor
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.
Preamble RSS and Nth Best Preamble RSS
Dependencies: Terminal, Carrier, Indoor
These arrays display the highest (and Nth highest) Preamble RSS levels. They
represent average values and are therefore calculated with fades of 0dB.
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
Dependencies: Terminal, Carrier, Indoor
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 dialog) meets the coverage reliability criteria specified in the Sim Display
Settings 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.
Page 54
Page 55
UL PUSC CINR
Dependencies: Terminal, Carrier, Indoor, speed
The calculation of the UL PUSC CINR assumes that the terminal is transmitting over
all available data subcarriers.
Page 56
DL FUSC CINR
Dependencies: Terminal, Carrier, Indoor, speed
This is the DL CINR value for the FUSC zone.
DL OPUSC CINR
Dependencies: Terminal, Carrier, Service, Indoor, Bearer
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
Dependencies: Terminal, Carrier, Indoor, speed
This is the DL CINR value for the PUSC zone.
DL AMC Worst Interferer Array
Dependencies: Terminal, Carrier
This array displays the worst interferer at each pixel. The pixel ownership is
determined by the Best Server by DL AMC CINR array.
DL FUSC Worst Interferer Array
Dependencies: Terminal, Carrier
This array displays the worst interferer at each pixel. The pixel ownership is
determined by the Best Server by DL FUSC CINR array.
DL OPUSC Worst Interferer Array
Dependencies: Terminal, Carrier
This array displays the worst interferer at each pixel. The pixel ownership is
determined by the Best Server by DL OPUSC CINR array.
DL PUSC Worst Interferer Array
Dependencies: Terminal, Carrier
This array displays the worst interferer at each pixel. The pixel ownership is
determined by the Best Server by DL PUSC CINR array.
Page 57
General Arrays
CPE Azimuth 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
Dependencies: Terminal, Carrier, Indoor
This array displays the minimum UL required TX power for a given receiver
sensitivity (specified in the Site Database).
DL Throughput Array and UL Throughput Array
Dependencies: Terminal, Carrier
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.
Simulation Reports
This section provides descriptions of the network performance reports that can be
generated from the Simulator (when it is run in the snapshot mode).
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 113.
Page 58
This Result
Describes
The mean number of successful service connections that are in either soft handover
or softer handover.
The mean number of successful service connections that are in softer handover.
The proportion of the failures that were due, in part, to No Uplink Resource Primary
Channel.
The proportion of the failures that were due, in part, to No Downlink Resource
Primary Channel.
The proportion of the failures that were due, in part, to Uplink Resource Channel
Limit Reached.
The proportion of the failures that were due, in part, to Downlink Resource Channel
Limit Reached.
This Result
Describes
Low Pilot
The proportion of the failures that were due, in part, to Low Pilot.
The proportion of the failures that were due, in part, to Downlink Eb/No Range.
The proportion of the failures that were due, in part, to Downlink Eb/No Capacity.
Uplink Eb/No
The proportion of the failures that were due, in part, to Uplink Eb/No.
The proportion of the failures that were due, in part, to Noise Rise.
The proportion of the failures that were due, in part, to compatibility issues in terms
of the network and configuration parameters. There may be a problem with the
carriers, bearers, services, terminal types or filters used, so you should check your
configuration and simulation set-up.
No Covering Cells
The proportion of the failures that were due, in part, to the fact that there was no
pathloss information in the pixel at the location of the terminal.
Describes
Cell Identity
Failure Rate
The percentage of the failures that were due, in part, to uplink resource
Channel Limit Reached.
The percentage of the failures that were due, in part, to downlink resource
channel limit reached.
The percentage of the failures that were due, in part, to low pilot.
The percentage of the failures that were due, in part, to downlink Eb/No
Range.
The percentage of the failures that were due, in part, to downlink Eb/No
Capacity.
The percentage of the failures that were due, in part, to uplink Eb/No.
For UMTS networks there are potentially 36 different resource types but only
those that have been defined will be displayed.
Page 59
Describes
Cell Identity
This value shows the mean transmitted downlink traffic power per cell
(calculated).
This is the sum of the traffic channel power and all of the downlink channel
powers.
This value shows the Max TX Power limit that you have set per cell.
This is the total time-averaged common channel power. The primary and
secondary common channel powers that the user specifies in the site dialog
are peak powers.
The total time-averaged common channel power is given by:
Mean_Common_Power = 0.9 x Peak_Primary_Common_Power + 1.0 x
Peak_Secondary_Common_Power
All powers in this formula are in Watts.
This value shows the downlink pilot power that you have set per cell.
Page 60
This Result
Describes
Cell Identity
The mean number of uplink resource primary channels used per cell.
The mean number of uplink resource channels used for soft handover per cell.
The mean number of uplink resource channels used for softer handover per cell.
The mean number of downlink resource primary channels used per cell.
The mean number of downlink resource channels used for soft handover per cell.
The mean number of downlink resource channels used for softer handover per cell.
For UMTS networks there are 36 different resource types but only those that have
been defined will be displayed.
Describes
Cell ID
Total Samples
This is the total number of terminals used to calculate the blocking probability.
This figure will increase as more snapshots are performed.
Blocking Probability
The confidence interval on the blocking probability. The interval will tend to
decrease as the total number of samples increases.
Percentage of Blocks Due to UL Resource The percentage of the blocks that were due, in part, to Uplink Resource
Channel Limit Reached.
Channel Limit Reached.
Percentage of Blocks Due to DL Resource The percentage of the blocks that were due, in part, to Downlink Resource
Channel Limit Reached.
Channel Limit Reached.
Percentage of Blocks Due to Downlink
Eb/No (Capacity)
The percentage of the blocks that were due, in part, to Downlink Eb/No
Capacity.
The percentage of the blocks that were due, in part, to Noise Rise.
Notes :
The blocking reports are only available if selected in the checkbox in step 2 of 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.
Page 61
Describes
Mean in Handover
Bad C/I
UMTS only
This Result
Describes
The mean number of successful service connections that are in either soft handover
or softer handover.
The mean number of successful service connections that are in softer handover.
The proportion of the failures that were due, in part, to No Uplink Resource Primary
Channel.
The proportion of the failures that were due, in part, to No Downlink Resource
Primary Channel.
The proportion of the failures that were due, in part, to Uplink Resource Channel
Limit Reached.
The proportion of the failures that were due, in part, to Downlink Resource Channel
Limit Reached.
Low Pilot
The proportion of the failures that were due, in part, to Low Pilot.
The proportion of the failures that were due, in part, to Downlink Eb/No Range.
The proportion of the failures that were due, in part, to Downlink Eb/No Capacity.
Uplink Eb/No
The proportion of the failures that were due, in part, to Uplink Eb/No.
The proportion of the failures that were due, in part, to Noise Rise limit.
Joint
Page 62
This Result
Describes
Mean Attempted
Mean Served
Mean Failed
The proportion of the failures that were due, in part, to compatibility issues in terms
of the network and configuration parameters. There may be a problem with the
carriers, bearers, services, terminal types or filters used, so you should check your
configuration and simulation set-up.
No Covering Cells
The proportion of the failures that were due, in part, to the fact that there was no
pathloss information in the pixel at the location of the terminal.
Describes
UMTS only
This Result
Describes
The percentage of failures that were due, in part, to no uplink resource Primary
Channel.
The percentage of the failures that were due, in part, to uplink resource
Channel Limit Reached.
The percentage of the failures that were due, in part, to downlink resource
channel limit reached.
The percentage of the failures that were due, in part, to low pilot.
The percentage of the failures that were due, in part, to downlink Eb/No Range.
The percentage of the failures that were due, in part, to downlink Eb/No
Capacity.
The percentage of the failures that were due, in part, to uplink Eb/No.
Joint
This Result
Describes
Cell Identity
Page 63
Failure Rate
For UMTS networks there are potentially 36 different resource types but only
those that have been defined will be displayed.
Describes
Mean Attempted
Mean Served
Mean Failed
The mean number of successful service connections that are in either soft handoff or
softer handoff.
The mean number of successful service connections that are in softer handoff.
No DL Primary Channel
The proportion of the failures that were due, in part, to No Downlink Primary
Channel.
The proportion of the failures that were due, in part, to Downlink Channel Limit
Reached.
Low Ec/Io
The proportion of the failures that were due, in part, to Low Ec/Io.
The proportion of the failures that were due, in part, to Downlink Eb/Io Range.
The proportion of the failures that were due, in part, to Downlink Eb/Io Capacity.
Uplink Eb/Nt
The proportion of the failures that were due, in part, to Uplink Eb/Nt.
The proportion of the failures that were due, in part, to Noise Rise Limit.
The proportion of the failures that were due, in part, to compatibility issues in terms
of the network and configuration parameters. There may be a problem with the
carriers, bearers, services, terminal types or filters used, so you should check your
configuration and simulation set-up.
No Covering Cells
The proportion of the failures that were due, in part, to the fact that there was no
pathloss information in the pixel at the location of the terminal.
Page 64
Describes
Sector Identity
Failure Rate
The percentage of the failures that were due, in part, to downlink channel limit
reached.
The percentage of the failures that were due, in part, to low Ec/Io.
The percentage of the failures that were due, in part, to downlink Eb/Io
Range, that is failures in which the maximum available traffic channel power is
exceeded.
The percentage of the failures that were due, in part, to downlink Eb/Io
Capacity, that is failures in which the cells maximum transmission power is
exceeded.
Percentage of Failures due to Uplink Eb/Nt The percentage of the failures that were due, in part, to uplink Eb/Nt.
Percentage of Failures due to Noise Rise
Describes
Mean Attempted
Mean Served
Mean Failed
Low Ior/Ioc
The proportion of the failures that were due, in part, to Low Ior/Ioc.
The proportion of the failures that were due, in part, to Downlink Eb/Io Range.
The proportion of the failures that were due, in part, to Downlink Eb/Io Capacity.
Uplink Eb/Nt
The proportion of the failures that were due, in part, to Uplink Eb/Nt.
The proportion of the failures that were due, in part, to Noise Rise Limit.
The proportion of the failures that were due, in part, to compatibility issues in terms
of the network and configuration parameters. There may be a problem with the
carriers, bearers, services, terminal types or filters used, so you should check your
configuration and simulation set-up.
MAC Indexes
The proportion of the failures that were due, in part , to an insufficient number of
MAC Indexes being available.
No Covering Cells
The proportion of the failures that were due, in part, to the fact that there was no
pathloss information in the pixel at the location of the terminal.
Page 65
Describes
Sector Identity
This value shows the mean transmitted downlink traffic power per sector carrier
(calculated).
This is the sum of the traffic channel power and all of the downlink channel powers.
This value shows the Max PA Power limit that you have set per sector carrier.
Rated PA Power
This shows the rated PA power that you have set per sector carrier.
This value shows the sum of paging powers that you have set per sector carrier.
This value shows the downlink pilot power that you have set per sector carrier.
Sync channel power that you have set per sector carrier.
This shows the mean (time-averaged) transmit power of the broadcast control
channel.
Quick Paging Channel Power (dBm) This shows the mean (time-averaged) transmit power of the quick paging channel.
Common Power Control Channel
Power (dBm)
This shows the mean (time-averaged) transmit power of the common power control
channel.
This shows the mean (time-averaged) transmit power of the common assignment
channel.
This shows the mean (time-averaged) transmit power of the common control channel.
This shows the mean (time-averaged) transmit power of the dedicated control
channel.
Page 66
This Result
Describes
Sector Identity
The mean number of downlink channels used for primary connections per sector.
The mean number of downlink channels used for soft handoff per sector.
The mean number of downlink channels used for softer handoff per sector.
Describes
SectorID
Total Samples
This is the total number of terminals used to calculate the blocking probability.
This figure will increase as more snapshots are performed.
Blocking Probability
The confidence interval on the blocking probability. The interval will tend to
decrease as the total number of samples increases.
The percentage of blocks that were due, in part, to No Uplink Primary Channel.
The percentage of the blocks that were due, in part, to Downlink Channel Limit
Reached.
The percentage of the blocks that were due, in part, to Downlink Eb/Io capacity.
The percentage of the blocks that were due, in part, to Noise Rise.
Notes :
The blocking reports are only available if selected in the checkbox in step 2 of the
Simulator Wizard
The statistics given are the reasons for failure to the best server.
Page 67
Describes
Sector Identity
This is the sum of the traffic channel power and all of the downlink channel
powers.
Describes
Sector Identity
The mean Internet Protocol packets per second and is calculated as:
Average time a packet waits (in seconds) in a queue before being transmitted.
Page 68
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 can be displayed for UMTS, CDMA2000 and EV-DO
technologies and contains the following information:
This Result
Describes
Cell/Sector Identity
Describes
Cell/Sector Identity
This value shows the noise rise over thermal noise per cell/sector.
The confidence interval on the noise rise. The interval will tend to decrease as
more snapshots are performed.
Load (%)
This value shows the ratio of noise from terminals that have this cell in the active
set to noise from terminals that do not have this cell in the active set, it is
expressed as a percentage.
Page 69
LTE Reports
Here is the list of LTE reports you can generate when using the Simulator:
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 113.
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 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%.
Cell Failure Report
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 73.
Page 70
Page 71
Page 72
Describes
Cell Identity
Failure Rate
DL RSRP
DL RSRQ
DL BCH/SCH SINR
UL SINR
The terminal cannot meet the SINR requirement of the UL bearer, even if the
terminal transmits at maximum power.
DL SINR
DL Capacity
UL Capacity
No Pathloss Data
Page 73
Page 74
APPENDIX B
The Prediction
Management System
Prediction files 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 when they are
created, and manage them as a cache of precalculated data.
Therefore, in ENTERPRISE, the concept behind the storage of the prediction 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 this that at some stage the disk might become full and consist of
many unwanted prediction 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, based on a 'least-used' algorithm.
As a vital input to this algorithm, you need to specify the maximum disk space for the
storage of these files, on a per prediction folder basis. This limit is specified on the
User Data Directories tab of the Project Settings (Modify Project) dialog box, and is
described in the ENTERPRISE User Reference Guide.
Example of Setting Maximum Disk Space for Prediction File Storage in the Modify Project dialog box
Page 75
Overview of Algorithm
The settings for maximum disk space specified, as described above, are stored in a
configuration file in the root of the prediction folder.
The prediction 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 creation session.
The weighting function takes the following factors into consideration for each
prediction file (most important first) :
The elapsed time since the file was last used
The amount of time that was needed to perform the pathloss calculation
The number of times the file has been loaded
If a "disk full" error occurs during prediction creation, then the file management
system may be automatically invoked early to try to provide some space for the
prediction that has just been calculated. If this fails to provide enough space then a
"disk full" error is written to the message log.
The prediction management algorithm only monitors files generated by
ENTERPRISE, and ignores any other files.
Prediction System Interface API
There is some separate information regarding third party integration/interaction with
ENTERPRISE. This information is included in the ENTERPRISE Technical Reference
guide.
Page 76
A file with a large 'position' has more chance of being deleted than one with a small
'position'.
The basic concept is as follows:
The most important factor used in determining the position of a file in the list is
the elapsed time since the file was last loaded.
The position can also be influenced by a modifier weighting:
Files that have been 'loaded many times' are less likely to be deleted
Modifier Calculation
1
The time taken to create the prediction is recorded and will result in an initial
modifier as follows:
Creation Time
Modifier
0-10s
1.2
10s-20s
1.15
20s-40s
1.1
40s-1.5m
1.05
1.5m-2.5m
2.5m-5m
0.95
5m-10m
0.9
10m-20m
0.85
20m-40m
0.8
40m+
0.75
Page 77
The number of times a file has been loaded is recorded and then used to adjust the
modifier, as follows:
Number of loads
Add to modifier
+0.05
1-5
5-10
-0.03
10-20
-0.06
20-40
-0.09
40-80
-0.12
80-160
-0.15
160-320
-0.18
320-640
-0.21
640+
-0.24
All the above values are stored in the configuration file in the root of the
prediction folder, and can be modified by your administrator if necessary.
Page 78
APPENDIX C
Description
Co-channel Area
The area* served by cell A that would be affected by interference if A and B were
assigned the same carrier.
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.
The amount of traffic* served by cell A that would be affected by interference if A and
B were assigned adjacent carriers.
Page 79
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.
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.
Examples of Interference Table files can be found, along with a description of the
file format, in the ENTERPRISE Technical Reference Guide.
Important:
From version 7.0 onwards, the Interference Table file format can accommodate
GSM, AMPS, Mobile WiMAX and LTE. For GSM and AMPS, the file contains cell
layer and sub-cell information. For Mobile WiMAX and LTE, the file contains cell
information.
The traffic units for GSM are 'mE' (milli-Erlangs), but the traffic units for Mobile
WiMAX and LTE are 'T' (Terminals).
Page 80
Description
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.
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.
Sums the co-channel C/I levels for all possible interfering frequencies and
presents the average C/Ic level.
Sums the adjacent channel C/I levels for all possible interfering frequencies
and presents the average C/Ia level.
Sums the combined co-channel and adjacent C/I levels for all possible
interfering frequencies and presents the average C/(Ic_Ia) level.
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.
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.
The worst connection and the worst interferer calculations are the same in the case
of a non-frequency hopping network.
Page 81
For:
Where:
For each non-hopping carrier fi in the serving sub-cell, C/I(fi) is calculated.
For the hopping frequency group in the serving sub-cell, a single C/I(FH) is
calculated.
(2)
Where:
is the averaged C/I for the hopping carriers.
is the number of hopping frequencies.
is the number of non-hopping frequencies.
is frequency Diversity Gain.
Page 82
, where
) is calculated.
For the hopping frequency group in the serving sub-cell, a single C/I(FH) is
calculated.
The denominator in the equation above can never be zero ( and cannot both
be 0 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.
Where:
For each (non-hopping) carrier f1 in the serving sub-cell, C/I(
) is calculated.
Where:
For each (non-hopping) carrier fi in the serving sub-cell, C/I(
) is calculated.
Page 83
Page 84
C/I (dB)
-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.2200000000
0.2000000000
0.1700000000
0.1500000000
0.1200000000
0.1000000000
0.0900000000
0.0780000000
0.0660000000
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
C/I (dB)
26
0.0000000001
27-45
0.0000000000
1 is used if
, is used if
, 0 is used otherwise
Where:
C/I(i)
SSC(i)
i,j
A particular frequency
SIC(K,i)
Interfering cell
L(K,j)
V(K,j)
f (i)
Page 85
The following graph shows the relationship between the Probability of Bit Error and
the C/I:
BERAV(serving cell) is calculated as the average BER(i) for all frequencies in the cell:
Where:
x Number of FH frequencies per TRX
mFH
nTRX
Page 86
Where:
is the number of TRX allocated to the hopping carrier layers
is the number of hopping carriers
1 is used if
, is used if
, 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.
and
PTOT = Average of all P(i) in the cell
Page 87
Page 88
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.
Where:
=
The adjacent channel interference caused on allocation i by allocation j (Units: 200*mE or 20,000*km)
The separation costs (from equipment, neighbours, exceptions or close separations) between
allocations i and j
The handover count and intermodulation interference costs associated with allocation i
Page 89
Where:
are sub-cells
and
and
is the C/I or C/A separation count for all TRX combinations on subcells
) traffic load (
):
) can then be
Page 90
and the
Where:
is total shared traffic channels required
is average (long term) number of TS required for Circuit Switched traffic (=
Where:
e
Page 91
FCC Calculations
This section describes the algorithms used to calculate the data provided in the FCC
report.
Antenna Height AAT
The Antenna Height AAT is calculated in metres.
The calculation is:
Antenna height + Site ground height + Radial average terrain elevation
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.
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.
Page 92
Minimum
32dBu Served
N/A
Minimum of 30 metres
32dBu Unserved
ERP>=10 W
Minimum of 30 metres
ERP<=10 W
Minimum of 3 metres
N/A
Minimum of 8 metres
Gulf of Mexico
You will receive a warning if the Average Radial distance exceeds 40.2 km (79.1
km for Gulf of Mexico cells).
Transmitting ERP Watts
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.
You will receive a warning if the ERP exceeds 500W.
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.
Used ERP is the maximum of:
0.1 W
Maximum ERP/500
Transmitting ERP for the radial
Area within the Service Area Boundary
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.
Heron's Formula for calculation of area of scalene triangle:
A = SQR(S (S-a) (S-b) (S-c))
SQR - Square Root
a, b, c sides of the triangle
S half the perimeter of triangle, that is (a+b+c)/2
Page 93
32dBu Served
D = 2.531 x Used Antenna Height(m) ^ 0.34 x Used ERP for Radial in Watts ^ 0.17
and
32 dBu 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.
Effective Frequency Re-use
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.
Where:
REFF is the Effective Frequency Re-use for a sub-cell
NF is the total number of carriers available to hopping TRX on the sub-cell (note: this
is not the MA list length)
NTRX is the number of hopping TRX on the sub-cell
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.
Page 94
Where:
LFREQ is the Frequency Load of a sub-cell
LFRACTION is the Fractional Load of a sub-cell
LHW is the Hardware Load of a sub-cell
NTRX is the number of hopping TRX on the sub-cell
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 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.
Page 95
Page 96
APPENDIX D
Page 97
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.
Page 98
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.
Littles 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
= mean session arrival rate
.T
Page 99
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.
( N pc 1)D pc
N pc ( N d 1)D d
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 packets 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.
Page 101
Scheme
GPRS
CS - 1
EGPRS
Link Adaption
Family
Modulation
RLC Block
Size (bits)
GMSK
9.05
181
CS - 2
13.4
268
CS - 3
15.6
312
CS - 4
21.4
428
8.8
176
MCS - 1
GMSK
MCS - 2
11.2
224
MCS - 3
14.8
296
MCS - 4
17.6
352
MCS - 5
MCS - 6
29.6
MCS - 7
44.8
MCS - 8
54.5
1090
MCS - 9
59.2
1184
8 - PSK
22.4
448
592
896
In order 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.
Page 102
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 on page 106.
Delay Class
GPRS has four different traffic classes. The following table shows the parameters that
specify the related QoS requirements:
Traffic Class
Medium
Application
One-way Delay
Conversational
Audio
Telephony
4-25
<150ms
Data
Telnet
<8
<250ms
Audio
Streaming (HQ)
32-128
<10s
Video
On-way
32-384
<10
Data
FTP
<10s
Audio
Voice messaging
4-13
<1s
Data
Web browsing
<4s/page
Streaming
Interactive
Page 103
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:
Reliability Class
10
10
10
Where:
Throughput(C/I) = throughput in kb/s read off the throughput per timeslot graph for
the C/I achieved by the link
PeakDataRa tePerSlot = peak rate per slot for the given coding scheme (the
asymptote of the throughput per timeslot graph
BLER(C/I) = block error rate for the C/I achieved by the link
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 112.
Page 104
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.
Peak throughput class
Mean throughput
(bytes per hour)
100
16
200
32
500
64
1 000
128
2 000
256
5 000
512*
1024*
17
20 000 000
2048*
18
50 000 000
Best Effort
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:
PeakThroughput
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.
Page 105
Page 106
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.
Page 107
Page 108
Set the basic run length to ensure at least 1000 or 2000 packet admission requests
are made to the cell for each service.
Repeat the run (replicate) 5 times and calculate the confidence interval half width
H5.
If the confidence interval is less than 10% of the mean delay, the desired accuracy
has been obtained.
, and variance
k Y
i
k
i 1
i 1
(Yi Y ) 2
(k 1)
2.
Hi
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:
N req
S req
Treq
S req
N req
packets
session arrives
S req
N pc .N d
packets, so
N req
N pc .N d
(1)
The session arrivals are modelled as a Poisson process, and so the expected time until
the
Treq
S req
S req
(2)
Treq
N req .T
N pc .N d .N
Page 109
N req
N .N pc .N d
S req
1 .T
Delay
Count
0.F
C0
1.F
C1
2.F
C2
...
...
...
n.F
Cn
...
...
...
N.F
CN
TP
ci
i 0
P ( n)
cn
TP
ci
CP(n)
Page 110
i 0
TP
N
D
Mean delay
F.
n.P(n )
n 0
N
Standard deviation
(F.n
n 0
D ) 2 .P(n )
).
Transmission time:
Ttrans
8.S d
1000.b
Page 111
0.01. rt
BLER
1 BLER
1 seconds
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, CollierMacmillan Ltd, p.193
Page 112
APPENDIX E
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)
GSM/UMTS (joint)
CDMA2000
EV-DO
Fixed WiMAX
Mobile WiMAX
LTE
Technology-specific documents are available, containing comprehensive details of all
the algorithms and outputs related to the Simulator. If your company is registered for
a customer web account, and you know the login password, you can download these
specialist documents. To do this, log in to the Product Support page, click the User
Reference Guides link, select the relevant software version from the drop-down box,
and then click the 'Static Simulations' link for the appropriate technology.
Page 113
Page 114
F
Frequency Planning
automatically using ILSA 88
Index
G
GPRS
algorithms 79
arrays 18, 19
GSM
algorithms 79
A
Algorithms
FCC calculations 92
Frequency hopping 85
Frequency Re-use and Load 94
GPRS capacity 90
ILSA cost function 89
Interference arrays 81
Interference Tables 79
MAIO planning cost function 90
Non-Frequency hopping 87
Packet QoS 97
Prediction file caching algorithm 75
Arrays
2g (GSM Sim) 22
2g and 2.5g (Non-Sim) 12
3g (UMTS and CDMA2000) 24
best server 13, 14, 21
CDMA2000 24
descriptions 11
GSM (Sim) 22
HSPA 36, 38
interference (2g Non-Sim) 14
LTE 41
pilot coverage 25
types available 11
UMTS 24
WiMAX (Fixed) 51
WiMAX (Mobile) 53
Assignments, carriers 88
I
iDEN
algorithms 79
ILSA
about 88
cost function 89
Interference
arrays 12, 14, 15, 16, 17
P
Packet Quality of Service algorithms 97
Planning
frequency 88
PMR
algorithms 79
Prediction file management 75
Predictions
file caching system 75
file management algorithm 75
Q
QoS
algorithms 97
R
Reports
descriptions 58
types available 58
B
Best Server arrays 13, 14
S
C
Caching algorithm for predictions 75
Carriers
assignments 88
Coverage
probability arrays 23, 25, 32, 42, 52, 54
Coverage Probability arrays 23, 25, 32, 42, 52, 54
E
EGPRS
arrays 19, 20, 21
Page 115
Page 116