Wi-Fi Static Simulations
Wi-Fi Static Simulations
V 9.0
This document is supplementary to the User Reference Guides, and is protected by copyright and
contains proprietary and confidential information. No part of the contents of this documentation may be
disclosed, used or reproduced in any form, or by any means, without the prior written consent of
TEOCO.
Although TEOCO has collated this documentation to reflect the features and capabilities supported in
the software products, the company makes no warranty or representation, either expressed or implied,
about this documentation, its quality or fitness for particular customer purpose. Users are solely
responsible for the proper use of ENTERPRISE software and the application of the results obtained.
TEOCO
Cassini Court
Randalls Research Park
Randalls Way
Leatherhead
Surrey KT22 7TW
ENGLAND
VERSION HISTORY
Version Date Author Comments
1.0 2013/08/07 V. Kontogeorgos Wi-Fi in ASSET v8.1
1.1 2013/08/22 V. Kontogeorgos Updated
1.2 2013/09/02 V. Kontogeorgos Version 9.0
1.3 2015/03/23 V. Kontogeorgos Updated Multiple-technology arrays
Updated Terminal Info arrays
Updated Reports
1.4 2015/03/24 V. Kontogeorgos Added Inter-Technology Interference
CONTENTS
1 What Is A Snapshot?................................................................................................................... 4
1.1 Randomness in a Cellular Network .................................................................................. 4
1.2 Averaging in Coverage and Capacity Evaluations ......................................................... 7
1.3 Why Produce Snapshots? .................................................................................................... 7
2 Formulae ....................................................................................................................................... 8
2.1 List of Principal Symbols .................................................................................................... 8
2.2 Notation ................................................................................................................................. 9
2.3 Available Resources ........................................................................................................... 10
2.4 Downlink Power Formulae .............................................................................................. 12
2.5 Link Budget Formulae ....................................................................................................... 12
3 Snapshot Overview................................................................................................................... 13
3.1 Random Terminal Distribution ........................................................................................ 13
3.2 Gathering Of Results ......................................................................................................... 13
4 Connection Evaluation in a Snapshot ................................................................................... 14
4.1 Connection Scenario Prioritisation .................................................................................. 14
4.2 Failure Reasons ................................................................................................................... 14
5 Output Arrays and Reports ..................................................................................................... 15
5.1 Array dependencies ........................................................................................................... 15
5.2 Pathloss Arrays ................................................................................................................... 17
5.3 Downlink Coverage Arrays .............................................................................................. 17
5.4 Throughput Arrays ............................................................................................................ 18
5.5 Miscellaneous Arrays ........................................................................................................ 18
5.6 Composite Tech Arrays ..................................................................................................... 19
5.7 Terminal Info Arrays ......................................................................................................... 20
5.8 Simulator Reports .............................................................................................................. 22
6 Coverage Probability Calculations ........................................................................................ 23
6.1 Fades in the Simulation Snapshots .................................................................................. 23
6.2 Fades in Arrays for Mean Values ..................................................................................... 24
6.3 Fades in Coverage Array Calculations ............................................................................ 24
7 Inter-Technology Interference ................................................................................................ 25
7.1 Introduction ........................................................................................................................ 25
7.2 Inter-Technology Interference Formulae ........................................................................ 26
7.2.1 Uplink Received Interference ........................................................................................... 26
7.2.2 Downlink Received Interference ...................................................................................... 27
7.2.3 Carrier Overlap Calculations ............................................................................................ 28
1 WHAT IS A SNAPSHOT?
1.1 RANDOMNESS IN A CELLULAR NETWORK
In a simulation of a cellular network there are two main types of randomness that one needs to
consider.
We shall consider the spatial domain to be discrete and consisting of a large number of pixels (bins)
some of which will contain terminals. Each possible pattern of terminal locations has an associated
probability of occurrence. We can label these spatial patterns 1 , 2 , etc and represent the
corresponding probabilities of occurrence by (1 ), (2 ), etc. An example of two spatial patterns
1 and 2 are shown below.
1 2
X
X
X X
X
X
X
X
X X
X X
X
Each spatial pattern has many possible configurations of transmitting and non-transmitting terminals.
Two such configurations for the spatial patterns 1 and 2 are shown below, with 1 representing a
transmitting terminal, and 0 a non-transmitting terminal.
(1, 1 ) (2, 1 )
1
1
1 0
0
1
0
1
0 0
1 0
1
(1, 2 ) (2, 2 )
0
0
1 1
0
0
1
0
0 0
0 1
1
We call each of these patterns a spatio-temporal pattern to highlight the fact that we have specified
spatial locations of terminals and also their temporal state (transmitting/non-transmitting). We can
label the spatio-temporal patterns for spatial pattern 1 as follows (1, 1 ), (1, 2 ) and etc and their
probabilites of occurrence (1, 1 ), (1, 2 ) and etc. Note that the probability of occurrence of a
spatio-temporal pattern (, ), is proportional to the probability of occurrence of the spatial pattern
:
(, ) = ( )( | ). (1)
One can think of a spatio-temporal pattern as being a picture of a real network at a random instant in
time. This is what most people have in mind when one mentions a simulation snapshot, but a
snapshot in our simulator represents something slightly different, as explained below.
The ideal static simulation would calculate an average quantity (e.g. the average noise rise on a cell) by
performing a weighted sum over the set of all possible spatio-temporal patterns (, ), with the weight
for a pattern being its probability of occurrence. So the average of some quantity would be given by
= (, )(, ). (2)
,
= (, ) (, )( | ). (3)
The summations in (2) and (3) are over every conceivable pattern of terminal locations and activities,
including the unlikely ones, so clearly some simplifications are necessary in any practical static
simulator.
This simplification is the most common one made in static simulations, and it is used universally.
Instead of considering all spatial patterns, we consider a set of sample spatial patterns drawn from
the distribution of all spatial patterns. The first weighted sum in (3) can then be approximated by a
simple average over the set of sample spatial patterns:
1
(, )( | ). (4)
Spatial randomness is therefore handled explicitly by considering a set of sample spatial patterns that
have been selected in a random and unbiased way. There is still the issue of how to handle the
different temporal states for each sample spatial pattern. There are two main approaches we can use:
This simplification is fairly common but has some drawbacks as explained below. Firstly, as in the
previous simplification, one selects a sample spatial pattern from the set of all possible spatial patterns,
making sure that the selection is made in a random and unbiased way. One then assigns a random
activity flag (1 or 0) to each terminal in the pattern, to indicate if the terminal is transmitting or not.
The probability of assigning a 1 to a terminal is just the service activity factor (% resource element
[RE] usage) for that terminal. This ensures that activity flags are assigned in a random and unbiased
way. The weighted sum over the set of all spatio-temporal patterns in (2) can be approximated by a
simple average over the set of sample spatio-temporal patterns:
1
(, ). (5)
,
If we called a spatio-temporal pattern a snapshot then the above formula simply says that we can
approximate by performing a simple average over the snapshots. This simple average works because
the sample spatio-temporal patterns are selected in a random and unbiased way. Also note that this
averaging explicitly accounts for spatial randomness and explicitly accounts for temporal randomness.
For low activity services, the user can do 100s of snapshots and never set an activity flag, and
therefore certain outputs may not have any results. For example, a simulation report may say
that many users are served on a cell but that there is no throughput on the cell. Forcing the
user to run 1000s of snapshots is unacceptable in a commercial tool, so we either have to
remove the problem outputs or calculate them some other way.
For the above reasons, we do not use Simplification 2 and use the following simplification instead.
As before, one selects a sample spatial pattern from the set of all possible spatial patterns, but now we
completely remove the activity flags from the randomly scattered terminals. Each terminal is therefore
neither instantaneously active nor instantaneously inactive, but rather represents a sort of time-
averaged entity. Essentially, this means that when we examine the resources it consumes, we use the
time-averages for these quantity, or the specified average service rate in relation to the cell capacity.
So in our simulator, a snapshot does not represent a random instant in time for a random distribution
of terminals, but rather the average instant in time for a random distribution of terminals. The
snapshot represents the average instant because all the measures of system load (i.e. resource usage and
throughput) are time-averages.
It is still valid to perform simple averages of quantities over our snapshots. However, averaging over
the snapshots now explicitly accounts for spatial randomness only. The temporal randomness is now
handled implicitly within each snapshot through the use of time-averages in our calculations. Time-
averages feature in the evaluation of both coverage and capacity as described below.
= , (6)
where, is the Received Signal Strength, is the Cell TX Power and is the Linkloss,
To check for coverage, we evaluate RSS against the terminals required RSS.
The capacity constraint is that the aggregate average service rate of all served terminals must not
exceed the cell available capacity.
By running many snapshots, values for these quantities are obtained for different spatial distributions of
terminals which are further used to analyse the UL and DL coverage for the system.
2 FORMULAE
Feeder loss, including feeder connector Loss for cell
Body Loss of terminal
Pathloss between between cell and terminal
2.2 NOTATION
Symbols in subsequent sections use the following notation.
p
indicates a sum over all carriers p.
J
indicates a sum over all cells J.
k
indicates a sum over all terminals k.
kJ
indicates a sum over all terminals k in cell J.
Unless stated otherwise, all quantities and formulae are in standard SI units, not in dB.
Downlink
The available downlink resources of the cell consist of the available downlink capacity of the cell
which is offered for consumption by Wi-Fi enabled terminals.
(7)
=
where
is the nominal downlink capacity, is the downlink capacity that is reserved for
use unrelated to the operator and is the net available downlink capacity of cell .
The cell downlink served throughput is the summation of the downlink service rate for all terminals
served by this cell:
(8)
=
where is downlink service rate for served terminal and is total served throughput in the
downlink for cell .
The cell downlink served throughput is constrained by the downlink available capacity of the cell:
(9)
Uplink
The available uplink resources of the cell consist of the available uplink capacity of the cell which is
offered for consumption by Wi-Fi enabled terminals.
(10)
=
where
is the nominal uplink capacity, is the uplink capacity that is reserved for use
unrelated to the operator and is the net available uplink capacity of cell .
The cell uplink served throughput is the summation of the uplink service rate for all terminals served
by this cell:
(11)
=
where is uplink service rate for served terminal and is total served throughput in the uplink
for cell .
The cell uplink served throughput is constrained by the uplink available capacity of the cell
(12)
DL Loss
(13)
=
.
The term
is Mast Head Amplifier Insertion Loss as specified on the MHA equipment. The terms
and
are read from the prediction file.
DL EiRP
, =
, (14)
(15)
RSS,, = ,
3 SNAPSHOT OVERVIEW
The key purpose of a snapshot is to provide us with measures of system load for a particular
distribution of terminals. To obtain these measures of system load, we must calculate uplink and
downlink transmission powers for all the links in the system. A snapshot involves the following stages:
Gathering results
Consider a pixel that has a terminal density of terminal/km2 and an area of km2, so that the average
number of terminals in the pixel is . We note that:
Terminal occurrences within the pixel are independent of each other, and are spatially uniform
within the pixel. In other words, a terminal is just as likely to be located at one point within
the pixel as any other point within the pixel.
The probability that two or more terminals are located at exactly the same point within a pixel
is zero. This is simply because there are an infinite number of locations within the pixel.
These imply that terminal occurrence is a spatial Poisson process within the pixel. Therefore the total
number of terminals in the pixel satisfies the Poisson distribution:
(16)
( terminals) = () / !
We choose the number of terminals to assign to the pixel by drawing a number from this Poisson
distribution. Doing this at each pixel ensures our terminal distribution is unbiased. Since the sum of
many Poisson distributions is also a Poisson distribution, the total number of terminals in the snapshot
will also be Poisson distributed.
One may note that if the average number of terminals at a pixel is small ( 1), then working to
first order in ,
(0 terminal) (1 ), (17)
(1 terminal) .
So one is effectively making a binary decision about whether a terminal should be placed at the pixel.
After creating the random terminal distribution, the terminals are randomly sequenced. This determines
the order in which they will be considered during the power iterations .
The DL data rate of the connection (this is given by the Wi-Fi DL service rate)
The UL data rate of the connection (this is given by the Wi-Fi UL service rate)
Typically, several connection scenarios are available to each terminal. Our snapshot attempts to
connect the randomly spread terminals to the network in the most favourable way possible, so some
logic is required for ranking the different scenarios that each terminal may use.
The rules for ranking scenarios during connection evaluation are (in order of decreasing importance):
Prefer cells with higher RSS levels to cells with lower RSS levels
DL RSS
This means that Signal Strength requirement specified on the terminal type is not satisfied.
UL Capacity
This means that the cell has insufficient UL available capacity to serve the UL service rate.
DL Capacity
This means that the cell has insufficient DL available capacity to serve the DL service rate.
User Limit
This means the number of served users on the cell has reached the limit specified by the
Max Number of Users cell parameter.
No covering cells
This means that no pathloss data is available for the terminals location.
If all of the connection scenarios available to a terminal fail to produce a connection, then the terminal
is classified as a failure. Note that each scenario in the list can fail for multiple reasons. Also, different
scenarios in the list can fail for different sets of reasons. ASSET only records the failure reasons of the
top scenario, as in most cases this provides the most useful information as to why a terminal fails. The
breakdown of all failure reasons except for No Valid Connection Scenarios and No Covering Cells
are logged in respective failure reports.
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 or define the loads manually. Remember that 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).
The following table lists the types of array that are available in the simulator, and shows some of their
dependencies. Most terms (e.g. Indoor) should be self-explanatory.
Fading means the array depends on the standard deviation of shadow fading for the clutter
type.
Reliability level means the array depends on the coverage reliability threshold in the array
settings dialog. The user can change this parameter and then redraw the array without running
any more snapshots.
Snapshots means that the presence of the array depends on whether snapshots have been run
or not. The results and accuracy of the array are dependent the number of snapshots done.
Other Tech means that the presence of the array is dependent on the inclusion of other
technology types in the Simulation. Other technology types can be GSM, UMTS and LTE.
C T S V I F R n O
Pathloss Arrays
Wi-Fi: DL Loss X X X
Wi-Fi: Nth DL Loss X X X
Wi-Fi: Line Of Sight X X
Downlink Coverage Arrays
Wi-Fi: Best Server X
Wi-Fi: Nth Best Server X
Wi-Fi: DL RSS X X X
Wi-Fi: Nth Best DL RSS X X X
Wi-Fi: DL RSS Coverage Probability X X X X
Wi-Fi: DL RSS OK X X X X X
Wi-Fi: Number of DL RSS OK X X X X X
Throughput Arrays
Wi-Fi: DL Cell Throughput (kbps) X P
Wi-Fi: UL Cell Throughput (kbps) X P
Miscellaneous Arrays
All Servers (Wi-Fi) X X X
Composite Tech Arrays
Composite: Best Server X X X X X
Composite: Tech Type X X X X X X
Composite: All Tech Types X X X X X X
Composite: Best Carrier / Cell-Layer X X X X X
Terminal Info Arrays
Terminal Info (Wi-Fi): Failure Rate X P
Terminal Info (Wi-Fi): Failure Reason X P
Terminal Info: Speed (km/h) X P
These are the downlink losses of the Best Server and the Nth Best Server as calculated by (13). They
represent average values and are therefore calculated with fades of 0 dB.
This is a two-valued array (LOS, non-LOS) for the Best Server by RSS. 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) DL RSS for the terminal.
These are the highest (and Nth highest) DL RSS levels as calculated by (15). 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
Dependencies: Terminal, Carrier, Indoor, Fading, Reliability
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 Array Settings Sim Display Thresholds.
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
Array Settings Sim Display Thresholds.
This is the application layer DL cell throughput, as calculated by (8), 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.
This is the application layer UL cell throughput, as calculate by (11), 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.
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. Cell ranking is primarily based on the carrier/cell layer priorities which
are specified off the Service. Secondarily, cells of a specific technology type are ordered by Signal
Strength (GSM: RSS, UMTS: RSCP, LTE: RSRP, Wi-Fi: DL RSS). The terminals 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, Wi-Fi: Required Signal Strength).
The array has a dependency on Cell Load Levels, due to the interference-related terminal requirements.
The display thresholds are set for each technology type individually in Array Settings Sim Display
Settings.
This is the technology type of the serving cell as determined in the Composite: Best Server array.
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 in case of UMTS, LTE and Wi-Fi, or Cell-Layer in case of GSM of the serving cell
as determined in Composite: Best Server array.
The failure rate is the proportion of attempted terminals at a pixel that failed to make a connection. It is
calculated as a percentage as follows:
The accuracy of the result at a pixel is clearly limited by the number of attempts made at the pixel. For
example, if only one attempt has been made, the result will either be 0% or 100%. So the Failure Rate
array gives a rough visualisation of the problem areas of the network.
This array shows failures and successes in a single array. 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. So if
the last terminal that was attempted at a pixel succeeded, then the pixel will be labelled a success,
regardless of how many terminals may have failed there in other snapshots. Likewise, if the last
terminal at a pixel failed, then the pixel will be labelled as a failure, regardless of how many terminals
succeeded there in other snapshots. Therefore locations that are more likely to serve terminals in a
snapshot rather than fail them, are more likely to be labelled as successes than failures.
A terminal can fail for multiple reasons. When this occurs, only a single reason is reported when
writing a value at the pixel. This is achieved by sensibly ranking the failure reasons for the terminal
and using the most dominant one. For example, there is no point in indicating a capacity failure for a
terminal if it does not have coverage. In other words, coverage failures rank more highly than capacity
failures.
The failure reason categories are ranked as follows (most dominant failure reasons first). For clarity,
the categories in the legend are shown in the same order.
o Success
o No Covering Cells
o No Valid Scenarios
o DL RSS
o UL Capacity
o DL Capacity
o User Limit
This plot shows the speed of the terminal in the corresponding Failure Reason plot. The value shown
at a pixel is determined by last terminal that was attempted there, regardless of the snapshot in which it
was attempted.
This category comprises two arrays, the Terminal Info: Tech Type (Served) and the Terminal Info: Tech
Type (Failed). After a terminal has been evaluated in a snapshot, it will be marked in precisely one of
the following ways:
1) As failure due to No Valid Scenarios / No Covering Cells in the Tech Type (Failed) array.
It will also appear as a No Valid Scenarios / No Covering Cells failure in the Failure
Reason array of every individual technology.
2) As a success in Tech Type (Served) array, showing the tech type used for connection.
The Failure Reason array for that technology will show Success.
3) As a failure in the Tech Type (Failed) array, showing the tech of the most relevant failure
reason.
The Failure Reason array for that technology will show the according failure reason.
This array shows the serving technology type (GSM, UMTS, LTE or Wi-Fi) where
the Terminal Info (GSM): Failure Reason array is reporting Success or
the Terminal Info (UMTS): Failure Reason array is reporting Success or
the Terminal Info (LTE): Failure Reason array is reporting Success or
the Terminal Info (Wi-Fi): Failure Reason array is reporting Success.
There is a separate category to show locations with No Valid Scenarios / No covering cells.
This array shows the failed technology type (GSM, UMTS, LTE or Wi-Fi) where
the Terminal Info (GSM): Failure Reason array is not reporting Success or
the Terminal Info (UMTS): Failure Reason array not reporting Success or
the Terminal Info (LTE): Failure Reason array not reporting Success or
the Terminal Info (Wi-Fi): Failure Reason array not reporting Success.
There is a separate category to show locations with No Valid Scenarios / No covering cells.
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, as explained in section 5.7 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%.
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.
These reports provide the breakdown of per cell served throughputs for each service.
This report provides the breakdown of per cell successfully served terminals in UL and DL. It includes
cells of other technologies that are present in the simulation.
In the second mode coverage arrays can be obtained after running a very small number of snapshots
(typically 10s) and arrays converge quickly. If no snapshots have been run, then coverage arrays are
still available but they give the coverage probabilities in an unloaded system.
We introduce the following notation to represent the probability density function for a normally
distributed random variable with mean and standard deviation .
1 ( )2 (18)
(; , ) = exp ( ),
2 2 2 2
Shadow fading is modelled in a snapshot by randomising the pathlosses experienced by the randomly
scattered terminals. Shadow fades are log-normally distributed, and the user specifies the shadow
fading standard deviation for indoor and outdoor terminals in each clutter type. In reality, the fades
between a terminal and the cells that cover it will exhibit a degree of correlation. In particular, a
terminal is likely to have similar fades to cells that are located on the same site. To account for this, the
user specifies two parameters in the Monte Carlo Wizard:
The normalised inter-site correlation coefficient which is the correlation between
fades to cells on different sites.
The normalised intra-site correlation coefficient which is the correlation between
fades to cells on the same site.
These two parameters must satisfy the constraints 0 1. For each randomly
scattered terminal in a snapshot, a set of correlated fades to the covering cells is generated using the
following procedure. All the random numbers mentioned below are independent and normally
distributed with zero mean and unit variance, and is the standard deviation of the shadow fading at
the pixel in dB.
(19)
( + + 1 )
The above procedure is performed for each of the randomly scattered terminals at the beginning of a
snapshot. Fades for different terminals are uncorrelated even if they are located in the same pixel.
In the absence of fading, let the DL RSS (in Watts) for cell be represented by . If cell has a
fade of dB, then the DL RSS is given by (10 /10 ).
Find the fade that causes the DL RSS to exactly satisfy the RSS requirement specified on
the terminal type. Call this fade . Note that may be positive or negative. Any fade
bigger than will give an inadequate RSS.
Since is normally-distributed with a mean of 0 dB and standard deviation of dB, the probability
that > is given by
(20)
( > ) = (; 0, )
This is the probability that the DL RSS does not meet the requirement.
7 INTER-TECHNOLOGY INTERFERENCE
The current chapter is common to the GSM, UMTS & HSPA, LTE and Wi-Fi Static Simulations
documents.
7.1 INTRODUCTION
The Multiple Technology Simulator allows considering the effects of inter-carrier interference for
carriers of the same technology and carriers of different technologies. The considered technologies are
GSM, UMTS, LTE and Wi-Fi. The selection in Step 2 of the Simulator Wizard determines the
technology types that are considered for the subsequent calculations.
Carriers can be fully, partially or non-overlapping. Non-overlapping carriers can still be adjacent, hence
interfering with each other. The relative position of carriers is determined by their Low and High
frequencies that specify the operative range of the carrier.
INTERFERER
1 2
VICTIM
Figure 2: Illustration of overlapping carriers
Inter-tech Downlink
Interfering Power
Serving Interfering
Own-tech Othertech
Site Site
Intra-tech Intra-tech
Uplink/Downlink Uplink/Downlink
Served Interfering
Own-tech Othertech
Terminal Terminal
Inter-tech Uplink
Interfering Power
Assuming Wi-Fi to be the reference technology in the context of the current document, the other
interfering technologies can be GSM, UMTS and LTE.
Note: The uplink is not modelled for GSM and Wi-Fi, which means that GSM and Wi-Fi terminals
uplink transmission is not considered for interference.
Tech denotes the summation over the technologies that have been selected in the
Simulator Wizard, excluding , where = {-} and = {, , } in the
context of the current document.
This is the interference received in the uplink by cells and consists of two components
i. UL-UL: The uplink of -technology terminals interfering with the uplink of cells
ii. DL-UL: The downlink of -technology cells interfering with the uplink of cells
, Tech
The combined effect of these two components is modelled via , , the Inter-technology UL
Noise Rise due to cells and terminals of technologies and it is specified in the Site DB.
, inter Tech
where , is the inter-technology UL received interference of cell employing carrier due
Tech
to cells and terminals of technologies. , is the Channel Protection factor for the
, Tech
technologies and it is input from Site DB for cell . , is the UL Noise Rise due to the
technologies and it is input from Site DB for cell . , is the UL thermal noise power.
On the cell, in Site DB, the combined inter-technology total UL Noise Rise, disregarding any
Channel Protection factors, is reported as:
On the cell, in Site DB, the combined UL Noise Rise for all included technologies, disregarding
any Channel Protection factors, is reported as:
This is the interference received in the downlink by terminals and consists of two components:
, Tech,
The effect of these this component is modelled via ,, , the inter-technology DL Noise
Rise due to terminals of technologies and it is specified in the Site DB.
, inter Tech,
where ,, is the inter-technology DL received interference for terminal served by cell
Tech
employing carrier due to terminals of technologies. , is the Channel Protection factor for
, Tech,
the technologies and it is input from Site DB for cell . , is the DL Noise Rise due
to terminals of the technologies and it is input from Site DB for cell . , is the DL thermal
noise power.
On the cell, in Site DB, the combined inter-technology total DL Noise due to -technology
terminals, disregarding any Channel Protection factors, is reported as:
, inter Tech,
where ,, is the received DL interference for terminal served by cell employing carrier
Tech
due to terminals of technologies. ,, is the Channel Protection factor for the
technologies and it is input from Site DB for cell . is the DL carrier overlap for victim carrier
and interfering carrier as given by (A33). is the total time-average transmitted power of -
technology cell . is the link loss between -technology cell and terminal .
For perfectly rectangular transmission and reception bandwidths, the overlapping bandwidth is given
by
1 (A28)
= max (0, min( , ) max( , )) .
We define the overlap factor as the proportion of the interfering carrier bandwidth that overlaps the
victim carrier, as follows
1 1 (A29)
= / .
The interferer has attenuation factor for interference transmitted on adjacent bandwidths (i.e. from
{ } to , and to { + }). The bandwidth overlap between the victim and these
adjacent bandwidths is given by
2
= max (0, min( , + ) max( , )) + (A30)
max (0, min( , ) max( , )) ,
and the corresponding overlap factor for these adjacent bandwidths becomes
2 2 (A31)
= / .
1 2 (A32)
= + ,
The inter-duplex mode overlap ratios are also included in the overall overlap calculations as
given by the following table
Inter-duplex Overlap (
)
Interferer
GSM, UMTS, FDD LTE, Wi-Fi TDD LTE
Victim
GSM, UMTS,
1 1
FDD LTE, Wi-Fi
Interference is scaled based on the 1 if both victim and interferer use the
frame configuration of the victim same frame configuration, else it is
TDD LTE LTE TDD carrier, i.e. proportion of scaled accordingly, i.e. proportion of
subframes in UL/DL. overlapping subframes in UL/DL.
(A33)
= .