Professional Documents
Culture Documents
Actix Spotlight User Guide Aug 2010
Actix Spotlight User Guide Aug 2010
User Guide
August 2010
www.actix.com
The content of this manual is provided for information only, is subject to change without
notice, and should not be construed as a commitment by Actix. Actix assumes no
responsibility or liability for any errors or inaccuracies that appear in this documentation.
Copyright Actix 2010. All rights reserved. All trademarks are hereby acknowledged.
www.actix.com
Contents
1 ABOUT SPOTLIGHT .....................................................................................6
1.2 USING SPOTLIGHT TO SOLVE NETWORK PROBLEMS ...................................................... 7
1.3 ABOUT SPOTLIGHT PROJECTS ............................................................................... 9
www.actix.com
www.actix.com
1 About Spotlight
Todays performance optimization and troubleshooting processes are typically
inefficient, costly, and error prone. Engineering teams commonly use disparate
tools that are poorly integrated lacking the automation and scalability
fundamental for rolling out and maintaining complex wireless networks.
Actix Spotlight lowers the overall cost of performance optimization by delivering
maximum engineering productivity in a managed workflow.
Designed by optimization engineers, for optimization engineers, Spotlight
identifies key performance indicators, provides automated root-cause
troubleshooting, coverage and interference identification, and concise reporting.
Engineers can solve and report on more problems faster by eliminating time
consuming data manipulation and manual deduction.
Grade of Service this determines the relative grade of service for cells,
based on user-defined thresholds.
Neighbor List Analyses this grooms 3G-3G and 3G-2G neighbor lists,
based on scanner data for sites positioned within a user-defined radius.
1.1.3 Reporting
Spotlight displays the results of its automatically generated analyses on
integrated, professional-quality reports including embedded maps.
www.actix.com
5
2
3
6
1.2.2 Optimize neighbor lists and export suggested changes to the OMC
Use the Neighbor List analyses in the Radio Network Explorer. This process should
be performed as part of the rollout phase of a network to construct and optimize
the adjacency lists of each cell, and throughout the life of the network as changes
to traffic and tilt affect the coverage pattern and interference interaction between
the cells.
www.actix.com
Template used for the project. This defines the extent of the data from the
drive test files that you want to process and store within Spotlight's
database, and defines which KPIs and reports will be used in the project.
The term KPI (key performance indicator) means not simply a statistic that
reflects network performance in some way, but also a related pre-defined
analysis. For all of the KPIs that represent an issue, an overall summary is shown
in the Spotlight Summary Dashboard side panel. However, the analysis is
provided in either the Event Explorer or the Radio Network Explorer, depending
on the KPI type:
Event KPIs - Most of these KPIs relate to a specific type of call or session
failure event, such as dropped calls or handover, call setup or location
update failures, etc. and include automated root cause diagnosis and
drilldown to the sequential message data at the click of a button.
However, some of these KPIs relate to general events (such as call
attempts) in order to provide context for the failure events and these do
not include diagnostics and drilldown functionality.
Radio Network KPIs - These KPIs relate to general issues for the radio
network, such as coverage, pilot pollution, missing neighbors, and so on.
For these KPIs, the Radio Network Explorer provides a detailed analysis
that is very specific to the particular issue.
Reports provide summaries, tables, charts, and maps that can be saved as an
Excel workbook or Web page.
www.actix.com
10
Analyzer
Group
Analyzer Name
Purpose
Site Name
CDMA_Site
SiteName
Site Number
CDMA_Site
SiteID
Latitude
CDMA_Site
Latitude
Longitude
CDMA_Site
Longitude
Sector Number
CDMA_Cell
Sector ID
Sector-specific information
useful for display on maps
(can be alpha or numeric)
Azimuth
CDMA_Cell
Azimuth
www.actix.com
11
Parameter
Analyzer
Group
Analyzer Name
Purpose
Beamwidth
CDMA_Cell
Beamwidth
PN Offset
CDMA_Cell
PN
Base Station
Power
CDMA_Cell
EIRP
Mobile Country
Code
CDMA_Cell
MCC
System Identity
CDMA_Cell
SID
Network Identity
CDMA_Cell
NID
Broadcast
Identity
CDMA_Cell
BID
PctPilot
CDMA_Cell
PctPilot
PctTraffic
CDMA_Cell
PctTraffic
PctPaging
CDMA_Cell
PctPaging
PctSync
CDMA_Cell
PctSync
Active Set
Search Window
Setting
CDMA_Cell
SRCH_WIN_A
Neighbor Set
Search Window
Setting
CDMA_Cell
SRCH_WIN_N
List of neighbors
CDMA_Cell
CDMANeighborList
Sector Display
Wildcard
CDMA_Cell
Face_Display
Sector Display
Wildcard
CDMA_Cell
Azimuth_Display
Sector Display
Wildcard
CDMA_Cell
Phase_Display
www.actix.com
12
Parameter
Analyzer
Group
Analyzer Name
Purpose
Layer Type
CDMA_Cell
LayerType
The figure below is an example of a delimited CDMA file that could be used to
import a site list into Analyzer. Though the columns can be in any order for
import into Analyzer, the figure shows all of the REQUIRED fields. Additionally,
the Excel spreadsheet must be saved as a TEXT file for import into Analyzer.
The Site ID field must contain a unique value for each site location.
Beware of non-unique Site IDs that is, entries that have multiple sets of
latitudes and longitudes for the same Site ID. Duplicated Site IDs will
result in site markers appearing on the map without sector wedges. Site
Names do not need to be unique they are just used for labeling
purposes.
13
Before importing new cells into Analyzer, ensure that Analyzer is pointing
to a valid cell site database.
A valid cell site database is a text file in which the first line contains the
text below:
; #NetworkData datafile
C:\Program Files\Actix\Analyzer\Bin\Cellrefs
The file to be populated need not be named cellrefs.txt. Rename this file
with a meaningful name in order to prevent the file from being overwritten
during reinstallation.
To point the Analyzer to the file you wish to populate with the new cell site data,
use the File Location line in the Tools > Preferences dialog. See the section on
Loading Cell Site Data later in this document for more details.
www.actix.com
14
The Network Explorer display consists of two panels. The left panel
contains a tree view of the network element data. The right panel shows
details about relevant parameters for the current selection. If you have
pointed Analyzer to a cellrefs file containing only header information, you
will not see any cell site data at this time.
2
From the toolbar, select Import > Import From New Template to open
the Import dialog.
In most cases, the default information under the General Settings and
Coordinate Information headers will apply. Adjust these settings if
necessary.
Click Next.
www.actix.com
15
Expand the CDMA_Site data node. Click in the Column field next to the
Site_Name parameter. Select the parameter name from your site
database that corresponds to the Site_Name parameter. Repeat for each
of the required fields in the CDMA_Site data node, based on the table
below (See Appendix A: Cell Site Parameters for more information on
other technologies):
Field
Site_Name
Optional, but this field is frequently used for the site label.
SiteID
Required, and this field must be unique for each site in the
database.
Latitude
Required
Longitude
Required
www.actix.com
16
10 Expand the CDMA_Cell data node. Click in the Column field next to the
Sector_ID parameter. Select the parameter name from your site database
that corresponds to the Sector_ID parameter. Repeat for each of the
required fields in the CDMA_Cell data node, based on the table below (See
Appendix A: Cell Site Parameters for more information on other
technologies):
Field
Sector_ID
Azimuth
Required
Beamwidth
Required
EIRP
Optional
PN
Required
MCC
Optional
SID
Optional
www.actix.com
17
Field
NID
Optional
BID
Optional
PctPilot
Optional
PctTraffic
Optional
PctPaging
Optional
PctSync
Optional
SRCH_WIN_A
Optional
SRCH_WIN_N
Optional
CDMANeighborList
Optional
Face_Display
Azimuth_Display
Phase_Display
LayerType
11 Click Finish when all the columns have been assigned. If the current
workspace contains existing site data, you will be asked whether you want
to remove existing data before importing new data. Select Yes to
overwrite existing data. Select No to append to existing data.
If any errors occur during the import, a pop-up message will indicate that
an error log has been created. The error log specifies the cause of each
error encountered and can be found in:
C:\Program Files\Actix\Analyzer\Bin\Cellrefs\ImportErrors.log
12 Inspect the cell data in the Network Explorer by expanding the
All_CDMA_Site_Elements folder in the left-hand pane of the Network
Explorer.
13 Double-click on any site name in the right hand pane. The Name, Location
and ID of the site will appear, as well as a folder containing CDMA Cell
Elements. Drill into the CDMA Cell Elements folder and examine the values
corresponding to each sector.
14 To save the formatted site information, select the Save button.
www.actix.com
18
15 Close the Network Explorer by clicking the X at the upper right hand
corner.
16 After closing the Network Explorer, view a new map by selecting View >
Display New Map.
17 If cell icons do not appear on the map, right click on the CDMA_Cell layer
in the map legend at the left hand side of the map window. Select Zoom to
Layer to zoom the map to the appropriate location. Be sure to close the
map with the X at the upper right hand corner to save all changes to the
map view.
www.actix.com
19
Using a text editor such as Windows Notepad, copy all of the second
cellrefs file apart from the first line, and paste it in at the end of the first
cellrefs file.
You now have a cellrefs file that can import data for both technologies.
In the Change Preferences dialog, on the File Location line, click on the
name of the current cellrefs file.
In the Open dialog, navigate to the cellrefs file you would like to use and
select Open.
A message box will be displayed saying that the new cellrefs file takes
effect when a new workspace is loaded. Click OK to close the message
box. Analyzer loads cells upon opening Analyzer or starting a new
workspace. From the Main Menu, choose File > New Workspace to
create a new workspace.
In the new workspace, click View > Display New Map. If cell icons do
not appear on the map, right click on the CDMA_Cell layer in the map
legend at the left hand side of the map window. Select Zoom to Layer to
zoom the map to the appropriate location. Be sure to close the map with
the X at the upper right hand corner to save all changes to the map
view.
20
In the Layer Control dialog box, select the site layer (named CDMA_SiteSite_Name)
Under the Properties heading in the Layer Control dialog, press the
Labels button.
The MapInfo-style Label Properties box will appear. Check each of the
following options:
Show
In the Label Properties box, use the drop down Data Field menu to
determine the label format to display. Currently, there are two formats of
labels from which to choose:
If you wish to offset the label from the cell site symbol, use the options in
the Position box in the Label Properties dialog.
If you wish to change the font of the labels, use the Label Style button in
the Properties dialog.
The Site Labels have been formatted. Next, format the Cell Labels:
1
In the Layer Control dialog box, select the cell layer (named CDMA_CellBeamwidth-PN)
Under the Properties heading in the Layer Control dialog, press the Labels
button
The MapInfo-style Label Properties box will appear. Check each of the
following options:
Show
www.actix.com
21
In the Label Properties box, use the drop down Data Field menu to
determine the label format to display. All CDMA_Cell parameters are
available as options for labeling.
The PN Label shows the PN for each sector, displayed next to the sector. If
you wish to offset the label from the cell site symbol, use the options in
the Position box in the Label Properties dialog.
If you wish to change the font of the labels, use the Label Style button in
the Properties dialog.
Click OK in the Label Properties dialog, and then OK in the Layers dialog to
apply the labels.
www.actix.com
22
Use the Cell Color drop-down choose how to color the field. To make all
sectors the same color, specify an unused field (i.e. MCC). To color sectors
by face (i.e. 1 = red, 2 = yellow, 3 = blue) choose Sector_ID.
Site coloring will appear as specified. To modify face colors, expand the
CDMA_Cell parameter in the legend. Right-click on individual ranges and
choose Selected Ranges Style to modify colors.
Note that the sector need not be colored and labeled by the same parameter. The
figure below shows sectors colored by Sector_ID and labeled with the PN. Use the
Layer Control dialog to adjust labeling as desired.
www.actix.com
23
From the main menu, select Cells > Search for Cells.
From the main menu, select Window > Tile Horizontally or Window > Tile
Vertically to arrange the CellRefs Search dialog and the map in the
workspace.
Use the Add, Edit and Delete buttons to modify search criteria.
Click the Search Now button to show in the Results window all matching
cell sites from the current cellrefs file.
From the Results window, select a row to highlight and center the
corresponding sector on the map.
Click the Highlight All button to highlight all matching sectors on the
map.
www.actix.com
24
From the main menu, select Cells > Display Cell Data.
From the main menu, select Window > Tile Horizontally or Window > Tile
Vertically.
Click on a sector wedge or site dot on the map. Details about that sector
or site will appear in the Display Cell Data window.
www.actix.com
25
www.actix.com
26
3 Starting Spotlight
To start Spotlight, click on Actix Software from the Windows Start menu (or, if
you have a combination of licensed products, select Spotlight from the
Engineering Process dialog).
This screen is now displayed:
If you have just started using Spotlight, you will want to create a New
Project.
If you want to Delete a listed project, note that you will be asked to
confirm your choice.
Note that you can also choose to start in classic mode, without the Spotlight
interface and analyses, and directly investigate the data using Analyzer's rich tool
set.
www.actix.com
27
4 Creating a Project
4.1 Step 1: Choose Name and Template
This page is the first step in creating a new Spotlight project.
www.actix.com
28
You can also use the settings and thresholds links to set various other
options for your project.
CellRefs Select a valid cellrefs file that contains the details (name, ID,
and location, etc.) of all of the cell sites and sectors that you want to
analyze. If you want to analyze data from more than one technology, the
cellrefs file must contain the information for all of those technologies.
Note Spotlight always makes a local copy of the
selected cellrefs file, in case the original cellrefs file is
updated to reflect changes made to the network. The
Spotlight project database relies on the associated
cellrefs file remaining unchanged if it is, the project
will no longer work. Spotlight is designed to be used
for short-duration drive test campaigns, so this
should not present a problem and if you do need to
use the new cellrefs data, simply create a new
project that references the new cellrefs file.
Settings Click this link to open the Preferences dialog box. This has
many options, many of which configure the way various specific types of
data are decoded. There are also a number of neighbor list settings for
CDMA and UMTS these are used to fine-tune the algorithms used by the
neighbor list analyses in the Radio Network Explorer.
www.actix.com
29
Although you can change these settings using the Data Settings link in the
Radio Network Explorer's top panel, you should set them using the link on
this page when you create the project.
Note When you work in Spotlight, make sure that
you do not enable the Automatic Import options in
the CellRefs group of Preferences.
Thresholds Click this link to open the Thresholds Editor, where you can
configure the user-defined thresholds that are used in Spotlight.
Thresholds are used in Spotlight in two main ways:
www.actix.com
30
Spotlight does not expect that the cellrefs file will change after you have
started loading datathe addition of even a single cell sector in the
cellrefs file can result in incorrect results within Spotlight (this is why
Spotlight is not compatible with the Automatic Import option for cellrefs
data.)
By saving and reloading the cellrefs file and other preferences and thresholds with
the project, Spotlight avoids these potential problems. However, it does mean
that any changes you subsequently make to the preferences and thresholds while
working on the project will be lost next time you reload the project.
For example, you can change the neighbor list preferences using the Data
Settings link in the Radio Network Explorer's neighbor list pages. As soon as you
close the dialog box, the page will be updated to reflect the new settings.
However, next time you reload the project, the neighbor list settings will revert to
those that were selected when you originally created the project.
You should therefore think through your requirements and set the settings and
preferences accordingly before you start loading data.
Note Although you can change preferences and
settings at any time using the Display Thresholds and
Preferences options on the main Tools menu, this is
not recommended when using Spotlight, because
changing the CellRefs file can cause incorrect results
and changing the other settings is potentially
confusing. Although changing most of the
preferences and thresholds will not affect the data
stored in your project's repository, it will affect
drilldown data and any data that you load into
Analyzer Classic for detailed analysis, with a potential
for confusing discrepancies between the two sets of
results. Also, the changes will be lost when you
reload the project, as explained earlier.
www.actix.com
31
www.actix.com
32
Once the list of chosen files has been populated, you can remove a specific
file by clicking the remove link at the end of the row. You can also use the
Remove All Files button if necessary.
Click Done to load the data and open the Summary Dashboard.
www.actix.com
33
If you have configured multiple devices during the template configuration phase,
a separate tab per device will appear in the dashboard.
Note that due to the potential amount of information
on display, Spotlight is designed to be used at full
application window size, so you should keep your
Spotlight application window maximized at all times.
www.actix.com
34
If your current project uses Global Filters, a related link appears in the navigation
bar. Click on the link to show a dialog similar to this:
This dialog allows you to specify any files or streams that you want to exclude
from the analysis, and allows you to filter by time (not shown above).
Once you have specified the filter, note that you need to click the Add Filter link
on the right to create the filter.
If you have configured regional filtering, this dialog will also give you the option
to filter by region.
www.actix.com
35
The Analyzer Classic tab allows you to load selected files for analysis in Analyzer:
www.actix.com
36
www.actix.com
37
CDMA
EcIo_1stBest
EVDO
Consolidated_SINR_For_Nth_Best_Pilot[0]
GSM
ServRxLevSub
UMTS / HSPA
Uu_ActiveSet_EcNo[0]
From this map, you may be able to see one or more areas that may require
investigation, using a Spotlight report or by following a link for a critical or
important issue. Cell sector wedges are color-coded as follows:
green sectors were serving during part of the drive
yellow sectors were seen during the drive but were never serving
empty sectors were not seen during the drive
www.actix.com
38
www.actix.com
39
On the bottom right, the Show Excel Report button lets you open the report as
a Microsoft Excel file. From here, you can use the functionality of Excel to perform
further analyses on the data, or simply save the report as an Excel file or print it
out. Note that the maps are inserted into the Excel file as linked bitmaps. This
means that if you save the report in Excel for a project (A) and then run the
report again on a different project (B), the map bitmaps will be updated to reflect
the data in project B. If you subsequently reopen the workbook that you saved
for project A, Excel will display a message saying that the workbook contains
links to other data sources and asking whether you want to update them. Make
sure you choose the Don't Update option, because otherwise the report will be
updated with the maps from project B.
The Save button exports the report as a web page. Note that the web page has
an associated subfolder with a unique name containing various image and other
files relating to that report. However, the image files in each subfolder are always
called image1.gif, image2.gif, which may cause you problems in some situations.
www.actix.com
40
...or by clicking on an appropriate Issue link in the Issues panel on the left of the
Summary Dashboard page:
www.actix.com
41
The available Radio Network analyses for all technologies are as follows:
When you are viewing a particular Radio Explorer analysis page, you may find
that several analysis conditions apply, depending on the data loaded in the
project. At the top left, you will see a tab for each of these, taking you to the
appropriate analysis.
www.actix.com
42
Click on an appropriate issue link (or on the Radio Network Explorer image
followed by the Cell Coverage tab) to open the Cell Coverage analysis
page.
www.actix.com
43
Note that drive test data is binned according to the selections made in
step 4 of defining the project template. However, any events displayed on
the map (for example, by using the Events drop-down menu) will use the
exact position rather than a binned position, so events might not align
with the data points.
2
From the top table, click on the column heading # > Dist. to sort the
table by this value.
Look for differences between the # > Dist. value and # Samples. Be
careful not to include sectors with low sample counts (for example, below
50) as these will not be statistically relevant.
Here is one such site - Site A, Sector 3. Some samples (highlighted) are
shown well outside the overspill threshold (the red circle around the
selected cell) and close to another cell.
www.actix.com
44
Note that as the samples are now no longer seen, this is not a problem.
www.actix.com
45
Continuing to investigate the sectors from the top table, we find another
potential problem sector, Site B Sector 2.
There may be a problem with the highlighted neighboring sector, which could be
solved by downtilting the selected sector. First, check that the two cells are twoway neighbors.
www.actix.com
46
Map - When you click a row in the top table or on a site on the map, the
map shows the coverage wedge for the selected cell, EcIo and the
CDMA_Important_Issues (CDMA Grade of Service) attribute. The red circle
represents the coverage design boundary, configured using
SL_Overspill_Dist_Threshold. Data points outside this circle represent
overspill.
Side Panel - When no rows are selected, the side panel displays overview
information. A table shows details of the sites: Best EcIo, Rx Power, and
CDMA Grade of Service. When a site is selected, the panel shows various
KPI values for the site and a histogram of the distances at which the cell
was measured. A red line indicates the maximum range for the analysis,
as defined by SL_Overspill_Dist_Threshold.
Filters Select this link to specify filters for the table on the top panel.
Events List of the event attributes that can be plotted on the map. So
while looking at pilot pollution you could dump the CDMA Dropped Call
event on the map and quickly find out if the call dropped due to pilot
pollution. Currently plotted events are shown in red in the list.
www.actix.com
47
This table shows how the CDMA Grade of Service is computed at each point:
CDMA Grade of
Service
EcIo
condition*
MRx Power
condition*
MTX Power
condition*
Excess interference
Within
Exceed
Within
External interference
Within
Exceed
Exceed
Exceed
Exceed
Exceed
Within
Within
Within
Low Rx signal
Exceed
Within
Exceed
Poor coverage
Within
Within
Exceed
*Conditions:
www.actix.com
48
To start this analysis, from the Summary Dashboard page click on the
Radio Network Explorer button and click on this tab, or click on an
appropriate Issue in the left-hand Issues panel.
If you have not done so before, check the data settings that control the
neighbor list analysis algorithm.
You can now see the sector with the highest number of recommended
additions to its neighbor list.
www.actix.com
49
Click on the top row in the table to show information for that sector.
The map now shows green lines to each new neighbor recommendation.
The thickness of each line shows how well the suggestion meets the
criteria of the analysis. The circle represents the user-defined radius used
by the analysis to identify potential neighbors. The map also displays the
data points used in the analysis.
Note that drive test data is binned according to the selections made in
step 4 of defining the project template. However, any events displayed on
the map (for example, by using the Events drop-down menu) will use the
exact position rather than a binned position, so events might not align
with the data points.
5
www.actix.com
50
If you accept all suggestions for a sector, you can click the related button
in the table to mark your choice.
Note that the number beside the button changes to match your selection.
For example, if there were 6 suggested additions in the first row, with
none currently selected for export, the number would show 0/6. If you
clicked the button, the number would read 6/6. If you do not want to
select every recommendation for a sector, you can use the table in the
side panel on the left, which shows each recommendation for a sector
individually. So if you selected 3 additions, this would result in the number
reading 3/6. This can be useful if there are a large number of
recommendations and you need to keep track of how many you have
already selected.
7
Repeat this process for each row in the top table, as necessary.
You can now go through the same process for the 'Removals' column.
Note that by default the map does not show lines for removal
recommendations.
Once you are satisfied with the recommendations that you have selected,
you can output them to a CSV file. From the top of the page, click the
Export data link.
www.actix.com
51
Map - When a row is clicked in the top panel or a site is clicked on the
map, lines to neighbors are drawn from that site. The circle represents the
user defined radius (Maximum Intersite Distance) used by the analysis to
identify potential neighbors.
Filters Select this link to specify filters for the table on the top panel.
Events List of the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
Data Settings This link opens up a dialog box for configuring the
algorithm that Spotlight uses for the missing neighbor analysis, which can
be used to build lists of suggested neighbor cells to add and remove. All of
the options take effect immediately after you click OK. See below for more
information.
Default
Description
Ec/Io
Threshold
(dB)
-17
Maximum
Neighbors
13
Addition
Threshold (%)
www.actix.com
52
Setting
Default
Description
Removal
Threshold (%)
0.2
Minimum
Measurements
50
Maximum
Intersite
Distance
(meters)
20000
Angle to site
threshold
(degrees)
90
www.actix.com
53
Setting
Default
Description
Include
existing
neighbors
Selected
Only process
first best PN
Selected
Max Neighbor
List Size
32
Once a potential neighbor list has been calculated for each data point, they are
aggregated by serving cell to produce the recommended neighbor list. This is
compared with the existing list to calculate which are additions, retentions and
removals.
www.actix.com
54
The map shows the drive test data and the Pilot Pollution events. Note
that drive test data is binned according to the selections made in step 4 of
defining the project template. However, events plotted on the map (for
example, by using the Events drop-down menu) will use their exact
position rather than a binned position, so events might not align with the
data points.
www.actix.com
55
Sort the top table by Pilot Pollution Events and click on the top row
(that is, the sector with the most associated pilot pollution problems). In
this example that is CDMA_Site_41, Sector 3, which has 183 pilot pollution
events.
The map now highlights the selected sector. Outbound pollution lines are
drawn in red from the selected sector to the sectors being polluted. The
arrow on each line points from the polluting sector to the polluted sector.
The thickness of the lines indicates the degree to which pilot pollution was
detected for the selected sector, based on the loaded data. Inbound pilot
pollution lines are drawn in blue. Rolling over a line with the cursor shows
a pop-up message box giving more information on the pollution.
The left hand panel displays details of the outbound pollution for the
selected sector. In this example, the selected sector is polluting three
other sectors.
www.actix.com
56
Now de-select the Outbound Pilot Pollution Total box to hide the
outbound polluting lines and select the Inbound Pilot Pollution Total
box.
The left hand panel displays details of the inbound pollution for the selected
sector. In this example, the selected sector is being polluted by five other sectors.
Note that you can also sort this table - for example by distance, which helps you
identify distant sectors that might need downtilting, or if the serving cell needs
uptilting for greater coverage.
www.actix.com
57
Map - When you click a row in the top table or on a site on the map, lines
to inbound as well as outbound pollution are drawn from that site. All the
pilot pollution events involving the site are also plotted on the map. The
lines to polluters have a direction arrow suggesting inbound or outbound
pollution.
Side Panel - Shows details of the inbound and outbound pollution for the
selected site.
Filters Select this link to specify filters for the table on the top panel.
Attributes Lists the most commonly used attributes. Select one or more
to plot on the map. Currently plotted attributes are shown in red in the
list. The currently selected attributes will be kept as you move between
Spotlight's analysis pages.
Events Lists event attributes, Select one or more to plot on the map. So,
while looking at pilot pollution you could dump the CDMA Dropped Call /
EVDO Dropped Connections event on the map and quickly find out if the
connection was dropped due to pilot pollution. Currently plotted events are
shown in red in the list.
www.actix.com
58
Mobile Tx Power
Mobile Rx Power
RLP Rx Throughput
RLP Tx Throughput
DRC Rate
Before using this analysis, from the Summary Dashboard, select the
EVDO Report. Examine the report to obtain an overview of the system
performance.
Click on the Radio Network Explorer icon and then the System
Performance tab.
www.actix.com
59
Select from the Metrics drop-down menu the performance metric that you
want to examine.
Click the column title # < Threshold to show the sectors with the highest
number of samples that exceed the performance threshold. Check the #
Samples column to make sure that you are looking at data that is
statistically significant - for example, with 50 or more samples.
The Performance Met column shows whether the currently selected metric
has been achieved or failed for each sector.
Click on a row in the table to show various KPI values for the selected site
and a distribution chart for the currently selected metric.
www.actix.com
60
Click on the sector icon next to the Performance Met column heading to
show on the map those sectors that are not performing adequately.
Map - When you click a row in the top table or on a site on the map, the
map shows the corresponding metric for the selected site.
Side Panel - Displays various KPI values for the selected site and a
distribution chart for the currently selected metric.
Filters Select this link to specify filters for the table on the top panel.
www.actix.com
61
Events List of the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
Metrics Select the performance metric to be used for the analysis. You
can easily switch between metrics.
Notes
SINR
PER
Mobile Rx Power
Mobile Tx Power
www.actix.com
62
Metric
Notes
RLP Rx Throughput
RLP Tx Throughput
DRC Rate
Compares DataRate_Requested_ShortTermAverage_Kbps
with the user-defined DRC Rate threshold
EVDO_DRC_Rate_Requested_Threshold.
Low DRC % = (Bins with DRC < Thresh) / (Total
measurement bins) X 100
Performance criteria met, if:
(1 - % of Low DRC) >
(EVDO_DRC_Recommended_Performance_Threshold) %
www.actix.com
63
Visualize the neighbor BCCH, TCH and BSIC plans, within the range
G_Interference_Radius (drawn as a dotted blue circle on the map).
Note that several rows in the top table have a low sample count, '#', and
so are unreliable to use in this investigation.
www.actix.com
64
To remove rows with low sample counts, apply a Filter with a threshold
of, say, 50 counts. Click Add Filter and OK.
Important Issue
Attribute
ServRxQualSub
ServRxLevSub
NumNeighbors within 5 dB
www.actix.com
65
Examine the top table of the analysis for indications of poorly performing
cells relating to the Important Issue, and select likely candidate rows.
In the example below, a problem row has been selected. The first map
image shows the 'NumNeighbors within 5 dB' attribute plotted, which
highlights an area of poor dominance (drawn in red). The second map
image shows RxLev (Where Seen) plotted for the same sector, which
shows that it covers an unnecessarily large area. This could be corrected
by applying some downtilt to the sector.
www.actix.com
66
Use the top table to locate and select cells exhibiting this combination of
poor RxQual and good RxLev.
www.actix.com
67
Map - When you click a row in the top table or on a site on the map, the
map shows the coverage wedge for the selected cell, EcIo & RSCP. The red
circle represents the user-configured coverage design boundary, and data
points outside this circle represent overspill.
Analysis The page can operate in two analysis modes: Best Server and
Where Seen. Best Server mode shows the Ec/Io attribute when the
selected cell was the best server (and also RxQual). The Where Seen
mode shows RxLev whenever the cell was measured; coverage footprints
can only be seen for those cells that were best servers at least once during
the drive.
Filters Select this link to specify filters for the table on the top panel.
Events Lists the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
Attributes Lists the most commonly used attributes that can be plotted
on the map. Currently plotted attributes are shown in red in the list. The
currently selected attributes will be kept as you move between Spotlight's
analysis pages.
BCCH
# - Number of samples. Ensure that the site you are looking at has
a statistically viable number of samples.
> D(ist.) - Number of samples greater than the coverage design
boundary (defined by SL_Overspill_Dist_Threshold).
RxQual, RxLev, (Average, Max, Min). Note that clicking on the icon
only displays the Average value.
% > Beam Percentage of points outside the cell beamwidth.
% >180 Beam Percentage of points outside a hypothetical
beamwidth of 180 degrees.
Link Diff This is the difference between UL and DL pathloss and is
used to highlight cell with possible LNA (TMA) issues, if the
difference is greater the 8 dB, where:
UL = UE Tx Power - BTS Sensitivity + BTS Antenna Gain
DL = BTS EIRP - RxLevSub
www.actix.com
68
Poor Ql, Poor Lv and No Dom - see Coverage criteria below for
details.
Side Panel - Each tab displays various KPIs for the selected site. Note that
if you have the Visualization tab selected and you select a sector not
included in the visualization, you will lose the other tabs, and will need to
click on a row in the top table to show them again.
www.actix.com
69
Distance tab - Displays a histogram of the distances at which the cell was
measured. A red line at the top indicates the maximum range for the
analysis (equating to the red circle on the map), as defined by
SL_Overspill_Dist_Threshold (changeable from the Tools, Display
Thresholds command). Note that the side panel only shows Best Server
data, so if you set the Analysis (see below) to 'Where Seen', the map will
only show Where Seen data, so there may appear to be a discrepancy
between the two views.
Visualization tab - Displays BCCH, TCH (if available in the cellrefs file) and
Co BSIC co- and adjacent channel interference on the map by coloring in
the interfering sectors, out to a distance defined by the threshold
G_Interference_Radius (which can be changed using the Tools, Display
Thresholds command). See also the previous worked example of GSM
visualization.
Note that the color is determined by the first satisfied condition, in the
following order: BCCH co-interference, TCH co-interference, BCCH
adjacent upper, BCCH adjacent lower, TCH adjacent upper, TCH adjacent
lower.
www.actix.com
70
In the TCH example below, there is 1 BCCH channel and 3 TCH channels
used by the sector. Each row shows three interfering TCH channels, and so
the %Intrf is 100% x 3/4 = 75%.
www.actix.com
71
www.actix.com
72
Criteria
ServRxQualSub <
G_RxQualSub_Max threshold
Poor Signal
Strength
ServRxLevSub <
G_RxLevSub_Min threshold
No Serving Cell
Dominance
No Dom
Good Design
G. Design %
*This is the percentage of data points where one (or more than one) condition
applies.
www.actix.com
73
To start this analysis, from the Summary Dashboard page, click on the
Radio Network Explorer button and click on this tab, or click on an
appropriate link in the left-hand Issues panel.
If you have not done so before, check the data settings that control the
neighbor list analysis algorithm. In this example, we will be interested in
the Minimum Samples and the Addition Threshold. If you alter a data
setting, the analysis will immediately update.
www.actix.com
74
Click on the top row in the table to show information for that sector.
The map now shows lines to the recommended additions (there are many
additions in this example as the cellrefs file does not contain any 3G-2G
neighbor definitions - therefore there are also no retentions or removals
suggested). The thickness of each line shows how well the suggestion
meets the criteria of the analysis. The circle represents the radius of the
Maximum Intersite Distance (defined in the Data Settings dialog) used by
the analysis to identify potential neighbors.
The map also displays the data points used in the analysis. The side panel
on the left shows each recommendation for a sector individually, sorted by
the % of data points that meet the recommendation algorithm.
Note that drive test data is binned according to the selections made in
step 4 of defining the project template. However, any events displayed on
the map (for example, by using the Events drop-down menu) will use the
exact position rather than a binned position, so events might not align
with the data points.
www.actix.com
75
Repeat this process for each row in the top table, as necessary.
You could now go through the same process for the 'Removals' column
(this example contains no 'removals' suggestions). Note that by default
the map does not show lines for removal recommendations.
www.actix.com
76
Once you are satisfied with the recommendations that you have selected,
you can output them to a CSV file. From the top of the page, click the
Export data link.
Map - When you click a row in the table or a site on the map, lines to
neighbors are drawn from that site. The circle represents the user-defined
radius (Maximum Intersite Distance) used by the analysis to identify
potential neighbors. The map also shows the data points used in the
analysis.
Filters Select this link to specify filters for the table on the top panel.
Attributes Lists the most commonly used attributes that can be plotted
on the map. Currently plotted attributes are shown in red in the list. The
currently selected attributes will be kept as you move between Spotlight's
analysis pages.
Events Lists the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
Data Settings This link opens up a dialog box for configuring the
algorithm that Spotlight uses for the missing neighbor analysis, which can
be used to build lists of suggested neighbor cells to add and remove. All of
the options take effect immediately after you click OK. See below for more
information.
www.actix.com
77
Default
Description
RxLev
Threshold
(dB)
-95
Reporting
Range
(dB)
Addition
Threshold
(%)
Removal
Threshold
(%)
0.2
Minimal
Samples
50
Maximum
Intersite
Distance
(meters)
5000
Only
process
first best
ARFCN
Selected
Max
Neighbor
List Size
32
www.actix.com
78
Setting
Default
Description
Angle to
site
threshold
(degrees)
90
www.actix.com
79
7.8.2 Example
The Summary Dashboard shows an Important Issue relating to Poor Coverage.
Hovering over the link shows the thresholds used to identify this issue.
Note that these thresholds have already been applied to the loaded data, and
changing the thresholds at this point will have no effect on the analysis.
1
www.actix.com
80
To remove rows with low sample counts, apply a Filter with a threshold
of, say, 50 counts by selecting #Samples, > and enter 50. Click Add
Filter and OK.
www.actix.com
81
Color the cells by RSRP by clicking on the multi-cell icon beside the column
heading (the icon should become colored to indicate this is toggled on).
Looking at the map, note that there are some samples with poor RSRP
despite being very close to the problem sector.
www.actix.com
82
Top Panel - Shows a table of summary information. The table contains the
following information:
Scanner
# - Number of samples. Ensure that you are looking at a
statistically sensible number of samples.
> Dist - Number of samples greater than the coverage design
boundary (defined by SL_Overspill_Dist_Threshold).
RSRP, RSRQ (Max, Min, Ave).
> Beam Percentage of points outside the cell beamwidth.
>180 Beam Percentage of points outside an imaginary
beamwidth of 180 degrees.
Clicking on a row in this table causes the side panel to display more
information about the site. The map zooms to the site and displays its
coverage.
Map - When you click a row in the top table or on a site on the map, the
map shows the coverage wedge for the selected cell, RSRP and RSRQ. The
red circle represents the user-configured coverage design boundary, and
data points outside this circle represent overspill.
Side Panel
Quality tab Displays a quadrant chart with the percentage values of
points in good/bad RSRP and good/bad RSRQ, as defined by
LTE_Scan_PoorRSRP_Threshold and LTE_Scan_PoorRSRQ_Threshold.
Dist tab Displays a histogram of the distances at which the cell was
measured. A red line indicates the maximum range for the analysis, as
defined by SL_Overspill_Dist_Threshold.
Vis tab Displays cell details.
Analysis Select LTE Scanner Where Seen or Best Server analysis mode.
Changing the mode affects the RSRP attribute that is displayed on the
map. Best Server mode shows the RSRP when the selected cell was the
best server. The Where Seen mode shows the RSRP whenever the cell was
measured; coverage footprints can only be seen for those cells that were
best servers at least once during the drive. In multi-carrier environments,
you can perform analyses from the perspective of one carrier.
Cell Search Visualize a cell on the map. Input a Site Name, Sector ID, or
PCI (previously named L1_CID) to visualize; this feature would color red
all the cell(s) matching the selected criteria.
Filters Select this link to specify filters for the table on the top panel.
Events Lists the event attributes that can be plotted on the map.
Currently there are no events to display.
Attributes Lists the most commonly used attributes that can be plotted
on the map. Currently plotted attributes are shown in red in the list. The
currently selected attributes will be kept as you move between Spotlight's
analysis pages.
www.actix.com
83
To start this analysis, from the Summary Dashboard page, click on the
Radio Network Explorer button and click on this tab, or click on an
appropriate link in the left-hand Issues panel.
If you have not done so before, check the data settings that control the
neighbor list analysis algorithm. In this example, we will be interested in
the Minimum Samples and the Addition Threshold. If you alter a data
setting, the analysis will immediately update.
www.actix.com
84
Click on the top row in the table to show information for that sector.
The map now shows lines to the recommended additions (there are many
additions in this example as the cellrefs file does not contain any 3G-2G
neighbor definitions - therefore there are also no retentions or removals
suggested). The thickness of each line shows how well the suggestion
meets the criteria of the analysis. The circle represents the radius of the
Maximum Intersite Distance (defined in the Data Settings dialog) used by
the analysis to identify potential neighbors.
The map also displays the data points used in the analysis. The side panel
on the left shows each recommendation for a sector individually, sorted by
the % of data points that meet the recommendation algorithm.
Note that drive test data is binned according to the selections made in
step 4 of defining the project template. However, any events displayed on
the map (for example, by using the Events drop-down menu) will use the
exact position rather than a binned position, so events might not align
with the data points.
www.actix.com
85
Repeat this process for each row in the top table, as necessary.
You could now go through the same process for the 'Removals' column
(this example contains no 'removals' suggestions). Note that by default
the map does not show lines for removal recommendations.
www.actix.com
86
Once you are satisfied with the recommendations that you have selected,
you can output them to a CSV file. From the top of the page, click the
Export data link.
Map - When you click a row in the table or a site on the map, lines to
neighbors are drawn from that site. The circle represents the user-defined
radius (Maximum Intersite Distance) used by the analysis to identify
potential neighbors. The map also shows the data points used in the
analysis.
Filters Select this link to specify filters for the table on the top panel.
Attributes Lists the most commonly used attributes that can be plotted
on the map. Currently plotted attributes are shown in red in the list. The
currently selected attributes will be kept as you move between Spotlight's
analysis pages.
Events Lists the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
Data Settings This link opens up a dialog box for configuring the
algorithm that Spotlight uses for the missing neighbor analysis, which can
be used to build lists of suggested neighbor cells to add and remove. All of
the options take effect immediately after you click OK. See below for more
information.
www.actix.com
87
Default
Description
RxLev
Threshold
(dB)
-95
Reporting
Range
(dB)
Addition
Threshold
(%)
Removal
Threshold
(%)
0.2
Minimal
Samples
50
Maximum
Intersite
Distance
(meters)
5000
Only
process
first best
ARFCN
Selected
Max
Neighbor
List Size
32
www.actix.com
88
Setting
Default
Description
Angle to
site
threshold
(degrees)
90
Once a potential neighbor list has been calculated for each data point, they are
aggregated by serving cell to produce the recommended neighbor list. This is
compared with the existing list to calculate which are additions, retentions and
removals.
www.actix.com
89
A GSM scanner or handset stream that was logged at the same time. If a
handset stream is used, it must have been logged in idle mode.
These must have been loaded using a suitable matching cellrefs file, which
must contain a field called GSMNeighborList on the WCDMA_Cell network
element.
To start this analysis, from the Summary Dashboard page, click on the
Radio Network Explorer button and click on this tab, or click on an
appropriate Issue in the left-hand Issues panel:
www.actix.com
90
If you have not done so before, check the data settings that control the
neighbor list analysis algorithm. In this example, we will be interested in
the Minimum Sample Count and the Addition Threshold. If you alter a data
setting, the analysis will immediately update.
Click on the top row in the table to show information for that sector.
www.actix.com
91
The map now shows lines to the recommended additions (there are many
additions in this example as the cellrefs file does not contain any 3G-2G
neighbor definitions - therefore there are also no retentions or removals
suggested). The thickness of each line shows how well the suggestion
meets the criteria of the analysis. The circle represents the user-defined
radius (Maximum Intersite Distance) used by the analysis to identify
potential neighbors.
The map also displays the data points used in the analysis. The side panel
on the left shows each recommendation for a sector individually, sorted by
the % of data points that meet the recommendation algorithm.
Note that drive test data is binned according to the selections made in
step 4 of defining the project template. However, any events displayed on
the map (for example, by using the Events drop-down menu) will use the
exact position rather than a binned position, so events might not align
with the data points.
5
www.actix.com
92
If you disagree with a suggested addition, you may want to use the SC
Search feature to find an alternative sector to add to the neighbor list.
Note that in this case you will not be able to output your choice, and will
need to make the correction to the switch manually (for example, by
editing the CSV file).
Repeat this process for each row in the top table, as necessary.
You could now go through the same process for the 'Removals' column
(this example contains no 'removals' suggestions). Note that by default
the map does not show lines for removal recommendations.
Once you are satisfied with the recommendations that you have selected,
you can output them to a CSV file. From the top of the page, click the
Export data link.
Map - When you click a row in the table or a site on the map, lines to
neighbors are drawn from that site. The circle represents the user-defined
radius (Maximum Intersite Distance) used by the analysis to identify
potential neighbors. The map also shows the data points used in the
analysis.
Filters Select this link to specify filters for the table on the top panel.
Attributes Lists the most commonly used attributes that can be plotted
on the map. Currently plotted attributes are shown in red in the list. The
currently selected attributes will be kept as you move between Spotlight's
analysis pages.
Events Lists the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
www.actix.com
93
Data Settings This link opens up a dialog box for configuring the
algorithm that Spotlight uses for the missing neighbor analysis, which can
be used to build lists of suggested neighbor cells to add and remove. All of
the options take effect immediately after you click OK. See below for more
information.
Default
UMTS
Threshold
Type
Description
Depending on which measurement your network uses for
determining when to hand over, select EcIo, RSCP, EcIo or
RSCP, or EcIo and RSCP.
EcIo
Threshold
(dBm)
RSCP
Threshold
(dBm)
-100
GSM
Neighbor
Threshold
(dBm)
-95
Minimal
Sample
Count
50
Maximum
Intersite
Distance
(meters)
5000
Addition
Threshold
(%)
www.actix.com
94
Setting
Default
Description
Removal
Threshold
(%)
0.2
Only
process
first best
SC
Selected
Max
Neighbor
List Size
32
Angle to
site
threshold
(degrees)
90
www.actix.com
95
Note that these thresholds have already been applied to the loaded data, and
changing the thresholds at this point will have no effect on the analysis.
10 From the Summary Dashboard, click on an appropriate issue link or the
Radio Explorer icon to open the Cell Coverage analysis page.
11 The Issues panel showed a high percentage of System Interference issues,
so examine the top table of the analysis for indications of poorly
performing cells. Note that several rows have a low sample count and so
are unreliable to use in this investigation.
www.actix.com
96
12 To remove rows with low sample counts, apply a Filter with a threshold
of, say, 50 counts. Click Add Filter and OK.
www.actix.com
97
15 Looking at the map, note that there are some samples with poor EcIo
despite being very close to the problem sector.
Note that drive test data is binned according to the selections made in
step 4 of defining the project template. However, any events displayed on
the map (for example, by using the Events drop-down menu) will use the
exact position rather than a binned position, so events might not align
with the data points.
16 So what other cells are interfering to cause this situation? Experiment with
plotting various Events and Attributes - plotting the Uu_ActiveSet_Count
attribute shows that there is only one clear server, Site 8130 Sector B.
This may indicate a missing neighbor.
www.actix.com
98
17 Click on the 3G Neighbor List tab. Note that the map and table keep the
focus on the selected cell.
Here we can see that there is a suggested addition to the neighbor list, so
exporting and using that new neighbor should solve the problem. See the
3G Neighbor List analysis for more information.
www.actix.com
99
Click on the issue link to open the Cell Coverage analysis page.
Filter out any rows with low sample counts, as described in the previous
example.
As the problem concerns data points outside the serving cell beamwidth,
sort by >180 Beam by clicking on the column heading.
Color the map cells by >180 Beam by clicking on the icon next to the
column heading.
Note that the top two sectors are in the same site. Select the top sector
row.
www.actix.com
100
Ensure that in the top panel, you select the Analysis 'Scanner - Where
Seen'.
Looking at the map, note that the samples seen for the selected sector
appear in the beam of the other offending sector. Select the other sector
from the table or the map to confirm that this is a crossfeeder situation.
Top Panel - Shows a table of summary information. The table contains the
following information:
Scanner
# - Number of samples. Ensure that you are looking at a
statistically sensible number of samples.
> Dist. - Number of samples greater than the coverage design
boundary (defined by SL_Overspill_Dist_Threshold).
EcNo, RSCP (Max, Min, Ave).
> Beam. Percentage of points outside the cell beamwidth.
>180 Beam. Percentage of points outside an imaginary
beamwidth of 180 degrees.
Handset
# - Number of samples. Ensure that you are looking at a
statistically sensible number of samples.
> Dist. - Number of samples greater than the coverage design
boundary (defined by SL_Overspill_Dist_Threshold).
EcNo, RSCP (Max, Min, Ave).
Link Diff. This is the difference between UL and DL pathloss and
is used to highlight cell with possible LNA (TMA) issues, if the
difference is greater the 8 dB.
www.actix.com
101
Map - When you click a row in the top table or on a site on the map, the
map shows the coverage wedge for the selected cell, EcIo & RSCP. The red
circle represents the user-configured coverage design boundary, and data
points outside this circle represent overspill.
Side Panel - Displays various KPI values for the site selected and a
histogram of the distances at which the cell was measured. A red line
indicates the maximum range for the analysis, as defined by
SL_Overspill_Dist_Threshold.
Filters Select this link to specify filters for the table on the top panel.
Events Lists the event attributes that can be plotted on the map.
Currently plotted events are shown in red in the list.
Attributes Lists the most commonly used attributes that can be plotted
on the map. Currently plotted attributes are shown in red in the list. The
currently selected attributes will be kept as you move between Spotlight's
analysis pages.
www.actix.com
102
Sort the top table by Outbound Cells and click on the top row.
www.actix.com
103
In this example, as the selected sector 55662 looks like the best candidate
for investigation as it has a high number of Too Many Servers events, and
Outbound and Inbound Cell polluters.
3
De-select the Inbound Cells box to hide the inbound polluting lines.
The map now highlights the selected sector. Outbound pollution lines are
drawn in red from the selected sector to the sectors being polluted. The
arrow on each line points from the polluting sector to the polluted sector.
The thickness of the lines indicates the degree to which pilot pollution was
detected for the selected sector, based on the loaded data. Inbound pilot
pollution lines are drawn in blue. Rolling over the lines with the cursor
displays more detailed information (see the example below).
The map also shows the Too Many Server events. Note that drive test data
is binned according to the selections made in step 4 of defining the project
template. However, any events displayed on the map (for example, by
using the Events drop-down menu) will use the exact position rather than
a binned position, so events might not align with the data points.
4
The inbound polluters are shown by blue lines, and that you can hide or
show these polluting lines by clearing or checking the related box in the
top table. De-select Outbound Cells and select Inbound Cells.
On the map, to show lines to cells, drag a box around the area with a
cluster of Too Many Server events.
www.actix.com
104
There is no clear dominator in this area, and a few polluting cells are some
distance away, so you would need to improve the coverage in that area.
In the image below, the EcIo values have been plotted on the map to
confirm the situation near the Too Many Server events.
At this point you could use the Cell Coverage tab to see the best way to
improve the coverage for the selected sector.
6
To see how the selected sector is polluting other sectors, from the top
table, de-select Inbound Cells and select Outbound Cells.
www.actix.com
105
Map - Click a row in the top panel or a site on the map, to draw lines to
inbound as well as outbound pollution from that site. All the pilot pollution
events involving the site are also plotted on the map. The lines to polluters
have a direction arrow suggesting inbound or outbound pollution.
Side Panel - Shows details of the inbound and outbound pollution for the
selected site.
Filters Select this link to specify filters for the table on the top panel.
Attributes Lists the most commonly used attributes. Select one or more
to plot on the map. Currently plotted attributes are shown in red in the
www.actix.com
106
list. The currently selected attributes will be kept as you move between
Spotlight's analysis pages.
Events Lists event attributes. Select one or more to plot on the map. So,
while looking at pilot pollution, you could plot the UMTS Dropped Call
event on the map and quickly see if the call dropped due to pilot pollution.
Currently plotted events are shown in red in the list.
www.actix.com
107
A good value for the F factor is below 3 (or 4) over 95% of the cell area. If a cell
has a higher value, the capacity of this cell will be impacted, and even more so
when the network becomes loaded.
Note When examining drive data, the F-Factor is
very dependent on the route, because at the edge of
cells the F-factor will naturally be higher.
www.actix.com
108
www.actix.com
109
www.actix.com
110
Selecting the heading sorts the table by that KPI. The symbol beside the top table
heading indicates the additional effect of selection:
www.actix.com
111
In this example, EcIo has been selected from the Attributes menu at the top and
displayed on the map. There are some poor values surrounding the dropped call
event, which is expected for a handover problem. Plotting pilot pollution events
may also help you to understand the situation here.
Note that drive test data is binned according to the selections made in step 4 of
defining the project template. However, any events displayed on the map will use
the exact position rather than a binned position, so they may not necessarily
align with the data points.
Drilldown allows you to view selected data related to the event on the Drilldown
page, which shows a range of analysis views appropriate to the type of diagnosis.
For more information, see the section on Drilldown on p112.
Filters The table on the top panel can be filtered by adding filters
through this dialog
Events drop-down menu List of the event attributes that can be plotted
on the map. See the Attribute / Event Help (available from the Help menu)
for more information.
www.actix.com
112
Detailed event diagnostics - The left hand side panel provides a diagnosis
for the failure event, consisting of these sections:
www.actix.com
113
Task Failure Rate. Task is used to refer to any data upload or download;
for example, an FTP put or get, browsing a web page or a ping test.
For more information on the thresholds used to identify these issues, see
Appendix D: Data Service Analysis thresholds.
Clicking on an Issue link takes you to the Event Explorer page for Data Service
Analysis:
www.actix.com
114
Here is an example of a drilldown into upload data, showing the HSUPA Radio
Chart from the drilldown analysis:
In the first half of the Task, there are two main obvious causes for low
throughput:
In the second half of the Task, we can see a correlation between higher SGI and
higher throughput (labeled 1 in the screenshot).
www.actix.com
115
Here is an example of a drilldown into download data, showing the HSDPA Radio
Chart from the drilldown analysis:
Examining this HSPA call leads to three routes for improving the radio network
performances (labeled in the above screenshot):
1 Low UE frame usage
The throughput (the blue line at the top) clearly matches the UE frame usage
(the histogram near the bottom). Extended periods of low UE frame usage could
indicate that the HSPA network is congested in this area. The possible causes and
corresponding actions would be:
www.actix.com
116
The Iub link capacity cannot support the user traffic add more Iub
capacity for this Node B.
Change the HSPA cell change criteria in the RNC to speed up HSPA cell
changes.
The Scheduler in the Node B periodically reduces the scheduling for this
UE in order to average out the throughput between users.
The data buffer for the UE in the Node B empties periodically, because the
data gets transferred on the air interface faster than the Node B gets data
from the RNC. The reason could be a data buffer dimensioning issue
somewhere in the data transmission chain, or an Iub capacity issue.
www.actix.com
117
www.actix.com
118
Once you have input the Before Window and After Window values, click on Begin
Drilldown. This will take you to the detailed Drilldown page.
www.actix.com
119
The top Dropped Call event has been selected for drilldown; clicking on the Begin
Drilldown button starts the drilldown process and displays the drilldown page.
www.actix.com
120
The page shows several views to help you analyze the event in more detail.
Detailed Event Diagnostics are in a panel on the left, also showing the
originating data file name.
A map and the UMTS Event Navigator window display attributes relating to
the selected event.
This set of views, called a screen layout, is standard for this type of event. Each
drilldown that is based on a different failure event will have its own screen layout.
This particular layout provides most of the information needed to diagnose a
dropped call. The UMTS Event Navigator shows the event and the serving SC. The
charts give the SIR, EcNo, RSCP and Tx power information around the event.
Note All the views will have data only for the time
window specified in the previous step.
You can access standard Analyzer views from the View menu, and also make use
of the Replay control to step through the data.
www.actix.com
121
Check the box to the left of each file that you want to load into Analyzer
Classic.
www.actix.com
122
Files that are already loaded have their boxes checked and disabled, and
can be unloaded using the Unload All button (which is disabled if there are
no loaded files). Note that this does not affect the project database in any
way.
4
Click the Load Files button. This loads any checked files that are not
already loaded.
Once the load is complete, the current views are minimized and two new
views are displayed: an Attribute Explorer on the left, and a new Task
Window positioned in the top right corner of the available screen area,
containing a single Return to Spotlight link.
When you have finished using Analyzer Classic, you can click on the
Return to Spotlight link, which will restore the Spotlight view. If you do
not want to return to Analyzer Classic and re-examine the selected data,
you can now click on the Unload All button to close files loaded into
Classic. Note that this will not close any files that have been loaded into
Analyzer Classic which are not listed as loaded into the project repository.
www.actix.com
123
From the Spotlight Dashboard, click on the Reports link to open the
Reports dialog.
www.actix.com
124
Select the Attribute that you want to display on the output images. The
available options will depend on the selected Technology. Only one
attribute may be exported for each use of this function.
Now select the Footprint for the cell in each output image:
Where Seen the image only includes those points where the cell could
be seen during the drive(s). The cell is only included if it was best server
at some point in the drive(s).
Where Best the image only includes those points where the cell was the
best server during the drive(s).
Select how you want to Plot the results. This depends on the selected
Technology; the example shown is for UMTS Scanner, and the choice is By
SC or By Sector. One image will be exported for each SC, Sector or other
selection that meets the other criteria entered in this dialog.
If by SC (or BCCH etc.) is chosen, then all sectors on
that SC (and UARFCN if defined in the cellrefs) will be
exported in one image. Cells on the same SC but that
were not seen during the drive will not be
highlighted.
Select the Min Sample Count threshold. The number of points for the
attribute must be equal to or higher than this value for an image to be
exported.
Each image will cover the area of the Union of the bounds of the
attributes, plus the highlighted cells, plus a 4% padding. Select the Map
Image Format:
PNG The default map image format option, as PNG files are small yet
remain clear.
BMP This results in much larger graphics files, and is only recommended
if you intend to use the images with Microsoft Excel. If you use Insert
Object in Excel, you have the ability to link to a graphics file. Only links to
BMP files will show the actual image other formats will only show an
image icon.
The legend for a plot is always output in BMP format regardless of this
selection.
Enter the Map Image Size in pixels, where Size X is the width of the
image and Size Y is the height.
10 To display the coverage wedge and overspill circle, check the Coverage
Wedge box. The coverage wedge and overspill distance circle are drawn
by default
11 To export the legend for each image as a separate BMP image, check the
Legend box. The legend is not be exported by default.
12 Once you are satisfied with your selections, click the Generate button.
Spotlight will now cycle through the sectors and create an image for each
one that matches your criteria. Some sectors may appear on the screen
very briefly these failed to match the selected criteria.
www.actix.com
125
www.actix.com
126
www.actix.com
127
After clicking Done on the last page, you are returned to the New Project start
page, where the new template appears in the list of project templates.
Note For convenience, Spotlight appends the date
on which it was created to the project template's
name.
Template Name - Enter a unique name for the template. This must not
contain any of the following characters: \ / : * ? " < > |.
www.actix.com
128
The simplest scenario is when the data was logged by one handset and
optionally one scanner in a single drive test unit. In this scenario, it is
generally safe to combine the data from both logging devices into a single
Spotlight device, because generally, the handset and scanner data is
stored in different attributes and the KPIs and statistics are based on one
type of attribute or another and therefore provide a means of separating
the two types of data. However, you might want to separate the handset
and scanner data into separate devices for convenience or clarity.
Another common scenario is when data is logged by two handsets and one
scanner in a single drive test unit. Typically, one handset does a
succession of short (approximately 90-second) calls separated by 30
seconds of idle time. The other handset is for "long calls", in which the
handset stays in call until the call drops, whereupon the dialer immediately
starts a new long call. Typically, the short calls provide data for event
KPIs, such as the percentage of call setups that were successful, etc.,
whereas the long calls provide data for measuring the radio performance.
Combining the data would normally give misleading results. For example,
the long call data would by definition have an almost 100% dropped call
rate and so if used for event KPIs, it would skew the dropped call rate. For
www.actix.com
129
this scenario, you should therefore create separate devices for the short
and long call data.
A similar scenario occurs when a single drive test unit has two devices, but
one was used for voice calls and the other for data. Like scanner and
handset data, generally, data logged from voice and data calls is stored in
separate attributes, and KPIs and statistics are typically based on one type
or the other. However, for clarity it is generally advisable to separate the
data into different logical devices. This avoids any risk of combining data
inappropriately and thereby creating invalid KPIs.
All of the drive test scenarios that we have considered so far involve a
single drive test unit (that is, one vehicle plus logging equipment). When
there are multiple drive test units driving different routes on the same
days, there is no reason why you should not combine data logged for the
same purpose in the different drive test units. For example, it would
typically be valid to combine short call data collected by different drive test
units on the same days in different parts of a city or state. However, if the
data was logged for different purposes (such as the short and long call
data described above), you should generally separate it into different
logical devices, for the reasons explained earlier.
www.actix.com
130
You create a new device by clicking the Add Device button, which opens
this dialog:
Import From File - You can use this button to browse to a typical log file
that will be loaded into the project. When you select the file, Spotlight lists
the name of every data stream that it contains. When you select a name
in the list, Spotlight inserts the stream name into the Filter box above.
Typically, you would then edit it in the Filter box, in order to make the
filter more generally applicable.
When you are ready, click Add to add the device to the project template.
www.actix.com
131
www.actix.com
132
For performance reasons, select only those KPIs and reports that are
relevant for the tasks you plan to perform and the data you plan to load
into the projects based on this template. For example, if you are planning
to load only GSM voice data, deselect all of the KPIs and reports that do
not relate to GSM voice calls.
www.actix.com
133
One of the attributes is highlighted in red to indicate that it has been chosen from
the Attribute Picker panel.
www.actix.com
134
Binned Data Queries - This lists the binned data queries that relate to the
KPIs and reports that you selected in Step 3. Each of these contains a
number of attributes and binned queries that are used for display on the
map, etc. When you select a binned data query, the attributes and binned
queries it contains are listed in the central Attributes panel. You cannot
remove these, because they are required for the features that are
associated with the selected KPIs and reports. However, you can add
additional attributes using the Attribute Picker on the right side. Typically
each technology has two or more binned data queries. For example, for
UMTS there are binned data queries as follows:
If you want to add additional attributes, select the appropriate binned data
query to add them to. For example, if you are adding a UMTS scanner
attribute, select the UMTS Scanner BinnedData query.
Queries that have Sector Handle in their name are for internal use and
you should not add any attributes to them.
Attributes - This lists the attributes and binned queries that are in the
binned data query that is selected on the left side and any additional
attributes that you have added using the Attribute Picker on the right side.
The additional attributes are highlighted, indicating that you can remove
them. (You do this by selecting the attribute and clicking Remove
Attribute.)
Attribute Picker - This is a tree view that lists all of the possible attributes.
Select any attributes that you want to include. Make sure you add the
attributes to the appropriate binned data query as described above.
Note that array attributes are shown in the tree view as individual items,
rather than expandable items. What happens when you select an array
attribute depends on the internal structure of the binned data query that is
selected:
135
do not want to use. For example, for a "Top n" attribute, you might
want to delete all but the first three or four index positions. You
cannot add array attributes that have 32 or more possible index
positions.
However, for some binned data queries (such as the GSM Scanner
BinnedData query), when you select an array attribute, Spotlight
adds it to the list of attributes as a single item (using the array
indexer syntax) and automatically includes every index position for
which there is data.
Note Although Spotlight can handle a considerable
number of attributes, there are limits imposed by the
technologies that underlie the repository technology.
These limits are documented in detail in the
Repository Manager section. Note that the fast
binning option detailed below creates more compact
databases and avoids problems with the limit to the
number of "subselects" documented in the linked
topic.
11.4.2 Binning
The binning settings control how the device's binned data is stored in the
repository and how it is subsequently displayed on the map and the other binned
data views. Note that once the project is created, the binning settings cannot be
changed. For example, changing the binning settings in the Preferences dialog
does not affect data loaded into the Spotlight repository. (However, it does affect
the drilldown data and any Spotlight data that you have loaded into Analyzer
Classic.)
Spotlight always uses the location binning mechanism, which sorts the raw data
values into a geographical grid and then performs an averaging operation to
produce a single value for each square in the grid (sometimes call a bin). This
has the effect of smoothing the data and reducing the number of rows or data
points that would otherwise be stored in the database and subsequently
displayed. The averaging operation that is performed is determined by the
internal attribute definition. For most attributes, a simple average operation is
performed, but some use other operations, such as the mode or count.
The binning options are:
Fast binning - Select this option if you want to use the fast bin
aggregation method (this is recommended). This means that in bins that
the drive test(s) passed through more than once, the results from the last
drive will be displayed. De-select this option if you want the results from
all of the drives to be aggregated together. Although this is technically
more accurate, it is considerably slower, particularly when displaying data
on the map. In addition when working with very large volumes of data, the
increased accuracy is likely to be of limited value in practice. See Fast Bin
Aggregation in the online help for more information.
Units of measurement - The possible units are meters and arc seconds.
You must choose the unit that matches the projection system that you are
using. If the data will be displayed on vector-based maps, you can
www.actix.com
136
generally use arc seconds and the default projection system, which is the
World Geodetic System 1984 (WGS 84) projection system, which is used
by GPS. However, if the data is to be displayed on raster maps, you should
generally choose the projection system used in those maps and the correct
units for that system. See Map Projections in the online help for an
overview of the issues.
X and Y bin size - These define the dimensions of the squares in the
geographical grid. The X axis corresponds to longitude and the Y axis to
latitude. The sizes must be specified in the appropriate units for the
projection system. The default sizes are 3 arc seconds and 50 meters.
Note that using larger bin sizes reduces the size of the database and
improves performance.
For the Y axis, the approximate size in arc seconds can be calculated from
a size in meters using the following formula:
X and Y origin - By default, the starting point for the geographical grid is
the false origin (0, 0) defined for the selected projection system. This has
the advantage that, by default, all of the location grids are the same.
However, sometimes you may want to move the start point because, for
example, you want to align the grid with one used in another system. You
do this by specifying an offset for either or both of the coordinates in the X
origin and/or Y origin text boxes. You must specify the offset in the same
units as you used to define the size of the bins (and this must correspond
to the measurement system used by the projection system).
www.actix.com
137
Projection - Select the projection system that you want to use. The
options in the drop-down list are the projection systems that are
supported directly by Analyzer and that use the units of measurement
selected above. The Default option for arc seconds corresponds to the
WGS 84 projection system. There is no default option for meters, but you
can use one of the ED79 UTM (Universal Transverse Mercator) system
options. ED79 UTM is a generic map projection system that divides the
globe up into a number of zones. You need to select the appropriate zone
for the area in which the data was collected. See the online help section
ED79 UTM Zone Lookup for more information.
For the Regional Filters, you can choose to allow filtering by Cluster Name and
Clutter Type.
Note Regional filtering option is not shown in the
above example. To enable filtering by region, you
need to have already defined the regions, created a
new Spotlight Template and on the Filtering page
checked the relevant region types under Region
Filters.
When you click Done, you are returned to the new project page, where the new
template appears in the list of project templates.
www.actix.com
138
12 Troubleshooting Spotlight
12.1 No repository detected
Spotlight was unable to find your project database. Ensure that your MS SQL
service is active and try to start your project again, following these steps:
1
If the Status is blank, from the toolbar, click on the Start Service
button.
If the service does not restart, you will need to uninstall and reinstall Actix
Spotlight.
www.actix.com
139
Analyzer
Group
Analyzer Name
Purpose
Site Name
CDMA_Site
SiteName
Site Number
CDMA_Site
SiteID
Latitude
CDMA_Site
SiteLatitude
Longitude
CDMA_Site
SiteLongitude
Sector
Number
CDMA_Cell
Sector ID
Can be 1,2,3 etc.
or a combination
of site numbers
Sector-specific information
useful for display on maps.
Azimuth
CDMA_Cell
Azimuth
Beamwidth
CDMA_Cell
Beamwidth
PN Offset
CDMA_Cell
PN
Base Station
Power*
CDMA_Cell
EIRP
Mobile
Country
Code*
CDMA_Cell
MCC
System
Identity*
CDMA_Cell
SID
Network
Identity*
CDMA_Cell
NID
Broadcast
Identity*
CDMA_Cell
BID
PctPilot*
CDMA_Cell
PctPilot
PctTraffic*
CDMA_Cell
PctTraffic
PctPaging*
CDMA_Cell
PctPaging
140
Imported
Parameter
Analyzer
Group
Analyzer Name
Purpose
PctSync*
CDMA_Cell
PctSync
Active Set
Search
Window
Setting*
CDMA_Cell
SRCH_WIN_A
Neighbor Set
Search
Setting*
CDMA_Cell
SRCH_WIN_N
List of
neighbors*
CDMA_Cell
CDMANeighborList
Sector
Display
Wildcard*
CDMA_Cell
Face_Display
Sector
Display
Wildcard*
CDMA_Cell
Azimuth_Display
Sector
Display
Wildcard*
CDMA_Cell
Phase_Display
Layer type*
CDMA_Cell
Layer_type
*Optional.
Analyzer
Group
Analyzer Name
Purpose
Site Name
GSM_Site
SiteName
Site Number
GSM_Site
SiteID
Latitude
GSM_Site
Latitude
Longitude
GSM_Site
Longitude
141
Imported
Parameter
Analyzer
Group
Analyzer Name
Purpose
Sector
Number
GSM_Cell
SectorID
Can be 1,2,3,
etc, or a
combination of
site numbers
Sector-specific ID information
useful for display on maps.
Azimuth
GSM_Cell
Azimuth
Beamwidth
GSM_Cell
Beamwith
Base Station
Power
GSM_Cell
EIRP
Broadcast
Control
Channel
GSM_Cell
BCCH
Mobile
Network
Code
GSM_Cell
MNC
Mobile Color
Code
GSM_Cell
MCC
Location
Area Code
GSM_Cell
LAC
Cell ID value
GSM_Cell
CI
Cell ID value.
Base Station
Identity
Code
GSM_Cell
BSIC
Layer type
GSM_Cell
Layer_type
Analyzer
Group
Analyzer Name
Purpose
Site Name
LTE_Site
Site_Name
Site Number
LTE_Site
SiteID
Latitude
LTE_Site
Latitude
www.actix.com
142
Imported
Parameter
Analyzer
Group
Analyzer Name
Purpose
Longitude
LTE_Site
Longitude
Sector
Number
LTE_Cell
Sector_ID
Sector-specific information
useful for display on maps (can
be alpha or numeric)
Azimuth
LTE_Cell
Azimuth
Beamwidth
LTE_Cell
Beamwidth
EIRP*
LTE_Cell
EIRP
Downlink
EARFCN
LTE_Cell
DL_EARFCN
Layer1 Cell
Identity
LTE_Cell
PCI
MCC*
LTE_Cell
MCC
MNC*
LTE_Cell
MNC
* Optional.
Analyzer
Group
Analyzer Name
Purpose
Site Name
UMTS_Site
SiteName
Site Number
UMTS_Site
SiteID
Latitude
UMTS_Site
Latitude
Longitude
UMTS_Site
Longitude
Sector
Number
UMTS_Cell
Sector_ID
Sector-specific information
useful for display on maps
(can be alpha or numeric)
www.actix.com
143
Imported
Parameter
Analyzer
Group
Analyzer Name
Purpose
Azimuth
UMTS_Cell
Azimuth
Beamwidth
UMTS_Cell
Beamwidth
SC
UMTS_Cell
SC
EIRP*
UMTS_Cell
EIRP
MCC*
UMTS_Cell
MCC
MNC*
UMTS_Cell
MNC
LAC*
UMTS_Cell
LAC
CI*
UMTS_Cell
CI
Neighbor
List*
UMTS_Cell
WCDMANeighborList
Layer Type*
UMTS_Cell
LayerType
* Optional.
www.actix.com
144
www.actix.com
145
www.actix.com
146
www.actix.com
147
www.actix.com
148
www.actix.com
149
www.actix.com
150
www.actix.com
151
www.actix.com
152
14.3.2 Main
www.actix.com
153
14.3.4 RF
14.3.5 Throughputs
www.actix.com
154
www.actix.com
155
14.4.1 Report
www.actix.com
156
www.actix.com
157
www.actix.com
158
14.4.4 Radio
www.actix.com
159
14.4.5 CD Domain
www.actix.com
160
14.5.1 Report
www.actix.com
161
www.actix.com
162
14.5.3 Radio
The PDF and CDF of ALL the actual CQI samples present in the logs are provided.
In addition, the tables report the following statistics for CQI:
Mean
Mode
www.actix.com
163
Median
Total # samples
Maximum
95% Percentile
Minimum
The HARQ statistics section shows the distribution between ACK, NACK and DTX
samples of all the HARQ processes recorded. Details per call can be accessed at
the bottom of the page by clicking on the link below the table.
14.5.4 HS mobility
www.actix.com
164
www.actix.com
165
14.6.1 Report
www.actix.com
166
14.6.2 Overview
www.actix.com
167
www.actix.com
168
14.6.4 Radio
www.actix.com
169
www.actix.com
170
SL_Overspill_Dist_Threshold
CDMA_AvgForwardFER
This threshold is used for diagnosing areas of poor quality. Recommended value
is 2.
15.1.2.2
CDMA_EcIoCombinedThreshold
This threshold is used in conjunction with Mobile Rx Power and Mobile Tx Power
Thresholds to determine the diagnosis for the dropped call, failed call and voice
call with poor quality. Recommended value is -12 dB. Values should vary between
-16 and -12 dB.
15.1.2.3
CDMA_ImportantIssue_ExcessInterference
This threshold is used for filtering out files that have percentage of excess
interference cases less than the threshold. Recommended value is 2.
15.1.2.4
CDMA_ImportantIssue_ExternalInterference
This threshold is used to filter out the display of data in the CDMA Dashboard that
have percentage of bad EcIo, high Tx, good Rx problems cases less than the
threshold. Recommended value is 2.
15.1.2.5
CDMA_ImportantIssue_FwdLinkProblem
This threshold is used to filter out the display of data in the CDMA Dashboard that
have percentage of forward link problems cases less than the threshold.
Recommended value is 2.
www.actix.com
15.1.2.6
171
CDMA_ImportantIssue_LowRX
This threshold is used to filter out the display of data in the CDMA Dashboard that
have percentage of low rx problems cases less than the threshold. Recommended
value is 2.
15.1.2.7
CDMA_ImportantIssue_PoorCoverage
This threshold is used for filtering out files that have percentage of poor coverage
cases less than the threshold. Recommended value is 2.
15.1.2.8
CDMA_ImportantIssue_PoorQuality
This threshold is used to filter out the display of data in the CDMA Dashboard that
have percentage of calls with poor quality cases less than the threshold.
Recommended value is 2.
15.1.2.9
CDMA_ImportantIssue_RevLinkProblem
This threshold is used to filter out the display of data in the CDMA Dashboard that
have percentage of rev link problems cases less than the threshold.
Recommended value is 2.
15.1.2.10 CDMA_MobileRxPowerThreshold
This threshold is used in conjunction with EcIo and Mobile Tx Power Thresholds to
determine the diagnosis for the dropped call, failed call and voice call with poor
quality. Recommended value is -80 dBm. Values should vary between -75 and 90 dBm.
15.1.2.11 CDMA_MobileTxPowerMinFilterThreshold
This threshold is used in conjunction with Mobile Tx Power Max Threshold to filter
out messages when the transmitter is disabled due to high FFER. Default is -30.
15.1.2.12 CDMA_MobileTxPowerMaxFilterThreshold
This threshold is used in conjunction with Mobile Tx Power Min Threshold to filter
out messages when the transmitter is disabled due to high FFER. Default is 23.
15.1.2.13 CDMA_MobileTxPowerThreshold
This threshold is used in conjunction with EcIo and Mobile Rx Power Thresholds to
determine the diagnosis for the dropped call, failed call and voice call with poor
quality. Recommended value is 5 dBm. Values should lie between 0 and 10 dBm.
15.1.2.14 CDMA_PilotPollution_Count_Threshold
This is the absolute number of pilots (with Ec/Ios above
CDMA_PilotPollutionThreshold) required to trigger a pilot pollution event. The
recommended value is 3 and values should lie between 2 and 4.
15.1.2.15 CDMA_PilotPollutionThreshold
This threshold alerts the user of pilot pollution when the signal level falls below
this threshold. Recommended value is -14 dB. Values should lie between -10 and
-18 dB.
www.actix.com
172
EVT_CDMAImportantIssue
1 = Turns on the CDMA Important Issue Detect event diagram for CDMA
Troubleshooter; 0 = CDMA Important Issue analysis is turned off to improve file
load speeds. Default is 0.
15.1.3.2
EVT_CDMANeighborListIssueDetect
1 = Turns on the CDMA Neighbor List Issue Detect event diagram for CDMA
Troubleshooter; 0= CDMA Neighbor List Issue Detect analysis is turned off.
Default is 0.
15.1.3.3
EVT_CDMAServerKey
1 = Turns on the CDMA Server Key event diagram for CDMA Troubleshooter; 0 =
CDMA Server Key analysis is turned off to improve file load speeds. Default is 0.
15.1.3.4
UniqueNeighborList
1 = Turns on the unique neighbor list analysis for CDMA, EVDO Troubleshooter; 0
= unique neighbor list analysis is turned off to improve file load speeds. Default is
0.
CDMA_EcIoInterferenceThreshold
Recommended value is -15 dBm. The maximum should not be higher than 0 and
minimum should not be lower than -25 dBm.
15.1.4.2
CDMA_EVDO_TooManyActivePNsThreshold
In calculating "Too Many Servers", when 4 or more pilots (including the best
server) are within the threshold value in dB of the best server, it creates a "too
many server" event. Recommended value is 5 dB and the minimum and the
maximum should be around 1 and 10 dB.
15.1.4.3
CDMA_TooManyActivePNsThreshold
In calculating "Too Many Servers", when 4 or more pilots (including the best
server) are within the threshold value in dB of the best server, it creates a "too
many server" event. Recommended value is 5 dB and the minimum and the
maximum should be around 1 and 10 dB.
CDMA_CallDropRate
This threshold is used to determine the criterion for KPI acceptance in the
Repository views. The Call Drop Rate should not exceed 2% of all successful calls
in the busy hour. If the resulting KPI is equal or less than this value, it will be
flagged as accepted and will show up as a green tick mark in the KPI table. If it is
higher than this value, it will be flagged as failed and will show up as a red cross
in the KPI table. The default value is 2%.
www.actix.com
15.1.5.2
173
CDMA_CallSetupSuccessRate
This threshold is used to determine the criterion for KPI acceptance in the
Repository views. The Call Setup Success Rate should be in excess of 98% for
most GSM networks in the busy hour. If the resulting KPI is equal or in excess to
this value, it will be flagged as accepted and will show up as a green tick mark in
the KPI table. If it is less than this value, it will be flagged as failed and will show
up as a red cross in the KPI table. The default value is 98%.
15.1.5.3
CDMA_CallSetupTime
This threshold is used for determining calls with excessive setup time.
Recommended value is 2000 ms.
15.1.5.4
CDMA_OverAllSuccessRate
This threshold is used to determine the criterion for KPI acceptance in the
Repository views. The Overall Success Rate should be in excess of 98% for most
GSM networks in the busy hour. If the resulting KPI is equal or in excess to this
value, it will be flagged as accepted and will show up as a green tick mark in the
KPI table. If it is less than this value, it will be flagged as failed and will show up
as a red cross in the KPI table. The default value is 98%.
www.actix.com
174
www.actix.com
175
Diagnosis
Coverage Issue
Excessive Interference
Poor Coverage
External Interference
Low Rx Signal
Poor Quality
Pilot Pollution
Other
www.actix.com
176
HSDPA_CQI_Threshold
HSUPA_SGI_Threshold
This threshold is used to determine the minimum acceptable Serving Grant Index
value. The default value of 18 corresponds to ~10 dB. The HSUPA SGI format
group controls the exact mapping of the threshold values to dB values (shown
below).
Threshold
Value
dB
Threshold
Value
dB
Threshold
Value
dB
-9.5
14
6.0
28
20.0
-8.0
15
7.1
29
21.0
-6.6
16
8.1
30
22.1
-5.5
17
8.9
31
23.0
-4.4
18
9.9
32
24.0
-2.7
19
11.0
33
25.0
-1.9
20
12.0
34
26.0
-1.2
21
13.0
35
27.0
0.0
22
14.0
36
27.8
1.1
23
15.0
37
28.8
10
2.1
24
16.0
38
None
11
2.9
25
17.0
63
N/Av
12
4.1
26
18.0
13
5.1
27
19.0
www.actix.com
177
Absolute_ApplicationLowTput_DL_Threshold
Absolute_ApplicationLowTput_UL_Threshold
Application_LowTput_GPRS_DL_Threshold
Application_LowTput_GPRS_UL_Threshold
Application_LowTput_HSDPA_DL_Threshold
Application_LowTput_HSDPA_UL_Threshold
Application_LowTput_HSPA_DL_Threshold
Application_LowTput_HSPAPlus_DL_Threshold
Application_LowTput_HSPAPlus_UL_Threshold
www.actix.com
178
16.1.2.10 Application_LowTput_HSUPA_UL_Threshold
This threshold is used to determine the minimum acceptable application
throughput value for uplink in HSUPA for the Below Composite Threshold KPI. The
default value is 600 kB/sec.
16.1.2.11 ApplicationLowTput_Idle_DL_Threshold
This threshold is used to determine the minimum acceptable application threshold
value for downlink in Idle mode for the Below Composite Threshold KPI. Default is
the same as HSPA. Change this to correspond to the network that you are
testing.
16.1.2.12 ApplicationLowTput_Idle_UL_Threshold
This threshold is used to determine the minimum acceptable application threshold
value for uplink in Idle mode for the Below Composite Threshold KPI. Default is
the same as HSPA. Change this to correspond to the network that you are
testing.
16.1.2.13 ApplicationLowTput_UMTS_DL_Threshold
This threshold is used to determine the minimum acceptable application
throughput value for downlink in UMTS for the Below Composite Threshold KPI.
The default value is 200 kB/sec.
16.1.2.14 ApplicationLowTput_UMTS_UL_Threshold
This threshold is used to determine the minimum acceptable application
throughput value for uplink in UMTS for the Below Composite Threshold KPI. The
default value is 40 kB/sec.
www.actix.com
179
G_Cell_Reselect_Duration
This threshold determines the maximum time for a cell reselection. Any values
above this threshold will be flagged as excessive high cell reselection time.
Default is 15000ms.
17.1.1.2
G_Cell_Reselect_Time
This threshold determines the window during which cell reselections may take
place. Any two reselections occurring within this threshold will be flagged as
abnormally high cell reselections. Default is 15000ms.
17.1.1.3
G_RMAC_C_Value_Min
G_RMAC_CV_BEP_Max
G_RMAC_DL_TS_Min
G_RMAC_MEAN_BEP_Max
G_RMAC_Power_Reduction_Max
G_RMAC_Sign_Var_Min
17.1.1.9
180
G_RMAC_TAI_Max
This threshold is used to determine the maximum acceptable TAI value. Default is
10.
G_T3240_RAUTimer
This timer is used to determine the time (in ms) the system will wait for GPRS
MM Routing Area Update Request messages to be answered with a GPRS MM
Routing Area Update Accept before registering a Routing Area Update Failure.
Default is 15000ms.
17.1.2.2
G_T3310_AttachTimer
This timer is used to determine the time (in ms) the system will wait for GPRS
MM Attach Request messages to be answered with a GPRS MM Attach Accept
before registering an Attach Failure. Default is 15000ms.
17.1.2.3
G_T3321_DetachTimer
This timer is used to determine the time (in ms) the system will wait for GPRS
MM Detach Request messages to be answered with a GPRS MM Detach Accept
before registering an Detach Failure. Default is 15000ms.
17.1.2.4
G_T3380_PDPActTimer
This timer is used to determine the time (in ms) the system will wait for GPRS SM
Activate PDP Context Request messages to be answered with a GPRS SM Activate
PDP Context Accept before registering a PDP Context Activation Failure. Default is
8000ms.
EGPRS_Duration_Period
This threshold is used to determine the period over which the minimum
acceptable throughput value for RLC / LLC are evaluated in EGPRS. Default is
15000ms.
17.1.3.2
EGPRS_LLC_DL_Min
This threshold is used to determine the minimum acceptable throughput value for
LLC downlink in EGPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 5.
17.1.3.3
EGPRS_LLC_UL_Min
This threshold is used to determine the minimum acceptable throughput value for
LLC uplink in EGPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 1.
17.1.3.4
EGPRS_RLC_DL_Min
This threshold is used to determine the minimum acceptable throughput value for
RLC downlink in EGPRS. This factor is highly dependent on the typical allocation
of static / dynamic pdTCHs in your network. Default is 10.
www.actix.com
17.1.3.5
181
EGPRS_RLC_UL_Min
This threshold is used to determine the minimum acceptable throughput value for
RLC uplink in EGPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 2.
17.1.3.6
GPRS_Duration_Period
This threshold is used to determine the period over which the minimum
acceptable throughput value for RLC / LLC are evaluated in GPRS. Default is
15000ms.
17.1.3.7
GPRS_LLC_DL_Min
This threshold is used to determine the minimum acceptable throughput value for
LLC downlink in GPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 5.
17.1.3.8
GPRS_LLC_UL_Min
This threshold is used to determine the minimum acceptable throughput value for
LLC uplink in GPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 1.
17.1.3.9
GPRS_RLC_DL_Min
This threshold is used to determine the minimum acceptable throughput value for
RLC downlink in GPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 10.
17.1.3.10 GPRS_RLC_UL_Min
This threshold is used to determine the minimum acceptable throughput value for
RLC uplink in GPRS. This factor is highly dependent on the typical allocation of
static / dynamic pdTCHs in your network. Default is 2.
182
or GPRS_Events==14
or GPRS_Events==15
Attach Failure
(10 second window up to the event)
Where time - default(prev_time_where(x), 0) > 5000
and
GPRS_Attach_Reject
or GPRS_Attach_Failure
or GPRS_Attach_Aborted
or TEMSEvent_GPRS_Attach_Failure
or TEMSEvent_GPRS_Attach_Aborted
or GPRS_Events==8
or GPRS_Events==9
or GPRS_Events==10
PDP Context Activation Failure
(10 second window up to the event)
Where time - default(prev_time_where(x), 0) > 5000
and
GPRS_PDPContextAct_Reject
or GPRS_PDPContextAct_Failure
or GPRS_PDPContextAct_Aborted
or TEMSEvent_GPRS_PDPContextActivation_Failure
or GPRS_Events==2
or GPRS_Events==3
or GPRS_Events==4
www.actix.com
183
www.actix.com
184
Diagnosis
default(RMAC_Sign_Var, 0) >=
G_RMAC_Sign_Var_Min +
default(RMAC_8PSK_CV_BEP, 7) <=
G_RMAC_CV_BEP_Max +
default(RMAC_GMSK_CV_BEP, 7) <=
G_RMAC_CV_BEP_Max
>0
Interference
default(RMAC_RxQual, 0) >=
G_RxQualSub_Max +
default(RMAC_8PSK_MEAN_BEP, 31) <=
G_RMAC_MEAN_BEP_Max +
default(RMAC_GMSK_Mean_BEP, 31) <=
G_RMAC_MEAN_BEP_Max +
default(ServRxQualSub, 0) >=
G_RxQualSub_Max
>0
default(RMAC_Power_Reduction, 0) >=
G_RMAC_Power_Reduction_Max
default(GPRS_DL_Timeslot_Numbers_Num, 3)
<= G_RMAC_DL_TS_Min +
default(RMAC_DL_NumTimeslots_Used_Actual,
3) <= G_RMAC_DL_TS_Min
>0
Co/Adjacent Channel
allocations between neighbors
default(RMAC_TimingAdvanceIndex, 0) >=
G_RMAC_TAI_Max
The 'default' function means 'use the first value in brackets if possible, otherwise
use the second value'.
www.actix.com
185
Average_PER_Threshold
This threshold is used to indicate a pass threshold for the Average PER (%) for
cluster acceptance. Default is 3.
18.1.1.2
Average_SINR_PN0_Threshold
This threshold is used to indicate a pass threshold for the Average SINR for
PN_Nth_Best_0 (dB) for cluster acceptance. Default is 3.
18.1.1.3
CDMA_EVDO_MobileRxPowerThreshold
This threshold is used in conjunction with EcIo and Mobile Tx Power Thresholds to
determine the diagnosis for the dropped call, failed call and voice call with poor
quality. Recommended value is -80 dBm. Values should vary between -75 and 90 dBm.
18.1.1.4
CDMA_EVDO_PilotPollution_Count_Threshold
CDMA_EVDO_PilotPollutionThreshold
Max_TxPower_Threshold
This threshold is used to indicate a pass threshold for the maximum Transmit
Power (in dBm) for cluster acceptance.
18.1.1.7
Min_TxPower_Threshold
This threshold is used to indicate a pass threshold for the minimum Transmit
Power (in dBm) for cluster acceptance.
www.actix.com
186
EVT_EVDOLowThroughput
EVT_EVDOServerKey
1 (default) = Turns on the EVDO Server Key event diagram for EVDO
troubleshooter; 0 = this analysis is turned off to gain on file load speeds.
18.1.2.3
EVT_VerituneEVDOPilotPollution
1 (default) = Turns on the analysis for EVDO pilot pollution; 0 = this analysis is
turned off to gain on file load speeds.
18.1.2.4
SchedulerAnalysis
AccessAttemptDuration_Threshold
This threshold is used to indicate a pass threshold for the Access Attempt Setup
time for cluster acceptance. Default is 3.
18.1.3.2
ConnectionAttemptDuration_Threshold
This threshold is used to indicate a pass threshold for the Connection Attempt
Setup time for cluster acceptance. Default is 3.
18.1.3.3
ConnectionReleaseDuration_Threshold
This threshold is used to indicate a pass threshold for the Connection Release
time for cluster acceptance. Default is 3.
18.1.3.4
PPPSetupTime_Threshold
This threshold is used to indicate a pass threshold for the PPP Session Setup time
for cluster acceptance. Default is 3.
CDMA_EVDO_DRCRate_0
This is the data rate requested in bps for DRC Index 0. Default is 0.
18.1.4.2
CDMA_EVDO_DRCRate_1
This is the data rate requested in bps for DRC Index 1. Default is 38400.
18.1.4.3
CDMA_EVDO_DRCRate_10
This is the data rate requested in bps for DRC Index 10. Default is 1228800.
www.actix.com
18.1.4.4
187
CDMA_EVDO_DRCRate_11
This is the data rate requested in bps for DRC Index 11. Default is 1843200.
18.1.4.5
CDMA_EVDO_DRCRate_12
This is the data rate requested in bps for DRC Index 4. Default is 2457600.
18.1.4.6
CDMA_EVDO_DRCRate_13
This is the data rate requested in bps for DRC Index 13. This value is reserved.
Default is 0.
18.1.4.7
CDMA_EVDO_DRCRate_14
This is the data rate requested in bps for DRC Index 14. This value is reserved.
Default is 0.
18.1.4.8
CDMA_EVDO_DRCRate_15
This is the data rate requested in bps for DRC Index 15. The DRC Channel is Off
for Index 15. Default is 0.
18.1.4.9
CDMA_EVDO_DRCRate_2
This is the data rate requested in bps for DRC Index 2. Default is 76800.
18.1.4.10 CDMA_EVDO_DRCRate_3
This is the data rate requested in bps for DRC Index 3. Default is 153600.
18.1.4.11 CDMA_EVDO_DRCRate_4
This is the data rate requested in bps for DRC Index 4. Default is 307200.
18.1.4.12 CDMA_EVDO_DRCRate_5
This is the data rate requested in bps for DRC Index 5. Default is 307200.
18.1.4.13 CDMA_EVDO_DRCRate_6
This is the data rate requested in bps for DRC Index 6. Default is 614400.
18.1.4.14 CDMA_EVDO_DRCRate_7
This is the data rate requested in bps for DRC Index 7. Default is 614400.
18.1.4.15 CDMA_EVDO_DRCRate_8
This is the data rate requested in bps for DRC Index 8. Default is 921600.
18.1.4.16 CDMA_EVDO_DRCRate_9
This is the data rate requested in bps for DRC Index 9. Default is 1228800.
18.1.4.17 CDMA_EVDO_EcIoInterferenceThreshold
Recommended value is -15 dBm. The maximum should not exceed 0 and the
minimum should not be below -25 dBm.
www.actix.com
188
AccessAttemptFailRate_Threshold
This threshold is used to indicate a pass threshold for the EVDO Access Attempt
Fail rate for cluster acceptance. The default is 5%.
18.1.5.2
AccessAttemptSuccessRate_Threshold
This threshold is used to indicate a pass threshold for the EVDO Access Attempt
success rate for cluster acceptance. The default is 95%.
18.1.5.3
Average_Rx_RlpRetransmissionRate_Threshold
This threshold is used to indicate a pass threshold for the Average Receive RLP
Retransmission rate for cluster acceptance. The default is .3.
18.1.5.4
Average_RxRlpThputInst_Threshold
This threshold is used to indicate a pass threshold for the Average Receive RLP
Throughput Inst. (kbps) for cluster acceptance. The default is 100 kbps.
18.1.5.5
Average_RxTCHThroughput_Threshold
This threshold is used to indicate a pass threshold for the Average Receive TCH
Throughput (kbps) for cluster acceptance. The default is 100 kbps.
18.1.5.6
Average_Tx_RlpRetransmissionRate_Threshold
This threshold is used to indicate a pass threshold for the Average Transmit RLP
Retransmission rate for cluster acceptance. The default is .3.
18.1.5.7
Average_TxRlpThputInst_Threshold
This threshold is used to indicate a pass threshold for the Average Transmit RLP
Throughput Inst. (kbps) for cluster acceptance. The default is 25 kbps.
18.1.5.8
ConnectionAttemptFailRate_Threshold
This threshold is used to indicate a pass threshold for the EVDO Connection
Attempt Fail rate for cluster acceptance. Default is 5%.
18.1.5.9
ConnectionAttemptSuccessRate_Threshold
This threshold is used to indicate a pass threshold for the EVDO Connection
Attempt success rate for cluster acceptance. The default is 95%.
18.1.5.10 ConnectionReleaseSuccessRate_Threshold
This threshold is used to indicate a pass threshold for the EVDO Connection
Release Success rate for cluster acceptance. The default is 95%.
18.1.5.11 PPPConnectionSuccessRate_Threshold
This threshold is used to indicate a pass threshold for the PPP Connection Success
Rate for cluster acceptance. The default is 95%.
www.actix.com
189
18.1.6 RevA
18.1.6.1
RL_Throughput_Threshold
This threshold (in kbps) is used to set the Low Throughput event for RL for both
HICAP and LOLAT modes over all packet sizes. All RL Throughput values less than
or equal to RL_Throughput_Threshold value for all continuously
RL_Throughput_TimeLimit_Threshold seconds will be flagged as a Low RL
Throughput issue. The default is 50 kbps.
18.1.6.2
RL_Throughput_TimeLimit_Threshold
This threshold is used to set the time limit in seconds to be used in computing the
Low Throughput event for RL Packets. All RL Throughput values less than or equal
to RL_Throughput_Threshold value for continuously
RL_Throughput_TimeLimit_Threshold seconds will be flagged as Low RL
Throughput issue. Default is 15 seconds.
18.1.6.3
SU_Rx_Throughput_Threshold
This threshold (in kbps) is used to set the Low Throughput event for TC averaged
over time including the time the AN did not serve the AT. All Single User
Throughput values less than or equal to SU_Rx_Throughput_Threshold value for
continuously SU_Rx_Throughput_TimeLimit_Threshold seconds will be flagged as
a Low SU Throughput issue. Default is 500 kbps.
18.1.6.4
T2P_Avg_Threshold
This threshold (in dB) indicates the optimum value above which the transmission
data rate is satisfactory. The default value is 10 dB.
# Low Throughput
# Setup Failures
# Scheduling Issues
# Excessive Setup
www.actix.com
190
www.actix.com
191
Diagnosis
Poor Quality
Low Signal
Pilot Pollution
Other
www.actix.com
192
www.actix.com
193
Diagnosis
Network Overload
Low Signal
Poor Quality
Pilot Pollution
Other
www.actix.com
194
www.actix.com
195
Diagnosis
Network Overload
Low Signal
Poor Quality
Pilot Pollution
Other
www.actix.com
196
19.1.1 Spotlight
19.1.1.1
SL_Overspill_Dist_Threshold
Dragged_Dominance_Hysteresis
This threshold is the dBm hysteresis applied to the Best Neighbor Level to trigger
a loss of dominance of the server. Once a loss of dominance is triggered, and not
re-established before the Dragged_HO_Window timer expires, then any
subsequent Handover Failure or Dropped Call will trigger the Dragged Handover
Failure or Dragged Drop. Dominance loss = ServRxLevSub < (Best_Nbr Hysteresis). The default value is 5 dBm.
19.1.2.2
Dragged_HO_Window
This threshold is the number of milliseconds that the MS must lose dominance
for, before a Dragged Handover Failure or Dragged Dropped Call is triggered. The
default value is 10000 ms.
19.1.2.3
Ping_Pong_HO_Window
This threshold is the number of milliseconds during which a handover back to the
previous cell will trigger the Ping Pong Handover Event. The default value is 6000
ms.
G_Distance_Max
This threshold is used to determine the maximum distance allowed per cell.
Typically, values in excess of 8000 meters are usually regarded as distant serving
cells.
www.actix.com
19.1.3.2
197
G_Handover_Min
G_MsTxPowStepOrdered_Min
G_Prolong_Interf_timer
This threshold is used in conjunction with the signal strength and signal quality to
determine prolong interference that is, good signal strength but bad quality in
this time window will cause a prolong interference event.
19.1.3.5
G_RxLevSub_Min
This threshold is used to determine the minimum acceptable value for signal
strength. Any signal below this threshold is categorized as poor coverage.
Recommended value: -95 dBm.
19.1.3.6
G_RxQualSub_Max
G_TimingAdvance_Max
G_Interference_Radius
This value is used to define a radius of analysis about a selected sector for coadjacent interference and neighbors visualizations in the Cell Plan Viewer. You
can set the units to be used (either miles or kilometers) in Preferences, General
Settings, Distance Units.
19.1.4.2
G_ScanSortSigLevel_Min
This value is used in relation to the scanner signal level; for example, in the
Channel Overlap analysis in the GSM Cell Plan Viewer.
G_Timeout_ChannelRequest
This value is used to determine the time (in ms) the system will wait for RR
Channel Request messages to be answered before registering a Call Setup
Failure. Default is 3000 ms.
www.actix.com
198
SL_GSM_Ant_Gain_Threshold
This threshold is the default Antenna gain, used in the calculation of pathloss. The
default value is 18.4 dB.
19.1.6.2
SL_GSM_BTS_Sens_Threshold
This threshold is the default BTS receive sensitivity, used in the calculation of UL
pathloss. The default value is -120 dBm.
19.1.6.3
SL_GSM_EIRP_Threshold
This threshold is the default EIRP, used in the calculation of DL pathloss. The
default value is 55.
19.1.6.4
SL_GSM_High_TX_Power_Threshold
This threshold is used for determining a High TX condition. The default value is
30.
19.1.6.5
SL_GSM_RapidPathloss_RxLev_Threshold
SL_GSM_RapidPathloss_RxQual_Threshold
SL_GSM_RapidPathloss_Time_window_Threshold
This threshold is used to define the window over which Rapid Pathloss is
performed. The default value is 3000 ms.
19.1.6.8
SL_GSM_Site_Issues_Dist_Threshold
This threshold is used in the outside beamwidth analysis, and only data within
this distance from the site is considered for the analysis. The default value is
5000m.
G_Analysis_Time_After
This value is used to determine the time (in ms) allocated to investigate the radio
conditions AFTER the detected event occurrence. Typically, values of 5000 to
10000 ms are used. Values less than 5000 ms will tend to be more accurate, but
less attributes will be detected, while values in excess of 10000 ms tend to have
a high detection of attributes, but with relatively low accuracy since the time
under analysis is large.
www.actix.com
19.1.7.2
199
G_Analysis_Time_Before
This value is used to determine the time (in ms) allocated to investigate the radio
conditions PRIOR to the detected event occurrence. Typically, values of 5000 to
10000 ms are used. Values less than 5000 ms will tend to be more accurate, but
fewer attributes will be detected, while values in excess of 10000 ms tend to
detect a large number of attributes, but with relatively low accuracy since the
time under analysis is large.
19.1.7.3
G_CallDropRate
This threshold is used to determine the criterion for KPI acceptance in the
repository views. The Call Drop Rate should not exceed 2% of all successful calls
in the busy hour. If the resulting KPI is equal to or less than this value, it will be
flagged as accepted and will show up as a green tick mark in the KPI table. If it is
higher than this value, it will be flagged as failed and will show up as a red cross
in the KPI table.
19.1.7.4
G_CallSetupSuccessRate
This threshold is used to determine the criterion for KPI acceptance in the
repository views. The Call Setup Success Rate should be in excess of 98% for
most GSM networks in the busy hour. If the resulting KPI is equal to or in excess
of this value, it will be flagged as accepted and will show up as a green tick mark
in the KPI table. If it is less than this value, it will be flagged as failed and will
show up as a red cross in the KPI table.
19.1.7.5
G_HandoverSuccessRate
This threshold is used to determine the criterion for KPI acceptance in the
repository views. The Handover Success Rate should be in excess of 98% for
most GSM networks in the busy hour. If the resulting KPI is equal or in excess to
this value, it will be flagged as accepted and will show up as a green tick mark in
the KPI table. If it is less than this value, it will be flagged as failed and will show
up as a red cross in the KPI table.
19.1.7.6
G_LocationUpdateSuccessRate
This threshold is used to determine the criterion for KPI acceptance in the
repository views. The Location Update Success Rate should be in excess of 98%
for most GSM networks in the busy hour. If the resulting KPI is equal or in excess
to this value, it will be flagged as accepted and will show up as a green tick mark
in the KPI table. If it is less than this value, it will be flagged as failed and will
show up as a red cross in the KPI table.
19.1.7.7
G_OverAllSuccessRate
This threshold is used to determine the criterion for KPI acceptance in the
repository views. The Overall Success Rate should be in excess of 98% for most
GSM networks in the busy hour. If the resulting KPI is equal or in excess to this
value, it will be flagged as accepted and will show up as a green tick mark in the
KPI table. If it is less than this value, it will be flagged as failed and will show up
as a red cross in the KPI table.
www.actix.com
200
www.actix.com
201
www.actix.com
202
Diagnosis
RR Failed
Immediate Reject
User Release
Poor Coverage
Interference
Other
www.actix.com
203
www.actix.com
204
Diagnosis
RR Failed
Immediate Reject
LU Reject
Poor Coverage
Interference
System Released
Other
www.actix.com
205
www.actix.com
206
Diagnosis
System Released
Missing Neighbor
Handover Problem
Poor Coverage
Interference
Other
Handover Impossible
(TA out of Range)
www.actix.com
207
Call Attempts
Dropped Calls
Call Drop
For failure scenarios where a transition to Idle mode occurs (such as the dropped
call under investigation in this example), we strongly recommend that, in the
Drilldown options, you select a long 'After Window' (in the tens of seconds).
Please refer to the description of HSPA KPIs on p207 for details of HSPA
diagnostics.
www.actix.com
208
The first example of an HSPA Dropped Call is a case of HSPA to R99 transition via
Idle mode. The UE goes out of HSPA coverage and is forced into Idle mode by the
network, which then re-establishes the radio connection on the new site in R99.
The diagnostic panel provides essential information, such as the last SC under
HSPA coverage (104), and the target SC in R99 (45). This can also be clearly
seen on the map. One interesting binned data attribute to display on the map is
the UE state, which indicates what kind of resources (if any) are allocated to the
UE (HSPA, DCH_R99, FACH). By plotting this binned data on the map, we can
confirm the diagnosis, and can visualize the transitions from HSPA to DCH_R99.
20.2.1 Drilldown
You can investigate all the KPIs with diagnostic information with the Drilldown
mechanism.
The dropped call under investigation in this example, includes a transition to Idle
mode, so in the Drilldown options, a long 'After Window' of 30 seconds was
selected.
www.actix.com
209
The main aspects to point out from the screen layout are:
The Active Set analysis: it can be clearly seen that at the moment of the
call drop, SC_45 is much stronger than SC_104 (the current HSPA server)
In the Protocol Stack Browser, it is worth noting that the user consistently
reports that SC_45 has a better signal than SC_104 (several Measurement
Report messages), until the network decides to release the radio
connection (RRC Connection Release message). Further down in the
signaling, the user is paged by the network, and the radio connection is
re-established on SC_45, but in R99.
The radio charts report the typical HSPA L1 measurements and give an
idea of the quality of the HSPA connection before the call drops. Due to
the UE dropping to Idle for several seconds, the HSPA radio performance
is less essential for the analysis as the user experience is compromised
anyway. However, the HSPA connection provides a good performance up
to a few seconds before the drops, as the throughput remains at
reasonable levels.
www.actix.com
210
Three different results from the root cause analysis are shown.
Skip the cases related to HSPA to R99 transition via Idle mode, as they coincide
with the dropped call events seen above. Whenever an HSPA Call Drop event is
detected, a Low Throughput event is also pegged, because transitions to Idle
involve a service interruption noticeable by the user.
The first case to analyze is the event caused by a Direct HS Cell Change - that is,
when the network points the user at another HS server cell. These cases should
introduce relatively short interruptions, so the settings of the thresholds that
control Low Throughput detection (see above) play a fundamental role here. It is
important to highlight that the diagnostic information provides information on the
type of Cell Change in terms of site and frequency. Cell Changes that involve a
change of site cause longer interruptions therefore these are the most common in
the diagnostic panel, like in this demo. If a change of frequency occurs, the
interruption is normally even longer. However, the technology seems not mature
yet to allow Direct Cell Changes with change of frequency (but we have seen
change of frequency cases with transitions to Idle mode).
www.actix.com
211
Other useful information to mention is signal strength of source and target cell
and all the HSPA physical layer measurement provided before and after the
event. For a well-designed network, the performance should improve following a
Cell Change. That is not always the case, as we will see shortly.
Now look at the second case of
Direct Cell Change shown on the
right.
It highlights that numerous Cell
Changes occurred in a very short
time, and this is a clear example of
network not optimized.
In the Drill-down section, we will be
able to see that the cell changes
occur between the same two cells,
casing a so-called ping-pong
scenario.
The performance slightly increases
right after the cell change, but as we
can see, the quality of the signal
(EcIo) in the target cell is already
degrading.
www.actix.com
212
20.3.1 Drilldown
All the KPIs with diagnostic information can be investigated further via the
Drilldown mechanism.
Just like for the HSDPA Call Drop KPI, remember to select a long after window
in the Drilldown options for scenarios that include Idle transitions.
www.actix.com
213
For the HS Direct Cell Change case, an After Window of 5 seconds is enough.
The Event Navigator below confirms the occurrence of several HS Cell changes
within a short time. Also, the Protocol Stack Browser window shows the signaling
associated with these mobility procedures. Finally, the radio graphs give an
overview of the level of degradation suffered from this poor design issue.
www.actix.com
214
For the Lack of Data to Transmit case, maintain the Drill-down settings used
above.
Here we can see that despite good radio conditions (check the numeric values of
CQI and its visual representation on the map) throughput is null before the event
detection.
Radio conditions get worse afterwards, and in fact, it is possible to see quite
easily from the Event Navigator form that a HS Cell Change occurs. But as
mentioned above this is another issue and completely unrelated to the lack of
data to transmit.
Network releasing the radio connection for causes other than user
inactivity or normal PDP Context deactivation
www.actix.com
215
UE drops to idle
The UE drops to idle when radio link conditions becomes poor. Typical
scenarios are:
- No coverage
- Excessive interference
- The UE is moving in an area where HSPA is not supported (and the
network does not handle direct HSDPA to R99 transitions).
Uu_HSDPALowRawThrou_Thresh
The value (in kbps) under which the instantaneous Raw HSDPA throughput is
considered LOW - It is used in conjunction with the threshold
Uu_HSDPALowThrouMaxTimeWin_Thres, to peg Low Raw MAC-HS Throughput
events in Drive Test.
20.4.2.2
Uu_HSDPALowNetThrou_Thresh
The value (in kbps) under which the instantaneous Net HSDPA throughput is
considered LOW - It is used in conjunction with the threshold
Uu_HSDPALowThrouMaxTimeWin_Thres, to peg Low Net MAC-HS Throughput
events in Drive Test.
20.4.2.3
Uu_HSDPALowThrouMaxTimeWin_Thres
The time (in msec.) that the HSDPA throughput is allowed to stay under a certain
value (Uu_HSDPALowRawThrou_Thresh or Uu_HSDPALowNetThrou_Thresh). If
the throughput stays under those raw or net throughput thresholds for a period
longer than Uu_HSDPALowThrouMaxTimeWin_Thres a Low Raw(Net) MAC-HS
Throughput event is pegged for Drive Test
www.actix.com
216
KPI/attribute
Related threshold
Uu_LowRawHSDPAThroughput
Uu_HSDPALowRawThrou_Thresh
Uu_HSDPALowThrouMaxTimeWin_Thres
Uu_LowNetHSDPAThroughput
Uu_HSDPALowNetThrou_Thresh
Uu_HSDPALowThrouMaxTimeWin_Thres
Uu_HSCellNotBestPilot
Uu_WinTimeHSnotBest
Uu_HSDPALowCQI_Thresh
Uu_HSDPAAvRegularSched_Thresh
Uu_HSDPAAvLowSched_Thresh
Uu_HSDPANet_To_L1_Throu_Thresh
Uu_HSDPAL1_To_Raw_Throu_Thresh
SL_UMTS_DT_Spotlight_CriticalIssues_HSDPAPea
kTput
HSDPA_NW_Acceptance_HSDPA_Failure_Rate
HSDPA_NW_Acceptance_Overall_PS_Failure_Rate
HSDPA_NW_Acceptance_HSDPA_Setup_Time
HSDPA_NW_Acceptance_HSDPA_Drop_Rate
HSDPA_NW_Acceptance_PS_Drop_Rate
Average EcIo
HSDPA_NW_Acceptance_EcIo_Threshold
HSDPA_NW_Acceptance_95_Percentile_MACHS_T
hroughput_Threshold
Average RSCP
HSDPA_NW_Acceptance_RSCP_Threshold
HSDPA_NW_Acceptance_95_Percentile_TCP_Thro
ughput_Threshold
HSDPA_NW_Acceptance_95_Percentile_CQI_Thre
shold
HSDPA_NW_Acceptance_95_Percentile_EcIo_Thr
eshold
HSDPA_NW_Acceptance_95_Percentile_RSCP_Th
reshold
Raw HS Throughput
Mobility scenarios
Whenever a mobility scenario occurs, expect throughput degradation. The
level of degradation is proportional to the duration of the mobility
procedure, during which the UE receives a limited amount of data - or no
data at all, as with Idle transitions.
www.actix.com
217
The sub-cases below are self-explanatory and are all mutually exclusive by
definition:
20.4.2.5
Net HS Throughput
www.actix.com
218
< Uu_HSDPANet_To_L1_Throu_Thresh
For the definition of the different types of HSDPA throughput, please refer
to the section on HSDPA Throughput KPIs.
www.actix.com
219
MAC-HS throughput KPIs (e.g. Mean, Mode, 95% percentile) are derived from the
MAC-HS instantaneous throughputs. Both raw and net instantaneous throughputs
are calculated every 200 msecs:
MAC - HS instantaneous throughput = (bytes received by the UE over
200ms)/200ms
The difference between Raw and Net MAC-HS throughput is that Raw throughput
includes ALL the packets scheduled for the UE, while Net throughput does not
include packets unsuccessfully decoded or re-transmitted:
Raw throughput -> All packets received by UE
Net throughput -> Only successfully decoded (not re-transmitted) packets
The following figure further clarifies the approach used for the calculation of Raw
and Net MAC-HS throughput:
20.5.1 Notes
In ideal scenarios, Raw and Net MAC-HS throughput are equal, but in
reality the Net throughput is always lower than the Raw throughput.
For the purpose of throughput calculation, the size of the entire MAC-HS
PDU is used; this includes MAC-HS header and padding. For this reason,
MAC-HS net throughput and RLC throughput do not coincide:
The Net DL TCP throughput is simply the downlink TCP throughput that
excludes TCP re-transmissions.
www.actix.com
220
SL_Overspill_Dist_Threshold
IUB_THROUGHPUT_PERIOD_THRES
This threshold is used to set the sampling period (in msec.) for the calculation of
MACd throughput over the Iub. Note that MACd throughput includes the header of
RLC and layer above (PDCP, IP, etc.). The default value is 1000 ms.
20.6.2.2
Uu_HSDPALowRawThrou_Thresh
This threshold is used to set the value (in kbps) under which the instantaneous
Raw HSDPA throughput is considered LOW - It is used in conjunction with the
threshold Uu_HSDPALowThrouMaxTimeWin_Thres, to peg Low Raw MAC-HS
Throughput events in Drive Test. For a definition of Raw HSDPA Throughput see
Uu_HSDPA_PayloadRate_L1. The default value is 400 kbps.
20.6.2.3
Uu_HSDPALowNetThrou_Thresh
This threshold is used to set the value (in kbps) under which the instantaneous
Net HSDPA throughput is considered LOW - It is used in conjunction with the
threshold Uu_HSDPALowThrouMaxTimeWin_Thres, to peg Low Net MAC-HS
Throughput events in Drive Test. For a definition of Net HSDPA Throughput, see
Uu_HSDPA_Throughput_MAC. The default value is 300 kbps.
20.6.2.4
Uu_HSDPALowThrouMaxTimeWin_Thres
This threshold is used to set the period of time (in msec.) that the HSDPA
throughput is allowed to stay under a certain value
(Uu_HSDPALowRawThrou_Thresh or Uu_HSDPALowNetThrou_Thresh). If the
throughput stays under those raw or net throughput thresolds for a period longer
than Uu_HSDPALowThrouMaxTimeWin_Thres a Low Raw(Net) MAC-HS
Throughput event is pegged for Drive Test. The default value is 3000 ms.
20.6.2.5
Uu_ThresGapBeforeThrComparison
This parameter indicates the gap between the end of the Cell Change procedure
and the start of the time interval used to calculate the TCP throughput for
comparison with the throughput during the cell change. The time interval is as
lons as the duration of the Cell Change procedure. The default value is 1000 ms.
www.actix.com
20.6.2.6
221
Uu_WinTimeHSnotBest
This threshold is used to set the period of time (in msec.) that the EcIo of the HS
Serving Cell is allowed to be lower than the best pilot EcIo in the Active Set. If
the quality of the HS Serving Cell is below the best pilot in the AS for a period
longer than this threshold a Uu_HSCellNotBestPilot event is pegged for Drive
Test. The default value is 1000 ms.
HSDPA_NW_Acceptance_HSDPA_Failure_Rate
This threshold is used to indicate a pass threshold for the HSPA call setup failure
rate.
20.6.3.2
HSDPA_NW_Acceptance_Overall_PS_Failure_Rate
This threshold is used to indicate a pass threshold for the overall PS call setup
failure rate (HSPA and R99).
20.6.3.3
HSDPA_NW_Acceptance_HSDPA_Setup_Time
This threshold is used to indicate an average HSPA call setup acceptance time.
20.6.3.4
HSDPA_NW_Acceptance_HSDPA_Drop_Rate
This threshold is used to indicate a pass threshold for the HSPA call drop rate.
20.6.3.5
HSDPA_NW_Acceptance_PS_Drop_Rate
This threshold is used to indicate a pass threshold for the PS R99 call drop rate.
20.6.3.6
HSDPA_NW_Acceptance_EcIo_Threshold
HSDPA_NW_Acceptance_RSCP_Threshold
HSDPA_NW_Acceptance_95_Percentile_MACHS_Throughput_
Threshold
This threshold is used to indicate the lowest required Raw MAC HS Throughput
value at the 95 percentile for HSPA Network acceptance (unit is kbit/sec).
20.6.3.9
HSDPA_NW_Acceptance_95_Percentile_TCP_Throughput_Thr
eshold
This threshold is used to indicate the lowest required TCP Throughput value at the
95 percentile for HSPA Network acceptance (unit is kbit/sec).
www.actix.com
222
20.6.3.10 HSDPA_NW_Acceptance_95_Percentile_CQI_Threshold
This threshold is used to indicate the lowest required CQI value at the 95
percentile for HSPA Network acceptance.
20.6.3.11 HSDPA_NW_Acceptance_95_Percentile_EcIo_Threshold
This threshold is used to indicate the lowest required EcIo value at the 95
percentile for HSPA Network acceptance.
20.6.3.12 HSDPA_NW_Acceptance_95_Percentile_RSCP_Threshold
This threshold is used to indicate the lowest required RSCP value at the 95
percentile for HSPA Network acceptance.
Uu_HSDPALowCQI_Thresh
This threshold is used to set the value under which the average CQI is considered
low (average calculated on the 5 secs. before the occurrence of a failure event).
NOTE: the threshold is expressed as the ratio (0..1) of the max achievable CQI.
The max achievable CQI is a function of the UE category and the modulation used
(QPSK or 16 QAM). See more information about this threshold under "HSPA Call
Drop". The default value is 0.4.
20.6.4.2
Uu_HSDPAAvRegularSched_Thresh
This threshold is used to set the value under which the average HS Scheduling is
a possible sign of regular scheduling in presence of other HSPA users (average
calculated on the 5 secs. before the occurrence of a failure event). NOTE: the
threshold is expressed as a percentage value (0..100). See more information
about this threshold in the help under "HSPA Low Raw Throughput". The default
value is 70%.
20.6.4.3
Uu_HSDPANet_To_L1_Throu_Thresh
This threshold is used to set the value under which the ratio between Net HS
Throughput average and L1 HS Throughput average is considered low enough to
assign the cause of Low Net HS Throughput not only to lack of data sent by the
network, but for example due to high retransmission levels. The average of the
Throughput values is calculated on the 5 secs. before the occurrence of the Low
Net Throughput event). NOTE: the threshold is expressed as the ratio (0..1). See
also Uu_HSDPALowNetThrou_Thresh and Uu_HSDPALowThrouMaxTimeWin_Thres
for the exact definition of the Low Net HS Throughput event, and
Uu_HSDPA_Throughput_L1 and Uu_HSDPA_Throughput_MAC for a definition of
L1 and Net HS throughput. The default value is 0.7.
20.6.4.4
Uu_HSDPAL1_To_Raw_Throu_Thresh
This threshold is used to set the value under which the ratio between L1 HS
Throughput average and Raw HS Throughput average is considered low enough
to assign the cause of Low Net HS Throughput not only to lack of data sent by the
network, but for example due to high retransmission levels. The average of the
Throughput values is calculated on the 5 secs. before the occurrence of the Low
Net Throughput event). NOTE: the threshold is expressed as the ratio (0..1). See
also Uu_HSDPALowNetThrou_Thresh and Uu_HSDPALowThrouMaxTimeWin_Thres
www.actix.com
223
for the exact definition of the Low Net HS Throughput event, and
Uu_HSDPA_Throughput_L1 and Uu_HSDPA_PayloadRate_L1 for a definition of L1
and Raw HS throughput. The default value is 0.7.
20.6.4.5
SL_UMTS_DT_Spotlight_CriticalIssues_HSDPAPeakTput
This threshold is used to filter out HSDPA Raw Tput peak performance issues from
the HSPA dashboard that are equal or less this value. The default value is 1500
(kbps).
www.actix.com
224
LTE_Scan_PoorRSRP_Threshold
This threshold is used to indicate poor RSRP values from scanner data.
Recommended value is -95 dBm and the minimum should not be lower than -105
dBm.
21.1.1.2
LTE_Scan_PoorRSRQ_Threshold
This threshold is used to indicate poor RSRQ values from scanner data.
Recommended value is -13 dB and the value should range between -10 and -18
dB.
21.1.2 Spotlight
21.1.2.1
SL_LTE_DT_Spotlight_ImportantIssues_Threshold
This threshold is used to filter out Important Issues from the LTE dashboard that
occur with a frequency greater than this value. Recommended value is 0.
SL_Overspill_Dist_Threshold
www.actix.com
225
22.1.1 Spotlight
22.1.1.1
SL_Overspill_Dist_Threshold
Uu_Scan_PilotPollution_Count_Threshold
Uu_Scan_PilotPollution_RSCP_Threshold
The RSCP threshold used by the Poor Interference with Strong Signal Strength
pilot pollution model (a Veritune feature). The default value is -100 dBm, and the
value should be between -90 and -110 dBm.
22.1.2.3
Uu_Scan_PilotPollutionThreshold
Uu_Scan_Poor_EcNoThreshold
This is used to indicate poor EcIo values from scanner data. Recommended value
is -15 dB and should lie between -18 and -10 dB.
22.1.2.5
Uu_Scan_Poor_RSCP_Threshold
This is used to indicate poor RSCP values from scanner data. Recommended value
is -95 dBm and should not be lower than -105 dBm.
www.actix.com
22.1.2.6
226
Uu_Scan_TooManyServers_Count_Threshold
Uu_Scan_TooManyServers_RSCP_Threshold
Uu_Scan_TooManyServersThreshold
In calculating "Too Many Servers", when 4 or more pilots (including the best
server) are within the threshold value in dB of the best server, it creates a "too
many server" event (based on scanner info). Recommended value is 5 dB and
the minimum and the maximum should be around 1 and 10 dB.
SL_Ant_Gain_Threshold
This threshold is the default Antenna gain, used in the calculation of pathloss. The
default value is 18.4 dB.
22.1.3.2
SL_BLER_Threshold
This threshold is used for determining a UMTS lost DL channel condition. The
default value is 10 dB.
22.1.3.3
SL_BTS_Sens_Threshold
This threshold is the default BTS receive Sensitivity, used in the calculation of UL
pathloss. The default value is -120 dBm.
22.1.3.4
SL_Detectedset_EcIo_Threshold
This threshold is used for determining if a detected set member strong enough to
be consider as a neighbor. The default value is -15 dB.
22.1.3.5
SL_EIRP_Threshold
This threshold is the default EIRP, used in the calculation of DL pathloss. The
default value is 50.
22.1.3.6
SL_MaxTimeBetweenRRC_REQandCallStart
This threshold is used for determining UMTS CS calls with excessive setup time.
Recommended value is 6000 ms.
22.1.3.7
SL_RapidPathloss_EcIo_Threshold
22.1.3.8
227
SL_RapidPathloss_RSCP_Threshold
SL_RapidPathloss_Time_window_Threshold
This threshold is used to define the window over which Rapid Pathloss is
performed. The default value is 3000 ms.
22.1.3.10 SL_Site_Issues_Dist_Threshold
This threshold is used in the outside beamwidth analysis, and only data within
this distance from the site is considered for the analysis. The default value is
5000m.
22.1.3.11 SL_UMTS_DT_Troubleshooter_CriticalIssues_Threshold
This threshold is used to filter out critical issues from the UMTS dashboard that
are equal or less then this value. Recommended value is 0.
22.1.3.12 SL_UMTS_DT_Troubleshooter_ImportantIssues_Threshold
This threshold is used to filter out Important issues from the UMTS dashboard
that are equal or less then this value. Recommended value is 0.
Uu_CoverageLimitedUE_TxPowerThreshold
Uu_EcNoInterferenceThreshold
This is used in conjunction with the RSCP Interference Threshold for the System
Interference event. If the CPICH_RSCP_in_ActiveSet is greater than
Uu_RSCP_Interference_Threshold and the CPICH_EcNo_In_ActiveSet is less than
Uu_EcNoInterferenceThreshold, then a System Interference event appears on the
map. Recommended value is -15 dB. Values should lie between -10 and -18 dBm.
22.1.4.3
Uu_HighUE_TxPower
www.actix.com
22.1.4.4
228
Uu_LowUE_TxPower
Uu_PilotPollutionThreshold
Uu_Poor_EcNoThreshold
Uu_Poor_RSCP_Threshold
Uu_RSCP_InterferenceThreshold
Uu_TooManyServersThreshold
In calculating "Too Many Servers", when 4 or more pilots (including the best
server) are within the threshold value in dB of the best server, it creates a "too
many server" event (based on scanner info). Recommended value is 5 dB and
the minimum and the maximum should be around 1 and 10 dB.
www.actix.com
229
The scanner's best cell is stronger than the best cell in the
active set, or weaker by less than
"Uu_Scan_UE_dB_Threshold" decibels.
230
www.actix.com
231
www.actix.com
232
Diagnosis
System Released
Missing Neighbor
Handover Problem
For the Raked RF Condition, the system picks the diagnosis with the
highest value, providing it is higher than the specified threshold:
Pilot Pollution
Pilot Pollution:
Too Many Servers
Interference Problem
CPICH_EcNo_in_ActiveSet <
Uu_EcNoInterferenceThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet >
Uu_RSCP_InterferenceThreshold (-80 dBm).
Coverage Limitation
Problem
CPICH_EcNo_in_ActiveSet <
Uu_Poor_EcNoThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet <
Uu_Poor_RSCP_Threshold (-95 dBm) AND
UeTransmittedPower >
Uu_CoverageLimitedUE_TxPowerThreshold (10
dBm).
Poor DL Coverage
Problem
CPICH_EcNo_in_ActiveSet <
Uu_PoorEcNoThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet <
Uu_Poor_RSCP_Threshold (-95 dBm) AND
UeTransmittedPower < Uu_LowUE_TxPower (-15
dBm).
Poor UL Coverage
Problem
CPICH_EcNo_in_ActiveSet >
Uu_Poor_EcNoThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet >
Uu_Poor_RSCP_Threshold (-95 dBm) AND
UeTransmittedPower > Uu_HighUE_TxPower (15
dBm).
Lost DL Channel
Investigate Further
(unknown diagnosis)
www.actix.com
233
www.actix.com
234
Diagnosis
System Rejected /
RRC Failure
CM Service Abort /
Reject
System Released
Missing Neighbor
Handover Problem
For the Raked RF Condition, the system picks the diagnosis with the
highest value, providing it is higher than the specified threshold:
Pilot Pollution
Pilot Pollution:
Too Many Servers
Interference Problem
CPICH_EcNo_in_ActiveSet <
Uu_EcNoInterferenceThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet >
Uu_RSCP_InterferenceThreshold (-80 dBm).
Limited Coverage
Problem
CPICH_EcNo_in_ActiveSet <
Uu_Poor_EcNoThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet <
Uu_Poor_RSCP_Threshold (-95 dBm) AND
UeTransmittedPower >
Uu_CoverageLimitedUE_TxPowerThreshold (10
dBm).
Poor DL Coverage
Problem
Poor UL Coverage
Problem
CPICH_EcNo_in_ActiveSet >
Uu_Poor_EcNoThreshold (-15 dB) AND
CPICH_RSCP_in_ActiveSet >
Uu_Poor_RSCP_Threshold (-95 dBm) AND
UeTransmittedPower > Uu_HighUE_TxPower (15
dBm).
Lost DL Channel
Investigate Further
(unknown diagnosis)
235
www.actix.com
236
www.actix.com
237
24 Index
9
95
95
95
95
95
percentile
percentile
percentile
percentile
percentile
A
Abnormal Connection Release, 191
AccessAttemptDuration_Threshold, 186
AccessAttemptFailRate_Threshold, 188
AccessAttemptSuccessRate_Threshold, 188
Add Device, 130
Analyzer Classic, 121
Another Call Started, 202, 204
Attribute Picker, 134
Average EcIo, 216
Average HSDPA Call Setup time, 216
Average RSCP, 216
Average_PER_Threshold, 185
Average_Rx_RlpRetransmissionRate_Threshold,
188
Average_RxRlpThputInst_Threshold, 188
Average_RxTCHThroughput_Threshold, 188
Average_SINR_PN0_Threshold, 185
Average_Tx_RlpRetransmissionRate_Threshold,
188
Average_TxRlpThputInst_Threshold, 188
B
Batch Sector Plot, 123
best serving cell, 42, 63
binned data, 37
Binned Data Queries, 134
binning settings, 135
C
Call Setup Failure diagnosis for GSM, 201
Call Setup Failure diagnosis for UMTS, 233
CDMA Cell Coverage, 8
CDMA Cell Coverage analysis, 42
CDMA cell site parameters, 139
CDMA events in the Event Explorer, 173
CDMA Neighbor List, 8
CDMA Neighbor List analysis, 48
CDMA Pilot Pollution analysis, 54
CDMA Spotlight Report, 144
CDMA thresholds, 170
CDMA/EVDO Pilot Pollution, 8
CDMA_AvgForwardFER, 170, 173
CDMA_CallDropRate, 172
CDMA_CallSetupSuccessRate, 173
CDMA_CallSetupTime, 173
CDMA_EcIoCombinedThreshold, 47, 170
CDMA_EcIoInterferenceThreshold, 172
CDMA_EVDO_DRCRate_0, 186
CDMA_EVDO_EcIoInterferenceThreshold, 187
CDMA_EVDO_MobileRxPowerThreshold, 185
CDMA_EVDO_PilotPollution_Count_Threshold, 185
CDMA_EVDO_PilotPollutionThreshold, 185
CDMA_EVDO_TooManyActivePNsThreshold, 172
CDMA_ImportantIssue_ExcessInterference, 170
CDMA_ImportantIssue_ExternalInterference, 170
CDMA_ImportantIssue_FwdLinkProblem, 170
CDMA_ImportantIssue_LowRX, 171
CDMA_ImportantIssue_PoorCoverage, 171
CDMA_ImportantIssue_PoorQuality, 171
CDMA_ImportantIssue_RevLinkProblem, 171
CDMA_MobileRxPowerThreshold, 47, 171
CDMA_MobileTxPowerMaxFilterThreshold, 171
CDMA_MobileTxPowerMinFilterThreshold, 171
CDMA_MobileTxPowerThreshold, 47, 171
CDMA_OverAllSuccessRate, 173
CDMA_PilotPollution_Count_Threshold, 171, 173
CDMA_PilotPollutionThreshold, 171, 173
CDMA_TooManyActivePNsThreshold, 172
cell coverage, determining, 8
cellrefs file, 9, 28
Channel mode unacceptable, 206
Choose Attributes, 133
Choose Devices, 128
Circuit Switched KPIs, 229
CM Service Abort / Reject, 202, 234
Co/Adjacent Channel allocations between
neighbors, 184
ConnectionAttemptDuration_Threshold, 186
ConnectionAttemptFailRate_Threshold, 188
ConnectionAttemptSuccessRate_Threshold, 188
ConnectionReleaseDuration_Threshold, 186
ConnectionReleaseSuccessRate_Threshold, 188
Consolidated_SINR_For_Nth_Best_Pilot[0], 37
coverage design boundary, 42
coverage footprint, 42, 63
Coverage Issue, 175
Coverage Limitation Problem, 232
Critical Issues section, 36
CSV file, 50
D
data files, 31
Data Service Analysis, 112
Data Settings link, 29
Detailed Event Diagnostics, 120
device filters, 131
Distance tab, 69
Distant Serving Cell, 184
Dragged_Dominance_Hysteresis, 196
Dragged_HO_Window, 196
DRC Rate, 62
Drill Down, 116
Drilldown page, 119
drilldown window, 117
Dropped Call diagnosis for CDMA, 174
Dropped Calls diagnosis for GSM, 205
Dropped Calls diagnosis for UMTS, 231
Dropped Connection diagnosis for EVDO, 190
www.actix.com
E
EcIo_1stBest, 37
EDGE cell site parameters, 140
EGPRS diagnoses, 183
EGPRS events in the Event Explorer, 181
EGPRS thresholds, 179
EGPRS_Duration_Period, 180
EGPRS_LLC_DL_Min, 180
EGPRS_LLC_UL_Min, 180
EGPRS_RLC_DL_Min, 180
EGPRS_RLC_UL_Min, 181
empty maps, 138
EVDO Cell Coverage, 8
EVDO Cell Coverage analysis, 42
EVDO events in the Event Explorer, 189
EVDO Neighbor List, 8
EVDO Neighbor List analysis, 48
EVDO Pilot Pollution analysis, 54
EVDO Rev A Spotlight Report, 151
EVDO Spotlight Report, 147
EVDO System Performance analysis, 8, 58
EVDO thresholds, 185
event detection, 29
Event Explorer, 109
EVT_CDMAImportantIssue, 172
EVT_CDMANeighborListIssueDetect, 172
EVT_CDMAServerKey, 172
EVT_EVDOLowThroughput, 186
EVT_EVDOServerKey, 186
EVT_VerituneEVDOPilotPollution, 186
Excessive Call diagnosis for UMTS, 235
Excessive Interference, 175
Excessive Power Reduction, 184
Export data, 50
export suggested changes to the OMC, 8
exporting a series of images, 123
External Interference, 175
F
F factor, 106
failure events, investigating, 8
Fast binning, 135
Forward Link Problem, 175
Frequency not implemented, 206
G
G_Analysis_Time_After, 198
G_Analysis_Time_Before, 199
G_CallDropRate, 199
G_CallSetupSuccessRate, 199
G_Cell_Reselect_Duration, 179
G_Cell_Reselect_Time, 179
G_Distance_Max, 196
G_Handover_Min, 197
G_HandoverSuccessRate, 199
G_Interference_Radius, 63, 197
G_LocationUpdateSuccessRate, 199
G_MsTxPowStepOrdered_Min, 197
G_OverAllSuccessRate, 199
G_Prolong_Interf_timer, 197
G_RMAC_C_Value_Min, 179
G_RMAC_CV_BEP_Max, 179
G_RMAC_DL_TS_Min, 179
G_RMAC_MEAN_BEP_Max, 179
G_RMAC_Power_Reduction_Max, 179
238
G_RMAC_Sign_Var_Min, 179
G_RMAC_TAI_Max, 180
G_RxLevSub_Min, 197
G_RxQualSub_Max, 197
G_ScanSortSigLevel_Min, 197
G_T3240_RAUTimer, 180
G_T3310_AttachTimer, 180
G_T3321_DetachTimer, 180
G_T3380_PDPActTimer, 180
G_Timeout_ChannelRequest, 197
G_TimingAdvance_Max, 197
Global Filters, 34
Global Filters, choosing, 137
GPRS_Duration_Period, 181
GPRS_LLC_DL_Min, 181
GPRS_LLC_UL_Min, 181
GPRS_RLC_DL_Min, 181
GPRS_RLC_UL_Min, 181
grade of service, 42
Grade of Service, CDMA, 47
GSM 2G Missing Neighbors, 8
GSM 2G Missing Neighbors analysis, 73
GSM Cell Coverage, 8
GSM Cell Coverage analysis, 63
GSM events in the Event Explorer, 200
GSM Spotlight Report, 155
GSM thresholds, 196
GSM visualization, 66
GSM/GPRS cell site parameters, 140
H
Handover Impossible, 206
Handover Issues, 229
Handover Problem, 206, 232, 234
Hard Handover Issues, 230
High retransmissions due to packet incorrectly
received in Downlink, 218
High retransmissions due to poor Uplink quality
conditions, 218
HS mobility, 163
HSDPA 3G Neighbor List analysis, 83
HSDPA 3G-2G Neighbor List analysis, 89
HSDPA Call Drop rate, 216
HSDPA Cell Coverage analysis, 95
HSDPA Cell Pilot Pollution analysis, 102
HSDPA Low Throughput example, 210
HSDPA Peak Tput, 216
HSDPA Setup Failure rate, 216
HSDPA Spotlight Report, 160
HSDPA thresholds, 220
HSDPA Throughput KPIs, 218
HSDPA_NW_Acceptance_95_Percentile_CQI_Thres
hold, 216, 222
HSDPA_NW_Acceptance_95_Percentile_EcIo_Thres
hold, 216, 222
HSDPA_NW_Acceptance_95_Percentile_MACHS_Th
roughput_Threshold, 216, 221
HSDPA_NW_Acceptance_95_Percentile_RSCP_Thre
shold, 216, 222
HSDPA_NW_Acceptance_95_Percentile_TCP_Throu
ghput_Threshold, 216, 221
HSDPA_NW_Acceptance_EcIo_Threshold, 216, 221
HSDPA_NW_Acceptance_HSDPA_Drop_Rate, 216,
221
HSDPA_NW_Acceptance_HSDPA_Failure_Rate,
216, 221
www.actix.com
I
images, exporting a series of, 123
Immediate Reject, 202, 204
Important Issues section, 36
inbound vs. outbound pilot pollution, identifying, 8
Interference, 184, 202, 204, 206
interference factor, 106
Interference Problem, 232, 234
Investigate Further, 232, 234
issues panel, 36
IUB_THROUGHPUT_PERIOD_THRES, 220
K
key performance indicator, 9
KPI, 9
KPIs and Reports, selecting, 132
L
Lack of data to transmit, 217
Limited Coverage Problem, 234
Load Entire File, 117
Location Update Failure diagnosis for GSM, 203
Log Files link, 121
Lost DL Channel, 232, 234
Low bandwidth allocation, 184
Low CQI values, 217
Low Raw HS Throughput, 217
Low Raw HS Throughput not detected, 217
Low RLP Rx Throughput, 193
Low RLP Tx Throughput, 193
Low Rx Signal, 175
Low scheduling rate, 217
Low Signal, 191, 193, 195
Low Throughput diagnosis for EVDO, 192
Low Tput KPI event, 216
LTE Cell Coverage analysis, 79
LTE cell site parameters, 141
LU Reject, 204
M
Max_TxPower_Threshold, 185
Maximum Intersite Distance, 51, 52, 73, 74, 83,
84, 89, 91
message level, identifying problems at the, 8
Microsoft Excel, 39
Min_TxPower_Threshold, 185
Missing Neighbor, 206, 232, 234
Mobile Rx Power, 61
Mobile Tx Power, 61
Mobility scenarios, 216
239
N
Neighbor List Issue, 175
neighbor list preferences, 30
neighbor lists, optimize, 8
Network Overload, 193, 195
network performance overview, 7
New Project, 26
New Template, 27, 126
No repository detected, 138
O
Other, 175, 191, 193, 195, 202, 204, 206
Overall PS Call Drop rate, 216
Overall PS Setup Failure rate, 216
P
Packet Switched KPIs, 229
PER, 61
Pilot Pollution, 175, 191, 193, 195, 232, 234
Ping_Pong_HO_Window, 196
PN Search, 49
Poor Coverage, 175, 202, 204, 206
Poor DL Coverage Problem, 232, 234
Poor Quality, 175, 191, 193, 195
Poor Radio Conditions, 184
Poor UL Coverage Problem, 232, 234
PPPConnectionSuccessRate_Threshold, 188
PPPSetupTime_Threshold, 186
Preferences dialog box, 28
project template, 127
Projection, 137
Protocol Stack Browser, 120
R
Radio Network Explorer, 40
Raked RF Condition, 232, 234
Rapidly Changing Radio Conditions, 184
relative grade of service, 42
Reports, 38
Repository Summary table, 121
Return to Spotlight link, 122
Reverse Link Problem, 175
RL_Throughput_Threshold, 189
RL_Throughput_TimeLimit_Threshold, 189
RLP Rx Throughput, 62
RLP Tx Throughput, 62
RR Failed, 202, 204
RRC Failure, 234
S
SchedulerAnalysis, 186
Scheduling Issues diagnosis for EVDO, 194
ServRxLevSub, 37
setting thresholds for data import, 25
settings, saving the project, 30
Show Excel Report, 39
SINR, 61
sites failing recommended design targets,
identifying, 8
SL_Ant_Gain_Threshold, 226
SL_BLER_Threshold, 226
SL_BTS_Sens_Threshold, 226
SL_Detectedset_EcIo_Threshold, 226
www.actix.com
T
T2P_Avg_Threshold, 189
thresholds, 29
thresholds, setting for data import, 25
Too Many Servers, 232, 234
top panel, 35
U
UMTS
UMTS
UMTS
UMTS
UMTS
3G Neighbor List, 8
3G Neighbor List analysis, 83
3G-2G Neighbor List, 8
3G-2G Neighbor List analysis, 89
Cell Coverage, 8
240
UMTS Cell Coverage analysis, 95
UMTS Cell Pilot Pollution analysis, 102
UMTS cell site parameters, 142
UMTS events in the Event Explorer, 229
UMTS Spotlight Report, 165
UMTS thresholds, 225
UMTS/HSPA Cell Pilot Pollution, 8
UniqueNeighborList, 172
Unload Files button, 122
Uu_ActiveSet_EcNo[0], 37
Uu_CoverageLimitedUE_TxPowerThreshold, 227
Uu_EcNoInterferenceThreshold, 227
Uu_HighUE_TxPower, 227
Uu_HSCellNotBestPilot, 216
Uu_HSDPAAvLowSched_Thresh, 216
Uu_HSDPAAvRegularSched_Thresh, 216, 222
Uu_HSDPAL1_To_Raw_Throu_Thresh, 216, 222
Uu_HSDPALowCQI_Thresh, 216, 222
Uu_HSDPALowNetThrou_Thresh, 215, 216, 220
Uu_HSDPALowRawThrou_Thresh, 215, 216, 220
Uu_HSDPALowThrouMaxTimeWin_Thres, 215, 216,
220
Uu_HSDPANet_To_L1_Throu_Thresh, 216, 222
Uu_LowNetHSDPAThroughput, 216
Uu_LowRawHSDPAThroughput, 216
Uu_LowUE_TxPower, 228
Uu_PilotPollutionThreshold, 228
Uu_Poor_EcNoThreshold, 228
Uu_Poor_RSCP_Threshold, 228
Uu_RSCP_InterferenceThreshold, 228
Uu_Scan_PilotPollution, 29
Uu_Scan_PilotPollution_Count_Threshold, 225
Uu_Scan_PilotPollution_RSCP_Threshold, 225
Uu_Scan_PilotPollutionThreshold, 225
Uu_Scan_Poor_EcNoThreshold, 225
Uu_Scan_Poor_RSCP_Threshold, 225
Uu_Scan_TooManyServers_Count_Threshold, 226
Uu_Scan_TooManyServers_RSCP_Threshold, 226
Uu_Scan_TooManyServersThreshold, 226
Uu_ThresGapBeforeThrComparison, 220
Uu_TooManyServersThreshold, 228
Uu_WinTimeHSnotBest, 216, 221
UuPilotPollution, 29
V
Visualization tab, 69
www.actix.com
241
www.actix.com
242
www.actix.com