Beruflich Dokumente
Kultur Dokumente
User Guide
Notices
U.S.Government Rights Warranty
Copyright Notice
The Software is “commercial computer THE MATERIAL CONTAINED IN THIS
© Keysight Technologies Finland, Ltd. 2017 software,” as defined by Federal DOCUMENT IS PROVIDED “AS IS,” AND IS
No part of this manual may be reproduced in Acquisition Regulation (“FAR”) 2.101. SUBJECT TO BEING CHANGED, WITHOUT
any form or by any means (including Pursuant to FAR 12.212 and 27.405-3 and NOTICE, IN FUTURE EDITIONS. FURTHER, TO
electronic storage and retrieval or Department of Defense FAR Supplement THE MAXIMUM EXTENT PERMITTED BY
translation into a foreign language) without (“DFARS”) 227.7202, the U.S. government APPLICABLE LAW, KEYSIGHT DISCLAIMS ALL
prior agreement and written consent from acquires commercial computer software WARRANTIES, EITHER EXPRESS OR IMPLIED
Keysight Technologies, as governed by under the same terms by which the WITH REGARD TO THIS MANUAL AND ANY
United States and international copyright software is customarily provided to the INFORMATION CONTAINED HEREIN,
laws. public. 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 License PARTICULAR PURPOSE. KEYSIGHT SHALL NOT
NTW00000A-90001 Agreement (EULA), a copy of which can be BE LIABLE FOR ERRORS OR FOR INCIDENTAL
found at OR CONSEQUENTIAL DAMAGES IN
Edition http://www.keysight.com/find/s CONNECTION WITH THE FURNISHING, USE,
Edition 1.00, July 2017 weula. The license set forth in the EULA OR PERFORMANCE OF THIS DOCUMENT OR
Documents Software Version represents the exclusive authority by ANY INFORMATION CONTAINED HEREIN.
which the U.S. government may use, SHOULD KEYSIGHT AND THE USER HAVE A
Published by: modify, distribute, or disclose the SEPARATE WRITTEN AGREEMENT WITH
Keysight Technologies Finland, Ltd. Software. The EULA and the license set WARRANTY TERMS COVERING THE
Yrttipellontie 10 forth therein, does not require or permit, MATERIAL IN THIS DOCUMENT THAT
90230 Oulu among other things, that Keysight: (1) CONFLICT WITH THESE TERMS, THE
Furnish technical information related to WARRANTY TERMS IN THE SEPARATE
Technology Licenses commercial computer software or AGREEMENT WILL CONTROL.
commercial computer software
The hardware and/or software described in documentation that is not customarily
this document are furnished under a license provided to the public; or (2) Relinquish
and may be used or copied only in to, or otherwise provide, the government
accordance with the terms of such license. rights in excess of these rights customarily A CAUTION notice denotes a hazard. It calls
provided to the public to use, modify, attention to an operating procedure,
practice, or the like that, if not correctly
Declaration of Conformity reproduce, release, perform, display, or
performed or adhered to, could result in
disclose commercial computer software
Declarations of Conformity for this product and or commercial computer software damage to the product or loss of important
for other Keysight products may be downloaded documentation. No additional data. Do not proceed beyond a CAUTION
from the Web. Go to government requirements beyond those notice until the indicated conditions are fully
http://www.keysight.com/go/conform set forth in the EULA shall apply, except to understood and met.
ity the extent that those terms, rights, or
and click on “Declarations of Conformity.” You licenses are explicitly required from all
can then search by product number to find the providers of commercial computer
latest Declaration of Conformity. software pursuant to the FAR and the
A WARNING notice denotes a hazard. It calls
DFARS and are set forth specifically in
attention to an operating procedure,
writing elsewhere in the EULA. Keysight
practice, or the like that, if not correctly
shall be under no obligation to update,
performed or adhered to, could result in
revise or otherwise modify the
personal injury or death. Do not proceed
Software. With respect to any technical
beyond a WARNING notice until the
data as defined by FAR 2.101,
indicated conditions are fully understood
pursuant to FAR 12.211 and 27.404.2
and met.
and DFARS 227.7102, the U.S.
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
3
Table of Contents
4
Nemo WindCatcher User Guide
5
Nemo WindCatcher User Guide
6
Nemo WindCatcher User Guide
7
Nemo WindCatcher User Guide
8
Nemo WindCatcher User Guide
9
Nemo WindCatcher User Guide
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 2010 C++ Redistributable from the following link:
(x86) https://www.microsoft.com/en-us/download/details.aspx?id=5555
(x64) https://www.microsoft.com/en-US/Download/details.aspx?id=14632
3. Install the Microsoft Visual Studio 2012 C++ Redistributable from the following link for (x86) and (x64)
https://www.microsoft.com/en-us/download/details.aspx?id=30679
4. Install the Microsoft .NET Framework 4.7.1 from the following link
https://www.microsoft.com/en-us/download/details.aspx?id=56116
10
Nemo WindCatcher User Guide
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 your current installed version of Nemo WindCatcher is older than version 3.6.3.0, please make sure to
uninstall Nemo WindCatcher version using Control Panel -> Programs and Features option prior to installing
this version
For any releases after 3.6.3.0, if Nemo WindCatcher is already installed on the computer, a pop-up window
will appear reminding to uninstall the existing version before installing the new version.
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.
11
Nemo WindCatcher User Guide
The default configuration, once set, will be saved until it is explicitly changed by the user.
12
Nemo WindCatcher User Guide
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 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.
13
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 they occur.
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.
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.
14
Nemo WindCatcher User Guide
15
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.
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.
16
Nemo WindCatcher User Guide
Database Settings
Nemo Windcatcher has support for MS Access and for SQLite database type. The user may define a
default ‘Database Location’ to automatically save generated database files
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.
17
Nemo WindCatcher User Guide
3.1.1.3 Interface
18
Nemo WindCatcher User Guide
• Open 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
19
Nemo WindCatcher User Guide
20
Nemo WindCatcher User Guide
Layer Control
This setting allows user to select the number of metric layers available in the Map View. Maximum
number of the layers is 10 and the default value is 5.
21
Nemo WindCatcher User Guide
3.1.1.4 RF configuration
22
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 to 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.
23
Nemo WindCatcher User Guide
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 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.
24
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
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).
25
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.
26
Nemo WindCatcher User Guide
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.
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.
27
Nemo WindCatcher User Guide
7. Device View: Lets you view the dataset by the devices and lets you open them individually
*The users can control the size of the dataset that gets loaded into Dataset Manager. Size limit can be specified by going to
Processing Default → Interface → Dataset Manager. If you set the size limit to 0MB, then all the datasets processed in
windcatcher, will get loaded into the dataset manager.
Currently, the default is set to 700 MB. Any dataset processed or opened which exceeds the size limit of 700 MB will open
automatically in Dataset Manager View
Note: Some editing options such as Cut/Merge Dataset, Merge Devices & few other features are temporarily
disabled for files opened through File Selection View. See Below for more details
28
Nemo WindCatcher User Guide
Note:
Under Home tab, we have temporarily disabled the following features ONLY for files opened via Dataset
Manager View:
29
Nemo WindCatcher User Guide
To access these features from home tab, the User must change the settings below and open the dataset
again
Processing Defaults → Interface → File Selection View → Uncheck ‘File Selection View’
1. You can add more datasets into the Dataset Manager by clicking the ‘Add dataset’ button
2. Or you can go to the folder on your computer, where you have the datasets, and drag n drop them into
the dataset pane
30
Nemo WindCatcher User Guide
2. Then click on the bins on the drive-route to select the corresponding Drive File
(To clear your selection, click the Clear button, in the bottom right hand corner)
31
Nemo WindCatcher User Guide
32
Nemo WindCatcher User Guide
33
Nemo WindCatcher User Guide
2. The drive files that belong to the area, gets selected in the map
3. To remove drive files from the selection, just double click on the drive you want to remove
4. Click on OPEN, to open the selected files for Analysis
34
Nemo WindCatcher User Guide
In the example above, the search returned files across 3 datasets, that matched the search term. The
user can select the files belonging to a dataset and open them in separate tabs
35
Nemo WindCatcher User Guide
• LTE RRC connection Reject SIP SESSION SETUP FAILURE UMTS connection access failure
• UMTS RADIO BEARER SETUP FAILED UMTS MM ATTACH REJECT CS Call blocked
• UMTS connection access failure UMTS RADIO BEARER SETUP FAILED SIP Session Setup Failure
• LTE Intra Frequency handover failure LTE Inter Handover Failure LTE MO CSFB Failure
• LTE MO eCSFB Failure LTE MT eCSFB Failure CS Call rejected
• SRVCC LTE To WCDMA Handover Failure LTE MT CSFB Failure
• LTE Non Optimized IRAT Handover to HRPD Connection Failure
• LTE to WiFi Handover Failure RTP Reception Interrupted
• LTE Inter RAT Handover UTRAN to LTE Failed WiFi to LTE Handover Failure
• UMTS Intra frequency Handoff Failed MTS Inter-Frequency Handoff Failure
• Inter-RAT Handover GSM to UTRAN Failed Inter-RAT Handover UTRAN to GSM Failed
• GSM Handover Failure
• CS Call End Network Disconnect
• LTE Inter RAT Handover UTRAN to LTE Failed
36
Nemo WindCatcher User Guide
4. You will get a notification in the status bar saying, ‘Report is running in background’. You can select
another dataset and right-click and select run-report. The reports will run one-after another
37
Nemo WindCatcher User Guide
5. You can still open the dataset and proceed with the analysis while the report is running in the background
6. Once the report is generated, the status will change to ‘Ready’ and the report will be open in Excel for
your review
38
Nemo WindCatcher User Guide
3. Choose a template and the location to save the report and click on ‘Generate’
This will run the report in the background and save it to the specified location, once the report is
generated
39
Nemo WindCatcher User Guide
4. Select the device for which you want to Run the report and click on ‘Run’
5. You will get a notification in the status bar saying, ‘Report is running in background’
40
Nemo WindCatcher User Guide
4. Click on the button next to SAVE AS to specify the SAVE location & Report-Name
5. You can choose to merge the devices in the selected datasets by choosing ‘Device label’
6. You can click on ‘Open Report’, in order to open the report after it is generated
7. Click on Generate and you will get a notification in the status bar saying, ‘Report is running in background’
and the report will open, once it is generated
41
Nemo WindCatcher User Guide
Polygon Cut:
1. Click on ‘Show drive route’ after right-clicking the dataset
2. Click on the ‘Cut polygon’ button from the side-ribbon and draw a polygon around the portion of the
drive-route you intend to cut
3. From the option that pops up, you can either choose ‘Inside’ or ‘Outside’ and then click the green tick
button. Both these options would create new datasets containing the CUT portions and will also
retain the Original Dataset As-Is
- Inside: Creates a new dataset after removing the selected portion
- Outside: Creates a new dataset by retaining only the selected portion
42
Nemo WindCatcher User Guide
File Cut:
File-Cut can either be performed through the map (or) by selecting the files from the datasets pane (left pane)
File-Cut through map
There are 2 ways to select files from the map:
1. Click on the bins on the map. This will select the corresponding file.
In the same fashion, if you want to select multiple files, hold CTRL and click on some more bins to select
additional files
2. To select files within a boundary, click on the select files button from the ribbon on the side and draw an
area on the map. This will select the files within that boundary
Now, inorder to CUT the selected files, click on the CUT FILE button on the side ribbon
43
Nemo WindCatcher User Guide
Device View:
Allows users to view the dataset by devices and lets you open the devices for Analysis
Click on the DEVICE VIEW button to see the dataset by devices
Expand the dataset, to see the listing of devices. Select the device you would like to Analyze and click on OPEN
44
Nemo WindCatcher User Guide
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’)
Once the ‘merge’ option is selected, the two devices are assigned the same Phone ID and the user selects
‘Accept’:
45
Nemo WindCatcher User Guide
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.
46
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.
47
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.
48
Nemo WindCatcher User Guide
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.
49
Nemo WindCatcher User Guide
50
Nemo WindCatcher User Guide
51
Nemo WindCatcher User Guide
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.
52
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.
53
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.
54
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.
55
Nemo WindCatcher User Guide
The ‘Bin style’ option enables the user to select the symbol displayed for each device processed.
56
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:
57
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’
58
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:
59
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).
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).
60
Nemo WindCatcher User Guide
61
Nemo WindCatcher User Guide
4 User-Interface Overview
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.
62
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.
63
Nemo WindCatcher User Guide
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:
64
Nemo WindCatcher User Guide
65
Nemo WindCatcher User Guide
In the summary report, there is a “Details” sheet for all the events with root causes also in table form.
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 any of the
66
Nemo WindCatcher User Guide
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.
67
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.
Accessi Retain
bility ability
68
Nemo WindCatcher User Guide
Mobilit
y
69
Nemo WindCatcher User Guide
70
Nemo WindCatcher User Guide
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.
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
71
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.
72
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
For the map plot you can select the device from the device filter on top of the parameter tree.
73
Nemo WindCatcher User Guide
• The individual device labels can be further edited by right-clicking on top of the device label to
open the device label editor.
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.
74
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
75
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.
76
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.
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.
77
Nemo WindCatcher User Guide
Overview
Users can drag and drop metrics from parameter tree onto the time series chart
• Drop down selection allows users to switch between line and bar chart
• Stack View checkbox to view the plotted metric separately one below the other
78
Nemo WindCatcher User Guide
• ‘Show Legend’ checkbox allows the users to toggle visibility of chart legend window
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
• 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
79
Nemo WindCatcher User Guide
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
The charting tool automatically places the metrics plotted on multiple Y axes depending upon the unit and
the legend range values
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.
80
Nemo WindCatcher User Guide
• 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.
81
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.
82
Nemo WindCatcher User Guide
83
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.
84
Nemo WindCatcher User Guide
4.11 Workspace
The ‘Workspace’ feature is provided to enable the user to reuse/share the layout with content of the
different views in Nemo WindCatcher. The ‘workspace’ created by a user is saved as. wws file and can be
shared between users. The workspace is saved with content related to the dataset which was active at
the time of saving
Save 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.
85
Nemo WindCatcher User Guide
Open Workspace
The wws files can be opened using the Workspaces>Open option and browsing onto the saved/shared
.wws file on the machine.
86
Nemo WindCatcher User Guide
4.12 Template
The ‘Template’ feature is provided to enable the user to reuse/share the layout without content of the
different views in Nemo WindCatcher. The template created by a user is saved as .xml file and can be
shared between users. The template can be applied to any active dataset by opening the template and
the views will be refreshed to show the layout of the template saved
87
Nemo WindCatcher User Guide
Save Template
After selection of the window views, the user may browse onto the ‘Save Template’ option as shown
above and save the view as .xml file on the machine
Open Template
The xml file can be opened using the ‘Open Template’ as shown above and browsing onto the location of
the .xml file
88
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.
89
Nemo WindCatcher User Guide
• 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.
90
Nemo WindCatcher User Guide
Select Create new threshold group icon , choose a name for threshold and define the desired
threshold, as shown below:
91
Nemo WindCatcher User Guide
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.
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.
92
Nemo WindCatcher User Guide
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.
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:
93
Nemo WindCatcher User Guide
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:
94
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.
95
Nemo WindCatcher User Guide
96
Nemo WindCatcher User Guide
Using the query editor, user can write SQL queries and save those queries to be saved as statistics queries
to be made available on the parameter tree on the main map view
The user defined queries appear on the parameter tree in ‘Available Statistics’ section under ‘User Defined
Statistics’. The tool also provides some off the shelf default statistics which are directly available under the
‘Available Statistics’ section
User defined queries can be edited by selecting the query from the Statistics Queries drop down in SQL
Query Editor
97
Nemo WindCatcher User Guide
User can view results from multiple custom statistics queries by either appending to one table view or ass
multiple table view tabs using the ‘+’ button and drag and drop from parameter tree
98
Nemo WindCatcher User Guide
User has the option to save the statistics selected as a template that can be used for quick access. The results
can be exported to Excel, csv or text format
99
Nemo WindCatcher User Guide
To create an in-building profile, click button available under “Home” tab. Once the profiler is
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 .
100
Nemo WindCatcher User Guide
Once the profiler MapInfo file is generated, start processing the in-building data and import the tab file
101
Nemo WindCatcher User Guide
Select the desired metrics to plot for desired device(s) with selected Legend options.
102
Nemo WindCatcher User Guide
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 like ‘print Map’ menu
Under the Export document there is an option to export the images also with the title.
103
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.
104
Nemo WindCatcher User Guide
105
Nemo WindCatcher User Guide
Choose the layer ending with ‘_Event’ for the desired device and then offset like what you would do for
metrics offset
Events plotted: LTE RRC Connection Fail and LTE Radio Link Failure
106
Nemo WindCatcher User Guide
107
Nemo WindCatcher User Guide
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:
108
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.
109
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.
110
Nemo WindCatcher User Guide
111
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.
112
Nemo WindCatcher User Guide
113
Nemo WindCatcher User Guide
114
Nemo WindCatcher User Guide
3. Click on ‘Open Image’ and load the image file that needs to be mapped with the drive route
115
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.
116
Nemo WindCatcher User Guide
4. The area will be highlighted once selected. Now, right click on the map to ‘create a polygon’
117
Nemo WindCatcher User Guide
118
Nemo WindCatcher User Guide
polygon” column of the database as 1 and all bins outside the polygon will be marked with a 0. This
metric can be used in the User Query and Reports to query the data inside or outside the polygon.
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.
119
Nemo WindCatcher User Guide
120
Nemo WindCatcher User Guide
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.
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.
121
Nemo WindCatcher User Guide
The following window will appear; this window can be docked on screen by double clicking the menu bar
on it.
122
Nemo WindCatcher User Guide
Selected metric & events can be exported in Excel, MapInfo & Google compatible KML formats.
123
Nemo WindCatcher User Guide
124
Nemo WindCatcher User Guide
2. Selection of the attribute: The user may select the attribute from the groups defined under the
‘Attributes’ tree or Add a new attribute
125
Nemo WindCatcher User Guide
• 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:
126
Nemo WindCatcher User Guide
• 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.
127
Nemo WindCatcher User Guide
128
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.
129
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.
130
Nemo WindCatcher User Guide
131
Nemo WindCatcher User Guide
132
Nemo WindCatcher User Guide
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.
133
Nemo WindCatcher User Guide
134
Nemo WindCatcher User Guide
Save Database:
• 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.
135
Nemo WindCatcher User Guide
136
Nemo WindCatcher User Guide
137
Nemo WindCatcher User Guide
• 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.
138
Nemo WindCatcher User Guide
139
Nemo WindCatcher User Guide
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.
140
Nemo WindCatcher User Guide
141
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.
142
Nemo WindCatcher User Guide
7 Analysis Features
143
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.
144
Nemo WindCatcher User Guide
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.
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.
145
Nemo WindCatcher User Guide
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 options will be displayed after a ‘right click’ on the map
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.
146
Nemo WindCatcher User Guide
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.
147
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 link labels can be hidden by clicking on ‘Hide link labels’ button
The user may select a sector and right click to view the ‘link sector to’ options:
148
Nemo WindCatcher User Guide
For 5G NR Sector to Bin feature, user has the following options including selecting individual beam index
which will plot the Sector to bin lines only for the selected beam index/indices
The color theme for the individual beams can be changed using ‘Sector Link Styles/Options’
149
Nemo WindCatcher User Guide
On plotting the Sector to bin for 5G NR data, user has option to export the plotted view using ‘View in 3D
(Google Earth export) which will create a .kmz file which user can open in Google Earth Online or using
desktop version of Google Earth
150
Nemo WindCatcher User Guide
From the drop-down menu of desired binning method, users must 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
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 capture distant
151
Nemo WindCatcher User Guide
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 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.
152
Nemo WindCatcher User Guide
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.
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
153
Nemo WindCatcher User Guide
RF analysis displays the window below where the user observes data for each serving PN/PSC/PCI
User may select a specific serving parameter and plot the list of metrics available in the drop down on
the map.
7.8 Reports
These reports can then be accessed as shown below from Reports → Open Custom Report menu
154
Nemo WindCatcher User Guide
• The template report includes nine green Tabs as shown below for different functionalities. The Most
important ones are EventData, MetricData and ImageData which are used to define KPIs needed in
the report
Other user created Tabs can be added to display the extracted information in a format determined by
the user using Excel functionalities.
‘MetricData’ Tab is filled by user with the list metrics that need to be extracted for the custom report.
The initial view of the Metric Data Tab is as below:
• Row 1 through Row 4 contains the headings. User can start defining metrics from Row 5
• Column A through Column H can be filled with user commands and the result of those commands will
be generated in Column I and onwards if applicable
• In the template refer to Tab “Description” to get the definition of each column and the way to use it
155
Nemo WindCatcher User Guide
156
Nemo WindCatcher User Guide
Shows the Metric/Event value as a condition for example if user wants to see
Metric Value Rx power greater than -95dBm, "Rx Power" needs to be input in "WhereKPI"
Column and ">-95" needs to input in "WhereCondition" column.
Where user has input "filter" in "WhereKPI" column to obtain the multiple
Condition Name conditions from "Conditions" Sheet, "WhereConditions" Column would
contain the Condition name from "Conditions" Table.
Where user has input "groupby" in "WhereKPI" column to group one metric
Groupby Name wrt other, "WhereConditions" Column would contain the GroupBy name from
"GroupBy" Table.
Capturing Images
Image captures can be configured using the ImageData Tab, which refers to Thresholds and Options on
respective Tabs. On the Image Tab, the user needs to define the Device ID and the range of cells to use for the
Image capture in columns I onwards. The metric, thresholds, options and any conditions for data selection is
defined in rows 5 onwards.
Metric Data
• Open empty template and go to MetricData Sheet
• In Cell A5 define the title as “Metric”
• In Cell B5 define the Technology as “LTE”
• Now in Cell C5 we need to define the name of the metric to be populated. Refer to Sheet “Metric List”
to see the comprehensive list of all the Metrics available for different technologies. Since we are
focused on LTE technology let’s get a metric for LTE; for example “Dominant RSRP” and put it in Cell C5
• In Cell D5 define the type of statistic needed for metric defined in Cell C5 for example to get the average
of a metric put “avg”. More statistical functions are defined in the list mentioned above.
• After doing all this your Row will appear as shown in below:
• Define the Dataset Name and Device ID of the device whose statistics are needed in Cell I2 and I3
respectively. If there are multiple devices whose statistics are needed proceed to Cell J2 and J3 and
define second device and so on. Mostly Dataset name is not required. It is only required when the
report consists of multiple datasets. If all the devices in the template are from the same dataset then
only Device ID is required
• Now save the template and the close it
• Open dataset to generate the report
• Go to Reports → Open Custom Reports menu and select the saved template to generate the report
157
Nemo WindCatcher User Guide
• Once the report is generated Cell I5 will be populated with the result as shown below
• One can reopen the template and start filling other rows to get more statistics for multiple metrics as
shown below:
158
Nemo WindCatcher User Guide
• One condition can be used in another condition as shown below. “condition2” has “condition1”
embedded in it
• Now to apply these filters add new Metrics in “Metric Data” Sheet. Put “filter” in column “G” and the
name of condition in column “H”. For example, if the count and average of “Dominant RSRP” is needed
with “condition1” it will be defined as shown in the snap below:
159
Nemo WindCatcher User Guide
• Once the report is generated from this template a new sheet will be created which will give the dump
of per bin value for “Dominant RSRP”as shown below:
• Create a new sheet in the template and copy the name of this new sheet created in the generated
report; in this case “LTE_Dominant RSRP_value_37”. Next time with the report is generated a new
sheet will not be created; rather same sheet “LTE_Dominant RSRP_value_37” will be populated
160
Nemo WindCatcher User Guide
• Close the template and generate the report. A new sheet will be created in the generated report with
the dump per bin values of metrics as shown below:
• Create a new sheet in the template and copy the name of this new sheet created in the generated
report; in this case “LTE_Multi1_multimetric_38”. Next time with the report is generated a new sheet
will not be created; rather same sheet “LTE_Multi1_multimetric_38” will be populated.
Note: To see unique values across tables, please add a new sheet called "ResultFilter" into the template.
In the A2 cell please put the name of the multimetric you want to filter, and then enter keyword "Distinct"
in the B2 cell.
161
Nemo WindCatcher User Guide
Before:
After:
162
Nemo WindCatcher User Guide
Com m ent Technology Metric Type MinRange MaxRange Where KPI Where Condition
Title DataSet _A _A
Title Report Device ID 1 1
Title Report Device Model
Metric LTE LTE_Metric_Dum p dum ptable dum p
GroupBy
The functionality allows the user to extract an aggregated value of a particular metric in reference to another
metric.
• To extract count, avg, min, max of ‘Cell ID RSRQ’ for each Cell ID
• Define the following in the GroupBy tab:
• Now define the metric and the ‘type’ within the MetricData sheet. Ensure that ‘groupby’ is defined
under column G and the name provided under column H:
• Close the template and generate the report. A new sheet will be created for each metric defined:
163
Nemo WindCatcher User Guide
• Create a new sheet in the template and copy the name of this new sheet created in the generated
report; in this case “LTE_Cell ID RSRQ_group by_5”, “LTE_Cell ID RSRQ_group by_6”, etc... Next time
with the report is generated a new sheet will not be created; rather same sheet “LTE_Cell ID
RSRQ_group by_5”, “LTE_Cell ID RSRQ_group by_6”, etc. will be populated.
Event Data
• Getting The Event count is same as getting the metric count. The only difference is that it will be
populated in EventData Sheet.
• In Cell A5 define the title as “Event”
• In Cell B5 define the Technology as “LTE”
• Now in Cell C5 we need to define the name of the event to be populated. Refer to Sheet “Event List”
to see the comprehensive list of all the Events available for different technologies. Since we are focused
on LTE technology let’s get some events for LTE; for example “LTE RRC Connection Request” and “LTE
RRC Connection Dropped” and put it in Cell C5.
• In Cell D5 define the type as “count”.
• Select Dataset name and Device ID in Cells I2 and I3. Now save and then close the template.
164
Nemo WindCatcher User Guide
• Once the report is generated it will show event counts as shown below:
Plotting Image:
• Use the threshold “RSRP” for plotting “Dominant RSRP” in cell D5 in ImageData sheet.
• In Cell E5 select the options with which the metric will be populated. Some options are Pre Defined as
shown below:
165
Nemo WindCatcher User Guide
• Select “option2” to see the plotted metric legend. The plot will not show any Event as “Event Legend”
and “Show Event” is set to “No” for option2. “IndividualValues” will only be set to “Yes” when a metric
is not range based for example “Cell ID” is not a range based metric.
• After Setting all these things the ImageData sheet is shown in snap below:
• In Cell I5 press “=” and then select the location where in image will be plotted. In this example it is
plotted at in Images Sheet, in the range B11:N38.
• Now save the template and generate the report.
• The Image will appear at the location mentioned in Cell I5 in ImageData sheet.
• If the images are plotted with Events, then specific events to be plotted can be mentioned in
“OptionsEvents” sheet. For example plot Dominant RSRQ with Event “LTE RRC Connection Dropped”
• Select “option1” as “Show Event” is set to “Yes” for it, then under sheet “OptionsEvents” put event
“LTE RRC Connection Dropped” in front of “option1” as shown below:
• Now “Dominant RSRQ” will be plotted with event ““LTE RRC Connection Dropped” as shown in snap
below:
• If the Map Routes and Cell Sites are loaded on the map, the images will come with them
166
Nemo WindCatcher User Guide
• Now create a column header ‘name’ which will be used to associate a metric with the devices defined
• For each device that needs to be displayed , add a column with the header ‘Device ID’
• Finally add a column header ‘Offset (Meter) to define the offset between the devices.
• Eg: consider the definition below:
• The device labels (found under Nemo WindCatcher>Dataset window) are added for each of the four
devices in a dataset.
• Now we would need to associate this information in the ‘ImageData’ tab with a metric plot
• The definition of the metric is similar to the one shown before, with the only difference being the
‘options’ column. The exact name defined in column ‘name’ should be copied here: eg. RSCP dev
• To map the plot, you may use any device cell and map it to the sheet you want the plot to be displayed
on. Eg:
• Type in ‘Metric’ under ‘Title’
• Type in ‘UMTS’ under ‘Technology’
• Type in the metric (Best Active RSCP) under ‘Metric’
• Type in ‘RSCP’ under ‘Threshold’
• Type in ‘RSCP dev’ under ‘Options’
• Now browse onto any device with the row, type in “=” and select the area where the plot view is
desired.
167
Nemo WindCatcher User Guide
‘Options’ sheet
G – Scale: turn the scale bar on/off. The default, empty, is no. The valid input parameters are
• Left the scale bar is shown in the left side of the map image
• Right the scale bar is shown in the right side of the map image
• Center the scale bar is shown in the center of the map image
• Yes the scale bar is shown in the left side of the map image
• No no scale bar shown in the map image
H - Event Filter: the input here is one condition defined in the Conditions sheet. Be default, we assume this
condition defined one or more than one events, event_id = 100…, and the events defined here will be
removed from the final map images
I - Exclusive Event Filter: was designed to use the fields “Custom_1”, “Custom_2”… in the bin_data table.
It will exclude all the bins whose field value is ‘0’
J - Legend Width: the input should be a number. It defines the width of the legend in columns. When the
legend was at the left of the map, the default is 3. If it is under the map image, the default width is 19.
K - Two Images: if it is “yes”, the legend will be drawn separately from the map image and put at the right
side of the defined area. If it is “no” or blank, the legend will be part of the map image at the right edge. If
the input is “bottom”, the legend will be a separated image and put below the map image. The default
width is 19 columns and the height was fixed as 12 rows, the gap between the bottom border of the map
image and top border of the legend is 2 rows.
L - Legend Border: if it is “yes”, a dark grey two pixel width border will be added to the legend
M- Metric Label: if yes, the metric label will be drawn besides each bin. Or, place the expected KPI name
in this column to show the value of that KPI
N – DataTable: when it is yes, the delta value between baseline and compared will be export to the a new
sheet
O – PerCellSite: the valid input format is like “siteName:[radium][unit]”, where the radium is a number and
the unit should be either “mile” or”km”. If the radium is not defined, the default value will be the
“Maximum Sector Coverage Distance” in the processing default. If the unit is not defined, it will be the unit
of the “Maximum Sector Coverage Distance”. Users must run the Map Site to Drive Route before use this
feature.
168
Nemo WindCatcher User Guide
• DriveRoute: if this is defined, the map view will be drawn according to the drive route
• Background: if this is defined, the application will try to sync the view of the map image with the bound
of the background image. If the image was not found, it followed the default behaviors
• Lat=[X];lon=[Y];scale=[Z]: the map will be centered with the latitude and longitude. The scale here will
be used as map scale.
• Lat=[Y];lon=[X]; scale =[Z];DriveRoute: the X and Y point is the center of the area. The scale here will be
used as map scale, and the DriveRoute is the keyword
• Lat=[Y];lon=[X];Zoom=[Distance][m];DriveRoute: the X and Y point is the center of the area. The
distance is the covered radius, and the DriveRoute is the keyword
• Blank, it is default. If the report was generated from main UI with databases opened, the map view will
be synced with the bound of the current active dataset. In all other cases, it will be synced with the
drive route.
• FirstBin;zoom=[numeric][m|km], FirstBin;scale=[numeric], working with the image-groupby-self
feature. Center the map to the first bin in the data table with the defined zoom or scale
• "FirstEventBin;[Zoom|Scale]=[50][m|km]", define the center and the zoom/scale of the map picture.
You must use the OptionEvent feature to define events with the metric. If you choose zoom, please
select the unit by either “m”, meter, or “km”, kilometer.
• Metric: if the metric layer has data, set view with the metric layer
Q - ImageMethod:
• If it is blank or "insert", the images will be inserted into the custom report.
• If it is "ExportJPG", the images will be exported into a folder, which is in the multiple build level in AT&T
lite reports, or in the building level in the RFV and RFO report, and in the
"C:\Users\[username]\Documents\Xceed Technologies, Inc\CustomReport" in the regular reports
• If it is “ExportJPG_[Tech]:[Event Name], the image file name will be [database]_[device
id]_[condition]_[P|L]_[Event Code]_[ref time]_[record index].jpg. All the generated image file names
and information will be saved in the "SavedImages" sheet when using this feature
• If the input is “ExportTab” then .tab files will be generated and saved in the location from where the
report template has run
R - Nearest: the valid input is "[A]=[B], where the A is KPI defined in the KPI mapping sheet, B is the column
name of the cell site table. If the sector layer was hooked, only the nearest bins to each cell site based on
the condition "A=B, will be plotted
S - BinSize: the valid value should be an integer greater than 0. The metric bin will be drawn the number
of value bigger than drive route, the unit is point.
T - ShowNoDataPlots: the blank drive route who doesn't contain data will not be plotted when this column
is "no". The default value is "yes", which means we plot a gray drive route even there is no data for the
metric
U - DriveRouteVisibility: we will not plot the drive route under the metric bins when this column is "no".
The default value of this column is "yes".
V - LayerOrder: by default, the layers in the map plot were ordered using CustomReport logic. If put
keyword "WCP", it will follow and keep exact the order in the WindCatcher Plus. This column works only
create a report from the main UI with the databases opened.
W - Multiple Legend Columns: by default, the legend has only one column. All the threshold listed from
top to bottom. If the value of this column is "yes", the application will generate the legend with multiple
columns if needed
169
Nemo WindCatcher User Guide
X - Legend Title: by default, the title of legend is displayed as "Metric Name - Device #". Users can use
keyword "Metric" to show metric name only, or "Device" to show the device id only. If the text in the
column is neither blank nor one of these two keywords, the text in this column will be displayed as the
title. The title will not be shown if the keyword is "None"
Y – Common Bin: default is “no”, use the device’s drive route. If it is “yes”, used the drive route from all
devices. If “Max”, plots the max value for each bin; if “min”, plots the min value of the bin. The default
aggregation function is averge.
Z – Draw Graticule: default “no”. If “yes”, draw the graticule with automagical settings, 10 even grid lines
in both directions without the line label.
Below are two valid input command line “yes;label:[yes|no]”,it shows/hides the label of the grid
“yes;label:[yes|no];unit:[degree|meter|feet];value:[decimal]”, it customizes the space between the lines.
The unit and value must be defined together. The units supported are degree, meter, and feet.
AA – Metric Select Condition: Valid values are min, max, avg and sum. If column contains any of these
values, will do the corresponding operation on selected metric bins.
AB – Plot Map without Data: the default is true. If the value is no, the image will not be plotted when
there is no data. In case the P column has keyword like “Lat=[Y];lon=[X]; scale =[Z];DriveRoute” or
“Lat=[Y];lon=[X];Zoom=[Distance][m];DriveRoute”, the image will not be plotted when no data
found within defined area. Otherwise, the empty drive route will be plotted
AC – Used if the background image for inbuilding shows up as a rotated Image. To correct the
rotated image, enter ‘No’ in this column for the desired option
170
Nemo WindCatcher User Guide
This option comes with a strict requirement that the metric defined in the ‘GroupBy’ tab and the metric
plot defined in the ‘ImageData’ tab must originate from the same table within the Nemo WindCatcher
database.
Eg: if you are looking to plot the RSRQ for each of the PCIs, you would want to look into the
‘LTE_perCellid_list’ table within the database
As per the KPI document, you would use the following KPI names:
171
Nemo WindCatcher User Guide
172
Nemo WindCatcher User Guide
keyword "FirstEventBin;[Zoom|Scale]=[##][m|km]" at the P column in the Options sheet, and then put
“ExportJPG_[Tech]:[Event Name]” in the Q column in the Options sheet, the image file name will be in a
format of “[database]_[device id]_[condition]_[P|L]_[Event Code]_[ref time]_[record index].jpg” and
saved at “C:\Users\[username]\Documents\Keysight Technologies\CustomReport\[yyyy-mm-dd-hh-mm-
ss]” folder. Also, all the image file names and their information will be saved in the "SavedImages" sheet.
Optionally, the users can define the online background by enter "ROADANDSTREET" at the F column in
the Options sheet. Below please see a sample of how to define this feature
Delta plots can be generated in Custom report between Baseline Device & Compare Device.
To generate a delta plot in custom report, “ImageData” tab will be used to provide Baseline device information. To
provide Compare device information a new tab called “DeltaMap” will be used. See below images as an example
for defining delta plots,
Please note that, in ‘ImageData tab’, “Title” column is using word “DeltaMap” which is an indication that this plot
will be a delta plot. ‘Technology’ & ‘Metric’ Columns will be used same as we use them in regular image plot.
Threshold for delta plots should be defined in manner so that it can accommodate expected Delta plot values see
below examples for ‘RSCP Delta’ & ‘EcIonew’ Thresholds which are defined for above mentioned example. For
‘Options’ column, two new sets are defined under the ‘Options’ tab for delta plots, user can define as many
options as needed based on the desired numbers of delta plots. Device Model in Column ‘I’ is indicating the
information for Baseline Device.
173
Nemo WindCatcher User Guide
Please note that the number 2 & 3 under Options (DeltaMap-2 & DeltaMap-3) are also indicating a reference
towards ‘DeltaMap’ Sheet where line numbers 2 & 3 are used to specify Compare Device info, it is really critical
to define these option correctly otherwise the delta information would be incorrect.
In the ‘DeltaMap’ tab, column ‘A’ i.e. ‘name’ is user definable, user can use any name here for their own reference.
Column ‘B’ & ‘G’ i.e. ‘Baseline Offset’ & ‘Compared Offset’ are always defaulted to ‘0’.
Column ‘C’ i.e. ‘Compared Dataset’ is for the Data Set name for Compare device, here user can provide the
database name if it is different from the Baseline Device otherwise a phrase “The Same One” can be used.
Functionality is same for Column ‘D’ i.e. ‘Compared Device Id’ & Column ‘E’ i.e. ‘Compared Metric’, her user can
provide Compare Device ID & Compared Metric if it is different from Baseline Device, otherwise a phrase “The
Same One” can be used.
In the example mentioned above, the delta plots will be generated between EQ1 & EQ2 devices for the metrics
defined in ‘ImageData’ tab (i.e. Dominant PSC EcIo & Dominant PSC RSCP) from the same Dataset.
Note: Delta plot feature can be used with regular images as well; therefore Image Data tab can carry regular
images information as well as the delta plot information.
174
Nemo WindCatcher User Guide
Marco Settings
Users have an option to execute embedded macro prior to report generation. For example, if a user has
defined a macro called “macro_1” within the template, and he/she can enable macro to run before
WindCatcher populating data into the report by configuring “MacroSettings” sheet as below:
Name RunBefore
macro_1 yes
Dump Query
Using dump query feature user can execute the SQL query and get the data query output into the report
template. This can be done by using the DumpTable sheet and below is the procedure to implement the
user query
Then go to the MetricData sheet and input the query name, type as dumptable and under the device id
dump
Note: Query will run for the whole dataset, if user want to filter query for specific device id, it has to be
mention in the query itself.
Dump Plot
Using the dump plot feature user can execute the user SQL query to produce the output in the format of
Image
175
Nemo WindCatcher User Guide
Go to the ImageData sheet and mention the query name in Metric Column and follow the regular
procedure of how we pull the Images from the ImageData sheet.
DumpPlot Sheet
ImageData Sheet
The above example will work when the Data column and bin id columns are mentioned in the query
itself.
There is another way when data and binid columns are not mentioned in query, in this case user need to
specify the Data column index and Binid index separately using the Data Field Index (col C) and BinId
Field Index (col D)
Example
In the above query Binid is 0 and Data field column is 3 since the data is ue_rsrp, considering that the
result from the above query as table and ue_rsrp will be at third position.
Using Dumpplot option user can still plot the events along with the map, the procedure to plot events
are same using the OptionEvent method.
UI Device Selection:
Before running the custom report template user can select the Devices using a drop down menu
from Open Custom Report option to run the report for selected devices
176
Nemo WindCatcher User Guide
Once the user click on the “Update Devices & Generate Report”, WCP will ask for selecting the report
template, once the template selection made again one more popup window will come to select devices,
below is the reference snap
To select the device user have to check it from the device list, once the user selected the list of devices
same list will be updated in the report template and then click on the Run button to run the report.
Note: The selected report will run only for the number of devices it was originally designed for.
For example, VoLTE Acceptance report is designed for 2 UE’s and hence even if the user selects 4 devices
using the device selection feature, the report will run only for the first two devices from the selection.
To plot both maps and sites user need to load the converted map file along with the drive data and then
run the report as usual, both maps and sties will come.
Sometimes only sites will come with the map and the size of each sector will be big, when user faces
such kind of issues while loading cell sites please follow the below procedure to correct it
Go to the Layer control option and then select the cell sites file
Go to the Options modify the size of the sector and then check the “Override Sector Sze”
Now run the report to see the drive route and cell sites with proper zoom level
177
Nemo WindCatcher User Guide
178
Nemo WindCatcher User Guide
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.
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
179
Nemo WindCatcher User Guide
180
Nemo WindCatcher User Guide
The PowerPoint report feature can be accessed using Reports->Open PPT Custom Report. The feature is
based of converting current excel report into PowerPoint format. Use of the feature requires the custom
report template to be set with correct paging and page size to print as per desired output in PowerPoint
Any of the current custom report template can be used to generate PowerPoint report
181
Nemo WindCatcher User Guide
182
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.
183
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.
184
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.
185
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.
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).
186
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.5.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.
187
Nemo WindCatcher User Guide
If there is a need for additional conditions needed customer can create also own conditions.
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.
188
Nemo WindCatcher User Guide
7.9.1 Interface
189
Nemo WindCatcher User Guide
Users can write simple and/or complex SQL queries using regular SQL query statements and the results of
the query will be displayed in the query editor as shown below
Users can save the query/queries to sql file and open it for later use.
190
Nemo WindCatcher User Guide
191
Nemo WindCatcher User Guide
192
Nemo WindCatcher User Guide
193
Nemo WindCatcher User Guide
194
Nemo WindCatcher User Guide
8 Project Manager
2. Scan the root folder containing raw drive test data in subfolders
195
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
6. To add background files and cell sites use the “Supporting Files” tab
196
Nemo WindCatcher User Guide
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
197
Nemo WindCatcher User Guide
4. Click “Create Sector Tab File” and provide location and name for the tab file.
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.
198
Nemo WindCatcher User Guide
• 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”.
199
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.
200
Nemo WindCatcher User Guide
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.
201
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.
If the folder contains Cell Site or polygon files in MapInfo format they will remain under the project
folder.
202
Nemo WindCatcher User Guide
9.2.4 Reporting
There are 2 level of reports available:
1) Project level: The project level report runs for all the data in the project. The report template is copied in
the project folder.
2) Workspace level: The workspace level report runs for all the data in all the projects under the workspace
folder. The report template is copied in the workspace folder. Note the workspace level report uses the
label in the template to pick up devices from the project databases and it creates a rollup database
(containing only data defined in the template) in the workspace folder.
Any Cell site file or MapInfo Tab file (for polygon etc.) copied in the project or workspace folder
will be displayed in the Image plots in the reports.
1) Manual: The report template can be manually uploaded by the WindCatcher Client or by copying to the
FTP folder.
2) Default: Default workspace and project level reports can be selected using the “User Settings” option
under the Automation folder. Any new project or workspace will automatically get these report templates
copied into the respective folders. Using this option, the user does not need to upload any report
templates and any new project or workspace he creates will run these reports. Note: This is the
configuration for near real time reporting use case.
3) Scheduled: A report can be scheduled to run based on a user schedule by double clicking on the yellow
schedule window, selecting the Project or Workspace Folder in the drop down, selecting the time and
203
Nemo WindCatcher User Guide
selecting the report template. The report will only run at the scheduled time by copying the report
template into the project or workspace folder. As an example if data collection is done all day and a
report is needed at the end of the day, it can be scheduled using this option.
1) Geo Binning: The user can define a bin size to create Geobin statistics or plots in the report template
2) Apply Polygon: If a Mapinfo file with polygons is copied in the project or workspace folder, this feature
will apply the polygon to update the database with the bins Inside or Outside the polygon
3) Apply Map Sites to route: This feature applies the cell sites to the database using the Map Sites to Route
Function.
204
Nemo WindCatcher User Guide
9.3 Dashboards
Client-Server automation module provides functionality to generate content based on SQL queries run on
the generated database/databases for the various workspace and projects that are processed using the
Automation module.
The generated content is stored in form of a SQL database which provides the source for Qlik Sense to
connect to and develop dashboards.
The dashboard content is generated by copying the dashboard query files to the Root folder. The dashboard
queries are created using the Query Editor in the Tools Menu. Note multiple dashboard queries can be
created and copied to the Root folder of Automation. The dashboard query run for any new project level
database and update a master SQLite dashboard database. The master SQLite dashboard database has the
Workspace and project name columns in addition to the query results. This file is accessed by Qlik server to
visual the dashboard contents or can be used by any 3rd party dashboard/ BI tool used by end users.
If a database is appended with new data, the existing content will be removed from the
SQLite dashboard database and replaced with new data.
Write SQL query using SQL Query Editor Interface that output the content/source data for use in dashboard
view development. Execute the query to validate the output results. Once validated, save the query to a
.sql file
Step 2:
205
Nemo WindCatcher User Guide
Dashboard content generation is currently only supported for Client-Server Automation module with the
intent to execute the SQL query/queries across all the workspaces/projects associated with a scan folder.
To that effect, the next step after having the SQL query ready is to copy the query file/files under the main
scan folder.
Step 3:
As the data gets processed through Client-Server Automation module, you will see a “qlik-source.db”
database getting added to the scan folder location. This “qlik-source.db” is the source database which Qlik
Sense will connect to for loading the data and updating the dashboard views as and when newer data gets
processed. That said, let’s look at how to setup Qlik Sense to load this database
A single scan folder can support multiple SQL query files and the results will be stored in single “qlik-
source.db” database
The above section talked about how to setup the Client-Server Automation module to generate
content/source data for Qlik Sense dashboards. The below section will provide you information on how to
develop dashboards using Qlik Sense by connecting to the generated “qlik-source.db” database
Pre-requisites
- User has access to Qlik Sense Hub and has the appropriate privileges to create dashboards on Qlik
Sense
Step1:
Prior to launching Qlik Sense to create dashboard (a.k.a app), user must setup the ODBC connection to the
“qlik-source.db”
206
Nemo WindCatcher User Guide
207
Nemo WindCatcher User Guide
208
Nemo WindCatcher User Guide
209
Nemo WindCatcher User Guide
210
Nemo WindCatcher User Guide
211
Nemo WindCatcher User Guide
- https://help.qlik.com/
- https://help.qlik.com/en-US/sense/February2018/Content/Home.htm
- https://www.youtube.com/channel/UCFxZPr8pHfZS0n3jxx74rpA
Once the dashboard has been developed and published to a particular stream in Qlik Sense, the following
steps can be taken to view them directly in WindCatcher
Open WindCatcher and Navigate to the ‘Client-Server’ tab and click ‘Dashboards
212
Nemo WindCatcher User Guide
213
Nemo WindCatcher User Guide
214
Nemo WindCatcher User Guide
The profile is built using the File Mover Configuration option in the Automation Tab.
1) Profile Name: multiple profiles can be created and they will run in a Top down order till they get applied.
2) Source Path: This is the location where the files from the FTP server are downloaded
3) Destination Path: This is the location where the files are parsed into. This should be the root folder of the
project repository
215
Nemo WindCatcher User Guide
4) Folder or File Name Selection: Folder selection will download the exact folder configuration from the
source folder to the destination folder. File name selection will use the file parsing rules in the advanced
project section for workspace and project folder creation.
5) Sample file name: Select a sample file to define the parsing options
6) Parsing options for the workspace/project folder creation include:
a. Delimiter based
i. Delimiter – Enter the delimiter in the file name used to populate the Select drop-down
such “_”, “,”, “-“etc,
ii. Select – Select the delimited field to define the workspace/project folder. Anytime this
field changes a new workspace is created. If a file name matches an existing
workspace/project it will be copied into it.
iii. Sample Name- Displays parsed output based on sample file name
b. Tag based – Creates workspace/project folder based on user input tag name.
c. Timestamp based – use the timestamp in the file name to create the workspace/project folders.
Users have to select the time format used in the file names.
d. File modified date based - Use the timestamp in the file modified date to create the
workspace/project folders. Users have to select the time format used in the file modified date.
e. Header based – Use select header fields in the Nemo file to create the workspace/project folders.
The headers are selected from the drop-down.
7) Select the + sign to add the parsing logic. The Up / Down arrows can be used to apply different parsing
rules in sequence
8) Select Save/Save as to save the profile
9) Select Add to create another profile
216
Nemo WindCatcher User Guide
The FTP server settings will allow users to set the IP address, Port, user credentials and the Root folder
on the FTP server to monitor. After entering the Server details click “Apply Settings”. Then select the root
folder and click “Start Download”.
217
Nemo WindCatcher User Guide
The Download New Files Only option downloads only file with timestamp greater than the most recent
file download. After the data has been downloaded from the FTP server the processing will start
automatically on the Windcatcher sever side.
218
Nemo WindCatcher User Guide
219
Nemo WindCatcher User Guide
The profile is built using the File Mover Configuration option in the Automation Tab.
1) Profile Name: multiple profiles can be created and they will run in a Top down order till they get applied.
2) Source Path: This is the location where the files from the FTP server are downloaded
3) Destination Path: This is the location where the files are parsed into. This should be the root folder of the
project repository
220
Nemo WindCatcher User Guide
4) Folder or File Name Selection: Folder selection will download the exact folder configuration from the
source folder to the destination folder. File name selection will use the file parsing rules in the advanced
project section for workspace and project folder creation.
5) Sample file name: Select a sample file to define the parsing options
6) Parsing options for the workspace/project folder creation include:
a. Delimiter based
i. Delimiter – Enter the delimiter in the file name used to populate the Select drop-down
such “_”, “,”, “-“etc,
ii. Select – Select the delimited field to define the workspace/project folder. Anytime this
field changes a new workspace is created. If a file name matches an existing
workspace/project it will be copied into it.
iii. Sample Name- Displays parsed output based on sample file name
b. Tag based – Creates workspace/project folder based on user input tag name.
c. Timestamp based – use the timestamp in the file name to create the workspace/project folders.
Users have to select the time format used in the file names.
d. File modified date based - Use the timestamp in the file modified date to create the
workspace/project folders. Users have to select the time format used in the file modified date.
e. Header based – Use select header fields in the Nemo file to create the workspace/project folders.
The headers are selected from the drop-down.
7) Select the + sign to add the parsing logic. The Up / Down arrows can be used to apply different parsing
rules in sequence
8) Select Save/Save as to save the profile
9) Select Add to create another profile
221
Nemo WindCatcher User Guide
The Nemo server settings will allow users to set the IP address and user credentials. After entering the
Server details click “Apply Settings”. Then select the root folder and click “Start Download”.
After the data has been downloaded from the Nemo Cloud the processing will start automatically on the
Windcatcher sever side.
222
Nemo WindCatcher User Guide
Next step is to browse to the root folder on the server and delete the workspace and/or project folders.
After deleting the workspace and/or project folders, 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’.
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.
223
Nemo WindCatcher User Guide
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.
9.7.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.
224
Nemo WindCatcher User Guide
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.
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.
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
225
Nemo WindCatcher User Guide
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.
226
Nemo WindCatcher User Guide
227
Nemo WindCatcher User Guide
228
Nemo WindCatcher User Guide
229
Nemo WindCatcher User Guide
230
Nemo WindCatcher User Guide
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.
231
Nemo WindCatcher User Guide
232
Nemo WindCatcher User Guide
233
Nemo WindCatcher User Guide
234
Nemo WindCatcher User Guide
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.
235
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:
236
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.
Transmission Max Rank:
237
Nemo WindCatcher User Guide
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:
238
Nemo WindCatcher User Guide
MCS Info:
239
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:
240
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 in the construction
241
Nemo WindCatcher User Guide
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:
242
Nemo WindCatcher User Guide
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 to adapt them to the size which can 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 to adapt them to the size which can 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.
243
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.
244
Nemo WindCatcher User Guide
245
Nemo WindCatcher User Guide
246
Nemo WindCatcher User Guide
Min SQI
Shows minimum SQI within a bin
Max SQI
Shows Maximum SQI within a bin
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.
247
Nemo WindCatcher User Guide
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.
248
Nemo WindCatcher User Guide
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
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
249
Nemo WindCatcher User Guide
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).
250
Nemo WindCatcher User Guide
251
Nemo WindCatcher User Guide
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.
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.
252
Nemo WindCatcher User Guide
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.
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)
253
Nemo WindCatcher User Guide
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.
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)
254
Nemo WindCatcher User Guide
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.
The following thresholds are available for the user to run this analysis:
255
Nemo WindCatcher User Guide
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
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)
256
Nemo WindCatcher User Guide
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.
SINR for PN
SINR for the selected PN across all sets. Only PNs present in the dataset are displayed in the
drop down box.
257
Nemo WindCatcher User Guide
Dominant Pilot PN
Dominant PN for the part of the drive is displayed.
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.
Dominant Pilot Ec
258
Nemo WindCatcher User Guide
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.
Data
The Data metrics represents all metrics related to the Data.
259
Nemo WindCatcher User Guide
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.
260
Nemo WindCatcher User Guide
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.
Forward IP Packets
The IP packets sent on the forward link.
Reverse IP Throughput
The IP throughput on the Reverse link.
Reverse IP Packets
The IP packets sent on the Reverse link.
261
Nemo WindCatcher User Guide
Reverse Link
The Reverse Link metrics represents all metrics of the reverse link.
Mobile
The mobile metrics represents all metrics related to the phone state.
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
262
Nemo WindCatcher User Guide
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.
263
Nemo WindCatcher User Guide
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 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
264
Nemo WindCatcher User Guide
EVDO Rev A
The EVDO Rev A metrics represent all metrics related to wireless internet data solutions.
265
Nemo WindCatcher User Guide
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.
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.
266
Nemo WindCatcher User Guide
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.
Advanced Metrics
The Advanced metrics are developed based on certain conditions and combination of one or several
basic metrics.
267
Nemo WindCatcher User Guide
268
Nemo WindCatcher User Guide
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.
a) Ec/Io of Selected PN
The Ec/Io of the Selected PN.
b) Ec of Selected PN
The Ec of the Selected PN.
269
Nemo WindCatcher User Guide
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.
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:
270
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.
271
Nemo WindCatcher User Guide
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.
4. Call Blocked
This sub category includes all events related to the call blocking.
272
Nemo WindCatcher User Guide
This event is triggered when the call attempt is blocked by the network with the reason given as
“Service Redirection”.
5. Call Connection
This sub category includes all events related to the call connection phase.
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.
6. Call End
This sub category includes all events related to the call end phase.
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.
Call End
This event is triggered when the call ends, but data is not available to determine the cause.
273
Nemo WindCatcher User Guide
7. Timers
This sub category includes all events related to the timers.
Handoff Process
a) Soft Handoff
This sub category includes all events related to soft handoff.
b) Hard Handoff
274
Nemo WindCatcher User Guide
c) Handoff Failure
This sub category includes all events related to handoff failure.
Network Problem
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.
275
Nemo WindCatcher User Guide
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.
c) Protocol Revision
This sub category includes all events related to new system protocol revision.
a) Session
This category lists all applications related to EVDO data session.
b) Access Attempt
This category lists all the application related to the access attempts.
c) Connection
This category lists all events related to Connection.
276
Nemo WindCatcher User Guide
d) Handoff
This category includes all events related to Handoff.
277
Nemo WindCatcher User Guide
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.
278
Nemo WindCatcher User Guide
WIMAX Serving RF
This section consists of all metrics corresponding to the WIMAX Serving RF.
WIMAX BSID
This section consists of metrics corresponding to WIMAX BSID
279
Nemo WindCatcher User Guide
This metric plots the total downlink PDU count sent to the SS in each bin.
280
Nemo WindCatcher User Guide
WIMAX Ping
This section consists of metrics corresponding to Ping.
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.
281
Nemo WindCatcher User Guide
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.
282
Nemo WindCatcher User Guide
This event is triggered when the RNG-REQ message is transmitted with the Network Re-entry Ranging
Request Flag TLV enabled.
283
Nemo WindCatcher User Guide
(C) Handover
(E) Others
284
Nemo WindCatcher User Guide
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
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.
285
Nemo WindCatcher User Guide
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
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
286
Nemo WindCatcher User Guide
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.
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
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
287
Nemo WindCatcher User Guide
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.
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
288
Nemo WindCatcher User Guide
289
Nemo WindCatcher User Guide
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.
290
Nemo WindCatcher User Guide
291
Nemo WindCatcher User Guide
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
like 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 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
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
292
Nemo WindCatcher User Guide
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
293
Nemo WindCatcher User Guide
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 signal strength, RSRQ additionally takes
the interference level into account due to the inclusion of RSSI. RSRQ therefore enables the combined effect
294
Nemo WindCatcher User Guide
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.
295
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.
296
Nemo WindCatcher User Guide
MCS:
297
Nemo WindCatcher User Guide
Throughput:
298
Nemo WindCatcher User Guide
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
299
Nemo WindCatcher User Guide
300
Nemo WindCatcher User Guide
20 Appendix K : 5G NR Metrics
20.1 5G NR UE Metrics
NR Best Serving PCI for selected set
Physical Cell ID of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Best Serving PCI-Beam Index for selected set
Physical Cell ID and Beam Index of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected
NR cell type
NR Timing offset for selected set
Timing offset of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Frequency offset for selected set
Frequency offset of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
Nth best NR Serving PCI
Physical Cell ID of the Nth best cell (cell ranking based on SS-RSRP in the bin)
Nth best NR Serving PCI - Beam Index
Combination of the Physical Cell ID and Beam Index of the Nth best cell (cell ranking based on SS-RSRP in
the bin)
NR Frequency band for selected set
Frequency band of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR-ARFCN
ARFCN of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Best SS-RSRP for selected set
SS-RSRP of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Best SS-RSRQ for selected set
SS-RSRQ of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Best SS-SINR for selected set
SS-SINR of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Best RSSI for selected set
RSSI of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected NR cell type
NR Best SS-RSRP for selected PCI
SS-RSRP of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI
NR SS-RSRP for selected PCI-Beam Index
SS-RSRP of the serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI-Beam Index
combination
Nth best NR SS-RSRP
SS-RSRP of the Nth best cell (cell ranking based on SS-RSRP in the bin)
NR Best SS-RSRQ for selected PCI
SS-RSRQ of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI
NR SS-RSRQ for selected PCI-Beam Index
SS-RSRQ of the serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI-Beam Index
combination
Nth best NR SS-RSRQ
SS-RSRQ of the Nth best cell (cell ranking based on SS-RSRP in the bin)
NR Best SS-SINR for selected PCI
SS-SINR of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI
NR SS-SINR for selected PCI-Beam Index
SS-SINR of the serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI-Beam Index
combination
Nth best NR SS-SINR
301
Nemo WindCatcher User Guide
SS-SINR of the Nth best cell (cell ranking based on SS-RSRP in the bin)
NR RSSI for selected PCI
RSSI of the best serving NR cell (cell with best SS-RSRP in the bin) for the selected PCI
NR Best SS-RSRP
SS-RSRP of the best serving NR cell in the bin
NR Best SS-RSRQ
SS-RSRQ of the best serving NR cell in the bin
NR Best SS-SINR
SS-SINR of the best serving NR cell in the bin
NR MAC downlink throughput
MAC throughput that is calculated from successfully received SDUs. With the devices that do not support
MAC throughput parameter the estimation of MAC throughput is calculated from successfully received
transport blocks
NR MAC downlink scheduled throughput
MAC throughput that is calculated from successfully received SDUs ignoring idle time. With the devices that
do not support MAC throughput parameter the estimation of MAC throughput is calculated from
successfully received transport blocks
NR PDSCH throughput
PDSCH throughput that is calculated from successfully received transport blocks
NR PDSCH scheduled throughput
PDSCH throughput that is calculated from transport blocks per scheduled slot based on sub carrier spacing
NR PUSCH throughput
PUSCH throughput that is calculated from successfully received transport blocks
NR PUSCH scheduled throughput
PUSCH throughput that is calculated from transport blocks per scheduled slot based on sub carrier spacing
NR MAC uplink throughput
The throughput that is calculated from successfully transmitted MAC SDUs. With the devices that do not
support MAC throughput parameter the estimation of MAC throughput is calculated from successfully
delivered transport blocks
NR MAC uplink scheduled throughput
The throughput that is calculated from successfully transmitted MAC SDUs ignoring idle time. With the
devices that do not support MAC throughput parameter the estimation of MAC throughput is calculated
from successfully delivered transport blocks
NR RLC downlink throughput
Total downlink RLC throughput is calculated over all radio bearers. The value of this parameter is calculated
based on the SDUs that are successfully transferred through the RLC layer. Missing and erroneous RLC
blocks are excluded from the throughput calculation
NR RLC uplink throughput
Total uplink RLC throughput. The value of this parameter is calculated based on the SDUs that are
successfully transferred through the RLC layer. Missing and erroneous RLC blocks are excluded from the
throughput calculation
NR PDCP downlink throughput
Total downlink PDCP throughput is calculated over all radio bearers. The value of this parameter is
calculated based on the SDUs that are successfully transferred through the PDCP layer. Missing and
erroneous PDCP blocks are excluded from the throughput calculation
NR PDCP uplink throughput
Total uplink PDCP throughput. The value of this parameter is calculated based on the SDUs that are
successfully transferred through the PDCP layer. Missing and erroneous PDCP blocks are excluded from the
throughput calculation
NR RACH type
302
Nemo WindCatcher User Guide
NR TX power PUCCH
303
Nemo WindCatcher User Guide
The average transmit power for PUCCH calculated over the reporting period
NR TX power PUSCH
The average transmit power for PUSCH calculated over the reporting period
NR TX Power SRS
The average transmit power for SRS calculated over the reporting period
NR PDSCH modulation for CW0
Average scheduled modulation for codeword 0
NR PDSCH modulation for CW1
Average scheduled modulation for codeword 1
NR PDSCH MCS index for CW0
Average scheduled modulation and coding scheme index for codeword 0
NR PDSCH MCS index for CW1
Average scheduled modulation and coding scheme index for codeword 1
NR PUSCH modulation for CW0
Average scheduled modulation for codeword 0
NR PUSCH MCS index for CW0
Average scheduled modulation and coding scheme index for codeword 0
NR PDSCH scheduled rank
Average scheduled rank during the previous reporting period
NR PDSCH PRBs
Average scheduled PRBs during the previous reporting period
NR PDSCH TB size for CW0
Average scheduled transport block size for codeword 0
NR PDSCH TB size for CW1
Average scheduled transport block size for codeword 1
NR PUSCH scheduled rank
Average scheduled rank during the previous reporting period
NR PUSCH PRBs
Average scheduled PRBs during the previous reporting period
NR PUSCH TB size for CW0
Average scheduled transport block size for codeword 0
Troubleshooting-Poor Coverage:
Best SS-RSRP is less than user defined threshold (default value -120). Result is binary, 1 – Red (Meets
condition) or 0 – Grey (Does not meet condition)
Troubleshooting-Possible Interference:
Best SS RSRP >= Threshold (-95 default) and SS SINR is <= Threshold (5 default). Result is binary, 1 – Red
(Meets condition) or 0 – Grey (Does not meet condition)
Troubleshooting-Number of Servers:
Count of Best PCI values above user defined RSRP threshold (default value -120)
Troubleshooting-Number of Beams:
Count of Best PCI-Beam Indexes values above user defined RSRP threshold (default value -120)
Troubleshooting-Number of Beams for PCI:
Count of Best PCI-Beam Indexes values above user defined RSRP threshold (default value -120) for user
selected PCI
Troubleshooting-Number of Servers Within Threshold:
Count of Best PCI values above user defined RSRP threshold (default value -120) and within X dB of Best
Server (Default 5dB)
Troubleshooting-Number of Beams Within Threshold:
Count of Best PCI-Beam Indexes values above user defined RSRP threshold (default value -120) and within
X dB of Best Server (default 5dB)
Troubleshooting-Number of Beams for PCI Within Threshold:
304
Nemo WindCatcher User Guide
Count of beam Indexes values above user defined RSRP threshold (default value -120) for user selected PCI
and within X dB of Best Server (default 5dB)
20.2 5G NR Events
SN Addition Request:
Triggered when an RRC Connection Reconfiguration Layer 3 message containing NR-r15 Secondary Cell
Group Config is seen on DL-DCCH channel
SN Configured:
Triggered when an RRC Connection Reconfiguration Complete Layer 3 message containing scg-
ConfigResponseNR-r15’ is seen in UL-DCCH channel
SCG Change Failure:
Triggered when an SCG Failure InformationNR-r 15 Layer 3 message is seen in UL-DCCH. The event tooltip
provides the failure type information
NR Intra Handover Request:
Triggered when an RRC Connection Reconfiguration Layer 3 message containing NR-r15 Secondary Cell
Group Config is seen on DL-DCCH channel where SSB ARFCN before is same as the SSB ARFCN seen in the
layer 3 message
NR Intra Handover Reconfiguration Success:
Triggered when an RRC Connection Reconfiguration Complete Layer 3 message containing scg-
ConfigResponseNR-r15’ is seen in UL-DCCH channel where SSB ARFCN before is same as the SSB ARFCN
seen in the layer 3 message
NR Intra Handover Success:
Triggered on successful RACH completion after RRC Connection Reconfiguration Complete Layer 3 message
containing scg-ConfigResponseNR-r15’ is seen in UL-DCCH channel where SSB ARFCN before is same as the
SSB ARFCN seen in the layer 3 message
NR Intra Handover Failure:
Triggered on unsuccessful RACH completion after RRC Connection Reconfiguration Complete Layer 3
message containing scg-ConfigResponseNR-r15’ is seen in UL-DCCH channel and when an SCG Failure
InformationNR-r 15 Layer 3 message is seen in UL-DCCH where SSB ARFCN before is same as the SSB ARFCN
seen in the layer 3 message
NR Inter Frequency Handover Request:
Triggered when an RRC Connection Reconfiguration Layer 3 message containing NR-r15 Secondary Cell
Group Config is seen on DL-DCCH channel where SSB ARFCN before is different from the SSB ARFCN seen
in the layer 3 message
NR Inter Frequency Handover Reconfiguration Success:
Triggered when an RRC Connection Reconfiguration Complete Layer 3 message containing scg-
ConfigResponseNR-r15’ is seen in UL-DCCH channel where SSB ARFCN before is different from the SSB
ARFCN seen in the layer 3 message
NR Inter Frequency Handover Success:
Triggered on successful RACH completion after RRC Connection Reconfiguration Complete Layer 3 message
containing scg-ConfigResponseNR-r15’ is seen in UL-DCCH channel where SSB ARFCN before is different
from the SSB ARFCN seen in the layer 3 message
NR Inter Frequency Handover Failure:
Triggered on unsuccessful RACH completion after RRC Connection Reconfiguration Complete Layer 3
message containing scg-ConfigResponseNR-r15’ is seen in UL-DCCH channel and when an SCG Failure
InformationNR-r 15 Layer 3 message is seen in UL-DCCH where SSB ARFCN before is different from the SSB
ARFCN seen in the layer 3 message
305
Nemo WindCatcher User Guide
Dominant Band:
Band information of the dominant cell (cell with best SS-RSRP in the bin)
NR-ARFCN:
ARFCN number of the dominant cell (cell with best SS-RSRP in the bin)
Dominant PCI:
Physical Cell ID of the dominant cell (cell with best SS-RSRP in the bin)
Dominant Numerology(kHz):
Numerology in kHz of the dominant cell (cell with best SS-RSRP in the bin)
Dominant PCI-Beam Index:
Combination of Physical Cell ID and Beam Index number of the dominant cell (cell with best SS-RSRP in the
bin)
Nth Best PCI-Beam Index:
Combination of Physical Cell ID and Beam Index of the Nth best cell (cell ranking based on SS-RSRP in the
bin)
Dominant PCI-Beam Index for Selected PCI:
Combination of Physical Cell ID and Beam Index number of the dominant cell (cell with best SS-RSRP in the
bin) for the selected PCI value
Dominant SS-RSRP:
Secondary synchronization reference signal receive power of the dominant cell (cell with best SS-RSRP in
the bin)
Dominant SS-RSRP for Selected PCI:
Secondary synchronization reference signal receive power of the dominant cell (cell with best SS-RSRP in
the bin) for the selected PCI value
SS-RSRP per PCI-Beam Index:
Secondary synchronization reference signal receive power of select PCI-Beam Index combination
Nth Best SS-RSRP:
Secondary synchronization reference signal receive power of the Nth best cell
Dominant SS-RSRQ:
Secondary synchronization reference signal receive quality of the dominant cell (cell with best SS-RSRP in
the bin)
Dominant SS-RSRQ for Selected PCI:
Secondary synchronization reference signal receive quality of the dominant cell (cell with best SS-RSRP in
the bin) for the selected PCI value
SS-RSRQ per PCI-Beam Index:
Secondary synchronization reference signal receive quality of select PCI-Beam Index combination
Nth Best SS-RSRQ:
Secondary synchronization reference signal receive quality of the Nth best cell
Dominant SS-SINR:
Secondary synchronization reference signal-to-noise ratio of the dominant cell (cell with best SS-RSRP in
the bin)
Dominant SS-SINR for Selected PCI:
Secondary synchronization reference signal-to-noise ratio of the dominant cell (cell with best SS-RSRP in
the bin) for the selected PCI value
SS-SINR per PCI-Beam Index:
Secondary synchronization reference signal-to-noise ratio of select PCI-Beam Index combination
306
Nemo WindCatcher User Guide
307
Nemo WindCatcher User Guide
308
Nemo WindCatcher User Guide
Troubleshooting-Possible Interference:
Dominant SS RSRP >= Threshold (-95 default) and SS SINR is <= Threshold (5 default). Result is binary, 1 –
Red (Meets condition) or 0 – Grey (Does not meet condition)
Troubleshooting-Number of Servers:
Count of Dominant PCI values above user defined RSRP threshold (default value -120)
Troubleshooting-Number of Beams:
Count of Dominant PCI-Beam Indexes values above user defined RSRP threshold (default value -120)
Troubleshooting-Number of Beams for PCI:
Count of Dominant PCI-Beam Indexes values above user defined RSRP threshold (default value -120) for
user selected PCI
Troubleshooting-Number of Servers Within Threshold:
Count of Dominant PCI values above user defined RSRP threshold (default value -120) and within X dB of
Best Server (Default 5dB)
Troubleshooting-Number of Beams Within Threshold:
Count of Dominant PCI-Beam Indexes values above user defined RSRP threshold (default value -120) and
within X dB of Best Server (default 5dB)
Troubleshooting-Number of Beams for PCI Within Threshold:
Count of beam Indexes values above user defined RSRP threshold (default value -120) for user selected PCI
and within X dB of Best Server (default 5dB)
309
Nemo WindCatcher User Guide
21 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
nemo.support@keysight.com. Note that for full support you need to have the Maintenance Agreement.
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
310
Nemo WindCatcher User Guide
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.
311