RN Nemo Outdoor 7 6 0 7 30th June 2015

WWW.ANITE.
COM/NEMO
NEMO OUTDOOR 7.6.0 RELEASE

TECHNICAL BULLETIN & RELEASE NOTES
NEMO OUTDOOR 7.6.0 TECHNICAL BULLETIN AND RELEASE NOTES
Copyright
The information contained in this document is confidential and no part of it may be copied or
reproduced in any form without the written consent of Anite Network Testing. Additionally, this
document is not to be passed to or discussed with third parties without the prior written permission
of Anite Network Testing.
Anites products are subject to continual development and specifications may change. Users of
Anites products and documentation should exercise their own independent judgement to evaluate
the suitability of Anites products and documentation for their particular use. Anite does not accept
any liability arising from the application or use of the product or this documentation.
All reasonable care has been made to ensure that this document is accurate. If you have any
comments on this document, or would like details of any Anite products, services or equipment,
please contact us through the Anite website.
Version
7.6.0.7
Page 2
Date
30 of June 2015
Summary of Changes
CONTENTS
1 NEW FEATURES ................................................................................................. 5

1.1
LTE-A 3 component carrier aggregation ........................................................ 5
1.2
Small cell and DAS indoor measurement enhancements .................................. 7
1.2.1
Small cell and distributed antenna system types .................................... 7
1.2.2
DAS anomaly analysis in indoor view .................................................... 7
1.2.3
Real-time RF ingress analysis calculation ............................................... 9
1.2.4
UTM coordinates and marker coordinate conversion with iBwave files ..... 10
1.2.5
Area zones with iBwave importing ...................................................... 11
1.2.6
Measurement filename parameter based on iBwave floorplan identifier ... 11
1.3
Nemo Media Router .................................................................................. 12
1.3.1
New features in Nemo Media Router version 2.30 ................................. 13
1.3.2
Nemo Media Router licensing options .................................................. 15
1.3.3
Compatibility and update process ....................................................... 15
1.3.4
Supported handsets with Nemo Media Router ...................................... 16
1.4
Generic handler enhancements .................................................................. 17
1.4.1
1.5
Support for GSM WFS AMR codec ....................................................... 17
Qualcomm handler enhancements .............................................................. 18
1.5.1
Support for new messages with Qualcomm diagnostics logging .............. 18
1.5.2
Other enhancements ........................................................................ 18
1.6
HiSilicon handler enhancements ................................................................. 18
1.6.1
Forcing to barred PCI ........................................................................ 19
1.6.2
GSM and UMTS band lock .................................................................. 19
2 APPLICATIONS AND PROTOCOLS ....................................................................... 20

2.1
Dropbox testing ....................................................................................... 20
2.2
Support for data transfers using IPv6 tunneling over IPv4 connection ............. 21
2.3
Support for TCP connection establishment time............................................ 21
3 OTHER FEATURES & UPDATES ........................................................................... 22

3.1
Generic scanner handler enhancements ...................................................... 22
3.2
Nemo FSR1 scanner handler enhancements ................................................ 22
3.2.1
3.3
PCTel scanner handler enhancements ......................................................... 23
3.3.1
3.4
TD-SCDMA ...................................................................................... 22
PCTEL MXflex support ....................................................................... 23
Rohde & Schwarz scanner handler enhancements ........................................ 23
3.4.1
Vicom interface ................................................................................ 23
3.4.2
TSME MIMO scanning........................................................................ 23
3.5
Nemo Invex new features ......................................................................... 25
4 USER INTERFACE ............................................................................................. 26
Page 3
4.1
Measurement file uploading directly to Nemo Xynergy .................................. 26
4.2
Other UI enhancements ............................................................................ 26
5 ERROR CORRECTIONS ...................................................................................... 28

6 NEW DEVICES ................................................................................................. 29
6.1
Handsets and USB modems ....................................................................... 29
6.2
Scanner receivers .................................................................................... 30
7 QUALCOMM-BASED WCDMA AND CDMA2000 TERMINALS AND DATA CARDS ........... 31

8 COMPUTER HARDWARE AND SOFTWARE REQUIREMENTS ..................................... 32
9 DEVICE CONFIGURATION AND WORKSPACE FILES ............................................... 33
10 INSTALLATION ................................................................................................ 34
10.1 Supported operating systems .................................................................... 34
10.2 First-time installation ................................................................................ 34
10.3 Update/Upgrade ....................................................................................... 34
10.4 Uninstallation .......................................................................................... 35
10.5 Dongle runtime drivers ............................................................................. 35
11 LIMITATIONS WITH WINDOWS 8 OPERATING SYSTEM ......................................... 36
12 LIMITATIONS AND ISSUES WITH WINDOWS 7 OPERATING SYSTEM....................... 37
13 FILE FORMAT CHANGES .................................................................................... 38
14 KNOWN ISSUES ............................................................................................... 39
14.1 General and user interface ........................................................................ 39
14.2 Nemo Commander ................................................................................... 40
14.3 Nemo Media Router .................................................................................. 40
14.4 Nemo Walker II/ Nemo Multi Lite ............................................................... 41
14.5 Applications and protocols ......................................................................... 41
15 TROUBLESHOOTING DEVICE CONNECTIVITY ISSUES ........................................... 44
16 TROUBLESHOOTING DATA TRANSFER ISSUES ..................................................... 45
16.1 PS connection works but no data ................................................................ 45
16.2 Antivirus filtering...................................................................................... 45
16.3 Low data throughputs ............................................................................... 46
16.3.1 All Windows versions ........................................................................ 48
16.3.2 Windows 7 ...................................................................................... 49
16.4 Issues with HTTP browsing testing ............................................................. 51
17 REFERENCES ................................................................................................... 52
18 NEMO TOOLS................................................................................................... 53
Page 4
1 NEW FEATURES
Nemo Outdoor 7.6.0 release includes support for the following new features:
LTE-A 3 Component Carrier Aggregation
Small cell and DAS indoor measurement enhancements
New features of Nemo Media Router 2.30 including packet capturing and phone UI monitoring
and control, over-the-air updates etc.
Dropbox testing (PC-based)
IPv4v6 tunneling
TD-SCDMA support with Nemo FSR1 scanner receiver
PCTel MXflex
R&S TSME MIMO measurements
Qualcomm handler enhancements
HiSilicon handler enhancements
Measurement file uploading to Nemo Xynergy
New devices
1.1 LTE-A 3 component carrier aggregation

Anite Network Testing is introducing another industry-first: support for LTE-A FDD, 3 component
carrier aggregation category 6 (300Mbps) testing with Qualcomm Snapdragon 808.
With Nemo Outdoor and Nemo Invex, operators can monitor the performance and quality of their
LTE-A networks. The measurements provide detailed information about the primary (PCell), 1st
(SCell0) and 2nd (SCell1) secondary component carriers, including cell type, PCI, CFI, band,
bandwidth, link adaptation, and radio resource allocation. Nemo Outdoor platform provides true and
accurate data throughput metrics without any limitations with all data protocols. In order to achieve
maximum throughputs with LTE-A devices, the device must be connected to a SuperSpeed USB 3.0
port using a high-quality USB 3.0 cable. Nemo Media Router application will be available with
commercial UEs making it possible to run data protocols on the device.
For detailed information, please see the Nemo file format specification version 2.23 and Nemo
Outdoor LTE data sheets. With Qualcomm-based Cat 6 UEs, option OD0700-44, Qualcomm LTE-A CA
3CC Cat.6 is required in addition to the basic Qualcomm LTE license or Qualcomm LTE-A 2CC license.
With Cat 9 UEs, license option OD0700-47, Qualcomm LTE-A CA 3CC Cat.9 is required.
Page 5
Figure 1. LTE-A example view showing PCell, SCell0 and SCell1 information
The following table explains the parameters to be logged with different UE categories and handlers.
UE Category
Page 6
Handler/ License
Parameters Logged
Cat 4 or Cat 6
Qualcomm LTE FDD
Log everything except Secondary

Cell parameters
Cat 4
Qualcomm LTE-A CA 2CC Cat.4
Log everything including

parameters for 1st Secondary Cell
(SCell0)
Cat 6

Cell parameters
Cat 4 or Cat 6

parameters for 1st Secondary Cell
(SCell0)
Cat 6

parameters for 1st and 2nd
Secondary Cells (Pcell, SCell0,
SCell1)
Cat 9

SCell1)
Cat 9
Log everything except parameters

for 2nd Secondary Cell (PCell,
SCell0)
Cat 6 or Cat 9

UE Category
Handler/ License
Parameters Logged
SCell1)
Cat 4
Log everything

Cat 9
Log everything except parameters

for 2nd Secondary Cell (PCell,
SCell0)
Cat 9

Cell parameters
Table 1. Qualcomm handler compatibility
User is notified if the handler is not compatible with the UE and some of the parameters are not
logged:
Error: Some of the data is not logged due to missing license option. You can still continue
measurement. Please contact Nemo Technical Support for further information.
Go back to list of new features.
1.2 Small cell and DAS indoor measurement enhancements

1.2.1 Small cell and distributed antenna system types
Support for DAS and small cell cell types in the map and indoor views has been added. Information
about the cell types is stored in BTS (cell site file). BTS file format version 1.15 includes the
following new cell types: SMALL_CELL and DAS. Cell icon on the map is shown as a circle.
1.2.2 DAS anomaly analysis in indoor view

With the DAS anomaly analysis user can easily check and verify in-building small cells and DAS
(Distributed Antenna Systems) antennas giving simple pass, fail or untested result for each cell.
With this simple test engineers can verify that all cells are tested and passed without need to revisit
and redo the indoor venue.
By using either iBwave indoor plans or Nemo BTS files (.nbf), indoor small cell antennas and
transmitters can be shown on the indoor map. Analysis can be enabled and settings defined via BTS
properties.
When the analysis is enabled, a new circle is drawn around cells that have a cell type of either DAS
or small cell and direction is set to 360 degrees. The cell type must be defined in the BTS file. The
color of the large circle depends on the cell test status and the transparency setting.
Whenever a marker is placed within the test radius of the serving cell location, the current signal
level of the serving cell is checked. If the signal level exceeds the configured limit, cell is considered
as passed. If the signal level is below the configured limit, the cell is considered as failed.
Page 7
Figure 2. Failed cell on left side (red) and passed cell on the right (green).
The same analysis is also performed during playback mode if the analysis is enabled.
In addition to the map view, a table displays the analysis results for each cell. The table includes
information about the system, band, channel number, Cell ID, PCI/SCR/PN, cell name, cell type,
signal level (RX Level, RSCP, or RSRP depending on system), and test status (Passed, Failed or
Untested). With multi-configurations, each device needs its own map view.
Figure 3. DAS anomaly analysis results.
Page 8
1.2.3 Real-time RF ingress analysis calculation

RF ingress analysis calculates distributions related to indoor (small cell and DAS) vs outdoor
(macro) cell coverage and gives real-time information whether RF ingress by macro cell is detected
or not or do small/DAS cells provide clear dominance indoors. The analysis is based on BTS file cell
type information read from the BTS file (.nbf). A cell is considered to be indoor or small cell if the
cell type in the BTS file is SMALL_CELL or DAS, otherwise the cell type is macro cell.
The following distribution value sets are calculated:
Parameter
Thresholds
Serving cell type Macro %
Cumulative percentage of time where

the serving cell type is macro cell. This
value should be as low as possible
during indoor measurements. High
value indicates RF ingress by macro
cells and optimization is needed.
Serving cell type Small %
Cumulative percentage of time where

the serving cell type is small cell. High
value indicates good dominance of
small/ DAS cells.
No RF ingress detected %
Macro vs small sell

strength. Level of the
strongest small cell < -6
dB
Cumulative percentage of time when

the level of the strongest macro cell
has been lower than the level of the
strongest small cell. No RF ingress
detected. High value indicates good
dominance of small/ DAS cells.
Moderate RF ingress
Macro vs small cell

strength >= -6 and < -1
dB

has been lower or close to level of the
strongest small cell. High value
indicates moderate RF ingress caused
by macro cells.
Macro vs small cell

strength >= -1 to -1 dB

has been equal to the strongest small
cell. High value indicates high RF
ingress caused by macro cells and
optimization is needed.
Macro vs small cell

strength >= 1 dB

has been higher than the level of the
strongest small cell. High value
indicates serious RF ingress caused by
macro cells and optimization is needed.
detected %
High RF ingress
detected %
Serious RF ingress
detected %
Table 2. RF ingress parameters.
Page 9
Description
Figure 4. RF ingress analysis parameters.

The signal strength comparison is done for each system and the comparison is performed for
serving, neighbor, detected, listed and monitored cells in each system.
LTE: RSRP
UMTS: RSCP
GSM: RXL Sub/RXL full (neighbor set)
CDMA: RSCP
It is also possible to plot RF ingress cell type (n/a, macro, small, macro+small) with map route
coloring using a colorset.
Figure 5. Cell type.
1.2.4 UTM coordinates and marker coordinate conversion with iBwave files
iBwave files may contain UTM coordinates in addition to WGS84 coordinates. iBwave support has
been updated to support both coordinate formats when loading transmitter files. Please note that
both the tab file and transmitter file must use the same coordinate system.
A new option has been added to indoor settings to save markers in GPS (lat. / lon.) WGS84 format
when the iBwave file has UTM coordinates. The coordinate system used is saved in the marker file.
The coordinate system will be saved under [CoordinateFormat], coordinatesystem, e.g. below:
[CoordinateFormat]
coordinatesystem=latlon
Currently three values are supported by Nemo Outdoor and Nemo Handy:
latlon
utm
metric
If the floorplan uses generated, non-earth coordinates (i.e. imported with map dimensions instead
of georegistering), the value is metric.
In playback mode, the coordinate system is detected when loading marker files so that both WGS84
and UTM format marker files are displayed correctly.
Page 10
Figure 6. Indoor properties.
1.2.5 Area zones with iBwave importing

Zones in iBwave files are defined as MapInfo mif/mid files. An option has been added to Indoor
window to display the zones on top of the floorplan. Zones can be used e.g. to show DAS antennas
for particular area.
Figure 7. iBwave floorplan with area zones.
1.2.6 Measurement filename parameter based on iBwave floorplan identifier

New parameter %G or %g has been added to the measurement filename template. The
parameter value identifies the GUID value of the currently active iBwave floorplan layer.
This parameter is only supported in Indoor Mode measurement with an open IBWC building file.
Figure 8. Indoor mode.
Page 11
Figure 9. Filename editor.

1.3 Nemo Media Router

Nemo Media Router is the Anite Network Testing proprietary communications interface and
application developed for Android-based smartphones (patent pending). With the Nemo Media
Router (NMR) interface Android-based smartphones communicate with PC-based applications, such
as Nemo Outdoor and Nemo Invex. The initial version of NMR included support for voice quality
testing PESQ and POLQA.
NMR provides the real QoE measurements as all the services are running on a smartphone. A PC
user controls and runs the services on the phone via an NMR interface. The NMR application on the
phone transfers the KPIs related to the data transfer to the PC. NMR is the solution for current and
future technologies supporting high data rates, such as, using multiple LTE Cat 6 UEs on a single
CPU.
Key Benefits
Cost-effective and simplified. Ideal for benchmarking and running simultaneous LTE highspeed UEs on a single commercial laptop with up to six handsets
Enhanced data capacity per CPU which means more devices per CPU with higher data rates
compared to running data services on a PC
Only one IP address (host address) for all test UEs with multi-configurations
No limitations for performing application testing with multiple UEs simultaneously on a

single CPU, (e.g. YouTube testing)
Measurement is done from end-user perspective using smartphones QoS settings
No issues with PC CPU load lowering data rates. No need to tweak TCP/IP settings on the PC
Smaller (lighter) and cost-effective hardware and easy installation. In some cases no
permanent installation needed due to much lower overall power consumption
Data transfers can be made using the NMR interface where the protocol service is running on a
smartphone. User can select via the Nemo Outdoor device configuration settings the appropriate
method for performing data transfers. The NMR application must be installed on a smartphone and
have a valid license. If NMR is activated, all supported commands/services are always executed via
Page 12
NMR. Commands/services that are not supported by NMR are automatically executed on the PC.
The user interface uses the same manual and scripted commands with NMR as with PC.
With voice quality measurements, the smartphone records the received sample audio files and
transfers audio files via the NMR interface to a computer in real time. The computer calculates the
PESQ/POLQA MOS scores and the values are written to the Nemo Outdoor log file. PESQ and POLQA
licensing will remain the same. NMR also supports multiple phones connected simultaneously to one
CPU. The maximum number of simultaneous connections with voice quality and data is six phones
connected to one CPU with Windows 8 OS and eight phones with Windows 7 OS.
Standard data cable (OD0100-08) Hama micro USB 2.0 USB A to micro B cable must be used with
the test handsets.
1.3.1 New features in Nemo Media Router version 2.30

This version includes new features introduced in the following chapters, error corrections and
enhancements that improve the reliability.
1.3.1.1 Test handset user interface monitoring and controlling via Nemo Outdoor user
interface
Sometimes there is a need to change the test handset settings before testing, for example, to
disable data roaming or change APN settings. With a high number of test handsets, and especially
when handset isolation modules are used, changing the settings requires opening the housing which
makes the process slow and inconvenient for the user. With the latest release NMR supports test
handset UI monitoring and controlling via the TeamViever QuickSupport application installed to the
test handsets. This makes it possible to make a remote connection to the test handset via the
Nemo Outdoor user interface. Please note that one active connection at a time is supported, i.e.
connections to several handsets simultaneously are not possible. The laptop running Nemo Outdoor
must be connected to the internet, for example by using a dedicated handset or a USB modem
connected to the controlling laptop. The test handset must be in service and support data services.
Packet data must be enabled. NOTE! Samsung Galaxy S4 Mini (GT-I9197) do not support remote
control.
The Teamviewer Quick Support (QS) application and Teamviewer Remote Control add-on module
are preinstalled to all test handsets delivered by Anite Network Testing with the Nemo Invex
handset isolation modules. TeamViewer must be installed also to the PC running Nemo Outdoor.
These applications can be downloaded from the Nemo User Club. Please note that Teamviewer can
be used free of charge only with non-commercial use. Customers using the UI monitoring and
controlling with the TeamViewer tools for commercial use must obtain the licenses directly from
TeamViewer (www.teamviewer.com).
The following table shows the required applications with compatible version numbers. The
TeamViewer applications must not be automatically updated until notified by Anite Network Testing.
Updating can cause the remote UI and control to stop working.
Page 13
Application
Version
Nemo Media Router
2.30.099
Nemo Outdoor
7.6.0.7
TeamViewer (PC)
10.0.43174
Application
Version
TeamViewer QuickSupport (test handset)
10.0.3224 and 10.0.3264
TeamViewer QuickSupport Add-on for Samsung
8.0.1184
Table 3. Compatible versions.
1.3.1.2 Packet capturing

Support for packet capturing (.pcap) and file writing to the TCPSTAT-event has been added. Users
can activate/ enable packet capturing for the device from device properties. With test devices
running NMR version 2.30 or higher, packet capturing is done by NMR on the test handset. During
measurements, the packet capturing file is stored to the memory of the handset. The packet
capturing file is transferred to the PC after measurement is stopped. A pcap file is generated for
each test device. The IP service access time and IP termination time KPIs can be extracted from the
pcap file. KPIs can be logged only by enabling the packet capturing. Full packet capturing logging
should be done only when troubleshooting the required. For test handsets without the NMR
application, the pcap file is generated on the PC.
1.3.1.3 HTTP PUT

HTTP PUT protocol running on PC was implemented to Nemo Outdoor version 7.5.0. Now this
protocol is supported also with NMR. Both POST and PUT operations to upload files with the HTTP
protocol can be selected via Nemo Outdoor UI.
HTTP POST
Requests that the server accepts the entity enclosed in the request as a new subordinate of the web
resource identified by the URI. The data POSTed might be, for example, an annotation for existing
resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of
data that is the result of submitting a web form to a data-handling process; or an item to add to a
database.
HTTP PUT
Requests that the enclosed entity be stored under the supplied URI. If the URI refers to an already
existing resource, it is modified; if the URI does not point to an existing resource, then the server
can create the resource with that UR. [2]
1.3.1.4 GPS information

Instead of using a separate GPS receiver for positioning, user can enable GPS data from the test
handset running the NMR application. User can enable GPS data only for one device in a multidevice configuration. Note that every NMR GPS-enabled device creates GPS events for all devices in
the measurement. It is recommended to enable GPS only with one NMR device.
1.3.1.5 Over-the-air updates

Nemo Media Router application updates can be done using the NMR user interface. Together with
the test handset UI remote control and monitoring, OTA updates can be done also with Nemo Invex
handset isolation modules without opening the cover.
Page 14
1.3.2 Nemo Media Router licensing options

Nemo Media Router version 2.00 introduced new licensing options. Licenses can be easily upgraded
over the air (OTA) by launching the Nemo Media Router application after installing the application to
the handset. The following license options are available with Nemo Media Router version 2.30:
Product
Code
Option
Description
OD1600-04
NMR Voice Quality Testing

Option
Transfers audio files via the NMR interface to

a computer in real time. Requires also Nemo
Outdoor or Nemo Invex PESQ & POLQA
licenses (optional license)
OD1600-05
NMR Data & Application

Testing Option
Includes FTP, Ping, HTTP/ HTTPS, YouTube

video streaming, and HTML browsing
protocols. Client running on the smartphone
(optional license)
OD0700-38
WLAN Option
Enables WLAN measurements

NOTE! Not available with HI modules
(optional license)
Table 4.NMR 2.30 license options.
1.3.3 Compatibility and update process

Nemo Media Router version 2.30.099 is compatible with Nemo Outdoor 7.6.0.7. NOTE! NMR
versions 1.0 or 1.1 are not supported with Nemo Outdoor version 7.3.0.6 or higher. Customers
using Nemo Media Router versions 1.0 or 1.1 should not update Nemo Outdoor to the latest version
before updating the Nemo Media Router application on the test handsets. Nemo Media Router
application and installation instructions are available in the Nemo Outdoor user manual. NMR
application can be downloaded from the Nemo User Club and it is recommended to copy files to a
USB flash drive e.g. Kingston DTDUO 16GB or similar supporting micro USB port. Start the NMR
application on the phone and change the mode to Mass memory by clicking the USB (Outdoor)
text if you want to use the flash drive. Plug the flash drive to the handset. Alternatively use the
handset browser and download the files directly from Nemo User Club. After the NMR installation
proceed with the TeamViewer application installations. First install the TeamViewer QuickSupport
and then the Add-On for Samsung. After installation remember to change the mode back to
Outdoor. NOTE! For commercial use the TeamViewer license is required. Please contact
TeamViewer directly. In the future check for updates by using the NMR application by selecting
Check for updates from the NMR menu.
Page 15
1.3.4 Supported handsets with Nemo Media Router

The handsets shown in the table below are supported with the Nemo Media Router application.
Version number presents the versions at the time of initial release.
Product
Code
Handset
Firmware
NMR version (*)
Nemo Outdoor
version (*)
TBA
Samsung Note 4
Note SM-N910T
(TMOB)
MPSS.DI.3.0.c5-00300M9625TAARANAZM1.7386.2 (TAARANAZ Nov

11 2014 19:36:24)
2.30.099
7.6.0.7
TBA
Sony Xperia Z3
D6653
MPSS.DI.3.0.c9.1-00022M8974AAAAANAZM-1
(AAAAANAZ Nov 26 2014
03:27:54)
2.30.099
7.6.0.7
MH1700-45
Samsung Galaxy S5
SM-G900M
MPSS.DI.2.0.1.c2.200006M8974AAAAANRZM-1
(AAAAANRZ May 9 2014
21:44:23)
2.20.078
7.5.0.5
MH1700-39
Samsung Galaxy
Note 4
MPSS.BO.1.0.r10-00108M9635TAARANAZM1.5514.1 (TAARANAZ Sep

16 2014 20:04:39)
2.11.060
7.4.1.13
MPSS.BO.1.1.r10-00108M9635TAARANAZM1.5514.1 (TAARANAZ Oct

4 2014 16:47:00)
2.11.060
7.4.1.13
MPSS.DI.2.0.1.c2-00055M8974AAAAANRZM-1
(AAAAANRZ May 23 2014
19:27:09)
2.11.060
7.4.1.13
(AAAAANRZ Mar 31 2014
01:04:01)
2.11.060
7.4.1.13
SM-N910F
MH1700-40
Samsung Galaxy
Note 4
SM-N910G
MH1700-41
Samsung Galaxy S5
SM-G900T1
(Metro PCS)
MH1700-42
Samsung Galaxy S5
SM-G900R4
(US Cellular)
MH1700-35
Samsung Galaxy S5
4G+ SM-G901F
MPSS.BO.1.0.c1-00091M9635TAARANAZM-1
(TAARANAZ Aug 11 2014
11:59:20)
2.10.054
7.4.0.9 (Data only,

not voice quality)
MH1700-26
Samsung Galaxy S5
SM-G900I
15:46:27). Android 4.2
2.01.042
7.3.1.9
MH1700-25
Samsung Galaxy S5
SM-G900F
15:46:27). Android 4.2
2.01.041
7.3.1.9
MH1700-29
Samsung Galaxy S5
SM-G900T (T-
M9615ACEHWMAZD1795
(ACEFWMAZ Aug 17 2012
2.01.041
7.3.1.9
Page 16
Product
Code
Handset
Firmware
NMR version (*)
Nemo Outdoor
version (*)
Mobile)
20:29:27)
MH1700-30
Samsung Galaxy S5
SM-G900P (Sprint)
M8930B-AAAATAZM5.0.060165 (BBAAATAZ
Jan 30 2014 14:45:25)
2.01.041
7.3.1.9
MH1700-31
Samsung Galaxy S5
SM-G900W8 (Bell)
M8930B-AAAATAZM5.0.060165 (BBAAATAZ
Jan 30 2014 14:45:25)
2.01.041
7.3.1.9
100314-21
Samsung Galaxy S
III (I9305)
M9615ACEHWMAZD1795
(ACEFWMAZ Aug 17 2012
20:29:27)
1.0.011
7.1.0.6
2.00.034
7.3.0.6
MH1700-03
Samsung Galaxy S4
(GT-i9505)
M9615A-CEFWTAZM4.0.17062 (ACEFWTAZ
Apr 12 2013 18:16:13)
2.00.034
7.3.0.6
MH1700-07
Samsung Galaxy S4
Mini (GT-i9195)
M8930B-AAAATAZM3.2.27040 (BBAAATAZ Jul

15 2013 11:32:02)
1.10.015
7.2.0.6
2.00.034
7.3.0.6
MH1700-10
Samsung Galaxy
S4+ (GT-i9506)
M8974A-AAAANAZM1.0.180095 (AAAAANAZ
Dec 12 2013 16:26:28)
Android 4.3
2.00.034
7.3.0.6
MH1700-17
Samsung Galaxy
Note 3 (SM-N900T)
SET_BY_CM (AAAAANAZ
Sep 13 2013 18:20:25)
2.00.034
7.3.0.6
MH1700-19
Samsung Galaxy S4
Mini (SPH-L520
Sprint)
M8930B-AAAATBZM6.0.01049 (BBAAATBZ
Nov 4 2013 20:22:08)
2.00.034
7.3.0.6
Table 5. Supported handsets with Nemo Media Router application.

Standard data cable (OD0100-08) Hama micro USB 2.0 USB A to micro B cable must be used with
the test handsets.
(*) with initial release.
For a complete list of supported devices, please see the separate document Nemo Outdoor 7.5.0.5
Compatible Devices.pdf.
Do not upgrade, root, or reflash your measurement terminal firmware. Doing so will
cause the terminal to permanently lose its measurement capability!
1.4 Generic handler enhancements

1.4.1 Support for GSM WFS AMR codec
GSM WFS AMR full rate channel for wideband speech. Information is logged to CHI event.
Page 17
1.5 Qualcomm handler enhancements

Qualcomm handler includes the enhancements mentioned in the following chapters and error
corrections. Please see the readme.html located in the installation folder of Nemo Outdoor for a list
of error corrections.
1.5.1 Support for new messages with Qualcomm diagnostics logging

Activating the NBL logging and trace decoding support has been added for the following new
Qualcomm diagnostics messages:
ML1 PUCCH Power Control (per TTI)
ML1 PUSCH Power Control (per TTI)
L1 CDRX Event Info
LL1 PDSCH Demapper Config
L1 PCFICH Decoding Results
LL1 PDCCH Decoding Results
ML1 PDSCH Stats Indicator
L1 PMCH Decode Results
ML1 All DL Channels Decode Results
ML1 PDCCH PHICH Ind Report
ML1 GM TX Report
ML1 Uplink PKT Build Indication
ML1 Radio Link Monitoring Info
RLC DL UM Data PDU
RLC UL UM Data PDU
PDCP DL Data PDU
PDCP DL Cipher Data PDU
PDCP UL Data PDU
PDCP UL Cipher Data PDU
With the optional Qualcomm diagnostics data logging it is possible to log high sample rate per TTI.
A separate .nbl file is generated along with the .nmf ASCII log file.
1.5.2 Other enhancements
Support for LTE cell measurements during UMTS
Support for CSFB calls events between LTE and CDMA with Qualcomm-based terminals
1.6 HiSilicon handler enhancements

HiSilicon handler includes the enhancements mentioned in the following chapters and error
corrections. Please see the readme.html located in the installation folder of Nemo Outdoor for a list
of error corrections.
Page 18
1.6.1 Forcing to barred PCI

UE can be forced to a barred PCI (LTE cell). The UE reads SIB1 from a barred LTE cell when cell
barring is not set to ignore. It may take up to five minutes for the UE to read the SIB1 again from
that same cell. The cell barring forcing status cannot be read from the device so it is not updated in
LOCK event and Nemo Outdoor UI when a device is started.
1.6.2 GSM and UMTS band lock

GSM and UMTS band lock with HiSilicon based Huawei Android devices is now supported.
Please see the readme.html located in the installation folder of Nemo Outdoor for a list of error
corrections.
Page 19
2 APPLICATIONS AND PROTOCOLS
2.1 Dropbox testing

Dropbox is a file hosting service operated by Dropbox, Inc. that offers cloud storage, file
synchronization, personal cloud, and client software. Dropbox allows users to create a special folder
on their computers, which Dropbox then synchronizes so that it appears to be the same folder (with
the same contents) regardless of which computer is used to view it. Files placed in this folder are
also accessible via the Dropbox website and mobile apps. Data is transferred using HTTPS data
protocol.
With Nemo Tools users can perform manual or automated file upload and download testing and use
their Dropbox account similar to regular users. With the initial support, a PC-based solution is
available with single or multi configurations. PC-based Dropbox testing does not require an optional
license. The following KPIs and statistics are available:
Service Accessibility
DNS host name resolution time (ms)
Dropbox connection attempts
Dropbox connection success
Dropbox connection failures
Dropbox connection time (Service access time)
Dropbox connection attempt success rate
Dropbox connection success rate
Dropbox connection time
Service Retainability
Dropbox disconnects (dropped)
Dropbox disconnects (normal)
Dropbox transfer attempts
Dropbox transfer failures
Dropbox transfer success
Service Integrity
Dropbox transfer success rate
Dropbox transfer time
Application data throughput DL/ UL
Others
Page 20
Dropbox operation (Upload/ Download)
2.2 Support for data transfers using IPv6 tunneling over IPv4
connection
Support for application protocol transfers with IPv6v4 tunneling has been implemented. Data
transfers using IPv6 addresses are supported using a new IPv6 option in the transfer configuration.
In case the host does not support IPv6, the transfer is reverted to IPv4.
2.3 Support for TCP connection establishment time

TCP connection establishment time is the delay calculated between SYN and SYN-ACK frames
during TCP handshake when making a connection to a remote host. KPI is available with the
following protocols: FTP, HTTP (GET), POP3, IMAP, SFTP, SMTP, TCP Iperf and Twitter. Value is
written to DAC event. KPI is not available when data protocols are running by NMR.
Page 21
3 OTHER FEATURES & UPDATES
Chromium API upgraded from 1.1180 to 3.2339

o
Fixes stability issues seen with some of the webpages
PEVQ-S upgraded from 1.6 to 1.14

o
Includes bug fixes and other enhancements
3.1 Generic scanner handler enhancements

A new parameter called MIMO mode has been added to the OFDMSCAN event that indicates the
current MIMO mode of each LTE PCI. The value of the parameter specifies the received TX-RX port
configuration in the following format: [number of TX ports used] x [number of RX ports used].
3.2 Nemo FSR1 scanner handler enhancements

3.2.1 TD-SCDMA
TD-SCDMA pilot scanning is supported with bands 34, 39 and 40 (A-F). Requires Nemo FSR1
firmware version 04.04.00 and optional Nemo FSR1 TD-SCDMA handler option, OD0700-45. The
following parameters are supported:
Carrier RSSI (pilot scanning mode) (PCCPCH)
Carrier RSSI (pilot scanning mode) (SYNC DL)
Cell parameters ID (PCCPCH)
Cell parameters ID (SYNC DL)
Channel number (PCCPCH)
Channel number (SYNC DL)
Channel type
Ec/I0 (PCCPCH)
Ec/I0 (SYNC DL)
RSCP (PCCPCH)
RSCP (SYNC DL)
Time offset (PCCPCH)
Time offset (SYNC DL)
Frequency scanning or band scan with TD-SCDMA is not currently supported.
Page 22
3.3 PCTel scanner handler enhancements
SeeGullMaster API upgrade to 1.8.0.2 for MX, EXflex and IBflex scanners
Support for LTE FDD band 25 has been added to MX, EXflex and IBflex scanners
Support for LTE TDD band 44 has been added to EXflex and IBflex scanners
3.3.1 PCTEL MXflex support

The initial version supports the following systems and bands:
GSM 850/ 900/ 1800/ 1900
UMTS 850/ 900/ 1800/ 1900/ 2100/ AWS
CDMA/ EVDO 800/ 1900
TD-SCDMA 2000 band A
LTE FDD & TDD. E-UTRA bands 1- 5, 7-8, 12-14, 17-21, 24, 27-28, 38-43
Frequency scanning, pilot mode scanning and spectrum scanning are supported. Requires handler
OD0700-46, PCTEL MXflex. The systems, bands, and scanning features above require optional
technology, bands, and software options for PCTEL MXflex scanner receiver. Please contact Anite
sales for further information.
3.4 Rohde & Schwarz scanner handler enhancements

3.4.1 Vicom interface
Added support for Vicom interface version 15.50.
3.4.2 TSME MIMO scanning

For LTE MIMO measurements, two TSMEs can be connected to the same PC running Nemo Outdoor
and synchronized. Synchronization is done using the accessory cable TSME-ZC2 (1522.6560.02)
between the TSME AUX ports. TSMEs are connected to the PC with a single LAN port via an Ethernet
switch. Both TSMEs can be powered from the same power source using the TSME-ZYC
(1514.7290.02) DC Y-cable.
Each TSME needs a band option (can be for a different number of bands). In total, one LTE
MS0200-13 and one MIMO option MS0200-15 must be present, on TSME1 or TSME2.
Figure 10. Example configuration.
Page 23
Figure 11. TSME MIMO HW configuration.

[1]
Ordering Information for TSME MIMO HW Kit
Product Code
MS1200-00
Item
R&S TSME MIMO HW Kit
Description
Includes:
MS0200-01, Synchronization cable
for 2 TSME (TSME-ZC2)
1522.6560.02, 1pcs 105
MS0200-02, Power DC Y-cable for
2 TSME (TSME-ZYC)
1514.7290.02, 1pcs
499038-01, HP/3Com Gigabit
Switch 5 Port or similar
499048-05, Inverter Mascot 9984
12V 150W for the switch. NOTE:
with EU socket!
Table 6. TSME MIMO HW kit.
Page 24
3.5 Nemo Invex new features

The following new features related to the Nemo Invex system help users to distinguish the physical
connections between the Nemo Invex system and the test devices more easily.
Displaying Nemo Invex system-related information in Start Devices dialog, including Nemo
Invex chassis number (with Nemo Invex II only), UIC slot number, and USB port number.
Support for Nemo Invex reset commands in Start Devices dialog. User can perform the Nemo
Invex UIC module reset operation and the USB port reset operation (new in version 7.6.0)
with a context-menu command. When the USB port reset is executed, it will disable the
requested USB port, wait for 5 seconds, and re-enable the port.
Improved device not responding error message for Nemo Invex with information about the
chassis number (with Nemo Invex II only), UIC slot number, and USB port number for
devices connected to Nemo Invex.
Page 25
4 USER INTERFACE
4.1 Measurement file uploading directly to Nemo Xynergy

With this new feature Nemo Outdoor and Nemo Invex users can easily generate a folder structure
and upload the measurement files directly to Nemo Xynergy data analytics tool. Files are uploaded
to folders based on the selected project type, region, market, cluster, and project.
Uploading the files to Nemo Xynergy can be done through the Measurement Report dialog,
Measurement List configuration, and through the generic upload in the File/Send
Measurements to server.
Figure 12. Nemo Xynergy send measurements options.
4.2 Other UI enhancements
Improved device mode configuration in Auto detection dialog allowing user to multi-select
devices and change the data/voice quality settings for multiple devices easily.
Support for window hiding with browser and PEVQ-S protocols.
Support for option to include packet capture logs (.pcap), statistics (.csv), .gpx (xxfile), and
indoor marker (.mrk) in measurement file upload
o
New user interface option has been added that allows the user to specify if the files
listed above should be sent during measurement file upload
In remote mode, when field unit is controlled by Nemo Commander, the option can
be selected with Nemo Commander
Page 26
Images can be exported to Excel using edit/export images function
Support for copying parameter descriptions to clipboard in the parameter tree
New CSFB call statistics

o
CSFB call setup time (alerting)
Delay from L3 EXTENDED_SERVICE_REQUEST layer message in LTE to call

connected, alerting event in UMTS (CAC2 event)
CSFB call setup time (answered)
Delay from L3 EXTENDED_SERVICE_REQUEST layer message in LTE to call

connected, answered event in UMTS (CAC 3 event)
Support for IMS SMS statistics parameters

o
SMS statistics parameters are calculated on normal SMS messages and IMS SMS
messages and IMS SMS statistics on IMS SMS messages only
Page 27
Support for specifying the number of decimals for the parameters in the user interface
New CDMA and EVDO statistics

o
RSCP active set measurement avg., max and min
Ec/I0 active set measurement avg., max and min
Carrier RSSI measurement avg., max and min
Separate statistics for PESQ and POLQA audio quality average
Support for LTE and UMTS RRC connection statistics
Support for IMS registration success statistics parameter
5 ERROR CORRECTIONS
Please see the readme.html located by default in the C:\Program Files (x86)\Anite\Nemo Outdoor
for error corrections.
Page 28
6 NEW DEVICES
6.1 Handsets and USB modems

Product
Code
TBA
Handset
Dev. Capability
Huawei
Mate7-L09
LTE FDD
700/800/850/900/1800/1900
/2100/AWS/2600
Limited
support
LTE TDD 2300
Handler
HiSillicon
# Verified
UEs/ CPU
FW version
FW:
21.223.00.00.031
Huawei Mobile
Connect 1.3.0.0
FW:
21.300.00.01.020
Huawei Mobile
Connect 1.3.0.0
MPSS.BO.2.0.1.c3
.5-00023M9635TAARANAZ
M1.15158.1.15214.
SAMSUNG USB
Drive for Mobile
Phones 1.5.45.0
LTE-A CA
2CC Cat.6
Driver
(E-UTRAN bands 28, 20, 5, 8,

3, 2, 1, 4, 7, 40)
LTE UE Cat 4, 6
CA intra-band contiguous:
40C, 28C, 1C, 2C, 3C, 4C, 5C,
7C, 8C, 20C
CA intra-band noncontiguous: N.A.
CA inter-band: 1A_5A,
1A_20A, 1A_28A, 2A_28A,
3A_5A, 3A_7A, 3A_20A,
3A_28A, 4A_28A, 5A_1A,
5A_3A, 7A_8A, 7A_20A,
7A_3A, 8A_7A, 20A_3A,
20A_7A, 28A_1A, 28A_2A,
28A_3A, 28A_4A
WCDMA
850/900/1900/2100/AWS
HSDPA UE Cat 24, HSUPA UE
Cat 6
GSM 850/900/1800/1900
TBA
Huawei
Mate7-TL00
LTE FDD 1800/2100/2600
HiSillicon
LTE TDD
1900/2300/2500/2600
LTE-A CA
2CC Cat.6
Limited
support
(E-UTRAN bands 3, 1, 7, 39,

40, 41, 38)
LTE UE Cat 4, 6
CA intra-band contiguous:
38C, 39C, 40C, 41C, 1C, 3C,
7C
CA intra-band noncontiguous: N.A.
CA inter-band: N.A.
WCDMA 850/900/1900/2100
Cat 6
GSM 850/900/1800/1900
TBA
Samsung S6
SM-G920P
(Sprint)
LTE FDD
700/850+/850/1900/1900+/
AWS
LTE TDD 2500
Page 29
Qualcomm
LTE-A 2CC
Cat. 6
FDD/ TDD
Product
Code
Handset
Limited
support
Dev. Capability
Handler
(E-UTRAN bands 12, 26, 5, 2,

25, 4, 41)
Qualcomm
CDMA/
1xEVDO
LTE UE Cat 4
# Verified
UEs/ CPU
FW version
Driver
1 (TAARANAZ Mar
8 2015 17:31:32)
WCDMA 850/900/1900/2100
Cat 6
GSM 850/900/1800/1900
CDMA2000-HRPD
800/ESMR800/1900
(Band class 0, 10, 1)
CDMA2000-1xRTT
800/ESMR800/1900
(Band class 0, 10, 1)
HSPA 42.2/5.76 Mbps, LTE
Cat6 300/50 Mbps, EV-DO
Rev.A 3.1 Mbps
TBA
Samsung
Note 4
SM-N910T
(TMOB)
LTE FDD
700ac/700cb/850/900/1800/1
900/2100/AWS/2600
(E-UTRAN bands 12, 17, 5, 8,
3, 2, 1, 4, 7)
Qualcomm
MPSS.DI.3.0.c500300M9625TAARANAZ
M-1.7386.2
(TAARANAZ Nov
11 2014
19:36:24)
SAMSUNG USB
Drive for Mobile
Phones 1.5.45.0
MPSS.DI.3.0.c9.1
-00022M8974AAAAANAZ
M-1 (AAAAANAZ
Nov 26 2014
03:27:54)
Sony Xperia eng

drivers
v.2.1.0.82
LTE-A CA
2CC Cat.4
LTE UE Cat 4
CA inter-band: 2A_4A (BCS
1), 4A_12A, 4A_2A (BCS 1),
12A_4A
WCDMA 850/1900/2100/AWS
Cat 6
GSM 850/900/1800/1900
TBA
Sony Xperia
Z3 D6653
LTE FDD
700/850/900/1800/2100/
Qualcomm
LTE FDD/
TDD
2600
LTE TDD 2300
(E-UTRAN bands 28, 5, 8, 3,
1, 7, 40)
LTE UE Cat 4
WCDMA 850/900/1900/2100
Cat 6
GSM 850/900/1800/1900
Table 7. New supported UEs.
6.2 Scanner receivers

Product
Code
MS11000-00
Scanner
Handler
# Verified
scanners/CPU
FW version
Driver
PCTEL MXflex 4 Port

Base Platform Receiver
PCTEL
MXflex
SWVer 5. 0. 0. 0,
APIVer 1. 8. 0. 2
MX winusb
Table 8. New supported scanners.
Page 30
7 QUALCOMM-BASED WCDMA AND

CDMA2000 TERMINALS AND DATA
CARDS
Nemo Outdoor is compatible with all devices labeled as CDMA by Qualcomm or QUALCOMM 3G
CDMA using the Qualcomm chipsets. However, Anite Network Testing cannot guarantee full
functionality when a test terminal is used with a Qualcomm-compatible handler. Video calls, for
example, might not work. Please see the separate document Nemo Outdoor 7.6.0.7 Compatible
Devices.pdf. for a list of verified Qualcomm-based CDMA and WCDMA terminals.
CDMA terminals with or without RUIM card purchased from Anite Network Testing must be
registered with a local CDMA operator. Anite Network Testing does not take any responsibility if a
local operator restricts the registration of test terminal(s) supplied by Anite Network Testing.
Page 31
8 COMPUTER HARDWARE AND

SOFTWARE REQUIREMENTS
PC (Lenovo or Dell recommended) with Windows 7 Professional (32/64 bit)
Processor Intel Core i7 2.66GHz or higher
SSD drive recommended
100 MB of free hard disk space for installation and use; 4 GB recommended
One USB port for copy protection module
Ethernet port RJ45
Display resolution 1400 x 900 recommended
Memory 4GB RAM minimum, 8GB recommended
One USB port for copy protection module
One USB port per mobile
Depending on the scanner used, one USB port or serial port or RJ45 or FireWire port per
scanner
One USB port for an external GPS receiver
Page 32
9 DEVICE CONFIGURATION AND

WORKSPACE FILES
Device configuration and workspace files made by Nemo Outdoor 7.5.1 are fully compatible with
Nemo Outdoor 7.6.0.
Page 33
10 INSTALLATION
10.1 Supported operating systems

Supported operating systems are Windows 7 (32/ 64-bit) and Windows 8 (32/ 64-bit).
Windows 7 Professional is highly recommended.
10.2 First-time installation
Note that the installation must be run under Administrator account or other user
account with administrative privileges. Nemo Outdoor setup 7.5.1.8.exe or higher
includes also the IP packet capturing monitoring.
Start Windows and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D).
Copy paste the files to your PC. Select Start | Run in the Windows Status bar. Type D:\Nemo
Outdoor 7.x\Nemo Outdoor x.xx.x in the Open field (xx refers to the version number). Run the
setup.exe and click the OK button. After the installation program starts, follow the instructions on
your screen. NOTE! When the Nemo Outdoor software installation is complete, you will need to
restart the computer.
10.3 Update/Upgrade
Note that installation must be run under Administrator account or other user account
with administrative privileges. Note that if the existing Nemo Outdoor version is
6.2.1.x or older it must be uninstalled via add or remove programs before the Nemo
Outdoor 7.6.x installation can be ran.
Nemo Outdoor setup 7.5.1.8.exe or higher includes also the IP packet capturing
monitoring.
Start Windows and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D).
Copy paste the files to your PC. Select Start | Run in the Windows Status bar. Type D:\Nemo
Outdoor7\Nemo Outdoor x.xx.xx in the Open field (xx refers to the version number). Run the
setup.exe and click the OK button. After the Installation program starts, follow the instructions on
your screen. NOTE! With Nemo Outdoor 6.21 or earlier version the copy protection key must be
attached to USB port during the installation and uninstallation when asked. When the Nemo
Outdoor software installation is complete, you will need to restart the computer.
Page 34
10.4 Uninstallation
Note that the uninstallation must be run under Administrator account or other user
account with administrative privileges.
Nemo Outdoor application must be uninstalled via Add or Remove Programs. NOTE! With Nemo
Outdoor versions 5.80- 6.21 the copy protection key must be attached to USB port during the
uninstallation. With Nemo Outdoor 6.3.x onwards copy protection module is not needed during
uninstallation. When the Nemo Outdoor software uninstallation is complete, you will need to restart
the computer.
10.5 Dongle runtime drivers
Note that the Nemo Outdoor version 7.5.x or higher do not include dongle runtime
driver as the new dongle key is driveless. In case software license is used with Nemo
Outdoor application runtime driver can be installed from http://www.safenetinc.com/sentineldownloads/
Page 35
11 LIMITATIONS WITH WINDOWS 8

OPERATING SYSTEM
Windows 8 operating system has been tested and verified with a limited number of test devices.
NOTE! Windows 7 operating system is highly recommended to be used with Nemo

Outdoor.
Device
Number of UEs/
CPU
Huawei E392/
E398
Driver version: 23.003.07.00.03
Nokia C7-00
Driver version: 7.1.101.0
Nokia 500
Nokia Lumia
920
Driver version : Qualcomm HS-USB Modem 9001 v2.1.0.5

(modem port driver), Qualcomm Drivers for Windows
v1.0.15 (add/remove programs)
Samsung
Galaxy S III GTi9305
Driver version: Kies version 2.3.3.12085_7, driver version

1.5.18.0
Sierra 320U
PcTel MX
MX winusb
PcTel EX
2.1.1.0
(RM-821)
Driver/ Notes
Terratec DMX 6Fire sound card is not compatible with Windows 8 operating system
at the time of release
Page 36
12 LIMITATIONS AND ISSUES WITH

WINDOWS 7 OPERATING SYSTEM
The following limitations with Windows 7 operating system have been noticed and verified by Anite
Finland or informed by the vendors:
ZTE MF820T modem with Windows 7 OS. Device is conflicting with the Sentinel HASP key driver
used with Nemo Outdoor application. After ZTE modem is installed, Sentinel HASP key cannot be
detected by Nemo Outdoor. A workaround is to change the auto tuning settings to normal
immediately after the ZTE modem is installed. Please see Test Devices Known Issues document
for further details on how to change the auto tuning mode
Devices not supporting Windows 7 operating system:
PCTEL LX tri-band scanning receiver

Other limitations:
Debug logging needs administrative privileges if User Account Control Settings (UAC) is
enabled. It is recommended to change UAC settings to Never notify. This can be done
via User Account Control Settings
If UAC is set to always notify it might cause issues with data testing. PS connection can
be established but data transfer cannot be done. Its recommended to change UAC
settings to Never notify. This can be done via User Account Control Settings
Table 9. UAC settings.
Page 37
13 FILE FORMAT CHANGES
Nemo Outdoor 7.6.0 supports the Nemo file format version 2.23 including the following updates and
changes.
Added support for UTM coordinate system value and new iBwave file, venue, building, and floor
name parameters. (#FLOORPLAN)
Added failure battery status value. (DEVI)
Added support for Glonass GPS fix type. (GPS)
Added support for GSM WFS (wideband full rate for speech) channel. (CHI, AMRS)
Added support for MIMO mode information. (OFDMSCAN)
Added support for three and four cells LTE carrier aggregation.
Added support for file_size with Dropbox protocol (DREQ)
Added support for TCP Connection Establishment Time (DAC)
Added support for LTE PDCCH format reporting. (PHRATE)
Added support for non-critical 1/8 vocoder rate and service option for CDMA. (VOCS)
Increased maximum UE TX power from 33 dBm to 40 dBm
Nemo Outdoor 7.60 is compatible with Nemo WindCatcher 3.5.3.0, available on September 2015,
Nemo Xynergy release 15.9.0 available on September 2015. Nemo Commander version 7.30.01,
Nemo Analyze 7.40, available on August 2015. Existing Nemo analytics tools can be used to post
process files made with Nemo Outdoor 7.60 but the new parameters are not parsed.
Page 38
14 KNOWN ISSUES
Test device related known issues for UEs, scanners, and other devices are listed in a separate
document: (Nemo_Outdoor_7.6.0.7_Test_Device_Technical_Notes_June_2015.pdf).
14.1 General and user interface
Note that if there is a system that measures acceleration in the laptop and which
causes the hard disk to stop when jolted, it should be turned off. Otherwise there
may be breaks in the measurement files. With voice quality testing this can be seen
with missing MOS scores, and with other test devices with gaps in the measurement
results
Table 10. Lenovo active protection system properties.
Running Nemo Outdoor setup directly from the USB flash memory wont work. Workaround
is to copy the files to PC prior running the setup
Download stops responding. Applies to Windows Vista and Windows 7 operating systems.
When you try to download a file, the download stops responding and then times out. The
problem occurs when you use a USB modem that has a data transfer speed that is faster
than or equal to 240 kilobits per second (Kbps). The problem occurs because of a limitation
in the current USB modem driver (Usbser.sys). The hotfix download is available from
http://support.microsoft.com/kb/925681
Please select View and request hot fix downloads and follow the instructions to download
the appropriate file. Files can be found also from the DVD supplied by Anite (Nemo Outdoor
Page 39
6.0\Setup\Microsoft hot fix). Please note that for each operating system there is a separate
file available:
Windows 7, Windows6.1-KB925681-x86.msu
Windows Vista, Windows6.0-KB925681-x86.msu

It is highly recommended not to use the User Parameters functionality during multi device
testing as the decoding of L3/ RRC messages will cause a high CPU load. If performance
problems are found, it is recommended to remove all user parameters from the user
interface.
If the message Server Busy is displayed on the screen, it is recommended that the
packetmon.exe be killed using the task manager. Packetmon.exe is used by the Microsoft
Network Monitor. Microsoft Network Monitor is needed only with the video streaming quality
or IP packet capturing functionalities. If IP packet capturing or video streaming quality
measurements are not required its recommended to not install Microsoft Network Monitor.
Line graph zooming with mouse wheel does not work occasionally
14.2 Nemo Commander

When the Nemo Invex system includes two or more active chassis, the measurement file prefix is in
format: unitprefix_unit_unitprefix_unit_date and time. E.g.
remote_invex_240031175011170167_remote_invex_240031175011170167_14Mar14_110000
14.3 Nemo Media Router
A data cable must be connected to the computer and to the test handset before switching on
power to the handset. In case handset power is turned on before connecting the data cable,
Nemo Media Router does not always detect the data cable and connection to Nemo Outdoor
fails. In such a case, exit the NMR application and it will automatically restart.
Samsung Galaxy S4 mini (GT-I9197) do not support remote control
Packet capturing, full logging should be used only for troubleshooting purposes as the file size
of the packet capturing file is limited by the memory of the test handset. Error message is
shown in the Nemo Outdoor user interface when memory is full
Remote UI control and monitoring:

o
If user has already started a PC client connection to the device before NMR is asked
to start accepting connections, it may take over 30s for the connection to succeed
Screen power saver should be disabled, because Teamviewer will not work if it is
not visible and the active application
DNS query is not supported
Application level throughput is not available with HTTP browsing testing
iPERF UDP DL testing cannot be done with test handsets running Nemo Media Router
application. Non-NMR test handsets are required
Ping testing using delay from reply to request does not work using NMR. Workaround is to use
delay between requests. Repeat until stopped is not supported at the moment and repeat X
times should be used
Page 40
WLAN measurements via Nemo Media Router

o
WLAN quality is not available
WLAN measurement is not supported with Invex HI modules
YouTube measurements via Nemo Media Router

o
PER event is not available
Data stream playback position, data transfer content type, data transfer video
codec and data transfer audio codec and file size are not available
14.4 Nemo Walker II/ Nemo Multi Lite

Nemo Multi Lite
Samsung Galaxy Note 4 SM-N910G/ F/ T handsets must be removed from the holders
before closing the lid. Otherwise closing the lid will damage the handsets. The suitcase has
not been designed for bigger handsets, such as Note 4.
When using max. six Samsung smartphones (e.g. Note 4 handsets), the system cannot
charge all handsets, and therefore the batteries of the test handsets will run out. It is
recommended to start testing with fully loaded batteries. For example with YouTube testing,
measurement duration is limited to ~four hours.
Nemo Walker II
Number of USB devices exceeded error messages might appear with certain laptops when
more than five test UEs are connected to Nemo Walker II USB hubs. Issue is seen especially
with Lenovo Yoga laptops. It is advised to connect max. four UEs per USB hub. With
computers having both USB 2.0 and USB 3.0 ports, it is advised to connect the first USB
data cable to USB 2.0 port and the second USB data cable to USB 3.0 port. Disabling USB
3.0 from the BIOS is also an alternative with laptops running Windows 8.x OS. Laptops with
Windows 7 OS, uninstalling the Intel USB 3.0 eXtensible Host Controller Driver via add/
remove program can be done. The recommended laptop with Nemo Walker II with up to
eight test handsets is Lenovo T430S.
Samsung Galaxy Note 4 SM-N910G/ F or similar size of handsets cannot be used with the
Nemo Walker II chassis. Chassis has not been designed for big handsets, such as, Note 4.
14.5 Applications and protocols

Dropbox testing
File size is not written to the DREQ event and because of that, the device status does not
show a progress bar for DL or UL transfers
With uplink data transfers the UL data throughput goes up and down. This is normal
behavior as the uploaded files are split to 4MB fragments and uploaded to server with
separate upload commands.
With multi data transfers, e.g. benchmarking Dropbox testing, different local file names
must be used for each test device. In multi-script it means that you can download the same
file with all devices, but you must write it with different names to the local disk
Page 41
PEVQ-S Streaming analysis
Only one active PEVQ-S connection is supported per PC. Only one active PS connection is
allowed while executing PEVQ streaming. When multiple test handsets are connected to the
same PC, a PS connection with only the test handset executing PEVQ-S testing is allowed.
If a test handset has Nemo Media Router application installed, it prevents PEVQ-S testing as
NMR test handsets are always online. In such case, to run multiple PEVQ-S connections
simultaneously, a dedicated PC is required with only one NMR test handset connected to the
PC.
Facebook testing
Facebook limits the number of updates you can post. If you see an error message, it means
the Facebook limit has been reached. It is not a permanent error, so the feed will continue
to work, and once the limit is reset on Facebook end (daily), new posts will be posted again
automatically
When benchmarking Facebook application, it is recommended to run Facebook testing for

each operator on a different UIC module. This way it is possible to use different Facebook
user accounts with different test devices. If benchmarking is done using a commercial laptop,
the same user account settings must be used with all test devices.
VoLTE IR.92 voice/ SMS and IR9.4 calls
CAA event type is written as voice not VoLTE when call is generated via Nemo Outdoor user
interface. This is because at the time of the call attempt, call type is unknown
SIP UL/ DL messages are missing occasionally
With networks using encryption, it is required to perform radio off/ radio on for the VoLTE
test UE and wait ~40 seconds. During this time SIP server registering is shown in the user
interface even if the UE is already registered. After this, measurements can proceed
normally.
With IMS SMS testing its not recommended to use more than 160 characters
PVI video streaming
Video streaming MOS and jitter values are occasionally reported with value zero
PVI video quality parameters are not available with 64 bit operating systems. PVI streaming
without video quality parameters is supported with both 32 and 64 bit operating systems
VLC media player:
Retrieving proper error messages (streaming cause codes) is missing. VLC player version
2.1.0 required with Nemo Outdoor version 7.3.0.6 or higher
USSD testing:
USSD testing is not supported with Huawei UEs
FTP UL data transfers:
Occasionally FTP UL data throughput values can exceed the maximum value supported by
the network. This is seen at the beginning of data transfers. The root cause is that the
operating system can buffer the data
Page 42
VoIP testing:
Other PS data connections are not allowed at the same time with the same computer. Issue
has been reported to the vendor.
Only one VoIP connection per CPU can be done at the moment. Issue reported to the
vendor.
WAP testing. The WAP protocol stack used in Nemo Outdoor supports the following
contents:
Content Type
WMLC, WML 1.1/1.2/1.2.1 text and binary, WMLScript 1.1/1.2/1.2.1 text and binary
Character Sets, WML Char-sets, US ASCII, UTF-8, UCS-2
ISO8859-1 (Latin), ISO8859-2 to 10 (other European), ISO8859-13 to 15 (other

European), SHIFT JIS (Japanese), WSP 1.0 (5 July 2001), WTP 0.0 (10-Jul-2001), WTLS
(06-April-2001)2, WP-HTTS (29-Mar-2001), WAP 2.0 /MMS
Streaming (Catra)
Nemo Outdoor cannot establish streaming with the Nemo Server Catra streaming service.
With Nemo Handy, streaming is working correctly with the included test files.
CDMA SMS end-to-end testing
To be able to calculate end-to-end delivery time, SMS testing must be done using the same
operator between two terminals. This is due to the fact that SMS message ID changes from
operator to operator.
MMS testing
In case of high MMS sending/receiving failures it is recommended to increase the default

time out time from 30 seconds e.g. to 60 seconds.
With Nemo Outdoor 6.3 onwards the required Microsoft Network Monitor version is 3.4.
If IP packet capturing is not required it is highly recommended to uninstall it, as it affects to

the CPU performance.
If data throughput problems are experienced with Windows 7 operating systems and you
are using auto-tuning TCP receive window, please see article
http://blogs.msdn.com/wndp/archive/2007/07/05/receive-window-auto-tuning-onvista.aspx or try to set the auto-tuning level to highlyrestriced." Auto tuning can be
restricted by running netsh interface tcp set global autotuninglevel=restricted from the
command prompt. We have found that the restricted mode will often allow some of the
benefits of auto tuning with a number of problematic devices. Current auto tuning level can
be shown with the command netsh interface tcp show global.
With MMS testing the data transfer status can occasionally show more than 100%.
Page 43
15 TROUBLESHOOTING DEVICE
CONNECTIVITY ISSUES
In general all power saving options should be disabled and high performance power settings should
be used. Battery stretch should not be used and USB port power saving option should be
deselected.
Table 11. Generic USB hub properties
Page 44
16 TROUBLESHOOTING DATA TRANSFER

ISSUES
16.1 PS connection works but no data

If UAC is set to always notify it might cause issues with data testing. PS connection can be
established but data transfer cannot be done. Its recommended to change UAC settings to Never
notify. This can be done via User Account Control Settings. If UAC settings cannot be changed its
highly recommended to start Nemo Outdoor application with administration rights by right clicking
Nemo Outdoor icon and by selecting Run as administrator.
Table 12. UAC settings.
16.2 Antivirus filtering

Disable antivirus application and Windows firewall. If data transfer still does not work, please do the
following:
Activate PS connection (activate PDP context)
Go to Network settings and choose appropriate connection assigned for device. Go to

Connection properties and check that antivirus NDIS filtering is unchecked.
Page 45
Table 13. Network Connections.
Table 14. Antivirus NDIS Filter.
16.3 Low data throughputs

In case lower data throughputs are received with Nemo Outdoor compared to third-party
applications, read this document for troubleshooting throughput problems with various TCP based
protocols. Please note that the following applies to PC based data transfers, not to the data
transfers made by Nemo Media Router application running on the Android based smartphone.
In case low throughput values are monitored with Nemo Outdoor and also with third-party
applications, the issue can most likely be seen by observing link adaptation parameters.
For example, low average CQI and high MAC-HS 3rd retransmission rate indicate an area of bad
coverage or high interference. Low HS-SCCH usage rate (= high HSDPA DTX percentage ratio)
points to capacity, server or transmission problems.
In LTE networks, observe physical resource block allocation (PRB) and signal to noise ratio (SNR).
PRB affects throughput directly. Values less than maximum may indicate other users in the cell, a
bottleneck in the transmission network or not enough data to be sent (application does not need all
the available bandwidth). If data throughputs in LTE are lower than expected, it is recommended to
adjust the buffer size via Nemo Outdoor user interface, for example, to value 1024. It should be
noted that buffer size must be adjusted separately for each protocol (e.g. for FTP and HTTP).
Page 46
Requested throughput much higher than the actual measured throughput may indicate that there
are other users sharing the radio resources of the cell or some other bottleneck in the network that
prevents the mobile from getting the maximum achievable throughput.
High PUSCH TX power values indicate a lack of uplink coverage.
When operating in the dynamic range of link adaptation, average BLER (PDSCH BLER) should be
higher than 0, typically 10-20%, in order to achieve the gain of HARQ retransmission scheme
Residual BLER after all HARQ retransmissions should be 0%. Higher values indicate that the radio
link is about to drop. Observe the MAC downlink/uplink residual BLER (%) values.
Other things that could help troubleshooting:
Disable any firewall and/or antivirus software that could reduce the throughput. Some HSPA
USB interfaces may also install their own software which may affect to window size settings
in registry
Disable IP packet monitoring from the advanced properties
Table 15. IP packet capture settings.
Try another FTP server for comparison
Command prompt FTP throughput. This comparison is recommended because command

prompt FTP does not use any multithreading or other non-standard methods. For better
results, keep Nemo Outdoor at the background measuring the mobile network while making
the transfers. Also try different servers
For Nemo Outdoor 5.60 and older versions: Run a script with simultaneous FTP transfers to
see if the throughput increases. Does not work manually, script is always needed
For Nemo Outdoor 5.70 and later versions: Use the multithread feature of the FTP protocol
to test simultaneous transfers. Works also manually
For Nemo Outdoor 6.30 and later versions: Transmit/receive buffer size should not be
mixed with the TCP receive window size which is the global setting. TCP receive window
size affects the TCP/ IP layer whereas transfer buffer size affects the application layer.
Transfer buffer size can be adjusted per socket. This means that the transfer buffer size can
be adjusted for each test UE separately. Transfer buffer size can be adjusted with the FTP,
SFTP, HTTP, POP3, SMTP, and IMAP protocols
Page 47
When buffer size is not checked from user interface, Nemo Outdoor checks if auto-tuning is
on with Windows 7. If auto-tuning is on, no values are set. Otherwise the static value 64k is
used.
Normally default buffer values are acceptable. But if low data throughputs are still
experienced, increasing the receive/transmit buffer size may increase data throughput.
In uplink direction, transfer buffer size too high can be seen as high data throughput peak
at the beginning of the data session. For example, it is possible that measured data
throughput peak is higher than what the cellular system supports. In this case, decreasing
the transfer buffer size in uplink direction will eliminate high data throughput peaks.
Table 16. Data transfer settings.
Make a comparison test between Nemo Outdoor and the connection manager used with the
device. When configuring a device with Nemo Outdoor, only the trace port should be
defined. The modem port and dial-up connection must be left blank. As ports are left blank
it is not possible to perform a manual PDP context activation or data transfer via Nemo
Outdoor. However, a script file with data connection commands can be used. Script files
should include only data transfer commands, not Attach/detach or PDP context activation or
deactivation commands. Start a data transfer and observe the application data throughput
value. Make the same test again but this time make a connection using Nemo Outdoor.
16.3.1
All Windows versions

How to check the TCP window size from packet logs:
Using Wireshark:
1. Check the .pcap file and look at the (non FTP-DATA) TCP traffic in the middle of the
transfer. Window size value tells the current TCP window size used.
Using Nemo Outdoor:

1. Open a packet grid window in Nemo Outdoor.
2. Look at the TCP traffic in the middle of an FTP transfer with PayloadLen=0:
Page 48
3. Double click the frame to get detailed frame info. Look at the Tcp tree. Window shows the
current value.
Using debug logs (for developers, help desk, etc.):

1. Look for the GetWindowSizeFromRegistry() function.
TCP Window size set to n = Value found from registry.
TCP Window size set to default: n = Value not found from registry. Set to default.
TCP Auto-Tuning detected. Window size not set. = Windows Vista/7 is using auto-tuning TCP
window.
A measurement file (.nmf) does not save window size info. Packet log and/or debug log is always
needed.
16.3.2
Windows 7
Windows 7 does not use static window sizes from the registry. They rely on dynamic window size
which is handled by TCP auto tuning feature. However, if the same registry value that Windows
uses is set, Outdoor reads it and adjusts the manual window size based on this value. In most
cases, the registry has been edited by a third-party software or a USB mobile interface
driver/software. This registry entry can be removed.
If the TCP auto-tuning is disabled Nemo Outdoor will use its default window size 64 KB. Outdoor
5.40 and newer checks the auto-tuning state and does not change any window sizes if auto-tuning
is enabled.
How to check TCP auto-tuning state:
1. Open command prompt by typing CMD to Search programs and files field.
2.
Page 49
Type netsh interface tcp show global
Receive Window Auto-Tuning Level shows the current state.
Please note that administrator rights are required to change auto-tuning settings.
Open command prompt by typing CMD to Search programs and files field. Right-click and select
Run as administrator.
Table 17. Run as administrator.

To disable auto-tuning type netsh interface tcp set global autotuning=disabled. This limits the TCP
window size to 64KB. However, Outdoor sets its own default 256KB when auto-tuning is disabled.
To increase the maximum TCP window size that auto-tuning uses, type netsh interface tcp set
global autotuning=highlyrestricted.
Below are all the values of auto-tuning level with explanations:
disabled: Uses a fixed value for the TCP receive window. Limits to 64 KB (65535).
highlyrestricted: Recommended. Allows the receive window to grow beyond its default
value, very conservatively.
restricted: Recommended. Somewhat restricted growth of the TCP receive window beyond
its default value.
normal: Default value. Allows the receive window to grow to accommodate most conditions.
experimental: Allows the receive window to grow to accommodate extreme scenarios (not
recommended, it can degrade performance in common scenarios, only intended for
research purposes). It enables receive window values of over 16 MB.
Page 50
16.4 Issues with HTTP browsing testing

Selecting Automatic configuration or Proxy settings can cause problems with HTTP browsing
testing, such as, increase the page downloading time. In such a case automatic/ proxy settings
should be disabled.
Table 18. LAN settings.
Page 51
17 REFERENCES
[1] R&S TSME presentation
Page 52
18 NEMO TOOLS
Anite offers a complete product portfolio for all wireless network measuring and analyzing needs on
all major network technologies.
Nemo Outdoor
Nemo Outdoor is a portable engineering tool for measuring and monitoring

the air interface of all major network technologies.
Nemo Invex II
Nemo Invex II is the state-of-the-art 2nd generation benchmarking solution

for testing wireless networks and devices. The system enables testing with up
to 50 test devices simultaneously on all available wireless technologies in one
test drive.
Nemo Invex
Nemo Invex is a chassis-based benchmarking tool for wireless network

measurements.
Nemo Handy-A
Nemo Handy-A is a lightweight, Android smartphone-based air interface

measurement tool wireless networks.
Nemo Walker Air
Nemo Walker Air is a portable tool for indoor measurements and

benchmarking. Nemo Walker Air enables conducting multi-technology
measurements on the air interface of wireless networks.
Nemo IBC Meter
Nemo In-Building Coverage Meter (IBC Meter) is a fast and easy to use
Android application for instantly testing indoor coverage and performance.
Measurement data can be uploaded to central server or emailed to a
customer as a report.
Nemo CEM Observer
Nemo CEM Observer is an in-depth troubleshooting solution for real-time

mobile service monitoring from the customers perspective. It is the first step
towards bringing drive test level diagnostics data into the CEM domain, thus
enabling the root cause analysis of user experience problems.
Nemo CEM Solution
Nemo CEM solution is a powerful, flexible, and scalable set of tools for
monitoring wireless network performance and services from the end user
point of view.
Nemo Autonomous Nemo Autonomous is the first practical lightweight solution for performing
fully automated large-scale measurements on the air interface of all major
network technologies. Nemo Autonomous streamlines your network
measurement, troubleshooting, statistical reporting, and benchmarking
processes, maximizes your awareness of what is happening in the network,
and makes achieving all this considerably easier and more cost efficient.
Nemo Commander Nemo Commander is a platform for centrally controlled network testing. It
allows network operators to remotely operate Nemo Outdoor, Nemo Invex
and Nemo Handy-A test units and check their status. Nemo Commander
supports all devices and test protocols currently supported with Nemo tools,
including scanners.
Page 53
Nemo FSR1
Nemo FSR1 is a revolutionary, modular digital scanning receiver that provides

accurate, reliable high-speed RF measurements of wireless networks across
multiple bands and technologies.
FOR ANALYSIS AND REPORTING

Nemo Analyze
Nemo Analyze is a powerful and versatile, cutting-edge analysis tool for

performing benchmarking, troubleshooting, and statistical reporting based on
drive test data. The system incorporates an innovative, low-maintenance
database engine that has been designed and optimized specifically for highperformance post-processing of drive test data.
Nemo WindCatcher
Nemo WindCatcher is the industry leading desktop-based drive test data

post-processing tool for radio access network analysis used by design
engineers, performance engineers, handset testing groups, and technology
development groups.
Nemo Xynergy
Nemo Xynergy is a powerful, scalable, and easy-to-use web-based platform

for analyzing drive test, OSS, and subscriber data. It automates key tasks in
the entire network management life cycle and supports multiple, disparate
data sources and vendors for all major network technologies.
Page 54
www.anite.com/nemo
CONTACT DETAILS
talk +358 50 395 7700

read anite.com/nemo
write nemo.sales@anite.com
2015

RN Nemo Outdoor 7 6 0 7 30th June 2015

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RN Nemo Outdoor 7 6 0 7 30th June 2015

Загружено:

Авторское право:

Доступные форматы

WWW.ANITE.

NEMO OUTDOOR 7.6.0 RELEASE

NEMO OUTDOOR 7.6.0 TECHNICAL BULLETIN AND RELEASE NOTES

NEMO OUTDOOR 7.6.0 TECHNICAL BULLETIN AND RELEASE NOTES

1 NEW FEATURES ................................................................................................. 5

LTE-A 3 component carrier aggregation ........................................................ 5

Small cell and DAS indoor measurement enhancements .................................. 7

Small cell and distributed antenna system types .................................... 7

DAS anomaly analysis in indoor view .................................................... 7

Real-time RF ingress analysis calculation ............................................... 9

Area zones with iBwave importing ...................................................... 11

Measurement filename parameter based on iBwave floorplan identifier ... 11

Nemo Media Router .................................................................................. 12

New features in Nemo Media Router version 2.30 ................................. 13

Nemo Media Router licensing options .................................................. 15

Compatibility and update process ....................................................... 15

Supported handsets with Nemo Media Router ...................................... 16

Generic handler enhancements .................................................................. 17

Support for GSM WFS AMR codec ....................................................... 17

Qualcomm handler enhancements .............................................................. 18

Support for new messages with Qualcomm diagnostics logging .............. 18

Other enhancements ........................................................................ 18

HiSilicon handler enhancements ................................................................. 18

Forcing to barred PCI ........................................................................ 19

GSM and UMTS band lock .................................................................. 19

2 APPLICATIONS AND PROTOCOLS ....................................................................... 20

Dropbox testing ....................................................................................... 20

Support for TCP connection establishment time............................................ 21

3 OTHER FEATURES & UPDATES ........................................................................... 22

Generic scanner handler enhancements ...................................................... 22

Nemo FSR1 scanner handler enhancements ................................................ 22

PCTel scanner handler enhancements ......................................................... 23

Rohde & Schwarz scanner handler enhancements ........................................ 23

Vicom interface ................................................................................ 23

TSME MIMO scanning........................................................................ 23

Nemo Invex new features ......................................................................... 25

4 USER INTERFACE ............................................................................................. 26

NEMO OUTDOOR 7.6.0 TECHNICAL BULLETIN AND RELEASE NOTES

Measurement file uploading directly to Nemo Xynergy .................................. 26

Other UI enhancements ............................................................................ 26

5 ERROR CORRECTIONS ...................................................................................... 28

Handsets and USB modems ....................................................................... 29

Scanner receivers .................................................................................... 30

7 QUALCOMM-BASED WCDMA AND CDMA2000 TERMINALS AND DATA CARDS ........... 31

NEMO OUTDOOR 7.6.0 TECHNICAL BULLETIN AND RELEASE NOTES

LTE-A 3 Component Carrier Aggregation

Small cell and DAS indoor measurement enhancements

Dropbox testing (PC-based)

TD-SCDMA support with Nemo FSR1 scanner receiver

R&S TSME MIMO measurements

Qualcomm handler enhancements

HiSilicon handler enhancements

Measurement file uploading to Nemo Xynergy

1.1 LTE-A 3 component carrier aggregation

NEMO OUTDOOR 7.6.0 TECHNICAL BULLETIN AND RELEASE NOTES

Qualcomm LTE FDD

Log everything except Secondary

Qualcomm LTE-A CA 2CC Cat.4

Log everything including

Qualcomm LTE-A CA 2CC Cat.4

Log everything except Secondary

Qualcomm LTE-A CA 2CC Cat.6

Log everything including