Nemo Outdoor 7.50 Release: Technical Bulletin & Release Notes

WWW.ANITE.
COM/NEMO
NEMO OUTDOOR 7.50 RELEASE

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

1.1
IR.94 - IMS profile for conversational video service ........................................ 6
1.2
IR.92 - IMS profile for SMS.......................................................................... 6
1.3
Enhanced forcing features with Qualcomm-based UEs..................................... 7
1.4
New dongle support .................................................................................... 8
1.4.1
Migration process for old USB dongle keys ............................................. 9
1.4.2
Migration process for new USB dongle keys ......................................... 11
1.5
Venture scanners ..................................................................................... 12
1.5.1
1.6
Venture MRX3808A/ L RF Measurement Receivers ................................ 12
Nemo Media Router version 2.20................................................................ 12
1.6.1
WLAN measurements ........................................................................ 13
1.6.2
YouTube video streaming .................................................................. 13
1.6.3
HTML browsing ................................................................................ 13
1.6.4
Voice quality audio RX activity status .................................................. 14
1.6.5
Call answering mode......................................................................... 14
1.6.6
Airplane mode ................................................................................. 14
1.6.7
Audio playback................................................................................. 14
1.6.8
NMR version and protocol information ................................................. 14
1.6.9
New NMR handsets ........................................................................... 14
1.6.10 Nemo Media Router licensing options .................................................. 15

1.6.11 Compatibility and update process ....................................................... 15
1.7
Nemo Commander/ Remote enhancements ................................................. 15
1.7.1
Sending measurement files with periodic reports .................................. 16
1.7.2
Manual remote measurement session ................................................. 16
1.7.3
Area-based measurements ................................................................ 16
1.7.4
Integrated TeamViewer ..................................................................... 16
1.7.5
Test device RF cross-checking with user-configurable threshold ............. 16
1.7.6
Navigation ....................................................................................... 16
2 APPLICATIONS AND PROTOCOLS ....................................................................... 19

2.1
Twitter .................................................................................................... 19
2.2
Instagram ............................................................................................... 20
2.3
HTTP PUT ................................................................................................ 21
3 OTHER FEATURES & UPDATES ........................................................................... 22
Page 3
3.1
Measurement pausing when GPS coordinates do not change .......................... 22
3.2
GPS timestamp verification with NMEA devices ............................................ 22
3.3
IP access time and IP termination time parameters for HTTP browsing protocol 22
3.4
PEVQ-S video database files updates .......................................................... 22
3.5
Updates .................................................................................................. 22
3.6
Generic handler enhancements .................................................................. 23
3.6.1
LTE-A 2CC Cat 6 handlers ................................................................. 23
3.6.2
LTE requested throughput estimation .................................................. 23
3.6.3
TTI bundling .................................................................................... 24
3.6.4
GSM RX quality logging from SDCCH channel ....................................... 24
3.7
Qualcomm handler enhancements .............................................................. 25
3.8
HiSilicon handler enhancements ................................................................. 25
3.9
Broadcom handler enhancements ............................................................... 25
3.9.1
Cell ID logging during Cell-DCH UMTS RRC state .................................. 25
3.10 Generic scanner handler enhancements ...................................................... 25

3.10.1 Sweep max and min RX levels ........................................................... 25
3.10.2 Native RBW support .......................................................................... 25
3.11 Nemo FSR1 scanner handler enhancements ................................................ 25
3.11.1 New bands ...................................................................................... 25
3.11.2 SIB decoding ................................................................................... 26
3.12 PCTel scanner handler enhancements ......................................................... 26
3.12.1 PCTel IBflex scanner ......................................................................... 26
3.12.2 PCTel EXflex scanner ........................................................................ 27
3.13 Rohde & Schwarz scanner handler enhancements ........................................ 27
3.13.1 TSMW & TSME ................................................................................. 27
3.13.2 TSMW ............................................................................................. 27
4 NEMO INVEX NEW FEATURES ............................................................................ 28
4.1
Support for Nemo Invex I and Nemo Invex II hardware health information ..... 28
4.2
Nemo Invex status view ............................................................................ 28
5 USER INTERFACE ............................................................................................. 29

5.1
Indoor measurement enhancements ........................................................... 29
5.1.1
Indoor measurement mode ............................................................... 29
5.1.2
Creating markers based on GPS location in Indoor mode ....................... 29
5.1.3
Logging floorplan information to measurement file header ..................... 29
5.2
UI statistics ............................................................................................. 30
5.3
Measurement list based on areas ............................................................... 31
5.4
Improved USSD testing............................................................................. 32
5.5
Scanning ................................................................................................. 32
5.6
Map ........................................................................................................ 32
5.7
Other ...................................................................................................... 32
6 NEW DEVICES ................................................................................................. 33

6.1
Handsets and USB modems ....................................................................... 33
6.2
Scanner receivers .................................................................................... 34
6.3
Supported handsets with Nemo Media Router .............................................. 34
7 QUALCOMM-BASED WCDMA AND CDMA2000 TERMINALS AND DATA CARDS ........... 37

8 COMPUTER HARDWARE AND SOFTWARE REQUIREMENTS ..................................... 38
Page 4
9 DEVICE CONFIGURATION AND WORKSPACE FILES ............................................... 39

10 DISCONTINUED DEVICES & FEATURES ............................................................... 40
11 INSTALLATION ................................................................................................ 41
11.1 Supported operating systems .................................................................... 41
11.2 First-time installation ................................................................................ 41
11.3 Update/Upgrade ....................................................................................... 41
11.4 Uninstallation .......................................................................................... 41
11.5 Dongle runtime drivers ............................................................................. 42
12 LIMITATIONS WITH WINDOWS 8 OPERATING SYSTEM ......................................... 43
13 LIMITATIONS AND ISSUES WITH WINDOWS 7 OPERATING SYSTEM....................... 44
14 FILE FORMAT CHANGES .................................................................................... 45
15 KNOWN ISSUES ............................................................................................... 46
15.1 General and user interface ........................................................................ 46
15.2 Nemo Commander ................................................................................... 47
15.3 Applications and protocols ......................................................................... 47
16 TROUBLESHOOTING DEVICE CONNECTIVITY ISSUES ........................................... 50
17 TROUBLESHOOTING DATA TRANSFER ISSUES ..................................................... 51
17.1 PS connection works but no data ................................................................ 51
17.1.1 Antivirus filtering .............................................................................. 51
17.2 Low data throughputs ............................................................................... 52
17.2.1 All Windows versions ........................................................................ 54
17.2.2 Windows 7 ...................................................................................... 55
17.3 Issues with HTTP browsing testing ............................................................. 57
18 REFERENCES ................................................................................................... 58
19 NEMO TOOLS................................................................................................... 59
Page 5
1 NEW FEATURES
Nemo Outdoor 7.5.0 release includes support for the following new features:
IR.94 - IMS Profile for Conversational Video Service
IR.92- IMS Profile for SMS
Enhanced Forcing Features with Qualcomm Based UEs
New Dongle Support
Venture Scanners
Nemo Media Router Version 2.2
Nemo Commander Enhancements
Applications and Protocols
Qualcomm Handler Enhancements
HiSilicon Handler Enhancements
Broadcom Handler Enhancements
Nemo FSR1 Scanner Handler Enhancements
PcTel Scanner Handler Enhancements
R&S Scanner Handler Enhancements
New Devices
User Interface
Discontinued Devices & Features
1.1 IR.94 - IMS profile for conversational video service

IR.94 is the GSMA/3GPP associations IMS Profile for Conversational Video Service, i.e. video call over
packet switched data. This new service can now be measured with Nemo Outdoor. Nemo Outdoor is
collecting all the key metrics of VoLTE video calls including accessibility, retainability, SIP signalling,
RTP packets for video, and VoIP codecs.
SRVCC information is logged to CALLMODI event including information about the call modification
type and result. VoLTE video call testing is supported with Qualcomm IMS and Samsung IMS clients.
Requires Nemo Outdoor option OD1600-11, IR.94 IMS Video Call. This option also supports voice and
SMS testing over LTE. Handsets using the Samsung IMS client also require the NMR application
installed to the test handset with OD1600-04, NMR Voice Quality Testing option.
Go back to list of new features.
1.2 IR.92 - IMS profile for SMS

IR.92 is the GSMA IMS Profile for SMS, detailing how SMS is sent in 4G/LTE. SMS testing over IMS
provides the SMS message events for send/receive and also SIP messages. MSG events include
Page 6
new IMS SMS message type. SMS over IMS is supported with Qualcomm IMS and Samsung IMS
clients. Requires the Nemo Outdoor option OD1600-10, IR.92 IMS Voice and SMS Option. Handsets
with Samsung IMS client also require the Nemo Media Router application installed to the test
handset with the option OD1600-04, NMR Voice Quality Testing.
1.3 Enhanced forcing features with Qualcomm-based UEs

The updated Qualcomm handler includes the following enhancements to the forcing features:
System lock
o
Band lock
o
This is real hard carrier lock
Works on many terminals, tested with S5, S4 Mini, S4+, Note4, reboot required
UARFCN + Scr. Code lock (NEW!)

Tested with S5, reboot required
EARFCN lock
o
Works on all terminals, no reboot required
UARFCN lock
Works on all terminals, reboot required
Combined EARFCN + PCI lock

o
Tested with Note 3, S4+, S4 mini terminals, reboot required
Note: With newer terminals (S5, Note 4, etc.) supported as well but lock is disabled
on RRC connection release
GSM BCCH lock (NEW!)

o
AMR codec activation

o
Works on all terminals, reboot required
As a reboot is required, it is recommended to use a ~45 s wait command in script files if forcing
commands are used.
Page 7
1.4 New dongle support
The new USB dongle key must be available before updating Nemo Outdoor
application to version 7.5.0 or higher. Nemo Outdoor version 7.5.0 or higher is
not backwards compatible with the old license dongles.
The computer used for the dongle migration must have Nemo Outdoor installed
and connected to the internet.
If the old dongle key contains both Nemo Outdoor and Nemo Analyze licenses,
please do not run the migration tool. Instead, contact nemo.support@anite.com.
Before running the migration tool, please check the TS Expiration date for the
old dongle key from the Nemo Outdoor Help menu (About | License
Information). If your technical support agreement has expired, do not run the
migration tool. Migration can be done only with dongle keys that have a valid TS
agreement. If your TS agreement has expired, please contact Anite Network
Testing, nemo.support@anite.com.
Do not unplug the dongle keys during the migration process. This may
permanently damage the license keys
All fielded dongle keys and licences must be migrated to new one before customers are able to use
Nemo Outdoor version 7.5.0 or higher. To make the migration easier for the customers, Anite
Network Testing has developed a dongle swapping tool that is capable to make the migration in
user convenient way. Old dongle key and the new dongle key must be connected on the same PC,
including also the migration tool installed and then the customer starts migration in the tool. The
tool kills the old dongle and activates the new one and registers the new dongle.
Before starting the migration process please check what kind of dongle key you are currently using
with Nemo Outdoor. If you have the old dongle key shown in Figure 1, please see the instructions in
chapter Migration process for old USB dongle keys.
Figure 1.Old dongle key.

If you have the new dongle key shown in Figure 2, please see the instructions in chapter Migration
process for new USB dongle keys.
Page 8
Figure 2. New dongle key.
1.4.1
Migration process for old USB dongle keys
1. Anite sends an empty dongle (without a product license) automatically to all customers with a valid
TS agreement. The new dongle will be sent to a separately agreed customer address. In case you
have not been contacted by Anite regarding the dongle migration, please contact
nemosupport@anite.com.
2. After receiving the empty dongle, download and install the migration tool from
www.nemo.fi/tools/migrationtool.zip
3. Extract the migration tool zip-file on the computer that has Nemo Outdoor or Nemo Analyze
installed.
4. Plug in both the old and new dongle in your computers USB ports. Both dongles MUST be plugged
in simultaneously.
5. Run the DriverlessMigrationClient.exe file to start the migration tool.
6. Make sure the migration tool identifies both dongles (keys) connected (Time and Time Driverless
dongles).
Page 9
Do not unplug the dongle keys during the migration process. This may
permanently damage the keys.
7. Start the migration tool.
Figure 3.Migration tool.

8. Click the Migrate License button to start the migration process
9. The migration tool reads the license details from the old dongle and sends the details to Anite
Network Testing over the internet.
10. Anite creates a new license with a similar configuration and sends the new license to the migration
tool over the internet.
11. The migration tool activates the new dongle and writes the new license details on the dongle. The
migration tool also tests that the new dongle works properly.
12. After testing that the new dongle works properly, the migration tool deactivates the old dongle and
informs the customer that the migration process was successful and the new dongle with the
product license is ready for use.
13. The migration tool can be now removed and the old dongle key can be disposed of.
Page 10
1.4.2
Migration process for new USB dongle keys
1. Download and install the migration tool from www.nemo.fi/tools/migrationtool.zip

2. Plug in the dongle key to the computer where you installed the migration tool.
Do not unplug the dongle key during the migration process. This may
permanently damage the key.
3. Start the migration tool.
Figure 4. Migration tool.

4. Click the Migrate License button to start the migration process
5. The migration tool reads the license details from the dongle and sends the details to Anite Network
Testing over the internet.
6. Anite creates a new license with a similar configuration and sends the new license to the migration
tool over the internet.
7. The migration tool writes the new license details on the dongle. The migration tool also tests that
the dongle works properly.
8. After testing that the dongle works properly, the migration tool informs the customer that the
migration process was successful and the dongle with the new product license is ready for use.
9. The migration tool can now be removed.
Page 11
1.5 Venture scanners

Venture scanners extend the scanner support with Nemo Outdoor drive test tool. Two new scanning
receivers are supported.
1.5.1 Venture MRX3808A/ L RF Measurement Receivers

Supported technologies are GSM, UMTS, CDMA/ EVDO and LTE FDD & TDD. Basic scanning features
are supported. Requires option OD0700-34, Handler Venture MRX 3808A/ L.
1.6 Nemo Media Router version 2.20

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

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

Cell measurements for WLAN are supported via the NMR application running on Android-based
smartphones. The user has the option to enable/disable WLAN measurements per handset via the
Nemo Outdoor user interface. The following parameters are logged:
Figure 5.WLAN parameters.

WLAN measurement requires NMR option OD0700-38 per test handset.
Note that WLAN measurements can be supported only with test handsets without
any RF isolation modules.
1.6.2 YouTube video streaming

YouTube video streaming was introduced with Nemo Outdoor in 2013. Video streaming testing is
supported by default in Nemo Outdoor and Nemo Invex measurement systems. However video
streaming is performed on a PC or a UIC module with Nemo Invex using VLC player. Each Nemo
Outdoor system can perform one active video streaming connection at a time (one active
connection per CPU or UIC).
With the latest version of the Nemo Media Router application, YouTube video streaming is
supported providing real QoE measurements using the smartphones QoS settings. Nemo Invex
customers will also see benefits as YouTube benchmarking can be done with less UICs lowering the
cost and total power consumption of the measurement equipment.
For further information about the recorded YouTube KPIs please see the YouTube white paper on
our website: http://www.anite.com/businesses/network-testing/white-papers-0#.VNm8sPmUd8E
NMR YouTube video streaming option OD0700-37 is included in the OD1600-05, NMR Data &
Application Testing Option.
1.6.3 HTML browsing

HTML browsing with Nemo Media Router application provides real QoE results. Especially with multi
configurations using multiple test UEs, it provides clear benefits as the same script file can be used
Page 13
with all test UEs. It is no longer necessary to use the routing table modification in Nemo Outdoor to
allow loading the content from different servers. NMR HTML browsing option OD0700-36 is included
in the OD1600-05, NMR Data & Application Testing Option.
1.6.4 Voice quality audio RX activity status

End users are experiencing random audio muting during phone calls. When a call is answered, only
silence can be heard. When audio is lost during a phone call, it usually remains silent until the end
of the call. These calls can also be seen by observing Audio quality MOS scores as the score drops
significantly during silent calls.
Audio RX activity status has been supported earlier only using a separate sound card. Now this
parameter is available via NMR while doing voice quality measurements. During RX mode the voice
quality measurement system continuously monitors the energy of the received signal for each
received audio frame and writes the audio quality signal status to the measurement file. If the
energy of the received signal drops below the specified threshold for a specified amount of time, the
audio quality signal state is set to Not detected. If the energy of the received signal goes above
the specified threshold for a specified amount of time, the audio quality signal state is set to
Detected. The threshold values are fixed.
1.6.5 Call answering mode

Earlier call answering modes were supported only with test UEs without NMR. Now call answering
modes are supported also with test UEs used with NMR.
1.6.6 Airplane mode

Airplane mode (radio on/radio off) commands are now supported also via NMR application. This is
useful for testing attach/PDP context activation procedures.
1.6.7 Audio playback

Audio playback option is supported with voice and video calls. User can select an audio (WAV) file
and enable audio playback. The selected voice file is uploaded to NMR which will then play the audio
in a loop during voice and video call. This feature can be used, for example, with emergency calls to
play a particular audio message in case the call reaches a live operator.
1.6.8 NMR version and protocol information

A new measurement file header event #NMR is logged and contains the NMR application version
information and a list of supported data protocols. This information can be used later on to
determine whether a particular data protocol testing was done with NMR or PC.
1.6.9 New NMR handsets

The handsets shown in the table below are supported with Nemo Media Router:
Page 14
Product
Code
Handset
Firmware
NMR
version
Nemo Outdoor
version (*)
MH1700-45
Samsung Galaxy S5
SM-G900M
MPSS.DI.2.0.1.c2.2-00006M8974AAAAANRZM-1
(AAAAANRZ May 9 2014
21:44:23)
2.20.078
7.5.0.5
Table 6. 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.6.10
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.20:
Product
Code
Option
Description
OD1600-04
NMR Voice Quality Testing

Option
Transfers audio files via the NMR interface to

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

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

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

NOTE! Not available with HI modules
(optional license)
Table 7.NMR 2.20 license options.
1.6.11
Compatibility and update process
Nemo Media Router version 2.20.078 is compatible with Nemo Outdoor 7.5.0.5. 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://www.nemotechnologies.com/index.php?246. File NemoMediaRouter.apk is located under
Nemo Outdoor 7.5.0.5
NMR Data & Application Testing Option can be fetched from NMR license server automatically for all
the currently fielded units purchased with the NMR data & application option. This can be done by
launching the Nemo Media Router 2.20 application on the phone after installation.
1.7 Nemo Commander/ Remote enhancements

All new features requires Nemo Commander version 7.20 or higher and Nemo Outdoor/Nemo Invex
probes with the Remote option.
Page 15
1.7.1 Sending measurement files with periodic reports

New option has been added to the enable sending of measurement files with periodic reports.
Additionally, system ensures that the measurement files are sent always at the end of the session.
1.7.2 Manual remote measurement session

User can start and stop sessions manually during a measurement session period. This is useful, e.g.
in case driver does not arrive to the measurement area on the scheduled time.
1.7.3 Area-based measurements

Measurement session can be triggered to start and stop based on predefined areas. Area-based
sessions are defined in Nemo Commander. Measurement session is automatically started when
entering the area and stopped when leaving the area. Nemo Outdoor output window and report
contain information about areas.
1.7.4 Integrated TeamViewer

Integrated TeamViewer with Nemo Outdoor/ Nemo Invex remote option provides easy access
directly from Nemo Commander to any Nemo Outdoor/Nemo Invex probe on the field giving full
remote access and control.
The TeamViewer application must be installed to the PC as a service. During the installation process
the user defines the password. The TeamViewer ID is sent to Nemo Commander in the status
report. The password must be defined in Nemo Commander manually as the information cannot be
included in the status report. Nemo Outdoor has an option to enable/disable the TeamViewer
integration in Remote mode (only enabled when TeamViewer is installed on the PC).
1.7.5 Test device RF cross-checking with user-configurable

threshold
In order to prevent measurements with missing/incorrect RF antenna connections, a user can
perform RF cross-checking with the test devices connected to Nemo Outdoor.
RXL/RSSI value of each measured channel/carrier is read from each UE and scanner. The value
from each test device including serving cell and neighbor information is compared to the highest
value from all devices. If the measured value is less than X dB below the highest value, a warning
message is displayed to the user. The message includes the channel number and the device
name(s). The offset value X is user-definable.
In Remote mode with Nemo Commander the offset value X is read from the configuration file and
the level check warning is shown in Nemo Commander.
1.7.6 Navigation
Navigation is a new optional feature in Nemo Commander. The drive test route can be planned and
generated by Nemo Commander using OpenStreetMap maps. The drive test route can be defined
without any limitations to the number of waypoints but up to 24 waypoints can be included in the
route sent to the Navigon application. If the drive test route has more than 24 waypoints, multiple
routes are used. Nemo Commander generates a URL link for the drive test route(s) that can be sent
to the driver by email directly from Nemo Commander. By using the iPhone or iPad, driver clicks the
URL link in the email to launch the Navigon application on the iPhone or iPad. iPhone and iPad are
Page 16
available also from Anite Network Testing as optional items. Navigon application must be purchased
separately from App Store.
Requirements:
Nemo Commander
Nemo Outdoor or Nemo Invex with Remote option
iPhone or iPad with Navigon application and email account
Table 8. Predefined drive test route in Nemo Commander.
Table 9. Drive test route in Navigon.
Page 17
1.7.6.1 Ordering information

Product
Option
Description
OD1100-07
iPhone 6
Includes:
(GSM)
Plus
OD1100-08
Navigation
(CDMA)
HW Package
Code
Apple iPhone 6 Plus (16GB)

Model A1524 (GSM), (MH0001-01)
Model A1524 (CDMA), (MH0001-02)
Hama USB Car Charger, 5V/2.4 A,
(419007-14)
Arkon MG279 Universal Smartphone
Mount iPhone 6 Plus Holder for
iPhone and Android Smartphones
(OD0100-18)
OD1100-09
iPad Mini 3
Includes:
Navigation
HW Package
Apple iPAD Mini 3 WiFi + Cellular

(16GB)
Model A1600 (MH0001-03)
Hama USB Car Charger, 5V/2.4 A,
(419007-14)
Arkon SM6-CM117 - iPad Mini
Windshield Mount with Extending
Mount Arm (OD0100-19)
Table 10. Navigation HW packages.

Page 18
2 APPLICATIONS AND PROTOCOLS
2.1 Twitter
Twitter is an online social networking service that enables users to send and read short 140character messages called "tweets". Registered users can read and post tweets, but unregistered
users can only read them. Users access Twitter through the website interface, SMS, or mobile
device application.
Twitter has been ranked as the third most used social network based on their count of 6 million
unique monthly visitors and 55 million monthly visits. That is why Twitter has been selected as one
of the new applications to be supported with Nemo tools. Now operators have the possibility to test
and benchmark the Twitter application in their network.
From the point of view of the end-user QoS, there are some characteristics that should be captured
by Twitter testing. The first one, corresponding to the service accessibility category, should
measure whether the access to Twitter account and access token is successful or not after the user
request. Another important quality aspect is that the Twitter operations do not get stuck at some
point. The service retainability category should, therefore, contain a KPI that measures the ability of
the different Twitter operations to complete. Finally, under service integrity, the KPIs should
contemplate quality aspects. Therefore, these KPIs should evaluate the delayed time experienced.
Application data throughput is also recorded but due to quite low data rates used by Twitter, it is
not as an important KPI as service accessibility, service retainability, and times experienced.
Twitter testing is supported with multi configurations with a single CPU. Protocol runs on a PC or a
UIC module with Nemo Invex. Twitter testing can be done manually or with script files. Before
starting the test, a Twitter login must be done using the test handset UI.
The following statistics are recorded in addition to DNS query, network availability, and accessibility
(PS data connections and data transfer statistics). For the access and retainability failures, Twitter
specific protocol errors are written to the log file.
Table 11. Twitter statistics.
Page 19
The following Twitter operations are supported:
Load home page
Load profile
Follow Twitter feed
Text tweet
Photo tweet
NOTE! Twitter has the following technical limits for accounts. These must be taken into account
when doing Twitter testing with Nemo Tools:
Direct messages (daily): The limit is 1,000 messages sent per day.
Tweets: 2,400 per day. The daily update limit is further broken down into smaller limits for
semi-hourly intervals. Retweets are counted as Tweets.
Changes to account email: Four per hour.
Following (daily): The technical follow limit is 1,000 per day. Please note that this is a
technical account limit only, and there are additional rules prohibiting aggressive following
behavior. Details about following limits and prohibited behavior are on Twitters Follow
Limits and Best Practices page.
Following (account-based): Once an account is following 2,000 other users, additional follow
attempts are limited by account-specific ratios.
These limits include actions from all devices, including web, mobile, phone, API, etc. API
requests from all third-party applications are tracked against the hourly API limit. People
who use multiple third-party applications with their account will therefore reach the API
limit more quickly. For more information on this topic, please see Twitters API Rate Limiting
page.
These limits may be temporarily reduced during periods of heavy site usage.
2.2 Instagram
Instagram is an online mobile photo-sharing, video-sharing and social networking service that
enables its users to take pictures and videos, and share them on a variety of social networking
platforms, such as Facebook, Twitter, Tumblr, and Flickr. The maximum duration for Instagram
videos is 15 seconds. In December 2014, Instagram co-founder Kevin Systrom announced that
Instagram has 300 million users accessing the site per month. [4]
From the point of view of the end-user QoS, the same characteristics are captured as with Twitter
testing: service accessibility, service retainability, and service integrity.
Instagram testing is supported with multi configurations with a single CPU. Protocol runs on a PC or
a UIC module with Nemo Invex. Instagram testing can be done manually or with script files. Before
starting the test, Instagram login must be done using the test handset UI.
The following statistics are recorded in addition to DNS query, network availability, and accessibility
(PS data connections and data transfer statistics). For the access and retainability failures,
Instagram-specific protocol errors are written to the log file.
Page 20
Instagram testing supports the following operations:
Load user feed
Load self feed
Load popular feed
Search media with a tag
2.3 HTTP PUT

A new option has been added to the user interface to allow the user to use both POST and PUT
operations to upload files with the HTTP protocol.
HTTP POST
Requests that the server accepts the entity enclosed in the request as a new subordinate of the web
resource identified by the URI. The data POSTed might be, for example, an annotation for existing
resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of
data that is the result of submitting a web form to a data-handling process; or an item to add to a
database.
HTTP PUT
Requests that the enclosed entity be stored under the supplied URI. If the URI refers to an already
existing resource, it is modified; if the URI does not point to an existing resource, then the server
can create the resource with that UR. [2]
Page 21
3 OTHER FEATURES & UPDATES
3.1 Measurement pausing when GPS coordinates do not change

New option has been added that allows the user to enable a trigger that checks if the latitude and
longitude of N consecutive GPS events are identical (where N is user-configurable value).
When the trigger condition is met, measurement is paused, ERR-event is written, and a notification
message is displayed to the user. Pause is automatically released and script continues normally
when GPS coordinates are updated.
3.2 GPS timestamp verification with NMEA devices

Real time verification continuously stores the timestamp of three most recent GPS messages and
checks that the timestamps are increasing and the timestamp increment matches the difference
between the message arrival times. If the verification fails, Time Drifting information is written to
the GPS event.
3.3 IP access time and IP termination time parameters for HTTP

browsing protocol
Enables the calculation of HTTP Session Time (from first [SYN] to the last data packet).
3.4 PEVQ-S video database files updates

PEVQ-S database corresponding to each test video is generated and supplied by OPTICOM.
Physically the PEVQ-S database is located on the same computer where Nemo Outdoor is running.
With Nemo Invex files are located in the UICs. The required PEVQ-S database (.sqlite) and HTML
files for each video are separated from the Nemo Outdoor installation package. Files must be stored
to the Nemo Tools\Video Files folder. OPTICOM provides an updated version of the database to the
customers in case of any changes in the video quality layers or container formats at the YouTube
servers.
With the new update functionality, new video files can be fetched using Nemo Outdoor user
interface. It should be noted that PEVQ-S video database file updates are available only for the
customers who have purchased and have valid annual PEVQ-S Server Access option (OD0700-31).
3.5 Updates
Page 22
Facebook Graph API upgrade from version 1.0 to 2.0
CodeJock Toolkit upgrade to version 16.4.0
3.6 Generic handler enhancements

3.6.1 LTE-A 2CC Cat 6 handlers
Qualcomm LTE-A 2CC Cat 6 handler has been changed. Earlier with LTE-A Cat 6 UEs without a
compatible handler, most of the parameters were n/a. The updated Qualcomm LTE-A 2CC Cat 6 is
now required to be able to log LTE secondary cell parameters with Cat 6 UEs. Primary cell
parameters can be now logged and viewed normally even if the base Qualcomm LTE license is only
active. The same implementation applies also to HiSilicon LTE handlers.
UE Category
Handler/ License
Parameters Logged
Cat 4 or Cat 6
Qualcomm LTE FDD

HiSilicon Balong 710 LTE
Logging everything except LTE

SCell parameters
Qualcomm LTE-A CA 2CC

Cat.4
Log everything including

parameters for one LTE SCell
Cat 4
HiSilicon Balong 720 LTE-A

2CC Cat.4
Cat 6

Cat.4
Log everything except LTE

SCell parameters

2CC Cat.4
Cat 4 or Cat 6

Cat.6
Log everything including

parameters for one LTE SCell

2CC Cat.6
User is notified if a Cat 6 device is used without the LTE-A 2CC Cat 6 license.
3.6.2 LTE requested throughput estimation

LTE requested throughput estimation is the new parameter calculated with all LTE handlers
(Qualcomm, HiSilicon, Broadcomm, and Nvidia).
Computational throughput is based on the rank indicator, used bandwidth, wideband CQIs for
codeword 1 and 1 and eNodeB DL configuration assuming that all PDSCH resources are allocated for
the UE. As the LTE requested throughput is a computional value, it is possible that computational
throughput is lower than the actual achieved data throughput of the UE. This is due to the reason
that the first three symbols are assumed for PDCCH control signaling.
LTE requested throughput is the data throughput that would have been achieved if the network had
sent the link adaptation parameters defined by the CQI. Parameter is written to the Channel quality
indicator event (CQI).
In the example below the LTE requested throughput value ~83Mbs is constantly higher than the
actual measured data throughput ~38Mbs. Data throughput in this case is limited by the scheduler
or there is a problem in the public internet/server as the UE is not receiving any data. SNR is in
decent level but PRB utilization is 46.5%. Constantly low PRB allocation values can also indicate a
bottleneck in the transmission path before radio.
Page 23
Table 12. LTE requested data throughput.

3.6.3 TTI bundling

TTI bundling information is written to the Channel Info event with values Disabled or Enabled.
TTI bundling is an LTE feature to improve coverage at cell edge or in poor radio conditions. UE has
limited power in uplink (only 23dBm for LTE) which can result in many re-transmissions at cell edge
(poor radio). Re-transmission means delay and control plan overhead which may not be acceptable
for certain services like VoLTE. HARQ is a process where receiver combines the new transmission
every time with previous erroneous data. There is one drawback however, that it can result in delay
and too much control overhead in case of poor radio conditions if the sender has to attempt many
transmissions. With TTI bundling the data is sent with few versions (redundancy versions) of the
same set of bits in consecutive TTI and eNB sends back Ack when it successfully decodes the bits.
[1]
3.6.4 GSM RX quality logging from SDCCH channel

Generic implementation for all handlers supporting GSM RXQ full and sub parameters. The RXQ is
now logged also from SDCCH channel. Implemented to Qualcomm, Broadcom, and legacy Nokia
NTM3 handlers.
Page 24
3.7 Qualcomm handler enhancements

Qualcomm handler includes the enhancements mentioned in the chapter 3.6 and error corrections.
Please see the readme.html located in the installation folder of Nemo Outdoor for a list of error
corrections.
3.8 HiSilicon handler enhancements

UE can be forced to a barred LTE cell. UE reads SIB1 from a barred LTE cell when cell barring is not
set to ignore. It may take up to 5 minutes for the UE to read the SIB1 again from that same cell.
The cell barring forcing status cannot be read from the device so it is not updated in LOCK event
and Nemo Outdoor UI when a device is started.
Support for LTE detected TX antenna ports parameter.
Please see the readme.html located in the installation folder of Nemo Outdoor for a list of error
corrections.
3.9 Broadcom handler enhancements

3.9.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.
3.10 Generic scanner handler enhancements

3.10.1
Sweep max and min RX levels
Sweep maximum and sweep minimum RX level values per measured bandwidth are logged with
spectrum scanning. New parameters are logged to Spectrum Scanning Result event
(SPECTRUMSCAN).
3.10.2
Native RBW support
The sample count parameter was used to determine the sample count measured for the given
frequency range. As the support for Anritsu MS2717B analyzer has been discontinued also the
sample count parameter has been removed from the spectrum scanning settings. Sample count has
been replaced with the native RBWs supported with the different scanning receivers.
3.11 Nemo FSR1 scanner handler enhancements

3.11.1
New bands
Following new bands have been added to the Nemo FSR1 handler.
Page 25
Frequency MHz (DL)
Band
420- 493
CDMA Band class 5
Frequency MHz (DL)
Band
462.5 467.5
E-UTRA Band 31
728 746
CDMA Band class 19
746 758
CDMA Band class 7
757 769
CDMA Band class 18
851 940
CDMA Band class 10
860 875
E-UTRA Band 18
875 885
E-UTRA Band 6
860 894
CDMA Band class 0
915 921
CDMA Band class 12
832 870
CDMA Band class 3
1844.9 - 1879.9
E-UTRA Band 9
2180 2200
E-UTRA Band 23, CDMA Band class 21
2624 2690
CDMA Band class 16
3400 3600
E-UTRA Band 42
3510 3590
E-UTRA Band 22
3600 3800
E-UTRA Band 43
Table 13. New bands for Nemo FSR1.
3.11.2
SIB decoding
SIB1 message decoding is supported with Nemo FSR1 firmware version 04.04.00 or higher. SIB2+
messages are not decoded.
3.12 PCTel scanner handler enhancements

3.12.1
PCTel IBflex scanner
The following systems and bands have been added:
Page 26
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).
3.12.2
PCTel EXflex scanner
The following systems and bands have been added:
LTE TDD E-UTRA bands: 42 (3400 3600MHz) and 43 (3600 3800MHz).
3.13 Rohde & Schwarz scanner handler enhancements

3.13.1
TSMW & TSME
Vicom interface version 15.30 supported.
3.13.2
TSMW
New radio channel data logging added. The following detailed radio channel data is logged:
UMTS CIR
LTE CIR
LTE MIMO matrix
Values are written to a separate binary file due to the excessive amount of data. Playback of the file
is not supported. This feature is intended for the customers using the Propsim radio channel
emulators. Requires license option OD0700-35, R&S TSMW Radio Channel Data Logging.
Page 27
4 NEMO INVEX NEW FEATURES
4.1 Support for Nemo Invex I and Nemo Invex II hardware health
information
The Nemo Invex hardware health information is logged to file in real time. New Nemo Invex Health
Information event (IHI) includes the voltage, current, and temperature information for the chassis
and UIC. Information about the chassis battery status is also collected including voltage, current,
and charging state. With Nemo Invex II information is collected also for HIM modules.
4.2 Nemo Invex status view

The existing Nemo Invex Server status has been replaced with a new Nemo Invex status view that
displays the physical configuration of the Nemo Invex system. Both Nemo Invex I and Nemo Invex
II systems are supported.
Nemo Invex I system consists of one chassis with 13 slots and Nemo Invex II system consists of up
to five chassis with 13 slots. The view shows each chassis and allows the user to arrange the
chassis layout (stacked or side-by-side) with drag and drop. For each chassis the view shows the
modules connected in each slot of the chassis. The following information is displayed: chassis
number and module type (UIC, HIM, UIM, SMM and HIM with device name).
User can select a module to display detailed information in a separate window/panel. View shows
hardware alerts and indicates the source module from which the alert occurred. View also shows
alerts, such as high voltage, high voltage shutdown, low voltage, battery operation, battery voltage
low, and battery shutdown.
Page 28
5 USER INTERFACE
5.1 Indoor measurement enhancements

5.1.1 Indoor measurement mode
New indoor measurement mode selection has been added to the measurement menu and main
toolbar to ensure that indoor measurements are done in a correct way and that all the files related
to the particular indoor measurement session are available. These new rules set some restrictions
on the indoor measurement itself, but save time during post-processing as all the files related to
the particular indoor measurement session are package together and are correct. In indoor mode
the following new functionality has been implemented:
Measurement cannot be started until user has Indoor window open and a floorplan loaded
When the measurement is started, the user is prompted to select the starting position in
the Indoor window. The selected location is then used to automatically create the first
marker.
Measurement archive compression is enabled automatically in Indoor mode
It is not allowed to change the floorplan file or current floor layer during measurement. To
change the floorplan file or current floor measurement must be stopped first
5.1.2 Creating markers based on GPS location in Indoor mode

Following new functionality has been added to indoor maps. When the measurement is done in
indoor mode and the current floorplan uses real (georeferenced) coordinates, the GPS location
received from the device is displayed with a position icon in the Indoor window. Instead of placing a
marker manually in the floorplan, user can add georeferenced markers based on current GPS
coordinates using the indoor map toolbar or spacebar. When using a map without real GPS
coordinates, the GPS marker tool is not available.
5.1.3 Logging floorplan information to measurement file header

The following information is logged to measurement the file header (#FLOORPLAN) in indoor
mode:
Table 14.Floorplan information.
Page 29
5.2 UI statistics
Following new VoLTE voice statistics have been added:

o
VoLTE calls
VoLTE calls alerting
Ratio of IMS Registration attempts/ failures
VoLTE call disconnects (dropped)
Time between call attempt to call connection when in LTE
IMS Registration Failure Rate
Time between call attempt to call connection
LTE call setup time (ms)
Time between VoLTE call attempt to VoLTE call connection
Overall Call Setup Time (ms)
Ratio of all call attempt failures/ all call attempts in all systems
VoLTE Call Setup Time (ms)
Ratio of call attempt failures/ call attempts in LTE
Overall call accessibility
Ratio of VoLTE access failures / VoLTE calls
LTE call accessibility (%)
Number of call attempt failures
VoLTE LTE accessibility (%)
Number of alerting VoLTE calls
VoLTE call attempt failures
Number of VoLTE calls
Number of dropped VoLTE calls
VoLTE call drop rate (%)
Ratio of VoLTE call disconnects (drops) / VoLTE call connections with

alerting state
Overall calls
Overall call disconnects (dropped)
Ratio of all call disconnects (drops) / all call connections with alerting state
VoLTE intra LTE handover failures
Page 30
Number of all dropped calls in all systems
Overall call drop rate (%)
Number of all voice calls
Number of handover failures during intra LTE HO
VoLTEe Intra LTE Handover Failure Rate (%)
VoLTE Intra LTE Interruption Time (ms)
Time between Intra LTE HO attempt to LTE HO success
SRVCC failures (RAN view)
Ratio of Volte Intra LTE HO Failures / VoLTE Intra HO Attempts
Number of failed Inter-system Handovers from LTE
SRVCC failure rate (RAN view) (%)
Ratio of Inter-system handovers failures/ Inter system handover attempts

from LTE
SRVCC Interruption Time (ms)
Time between Handover to UTRAN Command to Handover UTRAN Complete

messages
VoLTE POLQA DL average
VoLTE POLQA DL average before SRVCC (to match OD naming convention)
Average POLQA DL score per VoLTE call
Average POLQA DL score per VoLTE call before SRVCC
Table grid support for statistical results

o
Distribution statistics can be displayed also in the table grid view in addition to the
parameter grid
Call answer time

o
Time from call attempt (CAA) to answered state (CAC3)
Call attempt time correction parameter

o
New statistics parameter calculating delay from paging to ALERTING and paging to
CONNECT is calculated. Value is written to CAA event.
MTC call setup time calculation

o
New parameter written to the CAA event that indicates the delay from the first
received paging message to the CAA event (SETUP message). Implemented for
GSM, UMTS, and LTE (CS fallback).
5.3 Measurement list based on areas

Area-based measurements are now supported with measurement lists. User can define
measurement areas to be used with measurement lists. User has the option to define rectangular
and polygonal trigger areas and blocked areas using OpenStreetMap maps. With trigger areas
measurement is allowed and with blocked areas measurement is put on pause. Measurement is also
paused if GPS fix is lost for a predefined time (e.g. 20 seconds). Measurement is resumed when
entering a trigger area again.
Pause logic and areas work as follows:
Only trigger areas are defined: measurement is allowed in these areas, other areas are
considered to be blocked, i.e. measurement is not allowed
Page 31
Only blocked areas are defined: measurement is not allowed in blocked areas, other areas
are considered to be trigger areas, i.e. measurement is allowed
5.4 Improved USSD testing

USSD message sending support has been extended to support sending of numeric sequences during
a single USSD session.
5.5 Scanning
Updated E-UTRA bands

o
Updated spectrum scanning sets for all E-UTRA UL and DL bands
LTE scanning configuration

o
Dialog checks that either sync or reference signal options are selected. Error
message is displayed if both options are unselected
5.6 Map
Multiple values can be shown as a labels next to the route line
Separate color for current serving cell BTS icons can be configured in map view
5.7 Other
Data transfer server hostname checking has been modified to ignore devices that use Nemo
Media Router (NMR). Devices that use NMR can use the same hostname/address than other
devices without problems.
Notifications: Event triggering ruleset syntax has been extended to support OR-operation
between rules as well as grouping and mixing of AND and OR rule combinations. For
example, the following notification rule can be done:
o
RSRP (pcell) is greater than or equal to -100 AND packet state is equal to active)
OR E-UTRAN carrier RSSI (pcell) is greater than or equal to -62.
Page 32
6 NEW DEVICES
For a complete list of supported devices, please see the separate document Nemo Outdoor 7.5.0.5
Compatible Devices.pdf.
Do not upgrade, root, or reflash your measurement terminal firmware. Doing so will
cause the terminal to permanently lose its measurement capability!
6.1 Handsets and USB modems

Product
Code
MH1700-45
Handset
Samsung
Galaxy S5
SM-G900M
Dev. Capability
Handler
# Verified
UEs/ CPU
FW version
LTE FDD
700/800/850/900/1800/
1900/2100/AWS/2600
(E-UTRA bands 17, 20, 5,
8, 3, 2, 1, 4, 7)
Qualcomm
LTE-A
FDD
1 (without
NMR)
MPSS.DI.2.0.1.c2.200006M8974AAAAANRZM-1
(AAAAANRZ May 9
2014 21:44:23)
SAMSUNG USB
Drive for Mobile
Phones 1.5.45.0
Qualcomm
LTE-A
FDD Cat 4
MPSS.DI.3.0.c9.100005M8974AAAAANAZM-1
(AAAAANAZ Aug 26
2014 04:41:32)
2.1.0.82
Cat4
Driver
WCDMA 850/900/1900/
2100
Quad band GSM
HSPA 42.2/5.76
LTE Cat 6
MH1600-01
Sony Xperia
Z3 D6603
LTE FDD
700c/700bc/800/850/900
/1800/1900/2100/AWS/2
600
(E-UTRA bands 13, 17,
20, 5, 8, 3, 2, 1, 4, 7)
LTE UE Cat 4
WCDMA
850/900/1900/2100/AW
S
HSDPA UE Cat 24, HSUPA
UE Cat 6
GSM 850/900/1800/1900
MH1600-02
Sony Xperia
Z3 D6653
LTE FDD
700/850/900/1800/2100
/2600
LTE TDD 2300
(E-UTRA bands 28, 5, 8,
3, 1, 7, 40)
LTE UE Cat 4
WCDMA
850/900/1900/2100
HSDPA UE Cat 24, HSUPA
UE Cat 6
GSM 850/900/1800/1900
Qualcomm
LTE-A
FDD Cat 4
MPSS.DI.3.0.c9.100022M8974AAAAANAZM-1
(AAAAANAZ Nov 26
2014 03:27:54)
2.1.0.82
NA
Netgear
790S
LTE-A
700/900/1800/2100/260
0 MHz (E-UTRA bands 1,
3, 7, 8 and 28
LTE Carrier aggregation
Qualcomm
LTE-A
FDD Cat 6
MPSS.BO.1.0.r10.400027M9635TAAAANAZMC1032805
(C1032805 Oct 16
AC78xSDrivers_B
3978_3.exe
(UE SIM
locked)
Page 33
Product
Code
Handset
Dev. Capability
Handler
# Verified
UEs/ CPU
on bands 3+28, 28+7,

3+7 and 7+7
FW version
2014 21:23:57)
WCDMA
850/900/1900/2100 MHz
Table 15. New supported UEs.
6.2 Scanner receivers

Product
Code
Scanner
Handler
# Verified
scanners/
CPU
FW version
MS0900-00
Venture
MRX3808A
RF
Measurement
Receiver
Venture
MRX A/L
MRX3808A,
SG53100104,
2014080714
No driver
(requires Java SE
Development Kit
7u67)
MS0900-01
Venture
MRX3808L
RF
Measurement
Receiver
Venture
MRX A/L
MRX3808L,
US14400001,
2014080714
No driver
(requires Java SE
Development Kit
7u67)
MRX3808L,
US14400001,
2014080714
Driver
Table 16. New supported scanners.
6.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-45
Samsung Galaxy S5
SM-G900M
21:44:23)
2.20.078
7.5.0.5
MH1700-39
Samsung Galaxy
Note 4
MPSS.BO.1.0.r10-00108M9635TAARANAZM1.5514.1 (TAARANAZ Sep

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

4 2014 16:47:00)
2.11.060
7.4.1.13
2.11.060
7.4.1.13
(Metro PCS)
MPSS.DI.2.0.1.c2-00055M8974AAAAANRZM-1
19:27:09)
Samsung Galaxy S5
MPSS.DI.2.0.1.c2.2-
2.11.060
7.4.1.13
SM-N910F
MH1700-40
Samsung Galaxy
Note 4
SM-N910G
MH1700-41
Samsung Galaxy S5
SM-G900T1
MH1700-42
Page 34
Driver
Product
Code
Handset
Firmware
SM-G900R4
00006M8974AAAAANRZM-1
(AAAAANRZ Mar 31 2014
01:04:01)
(US Cellular)
NMR version (*)
Nemo Outdoor
version (*)
MH1700-35
Samsung Galaxy S5
4G+ SM-G901F
MPSS.BO.1.0.c1-00091M9635TAARANAZM-1
(TAARANAZ Aug 11 2014
11:59:20)
2.10.054
7.4.0.9 (Data only,

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

15 2013 11:32:02)
1.10.015
7.2.0.6
2.00.034
7.3.0.6
MH1700-10
Samsung Galaxy
S4+ (GT-i9506)
M8974A-AAAANAZM1.0.180095 (AAAAANAZ
Dec 12 2013 16:26:28)
Android 4.3
2.00.034
7.3.0.6
MH1700-17
Samsung Galaxy
Note 3 (SM-N900T)
SET_BY_CM (AAAAANAZ
Sep 13 2013 18:20:25)
2.00.034
7.3.0.6
MH1700-19
Samsung Galaxy S4
Mini (SPH-L520
Sprint)
M8930B-AAAATBZM6.0.01049 (BBAAATBZ
Nov 4 2013 20:22:08)
2.00.034
7.3.0.6
Table 17. 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.
Page 35
(*) with initial release.

Page 36
7 QUALCOMM-BASED WCDMA AND

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

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

WORKSPACE FILES
Device configuration and workspace files made by Nemo Outdoor 7.4.x are fully compatible with
Nemo Outdoor 7.5.x.
Page 39
10 DISCONTINUED DEVICES &

FEATURES
Anite Network Testing announced end of sales and end of life for the software handlers listed below
on 1st of September 2014. This announcement applied to the Nemo Outdoor version 7.5.0. The last
version supporting the software handlers & devices listed below is Nemo Outdoor version 7.4.0.
Customers using these products are kindly requested to contact Anite Network Testing
(sales@anite.com) or local sales representatives for further information about the upgrades.
Product Code
Handler SW/ Device
312002-00, 312022-00
Nokia 6230, 6230i, 6230US
320033-00
312001-00
Nokia 6630
399004-00, 399006-00
Nokia 6680 (ENG/ CH)
312024-00
Nokia 6280/ 6282
312016-00
Nokia N80/ N80US/ N92/ N75
313076-00
Nokia 3500/ 3500US
313018-00
Nokia 6086
312032-00
Nokia 6125/ Nokia 6136
312037-00
Nokia 7376
312030-00, 312006-00, 313075-00
Motorola Exxx/ Vxxx series
312004-02, 320077-08
LG L1000/ L2000 (LTE)
313007-00,
RunCom WiMAX
320080-03
Samsung LTE
312029-00
Handler SW for Anritsu MS2721B
Table 18. Discontinued handlers/ devices.
Page 40
11 INSTALLATION
11.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.
11.2 First-time installation
Note that the installation must be run under Administrator account or other user
account with administrative privileges. Nemo Outdoor setup 7.5.0.5.exe includes
also the IP packet capturing monitoring.
Start Windows and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D).
Copy paste the files to your PC. Select Start | Run in the Windows Status bar. Type D:\Nemo
Outdoor 7.x\Nemo Outdoor x.xx.x in the Open field (xx refers to the version number). Run the
setup.exe and click the OK button. After the installation program starts, follow the instructions on
your screen. NOTE! When the Nemo Outdoor software installation is complete, you will need to
restart the computer.
11.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.5.x installation can be ran.
Nemo Outdoor setup 7.5.0.5.exe includes also the IP packet capturing monitoring.
Start Windows and insert the Nemo Outdoor USB memory flash drive in your PC (e.g. drive D).
Copy paste the files to your PC. Select Start | Run in the Windows Status bar. Type D:\Nemo
Outdoor7\Nemo Outdoor x.xx.xx in the Open field (xx refers to the version number). Run the
setup.exe and click the OK button. After the Installation program starts, follow the instructions on
your screen. NOTE! With Nemo Outdoor 6.21 or earlier version the copy protection key must be
attached to USB port during the installation and uninstallation when asked. When the Nemo
Outdoor software installation is complete, you will need to restart the computer.
11.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
Page 41
uninstallation. When the Nemo Outdoor software uninstallation is complete, you will need to restart
the computer.
11.5 Dongle runtime drivers
Note that the Nemo Outdoor version 7.5.x or higher do not include dongle runtime
driver as the new dongle key is driveless. In case software license is used with Nemo
Outdoor application runtime driver can be installed from http://www.safenetinc.com/sentineldownloads/
Page 42
12 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
Driver version: 23.003.07.00.03
Nokia C7-00
Driver version: 7.1.101.0
Nokia 500
Nokia Lumia
920
Driver version : Qualcomm HS-USB Modem 9001 v2.1.0.5

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

1.5.18.0
Sierra 320U
PcTel MX
MX winusb
PcTel EX
2.1.1.0
(RM-821)
Terratec DMX 6Fire sound card is not compatible with Windows 8 operating system at the time of
release
Page 43
Nemo Walker II can be used with up to six UEs
13 LIMITATIONS AND ISSUES WITH

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

Other limitations:
Debug logging needs administrative privileges if User Account Control Settings (UAC) is
enabled. It is recommended to change UAC settings to Never notify. This can be done
via User Account Control Settings
If UAC is set to always notify it might cause issues with data testing. PS connection can
be established but data transfer cannot be done. Its recommended to change UAC
settings to Never notify. This can be done via User Account Control Settings
Table 19. UAC settings.
Page 44
14 FILE FORMAT CHANGES
Nemo Outdoor 7.5. supports the Nemo file format version 2.22 including the following updates and
changes:
Added support for NMR (Nemo Media Router) information. (#NMR)
Added support for Invex health information. (IHI)
Added support for floorplan information. (#FLOORPLAN)
Added support for GPS status parameter. (GPS)
Added support for first indication about call to CAA time difference. (CAA)
Added support for dropbox application test protocol. (DAA, DAF, DAC, DAD, DREQ, DCOMP,
DRATE)
Added support for security protocol and authentication scheme. (DAA)
Added support for IMS video call. (CAA, CAF, CAC, CAD, VOIPI, RTPJITTER)
Added support for IMS message sending and receiving. (MSGA, MSGS, MSGF)
Added support for call modification indication. (CALLMODI)
Added support for LTE TTI bundling parameter. (CHI)
Added support for secondary carrier LTE TDD special subframe configuration parameter. (CHI)
Added support for USSD message sequences. (MSGA, MSGS, MSGF)
Added support for SMS over IMS measurements. (MSGA, MSGS, MSGF)
Added support for cdmaOne, CDMA 1x, and EVDO bands 13, 14, 16, 18, 19, and 21.
Added support for GSM C/I, CDMA/EVDO delay spread, and LTE PRB scanning option for scanning
configuration. (SCANCONFIG)
Added support for LTE pilot measurement mode parameter for scanning configuration.
(SCANCONFIG)
Added support for CDMA/EVDO pilot increment parameter for scanning configuration.
(SCANCONFIG)
Added support for minimum and maximum RX level spectrum scan measurements.
(SPECTRUMSCAN)
Changed VoLTE call type to IMS voice call type.
Fixed UE based OTDOA position report type to NW based OTDOA. (POSI)
Page 45
15 KNOWN ISSUES
Test device related known issues for UEs, scanners, and other devices are listed in a separate
document: (Nemo_Outdoor_7.5.0.5_Test_Device_Technical_Notes_Feb_2015.pdf).
15.1 General and user interface
Note that if there is a system that measures acceleration in the laptop and which
causes the hard disk to stop when jolted, it should be turned off. Otherwise there
may be breaks in the measurement files. With voice quality testing this can be seen
with missing MOS scores, and with other test devices with gaps in the measurement
results
Table 20. Lenovo active protection system properties.
Running Nemo Outdoor setup directly from the USB flash memory wont work. Workaround
is to copy the files to PC prior running the setup
Download stops responding. Applies to Windows Vista and Windows 7 operating systems.
When you try to download a file, the download stops responding and then times out. The
problem occurs when you use a USB modem that has a data transfer speed that is faster
than or equal to 240 kilobits per second (Kbps). The problem occurs because of a limitation
in the current USB modem driver (Usbser.sys). The hotfix download is available from
http://support.microsoft.com/kb/925681
Please select View and request hot fix downloads and follow the instructions to download
the appropriate file. Files can be found also from the DVD supplied by Anite (Nemo Outdoor
Page 46
6.0\Setup\Microsoft hot fix). Please note that for each operating system there is a separate
file available:
Windows 7, Windows6.1-KB925681-x86.msu
Windows Vista, Windows6.0-KB925681-x86.msu

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

WLAN measurements via Nemo Media Router
WLAN quality is not available
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
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 IR.92 voice/ SMS and IR9.4 calls
CAA event type is written as voice not VoLTE when call is generated via Nemo Outdoor user
interface. This is because at the time of the call attempt, call type is unknown
SIP UL/ DL messages are missing occasionally
With networks using encryption, it is required to perform radio off/ radio on for the VoLTE
test UE and wait ~40 seconds. During this time SIP server registering is shown in the user
interface even if the UE is already registered. After this, measurements can proceed
normally.
Page 47
With IMS SMS testing its not recommended to use more than 160 characters
PVI video streaming
Video streaming MOS and jitter values are occasionally reported with value zero
PVI video quality parameters are not available with 64 bit operating systems. PVI streaming
without video quality parameters is supported with both 32 and 64 bit operating systems
VLC media player:
Retrieving proper error messages (streaming cause codes) is missing. VLC player version
2.1.0 required with Nemo Outdoor version 7.3.0.6 or higher
USSD testing:
USSD testing is not supported with Huawei UEs
FTP UL data transfers:
Occasionally FTP UL data throughput values can exceed the maximum value supported by
the network. This is seen at the beginning of data transfers. The root cause is that the
operating system can buffer the data
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.
Page 48
With Nemo Outdoor 6.3 onwards the required Microsoft Network Monitor version is 3.4.
If IP packet capturing is not required it is highly recommended to uninstall it, as it affects to

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

ISSUES
17.1 PS connection works but no data

If UAC is set to always notify it might cause issues with data testing. PS connection can be
established but data transfer cannot be done. Its recommended to change UAC settings to Never
notify. This can be done via User Account Control Settings. If UAC settings cannot be changed its
highly recommended to start Nemo Outdoor application with administration rights by right clicking
Nemo Outdoor icon and by selecting Run as administrator.
Table 22. UAC settings.
17.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.
Page 51
Table 23. Network Connections.
Table 24. Antivirus NDIS Filter.
17.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).
Page 52
Requested throughput much higher than the actual measured throughput may indicate that there
are other users sharing the radio resources of the cell or some other bottleneck in the network that
prevents the mobile from getting the maximum achievable throughput.
High PUSCH TX power values indicate a lack of uplink coverage.
When operating in the dynamic range of link adaptation, average BLER (PDSCH BLER) should be
higher than 0, typically 10-20%, in order to achieve the gain of HARQ retransmission scheme
Residual BLER after all HARQ retransmissions should be 0%. Higher values indicate that the radio
link is about to drop. Observe the MAC downlink/uplink residual BLER (%) values.
Other things that could help troubleshooting:
Disable any firewall and/or antivirus software that could reduce the throughput. Some HSPA
USB interfaces may also install their own software which may affect to window size settings
in registry
Disable IP packet monitoring from the advanced properties
Table 25. IP packet capture settings.
Try another FTP server for comparison
Command prompt FTP throughput. This comparison is recommended because command

prompt FTP does not use any multithreading or other non-standard methods. For better
results, keep Nemo Outdoor at the background measuring the mobile network while making
the transfers. Also try different servers
For Nemo Outdoor 5.60 and older versions: Run a script with simultaneous FTP transfers to
see if the throughput increases. Does not work manually, script is always needed
For Nemo Outdoor 5.70 and later versions: Use the multithread feature of the FTP protocol
to test simultaneous transfers. Works also manually
For Nemo Outdoor 6.30 and later versions: Transmit/receive buffer size should not be
mixed with the TCP receive window size which is the global setting. TCP receive window
size affects the TCP/ IP layer whereas transfer buffer size affects the application layer.
Transfer buffer size can be adjusted per socket. This means that the transfer buffer size can
be adjusted for each test UE separately. Transfer buffer size can be adjusted with the FTP,
SFTP, HTTP, POP3, SMTP, and IMAP protocols
Page 53
When buffer size is not checked from user interface, Nemo Outdoor checks if auto-tuning is
on with Windows 7. If auto-tuning is on, no values are set. Otherwise the static value 64k is
used.
Normally default buffer values are acceptable. But if low data throughputs are still
experienced, increasing the receive/transmit buffer size may increase data throughput.
In uplink direction, transfer buffer size too high can be seen as high data throughput peak
at the beginning of the data session. For example, it is possible that measured data
throughput peak is higher than what the cellular system supports. In this case, decreasing
the transfer buffer size in uplink direction will eliminate high data throughput peaks.
Table 26. 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.
17.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:
Page 54
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.
17.2.2
Windows 7
Windows 7 does not use static window sizes from the registry. They rely on dynamic window size
which is handled by TCP auto tuning feature. However, if the same registry value that Windows
uses is set, Outdoor reads it and adjusts the manual window size based on this value. In most
cases, the registry has been edited by a third-party software or a USB mobile interface
driver/software. This registry entry can be removed.
If the TCP auto-tuning is disabled Nemo Outdoor will use its default window size 64 KB. Outdoor
5.40 and newer checks the auto-tuning state and does not change any window sizes if auto-tuning
is enabled.
How to check TCP auto-tuning state:
1. Open command prompt by typing CMD to Search programs and files field.
2.
Page 55
Type netsh interface tcp show global
Receive Window Auto-Tuning Level shows the current state.
Please note that administrator rights are required to change auto-tuning settings.
Open command prompt by typing CMD to Search programs and files field. Right-click and select
Run as administrator.
Table 27. Run as administrator.

To disable auto-tuning type netsh interface tcp set global autotuning=disabled. This limits the TCP
window size to 64KB. However, Outdoor sets its own default 256KB when auto-tuning is disabled.
To increase the maximum TCP window size that auto-tuning uses, type netsh interface tcp set
global autotuning=highlyrestricted.
Below are all the values of auto-tuning level with explanations:
disabled: Uses a fixed value for the TCP receive window. Limits to 64 KB (65535).
highlyrestricted: Recommended. Allows the receive window to grow beyond its default
value, very conservatively.
restricted: Recommended. Somewhat restricted growth of the TCP receive window beyond
its default value.
normal: Default value. Allows the receive window to grow to accommodate most conditions.
experimental: Allows the receive window to grow to accommodate extreme scenarios (not
recommended, it can degrade performance in common scenarios, only intended for
research purposes). It enables receive window values of over 16 MB.
Page 56
17.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.
Table 28. LAN settings.
Page 57
18 REFERENCES
[1] http://4g-lte-world.blogspot.fi/2012/05/tti-bundling-in-lte.html
[2] [3] Wikipedia
[4] https://support.twitter.com/articles/15364-twitter-limits-api-updates-and-following
[5] Wikipedia
Page 58
19 NEMO TOOLS
Anite offers a complete product portfolio for all wireless network measuring and analyzing needs on
all major network technologies.
Nemo Outdoor
Nemo Outdoor is a portable engineering tool for measuring and monitoring

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

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

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

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

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

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

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

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

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

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

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

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

Nemo Outdoor 7.50 Release: Technical Bulletin & Release Notes

Загружено:

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

Исходное описание:

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

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

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

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

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

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

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

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

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

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

Nemo Outdoor 7.50 Release: Technical Bulletin & Release Notes

Загружено:

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

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

WWW.ANITE.

NEMO OUTDOOR 7.50 RELEASE

NEMO OUTDOOR 7.5.0 TECHNICAL BULLETIN AND RELEASE NOTES

NEMO OUTDOOR 7.5.0 TECHNICAL BULLETIN AND RELEASE NOTES

1 NEW FEATURES ................................................................................................. 6

IR.94 - IMS profile for conversational video service ........................................ 6

IR.92 - IMS profile for SMS.......................................................................... 6

Enhanced forcing features with Qualcomm-based UEs..................................... 7

New dongle support .................................................................................... 8

Migration process for old USB dongle keys ............................................. 9

Migration process for new USB dongle keys ......................................... 11

Venture scanners ..................................................................................... 12

Venture MRX3808A/ L RF Measurement Receivers ................................ 12

Nemo Media Router version 2.20................................................................ 12

WLAN measurements ........................................................................ 13

YouTube video streaming .................................................................. 13

HTML browsing ................................................................................ 13

Voice quality audio RX activity status .................................................. 14

Call answering mode......................................................................... 14

Airplane mode ................................................................................. 14

NMR version and protocol information ................................................. 14

New NMR handsets ........................................................................... 14

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

Nemo Commander/ Remote enhancements ................................................. 15

Sending measurement files with periodic reports .................................. 16

Manual remote measurement session ................................................. 16

Area-based measurements ................................................................ 16

Integrated TeamViewer ..................................................................... 16

Test device RF cross-checking with user-configurable threshold ............. 16

2 APPLICATIONS AND PROTOCOLS ....................................................................... 19

HTTP PUT ................................................................................................ 21

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

Measurement pausing when GPS coordinates do not change .......................... 22

GPS timestamp verification with NMEA devices ............................................ 22

PEVQ-S video database files updates .......................................................... 22

NEMO OUTDOOR 7.5.0 TECHNICAL BULLETIN AND RELEASE NOTES

Generic handler enhancements .................................................................. 23

LTE-A 2CC Cat 6 handlers ................................................................. 23

LTE requested throughput estimation .................................................. 23

TTI bundling .................................................................................... 24

GSM RX quality logging from SDCCH channel ....................................... 24

Qualcomm handler enhancements .............................................................. 25

HiSilicon handler enhancements ................................................................. 25

Broadcom handler enhancements ............................................................... 25

Cell ID logging during Cell-DCH UMTS RRC state .................................. 25

3.10 Generic scanner handler enhancements ...................................................... 25

Nemo Invex status view ............................................................................ 28

5 USER INTERFACE ............................................................................................. 29

Indoor measurement enhancements ........................................................... 29

Indoor measurement mode ............................................................... 29

Creating markers based on GPS location in Indoor mode ....................... 29

Logging floorplan information to measurement file header ..................... 29

Measurement list based on areas ............................................................... 31

Improved USSD testing............................................................................. 32

6 NEW DEVICES ................................................................................................. 33

Handsets and USB modems ....................................................................... 33

Scanner receivers .................................................................................... 34

Supported handsets with Nemo Media Router .............................................. 34

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

NEMO OUTDOOR 7.5.0 TECHNICAL BULLETIN AND RELEASE NOTES

9 DEVICE CONFIGURATION AND WORKSPACE FILES ............................................... 39

NEMO OUTDOOR 7.5.0 TECHNICAL BULLETIN AND RELEASE NOTES