Nemo - Outdoor - Release Note

er’s Manual
Technical Bulletin
and Release Notes
Keysight
Nemo
Insert the
Outdoor 8.3.0
Title in this
Release
Space
Table of Contents
Introduction ................................................................................................................................... 3
Copyright ............................................................................................................................... 3
New Features ............................................................................................................................... 4
Nemo Media Router ...................................................................................................................... 5
New features ............................................................................................................................. 5
Enhanced video and audio quality measurements ................................................................. 5
New NMR devices ................................................................................................................. 6
Voice quality support with Exynos based devices .................................................................. 6
Viber testing ........................................................................................................................... 6
Miscellanous ........................................................................................................................ 10
Error corrections ...................................................................................................................... 10
Nemo Media Router licensing options ..................................................................................... 11
Compatibility and update process ............................................................................................ 12
Supported handsets with Nemo Media Router......................................................................... 13
New Devices ............................................................................................................................... 23
Qualcomm-based WCDMA and CDMA2000 Terminals and Data Cards ..................................... 25
Nemo Cloud ................................................................................................................................ 26
Configuration support for PCTEL scanners ............................................................................. 26
Miscellanous............................................................................................................................ 26
Nemo Navigation Assistant...................................................................................................... 26
Qualcomm Software Handler Updates ........................................................................................ 27
New component carrier and MIMO metrics .............................................................................. 27
New bands and other additions ............................................................................................... 28
Samsung Shannon Software Handler Updates ........................................................................... 29
New component carrier and MIMO metrics .............................................................................. 29
LAA support ............................................................................................................................ 29
Neul Software Handler Updates .................................................................................................. 30
Generic Scanner Handler Updates.............................................................................................. 32
Keysight Spectrum Analyzers and Scanning Receivers ........................................................... 32
PCTEL Scanner Handler Updates ........................................................................................... 32
PCTEL IBflex Lite................................................................................................................. 32
PCTEL IBflex and IBflex Lite ................................................................................................ 32
Rohde & Schwarz Scanner Handler updates ........................................................................... 33
QoS & QoE Testing .................................................................................................................... 34
User Interface Updates ............................................................................................................... 35
Nemo File Format ....................................................................................................................... 39
Discontinued Products ................................................................................................................ 39
Discontinued Chipsets and Test Device Handler Software Options ......................................... 39
Discontinued Software License Options .................................................................................. 40
Discontinued Commercial Software Packages and Handler Software Options ........................ 40
Computer Hardware and Software Requirements ....................................................................... 41
Device Configuration and Workspace Files ................................................................................. 42
Nemo Outdoor accessories and verified configurations ........................................................... 42
Installation................................................................................................................................... 42
First-time installation................................................................................................................ 42
Update/Upgrade ...................................................................................................................... 43
Uninstallation ........................................................................................................................... 43
Dongle runtime drivers ............................................................................................................ 43
Limitations and Issues with Windows 7 Operating System .......................................................... 43
Known Issues ............................................................................................................................. 44
General and user interface ...................................................................................................... 44
Nemo Analyze ......................................................................................................................... 45
Nemo Cloud ............................................................................................................................ 45
Nemo Media Router ................................................................................................................ 45
Nemo Media Router for Android ........................................................................................... 45
Nemo Media Router for iOS ................................................................................................. 48
Nemo Backpack and Nemo Carrying Case ............................................................................. 48
Nemo Multi Lite and Nemo Walker II ....................................................................................... 49
Applications and protocols ....................................................................................................... 50
Troubleshooting Device Connectivity Issues ............................................................................... 52
Troubleshooting Data Transfer Issues ........................................................................................ 52
PS connection works but no data ............................................................................................ 52
Antivirus filtering ...................................................................................................................... 53
Low data throughputs .............................................................................................................. 53
All Windows versions ........................................................................................................... 55
Windows 7 ........................................................................................................................... 56
Issues with HTTP browsing testing .......................................................................................... 58
Low data throughput with Nemo Media Router application ...................................................... 58
Introduction
This document contains the release notes of Nemo Outdoor version 8.3.0, released July 2018. The document
describes new functionalities and features.
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 Keysight Technologies, Inc. Additionally, this document is not to be passed
to or discussed with third parties without the prior written permission of Keysight.
Keysight’s products are subject to continual development and specifications may change. Users of Keysight’s
products and documentation should exercise their own independent judgement to evaluate the suitability of
Keysight’s products and documentation for their particular use. Keysight 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 Keysight products, services or equipment, please contact us through the
Keysight Website.
July 2018
New Features
Nemo Outdoor 8.3.0 release includes the following new main features:
• Enhanced video and audio quality measurements

• New KPIs for LTE-A CA and MIMO
• Nemo Cloud:
o Configuration support for PCTEL scanners
• Nemo Media Router application
o Voice quality support with Exynos based Samsung Galaxy S9 devices
o Viber testing
• New devices:
o Samsung Galaxy S9+ SM-G965F
o Sony Xperia XZ2 H8266
o PCTEL IBflex Lite
o Lierda NB86G LSD4NBT0611-02D0
• New script command
• Nemo File Format 2.36
Nemo Media Router
New features
Enhanced video and audio quality measurements
The new implementation of Telchemy's industry-leading VQmon® performance analysis technology is now
running on both Android and Windows based platforms simultaneously. Switching between platforms is done
seamlessly depending on technology and test UE capabilities in different systems. The new method expands the
number of test handsets to be used for IP audio and IP video quality testing using Qualcomm and Exynos based
devices. It also provides quality metrics during transition between systems e.g. from VoLTE to VoWiFi.
VQMon® obtains quality metrics and analytics for both voice and video calls. It provides accurate QoE scores
and critical diagnostics for every VoIP call and mobile video session. It incorporates support for key
international standards including ITU-T P.564, ITU-T G.107, ITU-T G.1020, ETSI TS 101 329-5 Annex E and IETF
RFC 3611. VQmon is a "no-reference" algorithm that does not use the original reference signal.
Users do not need to configure any settings from Nemo Outdoor measurement properties except select the
audio file. Quality metrics are automatically reported for voice IP and video IP calls. Please note that certain
limitations apply depending on handset model, type and physical location. For example, handsets inside Nemo
Invex II HI modules or other enclosures cannot be used for video quality monitoring.
Requires license NTA50058A, “Nemo Media Router IMS audio and video call quality software option”. One
license per test device is required. Requires Nemo Media Router version 8.30 or higher.
Figure 1. Audio and video quality metrics during call transition from Wi-Fi -> LTE-> Wi-Fi.
Device VoLTE ViLTE ViLTE VoWi-FI ViWi-FI ViW-iFI
Audio Audio Video Audio Audio Video
MOS MOS MOS MOS MOS MOS
Samsung Galaxy √ √
S9 SM-G960F
Sony Xperia XZ √ √ √
Premium G8141
Sony Xperia XZ2 √

H8266
Samsung Galaxy √ √ √ √ √ √
S9 SM-G960U
(TMOB)
Table 1. Supported devices and verified quality metrics with different systems.
New NMR devices
• Samsung Galaxy S9+ SM-G965F

• Sony Xperia XZ2 H8266
Voice quality support with Exynos based devices
Voice quality support with Exynos based Samsung Galaxy S9 devices. The following devices has been verified
with UMTS and VoLTE:
• Samsung Galaxy S9 SM-G960F

• Samsung Galaxy S9+ SM-G965F
NOTE! While serving system is GSM audio MOS values are not valid. Headset/ headphones must not be
connected to device.
Viber testing
Viber testing support allows users to test the functionality of the application from the end-user perspective and
to benchmark the performance with other operators. Both manual and fully automated testing with script files
are supported. Supported Viber operations, trigger points and KPIs are Keysight Network Testing proprietary.
Parallel Viber and data testing are also supported. The initial version supports the following Viber operations:
• Messages
o Send message to selected contact
o Send image to selected contact
• Voice calls
o Make call / receive call
Viber connection and status events
Viber Voice Call Attempt

MO Call Attempt, originated call (CAA)
Definition Recorded when Viber application test begin and user press make voice call button in Viber
application.
Condition Viber application running
Trigger Point User initiates the Viber voice call.
MT Call Attempt, terminated call (CAA)

Definition Recorded when Viber application test begin and incoming call is received
Condition Viber application running
Trigger Point Call status is changed to ringing
Viber Voice Call Connected (Ringing)

MO / MT Call Connected (CAC1 and CAC2)
Definition Recorded when Viber voice call is ringing. Both CAC 1 and CAC 2 events are
written.
Condition MO call: User have initiated the Viber voice call. MT call: Incoming call is received
Trigger Point Viber voice call status changed to ringing.
Viber Voice Call Connected (Answered)

MO / MT Call Connected (CAC3)
Definition Recorded when Viber voice call is answered
Condition Viber voice call status is ringing.
Trigger Point Viber voice call status changed to answered.
Viber Voice Call Disconnected

Normal Call Disconnect (CAD1)
Definition Recorded when Viber voice call is ended by A- party. NOTE! Call should be ended always
by A- party. In case B- party ends the call or call ends for some other reason it’s counted
as a drop call.
Condition Viber voice call status is answered.
Trigger Point Viber voice call ended by A- party

Call Disconnect, User busy (CAD14)
Definition Recorded when B- party is busy
Condition Viber voice call status changed to ringing and user is busy.
Trigger Point B- party is rejecting incoming call.

Call Disconnect, Drop call (CAD2)
Definition Recorded when voice call drops
Condition Viber voice call status changed to answered and call is not ended by A- party. NOTE! Call
should be ended always by A- party. In case B- party ends the call or call ends for some
other reason it’s counted as a drop call.
Trigger Point Call is not ended by A- party
Viber Voice Call Failed
MO / MT Call Attempt Failure (CAF1)
Definition Timeout before connection
Condition User have initiated the Viber voice call.
Trigger Point Viber voice call status is not changed to ringing and timeout is exceeded.

MO / MT Call Attempt Failure (CAF5)
Definition Test system failure
Condition User have initiated the Viber voice call
Trigger Points Viber not installed or registered
No contact found in Viber contact list
Viber application is closed before call alerting state

MT Call Attempt Failure (CAF13)
Definition Incoming call not received
Condition Viber voice call status is ringing
Trigger Points Viber voice call status is not changed to answered and timeout is exceeded.
Viber Message Data Attempt

Data attempt (DAA)
Definition Viber starts
Condition Viber application starts
Trigger Points Viber application begin
Viber Message Data Connection Success / Request

Data connection success (DAC) and data connection request (DREQ)
Definition Viber application starts
Condition Viber application registered
Trigger Points Send message button is pressed. Both DAC and DREQ events are written.
Viber Message Data Connection Failed

Data connection failed (DAF 3)
Definition Viber message sending fails. Protocol error or timeout.
Condition Viber test begin
Trigger Points Viber not installed or registered
No contact found in Viber contact list
Viber disappears before message/image is sent
Send button not pressed before exceeding timeout
Viber Message Data Complete Success

Data completed (DCOMP 1) and Data disconnect (DAD 1)
Definition Viber message sent successfully
Condition Send button is pressed
Trigger Points Message state is sent. Both DCOMP and DAD events are written.
Viber Message Data Complete Failed

Data completed (DCOMP 3) and Data disconnect (DAD 3)
Definition Viber message sending fails. Protocol error or timeout.
Condition Send button is pressed
Trigger Points Viber application disappears before send button is pressed or send cannot be executed.
Message status is pending and timeout time is exceeded.
Table 2. Viber trigger points and statistics.
Viber Call Statistics
• Viber call attempt failures

• Viber call attempt failure (system failure)
• Viber call attempt success rate (%)
• Viber call attempts
• Viber call connects
• Viber call disconnects (dropped)
• Viber call disconnects (normal)
• Viber call duration (ms)
• Viber call setup time (ms)
• Viber call success rate (%)
• Viber calls received
Viber Message Statistics
• Viber connection attempt success rate (%)

• Viber connection attempts
• Viber connection failures
• Viber connection success
• Viber connection success rate (%)
• Viber connection time (ms)
• Viber disconnects (dropped)
• Viber disconnects (normal)
• Viber transfer attempts
• Viber transfer failures
• Viber transfer success
• Viber transfer success rate (%)
• Viber transfer time (ms)
Viber testing is supported as on-device measurement only with Nemo Media Router application and is verified
with the following devices:
• HTC 11u
• Samsung S8 SM-G950F
• Samsung S9 SM-G960F
• Sony XZ Premium G8141
• Sony Xperia XZ1 G8342
Viber testing is optional and requires NTA50174A Nemo Media Router Viber Software Testing Option. Text
autocorrection must be disabled from device.
Miscellanous
• Reading IMSI (international mobile subscriber identity) information from device. IMSI reading
implemented to NMR as information cannot be fetched by AT commands with all devices.
Error corrections
Support Title
Ticket
Fixed crash issue with HTTP multi thread testing.
Fixed issue where USB state wasn’t recognized reliably during first start of NMR application
Fixed issue with calls where NMR did not receive call status update when call failed right
away
Fixed issue with screen casting causing high CPU load. Issue was seen with Samsung
Galaxy S7 Edge SM-G935F
Facebook crash issue fixed. Occasionally application crashed when Facebook data transfer
was disconnected (DAD).
Table 3. NMR 8.30 error corrections.
Nemo Media Router 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 or via Nemo Outdoor user interface with NMR version 7.90 onwards.
The following license options are available with Nemo Media Router version 8.30 for Android:
Product Code Description

Base Software Packages
NTA50054A Nemo Media Router Basic Includes voice call and VoLTE support. Requires also
Nemo Outdoor or Nemo Invex PESQ & POLQA licenses
for voice quality testing (optional license)
NTA50097A Nemo Media Router Pro Includes Nemo Media Router Basic features, Nemo Media
Router data and application software testing option and
Nemo Media Router WLAN software option
Options
NTA50055A Nemo Media Router data and Requires existing NMR Basic product.
application software testing option Includes basic data and social media applications (FTP,
Ping, HTTP/ HTTPS, YouTube video streaming, and HTML
browsing protocols)
NTA50056A Nemo Media Router WLAN Requires existing NMR Basic product.
software option Enables WLAN measurements
NOTE! Not available with HIM modules /2 slot wide HIM.
Required with VoWiFi and ViWiFi measurements
NTA50057A Nemo Media Router PEVQ-S Requires existing NMR Basic or NMR Pro product.
software testing option Enables PEVQ-S video streaming analysis option and
Netflix testing. (YouTube). One license per test handset
NTA50058A Nemo Media Router IMS audio Requires existing NMR Basic or NMR Pro products.
and video call quality software Enables IMS audio and video call quality testing. One
option license per test handset
NTA50120A Nemo Media Router U-vMOS Requires existing NMR Basic or NMR Pro products. U-
software testing option vMOS is Huawei’s objective criteria for measuring video
experiences based on the actual user experience.
Algorithmn is running on- device and own license option is
needed per test handset. Please see the release
documentation for compatible devices
NTA50123A Nemo Media Router WhatsApp Requires existing NMR Basic or NMR Pro products.
Software Testing Option WhatsApp testing option is Nemo Wireless Network
Testing proprietary solution running on- device and own
license option is needed per test handset. Please see the
release documentation for compatible devices
NTA50174A Nemo Media Router Viber Requires existing NMR Basic or NMR Pro products. Viber
Software Testing Option testing option is Nemo Wireless Network Testing
proprietary solution running on- device and own license
option is needed per test handset. Please see the release
documentation for compatible devices
Table 4. NMR 8.30 license options.

Compatibility and update process
Application Version Information
Nemo Media Router 8.30.370 (for Android)
1.10.14 (for iOS 11)
Nemo Browser nemobrowser-53.0.1.android-arm-final2.apk
Netflix 4.16.1 build 15145 (Netflix.mediaclient_4.16.1_build_15145)
Nemo Outdoor 8.3.0.8
TeamViewer (PC) 11.0.53254
NOTE! To be used only with 10.0.43174
Android-based handsets 10.0.47484
TeamViewer QuickSupport teamviewer_quicksupport_11.0.4203.apk
(Android-based test handset)
NOTE! To be used only with
Android-based handsets
TeamViewer QuickSupport Add-on teamviewer_quicksupport_addon_samsung_10.0.3086.apk
for Samsung
TeamViewer QuickSupport Add-on teamviewer_quicksupport_addon_htc_10.0.3086.apk
for HTC
Table 5. Compatible versions.
Nemo Media Router version 8.30 is compatible with Nemo Outdoor 8.3.0. NOTE! NMR Android versions 1.0 or
1.1 are not supported with Nemo Outdoor version 7.3.0.6 or higher. Customers using Nemo Media Router
Android 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 updates can be done using the
over the air update via NMR user interface from version 2.30.099 onwards or using the local NMR application
software update via Nemo Outdoor user interface from version 7.9.0 onwards.
To check for OTA software updates, make sure that Wi-Fi or mobile data is enabled, tab the button at the
bottom of the NMR main view and select Check for updates. Notice! Nemo browser is a separate installation
package that needs to be installed to the NMR test handset after NMR has been updated to the latest version. If
Nemo Browser is not installed, you need to manually download the Nemo browser APK file to your Nemo Media
Router handset from https://www.keysight.com/ssoauth/login.jsp. Alternatively, you can use the below QR
code to load the latest Nemo Browser version or using this URL from your Android browser:
http://handy.nemo.fi/Browser/Nemobrowser.apk
Figure 2. QR code
NOTICE: Do not launch the Nemo Browser directly. Nemo Handy and Nemo Walker Air will automatically
Please follow the steps below.
Nemo Outdoor/ Nemo Invex II NMR test handsets
1. Update Nemo Media Router to the latest version using OTA update or local update method.
2. Use local update to install the Nemo browser (nemobrowser-53.0.1.android-arm-final2.apk) to
your Nemo Media Router handset.
3. Install the file and follow the instructions.
4. Update Nemo Outdoor to version 8.3.0
5. Re-start the Nemo Media Router application.
Do not launch Nemo browser directly. Nemo Media Router will automatically launch the
browser and at the same time activate the API in the browser. In case you open the
browser manually please shut down the application before conducting HTML testing
with Nemo Outdoor.
When updating NMR from version 2.20.xx or older, please see the Nemo Outdoor user manual chapter Installing
Nemo Media Router.
Nemo Media Router for iOS is available from the App Store.
Supported handsets with Nemo Media Router
The handsets shown in the table below are supported with the Nemo Media Router application.
Product Handset Firmware/ NMR/ Nemo PEVQ-S Screen VQMon, u-vMOS

Code Nemo ID Teamviewer Outdoor video Casting Audio/
versions version streaming Video
(with analysis quality
(with initial initial
release) monitoring1
release)
NTT20120A Sony MPSS.AT.4.0.c2 8.30.370 8.3.0.8 No No No Yes
Xperia .7-00104-
XZ2 SDM845_GEN_
H8266 PACK-1
(sdm845.g Jun
1 2018
03:49:56)
(Android 8.0.0)
Nemo ID:
23444/1
NTT20125A Samsung "G965FXXU1AR 8.30.370 8.3.0.8 No No No No
Galaxy D6, ICDver 5.21,
S9+ SM- chipset
G965F 0x360","23699","
1","samsung/sta
r2ltexx/star2lte:8
.0.0/R16NW/G9
65FXXU1ARD4:
user/release-
keys"
Nemo ID: 23669
NA LG G6 MPSS.TH.2.0.1. 8.21.335 8.2.1.14 Yes No No No
(LG-H873) c3.1-00014-
M8996FAAAAN
AZM-
1.86009.12.962
80.1
(LGH873AT Nov
1 2017
12:32:00),22884
,2,lge/lucye_glob
al_ca/lucye:7.0/
NRD90U/17305
1226dc29:user/r
elease-keys
Nemo ID:
22884/2
NTT20091A Samsung G960FXXU1AR 8.21.335 8.2.1.14 Yes Yes No No

Galaxy S9 C4, ICDver 5.21, PEVQ-S and
SM- chipset Netflix
G960F 0x360,23208,2,s
amsung/starltex
x/starlte:8.0.0/R
16NW/G960FXX
U1ARC5:user/re
lease-keys
Nemo ID:
23208/2
NTT20092A Samsung Qualcomm 8.21.335 8.2.1.14 Yes No No No
Galaxy S9 Snapdragon 845
SM- MPSS.AT.4.0.c2
G960U .5-00045-
(AT&T) SDM845_GEN_
PACK-
1.135721.2
(sdm845.g Feb
11 2018
13:39:26)
Nemo ID:
23313/1
NTT20093A Samsung Qualcomm 8.21.335 8.2.1.14 No No No No
SM- MPSS.AT.4.0.c2
G960U .5-00045-
(TMOB) SDM845_GEN_
PACK-
1.135721.2
(sdm845.g Feb
11 2018
13:39:26),"2331
3","2","samsung/
starqltesq/starqlt
esq:8.0.0/R16N
W/G960USQU1
ARB7:user/relea
se-keys"
Nemo ID:
23313/2
NTT20094A Samsung Qualcomm 8.21.335 8.2.1.14 No Yes No No
SM- MPSS.AT.4.0.c2
G960U .5-00045-
(Sprint) SDM845_GEN_
PACK-
1.135721.2
(sdm845.g Feb
11 2018
13:39:26),"2331
3","2","samsung/
starqltesq/starqlt
esq:8.0.0/R16N
W/G960USQU1
ARB7:user/relea
se-keys"
Nemo ID:
23313/2
NTT20094A Samsung Qualcomm 8.21.335 8.2.1.14 No No No No
SM- MPSS.AT.4.0.c2
G960U .5-00045-
(Verizon) SDM845_GEN_
PACK-
1.135721.2
(sdm845.g Feb
11 2018
13:39:26)
Nemo ID:
23383/2
SM- MPSS.AT.4.0.c2
G960W .5-00045-
(Canada) SDM845_GEN_
PACK-
1.135721.4
(sdm845.g Mar
12 2018
11:29:33),23314
,2,samsung/star
qltecs/starqltecs:
8.0.0/R16NW/G
960WVLU1ARC
1:user/release-
keysNemo ID:
23314/1
NA Samsung Qualcomm 8.21.335 8.2.1.14 Yes No No No
SM- MPSS.AT.4.0.c2
G960U1 .5-00045-
(Cspire) SDM845_GEN_
PACK-
1.135721.4
(sdm845.g Feb
25 2018
13:20:27),23399
,2,samsung/star
qlteue/starqlteue
:8.0.0/R16NW/G
960U1UEU1AR
BG:user/release
-keys
Nemo ID:
23399/2
SM-G9600 MPSS.AT.4.0.c2
(Mexico) .1-00141-
SDM845_GEN_
PACK-
1.136250.7
(sdm845.g Feb
24 2018
11:06:45),23485
,1,samsung/star
qltezh/starqltech
n:8.0.0/R16NW/
G9600ZHU1AR
BG:user/release
-keys
Nemo ID:
23431/1
23485/1
NTT20095A Sony MPSS.AT.2.0.c4 8.21.335 8.2.1.14 Yes Yes No No
Xperia .3-00197- + Netflix
XZ1 8998_GEN_PA
G8342 CK-1 (8998.gen
(dual-SIM) Dec 5 2017
04:24:57),23140
,1,Sony/G8342/
G8342:8.0.0/47.
1.A.8.49/374421
9090:user/releas
e-keys
Nemo ID:
23140/1
NTT20085A Sony MSM8998 8.20.314 8.2.0.10 Yes Yes No Yes

Xperia Nemo ID: 22631 + Netflix
XZ1 / 22747 /22956
G8341
MPSS.AT.2.0.c4
.3-00197-
8998_GEN_PA
CK-1 (8998.gen
Dec 5 2017
04:24:57)
Android 8.0
NA Essential 2.0.c4-M1.3.1 8.11.286 8.1.1.16 Yes No No Yes
Phone (8998.gen Nov 1
PH-1 2017 22:44:47)
Nemo ID:
22759/2
NTT20078A Samsung "MPSS.AT.2.0.c 8.10.273 8.1.0.12 Yes Yes No No

Galaxy S8 2.2-00006-
SM- 8998_GEN_PA
G950U CK-
(AT&T) 1.90474.8.9773
4.8 (8998.gen
Jul 14 2017
14:01:05)","2219
4","1","samsung/
dreamqltesq/dre
amqltesq:7.0/NR
D90M/G950US
QU1AQGA:user/
release-keys"
NTT20084A Samsung MPSS.AT.2.0.c2 8.10.273 8.1.0.12 No No No No
Galaxy S8 .2-00167-
SM- 8998_GEN_PA
G950U CK-1.107921.1
(Sprint) (8998.gen Jul 29
2017
11:40:10),"2225
5","1","samsung/
dreamqltesq/dre
amqltesq:7.0/NR
D90M/G950US
QU1AQGL:user/
release-keys"
NTT20079A Samsung "MPSS.AT.2.0.c 8.10.273 8.1.0.12 Yes Yes No No
Galaxy S8 2.2-00006-
SM- 8998_GEN_PA
G950U (T- CK-
Mobile) 1.90474.8.9773
4.8 (8998.gen
Jul 14 2017
14:01:05)","2219
4","1","samsung/
dreamqltesq/dre
amqltesq:7.0/NR
D90M/G950US
QU1AQGA:user/
release-keys"
NTT20097A Samsung MPSS.AT.2.0.c2 8.10.273 8.1.0.12 No No No No
Galaxy S8 .2-00167-
SM- 8998_GEN_PA
G950U CK-1.107921.1
(Verizon) (8998.gen Jul 29
2017
11:40:10),"2225
5","1","samsung/
dreamqltesq/dre
amqltesq:7.0/NR
D90M/G950US
QU1AQGL:user/
release-keys"
NTT20069A Samsung MPSS.AT.2.0.c2 8.10.273 8.1.0.12 Yes No No No

Galaxy S8 .2-00152-
SM- 8998_GEN_PA
G950W CK-1T
(Canada (8998.gen Aug
variant) 3 2017
10:43:43)","2217
9","1","samsung/
dreamqltevl/drea
mqltecan:7.0/NR
D90M/G950WV
LS1AQH1:user/r
elease-keys
NA Samsung MPSS.AT.2.0.c2 8.10.273 8.1.0.12 Yes Yes No Yes
Galaxy S8 -00593-
SM-G9500 8998_GEN_PA
CK-1.108464.1
(8998.gen Aug
16 2017
19:26:46)","2240
4","1","samsung/
dreamqltezc/dre
amqltechn:7.0/N
RD90M/G9500Z
CU1AQH6:user/
release-keys
NA Samsung N950FXXU1AQ 8.10.273 8.1.0.12 Yes No No No
Galaxy HB, ICDver
Note 8 5.18, chipset
SM-N950F 0x355,"22440","
1","samsung/gre
atltexx/greatlte:7
.1.1/NMF26X/N9
50FXXU1AQI1:u
ser/release-
keys"
NTT20065A HTC U11 MPSS.AT.2.0.c4 8.02.245 8.02.22 No No No No
(2PZC300 -00242.1-
00) 8998_GEN_PA
CK-
1.99509.3.1000
16.1 (8998.gen
May 23 2017
18:47:46)
NTT20064A Sony "MPSS.AT.2.0.c 8.02.245 8.02.22 Yes Yes No Yes
Xperia XZ 4.3-00006-
Premium 8998_GEN_PA
G8142 CK-1.94857.13
single (8998.gen May
25 2017
18:33:40)","2185
9","1","Sony/G8
142/G8142:7.1.1
/45.0.A.5.1/4759
98232:user/relea
se-keys"
NTT20063A Sony "MPSS.AT.2.0.c 8.02.245 8.02.22 No No No No
Xperia XZ 4.3-00006-
Premium 8998_GEN_PA
G8141 CK-1.94857.11
multi (8998.gen May
1 2017
17:14:51)","2172
2","1","Sony/G8
141/G8141:7.1.1
/45.0.A.1.229/42
11101182:user/r
elease-keys"
NTT20075A Samsung G950FXXU1AQ POLQA & PESQ 8.0.0.15 Yes No No Yes

Galaxy S8 DG, ICDver supported from (Requires
SM- 5.17, chipset 8.02.245 version
G950F 0x355 onwards 8.01)
8.00.233
NTT20076A Samsung G955FXXU1AQ 8.00.233 8.0.0.15 Yes No No Yes

Galaxy C9, ICDver 5.17, (Requires
S8+ SM- chipset 0x355 version
G955F 8.01)
NTT40081A Samsung MPSS.TH.2.0.c2 8.01.244 8.0.1.20 No Yes No No

Galaxy S7 -00178-
SM- M8996FAAAAN
G930R7 AZM-1
(CSpire) (8996.gen Apr
13 2017
19:39:35)","2180
8","1","samsung/
heroqlteacg/hero
qlteacg:7.0/NRD
90M/G930R7W
WU4BQD3:user/
release-keys
NA Samsung MPSS.TH.2.0.c2 8.01.244 8.0.1.20 No No No No
Galaxy S7 -00171-
SM- M8996FAAAAN
G930V AZM-1.81356.3
(Verizon) (8996.gen Mar
13 2017
16:13:31)","2152
1","4","Verizon/h
eroqltevzw/hero
qltevzw:7.0/NRD
90M/G930VVRU
4BQA4:user/rele
ase-keys
NTT20052A Samsung MPSS.TH.2.0.c2 8.00.233 8.0.0.15 Yes No No
Galaxy S7 .1-00018-
SM- M8996FAAAAN
G930P AZM-
1.78569.1.7897
8.1 (8996.gen
Dec 21 2016
14:28:49)","2131
7","1","samsung/
heroqltespr/hero
qltespr:6.0.1/MM
B29M/G930PVP
E4APL6:eng/test
-keys
Not Sonim MPSS.DI.2.0.1.c NMR 8.00.233 8.0.0.15 No Yes No
available via XP7700 1-00017-
Keysight (DAAAANAZ
Apr 28 2016
15:57:11)
MPSS.DI.2.0.1.c
1.18-VOLTE-
(DAAAANAZ
Dec 2 2016
15:53:04)
Not Apple 1.33.00_DEBUG NMR 1.10.14 7.9.1.16 No No No
available via Iphone 7 (MPSS. TH. Nov (iOS)
Keysight (A1160) 6 2016
18:23:16)
NTT20050A Google MPSS.TH.2.0.2. NMR 7.9.1.220 7.9.1.16 Yes Yes No

Pixel G- c1-00005-
2PW4100 M8996FAAAAN
AZM-
1.78021.1.7805
3.1 (8996.gen
Nov 19 2016
02:02:25)","2088
7","1","google/sa
ilfish/sailfish:7.1.
1/NMF26Q/3537
182:user/release
-keys
NTT40041A Huawei P9 21.201.00.00.03 NMR 7.90.210 7.9.0.9 No Yes No
EVA – L09 1
NTT40043A Sony 39.0.A.1.250 NMR 7.90.210 7.9.0.9 No No No
Xperia XZ R7B NO (1305-
F8331 1010)
NTT40039A HTC 10M MPSS.TH.2.0.c1 NMR 2.52.177 7.8.2.18 Yes (7.90 Yes
(Orange & .8-00004- teamviewer onwards)
Taiwan M8996FaaaaNA 10.0.47484
variants) ZM-
1.47560.3.4855 teamviewer_
2.3 (8996.gen quicksupport_11
Mar 31 2016 .0.4203 and
22:18:46) teamviewer_quic
(Orange variant) ksupport_addon
_samsung_10.0.
3086 and QS
MPSS.TH.2.0.c1 Add-On: HTC
.8.00004.M8996
FAAAANAZM-
1.50355.1.5191
2.1 (8996.gen
Apr 25 2016
15:13:02)
Taiwan variant
NTT40036A Sony MPSS.TA.2.0.c1 NMR 2.52.177 7.8.2.18 Not Yes
Xperia X 4-00002- supported
F5121 8976_GEN_PA
CK-1 (8976.gen
May 5 2016
03:38:55)
NTT40037A Sony MPSS.TH.2.0.c1 NMR 2.52.177 7.8.2.18 Yes (7.90 Yes
Xperia .11-00006- onwards)
Performan M8996FAAAAN
ce X AZM-1
F8131 (8996.gen Aug
10 2016
03:41:02)
NTT40038A Sony MPSS.TH.2.0.c1 NMR 2.52.177 7.8.2.18 Yes with Yes

Xperia .11-00006- NMR 8.01
Performan M8996FAAAAN onwards
ce X AZM-1
F8132 (8996.gen Jun 2
2016 20:11:33)
NA Samsung N920GUBU2BP 2.52.177 7.8.2.18 Yes NA
Galaxy E4, ICDver 5.00, teamviewer_quic
Note 5 chipset SS333 ksupport_
SM-
N920G 11.0.4203.apk
teamviewer_quic
ksupport_addon
_samsung_10.0.
3086.apk
NTT40047A Samsung G935FXXE1AP 2.51.164 7.8.1.14 Yes Yes Yes
Galaxy S7 D1 Device requires
edge (SM- an engineering
935F, firmware for
Optus) NMR use
NTT40045A Samsung G928W8VLU2B 2.51.164 7.8.1.14 Yes
Galaxy S6 PC5, ICDver
edge+ 5.00, chipset
(SM- SS333
G928W8)
NTT40040A Samsung MPSS.TH.2.0.c2 2.51.164 7.8.1.14 NMR
Galaxy S -00060- 7.91.220
7 (SM- M8996FAAAAN onwards
G9300) AZM- VoWiFi
1.42191.6.4319 audio
5.15 (8996.gen
Mar 17 2016 ViWiFI
16:28:28) video
Not Apple 1.56.00_DEBUG NMR for iOS 7.8.0.8

available via iPhone 6S (MPSS.BO. Jan v1.00.9
Keysight (A1688) 13 2016
Network 18:02:43)
Testing
NTT40044A Samsung G928KKKU1AO 2.50.156 7.8.0.8 Yes
Galaxy 6 H4 ICDver 4.90,
edge+ chipset SS333
(SM-
G928K)
NTT40034A Samsung MPSS.BO.2.0.1. 2.41.137 7.7.1.14 Yes Yes
Galaxy c3.5-00137- teamviewer_quic
Note 5 M9635TAARAN ksupport_
SM-N9200 AZM-1
(TAARANAZ 11.0.4203.apk
Nov 24 2015 teamviewer_quic
20:51:00) ksupport_addon
_samsung_10.0.
3086.apk
NTT40004A Sony 32.0.A.6.170_R1 2.41.137 7.7.1.14
Xperia Z5 6B (1298-3443 teamviewer_quic
E6653 Telstra AU) ksupport_
11.0.4203.apk
NTT40001A Motorola MPSS.BO.2.5.c 2.41.137 7.7.1.14 Yes
Moto X 8-00010- teamviewer_quic
Pure M8994FAAAAN ksupport_
Edition AZM-1
XT1575 (FAAAANAZ Jul 11.0.4203.apk
23 2015
14:27:30)
NTT40031A Samsung G928FXXU1AO 2.40.125 7.7.0.9 Yes
Galaxy S6 H3, ICDver 4.90, teamviewer_quic
edge+ chipset SS333 ksupport_11.0.4
SM- 203
G928F teamviewer_quic
ksupport_addon
_samsung_10.0.
3086
NTT40032A Samsung N920IDVU1AOH 2.40.125 7.7.0.9 Yes
Galaxy 3, ICDver 4.90, teamviewer_quic
chipset SS333 ksupport_11.0.4
Note 5 203
SM-N920I teamviewer_quic
ksupport_addon
_samsung_10.0.
3086
NTT40023A Samsung G920FXXU1AO 2.31.108 7.6.1.12 Yes
Galaxy S6 CWICDver 4.80
SM-
G920F
NTT40046A Samsung G920W8VLU1A 2.31.108 7.6.1.12
Galaxy S6 OE1, ICDver
SM- 4.61
G920W8
(Bell)
NTT40030A Samsung G920IDVU1BOF 2.31.108 7.6.1.12 Yes
Galaxy S6 6, ICDver 4.90,
SM-G920I chipset SS333
(APAC)
NTT40022A Samsung MPSS.BO.2.0.1. 2.31.108 7.6.1.12 Yes
S6 SM- c3.5-00023-
G920P M9635TAARAN
(Sprint) AZM-
1.15020.1.1564
3.1 (TAARANAZ
May 5 2015
01:51:10)
NTT40021A Samsung MPSS.BO.2.0.1. 2.31.108 7.6.1.12 Yes
Galaxy S6 c3.5-00051-
SM-G9208 M9635TAARAN
(Taiwan) AZM-
1.17099.2.1743
2.1 (TAARANAZ
Apr 23 2015
10:06:47)
NTT40028A Samsung G920TUVU2CO 2.31.108 7.6.1.12 Yes From NMR
Galaxy S6 F8, ICDver 7.90
SM- 4.61, chipset onwards
G920T SS333 ViLTE video
(T-Mobile) VoWiFi
audio
ViWiFi
audio/video
NTT40035A Samsung MPSS.DI.3.0.c5- 2.30.099 7.6.0.7 Yes
Note 4 00300-
Note SM- M9625TAARAN
N910T AZM-1.7386.2
(TMOB) (TAARANAZ
Nov 11 2014
19:36:24)
NTT40003A Sony MPSS.DI.3.0.c9. 2.30.099 7.6.0.7 Yes
Xperia Z3 1-00022-
D6653 M8974AAAAAN
AZM-1
(AAAAANAZ
Nov 26 2014
03:27:54)
NTT40020A Samsung MPSS.DI.2.0.1.c 2.20.078 7.5.0.5
Galaxy S5 2.2-00006-
SM- M8974AAAAAN
G900M RZM-1
(AAAAANRZ
May 9 2014
21:44:23)
NTT40015A Samsung MPSS.BO.1.0.r1 2.11.060 7.4.1.13 Yes Yes
Galaxy 0-00108-
Note 4 M9635TAARAN
SM-N910F AZM-1.5514.1
(TAARANAZ
Sep 16 2014
20:04:39)
NTT40016A Samsung MPSS.BO.1.1.r1 2.11.060 7.4.1.13
Galaxy 0-00108-
Note 4 M9635TAARAN
SM- AZM-1.5514.1
N910G (TAARANAZ Oct
4 2014
16:47:00)
NA Samsung MPSS.DI.2.0.1.c 2.11.060 7.4.1.13
Galaxy S5 2-00055-
SM- M8974AAAAAN
G900T1 RZM-1
(AAAAANRZ
(Metro May 23 2014
PCS) 19:27:09)
Galaxy S5 2.2-00006-
SM- M8974AAAAAN
G900R4 RZM-1
(AAAAANRZ
(US Mar 31 2014
Cellular) 01:04:01)
NA Samsung MPSS.BO.1.0.c 2.10.054 7.4.0.9

Galaxy S5 1-00091- (Data
4G+ SM- M9635TAARAN only, not
G901F AZM-1 voice
(TAARANAZ quality)
Aug 11 2014
11:59:20)
Galaxy S5 2.2-00006-
SM-G900I M8974AAAAAN
RZM-1
(AAAAANRZ
Mar 29 2014
15:46:27).
Android 4.2
NTT40007A Samsung MPSS.DI.2.0.1.c 2.01.041 7.3.1.9 Yes
Galaxy S5 2.2-00006-
SM- M8974AAAAAN
G900F RZM-1
(AAAAANRZ
Mar 29 2014
15:46:27).
Android 4.2
NTT40009A Samsung M9615ACEHW 2.01.041 7.3.1.9 Yes
Galaxy S5 MAZD1795
SM- (ACEFWMAZ
G900T (T- Aug 17 2012
Mobile) 20:29:27)
NTT40010A Samsung M8930B- 2.01.041 7.3.1.9
Galaxy S5 AAAATAZM-
SM- 5.0.060165
G900P (BBAAATAZ Jan
(Sprint) 30 2014
14:45:25)
NTT40011A Samsung M8930B- 2.01.041 7.3.1.9
Galaxy S5 AAAATAZM-
SM- 5.0.060165
G900W8 (BBAAATAZ Jan
(Bell) 30 2014
14:45:25)
NA Samsung M9615ACEHW 1.0.011 7.1.0.6
Galaxy S MAZD1795 2.00.034 7.3.0.6
III (I9305) (ACEFWMAZ
Aug 17 2012
20:29:27)
NA Samsung M9615A- 2.00.034 7.3.0.6 Yes
Galaxy S4 CEFWTAZM-
(GT-i9505) 4.0.17062
(ACEFWTAZ
Apr 12 2013
18:16:13)
NA Samsung M8930B- 1.10.015 7.2.0.6
Galaxy S4 AAAATAZM- 2.00.034 7.3.0.6
Mini (GT- 3.2.27040
i9195) (BBAAATAZ Jul
15 2013
11:32:02)
NA Samsung M8974A- 2.00.034 7.3.0.6
Galaxy AAAANAZM-
S4+ (GT- 1.0.180095
i9506) (AAAAANAZ
Dec 12 2013
16:26:28)
Android 4.3
NA Samsung SET_BY_CM 2.00.034 7.3.0.6
Galaxy (AAAAANAZ
Note 3 Sep 13 2013
(SM- 18:20:25)
N900T)
NA Samsung M8930B- 2.00.034 7.3.0.6
Galaxy S4 AAAATBZM-
Mini (SPH- 6.0.01049
L520 (BBAAATBZ
Sprint) Nov 4 2013
20:22:08)
Table. Supported handsets with Nemo Media Router application.
Table 6. Supported handsets with Nemo Media Router application.
For a complete list of supported devices, please see the separate document Nemo Outdoor 8.3.0 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!
New Devices
Product Device Firmware/ Handler UEs Technology Driver
Code Nemo ID SW /
CPU
NTT20125A Samsung "G965FXXU1 Samsung 1 LTE bands: FDD Samsung USB
Galaxy ARD6, ICDver Shannon 700APT/700a/700b/700c/800/800 Drivers 1.5.63.0
S9+ SM- 5.21, chipset 360 GSM/ Lower/800Upper/850/850+/900/15
G965F 0x360","23699 UMTS/ 00Lband/1800/1900/1900+/2100A
","1","samsung LTE-A WS/2100AWS-3/2100/2600 TDD
/star2ltexx/star 3CC or 1900/2000/2300/2500/2600/5500U
2lte:8.0.0/R16 4CC or nlicensed
NW/G965FXX 5CC FDD (E-UTRA bands 28, 12, 17, 13, 20,
U1ARD4:user/ & TDD 18, 19, 5, 26, 8, 32, 3, 2, 25, 4, 66,
release-keys" 1, 7, 39, 34, 40, 41, 38, 46)
Nemo ID: NOTE: Device capabilities may
23669 differ by markets and mobile
operators.
NTT20120A Sony Qualcomm Qualcomm 1 LTE bands: FDD Sony_eng_drive
Xperia XZ2 SDM845 LTE-A 700APT/700a/700b/700c/700d(DL rs (4.0.1.9)
H8266 Snapdragon 5CC Cat only)/800/800Upper/850/850+/900
845 18/ 2CC /1500L(DLonly)/1800/1900/2100A
MPSS.AT.4.0. UL Cat13 WS/2100AWS-3/2100/2600 TDD
c2.7-00104- 1900/2300/2500/2600
SDM845_GEN (E-UTRA bands: 28, 12, 17, 13,
_PACK-1 29, 20, 19, 5, 26, 8, 32, 3, 2, 4, 66,
(sdm845.g Jun 1, 7, 39, 40, 41, 38
1 2018 LTE UE Category: 12, 10, 7, 4
03:49:56)
(Android 8.0.0) LTE UE Category DL: 15, 12
Nemo ID: LTE UE Category UL: 13
23444/1 256QAM DL: supported on all
bands
64QAM UL: supported on all
bands
WCDMA bands: 1, 2, 4, 5, 6, 8, 19
GSM bands: 850/900e/1800/1900
NOTE: Device capabilities may
differ by markets and mobile
operators.
NTT20134A Lierda SSB,V150R10 Neul NB- 1 LTE bands FDD Lierda_NB86G_
NB86G 0C10B200SP1 IoT 700APT/700a/700b/700c/700PS/8 Vers2.2.0.0.zip
LSD4NBT0 , 00/800Lower/800Upper/900/850/8
611-02D0 SECURITY_A, 50+/1800/1900/1900+/2100AWS-
V150R100C20 3/2100
B300, (E-UTRA bands: 28, 12, 17, 13,
PROTOCOL_ 14, 20, 18, 19, 5, 26, 8, 3, 2, 25,
A,V150R100C 66, 1)
20B300,
APPLICATION LTE UE Category: nb1
_A,B300R0Lie
rda1501301,
SECURITY_B,
V150R100C20
B300,
RADIO,Lierda
_cal_A01
NTS13501A PCTEL ProductRefVer 1 Multi system. Please see the PCTel VCP
/ IBFlex Lite 1. 0.19. 0, separate PCTEL IBflex Lite data 2.1.1.0
NTS13502A ESN sheet for further details
00000000815
10012,
ASN1Ver 1.
6. 0. 0, -E
SWVer 2. 2.
7. 0, APIVer
1.13. 0. 0
Table 7. New test devices.

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, Keysight 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 8.3.0 Compatible Devices.pdf. for a list of verified Qualcomm-based CDMA
and WCDMA terminals.
CDMA terminals with or without RUIM card purchased from Keysight Network Testing must be registered with
a local CDMA operator. Keysight Network Testing does not take any responsibility if a local operator restricts
the registration of test terminal(s) supplied by Keysight Network Testing.
Nemo Cloud
Configuration support for PCTEL scanners
• Added remote configuration support for PCTEL MX, MXflex, IBflex and IBflex Lite scanner receivers.
Requires Nemo Cloud version 2.41.
Miscellanous
• Editing scripts included in the active Work Order is blocked to prevent measurements with incorrect
script settings
• A device phone number can be added/changed from Nemo Cloud. However, if the number can be read
directly from the test device, this number is used
• Device label can be added/changed from Nemo Cloud. Note that this label is overwriting any locally
made labels. Device label helps to identify test devices
• Added option to backup measurement files to local drive sent to Nemo Cloud
o When “Enable backup” is selected, files sent to Nemo Cloud are stored to “Sent” folder instead
deleted
o Option can be found from Nemo Cloud/ Settings/ Enable backup
o With the Manage Files user can see the list of sent files and also delete selected files
Figure 3. Nemo Cloud Ribbon bar.
Nemo Navigation Assistant
Product Nemo Outdoor

Nemo Navigation Assistant 8.2.0 or later
v1.00.12

Qualcomm Software Handler Updates
New component carrier and MIMO metrics
The new metrics present statistical information calculated from all CA carriers during the reporting period and
aggregates the impact of all CA carriers to single metrics for easier visualization and map plotting. The link
adaptation summary (PLAISUM) event is logged/aggregated after packet link adaptation information for
downlink events for all serving cells (PLAID). TTIs with no data are considered in the calculations.
• Total DL PRB usage

o The average of the total downlink PRB allocation across all serving cells
• Total DL PRB utilization (%)
o Percentage of PRBs utilized over the reporting period and over all serving cells. Indicates the
usage of radio resources over the total resources.
• DL streams
o The average of the total downlink MIMO streams across all serving cells.
• Scheduled serving cells
o The average number of scheduled serving cells during the reporting period
In the example below the detailed information seen in the event view is aggregated in LTE CA Total PRB
utilization and streams view.
Figure 4. LTE CA summary information.

New bands and other additions
• Added E-UTRA bands 49, 50, 51, 52, 72, 73, 74, 75, 76, 85, 252 Unlicensed NII-1) and 255 (Unlicensed
NII-3)
• Optional Qualcomm diagnostics logging (per TTI) and decoder updated supporting the following new
messages:
o LTE ML1 Connected mode LTE intra-frequency measurement results
o LTE LL1 PUCCH CSF log
o LTE ML1 DCI information report
o LTE ML1 PDSCH stat indication
o LTE ML1 PUCCH power control
o LTE ML1 PUSCH power control
o LTE ML1 PDCCH-PHICH indication report
o LTE ML1 radio link monitoring
o LTE ML1 random access request (MSG1) report
o LTE ML1 random access response (MSG2) report
o LTE ML1 UE identification message (MSG3) report
o LTE LL1 serving cell frame timing
• Previously supported messages
o LTE LL1 serving cell frame timing
o LTE LL1 PUSCH TX report
o LTE LL1 PUCCH TX report
o LTE LL1 PUCCH CSF
o LTE LL1 PUSCH CSF
o LTE LL1 PDSCH decoding results
o LTE LL1 PDSCH demapper configuration
o LTE LL1 PCFICH decoding results
o LTE LL1 PDCCH decoding results
o LTE ML1 DCI information report
o LTE ML1 PDCCH-PHICH indication report
o LTE ML1 uplink PKT build indication
o LTE ML1 PDSCH stat indication
o LTE ML1 connected mode LTE intra frequency measurement results
o LTE ML1 random access request (MSG1) report
o LTE ML1 random access response (MSG2) report
o LTE ML1 UE identification message (MSG3) report
o LTE ML1 contention resolution message (MSG4) report
o LTE ML1 PUSCH power control
o LTE ML1 PUCCH power control
o LTE ML1 CDRX event info
o LTE ML1 PMCH decode results
o LTE ML1 all DL channels decode results
o LTE ML1 GM TX report
o LTE ML1 radio link monitoring info
o LTE MAC DL transport block
o LTE MAC UL transport block
o LTE MAC UL TX statistics
o LTE RLC DL AM all PDU
o LTE RLC DL UM data PDU
o LTE RLC UL AM all PDU
o LTE RLC UL UM data PDU
o LTE PDCP UL statistics
o LTE PDCP DL data PDU
o LTE PDCP DL data PDU with ciphering
o LTE PDCP UL data PDU
o LTE PDCP UL data PDU with ciphering
Samsung Shannon Software Handler Updates
New component carrier and MIMO metrics
The new metrics present statistical information calculated from all CA carriers during the reporting period and
aggregates the impact of all CA carriers to single metrics for easier visualization and map plotting. The link
adaptation summary (PLAISUM) event is logged/aggregated after packet link adaptation information for
downlink events for all serving cells (PLAID). TTIs with no data are considered in the calculations.
• Total DL PRB usage

o The average of the total downlink PRB allocation across all serving cells
• Total DL PRB utilization (%)
o Percentage of PRBs utilized over the reporting period and over all serving cells. Indicates the
usage of radio resources over the total resources.
• DL streams
o Not supported with Shannon based devices
• Scheduled serving cells
o Not supported with Shannon based devices
LAA support
• Added support for E-UTRA band 46, TDD 5200, U-NII

Neul Software Handler Updates
Added the following new parameters:
• eDRX & PSM information logging

o Values requested by UE (ATTACH REQUEST, TRACKING AREA UPDATE REQUEST) and values
assigned by network (ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT) are logged to
requested power save mode and (PSMR) power save mode parameters (PSMI) events.
Figure 5. Requested and active eDRX and PSM parameters.
• New features:
o eDRX & PSM settings configuration for LTE-M (NB-S1 mode eDRX cycle) and NB-IoT (NB-S1
mode eDRX cycle)
o Settings can be configured via UE settings
Figure 6. eDRX and PSM configuration dialog and example views for eDRX and PSM parameters.
• New firmware:
o Support for Boudica 150 chipset, firmware versions V150R100C10B200,
V150R100C10B200SP1 and V150R100C20B300
o Support for Quectel BC95 EVB evaluation kit firmware version R01A04/
V100R100C10B657SP3
Generic Scanner Handler Updates
No changes.
Keysight Spectrum Analyzers and Scanning Receivers
No changes in this release
Product Firmware Nemo Outdoor

Nemo FSR1 FSR 04.05.12 8.1.0 or later
scanner receiver
Keysight FieldFox A.09.53 7.9.0 or higher
Handheld RF and
Microwave
Analyzers
PCTEL Scanner Handler Updates
PCTEL IBflex Lite
Added support for PCTEL IBflex Lite scanner receiver. Handler software for PCTEL IBflex scanner supports
both models IBflex and IBflex Lite scanner receivers. PCTEL IBflex Lite provides the same KPIs as PCTEL IBflex
but without MIMO support.
Feature comparison
Feature IBflex ® IBflex ® Lite

Band Range 10 MHz – 6 GHz 10 MHz – 6 GHz
Supported Technologies LTE (FDD and TDD), LTE-LAA, NB-IoT, WCDMA, CDMA, EV-DO, TD-SCDMA, GSM, Wi-Fi LTE (FDD and TDD), LTE-LAA, NB-IoT, WCDMA, CDMA, EV-DO, TD-SCDMA, GSM, Wi-Fi
Simultaneous Multi-Technology Measurement Yes Yes
Fast Blindscan Yes, 3 Mode Yes, 3 Mode
2x2
LTE MIMO Measurements 4x2 No
eMBMS Measurements Yes Yes

Layer 3 Measurements LTE (FDD and TDD), WCDMA, CDMA, GSM, TD-SCDMA LTE (FDD and TDD), WCDMA, CDMA, GSM, TD-SCDMA
Connect with Bluetooth®, USB, and Ethernet Yes Yes
SD Card Storage Yes No
Signal Analyzer Option Available Yes Yes
Maximum Power 18W; 10W Power Save Mode) 18W
• Without Battery Pack: • Without Battery Pack:
7.6” D x 4.4” W x 1.55” H 7.6” D x 4.4” W x 1.55” H
(192 mm D x 111.8 mm W x 39.4 mm H) (192 mm D x 111.8 mm W x 39.4 mm H)
Size
•With Battery Pack: • With Battery Pack:
10.1” D x 4.4” W x 2.1” H 10.1” D x 4.4” W x 2.1” H
(257.6 mm D x 111.8 mm W x 53.1 mm H) (257.6 mm D x 111.8 mm W x 53.1 mm H)
• Without Batteries: 2.4 lb (1.1 kg) • Without Batteries: 2.4 lb (1.1 kg)
Weight
• With Batteries: 3.8 lb (1.7 kg) • With Batteries: 3.8 lb (1.7 kg)
Figure 7. IBflex vs IBflex Lite.
PCTEL IBflex and IBflex Lite
• Added E-UTRA band 70 support (AWS-4, 1995 MHz-2020 MHz DL)

PCTEL IBflex 2. 2. 7. 0/ API 1.13.0.0 8.2.0 or later
PCTEL IBflex Lite 2. 2. 7. 0/ API 1.13.0.0 8.3.0 or later
PCTEL MXflex 5.2.0.0 / API 1.13.0.0 8.2.0 or later

Rohde & Schwarz Scanner Handler updates
TSME & TSMW
• Added E-UTRA band 70 support (AWS-4, 1995 MHz-2020 MHz DL)

Rohde & Schwarz Firmware 3.01.03/ Vicom 16.05 8.2.0 or later
TSME Scanner
Rohde & Schwarz Firmware 2.10 8.2.0 or later
TSMW Scanner

QoS & QoE Testing
Application throughput downlink 1s

The latest release introduces a new KPI called “Application throughput downlink 1s” and it is defined as
follows:
• Start trigger point: First packet containing content (same as ETSI method A)
• Stop trigger point: 1 second from the start trigger point
The new KPI is supported with FTP, HTTP and HTTP browsing data protocols. It includes payload data from all
sockets including HTTP headers. The parameter is useful especially with the HTTP browsing with dynamic
content such as ads etc. without a well-defined last data packet. Currently, the parameter is supported with PC-
based measurements only. Nemo Media Router (on-device measurements) support will be available 4Q/2018.
Figure 8. Trigger points.
Requirements:
• Network Monitor must be installed

• IP capture must be enabled (no need for logging)
• IPv6 must be disabled from device network settings
User Interface Updates
New Wait command- Time Synchronization Point
The new “Time Synchronization Point” command in scripts is useful especially when mobile-to-mobile test calls
are made between different two field units as it eliminates any possible delay variables with call setup and call
disconnections. It provides accurate time synchronization on both A- and B- sides with multiple devices. Also,
when a certain command must be executed exactly after an elapsed time (t=0) with more than one device.
Each time the script runs into a Time Synchronization Point, it checks the elapsed time from the previous Time
Synchronization Point and waits until the wait time condition is met. This way the script engine keeps the
original reference time point of (t=0) regardless of script iteration in order to prevent time from drifting.
Example: Imagine running the script below three times:
1. Make Call (duration=30 sec)
2. End Call
3. Wait (Sync Point 60 sec)
4. Receive Call (timeout=45 sec)
6. Wait (Sync Point 90 sec)
Iteration #1:
Sync Point #1: Check if (60) secs have been elapsed since (t=0)
Sync Point #2: Check if (60+90) secs have been elapsed since (t=0)
Iteration #2:
Sync Point #1: Check if (60+90+60) secs have been elapsed since (t=0)
Sync Point #2: Check if (60+90+60+90) secs have been elapsed since (t=0)
Iteration #3:
Sync Point #1: Check if (60+90+60+90+60) secs have been elapsed since (t=0)
Sync Point #2: Check if (60+90+60+90+60+90) secs have been elapsed since (t=0)
Figure 9. A-party script file.
Figure 10. B-party script file.
Miscellaneous
• Measurement profiles can be copied. This makes it easier and faster to make new measurement
profiles with different settings e.g. for FTP data transfers
• Graphical script engine improvement: Draw implementation has been changed so that sequential
command starts on the same line
• Added application name and operation to function column of script editor. This helps identifying what
is the application and operation command without opening the command line
• User definable frequency units (Hz, kHz, MHz and GHz) for different UI controls
• Added feature to hide current position icon in map window. Useful e.g. when taking screenshots
• Notification icons updated
o Icon size can be adjusted via User Interface properties->Paths->Images
Figure 11. New notification icons.
Nemo File Format
Nemo Outdoor version 8.3.0 supports the Nemo file format version 2.36. Existing Nemo analytics tools can be
used to post-process files made with Nemo Outdoor 8.3.0 but the new parameters are not parsed. Nemo file
format 2.36 will be supported in Nemo Analyze version 8.2, Nemo Xynergy version 18.3 and Nemo WindCatcher
version 3.6.6.x.
• Added support for E2E server host and IP address information. (#SERVER)
• Added support for WhatsApp video testing. (CAA, CAF, CAC, CAD)
o Note: Operation is not currently supported with Nemo collection tools
• Added support for Viber testing. (CAA, CAF, CAC, CAD, DAA, DAF, DAC, DAD, DREQ, DCOMP)
• Added support for the first one second transfer throughputs. (DSUMMARY)
• Added support for mScore TCP packet loss and summary link parameters. (DSUMMARY)
• Added support for E-UTRA bands 49, 50, 51, 52, 72, 73, 74, 75, 76, 85, 240, and 250.
• Added support for LTE serving cell indexes up to seven.
• Added support for LTE ranks up to eight. (PLAID, CQI)
• Added support for LTE serving cell indexes from five to seven.
• Added support for link adaptation summary. (PLAISUM)
• Added support for eDRX and PSM forcing. (LOCK)
• Added support for requested and used PSM and eDRX timer values. (PSMR, PSMI)
Discontinued Products
Discontinued Chipsets and Test Device Handler Software Options
The following Keysight Wireless Network Testing Solution products have been discontinued. New versions of
the software will not be provided or tested with the Nemo Outdoor and Nemo Invex platforms from version
8.3.0 onwards.
Product Code Handler Software Option Chipset/Vendor Notes

NTA50092A Handler for Altair LTE FDD/ Altair
TDD
NTA50034A Handler software for Altair LTE Altair
TDD
NTA50035A Handler software for Altair LTE Altair
FDD
NTA50036A Handler software for HiSilicon Balong 7x0 / Hisilicon Balong 7x0 chipset
7x0 GSM /UMTS/ LTE-A 2CC
NTA50011A Handler software for HiSilicon / Balong 7x0 / Hisilicon Replaced by NTA50010A
HiSilicon Kirin GSM / UMTS / Handler software for HiSilicon
LTE-A 2CC Kirin GSM / UMTS / LTE-A
2CC
NTA50042A Handler software for Motorola Motorola
iDEN
NTA50040A Handler software for Beceem Beceem
BCS200/BCSM 250/3300
NTA50087A Handler software for DRT DRT
4311B and WiMAX scanner
NA Handler software for Datang/ Datang/ Leadcore
Leadcore
Discontinued Software License Options
Product Code Software License Option Notes

NTA60004A Qchat PTT software option
Discontinued Commercial Software Packages and Handler Software Options
Product Code Name Notes

NTA50004A Nemo Outdoor 2G/ 3G Starter Replaced by NTA50074A
Package Nemo Outdoor 2G/ 3G/ 4G
Starter Package
NTA50063A Handler for Samsung Shannon Individual handler software

GSM option discontinued. Part of the
Handler Software packages.
NTA50064A Handler for Samsung Shannon Individual handler software
UMTS option discontinued. Part of the
Handler Software packages.
NTA50155A Handler for Samsung Shannon Replaced by NTA50160A
333/335 GSM/ UMTS Handler for Samsung Shannon
333/335/355 GSM/ UMTS/
LTE
333/335 GSM/ UMTS/ LTE Handler for Samsung Shannon
333/335/355 GSM/ UMTS/
LTE
333/335 GSM/ UMTS/ LTE-A Handler for Samsung Shannon
2CC 333/335/355 GSM/ UMTS/
LTE-A 2CC
333/335 GSM/ UMTS/ LTE-A Handler for Samsung Shannon
3CC 333/335/355 GSM/ UMTS/
LTE-A 3CC
333/335/355 GSM/ UMTS Handler for Samsung Shannon
333/335/355 GSM/ UMTS/
LTE-A 4CC
Computer Hardware and Software Requirements
• PC (Lenovo or Dell recommended) with Windows 8 ® or Windows 10 ® Professional (32/64 bit)
• Processor Intel® Core™ i7 2.66GHz or higher
• SSD drive recommended

• 500 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
• Internal 3G/ 4G modem or WiFi hotspot is recommended when using end to end call communication with
Nemo Server and with Nemo Cloud
Device Configuration and Workspace Files
Device configuration and workspace files made by Nemo Outdoor version 8.3.0 are fully compatible with Nemo
Outdoor versions 8.2.2 and 8.2.1.
Nemo Outdoor accessories and verified configurations
No new device configurations tested with this release. The following multi device configurations has been
verified by Nemo Wireless Network Solutions.
Device Nemo Backpack Nemo Carrying Case

(number of devices) (number of devices)
Samsung Galaxy S7 9 8
SM-G9300
SM-G950F
SM-G960F
SM-G960U/ U1/ W
Sony Xperia XZ 9 8
Premium G8141
Sony Xperia XZ 9 8
Premium G8142
Table 12. Verified multi configurations.
Installation
Supported operating systems are Windows 7 ® (32/ 64-bit), Windows 8 ® (32/ 64-bit) and Windows 10.
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. NOTE! Microsoft Network Monitoring 3.4 must be
installed to enable the packet capturing.
Start Windows® and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D). Copy 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.
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 run.
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 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.
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 a copy protection module is not needed during uninstallation. When the Nemo Outdoor
software uninstallation is complete, you will need to restart the computer.
Dongle runtime drivers
In case software license (Nemo GLS) is used with Nemo Outdoor application the runtime driver must be chosen
at the time of installing Nemo Outdoor application.
Limitations and Issues with Windows 7 Operating System

The following limitations with Windows 7 operating system have been noticed and verified by Keysight Finland
or informed by the vendors:
- Debug logging needs administrative privileges if User Account Control Settings (UAC) is enabled. It is
recommended to change the 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 is recommended to change the UAC settings to Never notify. This can be
done via User Account Control Settings.
Figure 12. UAC settings.
Known Issues
Test device related known issues for UEs, scanners, and other devices are listed in a separate document:
(Nemo_Outdoor Test_Device_Technical_Notes).
General and user interface
Note that if there is a system that measures acceleration in the laptop and that 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 13. Lenovo active protection system properties.

- Google map issues:
- 22449: Map layers flash too often
- 22450: Using "Points of interest" interferes with the layer drawing
- Auto center is disabled when map is moved by user
- Scanner profile files:

- Scanner profile files is supported only with on-line mode
- NB-IoT scanning profile not supported with initial release
- Script is not started when "Start measurement list on startup" is chosen from UI properties
- 23037: Moved indoor markers are not saved to .mrk file if it is compressed
Nemo Analyze
- Nemo Analyze initialization fails if Nemo Analyze is already open and the user clicks the Analyze button in
the Nemo Outdoor UI to open the files.
- Export to Nemo Analyze. When an open workbook or open report is selected, the loaded measurement file
is shown twice in the Analyze Measurements database, i.e., there are two number 1 devices in the
measurements database.
Nemo Cloud
- Nemo Navigation Assistant: TOMTOM Bridge navigator unit cannot be used via Bluetooth connection with
Nemo Outdoor application
- Scanner configuration
- GSM TOP-N scanning configuration is not working with Nemo Cloud

- Spectrum scanning cannot be configured via Nemo Cloud
- Rohde & Schwarz scanners are not supported
- Devices without IMEI information cannot be configured and used via Nemo Cloud.
Nemo Media Router

Nemo Media Router for Android
- Viber testing. The following limitations apply:
- Text autocorrection must be disabled from device

- Parallel activities which include UI interaction are not allowed including browser based tests,
screen cast, application start
- Any UI interruptions or user interaction which removes WhatsApp from active application status
will fail the tests
- Call failures and call drops are detected only with MO calls
- Viber transfer failures includes also failures caused by test system
- Voice quality testing is not currently supported

- Proximity sensor and screen saver of the test device prevents Viber testing with Nemo Invex II
HIM/ SHIM modules. Workaround is to connect a headset to the audio connector to disable
proximity sensor. The following HIM/ SHIM modules did not include the audio cable prior delivery
and therefore cannot be used for Viber testing:
• Nemo Invex II handset isolation module for Samsung Galaxy S3. All variants
• Nemo Invex II handset isolation module for Samsung Galaxy S8 / S8+. All variants
• Nemo Invex II handset isolation module for Samsung Galaxy Note 4. All variants
• Nemo Invex II, handset isolation module for Sony Xperia Z3 (D6653)
• Nemo Invex II SHIM Sony Xperia X Performance. All variants
• Nemo Invex II HIM Sony Xperia XZ premium. All variants
• Audio cable will be included with S8/ S8+ and Sony Xperia XZ premium handsets
with the new orders.
- Headset must be connected to handset always when handset is used inside a closure e.g. with
Nemo Backpack and similar products
- WhatsApp testing. The following limitations apply:
- Phone language must be English, Spanish or French
- Parallel activities which include UI interaction are not allowed including browser based tests,
screen cast, application start
- Any UI interruptions or user interaction which removes WhatsApp from active application status
will fail the tests
- Call failures and call drops are detected only with MO calls
- WhatsApp transfer failures includes also failures caused by test system
- Voice quality testing is not currently supported
- Proximity sensor and screen saver of the test device prevents WhatsApp testing with Nemo Invex
II HIM/ SHIM modules. Workaround is to connect a headset to the audio connector to disable
proximity sensor. The following HIM/ SHIM modules did not include the audio cable prior delivery
and therefore cannot be used for WhatsApp testing:
• Nemo Invex II handset isolation module for Samsung Galaxy S8 / S8+. All variants
• Nemo Invex II, handset isolation module for Sony Xperia Z3 (D6653)
• Nemo Invex II SHIM Sony Xperia X Performance. All variants

• Nemo Invex II HIM Sony Xperia XZ premium. All variants
• Audio cable will be included with S8/ S8+ and Sony Xperia XZ premium handsets
with the new orders.
- Headset must be connected to handset always when handset is used inside a closure e.g. with
Nemo Backpack and similar products
- iPERF data transfers
- With SM-G960U (Sprint) iPERF testing returns always “Protocol error or timeout”
- Qualcomm based UEs e.g. Sony ZX Performance G8141:
• UDP iPERF:
o RLC DL throughput shows over two times higher values compared to

application layer throughput
o RLC UL throughput is constantly 0.4Mbps and application layer
throughput reports much higher values
o With DL + UL mode application throughput DL do not report any values
- Samsung Shannon based UEs e.g. Galaxy S7 and S8 series:
• RLC data throughput DL / UL values are not reported with S8 series devices
• TCP iPERF:
• UDP iPERF:
- 22936: Access Point Name (APN) must be defined in the test handset. APN used in the script file is ignored
by NMR application.
- Team Viewer version 11 should be used with the Samsung Galaxy S6 and Note 5 handsets.
- GPS fix source type (Glonass/GPS) cannot be identified when using NMR for GPS data.
- 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 the memory is full.
- Remote TeamViewer UI control and monitoring:
- If the 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 the screen is not
visible. Occasionally TeamViewer connection to the handset fails. Try again.
- Samsung Galaxy S4 mini (GT-I9197) and Samsung Galaxy S7 edge SM-G935F (Optus) do not
support remote control.
- HTTP/HTTPS browsing
- As redirection is allowed with NMR version 2.40 onwards with certain web pages, the browser
may prompt to use the mobile versions of websites instead of the full versions and also ask to add
local weather information, etc. If the user does not select any option, the web page is not loaded.
Therefore, it is important to pretest the web page using the internet browser of the phone before
measurements, including browsing. An alternative method is to change the user agent settings via
the Android browser. In case the handset is inside the Nemo Invex HI module, use a Teamviewer
remote connection to change the settings:
1. In the address bar, type: about:debug and hit return
2. Go to the settings menu and look for the UAString
3. Open up UAString and select desktop

4. Return to your browser. Browser will be seen as a desktop browser when you visit
sites.
- 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.
- WLAN measurements via Nemo Media Router
- WLAN quality is not available
- WLAN measurement is not supported with Nemo Invex HI modules
- Huawei u-vMOS measurements
- Video codec is not available
- PEVQ-S and Netflix measurements via Nemo Media Router
- Video codec is not available
- 22458: Video MOS is not available when test device has IPv6 address assigned
- YouTube measurements via Nemo Media Router
- 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
Nemo Media Router for iOS

- Access Point Name (APN) must be defined in test handset. APN used in the script file is ignored by NMR
application.
Nemo Backpack and Nemo Carrying Case
Issue with hub downstream USB port power. The USB hub occasionally leaves the hub downstream USB port
power off when the hub is started after a long period of being powered down.
Please download the Acroname software package from here:

https://acroname.com/system/files/software/brainstem_dev_kit_mswindows_i386_1.zip
After unzipping the file, you will find a tool called Hubtool under the /bin folder which will allow you to connect
to the hub and check the status of each port. With the Hubtool you can switch on each individual port and save
the configuration (see image below).
Figure 14. Acroname HubTool.
Nemo Multi Lite and Nemo Walker II
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 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 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 Backpack
2.0 chassis. Chassis has not been designed for big handsets, such as, Note 4.
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.
PEVQ-S streaming analysis (PC-based using Flash player)
- 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.
- 22458: Video MOS is not available when test device has IPv6 address assigned
Facebook testing
- Effective from 1st of August 2018. Facebook have tightened developer account conditions and all developer
accounts need to be re-validated. Submission process is ongoing but the following Facebook operations are
not yet approved:
- Get friend list

- Post a status update
- Post an image
- Post a video
- The only operation approved currently is the “Get user feed”. This means that operations listed above will
be blocked by Facebook and cannot be tested with Nemo collection tools.
- Facebook limits the number of status updates and image postings

- 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’s end (daily), new
posts will be posted again automatically
- Currently each app is given an allotment of 200 API calls per user in any given 60-minute window.
Please note that Facebook can change this limit. Please see more details from:
https://developers.facebook.com/docs/graph-api/advanced/rate-limiting
- Custom Facebook test applications offer more flexibilities to test Facebook with drive test tools as
some of the limits seen with normal Facebook apps do not apply, such as number of allowed
postings per hour. Please see the following link for further information:
https://developers.facebook.com/docs/apps
- To create your own Facebook test application, please login to
https://developers.facebook.com/docs/apps/register
- If Facebook benchmarking is done using a commercial laptop, the same user account settings must be used
with all test devices
Instagram testing
- Due to changes in the application login (GDPR policy), Instagram testing cannot be done with Nemo
Outdoor and Nemo Invex II. Issue will be fixed to version 8.3.1.
- Due to changes in the application permission policy and in the application protocol interface (API)
provided by Instagram the following Instagram operations cannot be supported:
- Load user feed
- Load popular feed
- Search media with a tag

- Customers can continue to test accessibility to Instagram service using the Load self- feed operation only.
Old script files can be used but operations that are not supported are ignored.
VoLTE / IMS SMS / ViLTE / VoWiFi/ ViWiFi
- Call type in the call attempt event (CAA) is written as a voice call, not VoLTE or WLAN IMS voice call when a
call is generated via Nemo Outdoor user interface. This is because the call type is unknown at the time of
the call attempt. Call type in the call connection event (CAC) should be observed.
- When enabling WLAN measurement from Nemo Outdoor, a notification Turning on Wi-Fi will turn off USB
Tethering. Continue? is shown in device UI. WLAN will not be activated before the user responds to the
dialog. This dialog will not affect the functionality, the connection between NMR and Nemo Outdoor stays
active.
VQMon
- Audio and video quality metrics are not reported after system change from cellular to Wi-Fi
- Absolute and relative Video/audio quality MOS DL and UL are not reported
USSD testing:
- USSD testing is not supported with Huawei and Shannon based 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.
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.
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 15. Generic USB hub properties
Troubleshooting Data Transfer Issues

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 is recommended to change the UAC settings to Never notify. This can be done via
User Account Control Settings. If the UAC settings cannot be changed it is highly recommended to start Nemo
Outdoor application with administration rights by right-clicking Nemo Outdoor icon and by selecting Run as
administrator.
Figure 16. UAC settings.

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 the device. Go to Connection
properties and check that antivirus NDIS filtering is unchecked.
Figure 17. Network connections.
Figure 18. Antivirus NDIS Filter.
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 data transfers made by Nemo Media Router application
running on Android-based smartphone. If you experience low data throughput with Nemo Media Router
application, please see the chapter Low data throughput with Nemo Media Router application.
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).
When requested throughput is much higher than the actual measured throughput, it 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 19. 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 that is 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 20. 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. Do the
same test again but this time make a connection using Nemo Outdoor.
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.
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, Nemo
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. Nemo 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.
3. Open command prompt by typing “CMD” to ”Search programs and files” field. Right-click and select Run
as administrator.
Figure 21. Run as administrator.
4. To disable auto-tuning type “netsh interface tcp set global autotuning=disabled”. This limits the TCP
window size to 64KB. However, Nemo Outdoor sets its own default 256KB when auto-tuning is
disabled.
5. To increase the maximum TCP window size that auto-tuning uses, type “netsh interface tcp set global
autotuning=highlyrestricted”.
6. 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.
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. From Nemo
Outdoor 7.7.0 onwards, proxy settings can be enabled.
Figure 22. LAN settings.
Low data throughput with Nemo Media Router application
New Android-based smartphones with Android version 6.0 have battery optimization enabled by default. It will
stop some CPU and network activity operating in the background for Android apps, thus saving battery. Battery
optimization is activated when handset is left idle for a period of time, while unplugged and with the screen off.
Battery saving mode interrupt background activity for Android applications such as Nemo Media Router. E.g.
with data transfers this is seen with limited data throughput values. Battery saving option is disabled by default
for the handsets delivered by Keysight Network Testing. However, in case of low data throughput is
experienced the following settings should be checked and battery optimization should be disabled for all
applications. Please note that settings menu varies depending on handset vendor and model. Step by step
instructions per handset can be found from the device configuration guide.
1. Select phone's settings.

2. Select battery from the device list and select battery optimization from the menu icon at the top-right
of the screen.
3. Select all apps from the drop-down menu in the center of the display. Now you'll see all the apps that
are Doze-enabled.
Figure 23. Battery optimization settings.
4. Select Don’t optimize for all apps and then tap Done.
5. Now you're set up.

Nemo - Outdoor - Release Note

Uploaded by

Copyright:

Available Formats

You might also like

Nemo - Outdoor - Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nemo - Outdoor - Release Note

Uploaded by

Copyright:

Available Formats

er’s Manual

• Enhanced video and audio quality measurements

Sony Xperia XZ2 √

New NMR devices

• Samsung Galaxy S9+ SM-G965F

Voice quality support with Exynos based devices

• Samsung Galaxy S9 SM-G960F

Viber connection and status events

Viber Voice Call Attempt

MT Call Attempt, terminated call (CAA)

Viber Voice Call Connected (Ringing)

Viber Voice Call Connected (Answered)

Viber Voice Call Disconnected

Viber Voice Call Disconnected

Viber Voice Call Disconnected

Viber Voice Call Failed

Viber Voice Call Failed

Viber Message Data Attempt

Viber Message Data Connection Success / Request

Viber Message Data Connection Failed

Viber Message Data Complete Success

Viber Message Data Complete Failed

Table 2. Viber trigger points and statistics.

Viber Call Statistics

• Viber call attempt failures

Viber Message Statistics

• Viber connection attempt success rate (%)

Product Code Description

Table 4. NMR 8.30 license options.

Table 5. Compatible versions.

Supported handsets with Nemo Media Router

Product Handset Firmware/ NMR/ Nemo PEVQ-S Screen VQMon, u-vMOS

NTT20091A Samsung G960FXXU1AR 8.21.335 8.2.1.14 Yes Yes No No

NTT20085A Sony MSM8998 8.20.314 8.2.0.10 Yes Yes No Yes

NTT20078A Samsung "MPSS.AT.2.0.c 8.10.273 8.1.0.12 Yes Yes No No

NTT20069A Samsung MPSS.AT.2.0.c2 8.10.273 8.1.0.12 Yes No No No

NTT20075A Samsung G950FXXU1AQ POLQA & PESQ 8.0.0.15 Yes No No Yes

NTT20076A Samsung G955FXXU1AQ 8.00.233 8.0.0.15 Yes No No Yes

NTT40081A Samsung MPSS.TH.2.0.c2 8.01.244 8.0.1.20 No Yes No No

NTT20050A Google MPSS.TH.2.0.2. NMR 7.9.1.220 7.9.1.16 Yes Yes No

NTT40038A Sony MPSS.TH.2.0.c1 NMR 2.52.177 7.8.2.18 Yes with Yes

Not Apple 1.56.00_DEBUG NMR for iOS 7.8.0.8

NA Samsung MPSS.BO.1.0.c 2.10.054 7.4.0.9

Table 6. Supported handsets with Nemo Media Router application.

Table 7. New test devices.

Figure 3. Nemo Cloud Ribbon bar.

Nemo Navigation Assistant

Product Nemo Outdoor

Table 8. Compatible versions.

New component carrier and MIMO metrics

• Total DL PRB usage

Figure 4. LTE CA summary information.

• Total DL PRB usage

• Added support for E-UTRA band 46, TDD 5200, U-NII

• eDRX & PSM information logging

Figure 5. Requested and active eDRX and PSM parameters.

Keysight Spectrum Analyzers and Scanning Receivers

No changes in this release