IUS1.0#3a Detection of Cells Suffering From Island Problem

SIEMENS
Confidential - for internal use only
Use case
Tool:
Specification number:
Title:
ANATOM
3a
Related request Nr:
Detection of "island problem"
Author:
Date:
Description Version:
Relevant Specification
Krystian Majchrowicz
03.12.2004
1.0
Department:
Phone:
Description State:
COM SDC NA B1
+48 71 7992 441
IUS
Title
Error: Reference source not found
Date
Number
Author
3a
Error: Reference source not found
Version
Page
Error: Reference
source not found
IUS 1.0
1 of 23
SIEMENS
TABLE OF CONTENTS
1
GENERAL................................................................................................................................ 3
1.1
Contributions..................................................................................................................................... 3
1.2
Document History.............................................................................................................................. 3
1.3
Abbreviations..................................................................................................................................... 3
1.4
Hints.................................................................................................................................................... 3
OBJECTIVE............................................................................................................................. 4
REQUESTED KPIS/MEASUREMENTS...................................................................................5
3.1
The cell which generates the island.................................................................................................5
3.1.1
Sum of all received UL RxLEV measurements correlated with Timing Advance in range 7.............5
3.1.2
Sum of all received DL RxLEV measurements correlated with Timing Advance in range 7.............6
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
The rate of handover indications rejected due empty neighbour list................................................8
3.2
The KPIs used in further analysis.................................................................................................... 8
3.2.1
3.2.2
3.2.3
3.2.4
Sum of all received DL RxLEV measurements correlated with Timing Advance in range 1...........10
3.2.5
Sum of all received UL RxLEV measurements correlated with Timing Advance in range 2...........10
3.2.6
3.2.7
3.2.8
3.2.9
3.2.10
PROBLEM DETECTION........................................................................................................16
4.1
Problem description........................................................................................................................ 16
4.2
Problem reporting............................................................................................................................ 17
4.2.1
Used filters and threshold.............................................................................................................. 22
4.2.2
Additional analysis possibilities with ANATOM..............................................................................23
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
2 of 23
SIEMENS
1 General
1.1
Contributions
In addition to the authors named on the cover page, the following persons have collaborated on
this document:
M. Lipski
A. Rocchetti
1.2
Document History
Version
0.1
0.2
0.3
1.0
1.3
Date
10.10.2004
19.10.2004
09.11.2004
03.12.2004
Change
Initial version
Change of the concept
Change of the concept due to A. Rocchetti suggestions
Set to IUS
Abbreviations
BSC
BSCN
BTS
BTSN
HO
KPI
NB
SACCH
TA
TCH
1.4
COM SDC NA B1
COM MN PG NT NE 5
Base Station Controller

Base Station Controller Number
Base Transceiver Station
Base Transceiver Station Number
Handover
Key Performance Indicator
Neighbour
Slow Associated Control Channel
Timing Advance
Traffic Channel
Hints
Formulas as denoted in chapter 3 can be copied into ANATOM formula editor to be used in
ANATOM. Extra files representing an export of the used KPIs and the used reports are included:
AnatomKPIExport_us
er_ISL.sql
Title
Number
Author
3a
Detection_of_cells_s
erving_the_island.arc
TA_distribution_in_d
ownlink.arc
TA_distribution_in_u
plink.arc
Date
Version
Page
IUS 1.0
3 of 23
SIEMENS
2 Objective
The island problem means the situation where MS is served by a BTS, which is not a best server
for the area where the MS is currently staying. An island is defined as an area where the service is
provided by another BTS within the area of other best server.
Cell 2
Cell 1
BTS1
Cell 2
Cell 2
Best server: Cell 1
BTS2
Best server: Cell 2
The picture above shows an island problem. Cell 2 generates the island problem. The island is the
area marked yellow for which the best server is BTS2. However, according to coverage plan the
best server for this area is supposed to be BTS1. The coverage area for BTS1 is not continuous
it does not follow a regular distribution. It means that in coverage area served by the BTS1, the
coverage provided by the other cell (BTS2) exists. If areas far outside the continuous best server
area are also covered by the cell (as it is shown above), this might lead to performance
degradation of the network. In this area, there can be more call drops for calls set-up, because
handover might not be possible. The serving area where island problem occurs can also suffer
from bad handover performance due to wrong NB list. Additionally BTS power resources are
wasted to serve far mobiles what increases interference.
The geographical localization of the area, where such a situation can occur, should be detected
and further optimisation steps should be taken.
The goal of this use case is to detect cells suffering from island problem and to get a hint where
these coverage islands might be located. Detection of this problem could give some valuable
information in taking decision while optimising network coverage.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
4 of 23
SIEMENS
3 Requested KPIs/measurements
3.1
The cell which generates the island.
Long name:
Short name:
Description:
Formula:
Remarks:
KPIs/ PM counters
used in formula:
Anatom category:
Aggregation:
3.1.1
Sum of all received UL RxLEV measurements correlated with Timing Advance in

range 7
Long name:
Short name:
Description:
Formula:
Remarks:
Title
Number
Author
The cell which generates the island

ISLAND
This KPI can show two different results 0 or 1 with the meaning 0=cell
does not serve the island and 1=cell serves the island.
anatom_globals.log_or(anatom_globals.log_or(anatom_globals.log_or(a
natom_globals.gt(TA7_UL,0),anatom_globals.gt(TA7_DL,0)),anatom_gl
obals.log_or(anatom_globals.gt(TA6_UL,0),anatom_globals.gt(TA6_DL,
0))),anatom_globals.log_and(anatom_globals.log_or(anatom_globals.gt(
TA5_UL,0), anatom_globals.gt(TA5_DL, 0) ) ,
anatom_globals.gt(HO_IND_REJ_RATE_C1, 0.25) ) )
The cell is generating the island if for last two ranges of TA defined to
cover the area far outside the cell there are some measurements in UL
or DL. Another indication for the problem is if there are some
measurements for TA5 in UL or DL and at the same time more then 25%
of all HO indications are rejected due to empty neighbour list. The user
can change this threshold by editing the KPI formula with ANATOM
formula editor to his specific needs.
TA7_UL
(new, see chapter 3.1.1)
TA7_DL
TA6_UL
TA6_DL
TA5_UL
(new, see chapter 3.1.5
TA5_DL
HO_IND_REJ_RATE_C1
Island problem
SUM
3a
Sum of all received uplink RxLEV measurements correlated with Timing

Advance in range 7
TA7_UL
This KPI calculates the number of all received RxLEV measurements
correlated with timing advance range 7 in uplink direction. The result of
this KPI is dependent on the setting of the received level bands for the
correlated RXLEV-TA measurements (TA from band 7).
rollup_from.trx(BSCN, BTSN, "RXLEV0_TA7_UL", "SUM") +
rollup_from.trx(BSCN, BTSN, "RXLEV7_TA7_UL", "SUM")
Since received level correlated with TA measurements are done by
counters on the TRX level, and the island analysis are done on the BTS
level, the rollup function was used in KPI to aggregate data on the
required level.
Date
Version
Page
IUS 1.0
5 of 23
SIEMENS
KPIs/ PM counters CRXLVTAD [8,16,24,32,40,48,56,64](raw counter 8.2)

used in formula:
Anatom category: Island problem
Aggregation:
SUM
3.1.2
Sum of all received DL RxLEV measurements correlated with Timing Advance in

range 7
Long name:
Sum of all received downlink RxLEV measurements correlated with

Timing Advance in range 7
Short name:
TA7_DL
Description:
correlated with timing advance range 7 in downlink direction. The result
of this KPI is dependent on the setting of the received level bands for the
Formula:
rollup_from.trx(BSCN, BTSN, "RXLEV0_TA7_DL", "SUM") +
rollup_from.trx(BSCN, BTSN, "RXLEV7_TA7_DL", "SUM")
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.1.3

range 6
Long name:

Advance in range 6
Short name:
TA6_UL
Description:
Formula:
Remarks:
required level.
used in formula:
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
6 of 23
SIEMENS
Anatom category:
Aggregation:
3.1.4
Island problem
SUM

range 6
Long name:

Short name:
TA6_DL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.1.5

range 5
Long name:

Advance in range 5
Short name:
TA5_UL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
7 of 23
SIEMENS
3.1.6

range 5
Long name:

Short name:
TA5_DL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.1.7
The rate of handover indications rejected due empty neighbour list.
Long name:
Short name:
Description:
The rate of handover indications rejected due empty neighbour list

HO_IND_REJ_RATE_C1
This KPI shows rate of handover indications rejected due empty
neighbour list in relation to all handover indications.
Formula:
NO_HO_ATT_C1 / (anatom_globals.value_add(NO_HO_ATT_C1,
NO_HO_ATT_C2, NO_HO_ATT_C3, NO_HO_ATT_C4) +
anatom_globals.value_add(INTER_BSC_HO_ATT, INTER_HO_ATT,
INTER_SYS_HO_ATT) )
Remarks:
Only one KPI is defined making no difference between intracell, intercell,
interBSC and intersystem HO.
KPIs/ PM counters INTRA_HO_ATT
(predefined 11.1.1a)
used in formula:
INTER_HO_ATT
INTER_BSC_HO_ATT
INTER_SYS_HO_ATT
NO_HO_ATT_C1..C4
(raw counter NHOINRHA [1..4] 1.43)
Aggregation:
AVG
3.2
The KPIs used in further analysis
3.2.1

range 0.
Long name:
Short name:
Description:
Title
Number
Author
3a

Advance in range 0
TA0_UL
Date
Version
Page
IUS 1.0
8 of 23
SIEMENS

Formula:
Remarks:
required level.
KPIs/ PM counters CRXLVTAD [1,9,17,25,33,41,49,57] (raw counter 8.3)
used in formula:
Aggregation:
SUM
3.2.2

range 0.
Long name:

Short name:
TA0_DL
Description:
Formula:
Remarks:
required level.
KPIs/ PM counters CRXLVTAD [1,9,17,25,33,41,49,57] (raw counter 8.3)
used in formula:
Aggregation:
SUM
3.2.3

range 1.
Long name:
Short name:
Description:
Title
Number
Author
3a

Advance in range 1
TA1_UL
Date
Version
Page
IUS 1.0
9 of 23
SIEMENS
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.4

range 1.
Long name:

Short name:
TA1_DL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.5

range 2.
Long name:
Short name:
Description:
Title
Number
Author
3a

Advance in range 2
TA2_UL
Date
Version
Page
IUS 1.0
10 of 23
SIEMENS
Formula:

Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.6

range 2.
Long name:

Short name:
TA2_DL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.7

range 3.
Long name:
Short name:
Description:
Formula:
Title
Number
Author
3a

Advance in range 3
TA3_DL
Date
Version
Page
IUS 1.0
11 of 23
SIEMENS

Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.8

range 3.
Long name:

Short name:
TA3_DL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.9

range 4.
Long name:
Short name:
Description:
Formula:
Title
Number
Author
3a

Advance in range 4
TA4_DL
Date
Version
Page
IUS 1.0
12 of 23
SIEMENS

Remarks:
required level.
used in formula:
Aggregation:
SUM
3.2.10 Sum of all received DL RxLEV measurements correlated with Timing Advance in
range 4.
Long name:

Short name:
TA4_UL
Description:
Formula:
Remarks:
required level.
used in formula:
Aggregation:
SUM
Note: As the ranges for correlated TRX measurements are configured through BSC database the
settings of the ranges have to be known when constructing/interpreting the KPIs.
The correlated TRX measurements are created using the following command:
CREATE SCANCTRX: NAME=SCANCTRX:scann, OBJLST= [,START=] [,STOP=], [RECINT=]
[,RXLVR=] [,TIMADVR=] [,FER=] [,FERSERTYPE=];
The setting for the receive level bands is done through the parameter RXLVR.
This parameter requires 7 input values, which define 8 ranges for RXLEVred (Input_value1,
Input_value2Input_value7);the input_values are defined by means of the rangeBound<n> fields
(<n>=1..7) of the RXLEV_RED parameter. The allowed input values for RXLEV are 0 to 63, as
defined in GSM 05.08.
The correspondence between the Input_values, RXLED_RED and RXLEV is the following:
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
13 of 23
SIEMENS
RXLEV_RED_Range0:
RXLEV_RED_Range1: Input_value1 <
RXLEV
RXLEV
RXLEV
RXLEV
RXLEV
RXLEV
RXLEV
RXLEV
Inputvalue1
Inputvalue2
Inputvalue3
Inputvalue4
Inputvalue5
Inputvalue6
Inputvalue7
Validity range:
rxLevRanges
rangeBound1: 063 (default value = 7)
Using the default values would lead to the following ranges
Range 0
-103
dBm
Range 1
-104-95
dBm
Range 2
-94-87
dBm
Range 3
-86-79
dBm
Range 4
-78- 71
dBm
Range 5
- 70- 63
dBm
Range 6
-62- 55
dBm
Range 7
> -55 dBm
The setting for timing advance bands is done through the parameter TIMADVR.
This parameter requires 7 input values, which define 8 ranges for the Timing Advance TAred
(Input_value1, Input_value2Input_value7); the input values are related to the Timing Advance
(TA) and Timing Offset (TO) of the measurement report.
(TA = TOMeasurementreport + TAMeasurementreport )
The TA value is then related to steps of about 550 meters.
The allowed input values for TA are 0 to 216 (integer).
The correspondence between the Input_values, TA_RED and TA is the following:
TA_RED_Range0:
TA_RED_Range1: Inputvalue1 <
TA
TA
TA
TA
TA
TA
TA
TA
Inputvalue1
Inputvalue2
Inputvalue3
Inputvalue4
Inputvalue5
Inputvalue6
Inputvalue7
If there are no input parameters defined, the default values shall be taken.
Default values (inputvalue1-inputvalue2--inputvalue7) = 1-2-3-4-5-6-7;
Using the default values would lead to the following ranges:
Range 0
TA1
Range 1
1<TA2
Range 2
2<TA3
Range 3
3<TA4
Range 4
4<TA5
Range 5
5<TA6
Range 6
6<TA7
Range 7
7<TA
It is very important to properly define the range bounds for TA values by correct setting the
Inputvalue1- Inputvalue7, because it determines whether the island will be identified or not.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
14 of 23
SIEMENS
The user must be aware that the default values of TIMADVR parameter will hardy lead to the
meaningful results as they are not related to the real cell dimension.
For needs of this use case it is necessary to define input values of the parameter TIMADVR
according to the following configuration:
The TA ranges: TA_RED_Range0 .. TA_RED_Range3 cover the whole cell area in this way that
first three ranges cover the biggest part of the cell and range TA_RED_Range3 covers the border
but it is still part of the cell coverage area. The range TA_RED_Range4 should cover small belt
around the cell (approximately 2 km wide), TA_RED_Range5 should still cover relatively small area
and the last two ranges (TA_RED_Range6 and TA_RED_Range7) should cover the left largest
area.
This is done in order to analyse TA distribution and detect whether the cell serves the island (TA
values from the ranges outside the cell).Therefore it is strongly recommended to adjust setting of
the parameter TIMADVR in the scanner to the size of cell radius. Obviously the size of the cell
depends on the clutter type.
For the suburban were cells with radius of 10 km exist it is suggested to use the following values:
Inputvalue1 = 6,
Inputvalue2 = 12,
Inputvalue3 = 18,
Inputvalue4 = 20,
Inputvalue5 = 24,
Inputvalue6 = 34,
Inputvalue7 = 50,
which correspond to TA bands 0-216.
Using the recommended values would lead to the following ranges:
Range 0
TA6
Range 1
6<TA12
Range 2
12<TA18
Range 3
18<TA20
Range 4
20<TA24
Range 5
24<TA34
Range 6
34<TA50
Range 7
50<TA
For the clatter types where cells with smaller cell radius exists (below 2 km) it is not possible to
analyse the TA distribution in specified in this use case way, because it needs 4 ranges with at
least 4 different TA values what corresponds to at least 2 km of the cell radius.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
15 of 23
SIEMENS
4 Problem detection
4.1
Problem description
The important matter of the detection process is to identify the symptoms, which can point out cells
with island problem. The idea of this use case is to identify these cells which generate the island.
a) TA values from the ranges defined for the area outside the cell
As it is described in chapter 3 for needs of this use case it is necessary to define input values
of the parameter TIMADVR in this way that the TA ranges: TA_RED_Range0 ..
TA_RED_Range3 cover the whole cell area while TA_RED_Range4 and TA_RED_Range7
cover the area outside the cell. Since last two ranges TA_RED_Range6, TA_RED_Range7 are
defined to cover the largest part of the zone outside the cell coverage area there should be no
traffic at all (no measurements with TA6 or TA7). Therefore it is enough that cell has some
(more then 0) measurements with TA 6 or TA 7 to be pointed as generating the island.
The range TA5 also covers the area beyond the nominal cell radius, however it is relatively
near to the cell coverage area and there is some risk of dragging the call from the cell to this
area. To exclude the risk of identifying the cell with many dragged calls (instead of identifying
the cell generating the island) the amount of HO indications rejected due to empty NB list must
be high.
b) High rate of handover indications rejection rate due to empty neighbour list.
If the INTERCELL HANDOVER CONDITION INDICATION with the content The list of
preferred neighbour cell is empty was received from BTS it means that handover was
supposed to be performed but due to lack of suitable target cell in NB list, it was not triggered.
The indication of this problem means that handover was necessary but no neighbour was
available. This could happen in case of lack of coverage or missing neighbour.
If the mobile is served by the cell A but should be served by the cell B it receives the BA list
from cell A however it can happen that BA list wasnt received properly due to insufficient signal
level on SACCH caused by lack of coverage. In this situation the island problem is a specific
case of coverage problem.
Since high rate of handover indications rejection rate due to empty neighbour list may not
necessary mean island problem but poor coverage or missing neighbour this symptom was joined
together with TA values from the ranges defined for the area outside the cell to indicate cells
serving the island. It is defined that cell serves the island in case that it has some measurements
from the range TA5 defined for the area beyond the cell radius and additionally high rate of
rejected HO indications due to empty NB list exit.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
16 of 23
SIEMENS
4.2
Problem reporting
A specific report was defined in ANATOM to detect the described island problem and to display it
to the user.
The report is called: Detection_of_cells_serving _the_island.arc
and can be opened through universal report template in ANATOM.
After the report is opened the user has to specify objects and time range to be analysed and starts
the report by pushing the button Refresh. Afterwards the following result will be displayed for the
selected criteria.
The report contains information about island problem based on the KPIs as defined in chapter 3.
The results are grouped by BSCN and CELLGLID_CI (Cell Global ID Cell Identifier).
Extra information about the network performance is given through the TCH DROP_RATE and
TCH_DROP_ERLH. In order to identify whether the cell serves one or more island the amount of
measurements for TA 5..TA7 in UL and DL is presented.
If the user is now interested in seeing the details for BSC0 he can expand the data grid to CGI
level by expanding BSC0. The user then will see the following details:
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
17 of 23
SIEMENS
It can be noticed that cell 10190 is indicated as serving the island for each of nine observation
days. Additionally, the amount of TCH drops per Erlanghour is more then twice higher then the
average of the whole BSC region and the rate of TCH drops is four times higher then the average.
Note:
For this use case it is very important to perform measurements with BSC parameter (TIMADVR)
set according to the strategy described in chapter 3. Since for the network presented on the
examples, this parameter was not set properly, the results are not representative. Therefore there
are so many examples of detected cells serving the island.
Further information can be exposed by opening the details for the affected cell. As for the report
more than one day were selected, the details for the different days are displayed.
Since ANATOM also offers geographical representation of data the analysis results can also be
displayed on a map. From the predefined report, the user can switch to geographical
representation by choosing the related sheet named geographical.
The pre-selected KPIs are applied automatically to this sheet. The network elements should
remain marked, so the user neednt specify them again. The only thing to be specified is the
desired day from the time selection panel:
and KPI which should be displayed from drop-down menu (i.e. ISLAND_HOST)
By pressing the button Refresh the data will be displayed on the map.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
18 of 23
SIEMENS
The cell marked in red generates the island.

The user now wants to identify the BTS of interest on the map. For this purpose he can use the
feature Find cell
provided by ANATOM. The user selects the cell he wants to find on the map
and specifies the radius of the surrounding he wants to display around the cell in terms of km.
In this example the geographical display will change displaying the site in the center where the cell
with the following attributes, BSCN=0 and BTSN=1.03 belongs to. A radius of 20 km around the
evaluated cell will be displayed. Also the neighbours belonging to the cell will be indicated by
connecting lines to the neighbor cells.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
19 of 23
SIEMENS
As it can be noticed the cell detected as serving the island has only two neighbours and each of
them is indicated as the cell with the problem.
If the cell serving the island was detected there is the possibility to verify the results by analysing
the distribution of TA values. For this purpose two additional reports to support the use case were
prepared. These are:
TA_distribution_in_downlink.arc and TA_distribution_in_uplink.arc
and they can be opened through universal report template.
After the first report is opened the user has only to specify objects and time range to be analysed
and start the report by pushing the button Refresh. Afterwards the following result will be
displayed for the selected objects and time range. For the cell 10190 BTS(0.002) on October 21 st
the distribution looks like:
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
20 of 23
SIEMENS
As it can be noticed there are many measurements for TA ranges covering the area outside the
cell. Obviously as it was mentioned before the results are not representative due to the fact that the
TA configuration was not implemented in the network.
To check if the similar distribution occurs for uplink direction, the user has to open the second
report. After refreshing of the report, the following result is displayed:
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
21 of 23
SIEMENS
4.2.1
Used filters and threshold
Following thresholds are used for problem detection and are predefined through KPI definition.
1
The cells which serve the island

AND
OR
TA5_ UL
TA5_ DL
HO_IND_REJ_RATE_C1
TA6_ UL
TA6_ DL
TA7_ UL
TA7_ DL
OR
>0
>0
>0.25
>0
>0
>0
>0
If in uplink or downlink there are some measurements (more then 0) with TA from ranges defined to
cover the largest part of area far outside the cell (TA6 and TA7) then the cell is pointed as serving
the island.
The problem of serving the island also exists in case there are some measurements in UL or DL
from ranges defined to cover the zone beyond the nominal cell radius relatively near to the cell
coverage area and at the same time the handover indication rejection rate due to empty NB list is
higher then 25%.
Remark: The user can change the applied thresholds by changing the KPI definition in ANATOM
formula editor.
Example:
Formula
editor
Applied
threshold
The formulas of the KPIs using counters from the TRX level have to be adapted to the settings
used for correlated TRX measurements to the specific needs of the user.
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
22 of 23
SIEMENS
4.2.2
Additional analysis possibilities with ANATOM
If the cell serving the island was pointed it might be interested for the user to find the cell which
hosts this island. In order to this the reports presented before (TA_distribution_in_downlink.arc
and TA_distribution_in_uplink.arc) can be used. If the distribution of the TA ranges covering the
cell coverage area (TA0..TA3) is non continuous (there are some gaps) this can indicate two
phenomenons:
the traffic is not distributed equally over the served area (depends on the type of terrain
forest, lake, etc.)
the evaluated cell host an island all subscribers, who should be served by this cell are
in fact served by other one.
On the example below we have gap for TA1 in UL (very few measurements in comparison to
the adjacent ranges). As it was mentioned above the reason could be the hosted island or the
terrain where there is almost no traffic (for instance lake).
Remark: Further possibilities are described in ANATOM user manual and related documents.
Related documentation:
ANATOM user manuals

MapInfo Professional User Guide
Title
Number
Author
3a
Date
Version
Page
IUS 1.0
23 of 23

IUS1.0#3a Detection of Cells Suffering From Island Problem

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IUS1.0#3a Detection of Cells Suffering From Island Problem

Uploaded by

Copyright:

Available Formats

SIEMENS

Confidential - for internal use only

Error: Reference source not found

Confidential - for internal use only

The cell which generates the island.................................................................................................5

The rate of handover indications rejected due empty neighbour list................................................8

The KPIs used in further analysis.................................................................................................... 8

Used filters and threshold.............................................................................................................. 22

Additional analysis possibilities with ANATOM..............................................................................23

Confidential - for internal use only

Base Station Controller

Confidential - for internal use only

Best server: Cell 1

Best server: Cell 2

Confidential - for internal use only

The cell which generates the island.

Sum of all received UL RxLEV measurements correlated with Timing Advance in

The cell which generates the island

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

KPIs/ PM counters CRXLVTAD [8,16,24,32,40,48,56,64](raw counter 8.2)

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

The rate of handover indications rejected due empty neighbour list.

The rate of handover indications rejected due empty neighbour list

The KPIs used in further analysis

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

correlated with timing advance range 0 in uplink direction. The result of

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

rollup_from.trx(BSCN, BTSN, "RXLEV0_TA2_UL", "SUM") +

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

rollup_from.trx(BSCN, BTSN, "RXLEV1_TA3_UL", "SUM") +

Sum of all received DL RxLEV measurements correlated with Timing Advance in

Sum of all received downlink RxLEV measurements correlated with

Sum of all received UL RxLEV measurements correlated with Timing Advance in

Sum of all received uplink RxLEV measurements correlated with Timing

Confidential - for internal use only

rollup_from.trx(BSCN, BTSN, "RXLEV3_TA4_UL", "SUM") +