Analyzer Training UMTS HSPA Final20090430 B A4 NJR PDF

UMTS/HSPA
Technology
Training Course
April 2009
Edition B 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 2009. All rights reserved. All trademarks are hereby acknowledged.
Contents
INTRODUCTION .............................................................................................6
SCOPE OF THE COURSE............................................................................................. 6
WHO SHOULD ATTEND ANALYZER TRAINING? .................................................................. 6
PREREQUISITES ..................................................................................................... 7
WHAT CAN YOU DO WITH ANALYZER? ..................................................................8
UMTS SECTION ............................................................................................9

GETTING STARTED ................................................................................................. 9
Open Actix Software ....................................................................................... 9
Splash Screen ................................................................................................ 9
Choosing an Engineering Process .................................................................... 10
Configuring Cellrefs....................................................................................... 11
Configuring Your Solution .............................................................................. 12
Loading Data File .......................................................................................... 13
EXPLORING THE WORKSPACE ................................................................................... 13
Examining UMTS Handset Data ...................................................................... 13
Examining technology-independent data ......................................................... 16
Examining UMTS scanner data ....................................................................... 17
Searching for Attributes................................................................................. 18
Exercise: Favorites Group .............................................................................. 19
VIEWING DATA.................................................................................................... 21
Viewing Data on Maps ................................................................................... 21
Viewing Data on Charts ................................................................................. 27
Modifying Chart Properties ............................................................................. 28
Viewing Data in Tables .................................................................................. 29
Viewing Data in the Message Browser ............................................................. 33
Viewing data in the Protocol Stack Browser ...................................................... 35
Viewing Data on Workbooks ........................................................................... 36
Viewing Data on StateForms .......................................................................... 37
Using Preconfigured StateForms ..................................................................... 38
Exercise: Drop Call Analysis (Handover Problem) .............................................. 40
Viewing Custom Forms with the StateForms Editor ........................................... 41
Modifying an Existing StateForm File ............................................................... 42
Exercise: Creating Your Own StateForms File ................................................... 44
PERFORMING PRE-CONFIGURED UMTS ANALYSES ........................................................... 48
Reporting UMTS Network Performance ............................................................ 48
Running Application Packs ............................................................................. 49
Running a Pre-Defined Report ........................................................................ 53
PERFORMING CUSTOM ANALYSIS IN ANALYZER ............................................................... 55
About Queries .............................................................................................. 55
Filter Analysis .............................................................................................. 56
Working with Pre-configured Filters ................................................................. 56
Binned Query Analysis................................................................................... 62
Histogram and Statistic Query Analysis ........................................................... 70
Crosstab Query ............................................................................................ 73
Event Query Analysis .................................................................................... 80
REPORTING NETWORK PERFORMANCE ......................................................................... 87
Creating a Custom Report .............................................................................. 87
Modifying a Custom Report ............................................................................ 90
HSPA SECTION .......................................................................................... 93
GETTING STARTED ............................................................................................... 93
Configuring Cellrefs....................................................................................... 94
Configuring Your Solution .............................................................................. 95
Loading Data File .......................................................................................... 96
EXPLORING THE WORKSPACE ................................................................................... 96
Examining HSUPA file.dt1 .............................................................................. 96
Searching for Attributes................................................................................. 97
Exercise: Favorites Group .............................................................................. 98
VIEWING DATA.................................................................................................... 99
Viewing Data on Maps ................................................................................... 99
Viewing Data on Charts ............................................................................... 106
Modifying Chart Properties ........................................................................... 108
Viewing Data in Tables ................................................................................ 108
Viewing Data in the Message Browser ........................................................... 110
Viewing Data in the Protocol Stack Browser ................................................... 112
Exercise: Call Drop Analysis ......................................................................... 113
Viewing Data on Workbooks ......................................................................... 117
Viewing Data on StateForms ........................................................................ 119
Using Preconfigured StateForms ................................................................... 119
Viewing Custom Forms with the StateForms Editor ......................................... 122
Modifying an Existing StateForm File ............................................................. 123
Exercise: Creating Your Own StateForms ....................................................... 125
PERFORMING PRE-CONFIGURED HSDPA ANALYSES ....................................................... 128
Reporting HSDPA Network Performance ......................................................... 128
Running Application Packs ........................................................................... 129
Running a Pre-Defined Report ...................................................................... 130
Modifying a Custom Report .......................................................................... 130
PERFORMING CUSTOM ANALYSIS IN ANALYZER ............................................................. 131
About Queries ............................................................................................ 131
Filter Analysis ............................................................................................ 132
Attribute Spy ............................................................................................. 135
Binned Query Analysis................................................................................. 136
Event Queries Analysis ................................................................................ 139
Crosstab Query Analysis .............................................................................. 143
Histogram.................................................................................................. 152
REPORTING NETWORK PERFORMANCE ....................................................................... 154
Creating a Custom Report ............................................................................ 154
Repository ................................................................................................. 157
APPENDIX UMTS.A: THRESHOLDS ................................................................. 165

MODIFYING UMTS THRESHOLDS ............................................................................. 165
UMTS > Event_Control ................................................................................ 165
UMTS > Scan_coverage .............................................................................. 166
UMTS > UE_Coverage ................................................................................. 166
APPENDIX UMTS.B: SCANNER-BASED NETWORK ROLLOUT ANALYSES ...................... 168

NEIGHBOR LIST ANALYSIS .................................................................................... 168
CPICH POLLUTION ANALYSIS ................................................................................ 171
HANDOFF ANALYSIS ............................................................................................ 174
SIMULATED ACTIVE SET ....................................................................................... 176
APPENDIX UMTS.C: EVENT DEFINITIONS ......................................................... 177

EVENT DATA ..................................................................................................... 177
Call Events ................................................................................................ 177
RRC Events ................................................................................................ 180
RAB Events ................................................................................................ 181
Coverage Events ........................................................................................ 181
Handoff Events ........................................................................................... 182
APPENDIX HSPA.A: THRESHOLDS .................................................................. 183

MODIFYING HSPA THRESHOLDS ............................................................................. 183
HSDPA Thresholds ...................................................................................... 183
HSDPA > HSDPA_NW_Acceptance Thresholds ................................................ 184
APPENDIX HSDPA.B: DATA SETTINGS FOR NEIGHBOR ANALYSIS ............................ 186
APPENDIX HSDPA.C: EVENTS DIAGNOSES ....................................................... 188

HSDPA CALL DROPS .......................................................................................... 188
LOW THROUGHPUT ISSUES .................................................................................... 188
Low Raw HS Throughput ............................................................................. 190
Low Net HS Throughput .............................................................................. 191
KNOWN ISSUES ................................................................................................. 192
WHERE TO GET MORE HELP? ........................................................................ 193

HELP FILE ........................................................................................................ 193
MYACTIX AND SUPPORT ....................................................................................... 194
Actix Analyzer UMTS/HSPA Training Course April 2009 Introduction 6
Introduction
Scope of the course

The UMTS/HSPA Training Course consists of two separate sections based on
different technologies. Each section provides an in-depth understanding of what
Actix Analyzer can do and how it can help you to improve the quality of service
for your network subscribers.
Advanced users will be re-introduced to Analyzer features and to new network

applications that can be performed using Analyzer by going through some
examples and exercises in the course. The instructors for this course are experts
in using Analyzer to increase productivity and are familiar with the challenges
faced by engineers working in cellular/PCS environments.
Class size is limited to ensure that everyone receives extensive one on one
instruction. Participants are given ample opportunity to ask questions relevant to
their particular optimization needs. Upon completing the course, participants will
be able to put what they learned in the class to work to identify and solve real
network problems.
The course begins with a high-level presentation of the Analyzer interface and its
capabilities. We will then cover how Analyzer can be customized to tailor existing
optimization processes to the specific needs of the participants.
Who Should Attend Analyzer Training?

 Engineers responsible for enhancing cellular performance and
implementing wireless system optimization
 System Performance Engineers responsible for measuring and quantifying

network quality relative to competitors and/or established benchmarks
 Engineers looking to further understand the application of drive test, call

trace and protocol data in optimizing networks
 Experienced technicians involved in field optimization
 Anyone looking to maximize the return on their investment in Actix

Analyzer
Actix Analyzer UMTS/HSPA Training Course April 2009 Introduction 7
Prerequisites
Before you begin, you should have attended the Basic Features Analyzer
Training Course where you are familiar with all the basic features and how to
navigate within Analyzer. You should also have:
 Familiarity with network infrastructure and operation of the air interface
 A general understanding of drive test and call trace collection and post-
processing methodology and advantages/limitations with each dataset
 Access to Actix Analyzer software
 Basic computer literacy, including familiarity with Windows and MS Office

applications
 A computer that should meet these minimal hardware requirements:
Item Requirement
Processor 600 MHz Pentium III-compatible or faster processor; 1GHz or

faster processor recommended.
Framework Before installing SQL Server 2005 Express Edition SP2, you must
install the .NET Framework 2.0; this occurs automatically in the
standard Actix installation.
Operating System Windows XP with Service Pack 2 or later.

Microsoft Windows 2000 Professional with SP4.
Microsoft Windows 2000 Server with Service Pack 4 or later.
Windows Server 2003 Standard, Enterprise, or Datacenter
editions with Service Pack 1 or later.
Windows Server 2003 Web Edition SP1.
Windows Small Business Server 2003 with SP1 or later.
Windows Vista.
Actix software runs on 64-bit Windows as a 32-bit application,

but dongles will only work on 32-bit Windows.
Memory 192 megabytes (MB) of RAM or more; 512 MB or more

recommended.
Hard Disk Approximately 350 MB of available hard-disk space for the

recommended installation.
Approximately 425 MB of additional available hard-disk space for
SQL Server Books Online, SQL Server Mobile Books Online, and
sample databases.
Other Requirements Microsoft Internet Explorer 6.0 SP1 or later.

Microsoft Office 2000 or above (required by Actix Software).
Actix Analyzer UMTS/HSPA Training Course April 2009 What can you do with Analyzer? 8
What can you do with Analyzer?

The flow chart below illustrates briefly how Analyzer can help you in your day-to-
day work.
Starting up Analyzer
Getting started by configuring cell site info, set

preferences, aggregating data and loading logfiles
Exploring workspace by examining the loaded data
Viewing Data by displaying in maps, charts, tables or

reports for easy analysis
Performing UMTS/HSPA Performing customized UMTS/HSPA

analyses based on analyses using queries such as filter,
preconfigured applications binned, histogram, crosstab and event
Reporting Network Performance by

preconfigured or customized report(s)
Saving your work or preferred layout using

the screen layout feature
Closing down Analyzer
Actix Analyzer UMTS/HSPA Training Course April 2009 UMTS Section 9
UMTS Section
The following section explains how Analyzer can help you to troubleshoot and
analyse the UMTS data.
Getting Started
Open Actix Software
Splash Screen
After you have clicked on Actix Software, a splash screen starts up and initializes
the software.
Choosing an Engineering Process
Configuring Cellrefs
The next step is to make sure a valid imported cell-site reference file - cellrefs
file is selected. To point Analyzer to your cellrefs file:
1. Select Tools  Preferences from the main menu.
2. In the Change Preferences dialog box, locate CellRefs  File

Location and click on the filename in the Value column to change your
filename.
3. In the Open dialog box, select the cellrefs file you would like to use and
select Open. In this course, we will be using ‘UMTS Training
Cellrefs.txt’ which is located at
C:\Program Files\Actix\Analyzer\Bin\Cellrefs
4. Click OK to close the Preferences dialog.
5. To make sure you’ve loaded the correct cellrefs, click on View
Display New Map from the main menu to display a new map. If an
empty map is displayed, right-click on the map, select Zoom  Go to
Layer  WCDMA_Cell-Beamwidth-LayerSize-SC or WCDMA_Site-
Site_Name.
The cell sites are now visible.
Configuring Your Solution

The next step is to configure your map views, set your event detection
thresholds, preferences and data aggregation before you load your data files.
Map Views
You may now configure your map view by:
 Setting up the map background and layers
 Changing the label properties
 Changing the display properties
 Showing lines to cell on the map, or
 Changing the size of cell site sectors.
Event Detection Thresholds and Data Aggregation

It is important to choose the scenario you prefer. To ensure an accurate
analysis, make sure you set the correct event detection thresholds values. You
can do this by selecting Tools  Preferences from the main menu.
Lastly, select the relevant data aggregation or different binning mode such as
time, location, distance and message to filter out the unimportant message
information and achieve a faster loading time.
The above mentioned configurations can be found in the

Analyzer Basic Features Guide.
Loading Data File

After you have configured all the settings and preferences, it is time to load your
data file(s). In this course, we will be loading the following data files:
 UMTS Voice 1.dt1
 UMTS Data 1.SD5
 Agilent Scanner 1.mdb
A ‘+’ will appear next to the Loaded Data Files folder in the Workspace
Browser once files have been loaded. Click on the ‘+’ to expand the folder and
view the loaded files. Notice that all of the files were loaded into this workspace.
Data files from any collection equipment supported by Analyzer can be opened
and displayed in the same workspace.
Exploring the Workspace

Examining UMTS Handset Data
1. Expand the UMTS Voice 1 file tree in the Attribute Explorer.
2. Expand the layers under the handset data stream labelled Nemo3GPP
(0), then expand the UMTS node and examine each data group and
parameter, as shown the figure below.
Upon loading a UMTS handset file, note that several data groups are created.
These data groups are common to all UMTS handset files, regardless of data
collection vendor. Each group will appear as long as at least one parameter
within that group was collected by the device.
The following data groups are created under the UMTS node:
 Downlink Measurements – This group contains Uu interface

measurements reported by the mobile.
 Pilot Measurements – This group contains signal strength

measurements for individual SCs detected within the logfile.
 Dedicated Radio Link – Once a call has been established, parameters

that are associated with the SCs serving the call, such as Handoff State,
are contained here.
 Uu_RRC – Radio Resource Control is the protocol layer governing air

interface communication within the UMTS network. Parameters associated
with protocol messaging can be found in this group.
 Event Data – Call events triggered by the current state of the UMTS
mobile. If an event is not present in the tree, it did not occur in the file.
This group also contains events with user-definable thresholds, such as
Uu_PilotPollution and Uu_CoverageLimited. The thresholds for these
events can be modified under the Tools → Thresholds menu.
 Statistics Data – This group contains statistics calculated based on UMTS

protocol messaging, including Call Duration and timing components of Call
Setup Time.
 Vendor Specific – This group contains parameters unique to a specific

type of data collection equipment.
 Rake Finger Measurements (Qualcomm chipset handsets only) – This

group provides individual finger measurements, including multipath
measurements for the same SC.
Additional attributes are available for UMTS files containing wireless data
activity:
1. Expand the UMTS Data 1 file tree in the Attribute Explorer.

2. Expand the layers under the Qualcomm SURF 6200 WCDMA Phone
(3) stream, and notice how the UMTS radio network metrics are
organized the same way as in the UMTS Voice 1 file.
3. Expand the layers under the Data Device (2) and expand the Data
Testing node. Examine each group and attribute, as shown the
screenshot on next page.
The Data Testing node in a UMTS handset stream provides data attributes that
are not specific to a single wireless technology.
Under the Data Testing node, the following groups may be found:
Application Measurements – Find the instantaneous application layer

throughput here. This value most closely approximates to the end user’s
experience.
Protocol Measurements – This group contains throughput values for each

layer in the IP stack. This group contains statistics for the IP, PPP, TCP, ICMP
and RLP2 layers.
IP (Internet Protocol) provides a connectionless addressing scheme of

packets, or datagrams, to be delivered in a packet-switched data network.
TCP (Transmission Control Protocol) establishes a virtual connection

between a source and a destination in a data network.
PPP (Point to Point Protocol) serves primarily to provide some security to

datagrams in the IP network.
ICMP (Internet Control Message Protocol) supports error, control and

informational messages within the data network.
RLP2 information is provided in some drive-test formats to represent the

physical connection between the mobile and the test system.
Task Settings – This group contains task identifiers including Task_Id and
Task_Name.
Task Summary – This group contains application level parameters summarizing

the entire task.
Ping Statistics – This group contains metrics for any ping session within the
logfile.
Application Statistics – This group contains the number of bytes transmitted

by the data application.
Connection – This group contains details for data connections activated within
the logfile.
HTTP Statistics – This group contains metrics for any HTTP session within the
logfile.
Examining technology-independent data

Under the UMTS Voice 1  Nemo3GPP (0) handset stream, expand the
Independent node to look at technology-independent parameters that have
been decoded. In addition to GPS measurements, device-specific data, and
internal Actix messages, find the following groups here:
GPS Data – This group contains mobile longitude, latitude, distance traveled,
and speed.
Message Info – The date and time for the start of the data stream can be
found in this group. This information is useful when building report templates.
Site Data Node – If a cell site database is being used, the software will
automatically calculate these measurements that take both the drive and the cell
site information into account. Some of the measurements contained here are:
 ServingCellDistance–distance, in meters, to the serving sector
 NeighborCellDistance–distance, in meters, to non-primary serving sectors
File Info – In this node find label and timestamp information for the logfile
under investigation.
Vendor Specific – Vendor-specific measurements may be grouped here, or

under the UMTS node. In either case, this group provides measurements specific
to the particular collection device used.
Device Info – This group contains settings for the mobile device on which data
is logged.
Examining UMTS scanner data

Due to the nature of the coding scheme in a UMTS system, scanner data is an
invaluable tool for detecting problems in the network. Because SCs are reused
across a UMTS network with a much lower frequency than in an FDMA/TDMA
network, each SC scan can be directly linked to a particular site or sector in the
network.
The Agilent Scanner 1.mdb file already opened in the workspace contains SC
scanner data in the E6455C (IMT2000 Receiver) (1) stream.
Expand the scanner stream to reveal the contents:
Under the UMTS data group, several groups have been created to
help you easily drill down into the data. For each scanner stream,
the following nodes are available:
Other – This group contains scanner measurements concerning RSSI, Chip

Offset, Carrier Error and the Scan Code Group.
Nth Best – This node contains ranked measurements for EcNo, RSCP, SC and
PathLoss. Within each group, the “0” element contains the best performing data.
For example, CPICH_Scan_EcIo_SortedBy_EcNo_0 gives the strongest EcNo
of all SCs scanned.
Ec/Io – This group contains the interference-to-chip-energy measurements

organized by various dimensions.
RSCP – This group contains the Received Signal Code Power organized by
various dimensions.
Delay – Find the CPICH Scan Delay Spread for each SC in this group.
Pilot Measurements – Find the CPICH PathLoss for each SC in this group.
Active Set – This group contains simulated Active Set measurements based on
scanner data and the user-defined WCDMA settings in the Tools  Preferences
dialog.
Monitored Set – This group contains simulated Monitored Set measurements

based on scanner data and the user-defined WCDMA settings in the Tools 
Preferences dialog.
Event Data – Events in this group are based on the simulated Active Set and
Monitored Set SCs based on scanner data and user defined thresholds set under
WCDMA in the Tools  Preferences dialog.
Searching for Attributes

Sometimes it can be quite tedious to locate the exact attribute (or parameters)
that you need for analysis. Use the “Find Attribute” feature to search the
parameter trees. You can perform the search by selecting
Tools  Find Attribute or Ctrl-shift-F from the main menu. The search panel
will open as part of the Workspace Explorer window.
Exercise: Favorites Group

It is a good idea to place your most frequently
accessed attributes in a Favorites Group. This
group can be viewed by clicking on the
Favorites tab in the Workspace.
You can either use the Find Attribute feature or right-click on the
attribute to add to Favorites.
In this exercise, please set the following favorites for UMTS handset parameters
based on handset stream of UMTS Voice 1:
1. In the Attribute Explorer, click to select the 3G UMTS  Downlink

Measurements  UTRA_UE_CarrierRssi attribute, then right-click on
it and choose Add to Favorites from the pop-up menu. Also add the
UE_TxPow attribute to Favorites.
2. Under Dedicated Radio Link, right-click on Uu_UE_HandoffState
and add it to Favorites.
3. Under the Event Data  Call group, find Uu_CallDropped and
Uu_OutgoingCallSetupFail and add them to Favorites.
4. Under the Event Data  Coverage group, find Uu_PilotPollution and
Uu_CoverageLimited and add them to Favorites.
5. In the Attribute Explorer, click on the Favorites tab. A tree view of
the items you added is displayed. You can easily move between All and
Favorites as necessary.
The attributes that you define as Favorites will be available on the Favorites tab
for any data file open in the workspace that contains those attributes, as well as
for any new files opened that contain the specified parameters.
To remove a parameter from favorites, select the parameter. Right-click on it

and choose ‘Remove Favorite.’
Favorites are saved in the Favorites.dat file located in the

C:\ProgramFiles\Actix\ Analyzer\Bin\XMLFiles directory. To share
Favorites with another user, copy the Favorites.dat file to the same
directory on the desired machine.
Viewing Data
In Analyzer, data can be viewed in a variety of ways to facilitate easy analysis.
You can plot parameters on maps and display them on charts, tables, and in
workbooks. Please refer to your Basic Features Guide for an overview of these
features.
Viewing Data on Maps

There are two options for viewing data on maps:
 To view any parameter on a new map: Right-click on the parameter of

interest in the Workspace Browser and select Display on Map.
 To view a parameter on a map already open in the workspace:

Click and drag the parameter of interest onto a map already open in the
workspace.
 For example, display the Uu_ActiveSet_EcNo from the handset stream

of the UMTS Voice 1 file on a map.
Right-click on one of
the legend and select
Multiline to display the
legend in multiple lines.
Modifying Legend Ranges

If you prefer to set a range that suits your preference. You can modify the
legend by following these steps:
1. In the legend, right-click on UMTS  Downlink Measurements 

Uu_ActiveSet_EcNo and select Modify Ranges to change the ranges
displayed.
2. Remove any unwanted ranges by highlighting the range and selecting

the Remove button. Ranges must be removed one at a time. Analyzer
will not allow the deletion of the last two remaining ranges.
3. Enter the maximum and minimum value for each range and click
Update to modify an existing range, or Add to add a new range. Use
the Below and Above buttons to specify “edge” ranges. The
recommended approach to modifying legend ranges is to start with the
minimum value ranges and work your way toward the maximum.
4. Within the Modify Ranges dialog, you can change the color assigned to
each of your new ranges. With the range highlighted, click on the
Selected Button in the Set Colors section. To set all of the ranges to
default colors, click on the Default button in the Set Colors section.
5. Press Close to close the Modify Ranges dialog and return to the
workspace. All range and color settings are automatically saved with the
Modify Ranges dialog is closed.
Use the Cancel button to back out of any changes you do not
want to keep.
More Range Display Options

Right-click on the stream in the legend for more legend options:
 Select Attribute Style to change the color, size and shape of the data
trail. These parameters affect all data points for this parameter,
regardless of value.
 Style Setting lets you decide whether to indicate a parameter’s value

range changes by color, size, or shape.
 The Set Legend To menu item allows you to maintain multiple legend
configurations for a single parameter. The default legend settings will
always be used upon entering a new Analyzer workspace. To maximize
the utility of this feature, give a unique name to each legend configuration
for a parameter, and set the preferred configuration to be the default.
 The Copy Legend to Clipboard and Export to File options let you
create an image of the legend for use in other Windows programs.
 Change the style of an individual range without re-entering the Modify

Ranges dialog by right-clicking on the range and selecting Selected
Range’s Style.
 Changes to legend settings are automatically saved by Analyzer. This

information is saved in XML files, one for each parameter. The files are
saved in the C:\Program
Files\Actix\Analyzer\Bin\FormatGroups\UserSettings folder.
After legends have been modified and saved as desired on one computer,
you can transfer these files to the same location on another computer to
share legend settings between users.
Using Map Offset Tool

Offsetting of a data trail on the map may be achieved by manually offsetting the
data on the map, or by specifying a numeric distance to offset the trail in the x
and y directions.
To use the Offset Tool to offset a trail:
1. Display UTRA_UE_CarrierRssi on the map in addition to

Uu_ActiveSet_EcNo_0 by dragging UTRA_UE_CarrierRssi onto the
existing map.
2. In the Map Layers dialog, highlight the
layer you wish to offset and then
select Offset  Offset Tool.
3. Move the Offset Tool cursor to
determine how much to offset the
trails. Click the mouse once to accept the modified position.

4. To remove the offset, select the offset layer in the Map Layers dialog,
select Offset, and click on Reset.
5. If you wish to specify a specific offset distance, type the distance in the
X and Y text boxes in the Offset Layers dialog. Type 0 for both the X
and Y offset to return the offset trail to its original position. The
distance units for offset are based on the setting found by right-
clicking on the map and selecting Map Units  Distance.
Uu_ActiveSet_EcNo_0
UTRA_UE_CarrierRssi
6. To remove the offset, select the offset layer in the Map Layers dialog,
select Offset, and click on Reset.
X and Y text boxes in the Offset Layers dialog. Type 0 for both the X and
Y offset to return the offset trail to its original position. The distance
units for offset are based on the setting found by right-clicking on the
map and selecting Map Units  Distance.
Exploring the Map Toolbar

The map toolbar contains many features to show more information on the map.
It is very useful – for example, you can use a Region Filter if you only want to
examine a smaller area or region. You can also make your own notation by using
the Annotations feature. This is useful if you want to print the map for your
report later.
As you may have noticed, it is not very easy for a first time user to remember all
the icons. To display the description of each icon, go to Tools  Preferences 
General Settings  unselect the Use Small Icon checkbox.
You can find more information in the Basic Features Guide regarding how to
print a map and the following map view configuration:
 Setup Map background and layers
 Change the label properties of a map layer
 Change the display properties of a map layer
 Show lines to cells on map, and
 Change the size of cell site sectors
Adding Annotations to the Map

Annotations are a means of adding text and simple shapes to your map. You can
use these to indicate trouble spots or point out features of interest in your
network.
1. In the Layer Control dialog, select the Annotations layer and use the
Reorder  Up button to move it to the top.
2. Close the Layer Control dialog.
3. Select the Annotations icon from the map toolbar. The

additional annotations icons will appear on the right of the map toolbar.
4. Click on the either the Symbol icon to mark a on the map or use the
Text icon to insert text. The cursor will change to insert text mode.
5. Click on the map to place the symbol or text and type in the desired
text.
6. Return the cursor to the passive mode by clicking on the Select icon
.
7. To edit the text, select the text using the Edit Text icon.
8. To change the style or font, click on the Edit Text icon and then click on
the text you want to edit, right click on the text again and select Tool 
Feature Style.
9. To remove text, select the text box using the Select tool and press the
delete key. If you want to remove all notations, click on the Clear icon.
Using Direction Button

The Direction button allows you to display directional arrows on any drive-test
map. These arrows indicate the direction of the drive test vehicle during
collection. The Direction icon is located on the Map Toolbar.
Filtering Data Using Region Filtering

The Region Filter can be used to filter data displayed on maps. It can be very
helpful when trying to isolate data in one geographical area.
1. From the Map Toolbar, click the Region Filter icon . Three additional
options will now appear on the map toolbar; including a Polygon drawing
tool. The cursor will now appear as a cross-hair on the map.
2. Draw the polygon over a certain map area by clicking on a series of
points. The first click on the map starts the polygon. Drag the cursor to
each corner of the desired region to filter and click the mouse once. To
finish drawing the polygon, double-click near the starting point to
establish a line between the last point and the first point.
3. Draw any other polygons, as needed.
4. To filter data, click the down-arrow next to Filter and select either
Include or Exclude. “Include” is the default filter.
Any additional attributes that are dragged onto a map

using regional filtering will also be filtered.
5. To remove the filter, select Remove All icon from the map toolbar.
This will delete all existing region filters in that map. Region filters in
other map windows are unaffected.
Viewing Data on Charts

Analyzer can create a variety of charts for the analysis and inspection of data.
There are two ways to view data on charts:
 To view any parameter on a new chart: Right-click on the parameter

of interest in the Workspace Browser and select Display on Chart.
 To view a parameter on a chart already open in the workspace:

Click and drag the parameter of interest onto a chart already open in the
workspace.
To demonstrate some of the chart capabilities in Analyzer, we will create a Time

Series chart containing wireless data parameters.
1. In the UMTS Data 1 file in the Attribute Explorer, expand Data Device
(2)  Data Testing  Application Measurements and select
App_Throughput_DL.
2. Right-click on App_Throughput_DL and choose Display on Chart
from the pop-up menu. Notice that a chart appears with a throughput
value at each data point.
3. Click on the Histogram button to view the data as a distribution. The

ranges that appear are the same ranges that were set for this attribute on
the map legend.
4. Click on the Series button to return the chart to a time series chart.
5. You may wish to examine an area with particularly high or low throughput
in detail. To zoom in on a section of the chart, click and drag a rectangle,
moving from upper left to lower right. To return to the previous zoomed
view, click and drag a rectangle moving from lower right to upper left.
6. Drag and drop App_Throughput_UL onto the chart.
7. Drag and drop Task_Time_Elapsed onto the chart. Your chart should
look like the screenshot below.
Throughput and Task Time appear on different axes as

they are measured in different units.
8. Drag and drop the Event_Task_Start and Event_Task_End events (from

the Event Data group) onto this chart. The events will appear on the
chart as vertical lines.
A Task defines a single user-defined process, which operates over a well-defined

period of time (that is, it has a start point and an end point), such as an FTP file
download, a PING command, or a web page download. In the case of drive tests,
all of the vendors have a series of pre-defined tasks and some allow users to
define custom tasks of their own.
Modifying Chart Properties

Many chart properties can be customized through the Properties dialog. Right-
click on the chart and choose Chart Properties from the menu.
1. Reposition the Properties Dialog so that you can see the chart with
the dialog open. As you change the properties of the chart, the chart is
automatically updated.
2. On the Chart Series page, click the Title button to change the title of
one of the series.
3. Still on the Chart Series page, use the up and down arrows to change
the order in which the parameters are plotted. This also affects their
position in the legend.
4. On the Chart Axis page, redefine the style for the axis, labels, and
ticks.
5. On the Chart Legend page, modify the fonts and colors.
6. Create a three-dimensional chart using the options on the Chart 3D
page.
7. Click Close to close the Properties dialog when you are satisfied with the
formatting you have done.
8. Click on the Copy icon to place a copy of your chart on the clipboard.
9. In Word or PowerPoint, click Edit  Paste to paste your chart into that
application.
10. In Analyzer, with the chart still open, create a map displaying the
same data. Make sure that the Select tool is activated on the map. Click
to select data on either the map or the chart and notice that the views
are synchronized.
Viewing Data in Tables

Tables provide a quick view of numeric data for a selected parameter. You can
look at statistics, such as mean, minimum, and maximum, histogram distribution
information, or the time series data for the parameter displayed on a
spreadsheet. Tables can be synchronized with maps to provide an integrated
view of network data. A trouble area that is identified quickly on a map using
visual inspection can then be examined more closely on a table by looking at
exact numerical values of key parameters.
There are two ways to view data on tables:
 To view any parameter on a new table: Right-click on the parameter

of interest in the Workspace Browser and select Display on Table.
 To view a parameter on a table already open in the workspace:

Click and drag the parameter of interest onto a table already open in the
workspace.
To demonstrate the functionality of the Analyzer table in network optimization

applications, we will create a new table containing some parameters related to
wireless data network analysis.
1. Display App_Throughput_DL from the Data Device (2) stream of

UMTS Data 1 on a table. To do this, select Data Device (2)  Data
Testing  Application Measurements  App_Throughput_DL, then
right-click and select Display on Table.
Stream Selection
Box
Histogram tab parameter selector
2. Drag App_Throughput_UL onto the same table to view the values

side-by-side.
3. Click on the Histogram tab and notice the ranges and counts. The
histogram ranges correspond to the map legend ranges set for the last
parameter displayed on the table. Use the drop-down list at the bottom
to switch between histogram values for the different parameters.
4. Click on the Statistics tab and notice the automatically calculated

statistics for all parameters displayed on the table.
5. Click on the Series tab to return to that view. Then drag the
Task_App_Bytes_DL and Task_App_Bytes_UL parameters onto
the same table.
6. Display Task_App_Bytes_DL and Task_App_Bytes_UL on a new
chart in the workspace.
7. Tile the table and the chart in the workspace by selecting Window 
Tile Horizontally from the main menu.
8. With the table and chart visible in the workspace, select any point on
the chart. Notice that the table synchronizes to the same point, and
that the throughput and round trip time values are now visible. In this
case, correlating the parameters using multiple views provides insight
into the amount of data downloaded during the application for which
instantaneous throughput values are available.
9. Open another UMTS data file in the current workspace. Use the stream
selection box to look at new handset data in the same table
configuration without having to repeat the work you did to set up the
original table.
Viewing Data in the Message Browser

Analyzer provides the Message Browser to allow you to analyze the messaging
reported by the logging device. The browser also includes events derived from
the Layer 3 messaging and searching and filtering operations on the data. The
Message Browser can play an integral part in a problem-area investigation when
it is used in conjunction with the Analyzer map and table.
To open the Message Browser right-click on the Nemo3GPP (0) handset stream
under the UMTS Voice 1 file and choose Display Message Browser from the
pop-up menu.
1. Click on an event in the Event Panel. Watch as the Messaging

Window synchronizes to display the messaging information
corresponding to the event you selected. This allows a quick view of the
specific messaging associated with a particular event.
2. The search function can be used to locate a particular parameter in the
messaging, even if the message name is unknown. In the Search box,
type ‘ActiveSetUpdateComplete’, then click the
Find Next button to find the next occurrence of this text string in
the file. Continue the search by clicking the Find Next icon to find each
subsequent occurrence of the string. The Active Set Update Complete
message signifies a change to the active set. The Soft Handover

message immediately following the Active Set Complete message
indicates which SCs have been added to or removed from the Active Set
during the procedure.
3. Right-click on the message area and choose Properties from the pop-
up menu. In the Properties dialog, click on the Message Format tab
and click the Change button to modify the font for the Message
Browser.
4. On the Message Filtering tab of the Properties dialog, uncheck All

Message Types and check UMTS RRC Messages to show only
messaging associated with the UMTS Radio Resource Control layer. The
message filtering capability is useful when investigating specific events,
and only those messages associated with those events are of interest.
5. Select a section of text in the Message Browser and click on Copy

icon. Open Microsoft Word and click Edit  Paste to paste the text
into the current document.
Viewing data in the Protocol Stack Browser

The Protocol Stack Browser allows the user to browse quickly through
messages by examining the header only. Once a message of interest is identified
in the top pane of the Protocol Stack Browser, the details of the message can be
examined in the bottom pane. The following Protocol Stack Browser view is
available for UMTS drive test data:
 UMTS Radio Interface – The message pane displays Radio Resource

Control (RRC) messaging, RRC message cause values, and Layer 3
messaging. RRC messaging represents communication between the
mobile and Node B, while Layer 3 messaging represents communication
between the mobile and 3G MSC.
Other UMTS views include:
 UMTS Radio Interface and Protocol Signaling
 UMTS Signaling and IP Messaging
 UMTS UTRAN Protocol Signaling
UMTS networks are backwards compatible with and can hand off to GSM
networks. Drive test files that contain UMTS and GSM / GPRS data will also have
the following Protocol Stack Browser views available:
 GSM Layer 3 – Message pane displays GSM Layer 3 messages / message

direction.
 GSM Layer 3 Signalling – Message pane displays GSM Layer 3

messages only.
 GPRS Events – Message pane displays messages signifying GPRS events.
 GPRS RLC / MAC – Message pane displays GSM Layer 3, and GPRS RLC
and MAC messages.
Viewing Data on Workbooks

In some cases, the Analyzer Table may not provide enough flexibility for viewing
data. Analyzer’s Workbook feature provides a more flexible method for detailed
analysis of trouble areas. This format allows data to be searched, sorted,
filtered, formatted, and printed through Microsoft Excel.
There are two ways to view data on workbooks:
 To view any attribute on a new workbook: Right-click on the

parameter of interest in the Workspace Browser and select Display on
Workbook.
 To view an attribute on a workbook that has already been opened:

Right-click on the parameter of interest in the Workspace Browser and
select Display on Workbook (active).
To view the Uu_UE_HandoffState attribute from the UMTS Voice 1:

Nemo3GPP (0) handset stream on a workbook:
1. Select Dedicated Radio Link  Uu_UE_HandoffState, then right-

click and select Display on Workbook.
The series data is displayed in Excel with time,

latitude, and longitude.
2. Click on the Histogram Formatted Data tab and notice the ranges
and counts.
3. Click on the Statistics Formatted Data tab and notice the

automatically calculated statistics.
4. Close the workbook without saving changes.
Viewing Data on StateForms

Actix StateForms allow you to view multiple performance metrics
simultaneously. Used in conjunction with the replay tool, maps, tables, and
charts, you can quickly ascertain the values of several optimization parameters
for problem identification.
Using Preconfigured StateForms

A number of preconfigured UMTS StateForms enable the user to quickly identify
and troubleshoot important network events. The preconfigured forms available
for UMTS drive test data are:
For example, display UE Active+Monitored Set form for UMTS Voice 1 file:
1. Right-click on the stream name Nemo 3GPP (0) in the Attribute

Explorer and choose Display Form UMTS UE Active+Monitored
Set. Forms can also be selected from the View  Forms option on the
main menu.
2. In general, when selecting a form, make sure that the form that you
have selected applies to the type of data you want to analyze.
Do not select the UMTS data form for a logfile

containing voice calls.
3. If the Stream Selector is not visible, right-click on the form and select
Stream Selector. The Stream Selector drop-down will appear. Use the
drop-down list to select the stream that you wish to view. If you are not
seeing information in the forms, verify that the right data stream is
selected.
4. Forms with measurement views like UMTS Active+Monitored Set

Form or the UMTS Data Session Form are best viewed when docked
close to the Replay Tool at the side of the screen, as seen in the
screenshot below.
To dock a form on the left side of the workspace, bring up

the form and click the docking button (to the left of the
minimize button). Click the gray horizontal line at the top of
the form, drag over the bottom section of the Workspace
Browser, and release. Once docked, as in the view above, it
is possible to adjust the top and right-hand borders to allow
for more viewing space in the platform.
5. Forms with chart views like the UMTS Voice Event Navigator or the
UMTS Data Event Navigator may be best viewed when docked at the
bottom of the screen as shown below.
To dock a form at the bottom of the workspace, bring up the form and use the
docking button (to the left of the minimize button) to dock it next the
Workspace Browser. Then, making sure that the right border of the form does
not stretch past the midpoint of the entire Analyzer viewing platform, drag the
thin gray line of the form to the bottom right side of the screen so that it is
completely on the left half of the viewing platform. Once docked as shown in the
view above, you can adjust the top border to allow for more viewing space in the
platform.
Preconfigured forms can be edited to meet your individual analysis needs. The
following sections describe the modification of existing forms, and the creation of
new forms from scratch using the StateForms Editor.
Exercise: Drop Call Analysis (Handover Problem)

Let’s make use of what we have displayed so far to investigate a call drop.
1. Drag and drop the Uu_HandoverProblem to the existing map.
2. Click on the Direction button to see which route or direction the

drive test is heading towards. Synchronize the map with the PSB and
stateforms and use the replay tool to see what happened at least 6 to 8
seconds before the call is dropped.
3. As you can see in the screenshot below, within an 6-second window
leading up to the drop, the number of times that the first best SC in the
monitored set is strong than the first best SC in the Active Set occurred
many times. If that number is greater than the number of times the
Active set is stronger than the Monitored set, and there are no Active
set update messages, a Handover problem is flagged.
4. Confirmed this by stepping through all the ActiveSetUpdate and
MeasurementReport messages in PSB.
Viewing Custom Forms with the StateForms Editor

The StateForms Editor allows you to view custom forms, modify existing
forms, and build new forms from scratch. The components of the StateForms
Editor window are shown in the screenshot below.
Stream
selection box
StateForms
toolbar
Attribute
values
1. From the Tools menu, select StateForms Editor.
If the generic UMTS handset form does not launch, right-

click on the blank stateform box and select Open File.
Browse to the
C:\Program Files\Actix\Analyzer\Stateforms directory
and open the file called UMTS Handset.axl.
2. Once loaded, make sure a stream is selected in the StateForms stream

selection box. The selected stream must correspond to data currently
displayed on another Analyzer view (map, chart, table or message
browser).
If the stream selection box is not visible, right-click on the

stateform box and select Stream Selector. The stream
selection box will appear.
3. Select any point on a map, chart, or table and notice that the contents
of the form will update to reflect the state of the network at the point
you selected.
Verify that the stream selector in the StateForms window is

showing the same stream that you are trying to synch
with.
Modifying an Existing StateForm File

You can use an existing StateForm file as it is, or you can make modifications to
it. The buttons on the StateForms tool bar are:
Delete, Cut, Copy, Paste, and Toggle Design Mode.
Select, Label, Attribute Value, Array Attribute Value, Time

Chart, Scan Chart, and Group Box.
Delete – Removes an object from the form. Using the delete key on your
keyboard will not work.
Cut – Removes an object from the form and puts it on the clipboard.
Copy – Copies an object to the clipboard by selecting it and click the Copy
button.
Paste – Pastes a copied of an object from the clipboard to the form.
Toggle Design Mode – Toggles between the design and view mode. To
exit the design mode and return to the view mode, click the Toggle Design
Mode button.
Select – Switches to select mode where it allows you to select an object

on the form.
Label – Creates a text box in a form by clicking and dragging a rectangle,

then type your text into the Caption field in the attribute window.
Attribute Value – Allows you to add an attribute to a form by clicking

and dragging a rectangle then choose an attribute from the list. The value
of that attribute will be displayed in the rectangle you defined.
Array Attribute Value – Allows you to add an array to a form by clicking

and dragging a rectangle to define a table. In the attribute window,
specify the number of rows and columns your table will have.
Time Chart – A Navigator Time chart helps to highlight problems or

important events within a logfile. An Attribute Time Chart provides more
information about a problem by highlighting how values change over time.
Scan Chart – A “Spectrum Analyzer”-like view; this chart is useful for

investigating array data from scanners and neighbor lists.
Group Box – Used to clarify which attributes on your form belong

together, click and drag to define a rectangle.
Suppose the UMTS handset file has almost everything you would like to see, but
that you are also interested in the handoff state.
To add handoff state to the StateForms display:
1. If you do not already have the StateForms file displayed, click Tools 
Display StateForms. Click Open File and choose the UMTS Handset
file.
2. Click on the Toggle Design Mode button on the StateForms tool
bar.
3. The StateForms window now shows the design view:
4. Add the Uu_UE_HandoffState label by clicking the Label button .

Click and drag the rectangle.
5. Select the label object and change the Caption to
Uu_UE_HandoffState.
6. To display the value for the Handoff State, click the Attribute Value
button then click and drag a rectangle to the right of the
Uu_UE_HandoffState label.
7. Select the Uu_UE_HandoffState Attribute Value object and make the
following modifications:
 Attribute: 3G UMTS  Dedicated Radio Link  Uu_UE_HandoffState
 Show Value Text: True
 Specify Min+Max: True
 Bar Range Min: 0
 Bar Range Max: 0
8. The final result should look like:
Exercise: Creating Your Own StateForms File

Several sample stateforms are provided by Actix. Custom forms can also be
designed from scratch. You can do this by creating a new StateForms file or by
adding a new sheet to a current file. We will create a new file or stateform
(Training StateForm) for this example. The finished form will look like this:
If you do not have the StateForms window open, click Tools  StateForms
Editor.
1. To start a new StateForms file, right-click inside the StateForms

Editor and select Design Mode. The stateforms sheet can now be
edited and objects can be added.
2. Add the UTRA_UE_CarrierRSSI label by clicking the Label button .

Click and drag the rectangle.
3. Select the label object and make these modifications in the Attribute
Window:
 Caption: UTRA_UE_CarrierRSSI
 Autosize Font: False
 Font Size: 9
4. Repeat steps 3 and 4 for the Uu_Pilot_Downlink_BER label, setting

the caption to ‘Uu_Pilot_Downlink_BER’.
5. To display the value for UTRA_UE_CarrierRSSI label, click the
Attribute Value button then click and drag a rectangle to the right of the
UTRA_UE_CarrierRSSI label.
6. Select the UTRA_UE_CarrierRSSI Attribute Value object and make the
following modifications:
 Attribute: 3G UMTS  Downlink Measurements 

UTRA_UE_CarrierRSSI
 Font Size: 9
7. Repeat steps 6 and 7 for the FER Attribute Value, setting the attribute to
Uu_Pilot_Downlink_BER.
8. To create the Attribute Bar for UTRA_UE_CarrierRSSI, click on the
Attribute Bar button then click and drag a rectangle to the right of the
UTRA_UE_CarrierRSSI attribute value object.
9. Select UTRA_UE_CarrierRSSI Attribute Bar and make the following
modifications in the Attribute Window:
 Bar Range Min: -110
 Bar Range Max: -45
 Bar Color:
 Attribute: 3G UMTS  Downlink Measurements 

UTRA_UE_CarrierRSSI
 Show Value Text: False
 Show Min Text: True
 Show Max Text: True
 Show Minor Ticks: True
 Show Major Ticks: True
 Minor Ticks Spacing: 5
 Font Size: 6
 Border Line: True
10. To create the Uu_Pilot_Downlink_BER attribute bar, click on the

Attribute Bar button, then click and drag a rectangle to the right of the
Uu_Pilot_Downlink_BER attribute value object.
11. Select the Uu_Pilot_Downlink_BER Attribute Bar object and
make the following modifications in the Attribute Window:
 Bar Color:
 Attribute: 3G UMTS  Pilot Measurements 

Uu_Pilot_Downlink_BER
 Font Size: 6
12. To add the Group Box object, click on the Group Box button,
then click and drag a rectangle around all of the items on your form.
13. Select the Group Box object and make the following modification in
the Attribute Window:
 Caption: Network Parameters
 Fore Color: Dark Blue
 Font Size: 14
 Default Font: False
 Font Bold: True
14. Click the Save As button and save the StateForms file in the
Stateforms directory and call it Training StateForms.axl.
15. Return to the View Mode by clicking on the Toggle Design Mode
button.
16. Test your new form by displaying a parameter from the UMTS
Voice 1 handset stream on a map. Make sure that the handset stream
is selected in the StateForms stream selector box. Click on any point on
the map, and see the parameter values for Carrier RSSI and Pilot
Downlink BER appear on your StateForm.
Performing Pre-configured UMTS Analyses

Reporting UMTS Network Performance
The reporting features in Analyzer allow you to create high-level management
reports based on your data. Two different mechanisms exist for producing
integrated, polished reports that can be used to analyze high-level network
statistics or communicate test results in a professional format:
 Application Packages are a technology-specific series of reports that are

installed automatically with every Actix Software installation. Application
Packs are typically used to obtain a high-level overview of call statistics.
They can be used when a professional, formatted output is required, but
time constraints do not allow for the creation of a custom template.
 Reports are user-definable formatted outputs that make use of Analyzer’s

integration with Microsoft Excel. Reports may be included with an Analyzer
installation (such as the UMTS Training Materials), but are not always
included. Reports, unlike Application Packs, allow for formatted outputs of
multiple streams of data. Use Reports when generating outputs for
multiple streams of data and when you want to design a custom
formatted template from scratch.
This section describes the use of both reporting mechanisms, including running
Application Packs, running pre-defined Reports, and creating custom Reports.
Application Packages
Actix Analyzer contains Application Packages specific to UMTS. The Application
Packs are a series of reports, each focusing on a particular aspect of mobile
network optimization.
The Application Packs currently available for analysis of UMTS handset data are:
 UMTS Call Statistics
 UMTS Call Setup Analysis
 UMTS CPICH Level Analysis
 UMTS Data Analysis
 UMTS Drive Test Summary
 UMTS Handoff Analysis
 UMTS Quality Analysis
 UMTS Cluster Acceptance App Pack
An Application Pack is currently available for analysis of UMTS scanner data:
 UMTS Accelerated Network Rollout (See Appendix UMTS.B)
Running Application Packs

Once a data file is loaded, the Application Packages can be accessed in one of
two ways:
1. Through the Analysis menu on the main menu.

2. By right-clicking on the stream name in the Workspace Browser
The Application Packs require Analyzer to be pointing to a

valid cellrefs file in order to function properly.
Once you have selected one of the Application Packs from the menu, an
Application Pack window will appear. The window is divided into two panes.
The top panel is called the Statistics Explorer, and it contains a summary of
major call events and statistics for the selected stream. Information in the cell
explorer is organized by serving site and sector.
The bottom pane is the Report Window and contains a list of available reports
associated with the selected Application Pack. Once executed, the results of the
reports can be saved, printed, and shown in their raw form in Microsoft Excel.
Statistics
Explorer
Summary
by Site
Report Window
UMTS Drive Test Summary

This application pack contains the following reports:
 File Summary – This report provides information about the drive route,
calls made and received, coverage and quality in the logfile.
 Coverage Summary – This report summarizes the strongest EcNo and

the strongest RSCP in the Active Set, providing statistics and distribution
information for each metric.
The Coverage Summary report is shown as below:
UMTS Call Setup Analysis

 Call Setup Status – This report provides a breakdown of call setup

attempts, including successful attempts, failed attempts, and failed
attempt causes.
 Call Sequence Outcome – This report provides a listing of which call

sequence messages have been seen for each call in the logfile.
UMTS Call Statistics

 Call Statistics – This report provides call setup and termination statistics,
including the access failure rate, dropped call rate, and successful call
rate.
 Call Sustainability – This report provides call duration statistics and is

particularly useful for analyzing the sustainability for long-call testing
configurations.
 Call Timing Analysis – This report provides time-based statistics for

each call recorded in the logfile. Timing analysis statistics include time
between setup messages, average time between measurement reports
and Active Set Updates, average time between Active Set Update
messages, and call duration.
UMTS CPICH Level Analysis

 CPICH b4 RRC Con Req – This report shows CPICH measurements for
the active and monitored sets in a five-second window leading up to each
RRC connection request in the logfile.
 CPICH after Call End or Drop – This report shows CPICH

measurements for the active and monitored sets in a ten-second window
following each successfully completed or dropped call.
 CPICH during Call – This report provides mean CPICH performance

metrics during each call in the logfile.
 CPICH before Call End or Drop - This report shows CPICH

measurements for the active and monitored sets in a five-second window
before the end of each call in the logfile.
UMTS Handoff Analysis

 Handoff Breakdown Analysis – This report provides handoff state

statistics, including actual vs. goal metrics for target percent of drive in
soft handoff.
 SHO per Event 1a 1b 1c – This report breaks down the number of Active
Set Update additions (Event 1a), removals (Event 1b) and replacements
(Event 1c) within the logfile.
UMTS Quality Analysis

 This application pack contains the following reports:
 Overall BLER – This report provides statistics and distribution

information for the block error rate for the downlink transport channel.
 BLER per Call – This report provides block error rate statistics on a per
call basis. Statistics provided include call duration, maximum BLER,
minimum BLER and mean BLER.
 BLER During SHO – This report provides BLER statistics during soft
handover. Statistics are calculated during the period from each RRC Active
Set Update message until each Update Complete message.
Running Reports from an Application Pack

As an example, we will run the BLER During SHO summary from the UMTS
Quality Analysis Application Pack.
1. Open UMTS Voice 1 file if it is not already open in your workspace.

2. Right-click on the Nemo3GPP (0) stream, and display UMTS Quality
Analysis from the menu.
3. Double-click on the BLER During SHO summary in the Report
Window.
4. You can look at the results of the report in Analyzer, or you can click on
the Show Excel Report to look at it in Excel, or click on Save to save
an .xls copy on your computer.
Running a Pre-Defined Report

Since Application Packs are built into the Analyzer, they may not exactly meet
your team’s reporting requirements. Additionally, App Packs can only be run on
a single stream of data. Analyzer Reports allow you to create custom reports
using Microsoft Excel, and those reports may include data from multiple streams.
Reports from multiple measurement sources allow you to compare data collected
simultaneously or look at your network before and after making a change.
In this section, you will populate a pre-defined report template that contains
multiple data streams. In the next section, you will create a custom report from
scratch.
To run the pre-defined report:
1. From the Analyzer main menu, select Workbook  Open

Workbook/Report.
2. Navigate to C:\Documents and Settings\All Users\Application
Data\Actix\Analyzer\Reports and open the report called UMTS – GPRS
Throughput Report.xls.
3. Select the Nemo3GPP (0) handset stream from EGPRS Drive Test
1.dt1 to replace the EGPRS stream. Click OK to confirm.
4. Next, select the Data Device (2) data stream from UMTS Data 1.sd5
and click OK.
5. After a few moments, the report will be generated within Microsoft
Excel. When this process is complete, click on the Report tab in the
Excel workbook and examine the formatted report.
The output of the report will look like this:
The UMTS Training Materials come with several pre-defined reports for UMTS
voice and data calls that can be run according to the steps above. The following
table describes each report and indicates what type of data each report should
be run with.
Report Name To be run on Data Description of Report

Streams of Type: Sheets
Application UMTS Data Logfile Provides statistics and
Throughput Report.xls distribution information for
downlink Application Throughput
UMTS – GPRS E/GPRS Data Logfile Provides distribution comparison
Coverage Report.xls UMTS Data Logfile via pie chart of coverage for an
E/GPRS drive and a UMTS drive
UMTS – GPRS E/GPRS Logfile Compares throughput statistics
Throughput Report.xls UMTS Data Logfile for an E/GPRS network and a
UMTS network
Performing Custom Analysis in Analyzer

You can create a wide variety of customized analyses using Analyzer. You may
want to highlight potential voice or data problem areas, or test for common
symptoms of bad radio link quality for the purpose of speeding up the analysis of
data. Your customized analysis, called a query, can be saved in a Workspace and
reused for future drive data. The queries can be created, accessed, and edited in
the Workspace through the Analysis Manager.
About Queries
Queries are a means of searching and filtering data based on events and
thresholds you define. Queries operate on binned data and are written using
Boolean expressions and arithmetic operations containing data parameters from
one or more data streams. Analyzer supports six types of queries:
 Filter Analysis
 Binned Query Analysis
 Cross Tab Query Analysis
 Event Query
 Statistic Analysis
 Histogram Analysis
Analyzer supports the use of queries to assist in the detection, correction, and
presentation of network problems. In this section a number of these analyses
are used for examining various aspects of voice and data networks.
All custom analyses can be saved for future use through the Analysis Manager:
1. Select Tools  Analysis Manager or press Ctrl-A to start the Analysis

Manager.
2. In the Analysis Manager, select the Existing Analysis tab.
3. Select any queries that you wish to save and click the Export button.
4. Browse to a folder that you wish to save your query in. Analyzer’s
default structure provides the C:\Program
Files\Actix\Analyzer\Queries folder for an easy place to store
queries.
5. Name the *.aqf file UMTS_Training_Class_Queries. All queries
created during training may be stored in the same file.
6. To import the queries into a new Analyzer session, go to the Existing
Analysis tab of the Analysis Manager and select the Import button.
Browse to find the *.aqf file in which you saved your queries.
Filter Analysis
Sometimes it is desirable to examine only a subset of the data points collected in
a logfile. We can use a filter to look only at those data points of interest to us.
A filter analysis tests data on a single criterion and displays the data only if the
criterion is met. This provides the engineer with a quick way to identify trouble
areas in which to focus optimization efforts.
Working with Pre-configured Filters

You have a set of UMTS filters installed in the workspace. These are:
 Poor Mobile Receive Power: Uu_ActiveSet_RSCP[0] < -95 dBm
 High Mobile Transmit Power: UE_TxPow > 0 dBm
 Low Mobile Transmit Power: UE_TxPow < -30 dBm
 High Mobile Receive Power: Uu_ActiveSet_RSCP[0] > -80 dBm
 Poor Ec/No: Uu_ActiveSet_EcNo[0] < -15 dBm
 Good Ec/No: Uu_ActiveSet_EcNo[0] > -8 dBm
To activate these pre-configured UMTS filters
1. Display any attribute of interest in the workspace (i.e. map, chart, table,
message browser).
2. Right-click on the stream name and select Filter, then the filtered
name.
3. All views will update to show only data points that meet the filter
criteria.
4. Multiple filters may be selected at once. The And and Or options on the
filter menu designate the method for combining multiple filters.
Filters can be used to quickly identify areas with poor network performance. In
this case, we will filter all points with high traffic channel downlink BLER, and use
the results to pinpoint where quality problems are occurring and try to
determine what is causing them. You can create a filter query which highlights
those points which have Uu_TrCh_DownlinkBlerAgg > 10% to identify all the
locations on the drive with poor quality of service.
To create this filter:
1. From the main menu, select Tools  Analysis Manager.

2. Select the Filter icon in the dialog and click on New.
3. For the Filter Name, enter ‘High Traffic Channel BLER’.
4. Use the Attribute Chooser to select Uu_TrCh_DownlinkBlerAgg

from the 3G UMTS  Downlink Measurements group.
It is important to use the Attribute Choose to choose your

attribute because Analyzer will automatically add the
state() function around your filter attribute, and “hold” it
across all other messages that do not contain that attribute.
5. Choose “>=” for the operator

6. Enter ‘10’ for the Threshold.
State() function returns the value of

an attribute at the current message
position or, if that has not been set,
the previous valid value.
7. Click OK to create the filter. Analyzer will automatically apply the filter
to any information already displayed in the workspace.
8. Confirm that the query was created by going to Tools  Analysis
Manager and clicking on the Existing Analyses tab. The High Traffic
Channel BLER filter should be listed under the Filters category.
9. From the Existing Analyses tab, save the High Traffic Channel BLER
Filter to the UMTS_Training_Class_Queries.aqf file by selecting it
and the High Traffic Channel BLER query and using the Export
button. Multiple queries may be saved in one *.aqf file.
10. Display any parameter (i.e. RSSI, EcNo, Uu_ActiveSet_SC_0) on
the map. Apply the filter by right-clicking on the stream name in the
Attribute Explorer and selecting Filter → High Traffic Channel BLER.
Notice that only points with BER exceeding the defined threshold appear
on the map. The filter has provided a quick way of illuminating trouble
spots and focusing optimization efforts.
Uu_ActiveSet_EcNo_0
with High Traffic Channel
BLER filter
11. Remove the filter from the map by right clicking on the handset
data stream under UMTS Voice 1 file by selecting Filter, and
unchecking the High Traffic Channel BLER filter. The filter can be
reapplied at any time through the same method.
In UMTS networks, areas with interference are typically identified as those
locations experiencing poor BLER but strong Carrier RSSI. Filters may be
combined using Boolean operations in Analyzer to look at more than one
condition at each data point.
12. Create a new filter called Strong Carrier RSSI, which filters on
data points where UTRA_UE_CarierRSSI is greater than –8 dB.
13. Apply the filter to the handset stream of UMTS Voice 1.

14. With the High Traffic Channel BLER filter applied, right click on
the handset stream, select Filter, and make sure that the AND operator
is selected with a bullet.
15. Returning to the Filter menu, apply the Strong Carrier RSSI filter
in addition to the High Traffic Channel BLER filter.
What do the data points remaining on the map at this point indicate?
Be sure to save the Strong Carrier RSSI filter, in addition to the other
queries you’ve created, in your UMTS_Training_Class_Queries.aqf file,
making sure to select all of the filters and queries.
Additional custom filters

Filters may be created on any parameter in the Attribute Explorer. Some
additional filter ideas that may be useful for UMTS analysis are included in the
UMTS Training Queries.aqf file that is installed with the training materials,
and are described here:
 The High Drive Test Speed filter shows data points at which the drive
test vehicle was traveling at speeds greater than 60 kilometers per hour.
This query will be valid for files containing the SpeedKph parameter in
the Independent  GPS Data group. This query may be modified for
different speeds, or to work with the SpeedMph parameter when
relevant.
 The Distant Server filter shows data points at which the serving cell is
more than 6 kilometers from the data point. This query is based on the
ServingCellDistance parameter, which is present in the Attribute
Explorer when the Actix Software is pointing to a valid cell site file.
 The Mobile Not In Idle State filter shows data points where the
Uu_CallState parameter is not equal to 1 (Idle). As with all filters, this
filter may be applied to any parameter displayed. For example, it may be
useful to map the UU_UE_HandoffState parameter and apply this filter
to show the Handoff State only when the mobile is in a call.
When entering a threshold for a parameter with discrete values, it

is necessary to type the enumerated value of the choice you wish to
select. In this case, it is necessary to type a ‘1’ in the text box as
selecting ‘1=idle’ from the drop down list will corrupt the filter.
Binned Query Analysis

The Binned Query allows you to define a new parameter based on existing
parameters, using functions and inequalities. The results of a binned query can
be displayed on a map, chart, table, or workbook.
ServingCellDistance in Miles
By default, Analyzer displays the serving cell distance in meters. A simple, yet
very useful example of a binned query is the conversion of the serving cell
distance from meters to miles.
Create the ServingCellDistance in Miles query using the Analysis Manager:
1. Select Tools  Analysis Manager.

2. Select the Binned Query icon in the dialog and click on New.
3. Enter ‘ServingCellDistance_in_Miles’ for the description.
4. In the parameters box, find the serving cell distance under
Independent  Site Data Node  ServingCellDistance and double-
click on it to add it to the expression.
5. At the end of the text in the Expression Builder, type in ‘/1609.344’.
6. Set the Format to Float. The easiest way to do this is to select the
Format drop down dialog and start typing Float in the window.
7. Click OK to create the query.

8. Click OK again to close the Analysis Manager.
The query will appear in the Queries group under every data stream
in the workspace. Under the handset stream, expand the Queries 
Binned Queries group.
9. Right-click on the ServingCellDistance_in_Miles query and choose

Display on Map to display the query results on a map.
Scanner Pilot Pollution Query

The Binned Query analysis allows you to create a new expression, as a
parameter, based on existing parameters. This is useful for adding non-standard
analyses, like pilot pollution based on UMTS scanner data, where each vendor
has their own definition for the analysis.
Mathematically speaking, the CPICH_Scan_EcIo_For_SC data set is an array that

contains Ec/Io data for all SCs measured at each data point. The array_count
function counts the number of SCs in this array which have an Ec/Io > -15 dB.
The query returns a ‘1’ when the Pilot Pollution criteria are met and a ‘0’ when
they are not.
In terms of the network, this query finds all bins where there were more than
four servers above -15 dB. Thus, this query detects areas where there are
multiple servers, no dominant server, and/or poor signal quality.
To create the Scanner Pilot Pollution query using the Analysis Manager:

3. Enter ‘Scanner Pilot Pollution’ for the Description.
4. We will create a custom parameter that counts the number of PNs

above –15 dB at each point on the drive, and returns a value of ‘True’ if
it exceeds 3. The Expression is:
array_count(CPICH_Scan_EcIo_For_SC[], >, -15) >= 4
5. In the lower right hand window, select ‘array_count’ from the list of
functions. Notice the pop-up description for each function. Double-click
on the ‘array_count’ function to add it to the expression. The
expression window now contains:
array_count(«attribute[]»,«operation», «expr»)
6. Highlight the <<attribute[]>> parameter. In the lower left hand
window, step through the 3G UMTS  EcIo group to find the
attribute CPICH_Scan_EcIo_for_SC. Double-click the attribute to
add it to the expression.
7. In place of <<operation>>, <<expr>>, enter ‘>’and ‘-15’.
8. After the closing parenthesis, enter ‘>=4’.
9. In the format drop-down list, set the Format to Boolean.
10. Click OK to finish creating the binned query. While still in the
Analysis Manager, take the opportunity to save the query to the
UMTS_Training_Class_Queries.aqf file.
11. Click OK to close the Analysis Manager.
This query is applicable to analyze Scanner data only.
Look at the results of the query for a UMTS scanner on the map. Points with Pilot
Pollution, as defined by the expression, will show up on the map as a Boolean 1.
Points with no Pilot Pollution will show up as a 0.
You may be interested in looking at the number of SCs above the threshold at
each location, as opposed to a Boolean value that designates data points where
more than four SCs are above that threshold.
How could you modify the Pilot Pollution Identification

query you just created to give the number of SCs above –15
dB at each data point?
The results of the Scanner Pilot Pollution query indicate where the Pilot Pollution
condition exists. To determine which SCs contribute to the condition, it may be
useful to display the EcIo values for each SC on a table, or to create a custom
StateForm for viewing the levels of the Top N SCs.
Additional Binned Queries

Binned queries may include any expression or combination of parameters from
the workspace. Some additional binned query ideas that may be useful for UMTS
analysis are included in the UMTS Training Queries.aqf file that is installed
with the training materials, and are described here:
 The Number of SCs Within 3 dB of the Strongest Server query

provides the number of SCs at each data point, including the strongest
SC, measured within 3 dB of the strongest server. The expression uses
the UMTS scanner parameter CPICH_Scan_EcIo_SortedBy_EcIo,
which provides the scanned EcIo values in order from strongest to
weakest. The array_max function is used to ensure that the strongest
EcIo value is selected for comparison purposes. The Format for this
expression is Count.
 The High Active Set Count query indicates data points where there are
three or more SCs in the Active Set. The threshold in this expression can
be modified as required. The Format for this expression is Boolean, so
that the query will return a ‘True’ or ‘False’ result depending upon
whether the high active set count condition is met.
 Some attributes, such as Uu_CallState, are collected infrequently, and

may appear sporadically when displayed on any data view. In such cases,
the state function may be used to hold the last valid value of the attribute
and provide a solid data trail. The Uu_CallState Last Valid Value query
demonstrates the use of the state function to hold the last valid value for
Uu_CallState, providing a solid data trail for that parameter.
 It may be desirable to find the strongest SC, or the EcIo of the strongest
SC, for a user-defined list. The “subarray” function types allow the user
to find the nth strongest/weakest element in a list specified by the user.
The Scanner Strongest SC - User Defined List and Scanner
Strongest EcIo - User Defined List queries return the strongest
SC/EcIo for SCs 11, 12, 13 and 14. The list may be modified for the SCs
of interest.
 It is possible to filter on the results of a binned query expression. This

technique is used in the Display SysInfo Messages filter. It shows only
data points at which these messages were received. The Filter Wizard for
this analysis is shown below:
The Message Type Filter expression was created to specify the messages to
include in the filter:
The expression uses the Boolean AND (‘&&’) operator to specify

Uu_RRC_MsgType numbers that indicate SysInfo messages (1100 – 3600).
The expression returns a “true” value if the current Uu_RRC_MsgType falls
within this range. The filter is set up to include only those data points where this
expression evaluates to “true”. When entering a threshold for a parameter with
discrete values, it is necessary to type the enumerated value of the choice you
wish to select. In this case, it is necessary to type a ‘1’ in the text box –
selecting ‘1 = true’ from the drop down list will corrupt the filter.
Histogram and Statistic Query Analysis

Serving cell distance is an important parameter to consider when diagnosing
network problems. Knowing the average serving cell distance throughout a
logfile or the number of data points at which the distance is high may indicate
whether the data network is performing properly.
Histogram and Statistic Queries are available to provide these analysis formats
for custom expressions. Since the serving cell distance in miles is not available
as a standard parameter, it is necessary to use the Histogram and Statistic
Query formats to provide results for this type of analysis.
ServingCellDistance in Miles Statistic Query

The following example describes the creation of a Statistic Query for the
ServingCellDistance in Miles custom expression.
1. Create a new Binned Query to provide the ServingCellDistance in

Miles. Refer to the previous Binned Query section if you have not
already created this query.
2. Display the ServingCellDistance in Miles binned query results for
UMTS Voice 1 on a chart to verify that the query is working properly.
3. From the Analysis Manager, create a new Statistic Query to provide

statistics for the new ServingCellDistance in Miles expression:
 Query Name: ServingCellDistance In Miles Statistics
 Expression: Use the button to select the ServingCellDistance

In Miles expression created in Step 1.
 Choose not to exclude data from the calculation.
4.
Statistic query results can be found in the Queries  Statistics group under
each data stream in your file. Display the ServingCellDistance In Miles
Statistics query results for UMTS Voice 1 on a table. Select the Statistics tab
on the table.
 What is the mean serving cell distance in miles for this file?
 What is the maximum serving cell distance in miles for this

file?
ServingCellDistance in Miles Histogram
The following example describes the creation of a Histogram for the
ServingCellDistance in Miles custom expression.
1. From the Analysis Manager, create a new Histogram to provide a

distribution plot for the ServingCellDistance In Miles parameter:
 Query Name: ServingCellDistance In Miles Distribution
 Expression: Use the button to select the ServingCellDistance

In Miles expression created in Step 1.
 Select the option to “Specify ranges for my histogram bars”.
 Set the following ranges:
 Click OK to exit the Histogram Wizard.
2. Save this query, in addition to the other queries you’ve created, in your
UMTS_Training_Class_Queries.aqf file, making sure to include all of
the previously created queries and filters.
3. Histogram query results can be found in the Queries  Histograms

group under each data stream in your Attribute Explorer. Display the
ServingCellDistance In Miles Distribution results on a chart.
In what range did most ServingCellDistance In Miles values

fall for this file?

A histogram query may be used to the view the distribution for any parameter
consisting of different data ranges than the defaults. The screenshot below is a
histogram for the UTRA_UE_CarrierRssi parameter. Notice that the ranges on

the X-axis are different from the default ranges provided when mapping this
parameter. Histogram Query results may be embedded in a report to provide
specialized ranges that are different from those used for mapping in the
workspace.
Crosstab Query
The Crosstab query is used to group data and display statistics for each group.
The groups can be sorted, and a query can contain several options for grouping
data.
...Sort by Site and Sector Crosstab Query

The Crosstab query may be used to group UMTS data by serving site and sector.
This example will have the Serving Site and Serving Sector as the grouping
options, and the mean RSSI, maximum number of SCs in the active set, and
number of dropped calls as the statistics to display for each group. When the
query is completed and the results are displayed on the Statistics Explorer, it will
look like this:
To Create the Crosstab Query:
2. Select the Crosstab Query icon and click on New.

3. Name the query “Sort by Site and Sector”.
4. Click on the New Dimension button. The query dimension allows you
to group and order your results using the attribute you select.
 Use the Attribute Chooser to select Independent  Site Data

Node  ServingCellID to add the serving site as the first dimension.
 Use the Attribute Chooser again to select Independent  Site Data

Node  ServingSectorID to add the serving sector as the second
dimension.
 The query statistics are the results that you would like to include for
each dimension. The parameters that you choose will be displayed
as the columns in the Statistics Explorer. The statistics that we will
include in this query are the mean RSSI, maximum number of
SCs in the active set, and the number of dropped calls. All of
these statistics will be available for the complete drive, for each
serving site and sector. Specific parameters relating to each

statistic are included in the table below.
5. Click on the New Statistic button to launch the Statistic Window.
 Enter the Statistic name.
 Use the Attribute Chooser to select the statistic of interest.
 Select the method to use to calculate the statistic.
 Click OK when finished with the Statistic Window.
Statistic Name Expression Method of

Calculation
Mean RSSI UTRA_UE_CarrierRssi Mean
Max Active Set Count Uu_ActiveSet_Count Max
# Dropped Calls Uu_CallDropped Count

(Note: it is necessary to change the format
group of this parameter to ‘Count’. To do
this, ‘Edit’ the expression and type ‘count’ in
the format group drop down.
6. Once completed, click OK in all other active dialogs to complete the

query.
7. Save the Sort by Site and Sector Crosstab query, in addition to the
other queries you’ve created, in your UMTS_Training_Class_Queries.
aqf file.
Display the Crosstab query results

Once created, the Crosstab query results can be displayed in the Statistics
Explorer by right clicking on the query in the Attribute Explorer, and selecting
Display in Statistics Explorer. The Statistics Explorer will launch and the
results can be viewed, sorted by Serving Cell ID or Serving Sector ID. The
queries can also be displayed in Excel workbooks.
 Run the Crosstab query on the UMTS Voice 1 handset stream.
Filter the Crosstab query results
The Filter button on the Statistics Explorer may be used to quickly filter
query results in the Stats Explorer and in any other data view. In this case, it
may be useful to view data for only one serving site, such as Site 109.
1. View Uu_ActiveSet_EcNo_0 from the UMTS Voice 1 handset stream

on a map. Display the Uu_CallDropped event on the same map.
2. Tile the map and the Statistics Explorer vertically in the workspace by
selecting Window  Tile Vertically.
3. In the Statistics Explorer, select the row for Site 109.
4. With the row for Site 109 selected, press the Filter button in the
Statistics Explorer. Notice that only data points served by this site
remain in the Statistics Explorer and on the map.
5. To remove filtering, click the Filter button again. The filter will be
unapplied from both the map and the Statistics Explorer.
Additional Crosstab queries

Crosstab queries may be used to sort statistics by any relevant dimension. Some
additional Crosstab query ideas that may be useful for UMTS analysis are
included in the UMTS Training Queries.aqf file that is installed with the
training materials, and are described here:
 The Sort by Strongest Active SC query provides the same statistics as

the Sort by Site and Sector query, though the results are sorted by the
strongest Active SC. The Copy From button in the Crosstab query wizard
may be used to copy the stats from the Sort by Site and Sector, instead
of building each statistic from scratch.
 The Sort by Data Task ID query provides statistics for a UMTS data log
sorted by the unique ID assigned to each task in the file. The statistics
provided include the Task Name for each task, throughputs, round trip
time values, and elapsed time for each task.
 The Sort by Data Task Name query provides statistics for a UMTS data
log sorted by the each task name in the file. The Task Name is not
necessarily unique within a logfile, so results may group several tasks
which have the same name. The statistics provided are similar to those
included in the Sort by Data Task ID query, and may be obtained by
using the Copy From button, instead of recreating the statistic from
scratch.
 The Sort by Call ID query provides statistics for each call in the logfile.
The Dimension for this query is the Uu_Call_ID parameter. The
Statistics for this query make use of expressions, defined as follows:
Statistic Expression Method of Format

Name Calculation Group
Call Duration Uu_CallDuration/60000 Maximum Value Float
(minutes)
Call Setup Uu_TimeBetweenRRC_REQandCallSta Maximum Value Time
Time (ms) rt
# Dropped Uu_CallDropped Count Count
Calls
# Call Setup default(Uu_IncomingCallSetupFail*1, Count Count
Failures Uu_OutgoingCallSetupFail*1)
% Bad Uu_Pilot_DownlinkBER >= 10 Percentage Percent
Quality True
The Sort by Call ID query will look like this when displayed on the Statistics
Explorer:
Event Query Analysis

The Event Query allows you to extract key performance statistics for a user-
defined time or message window before or after a defined event like a handover
failure or dropped call. Viewing the window surrounding an event can provide
insight into whether a pattern exists among undesirable events, such as multiple
drops in an area due to low coverage.
We will create an Event Query to return statistics for a five-second window for
each dropped call in the file. The query results can be displayed on the Statistics
Explorer as in the screenshot below:
To create the Dropped Call Window Event Query:
2. Select the Event Query icon in the dialog and click on New.
3. For the Trigger Selection, use the Attribute Chooser to select 3G

UMTS  Event Data  Call  Uu_CallDropped. The attribute will
show up in the triggering window.
4. Click Next> to continue.

5. For the name of the query, enter ‘Dropped Call Window’.
6. In an Event Query, the query dimension is set by default to be the
EventTime. In this case, we will use the default dimension.
7. To define a statistic to be displayed in the event window, click on the

New Statistic button to launch the Statistic window.
8. For the name, enter ‘Site ID’.
9. Choose the Edit button below the line that reads “Enter the
expression that should be calculated in your statistic:”.
10. The Expression Builder will launch. Inside the top portion of the
window, type State(). This State() function is required to ensure that
the last valid value of the parameter persists.
11. Click inside the parentheses of the State() function. In the
Parameters area of the Expression Builder, expand the Independent
 Site Data Node tree. Double-click on the ServingCellId parameter
to insert it into the expression.
12. Click OK to exit the Expression Builder.
13. In the Statistic window, select the method to calculate the

statistic. In this case, select Last Value. Click OK when finished with
the Statistic window.
14. Repeat steps 7 through 13 above to define the following statistics

(choose an appropriate name for each one). The statistics that do not
require the use of the State() function can be picked using the
Attribute Chooser instead of the Expression Builder.
Expression Method to Calculate

State(ServingSectorID) Last Value
State(Uu_Call_ID) Last Value
Uu_UE_HandoffState Last Value
UTRA_UE_CarrierRSSI Mean
UE_TxPow Mean
Uu_Pilot_DownlinkBER Mean
Uu_ActiveSet_SC[0] Last Value
Uu_ActiveSet_EcNo[0] Mean
query.
Displaying Event Queries

Once created, the event query can be displayed in the Statistics Explorer by
right-clicking on the query in the workspace, and selecting Display in Statistics
Explorer. The Statistics Explorer will launch and the results can be viewed,
sorted by the time of the event (in milliseconds). The queries can also be
displayed in Excel workbooks.
Run the event query on the UMTS Voice 1 handset stream.
 How many dropped calls occurred in this file?

 What appears to be the primary reason for the dropped call(s)?
Remember to save the Dropped Call Window event query, in addition to the
other queries you’ve created, in your UMTS_Training_Class_Queries.aqf file,
making sure to include all of the filters and queries.
Additional Event Queries

Event Queries may be developed to analyze any event within a logfile. Some
additional Event Query ideas that may be useful for UMTS analysis are included
in the UMTS Training Queries.aqf file that is installed with the training
materials, and are described here:
 The Active Set Update Summary Event Query provides statistics at

each Active Set Update in a logfile, including the SCs in the Active Set at
the Update, the Active Set Size at the Update, and the time between the
current and previous Active Set Updates.
 The Event Query can serve as a mechanism for extracting individual calls
as separate streams in the Attribute Explorer. This technique is illustrated
in the UMTS Drive Test Call Extractor Event Query. When displayed on
the Statistics Explorer, this query appears to be very similar to the Sort
by Call ID Query.
The two primary differences between the results of the UMTS Drive Test Call
Extractor Query and the Sort by Call ID Query are:
 The UMTS Drive Test Call Extractor Query contains an extra statistic,
in that Call ID is included as the last statistic.
 The Analyze button is active in the Statistics Explorer when the UMTS
Drive Test Call Extractor Query is displayed. Selecting any Call ID in
the Statistics Explorer and clicking the Analyze button will cause a new
substream containing data from that call to be extracted in the Attribute
Explorer. Data can be displayed and analyzed from any substream in the
same way for any standard stream.
The UMTS Drive Test Call Extractor Query is an Event Query set up as
follows:
 Trigger Selection: state(Uu_Call_ID)>0
 Messages Before Event: 0
 Messages After Event: 0
 Discriminator: state(Uu_Call_ID)
 Dimension: state(Uu_Call_ID) (remove the default EventTime

dimension)
 Statistics: Same as the statistics for the Sort by Call ID Query, with the
addition of the Call ID statistic (last value of state(Uu_Call_ID))
Reporting Network Performance

Creating a Custom Report
Creating your own formatted report template is as easy as viewing the data you
require on a workbook, and then formatting the report page using Excel.
The objective of this section is to create a simple report, like the one shown
below, to display a histogram distribution and statistics for
Uu_TrCh_DownlinkBlerAgg. Since BLER is a parameter that can be used to
estimate the integrity of the air interface, the value of this parameter throughout
a network is of great importance.
1. Ensure that the UMTS Voice 1.dt1 file is loaded into the Workspace.
2. Select Uu_TrCh_DownlinkBlerAgg from 3G UMTS  Downlink
Measurements. Right-click it and choose Display on Workbook.
Excel will launch. The Workbook will contain three sheets, which can be
accessed by clicking on the corresponding tab at the bottom sheet
window.
3. Click on any blank sheet in the workbook and rename the sheet
“Report”.
4. Click on the Histogram Formatted Data tab. Click and drag to define
a window around the data set, including the column headers.
5. Select the chart wizard icon from the top menu bar of Excel.
6. The chart wizard will open:
7. Select a simple column chart and follow the Wizard prompts and
instructions. Name the chart title “BLER Distribution”.
8. Click the Finish button in the chart wizard and a basic chart will be
created.
9. Cut and paste the new chart onto the “Report” sheet in the workbook
or choose to have the chart inserted as an object on the Report sheet.
10. To place the mean and standard deviation statistics in the table
in your report, type “=” in the cell you would like to hold the value on
the Report sheet. Then switch to the Statistic Formatted Data tab and
select the cell containing the data you wish to add to your report. Press
Enter after selecting that cell to create the reference.
11. Add a title to the worksheet, position the histogram on the page,
format a table around the statistics and add any other desired
formatting.
12. Remove all data in all sheets except those in Report sheet
before you save.
13. From the Excel main menu, select File  Save. Save the file in
C:\Program Files\Actix\Analyzer\Reports folder and name it
BLER_Histogram_and_Statistics_Report.
14. Close the Excel workbook.
Running Your Report with New Data

1. Ensure that the UMTS Voice 2 file is loaded into the Workspace.
2. Select Workbook  Open Workbook to open the
BLER_Histogram_and_Statistics_Report saved previously to the
C:\Program Files\Actix\Analyzer\Reports directory.
3. A dialog will appear that prompts you to select a data stream(s):
4. Select the Nemo3GPP (0) handset stream from UMTS Voice 2 file and
watch the formatted report regenerate for the new data.
Modifying a Custom Report

Reports can be upgraded or modified at any time. To modify an existing report:
1. Run the report through the Workbook  Open Workbook menu

before making any modifications.
2. Make modifications to the existing report, including adding additional
parameters from the same data stream, adding the same parameters
from different data stream, or making cosmetic adjustments.
3. Save the file.
Making modifications to a report by opening the Excel file in

Windows will cause the Analyzer report to become corrupt.
Some suggestions for upgrading existing reports:
 Add Additional Parameters to the Report - Add to the existing report

different parameters from the same data stream using the Display on
Workbook (Active) command. Update the Report page to show results
for all parameters included.
 Create a Comparison Report – Add to the existing report the same

parameter from a different data stream using the Display on Workbook
(Active) command. Update the Report page to show results for both data
sets.
 Provide Histogram Results as a Percentage – Histogram results

expressed as a percentage may provide a more meaningful comparison
than results expressed as a count. Create an Intermediate sheet in Excel
to convert the histogram values into percentages. Update the Source Data
for the histogram chart to reflect the new display method.
 Embed an Excel Macro in a Report – Any Excel format or technique

may be applied to a report, including macros which automate specific
tasks within Microsoft Excel. The UMTS_CarrierRSSI_Delta_Report
provides an example of a report containing an Excel macro. This report
provides a comparison of the UTRA_UE_CarrierRSSI parameter at
common locations in two different logfiles.
To generate results from the report:
1. For the best results, set the workspace binning to Location Binned, X Bin
Size = 200 meters, Y Bin Size = 200 meters.
2. Open two logfiles which contain common data points.
3. Run the UMTS_CarrierRSSI_Delta_Report on the two logfiles.
4. On the Report sheet, click the Create Table button. The Create Table
button invokes a macro that looks for matching locations in the two
logfiles, and populates the table with the CarrierRSSI values at those
data points.
5. To map the Carrier RSSI Delta values, save the resulting table as a
delimited text file. Use the File → Import Text File option to import
the data. Once the data is imported, the parameters may be viewed
using all standard viewing mechanisms.
Actix Analyzer UMTS/HSPA Training Course April 2009 HSPA Section 93
HSPA Section
This section explains how Analyzer can help you to troubleshoot and analyse the
HSPA data.
Getting Started
If Actix Software is loaded, you can restart the software by:
1. Close down the current Actix Software, then restart the software from
Start  All Programs  Actix  Actix Software, or
2. From the main menu, select File  Start New Engineering Process,
or
3. From the main menu, select File  New Workspace or press
Ctrl-Shift-N to start a new workspace, or
4. Click on the New Workspace icon to start a new workspace.
If you restart the entire Actix Software, a Splash screen will appear before the
Choose Engineering Process message box appears. Click on the Analyzer
Classic option to proceed.
If you prefer to set Analyzer Classic as your default startup application

every time you launch Actix Software, make sure you check on
before you click on Analyzer Classic to

begin.
Configuring Cellrefs
The next step is to make sure a valid imported cell-site reference file - cellrefs
file is selected. To point Analyzer to your cellrefs file:
1. Select Tools  Preferences from the main menu.
2. In the Change Preferences dialog box, locate CellRefs  File

Location and click on the filename in the Value column to change your
filename.
3. In the Open dialog box, select the cellrefs file you would like to use and
select Open. In this course, we will be using ‘HSPA Training
Cellrefs.txt’ which is located at
C:\Program Files\Actix\Analyzer\Bin\Cellrefs
4. Click OK to close the Preferences dialog.
5. To make sure you’ve loaded the correct cellrefs, click on View
Display New Map from the main menu to display a new map. If an
empty map is displayed, right-click on the map, select Zoom  Go to
Layer  WCDMA_Cell-Beamwidth-LayerSize-SC:850 or
WCDMA_Site-Site_Name. The cell sites are now visible.
Configuring Your Solution

Next you need to configure your map views, set your event detection thresholds,
preferences and data aggregation before you load your data files.
Map Views
You may now configure your map view by:
 Setting up the map background and layers
 Changing the label properties
 Changing the display properties
 Showing lines to cell on the map, or
 Changing the size of cell site sectors.
Event Detection Thresholds and Data Aggregation

It is important to choose the scenario you prefer. To ensure an accurate
analysis, make sure you set the correct event detection thresholds values. You
can do this by selecting Tools  Preferences from the main menu.
Lastly, select the relevant data aggregation or different binning mode such as
time, location, distance and message to filter out the unimportant message
information and achieve a faster loading time.
The above-mentioned configurations can be found in the

Analyzer Basic Features Guide.
Loading Data File

After you have configured all the settings and preferences, is time to load your
data file(s). In this course, we will be loading the
HSDPA data files:
 NENY_M01A_S05_K01_D01_07222008_001
 NENY_M01A_S05_K01_D01_07222008_002
HSUPA data file:
 HSUPA file.dt1
A ‘+’ will appear next to the Loaded Data Files folder in the Workspace
Browser once files have been loaded. Click on the ‘+’ to expand the folder and
view the loaded files. Notice that all of the files were loaded into this workspace.
Data files from any collection equipment supported by Analyzer can be opened
and displayed in the same workspace.
Exploring the Workspace

Examining HSUPA file.dt1
1. Expand the HSUPA file.dt1 file tree in the
workspace.
2. Expand the layers under the Nemo3GPP
(0) stream and examine each data group
and parameter or attribute, as shown in the
screenshot beside.
Several data groups are common in Analyzer to all
UMTS/HSPA files, regardless of data collection
vendor. Each group will appear as long as at least
one attribute within that group was collected by the
device.
The following HSPA specific data groups are created

under the MS4 stream:
 Dedicated Radio Link

This 3G HSPA group contains measurements
from the Actix Event Detection such as HSPA
serving cell, Status, Call ID, source & target
cell for HS mobility, HSPA cell change site &
frequency type, HSPA mode, and status in HSPA/FACH/Idle/Start time and

so on.
 Downlink Measurements
This 3G HSDPA group includes measurements reported by the UE related
to HSDPA technology such as payload rate, throughput MAC, average CQI,
NACK rate, DTX rate, UE frame usage and so on.
 Uplink Measurements
This 3G HSUPA group includes measurements reported by the UE related
to HSUPA technology such as payload rate, SGI average, ACK and NACK
rate, UE frame usage, count/modulation/SF/TB size for Traffic Channel
Link and so on.
 Event Data
This 3G HSPA group contains HSPA related events such as call setup ok,
call drop, low raw or net throughput, cell change ok and so on.
 Statistic Data
This 3G HSPA group contains measurements related to the timing of the
HSPA procedure such as session duration, cell change duration or time
between, average TCP throughput during cell change and so on.
There are common attributes shared between UMTS and HSPA. Details
regarding UMTS Drive Test Measurements group’s attributes can be
found in the UMTS Section.
Searching for Attributes

Sometimes it can be quite tedious to locate the exact attribute (or parameters)
that you need for analysis. Use the “Find Attribute” feature to search the
parameter trees. You can perform the search by selecting
Tools  Find Attribute or Ctrl-shift-F from the main menu. The search panel
will open as part of the Workspace Explorer window.
Exercise: Favorites Group

It is a good idea to place your most frequently accessed attributes in a Favorites
Group. This group can be viewed by clicking on the Favorites tab in the
Workspace.
You can either use the Find Attribute feature or

Right-Click on the attribute to add to favorites.
In this exercise, please set the following favorites for handset attributes based
on Nemo3GPP (0) handset stream of HSUPA file.dt1:
1. In the Workspace, click to select the DownLink Measurements  3G

UMTS  3G HSDPA  Uu_HSDPA_Throughput_MAC attribute, then
right-click on it and choose Add to Favorites from the pop-up menu.
Add also Uu_HSDPA_NACK_Rate_without_DTX and
Uu_HSDPA_UeFrameUsage to your favorite group.
2. Under Uplink Measurements  3G UMTS  3G HSUPA, select the
following attributes to your favorite group:
 Uu_HSUPA_RSN_Distribution_0
 Uu_HSUPA_PayloadRate_L1
 Uu_HSUPA_SGI_Average
3. To view your favorites, at the workspace, click on the Favorites tab. A

tree view of the items that were added is displayed. You can easily
move between All and Favorites as necessary.
The parameters that you define as favorites will be available on the Favorites
tab for any data file open in the workspace that contains those parameters, as
well as for any new files opened that contain the specified parameters.
To remove a parameter from favorites, select the parameter. Right-click on it

and choose ‘Remove Favorite.’
Favorites are saved in the Favorites.dat file located in the

C:\ProgramFiles\Actix\ Analyzer\Bin\XMLFiles directory. To share
Favorites with another user, copy the Favorites.dat file to the same
directory on the desired machine.
Viewing Data
In Analyzer, data can be viewed in a variety of ways to facilitate easy analysis.
You can plot parameters on maps and display them on charts, tables, and in
workbooks. Please refer to your Basic Features Guide for an overview of these
features.
Viewing Data on Maps

There are two options for viewing data on maps:
 To view any parameter on a new map: Right-click on the parameter of

interest in the Workspace Browser and select Display on Map.
 To view a parameter on a map already open in the workspace:

Click and drag the parameter of interest onto a map already open in the
workspace.
 For example, display the DownLink Measurements  3G UMTS  3G

HSDPA  Uu_HSDPA_Throughput_MAC attribute on map.
Right-click on one of the legend

and select Multiline to display the
legend in multiple lines.
Modifying Legend Ranges

If you prefer to set a range that suits your preference. You can modify the
legend by following these steps:
1. In the legend, right-click on Uu_HSDPA_Throughput_and select

Modify Ranges to change the ranges displayed.
2. Remove any unwanted ranges by highlighting the range and selecting

the Remove button. Ranges must be removed one at a time. Analyzer
will not allow the deletion of the last two remaining ranges.
3. Enter the maximum and minimum value for each range and click
Update to modify an existing range, or Add to add a new range. Use
the Below and Above buttons to specify “edge” ranges. The
recommended approach to modifying legend ranges is to start with the
minimum value ranges and work your way toward the maximum.
4. Within the Modify Ranges dialog, you can change the color assigned to
each of your new ranges. With the range highlighted, click on the
Selected Button in the Set Colors section. To set all of the ranges to
default colors, click on the Default button in the Set Colors section.
5. Press Close to close the Modify Ranges dialog and return to the
workspace. All range and color settings are automatically saved with the
Modify Ranges dialog is closed.
Use the Cancel button to back out of any changes you do not
want to keep.
More Range Display Options

Right-click on the stream in the legend for more legend options:
 Select Attribute Style to change the color, size and shape of the data
trail. These parameters affect all data points for this parameter,
regardless of value.
 Style Setting lets you decide whether to indicate a parameter’s value

range changes by color, size, or shape.
 The Set Legend To menu item allows you to maintain multiple legend
configurations for a single parameter. The default legend settings will
always be used upon entering a new Analyzer workspace. To maximize
the utility of this feature, give a unique name to each legend configuration
for a parameter, and set the preferred configuration to be the default.
 The Copy Legend to Clipboard and Export to File options let you
create an image of the legend for use in other Windows programs.
 Change the style of an individual range without re-entering the Modify

Ranges dialog by right-clicking on the range and selecting Selected
Range’s Style.
 Changes to legend settings are automatically saved by Analyzer. This

information is saved in XML files, one for each parameter. The files are
saved in the C:\Program

Files\Actix\Analyzer\Bin\FormatGroups\UserSettings folder.
After legends have been modified and saved as desired on one computer,
you can transfer these files to the same location on another computer to
share legend settings between users.
Using Map Offset Tool

Offsetting of a data trail on the map may be achieved by manually offsetting the
data on the map, or by specifying a numeric distance to offset the trail in the x
and y directions.
To use the Offset Tool to offset a trail:
1. Display the DownLink Measurements  3G UMTS  3G HSDPA 

Uu_HSDPA_CQI_Average onto the existing map.
2. In the Map Layers dialog, highlight the layer you wish to offset and
then select Offset  Offset Tool.
3. Move the Offset Tool cursor to determine
how much to offset the trails. Click the
mouse once to accept the modified
position.
Uu_HSDPA_CQI_Average
Uu_HSDPA_Throughput_MAC
4. To remove the offset, select the offset layer in the Map Layers
dialog, select Offset, and click on Reset.
X and Y text boxes in the Offset Layers dialog. Type 0 for both the X
and Y offset to return the offset trail to its original position. The distance
units for offset are based on the setting found by right-clicking on the
map and selecting Map Units  Distance.
Exploring the Map Toolbar

The map toolbar contains a lot of features to show more information on the map.
It is very useful – for example, you can use a Region Filter if you only want to
exam a smaller area or region. You can also make your own notation by using
the Annotations feature. This is very practical if you want to print the map for
your report later.
As you may have noticed, it is not very easy for a first time user to remember all
the icons. To display the description of each icon, go to Tools  Preferences 
General Settings  unselect the Use Small Icon checkbox.
You can find more information in the Basic Features Guide regarding how to
print a map and the following map view configuration:
 Setup Map background and layers
 Change the label properties of a map layer
 Change the display properties of a map layer
 Show lines to cells on map, and
 Change the size of cell site sectors
Adding Annotations to the Map

Annotations are a means of adding text and simple shapes to your map. You can
use these to indicate trouble spots or point out features of interest in your
network.
1. In the Layer Control dialog, select the Annotations layer and use the
Reorder  Up button to move it to the top.
2. Close the Layer Control dialog.
3. Select the Annotations icon from the map toolbar. The

additional annotations icons will appear on the right the map toolbar.
4. Click on the either the Symbol icon to mark a on the map or use the
Text icon to insert text. The cursor will change to insert text mode.
5. Click on the map to place the symbol or text and type in the desired
text.
6. Return the cursor to the passive mode by clicking on the Select
icon .
7. To edit the text, select the text using the Edit Text icon.
8. To change the style or font, click on the Edit Text icon follow by click on
the text you want to edit, right click on the text again and selecting
Tool  Feature Style.
9. To remove text, select the text box using the Select tool and press the
delete key. If you want to remove all notations, click on the Clear icon.
Using Direction Button

The Direction button allows you to display directional arrows on any drive-test
map. These arrows indicate the direction of the drive test vehicle during
collection. The Direction icon is located on the Map Toolbar.
Filtering Data Using Region Filtering

The Region Filter can be used to filter data displayed on maps. It can be very
helpful when trying to isolate data in one geographical area.
1. From the Map Toolbar, click the Region Filter icon . Three additional
options will now appear on the map toolbar; including a Polygon
drawing tool. The cursor will now appear as a cross-hair on the map.
2. Draw the polygon over a certain map area by clicking on a series of
points. The first click on the map starts the polygon. Drag the cursor to
each corner of the desired region to filter and click the mouse once. To
finish drawing the polygon, double-click near the starting point to
establish a line between the last point and the first point.
3. Draw any other polygons, as needed.
4. To filter data, click the down-arrow next to Filter and select either
Include or Exclude. “Include” is the default filter.
Any additional attributes that are dragged onto a map

using regional filtering will also be filtered.
5. To remove the filter, select Remove All icon from the map toolbar.
This will delete all existing region filters in that map. Region filters in
other map windows are unaffected.
Viewing Data on Charts

Analyzer can create a variety of charts for the analysis and inspection of data.
There are two ways to view data on charts:
 To view any parameter on a new chart: Right-click on the parameter

of interest in the Workspace Browser and select Display on Chart.
 To view a parameter on a chart already open in the workspace:

Click and drag the parameter of interest onto a chart already open in the
workspace.
To demonstrate some of the chart capabilities in Analyzer, we will create a Time

Series chart containing wireless data parameters. Make sure the
NENY_M01A_S05_K01_D01_07222008_001 file is loaded.
1. In the Qualcomm UMTS Handset (TM 6280) (3) - MS4 Handset

Measurements stream expand DownLink Measurements  3G UMTS 
3G HSDPA and select Uu_HSDPA_Throughput_MAC.
2. Right-click on Uu_HSDPA_Throughput_MAC and choose Display on
Chart from the pop-up menu. Notice that a chart appears with a
throughput value at each data point.
3. Click on the Histogram button on the menu bar to view the data as
a distribution. The ranges that appear are the same ranges that were
set for this parameter on the map legend.
4. Click on the Series button to return the chart to a time series chart.
5. You may wish to examine an area with particularly high or low
throughput in detail. To zoom in on a section of the chart, click and drag
a rectangle, moving from upper left to lower right. To return to the
previous zoomed view, click and drag a rectangle moving from lower
right to upper left.
6. Drag and drop DownLink Measurements  3G UMTS  3G HSDPA
 Uu_HSDPA_NACK_Rate_without_DTX and
Uu_HSDPA_UeFrameUsage onto the same chart and examine the
data.
Modifying Chart Properties

1. Many chart properties can be customized through the Properties dialog.
Right-click on the chart and choose Chart Properties from the menu.
2. Reposition the Properties Dialog so that you can see the chart with
the dialog open. As you change the properties of the chart, the chart is
automatically updated.
3. On the Chart Series page, click the Title button to change the title of
one of the series.
4. Still on the Chart Series page, use the up and down arrows to change
the order in which the parameters are plotted. This also affects their
position in the legend.
5. On the Chart Axis page, redefine the style for the axis, labels, and
ticks.
6. On the Chart Legend page, modify the fonts and colors.
7. Create a three-dimensional chart using the options on the Chart 3D
page.
8. Click Close to close the Properties dialog when you are satisfied with
the formatting you have done.
9. Click on the Copy icon to place a copy of your chart on the clipboard.
10. In Word or PowerPoint, click Edit  Paste to paste your chart into
that application.
11. In Analyzer, with the chart still open, create a map displaying the
same data. Make sure that the Select tool is activated on the map. Click
to select data on either the map or the chart and notice that the views
are synchronized.
Viewing Data in Tables

Tables provide a quick view of numeric data for a selected parameter. You can
look at statistics, such as mean, minimum, and maximum, histogram distribution
information, or the time series data for the parameter displayed on a
spreadsheet. Tables can be synchronized with maps to provide an integrated
view of network data. A trouble area that is identified quickly on a map using
visual inspection can then be examined more closely on a table by looking at
exact numerical values of key parameters.
There are two ways to view data on tables:
 To view any parameter on a new table: Right-click on the parameter

of interest in the Workspace Browser and select Display on Table.
 To view a parameter on a table already open in the workspace:

Click and drag the parameter of interest onto a table already open in the
workspace.
To demonstrate the functionality of the Analyzer table in network optimization

applications, we will create a new table containing some parameters related to
wireless data network analysis. In this example, we will be looking at the
retransmission sequence numbers before a call dropped. Make sure the HSPA
file.dt1 is loaded.
1. Display the Uu_HSUPA_RSN_Distribution_0 attribute from the

handset stream of HSPA File 1 on a table. To do this, select UpLink
Measurements  3G UMTS  3G HSUPA stream then right-click and
select Display on Table.
2. Drag the rest of the RSN attributes such as
Uu_HSUPA_RSN_Distribution_1, Uu_HSUPA_RSN_Distribution_2
and Uu_HSUPA_RSN_Distribution_3 onto the same table.
3. Drag the 3G UMTS  Event Data  3G HSPA  Call 
Uu_HSPACall_Dropped and DownLink Measurements  3G UMTS
 3G HSDPA  Uu_HSDPA_Throughput_MAC on to the same table
to view the values side-by-side.
4. Click on the Histogram tab and notice the ranges and counts. The
histogram ranges correspond to the map legend ranges set for the last
attribute displayed on the table. If you have displayed two or more
attributes, use the drop-down list at the bottom to switch between
histogram values for the different attributes.
You can select

the attribute
from here to be
displayed on
histogram.
5. Click on the Statistics tab and notice the automatically calculated

statistics for the attributes displayed on the table. Click on the Series
tab to return to that view.
6. To further investigate, display Uu_HSDPA_Throughput_MAC,

Uu_HSDPA_CQI_Average, Uu_HSDPA_NACK_Rate_without_DTS
and the Uu_HSPACall_Dropped on a chart.
7. Tile the table and the chart in the workspace by selecting Window 
Tile Horizontally from the main menu.
8. With the table and chart visible in the workspace, select any point on
the table. Notice that the chart synchronizes to the same point. Step
backwards from the Call Dropped on the table and notice the low
throughput values although high NACK rate and high average CQI.
9. If you have another HSPA file in the current workspace, use the stream
selection box to look at new handset data in the same table
configuration without having to repeat the work you did to set up the
original table.
Viewing Data in the Message Browser

Analyzer provides the Message Browser to allow you to analyze the messaging
reported by the logging device. The Browser also includes events derived from
the NAS or Layer 3 messaging and searching and filtering operations on the
data. The Message Browser can play an integral part in a problem-area
investigation when it is used in conjunction with the Analyzer map and table.
Make sure the HSPA file.dt1 file is loaded. To open the Message Browser, right-
click on the Nemo3GPP (0) stream and choose Display Message Browser
from the pop-up menu.
1. Click on an event in the Event Panel. Watch as the Messaging

Window synchronizes to display the messaging information
corresponding to the event you selected. This allows a quick view of the
specific messaging associated with a particular event.
2. The search function can be used to locate a particular parameter in the

messaging, even if the message name is unknown. In the Search box,
type RRCConnectionRelease then click the Find
Next icon to find the next occurrence of this text string in the file.
Continue the search by clicking the Find Next icon to find each
subsequent occurrence of the string.
3. Right-click on the message area and choose Properties from the pop-
up menu. In the Properties dialog, click on the Message Format tab
and modify the Font for the Message Browser.
4. Select a section of text in the Message Browser and click on the Copy
icon. Open Microsoft Word and click Edit  Paste to paste the text
into the current document.
Viewing Data in the Protocol Stack Browser

The Protocol Stack Browser (PSB) is a new view that allows the user to quickly
browse through messages by examining the header only. Once a message of
interest is identified in the top pane of the Protocol Stack Browser, the details of
the message can be examined in the bottom pane.
HSPA uses the same protocols as UMTS for example NAS is called Layer 3 in
PSB and the RRC protocols. The main difference between UMTS and HSPA is
that the RRC messages contain more information, but they are the same
messages as UMTS.
The following UMTS PSB can be found in the UMTS section:
 UMTS Radio Interface
 UMTS UTRAN Protocol Signaling
 UMTS Radio Interface and Protocol Signaling
 UMTS Signaling and IP Messaging
Exercise: Call Drop Analysis

This is a simple exercise demonstrating how you can troubleshoot a dropped call
by using the map, table, protocol stack browser, stateform and message
browser. Make sure the NENY_M01A_S05_K01_D01_07222008_001 file is
loaded. As you already knew, HSPA is not an event-based technology. It is wise
to begin your investigation from the UMTS perspective.
1. In the Qualcomm UMTS Handset (TM 6280) (3) - MS4 Handset

Measurements stream expand DownLink Measurements  3G UMTS
and select Uu_ActiveSet_EcNo and display on map and chart.
2. Drag the DownLink Measurements  3G UMTS  Event Data 
Call  Uu_CallDropped_PS event onto the same map and chart.
3. Use the Direction arrow to determine the drive direction.
4. Watch the lines to cells at the end of the drive route. Notice that at the
end of the drive, the serving sector is the same as at the start of the
drive.
5. You can also use the Replay tool to simulate the drive test and view all
information simultaneously in map, chart, protocol stack browser and
table.
6. Right click on the MS4 handset stream and select Protocol Stack
Browser  UMTS Radio Interface view.
7. Right click on the MS4 handset stream and display the UMTS Active
Nbor Sets Chart and UMTS PS Event Navigator StateForms.
Arrange them by either moving them around or select Window  Tilt
Horizontally.
8. Synchronize the Protocol Stack Browser and StateForms with the
Uu_CallDropped_PS event on the map or chart.
At a glance at the chart and the UMTS Active Nbor Sets Chart stateForm,
you can see that the RF condition is poor and the serving cell is very weak
compared to the neighbors.
9. At the PSB, scroll up a little to msg 029063 at 07:54:50.010 and look
at the Active Set Update right before the call dropped. It seems like
the Active Set Update has removed the primary SC or the strongest
serving cell SC354 as you step through the messages.
10. Check also the UL-DCCH Measurement Report at msg 029040
at 07:54:49.420. At that particular time, the SC 354 was the 2nd
strongest cell and it made sense that it should be removed.
11. Within a very short period of 5 ms, SC 354 was dropped and the
poor RF environment couldn’t cope with the changes. Therefore the call
dropped.
Let’s look at the 2nd call drop.

From the UMTS Active Nbor Sets Chart stateForm, the Detection Set is
much stronger. We can easily conclude that this is a missing neighbor case.
To see if these drop calls are HSPA or UMTS,

12. Drag the DownLink Measurements  3G UMTS  Event Data
 3G HSPA  Call  Uu_HSPACall_Dropped onto the same map.
Note that both calls were lying on top of each other and this concludes
that they are the same calls.
13. Display Data Testing  Application Measurements 
App_Throughput_DL on table and chart to see the exact value of the
throughput.
14. Synchronize PSB with your table and chart by clicking on msg
031948 at 07:56:58.750 RRCConnection Release.
The Downlink application throughput seems to be too dense

with a time binning of 1000ms. A slight modification of time
binning to 250ms will provide a better result on the table.
To learn more about all HSPA dropped calls, please see Appendix HSDPA.C.
Viewing Data on Workbooks

In some cases, the Analyzer table may not provide enough flexibility for viewing
data. Analyzer’s Workbook feature provides a more flexible method for detailed
analysis of trouble areas. This format allows data to be searched, sorted,
filtered, formatted, and printed through Microsoft Excel.
There are two ways to view data on workbooks:
 To view any attribute on a new workbook: Right-click on the

parameter of interest in the Workspace Browser and select Display on
Workbook.
 To view an attribute on a workbook that has already been opened:

Right-click on the parameter of interest in the Workspace Browser and
select Display on Workbook (active).
To display the downlink application throughput from

NENY_M01A_S05_K01_D01_07222008_001: Qualcomm UMTS Handset
(TM 6280) (3) - MS4 stream on a workbook:
1. Select Data Testing  Application Measurements 

App_Throughput_DL, then right-click and select Display on
Workbook.
The series data is displayed in Excel with time, latitude, and longitude.
2. Click on the Histogram Formatted Data tab and notice the range and
counts.
3. Click on the Statistics Formatted Data tab and notice the

automatically calculated statistics.
4. Close the workbook without saving changes.
Viewing Data on StateForms

Actix StateForms allow you to view multiple performance metrics
simultaneously. Used in conjunction with the replay tool, maps, tables, and
charts, you can quickly ascertain the values of several optimization parameters
for problem identification.
Using Preconfigured StateForms

A number of preconfigured HSDPA StateForms enable the user to quickly identify
and troubleshoot important network events. The preconfigured forms available
for HSDPA drive test data are:
 HSDPA PS Call Drop Event Chart
 HSDPA Radio Info Chart
 HSDPA Active Set
 HSDPA Radio Info Table
 HSDPA Low Raw Throughput Radio Info Chart
 HSDPA Low Raw Throughput Event Chart
 HSDPA Low Raw Throughput Radio Info Table
For example, to view the HSDPA Radio Info Chart stateform:
1. Right-click on the handset stream name and choose Display Form 

HSDPA Radio Info Chart. Forms can also be selected from the View
Forms option on the main menu.
2. In general, when selecting a form, make sure that the form that you
have selected applies to the type of data you want to analyze.
3. If the Stream Selector is not visible, right-click on the form and select
Stream Selector. The Stream Selector drop-down will appear. Use
the drop-down list to select the stream you wish to view data for. If you
are not seeing information in the forms, verify that the right data
stream is selected.
4. Forms with measurement views like the Radio Info Chart form or the
Radio Info Table form may be best viewed when docked close to the
replay tool at the side of the screen as seen in the screenshot below.
To dock a form on the left side of the workspace, bring up

the form and click the docking button (to the left of the
minimize button). Click the gray horizontal line at the top of
the form, drag over the bottom section of the Workspace
Browser, and release. Once docked, as in the view above, it
is possible to adjust the top and right-hand borders to allow
for more viewing space in the platform.
Forms with chart views like the HSDPA PS Call Drop Event Chart may be best
viewed when docked at the bottom of the screen as shown below.
To dock a form at the bottom of the workspace, bring up the form and use the
docking button (to the left of the minimize button) to dock it next the Workspace
Browser. Then, making sure that the right border of the form does not stretch
past the midpoint of the entire Analyzer viewing platform, drag the thin gray line
of the form to the bottom right side of the screen so that it is completely on the
left half of the viewing platform. Once docked as in the view above, you can
adjust the top border to allow for more viewing space in the platform.
Pre-configured forms can be edited to meet your individual analysis needs. The
following sections describe the modification of existing forms, and the creation of
new forms from scratch using the Stateforms Editor.
Viewing Custom Forms with the StateForms Editor

The StateForms Editor allows you to view custom forms, modify existing
forms, and build new forms from scratch. The components of the StateForms
Editor window are shown in the screenshot below.
StateForms
toolbar
Parameter
values
1. From the Tools menu, select StateForms Editor.
If the generic HSPA handset form does not launch, right-

click on the blank stateform box and select Open File.
Browse to the C:\Program
Files\Actix\Analyzer\Stateforms directory and open the
file called TrainingDL_UL_InfoStateForm.axl.
2. Once loaded, make sure a stream is selected in the StateForms stream

selection box. The selected stream must correspond to data currently
displayed on another Analyzer view (map, chart, table or message
browser).
If the stream selection box is not visible, right-click on the

stateform box and select Stream Selector. The stream
selection box will appear.
3. Select any point on a map, chart, or table and notice that the contents
of the form will update to reflect the state of the network at the point
you selected.
Verify that the stream selector in the StateForms window is

showing the same stream that you are trying to synch
with.
Modifying an Existing StateForm File

You can use an existing StateForms file as it is, or you can make modifications to
it.
The buttons on the StateForms tool bar are:
Delete, Cut, Copy, Paste, and Toggle Design Mode.
Select, Label, Attribute Value, Array Attribute Value, Time

Chart, Scan Chart, and Group Box.
Delete – Removes an object from the form. Using the delete key on your
keyboard will not work.
Cut – Removes an object from the form and puts it on the clipboard.
Copy – Copies an object to the clipboard. Select the object and click the
Copy button.
Paste – Pastes a copied of an object from the clipboard to the form.
Toggle Design Mode – Toggles between the design and view mode. To
exit the design mode and return to the view mode, click the Toggle Design
Mode button.
Select – Switches to select mode where it allows you to select an object

on the form.
Label – Creates a text box in a form. Click and drag a rectangle, then
type your text into the Caption field in the attribute window.
Attribute Value – Allows you to add an attribute to a form. Click and

drag a rectangle then choose an attribute from the list. The value of that
attribute will be displayed in the rectangle you defined.
Array Attribute Value – Allows you to add an array to a form. Click and
drag a rectangle to define a table. In the attribute window, specify the
number of rows and columns your table will have.
Time Chart – A Navigator Time chart helps to highlight problems or

important events within a logfile. An Attribute Time Chart provides more
information about a problem by highlighting how values change over time.
Scan Chart – A “Spectrum Analyzer”-like view; this chart is useful for

investigating array data from scanners and neighbor lists.
Group Box – Used to clarify which attributes on your form belong

together, click and drag to define a rectangle.
Suppose the HSDPA StateForm has almost everything you would like to see, but
that you are also interested in the Uu_HSDPA_NACK_Rate_without_DTX
attribute. To add Uu_HSDPA_NACK_Rate_without_DTX to the StateForms

display:
1. If you do not already have the StateForms file displayed, click Tools 
Display StateForms. Click Open File and choose the HSPA handset
file.
2. Click on the Toggle Design Mode button on the StateForms tool

bar.
3. The StateForms window now shows the design view:
4. Add the NACK Rate label inside the Downlink Info group box by
clicking the Label Button . Click and drag the rectangle.
5. Select the label object and change the Caption to NACK Rate.
6. To display the value for the NACK Rate without DTX, click the Attribute
Value button then click and drag a rectangle to the right of the NACK
Rate label.
7. Select the NACK Rate without DTX Attribute Value object and make
the following modifications:
 Attribute: 3G UMTS  DownLink Measurements  3G HSDPA 
Uu_HSDPA_NACK_Rate_without_DTX
8. The final result should look like:
Exercise: Creating Your Own StateForms

Several sample stateforms are provided by Actix. Custom forms can also be
designed from scratch. You can do this by creating a new StateForms file or by
adding a new sheet to a current file. In this exercise, we will create a new
stateform called Training HSDPA Task Analysis. The finished form will look
like this:
If you do not have the StateForms window open, click Tools  StateForms
Editor.
1. To start a new StateForms file, right-click inside the StateForms Editor

and select Design Mode. The stateforms sheet can now be edited and
objects can be added.
2. Add the Avg CQI label by clicking the Label Button . Click and drag
the rectangle.
3. Select the label object and make these modifications in the Attribute
Window:
 Caption: Avg CQI
 Font Size: 10
4. Repeat steps 2 and 3 for the following labels:

 Uu Call State
 Task ID
 Task Application Type
5. To display the value for Avg CQI, click the Attribute Value button then
click and drag a rectangle to the right of the Avg CQI label.
6. Select the Avg CQI Attribute Value object and make the following
modifications:

 Text Change Flag: True
 Font Auto Size: False
 Font Height: 10
7. Repeat steps 5 and 6 for the setting the attribute value for Uu Call
State, Task ID and Task Application Type.
8. To create the Attribute Bar for Avg CQI, click on the Attribute Bar
(same as the Attribute Value button) button then click and drag a
rectangle to the right of the Avg CQI attribute value object.
9. Select the Avg CQI Attribute Bar and make the following modifications
in the Attribute Window:
 Bar Color:
 Font Size: 6
10. To add the Group Box object, click on the Group Box button,
then click and drag a rectangle around all of the items on your form.
11. Select the Group Box object and make the following modification in
the Attribute Window:
 Caption: HSDPA Task Analysis
 Fore Color: Dark Blue
 Font Size: 13
 Default Font: False
 Font Bold: True
12. Click the Save As button and save the StateForms file in the
Stateforms directory and call it HSDPA Training StateForms.axw.
13. Return to the View Mode by clicking on the Toggle Design Mode
button.
14. Test your new StateForms file by displaying an attribute from the
NENY_M01A_S05_K01_D01_07222008_001: Qualcomm UMTS
Handset (TM 6280) (3) - MS4 handset stream on a map. Make sure
that the handset stream is selected in the StateForms stream selector
box. Click on any point on the map, and see the parameter values for
average CQI, call state, task ID and task application type appear on
your StateForm.
Performing Pre-configured HSDPA Analyses

Reporting HSDPA Network Performance
The reporting feature in Analyzer allows you to create high-level management
reports based on your data. Two different mechanisms exist for creating for
producing integrated, polished reports that can be used to analyze high-level
network statistics or communicate test results in a professional format:
 Application Packages are a technology-specific series of reports that are

installed automatically with every Analyzer installation. Application Packs
are typically used to obtain a high-level overview of call statistics. They
can be used when a professional, formatted output is required, but time
constraints do not allow for the creation of a custom template.
 Reports are user-definable formatted outputs that make use of Analyzer’s

integration with Microsoft Excel. Reports may be included with an Analyzer
installation (such as the UMTS/HSPA Training Materials), but are not
always included. Reports, unlike Application Packs, allow for formatted
outputs of multiple streams of data. Use Reports when generating outputs
for multiple streams of data and when you want to design a custom
formatted template from scratch.
This section describes the use of both reporting mechanisms, including running
Application Packs, running pre-defined Reports, and creating custom Reports.
Application Packages
Actix Analyzer contains Application Packages specific to each mobile technology
supported by the software. The Application Packs are a series of reports, each
focusing on a particular aspect of mobile network optimization. The Application
Packs currently available for HSPA users is the HSDPA Network Acceptance. It
contains the following reports or summaries:
 Radio Link Performance Metrics
 HS mobility or cell change overview, and
 Channel Usage reports
Running Application Packs

Once a data file is loaded, the Application Packages can be accessed in one of
two ways:
1. Through the Analysis menu on the main menu.

2. By right-clicking on the stream name in the Workspace Browser
The Application Packs require Analyzer to be pointing to a

valid cellrefs file in order to function properly.
Once you have selected one of the Application Packs from the menu, an
Application Pack window will appear. The window is divided into two panes.
The top panel is called the Statistics Explorer, and it contains a summary of
major call events and statistics for the selected stream. Information in the cell
explorer is organized by serving site and sector.
The bottom pane is called the Report Window and contains a list of available
reports associated with the selected Application Pack. Once executed, the results
of the reports can be saved, printed, and shown in their raw form in Microsoft
Excel.
Statistics Explorer
Report Window
Please check out the UMTS Section if you are interested to

check out the UMTS application packs.
Running a Pre-Defined Report

Since Application Packs are built into Analyzer, they may not exactly meet your
team’s reporting requirements. Additionally, App Packs can only be run on a
single stream of data. Analyzer Reports allow you to create custom reports using
Microsoft Excel, and those reports may include data from multiple streams.
Reports from multiple measurement sources allow you to compare data collected
simultaneously or look at your network before and after making a change.
To run the pre-defined report:
1. From the Analyzer main menu select Workbook  Open

Workbook/Report.
2. Navigate to C:\Program Files\Actix\Analyzer\Reports and Open the
report called Task details report.xls.
3. Analyzer prompts you to select a data stream to replace the ‘before’
stream. Select the Qualcomm UMTS Handset (TM 6280) (3) - MS4
stream from NENY_M01A_S05_K01_D01_07222008_001 and click
OK.
4. Analyzer will generate the report and launch Excel. Expect for this to
take a few moments. When this process is complete, click on the Report
tab in the Excel workbook and examine the formatted report.
5. The output of the report will look like this:
Modifying a Custom Report

Analyzer reports can be upgraded or modified at any time. To modify an
existing report:
1. Run the report through the Analyzer Workbook  Open Workbook

menu before making any modifications.
2. Make modifications to the existing report, including adding additional
parameters from the same data stream, adding the same parameters
from different data stream, or making cosmetic adjustments.
3. Save the file.
Making modifications to a report by opening the Excel file in

Windows will cause the Analyzer report to become corrupt.
Performing Custom Analysis in Analyzer

You can create a wide variety of customized analyses using Analyzer. You may
want to highlight potential voice or data problem areas, or test for common
symptoms of bad radio link quality for the purpose of speeding up the analysis of
data. Your customized analysis, called a query, can be saved in a Workspace and
reused for future drive data. The queries can be created, accessed, and edited in
the Workspace through the Analysis Manager.
About Queries
Queries are a means of searching and filtering data based on events and
thresholds you define. Queries operate on binned data and are written using
Boolean expressions and arithmetic operations containing data parameters from
one or more data streams. Analyzer supports six types of queries:
 Filter Analysis
 Binned Query Analysis
 Cross Tab Query Analysis
 Event Query
 Statistic Analysis
 Histogram Analysis
Analyzer supports the use of queries to assist in the detection, correction, and
presentation of network problems. In this section a number of these analyses
are used for examining various aspects of voice and data networks.
All custom analyses can be saved for future use through the Analysis Manager:
1. Select Tools  Analysis Manager or press Ctrl-A to start Analysis

Manager.
2. In the Analysis Manager, select the Existing Analysis tab.
3. Select any queries that you wish to save and click the Export button.
4. Browse to a folder that you wish to save your query in. Analyzer’s
default structure provides the C:\Program
Files\Actix\Analyzer\Queries folder for an easy place to store
queries.
5. Name the *.aqf file HSPA_Training_Class_Queries. All queries
created during training may be stored in the same file.
6. To import the queries into a new Analyzer session, go to the Existing
Analysis tab of the Analysis Manager and select the Import button.
Browse to find the *.aqf file in which you saved your queries.
Filter Analysis
Sometimes it is desirable to examine only a subset of the data points collected in
a logfile. We can use a filter to look only at those data points of interest to us.
A filter analysis tests data on a single criterion and displays the data only if the
criterion is met. This provides the engineer with a quick way to identify trouble
areas in which to focus optimization efforts.
Filter: Filtering by Task ID

In this example, we will filter all points based on task id. You can create a filter
query which highlights those points which have a Task_Id = 2 to identify all the
locations on the drive that has a task id of 2.
1. Right-click on the handset data stream MS4 under

NENY_M01A_S05_K01_D01_07222008_001 and select Filter 
Create a New Filter.
2. For the Filter Name, enter ‘Filter by Task ID’.
3. Use the attribute chooser to select Task_Id from the Data Testing
 Task Summary group.
It is important to use the Attribute Choose to choose your

attribute because Analyzer will automatically add the
state() function around your filter attribute, and “hold” it
across all other messages that do not contain that attribute.
4. Choose “=” for the operator

5. Enter ‘2’ for the Threshold.
State() function returns the

value of an attribute at the
current message position or, if
that has not been set, the
previous valid value.
6. Click OK to create the filter. Analyzer will automatically apply the filter
to any information already displayed in the workspace.
7. Confirm that the query was created by going to Tools  Analysis
Manager and clicking on the Existing Analyses tab. The Filter by
Task ID filter should be listed under the Filters category.
8. From the Existing Analyses tab, save the Filter by Task ID Filter to
the HSPA_Training_Class_Queries.aqf file by selecting it and using
the Export button. Multiple queries may be saved in one *.aqf file.
9. Display any attribute such as Uu_HSDPA_CQI_Average or
Uu_HSDPA_Throughput_MAC on the map. Notice that only points
with Task ID = 2 appear on the map. The filter has provided a quick way
of illuminating trouble spots and focusing optimization efforts.
Average CQI with Task ID = 2
10. Remove the filter from the map by right clicking on the handset
data stream under NENY_M01A_S05_K01_D01_07222008_002,
selecting Filter, and unchecking the Filter by Task ID filter. The filter
can be reapplied at any time using the same method.
Filter Analysis: Good RSSI 3 Good Cells (Pilot Pollution)

In UMTS/HSPA networks, areas with interference are typically identified as
those locations with strong RSSI coverage but experiencing too many good
quality signals. Filters may be combined using Boolean operations in
Analyzer to look at more than one condition at each data point. We will even
include an expression in a filter in the following example.
Create a new filter for pilot pollution that filters all data points where
Uu_Scan_RSSI is greater than or equal to -80 dBm and the difference
between the 1st and 3rd signal value is less than 3 dB for
CPICH_Scan_EcIo_Sortedby_EcIo[].
1. Key in Good RSSI and 3 good cells as your filter name.
2. Click on the New button to key in the following expression in the
Expression Builder:
Uu_Scan_RSSI>-80 AND (CPICH_Scan_EcIo_SortedBy_EcIo[0]-
CPICH_Scan_EcIo_SortedBy_EcIo[2])<3
3. Select Boolean as the format group.

4. Click on OK to exit the Expression Builder.
5. Select 1=True as the Boolean threshold. Click OK to exit from the Filter
Wizard.
6. Display the CPICH_Scan_RSCP_SortedBy_EcIo[0] on map.
7. Apply this filter to a scanner file (if it is not applied automatically after
you’ve created the filter) by right clicking on the Scanner - MS1 stream
under NENY_M01A_S05_K01_D01_07222008_002 file.
Attribute Spy
Attribute spy is a smart feature that allows you to display detailed information
on an attribute set at a message. Often you might not know what other
attributes are associate to the attribute you have just displayed on a map, for
example in our previous filter example,
CPICH_Scan_RSCP_SortedBy_EcIo[0]. To find out information at a
particular point selected of an attribute, and even if there are other associated
attributes, you can select the View  Display Attribute Spy from the main
menu.
You can narrow down your search or view by right-clicking on any listed
attributes on the AxaAOAttributeSpy Class window to select a pre-defined
filter.
Binned Query Analysis

The Binned Query allows you to define a new attribute based on existing
attributes, using functions and inequalities. The results of a binned query can be
displayed on a map, chart, table, or workbook.
Binned Query: High HSDPA Throughput

In this example, we will create a binned query to detect a high HSDPA
throughput and filter by task id = “2”.
Create the High HSDPA Throughput query using the Analysis Manager:

3. Enter ‘High HSDPA Throughput’ for the description.
4. In the Expression Builder, type in:
If(Uu_HSDPA_Throughput_MAC>750 AND state(Task_Id)== 2,
Uu_HSDPA_Throughput_MAC,NULL)
5. Set the Format to Kilobits per second. The easiest way to do this is to
select the Format drop down dialog and start typing Kilobits per
second in the window.
6. Click OK to create the query.

7. Click OK again to close the Analysis Manager.
The query will appear in the Queries group under every data stream in
the workspace. Under the handset stream, expand the Queries 
Binned Queries group.
8. Right-click on the High HSDPA Throughput binned query and choose

Display on Map to display the query results on a map.
9. To verify if the result is correct, display the Task_Id and
Uu_HSDPA_Throughput_MAC attributes in a table. Note that the map
only displays MAC throughputs higher than 750 kbits/s and where the
task id is 2.
Binned Query: CQI Average When 5 Codes (High Throughput)

In the following example, we will be looking at the correlation between the high
CQI average and the high number of codes. As we already known, the more
codes being assigned in HSDPA means higher throughput. The result of this
query will show us the average CQI value of maximum throughput.
To create the CQI Average When 5 Codes query using the Analysis Manager:

3. Enter ‘CQI Average When 5 Codes for the Description.
4. We want to display the CQI average that has maximum throughput. The
Expression should look like:
If (Uu_HSDPA_NumberOfCodes_Distribution_without_DTX[5] ==
100, state(Uu_HSDPA_CQI_Average),NULL)
5. In the format drop-down list, set the Format to CQI Average.
6. Click OK to finish creating the binned query. While you are still in the
Analysis Manager, take the opportunity to save the query to the
HSPA_Training_Class_Queries.aqf file.
7. Click OK to close the Analysis Manager.
To display this query, right-click on the handset data stream MS4 under
NENY_M01A_S05_K01_D01_07222008_002  Queries  Binned
Queries  CQI Average When 5 Codes and select Display on Map. Drag the
Task_Id on the same map to see which task IDs have the maximum throughput
and check out the CQI average.
Good average CQI 22.4 with Task ID = 7
Bad average CQI 1.3 with Task ID = 8
Why is there a big difference between the two task ids’ CQI
average? Further investigate this by using the map, table,
charts, PSB and other queries to find out more about the
radio condition.
To further investigate this, we will create an event query to find out the number
of codes distribution versus the average CQI values.
Event Queries Analysis

The Event Query allows you to extract key performance statistics for a user-
defined time or message window before or after a defined event like a handover
failure or dropped call. Viewing the window surrounding an event can provide
insights into whether a pattern exists among undesirable events, such as
multiple drops in an area due to low coverage.
Event Query: 5 Codes Usage vs. CQI

From the previous CQI Average When 5 Codes Binned Query, we’ve discovered 2
very different CQI average values on a maximum throughput. To further
investigate the record with low CQI average, we will create an Event Query to
return the average CQI with a 300ms window for the percentage of number of
codes allocated to the UE in the file. This will provide us the correct information
regarding the average CQI values.
2. Select the Event Query icon in the dialog and click on New. An
Event Query Wizard will appear.
3. For the name of the query, enter ‘5 codes usage vs. CQI’.
4. For the Trigger Selection, click on Edit button and type in
isvalid(Uu_HSDPA_NumberOfCodes_Distribution_without_DTX[5])
5. For the Window Range, choose Based on time and set the window to
300 milliseconds before the event and 0 milliseconds after the
event.
6. Click Next> to continue.

7. Click on the ‘New Dimension’ button. The query dimension allows you
to group and order your results using the attribute you select. In the
Expression Builder, key-in Percentage of 5 codes as the description.
8. Type in this expression:

mround(get(Uu_HSDPA_NumberOfCodes_Distribution_without_DTX, 5,
event_message()),10) and select Percentage as your format.
9. Click OK to close the expression builder.

10. To define a statistic to be displayed in the event window, click on
the New Statistic button to launch the Statistic window.
11. For the name, enter ‘Avg. CQI with 300ms’.
12. Choose the Choose Attribute button below the line that reads
“Enter the expression that should be calculated in your statistic”
to select the Uu_HSDPA_CQI_Average attribute.
13. In the Statistic window, select the method to calculate the
statistic. In this case, select Mean.
14. Click on the Edit button under Filter. The Expression Builder will
launch. Inside the top portion of the window, type in
isvalid(Uu_HSDPA_CQI_Average) and set the format group as CQI
Average.
15. Click OK to exit the Expression Builder.

query.
Displaying Event Queries

Once created, the event query can be displayed in the Statistics Explorer by
right-clicking on the query in the workspace, and selecting Display in Statistics
Explorer. The Statistics Explorer will launch and the results can be viewed,
sorted by the time of the event (in milliseconds). The queries can also be
displayed in Excel workbooks.
To display the query we’ve just created, right-clicking on the handset data
stream MS4 under NENY_M01A_S05_K01_D01_07222008_002  Queries
 Binned Queries  5 codes usage vs. CQI and display on Statistics
Explorer.
To look into each message, set binning mode to message from Tools 
Preferences  Binning Mode on the main menu.
Display Uu_HSDPA_NumberOfCodes_Distribution_without_DTX_5,
Task_Id, Uu_HSDPA_CQI_Average and Uu_HSDPA_UeFrameUsage
attributes on a table.
Last value of
Uu_HSDPA_NumberOfCodes
_Distribution_without_DTX_
5.
When CQI got lower, there was no occurence at all for

Uu_HSDPA_NumberOfCodes_Distribution_without_DTX_5 and the UE frame usage went down to 0.
Crosstab Query Analysis

The crosstab query is used to group data and display statistics for each group.
The groups can be sorted, and a query can contain several options for grouping
data.
Crosstab Query: Data Task Analysis

The crosstab query may be used to group HSPA data by serving site and sector
or even logfile and stream. This example will have the logfile and stream as the
grouping options, and the task type, task duration, average DL & UL throughput,
average HSDPA throughput, NACK rate and frame usage as the statistics to
display for each group. When the query is completed and the results are
displayed on the Statistics Explorer, it will look like this:
To Create this Crosstab Query:
2. Select the Crosstab Query icon and click on New.

3. Name the query “Data Task Analysis”.
4. Click on the ‘New Dimension’ button. The query dimension allows you
to group and order your results using the attribute you select. Use the
attribute chooser to select Independent  File Info  FileName
to add the file name as the first dimension (Description: Log File
Name). Use the attribute chooser again to select Independent File
Info  StreamLabelShort (Description: Stream Name) to add the
stream name as the second dimension.
5. Continue to add the followings to the ‘New Dimension’:
 Data Testing  Task Settings  Task_Id

(Description: Task ID)
 3G UMTS  Dedicated Radio Link  Uu_Call_State

(Description: Radio Bearer Dist.)
Global Filter
6. The query statistics are the results that you would like to include for
each dimension. The attributes that you choose will be displayed as the
columns in the statistics explorer. The statistics that we will include in
this query are Task Type, Task Duration, Task Failed?, Avg App
Throughput DL, Avg App Throughput UL, Avg HSDPA Throughput,
Avg HSDPA NACK Rate and Avg HSDPA Frame Usage. All of these
statistics will be available for the complete drive, for each serving site
and sector.
7. To create the statistic:
 Click on the New Statistic button to launch the Statistic Window.
 Enter the Statistic name.
 Use the attribute chooser to select the statistic of interest.
 Select the method to use to calculate the statistic.
 Click OK when finished with the Statistic Window.
Specific attributes relating to each statistic are included in the table below.
Statistic Expression Method Filter

Name
Task Type Task_Application_Type Mean Isvalid(Task_Application_Type)
Format: DataTestType Format : Boolean
Task Duration Task_Duration Last isvalid(Task_Duration)
Format: Time (seconds) Value Format : Boolean
Task Failed? Default(Event_Task_Fail,0) Last Isvalid(Event_Task_Fail) OR
Value isvalid(Event_Task_End)
Format : Boolean Format : Boolean
Avg. App App_Throughput_DL Mean
Throughput DL
Format : Kilobits per second
Avg. App App_Throughput_UL Mean

Throughput UL
Avg. HSDPA Uu_HSDPA_Throughput_MAC Mean

Throughput
Avg. HSDPA Uu_HSDPA_NACK_Rate_withou Mean

NACK Rate t_DTX
Format : Precision1 Percentage
Avg. HSDPA Uu_HSDPA_UeFrameUsage Mean

Frame Usage
Format : Percentage
8. Insert a Global Filter to filter out invalid task id: state(Task_Id)>0

query.
Be sure to save the Data Task Analysis Crosstab Query, in addition to the
other queries you’ve created, in your HSPA_Training_Class_Queries.aqf file.
We’ll be using this crosstab query in our next lesson on reports and repositories.
Display the Crosstab Query Results

Once created, the Crosstab Query results can be displayed in the Statistics
Explorer by right-clicking on the query in the workspace, and selecting Display
in Statistics Explorer. The Statistics Explorer will launch and the results can be
viewed, sorted by data rate. The queries can also be displayed in Excel
workbooks.
To display the crosstab query we’ve just created, right-clicking on the handset
data stream MS4 under NENY_M01A_S05_K01_D01_07222008_002 
Queries  Crosstab Queries  Task details and display on Statistics
Explorer.
 What are the throughput values of these data

activities?
 Which Task ID uses HSDPA and which task id doesn’t?
 What does the number in bracket next to the task ID

stand for? I.e. 1(406)?
 What causes the tasks to fail for example task id 1

and 5? Further investigate this using the UMTS Radio
Interface Protocol Stack Browser.
Filter the Crosstab Query Results
The Filter button on the Statistics Explorer may be used to quickly filter
query results in the Stats Explorer and in any other Analyzer view. In this case,
it may be useful to filter out the task failed data for further investigation.
1. Display the Task_Id, Uu_LowRawHSDPAThrougput, and

Uu_RRC_Dropped_Event from the
NENY_M01A_S05_K01_D01_07222008_002 - MS4 handset stream
on a map.
2. Open the UMTS Radio Interface PSB.
3. Tile the map, PSB and the Statistics Explorer vertically in the workspace
by selecting Window  Tile Horizontally.
4. In the Statistics Explorer, select the Row for task id = 1 and task id
= 5.
5. With the rows for task id 1 and 5 highlighted, press the Filter button
in the Statistics Explorer. Notice that only data points served by this
site remain in the Statistics Explorer and on the map.
What causes these tasks to fail?

Investigation for Task ID 1:
Display these additional attributes on table:

Event_Task_Start,
Application_RX_Bytes_Cummulative,
Event_Task _Fail and Uu_Call State
By looking at the PSB, we know that task id 1 failed very quickly where the UE
was reconfigured to Cell_FACH about 10 seconds after the Task starts. This
explains why there was very little data or almost no data exchanged between
the UE and the network.
The next step is to verify whether the Application in the UE has received any
data by using the "Application_Rx_Bytes_Cumulative" attribute. It clearly
indicates that the UE received no data throughout the Task ID 1.
As a conclusion, it does not seem to be a radio problem but probably a network

problem; no radio network optimization required.
Investigation for Task ID 5:
Display these attributes on map:

Uu_CallDropped_PS,
Uu_OutgoingCall_OK,
Uu_Call_State and
App_Throughput_DL
We can see that there is a radio drop (Uu_CallDropped_PS) right before the
Task failure.
If we zoom in to the Task failure area:
After the PS dropped call, a new PS call is established, but the Application
throughput stays "0". The UE fails to reconnect to the Server after the PS
dropped call. The Task times out and fails.
To remove filtering, click the Filter button again. The

filter will be unapplied from both the map and the Statistics
Explorer.
Histogram
HSDPA Throughput Histogram

The Uu_HSDPA_Throughput_MAC gives the DL throughput measured at the
HARQ entity level, excluding transport blocks received by the UE with CRC errors
and transport blocks received successfully multiple times. In this example, we
will make use of Analyzer’s Histogram to provide a throughput analysis.
1. Create a new Histogram to provide the

Uu_HSDPA_Throughput_MAC using the following parameters.
 Histogram Name: HSDPA Throughput
 Expression: Use the button to select

Uu_HSDPA_Throughput_MAC
 Type of Histogram: I want to specify ranges for my histogram

bars
 Format: Kilobits per second
2. Key in ”0” in the Minimum Value and check on Inclusive checkbox.

3. Key in ”50” in the Maximum Value and click on “Add” button to add
range.
4. Continue to set the following range:
 Set the Minimum Value to: 50 (Inclusive).
 Set the Maximum Value to: 0.5.
 Select ‘Add’.
 Repeat for each data range till 500 to be displayed in the

histogram.
 Set the Maximum Value to: 750.
 Set the Maximum Value to: 1000.
 Set the Minimum Value to: 1000 (Inclusive) to set value > 1000.
 Click OK to exit the Histogram Wizard.
Global Filter
5. Set a global filter for a valid task id: state(Task_Id)>0

6. Histogram query results can be found in the Queries  Histograms
node under each data stream in your workspace. Display HSDPA
Throughput results on a table or chart.
Remember to save this query in addition to the other queries you’ve created, in
your HSPA_Training_Class_Queries.aqf file, making sure to include all of the
previously created queries and filters.
Reporting Network Performance

Creating a Custom Report
Creating your own formatted report template is as easy as viewing the data you
require on a workbook, and then formatting the report page using Excel.
The objective of this section is to create a simple report or a single file report.
We will be using our previous Data Task Analysis crosstab to create a report.
To create the report above:
1. Ensure that the NENY_M01A_S05_K01_D01_07222008_001 file is

loaded into the Workspace.
2. Ensure that the modified version of Task details for report crosstab
query (Crosstab - Task details for report.aqf) is loaded.
3. Right-click on Queries  Crosstab Queries  Task details for
report and choose Display on Workbook.
Excel will launch and the Workbook will contain three sheets,
which can be accessed by clicking on the corresponding tab
at the bottom sheet window.
4. Click on any blank sheet in the workbook and rename the sheet
“Report”.
5. Rename another sheet and name it Histogram Data tab. Create the
following table for HSDPA Avg. Throughput vs. Percentage of
Tasks.
=(COUNTIF('CrossTab Formatted
Data'!I2:I1000,"<600")-COUNTIF('CrossTab
Formatted Data'!I2:I1000,"<500"))/Report!C5
6. Select the chart wizard icon from the top menu bar of Excel. The
chart wizard will open.
7. Select a simple column chart and follow the Wizard prompts and
instructions.
8. Click the Finish button in the chart wizard and a basic chart will be
created.
9. Cut and paste the new chart onto the “Report” sheet in the workbook
or choose to have the chart inserted as an object on the “Report”
sheet.
10. Create these statistics with the following formulae:
Statistic Name Expression
Number of Tasks =COUNTIF('CrossTab Formatted Data'!I2:I1000,">0")
Average HSDPA =AVERAGE('CrossTab Formatted Data'!I2:I1000)

Throughput
Minimum Avg. HSDPA =MIN('CrossTab Formatted Data'!I2:I1000)
Throughput
Maximum Avg. HSDPA =MAX('CrossTab Formatted Data'!I2:I1000)
Throughput
Avg. HSDPA Frame Usage =AVERAGE('CrossTab Formatted Data'!K2:K1000)
11. Add a title to the worksheet, position the histogram on the page,
format a table around the statistics and add any other desired
formatting (Number with 2 decimal places).
12. From the Excel main menu, select File  Save. Save the file in
C:\Program Files\Actix\Analyzer\Reports folder and name it
Task_Details_Report.
13. Close the Excel workbook.
Running Your Report with New Data:

1. Ensure that the NENY_M01A_S05_K01_D01_07222008_002 file is
loaded into the Workspace.
2. Select Workbook  Open Workbook/Report to open the
Task_Details_Report saved previously to the C:\Program
Files\Actix\Analyzer\Reports directory. A dialog will appear that
prompts you to select a data stream(s):
3. Select the MS4 handset stream under the

NENY_M01A_S05_K01_D01_07222008_002 file and click OK.
Watch the formatted report regenerate for the new data.
We will be making use of the same crosstab query and report for the next
Repository section. Make sure you save a copy of your work.
Repository
Repository provides a mechanism for handling large volumes of data, by loading
the results of queries into a relational database, which is implemented using
Microsoft® SQL Server™ 2005 Express Edition. Currently only crosstab, event
and binned queries are supported.
In the Actix terminology, databases are called repositories. It is based on a

template, which specifies how the results are to be structured into data sources
(called devices) and which attributes and queries are to be included in each
device. Repository stores the binned data for the attributes as described in
Repository Binned Data.
Some of the engineering process modules use Repository to store data but hide
the details of creating repositories and loading data into them behind the task
pages. However, Analyzer Classic includes features that advanced users can use
to create new repositories directly, and to open, close, and delete existing
repositories, and to load data into them.
When a repository is open, it is displayed in the Open Repositories folder in

the Attribute Explorer. Data is loaded into the devices based on the stream name
filter and stream type specified in the Define Devices page of the Repository
Template.
Repository Template Wizard

You use the Repository Template Wizard to create templates that can then be
used for creating repositories. The template defines the structure of the new
repository, what type of data it is to be used for, how that data is to be
organized, etc. You can also use the Repository Template Wizard to edit an
existing repository template.
You start the Repository Template wizard from the Template Manager, which
lists the templates that already exist and also enables you to delete unwanted
templates.
Before you start creating a template, make sure that all of the queries that you
want to use in the template are already available in the Analysis Manager,
otherwise you will not be able to add them to the template. If necessary, close
the Template Manager, add the queries, and then start again. In our case, we
will make use of the Task Detail Crosstab query that we’ve created earlier.
To open the Template Manager, select Repository  Template Manager

from the main menu.
Creating a New Template

To create a new template:
1. Open the Template Manager and then click New. This opens the
Repository Template wizard's Welcome page.
2. In our example, we take the following settings as below:
 Combine data into single logical device (default)
 Binning Method: Location (default)
 Attributes (default)
 Select the Crosstab Queries  Task detail for repository.afq

for your query
 No filter (default)
 Summary (default)
 Provide a useful Template Name such as “Task Details

Template”.
 Click on Finish to create the template.
Creating a Repository
To create a repository based on the Task Details Template:
1. Select Repository  Create Repository from the main menu.
2. Key in “Task Details Repository” in the Name column and select the
Task Details Template from the Template drop down menu.
3. Click on the Create & Open button to proceed.
4. Right-click on the Task detail repository and select Load Data to load
all the related logfiles to your repository. In our case we only have two
logfiles.
5. A File load results message box will appear acknowledging how many
files were successfully loaded.
Creating a Repository Report:

To create a repository report:
1. Right-click on the Open Repositories  Task details repository 

All  Queries  Crosstab Queries  Task details for report and
display it on Workbook.
2. A workbook in Excel with a report for all logfiles will be created where
the repository is loaded.
3. Rename your report to Task details report for Repository.
4. Remove all data in the Crosstab Data sheet before you save your
report.
Report open from Repository will be different from report

open directly from Analyzer. You will not get the same
result. It is advisable to save a separate copy of your
repository report in a separate file.
Display a Repository
1. Select Open Workbook/Report from main menu and select Task
Details Report for Repository. Click on Open to proceed. A Stream
Selection message box will appear.
2. Select the All stream from Task details repository.
Note that there are 19 tasks and you can double check the result on the
Crosstab Formatted Data sheet.
Repository Statistics Explorer

At any time during an analysis, you can look at the Repository Statistics
Explorer, which lets you visualize and analyze the data processed into a
Repository.
If the Repository Statistics Explorer is not open, you can

open it from the View menu or a right click menu
The Queries on the left are broken down by device node (the following example
shows three nodes: Log File Name, Stream Name and Task Id):
You can select the Date Range button to show a toolbar that allows you to filter
the data by log file name, stream name or task id.
From a top-level summary view, you can drill-down to more detailed views on
specific problem areas, or use a Filter button to look at a specific problem.
When specific problem areas have been isolated, the Repository Statistics
Explorer can load the raw performance messaging detail into Analyzer for
further analysis.
Selecting the Reports button opens a pane in the lower right which
displays all associated Excel worksheet reports.
Filtering Data in Repository Statistics Explorer
You can filter the data in a Repository Statistics Explorer by clicking on the Filter
button . For example, to obtain all data with average application throughput
DL < 450 Kilobits per second, you can:
1. Create a filter where Avg. App Throughput DL < 450 and click on
Add button to add the filter to the Current Filter List
2. Select the filter from the Current Filter List and click on Apply button
to apply filter
3. The Repository Statistics Explorer will be refreshed with the filtered

result.
You can copy the filtered data by clicking on the Copy button to copy, and
paste it to an Excel file or a text file.
Repository is very useful to generate reports on a large set of

logfiles. The workflow you should follow is as below:
1. Create queries using Analysis Manager.
2. Create a report in Analyzer.
3. Create a Repository Template containing all the queries required

by the report.
4. Create a Repository and load all the log files.
5. Run your report on the Repository.
Detail information regarding repositories can be found in the Help 

Contents  Working with Repositories in Analyzer Classic
from the main menu.
Actix Analyzer UMTS/HSPA Training Course April 2009 Appendix UMTS.A: Thresholds 165
Appendix UMTS.A: Thresholds
Modifying UMTS Thresholds

You can modify threshold values for event detection using the Tools  Display
Thresholds command. It is important to set your threshold before loading the
data because it will affect the analysis, diagnosis and display of data in Spotlight.
To modify the value, simply click on the associated number and type in the new
value.
UMTS > Event_Control
Uu_CallSetupFailure_Num_RRCConnReq
Used in the detection of call setup failures, this is a temporary value for the
N300 counter until the network setting is retrieved from the SysInfo message.
Uu_CallSetupFailure_TimeDelay
Used in the detection of call setup failures, this is a temporary value for the
T300 timer until the network setting is retrieved from the SysInfo message.
Uu_ReEstablisment_wait_timer
This threshold is the timer (ms) used to wait for an RRC establishment after the
RRC has been dropped.
Uu_Scan_UE_dB_Threshold
When comparing scanner data with UE data, if an SC from the scanner is not
seen by the UE for a period of time (specified by Uu_Scan_UE_Timer), and the
scanner SC is within this threshold’s dB of the Best Active Set member, an event
is triggered. Recommended default is 5 dB.
Uu_Scan_UE_Timer
When comparing scanner data with UE data, if an SC from the scanner is not
seen by the UE (within a dB threshold specified by Uu_Scan_UE_dB_Threshold)
for this time period, and the scanner SC is within this threshold’s dB of the Best
Active Set member, an event is triggered. Recommended default is 6000ms.
Uu_t309_wait_timer
This threshold is the timer (ms) used to represent the delay within which a UE
must establish a radio link after a Cell Order Charge from UTRAN command has
been sent.
Uu__wait_timer_Complete
This threshold is the timer (ms) used to wait for a state change complete
message, (i.e. Maximum time between Radio Bearer Setup – Radio Bearer Setup
Complete). Default is 8 sec, Max value is 15 sec. Note: If value is set to Zero
this feature is disable.
UMTS > Scan_coverage

Uu_Scan_PilotPollutionThreshold
In calculating Pilot Pollution, this threshold sets up the level of interference
required for pegging the events (based on scanner info). When 4 or more pilots
are above this threshold, it creates a pilot pollution event. Recommended value
is -15dB and the minimum and the maximum should be around -18 and -10 dB.
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.
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.
Uu_Scan_TooManyServers_Count_Threshold
The absolute number of pilots (with Ec/I0 within
Uu_Scan_TooManyServersTHreshold of the Ec/I0 of the best server) required to
trigger a “too many server” event (based on scanner info). Recommended value
is 3 and the minimum and the maximum should be between 2 and 4.
Uu_Scan_TooManyServers_RSCP_Threshold
The CPICH RSCP threshold above which a Uu_Scan_TooManyServers event may
be pegged. The default value is -104dBm, and a range of values between -90
and -110dBm is typical.
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.
UMTS > UE_Coverage

Uu_CoverageLimitedUE_TxPowerThreshold
Used in the Coverage Limited event. If UeTransmittedPower is greater than
Uu_CoverageLimitedUE_TxPowerThreshold AND CPICH_RSCP_in_ActiveSet is
less than Uu_Poor_RSCP_Threshold AND CPICH_EcNo_in_ActiveSet is less than
Uu_Poor_EcNoThreshold, then a Coverage Limited event will appear on the map.
Recommended value is 10 dBm. The minimum should not be lower than 0 and
the maximum should not be higher than 25 dBm.
Uu_EcNoInterferenceThreshold
This is used in conjunction with the RSCP Interference Threshold for the System
Interference event. If CPICH_RSCP_in_ActiveSet is greater than
Uu_RSCP_Interference_Threshold and CPICH_EcNo_In_ActiveSet is less than
Uu_EcNoInterferenceThreshold, then a System Interference event appears on
the map. Recommended value is -15 dB, and between -10 and -18 dBm.
Uu_HighUE_TxPower
This is used in the Poor Uplink Coverage event. If UeTransmittedPower is greater
than Uu_HighUE_TxPower AND CPICH_RSCP_in_ActiveSet is greater than
Uu_Poor_RSCP_Threshold AND CPICH_EcNo_in_ActiveSet is greater than
Uu_Poor_EcNoThreshold, then Poor Uplink Coverage will appear on the map.
Recommended value is 15 dBm. Values should lie between 0 and 25 dBm.
Uu_LowUE_TxPower
Used in the Poor Downlink Coverage event. If UeTransmittedPower is less than
Uu_LowUE_TxPower AND CPICH_RSCP_in_ActiveSet is less than
Uu_Poor_RSCP_Threshold AND CPICH_EcNo_in_ActiveSet is less than
Uu_PoorEcNoThreshold, then the Poor Downlink Coverage event will appear on
the map. Recommended value is -15 dBm, and between -30 and 0 dBm.
Uu_PilotPollutionThreshold
In calculating Pilot Pollution, this threshold sets up the level of interference
required for pegging the events. When 4 or more pilots are above this threshold,
it creates a Pilot Pollution event. Recommended value is -15 dB and should lie
between -18 and -10 dB.
Uu_Poor_EcNoThreshold
This is used in the Coverage Limited event. If CPICH_EcNo_in_ActiveSet is less
than Uu_PoorEcNOThreshold AND CPICH_RSCP_in_ActiveSet is less than
Uu_Poor_RSCP_Threshold AND Ue_TransmittedPower is greater than
Uu_CoverageLimitedUE_TxPowerThreshold, then a Coverage Limited event will
appear on the map. It is also used in the Poor Uplink and Downlink Coverage
event. Recommended value is -15 dB and should lie between -18 and -10 dB.
Uu_Poor_RSCP_Threshold
This is used in three different events. In the cases where
CPICH_RSCP_in_ActiveSet is lower than Uu_Poor_RSCP_Threshold, it will trigger
either a Coverage Limited event or a Poor Downlink Coverage event. In the case
where it is greater than Uu_Poor_RSCP_Threshold, it will trigger a Poor Uplink
Coverage event. Other conditions must be satisfied for these events to occur -
please note the other thresholds involved. Recommended value is -95 dBm and
should not be lower than -105 dBm.
Uu_RSCP_InterferenceThreshold
This is used for the System Interference event. If CPICH_RSCP_in_ActiveSet is
greater than this threshold and CPICH_EcNo_in_ActiveSet is less than
Uu_Poor_EcNoThreshold, then a System Interference event appears on the map.
Recommended value is -80 dBm and should lie between -90 and -60 dBm.
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.
Actix Analyzer UMTS/HSPA Training Course April 2009 Appendix UMTS.B:
Scanner-Based Network Rollout Analyses 168
Appendix UMTS.B:
Scanner-Based Network Rollout Analyses
Neighbor List Analysis

The Neighbor List Analysis provides an automated approach for generating
optimal neighbor lists and overcoming major service degrading problems such as
missing neighbors.
The key components of the neighbor list module are:
 Generation of recommendations for optimal neighbor list settings based

on UMTS/WCDMA scanner drive test data.
 Integration with Network Element Database to audit existing neighbor lists

and suggest changes, and to correlate non-unique measured data
attributes such as Scrambling Code with unique identifiers such as Sector
ID.
The Neighbor List Module implements the following algorithm:
 Ec/Io measurements below a noise floor are filtered out of the data set
before analysis.
 User definable binning is used to reduce the number of measurement

points in each bin to create one value per bin – optionally, no binning at
all can be applied and the analysis will run on the full data set.
 At each point along the drive test, a list of prospective neighbors is

accumulated. If a neighbor signal is within a user-definable threshold of
the best server in the active set, then it is considered as a potential
neighbor.
 Using the geographic information in the log file and the SC, the network
element database is searched to identify the Sector and Cell IDs of the
SC.
 Once all the bins in the log file have been compiled into the symmetrical
matrix, the results are compared against actual neighbor lists contained in
the network element database and the following are calculated:
 A list of sector IDs included in the matrix, but not the actual neighbor list.
 A list of sector IDs included in the actual list, but not the matrix.
In the snapshot above, Cell A is the best server by CPICH Ec/Io. Cells B and C
are within a user-specified threshold of Cell A's are Ec/Io, and so are counted as
potential neighbors of A. Cell D is not within the required threshold and so is not
counted as a prospective neighbor, nor is Cell E which did not have a
measurable signal contribution at this point in the drive test.
Here is a sample symmetric prospective neighbor array, using sector IDs A, B, C

and D:
A B C D
A N/A 10 2 15
B 10 N/A 40 0
C 2 40 N/A 12
D 15 0 12 N/A
The limitations of this algorithm are:
 Results are only produced in areas that have been tested, so the test
areas should be carefully considered before removing any Sectors from
the neighbor lists.
 Drive test do not necessarily emulate the radio environment encountered

by pedestrian and in-building users; however, walk tests and in-building
test may be included in the analysis as desired.
To access the Neighbour List Recommendations report
1. Ensure that a suitable UMTS scanner file and the corresponding

Network Element Database are loaded.
2. Configuration parameters for this analysis can be set by selecting Tools
 Preferences  WCDMA Neighbor List. The configuration
preferences include the reporting range, maximum list size, addition
and removal thresholds and minimum number of samples to include a

server in the analysis.
3. From the main menu, select Analysis  UMTS Accelerated Network
Rollout.
4. Double-click on the Neighbour List Recommendations report icon in
the lower pane of the Application Pack.
5. If there is no cell site database corresponding to the current dataset, or
if the current cell site database does not contain neighbor list
information, the report will work, though the results in the “Cell”,
“Site” and “Action” columns will be invalid.
CPICH Pollution Analysis

The CPICH or Pilot Pollution Analysis uses an Simulated Active Set to estimate
which pilots would have been actively demodulated by the UE, and then detects
other pilots above a user-definable threshold that cause excessive interference.
Please see the Simulated Active Set section for more details on how the Active
Set is estimated based on WCDMA scanner measurements.
The pilot pollution algorithm has these components:
 Ec/Io measurements below a noise floor are filtered out of the data set
prior to analysis.
 User-definable binning is used to reduce the number of measurement

points in each bin to create one value per bin – optionally, no binning at
all can be applied and the analysis will run on the full data set.
 At each point along the drive test, CPICH Ec/Io data for each Scrambling
Code is used to assign SCs to an Active Set or a Pollution Set (please see
the Simulated Active Set section for more details).
 The Pollution Set consists of all SCs that are not in the Active Set, and
have a CPICH Ec/Io within a user specified pollution threshold of the
strongest CPICH Ec/Io in the Active Set.
SC.
 A pollution array is created in memory which records the number of times

each sector ID is seen as a source of pilot pollution.
 All bins in the log file are then processed into the pollution matrix.
In the example below, Cells A, B and C are part of the Active Set, as determined
by the Simulated Active Set module. Cell D has a CPICH Ec/Io within a user-
specified pollution threshold of the Active Set’s best server Ec/Io, and so is
counted as a contributor to pilot pollution at this point in the drive test. Cell E
has a CPICH Ec/Io that is not within this threshold and so is not a pollution
source.
Shown below is a sample pollution array indicating the number of points at

which each sector caused pilot pollution for sector IDs A, B, C and D:
Sector ID Pollution Count

A 0
B 150
C 45
D 12
Results are presented in the Pilot Pollution Analysis application report. In

addition, Pilot Pollution may be geographically analyzed for each SC by accessing
the Pollution_for_SC attribute in the Attribute Explorer.
To access the Pilot Pollution Analysis report
1. Ensure that a suitable UMTS scanner file and corresponding Network

Element Database are loaded in the workspace.
2. From the main menu, select Analysis → UMTS Accelerated Network
Rollout.
3. Double-click on the Pilot Pollution Analysis report icon in the lower

pane of the Application Pack.
4. Enter the Pilot Pollution Margin (dB). This margin is used to
determine which pilots in the monitored set are within close proximity to
the strongest pilot in the active set.
Shown below, the Pilot Pollution Analysis Report indicates the worst interferers
sorted by Scrambling Code:
Handoff Analysis
The Handoff Analysis module uses the Simulated Active Set to determine the
handoff state at each point along a drive test. Statistics on handoff state may
then be calculated and presented in a report format. Excessive handoff state
reduces capacity and increases infrastructure costs for a given traffic level.
Please see the Simulated Active Set section for more details on how the Active
Set is estimated based on WCDMA scanner measurements.
The handoff state algorithm has the following components:
 The Active Set of pilots is determined using the Simulated Active Set
module.
SC.
 Handoff state is calculated by determining the configuration of the sectors

in the Active Set.
 All bins in the log file are then processed into the handoff state matrix.
Reports showing the percentage of handoff state for each sector and for the total
drive test may then be calculated.
The Handoff State Analysis examines Sector IDs involved in call at a given drive
test point and determines which of
the above states applies, based on
UMTS scanner data:
To access the Handoff Analysis

report
1. Ensure that a suitable UMTS

scanner file and the
corresponding Network
Element Database are
loaded.
2. From the main menu, select
Analysis → UMTS
Accelerated Network
Rollout.
3. Double-click on the
Handoff Analysis report
icon in the lower pane of
the Application Pack.
The populated Handoff State Analysis report will look like this:
Simulated Active Set

The CPICH Pollution Analysis and Handoff Analysis reports are both based on a
calculated Active Set, which is determined by the Simulated Active Set Module.
The Simulated Active Set module implements the 3GPP handoff algorithm and
uses scanner Ec/Io measurements in conjunction with user-specified 3GPP
handoff thresholds to emulate the Active Set at each point along a drive test.
These thresholds, available for modification by the user, are in the Tools 
Preferences dialog under WCDMA. The attributes available for modification are
listed in the figure below, as indicated in the 3GPP specifications:
As well as being used in reports, the Simulated Active set parameters are
specified as attributes for UMTS scanner data, and may be displayed on any
standard data view. Below is a sample set of scanner data for three individual
SCs with color and vertical lines indicating transitions of pilots into and out of the
Active Set.
Actix Analyzer UMTS/HSPA Training Course April 2009 Appendix UMTS.C: Event Definitions 177
Appendix UMTS.C: Event Definitions
Event Data
The following tables explain which triggering sequence is applied based on the
call events, RRC events, RAB events, coverage events and handoff events.
Call Events
Call Event Name Triggering Sequence
Uu_OutgoingCallOK  Uu_RRC_MsgType == RRC Connection Request (1) with
Uu_RRC_RRCConnectionRequest_establishmentCause
equals any of the following:
*RRC_OriginatingConversationalCall
*RRC_OriginatingStreamingCall
*RRC_OriginatingInteractiveCall
*RRC_OriginatingBackgroundCall
*RRC_OriginatingSubscribedTrafficCall
*RRC_Registration
(1)
 Uu_RRC_MsgType == RRC Connection Setup
 Uu_RRC_MsgType == RRC Connection Setup Complete
(1)
 GSM_Um_Msg_Type == MM CM Service Request

(*)
 GSM_Um_Msg_Type == MM Authentication Request
(*)
 GSM_Um_Msg_Type == MM Authentication Response
(*)
 Uu_RRC_MsgType == Security Mode Command
(*)
 Uu_RRC_MsgType == Security Mode Complete
(*)
 GSM_Um_Msg_Type == CC Setup
(*)
 GSM_Um_Msg_Type == CC Call Proceeding
(*)
 Uu_RRC_MsgType == Radio Bearer Setup
(*)
 Uu_RRC_MsgType == Radio Bearer Setup Complete
(*)
 GSM_Um_Msg_Type == CC Connect
 GSM_Um_Msg_Type == CC Alerting OR CC Connect
Acknowledge
(1)
At least one of those messages (RRC Connection Request,
Setup or Complete) needs to be present to initiate the call
setup
(*)
The messages with the symbol star are usually present
but not mandatory

Uu_IncomingCallOK  Uu_RRC_MsgType == PagingType1 with
Uu_RRC_PagingRecord_cn_Identity_pagingCause equals
any of the following:
*TerminatingConversationalCall
*TerminatingStreamingCall
*TerminatingInteractiveCall
*TerminatingBackgroundCall
 Uu_RRC_MsgType == RRC Connection Request (2) with
(2)
 Uu_RRC_MsgType == RRC Connection Setup Complete
(2)
 GSM_Um_Msg_Type == RR Paging response

(*)
 GSM_Um_Msg_Type == MM Authentication Request
(*)
 GSM_Um_Msg_Type == MM Authentication Response
(*)
 Uu_RRC_MsgType == Security Mode Command
(*)
 Uu_RRC_MsgType == Security Mode Complete
(*)
 GSM_Um_Msg_Type == CC Setup
 GSM_Um_Msg_Type == CC Call Proceeding (*)
(*)
 Uu_RRC_MsgType == Radio Bearer Setup
 Uu_RRC_MsgType == Radio Bearer Setup Complete (*)
(*)
 GSM_Um_Msg_Type == CC Connect
 GSM_Um_Msg_Type == CC Alerting OR CC Connect
Acknowledge
(2)
setup. Paging type 1 message is required for an incoming
call.
(1)
setup
(*)
The messages with the symbol star are usually present
but not mandatory

Uu_OutgoingCallSetupFail  Uu_RRC_MsgType == RRC Connection Request with
*RRC_Registration
 Then any of the following options:
*Uu_RRC_MsgType == RRC Connection Reject or
*Uu_RRC_MsgType == RRC Connection Setup
*Uu_RRC_MsgType == RRC Connection Release or
*Any BCCH messages during the call setup
Uu_IncomingCallSetupFail  Uu_RRC_MsgType == PagingType1 with

Uu_RRC_PagingRecord_cn_Identity_pagingCause equals
any of the following:
 Uu_RRC_MsgType == RRC Connection Request with
 Then any of the following options:
*Uu_RRC_MsgType == RRC Connection Reject or
*Uu_RRC_MsgType == RRC Connection Setup
*Uu_RRC_MsgType == RRC Connection Release or
*Any BCCH messages during the call setup
Uu_CallCompleted  When in Call (Outgoing Call Ok or Incoming Call Ok),

you get one of the following messages:
*GSM_Um_Msg_Type == CC Disconnect or
*GSM_Um_Msg_Type == CC Release Complete or
*GSM_Um_Msg_Type == CC Release
 And any of the above messages with a normal cause for
ending the call (CauseCodeCC is equal or less than 31)

Uu_CallDropped  When in Call (Outgoing Call Ok or Incoming Call Ok),
you get any of the following options:
 Any BCCH Message or
 Uu_RRC_MsgType == RRC Connection Release AND
Release Cause is not Normal or
 One of the following messages:
*(GSM_Um_Msg_Type == CC Disconnect) OR
*(GSM_Um_Msg_Type == CC Release Complete) OR
*(GSM_Um_Msg_Type == CC Release)
*AND any of the above messages with NOT a normal
cause for ending the call (CauseCodeCC is greater than
31)
Uu_LocationUpdateOK  GSM_Um_Msg_Type == MM Location Updating Request
 GSM_Um_Msg_Type == MM Location Updating Accept
Uu_LocationUpdateFail  GSM_Um_Msg_Type == MM Location Updating Request

 GSM_Um_Msg_Type == MM Location Updating Reject
RRC Events
RRC Event Name Triggering Sequence
Uu_OutgoingRRC_ConnectionOK  Uu_RRC_MsgType == RRC Connection Request
with
Uu_RRC_RRCConnectionRequest_establishment
Cause equals any of the following:
*RRC_Registration
Complete
Uu_IncomingRRC_ConnectionOK  Uu_RRC_MsgType == RRC Connection Request

with
Uu_RRC_RRCConnectionRequest_establishment
Cause equals any of the following:
Complete
RAB Events
RAB Event Name Triggering Sequence
Uu_RadioBearerSetupOK  RAB Setup message
 Followed by RAB Setup Complete
Uu_RadioBearerSetupFail  RAB Setup message

 Followed by RAB Setup Failure
Uu_RadioBearerReleaseOK  RAB Release message

 Followed by RAB Release Complete
Uu_RadioBearerReleaseFail  RAB Release message

 Followed by RAB Release Failure
Coverage Events
All Coverage Events which make use of thresholds may be customized by the
user in the Tools  Display Thresholds menu.
Coverage Event Name Triggering Condition(s)

Uu_PilotPollution  4 or more pilots detected above
Uu_PilotPollutionThreshold
Uu_TooManyServers  4 or more pilots are detected within X dB of the server,

threshold X is set by the user as
Uu_TooManyServersThreshold
Uu_System_Interference  CPICH_EcNo_in_ActiveSet <

Uu_EcNoInterferenceThreshold and
 CPICH_RSCP_in_ActiveSet >
Uu_RSCP_InterferenceThreshold
Uu_Coverage_Limited  CPICH_EcNo_in_ActiveSet < Uu_Poor_EcNoThreshold

and
 CPICH_RSCP_in_ActiveSet < Uu_Poor_RSCP_Threshold
and
 UeTransmittedPower >
Uu_CoverageLimitedUE_TxPowerThreshold
Uu_PoorDL_Coverage  CPICH_EcNo_in_ActiveSet < Uu_Poor_EcNo_Threshold

and
 CPICH_RSCP_in_ActiveSet < Uu_Poor_RSCP_Threshold
and
 UeTransmittedPower < Uu_LowUE_TxPower_Threhold
Coverage Event Name Triggering Condition(s)

Uu_PoorUL_Coverage  CPICH_EcNo_in_ActiveSet > Uu_Poor_EcNoThreshold
and
 CPICH_RSCP_in_ActiveSet > Uu_Poor_RSCP_Threshold
and
 UeTransmittedPower > Uu_HighUE_TxPower_Threshold
Uu_HandoverProblem  This event monitors the Ec/No of Monitored Set SCs with the
Ec/No of Active Set SCs in an 8 second window prior to each
dropped call. The Uu_HandoverProblem event is pegged
if the Monitored Set SCs are stronger than the Active Set
SCs more often than the Active Set SCs are stronger than
the Monited Set SCs.
Uu_MissingNeighbor  SC in Active Set after drop is not in Active Set before drop
and
 SC in Active Set after drop is not in Neighbor List before
drop
Handoff Events
Handoff Event Name Triggering Sequence
Uu_HandoffOK  ActiveSetUpdate message (Uu_RRC_MsgType ==
ActiveSetUpdate)
 ActiveSetUpdateComplete message
(Uu_RRC_MsgType == ActiveSetUpdateComplete)
Uu_HandoffFail  ActiveSetUpdate message (Uu_RRC_MsgType ==

ActiveSetUpdate)
 ActiveSetUpdateFailure message (Uu_RRC_MsgType
== ActiveSetUpdateFailure)
Actix Analyzer UMTS/HSPA Training Course April 2009 Appendix HSPA.A: Thresholds 183
Appendix HSPA.A: Thresholds
Modifying HSPA Thresholds

You can modify threshold values for event detection using the Tools  Display
Thresholds command. It is important to set your threshold before loading the
data because it will affect the analysis, diagnosis and display of data in Spotlight.
To modify the value, simply click on the associated number and type in the new
value.
HSDPA Thresholds
The following thresholds are available under the root of the HSDPA node:
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.
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.
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.
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 thresholds 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.
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
long as the duration of the Cell Change procedure. The default value is 1000 ms.
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 > HSDPA_NW_Acceptance Thresholds

These thresholds are used for the HSDPA Spotlight Reports:
HSDPA_NW_Acceptance_95_Percentile_CQI_Threshold
This threshold is used to indicate the lowest required CQI value at the 95
percentile for HSDPA Network acceptance.
HSDPA_NW_Acceptance_95_Percentile_EcIo_Threshold
This threshold is used to indicate the lowest required EcIo value at the 95
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 HSDPA Network acceptance (unit is kbit/sec).
HSDPA_NW_Acceptance_95_Percentile_RSCP_Threshold
This threshold is used to indicate the lowest required RSCP value at the 95
HSDPA_NW_Acceptance_95_Percentile_TCP_Throughput_Threshold
This threshold is used to indicate the lowest required TCP Throughput value at
the 95 percentile for HSDPA Network acceptance (unit is kbit/sec).
HSDPA_NW_Acceptance_EcIo_Threshold
This threshold is used in conjunction RSCP threshold, to setup thresholds above
which measurements from the UE as seen good for HSDPA Network acceptance.
HSDPA_NW_Acceptance_HSDPA_Drop_Rate
This threshold is used to indicate a pass threshold for the HSDPA call drop rate.
HSDPA_NW_Acceptance_HSDPA_Failure_Rate
This threshold is used to indicate a pass threshold for the HSDPA call setup
failure rate.
HSDPA_NW_Acceptance_HSDPA_Setup_Time
This threshold is used to indicate an average HSDPA call setup acceptance time.
HSDPA_NW_Acceptance_Overall_PS_Failure_Rate
This threshold is used to indicate a pass threshold for the overall PS call setup
failure rate (HSDPA and R99).
HSDPA_NW_Acceptance_PS_Drop_Rate
This threshold is used to indicate a pass threshold for the PS R99 call drop rate.
HSDPA_NW_Acceptance_RSCP_Threshold
This threshold is used in conjunction EcIo threshold, to setup thresholds above
which measurements from the UE a seen good for HSDPA Network acceptance.
Appendix HSDPA.B:
Data Settings for Neighbor Analysis
Default
Setting Description
value
Reporting Range 5 For each data point, the algorithm creates a
(dB) candidate list that includes those SCs within the
Reporting Range value of the strongest signal. For
example, if the strongest signal is -4 dBm, the
default value of 5 dB would include in the
candidate list all weaker SCs with signal strengths
down to -9 dBm.
Maximum Size 15 Defines the maximum number of candidates in
the candidate list.
Addition 1 Defines the percentage of samples that must be
Threshold (%) reached to trigger a cell being added as a
suggested neighbor. This is used to reduce the
effect of stray signals.
Removal 0.2 Defines the minimum percentage of samples that
Threshold (%) cells in the current neighbor list must achieve in
order to be recommended for retention in the list.
When the percentages of samples fall below this
threshold, cells will be recommended for removal
from the list.
Minimum 50 Only sectors which have been measured above
Samples the Ec/Io Threshold at least this many times will
be included in the analysis. Note that the
algorithm works off Binned data.
Maximum 5000 Defines the maximum line-of-sight distance in
Intersite meters between two cells for one to be considered
Distance for inclusion on the other's neighbor list. For rural
(meters) areas where the average intersite distance is
naturally greater than a dense urban
environment, use a higher value.
To disable this feature, set this value to 0.
Default
Setting Description
value
Angle to site 90 Defines the maximum angle between the edge of
threshold a cell's beam width and the data point, for that
(degrees) cell to be considered for inclusion in the serving
cell's neighbor list.
In this example, the beam width is shown as a

darker blue arc, and the angle to site threshold in
lighter blue arcs on either side. Acceptable data
points are within this threshold of the candidate
sector's beam width, and are also within the
Maximum Intersite Distance (the blue circle).
This threshold ensures that missing neighbors are
not suggested from reflected signals or back-
lobes, and also that only cells angled towards the
data point are suggested.
To disable this feature, set this value to 0.
Include existing Selected Select this option for the current neighbor list in
neighbors the cellrefs file to be considered for additions and
removals.
Only process Selected Select this option to analyze the neighbors of the
first best SC best cell only. De-select this option if you want to
analyze the neighbor list of all of the cells within
the reporting range.
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.
Actix Analyzer UMTS/HSPA Training Course April 2009 Appendix HSDPA.C: Events Diagnoses 188
Appendix HSDPA.C: Events Diagnoses
HSDPA Call Drops

A HSDPA call is a UMTS PS Call where the UE is in 'HSDPA' state. Therefore, the
trigger of HSDPA Drop call is the same as UMTS PS Drop call, but a HSDPA Drop
call is only pegged when the UE is in HSDPA state at the moment the call drops.
Usually, whenever the UE goes from HSDPA to Idle without a normal call
release, an HSDPA Drop Call event is detected. Recurring scenarios are:
 Terminal spontaneously (that is, not network-forced) dropping the radio

connection
 Network releasing the radio connection for causes other than user
inactivity or normal PDP Context deactivation
The following failure cases are supported:
 Deactivation of PDP Context due to abnormal situations

When the network (SGSN) releases the PDP context for abnormal
scenarios (this is detected via a Deactivation PDP Context Request
downlink message with SM cause different from 'Regular deactivation'.
 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 HSDPA is not supported (and the
network does not handle direct HSDPA to R99 transitions).
 RRC Connection Release

The network (RNC) releases the RRC Connection with a cause other than
'Normal' or 'User Inactivity'.
Low Throughput Issues

Low throughput conditions are detected when the user throughput exceeds a
certain threshold for a specified period of time. The analysis can be based on
Raw MAC-HS throughput or Net MAC-HS throughput.
You can configure the detection mechanism via the following HSDPA thresholds:
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.
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.
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.
For more information on Raw and Net MAC-HS Throughput, please see the online
help HSDPA Throughput KPIs.
KPI/attribute Related Threshold

Uu_LowRawHSDPAThroughput Uu_HSDPALowRawThrou_Thresh
Uu_LowNetHSDPAThroughput Uu_HSDPALowNetThrou_Thresh
Uu_HSCellNotBestPilot Uu_WinTimeHSnotBest
Low Tput KPI event (Used for Uu_HSDPALowCQI_Thresh
diagnostic purposes only)
Uu_HSDPAAvRegularSched_Thresh
Uu_HSDPAAvLowSched_Thresh
Uu_HSDPANet_To_L1_Throu_Thresh
Uu_HSDPAL1_To_Raw_Throu_Thresh
HSDPA Peak Tput (threshold SL_UMTS_DT_Spotlight_CriticalIssues_HSDPA
determines if this is a critical PeakTput
issue in the Summary
dashboard)
HSDPA Setup Failure rate HSDPA_NW_Acceptance_HSDPA_Failure_Rate
Overall PS Setup Failure rate HSDPA_NW_Acceptance_Overall_PS_Failure_R
ate
Average HSDPA Call Setup HSDPA_NW_Acceptance_HSDPA_Setup_Time
time
KPI/attribute Related Threshold

HSDPA Call Drop rate HSDPA_NW_Acceptance_HSDPA_Drop_Rate
Overall PS Call Drop rate HSDPA_NW_Acceptance_PS_Drop_Rate
Average EcIo HSDPA_NW_Acceptance_EcIo_Threshold
95 percentile MAC-HS Tput HSDPA_NW_Acceptance_95_Percentile_MACH
S_Throughput_Threshold
Average RSCP HSDPA_NW_Acceptance_RSCP_Threshold
95 percentile DL TCP Tput HSDPA_NW_Acceptance_95_Percentile_TCP_T
hroughput_Threshold
95 percentile CQI Tput HSDPA_NW_Acceptance_95_Percentile_CQI_T
hreshold
95 percentile EcIo Tput HSDPA_NW_Acceptance_95_Percentile_EcIo_T
hreshold
95 percentile RSCP Tput HSDPA_NW_Acceptance_95_Percentile_RSCP_
Threshold
The following failure cases are supported:
Low 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. The sub-cases below are self-
explanatory and are all mutually exclusive by definition:
- HS Direct Cell change ongoing
- Intra-F HS Cell Change via Idle mode
- Inter-F HS Cell Change via Idle mode
- HS to DCH_R99 direct transition
- HS to DCH_R99 transition via Idle mode
 Low CQI values

These are detected when the average CQI in the last 3 seconds is below
the user-specified threshold Uu_HSDPALowCQI_Thresh. 30 is the
maximum value a UE can report, and Uu_HSDPALowCQI_Thresh is a
number between 0 and 1. The threshold needs to be a factor ranging from
0 to 1 rather than an absolute CQI threshold between 0 and 30, because
under certain scenarios UEs might only report 15 as the maximum CQI.
Low CQI values are an indication of poor radio downlink conditions.
 Lack of data to transmit

This is detected when the Statistical Mode of the Instantaneous Raw Tput
in the last 3 seconds is 0.
This scenario typically occurs when there is no activity (data), but the
handset is kept in HSDPA mode by the network.
 Low scheduling rate

This is detected when in the last 3 seconds, the average scheduling rate
(from the instantaneous scheduling rate dataset Uu_HSDPA_FrameUsage)
is below the user-specified threshold Uu_HSDPAAvRegularSched_Thresh
(0..1).
This may occur when more than one HSDPA user is present in the HS
Serving Cell where the event is detected.
Low Net HS Throughput

A Low Net HS Throughput can usually be associated with an underlying Raw
Throughput scenario. However, there are some interesting cases where, despite
a good Raw Throughput, the Net Throughput does not reach satisfactory levels:
 Low Raw HS Throughput

If Low RAW Tput is also detected, the diagnostic simply reports that the
cause of Net Tput degradation is related to underlying Raw Tput. Check
through the Low Raw Throughput KPI list of occurrences for the right
event (timestamp would be the same as the Low Net Tput event.
However, some useful measurement data are included in the table for the
Net Tput KPI and this data might be sufficient).
 Low Raw HS Throughput not detected

All the cases listed for Raw Throughput is still valid. However the
diagnostic alerts you that the threshold for Low Raw Throughput event
detection might not be restrictive enough, which would explain why only
Net Throughput issues are detected.
If high levels of retransmission occur, the 'Further Information' section provides

additional information regarding Net throughput. Two scenarios are analyzed:
 High retransmissions due to packet incorrectly received in

Downlink
This is detected when:
Uu_HSDPA_Throughput_L1 < Uu_HSDPAL1_To_Raw_Throu_Thresh
Uu_HSDPA_PayloadRate_L1
For the definition of the different types of HSDPA throughput, please refer
to the online help section on HSDPA Throughput KPIs.
 High retransmissions due to poor Uplink quality conditions

This is detected when:
Uu_HSDPA_Throughput_MAC < Uu_HSDPANet_To_L1_Throu_Thresh
Uu_HSDPA_Throughput_L1
For the definition of the different types of HSDPA throughput, please refer
to the online help section on HSDPA Throughput KPIs.
Known Issues
If a particular KPI event (for example, HSDPA Call Drop) occurs very close to the
end of the logfile, the event can be missing from the diagnostic panel in the KPI
dashboard. However, the event will be flagged in both the initial dashboard (as
part of the % Call Drop Critical Issue if the relevant threshold condition is
fulfilled) and the top table of the KPI dashboard, leading to a discrepancy in the
number of events displayed.
Actix Analyzer UMTS/HSPA Training Course April 2009 Where to Get More Help? 193
Where to Get More Help?

Help File
Analyzer includes comprehensive online help, which can be accessed by clicking
on Help menu on the main menu. The primary help documentation can be found
under Help  Contents. You can look up information about a particular topic
either by choosing an item from the index or by entering keywords and
performing a search.
Specific information, like the definition of engineering parameters, can be

accessed by clicking on Help  Attribute Help. You can look up an item in the
alphabetized list, or you can open the Context Help window, then click on an
item in the Workspace.
MyActix and Support

For more information regarding Spotlight, logon to our Extranet: MyActix. After
you’ve register yourself, you can download the latest Actix Software, self-study
modules, and report any problem concerning Spotlight.

Analyzer Training UMTS HSPA Final20090430 B A4 NJR PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Analyzer Training UMTS HSPA Final20090430 B A4 NJR PDF

Încărcat de

Drepturi de autor:

Formate disponibile

UMTS/HSPA

WHAT CAN YOU DO WITH ANALYZER? ..................................................................8

UMTS SECTION ............................................................................................9

APPENDIX UMTS.A: THRESHOLDS ................................................................. 165

APPENDIX UMTS.B: SCANNER-BASED NETWORK ROLLOUT ANALYSES ...................... 168

APPENDIX UMTS.C: EVENT DEFINITIONS ......................................................... 177

APPENDIX HSPA.A: THRESHOLDS .................................................................. 183

APPENDIX HSDPA.B: DATA SETTINGS FOR NEIGHBOR ANALYSIS ............................ 186

APPENDIX HSDPA.C: EVENTS DIAGNOSES ....................................................... 188

WHERE TO GET MORE HELP? ........................................................................ 193

Scope of the course

Advanced users will be re-introduced to Analyzer features and to new network

Who Should Attend Analyzer Training?

 System Performance Engineers responsible for measuring and quantifying

 Engineers looking to further understand the application of drive test, call

 Experienced technicians involved in field optimization

 Anyone looking to maximize the return on their investment in Actix

 Familiarity with network infrastructure and operation of the air interface

 Access to Actix Analyzer software

 Basic computer literacy, including familiarity with Windows and MS Office

 A computer that should meet these minimal hardware requirements:

Processor 600 MHz Pentium III-compatible or faster processor; 1GHz or

Operating System Windows XP with Service Pack 2 or later.

Actix software runs on 64-bit Windows as a 32-bit application,

Memory 192 megabytes (MB) of RAM or more; 512 MB or more

Hard Disk Approximately 350 MB of available hard-disk space for the

Other Requirements Microsoft Internet Explorer 6.0 SP1 or later.

What can you do with Analyzer?

Getting started by configuring cell site info, set

Exploring workspace by examining the loaded data

Viewing Data by displaying in maps, charts, tables or

Performing UMTS/HSPA Performing customized UMTS/HSPA

Reporting Network Performance by

Saving your work or preferred layout using

Closing down Analyzer

Choosing an Engineering Process

1. Select Tools  Preferences from the main menu.

2. In the Change Preferences dialog box, locate CellRefs  File

Configuring Your Solution

 Setting up the map background and layers

 Changing the label properties

 Changing the display properties

 Showing lines to cell on the map, or

 Changing the size of cell site sectors.

Event Detection Thresholds and Data Aggregation

The above mentioned configurations can be found in the

Loading Data File

 UMTS Voice 1.dt1

 UMTS Data 1.SD5

 Agilent Scanner 1.mdb

Exploring the Workspace

 Downlink Measurements – This group contains Uu interface

 Pilot Measurements – This group contains signal strength

 Dedicated Radio Link – Once a call has been established, parameters

 Uu_RRC – Radio Resource Control is the protocol layer governing air

 Statistics Data – This group contains statistics calculated based on UMTS

 Vendor Specific – This group contains parameters unique to a specific

 Rake Finger Measurements (Qualcomm chipset handsets only) – This

1. Expand the UMTS Data 1 file tree in the Attribute Explorer.

Application Measurements – Find the instantaneous application layer

Protocol Measurements – This group contains throughput values for each

IP (Internet Protocol) provides a connectionless addressing scheme of

TCP (Transmission Control Protocol) establishes a virtual connection