RN Nemo Outdoor 7.4.1.13 27th November 2014

WWW.ANITE.COM/NEMO

NEMO OUTDOOR 7.41 MAINTENANCE

RELEASE

TECHNICAL BULLETIN & RELEASE NOTES

NEMO OUTDOOR 7.41 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.

Anite’s products are subject to continual development and specifications may change. Users of

Anite’s products and documentation should exercise their own independent judgement to evaluate

the suitability of Anite’s 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.


CONTENTS

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

1.1 Nemo Media Router Version 2.11 ................................................................. 5

1.1.1 New NMR Handsets ............................................................................ 5

1.1.2 Nemo Media Router Licensing Options ................................................... 6

1.1.3 Compatibility and Update Process ......................................................... 6

1.2 Nemo Commander Enhancements ................................................................ 6

1.2.1 Manual Remote Measurement Session .................................................. 6

1.3 Qualcomm Handler Enhancements ............................................................... 6

1.4 HiSilicon Handler Enhancements .................................................................. 7

1.5 Broadcom Handler Enhancements ................................................................ 7

1.5.1 Cell ID Logging during Cell-DCH UMTS RRC State ................................... 7

1.6 Nemo FSR1 Scanner Handler Enhancements .................................................. 7

1.7 PCTel Scanner Handler Enhancements .......................................................... 7

1.7.1 PCTel IBflex Scanner .......................................................................... 7

1.7.2 PCTel EXflex Scanner .......................................................................... 7

1.8 Rohde & Schwarz Scanner Handler Enhancements ......................................... 7

2 NEW DEVICES ................................................................................................... 8

2.1 Handsets and USB Modems ......................................................................... 8

2.2 Scanners ................................................................................................... 9

2.3 Supported Handsets with Nemo Media Router ................................................ 9

3 QUALCOMM-BASED WCDMA AND CDMA2000 TERMINALS AND DATA CARDS ........... 11

4 COMPUTER HARDWARE AND SOFTWARE REQUIREMENTS ..................................... 12

5 DEVICE CONFIGURATION AND WORKSPACE FILES ............................................... 13

6 INSTALLATION ................................................................................................ 14

6.1 Supported Operating Systems ................................................................... 14

6.2 First-time Installation ............................................................................... 14

6.3 Update/Upgrade ....................................................................................... 15

6.4 Uninstallation .......................................................................................... 15

6.5 HASP Dongle Runtime Drivers .................................................................... 15

7 LIMITATIONS WITH WINDOWS 8 OPERATING SYSTEM ......................................... 16

8 LIMITATIONS AND ISSUES WITH WINDOWS 7 OPERATING SYSTEM ....................... 17

9 FILE FORMAT CHANGES .................................................................................... 18

10 KNOWN ISSUES ............................................................................................... 19


10.1 General and User Interface ........................................................................ 19

10.2 Nemo Commander ................................................................................... 20

10.3 Applications and Protocols ......................................................................... 20

11 TROUBLESHOOTING DEVICE CONNECTIVITY ISSUES ........................................... 22

12 TROUBLESHOOTING DATA TRANSFER ISSUES ..................................................... 23

12.1 PS Connection Works but No Data .............................................................. 23

12.1.1 Antivirus Filtering ............................................................................. 23

12.2 Low Data Throughputs .............................................................................. 24

12.2.1 All Windows Versions ........................................................................ 26

12.2.2 Windows Windows7 .......................................................................... 27

12.3 Issues with HTTP Browsing Testing ............................................................. 28

13 NEMO TOOLS................................................................................................... 30


1 NEW FEATURES

Nemo Outdoor 7.4.1 release includes support for the following new features and error corrections:

Nemo Media Router Version 2.11

Nemo Commander Enhancements

Qualcomm Handler Enhancements

HiSilicon Handler Enhancements

Broadcom Handler Enhancements

PcTel Scanner Handler Enhancements

New Devices

1.1 Nemo Media Router Version 2.11

No new features in the release.

1.1.1 New NMR Handsets

The handsets shown in the table below are supported with Nemo Media Router:

Product Code

Handset Firmware NMR version

Nemo Outdoor version (*)

MH1700-39

Samsung Galaxy Note 4

SM-N910F

MPSS.BO.1.0.r10-00108-M9635TAARANAZM-1.5514.1 (TAARANAZ Sep 16 2014 20:04:39)

2.11.060 7.4.1.13

MH1700-40


SM-N910G

MPSS.BO.1.1.r10-00108-M9635TAARANAZM-1.5514.1 (TAARANAZ Oct 4 2014 16:47:00)

2.11.060 7.4.1.13

MH1700-41

Samsung Galaxy S5

SM-G900T1

(Metro PCS)

MPSS.DI.2.0.1.c2-00055-M8974AAAAANRZM-1

(AAAAANRZ May 23 2014 19:27:09)

2.11.060 7.4.1.13

MH1700-42

Samsung Galaxy S5

SM-G900R4

(US Cellular)

MPSS.DI.2.0.1.c2.2-00006-M8974AAAAANRZM-1 (AAAAANRZ Mar 31 2014 01:04:01)

2.11.060 7.4.1.13

Table 1. New NMR handsets.


Standard data cable (OD0100-08) Hama micro USB 2.0 USB A to micro B cable must be used with

the test handsets.

1.1.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.10 or

higher:

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 protocols. Client running on the smartphone (optional license)

Table 2. NMR license options.

1.1.3 Compatibility and Update Process

Nemo Media Router version 2.10 is compatible with Nemo Outdoor 7.4.0.9. 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 update instructions are available from the Nemo User Club http://nemouserclub.anite.com. File

NemoMediaRouter.apk is located under Nemo Outdoor 7.4.0.9

NMR Data & Application Testing Option including Ping and HTTPS/ HTTPS protocols can be fetched

from NMR license server automatically for all currently fielded units purchased with the NMR data &

application option. This can be done by launching the Nemo Media Router 2.10 application on the

phone after installation.

1.2 Nemo Commander Enhancements

All new features require Nemo Commander version 7.20 or higher.

1.2.1 Manual Remote Measurement Session

User can start and stop manual sessions during a measurement session period.

1.3 Qualcomm Handler Enhancements

Please see the readme.html located in the installation folder of Nemo Outdoor for a list of error

corrections.


1.4 HiSilicon Handler Enhancements

Please see the readme.html located in the installation folder of Nemo Outdoor for a list of error

corrections.

1.5 Broadcom Handler Enhancements

1.5.1 Cell ID Logging during Cell-DCH UMTS RRC State

Cell ID and LAC are reported during the UMTS Cell-DCH RRC state. During the Cell-DCH state, the

UE reads and reports the new Cell ID when the cell with the current Cell ID is removed from the

active set. Please see the readme.html located in the installation folder of Nemo Outdoor for a list of

error corrections.

1.6 Nemo FSR1 Scanner Handler Enhancements

No changes.

1.7 PCTel Scanner Handler Enhancements

1.7.1 PCTel IBflex Scanner

The following systems and bands have been added:

LTE TDD E-UTRA bands: 38 (2570-2620MHz), 39 (1880-1920 MHz), 40 (2300-2400MHz),

41 (2496-2592.90MHz), 42 (3400 – 3600MHz) and 43 (3600 – 3800MHz). NOTE! E-UTRA

band 41 is the lower half (2496.00 – 2592.90 MHz).

1.7.2 PCTel EXflex Scanner

The following systems and bands have been added:

LTE TDD E-UTRA bands: 42 (3400 – 3600MHz) and 43 (3600 – 3800MHz).

1.8 Rohde & Schwarz Scanner Handler Enhancements

No changes.


2 NEW DEVICES

For a complete list of supported devices, please see the separate document Nemo Outdoor 7.4.1.13

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!

2.1 Handsets and USB Modems

Product Code

Handset Dev. Capability Handler # Verified UEs/ CPU

FW version Driver

MH1700-39


SM-N910F

LTE FDD700/800/850/900/1800/1900/2100/AWS/2600 (E-UTRA bands 17, 20, 5, 8, 3, 2, 1, 4, 7)

WCDMA 850/900/1900/ 2100

Quad band GSM

HSPA 42.2/5.76

LTE Cat 6

Qualcomm LTE-A FDD

Cat6

1 MPSS.BO.1.0.r10-00108-M9635TAARANAZM-1.5514.1 (TAARANAZ Sep 16 2014 20:04:39)

Samsung_USB_Driver_for_Mobile_Phones_1_5_45_0

MH1700-40


SM-N910G

LTE FDD700/850/900/1800/1900/ 2100/AWS/2600 TDD 2300/2600 (E-UTRA bands 28, 5, 8, 3, 2, 1, 4, 7, 40, 38)

WCDMA 850/900/1900/ 2100

Quad band GSM

HSPA 42.2/5.76

LTE Cat 6

Qualcomm LTE-A FDD Cat6

1 MPSS.BO.1.1.r10-00108-M9635TAARANAZM-1.5514.1 (TAARANAZ Oct 4 2014 16:47:00)


MH1700-41

Samsung Galaxy S5 SM-G900T1

(Metro PCS)

FDD 700/850/900/ 1800/1900/AWS/ 2100/2600 (E-UTRA bands 17, 5, 8, 3, 2, 4, 1, 7)

WCDMA 850/1900/AWS/ 2100

GSM 850/900/1800/1900

HSPA 42.2/5.76

LTE Cat 4

Qualcomm LTE FDD

1 MPSS.DI.2.0.1.c2-00055-M8974AAAAANRZM-1 (AAAAANRZ May 23 2014 19:27:09)


MH1700-42

Samsung Galaxy S5 SM-G900R4

(US Cellular)

FDD 700/850/1900 /AWS (E-UTRA bands 12, 17, 5, 2, 4)

CDMA/ EVDO 800/ 1900 (Band classes 0, 1)

LTE UE Cat 4 (150/ 51Mbps), EVDO Rev.A

Qualcomm LTE FDD/ EVDO Rev. A

1 MPSS.DI.2.0.1.c2.2-00006-M8974AAAAANRZM-1 (AAAAANRZ Mar 31 2014 01:04:01)



Product

Code

Handset Dev. Capability Handler # Verified

UEs/ CPU

FW version Driver

(3.1Mbps)

MH1700-43

Samsung Galaxy S5

SM-G9009W

(China Telecom)

LTE FDD 1800/ TDD 2600

WCDMA 850/ 1900/ 2100

CDMA 800

Quadband GSM

Qualcomm LTE FDD/ TDD/ EVDO Rev. A

1 MPSS.DI.3.0.c6-00088-M8974AAAAANAZM-1 (AAAAANAZ Aug 29 2014 17:32:07)


MH1700-44

Samsung Galaxy S5

SM-G9008V

(China Mobile)

LTE FDD 1800/2600

LTE TDD 1900/2300/2500/2600

(E-UTRA bands 3, 7, 39, 40, 41, 40)

LTE UE Cat 4

WCDMA 850/900/1900/2100

HSDPA UE Cat 24, HSUPA UE Cat 6

GSM 850/900/1800/1900

GPRS/EDGE Multislot class 12/12

Qualcomm LTE FDD/ TDD

1 MPSS.DI.2.0.1.c2-00064-M8974AAAAANRZM-1 (AAAAANRZ Sep 24 2014 11:38:24)


Table 3. New supported UEs.

2.2 Scanners

No new devices.

2.3 Supported Handsets with Nemo Media Router

The handsets shown in the table below are supported with the Nemo Media Router application.

Product Code

Handset Firmware NMR version Nemo Outdoor version (*)

MH1700-39 Samsung Galaxy Note 4

SM-N910F

MPSS.BO.1.0.r10-00108-M9635TAARANAZM-1.5514.1 (TAARANAZ Sep 16 2014 20:04:39)

2.11.060 7.4.1.13

MH1700-40 Samsung Galaxy Note 4

SM-N910G

MPSS.BO.1.1.r10-00108-M9635TAARANAZM-1.5514.1 (TAARANAZ Oct 4 2014 16:47:00)

2.11.060 7.4.1.13

MH1700-41 Samsung Galaxy S5

SM-G900T1

(Metro PCS)

MPSS.DI.2.0.1.c2-00055-M8974AAAAANRZM-1 (AAAAANRZ May 23 2014 19:27:09)

2.11.060 7.4.1.13


SM-G900R4

(US Cellular)

MPSS.DI.2.0.1.c2.2-00006-M8974AAAAANRZM-1 (AAAAANRZ Mar 31 2014

2.11.060 7.4.1.13


Product

Code

Handset Firmware NMR version Nemo Outdoor

version (*)

01:04:01)

MH1700-35 Samsung Galaxy S5 4G+ SM-G901F

MPSS.BO.1.0.c1-00091-M9635TAARANAZM-1 (TAARANAZ Aug 11 2014 11:59:20)

2.10.054 7.4.0.9

MH1700-26 Samsung Galaxy S5 SM-G900I

MPSS.DI.2.0.1.c2.2-00006-M8974AAAAANRZM-1 (AAAAANRZ Mar 29 2014 15:46:27). Android 4.2

2.01.042 7.3.1.9

MH1700-25 Samsung Galaxy S5 SM-G900F

MPSS.DI.2.0.1.c2.2-00006-M8974AAAAANRZM-1 (AAAAANRZ Mar 29 2014 15:46:27). Android 4.2

2.01.041 7.3.1.9

MH1700-29 Samsung Galaxy S5 SM-G900T (T-Mobile)

M9615ACEHWMAZD1795 (ACEFWMAZ Aug 17 2012 20:29:27)

2.01.041 7.3.1.9

MH1700-30 Samsung Galaxy S5 SM-G900P (Sprint)

M8930B-AAAATAZM-5.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-AAAATAZM-5.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

2.00.034

7.1.0.6

7.3.0.6


(GT-i9505)

M9615A-CEFWTAZM-

4.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-AAAATAZM-3.2.27040 (BBAAATAZ Jul 15 2013 11:32:02)

1.10.015

2.00.034

7.2.0.6

7.3.0.6

MH1700-10 Samsung Galaxy S4+ (GT-i9506)

M8974A-AAAANAZM-1.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-AAAATBZM-6.0.01049 (BBAAATBZ Nov 4 2013 20:22:08)

2.00.034 7.3.0.6

Table 4. 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.


3 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.4.0.9 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.


4 COMPUTER HARDWARE AND SOFTWARE REQUIREMENTS

PC (Lenovo or Dell recommended) with Windows 7 ® Professional (32/ 64- bit) or Windows

8 ® Professional (32/ 64- bit). Windows 7 ® Professional is highly recommended

Pentium III processor, minimum 1GHz, preferably 1.7 GHz for single mobile measurements

For multi data measurements Intel® Core Duo processor T2500 2.00GHz or higher

required. Intel® Core™ i7 recommended

For voice quality measurements with up to four channels with USB sound card Intel® Core

Duo processor T2500 2.00GHz or higher required. Intel® Core™ i7 recommended

For up to six channel voice quality measurements with USB sound card Intel® Quad Core

processor Q9100 2.26GHz or higher required. Intel® Core™ i7 recommended

512MB RAM minimum, 1GB RAM recommended

For multi data measurements with HSPA+ devices Intel® Quad Core processor Q9100

2.26GHz or higher required. Intel® Core™ i7 recommended

100 MB of free hard disk space for installation and use; 1 GB 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 serial port for each voice quality audio module or one USB port per sound card

One USB port for an external GPS receiver

Display resolution 1400 x 900 recommended


5 DEVICE CONFIGURATION AND WORKSPACE FILES

Device configuration and workspace files made by Nemo Outdoor 7.3.x are fully compatible with

Nemo Outdoor 7.4.1.


6 INSTALLATION

6.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.

6.2 First-time Installation

Note that the installation must be run under Administrator account or other user

account with administrative privileges.

If IP packet capturing is needed for 64-bit Windows, you need to install an

additional setup of Nemo Packet Monitor x64 7.x.x.exe (Nemo Outdoor and

Nemo Packet Monitor must be of the same version) found in the Nemo Outdoor

product package. Double-click the file and follow the steps in the installation

wizard to finish the installation. Microsoft Network Monitor installation package

is also required. For further information see the Nemo Outdoor User Manual

chapter “IP Packet Capturing”.

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. With Nemo Outdoor 6.30 onwards copy protection module is not needed

during installation.


6.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.3.1.x installation can be ran. During Sentinel HASP

driver installation, you are prompted to restart the computer. Press “Restart

later” to continue with the Nemo Outdoor 7.3.1 installation.

If IP packet capturing is needed for 64-bit Windows, you need to install an

additional setup of Nemo Packet Monitor x64 7.x.x.exe (Nemo Outdoor and

Nemo Packet Monitor must be of the same version) found in the Nemo Outdoor

product package. Double-click the file and follow the steps in the installation

wizard to finish the installation. Microsoft Network Monitor installation package

is also required. For further information see the Nemo Outdoor User Manual

chapter “IP Packet Capturing”.

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.

6.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.

6.5 HASP Dongle Runtime Drivers

Note that the Nemo Outdoor setup includes the required HASP dongle runtime

driver compatible with the application. The driver should not be updated, for

example, with Windows update or using a separate driver setup downloaded

from the internet. It is recommended not to install any other applications using

the HASP dongle runtime driver as different versions can conflict. In case the

HASP dongle runtime driver is updated and it conflicts with Nemo Outdoor, an

uninstallation of the current driver should be done via “Uninstall or change

program”. Locate the application called “Sentinel HASP Run- Time” and uninstall

it. Re-install Nemo Outdoor application.


7 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

Driver/ Notes

Huawei E392/ E398

2 Driver version: 23.003.07.00.03

Nokia C7-00 2 Driver version: 7.1.101.0

Nokia 500 2 Driver version: 7.1.101.0

Nokia Lumia 920

(RM-821)

1 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 GT-i9305

4 Driver version: Kies version 2.3.3.12085_7, driver version 1.5.18.0

Sierra 320U

1 Driver version: 6.0.3507.0004

PcTel MX 1 MX winusb

PcTel EX 1 2.1.1.0

Terratec DMX 6Fire sound card is not compatible with Windows 8 operating system at the time of

release.


8 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. It’s recommended to change UAC

settings to “Never notify”. This can be done via User Account Control Settings

Figure 1. UAC settings.


9 FILE FORMAT CHANGES

Nemo Outdoor 7.4.1 supports Nemo file format version 2.21.


10 KNOWN ISSUES

Test device related known issues for UEs, scanners, and other devices are listed in a separate

document: (Nemo_Outdoor_7.4.1.13_Test_Device_Technical_Notes_Nov_2014.pdf).

10.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

Figure 2. Lenovo active protection system properties.

Running Nemo Outdoor setup directly from the USB flash memory won’t 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

http://support.microsoft.com/kb/925681

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=925681&kbln=en-us


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 it’s recommended to not install Microsoft Network Monitor.

Line graph zooming with mouse wheel does not work occasionally

10.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”

10.3 Applications and Protocols

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

VoLTE 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 messages are missing occasionally

SIP DL message content is not available. Only message name is shown

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 and Samsung 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

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-on-vista.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%.

http://blogs.msdn.com/wndp/archive/2007/07/05/receive-window-auto-tuning-on-vista.aspx


11 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.

Figure 3. Generic USB hub properties


12 TROUBLESHOOTING DATA TRANSFER ISSUES

12.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. It’s recommended to change UAC settings to “Never

notify”. This can be done via User Account Control Settings. If UAC settings cannot be changed it’s

highly recommended to start Nemo Outdoor application with administration rights by right clicking

Nemo Outdoor icon and by selecting “Run as administrator”.

Figure 4. UAC settings.

12.1.1 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.


Figure 5. Network Connections.

Figure 6. Antivirus NDIS Filter.

12.2 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).


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

Figure 7. 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


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.

Figure 8. 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.

12.2.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:


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.

12.2.2 Windows Windows7

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. 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.

Figure 9. 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.

12.3 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.


Figure 10. LAN settings.


13 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 customer’s 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.


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 high-

performance 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.

RN Nemo Outdoor 7.4.1.13 27th November 2014

Documents

Transcript of RN Nemo Outdoor 7.4.1.13 27th November 2014