Keysight Nemo

WindCatcher

User Guide
Notices
U.S.Government Rights Warranty
Copyright Notice
The Software is “commercial computer THE MATERIAL CONTAINED IN THIS
© Keysight Technologies Finland, Ltd. software,” as defined by Federal DOCUMENT IS PROVIDED “AS IS,” AND IS
2017 Acquisition Regulation (“FAR”) 2.101. SUBJECT TO BEING CHANGED,
No part of this manual may be reproduced Pursuant to FAR 12.212 and 27.405-3 WITHOUT NOTICE, IN FUTURE EDITIONS.
in any form or by any means (including and Department of Defense FAR FURTHER, TO THE MAXIMUM EXTENT
electronic storage and retrieval or Supplement (“DFARS”) 227.7202, the PERMITTED BY APPLICABLE LAW,
translation into a foreign language) U.S. government acquires commercial KEYSIGHT DISCLAIMS ALL WARRANTIES,
without prior agreement and written computer software under the same EITHER EXPRESS OR IMPLIED WITH
consent from Keysight Technologies, as terms by which the software is REGARD TO THIS MANUAL AND ANY
governed by United States and customarily provided to the public. INFORMATION CONTAINED HEREIN,
international copyright laws. Accordingly, Keysight provides the INCLUDING BUT NOT LIMITED TO THE
Software to U.S. government customers IMPLIED WARRANTIES OF
Manual Part Number under its standard commercial license, MERCHANTABILITY AND FITNESS FOR A
which is embodied in its End User PARTICULAR PURPOSE. KEYSIGHT
NTW00000A-90001 License Agreement (EULA), a copy of SHALL NOT BE LIABLE FOR ERRORS OR
which can be found at FOR INCIDENTAL OR CONSEQUENTIAL
Edition http://www.keysight.com/find/ DAMAGES IN CONNECTION WITH THE
Edition 1.00, July 2017 sweula. The license set forth in the FURNISHING, USE, OR PERFORMANCE
Documents Software Version EULA represents the exclusive authority OF THIS DOCUMENT OR ANY
by which the U.S. government may use, INFORMATION CONTAINED HEREIN.
Published by: modify, distribute, or disclose the SHOULD KEYSIGHT AND THE USER
Keysight Technologies Finland, Ltd. Software. The EULA and the license set HAVE A SEPARATE WRITTEN
Yrttipellontie 10 forth therein, does not require or AGREEMENT WITH WARRANTY TERMS
90230 Oulu permit, among other things, that COVERING THE MATERIAL IN THIS
Keysight: (1) Furnish technical DOCUMENT THAT CONFLICT WITH
Technology Licenses information related to commercial THESE TERMS, THE WARRANTY TERMS
computer software or commercial IN THE SEPARATE AGREEMENT WILL
The hardware and/or software described computer software documentation that CONTROL.
in this document are furnished under a is not customarily provided to the
license and may be used or copied only in public; or (2) Relinquish to, or otherwise
accordance with the terms of such license. provide, the government rights in
excess of these rights customarily
A CAUTION notice denotes a hazard. It
Declaration of Conformity provided to the public to use, modify,
calls attention to an operating procedure,
reproduce, release, perform, display, or
Declarations of Conformity for this product practice, or the like that, if not correctly
disclose commercial computer software
and for other Keysight products may be performed or adhered to, could result in
or commercial computer software
downloaded from the Web. Go to damage to the product or loss of
documentation. No additional
http://www.keysight.com/go/confo important data. Do not proceed beyond a
government requirements beyond those
CAUTION notice until the indicated
rmity set forth in the EULA shall apply, except
conditions are fully understood and met.
and click on “Declarations of Conformity.” to the extent that those terms, rights, or
You can then search by product number to licenses are explicitly required from all
find the latest Declaration of Conformity. providers of commercial computer
software pursuant to the FAR and the
DFARS and are set forth specifically in A WARNING notice denotes a hazard. It
writing elsewhere in the EULA. Keysight calls attention to an operating procedure,
shall be under no obligation to update, practice, or the like that, if not correctly
revise or otherwise modify the
performed or adhered to, could result in
Software. With respect to any technical
personal injury or death. Do not proceed
data as defined by FAR 2.101, beyond a WARNING notice until the
pursuant to FAR 12.211 and 27.404.2 indicated conditions are fully understood
and DFARS 227.7102, the U.S. and met.
government acquires no greater than
Limited Rights as defined in FAR 27.401
or DFAR 227.7103-5 (c), as applicable
in any technical data.

2
 Nemo WindCatcher User Guide

Is the software of your measurement products up-to-date?

Keysight will periodically release software updates to fix known defects and incorporate product
enhancements. To search for software updates for your product, go to the Keysight Software
Manager website at:
www.keysight.com/find/softwaremanager

3
 Table of Contents

1 Introducing Nemo WindCatcher .......................................................................................................... 8

2 Minimum System Requirements .......................................................................................................... 9
2.1 System requirements........................................................................................................... 9
2.2 Prerequisites ........................................................................................................................ 9
2.3 Installation ............................................................................................................................ 9
3 Using Nemo WindCatcher – Basics ..................................................................................................10
3.1 Configure Nemo WindCatcher .......................................................................................... 10
3.1.1 Setting the processing defaults ............................................................................. 10
3.2 Workspace.......................................................................................................................... 24
3.2.1 Save the workspace ............................................................................................... 25
3.2.2 Open a workspace .................................................................................................. 26
3.3 Cell sites ............................................................................................................................. 26
3.3.1 Creation of the cell sites......................................................................................... 26
3.3.2 Default cell sites ..................................................................................................... 30
3.3.3 Sector display ......................................................................................................... 30
3.3.4 Remove cell sites.................................................................................................... 32
3.3.5 Discovered LTE and UMTS sites ............................................................................ 32
3.4 Create Geoset .................................................................................................................... 33
3.4.1 Background ............................................................................................................ 35
3.5 Bin style .............................................................................................................................. 36
3.6 Event settings..................................................................................................................... 37
3.7 Threshold settings ............................................................................................................. 39
3.7.1 Exporting thresholds and events ............................................................................ 41
3.8 Dataset creation and management .................................................................................. 41
3.8.1 Create new dataset ................................................................................................ 41
3.8.2 Open existing dataset............................................................................................. 42
3.8.3 Close dataset.......................................................................................................... 43
3.8.4 Merge datasets....................................................................................................... 43
3.8.5 Merge devices ........................................................................................................ 43
4 User-Interface Overview .......................................................................................................................45
4.1 Docked windows ................................................................................................................ 45
4.1.1 Windows view ........................................................................................................ 46
4.1.2 Legend window ...................................................................................................... 47
4.1.3 Failure Analysis Dashboard .................................................................................... 48
4.2 Tabbed windows ................................................................................................................ 55
4.3 Multiple maps .................................................................................................................... 55

4
 Nemo WindCatcher User Guide

4.4 Synchronization ................................................................................................................. 57

4.5 Metric and event plots ....................................................................................................... 57
4.6 Time series plots ................................................................................................................ 61
4.7 Tables ................................................................................................................................. 64
4.8 Printing / plotting .............................................................................................................. 64
4.9 PDF/CDF charts ................................................................................................................. 67
4.10 X-Y chart ............................................................................................................................ 68
5 User Queries ..............................................................................................................................................69
5.1 General usage .................................................................................................................... 70
5.2 Create a custom legend .................................................................................................... 71
5.3 Create a custom field......................................................................................................... 72
5.4 Creating user-defined metrics .......................................................................................... 72
5.4.1 Define the metric item............................................................................................ 72
5.4.2 Define the conditions ............................................................................................. 73
5.5 Creating user-defined report ............................................................................................ 73
5.5.1 Define the report item ............................................................................................ 73
5.5.2 Define the conditions ............................................................................................. 74
5.6 User queries in the parameter tree ................................................................................... 74
5.7 User Queries in Batch Print ............................................................................................... 76
6 Using Nemo WindCatcher – Advanced ...........................................................................................77
6.1 In-Building Profiler ............................................................................................................. 77
6.2 Batch printing..................................................................................................................... 78
6.3 Metrics/Events Offset ........................................................................................................ 81
6.3.1 Metrics Offset ......................................................................................................... 81
6.3.2 Events Offset .......................................................................................................... 82
6.4 Layer control ...................................................................................................................... 85
6.4.1 Metrics.................................................................................................................... 85
6.4.2 Selection................................................................................................................. 86
6.4.3 View ........................................................................................................................ 87
6.4.4 Editing .................................................................................................................... 87
6.4.5 Background maps .................................................................................................. 88
6.5 Multiple phones ................................................................................................................. 88
6.6 On-screen menus............................................................................................................... 90
6.7 Raster map sites to route .................................................................................................. 92
6.8 Polygon creation ................................................................................................................ 93
6.8.1 Polygon/boundary import ...................................................................................... 95
6.8.2 User Query for Polygon Filtering ............................................................................ 97
6.8.3 Report generation .................................................................................................. 98
6.9 Exporting reports and maps .............................................................................................. 98
6.10 Exporting tables ................................................................................................................. 99

5
 Nemo WindCatcher User Guide

6.11 Elevation profile ............................................................................................................... 100

6.12 Attribute Manager............................................................................................................ 101
6.13 Event diagram .................................................................................................................. 104
6.14 Root cause for Event Analysis ......................................................................................... 107
6.15 Processing VoLTE data .................................................................................................... 109
6.15.1 Saving processing default .................................................................................... 110
6.15.2 Create new dataset .............................................................................................. 111
6.15.3 Associating DRM file with PCAP file ..................................................................... 112
6.16 Exploring VoLTE data ....................................................................................................... 115
6.16.1 Message window .................................................................................................. 115
6.16.2 Event window ....................................................................................................... 115
6.16.3 Custom report generation .................................................................................... 116
6.16.4 Running the VoLTE acceptance report ................................................................. 117
7 Analysis Features .................................................................................................................................. 119
7.1 Event analysis................................................................................................................... 119
7.2 Delta plots ........................................................................................................................ 121
7.2.1 Dataset delta ........................................................................................................ 123
7.2.2 Handset delta ....................................................................................................... 123
7.3 Link to bin ......................................................................................................................... 123
7.4 Geo/distance binning ...................................................................................................... 125
7.5 Replay ............................................................................................................................... 125
7.5.1 Replay option ....................................................................................................... 126
7.6 Neighbor list analysis....................................................................................................... 127
7.7 RF analysis........................................................................................................................ 128
7.8 Reports ............................................................................................................................. 129
7.8.1 Predefined report templates ................................................................................ 129
7.8.2 Zoom option in reports ......................................................................................... 131
7.8.3 Report builder....................................................................................................... 132
8 Project Manager.................................................................................................................................... 140
8.1 Introduction to Project Manager Module ....................................................................... 140
8.2 iBwave cell sites............................................................................................................... 143
8.3 Cell site alignment ........................................................................................................... 145
9 Client Server ........................................................................................................................................... 146
9.1 Overview ........................................................................................................................... 146
9.2 Setting-up the server ...................................................................................................... 146
9.2.1 Creating the folder structure ................................................................................ 147
9.2.2 Enabling the Client Server functionality ............................................................... 147
9.3 Client – Project Repository .............................................................................................. 149
9.3.1 Overview ............................................................................................................... 149
9.3.2 Connecting to the server ...................................................................................... 149

6
 Nemo WindCatcher User Guide

9.3.3 Data Upload Manager .......................................................................................... 150

9.3.4 E-mail notification ................................................................................................ 151
9.4 FTP Server Upload ........................................................................................................... 152
9.5 Deleting files .................................................................................................................... 152
10 Appendix A: Supported Drive Test Formats ................................................................................ 154
11 Appendix B: LTE Metrics .................................................................................................................... 155
12 Appendix C: GSM Metrics .................................................................................................................. 173
13 Appendix D: UMTS Metrics ............................................................................................................... 178
14 Appendix E: CDMA Metrics ............................................................................................................... 185
15 Appendix F: WiMAX Metrics ............................................................................................................. 208
16 Appendix G: Event Definitions .......................................................................................................... 215
17 Appendix H: VoLTE Metrics ............................................................................................................... 221
18 Appendix I: LTE-Adv Metrics ............................................................................................................ 224
19 Appendix J: LTE-Adv Events ............................................................................................................. 230
20 Technical Support ................................................................................................................................ 231
20.1 Nemo Support Portal ....................................................................................................... 231
20.2 Phone and email support ................................................................................................ 231
20.3 Locations for Keysight Technologies .............................................................................. 232

7
 Nemo WindCatcher User Guide

1 Introducing Nemo WindCatcher

Nemo WindCatcher is a PC-based, drive-test post-processing tool developed by Keysight
Technologies, Inc. The product provides a complete solution to post-process, analyze and report
data, and brings several advanced analysis and productivity features and functionalities to the
engineer, packaged in a user-interface that is both powerful and intuitive.
Multiple data files from multiple phones, multiple frequencies and multiple sources (including up
link) may be processed together in one step and saved as datasets to be recalled later. This adds
great efficiency because all data files need only be processed once. Tremendous efficiency gains
are also achieved with value-added productivity features such as batch printing (which includes PN
and PCI batch printing).
Nemo WindCatcher provides multiple views like maps, charts, tables, phone data, event and
message browsers for detailed drill-down analysis of problem areas. These views are fully
synchronized to maximize the effectiveness and coherency of the data presented. Complementing
these views are additional, advanced features like automated event analysis, problem area
identification queries, delta plots, PN and PCI analysis that greatly reduce the time taken to identify
and analyze problem areas and events.
The functionality of Nemo WindCatcher is designed to maximize the productivity and efficiency of
engineers in their day-to-day work of evaluating drive test data, isolating problems and
recommending solutions to network problems. Nemo WindCatcher provides a comprehensive list
of all problems seen on the drive. Intelligent algorithms and innovative metrics are applied to these
problems to arrive at suggested root causes and ideas for possible fixes.
This user manual provides detailed information on how to use this product. The simple yet
powerful user interface combined with the strong engineering focus of the product should make
learning Nemo WindCatcher a quick, fun and easy process for engineers and managers at all
levels.

8
 Nemo WindCatcher User Guide

2 Minimum System Requirements

2.1 System requirements

Nemo WindCatcher can run on any PC with Microsoft Windows 7, Windows 8, Windows 8.1 and
Windows 10 operating system. The following are the minimum PC hardware requirements for
Nemo WindCatcher to operate optimally:
• Operating System: Windows 7, Widows 8, Windows 8.1, Windows 10
• Office: Microsoft Office 2003/2007/2010/2013
• RAM: 4 GB
• Processor Speed: 2.5 GHz
• Processor: i5 or i7 Core

2.2 Prerequisites
For the users using the Nemo License Setup with Sentinel HL dongle and having older than 3.5.6.0
release, the license file (c2v) must be updated to be able to use Nemo WindCatcher release 3.5.6.0
and newer. Contact Nemo Customer Support.

1) Install the Microsoft Visual Studio 2008 C++ Redistributable from the following link:
https://www.microsoft.com/en-us/download/details.aspx?id=29

2) Install the Microsoft Visual Studio 2012 C++ Redistributable from the following link:
https://www.microsoft.com/en-us/download/details.aspx?id=30679

2.3 Installation
All windows applications must be closed prior to WindCatcher installation. If stand-alone license
(Dongle) is in use, the user should unplug the dongle before starting the installation.

Download the WindCatcher.exe file and run it to begin the installation. Follow installation steps
and click Finish when complete.

If a previous version of Nemo WindCatcher is already installed on the computer, then while
installing the new version a pop-up window will appear to uninstall the existing version.

9
 Nemo WindCatcher User Guide

3 Using Nemo WindCatcher – Basics

The basic steps to use Nemo WindCatcher are as follows:
Configure Nemo WindCatcher settings – this step need only be performed once, and only needs to
be revisited if the usually rare situations when the configuration needs to be changed.
Create datasets out of drive test data to be processed. A dataset is a collection of data files that
form a single logical drive for analysis. A single dataset may consist of multiple phones, devices,
and/or multiple frequencies.
Plot metrics and charts to view and analyze the datasets.
Use in-built, powerful analysis features to greatly improve the efficiency and increase the quality of
the analysis.
Print maps and generate/export reports for offline analysis and documentation purposes.
These topics are discussed below. The analysis features are discussed separately under the section
on Analysis Features.

3.1 Configure Nemo WindCatcher

Nemo WindCatcher provides the flexibility to set a default configuration for data processing and
display. The default configuration includes Processing Defaults, Background Defaults, Symbol and
Thresholds.

The default configuration, once set, will be saved until it is explicitly changed by the
user.

3.1.1 Setting the processing defaults

From the Home menu, select Processing Defaults.

10
 Nemo WindCatcher User Guide

The following screen will be displayed:

Each of the options in the left hand side of the Processing Default Configuration window is
discussed in the following sub-sections.

3.1.1.1 Processing
Under the Processing tab the following options are present:
Average Type

There is a tremendous amount of data that gets generated by the phone in a serial, asynchronous
manner. It is therefore necessary to bin the data in order to display data efficiently. This field sets
the binning interval over which all data is averaged. During the process of Appending data to a
saved dataset, users should only append a binned mode to dataset with same binned mode.

• Time/Distance/Geo Binning
Data can be averaged by time, distance or Area (Geo). To change the size and/or type of bins,
make sure the desired averaging type is selected and change the values for Time (second) and
Distance (Meter) in the user entry box appropriately.

11
Nemo WindCatcher User Guide

The time interval can be set only in discrete units and the minimum interval is 1 second. The
distance interval can also be set only in discrete units, and the minimum interval is 5 meters.

The Layer 3 and Log data in the message browser will never be binned no matter what
the selection since each individual message must be displayed as their occur.

Import Log Data

Layer 3 and Log data can be imported in the following two ways:
• By checking the Import Layer3 Data and/or Import Log Data options and leaving the
event filter option unchecked, all Layer 3 and Log messages can be viewed in the
message browser. If this data is not desired than it can be deselected.
• By checking the Import Layer3 Data and/or Import Log Data options and the event filter
option. In this option only log and Layer 3 data before and after failure events in a user
defined window will be displayed in the event browser.

The processing will be significantly faster if the event filter for Log data is used to filter
the data or if the Log data option is not checked.

Import command/Response Data, selecting this function will allow the import of diagnostic
response messages during processing.
The Apply Log Message filter allows the user to apply a filter to the log messages that will be
displayed in the message browser. The specific messages to filter and display can be selected
using the Select Log Messages button.

By selecting this option the processing time will get extended, in order to get warning
message regarding the extended processing time you can select the Enable warning
Message for import log data option.

Packet Trace Data

Packet trace data can be imported in the following two ways:
• By checking the Import packet trace Data PCAP Log messages can be viewed in the
message browser. If this data is not desired than it can be deselected.
• By checking the Enable Packet Trace Analysis, all of PCAP related Metrics & Event will be
enabled & available for analysis.

To import VoLTE data from the data files we need to check Packet trace option along
with VoLTE option as well. Using the drop down box specific protocols can be selected
but that will increase the size of the database and slow down the processing. e.g. RTP,
RTCP, SIP etc.

12
Nemo WindCatcher User Guide

13
Nemo WindCatcher User Guide

Once the above mentioned option is checked before processing, following ‘Packet Trace’
and ‘VoLTE’ Metric set will be available to user under map tab and in the parameter tree.

Merge Phone and Data Device

This option is checked to ensure that the Trace and Dialup devices in JDSU AOD format are
merged into a single device.
Settings
• Merge Devices by Label- Enables Nemo WindCatcher to merge devices across files with
the device label, Devices can be merged by complete labels or by user defined, partial
label.

If not selected, devices across the files with the same label will not be merged.
• Remember previous settings in data table- It will populate the same set of parameters
selected in the Datatable view each time when a dataset is open and the user selects view
Datatable.
• Enhanced GPS Search- This feature can be utilized if any enhanced GPS data was
recorded during data collection.
• Show progress bar- The user can enable and disable the visibility of the progress bar
window.

14
 Nemo WindCatcher User Guide

Database Settings
Nemo Windcatcher has support for MS Access and for SQLite database tpes. The user may define
a default ‘Database Location’ to automatically save generated database files

3.1.1.2 Processing offset

Time Offset
The option enables the processing of data in-line with the time-zone that the data was collected
in. The data is processed with the GMT time zone when this option is not selected. User can apply
custom time offset by entering any desired timing.
UETR Offset
The option allows user to process Ericsson call trace data with the exact time offset defined in
‘hours, minutes, and seconds’ along with the drive test data.
PCAP Offset
The option allows user to add a time offset for PCAP file if the timestamps on PCAP file is not
aligned with drive test file.

15
 Nemo WindCatcher User Guide

3.1.1.3 Interface

Default Display View

This setting will allow the user to view the map or summary dashboard as the default view when
opening any new data in Nemo WindCatcher. The user may access to Summary view using the
options below:
• Set it as a default view when any new data is opened in Nemo WindCatcher

16
Nemo WindCatcher User Guide

• Open up the view after data is opened in Nemo WindCatcher through ViewsNew
Summary View menu:

This option allows a consolidated view of the data processed classified as shown below.
The following metric menus are available per device selection.
• Coverage
• Accessibility
• Retainability
• Mobility
• Integrity
• Availability

17
Nemo WindCatcher User Guide

Map co-ordinate System/ Distance Unit

The map unit provides the option to select Mile or Kilometer in addition to selection of co-ordinate
system for display in different views.
Map Offset for Multiple Devices/Frequencies
This option sets the offset between maps for different phones. To change the offset distance, enter
the Latitude and Longitude Offset. If the offset is not desired, then unselect the checkbox labeled
Enable Map Offset in Degrees.
• Enable In-Building Device Offset option allows user to enable offset between multiple
devices for in-building data.
• Enable Navigation Data Correction selection can be used to apply a fixed latitude and
longitude offset to the driven route.
Link to bin settings
• This Maximum Sector Coverage Distance field sets the coverage range for individual
sectors.
• Enable Link to Bin Label option allows user to turn on or off the link to bin labels on map
interface.
Drive Route Display
• Hide Bins with no GPS: This option will allow the user to hide bins that display no lat/long
values
• Hide Bins with no data: If a metric is plotted and the driven bin has no value available for
that bin then the bin would be hidden. If the option is not selected the bins without the
metric value will come with gray color.
• dB offset for receivers: This settings allows the user to apply the 6dB (by default) offset for
receiver devices
• Direction Indicator: This option allows user to user to hide or display the drive direction
indicator.
• Move Drive Route Over Cell site: This option allows the user to bring the drive route layer
above the cell site layer.
• Move Drive Route Over Event Layer: This option allows the user to move the drive route
layer above the event layer.
Legends Display
Show percentage in legends selection allows the user to view the percentage distribution for
metrics plotted in addition to the bin distribution.

18
Nemo WindCatcher User Guide

Layer Control
This setting allows user to select the number of mtric layers available in the Map View. Maximum
number of the layers is 10 and the default value is 5.

Cell Site Optimization

Whit this setting user can set the limits to display/not to display the cell sites and sectors on the
map plot. There are separate settings for the sites and for the sectors/cells. The limit to set is
based on the width of the visible area on the map. Before the sectors get visible, the cell sites are
displayed as dots/small circles on the map plot view.

19
 Nemo WindCatcher User Guide

3.1.1.4 RF configuration

WCDMA Scanner Settings

This option enables selection of minimum values for Received Power before processing the data to
filter out any PSC’s below that value.
WCDMA Call Block versus Drop Trigger
This option enables the user to select the call block trigger message. This is set to ‘Alerting CC
message’ as a default.
Avg Method in Bin
This option enables selection of the value displayed in a bin i.e. average over all the values in a bin
or the best values in a bin.

20
Nemo WindCatcher User Guide

iDEN
For iDEN link to Bin feature, this option allows user either to choose Cell ID, PCCH, or Sector Label
for link to Bin. The ‘Sector Label’ option for iDEN sites uses PCCH and TCH information. The user
would need to follow the procedure below while using the ‘link to bin’ feature:
1. Browse onto Home>processing default>RF Configuration>idem menu, select ‘Sector
Label’ and ‘Save’
2. Add the cell site layer
3. Browse onto Home and select ‘Map sites to Route’
CDMA Tooltip
This option enables the user to view the ‘sector name’ for a PN
CDMA Phone Analysis
This option enables the user to select the ‘window size’ in addition to allow for PNs of value 0 to be
included in the data processed in Nemo WindCatcher.
CDMA PN Scanner Settings
This option enables the user to set Value for PN Increment from Scanner Data.
Scanner Processing
This option enables the user define a minimum Ec/Io level for scanner data processing to filter out
any PN below this threshold. This feature is particularly useful in areas with poor coverage.
LTE Scanner SubBand Data
This option enables the user to process SubBand Scanner data which is useful for plotting
SubBand LTE metrics.

Receiver Data
This option must be selected before processing a receiver device. It allows the user to populate
metrics from the ‘Receiver’ menu in the ‘Map’ tab after data is processed.

Channel Settings
This option allows the user to filter the processing of data according to channel and frequency
which is only supported for GSM or iDEN technology.

21
 Nemo WindCatcher User Guide

3.1.1.5 Vendor specific

This option provides vendor specific settings for different formats.

Comarco
Display Comarco time- if the option is selected the messages in the message window will display
the vendor time.
Data Pro
Use standalone GPS if available- this option will use GPS information from standalone GPS and
bypass the scanner GPS information.
Split receiver device by different scans- if the receiver device is a scanning multiple frequencies
then by having this option checked separate devices will be created for different frequencies.
ZK
Auto adjust scanner threshold for correlation length- This option will allow users to ignore the
“default minimum accepted Ec/Io level” and will use new threshold for the minimum level based on
correlation lengths.
Accuver
Merge GPS from SCN files to DRM files- by checking this option Nemo WindCatcher will extract
GPS information from the scanner devices and merge it automatically into the UE devices. (Only
required if UE devices does not contain GPS information).
TEMS
Set GPS interpolation- Interpolation is the method of constructing new data points. Having
checked this option Nemo WindCatcher decodes correctly the ping point information and performs
interpolation between Lat/Long and thus solves the problem of sparse GPS point.
The user may define the TEMS RR used before processing the data.
Swissqual
Flip GPS- This option can be used to report corrected latitude and longitude for Swissqual
inbuilding data files which switch Lat/long.

22
 Nemo WindCatcher User Guide

Allows the user to consider the Stop and start measurement message as a reference parameter.
Indoor
Allows user to use WGS84 coordinates as the correct Lat/Long for constructing data points
specifically for Indoor data.
Nemo
Selecting “Use Nemo Fast Loader” option you can process Nemo log files collected with Nemo
collection tools much faster compared to Regular Windcatcher Processing

For Nemo Fast Loader SQLite data processing is required.

Nemo Fast Loader is based on Nemo Vendor Events so any analytics related to the
events from L3 signalling is not available in Nemo Fast Loader.
Failure Analysis dashboard is not available with Nemo Fast Loader.

Geobinning as a binning option is not supported with Nemo Fast Loader.

Starting with JDSU 19.1,this option allows user to process data using the JDSU API (selected as
default).
JDSU
Starting with JDSU 19.1,this option allows user to process data using the JDSU API (selected as
default).

3.1.1.6 Background process

23
 Nemo WindCatcher User Guide

Multi-Process
This option allows the user to use multiple CPUs for processing. The user can select the number of
CPUs to be used while processing.
Minimum Processing Logs Size
This option is applicable for the background processing mode and allows the user to select a
minimum size for the files processed in Nemo WindCatcher.

3.2 Workspace
The ‘Workspace’ feature is provided to enable the user to reuse/share the layout of the different
views in Nemo WindCatcher. The ‘workspace’ created by a user is saved as .wws file and can be
shared between users.

24
 Nemo WindCatcher User Guide

3.2.1 Save the workspace

After selection of the window views, the user may browse onto Workspaces>Save option and save
the view as .wws file on his machine.

25
 Nemo WindCatcher User Guide

3.2.2 Open a workspace

These .wws files can be opened using the Workspaces>Open option and browsing onto the
saved/shared .wws file on the machine.

3.3 Cell sites

3.3.1 Creation of the cell sites

Click following menu for cell site creation:

26
Nemo WindCatcher User Guide

This option allows the user to create cell site files from ‘.csv’ or ‘.txt’ or ‘.xls’ or’.xlsx’ or Nemo .nbf
files containing cell site information.

The following information must be entered correctly:

• Separator: e.g.: ‘Comma’ for a csv file, ‘Tab’ for a text file.
• Column Names: Select ‘First row has column names’
• Encoding; options include ANSI, Unicode, and OEM.
Map the ‘Available fields’ onto the appropriate ‘Base Station’ fields by dragging the values, select a
location to save the output MapInfo tab files and select OK.

27
Nemo WindCatcher User Guide

If the user wants to use the same cell site information format every time, the user can save the
mappings in a template. The next time user won’t have to map these fields again. After completing
mapping click on “save as” option & choose a name for future use. The next time after importing
cell site information file, the user can simply select the saved template from the drop down menu
which will map all fields automatically.

28
Nemo WindCatcher User Guide

Pie Colors may be chosen through the ‘Options’ tab:

The Options tab enables users to change the visible size of sectors, transparency of colors and the
color of the sector. The color of the sectors can be colored by Sector ID or by Azimuth Direction.
Choose the “store location” for output cell site files by clicking on “Save” button. Browse for
desired folder location where user wants to store these files.

29
 Nemo WindCatcher User Guide

3.3.2 Default cell sites

This option will allow user to choose default cell site i.e. every time user process data or open a
database, these cell sites will appear automatically as default cell sites.

Browse for already created cell sites to save them as default.

3.3.3 Sector display

Easy access to Sector Display Options is now available by selecting a sector and then right-
clicking on the Sector and Link to Bin Selections. This will enable to user to change the sector
display properties ‘on the fly’ after cell site creation. Site and sector label options may be modified
within this display

30
Nemo WindCatcher User Guide

• Sector Display Option via Right Click,

• Site and Sector Label options can be modified

• Sector Size, Color and opacity can be modified on the fly

31
 Nemo WindCatcher User Guide

3.3.4 Remove cell sites

This option will enable user to remove the imported cell sites from the background.

3.3.5 Discovered LTE and UMTS sites

For LTE and UMTS there is also an option to detect the sites without creating separate tab file. LTE
sites for MCC, MNC pairs. can be detected and plotted from the parameter tree under the LTE and
UMTS/HSPA metric menu (LTE or UMTS/HSPA  Sector  Discovered Sites). Under the
“Discovered Sites” there is a drill down menu from which you can select the MCC/MNC pairs for
which the LTE or UMTS sites can be plotted. Select the MNC and drag-and-drop it onto the map
plot and the sites will be shown as solid circles.
Hovering the cursor over the cell site on the map there will be a pop-up window showing Site ID,
EARFCN/UARFCN, Cell ID, Device ID, MCC. MNC and location in Lat/Lon.

32
 Nemo WindCatcher User Guide

For each of the MNC/MNC pair a separate map layer will be created and the layers can be manged
through the Layer Control.

3.4 Create Geoset

You can create a new geoset to be used as a back ground image. Click the “Greate GeoSet” icon under the
“Home” tab to open the Background map editor.

33
 Nemo WindCatcher User Guide

By clicking “New” the following window will be displayed to create the geoset as a background map.

The ‘plus’ sign will enable addition of data for creation of the geoset.

34
 Nemo WindCatcher User Guide

Once the selections are made, select ‘Apply’ and then ‘OK’ and a preview of the processed GST will
be displayed:

3.4.1 Background
This option will let you import the created GeoSet into your current map. A pop up window will
appear to let you browse to the saved GeoSet file to choose.

35
 Nemo WindCatcher User Guide

3.5 Bin style

The ‘Bin style’ option enables the user to select the symbol displayed for each device processed.

36
 Nemo WindCatcher User Guide

The ‘Style’ column enables the user to select the symbol, color, background and effects displayed
on the map for the corresponding device:

3.6 Event settings

The ‘Event Symbol Selection’ enables a user to select/modify an event to be displayed on the map,
chart, and/or the Event Tree.
Nemo WindCatcher provides a comprehensive set of call events right from handset registration
and call access through call end. These events can be viewed either in the event browser, map
view or both. The symbols and colors are user definable.

37
Nemo WindCatcher User Guide

From Home Tab click Event Settings, The following window will appear:

The events are categorized on the left pane under separate tabs forming logical groupings of
events (such as LTE Call Setup, LTE Registration, etc.). The events are further collected into sub-
categories within each category (such as LTE Authentication Failure, LTE AS Security Failure, etc.).
There are three checkboxes for each event selection, as shown. The first selection selects whether
to display the event on the event browser docked window or not. The second selection is for
display on the map. Note that these selections apply to all opened datasets, and will be
remembered the next time the application is opened.
The Third selection is the Show on Chart Option- Support for ‘events’ in the time-series charts.
Users may browse onto Home>Event Settings to select the event to ‘Show on Chart’ and select
‘Apply’

38
 Nemo WindCatcher User Guide

A symbol style, colour can be changed by simply double-clicking on the symbol from the menu
and making the requisite changes in the window displayed below:

3.7 Threshold settings

Thresholds may be user-defined for every metric available in Nemo WindCatcher according to the
analysis requirements.
To set a threshold, select Threshold Settings from the Home tab. This will display a list of metric
groups. Select the metric group of interest & change the threshold as desired.

39
Nemo WindCatcher User Guide

An example threshold specification window is shown below for the LTE Dominant RSRP metric
(under the LTE Dominant RF… metric group).

The following may be done:

• To change the individual threshold values, select the desired row, then select the
Threshold column. The value may then be changed to a valid, user-defined value.
• To change the individual threshold colours, select the desired row, and then click on the
down arrow to see a list of available colours.
• To change the number of threshold entries, select the “+” or “-” symbols repeatedly until
the number of entries are displayed.
• Select OK when complete & apply to save the changes. Select Cancel to abort without
saving the changes.
Threshold settings can also be changed from the parameter tree. Right-click over the metric and
select “Edit Threshold”.

Any changes made to threshold settings will only take effect the next time the
corresponding metric is plotted. The new settings will not apply to any metrics that are
already displayed on the map(s).

40
 Nemo WindCatcher User Guide

3.7.1 Exporting thresholds and events

Nemo WindCatcher allows users to export threshold and event settings to CFG files. These files
can be shared across users as well as users can create multiple settings for different analysis using
the ‘Settings’ menu.

3.8 Dataset creation and management

The first step in viewing data in Nemo WindCatcher will be to create a dataset from the data files
to be analyzed.
Nemo WindCatcher provides the powerful option to save the datasets once they are processed.
Therefore, this process of creating the dataset need only be performed once for each unique set of
drive data. These datasets may subsequently be opened immediately without needing to go
through the processing step again.

3.8.1 Create new dataset

From the main menu, select File, then New Dataset… or select the New Dataset -icon:

41
 Nemo WindCatcher User Guide

The following window will open:

Click on the Add button next to select the Drive Test Files and select all files that you wish to
process. Note that more than one file may be selected for processing, and these files may be of
any supported mobile phones.
Click on the Browse under the save Database section to select a directory and name to save the
processed data.
You may choose not to save the processed data, in which case the last step needs not to
be performed. However, in this case, you will need to repeat this process to view the
data the next time the application is loaded.
If a dataset has already been created, then this dataset may be reopened by selecting
the Open Dataset…icon that is next to the New Dataset…icon above.

3.8.2 Open existing dataset

To open a previously processed and saved dataset, select File, then Open Dataset… or select the
Open Dataset …-icon:

Browse to the directory that the dataset was saved and select the .mdb dataset database file. The
selected dataset will be loaded into Nemo WindCatcher as a new map window.

42
 Nemo WindCatcher User Guide

3.8.3 Close dataset

To close a dataset, select File, then Close Dataset and select the appropriate dataset to close.

3.8.4 Merge datasets

This option allows the user to merge more than 1 datasets in Nemo WindCatcher. When the option
is selected, a ‘Merge Datasets’ window opens up allowing the user to ‘Add Datasets’ to be merged.
Once the datasets are added, a location for the final merged dataset is selected (under ‘Browse’
highlighted below) and ‘OK’ selected, Nemo WindCatcher will merge the datasets and open the
final, merged dataset on the interface:

3.8.5 Merge devices

This option allows the user to merge devices within a dataset:

Manual Merge: This option allows the user to select the devices that need to be merged. User will
select the devices as per the snapshot below (note the two devices selected have unique ‘Phone
ID’)

43
Nemo WindCatcher User Guide

Once the ‘merge’ option is selected, the two devices are assigned the same Phone ID and the user
selects ‘Accept’:

Nemo WindCatcher will merge the two devices and re-open the dataset on the interface.
The Auto Merge option will search for similar devices (in case of phones similar MIN ESN) and
automatically merge the devices.

44
 Nemo WindCatcher User Guide

4 User-Interface Overview

4.1 Docked windows

Key information about the dataset associated with the active map window is contained within
windows along the sides of the application. On the left hand side there are docked windows for
layer 3 and phone log messages, events, binned phone data, legends and dataset information. In
the right hand side there are docked windows for the pone date in the selected bin on the map,
legend, user queries and for failure analysis dashboard
The default view is with all windows in the Collapsed Mode. This maximizes the map viewing area.
Any window can be expanded by just moving the mouse over the desired window on the side-bar
window selection.

This window may also be resized as required. To collapse the window again, just select any point
outside this window.
This window may also be Docked so that it is permanently expanded on the screen. In this docked
mode, the other windows in the application will be resized so that all windows are visible. To dock
the window, just select the push pin as shown:

Just select the push pin again to get this window out of the Docked state, and revert back to the
collapsible state.

45
 Nemo WindCatcher User Guide

Docked Windows may be changed to floating windows by just dragging it out from side bar. To
reinstate a docked window, double click window header & it will re-positioned to side bar.

4.1.1 Windows view

Under the View tab “Windows View” option will allow the user to retrieve any specific docked
window if it has been closed from the main interface.

46
 Nemo WindCatcher User Guide

4.1.2 Legend window

Legend window shows user all the events and metrics that are currently selected on the map
interface.

Thresholds for metrics can be adjusted on the fly by double clicking on the metric legend and the
Modify Ranged Theme page will open as shown below:

47
 Nemo WindCatcher User Guide

4.1.3 Failure Analysis Dashboard

With the failure analysis dashboard feature user can analyze failure events for GSM, UMTS and
LTE/VoLTE occurring in serving sectors. There are three categories - Accesibility, Retainability and
Mobility – for witch the analysis can be done. You can select device for the analysis and also if you
want to do it for data or voice calls. In addition to the failure analysis based on the events, with this
feature you can do an antenna orientation and overshooting analysis. For orientation and
overshooting analysis you need to have the cell site information available.
The Failure Analysis dashboard can be opened from the “Failure Analysis” tab located on the side
bar in the right hand side of the window.

4.1.3.1 Summary view

The Failure Analysis dashboard opens in a summary view showing the count of the root causes or
failure events within each of the categories for all the devices, for all the technologies, and for
voice and data connections. If the failure event cannot be allocated to any of the technologies,
then it is classified as “Other”.
For the orientation the summary view shows the number of sectors for which there are more than
75% of the samples outside of the 180 degree beam width. For the overshooting you can see from
the summary view the number of the sectors for which there are more than 90% of the samples
further than the pre-defined sector distance.
Based on the information shown in the summary view it is now easier and faster to investigate in
more detail the different failure types and root causes within different categories for a selected
device.
It is also possible to export the summary data to excel report. Just click “Export Summary”, browse
to the folder you want to save the summary report, name the file and save it.

48
Nemo WindCatcher User Guide

Below the screenshot of an example summary report.

In the summary report, there is a “Details” sheet for all the events with root causes also in table
form.

49
 Nemo WindCatcher User Guide

4.1.3.2 Dashboard analysis

For the deeper analysis just click one of the icons of the categories you want to analyse.
If you select for example “Retainability” category, there is a pie chart for the root causes and a pie
chart for the sectors that has been affected by any of the root causes shown in the root cause pie
chart.
In addition to the pie charts you will see the map and event analysis grid as well as before and after
RF analysis grid. The Event Analysis Grid & RF Analysis grids works in sync with the failure analysis.

You can now further analyse one of the root causes by clicking on top of the root cause wedge. The
selected wedge for that root cause gets bit loose from the pie chart and now you can see the
effected sectors for that root cause as well as the event and RF analysis grids. By further clicking

50
Nemo WindCatcher User Guide

any of the affected sector wedges the event in question shows up on the map view and in the event
analysis grid view.

There is an option to sync/un-sync the events within the affected sectors to map view. If the “Sync”
is activated the event will become visible on the map after clicking the wedge of the effected
sector. The sync option is activated by default. o If the “Sync” is not activated the event
information is visible in the event analysis grid view.

51
 Nemo WindCatcher User Guide

You can do similar, more detailed analysis also for the antenna orientation and for the
overshooting.

For the orientation analysis, the upper pie chart indicates the number of sectors for which there are
certain percentage of the samples outside of the 180 degree antenna beam width.
By further clicking the wanted percentage wedge you can see the affected sectors in the pie chart
below and the RF analysis grid under the map view for more detailed analysis
For the overshooting analysis, you can follow similar procedure. Now the number indicates the
number the sectors for which there are certain percentage of the samples further than the pre-
defined sector distance.
The failure analysis can be used also for analysing VoLTE events. If you have VoLTE data you need
to select 4G as a technology and Voice as a service.

4.1.3.3 Default events

For each of the event categories – Accessibility, Mobility, Retainability – there are pre-defined RF-
level events as default events and they can be seen by clicking the “Configure” icon after selecting
the category. You are not able to add or remove any events to/from the Default Events. If you want
to add events that are not included in Default Events, you can customize your own group of events.

52
 Nemo WindCatcher User Guide

Access Retain
ibility ability
Mobilit
y

4.1.3.4 User defined event groups

You can customize customize your own group of events if they are not included in the Default
Events. This feature is extremely handy if you want to analyze for example application level events
or collection tool vendor specific events.
The new event group for your own events can be created by clicking the icon to open
the empty pane for adding the events you want. The new event group can be named and
after updating the name it will appear as a new category in the right-hand side of the dashboard.
The events can then be added simply by dragging and dropping them from the parameter tree. If
the event you want to add is not a failure event, it can still be added but a notification message
pops up saying that it is not a failure event. After adding the events click “Save” and the pie charts
for the events and for the affected sectors will show up together with the event analysis grid. The
count of the events under that new category will be also shown in the Summary view.

53
Nemo WindCatcher User Guide

The events in the user specified event group can be

selected/unselected for the analysis by simply checking/un-checking
the event(s) from the event list. The event list can be opened by first
selecting the event group and then clicking “Configure”. After
making the event selections, again click “Save” to open the pie chart
view. If you want to update the event list, you can click “Reset” to
clear the event list and then you can drag and drop new events from
the parameter tree.
The user defined event group will remain there
when you open Nemo WindCatcher the next
time after closing it. The user defined group
can be removed by clicking the sign next
to the event group name.
For the sake of clarity all the pre-defined category tabs are shown as
orange tabs and all the customer defined categories are shown as
blue tabs.

54
 Nemo WindCatcher User Guide

4.1.3.5 Exporting the dashboard configuration

The dashboard customization can be included to .CFG file when exporting the settings. Under the
Home tab there is the “Export Setting” icon and when selecting the items to be exported there is a
thick box for the “User defined tab” under the Failure Analysis.

4.2 Tabbed windows

Nemo WindCatcher supports multiple datasets to be loaded into the application at the same time.
Each dataset is opened as a new tabbed window.

You may move between windows by just selecting the appropriate tab. The tabbed window title will
be modified appropriately to reflect any metric that is currently displayed on each map.

4.3 Multiple maps

Additional Map and/or Time-Series, X-Y chart, PDF?CDF chart windows can be opened for any of
the loaded datasets by selecting the appropriate dataset under the Views tab.

You may place windows side-by-side by selecting and dragging the desired window to the right or
below. Just Click on the icon below for the location selection i.e. left, right, top or bottom

55
Nemo WindCatcher User Guide

An example of a vertically split window using the above-mentioned technique is shown below:

All windows of the same dataset are synchronized, so this makes comparison between metrics very
convenient and powerful. The synchronization extends to between Map and Time-Series windows
as well.

56
 Nemo WindCatcher User Guide

4.4 Synchronization
Nemo WindCatcher implements complete synchronization of all possible views in any direction for
maximum effectiveness and efficiency in performing drill-down analyses of problems.
The following views are all synchronized with each other (from the same dataset):
• Maps (including multiple map windows for the same dataset)
• Time-series charts (including multiple time-series chart windows for the same dataset)
• Dropped Call Event Analysis Window
• High BLER/RxQual Analysis Window
• Message Window
• Event Window
• Phone Data Browser
• Tables

4.5 Metric and event plots

Any opened dataset in Nemo WindCatcher will begin with the Map view or with the summary view.
The initial Map view will show the drive route without any metrics plotted. The various events that
appeared on the drive will also be displayed.
To display any metric or event on the map, on the time chart or on the table you can drag and drop
metrics and/or events from the parameter tree opening in the left hand side of the map view. The
metrics and events are visible in the parameter tree for the metrics and events that are included in
the processed data set.

For the map plot you can select the device from the device filter on top of the parameter tree.

57
Nemo WindCatcher User Guide

Device filter in within the parameter tree

With the device filter within the parameter tree you can select the devices for which the metrics
can be plotted onto the map.
The device labels in the device filter can be edited:
• By right-clicking on top of the “Available Devices” you can open the editor to select the
fields visible in the device label as a default

• The individual device labels can be further edited by right-clicking on top of the device
label to open the device label editor.

• There is an option to select/unselect all the devices at once

• There is an event selection to make the events visible/invisible in the map view.
• Under the “Metrics” you can select to show and remove the metrics on the map view.
• The labels can be selected to be visible or invisible in the map plot.
• The metrics can be removed from the map simply by clicking the symbol beside the
metric.

If you change the device and/or event selection in “Selection” menu you need to click
“Apply” button to get the changes onto the map view.

58
Nemo WindCatcher User Guide

The metrics/events dropped on the map view are marked with the symbol. The metric/event can
be un-selected by clicking that symbol.

By clicking the Clear All on top corner of the parameter tree window you can un-select all the
metrics from the Map view.

Plotting of events on the map follows the same principle. Just select the event(s) and drag and
drop them. Deleting of the events can be done same way as with metrics – they can be deleted
one-by-one or all at the same time.

The thresholds for the metrics can be edited from the parameter tree

59
Nemo WindCatcher User Guide

The visibility of the metrics on the map view can be controlled either by Layer Control or by using
Metrics Offset functionality in the Map Tools menu.

From the Time Series Chart the metrics and events can be removed from the Chart option menu.

There is also search function included in the parameter tree. The search word can be written to the
search window and the matching metrics/events will be shown and highlighted on-the-fly.
You can return to the main level of the parameter tree by clicking the Clear tab.
By clicking the Clear All on top corner of the parameter tree window you can un-select all the
metrics from the Map view.

60
 Nemo WindCatcher User Guide

In the metrics can still be selected also traditionally from the menus for the Map view,
for the Time Series Chart and for the Data Table view. It is highly recommended that you
select the metrics and/or events either from the parameter tree or from the traditional
metric/event menus.
You may also select any of the Metrics to display by right-clicking anywhere within the
Map window. See section ‘On-screen menus’ for more details.

4.6 Time series plots

You may view any dataset metric as a time-series by selecting Views, then New Time Chart from
the main menu for the dataset currently opened, or by selecting the New Time Series icon as
follows:

If there are multiple datasets loaded, then select the desired dataset from the list.
The selected metrics and/or events can be dragged and dropped from the parameter tree as
described in section 4.5.

61
Nemo WindCatcher User Guide

Overview

Users can drag and drop metrics from parameter tree onto the time series chart

Chart view Toolbar (from left to right)

• Drop down selection allows users to switch between line and bar chart
• ‘Show Legend’ checkbox allows the users to toggle visibility of chart legend window

62
Nemo WindCatcher User Guide

User has the option to turn on/off the visibility of any chart series plotted from the legend
window check box
• The selection arrow serves multiple functions
o Activating the selection arrow allows the users to zoom into specific area on the chart
by holding the mouse left-click pressed and drawing a box around the area of interest
o Selection arrow also allows the users to click on the data points of the chart series and
sync to that point on the map. Users can also zoom in/out using mouse wheel scroll
over the chart area. A red dotted line on the chart provides reference information of
the synced bin on the map
• The hand selection tool also the users to pan across the chart view
• The refresh button allows the users to redraw/refresh the map on update of devices in
parameter tree
• The ‘Clear All’ option allows the users to clear the entire chart view
• The ‘Reset’ button allows the users to switch back to the original zoom level
• The ‘Print and Export’ option allows the users to print and export the plotted chart view to
various formats
• The ‘Save to Template’ option allows the user to save the metrics/events currently plotted as a
template to be used later for any other dataset. Multiple different templates can be saved
o The drop down allows to pick the template of choice for the chart view

The bottom preview window below the chart allows the users to
• Focus on an area by clicking on the area of interest in the preview window. The above
chart automatically zooms to that location
• Allows users to increase/decrease the width of the preview window and pan along the
chart view

Multiple time series chart window can be opened

The charting tool automatically places the metrics plotted on multiple Y axes depending upon the
unit and the legend range values

63
 Nemo WindCatcher User Guide

4.7 Tables
This feature provides an alternative view of data by displaying it in the tabular form. Select the
Tables icon to display the table for the current dataset.

The following can be done with the table:

• Fields can be added to the column display on the right by dragging and dropping from the
parameter tree as described in section 4.5.
• The table can be exported to an Excel spreadsheet or directly to a MapInfo tab file by
selecting the appropriate icons on the top of the window. Note that a separate MapInfo
tab file will be created for each phone in the dataset.
• The Field Name: column may be hidden or shown by toggling the Show/Hide Field Name
icon on the top. It is sometimes useful to hide this column so that more of the Tabular
Data fields may be viewed.
• All displayed fields in the Tabular Data section may be removed by selecting the Unselect
All Fields icon at the top of the table’s window. Note that the first 5 columns are
permanently on the table, and will not be removed with this button.

The table is fully synchronized with the rest of the browsers, maps and time-series plots
associated with the same dataset.
Once certain fields are selected for display on the Tabular Data window, these selections
will be remembered for every dataset opened after making these selections.

4.8 Printing / plotting

To print/plot the current map, select FilePrint Map/Chart or from the Map view, Click on

64
Nemo WindCatcher User Guide

The Print Preview screen will

appear with a preview of how
the printout will look like.

Select the Printer Setup from the icons if a non-default printer

/ settings need to be configured. Plotters are also supported,
including most paper sizes such as A, B, C, D and E-sizes.

65
Nemo WindCatcher User Guide

Once configured, the printout may either be printed on the selected printer by selecting Print or to
a PDF file by selecting Save as PDF.

To exit the preview without sending the printout, select Close.

66
 Nemo WindCatcher User Guide

4.9 PDF/CDF charts

PDF/CDF charts of selected metrics may be seen by selecting Views tab then PDF/CDF, or by
doing right click on map & by selecting Current Metric PDF/CDF.

The metrics for the selected devices (from the drill-down

menu) can be dragged and dropped from the parameter
tree. The selected KPI will be visible in the window on the
left side of the chart.

67
 Nemo WindCatcher User Guide

These PDF/CDF charts may be exported to excel file by selecting the Save to Excel icon. Also,
these charts can be exported into following formats by using Export button.

4.10 X-Y chart

X-Y chart can be created by clicking the X-Y icon and then dragging and dropping the metrics
from the parameter tree onto the chart window. Metric for X-axis must be selected first and then
the metric for the Y-axis. The selected metrics will be visible in the left-hand side of the chart.

68
 Nemo WindCatcher User Guide

5 User Queries
The User Query feature (docked window on the right side of the interface) can be used to plot user
defined KPIs and to create reports out of the user defined KPIs.

These features allow the user to create any metric or report based on any combination of existing
metrics and events in Nemo WindCatcher. Conditions may be applied to these metrics and reports
before generation.

69
 Nemo WindCatcher User Guide

5.1 General usage

These two features are fundamentally used in the same way. The interface is divided into 6
sections, as shown below.

• User Defined Metric/Report Selection Tabs: The user may select to either use the User
Defined Metrics (UDM) or the User Defined Report (UDR) feature by selecting the
appropriate tab.
• Metric/Report Item Definition: One or more items may be selected for the UDM/UDR.
• Conditions: One or more conditions may be applied to the selected UDM/UDR items.
• Icon Selections: The definition may be saved by selecting the icon.
• Previously defined Metrics/Reports: The defined UDM/UDR will now appear in the left
pane. This UDM/UDR may now be run by double-clicking the appropriate query on this
left pane or by selecting the Execute Query icon .
• Results: The results may be viewed on the results section on the right. These results may
be exported to an Excel .csv file by selecting the Export to CSV… icon . In the case of
UDM, the selected user defined metric will also appear on the map, color coded by the
legend defined.
Nemo WindCatcher allows the user to create their custom legend and field for the user queries,
please see sections below for detail.

70
 Nemo WindCatcher User Guide

5.2 Create a custom legend

In addition to the predefine legends for the user queries, a custom legend may be defined by
selecting the Setup Customized Metrics Threshold . The following window will appear:

Select Create new threshold group icon , choose a name for threshold and define the desired
threshold, as shown below:

71
 Nemo WindCatcher User Guide

5.3 Create a custom field

In order to facilitate the process of creating user queries, the user query section consists of a
custom filed option. To create a custom field, select the Create Customized Field icon . The
following window will appear:

The field may be defined by selecting the appropriate existing fields and operators. Note previously
defined custom fields may be used to create new custom fields, making this feature have virtually
limitless possibilities to create very complex custom fields.
Once created, enter an Expression Name (to be used to select the field) and an Expression Result
Alias (which will be the column heading in the results section). Select the Save Expression to User
Defined Field icon to save this custom field.

5.4 Creating user-defined metrics

For ease of illustration, the implementation will be explained using an example.
Example:
Objective: Create a User Query Metric displaying the Dominant RSRP for a specific Dominant RSRP
(Value > -85).

5.4.1 Define the metric item

The metric to plot may be selected from the second box in second section as shown below:

72
 Nemo WindCatcher User Guide

A list of all available metrics within Nemo WindCatcher will appear. Select the Dominant RSRP
(dBm) metric from the LTE Dominant Data group.
Select the appropriate threshold from the third box list.
The final definition should look as follows:

5.4.2 Define the conditions

The conditions are defined in the third section.
The first step is to create a new condition by selecting on the arrow and selecting Add a new
connection, as shown below.

Select the appropriate metrics and conditions. For this example, the Dominant RSRP (dBm) and
the corresponding value (>-85). Note that the list of available values in the current dataset for any
selected metric may be viewed by selecting the drop-down box, as shown below:

Additional conditions may be defined by left-clicking on the arrow again and selecting Add a new
condition.

5.5 Creating user-defined report

For ease of illustration, the implementation will be explained using an example.
Example:
Objective: Create a User Query Metric displaying the Dominant RSRP (dBm) for a specific LTE UE
RSRP.

5.5.1 Define the report item

The report items may be selected from the second box in section 2, as shown below:

73
 Nemo WindCatcher User Guide

Select the appropriate metric from the second box. Then, select the appropriate aggregation
method from the first box. Select the desired sorting if required from the third box.
Additional report items may be defined by left-clicking the green arrow and then selecting Add a
new field.
The final report item definition should appear as follows:

5.5.2 Define the conditions

The conditions are defined in section 3.
The first step is to create a new condition by selecting on the arrow and selecting Add a new
connection, as shown below.

Select the appropriate metrics and conditions. For this example, the Dominant RSRP (dBm) value
(>-85). Note that the list of available values in the current dataset for any selected metric may be
viewed by selecting the drop-down box, as shown below:

5.6 User queries in the parameter tree

The pre-defined and the user defined queries can be dragged-and-dropped from the User Query
window to parameter tree. The dragged-and-dropped queries are automatically placed under the
“Available User Queries” menu within the parameter tree. User Queries can then be dragged-and-
dropped from the parameter tree to the map view, to the time series chart or to the table view.

74
 Nemo WindCatcher User Guide

The threshold/legend of the User Query can be edited by selecting the query from the parameter tree
by right-clicking the mouse and then by clicking “Edit Threshold”. The query can be deleted from the
parameter tree similarly by selecting the query in question by right-clicking and then by selecting
“Delete User Query”

If there are conditions attached to the User Query they can be edited by clicking the tab for the
query in question.

75
 Nemo WindCatcher User Guide

5.7 User Queries in Batch Print

The user defined queries can also be selected for the batch print under the map tab. There is a group
created for the User Defined Queries within the Batch Print window. The user queries that are available
under the “Available User Queries” in the parameter tree are visible also in that group.

76
 Nemo WindCatcher User Guide

6 Using Nemo WindCatcher – Advanced

6.1 In-Building Profiler

In-building profiler feature will allow user to map the in-building background file (jpg, bmp etc) to
exact location on map by selecting 4 reference points.

To create an in-building profile, click button available under “Home” tab. Once the

profiler is launched, import the background file using tab.

Using the below “Anchor Points” option map the jpg lat/longs to actual lat/longs on the available
map.

Click on “P1” and click on jpg to get the pixel position, now click on the map for the actual
lat/longs on the Map available in the left window. Follow the same procedure to map all 4 points

and then hit “Apply” followed by .

77
 Nemo WindCatcher User Guide

Once the profiler MapInfo file is generated, start processing the in-building data and import the tab

file upon completion using or option.

6.2 Batch printing

Nemo WindCatcher can be configured to print several plots at the same time. To do so, select
MapFrom Print Menu, Click on Drop down Menu & then Batch Print….

78
Nemo WindCatcher User Guide

The following screen will appear:

79
Nemo WindCatcher User Guide

There is a search function for metrics to be plotted

Select the desired metrics to plot for desired device(s) with selected Legend options.

Once the metrics and devices have been selected, user has the option to ‘Clear Selection’, ‘Print
Preview’, ‘Print’, ‘Export to new or existing PowerPoint presentation’ or ‘Save’ the metric selection
as a template that may be selected at a later date:

The ‘Page Setup’ and ‘Export’ options are similar to ‘print Map’ menu

Under the Export document there is an option to export the images also with the title.

80
 Nemo WindCatcher User Guide

6.3 Metrics/Events Offset

6.3.1 Metrics Offset

It is sometimes useful to compare the performance of two or more metrics in conjunction to
understand possible correlations between these metrics. One of the ways to do this in Nemo
WindCatcher is using this Metrics/Events Offset feature.
To use this feature, click on the Metrics/Events Offset icon

The following window will appear:

A maximum of six offset metrics can be selected at any one time.

The offset distance between each metric offset can be set using the settings provided under the
Option  Default Offset section.
Then offset Pan can be used to create offset b/w multiple layers. Click on the center button to
reset the offset.

81
 Nemo WindCatcher User Guide

If the Selections on Map button is selected in the Map Selection Option, then there must have
been selections on the map prior to opening this offset metrics configuration window. To make
selections on the map, change the mouse pointer to one of the map selection pointers (see options
below) and select the desired drive test points prior to calling this configuration window.

Any offset metrics on the map may be subsequently cleared by clicking on the center button in
Offset Pan.

6.3.2 Events Offset

It is sometimes useful to offset plotted events to avoid the event symbol overlapping with the
metric plots. This helps the user to have full view of the metric/metrics and events side by side.

82
Nemo WindCatcher User Guide

One of the ways to do this in Nemo WindCatcher is using this Metrics/Events Offset feature.To use
this feature, click on the Metrics/Events Offset icon

The following window will appear:

Choose the layer ending with ‘_Event’ for the desired device and then offset similar to what you
would do for metrics offset

See example below

Metric plotted: RSRP

Events plotted: LTE RRC Connection Fail and LTE Radio Link Failure

83
Nemo WindCatcher User Guide

BEFORE APPLYING EVENTS OFFSET

AFTER APPLYING EVENTS OFFSET

84
 Nemo WindCatcher User Guide

6.4 Layer control

The purpose of the layer control is to control what gets displayed on the maps and how they are
displayed. Nemo WindCatcher utilizes the MapX software to display the maps, which is based on
the popular MapInfo format. Layers may be added, deleted and labeled just like how they are done
in MapInfo.

The most important tabs in the layer control are described below.

6.4.1 Metrics
In this tab, all of metrics which are currently plotted will be displayed, you select/unselect them to
make them visible or removed from the map. In addition, this tab allows the user to display labels
for the metric:

85
 Nemo WindCatcher User Guide

6.4.2 Selection
Each device is associated with a ‘route’ and ‘Event’ layer. The user may select the layers that he
wishes to view on the map:

In addition to this, the user may simply select the layer from the ‘layer’ tree and choose its visibility
options.

86
 Nemo WindCatcher User Guide

6.4.3 View
In this tab map scale, zoom & map orientation can be selected

6.4.4 Editing
In this tab Default styles for drawing tools can be selected.

87
 Nemo WindCatcher User Guide

6.4.5 Background maps

Additional Map layers can be added using the Add option under Layers and map layers can be
reordered using the Up and Down options under Reorder. The controls are identical to those used
in MapInfo.

6.5 Multiple phones

Nemo WindCatcher will automatically handle multiple phones within the same dataset. If the
collections of files that comprise a dataset contain information from more than one phone, then
Nemo WindCatcher automatically offsets the map plots for each phone. The offset separation may
be set by selecting Home, then Processing Default>Interface and then specifying the desired offset
in the Map Offset for Multiple Phones/Frequencies section.

88
Nemo WindCatcher User Guide

Any of these phones may be displayed or removed from being plotted on the map through the
layer control dialog window that is available by selecting the Layer Control icon.

Select or unselect the phones as desired by selecting device data layer in the Layer Control. Only
the selected phones will be displayed on the map upon selecting the OK button. See section on
Layer control for more details.
The Dataset Info docked window on the left bar contains information on each phone
such as the type of phone, IMEI number, etc.

89
 Nemo WindCatcher User Guide

6.6 On-screen menus

Nemo WindCatcher provides access to menus and bin information on the screen. There are two
different types of on screen menus, as described below.
No Selection Menu
The following menu is displayed when the mouse right-click button is pressed while there is no
selection on the active map:

Basic Metrics or Advanced Metrics

Any of the Metrics or Advanced Metrics may then be plotted on the map by making the
appropriate selection on this menu.

90
Nemo WindCatcher User Guide

Export Metrics/Events to Excel/MapInfo/Google Earth format

By pressing mouse right-click button on Map, and then by choosing Export Metrics/Event option
user may export Metrics or Events in Excel, Map info or Google Earth (.kml) compatible formats.

Google Earth export

After exporting the metric(s) to Google Earth the metrics can be plotted either with the labels or
without the labels.
The values of the bins have been grouped and each of the group can be selected from the menu
under the device.
The location of the legend can be selected for each of the Metric

91
 Nemo WindCatcher User Guide

6.7 Raster map sites to route

The following procedure enables a user to align a drive route to the image in the absence of a tab
file.
1. Make sure you have dataset and image file in same folder
2. Open your dataset and select “Drive Route to Raster Mapping

3. Click on ‘Open Image’ and load the image file that needs to be mapped with the drive
route

92
 Nemo WindCatcher User Guide

4. On this screen, you will align the drive route to picture image. You will need to select 4
lat/long points (P1, P2, P4, P4) on the drive route and select 4 X/Y pixel positions
corresponding to the 4 lat/long points on picture image respectively. The 4 points
selected should be generally on 4 corners to align the route points on the image file.
5. It will create a new TAB file at the same location. You will need to add the tab file via the
layer control option as explained previously.

6.8 Polygon creation

The following procedure is used to create and import polygons into:
1. Browse onto Map>Map Tools and select the ‘arrow ‘ on the lower right corner
2. Select the ‘polygon’ icon

93
Nemo WindCatcher User Guide

3. Select the area on the map for the polygon:

4. The area will be highlighted once selected. Now, right click on the map to ‘create a
polygon’

94
 Nemo WindCatcher User Guide

5. Save the polygon created which gets saved as a TAB file.

6.8.1 Polygon/boundary import

The boundary can be imported in the following ways:
1. You can select the “Apply Polygon” option on Right Click on the Map window. Once a MapInfo
tab file (as an example file created by following the Polygon creation steps above) is selected
it will apply this information to the dataset. All bins within the polygon will be marked with
“inside polygon” column of the database as 1 and all bins outside the polygon will be marked

95
Nemo WindCatcher User Guide

with a 0. This metric can be used in the User Query and Reports to query the data inside or
outside the polygon.

2. You may import the boundary through Map>Import Boundary menu:

Browse and select the MapInfo file, select the value for MapInfo field, select ‘Custom 1’ for
‘mapped field’ and provide a name under ‘mapped name’ for the boundary and select ‘Process’:

3. To import the polygon and remove a specific path from the route use the Cut option.

96
 Nemo WindCatcher User Guide

6.8.2 User Query for Polygon Filtering

The “inside polygon” or custom1 to custom 10 fields can be used in the User Queries to filter data
inside or outside the polygon.

97
 Nemo WindCatcher User Guide

6.8.3 Report generation

The mapped field above can be from Custom1 to Custom10. For reports theses, Custom fields are
available in KPI Mapping as shown below:

In the Custom Report if a user wants to exclude the area outside the polygon following condition
should be added in the condition’s tab.

In the example above Polygon is mapped to Custom1 field. When this condition “conditioncovered”
is applied to any metric in “Metric Data” table to Custom Report the result for that metric with be
generated after applying the exclusion.

6.9 Exporting reports and maps

The active map and various reports may be exported from Nemo WindCatcher for further analysis
and display purposes. The export functionality is as follows:
Export Message Data
The purpose of this report is to export the Layer 3 and Log messages to a text file for further
analysis. There are two options when this type of export is selected:
• All Messages
• Selected Messages
The All Messages… option will save all the messages that are available on the message browser
docked window in text format.

The All Messages… option could take a long time to export and result in very large text
output file, and should be used with care.

The Selected Messages… option will only export the messages that are selected on this message
browser. To use this option, first open the message browser docked window and select the range
of rows to export. Then select this Selected Messages option to perform the actual export.
There will be a window presented to specify the location and name of the exported file for both
these options.

98
 Nemo WindCatcher User Guide

6.10 Exporting tables

The table export feature provides a powerful method to export a wide variety of metrics and bin
counts to either an Excel spreadsheet or directly as a MapInfo tab file. This export is available
through the Data Tables feature under Views tab.

The following window will appear; this window can be docked on screen by double clicking the
menu bar on it.

99
 Nemo WindCatcher User Guide

Selected metric & events can be exported in Excel, MapInfo & Google compatible KML formats.

6.11 Elevation profile

Elevation profile available in the Map tools is used to provide the Elevation profile as a terrain.
Elevation on the y-axis of the graph is the height of the terrain above the sea level. Antenna height
has to be added on the top of elevation to know the RF radiation point.

100
 Nemo WindCatcher User Guide

6.12 Attribute Manager

The attribute manager enables the user to create and define new metrics that may be used for
plots within Nemo WindCatcher and for the Event analysis which will be detailed later in the
manual. An attribute is defined as an engine entity that aggregates values over a certain user
defined window size or bin interval.

The following window is displayed when the ‘Attribute Manager’ is selected

101
Nemo WindCatcher User Guide

An attribute can be created using the steps below:

1. Select the technology using the technology menu:

2. Selection of the attribute: The user may select the attribute from the groups defined
under the ‘Attributes’ tree or Add a new attribute

• The “data type’ allows the user to define the type of output expected i.e. double, string,
long, ulong, short, ushort, byte, character.
• The ‘Default Binning’ allows the user to select the aggregation method:

102
Nemo WindCatcher User Guide

The following binning options are available:

• Average: provides the average value of the attribute for the entire bin
• Current: provides the instantaneous value for the attribute
• Last_val: provides the last, valid value observed for the attribute for the bin.
• First_val: provides the first, valid value observed for the attribute for the bin.
• Second_val: provides the second, valid value observed for the attribute for the bin
• Minimum: provides the minimum value observed for the attribute for the bin
• Maximum: provides the maximum value observed for the attribute for the bin
• Accumulate: Adds all the values observed for the attribute within the bin
• The ‘Add Database Column Mapping’ allows the user to define an attribute that would be
added to the processed database in Nemo WindCatcher. Here the user can define the
binning, select the table and the column, define the ranking. The ‘Raw output’ option can
be selected for receiver devices.

103
 Nemo WindCatcher User Guide

6.13 Event diagram

The Event Diagram may be used to model call state, create events and statistics. The following
window is displayed when this option is selected from the ‘Tools’ tab:

104
Nemo WindCatcher User Guide

The user must select the ‘technology’ and ‘Format’ before creation/modification of an event
diagram. Each event diagram is comprised of several states and transitions. The user may ‘double
click’ on a state to define the expressions that evaluate when a state is entered or exited.

105
Nemo WindCatcher User Guide

The user may ‘double click’ on a transition to define the expressions that trigger the transition from
one state to the other:

The ‘expression editor’ can be used to define/modify the expression for the states and transitions:

The attribute selected from the ‘Attributes’ tree appears on the ‘KPI’ column. A function can be
selected from the ‘Functions menu’. The ‘Join’ menu allows the user to select ‘and’ and ‘or’
conditions. Once, all the information is entered select ‘Insert’ to add the condition. The user may
manually type in the information too.

106
 Nemo WindCatcher User Guide

6.14 Root cause for Event Analysis

The Event Analysis option enables the user to configure a set of KPIs for a given window size (in
ms) before and after an event. This information is stored as an XML file which is used by the engine
to process the drive test files. The following window is displayed when the ‘Event analysis’ option is
selected on the ‘Tool’ menu. The user must select the ‘technology’ before creation of an event
analysis.

The ‘root causes’ may be defined as per the steps below:

Step 1: Name the cause and ‘add’ it to the list
Step 2: Define the cause analysis using the ‘Expression Editor’

107
Nemo WindCatcher User Guide

These events will be displayed under the Tools>Event Analysis menu:

108
 Nemo WindCatcher User Guide

6.15 Processing VoLTE data

Make sure both DRM and PCAP files belong the same device are placed in the same folder

Configure “Processing Default”:

Processing tab:
• Select “Enable Packet Trace Analysis” to enable PCAP file associating with DRM file.
• Optional: Select “Import Packet Trace Data” to display packet trace data in message
window. This will not affect call event trigger or custom report results, but will shorten
processing time.

109
 Nemo WindCatcher User Guide

6.15.1 Saving processing default

110
 Nemo WindCatcher User Guide

6.15.2 Create new dataset

First select source DRM data

Save Database:
• In order to generate an end-to-end report, individual database is required to be created
for each device. VoLTE Acceptance Report is pre-configured to generate KPI from
database named with “_A” and “_B”. Therefore, it is required to save processed database
name containing “_A” and “_B” corresponding to each device.

111
 Nemo WindCatcher User Guide

6.15.3 Associating DRM file with PCAP file

1. Select “End-to-End” check box to enable RTP RTT calculation based on source and target
device
2. If DRM/PCAP files were collected based on single device, leave this box un-checked, but
RTP RTT will not be calculated
3. Select appropriate device under “Device/s” section that was used to collect source
DRM/PCAP files
4. Select the folder location of containing source DRM/PCAP file 1
5. Select the folder location containing target PCAP files  2
6. Select to populate source/target selection window below 3
7. Select DRM/PCAP files you would like to associate by checking check boxes in the
selection window  4
8. Once completed, click to begin file processing
9. Once completed, click to begin file processing

112
Nemo WindCatcher User Guide

10. Once finished processing, you should see below map window

113
Nemo WindCatcher User Guide

11. Repeat step 3 to processing and associate target DRM/PCAP files. Notice associating
PCAP files should now be associated in reverse direction as compare to step 4.

12. Below is the map window once finished processing:

114
 Nemo WindCatcher User Guide

6.16 Exploring VoLTE data

6.16.1 Message window

With VoLTE data processed, move cursor to “Message” tab to display message window. You
should notice SIP/RTP messages are now interleaved with LTE L3 messages.

6.16.2 Event window

With VoLTE data processed, move cursor to “Event” tab to display event window. VoLTE specific
events are aligned with LTE call events.

115
 Nemo WindCatcher User Guide

6.16.3 Custom report generation

Once both databases are successfully created, we are ready to generate VoLTE Acceptance Report
Make sure both database with file name containing “_A” and “_B” are opened.
If database name were not saved with “_A” or “_B”, open “VoLTE Acceptance Report” in
My Documents\Keysight Technologies\CustomReport\
Go to “Device Configuration” sheet in VoLTE Acceptance Report, adjust matching dataset name as
explained below.

6.16.3.1 Changing the device ID and dataset name in custom VoLTE acceptance report
Please note the device Id of the device used for drive test (In the above case it is 1) and Dataset
name
Open VoLTE Acceptance report.xlsm custom report located in Documents\Keysight
Technologies\CustomReport.
Change the Device Id column and dataset name available in the Device configuration spreadsheet
with the device id used for the drive test (1 in the above case) of the custom report and save the
xlsm.

116
 Nemo WindCatcher User Guide

6.16.4 Running the VoLTE acceptance report

Go to reports tab in the Nemo WindCatcher.
Click on ‘Open Custom report’ and select the option ‘Open Custom report’.
Select the necessary report from the custom report (VoLTE acceptance report) and click on ‘Ok’ to
run the report.

117
Nemo WindCatcher User Guide

Reports will be generated and will be available for you with all necessary fields populated, which
can be checked and saved for further use.

118
 Nemo WindCatcher User Guide

7 Analysis Features

7.1 Event analysis

The automated event analysis feature is one of the most powerful features in Nemo WindCatcher.
This feature provides the user with the ability to list all occurrences of the most critical customer-
perceived problems in one location.
Furthermore, the conditions before and after these problem events occurred are presented for
each event. This dramatically reduces the time taken to analyze the problem because the laborious
and non-value-added work of gathering this before/after data is automatically done.
Finally, a possible root cause is provided whenever possible using proprietary algorithms.
There are different types of event analysis available under this feature, namely:
• Dropped Calls Analysis
• High BLER/RxQual Analysis
• Blocked Calls Analysis
• Access Failure
To perform any of these analysis, execute the following steps:
Select the Event Analysis icon from Tools tab and select desired analysis.

119
Nemo WindCatcher User Guide

All occurrences of the selected event in the currently active dataset will be listed. An example for
Dropped Calls is shown below:

Click on the desired row to view details on that event below. The details include the conditions
before and after the drop, as well as a suggested root cause (if able to be automatically
determined from acquired data).
All maps and associated docked windows will be synchronized to the event selected. This makes it
very powerful and convenient for drill down analysis of the problem.

The Event Analysis window may also be docked by double-clicking on the top bar or
clicking once on the top bar and dragging the mouse to either the left, right or bottom
edge of the application.

Similarly, to the Event Drop Call Analysis, the Event Block Call Analysis is also available and it
synchronize block calls with the event, layer III, table, replay, and time axis function.

120
 Nemo WindCatcher User Guide

7.2 Delta plots

Delta plot is a powerful feature that provides the flexibility to compare two datasets collected on
the same route either by two handsets or collected by the same hand separately. Using this
option, engineers can compare datasets on the same route under different load condition as well
as comparing the multiple carrier coverage.
To use this feature, execute the following steps:
Select the Delta Plot icon from Views menu, and select New Delta Plot.

The following window will appear:

Select the two dataset / phone combinations and desired metric to compare from the
corresponding drop-down lists.
Specify the geographic bin size or the Time binning method to use. The entire drive test area based
on the selected data will be sectioned into square bins of the specified size. Subsequently, all
points from each set of data will be linearly averaged in each of these bins to be used for the delta
(difference) plot.

121
Nemo WindCatcher User Guide

Select Run. The resulting plot will display the difference between the first set of data and the
second (i.e. Baseline Metrics – Compared Metrics). The units will correspond to the metric selected
for comparison. Statistics will also be presented in the legend that summarizes the differences
calculated between the two sets of data.

The delta map provides the user the ability to export the data as an Excel sheet or create a
PDF/CDF chart. These option will be displayed after a ‘right click’ on the map

122
 Nemo WindCatcher User Guide

Once the delta plot window is opened, the metric being compared may be changed for the same
two sets of data by merely selecting the appropriate metric from the Delta Plot icon. The delta plot
will be recreated on the same map for this new metric.
The user may also create another delta plot window by following steps 1 to 5. There is no limit to
the number of such windows that can be opened, subject to system RAM constraints.
Note that since each data to be compared is specified as a combination of the dataset and phone
id, therefore this supports two types of comparisons, namely, Dataset Deltas and Handset Deltas.
These logical types of comparisons are described in more detail below.

7.2.1 Dataset delta

To perform this type of delta plot analysis, load each dataset separately into Nemo WindCatcher.
Perform the delta plot configuration as described earlier, and select the appropriate datasets under
Data 1 and Data 2. The phone ID will be the same for both data definitions.

7.2.2 Handset delta

To perform this type of delta plot analysis, load the dataset that contains information on the
multiple phones / devices. Perform the delta plot configuration as described earlier, and select the
appropriate Phone IDs under Data 1 and Data 2. The dataset will be the same for both data
definitions.

7.3 Link to bin

The Link Bin to Sector feature provides the ability to view the pilots serving each point along the
drive through lines drawn to the corresponding sectors. Note that this feature can only be utilized
if there are already cells displayed on the map. To use this feature, follow the steps below:
To activate the feature, browse onto Map>To Sector menu and select the option required e.g.:
active sector

123
Nemo WindCatcher User Guide

Now select the bin on the map and Nemo WindCatcher will display the link to the Active Sector:

Each subsequent point selected will result in the lines being redrawn to correspond to the new
point until the feature is turned off.
The user may select a sector and right click to view the ‘link sector to’ options:

The lines may be removed in a number of ways:

• Reselect one or more of the previous selections. This will toggle the lines off for those
selections, and the corresponding lines will be removed from the map.
• Select Remove Link. This will turn off the lines, but the line selections will still be active.
This means that fresh lines will be drawn the next time a selection is made on the map.

124
 Nemo WindCatcher User Guide

7.4 Geo/distance binning

Geo & Distance Binning Maps can be generated on the fly as well after processing data with Time
binning. The options are available under ‘Views’ tab

From the drop down menu of desired binning method, users have to choose the database on which
binning method is supposed to be applied

Once the database selected, the user interface will take the input for desired distance in meters

Click OK after entering desired distance for Area or Distance binning & new map window will open
with desired Area or Distance binned output for analysis.
Users can also select binning method for metric display from the following menu under ‘map’ tab.

This will allow users to change the binning method e.g. Average, Minimum or Maximum value for
that particular bin period.

7.5 Replay
The Replay feature automatically makes a selection move along the map. The Link Bin to Sector
feature need not be activated to use this feature, but is very powerful when combined to visually

125
 Nemo WindCatcher User Guide

capture distant pilot interferers which may otherwise be difficult to capture via other traditional
troubleshooting methods.
The replay is controlled by the Replay icons as shown:

Select the Start replay button to start the replay. Similarly, select the Stop replay, Step forward
and Step backward buttons to stop the replay and manually perform the replay respectively.

The data can be replayed with or without cell site information.

The replay function is fully synchronized with all docked windows and browsers,
including the Phone Data Browser, Message Window, Event Window and any opened
time-series windows for the same dataset.

7.5.1 Replay option

The Replay Speed function may be employed to adjust the Replay speed.

The Synchronization function allows the user to select synchronization of the Replay function with
the Message Data, Event Data Tree, Time Series Chart and Tabular Data. Just click on all
mentioned Data options, once the option becomes highlighted, it will be synchronized with the
replay.

126
 Nemo WindCatcher User Guide

7.6 Neighbor list analysis

Neighbor list analysis can be launched from ‘Tools’ tab. This feature can be used to determine
missing neighbors from the collected data.

This tool can be used with or without cell file in the background. Once the user clicks on above
icon, an analysis window will appear as below. If the cell file is already in the background then it
will appear in the sector field automatically & in case UE it will be used for missing neighbor
analysis as well. If the cell site file is not in the background then sector field will remain blank &
analysis will be performed based on collected information only.

127
 Nemo WindCatcher User Guide

Default criteria can be modified by user such as serving CINR & neighbor CINR threshold values for
example in case of LTE neighbor analysis. Once the values are set, User needs to click on Run
Analysis & a detailed report will be generated which can be exported in Excel as well.

7.7 RF analysis
RF analysis can be launched from ‘Tools’ tab. This feature can be used to summarize RF data for a
dataset

RF analysis displays the window below where the user observes data for each serving PN/PSC/PCI

128
 Nemo WindCatcher User Guide

User may select a specific serving parameter and plot the list of metrics available in the drop down
on the map.

7.8 Reports

7.8.1 Predefined report templates

The reports menu allows user to run an array of pre-defined reports and custom reports. Nemo
WindCatcher provides pre-defined reports for CDMA, GSM/UMTS, and iDEN technologies. In
addition various custom reports are available for CDMA, GSM/UMTS, iDEN and LTE. The most
commonly used custom report is the ‘Pre-post’ report (CDMA/EVDO/LTE) which is created as per
the procedure defined below:
The Pre-post template is located under Start> My Documents>Keysight Technologies folder.
Consider the example below for pre-post report creation:

129
Nemo WindCatcher User Guide

1. Create a pre dataset:

Process the pre-drive data in Nemo WindCatcher and save the database e.g.: Pre.mdb. Note the
‘Device Id’ of the pre devices by browsing onto the ‘DatasetInfo’ tab on the left side of the map:

2. Create a post dataset:

Process the pre-drive data in Nemo WindCatcher and save the database e.g.: Post.mdb. Note the
device ID of the post device by browsing onto the ‘DatasetInfo’ tab.
3. Template Update:
Open the report template and browse onto the ‘Device Mapping’ tab.
Enter the ‘Dataset’ and ‘Device ID’ information from steps 1 and 2
Save and close the Template.
For every new creation of the pre-post report, the user would need to enter information in the
‘device mapping’ tab of the template.

130
 Nemo WindCatcher User Guide

4. Open the two (pre and post) datasets in Nemo WindCatcher. Browse onto Reports>Open
Custom Report and browse onto the template that was saved in Step 3

The report generated will open in Excel.

7.8.2 Zoom option in reports

For a specific zoom that would be uniform throughout the report for image plots, open that
particular custom report before generating and select IMAGE DATA tab:
• Image data: cell A1, type in ‘zoom’. This will pick up the zoom from the current opened
dataset. This works similarly for custom report utility. This does not work for WPCM

131
 Nemo WindCatcher User Guide

• Option 2: A1: type in ‘zoom:200:meters’ . This will allow user to define the zoom level. This
will pick up the narrower width and zoom it. This works for all options of custom reports.
Currently, we support only meter, miles and kilometer.
• Above options do not work for WPCM.

7.8.3 Report builder

In Nemo Windcatcher there is a report builder feature with which it is possible to create custom
reports by dragging and dropping the metrics, events and map plots to empty excel template. The
template can be saved to be used to generate customized reports for other datasets.

7.8.3.1 Opening the Custom Report designer

Under the “Reports” tab there is a new icon to open the Report Designer window to create the
Custom Report:

132
 Nemo WindCatcher User Guide

Following window should now open:

7.8.3.2 Selecting the metrics

In the left hand side of the Report Designer window there are menus for Metrics and for Events.
The menus can be expanded from the “+“tab to get the technology specific menus for metrics and
events.

133
Nemo WindCatcher User Guide

By further expanding you can get the actual metrics and events visible to select the ones to be
used in the report template.

134
Nemo WindCatcher User Guide

Now you can just drag and drop the wanted metric to the template. You can select multiple
metrics with the different metric type to the same template.
After you have selected the metric or event you must complete the metric and device settings.
After dropping the Metric to one of the cells the settings window will appear to the right-hand side
of the window

You need to select the data set and device from the Device Database or from Label or from ID
scroll-down menus. After doing that the data base, device ID and the device label will be shown in
the menu windows
You also need to select the type of the metric to be shown in the report. The selection can be made
from the Metric type drill-down menu. There are totally 14 different types to select:
• Average,
• Count (Number of samples)
• Sum
• Minimum
• Maximum
• Standard deviation
• Mode
• Median
• Histogram
• Multimetric
• Value
• All value
• List

With the multimetric option you can select the multiple simultaneous metrics to be shown side by
side in the worksheet. For the selected metric the record_index, phone_id, latitude, longitude, and
time are populated from the bin_data table in the database. When using the multimetric type, it
must be selected for the first metric dragged to the worksheet and the rest of the metrics can be
dragged and dropped onto any of the cells in the multimetric row.

135
Nemo WindCatcher User Guide

When adding metrics for the multimetric view the added metrics are also shown in the Metric
setting menu in the right-hand side of the window. The first selected metric is the most upper one
in the window and the added ones can be seen in Multiple Metrics window.

If you want to plot the “Histogram” for the selected metric you must give the highest value, lowest
value and the step size into the metric setting menu. You cannot proceed with the histogram if you
haven’t given those as an input. After selecting the data set / device for the histogram the
Histogram setting menu is shown and the inputs can be given.

With “Histogram” it is also possible to show the distribution of the values as a pie chart. After
giving the values for Max, Min and Step you need to click “Preview” and then the pie chart icon at
the top of the Metric setting menu.

136
 Nemo WindCatcher User Guide

Pie chart should now be visible and it can be re-sized or re-located for the report template.
If the “Value” is selected as a metric type, all the metric values with the actual measurement data
in a bin are shown whereas with “AllValue” selected also the bin values with the default value are
shown in the case that the bin does not have actual measurement value.

7.8.3.3 Inserting a map to the report template

You can insert also the map plots for selected metrics and events to the template. After dragging
and dropping the metric or event you need to click the “Map” icon on the top of the Metric setting
pane and the place holder for the map and the expanded metric menu are shown with some
additional map settings. Just like with the regular metric plotting the data set / device selection is
needed for the map plots.

For the map plot, you need to select the threshold to get the correct legend with the pre-defined
thresholds. Open the drill down menu for the thresholds and select the one for the selected metric
(RSRP in this example).

137
 Nemo WindCatcher User Guide

You can change the location of the map plot in the template by first clicking on the “Location” field
in the Metric setting menu and then clicking the new cell location on the work sheet. You can also
re-size the map plot area. Again, first click on the “Location” field in the Metric setting menu. Then
select the cell where the metric is and paint the wanted cells to get the wanted size.

7.8.3.4 Conditions
For the metrics and map plots there are pre-defined conditions to be used if you want to see only
some range of the metrics. Open the “Condition” drill-down menu, select the wanted condition(s)
and set the values.

138
 Nemo WindCatcher User Guide

If there is a need for additional conditions needed customer can create also own conditions.

7.8.3.5 Saving the report template and running the report

During the creation of the report template, before saving it, it is possible to use the Preview –
functionality to check the report template. You can either preview just one metric or plot at the
time or you can preview all items you have inserted to the template.
To save the template just click the icon, browse the location and give the name to the template.
Running the report follows the same procedure used with the predefined standard report
templates – go to reports, open custom report and run it.

If this custom template is used to create the report for some other dataset you must re-
select the devices for each of the metrics or maps in the template. This must be done in
order to link the template to correct dataset.

139
 Nemo WindCatcher User Guide

8 Project Manager

8.1 Introduction to Project Manager Module

Project Manager is a functionality introduced in Nemo WindCatcher for processing folder based
drive test data. This will allow users to select the root folder and all the data available in the sub
folders will be processed automatically. A database is created for data in each subfolder. The
databases will be named based upon the root and subfolder names and stored along with the raw
files in their respective folders. To use the project manager, follow the below steps:
1. Launch Project Manager from the home tab,

2. Scan the root folder containing raw drive test data in subfolders

140
Nemo WindCatcher User Guide

3. Scan function will automatically scan all the subfolders and create separate groups for
each subfolder for processing.

4. Click “Select All Data” tab and click “Process All Data” for creating datasets for the
complete set of raw data. User can also selectively process data by selecting individual
files and click “Process Selected Data”
5. Once all the data is processed user can view the dataset using “Dataset” tab

141
Nemo WindCatcher User Guide

6. To add background files and cell sites use the “Supporting Files” tab

7. To run a custom report for all datasets or selective datasets use Dataset tab available at
the left top.

8. Click Custom Report (All Datasets) for providing custom report template which can run
over all processed datasets. To selectively run report on datasets, select the datasets
individually and click Custom Report (Selected Datasets) for providing template.
9. The projects which are processed using the project manager will be saved as workspace
and can be assessed if related datasets are available at the desired location.
10. While importing background or cell files users can create new filters by using “Add New
Filter” option

142
 Nemo WindCatcher User Guide

8.2 iBwave cell sites

Nemo WindCatcher has introduced feature to create cell sites/nodes for in-building data using
IBwave exported “xml” files. Use the below steps for creating IBwave cells.
1. Select “iBwave Inbuilding Cell Site” option from the home tab

2. Select the appropriate technology for cell sites

3. Import iBwave exported xml file using “Open” option.

4. Click “Create Sector Tab File” and provide location and name for the tab file.

143
Nemo WindCatcher User Guide

5. A new window will open to preview the newly created cell sites

6. Use Background, Layer Control or Default cell sites to import the cell sites on interface.

144
 Nemo WindCatcher User Guide

8.3 Cell site alignment

Nemo WindCatcher has introduced a new feature for in-building cells to align with the background
map using the offset controls in case they were not properly mapped during data collection.
• Click the “Use offset controls” and click “Select all cell sectors”

• Depending upon the offset required, choose the appropriate “Offset step (meters) using
the drop down.
• Click the arrow button to move the entire layer and align it with the background map
• User can also move individual sites by selecting the appropriate rows for cells and use the
offset button to move.
• New positions will be marked with blue and original with red plus signs.

• To make the new location permanent click “Apply Changes” and “Create Sector Tab File”.

145
 Nemo WindCatcher User Guide

9 Client Server

9.1 Overview
With Client Server functionality, it is possible to autonomously process data and generate reports
on the server side. The server can be used also as a centralized repository to store log files,
processed datasets and reports to be shared with multiple users.

9.2 Setting-up the server

On the server side, there must be Nemo WindCatcher installed with the Automation feature license
and with the Client Server feature license. The available features can be checked from the licence
manager in the upper right-hand corner.

146
 Nemo WindCatcher User Guide

9.2.1 Creating the folder structure

On the server side, the client server functionality utilizes the Automation function within the Project
Manager Module. To be able to automatically process the log files there must be a certain folder
structure for Workspaces and Projects. There must be a root folder – Scan Folder in PM - under
which there must be hierarchically two additional sub-folders for the Workspace and for the
Projects. The log files, processed data sets and reports will be uploaded and stored in the project
folder. There can be multiple Workspace folders and Project folders under the Root folder.

When setting up-the Scan Folders first time you must copy at least one measurement
file to the Project folder. It is highly recommended that you create a “Test Project” folder
for that purpose and to not use that folder when uploading measurement files later from
the client side.

9.2.2 Enabling the Client Server functionality

After creating the Scan folders, open the Nemo Windcatcher application on the server side. Then
open the Project Manager (1) and select the Automation tab (2). Before starting the monitoring,
you need to add the Scan Folder (3). Browse now to the location where you created the root folder
and select the root folder you created. Now the folder structure has been set-up.

147
Nemo WindCatcher User Guide

Last steps to be able to use the Client Server functionality from the client side are to start
monitoring the folders (4) and to start the server (5).
The progress of the processing on the server side can be checked from the Run Time Log.

148
 Nemo WindCatcher User Guide

9.3 Client – Project Repository

9.3.1 Overview
In the Project Repository window, you can browse the projects on the server and through it you
can also download raw files, databases and reports.

9.3.2 Connecting to the server

On the client side, the client server connection can be established from the Project Repository view
which can be opened by clicking “Server Repository” (2) icon under the Home tab (1). In the
Project Repository window after clicking the “Settings” icon (3) you can set the IP address and set
the port 8080 (4) to connect to the server.

The connection to the server can be tested and if it is successful the notification is shown in green.
Clicking “OK” will close the Server Setting view to return to the Project Repository view and the
status of the connection is shown in the bottom left-hand corner of the view.

149
 Nemo WindCatcher User Guide

The project view can be refreshed by clicking the icon next to the settings icon.
In the Project Repository window, you can browse the projects on the server and through it you
can also download raw files, databases and reports.

9.3.3 Data Upload Manager

The measurement files, associated report templates and pre-processed datasets (Access - .mdb
or SQLite - .xdb) can be uploaded to the server through the Data Upload Manager. Open the Data
Upload Manager by clicking the “Upload Data” icon at the top right-hand corner of the Project
Repository window.

Select the Workspace and the Project folders (1). They can be selected based on the folder
structure created on the server site under the Root folder. For adding the measurement data files
click “Add Data File” (2) and browse to location to select the files. You can also upload report
templates along with measurement data files (3) to generate report(s) or add report templates later
after the measurement files have been processed and the dataset has been created. To start the
uploading of the selected files and templates just click the “Upload” icon. There will be “check”
sign ( ) after the file name indicating that the upload of the file has been completed.

Instead of manually picking-up and adding the data files and report templates to the server there
is a “Scan Folder” option which can be used. You need to create a folder structure to your local
computer from where the files will be uploaded to the server. If the naming of the folders under the
“Scan folder” in the local machine differs from the folder naming on the server side, the folder
structure (with naming) will be copied to the server under the root folder.

150
 Nemo WindCatcher User Guide

9.3.4 E-mail notification

You can set the e-mail notifications to be sent to a pre-defined e-mail group (subscribe to the
project) to notify that the log files have been processed and that the report is available. The e-mail
groups can be created through e-mail settings in the Data Upload Manager window.

When creating an e-mail group there is an option whether the generated report(s) are to be
attached to the notification e-mail. You can add the e-mail address manually or using search
function for a specific address book.

After creating the e-mail group, it will be selectable in the Email Group drill-down menu in the
Data Upload Manager window.
You can also set the root level email-group(s) on the server side. Those e-mail group(s) can be
created and modified under the Automation menu within Project Manager.

The e-mail groups created on the client side are not editable on the server side.

151
 Nemo WindCatcher User Guide

9.4 FTP Server Upload

There is an option to connect the Windcatcher server machine to an FTP server and pull data from
there to be processed by Nemo Windcatcher on the server side.
In the FTP server, there must be similar root folder structure like with “Scan Folder” option
described in the previous section. The data in the Root folder must be organized in the Workspace
– Project folder hierarchy (all file in the project folder will be processed).

The FTP connection is available under the Automation menu within the Windcatcher Project
Manager window.

The FTP server settings will allow users to set the IP address, user credentials and the Root folder
on the FTP server to monitor. After entering the Server details click “Apply” (1). Then select the
root folder and click “Start Download” (2). Now after the data has been downloaded from the FTP
server the processing will start automatically on the Windcatcher sever side.

9.5 Deleting files

When there is a need to delete files from the Windcatcher server, the monitoring of the scan folder
and the server needs to stopped using the “Stop Monitor” and the ‘Stop Server’ button respectively
available under the Automation menu.

Next
step is to browse to the root folder on the server and delete the files from there. After deleting the

152
Nemo WindCatcher User Guide

files, you must come back to the Automation menu and click the” Clean Up” tab to finalize the
clean-up Once the desired clean-up is done, you can click on ‘Start Monitor’ and ‘Start Server’.

153
 Nemo WindCatcher User Guide

10 Appendix A: Supported Drive Test Formats

The following drive test formats are currently supported in Nemo WindCatcher for CDMA/EVDO,
GSM/UMTS, and LTE:
• JDSU SD5, AOD, AHD
• Andrew
• ASCOM Route reader
• Comarco
• TEMS Pocket, Symphony, Investigation
• Nemo Handy, Outdoor
• PCTel Insite, SeeGull, Clarify, EX DTR
• Qualcomm DM, ISF(QXDM), MobileView, QCHAT5.0
• Rhode & Schwartz Romes
• Spirent UDM
• Swissqual
• ZK
• Ericson – UETR reverse link support.
• Xcal/Accuver
• LG/LLDM
• Datapro
• Keysight
• Invex
• Wireless Pro
• Anritsu
• Wider Scanner
• Dingli
• LG LLDM

154
 Nemo WindCatcher User Guide

11 Appendix B: LTE Metrics

LTE Phone/Scan Data:

Dominant Channel RSSI (dBm):

RSSI is defined Received Signal Strength Indicator. A measurement defined as the total received
wideband power observed by a UE from all sources, including co-channel serving and non-serving
cells, adjacent channel interference and thermal noise within the measurement bandwidth. For
LTE, it is not reported as an independent measurement, but is an input to the derivation of RSRQ. If
there is more than one channel available, the Dominant Channel RSSI will be defined as RSSI for
dominant channel.
Dominant Channel RSSI-Tx1Rx1:
RSSI on tranmitter1 and receiver 1

155
Nemo WindCatcher User Guide

Dominant Channel RSSI-Tx1Rx2:

RSSI on tranmitter1 and receiver 2
Dominant Channel EARFCN:
An ARFCN defines a pair of Radio Frequency (RF) channel frequencies for uplink and downlink use.
EARFCN is defined as E-UTRA Absolute Radio Frequency Channel Number and is based on a 100-
kHz channel raster.
RSSI by Channel:
This metric will allow user to plot RSSI based on available channels.
Dominant PCI:
This metric will allow user to plot the dominant Cell ID.
RSRP (dBm):
Reference Signal Received Power (RSRP) is defined as a measurement which provides cell-specific
signal strength metric. This measurement is mainly used to rank different LTE cells according to
their signal strength as an input for handover and cell reselection decisions. The RSRP of a cell is
defined as the linear average over the power contributions (in Watts) of the Resource Elements
(REs) which carry cell-specific RS within the considered measurement bandwidth.
Dominant RSRP:
Defined as the maximum value of RSRP available across serving and neighbor PCI’s. It can be
further defined for each antenna combinations such as Dominant RSRP - Tx1Rx1, which will
provide RSRP for the combination of transmitter 1 and receiver 1
RSRQ:
Reference Signal Received Quality (RSRQ) is defined as a measurement which provides a cell-
specific signal quality metric. Similarly, to Reference Signal Received Power (RSRP), this
measurement is mainly used to rank different LTE cells according to their signal quality as an input
for handover and cell reselection decisions, for example in scenarios for which RSRP
measurements do not provide sufficient information to perform reliable mobility decisions. The
RSRQ is defined as the ratio N · RSRP/ (LTE carrier RSSI), where N is the number of Resource
Blocks (RBs) of the LTE carrier Received Signal Strength Indicator (RSSI) measurement bandwidth.
While RSRP is an indicator of the wanted signal strength, RSRQ additionally takes the interference
level into account due to the inclusion of RSSI. RSRQ therefore enables the combined effect of
signal strength and interference to be reported in an efficient way. If the UE is equipped with
multiple antennas, the reported RSRQ value is not permitted to be lower than the RSRQ computed
on the individual branches.
Dominant RSRQ:
Defined as the maximum value of RSRQ available across serving and neighbor PCI’s. It can be
further defined for each antenna combinations such as Dominant RSRQ - Tx1Rx1, which will
provide RSRQ for the combination of transmitter 1 and receiver 1.
RS CINR (dB):
Reference Signal Carrier-to-Interference-and-Noise Ratio is the ratio between the power of the
Radio Frequency (RF) carrier bearing the wanted signal and the total power of interfering signals
and thermal noise.
Dominant CINR:
Defined as the maximum value of CINR available across serving and neighbor PCI’s. It can be
further defined for each antenna combinations such as Dominant CINR - Tx1Rx1, which will
provide CINR for the combination of transmitter 1 and receiver 1
Dominant PSS RSSI:
This metric will provide RSSI of the dominant PSS. Primary Synchronization Signal is a sequence
transmitted by every LTE cell every 5 ms; it allows the UE to obtain slot synchronization and part of
the physical layer cell Identifier (cell ID). Three different sequences exist with a one-to-one
mapping to three different cell IDs within each of 168 groups of cell IDs. The PSS is based on
Zadoff-Chu (ZC) sequences

156
Nemo WindCatcher User Guide

Dominant PSS Quality:

This metric will provide quality of the dominant PSS. Primary Synchronization Signal is a sequence
transmitted by every LTE cell every 5 ms; it allows the UE to obtain slot synchronization and part of
the physical layer cell Identifier (cell ID). Three different sequences exist with a one-to-one
mapping to three different cell IDs within each of 168 groups of cell IDs. The PSS is based on
Zadoff-Chu (ZC) sequences
Dominant SSS RSSI (dBm):
This metric will provide RSSI of the dominant SSS. Secondary Synchronization Signal is used by
the UE to detect the LTE frame timing and to obtain the physical layer cell identity group. It is
transmitted twice in each 10 ms frame. The SSS sequences are based on maximum length
sequences, known as M-sequences. Each SSS sequence is constructed by interleaving, in the
frequency-domain, two length-31 Binary Phase Shift Keying (BPSK)-modulated sequences. These
two codes are two different cyclic shifts of a single length-31 M-sequence. The cyclic shift indices
of the M-sequences are derived from a function of the physical layer cell identity group. The two
codes are alternated between the first and second SSS transmissions in each radio frame. This
enables the UE to determine the 10 ms radio frame timing from a single observation of a SSS.
Dominant SSS Quality:
This metric will provide quality of the dominant SSS. Secondary Synchronization Signal is used by
the UE to detect the LTE frame timing and to obtain the physical layer cell identity group. It is
transmitted twice in each 10 ms frame. The SSS sequences are based on maximum length
sequences, known as M-sequences. Each SSS sequence is constructed by interleaving, in the
frequency-domain, two length-31 Binary Phase Shift Keying (BPSK)-modulated sequences. These
two codes are two different cyclic shifts of a single length-31 M-sequence. The cyclic shift indices
of the M-sequences are derived from a function of the physical layer cell identity group.
The two codes are alternated between the first and second SSS transmissions in each radio frame.
This enables the UE to determine the 10 ms radio frame timing from a single observation of a SSS.
Dominant Sync CINR:
This metric will provide dominant synchronized carrier to interference and noise ratio.
Dominant Sync Time Offset:
This metric will provide dominant sync timing offset in seconds.
Dominant Sync Quality (dB):
This metric will provide dominant synchronized RSRQ.
Dominant PSS CINR (dB):
This metric will provide CINR of the dominant PSS. Primary Synchronization Signal is a sequence
transmitted by every LTE cell every 5 ms; it allows the UE to obtain slot synchronization and part of
the physical layer cell Identifier (cell ID). Three different sequences exist with a one-to-one
mapping to three different cell IDs within each of 168 groups of cell IDs. The PSS is based on
Zadoff-Chu (ZC) sequences.
Dominant SSS CINR (dB):
This metric will provide CINR of the dominant SSS. Secondary Synchronization Signal is used by
the UE to detect the LTE frame timing and to obtain the physical layer cell identity group. It is
transmitted twice in each 10 ms frame. The SSS sequences are based on maximum length
sequences, known as M-sequences. Each SSS sequence is constructed by interleaving, in the
frequency-domain, two length-31 Binary Phase Shift Keying (BPSK)-modulated sequences. These
two codes are two different cyclic shifts of a single length-31 M-sequence. The cyclic shift indices
of the M-sequences are derived from a function of the physical layer cell identity group. The two
codes are alternated between the first and second SSS transmissions in each radio frame. This
enables the UE to determine the 10 ms radio frame timing from a single observation of a SSS.

157
Nemo WindCatcher User Guide

Dominant BCH RSSI (dBm):

This metric will provide RSSI of dominant BCH. Broadcast Channel is defined as the transport
channel carrying broadcast system information except that which is contained in the Master
Information Block (MIB).
Dominant Cell Distance:
This metric will plot distance from selected bin to dominant physical cell identity.
Dominant RSSI:
This metric will provide RSSI of the dominant physical cell identity. RSSI is defined Received Signal
Strength Indicator. A measurement defined as the total received wideband power observed by a
UE from all sources, including co-channel serving and non-serving cells, adjacent channel
interference and thermal noise within the measurement bandwidth. For LTE, it is not reported as
an independent measurement, but is an input to the derivation of RSRQ. If there is more than one
channel available, the Dominant Channel RSSI will be defined as RSSI for dominant channel.
Transmit Power:
This metric will provide UE transmit power

PUSCH Tx Power:
This metric will provide physical uplink shared channel transmit power.
PUCCH Tx Power:
This metric will provide physical uplink shared channel transmit power.
PRACH Tx Power:
This metric will provide physical random access channel transmit power.
Tx Power Headroom:
The power headroom (PH), expressed in dB. It is the difference between the configured maximum
UE output power and the estimated power for PUSCH transmission.
Wideband Metric:
The Wide Band Metric will provide the plot as observed by the UE over the entire channel
bandwidth.

158
Nemo WindCatcher User Guide

159
Nemo WindCatcher User Guide

Sub band Metric:

The Sub Band Metric will provide the plot metrics according to the collection of n adjacent Physical
Resource Blocks (PRBs) where the value of n can be 2, 3, 4, 6, or 8 depending on the channel
bandwidth.

160
Nemo WindCatcher User Guide

Serving Channel Info:

Serving Channel RSSI:

This metric will provide RSSI of the serving channel.
Frequency Band:
This metric will provide the frequency band of received signal.
DL Tx Frequency:
This metric will provide downlink transmit frequency.
UL Tx Frequency:
This metric will provide uplink transmit frequency
DL EARFCN:
This metric will provide downlink EARFCN. An ARFCN defines a pair of Radio Frequency (RF)
channel frequencies for uplink and downlink use. EARFCN is defined as E-UTRA Absolute Radio
Frequency Channel Number and is based on a 100 kHz channel raster.
UL EARFCN:
This metric will provide uplink EARFCN. An ARFCN defines a pair of Radio Frequency (RF) channel
frequencies for uplink and downlink use. EARFCN is defined as E-UTRA Absolute Radio Frequency
Channel Number and is based on a 100 kHz channel raster.
DL Bandwidth:
This metric will provide downlink bandwidth for serving channel.
UL Bandwidth:
This metric will provide uplink bandwidth for serving channel.
DL Bandwidth (Resource Block):
This metric will provide downlink resource block. Resource block is a unit of transmission resource
consisting of 12 subcarriers in the frequency domain and 1 timeslot (0.5 ms) in the time domain.
UL Bandwidth (Resource Block):
This metric will provide uplink resource block. Resource block is a unit of transmission resource
consisting of 12 subcarriers in the frequency domain and 1 timeslot (0.5 ms) in the time domain.

161
Nemo WindCatcher User Guide

Serving Cell Info:

Serving PCI:
This metric will provide the physical cell identity of the serving cell.
Serving Sector:
This metric will provide serving cell name.
DL Bandwidth:
This metric will provide downlink bandwidth of the serving channel.
UL Bandwidth:
This metric will provide uplink bandwidth of the serving channel.
Cell Antenna Count:
This metric will provide number of antenna available in the cell
DL CP Type:
This metric will provide the cyclic prefix type on downlink. This can be normal or extended.
UL CP Type:
This metric will provide the cyclic prefix type on uplink. This can be normal or extended.
Distance (Miles):
This metric will provide the distance of the UE from the serving PCI.
Path Loss:
This metric will provide Path-Loss. Path loss is defined as the attenuation of an electromagnetic
wave as it propagates through free space. In LTE, each UE measures the path-loss based on the
serving cell’s Reference Signals (RSs) by averaging measurements of the downlink Reference
Signal Received Power (RSRP). This is used to determine the uplink transmission power needed to
compensate for some or all of the path-loss.

162
Nemo WindCatcher User Guide

Serving RS Info:

Serving RS CINR:
This metric will provide CINR for serving PCI.
Serving RSRP:
This metric will provide RSRP for serving PCI.
Serving RSRQ:
This metric will provide RSRQ for serving PCI.
Serving RF Quality:

163
Nemo WindCatcher User Guide

Transmission Mode:
This metric will provide available Transmission mode.
MIMO Mode:
This metric will provide serving MIMO mode. MIMO is defined as Multiple-Input Multiple-Output. A
transmission scheme between a transmitter and a receiver both equipped with multiple antennas.
CQI Ant0:
This metric will provide CQI information for Antenna 0. Channel Quality Indicator. Information
signaled by a UE to the base station to indicate a suitable data rate (typically a Modulation and
Coding Scheme (MCS) value) for downlink transmissions, usually based on a measurement of the
received downlink Signal to Interference plus Noise Ratio (SINR) and knowledge of the UE’s
receiver characteristics.
CQI Ant1:
This metric will provide CQI information for Antenna 1. Channel Quality Indicator. Information
signaled by a UE to the base station to indicate a suitable data rate (typically a Modulation and
Coding Scheme (MCS) value) for downlink transmissions, usually based on a measurement of the
received downlink Signal to Interference plus Noise Ratio (SINR) and knowledge of the UE’s
receiver characteristics.
CQI Index Ant0:
This metric will provide CQI index for Antenna 0.
CQI Index Ant1:
This metric will provide CQI index for Antenna 1.
Wideband CQI:
This metric will provide CQI of the complete band.

164
Nemo WindCatcher User Guide

Transmission Max Rank:

This metric will provide Rank Count. Rank count is signaled to the eNodeB by UEs configured for
Physical Downlink Shared Channel (PDSCH) transmission modes 3 (open-loop spatial multiplexing)
and 4 (closed-loop spatial multiplexing). It corresponds to the number of useful transmission layers
for spatial multiplexing (based on the UE’s estimate of the downlink channel), enabling the eNodeB
to adapt the PDSCH transmissions accordingly
PMI:
This metric will provide Pre coding Metric Index.
RLC UL ReTx (%):
This metric will provide us with the uplink
Scheduling Grant Info:

Avg DL TB0 Size:

This metric will provide average downlink transport block size for stream 0.
Avg DL TB1 Size
This metric will provide average downlink transport block size for stream 1.
Avg DL TB Size
This metric will provide average downlink total transport block size.
Avg UL TB Size
This metric will provide average uplink total transport block size.
Avg DL PRB Assignment
This metric will provide Average Downlink Physical Resource Block Assignment. A unit of
transmission resource consisting of 2 sub-carriers in the frequency domain and 1 timeslot (0.5 ms)
in the time domain.

Avg UL PRB Assignment

This metric will provide Average Uplink Physical Resource Block Assignment. The unit of
transmission resource consisting of 2 sub-carriers in the frequency domain and 1 timeslot (0.5 ms)
in the time domain.

165
Nemo WindCatcher User Guide

MCS Info:

Dominant DL TB0 MCS

This metric will provide dominant MCS index for transport block 0 on downlink.
Dominant DL TB1 MCS
This metric will provide dominant MCS index for transport block 1 on downlink.
Dominant DL TB0 Modulation Type
This metric will provide dominant Modulation type for transport block 0 on downlink. This
modulation could be QPSK, 16 QAM or 64 QAM.
Dominant DL TB1 Modulation Type
This metric will provide dominant Modulation type for transport block 1 on downlink. This
modulation could be QPSK, 16 QAM or 64 QAM
Dominant UL TB MCS
This metric will provide dominant MCS index for transport block on uplink.
Dominant UL TB Modulation Type
This metric will provide dominant Modulation type for transport block on uplink. This modulation
could be QPSK, 16 QAM or 64 QAM
DL TB0 Modulation Type Utilization
This metric will provide time utilized in a bin by specific modulation type (QPSK, 16 QAM, and 64
QAM) for transport block 0 on downlink.
DL TB1 Modulation Type Utilization

166
Nemo WindCatcher User Guide

This metric will provide time utilized in a bin by specific modulation type (QPSK, 16 QAM, and 64
QAM) for transport block 1 on downlink.
UL TB Modulation Type Utilization
This metric will provide time utilized in a bin by specific modulation type (QPSK, 16 QAM, and 64
QAM) for transport block on uplink.
Most Used DL TB0 Modulation Type per Serving PCI
This metric will provide for modulation type for selected serving PCI on downlink for transport
block 0.
Most Used DL TB1 Modulation Type per Serving PCI
This metric will provide for modulation type for selected serving PCI on downlink for transport
block 1
Most Used UL TB Modulation Type per Serving PCI
This metric will provide for modulation type for selected serving PCI on uplink for transport block.
Nth Used DL TB0 Modulation Type
This metric will provide Nth best used modulation type for transport block 0 on downlink.
Nth Used DL TB1 Modulation Type
This metric will provide Nth best used modulation type for transport block 1 on downlink.
Nth Used UL TB Modulation Type
This metric will provide Nth best used modulation type for transport block on uplink.
Neighbor Cell Info:

PCI of Nth Best neighbor per RSRP

This metric will provide Best Neighbor PCI based on RSRP
RSRP of Nth Best Neighbor
This metric will provide RSRP of Neighbors based on strongest to weakest levels.
PCI of Nth Best Neighbor per RSRQ
This metric will provide Best Neighbor PCI based on RSRQ
RSRQ of Nth Best Neighbor
This metric will provide RSRQ of Neighbors based on strongest to weakest levels.
Total Number of Detected Neighbors
This metric will provide total numbers of available neighbors

167
Nemo WindCatcher User Guide

State Info:

EMM State
This metric will provide EMM information. Evolved Packet System Connection Management is a
Non-Access Stratum (NAS) state which reflects whether a UE is registered with the Mobile
Management Entity (MME) – either ‘registered’ or ‘deregistered’.
EMM Sub State
This metric will provide Evolved Packet System Connection Management sub state.
EMM Mode
This metric will provide Evolved Packet System Connection Management sub state mode.
RRC State
A UE is in RRC_CONNECTED when an RRC connection has been established. If this is not the case,
i.e. no RRC connection is established, the UE is in RRC_IDLE state
PLMN State
This metric will provide public land mobile network state.
RRC Cell Selection State
This metric will provide RRC Selection state.
UE Identification:

Serving MCC
This metric will provide serving Mobile Country Code (MCC) information. The MCC identifies
uniquely the country of domicile of a mobile subscriber. It consists of three digits. In LTE, it is used

168
Nemo WindCatcher User Guide

in the construction of network entity related identities such as the E-UTRAN Cell Global Identifier
(ECGI), the Global eNodeB Identifier and the Tracking Area Identity (TAI).
Serving MNC
This metric will provide serving Mobile Network Code (MNC) information. In conjunction with the
Mobile Country Code (MCC), the MNC uniquely identifies a mobile network operator/ carrier. In
LTE, it is used in the construction of network entity related identities such as the E-UTRAN Cell
Global Identifier (ECGI), the Global eNodeB Identifier, and the Tracking Area Identity (TAI).
Serving TAC
This metric will provide Tracking Area Code (TAC) information. The TAC is part of the Tracking Area
Identity (TAI). It is a 16-bit integer.
Serving TAI
This metric will provide Serving Tracking Area Identity (TAI) information. This is the identity used to
identify tracking areas. It is composed of a Tracking Area Code (TAC), a Mobile Network Code
(MNC) and a Mobile Country Code (MCC).
GUTI
This metric will provide Globally Unique Temporary Identity (GUTI). This is an unambiguous
identification of the UE that does not reveal the UE or the user’s permanent identity in the Evolved
Packet System (EPS). It also allows the identification of the Mobility Management Entity (MME) and
network.
S-TMSI
This metric will provide System Architecture Evolution - Temporary Mobile Subscriber Identity. The
S-TMSI is a unique identifier assigned to the UE by the Mobility Management Entity MME) to
identify the UE context while supporting subscriber identity confidentiality.

IMSI
This metric will provide International Mobile Subscriber Identity. A unique number associated with
each mobile phone user. It is stored in the SIM inside the phone and is sent by the phone to the
network. It is primarily intended for obtaining information on the use of the Public Land Mobile
Network (PLMN) by subscribers.

Data Throughput:

Physical DSCH Throughput

This metric will provide Physical Downlink Shared Channel throughput. The main downlink data
bearing channel in LTE. It is used for all user data, as well as for broadcast system information
which is not carried on the Physical Broadcast Channel (PBCH), and for paging messages.

169
Nemo WindCatcher User Guide

Physical USCH Throughput

This metric will provide Physical Uplink Shared Channel throughput. The LTE uplink physical
channel carrying scheduled data traffic and control signaling if some is required to be transmitted
in the same sub frame.
MAC DL Throughput
This metric will provide Medium Access Control (MAC) layer downlink throughput. This sub layer is
above the physical layer and below the Radio Link Control (RLC) layer in the LTE protocol stack.
The connection to the physical layer below is through transport channels, and the connection to
the RLC layer above is through logical channels. The MAC layer performs data transmission
scheduling and multiplexing/de-multiplexing between logical channels and transport channels. In
the UE, it is also responsible for control of random access, timing advance and discontinuous
reception.
MAC UL Throughput
This metric will provide Medium Access Control (MAC) layer uplink throughput. This sub layer is
above the physical layer and below the Radio Link Control (RLC) layer in the LTE protocol stack.
The connection to the physical layer below is through transport channels, and the connection to
the RLC layer above is through logical channels. The MAC layer performs data transmission
scheduling and multiplexing/de-multiplexing between logical channels and transport channels. In
the UE, it is also responsible for control of random access, timing advance and discontinuous
reception.
RLC DL Throughput
This metric will provide Radio Link Control (RLC) downlink throughput. The RLC layer is located
between the Packet Data Convergence Protocol (PDCP) layer and the Medium Access Control
(MAC) layer in the LTE user plane protocol stack. The main functions of the RLC layer are
segmentation and reassembly of upper layer packets in order to adapt them to the size which can
actually be transmitted over the radio interface. For radio bearers which need error-free
transmission, the RLC layer also performs retransmission to recover from packet losses.
Additionally, the RLC layer performs reordering to compensate for out-of-order reception due to
Hybrid Automatic Repeat request (HARQ) operation in the MAC layer. There is one RLC entity per
radio bearer.
RLC UL Throughput
This metric will provide Radio Link Control (RLC) uplink throughput. The RLC layer is located
between the Packet Data Convergence Protocol (PDCP) layer and the Medium Access Control
(MAC) layer in the LTE user plane protocol stack. The main functions of the RLC layer are
segmentation and reassembly of upper layer packets in order to adapt them to the size which can
actually be transmitted over the radio interface. For radio bearers which need error-free
transmission, the RLC layer also performs retransmission to recover from packet losses.
Additionally, the RLC layer performs reordering to compensate for out-of-order reception due to
Hybrid Automatic Repeat request (HARQ) operation in the MAC layer. There is one RLC entity per
radio bearer.

170
Nemo WindCatcher User Guide

Data Quality:

RLC DL BLER
This metric will provide downlink block error rate on radio link control layer.
Physical DSCH BLER
This metric will provide block error rate on physical downlink shared channel.
PBCH BLER
This metric will provide block error rate on physical broadcast channel.
Troubleshooting:

Poor Coverage
This metric allows the user to select a threshold for RSRP. All bins with RSRP values worse than
the threshold will be highlighted.

171
Nemo WindCatcher User Guide

Possible Interference (Scanner/UE)

This metric allows the user to define thresholds for Dominant RSRP and Dominant RSRQ. All bins
that are true for the thresholds will be highlighted.

LTE Low PDSCH Throughput in good RF

This metric allows the user to define thresholds for PDSCH throughput and Serving RS CINR. All
bins that are true for the thresholds will be highlighted.

LTE Low PDSCH Throughput in Poor RF

This metric allows the user to define thresholds for PDSCH throughput and Serving RS CINR. All
bins that are true for the thresholds will be highlighted
LTE Low PDSCH Throughput in Poor RF
This metric allows the user to define thresholds for PDSCH throughput and Serving RS CINR. All
bins that are true for the thresholds will be highlighted
Number of Servers Above Threshold (UE/Scanner)
The ‘No of Servers’ allows the user to define a delta between the Dominant PCI RSRP and the
RSRP of the other PCIs within the bin in Nemo WindCatcher. All bins that are true for the
thresholds will be highlighted

LTE Serving and Neighbor RSRP Comparison

This metric displays the delta as defined below:

LTE Consecutive Measurement Reports

The metric displays information for bins that observe a number of consecutive ‘measurement
report’ messages in the layer 3 data. The thresholds define the number of such messages observed
in a single bin. A large amount of consecutive measurement reports points to a possible missing
neighbor or a possible network issue
LTE Max RACH Retransmissions
The metric displays the maximum number of RACH retransmissions observed in a bin.

172
 Nemo WindCatcher User Guide

12 Appendix C: GSM Metrics

GSM Power
GSM Serving Cell Rx Level Full
Received Power for either Scanner or Phone when the DTX is not active
GSM Serving Cell Rx Level Sub
Received Power for Phone only during connect mode when the DTX is active.
GSM Best Neighbor Rx Level
Shows the Rx Level of the Best Neighbor
GSM Neighbor Rx Level
Shows the Rx Level of selected Neighbor
GSM Rx Level Full by BCCH
Shows Rx Level Full for selected BCCH
GSM Rx Level Full by Cell ID
Shows Rx Level Full for selected Cell ID
GSM Rx Level Full by TCH ARFCN
Shows Rx Level Full for selected TCH ARFCN
GSM Rx Level Sub by Cell ID
Shows Rx Level Sub for selected Cell ID
GSM Rx Level Sub by TCH ARFCN
Shows Rx Level Sub for selected TCH ARFCN
GSM Total Rx Power:
It is the total Power antenna is reading
GSM Tx Power Level
The Transmit Power of the phone. Transmit Power is the actual RF power output of the handset.
Mobile Power Class
Mobiles belong to different Power Class, depending on the maximum power they can transmit. Class
4 is commonly used
GSM Rx Qual
GSM Serving Cell Rx Qual Full
This parameter shows the signal quality. It is derived from the BER (Bit Error Rate) with continuous
transmission from tower.
GSM Serving Cell Rx Qual Sub
This parameter shows the signal quality. It is derived from the BER (Bit Error Rate) with discontinuous
transmission from tower
GSM Best Neighbor Rx Qual
Shows Rx Qual of the best neighbor
GSM Neighbor Rx Qual
Shows Rx Qual of selected neighbor
GSM Rx Qual Full By BCCH
Shows Rx Qual Full for selected BCCH
GSM Rx Qual Full by Cell ID
Shows Rx Qual Full for selected Cell ID
GSM Rx Qual Full by TCH ARFCN
Shows Rx Qual Full for selected TCH ARFCN
GSM Rx Qual Sub by Cell ID
Shows Rx Qual Sub for selected Cell ID
GSM Rx Qual Sub by TCH ARFCN
Shows Rx Qual Sub for selected TCH ARFCN

173
 Nemo WindCatcher User Guide

Average SQI
This metric is for TEMS only. It is Channel to Interference ratio. Shows average SQI within a bin.
Min SQI
Shows minimum SQI within a bin
Max SQI
Shows Maximum SQI within a bin

GSM Cell Identity

GSM Serving BCCH Channel No
Shows the channel number of serving BCCH
GSM Frequency Band
Shows the serving frequency Band Cellular/PCS/AWS)
GSM Serving BSIC
It is Base Station Identity Code. It is six-bit parameter with 3 bit bits for BCC (Base Station Color Code)
and 3 bits for NCC (Network Color Code).
GSM Serving MCC
Shows the serving Mobile Country Code
GSM Serving MNC
Shows Serving Mobile Network Code
GSM Serving LAC
Shows the Location Area code, along with MCC and MNC it gives location area information.
GSM Best Neighbor BCCH Channel No
Shows the BCCH of Best Neighbor
GSM Neighbor BCCH Channel No
Shows the BCCH of selected Neighbor
GSM Best Neighbor BSIC
Shows the BSIC of Best Neighbor
GSM Neighbor BSIC
Shows the BSIC of selected Neighbor

GSM Frame Error

FER Full
Shows Frame Error rate when the DTX is not active
FER Sub
Shows the Frame Error Rate when DTX is active
FER TCH
Shows the Frame Error Rate only for the Traffic Channel

GSM Codec
GSM Source Rate
Shows the rate at which the GSM speech codec is working. The rates can be Full, Half, AMR Full or
AMR Half
GSM AMR DL Dominant Rate
When Adaptive Multi Rate codec is used, it shows the dominant rate at the downlink
GSM AMR UL Dominant Rate
When Adaptive Multi Rate codec is used, it shows the dominant rate at the uplink.

174
 Nemo WindCatcher User Guide

GSM Physical Channel

GSM DTX State
Discontinuous transmission, a feature used to save battery and reduce network traffic by powering
down the mobile station transmitter when there isn't any speech to transmit. Shows “0” when DTX is
inactive and “1” when it is active
GSM Channel type
GSM Serving Cell Timeslot: Shows the timeslot of the Serving Cell used. Its value varies from 0 to 7.
GSM Hopping:
Shows if Hopping is assigned or not. “0” when hopping is not assigned and “1” when it is assigned
GSM Frequency Hopping Sequence Number
Shows the hopping sequence of the frequencies on the TCH. An HSN of zero corresponds to the cyclic
hopping sequence, and values 1 through 63 correspond to the pseudo random patterns.
GSM MAIO
Shows GSM mobile Allocation Index Offset. It refers a time delay separating traffic channels. With
proper MAIO planning it is possible to minimize interference between synchronized cells.
GSM Serving Cell Time Advance
The Time Advance is used to compensate for the time it takes a RF signal to go between the BTS and
MS.
GSM Serving Cell time Advance by BCCH
Shows the time advance of the selected BCCH.
C Value
It is the path loss criterion parameter used for cell selection and reselection. This is calculated by the
MS and used for deciding which cell to camp to.

GSM Adjacent Channel

Measured Channel RSSI of Selected Channel
Shows the Rx Level of selected Adjacent channel
Minimum C/A of Selected Channel
Shows Minimum Carrier to Adjacent radio within a bin. The carrier-to-adjacent ratio is defined as the
signal-strength ratio between a serving carrier and an adjacent carrier.
C/A-1 of Selected Channel
Shows the Carrier to Adjacent ratio between the serving carrier and the carrier 200 kHz below it.
C/A-2 of Selected Channel
Shows the Carrier to Adjacent ratio between the serving carrier and the carrier 400 kHz below it.
C/A+1 of Selected Channel
Shows the Carrier to Adjacent ratio between the serving carrier and the carrier 200 kHz above it.
C/A+2 of Selected Channel
Shows the Carrier to Adjacent ratio between the serving carrier and the carrier 400 kHz above it.

GSM Phone/Scan Data

Maximum RxLev
Shows the Maximum Rx Level within a bin.
Minimum Rx Level
Shows the Minimum Rx Level within a Bin
Average Rx Level
Shows the Average Rx Level within a Bin
RxLev of Selected BSIC
Shows the Rx Level of selected BSIC
RxLev of Selected Channel
Shows the Rx Level of selected Channel

175
 Nemo WindCatcher User Guide

RxLev of Selected Channel Filtered by BSIC

Shows the Rx Level of selected Channel and BSIC.
BSIC of Maximum RxLev
Shows the BSIC of maximum Rx Level
BSIC of Selected Channel
Shows the BSIC of selected Channel
Nth Strongest Channel
Shows the Nth Strongest Channel according to Rx Level
Channel of Maximum RxLev
Shows the Channel of Maximum Rx Level
Scanner Worst BER
Shows the worst scanned BER
Scanner Worst BER BCCH
Shows the BCCH of Worst scanned BER
Scanner BER of Selected BCCH
Shows the BER of selected BCCH
Best C/I Channel
Shows the channel with best Channel to Interference ratio.
Best C/I
Shows best Channel to interference ratio with a bin.
Worst C/I Channel
Shows the channel with worst Channel to Interference ratio.
Worst C/I
Shows worst Channel to interference ratio with a bin.
Worst C/I Timeslot
Shows the time slot with worst Channel to Interference ratio.
C/I of Selected Channel
Shows Carrier to interference ratio of selected Channel

GPRS/EGPRS
Coding Scheme-Downlink
Shows the coding scheme on the downlink
Coding Scheme-Uplink
Shows the Coding Scheme on the Uplink
Packet technology
Shows the packet technology either its GRRS or EGPRS.
Packet State
Shows the current Packet State for example Attach, Detached or Packet Session Active
GPRS MAC Mode DL
Shows the GPRS MAC Mode on the Downlink
GPRS MAC Mode UL
Shows the GPRS MAC mode on the Uplink
GMM State
Shows the GPRS Mobility Management State
GRR State
Shows GPRS radio Resource State
BEP Mean
Shows the mean Bit Error probability
No of Active DL Slots
Shows the number of time slots used for data transmission within a bin on downlink

176
Nemo WindCatcher User Guide

No of Active UL Slots
Shows the number of time slots used for data transmission within a bin on uplink
LLC Bytes Received
Shows the total number of bytes received on Logical Link Control Layer
LLC DL Throughput (kbps)
Shows the Downlink throughput on LLC which defines the logical link control layer protocol to be
used for packet data transfer between the mobile station (MS) and a serving GPRS support node
(SGSN)
LLC Bytes Sent
Shows the total number of bytes sent on Logical Link Control Layer
LLC UL Throughput (kbps)
Shows the Uplink throughput on LLC which defines the logical link control layer protocol to be used
for packet data transfer between the mobile station (MS) and a serving GPRS support node (SGSN)
LLC DL BLER
Shows the Downlink BLER on LLC which defines the logical link control layer protocol to be used for
packet data transfer between the mobile station (MS) and a serving GPRS support node (SGSN)
LLC UL BLER
Shows the Uplink BLER on LLC which defines the logical link control layer protocol to be used for
packet data transfer between the mobile station (MS) and a serving GPRS support node (SGSN).

177
 Nemo WindCatcher User Guide

13 Appendix D: UMTS Metrics

UMTS Power
UMTS Rx Power
The Received Power in the UMTS channel (includes useful energy and interference).
UMTS Max Rx Power
Shows Maximum Rx Power available within a bin
UMTS Min Rx Power
Shows minimum RX Power within a bin
UMTS Tx Power
The Transmit Power of the phone. Transmit Power is the actual RF power output of the handset.
UMTS Max Tx power
Shows Maximum Tx Power available within a bin
UMTS Min Tx power
Shows minimum Tx Power within a bin
UMTS SC RSCP Plot
Shows PSC’s, Received Signal Code Power. It is the total power of PSC.
UMTS Average SIR
Shows average UMTS Signal to interference ratio within a bin

UMTS Pilot/Scan Data

UMTS best finger EcIo
Average Ec/Io of the strongest finger.
UMTS Sum Finger EcIo
Aggregate Ec/Io value of all the fingers.
UMTS Sum Active Set EcIo
Aggregate Ec/Io value of all the fingers.
UMTS Sum All Set EcIo
Summation of Ec/Io in all sets.
UMTS Dominant Pilot EcIo
The Ec/Io of the pilot with the strongest Ec/Io value across all sets. The Dominant pilot could be in
the Active, Monitored or Detected set.
UMTS Best EcIo in Active Set
The strongest Ec/Io value of all the pilots in the Active set.
UMTS Best EcIo in Monitored Set
The strongest Ec/Io value of all the pilots in the monitored Set
UMTS Best EcIo in Detected Set
The strongest Ec/Io value of all the pilots in the Detected Set
UMTS EcIo for PSC
Shows EcIo for selected PSC
EcIo for Nth Best Pilot
Shows the EcIo of Nth best pilot
UMTS Dominant Pilot PSC
The pilot with the strongest Ec/Io value across all sets. The Dominant pilot could be in the Active,
Monitored or Detected set.
UMTS Best Active Pilot PSC
The pilot with the strongest Ec/Io value in the active set.
UMTS Best Monitored Pilot PSC
The pilot with the strongest Ec/Io value in the Monitored set.

178
 Nemo WindCatcher User Guide

UMTS Best Detected Pilot PSC

The pilot with the strongest Ec/Io value in the detected set.
UMTS PSC Nth Best Pilot
Shows the PSC of Nth (Strongest, 2nd Strongest …) best Pilot with respect to EcIo.
UMTS RSCP for PSC
Shows RSCP of Selected PSC
UMTS Sum all set RSCP
Summation of RSCP in all Sets
UMTS Dominant Pilot RSCP
The RSCP of the pilot with the strongest Ec/Io value across all sets.
UMTS Best Active RSCP
Shows RSCP of Best Active pilot
UMTS Sum Active RSCP
Summation of RSCP of all Pilots in Active Set
UMTS Best Monitored RSCP
Shows the RSCP of best Monitored pilot.
UMTS Best Detected RSCP
Shows the RSCP of best Detected pilot.
UMTS RSCP Nth best Pilot
Shows the Received Signal Code power of Nth Best pilot
UMTS Number Pilots in Active Set
Displays the number of Pilot in Active Set

HSDPA Metrics
HSDPA Serving PSC
Shows HSDPA Serving Primary Synchronization Code
HSDPA Serving CPICH EcIo
Shows EcIo for Serving Common Pilot Channel
HSDPA Serving RSCP
Shows RSCP of the Serving PSC
HSDPA Max CQI
Shows maximum channel quality index within a bin. CQI is being used by the base station to calculate
how much data to send to the user devices on the next transmission.
HSDPA Min CQI
Shows minimum channel quality index within a bin. CQI is being used by the base station to schedule
data transmission to send to the user devices on the next transmission.
HSDPA Average CQI
Shows average channel quality index within a bin. CQI is being used by the base station to calculate
how much data to send to the user devices on the next transmission.
HSDPA Percentage valid CQI
Shows percentage of valid CQI within a bin. Shows max channel quality index within a bin. CQI is
being used by the base station to calculate how much data to send to the user devices on the next
transmission.
HSDPA Average SIR
Shows average signal to interference ratio for HSDPA within a bin.
HSDPA ACK Subframes
Number of subframes for which acknowledgement is received i.e. the successful subframes.
HSDPA NACK Subframes
Number of subframes which are not acknowledged i.e. failed subframes
HSDPA ACK kbits
Data in kbits in the subframes which are acknowledged.

179
Nemo WindCatcher User Guide

HSDPA NACK kbits

Data in kbits in the subframes which are not acknowledged.
HSDPA ACK Rate
It shows the percentage of the acknowledged subframes within a bin.
HSDPA NACK Rate
It shows the percentage of not acknowledged subframes within a bin.
HSDPA DTX Subframes
Number of the subframes in discontinuous transmission mode.
HSDPA DTX Rate
It shows the percentage of discontinuous transmission mode subframes within a bin.
HSDPA Physical Requested Throughput
It shows the Physical throughput requested by the UE.
HSDPA Physical Scheduled throughput
It shows the Physical throughput scheduled by the RNC.
HSDPA Physical Served throughput
It shows the Physical throughput which was served.
HSDPA Residual BLER
Shows the Block error rate for the first retransmission
HSDPA Representative Number of HARQ Processed
Shows the number of Hybrid Automatic Requested processed within a bin. This varies from 0 to7.
HSDPA Number Active H-ARQ Flows
Shows the active number of Hybrid Automatic Request flows at a specific time.
HSDPA H-ARQ Metrics
Hybrid-ARQ is a technique combining FEC and ARQ methods that save information from previous
failed attempts to be used in future decoding.
HSDPA QPSK Utilization
Shows the utilization of QPSK modulation within a bin
HSDPA 16QAM Utilization
Shows the percentage utilization of 16 QAM within a bin
HSDPA Modulation Type
Shows the modulation type used mostly within a bin. It can be QPSK or 16 QAM

Error Rate
Downlink BLER
Shows the Block Error rate on the downlink
Downlink DCH BLER
Shows the Block Error rate for Dedicated Channel on the downlink
Downlink HS-DSCH BLER
Shows the Block Error rate for High Speed Downlink Shared Channel.

Data Throughput
Downlink Physical Layer Throughput
It shows the instantaneous Forward data throughput on the physical layer.
Downlink DCH Physical Layer Throughput
It shows the instantaneous Forward data throughput on the physical layer for Dedicated Control
Channel
Downlink HS-DSCH Physical Layer Throughput
It shows the instantaneous Forward data throughput on the physical layer for High Speed – Downlink
Shared Channel only.

180
 Nemo WindCatcher User Guide

Downlink RLC Throughput

The instantaneous Forward data throughput on the RLC layer. The Radio Link Control (RLC) layer sits
above the physical layer, and is responsible for error checking and retransmissions over the typically
noisy radio link. Metrics at this layer are often valued because they reflect the true performance
offered by the radio link.
Downlink RLC Throughput (Max)
Shows the Maximum value of Forward data throughput on the RLC layer within a bin.
Downlink RLC Throughput (Min)
Shows the Minimum value of Forward data throughput on the RLC layer within a bin.
Downlink RLC Cumulative Throughput
It shows the cumulative Forward data throughput on RLC layer.
Uplink RLC Throughput
It shows the instantaneous Reverse data throughput on the RLC layer.
Uplink RLC Throughput (Max)
Shows the Maximum value of Reverse data throughput on the RLC layer within a bin.
Uplink RLC Throughput (Min)
Shows the Minimum value of Reverse data throughput on the RLC layer within a bin.
Uplink RLC Cumulative Throughput
It shows the cumulative Reverse data throughput on RLC layer.

Data Applications
Data Application Type
The type of data application, for e.g. FTP, HTTP etc.
Downlink Application Throughput
The application layer throughput on the forward link
Downlink PPP Throughput
The Point to Point protocol throughput on Forward link
Downlink IP Packets
The IP packets on the forward link
Downlink TCP Packets
The TCP packets on the forward link
Downlink UDP Packets
The UDP Packets on the forward link.
Downlink PPP Packets
The PPP packets on the forward link.
Uplink Round Trip Time
This metric, displays the delay time for a packet to be received.
Uplink Application Throughput
The application throughput on the reverse link
Uplink PPP Throughput
The Point to Point protocol throughput on reverse link
Uplink IP Packets
The IP packets on the reverse link
Uplink TCP Packets
The TCP packets on the reverse link
Uplink UDP Packets
The UDP packets on the reverse link
Uplink PPP Packets
The PPP packets on the reverse link
Send Round Trip Time
This metric, displays the delay time for a packet to be sent.

181
 Nemo WindCatcher User Guide

Audio Quality
Audio MOS DL
Shows audio mean Opinion Score on the downlink
Audio MOS UL
Shows audio mean Opinion Score on the uplink

Video Quality
Video Quality Index (VQI)
Shows the Video Quality Index for video streaming. Link MOS is the quality parameter for voice, VQI
is the quality parameter for video.

Mobile
Call State
Shows the state of the phone. The states may be Idle, Connecting, Connected, and Access, which
may be further classified according to the technology.
Data transmission Mode
Shows the Data Transmission mode at some instance. The mode may be GSM, HSDPA, R99, FACH
or Idle.
UMTS UARFCN DL
Shows the UMTS UTRA Absolute Radio Frequency Channel Number on the downlink.
UMTS UARFCN UL
Shows the UMTS UTRA Absolute Radio Frequency Channel Number on the uplink.
UMTS UARFCN DL Frequency
Shows the frequency associated with UMTS UTRA Absolute Radio Frequency Channel Number on the
downlink.
UMTS UARFCN UL Frequency
Shows the frequency associated with UMTS UTRA Absolute Radio Frequency Channel Number on the
uplink.
GSM ARFCN DL
Shows the GSM Absolute Radio Frequency Channel Number on the downlink.
GSM ARFCN UL
Shows the GSM Absolute Radio Frequency Channel Number on the uplink.
GSM ARFCN DL Frequency
Shows the frequency associated with GSM Absolute Radio Frequency Channel Number on the
downlink.
GSM ARFCN UL Frequency
Shows the frequency associated with GSM Absolute Radio Frequency Channel Number on the uplink.

Log Files
Log Files
Shows the bins with reference to the log files in which they are present.
Drive Route
Shows the whole Drive Route.

Neighbor Analysis
This feature is located under the Tools menu.

182
Nemo WindCatcher User Guide

The following thresholds are available for the user to run this analysis:

The user would need to define the following before selecting ‘Run Analysis’
• ARFCN
• Server (dB): Select a threshold to define a server
• Neighbor
• RSCP: This value is used to provide an upper limit on RSCP for the data considered in the
analysis
• Windows Size: Any value below this (5dB) will not be considered as a polluter
• Server Bin Count
• Pollution Threshold: This value is used to provide a lower limit on the number of PSCs that
act as polluters in a bin
• Pollution Contribution: This value is used to provide a lower limit on the total number of
PSCs contributing to a polluting PSC

183
Nemo WindCatcher User Guide

The output displays the following information:

The first interferer for the case above would be column 4-Int. The relative Pollution level is
calculated as shown below:
(4-int+5-int+6-int+...+10-int)/ (1-int+2-Int+…+10-Int)

184
 Nemo WindCatcher User Guide

14 Appendix E: CDMA Metrics

Pilot
The pilot metrics represents all metrics related to the pilot.

Best Finger Ec/Io

Average Ec/Io of the strongest finger.

Sum Finger Ec/Io

Aggregate Ec/Io value of all the fingers.

Sum Active Set Ec/Io

Summation of Ec/Io in active set.

Sum All Set Ec/Io

Summation of Ec/Io in all sets.

Dominant Pilot Ec/Io

The Ec/Io of the pilot with the strongest Ec/Io value across all sets. The Dominant pilot could be
in the Active, Candidate, Neighbor or Remaining set.

Best Ec/Io in Active Set

The strongest Ec/Io value of all the pilots in the Active set.

Best Ec/Io in Candidate Set

The strongest Ec/Io value of all the pilots in the Candidate set.

Best Ec/Io in Candidate Set from PSMM

The strongest Ec/Io value of all the pilots reported in the Candidate set from the Pilot Strength
Measurement Message (PSMM). If there are multiple PSMM messages in a bin, then the last
PSMM message is used for this metric.

Ec/Io for PN
Average Ec/Io value of the selected PN across all sets. Only PNs present in the dataset are
displayed in the drop-down box.

Ec for PN
Average Ec value of the selected PN across all sets. Only PNs present in the dataset are
displayed in the drop-down box.

Delay for PN
Delay for the selected PN across all sets. Only PNs present in the dataset are displayed in the
drop down box.

Delay Spread for PN

Delay spread for the selected PN across all sets. Only PNs present in the dataset are displayed in
the drop-down box.

SINR for PN
SINR for the selected PN across all sets. Only PNs present in the dataset are displayed in the

185
Nemo WindCatcher User Guide

drop down box.

Ec/Io for Nth Best Pilot

Ec/Io for the Nth best PN across all sets. Only PNs present in the dataset are displayed in the
drop down box.

Ec for Nth Best Pilot

Ec for the Nth best PN across all sets. Only PNs present in the dataset are displayed in the drop
down box.

Delay for Nth Best Pilot

Delay for the Nth best PN across all sets. Only PNs present in the dataset are displayed in the
drop down box.

Delay Spread for Nth Best Pilot

Delay Spread for the Nth best PN across all sets. Only PNs present in the dataset are displayed in
the drop-down box.

SINR for Nth best PN

SINR for the selected Nth best PN across all sets. Only PNs present in the dataset are displayed
in the drop, down box.

Dominant Pilot PN
Dominant PN for the part of the drive is displayed.

Best Active Pilot PN

Best Active PN is displayed.

Best Active TX Antenna Polarization

Search Window Active Set
Search window for pilots in the Active Set (SRCH_WIN_A).
Search Window Neighbor Set
Search window for pilots in the Neighbor Set (SRCH_WIN_N).
Search Window Remaining Set
Search window for pilots in the Remaining Set (SRCH_WIN_R).

Power
The power metrics represents all metrics related to power.

Rx Power
The Received Power in the CDMA channel (includes useful energy and interference).

Tx Power
The Transmit Power of the phone. Transmit Power is the actual RF power output of the handset.

Tx Power Adjustment
The Transmit Power Gain Adjustment. Transmit Power Gain Adjustment is a running sum of all
the power control bits.

Rx Power by State
This metric displays the Received Power in the CDMA channel for desired phone state.

186
Nemo WindCatcher User Guide

Dominant Pilot Ec
The Ec (Chip Energy) of the dominant pilot. The dominant pilot is the pilot with the strongest
Ec/Io across all sets.

FER
The FER metrics represents all metrics related to the Frame Error Rate.

Forward FER Markov

The Forward Frame Error Rate (FER) for Markov and Voice Calls. FFER-Markov is the
percentage of forward frames received in error to the total received frames.

Forward FCH FER

The combined Forward Frame Error Rate for the Fundamental (FCH) Channel. It presents the
percentage of Forward FCH frames received in error. In the case of voice calls, this metric should
closely match the FFER-Markov, assuming all messages are captured correctly in the log file and
the system is correctly set up to support Markov calls.

Forward SCH FER

The Forward Frame Error Rate for the Supplemental (SCH) Channel. It presents the percentage of
Forward SCH frames received in error. A straight average is performed over SCH frames of all
rates.

Forward Weighted FER

This metric presents the combined weighted Forward Frame Error Rate for the Fundamental
(FCH) and Supplemental (SCH) Channel. It presents the percentage of Forward FCH and SCH
frames, weighted by the individual frame rates, received in error.

Forward Weighted SCH FER

This metric presents the Forward Frame Error Rate for the Supplemental (SCH) Channel. It
presents the percentage of Forward SCH frames, weighted by the individual frame rates, received
in error.

Data
The Data metrics represents all metrics related to the Data.

Forward Assigned Combined Rate

The assigned data rate on the Forward link, which includes the combined Fundamental (FCH) and
Supplemental (SCH) Channel data rates appropriately weighted. The assigned rate presents the
rate offered by the fixed network, and is calculated based on both good and bad frames received
over the downlink.

Forward Assigned SCH Rate

The assigned data rate on the Supplemental (SCH) Channel of the Forward link. The assigned rate
presents the rate offered by the fixed network, and is calculated based on both good and bad
frames received over the downlink.

Forward Physical Layer Throughput

The instantaneous Forward data throughput on the physical layer. This metric only counts the
good frames when computing the throughput.

187
Nemo WindCatcher User Guide

Forward RLP Throughput

The instantaneous Forward data throughput on the RLP layer. The Radio Link Protocol (RLP)
layer sits above the physical layer, and is responsible for error checking and retransmissions over
the typically noisy radio link. Metrics at this layer are often valued because they reflect the true
performance offered by the radio link.

Forward RLP Accumulated Throughput

The accumulated Forward data throughput on the RLP layer. The Radio Link Protocol (RLP)
layer sits above the physical layer, and is responsible for error checking and retransmissions over
the typically noisy radio link. Metrics at this layer are often valued because they reflect the true
performance offered by the radio link.

Forward RLP Re-transmit Rate

The retransmit rate on the RLP layer. It presents the percentage of retransmitted frames. The
Radio Link Protocol (RLP) layer sits above the physical layer, and is responsible for error
checking and retransmissions over the typically noisy radio link. Metrics at this layer are often
valued because they reflect the true performance offered by the radio link.

Reverse Assigned Combined Reverse Rate

The assigned data rate on the Reverse link, which includes the combined Fundamental (FCH) and
Supplemental (SCH) Channel data rates appropriately weighted.

Reverse Assigned SCH Rate

The assigned data rate on the Supplemental (SCH) Channel of the Reverse link. The Radio Link
Protocol (RLP) layer sits above the physical layer, and is responsible for error checking and
retransmissions over the typically noisy radio link. Metrics at this layer are often valued because
they reflect the true performance offered by the radio link.

Note that since the RLP involves handshaking between both the mobile and the fixed network to
perform the retransmissions, therefore even the reverse link statistics may be obtained from the
mobile end.

Reverse RLP Throughput

The instantaneous Reverse data throughput on the RLP layer. The Radio Link Protocol (RLP)
layer sits above the physical layer, and is responsible for error checking and retransmissions over
the typically noisy radio link. Metrics at this layer are often valued because they reflect the true
performance offered by the radio link.
Note that since the RLP involves handshaking between both the mobile and the fixed network to
perform the retransmissions, therefore even the reverse link statistics may be obtained from the
mobile end.

Reverse RLP Accumulated Throughput

The accumulated Reverse data throughput on the RLP layer. The Radio Link Protocol (RLP)
layer sits above the physical layer, and is responsible for error checking and retransmissions over
the typically noisy radio link. Metrics at this layer are often valued because they reflect the true
performance offered by the radio link.
Note that since the RLP involves handshaking between both the mobile and the fixed network to
perform the retransmissions, therefore even the reverse link statistics may be obtained from the
mobile end.

188
Nemo WindCatcher User Guide

Reverse RLP Re-transmit Rate

The retransmit rate on the RLP layer. It presents the percentage of retransmitted frames. The
Radio Link Protocol (RLP) layer sits above the physical layer, and is responsible for error
checking and retransmissions over the typically noisy radio link. Metrics at this layer are often
valued because they reflect the true performance offered by the radio link.
Note that since the RLP involves handshaking between both the mobile and the fixed network to
perform the retransmissions, therefore even the reverse link statistics may be obtained from the
mobile end.

Data Applications
The Data Application metrics represents all metrics related to data at the higher layers.

Data Application Type

The type of data application, for e.g. FTP, HTTP etc.

Forward Application Throughput

The application layer throughput on the forward link.

Forward PPP Throughput

The PPP layer throughput on the forward link.
Forward IP Throughput
The IP throughput on the Forward link.

Forward TCP Packets

The TCP packets sent on the forward link.
Forward UDP Packets
The UDP packets sent on the forward link.

Forward IP Packets
The IP packets sent on the forward link.

Forward PPP Packets

The PPP packets on the forward link.

Receive Round Trip Time

This metric, displays the delay time for a packet to be received.

Reverse Application Throughput

The application layer throughput on the Reverse link.

Reverse PPP Throughput

The PPP layer throughput on the Reverse link.

Reverse IP Throughput
The IP throughput on the Reverse link.

Reverse TCP Packets

The TCP packets sent on the Reverse link.

Reverse UDP Packets

The UDP packets sent on the Reverse link.

189
Nemo WindCatcher User Guide

Reverse IP Packets
The IP packets sent on the Reverse link.

Reverse PPP Packets

The PPP packets on the Reverse link.

Send Round Trip Time

This metric, displays the delay time for a packet to be sent.

Reverse Link
The Reverse Link metrics represents all metrics of the reverse link.

Primary Digital Gain

The Digital Gain for the primary sector.

Average Forward FCH Tx Power

The Average Transmit power of the Forward Fundamental Channel.
Average Forward SCH Tx Power
The Average Transmit power of the Forward Supplemental Channel.

Reverse Best FCH Eb/No

The best Eb/No of the Fundamental Channel.

Reverse FCH FER (%)

The Reverse Frame Error Rate for the Fundamental (FCH) Channel. It presents the percentage of
Reverse FCH frames received in error.

Reverse SCH FER (%)

The Reverse Frame Error Rate for the Supplemental (SCH) Channel. It presents the percentage of
Reverse SCH frames received in error. A straight average is performed over SCH frames of all
rates.

Reverse Weighted FER (%)

This metric presents the combined weighted Reverse Frame Error Rate for the Fundamental
(FCH) and Supplemental (SCH) Channel. It presents the percentage of Reverse FCH and SCH
frames, weighted by the individual frame rates, received in error.

Reverse Weighted SCH FER (%)

This metric presents the Reverse Frame Error Rate for the Supplemental (SCH) Channel. It
presents the percentage of Reverse SCH frames, weighted by the individual frame rates, received
in error.

Reverse Physical Layer Throughput

The instantaneous Reverse data throughput on the physical layer. This metric only counts the good
frames when computing the throughput

Mobile
The mobile metrics represents all metrics related to the phone state.

190
Nemo WindCatcher User Guide

Mobile Frequency Channel

The frequency channel or CDMA carrier that the phone is locked onto.

Call State
The call state of the phone. Possible states are Idle, Access, Registration, Call Connection, and Page
Response and Dedicated. Colors for the different Call State plots may be changed through ‘Mobile
Threshold’ menu

System
The system ID from the phone (Network).

Network
The Network ID from Network.

EVDO
The EVDO metrics represent all metrics related to wireless internet data solutions.

EVDO Downlink Serving Pilot PN

This metrics returns the PN identity of the serving pilot in each bin.

EVDO Downlink Serving Pilot SINR

The Downlink Serving Pilot SINR illustrates the average of the SINR values of the serving pilot in
each bin.

EVDO Best ASP SINR

This metric illustrates the average of the SINR values of the strongest Active Set pilot in a bin.

EVDO Best ASP C/I

This metric plots the Nemo WindCatcher database field Best_active_C_to_I in the Phone_data table.
The legends for this metric shall follow that used for the metric EVDO Best ASP SINR.

EVDO Best Candidate C/I

This metric sketches the Nemo WindCatcher database field Best_candidate_C_to_I in the
Phone_data
table. The legends for this metric will follow that used for the metric EVDO Best ASP SINR.

EVDO Dominant Pilot C/I

This metric shall plot the Nemo WindCatcher database field Dominant_PN_C_to_I in the Phone_data
table. The legends for this metric shall follow that used for the metric EVDO Best ASP SINR.

EVDO Forward PER

The Forward PER is a measure of the packet error over the forward link.

EVDO Rx Power Ant0 (dBm)

This metric is, the average of all receive power values received in each bin for Antenna 0.

EVDO Rx Power Ant1 (dBm)

This metric is, the average of all receive power values received in each bin for Antenna 1.

EVDO Rx Power Delta (dB)

This metric is the difference between the Rx power of antenna 0 and the Rx power of antenna 1.

191
Nemo WindCatcher User Guide

EVDO Tx Pilot Power (dBm)

The Tx Pilot Power metric is the average of all pilot transmit power values in each bin when the
amplifier (PA) state is on.

EVDO Forward RLP Average Bytes Request Per Nak

This metric is a measure of the average number of bytes requested per NAK received over the
forward link.

EVDO Max Predicted DRC Rate

The Max Predicted DRC Rate metric returns the maximum value of predicted DRC rate over all
slots of all messages that appear in each bin.

EVDO Avg Predicted DRC Rate

The Avg Predicted DRC Rate metric returns the average value of predicted DRC rate over all slots
of all messages that appear in each bin.

EVDO Max Transmitted DRC Rate

The Max Transmitted DRC Rate metric returns the maximum value of all DRC rates actually
transmitted over the reverse DRC channel. Please note that this information is only available when
the AT is in connected state.

EVDO Avg Transmitted DRC Rate

The Avg Transmitted DRC Rate metric illustrates the average value of all DRC rates actually
transmitted over the reverse DRC channel. Please note that this information is only available when
the AT is in connected state.

EVDO Downlink Slot Occupancy-Current AT

This metrics is the percentage of the slots on the downlink containing packets destined for the
current AT. This metric is computed as the ratio of the number of slots with ACK sent over the
uplink over total slots in bin.

EVDO Reverse Offered Physical Layer Throughput

This metrics is a measure of the throughput offered to the reverse link at the physical layer. The
throughput is obtained by computing the average good packet throughput over the bin at the
physical layer. Each packet is weighted by its rate when computing the throughput. Note that this
throughput is instantaneous and is measured over the duration of the bin.

EVDO Reverse RLP Average Bytes Request Per Nak

This metric is a measure of the average number of bytes requested per NAK received over the
reverse link.

EVDO Average Predicted RRI

The Average Predicted RRI provides the average of all predicted RRI values sent over the uplink
in a bin.

EVDO Actual RRI

The Actual RRI is the average of all actual RRI values sent over the uplink in a bin.

192
Nemo WindCatcher User Guide

EVDO Reverse Rate Limit

This metric sketches the values in the database field Reverse_rate_limit in the EVDO_data table.
The default value of ‘0’ should not be plotted. The legends for this metric will follow that used for
the metric EVDO Actual RRI.

EVDO Reverse PA Rate Limit

This metric shall plot the values in the database field Reverse_PA_rate_limit in the EVDO_data
table. The default value of ‘0’ should not be plotted. The legends for this metric shall follow that
used for the metric EVDO Actual RRI.

EVDO UATI
This metric plots the values in the database field UATI in the EVDO_data table. A unique color
shall be assigned to each unique value of UATI seen, similar to how the legends are formed for the
Mobile Frequency Channel metric.

EVDO Rev A
The EVDO Rev A metrics represent all metrics related to wireless internet data solutions.

Reverse HiCap Physical Layer Throughput

This metrics reports the physical layer throughput sent successfully over the reverse link of
packets in the HiCap mode.

Reverse LoLat Physical Layer Throughput

The metric reports the physical layer throughput sent successfully over the reverse link of packets
in the LoLat mode.

Reverse Physical Layer Throughput

This metric reports the overall physical layer throughput sent successfully over the reverse link
(both HiCap and LoLat combined).

Reverse Number HiCap Kbits Transmitted

This metric in conjunction with the reverse transmission time metric, can be used to reconstruct
the instantaneous throughput values reported in each bin.

Reverse Transmission Time

This metric measures the reverse transmission time over which both the HiCap and LoLat bits
were reported for the bin. This metric may be used along with the bit counts to reconstruct the
instantaneous throughput values reported in the bin.

Reverse HiCap Packet Error Rate

This metric reports the packet error rate over the reverse links for packets in the HiCap mode.

Reverse LoLat Packet Error Rate

This metric reports the packet error rate over the reverse links for packets in the LoLat mode.

Reverse Packet Error Rate

This metric reports the packet error rate over the reverse links for all packets combined (HiCap
and LoLat).

193
Nemo WindCatcher User Guide

Reverse Total HiCap Packet Transmitted

This metric reports the total number of HiCap packets transmitted over the reverse link. This
metric may be used along with the number of error packets to arrive at the instantaneous packet
error rates reported in each bin.

Reverse Total LoLat Packet Transmitted

This metric reports the total number of LoLat packets transmitted over the reverse link. This
metric may be used along with the number of error packets to arrive at the instantaneous packet
error rates reported in each bin.

Reverse HiCap Packet Error Packets

This metric in conjunction with the total HiCap packets transmitted metric, can be used to
reconstruct the instantaneous packet error rate values reported in each bin.

Reverse LoLat Packet Error Packets

This metric in conjunction with the total LoLat packets transmitted metric, can be used to
reconstruct the instantaneous packet error rate values reported in each bin.

Sub-Frame Utilization
This metric reports the percentage of sub frames with sub packets sent over the reverse link for the
AT.

Total Reverse Sub-Frame

This metric reports the total number of sub frames sent over the reverse link for the AT.

Total Reverse Sub-Frame with Packets

This metric reports the number of sub frames with sub packets sent over the reverse link for the
AT.
Reverse Number SubPacket0 Received Packets
This metric reports the total number of packets sent over the reverse link in the bin where the
packet transmission was successful in the first subpacket.

Reverse Number SubPacket1 Received Packets

This metric reports the total number of packets sent over the reverse link in the bin where the
packet transmission was successful in the second subpacket.

Reverse Number SubPacket2 Received Packets

This metric reports the total number of packets sent over the reverse link in the bin where the
packet transmission was successful in the third subpacket. Reverse Number SubPacket3 Received
Packets

Reverse Number SubPacket3 Received Packets

This metric reports the total number of packets sent over the reverse link in the bin where the
packet transmission was successful in the fourth subpacket.

Forwards MUP Physical Layer Throughput

This metric reports the forward physical layer throughput when the packets were specifically sent
as multi-user packets.

194
Nemo WindCatcher User Guide

Forwards Total MUP KBits

This metric reports the total number of MUP bytes received in each bin and may be used in
conjunction with the MUP transmission time to reconstruct the instantaneous physical layer
throughput reported for that bin.

Forwards MUP Time

This metric reports the total transmission time over which the MUP bytes were recorded and may
be used along with these byte counts to arrive at the instantaneous physical layer throughput
computed in each bin.

Sector
The Sector metrics represents all metrics related to the cell site sectors.

Color by PN
This metrics will color the sectors of the cell sites corresponding to the PN numbers.

Color By Sector Id
This metrics will color the sectors of the cell corresponding to the sector Id’s.

User Defined Color (CDMA)

This metrics allows the user to color the sections of the cell sites with own defined colors.
After selecting the User Defined Color metric, the following window will appear:
You may then select the desired Threshold value to use when displaying the sector colors. Please
note that these threshold values may be adjusted by going to the Threshold icon and selecting the
Other Thresholds... function. (For more detail please view Thresholds section)

Receiver
The receiver metrics represent all metrics related to CW, Spectrum Analyzers or scanning receivers.

Maximum RSSI
The strongest RSSI value across all scanned frequencies.

Minimum RSSI
The weakest RSSI value across all scanned frequencies.

Average RSSI
The average RSSI value across all scanned frequencies.

Frequency of Maximum RSSI

The frequency value corresponding to the strongest RSSI.

Channel of Maximum RSSI

The channel number corresponding to the strongest RSSI.

RSSI of Selected Frequency

The RSSI values for the frequency selected in the drop-down list.

RSSI of Selected Channel

The RSSI values for the channel selected in the drop-down list.

195
Nemo WindCatcher User Guide

Advanced Metrics
The Advanced metrics are developed based on certain conditions and combination of one or several
basic metrics.

a) IS95A Available Pilot

The number of pilots available for handoff based on the IS95A handoff algorithm. All pilots with
Ec/Io above the user defined threshold value will be considered as available candidate. This metric
provides a good indication of the number of pilots that will be used in the Active Set if the IS95A
algorithm is used. Note that this calculation is performed across all sets, and therefore is not
restricted to problems that may arise with pilots not actually entering the Active Set due to
neighbor list problems, cell resource problems, etc.

b) IS95B Available Pilot

The number of pilots available for handoff based on the IS95B/CDMA 2000 1XRTT handoff
algorithm. All pilots with Ec/Io within the user defined range value of the best serving pilot and
above the user defined threshold will be considered as available candidates. This metric provides a
good indication of the number of pilots that will be used in the Active Set if the IS95B algorithm
is used (though it does not exactly represent the algorithm used, it should serve as a close
approximation). Note that this calculation is performed across all sets, and therefore is not
restricted to problems that may arise with pilots not actually entering the Active Set due to
neighbor list problems, cell resource problems, etc.

c) Number of Pilot in Handoff

The number of pilots in handoff as reported by the phone. As opposed to the IS95A and IS95B
number of available pilot metrics, this metric reflects the actual number of pilots present in the
Active Set.

d) Number of Pilot by Set

The number of pilots above the user defined threshold value, in the selected set.

e) Pilot Usefulness Indicator

Indicates state of pilot at each location. Only PNs present in the dataset are displayed in the drop
down box. The pilot state could be one of the following:
This metric presents the usefulness of the pilot along the drive route. During pilot optimization, it
would generally be preferred to remove the pilot where it is less useful (such as when it is a weak
contributor, pilot polluter, etc.) and strengthen it where it is the most useful (such as when it is the
only pilot, dominant pilot, etc.

f) Strong Non-Active Pilot Indicator

The ratio of the best active to non-active pilot. A large positive value indicates the presence of a
strong non-active pilot. This metric indicates areas where poor performance could be attributed to
a strong pilot that is prevented from entering the Active Set, and instead presenting itself as a
significant interferer that may adversely affect the performance.

g) Interference Margin (Voice)

The amount of energy outside the active set for voice users. A large value indicates that there is
significant interference for voice users. This metric is computed by summing the total pilot power
seen and then subtracting the sum of all the pilots in the Active Set from it. A large value for this
metric implies that there is significant pilot energy outside of the Active Set, which may present
significant interference for voice users, especially under heavy loading.

196
Nemo WindCatcher User Guide

h) Interference Margin (Data)

The amount of energy outside the active set for data users. A large value indicates that there is
significant interference for data users. This metric is computed by summing the total pilot power
seen and then subtracting the strongest pilot power in the Active Set from it. A large value for this
metric implies that there is significant pilot energy outside of the Active Set, which may present
significant interference for data users. The reason why only the strongest Active Set pilot is used is
because this is the only pilot that is typically used during a data session, even in soft handoff areas.
This is especially true of Lucent networks before ECP Release 21.

i) No Soft Handoff Candidates

The locations with low active Ec/Io (Ec/Io less then user defined threshold) and no available soft
handoff candidates. This metric indicates all locations where the best active Ec/Io is less than a
pre-defined threshold and there are no soft handoff candidates available with pilot strength above
the threshold either.

j) EVDO Downlink Serving to Best ASP SINR Diff

This metric returns the average difference between the serving pilot SINR to the strongest Active
Set pilot (Best ASP) SINR in each bin. A negative value for this metric in a bin means that the
serving pilot was not the strongest pilot in the Active Set for that bin. The degree of difference is
reflected in the metric value in dB.

k) EVDO Virtual Handoff Time – Max (slots)

This metric will display the database field for the maximum virtual handoff time detected within a
time bin, over all virtual handoffs that occurred in that bin. Do not display this metrics for all bins
with default value (-1). The default legends for this metric shall be as follows:
0-4, 4-8, 8-12, 12-16, 16-20, >20.

l) EVDO Virtual Handoff Time – Min (slots)

This metric will display the database field for the minimum virtual handoff time detected within a
time bin, over all virtual handoffs that occurred in that bin. Do not display this metrics for all bins
with default value (-1). The default legends for this metric shall be as follows:
0-4, 4-8, 8-12, 12-16, 16-20, >20.

m) EVDO Virtual Handoff Time – Avg (slots)

This metric will display the database field for the average virtual handoff time detected within a
time bin, over all virtual handoffs that occurred in that bin. Do not display this metrics for all bins
with default value (-1). The default legends for this metric shall be as follows:
0-4, 4-8, 8-12, 12-16, 16-20, >20.

n) EVDO Virtual Handoff Count

This metric will display the database field for the count of the number of virtual handoffs in each
bin. Do not display this metrics for all bins with default value (-1). The default legends for this
metric shall be as follows:
0-1, 1-2, 2-3, 3-5, 5-10, >10.

PN Analysis
The PN Analysis presents metrics for analyzing pilots in detail. This analysis uses both phone and
PN scanner data. In the case of multiple frequencies scanned by a PN scanner there is a drop down
selection for Frequency.

197
Nemo WindCatcher User Guide

a) Ec/Io of Selected PN
The Ec/Io of the Selected PN.

b) Ec of Selected PN
The Ec of the Selected PN.

c) Ec/Io of Selected PN as Nth Best Server

The Ec/Io of the Specific PN as Nth Best server. This displays the locations where the specific PN
is a Best Server.

d) Ec of Selected PN as Nth Best Server

The Ec of the Specific PN as Nth Best server. This displays the locations where the specific PN is
a Best Server.

e) Ec/Io of Nth Best Server

The Ec/Io of the Nth Best Server (N is user definable).

f) Ec of Nth Best Server

The Ec of the Nth Best Server (N is user definable).

g) Ec/Io Difference between Serving Pilots

The Ec/Io difference between the Nth and Mth best server (where N and M are best, 2nd best, 3rd
best server etc).

h) Ec Difference between Serving Pilots

The Ec difference between the Nth and Mth best server (where N and M are best, 2nd best, 3rd best
server etc).

i) Delay Spread of Selected PN

The delay spread of the selected PN.

j) Delay Spread of Selected PN as Nth Best Server

The delay spread of the Specific PN as Nth Best server. This displays the locations where the
specific PN is a Best Server.

k) Delay Spread of Nth Best Server

The pilot delay spread of the Nth Best Server (N is user definable).

l) PN of Nth Best Server

The pilot number for of the Nth Best Server (N is user definable).

m) PN of Pilot Set
The pilot number for of the Best Active, Best Candidate, Best Neighbor or Best PSMM PN (this
plot only applies to Phone data).

n) Delay of Selected PN
The delay of the selected PN.

o) Delay of Selected PN as Nth Best Server

The delay of the Specific PN as Nth Best server. This displays the locations where the specific PN
is a Best Server.

198
Nemo WindCatcher User Guide

p) Delay of Nth Best Server

The pilot delay of the Nth Best Server (N is user definable).

q) Io
The total power (dBm) received for CDMA channel

Problem Areas
From troubleshooting menu click Problem areas. The following problem areas are pre-defined in
Nemo WindCatcher.

a) Poor Coverage
This analysis identifies areas with poor coverage and no dominant pilot. These areas can
experience poor performance like high FER, dropped and blocked calls. The network performance
in these areas may also get worse during busy periods when the amount of interference is high.
Query Condition:
Rx Power < -95
Tx Power > 12
Dominant Pilot Ec/Io < -13

b) Pilot Pollution
This analysis identifies areas with multiple pilots and no dominant pilot in an area with good
receive power.
Query Condition:
Dominant Pilot Ec/Io < -12
Number pilots within 5 dB of best pilot > 4
Interference Margin (Voice) > 3
Rx Power > -85

c) Poor Pilot Dominance

This analysis identifies areas with lack of a dominant pilot.
Query Condition:
Dominant Pilot Ec/Io < -10
Interference Margin (Data) > 3

d) Reverse Link Interference

This analysis identifies areas experiencing reverse link interference. Also, these areas have good
performance on the forward link.
Query Condition:
Tx power > 12
Dominant Pilot Ec/Io > -12
Rx power > -85
Interference Margin (Voice) < 3

e) Un-necessary IS95A Handoff Zones

This analysis identifies areas that have handoff zones based on the IS95A algorithm that would be
eliminated by the IS95B / CDMA 2000 algorithm.
Query Condition:
Dominant Pilot Ec/Io > -10
IS95A Available Pilots (-13dB thresh) – IS95B Available Pilots (3dB range) > 0

199
Nemo WindCatcher User Guide

Event Definitions

A. Call Processing

1. Mobile Registration
This sub category includes all events related to the registration process.

Mobile Registration
This event is triggered when the mobile registers with the network.

Registration Failure
This event is triggered when the mobile fails to receive acknowledgement from the network for
registration.

Registration Rejected
This event is triggered when the registration request by the mobile is rejected by the network.

2. Call Origination
This sub category includes all events related to the call origination process.

Call Origination
This event is triggered when the mobile initiates a call.

Origination Access Probe Failure

This event is triggered when the call origination attempt fails during the access probe state.

Origination Failure – No CAM

This event is triggered when the call origination attempt fails before a channel Assignment
Message (CAM) is seen.

Origination Failure – Other

This event is triggered when the call origination attempt fails for other/unknown reasons.

Call Start
This event is triggered when an acknowledgement is received from the BTS regarding the service
connect complete message. (Data Network Blocked and Data Application Failure)

Mobile Re – Sync
This event is triggered when the losing sync in the Idle mode and re-syncs.

3. Page Response
This sub category includes all events related to the call termination process.

Page Response
This event is triggered when the mobile responds to incoming call.

Page Response Access Probe Failure

This event is triggered when the call termination attempt fails during the access probe state.

Page response Failure – No CAM

This event is triggered when the call termination attempts fail before a channel Assignment

200
Nemo WindCatcher User Guide

Message (CAM) is seen.

4. Call Blocked
This sub category includes all events related to the call blocking.

Call Blocked – Reorder Order

This event is triggered when the call attempt is blocked by the network with the reason given as
“Reorder”.

Call Blocked – Intercept Order

This event is triggered when the call attempt is blocked by the network with the reason given as
“Intercept”.

Call Blocked – Power Cycled Order

This event is triggered when the call attempt is blocked by the network with the reason given as
“Power Cycled”.

Call Blocked – Released

This event is triggered when the call attempt is blocked by the network with the reason given as
“Released”.

Call Blocked – Service Option Rejected

This event is triggered when the call attempt is blocked by the network with the reason given as
“Service Option Rejected”.

Call Blocked – Service Redirection

This event is triggered when the call attempt is blocked by the network with the reason given as
“Service Redirection”.

Call Blocked – System Busy

This event is triggered when the call attempt is blocked by the network with the reason given as
“System Busy”.

5. Call Connection
This sub category includes all events related to the call connection phase.

Traffic Channel Acquisition Failure

This event is triggered when the call attempt fails because the mobile cannot acquire the traffic
channel.

Call Connected
This event is triggered when the call successfully connects to the traffic state.

Connection Failure
This event is triggered when the call attempt fails because the mobile cannot connect to the
network.

Service Option Rejected

This event is triggered when the call attempt fails because the network rejects the requested
service option.

201
Nemo WindCatcher User Guide

6. Call End
This sub category includes all events related to the call end phase.

Call End – Data Network Access Failure

This event is generated when a call ends with call ends due to network access failure.

Call Dropped
This event is triggered when the call is dropped.

Call Fail
This event is triggered when there is an access failure.

Mobile Release
This event is triggered when the call is released by the mobile.

Base Release
This event is triggered when the call is released by the network.

No Base Release after Mobile Release

This event is triggered when the base release is not received after mobile release.

Call End
This event is triggered when the call ends but data is not available to determine the cause.

Call End – Holding Time Expired

This event is triggered when the hold time for a call exceeds the hold time defined the network.

7. Timers
This sub category includes all events related to the timers.

T5m Fade Time Expired

This event indicates that the T5 fade timer has expired. The T5 timer expires when there are no
two consecutive good frames for 5 seconds. T30m Loss of Paging Channel in Idle Mode

T30m Loss of Paging Channel in idle Mode

This event indicates that the Paging Channel has been lost in the idle state. During idle state if no
paging channel message is received for more than 3 seconds the T30m event is triggered.

T40m Loss of Paging Channel

This event indicates that the Paging Channel has been lost in the access state. During access state
if no paging channel message is received for more than 3 seconds the T40m event is triggered.

T42m No Layer 3 Response

This event indicates that the Paging Channel has been lost in the waiting for order state. After the
access probe has been acknowledged if no paging channel message is received for more than 12
seconds the T42m event is triggered.

N1m Retransmission Counter Expired

This event indicates that the N1m Retransmission Counter has expired. The N1m retransmission
counter expires when a Reverse link message is not acknowledged and it has to be retransmitted
13 times

202
Nemo WindCatcher User Guide

8. Supplemental Channel Assignment

This sub category includes all events related to the supplemental channel (SCH) processing.

New SCH Assignment

This event is triggered when a new SCH is assigned.

SCH Assignment Continuation

This event is triggered when the existing data burst is extended.

SCH Anchor Transfer

This event is triggered when an anchor transfer occurs on the SCH.

New Reverse SCH Assignment

This event is triggered when a new reverse SCH is assigned.

Handoff Process

a) Soft Handoff
This sub category includes all events related to soft handoff.

Soft Handoff Directed

This event is triggered when the network directs the mobile to perform soft handoff.

Soft Handoff Complete at Mobile

This event is triggered when the mobile confirms that soft handoff has been completed.

b) Hard Handoff
This sub category includes all events related to hard handoff.

CDMA 3G -> 2G Handoff Directed

This event is triggered when the network directs the mobile to handoff from a 3G to a 2G network.

Hard Handoff Directed

This event is triggered when the network directs the mobile to perform a hard handoff.

Hard Handoff Complete at Mobile

This event is triggered when the mobile confirms that hard handoff has been completed.

c) Handoff Failure
This sub category includes all events related to handoff failure.

Hard Handoff Completion Failure

This event is triggered when the hard handoff attempt fails.

Soft Handoff Completion Failure

This event is triggered when the soft handoff attempt fails.

Handoff Complete No HCM

This event is triggered when the mobile confirms that hard handoff has been completed but HCM
message is received.

203
Nemo WindCatcher User Guide

Network Problem

a) Pilot Set Warning

This sub category includes all events related to pilot warnings.

Candidate PN from Remaining Set

This event is triggered when the PN in the candidate set is from the remaining set.

New Sync PN from Remaining Set

This event is triggered when the Sync PN after call end is in the remaining set before the call end.

b) High Forward Link FER

This sub category includes all events related to high forward link FER.

High Forward Link FER

This event is triggered when the mobile experiences high forward FFER continuously for a
specified duration.

Vendor Events
This category includes all events related to the application layer. Since the application layer is a
function of the data collection device used, these events are categorized according to the different
vendors. Please refer to Vendor documentation for explanation of these events.

Others

a) File Indicators
This sub category includes all events related to file start and end.

File Start
This event is triggered when a new file is started.

File End
This event is triggered when a file is ends.

b) Services
This sub category includes all events related to Service redirection.

Global Service Redirection

This event is triggered when the network sends a service redirection message.

c) Protocol Revision
This sub category includes all events related to new system protocol revision.

New System Protocol Revision

This event is triggered when the calls protocol revision is changed.

EVDO Call Processing

This category includes all events related to EVDO Call Processing.

204
Nemo WindCatcher User Guide

a) Session
This category lists all applications related to EVDO data session.

EVDO Session Attempt Success

This event is triggered when a specific session attempt log message is returned with Result =
Received UATI Assignment message.

EVDO Session Attempt Failure

This event is triggered when a specific session attempt log message is returned with Result = Did
not receive UATI Assignment message.

EVDO Session Close

This event is triggered when a specific session attempt is closed.

b) Access Attempt
This category lists all the application related to the access attempts.

EVDO Access Probe Success

This event is triggered when an AN acknowledgement is received in response to a Connection
Request message sent by the AT requesting a connection for a call.

EVDO Access Probe Failure

This event is triggered when the AT fails to receive an AN acknowledgement in response to a
Connection Request message sent by the AT requesting a connection for a call.

c) Connection
This category lists all events related to Connection.

EVDO AT Connection Request

This event is triggered when there is a connection request at the Access Terminal

EVDO AN Connection Request

This event is triggered when there is a connection request at the Access Network

EVDO Connection Success

This event is triggered when a Traffic Channel Assignment (TCA) message is received and both
links are able to acquire the traffic channel.

EVDO Connection Failure

This event is triggered when the AT and AN fail to complete the connection after the initial access
probe requesting the connection was successful.

EVDO Connection Blocked

This event is triggered when, upon a connection request, a specific log message is returned with
the Result = Connection Denied.

EVDO Call Start

This event is triggered when a new EVDO call starts.

205
Nemo WindCatcher User Guide

EVDO Connection Access Network Release

This event is triggered when a specific connection release log message is returned with the Reason
= AN Connection Close.

EVDO Connection Access Terminal Release

This event is triggered when a specific connection release log message is returned with the Reason
= AT Connection Close.

EVDO Connection Dropped

This event is triggered when a specific connection release log message is returned with the Reason
= System Lost.

EVDO Connection Release (Other)

This event is triggered when a specific connection release log message is returned with any reason
not already captured by other events.

EVDO Traffic Channel Assignment

This event is triggered by the EVDO layer3 “Traffic channel assignment” message under “Default
route update”
protocol.

EVDO Traffic Channel Complete

This event is triggered by the EVDO layer3 “Traffic channel complete” message under “Default route
update”
protocol.

d) Handoff
This category includes all events related to Handoff.

EVDO Soft Handoff

This event is triggered when an EVDO soft handoff is detected.

EVDO Soft Handoff Complete

This event is triggered when the soft handoff completion message is send from the mobile to the
new and old BTS.

EVDO Virtual Handoff

This event is triggered whenever a change in DRC cover used in any slot is detected. If transition
to null cover temporarily, then Serving PN = “None” during period when DRC Cover = 0.

Unexpected DRC Cover Detected

This event is triggered when an unexpected DRC Cover mode is detected on the DRC Channel.
This configures the AT to use the DRC Cover Fixed Mode for FTAP and specifies the DRC
Cover.

EVDO Color Code Change

This event is triggered by the EVDO layer3 “Quick configuration” message under “Overhead
messages” protocol.

Monitor 3G1X Paging from EVDO Connection

This event is triggered when 3G1X paging message is detected during the time mobile is

206
Nemo WindCatcher User Guide

connected with EVDO service.

Hybrid Mode EVDO _ 3G1X Call

This event is triggered when a transition handoff from EVDO to 3G1X is detected.

Hybrid Mode 3G1X _ EVDO

This event is triggered when a transition handoff from 3G1X to EVDO is detected.

e) Reverse Transmission
This category lists all events related to the Reverse Transmission.

EVDO XOn
Each occurrence of the Layer 3 Reverse Traffic channel message Xon Request

EVDO XOff
Each occurrence of the Layer 3 Reverse Traffic channel message Xoff Request.

Reverse Activity Bit Busy

This event is triggered whenever the 1xEV Reverse Link Packet Summary message is received
with the Combined Busy Bit field equal to 1. The event shall be added to the Reverse Transmission
group under the EVDO Call Processing tab.

207
 Nemo WindCatcher User Guide

15 Appendix F: WiMAX Metrics

Basic Metrics

WIMAX Serving RF
This section consists of all metrics corresponding to the WIMAX Serving RF.

WIMAX Serving RSSI (dBm)

This metric plots the RSSI of the serving BSID in each bin.

WIMAX Serving CINR (dB)

This metric plots the CINR of the serving BSID in each bin.

WIMAX Transmit Power (dBm)

This metric plots the transmit power of the SS in each bin.

WIMAX Serving BSID

This metric plots the last serving BSID of the sector serving the SS in each bin.

WIMAX Serving Preamble Index

This metric plots the Preamble Index of the Serving BSID in each bin.

WIMAX Serving Frequency (MHz)

This metric plots the Serving Frequency for each bin.

WIMAX BSID
This section consists of metrics corresponding to WIMAX BSID

WIMAX RSSI by BSID

This metric plots the RSSI by BSID.

WIMAX CINR by BSID

This metric plots the CINR by BSID.

WIMAX Preamble Index

This section consists of metrics corresponding to WIMAX Preamble Index

WIMAX RSSI by Preamble Index

This metric plots the RSSI of the selected Preamble Index.

WIMAX CINR by Preamble Index

This metric plots the CINR of the selected Preamble Index.

WIMAX Data Quality

This section consists of metrics corresponding to Data Quality

WIMAX Downlink PDU Error Rate (%)

This metric plots the downlink PDU error rate experienced by the SS in each bin. Error Rate =
Downlink PDU Error Count / Downlink PDU Total Count * 100%.

208
Nemo WindCatcher User Guide

WIMAX Downlink PDU Received Count

This metric plots the total downlink PDU count sent to the SS in each bin.

WIMAX Uplink PDU Transmitted Count

This metric plots the total Uplink PDU count sent to the SS in each bin.

WIMAX Handover Failure Rate (%)

This metric plots the handover failure rate experienced by the SS in each bin.

WIMAX Downlink Average Jitter (ms)

This metric plots downlink average jitter experienced by the SS in each bin.

WIMAX Uplink Average Jitter (ms)

This metric plots uplink average jitter experienced by the SS in each bin.

WIMAX Downlink Maximum Jitter (ms)

This metric plots downlink maximum jitter experienced by the SS in each bin.

WIMAX Uplink Maximum Jitter (ms)

This metric plots uplink maximum jitter experienced by the SS in each bin.

WIMAX Downlink Minimum Jitter (ms)

This metric plots downlink minimum jitter experienced by the SS in each bin.

WIMAX Uplink Minimum Jitter (ms)

This metric plots uplink minimum jitter experienced by the SS in each bin.

WIMAX Data Rate

This section consists of metrics corresponding to Data Rate.

WIMAX Downlink Application Layer Throughput (kbps)

This metric reports the downlink application layer throughput to the SS in each bin.

WIMAX Uplink Application Layer Throughput (kbps)

This metric reports the uplink application layer throughput to the SS in each bin.

WIMAX Downlink MAC Layer Throughput (kbps)

This metric reports the downlink MAC layer throughput to the SS in each bin.

WIMAX Uplink MAC Layer Throughput (kbps)

This metric reports the uplink MAC layer throughput to the SS in each bin.

WIMAX Downlink TCP Throughput (kbps)

This metric reports the downlink TCP throughput to the SS in each bin.

WIMAX Uplink TCP Throughput (kbps)

This metric reports the uplink TCP throughput to the SS in each bin.

WIMAX Downlink IP Throughput (kbps)

This metric reports the downlink IP throughput to the SS in each bin.

209
Nemo WindCatcher User Guide

WIMAX Uplink IP Throughput (kbps)

This metric reports the uplink IP throughput to the SS in each bin

WIMAX Ping
This section consists of metrics corresponding to Ping.

WiMAX Average Round Trip Delay (ms)

This metric plots the average round trip delays in each bin.

WiMAX Maximum Round Trip Delay (ms)

This metric plots the maximum round trip delay in each bin.

WiMAX Minimum Round Trip Delay (ms)

This metric plots the minimum round trip delay in each bin.

WiMAX Number Pings

This metric displays no of pings in each bin.

WiMAX Ping Access Failure Rate (%)

Metric under development
WiMAX Ping Loss Count
Metric under development

WiMAX Ping Current Count

Metric under development

WIMAX Scan Data

This section consists of metrics corresponding to Scan Data

Scanner Best Preamble RSSI (dBm)

This metric displays Best RSSI for all scanned preambles.

Scanner Best Preamble CINR (dB)

This metric displays CINR corresponding to the best reported RSSI.

Scanner Best Channel RSSI (dBm)

This metric displays Best Channel RSSI.

Scanner RSSI by Preamble (dBm)

This metric displays Scanner RSSI for the selected Preamble.

Scanner CINR by Preamble (dB)

This metric displays Scanner CINR for the selected Preamble.

Scanner RSSI by Channel (dBm)

This metric displays Scanner RSSI for the selected Channel.

Troubleshooting
From troubleshooting menu click Troubleshooting. The following problem areas are pre-defined in
Nemo WindCatcher/WIMAX. Please note that set up has default values for all these troubleshooting
functions.

210
Nemo WindCatcher User Guide

WIMAX Poor Coverage

This metric identifies areas with poor coverage. Each time bin is flagged as having this problem
area if the following condition is met: Serving RSSI < -95dBm

WIMAX Negative Handover Area

This metric identifies areas with negative handover. Each time bin is flagged as having this
problem area if the following conditions are met: Serving RSSI < -90dBm AND (Best Neighbor
RSSI – Serving RSSI) > 6dB

WIMAX No Handoff Index Available

This metric identifies areas where no handoff index is available. Each time bin is flagged as having
this problem area if the following conditions are met: Serving RSSI < -90dBm AND (Serving RSSI
- Best Neighbor RSSI) > 6dB

WIMAX Possible Interference

This metric identifies areas with possible interference. Each time bin is flagged as having this
problem area if the conditions input by the user or the default value are met: Default value setting
is Serving RSSI > -80dBm AND Serving CINR < 5dB. The user has the flexibility of entering any
threshold for the two above metrics.

WIMAX Co-Channel Interference

Under this section, three metrics are available.

Server to 1st Best Intra-FA Nbr RSSI Difference: This metric identifies area where there
is a potential co-channel interferer based on the RSSI difference between Serving Preamble
Index/Sector to 1st Best Intra-FA Neighbor.

Server to 2nd Best Intra-FA Nbr RSSI Difference: This metric identifies area where there
is a potential co-channel interferer based on the RSSI difference between Serving Preamble
Index/Sector to 2nd Best Intra-FA Neighbor.

Server to 3rd Best Intra-FA Nbr RSSI Difference: This metric identifies area where there
is a potential co-channel interferer based on the RSSI difference between Serving Preamble
Index/Sector to 3rd Best Intra-FA Neighbor.

WIMAX Poor MAC Layer Throughput Analysis

This metric identifies areas with poor MAC Layer data throughput. A bin is flagged as having this
problem area if Downlink MAC Layer Throughput < 3Mbps.

(A) Network Access

(a) WiMAX Initial Ranging Request

This event is triggered when the first RNG-REQ message is transmitted by the MS when it is INIT or
SYNC state.

(b) WiMAX Initial Ranging Retry

This event is triggered every time the MS sends RNG-REQ message following the Initial RNG-REQ
message until the RNG-RSP message is received back from the BS.

211
Nemo WindCatcher User Guide

(c) WiMAX Location Update Ranging Request

This event is triggered when the RNG-REQ message is transmitted with the Location Update Ranging
Request Flag TLV enabled.

(d) WiMAX Network Re-entry Ranging Request

This event is triggered when the RNG-REQ message is transmitted with the Network Re-entry
Ranging Request Flag TLV enabled.

(e) WiMAX Initial Ranging Abort

This event is triggered when the SS receives a RNG-RSP message with Abort Flag enabled.

(f) WiMAX Initial Ranging Success

This event is triggered when BS sends a RNG-RSP message in response to a RNG-REQ message
sent by the SS which contains the BASIC CID and PRIMARY MANAGEMENT CID TLVs.

(g) WiMAX Initial Ranging Failure

This event is triggered when there is an initial RNG-REQ message seen but no corresponding
RNGRSP message in 3.2 seconds.

(h) WiMAX Basic Capability Request Failure

This event is triggered when SS goes into SYNC State before sending out the SBC-REQ message.

(i) WiMAX Basic Capability Response Failure

This event is triggered when SS goes into SYNC State before receiving back the SBC-RSP message.

(j) WiMAX Privacy Key Management Request Failure

This event is triggered when SS goes into SYNC State before sending out the PKM-REQ message.

(k) WiMAX Privacy Key Management Response Failure

This event is triggered when SS goes into SYNC State before receiving back the PKM-RSP message.

(l) WiMAX Registration Request Failure

This event is triggered when SS goes into SYNC State before sending out the REG-REQ message.

(m) WiMAX Registration Response Failure

This event is triggered when SS goes into SYNC State before receiving back the REG-RSP message.

(n) WiMAX Service Addition Request Failure

This event is triggered when SS goes into SYNC State before sending out the DSA-REQ (Dynamic
Service Addition Request) message.

(o) WiMAX Service Addition Response Failure

This event is triggered when SS goes into SYNC State before receiving back the DSA-RSP (Dynamic
Service Addition Response) message or before sending out DSA-ACK (Dynamic Service Addition
Acknowledge) message.

(B) WiMAX Session

(a) WiMAX Session Start

This event is triggered when SS receives DSA-RSP message and acknowledges back by sending
DSAACK message.

212
Nemo WindCatcher User Guide

(b) WiMAX Session End

This event is triggered when SS sends DREG-REQ (SS De-Registration Message) to BS.

(c) WiMAX Session Drop

This event is triggered when SS goes to SYNC state before sending out DREG-REQ message.

(C) Handover

(a) WiMAX MS Handover Request

This event is triggered when SS transmits MOB_MSHO-REQ (MS Handover Request) message when
it wants to initiate HO.

(b) WiMAX BS Handover Request

This event is triggered when BS transmits MOB_BSHO-REQ (BS Handover Request) message.

(c) WiMAX BS Handover Response

This event is triggered when SS receives MOB_BSHO-RSP (BS Handover Response) message.

(d) WiMAX BS Handover Response Failure

This event is triggered when SS goes into SYNC state without receiving MOB_BSHO-RSP (BS
Handover Response) message.

(e) WiMAX Handover Indicator

This event is triggered when SS transmits MOB_HO-IND message for final indication that it is about
to perform a HO.

(f) WiMAX Handover Cancel

This event is triggered when SS transmits MOB_HO-IND message with flag set to Cancel.

(g) WiMAX Handover Reject

This event is triggered when SS transmits MOB_HO-IND message with flag set to Reject.

(h) WiMAX Handover Ranging Request

This event is triggered when SS transmits RNG REQ message with Handover flag enabled (that is,
TLV RangingPurposeIndication = 1).

(i) WiMAX Handover Ranging Response

This event is triggered when SS receives RNG RSP message which contains BASIC CID and
PRIMARY MANAGEMENT CID TLVs.

(j) WiMAX Handover Success

This event is triggered when there is a match between BSID in HO Indicator Message and the next
chip status message. The handover latency associated with this event is measured from the HO-IND
to RNG-RSP message (which contains the CID TLVs).

(k) WiMAX Handover Failure

This event is triggered when there is either a mismatch between BSID in HO Indicator Message and
next chip status message OR when the RNG RSP message is not received by MS with BASIC CID
and PRIMARY MANAGEMENT CID TLVs and the SS goes to SYNC state.

213
Nemo WindCatcher User Guide

(E) Others

(a) WiMAX Data File Start

This event is triggered for the first-time stamp and location in the drive data.

(b) WiMAX Data File End

This event is triggered for the last time stamp and location in the drive data.

214
 Nemo WindCatcher User Guide

16 Appendix G: Event Definitions

GSM EVENTS
Call Setup
GSM Alerting
This event is triggered when MSC informs the mobile that the called subscriber is being alerted via a
ring.
GSM Call Start
If there is no Call Origination message available and a DCCH, SACCH or FACCH is seen, the event
GSM Call Start is generated.
GSM Call Start Emergency
The Call Start Message when trying to call an emergency number. The mobile phone and the SIM
card have a pre-programmed list of emergency numbers.
GSM Call Start (Page response)
This event is triggered when mobile responds to an incoming call. Mobile receives RR PAGING
REQUEST TYPE 3 message and in response it sends a RR CHANNEL REQUEST message on RACH to
access a channel.
GSM Call Start (Mobile Originated)
This event is triggered when mobile initiates a call. This event is triggered by Channel Request
message. This message requests the Base Station System (BSS) for allocation for radio resources for
the RR connection setup. The mobile now waits for an assignment on the Access Grant Channel
(AGCH).
GSM Call Start (location Update)
In an idle mode whenever the mobile location is updated it establishes a RR connection to send the
location update to the network. This event is triggered by the message
GSM Call Established
This event is triggered by GSM CC Connect Message on SACCH Channel. This message is sent by
MSC to inform mobile that the call is connected.
GSM Access Failure
Call Setup Failure before GSM RR Immediate Assignment Message Setup Failure
GSM Call Connected
This event is triggered as soon as the call is connected and SACCH, FACCH or DCCH is seen of the
first time after the Idle mode.

Call handover
GSM Assignment
The event is triggered on GSM RR Assignment command message on DCCH. MSC informs the BSS
about the allocated voice circuit. The call is also switched from signaling to voice. The BSS notifies
the Mobile about the changeover to voice mode.
GSM Assignment Complete
The event is triggered on GSM RR Assignment Complete message on DCCH. This is mobile’s
acknowledgement to Assignment message.
GSM Assignment Failure
The event is triggered if the Assignment is failed.
GSM Radio Link Failure
This event is triggered when the Radio link cannot be established.
GSM Handover
This event is triggered on GSM RR Handover Command.
GSM Handover failure

215
 Nemo WindCatcher User Guide

this event is triggered when the handover attempt fails. In reply to Handover Command message if
GSM RR handover failure message appears on DCCH.
GSM Negative Handover
After handover if the Rx Lev of new channel is 3db less than the previous channel, negative handover
event is triggered.
GSM Ping Pong Handover
if the handover is done again within 3 seconds to the previous channel Ping Pong handover event is
triggered.

Location Update
Location Update
It is generated when periodic Location update takes place. The event is triggered on GSM MM
Location Updating request message.
Location Update Rejected
The event is triggered when the location update fails i.e. on the generation of the GSM MM Location
Updating reject message.

Signal Quality
GSM High Rx Qual
The event is triggered when the Rx Qual Sub in the Measurement Report is greater or equal to 5.

Call End
GSM Call Dropped
This message is triggered when the call is dropped.
GSM Call Blocked
Call Setup failure after the GSM RR Immediate Assignment message and before Call Established are
referred as Blocked Calls.
GSM Channel Normal Release
This event is triggered when the Channel is released normally.
GSM Channel Abnormal Release
This event is triggered when the channel is abnormally released.
GSM Channel Release without Call release
This event is triggered when the channel is released without the call being released.
GSM Call End
The event comes when the call is released. The event is triggered on the Channel Release Message
on GMS RR DCCH.

GPRS Event

Connection Setup
MM Attach Request: This event is triggered by GPRS MM –Attach Request Message. It is the request
by UE to start the Data session.
MM Attach Accept
If the attached request is accepted this event is generated. The event is triggered by GPRS MM –
Accept Request Message
MM Attach Complete
When the Attach is accepted, the MM Attach Complete message is sent by the UE. It is triggered by
GPRS MM –Attach Complete Message
MM Attach reject
If the attached request is rejected this event is generated.
MM Detach Request

216
 Nemo WindCatcher User Guide

When the session is completed, detach is requested to finish the connection. It is triggered by GPRS
MM – Detach Request Message.
MM Detach Accept
This event is generated when the detach request is acknowledged and accepted by the UE. It is
triggered by GPRS MM – Detach Accept Message.
Call Start – GPRS Connection
This event is triggered when the channel is requested by UE. It is triggered on GSM RR – Channel
Request Message.
GSM Call Start Retry
If the Channel request by UE is not acknowledged first time and channel is requested again by UE
this event is generated.
GSM Immediate Assignment-Dedicated mode
This event is triggered on GSM RR – Immediate Assignment Message with Mode defined as
Dedicated.
GSM Immediate Assignment-TBF
This event is triggered on GSM RR – Immediate Assignment Message with Mode defined as BF i.e.
Temporary Data Flow. A TBF is temporary and is maintained only for the duration of the data transfer
GPRS Packet Downlink Assignment
This event is generated when the Packet is ready to be sent on the downlink.
GPRS Packet Uplink Assignment
This event is generated when the Packet is ready to be sent on the uplink.
Activate PDP Context request
This event is triggered by GPRS SM –Active PDP Context Request message. It is the request by UE to
start the Data session.
Deactivate PDP Context request
When the session is completed, Deactivate PDP Context is requested to finish the connection. It is
triggered by GPRS SM – Deactivate PDP Context Request message.
Deactivate PDP Context Request-Abnormal Cause
When the Deactivate PDP Context is requested due to session being ended abnormally, this event is
generated.

Call End
Activate PDP Context Accept
If the Activate PDP Context request is accepted this event is generated. The event is triggered by
GPRS SM – Active PDP Context Accept message.
Activate PDP Context Reject
If the Activate PDP Context request is rejected this event is generated.

Modify PDP Context Accept

If the Activate PDP Context request is accepted with some conditions this event is generated.
Deactivate PDP Context Accept
This event is generated when the Deactivate PDP Context request is acknowledged and accepted by
the UE. It is triggered by GPRS SM – Deactivate PDP Context Accept Message.

UMTS Events

Call Setup
UMTS Connection Request
This event Is triggered when UMTS Connection request is made. It is triggered by RRC Connection
Request on CCCH.
UMTS Connection Rejected

217
 Nemo WindCatcher User Guide

This event is triggered when UMTS Connection Request is rejected

UMTS Connect request retry
It is triggered when the second or onward Connection requests are made.
UMTS Connection Access Failure
It is the Setup failure before RRC Setup Connection Complete
UMTS RRC Established
This event is generated when the RRC connection is established. This is generated by RRC UMTS
Alerting
This event is triggered when MSC informs the mobile that the called subscriber is being alerted via a
ring. It is generated when GSM CC Alerting message is triggered
UMTS Radio Link Failure
This event is triggered when the Radio link cannot be established.
UMTS Call established
This event is generated when the Call is established. It is triggered by GSM CC-Connect message.

State Transition
UMTS Cell Update request
The event is generated when the UE requests a Cell Update procedure. The event is triggered by Cell
Update Message.
UMTS Cell Update Retry
The event is generated if the Cell Update request of UE is not acknowledged by the RNC and it sends
the Cell Update Request again.
Active Set Update
The event is generated when the UTRAN/RNC sends the Active Set Update message to update the
UE’s active set while in the Cell DCH state.
Active Set Update Complete
The event is triggered when the Active set Update is completed on the UE. The event is triggered by
Active Set Update Complete Message.
UMTS directed retry Attempt
Directed retry re-directs the traffic to neighboring cells in case of congestion in Call Setup. This event
is generated when the attempt to Direct Retry is made.
UMTS directed retry success
Directed retry re-directs the traffic to neighboring cells in case of congestion in Call Setup. This event
is generated when the attempt to Direct Retry is successful.
UMTS Directed Retry Failure
Directed retry re-directs the traffic to neighboring cells in case of congestion in Call Setup. This event
is generated when the attempt to Direct Retry is failed.
UMTS DCH to FACH Transition
The event is triggered when transition from Dedicated Channel to Forward Access Channel is made.
UMTS DCH to PCH transition
The event is triggered when transition from Dedicated Channel to Paging Channel is made.
UMTS DCH to URA_PCH Transition
The event is triggered when transition from Dedicated state to URA_PCH (UTRAN Registration Area
_ Paging Channel) state is made. In URA_PCH state the UE will perform CELL UPDATE only when the
URA is changed for a UE.
UMTS FACH to DCH transition
The event is triggered when transition from Forward Access Channel to Dedicated Channel is made
UMTS FACH to PCH transition
The event is triggered when transition from Forward Access Channel to Paging Channel is made
UMTS FACH to URA_PCH Transition
The event is triggered when transition from Forward Access Channel to URA_PCH is made.

218
Nemo WindCatcher User Guide

UMTS PCH to FACH transition

The event is triggered when transition from Paging Channel to Forward Access Channel is made
UMTS URA_PCH to FACH transition
The event is triggered when transition from URA_PCH to Forward Access Channel is made.
UMTS FACH to Idle Mode Transition
The event is triggered when transition from Forward Access Channel Idle mode is made.
UMTS Inter Frequency Handover Directed
The event is triggered on the Inter Frequency Handover Command.
UMTS Inter Frequency Handover Success
The event is generated if the Inter frequency handover is successful.
UMTS Inter Frequency Handover Failure
The event is generated if the Inter frequency handover fails.
HSDPA Serving Cell Repoint
For Data when the Cell is changed this event is triggered.
UMTS to GSM Transition
The event is generated when the transition from UMTS to GSM is made
GSM to UMTS transition
The event is generated when the transition from GSM to UMTS is made
Inter-RAT Handover GSM to UTRAN Directed
The event is triggered when the handover is directed from GSM to UMTS. The event is triggered by
handover to UTRAN Message
Inter-RAT Handover GSM to UTRAN Complete
The event is triggered when the handover is successfully completed from GSM to UMTS. The event is
triggered by Handover Complete Message
Inter-RAT Handover UTRAN to GSM Directed
The event is triggered when the handover is directed from UMTS to GSM. The event is triggered by
handover from UTRAN Message
Inter-RAT Handover UTRAN to GSM Complete
The event is triggered when the handover is successfully completed from UMTS to GSM. The event is
triggered by Handover Complete Message
Inter-RAT Handover GSM to UTRAN Failure
The event is triggered when the handover from GSM to UMTS is not successful.
Inter-RAT Handover UTRAN to GSM Failure
The event is triggered when the handover from UMTS to GSM is not successful
GSM Monitoring UMTS
The event is generated when the UE is on GSM network and UMTS network is being monitored
UMTS Monitoring GSM
The event is generated when the UE is on UMTS network and GSM network is being monitored
Inter-RAT Cell Change Order from UTRAN
The event is triggered when the Cell Change order is directed from UMTS to GPRS/EGPRS for Data.
The event is triggered by Cell Change Order from UTRAN Message
Inter-RAT Cell Change Order from UTRAN Failure
The event is triggered when the Cell Change Order from UMTS to GPRS/EGPRS is not successful.
Inter-RAT Cell Change Order to UTRAN
The event is triggered when the Cell Change order is directed from GPRS/EGPRS to UMTS for Data.
The event is triggered by Cell Change Order to UTRAN Message
Inter-RAT Cell Change Order to UTRAN Failure
The event is triggered when the Cell Change order from GPRS/EGPRS to UMTS is not successful.
UMTS Compressed Mode Start
Compressed mode is needed if the UE needs to perform Inter-Frequency or Inter-RAT measurements.
This event is triggered when the Compressed Mode Starts.

219
 Nemo WindCatcher User Guide

UMTS Compressed Mode End

Compressed mode is needed if the UE needs to perform Inter-Frequency or Inter-RAT measurements.
This event is triggered when the Compressed Mode Ends.
HSDPA Started
The event is triggered when the HSDPA Session starts. It is triggered by Radio Bearer Setup Complete
Message.
HSDPA Stopped
This event is triggered when HSDPA session stops
HSUPA Started The event is triggered when the HSUPA Session starts.
HSUPA Stopped
This event is triggered when HSUPA session stops

Signal Quality
UMTS High BLER
This event is generating when the BLER is higher than a specific threshold.

Call End
UMTS Dropped Call
Drop Calls are triggered after CC Alerting (CS) or SM Activate PDP Context Accept (PS)
UMTS Call blocked
Setup Failures after RRC Connection Setup Complete and before CC Alerting (CS) or SM Activate
PDP Context Accept (PS) are categorized as Block Calls
UMTS Abnormal End
The event is generated when there is any abnormal call end.
UMTS UE Release
The event is generated when the user ends the call.
UMTS Ran Release
The event is generated when the system releases the call. This is triggered by RRC Connection
Released Message.

220
 Nemo WindCatcher User Guide

17 Appendix H: VoLTE Metrics

Avg RTP Packet Delay:

It is calculated as the average of the time difference between current packet and previous packet over
the bin
Max RTP Packet Delay:
It is calculated as the Maximum of the time difference between current packet and previous packet
at that particular bin
Avg RTP Jitter:
RTP Jitter is calculated continuously as each data packet i is received from that source SSRC,
Using the current D for that packet and the previous packet i-1.
J(i) = j(i-1) + (|D(I,i-1)| - j(i-1))/16
This Value is averaged over a bin and provided as Avg RTP jitter
Max RTP Jitter:
The maximum value of jitter in that bin is shown as Max RTP jitter.
Average RTP Packet Loss Rate:
During sip session, if an RTP message has a sequence number > last sequence number + 1, we know
there are some missing packets. In a bin. We know what the expected number of packets should be
based on the current sequence number. Packet Loss rate upon discovering missing packets would be
= 100* packet loss count / (total expected packets). We average this value over the bin and we get
the average rate.
Max RTP Packet Loss Rate:
Maximum value of RTP Packet Loss Rate in a particular bin
Avg Packet Loss:
Average count of Packet loss per bin
Avg RTP Round Trip Time:
RTP round trip time is based on A side and B side devices. This is basically the total uplink
time and downlink time and is calculated based on RTP sequence number identification from A side
to B side and another sequence number from B side to A side. These values are averaged over the
bin.

221
 Nemo WindCatcher User Guide

Max RTP Round Trip Time:

Based on the above definition, the Maximum value of RTT in a particular bin
Audio Quality:
POLQA which stands for Perpetual Objective Listening Quality Analysis. POLQA compares a known
speech signal to the degraded voice signal by simulating human hearing. Voice Quality can be
determined for Narrow Band (NB), Wide band (WB) and Super Wide Band (SWB)

POLQA Downlink:
Voice Quality for Downlink. Can be determined for NB, WB or SWB based on the band
POLQA Uplink:
Voice Quality for Uplink. Can be determined for NB, WB or SWB based on the band
Video Quality:

Video MOS:
Video MOS (Mean Opinion Score) is a number, from 1 to 5, 1 being the worst and 5 being the best
and is similar to audio MOS.
Video Jerkiness:
Jerkiness is a motion perceived as a series of distinct snapshots. This metric will provide the Jerkiness
of a Video
Video Blockiness:
Block distortion is a spatial degradation and is caused by coding impairments. This metric will provide
the Blocking of a Video
Video Blur:
Blurriness is a spatial degradation and is mostly caused by coding impairments. It is characterized by
the reduced sharpness of edges and loss of spatial detail.
Avg RTP HO Interruption Time:
During LTE Handover, there might be some dropped packets of RTP. We note the time we get the
last RTP incoming packet before handover request. We also note the time we get the first RTP
incoming packet after handover success. The difference is the handover interruption time. Average
value over the bin gives the Avg RTP HO interruption Time
Sum RTP HO Interruption Time:
Based on the above definition the sum of HO interruption time gives this metric on that particular bin.
Average RTP HO Packet Loss:
During LTE Handover there might be some dropped packets of RTP. We note the last incoming RTP
sequence number before Handover request. After successful handover (handover success event) we
note the first incoming RTP sequence number. The difference provides us the interruption time.
Sum RTP HO Packet Loss:
Based on the above metric definition, Sum RTP HO packet loss is the sum of all interruption loss per
bin

222
 Nemo WindCatcher User Guide

Semi-Persistent Scheduling:
The UE is pre-configured by the eNB with an SPS-RNTI (allocation ID) and a periodicity. Once pre-
configured, if the UE were to receive an allocation (DL / UL) using the SPS-RNTI (instead of the typical
C-RNTI), then this one allocation would repeat according to the pre-configured periodicity.
UL Interval (ms):
The pre-configured periodicity for UL
DL Interval (ms):
The pre-configured periodicity for DL
TTI Bundling:
When network sends a grant (DCI 0), UE transmit PUSCH at only one specific sub frame (4 ms after
the DCI 0 reception). TTI Bundling is a method in which UE transmit a PUSCH in multiple sub frames
in a row (4 sub frames according to current specification). In other words, UE transmit a PUSCH in a
'BUNDLED TTI. Values can be either TRUE or FALSE

223
 Nemo WindCatcher User Guide

18 Appendix I: LTE-Adv Metrics

PCI:
This metric will allow the user to plot the Physical Cell Id of the Primary cell (P-cell) and Secondary
Cells (S-cells 1-7)
EARFCN:
This metric will provide the EARFCN of the Primary cell (P-cell) and Secondary Cells(S-cells1-7).
EARFCN is defined as E-UTRA Absolute Radio Frequency Channel Number and is based on a 100 kHz
channel raster.
RSRP (dBm):
This metric will allow the user to plot the RSRP of the Primary cell (P-cell), Secondary Cells (S-cells
1-7) and the 1-3 best S-cells
Reference Signal Received Power (RSRP) is defined as a measurement which provides cell-specific
signal strength metric. This measurement is mainly used to rank different LTE cells according to their
signal strength as an input for handover and cell reselection decisions. The RSRP of a cell is defined
as the linear average over the power contributions (in Watts) of the Resource Elements (REs) which
carry cell-specific RS within the considered measurement bandwidth.
RSRQ (dB):
This metric will allow the user to plot the RSRQ of the Primary cell (P-cell), Secondary Cells (S-cells
1-7) and the 1-3 best S-cells
Reference Signal Received Quality (RSRQ) is defined as a measurement which provides a cell-specific
signal quality metric. Similarly, to Reference Signal Received Power (RSRP), this measurement is
mainly used to rank different LTE cells according to their signal quality as an input for handover and
cell reselection decisions, for example in scenarios for which RSRP measurements do not provide
sufficient information to perform reliable mobility decisions. The RSRQ is defined as the ratio N ·
RSRP/ (LTE carrier RSSI), where N is the number of Resource Blocks (RBs) of the LTE carrier Received
Signal Strength Indicator (RSSI) measurement bandwidth. While RSRP is an indicator of the wanted

224
 Nemo WindCatcher User Guide

signal strength, RSRQ additionally takes the interference level into account due to the inclusion of
RSSI. RSRQ therefore enables the combined effect of signal strength and interference to be reported
in an efficient way. If the UE is equipped with multiple antennas, the reported RSRQ value is not
permitted to be lower than the RSRQ computed on the individual branches.
RS CINR (dB):
This metric will allow the user to plot the RS CINR of the Primary cell (P-cell), Secondary Cells (S-
cells 1-7) and the 1-3 best S-cells
Reference Signal Carrier-to-Interference-and-Noise Ratio is the ratio between the power of the Radio
Frequency (RF) carrier bearing the wanted signal and the total power of interfering signals and
thermal noise.
Transmit Power:
This metric will provide UE transmit power of P-cell and S-cells (1-7), 1-3rd best S-cell
PUSCH Tx Power:
This metric will provide physical uplink shared channel transmit power transmit power of P-cell and
S-cells (1-7), 1-3rd Best S-cell
PUCCH Tx Power:
This metric will provide physical uplink shared channel transmit power transmit power of P-cell and
S-cells (1-7), 1-3rd Best S-cell
Avg DL PRB Assignment
This metric will provide Average Downlink Physical Resource Block Assignment of P-cell, S-cells (1-
7) and 1-3rd Best cells. A unit of transmission resource consisting of 2 sub-carriers in the frequency
domain and 1 timeslot (0.5 ms) in the time domain.
Avg UL PRB Assignment
This metric will provide Average Uplink Physical Resource Block Assignment of P-cell, S-cells (1-7)
and 1-3rd Best cells. The unit of transmission resource consisting of 2 sub-carriers in the frequency
domain and 1 timeslot (0.5 ms) in the time domain.

225
Nemo WindCatcher User Guide

Bandwidth:

DL Bandwidth:
This metric will provide downlink bandwidth of each component carrier.
UL Bandwidth:
This metric will provide uplink bandwidth of each component carrier.
Aggregated BW:
Aggregated bandwidth at each data point It can be for the chosen EARFCNs user wants to aggregate.
Once the EARFCNs are chosen, the KPI can be dragged to the map. It is average value of bandwidth
of all Cells within the bin

S-cell Count:
The number of S-Cells observed in the last RRC reconfiguration message received within a bin.

226
Nemo WindCatcher User Guide

MCS:

Dominant DL TB0 MCS

This metric will provide dominant MCS index for transport block 0 on downlink for P-cell and S-Cells
(1-7)
Dominant DL TB1 MCS
This metric will provide dominant MCS index for transport block 1 on downlink for P-cell and S-Cells
(1-7)
Dominant DL TB0 Modulation Type
This metric will provide dominant Modulation type for transport block 0 on downlink. This modulation
could be QPSK, 16 QAM or 64 QAM for P-cell and S-Cells (1-7)
Dominant DL TB1 Modulation Type
This metric will provide dominant Modulation type for transport block 1 on downlink. This modulation
could be QPSK, 16 QAM or 64 QAM for P-cell and S-Cells (1-7)
Dominant UL TB MCS
This metric will provide dominant MCS index for transport block on uplink for P-cell and S-Cells (1-
7)

227
 Nemo WindCatcher User Guide

Throughput:

Physical DSCH Throughput

This metric will provide Physical Downlink Shared Channel throughput for P-cell and S-cells (1-7).
The main downlink data bearing channel in LTE. It is used for all user data, as well as for broadcast
system information which is not carried on the Physical Broadcast Channel (PBCH), and for paging
messages.
Physical USCH Throughput
This metric will provide Physical Uplink Shared Channel throughput for P-cell and S-cells (1-7). The
LTE uplink physical channel carrying scheduled data traffic and control signaling if some is required
to be transmitted in the same sub frame.
Application Type
The type of data application, for e.g. FTP, HTTP etc.
Data Quality:

228
 Nemo WindCatcher User Guide

Physical DSCH BLER

This metric will provide block error rate on physical downlink shared channel for P-cell and S-cells
(1-7)
Physical USCH BLER:
This metric will provide block error rate on physical uplink shared channel for P-cell and S-cells (1-7)
Channel Quality Indicator:
This metric will provide Code Word 0 (CW0) and Code Word 1 (CW1) CQI values for the primary and
secondary cell(s).
MIMO mode:
This metric will provide the serving MIMO mode for P-cell and S-cell(s)
MIMO attribute:
This metric will provide the MIMO attributes for P-cell and S-cell(s)
Rank:
This metric will provide the maximum number of independent spatial channels in a bin for P-cell and
S-cell(s)
Latency KPIs:
There are Latency KPIs available in the event tree in event window to help the users to analyze the
drive and improve the performance of the network
• LTE CA On
• LTE CA Configured
• LTE CA Activated

229
 Nemo WindCatcher User Guide

19 Appendix J: LTE-Adv Events

Events for LTE Advanced are available under the “Event Settings”. Open
the Event Symbols Selection window by clicking the “Event Settings” in
the Home view and then select the LTEA-A events from the LTE event
menu.

230
 Nemo WindCatcher User Guide

20 Technical Support
If you have questions on or beyond this documentation about Nemo tools, please contact our
technical support service through Nemo Support Portal at http://nemo.support.keysight.com, call
us (local phone numbers can be found in chapter Phone and email support) or send us an email at
[email protected]. Note that for full support you need to have the Maintenance
Agreement.

20.1 Nemo Support Portal

Nemo Support Portal is a web interface for technical support, product-related questions, and RMA
requests. It offers a fast and convenient way to reach our technical support team and submit
repair, warranty repair, and calibration requests. Customers can open a support ticket, follow the
status of existing tickets, and request technical support 24/7/365. Furthermore, the Nemo Support
Portal includes a Knowledge Base for the most frequent and latest topics on Nemo Products.
Submitting a ticket via Nemo Support Portal ensures that our technical specialists have all the
necessary information available to solve your support case, resulting in faster response times.
Please go to http://nemo.support.keysight.com to access the portal and click Request access to
obtain a password to the system.

20.2 Phone and email support

During the warranty period, the phone support related to potential software errors is free of
additional charge. Registered users with a valid Maintenance Agreement are entitled to full
support. Nemo Support Portal is the preferred channel for technical support requests, but you can
also send us an email. When emailing, please let us know the number of your Software
Maintenance and Support Agreement.
Please contact us at the following locations (global email address [email protected]):

Global
Tel. +358 50 395 7800

Americas
Tel. +1 469 951 9105

APAC
Tel. +65 9746 2431

P.R. China
Tel. +86 10 6567 8528

India
Tel. +91 982 0016372

231
 Nemo WindCatcher User Guide

20.3 Locations for Keysight Technologies

Online assistance: http://www.keysight.com/find/assist

If you do not have access to the Internet, one of these centers can direct you to your nearest
representative:
Should the Declaration of Conformity be required, please contact a Keysight Sales Representative,
or the closest Keysight Sales Office. Alternately, contact Keysight at: www.keysight.com.

This information is subject to change

without notice.
© Keysight Technologies Finland, Ltd. 2017
Published in Finland, July 2017
NTW00000A-90001

232