RN Nemo Outdoor 6.4.0.7 5th December 2012


1 Introduction .............................................................................................................................................................. 5

2 New Applications & Features .................................................................................................................................... 6

2.1 Applications ....................................................................................................................................................... 6

2.1.1 New Video Streaming Statistics for YouTube Testing............................................................................... 6

2.1.2 Qchat Support (PTT Calls) ......................................................................................................................... 8

2.1.3 HTTPS Transfer Protocol ........................................................................................................................... 9

2.1.4 Support for Content Encoding Information with HTTP Browsing ............................................................. 9

2.1.5 Using External Applications with Nemo Invex .......................................................................................... 9

2.2 New Devices ...................................................................................................................................................... 9

2.2.1 Samsung Galaxy S III ................................................................................................................................. 9

2.2.2 Nokia 500 .................................................................................................................................................. 9

2.3 New Features .................................................................................................................................................. 10

2.3.1 ANR CGI Reporting.................................................................................................................................. 10

2.3.2 Nemo FSR1 Scanner Handler Improvements ......................................................................................... 11

2.3.3 Altair Handler Improvements ................................................................................................................. 11

2.3.4 Qualcomm Handler Improvements ........................................................................................................ 12

2.3.5 Updated GSM/UMTS/LTE NAS L3 Decoders ........................................................................................... 14

2.3.6 Rohde & Schwarz TSMW Scanner Handler Features .............................................................................. 14

2.3.7 PCTel EX/ MX Scanner Handler Improvements ...................................................................................... 18

2.3.8 Manufacturer & Model Information ...................................................................................................... 19

2.3.9 Measurement Error Events Written for Nemo Invex Hardware Alerts .................................................. 19

2.3.10 CPU Information Logged into Measurement File Header ...................................................................... 19

3 User Interface .......................................................................................................................................................... 19

3.1 Script Enhancements ....................................................................................................................................... 19

3.1.1 Waiting for Custom Condition in Script Wait Command ........................................................................ 19

3.1.2 Counters and Timers in Script Files ........................................................................................................ 20

3.1.3 Script Option to Prevent Script Stopping During Connection Establishment ......................................... 22

3.2 Editing BTS Files ............................................................................................................................................... 22

3.3 Map Enhancements ........................................................................................................................................ 22

3.3.1 OpenStreetMap Maps ............................................................................................................................ 22

3.3.2 Loading KMZ Map Files in Indoor View .................................................................................................. 22

3.4 Other User Interface Enhancements ............................................................................................................... 23

3.4.1 Show Advanced Device Measurement Options in Devices Window ...................................................... 23

3.4.2 Nemo Invex UIC Slot ID and UIC Temperature Information ................................................................... 23

3.4.3 User Defined Measurement Filename Templates .................................................................................. 23

3.4.4 Timezone Adjustment for GPS Time Synchronization ............................................................................ 23


3.4.5 Locking to Multiple Bands with Band Lock ............................................................................................. 24

3.4.6 Exporting Data Views as Word and PowerPoint Documents ................................................................. 24

3.4.7 Measurement Export Option for Exporting Multiple Measurement into Single Export File .................. 24

3.5 Miscellaneous .................................................................................................................................................. 24

4 Version History ........................................................................................................................................................ 25

5 New Devices ............................................................................................................................................................ 25

5.1 Handsets and USB Modems ............................................................................................................................ 26

5.2 Scanning Receivers .......................................................................................................................................... 27

5.3 Nemo Outdoor 6.4.0.7 New Devices and Licenses ......................................................................................... 28

6 Qualcomm-based WCDMA and CDMA2000 Terminals and Data Cards ................................................................. 28

7 Computer Hardware and Software Requirements ................................................................................................. 29

8 Device Configuration and Workspace Files ............................................................................................................. 29

9 Installation............................................................................................................................................................... 30

9.1 Supported Operating Systems ........................................................................................................................ 30

9.2 First-time Installation ...................................................................................................................................... 30

9.3 Update/Upgrade ............................................................................................................................................. 30

9.4 Uninstallation .................................................................................................................................................. 30

9.5 HASP Dongle Runtime Drivers ......................................................................................................................... 31

10 Limitations and Issues with Windows 7 Operating System .................................................................................... 31

11 File Format Changes ................................................................................................................................................ 32

12 Known Issues ........................................................................................................................................................... 32

12.1 General & User Interface ................................................................................................................................ 32

12.2 UEs................................................................................................................................................................... 33

12.2.1 Altair-based UEs ..................................................................................................................................... 33

12.2.2 Cassidian Handsets ................................................................................................................................. 33

12.2.3 Datang/Leadcore Handsets .................................................................................................................... 34

12.2.4 Motorola Handsets ................................................................................................................................. 34

12.2.5 Nokia Handsets ....................................................................................................................................... 34

12.2.6 Samsung Chipset-based UEs ................................................................................................................... 37

12.2.7 Qualcomm GSM/WCDMA-based UEs .................................................................................................... 38

12.2.8 Qualcomm (MDM9200/ 9600)-based UEs ............................................................................................. 42

12.2.9 LG LTE Modems (LG1000/ LG 2000) ....................................................................................................... 49

12.2.10 Qualcomm 3GPP2-based UEs ................................................................................................................. 49

12.3 Scanner Receivers ........................................................................................................................................... 49

12.3.1 Anritsu Scanners ..................................................................................................................................... 49

12.3.2 Nemo FSR1 Scanner................................................................................................................................ 49

12.3.3 PCTEL Scanners ....................................................................................................................................... 50


12.3.4 Rohde & Schwarz Scanners .................................................................................................................... 51

12.4 Nemo Invex ..................................................................................................................................................... 52

12.4.1 General ................................................................................................................................................... 52

12.4.2 Nemo Invex USB Isolation Module ......................................................................................................... 52

12.4.3 Nemo Invex UIC Module ......................................................................................................................... 52

12.5 Other Devices .................................................................................................................................................. 53

12.5.1 GPS receivers .......................................................................................................................................... 53

12.5.2 TerraTec DMX 6Fire & Maya44 USB Sound Cards .................................................................................. 53

12.5.3 Beceem BCS200/BCSM 250/3300 Wimax .............................................................................................. 55

12.6 Applications & Protocols ................................................................................................................................. 55

13 Troubleshooting Device Connectivity Issues ........................................................................................................... 57

14 Troubleshooting Data Transfer Issues ..................................................................................................................... 58

14.1 PS Connection Works but No Data .................................................................................................................. 58

14.1.1 UAC Settings ........................................................................................................................................... 58

14.1.2 Antivirus Filtering ................................................................................................................................... 59

14.2 Low Data Throughputs .................................................................................................................................... 59

14.2.1 All Windows Versions ............................................................................................................................. 61

14.2.2 Windows XP ............................................................................................................................................ 62

14.2.3 Windows Vista/Windows7 ..................................................................................................................... 62

14.3 Issues with HTTP Browsing Testing ................................................................................................................. 64


1 Introduction

Nemo Outdoor is a pioneering and leading-edge network measurement, optimization, and benchmarking solution for

perfecting the air interface of wireless networks. It collects measurement results and geographical coordinates, and

these measurement results further provide valuable information for network planning, roll-out, tuning, verification,

optimization, maintenance, and benchmarking purposes. Nemo Outdoor is always among the first-to-market with

support for the very latest technologies, such as, LTE FDD and TDD, HSPA+ dual cell, CDMA, 1xEVDO, GSM, WCDMA,

WiMAX, iDEN, TETRA and TD-SCDMA measurements.

Nemo Outdoor provides our customers with the flexibility and choice to meet the specific and growing needs of the

ever-evolving markets. Its powerful platform is expandable beyond current trends to those of the future, and all of

this materializes on a single platform. With Nemo Outdoor you can perform not only drive testing but also QoS and

benchmarking measurements on every standard network technology and on multiple simultaneous data connections.

This empowers the operators to reach both optimal network performance and time and cost-effectiveness.

Nemo Outdoor is extremely easy to set up, configure and use. Furthermore, Nemo Outdoor‘s utterly customizable and

smooth user interface offers the users the possibility to customize data views and workspaces for their specific needs

at any given time. This flexibility further manifests itself in the open file format (ASCII) which enables customers to

integrate in their optimization processes the use of not only the upscale Anite’s post-processing tool Nemo Analyze,

but also those of third-party vendors. In addition, Nemo Outdoor’s import/export feature allows for all user settings to

be transferred to or from another computer.

Through our close cooperation with several mobile and scanner manufacturers we ensure that our customers always

get to select amongst the latest test equipment. Currently Nemo Outdoor supports more than 270 test terminals and

scanner receivers, a figure which is constantly on the increase to meet the rapidly changing customer needs for

optimal satisfaction.


2 New Applications & Features

2.1 Applications

2.1.1 New Video Streaming Statistics for YouTube Testing

YouTube video support using HTTP links was introduced in Nemo Outdoor version 6.30. The reasons why YouTube

was selected as the preferred service for video streaming testing with Nemo Outdoor is that YouTube produces 22%

of the total global mobile traffic according to statistics [1]. Moreover, when inspecting only streaming services,

YouTube represents 52% of the total global mobile streaming. That is, YouTube is by far the most popular streaming

application over the globe. With Nemo Outdoor, statistical information can be collected, such as, number of data

attempts, failed data connections, data drops, successful data transfers, throughputs, and stream state.

With the latest version of Nemo Outdoor and additional trigger points, users can perform comprehensive YouTube

video testing from the end-user QoS perspective. New KPIs are needed due to the reason that when streaming is

performed using the HTTP/TCP transport mechanism, video quality degradation is avoided. HTTP streaming is used by

all Android and iOS based handsets. KPIs seen with the RTSP/UDP transport mechanism, such as video quality jitter

and video quality jerkiness, are obsolete. With the HTTP/TCP transport mechanism, video quality MOS is always either

1 (annoying) or 5 (perfect) on the MOS scale. Video quality MOS 1 presents a situation where video streaming

(playing) is totally frozen. VLC player version 2.04 is required. It can be down loaded from http://www.videolan.org/.

The following new KPIs are recorded in addition to network availability and accessibility (PS data connections and data

transfer statistics):

Service Accessibility

Streaming Set Up Success Rate (%)

Definition Ratio of successful stream playing starts after user requests the stream.

Condition PDP context is activated.

Trigger Points Start: User initiates the video request. Data request (DREQ) event in the measurement file

with streaming status

Stop: The video streaming starts. First data stream status (DSS) event with buffering status

Computation � NumberofSuccessful��DataAttemptsTotalNumberofStreamingDataRequestAttempts# × 100

Connection Time-out If the time for the video to initiate is greater than X seconds, the attempt is counted as

failure. Connection time-out time can be set by user via Nemo Outdoor user interface.

Default value is 30s.


Service Retainability

Streaming Completion Success Rate (%)

Definition Proportion of the times that the video is played until the end and the number of video

streaming playing started.

Condition Video streaming playing has started successfully.

Trigger Points Start: Video streaming playing starts. First data stream status (DSS) event with playing

status.

Stop: Video streaming reaches the end of the stream. Data transfer completed (DCOMP)

event with transfer status.

Computation �'(�)��*+SuccessfulStreamingDataTransfers,*��-'(�)��*+Streaming��. # × 100

Transfer Time-out After the playing is stopped for some reason and if the time for the video to restart is

greater than X seconds, the attempt is counted as a streaming data drop. Transfer time-out

time can be set by user via Nemo Outdoor user interface. Default value is 30s.

Service Integrity

Streaming Setup Delay [s]

Definition Duration between the point that the user requests the video and the start of the playing.

Condition The playing starts.

Trigger Points Start: user requests the video. Data request (DREQ) event in the measurement file with

streaming status

Stop: Video streaming playing starts. First data stream status (DSS) event with playing

status.

Computation t/012345671879 − t;9<8678<1=345>171?<@A<97BsC

Connection Time-out If the time for the video to initiate is greater than X seconds, the attempt is counted as

failure. Connection time-out time can be set by user via Nemo Outdoor user interface.

Default value is 30s.

Additional KPIs

Stream duration Written to DSS event. Video duration

Streamed duration Written to DSS event. Actual video duration including start delay and rebuffering time, i.e.,

the total delay experienced by user.

Streaming buffering Written to DSS event. Number of buffering events during playing

Playback position Written to DSS event. Showing playback position at the moment

Video resolution Written to DSS event.


The following KPIs are available with Nemo Analyze post-processing tool.

Streaming Delay Ratio

Definition Ratio that indicates the proportion between the length of the video stream and the actual

length of the playing counting start delay and rebuffering time, i.e., the total delay

experienced by user.

Condition Video playing has been successful until the end.

Trigger Points Start: User requests the video. Data request (DREQ) event in the measurement file with

streaming status

Stop: Stream is ended. Data transfer completed (DCOMP) event with successful transfer

status.

Computation VideoLengthHsIStartDelayHsI + RebufferingHsI + VideoLengthHsI

Remarks The closer to the unity indicates the better streaming experience.

Additional KPIs

Duration of buffering Duration of buffering during playing

User can also set the rebuffering timeout time with video streaming testing via the Nemo Outdoor user interface. It

sets the maximum allowed buffering duration during video playback.

References:

[1] “Allot MobileTrends: Global Mobile Broadband Traffic Report. Allot Communications, H1, 2011

[2] Video Streaming Development, Omnitele

2.1.2 Qchat Support (PTT Calls)

QChat is a Push-to-Talk (PTT) technology developed by Qualcomm. QChat, an application developed for the BREW

platform, is a PTT communication technology for 3G networks. QChat handsets and server software allow users to

connect instantaneously with other QChat users anywhere in the world with the push of a button. In addition, QChat

enables one-to-one (private) and one-to-many (group) calls over the 3G networks.[3]

QChat uses standard Voice over Internet Protocol (VoIP) technologies. Voice information is sent in digital form over IP-

based data networks (including CDMA) in discrete packets rather than traditional circuit-switched protocols, such as

those used in the public switched telephone network (PSTN).

PTT calls must be performed using the keypad of the phone when used with Nemo Outdoor application. Normal call

events and statistics are written when attempting or ending PTT calls. Different states of PTT calls, such as idle, getting

ready to receive, receiving, transmitting are written to VCHI event. Please see the file format specification for further

information. RTP packets are recorded and decoded with Nemo Outdoor application. Qchat is an optional feature in

Nemo Outdoor application and requires the license option 320081-20. QChat PTT calls can be performed, for example,

with the Kyocera DuraMax E4255 handset.


References:

[3] Reuters Company Overview, Qualcomm Incorporated

2.1.3 HTTPS Transfer Protocol

Hypertext Transfer Protocol Secure is a widely used communications protocol for secure communication over a

computer network. HTTPS file data transfers and also HTTPS browsing can be done with Nemo Outdoor application

using manual or automated mode.

2.1.4 Support for Content Encoding Information with HTTP Browsing

When “Decode content” option is selected from Nemo Outdoor user interface and HTTP data is compressed, the

transfer is identified by content encoding information (e.g. gzip). Information is written to DCONTENT event. This

information is useful, for example, when benchmarking performance of HTTP browsing between different operators

and page downloading times differ.

2.1.5 Using External Applications with Nemo Invex

External applications are ran in the UIC module instead of the controlling PC. User must set the command line in the

script file to point to the appropriate folder and file located on the UIC module.

2.2 New Devices

2.2.1 Samsung Galaxy S III

The latest Nemo Outdoor version 6.40 introduces support for several new Samsung Galaxy S III handsets:

o Samsung Galaxy S III (GT-i9305, EU)

o Samsung Galaxy S III (SCH-i535, Verizon)

o Samsung Galaxy S III (SPH-L710, Sprint)

Measurements from 2G to 4G are supported with the updated Qualcomm handler including CSFB calls.

Please see the Nemo Outdoor Qualcomm LTE and CDMA/ EVDO data sheets for further information.

2.2.2 Nokia 500

Nokia 500 based on the Symbian OS is supported with voice, voice quality, and ps data testing also with multi system

configurations controlled with single CPU. Requires Nokia 500 handler option (320075-15). Handset does not support

video call testing.

Please see chapter 5. “New Devices” for a full list of new test devices verified by Anite Finland.


2.3 New Features

2.3.1 ANR CGI Reporting

In LTE, the UE detects neighbor cells independently. Operator must set X2 and/ or S1 objects to the network to be able

to make handovers between cells. In case the network or the UE does not support the Automatic Neighbor Relation

(ANR) functionality , the UE detects unknown PCIs, measures, and reports back to the network with a measurement

report. If X2/ S1 objects are not set to the network, it is not possible to perform handovers, and most likely the

connection between an eNB and a UE is lost. The purpose of the Automatic Neighbor Relation (ANR) functionality is to

help manage neighbor relations of eNBs. When a UE detects an unknown PCI, it reports the Eutran Cell Global ID

(ECGI) of the unknown cell to the network. Based on the reported ECGI information, the network creates neighbor

relation to the new cell. ANR information is decoded and shown in the user interface of Nemo Outdoor and also

logged to file whenever the network sends a CGI reporting command to the UE (cellForWhichToReportCGI) and when

the UE reports neighbor cells (measResultNeighCells) to the network. Information is logged to the Automatic

neighbor relation information event including ANR type, channel number, PCI, Cell ID, TAC, MCC, and MNC.

Notifications and statistics can be shown for ANR events as well.

Figure 1. Example views of ANR information.


2.3.2 Nemo FSR1 Scanner Handler Improvements

The following new functionalities are supported with Nemo Outdoor 6.40 onwards. It should be noted that the ICD of

the Nemo FSR1 scanner with the firmware version 3.1 is backwards compatible with Nemo Outdoor 6.31 and 6.30.

• WCDMA L3 message decoding (Optional feature, FSR5600-00)

o Provides full BCCH message decoding. BCCH decoding can be activated via measurement properties

All existing customers are entitled to get a free update to firmware version 3.1 including WCDMA L3

message decoding.

• Support for Nemo FSR1 autodetection

o Scanner is detected automatically by Nemo Outdoor application

• New scanning modes for WCDMA : High dynamic and high speed

2.3.3 Altair Handler Improvements

The following new parameters and features have been added:

• New parameters:

o Support for RSSI level information (Cellmeas)

o RLCRATE & RLCRATEU

� Total RLC throughput and RLC throughputs / RB supported

o MACRATE & MACRATEU

� Throughputs supported

NOTE! RLC & MAC throughputs are supported on the latest Altair SW package, ALT3100_04_00_02_00_32_TF.

Previous versions do not report these parameters.

o LTE precoding matrix indicator (WB PMI)

� Written to CQI event. Requires Altair SW package, ALT3100_03_02_00_00_10_TF

o PRB utilization UL (in TDD mode)

o PRB utilization DL

� Written to PLAIU and PLAID events.

• New features:

o Device removal notification support

o Support for band lock


� Locking to multiple LTE FDD and LTE TDD bands simultaneously is supported

2.3.4 Qualcomm Handler Improvements

2.3.4.1 LTE

The following new LTE parameters and features have been added:

• New parameters:

o LTE precoding matrix indicator (WB PMI)

� Written to CHI event

o CQI per subband

� Written to CHI event

o PRB utilization UL

o PRB utilization UL/Index


o PRB utilization DL/Index



o RACH logical root sequence index

o Support for cyclic prefix with LTE

� Root sequence and CP information is written to CHI event

• Support for LTE CS fallback events and statistics. The following statistics are logged:

o CS fallback voice call attempts

o CS fallback voice call attempt failures

o CS fallback voice call attempt failures (system failure)

o CS fallback voice call connects (MOC/ MTC)

o CS fallback voice call attempt success rate

o CS fallback voice call setup time (MOC/ MTC)

o CS fallback calls received (MTC calls)

• Support for MMS messaging with LTE packet session

o MMS message sending and receiving is enabled when the access point name of the existing packet

session matches the access point name configured for MMS messages. This can be used in LTE

networks where MMS messages can be sent/received over the LTE APN

2.3.4.2 WCDMA

Neighbor cell index information is written to NLIST event.


2.3.4.3 LG Handler Improvements

The following new LTE parameters have been added:

o PRB utilization UL



2.3.5 Updated GSM/UMTS/LTE NAS L3 Decoders

All decoders have been updated and are 3GPP Rel. 10 compliant. LTE RRC decoder Rel 10. Ver. 10.6.0.

2.3.6 Rohde & Schwarz TSMW Scanner Handler Features

2.3.6.1 LTE MIMO Measurements with R&S TSMW

Multiple input multiple output (MIMO) technologies are an essential component of state-of-the-art mobile radio

systems – such as HSPA+1 and LTE2 – and are key to achieving extremely ambitious capacity goals that include

providing stable data rates in the two- to three-digit megabit per second range over a broad coverage area. The use

of spatial multiplexing allows the data rates to be multiplied without requiring additional bandwidth or increasing the

overall transmit power. However, the effectiveness of these technologies is not always guaranteed. The MIMO

channel state information (CSI) can be used to determine whether spatial multiplexing is practicable. For example,

under certain circumstances (such as identically polarized radio waves), spatial multiplexing does not bring any benefit

with respect to capacity even with a direct line of sight (LOS) between the transmitter and the receiver, while it is of

much more benefit in extreme cases of multipath propagation (such as indoor reception). Assessing the status of a

MIMO channel requires a continuous evaluation of complex matrices. Fortunately, relatively simple mathematical

indicators, such as the channel rank and condition, can be interpreted for a rapid assessment of the MIMO channel.

[5]

All of the MIMO specific measurements are based on the full bandwidth and can be applied to 4x2 and 2x2 MIMO

systems. The output is basically the channel matrix with complex values, meaning amplitude and phase. This

measurement needs to be done by each terminal using MIMO. Out of the channel matrix a so-called Singular-Value-

Decomposition is calculated. The results are called Singular Values and are used to get the Condition

Number (CN). The condition number qualifies the channel whether it is “ill-conditioned” (MIMO

not applicable) or “well-conditioned” (MIMO usable). In a case with CN < 10 dB, this “well-conditioned”

channel matrix would be useful when recovering the data streams. If the CN were >15 dB, it could be expected that

data recovery would be very sensitive to noise.


Figure 2. Channel matrix with condition number [5]

R&S TSMW provides the condition number and rank information to Nemo Outdoor once per second. MIMO scanning

results are reported for up to 32 cells (PCI) simultaneously. Condition number and other parameters shown in the

figure 3. are logged for each cell separately and contains scanning results per physical resource block. Low condition

number (CN) represents good conditions for MIMO. But the full MIMO performance also depends on the SINR of the

signal. So the system performance of a system with CN=0 dB and SINR=15 dB would be equal to a system with CN=15

dB and SINR=20 dB1. Bottom-line, the performance of a MIMO system depends on the Signal-to-Noise-Ratio and also

on the Condition Number. To understand throughput issues, both values need to be considered. The rank of the

channel matrix is thus an indicator of how many data streams can be spatially multiplexed on the MIMO channel. The

rank and condition of a channel matrix also exist for every possible matrix dimension and thus for every possible

MIMO constellation. [6]

The following new MIMO parameters shown in the figure 3. are logged with Nemo Outdoor in addition to parameters

available per port. Values are written to PRBSCAN event. Please note that option 315021-13 (LTE MIMO Scanner

Option TSMW-K30 1514.4085.02) is required to be able to make MIMO measurement with the R&S TSMW scanning

receiver. TSMW firmware version 1.13 is required.


Figure 3.Supported R&S TSMW MIMO parameters.

The following TX/RX combinations are available in the Vicom interface and are logged by Nemo Outdoor application

when WB scanning mode is used. Antenna port combinations are logged to OFDMASCAN event. The configuration of

the measurement task includes which eNB TX antenna port to measure: any combination of 0, 1, 2, and 3. On which

receiver frontend to measure: RX0, RX1, or both. Each measurement result includes which TX-RX combination was

measured. For example, TX0 RX1 means Reference Signal from eNB antenna 0 was measured on receiver frontend 1.


Figure 4.Supported R&S TSMW parameters/ antenna port/ port combinations.

2.3.6.2 LTE MIMO Antenna

Optional R&S MIMO antenna 42101-12 (TSMW-Z8 MIMO, 1518.1851.02) is required. NOTE! MIMO antenna is not

included in the option 315021-13 (LTE MIMO Scanner Option TSMW-K30 1514.4085.02) and it must be ordered

separately. The antenna must be used only indoors.

Key Benefits

• One antenna covers all bands between 700 MHz – 2700 MHz

• Applicable for 2x2 or 4x2 MIMO scenarios

• Reference MIMO antenna meets LTE MIMO requirements (balanced gain, high isolation and low correlation

coefficient)

Figure 5.R&S TSMW Z8 MIMO antenna [8].


References:

[5] Rohde & Schwarz Assessing a MIMO Channel

[6] How a R&S®TSMW scanner brings special advantage in a drive test system

[8] Technical information TSMW_Z8

2.3.6.3 Built-in GPS Data with R&S TSMW Scanner

The TSMW has a built-in GPS receiver. The SuperSense technology even allows a position fix with very poor GPS

satellite signals. In some cases this even works indoor, like in shopping malls with a thin metal roof. The scanner can

use the GPS for the synchronization but it does not need a GPS to get measurements. When no GPS is available, the

TSMW is able to use technology related Synch Channels for its own synchronization. The internal GPS can detect

satellites with -148 dBm for initial acquisition and then with -158 dBm for tracking the satellites. So once the position

fix is done, its even more sensitive. Internal GPS receiver of TSMW can be activated via Nemo Outdoor user interface

under measurement properties and it can be used also to log GPS coordinates to measurement files. [7]

[7] How a R&S®TSMW scanner brings special advantage in a drive test system

2.3.7 PCTel EX/ MX Scanner Handler Improvements

2.3.7.1 PCTel EX+ Scanner Receivers

PCTel EX+ scanners are supported on the Nemo Outdoor platform with PCTel EX and EX LTE handlers. To be able to

simultaneously measure GSM/ WCDMA and LTE systems, both PCTel EX and PCTel EX LTE licenses are required. NOTE!

All PCTel EX+ scanners with known system and band configurations are supported. Due to the large variety of

different systems and bands available with EX and EX+ scanners, Anite Finland cannot quarantee full compabilty with

all models.

Please see the Nemo Outdoor 6.4.0.7 Compatible Devices 5th December 2012.pdf for further information about the

supported systems and band variants. A combination of the listed systems and bands can be used with EX+ platform.

For example, from the list we can see that support for EX models LTE E800/2600 (UL/DL) and GSM 900/1800 WCDMA

2100 already exist in Nemo Outdoor. If these bands exists in the PCTel EX+ scanner, the device can be added to Nemo

Outdoor as two different scanning receivers. In case the supported systems and bands differ from the currently

supported models, the scanner cannot be used with Nemo Outdoor application.

2.3.7.2 GSM BCCH & WCDMA BCH Layer 3 Message Decoding with PCTel MX

User can select full L3 message decoding for GSM (SI) and WCDMA (SIB) separately. This requires the following

options: MX GSM Layer 3 Option OP522-GSM (315016-07) and MX WCDMA Layer 3 Option OP522-WCDMA (315016-

08).


2.3.7.3 LTE 800MHz ESMR and WCDMA 1800 Band Support with PCTel MX Scanner

• E-UTRA band 26, 814 MHz to 849 MHz DL, 859 MHz to 894 MHz UL. Known as ESMR 800 MHz (superset of

bands V, VI XVIII, and XIX).

• WCDMA 1800 (band III) 1805- 1880MHz.

2.3.8 Manufacturer & Model Information

Information can be seen for all test devices under configuration manager window during measurement and playback.

2.3.9 Measurement Error Events Written for Nemo Invex Hardware Alerts

Hardware alerts are written as ERR events in the measurement log. The following ERR event error texts have been

added:

• Hardware Voltage High

• Hardware Voltage Low

• Hardware Battery Operation

• Hardware Battery Voltage Low

• Hardware High Voltage Shutdown

• Hardware Battery Shutdown

2.3.10 CPU Information Logged into Measurement File Header

CPU information of the computer running the Measurement Server is written to the measurement file header.

This is logged as a new parameter in the #SERVERHW event. During playback, information is shown in the

configuration window.

3 User Interface

3.1 Script Enhancements

3.1.1 Waiting for Custom Condition in Script Wait Command

User can define a custom parameter rule and a maximum time in the script Wait command. The command waits until

the specified rule is matched or the maximum time is elapsed.

Figure 6. Script editor - wait settings.


3.1.2 Counters and Timers in Script Files

User can create a named timer or counter with a script command and use the value of the timer and counter in If and

Loop command rules.

Figure 7. Script editor- advanced options

In the example below, the script file is ran as long as number of GSM calls (counter) is less than five and the time

duration (timer) is less than 600s. First add the counter and timer to the script file. Timer is started on line 2 and it is

started on every loop.

Figure 8. Script editor, script with counter and timer.

Figure 9. Script editor – timer settings.

With IF/ end IF lines GSM calls count is incremented by one when the serving system is GSM.


Figure 10. Script editor - counter.

Lines 3 to 11 are looped as long as the number of GSM calls is less than 5 and duration is less than 600s. When the

counter value reaches 5 or the timer value reaches 600s, the script is completed.

Figure 11. Script editor- Loop.

Loops are created by using If/end IF commands and defining the loop criteria using GSM call counter and Duration

times made earlier.

Figure 12. Script editor- Loop settings


3.1.3 Script Option to Prevent Script Stopping During Connection Establishment

New script engine option that implemements a "soft" stopping of scripting. When enabled, the option delays the

script stopping if any of the devices has a call or connection attempt ongoing.

Figure 13. User Interface Properties.

3.2 Editing BTS Files

BTS files (extension .nbf) can be edited and saved via Nemo Outdoor user interface. Please see the Nemo Outdoor

user manual for further information.

3.3 Map Enhancements

3.3.1 OpenStreetMap Maps

In addition to MapInfo® Nemo Outdoor application can be used with OpenStreetMap maps. Same functionalities are

supported as with MapInfo® maps, such as, route coloring and overlaying BTS files. By default Nemo Outdoor installs

both maps but the user can choose not to install MapInfo maps by using the custom installation option.

3.3.2 Loading KMZ Map Files in Indoor View

Google Earth can be used to georegister raster images with building floorplans and these images can be saved as KMZ

files. Nemo Outdoor indoor map window can be used to view and place markers on KMZ raster images with

georeferenced coordinates. Please see Nemo Outdoor user manual for further instructions on how to overlay floor

plan image files with Google Earth application and how to use KMZ files with indoor testing.


3.4 Other User Interface Enhancements

3.4.1 Show Advanced Device Measurement Options in Devices Window

Figure 14. Measurement options.

3.4.2 Nemo Invex UIC Slot ID and UIC Temperature Information

User interface displays UIC slot ID and UIC temperature information. Information can be seen in the Server Status

view.

Figure 15.Server Status view

3.4.3 User Defined Measurement Filename Templates

Measurement file naming can be done using a number of built-in tags (such as %y for year) and with user defined

templates with custom tags. The template includes the name of the tag and a list of allowed values for each tag. The

template can be used also to specify the measurement filename format which defines how the tags are used in the

measurement filename. New dialog called “Filename Editor” has been added for building the template and it is

possible to export/import measurement file templates using the existing import/export settings feature. Filename

editor can be accessed via User Interface properties window.

3.4.4 Timezone Adjustment for GPS Time Synchronization

New user-configurable offset value that specifies the difference between GPS UTC time has been added. This offset is

used by handlers when GPS time synchronization is performed. It is highly recommended to use this setting when

performing voice quality measurements against Nemo Server and Nemo Server is using NTP time.


Figure 16. User interface properties.

3.4.5 Locking to Multiple Bands with Band Lock

Many test UEs allow multiple bands to be specified so the band lock command has been modified to allow multiple

bands.

3.4.6 Exporting Data Views as Word and PowerPoint Documents

All views in the workspace can be exported to Word and PowerPoint formats. One view (window) is exported per

page. Individual views can be exported in jpeg format.

Figure 17. Exporting images.

3.4.7 Measurement Export Option for Exporting Multiple Measurement into Single Export File

Instead of exporting each measurement file to separate export file, user can choose to export all files to a single file

using option “Export to single file”. System does not perfom any sanity check, such as, are measurement files made at

the same time or in the same location.

3.5 Miscellaneous

• User selectable measurement file location in the measurement report dialog

• Improved scanner status in the device status window

o Information in the SCANCONFIG-event is displayed in the device status window

• Parameter presentation modes with color sets

o Map/Indoor color set legend shows user-specified parameter presentation modes, for example, bps,

kBps, MBps for throughput values

• Resizable script editor window

• Maximizing data views that are docked together


o It is possible to maximize/restore data views that are docked together either vertically or

horizontally

• Presentation for LTE Cell ID eNB Id+Cell Id format

• LTE Cell ID (eCGI) parameter can be shown also in the eNB ID+ Cell ID format. eCGI= eNB ID+ Cell ID (int

(41218 div 256) =161 => eNB ID, 41218= mod 256 = 2 => Cell ID). Presentation can be changed via user

interface properties window

• New data transfer status value: transfer aborted

o Previously if a data transfer was stopped before completion, it was logged as a successful transfer.

New status value "Transfer aborted" is used. This allows users to differentiate completed transfers

from aborted transfers in post-processing

• Logging custom AT-commands and responses

o AT commands that are sent from the user interface with the send AT command are logged into the

measurement file. Also the responses for these commands are logged. If the command is not passed

to the UE there will be no events written. Information is logged to new “MODEM” event

• Low disk space warning for remote Measurement Servers

o Nemo Outdoor monitors disk space displaying a warning when the free disk space on any of the

connected remote Measurement Servers running on Nemo Invex UIC module is low

• Logging LTE TDD uplink/downlink configuration in SCANCONFIG event

• iDEN scanning with iDEN test terminal

• MMS messaging with LTE packet session

o MMS message sending and receiving is enabled when the access point name of the existing packet

session matches the access point name configured for MMS messages. This can be used in LTE

networks where MMS messages can be sent/received over the LTE APN

4 Version History

Please see the C:\Program Files (x86)\Anite\Nemo Outdoor\readme.html file for further information about the

changes with different UEs and scanner devices.

5 New Devices

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

Devices.pdf.


5.1 Handsets and USB Modems

• Samsung Galaxy S III (GT-i9305), EU

– GSM 850/900/ 1800/ 1900

– WCDMA 850/ 900/ 2100

– LTE FDD 800/ 1800/ 2600 (bands 20, 3, and 7)

• Samsung Galaxy S III (SCH-i535, Verizon)

– CDMA 2000/1xEV-DO Rev. A, 850/ 1900

– LTE FDD 700C (band 13)

• Samsung Galaxy S III (SPH-L710, Sprint)

– CDMA 2000/1xEV-DO Rev. A, ESMR 800/ 850/ 1900

– LTE FDD 1900/ 1900 PCS A-G (band 2 and 25)

• Nokia 500

– GSM 850 / 900 / 1800 / 1900

– HSDPA 850 / 900 / 1900 / 2100/ 2100 AWS (1700)

– GPRS/ EDGE Class 33

– HSDPA, 14.4 Mbps; HSUPA, 5.76 Mbps

– Symbian Anna OS, upgradeable to Nokia Belle OS

– Verified with up to 6 UEs with single CPU

– Voice quality testing supported

– Available with special firmware for 2G WB-AMR testing

– Available with ext. antenna

• Onda MT689DC

– DC-HSPA+ 900/2100 MHz 42.2 Mbps DL

– HSDPA 900/2100 MHz 14.4 Mbps DL


– HSUPA 2100/1900/900/850 5.76 Mbps UL

– UMTS 2100/1900/900/850 384 Kbps

– EDGE/GPRS 850/900/1800/1900 MHz 237 Kbps

• ZTE MF193 USB modem

– Quad band GSM/ HSDPA 850/1900/2100

– 7.2Mbps DL

• Kyocera DuraMax E4255

– CDMA/ 1xEVDO Rev. A 800/1900

– Qualcomm QSC6085

– Supports CDMA-based push-to-talk system

5.2 Scanning Receivers

Support for 06108 PCTEL EX Scanner GSM 900/ GSM 1800 /UMTS 850/ UMTS 2100.

Nemo FSR1 scanner handler updated to support firmware version 3.10. Nemo Outdoor 6.40 is compatible with Nemo

FSR1 scanner firmware versions 3.0 (FSR1_030003.ffw) and 3.10 (FSR1_03010x.ffw).

PCTEL MX handler updated to support MX scanner SeeGull Master API version 1.4.01. EX scanner handler updated to

support eICD version 2.1.11.0.

R&S scanner handlers updated to support ViCom interface version 14.71. R&S TSMW firmware 1.13 beta 201 is

required. New firmware can be downloaded from :

http://www2.rohde-schwarz.com/en/products/test_and_measurement/Drive_Test_Tools/hardware/TSMW-%7C-

Firmware-%7C-23-%7C-4874.html


5.3 Nemo Outdoor 6.4.0.7 New Devices and Licenses

Product

Code

Device Firmware Version License Handler Driver Max. # of

Verified

Devices/

CPU

413140-12

413133-06

with ext.

antenna

Samsung Galaxy S III

GT-i9305 EU

M9615ACEHWMAZD1795

(ACEFWMAZ Aug 17 2012

20:29:27)

Qualcomm LTE Qualcomm Kies_2.3.3.12085_7_5.exe ?

413139-14 Samsung Galaxy S III

SCH-i535, Verizon

M8960A-AAAANAZM-

1.0.442802 (AAAAANAZ Jul 4

2012 13:16:00)

Qualcomm LTE

OR

Qualcomm

CDMA/EVDO

Qualcomm 1.5.6.0 1

413139-15 Samsung Galaxy S III

SPH-L710, Sprint

M8960A-AAAANAZM-

1.0.102013 (AAAAANAZ Jul 18

2012 12:18:11)

Qualcomm LTE

OR

Qualcomm

CDMA/EVDO

Qualcomm 1.5.6.0 1

100314-19

Nokia 500 NTM 85 v1.0, 10-09-12, RM-

750, V 79u_sr1_11w42, 2009/II

NTM IF 3.6.3, 0x0

Nokia 500

(320075-15)

Nokia 500 7.1.92.0 6

NA Onda MT689DC MT68xDC.TIM.FW.B06

(ONDAMF68 Nov 18 2011

14:04:29)

Qualcomm

HSPA +DC

Qualcomm 3.2074.0.2 1

NA ZTE MF193 USB

modem

M6290A-KPRZL-2.4.0105T

(MF193 Jun 17 2011 17:07:52)

Qualcomm

HSDPA

Qualcomm 1.2074.6 1

NA Kyocera DuraMax

E4255

1.002SP (SNACAZ53 Sep 05

2011 19:43:30)

Qualcomm

CDMA/EVDO

Qualcomm NA 1

NA 06108

PCTEL EX Scanner

GSM 900/ GSM 1800

/UMTS 850/ UMTS

2100

NA PcTel EX PcTel EX NA 1

6 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 Finland Ltd 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 6.4.0.7 Compatible Devices.pdf. for a list of verified Qualcomm-based CDMA and WCDMA terminals.


CDMA terminals with or without RUIM card purchased from Anite Finland Ltd must be registered with a local CDMA

operator. Anite Finland Ltd does not take any responsibility if a local operator restricts the registration of test

terminal(s) supplied by Anite Finland Ltd.

7 Computer Hardware and Software Requirements

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

bit). Windows 7 ® Professional recommended

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

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

• For voice quality measurements with up to four channels with USB sound card Intel® Core Duo processor T2500

2.00GHz or higher required

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

2.26GHz or higher required

• 512MB RAM minimum, 1GB RAM recommended

• For multi data measurements with HSPA+ devices Intel® Quad Core processor Q9100 2.26GHz or higher required

• 100 MB of free hard disk space for installation and use; 1 GB recommended

• One USB port for copy protection module

• One USB port per mobile

• Depending on the scanner used, one USB port or serial port or RJ45 or FireWire port per scanner

• One serial port for each voice quality audio module or one USB port per sound card

• One USB port for an external GPS receiver

• Display resolution 1400 x 900 recommended

• Internet Explorer for viewing the help file

8 Device Configuration and Workspace Files

Device configuration and workspace files made by Nemo Outdoor 6.3.1.11 are fully compatible with Nemo Outdoor

6.4.0.7.


9 Installation

9.1 Supported Operating Systems

Supported operating systems are Windows XP ® (32/ 64-bit) and Windows 7 ® (32/ 64-bit).

9.2 First-time Installation

♦ Note that for Windows® XP and Windows® 7, the installation must be run under Administrator account or other

user account with administrative privileges.

Start Windows® and insert the Nemo Outdoor CD-ROM in your CD drive (e.g., drive D). Select Start | Run in the

Windows® Status bar. Type D:\Nemo Outdoor 6\Nemo Outdoor x.xx.x in the Open field (xx refers to the version

number). Run the setup.exe and click the OK button. After the installation program starts, follow the instructions on

your screen. NOTE! When the Nemo Outdoor software installation is complete, you will need to restart the computer.

With Nemo Outdoor 6.30 onwards copy protection module is not needed during installation.

9.3 Update/Upgrade

♦ Note that for Windows® XP and Windows® 7, the 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 6.4.x installation can be ran.

Start Windows® and insert the Nemo Outdoor CD-ROM in your CD drive (e.g., drive D). Select Start | Run in the

Windows® Status bar. Type D:\Nemo Outdoor6\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.

9.4 Uninstallation

♦ Note that for Windows® XP and Windows® 7, the uninstallation must be run under Administrator account or

other user account with administrative privileges.

Nemo Outdoor application must be uninstalled via Add or Remove Programs. NOTE! With Nemo Outdoor versions

5.80- 6.21 the copy protection key must be attached to USB port during the uninstallation. With Nemo Outdoor 6.3.x

onwards copy protection module is not needed during uninstallation. When the Nemo Outdoor software

uninstallation is complete, you will need to restart the computer.


9.5 HASP Dongle Runtime Drivers

♦ Note that the Nemo Outdoor setup includes the required HASP dongle runtime driver compatible with the

application. The driver should not be updated, for example, with Windows update or using a separate driver

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

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

it conflicts with Nemo Outdoor, an uninstallation of the current driver should be done via “Uninstall or change

program”. Locate the application called “Sentinel HASP Run- Time” and uninstall it. Re-install Nemo Outdoor

application.

10 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 section 14.2.3 for further details on how to change the auto tuning mode

• Devices not supporting Windows 7 operating system:

o PCTEL LX tri- band scanning receiver

• Other limitations:

o IP packet capturing via Nemo Outdoor does not work with Windows 7 64-bit version. Packet

capturing must be done using third party application

o Debug logging needs administrative privileges if User Account Control Settings (UAC) is enabled. It’s

recommended to change UAC settings to “Never notify”. This can be done via User Account Control

Settings

o If UAC is set to always notify it might cause issues with data testing. PS connection can be

established but data transfer cannot be done. It’s recommended to change UAC settings to “Never

notify”. This can be done via User Account Control Settings

Figure 18. UAC settings.


11 File Format Changes

Nemo Outdoor version 6.4.0.7 supports Nemo file format version 2.15. Nemo Analyze version 6.30.1 is compatible

with Nemo file format version 2.14.

12 Known Issues

12.1 General & User Interface

• Note that if there is a system that measures acceleration in the laptop and which causes the hard disk to stop

when jolted, it should be turned off. Otherwise there may be breaks in the measurement files. With voice

quality testing this can be seen with missing MOS scores, and with other test devices with gaps in the

measurement results.

Figure 19. Lenovo active protection system properties.

• Download stops responding. Applies to Windows XP, 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 6.0\Setup\Microsoft hot fix). Please note

that for each operating system there is a separate file available:

o Windows 7, Windows6.1-KB925681-x86.msu

o Windows Vista, Windows6.0-KB925681-x86.msu

o Windows XP, WindowsXP-KB925681-x86-ENU.exe

• It is highly recommended not to use the User Parameters functionality during multi device testing as the decoding

of L3/ RRC messages will cause a high CPU load. If performance problems are found, it is recommended to

remove all user parameters from the user interface.


• If the message “Server Busy” is displayed on the screen, it is recommended that the packetmon.exe be killed

using the task manager. Packetmon.exe is used by the Microsoft Network Monitor. Microsoft Network Monitor is

needed only with the video streaming quality or IP packet capturing functionalities. If IP packet capturing or video

streaming quality measurements are not required it’s recommended to not install Microsoft Network Monitor.

12.2 UEs

12.2.1 Altair-based UEs

• Harris MBC-100: UE frequently has gaps in the trace messages during idle mode even power saving is

disabled. Issue is seen with the firmware ALT3100_04_00_02_00_32_TF. Issue has been reported to chipset

vendor

• NSN USB-lte 7210:

o NSN connection manager application must be closed when the UE is used with Nemo Outdoor. When

the UE is connected to a USB port, the connection manager is automatically launched. This can be

avoided by changing the file name. Browse to "C:\Program Files\NSN LTE Connection Manager” and

rename the “nsnltecm.exe” to “nsnltecm.exe_"

o Power saving for UE should be disabled using the ADCC application provided by Altair with UEs having

firmware version ALT3100_04_00_02_00_23_TF. UEs with the firmware ALT3100_04_00_02_00_32_TF

or later power saving can be disabled by sending the following AT command to UE:

AT%SETCFG="PW_IDLE","NONE"

o This can be done e.g. using Nemo Outdoor application via measurement properties of the UE.

o The modem gets extremely hot during measurements. When the UE is overheated, trace messages are

not reported but the data transfer continues normally.

o UE frequently has gaps in the trace messages that occur about every 10s and last for 800ms.

o To avoid performance issues with the modem, the following modification is recommended. By this

modification the Altair LogCreator standalone functionality is disabled. Browse to folder C:\Program

Files\NSN LTE Connection Manager\Tools\ Internals\LogCreator\ and open file RunLogCreator.bat with

Notepad. Modify the following string:

Original:

LogCreator.exe -SA -FN:"50" -E -Y4:"LOG_SOCK_IF" -D4:".\LoggerDB\LTELogDB.txt" -

D1:".\LoggerDB\PhyFWLogDB.txt" -Q:"50000"

Modified:

LogCreator.exe -E -Y4:"LOG_SOCK_IF" -D4:".\LoggerDB\LTELogDB.txt" -

D1:".\LoggerDB\PhyFWLogDB.txt" -Q:"50000"

12.2.2 Cassidian Handsets

• MER value is not reported by the terminal


• The terminal does not answer all incoming calls when call modes are semi duplex or duplex. Auto-answer can

be enabled in the following ways with THR880i and THR880.

o THR880i:

• Plug in a headset (Nokia Headset Type HDC-9)

• Settings / Enhancement Settings / Headset / Automatic Answer --> On

• Settings / Profiles / Headset / Personalize / Incoming Call Alert: this must not be "Off".

• Settings / Profiles / Headset / Activate

• Reboot the phone.

o THR880i: Before the terminal can be used with Nemo Outdoor, the field test mode of the terminal must

be activated by the Cassidian TETRA Prorgramming Tool. Tool is available only from Cassidian.

o For THR880 the procedure is identical, except that there is a slightly different menu structure for the

steps. Instead of Settings | Profiles | Headset, the correct path is Profiles | Headset.

12.2.3 Datang/Leadcore Handsets

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Datang DTM8129 and Leadcore

LC 8130E handsets.

12.2.4 Motorola Handsets

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Motorola V9 handsets.

• Motorola iDEN i886:

o Handovers are not reported during packet session

o CREL has incorrect old cell information (same as the new cell)

o CELLMEAS writes the "Number of cells" to n-1, even though there are n cells reported. This causes

Outdoor not to show results for one reported cell.

12.2.5 Nokia Handsets

• Nokia general issues:

o Nokia connectivity cable driver with the Windows Vista operating system has been found to cause a

problem when establishing PDP context activation and also instabilities with test terminals.

o Usage of WCDMA RLC messages will cause phone instability during high-speed PS data activity. This is a

performance restriction. By default, RLC messages are not enabled with Nemo Outdoor.

o Terminals do not update the L1 counters (first 2 octets) in uplink SACCH PDUs that are reported to Nemo

Outdoor. These two octets always have value 0x00 0x00. This problem has been reported to Nokia.

• Nokia 500:

o Video calls are not supported by the handset

o Charging problem: During measurements after battery is fully charged, charging stops and does not start

again. In this case it is possible that the battery runs out during a long test.


o USSD testing is not supported

• Nokia E7-00:




o Concatenated SMS testing is not supported. Max. 160 charaters are supported.

o Windows XP fix KB943198 (http://support.microsoft.com/kb/943198) is needed when using HSDPA

category 6 or higher data transfer speeds.



o When the UE is locked to a WCDMA carrier, it only updates the intra-freq cell list and configured triggers

from SIB11 / SIB12 messages, and ignores the "measurement control" RRC messages updating intra-freq

measurement configuration.

o During measurements, the battery might run out because the terminal can be charged only via a USB

charger. It is highly recommended to use separate charger during measurement.

o During voice quality testing if separate charger cable is disconnected from terminal it can decrease MOS

score. It is recommend to unplug the charger after measurement is stopped.

o To further increase stability, it is recommended to do the following from the UI:

• Set Theme effects to OFF

• Set Animated background to OFF

• Set Call image to none

• Set Screen saver to none

• Delete additional home screens

• Set widgets to offline mode

• Set WLAN scanning to OFF

• Set sensors to OFF

• Nokia C7-00:


o With multiRAB testing UE is crashing due to limited power.



o Concatenated SMS testing is not supported. Max. 160 charaters are supported.


category 6 or higher data transfer speeds.
















• Nokia C5-00/ C5-00.2:




category 6 or higher data transfer speeds





measurement configuration

• Nokia C5-03 (RM-697), C5-03 LAT (RM-719) and C5-04AWS (RM-720):

o With Nokia C5-03 handsets, the screen of the handset should not be activated during voice quality calls.

Activating the screen causes interference to audio and decreases MOS scores.




category 6 or higher data transfer speeds







o Video calls are not supported at the moment. This is a limitation of the test terminal.










Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Nokia handsets:

6720, 612x, N95, N80, N85, N96 and N97

Modems

• Nokia 21M-02:

o NDIS interface isn't working with Win7 operating system, dial-up connection must be used. NDIS works

with Windows XP

o SMS testing is not currently supported

o MultiRAB not supported

o The following parameters are not supported: GSM RXQ sub/ full, FER, C/I, WCDMA RACH parameters,

HS-SCCH usage, MAC-hs block rate and number of Ack/ Nack messages

12.2.6 Samsung Chipset-based UEs

• Samsung Droid Charge (SCH-i510):

o If USB disconnects, the handler must be stopped before enabling the USB Tethering from the phone

again

o MMS testing not supported

o Only LTE system supported with Nemo Outdoor at the moment

o CS voice calls not enabled as UE is supported with LTE system only at the moment

o LTE link adaptation parameter statistics are reported only for one modulation / PRB allocation per

sample duration

o The following parameters are not available: MAC Downlink/ Uplink Throughput, MAC Downlink/ Uplink

Block Rate, MAC Downlink/ Uplink Residual BLER, PDSCH Block Rate and Timing Advance


12.2.7 Qualcomm GSM/WCDMA-based UEs

General Issues:

• USSD testing not supported with Huawei and Samsung UEs

• Qualcomm-based WCDMA terminals do not report the L3 CHANNEL REQUEST and L3 MEASUREMENT

REPORT messages. RRC CONNECTION REQUEST message is missing occasionally. Extended channel type is

reported only in circuit switched mode. For example, PDTCH channel is not reported.

• With HSPA+ USB modems it is recommended to use, if applicable, the original USB extension cable that

comes with the device to achieve higher data throughput. It has been noted that when a broadband device is

connected directly to the USB port of the computer, interference might lower data throughputs in some

cases

• Some MDM 8200 based devices reports incorrect WCDMA RLC throughput for uplink direction. Issue is not

seen with all vendors.

12.2.7.1 Bandrich Modems

• Bandrich Bandluxe C320:

o Cell change during PS data transfer from GSM to UMTS can occasionally cause device reset. After this,

the device still reports GSM cell information with a constant RX level value despite the serving system

actually being UMTS. The measurement must be stopped and restarted.

12.2.7.2 Blackberry Handsets

• Blackberry Torch 9810 (RDM71UW):

o UE is not very stable

o USSD testing not supported

o Video call/ voice quality testing not supported

o MultiRAB testing not supported. If CS is ended before data transfer ends, data transfer will end with

"timeout" immediately after the call is ended

o Forcing functions are not supported

o Auto answering does not function with application tester handler

o GSM: RXQ and FER not available

12.2.7.3 Huawei Modems

• Applies to all 3G and 4G Huawei USB modems. Huawei connection manager starts up every time when device

is plugged in. As a work around connection manager .EXE file can be renamed. It still gives some reinstall

warning when device is plugged in but this can be ignored.

• Applies to all 3G and 4G Huawei USB modems . NOTE! Nemo Outdoor 6.31 enables automatic DHCP with

Qualcomm-based devices using NDIS interface. The following procedure is required only with Nemo Outdoor


version 6.30 or older. Before measurements can be done with Nemo Outdoor application, the Internet

protocol properties must be manually changed to automatic mode. This must be done always after modem is

disconnected/reconnected. It’s required also if the device stops responding during measurement: Windows

XP: Go to Start | Control Panel | Network Connections, and right-click on Huawei Broadband Connection, and

select Properties. In the Local Area Connection Properties dialog, select Internet Protocol (TCP/IP) and click

on Properties. Select Obtain an IP address automatically. Select also “Obtain DNS server address

automatically”

• Windows 7: Go to Start | Control Panel | Network and Internet | Network and Sharing Center. Select Huawei

Broadband Connection in the View your active networks list. In the Local Area Connection Status dialog,

select Properties. In the Local Area Connection Properties dialog that opens, select the Networking tab, and

Internet Protocol Version 4 (TCP/IPv4) in the This connection uses the following items view. Click on

Properties. Select Obtain an IP address automatically. Select also “Obtain DNS server address automatically”

Figure 20. TCP/ IP properties.

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Huawei USB

modems: E270, E220, E1820, E169, E180, E367 and E372.

12.2.7.4 LG Terminals

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following LG handsets:

KF700 and P500.

12.2.7.5 Novatel Modems

• Novatel Ovation MC545 USB modem:

o Novatel connection manager application must be opened when device is connected to usb port of

computer. NOTE! Before starting Nemo Outdoor application connection manager application must be

closed. Otherwise device cannot be started.


Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Novatel USB

modems: MC996D, MC998D, 930D and 990D

12.2.7.6 Option Modems

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Option USB modems.

12.2.7.7 Samsung Handsets

• Samsung Galaxy Ace:

o Video calls are not supported

o No indication of incoming SMS message

o MMS testing is not supported

o Multi RAB works only if PS connection is established after voice call connection

o Device is shutting down when system lock is used

o PDP context activations and deactivations with multiple Samsung/Qualcomm terminals occasionally

cause instability problems with dial-up connections. Avoiding these commands when using script files is

recommended.

o International numbers starting with + do not work with Samsung terminals. It is advised to use 00 instead

of +.

• Samsung Omnia 7/ Focus/ Galaxy Ace:



o Multi RAB works only if PS connection is established before voice call connection

o Device is rebooting when system lock is used

o PDP context activations and deactivations with multiple Samsung/Qualcomm terminals occasionally

cause instability problems with dial-up connections. Avoiding these commands when using script files is

recommended.

o International numbers starting with + do not work with Samsung terminals. It is advised to use 00 instead

of +.

• Samsung SGH-A847:

o USB mode must be set to "Samsung PC Studio" to have the ports available. (Can be set permanently from

Menu -> Settings -> Connectivity -> Select USB Mode -> Samsung PC Studio)

12.2.7.8 Sierra Wireless Modems

• Sierra Wireless 312U/ 319U:

o Occasionally the network adapter interface (NDIS) disappears and device cannot perform PS data

connection. Workaround is to use the modem with microSD card or by disabling microSD card from the

device. By default Sierra Wireless modems do not include microSD cards. The microSD can be


permanently disabled with either AT commands or via a command line utility. The command line utility

ItmTk.exe can be downloaded from the Nemo User Club under “Drivers for Test Devices” folder. For AT

commands use e.g. Hyperterminal.

AT!ENTERCND=”A710”

AT!CUSTOM=”USBMSENABLE”,x 0=disable 1=enable

o Device is unstable with Win 7 operating system. Issue is seen especially with Lenovo computers. Issue is

seen with failed PDP context activations and it also causes Windows file corruption on all processes

under Windows 7 operating system. Measurement log file(s) might be empty or incomplete missing

footer information. This issue has been reported to vendor. It is recommended to use Windows XP SP3

operating system. Multi measurements with 319U are not supported at the moment with Lenovo

computers.

o No indication of incoming MMS message

• Sierra Wireless 312U/320U:

o If Lenovo W510 or other computer with USB 3.0 ports is used with Sierra Wireless USB modems, the

computer crashes immediately after the second USB modem is connected to the USB 3.0 port. Problem is

experienced with all 3xx- series USB modems provided by Sierra Wireless.

o The Watcher application must normally be running simultaneously with Nemo Outdoor in the

background if default settings of the application are used. However it is recommended to change the

default settings of the Watcher application to avoid any issues during measurements. If the user wants to

close the Watcher application but still wants to be able to conduct measurements with Nemo Outdoor,

the following settings from the Watcher application must be selected. NOTE! The option names seen in

the Watcher application depend on the application version. If multiple modems are used

simultaneously on the same computer, these settings must always be changed!

Figure 21. Watcher application.

• Watcher autolaunch must be disabled. Select “No”

• On exit, select “Do nothing”

• Check for updates, select “Never”

o MCC and MNC values reported by the device are occasionally incorrect.


o Instabilities noticed with the GSM system; e.g., data connection fails more often in GSM.

o It has been discovered that cell reselection from 2G to 3G does not necessary occur even when 3G

coverage is very good.

o With multi-device configuration when Nemo multi (USB hub) is disconnected and connected again,

all devices cannot necessarily be recognized. Each device must be separately unplugged and plugged

again to the Nemo multi hub to get them to work. It is recommended to add each device separately

to multi configuration each time.

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Sierra

Wireless USB modems: Aircard 885, 306, 307, 308, 309, 310U, Siptune 215.

12.2.7.9 Sony Ericsson Handsets

• Sony Ericsson Xperia Arc S (LT-18i):

o Phone is charged via a USB data cable and charging causes interference to audio when the serving

system is GSM. Interference is cyclic and it affects the uplink MOS score with Terratec sound card.

With a fully loaded battery, the UL MOS score decreases dramatically after a 30-minute phone call.

This lasts about 30 minutes. It is highly recommended that if used in voice quality testing, the

handset is used only for observing downlink MOS scores and phone calls are made between the

handset and a fixed line with Nemo Server. In mobile-to-mobile testing, the issue is also seen in

GSM. NOTE! The issue is not seen while the serving system is WCDMA


o Multi RAB works only in this order: Voice call -> PDP context activation. If PDP context activation is

made before voice call, the test fails

o When band lock is used, the phone reboots itself. Band lock is still functioning correctly

o Driver supports Windows 7 32- bit version

12.2.7.10 ZTE Modems

• ZTE MF668A modem:

o MO voice call works when “Trace” option is selected from the device advanced properties. NOTE!

MTC calls are not supported

o MultiRAB testing can be done only if packet connection is activated before a CS call

o No indication of incoming MMS message with application tester handler

12.2.8 Qualcomm (MDM9200/ 9600)-based UEs

General Issues:

• Listed cells are not reported in idle mode

• RRC CONNECTION REQUEST message is missing occasionally

• Requested throughput is not available


• Occasionally WCDMA monitored set are shown is active set. Issue is seen with 92xx/ 96xx chipsets

• Attach/detach commands should be avoided with LTE modems. Using these commands causes instabilities in

the UEs. UEs can also reset itself. It is recommended to choose from User Interface Properties ->

Measurement -> Force detach when going to idle mode -> No. This will prevent the UE from detaching. If

attach/ detach commands are needed frequently, for example, with script files, it is recommended that radio

off/radio on commands are used instead of attach/detach.

Figure 22. User Interface properties.

• When a voice call is terminated, the PS data connection is released with UEs that require the “Trace

interface” call method to make voice calls. MultiRAB testing is not recommended due to this reason.

12.2.8.1 Huawei LTE Modems

• Huawei E392/ E398 modem:

o Huawei connection manager starts up every time when device is plugged in. As a work around

connection manager .EXE file can be renamed. It still gives some reinstall warning when device is

plugged in but this can be ignored.

o Huawei E398 modem. NOTE! Nemo Outdoor 6.31 enables automatic DHCP with Qualcomm-based

devices using NDIS interface. The following procedure is required only with Nemo Outdoor version

6.30 or older.

� Before measurements can be done with Nemo Outdoor application, the Internet

protocol properties must be manually changed to automatic mode. This must be done

always after modem is disconnected/reconnected. It’s required also if the device

stops responding during measurement: Windows XP: Go to Start | Control Panel |

Network Connections, and right-click on Huawei Broadband Connection, and select

Properties. In the Local Area Connection Properties dialog, select Internet Protocol

(TCP/IP) and click on Properties. Select Obtain an IP address automatically. Select also

“Obtain DNS server address automatically”

� Windows 7: Go to Start | Control Panel | Network and Internet | Network and Sharing

Center. Select Huawei Broadband Connection in the View your active networks list. In


the Local Area Connection Status dialog, select Properties. In the Local Area

Connection Properties dialog that opens, select the Networking tab, and Internet

Protocol Version 4 (TCP/IPv4) in the This connection uses the following items view.

Click on Properties. Select Obtain an IP address automatically. Select also “Obtain DNS

server address automatically”.

Figure 23. TCP/ IP properties.


o No indication of incoming MMS message with application tester handler

o PDP context activations and deactivations with multiple Huawei USB modems occasionally cause

instability problems with dial-up connections. Avoiding these commands when using script files is

recommended.

o Huawei E392: LTE RSRQ listed not available

12.2.8.2 LG LTE Handsets

• LG P930

o The network adapter interface is not supported completely. The device can be used if the USB

tethering is enabled through the phone menu, and PS connection setting (in Nemo Outdoor) is set to

either dial-up or automatic

o If the USB connection is disconnected (i.e. device unplugged), the USB tethering must be re-enabled

on the phone in order to use the data connection

o When using the device in LTE, user must not issue manual packet session commands, instead, if the

connection needs to be torn down, user should use Radio On/Off commands

o With voice calls user must issue an "ATS0=1" AT command to enable the incoming calls. This must be

done every time the phone is restarted.

o No indication of incoming SMS

o MMS cannot be sent/ received when packet session is activated already


12.2.8.3 Pantech LTE Modems

• Pantech UML290 USB modem.

o NDIS interface can be used to make PS connection only while device is camping on LTE. NDIS

interface cannot be used with 2G or 3G connections. Instead of NDIS interface the dial up

connection should be used.

12.2.8.4 Samsung LTE Handsets

• Samsung Galaxy S III (GT-i9305, EU):

o When the UE is used with Nemo Outdoor, other UEs cannot be used simultaneously in data testing if

the NDIS interface is used to activate PS data connection. For example, simultaneous data testing

with Huawei LTE modem and Samsung Galaxy S III handset is not possible. It should be noted that

the issue does not limit using multiple Galaxy S III UEs for simultaneous data testing or together with

non-NDIS UEs, such as, Nokia test terminals.

o To be able to make voice calls the “Trace interface” call method must be selected from Nemo

Outdoor user interface via advanced properties. NOTE! When a voice call is terminated, the PS data

connection is released. MultiRAB testing is not recommended due to this reason.

o Manufacturer information cannot be read from the UE.

o Automatic answering to incoming calls can be done only when a headset is connected to the UE.

Use the original headset included in the sales package. Connect the headset to the phone and from

the phone menu select: Settings -> Call Answering/ Ending-> Press arrow “<” on the left upper

corner to go back to previous menu. Select Settings -> Accessibility -> Call Settings -> Accessory

Settings For Call -> Automatic Answering. Automatic answering will operate only with the headset

connected.

o Auto detection should not be used to add the device. Add the device manually. See the dial-up guide

for further instructions.

o SMS/ MMS message testing not supported at the moment


o Voice quality testing is not supported with sound cards

o UE does not support WB AMR codecs


o Radio On/ Off commands are not supported

o UE is always online. This means that attach/ detach and PDP context activation/ deactivation

commands cannot be used via Nemo Outdoor.

o If data testing is done manually without script files, recording must be started before data protocols

can be accessed via Nemo Outdoor. Without recording, the data protocol options in the UI are not

available.

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

o Settings. The following settings should be activated from the phone:

Data testing:

� Settings -> More settings -> Mobile networks -> Mobile data enabled-> Enable

� Settings -> More settings -> Mobile networks -> Network Mode -> AUTO

• Samsung Galaxy S III (SGH-i747):

o To be able to make voice calls the “Trace interface” call method must be selected from Nemo Outdoor

user interface via advanced properties. NOTE! When a voice call is terminated, the PS data connection is

released. MultiRAB testing is not recommended due to this reason.



o System lock not supported. UE must be locked to certain band.

• Samsung Galaxy S III (SGH-T999):


o To be able to make voice calls the “Trace interface” call method must be selected from Nemo Outdoor

user interface via advanced properties. NOTE! When a voice call is terminated, the PS data connection is

released. MultiRAB testing is not recommended due to this reason.



o System lock not supported. UE must be locked to certain band

• Samsung Galaxy S III (SCH-i535, Verizon):

o UE must be locked either to CDMA or LTE system when used with Nemo Outdoor. Multi system

measurements with single UE are not currently supported.

o Band locking does not work with CDMA/EVDO

o MOC voice call works only when the terminal is in CDMA/EVDO only mode. When device is in LTE,

calls do not go through.

o MMS or SMS messaging not supported

o Simultaneous voice calls and data connections do not work when UE is camping in CDMA and LTE

simultaneously. Simultaneous voice and data testing can be done only when UE is locked to CDMA

o Do not use Tethering, it will disable modem and trace ports

o EVDO TX Power is not reported

o Turn off always-on packet data (Menu -> Settings -> Wireless and Network -> More Settings ->

Mobile networks -> uncheck "Use Packet Data"

• Samsung Galaxy S III (SPH-L710, Sprint):

o UE must be locked either to CDMA or LTE system when used with Nemo Outdoor. Multi system

measurements with single UE are not currently supported.

o MOC voice call works only when the terminal is in CDMA/EVDO only mode. When device is in LTE,

calls do not go through.

o Band locking does not work with CDMA/EVDO

o MMS or SMS messaging not supported

o Simultaneous voice calls and data connections do not work when UE is camping in CDMA and LTE

simultaneously. Simultaneous voice and data testing can be done only when UE is locked to CDMA

o Packet connection occasionally fails when camping on CDMA


o Do not use Tethering, it will disable modem and trace ports

o Turn off always-on packet data (Menu -> Settings -> Wireless and Network -> More Settings ->

Mobile networks -> uncheck "Use Packet Data"

o Sometimes the network adapter appears with a yellow exclamation mark. The device must be

reconnected to the USB

o EVDO TX Power is not reported

• Samsung Galaxy S II LTE (GT-I9210):

o Autodetecting the device does not always choose the correct trace port. There are two ports with

same name and sometimes the correct port is chosen and sometimes not. It’s recommended to add

device manually to Nemo Outdoor


• Samsung Galaxy S II Skyrocket i727:

o To enable auto-answering functionality, user must first initialize the terminal for auto-answer with

an AT-command "ATS0=1". This must be done only once when the phone is used for the first time.


12.2.8.5 Sierra Wireless LTE Modems

• Sierra Wireless 330U USB modem:

o In GSM UE is unstable

o PDP context activations and deactivations cause instability problems. Avoiding these commands

when using script files is recommended

o MMS message testing not supported

• Sierra Wireless 313U/ 320U/ 330U:

o With LTE max. DL data throughput is limited to ~50Mbps with 320U

o Occasionally the network adapter interface (NDIS) disappears and device cannot perform PS data

connection. Workaround is to use the modem with microSD card or by disabling microSD card from

the device. By default Sierra Wireless modems do not include microSD cards. The microSD can be

permanently disabled with either AT commands or via a command line utility. The command line

utility ItmTk.exe can be downloaded from the Nemo User Club under “Drivers for Test Devices”

folder. For AT commands use e.g. Hyperterminal.

AT!ENTERCND=”A710”

AT!CUSTOM=”USBMSENABLE”,x 0=disable 1=enable

12.2.8.6 ZTE LTE Modems

• ZTE MF820T/ MF820D/ MF880:

o PDP context activations and deactivations cause instability problems. Avoiding these commands

when using script files is recommended


• ZTE MF880:

o UE does not work in GSM (FW: M9200B-SCAQTBZD-4.0.32 (SCAQTBZM Nov 15 2011 18:58:05)

o TX Power PUCCH/ PUSCH not available

12.2.9 LG LTE Modems (LG1000/ LG 2000)

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following LG LTE USB

modems: LG L1000, LG 2000, LG G7, LG G13, LG G17, LG VL600.

12.2.10 Qualcomm 3GPP2-based UEs

• If auto detection is used to add device to Nemo Outdoor the CS dial up connection should be manually

changed to “not used”. This can be done via device properties window.

• Currently MMS send functionality is supported with CDMA terminals. Received MMS messages are not

detected.

• FER F-SCH (supplemental channel) is not working correctly

12.2.10.1 LG Handsets

• LG KX206:

o Incoming calls are not automatically answered due to a limitation of the terminal.

12.2.10.2 Pantech Modems

• Pantech UM175:

o <automatic> for PS dial-up connection does not work with the device. A workaround is to create a

dial-up connection manually.

12.3 Scanner Receivers

12.3.1 Anritsu Scanners

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Anritsu scanner

receivers.

12.3.2 Nemo FSR1 Scanner

o GPS antenna should always be connected to scanner receiver

o GPS fix must be aqruided before starting CDMA/ EVDO scanning

o GPS fix must be be aqruided once before BSIC can be decoded. After fix is aqruided GPS connection /

fix is not needed anymore with GSM measurements

o Correlator parameter is no longer utilized by the FSR1 UMTS scanning algorithms with firmware 2.07

onwards. The user is encouraged to leave this parameter at its default value


o Please read the separate Nemo FSR1 3.0 release note for further information

12.3.3 PCTEL Scanners

• PCTEL EX scanner:

o Stopping measurement fails occasionally with EX scanners. Due to this reason starting new

measurement is failing. Workaround is to power cycle scanner receiver

o Pilot scanning works only in Top-N mode. This is a device feature

o Timeslot scanning is not supported

o The channel parameter is n/a when an empty PILOTSCAN measurement event is written

• PCTEL EX Wimax scanner:

o For Top-N preamble scanning to be successful, the scanning receiver must acquire a GPS fix at least

30 seconds before starting the Nemo Outdoor application in online mode. If the existing

configuration file includes a PCTEL WiMAX scanner, it is recommended to open the configuration file

in offline mode. If the scanner does not send any results after 30 seconds, it is recommended to

send a reset command to the scanner via the user interface.

• PCTEL EX GSM/TD-SCDMA scanner:

o Secondary frequency scanning is not supported by the scanning receiver

• PCTEL LX scanner:

o With the GSM/WCDMA scanner, the Internal GPS receiver should be activated only in UMTS mode

• PCTEL MX scanner:

o When MX scanner receiver is used with a Nemo Invex UIC module, other devices must not be

connected to the same UIC module.

o The power switch must remain in the Drive Test position at all times. The Indoor Test Mode is not

available at this time.

o USB LED does not illuminate.

o The GPS antenna needs to be connected before power up.

o Occasionally scanner device does not accept scanning configuration sent by Nemo Outdoor

application even though status is “scanning”. Device is not reporting any scanning results. In such

situations it is adviced to open device measurement properties again and press ok. Issue have been

reported to the vendor.

o Nemo Outdoor application does not detect if USB data cable is disconnected during the

measurement. “Device is not responding” message is not shown.

o Detecting and connecting the PcTel MX scanning receiver for the first time takes a much longer time.

Time depends on the number of available COM ports installed in the computer. With Win XP

computers the required time is longer than with Win7 operating system. The required time is ~2min-

10 min. It is recommend to save the hardware configuration file with Nemo Outdoor after the first


connection to the scanner receiver. Starting device with an existing hardware configuration file is

much faster.

12.3.4 Rohde & Schwarz Scanners

• TSML & TSMQ Windows 7 driver version 12.0.0.0. Please read the TSMx-NewFireWireDriver.pdf document

for further information about the installation process.

• After starting the measurement it can take up to 10- 20 seconds before the scanner receiver starts reporting

the scanning results

• The TSML and TSMQ devices might not work correctly when connected directly to the Firewire port of the

computer. If connection problems are experienced, it is recommended to use a PCMCIA express adapter card

“Firewire Express card TSPC-FW1 (415010-00)”.Problems with some Dell Notebooks. Possible problems are

caused by some of the drivers installed on Dell systems by default. The problems can be solved out by

removing the original system and re-installing the operating system only with the components necessary to

operate with the scanners.

In addition, it has been recognized that the systems which only provide 1024 bytes Host rec. buffer size

(instead of 2048 bytes) can cause issues with the scanning receivers. This can be checked from the Rohde &

Schwarz TSMx Device driver properties tab. Dell Vostro 1014 model has been found to be incompatible with

the R&S TSML-GW scanner. GSM scanning cannot be performed.

Figure 24. TSMQ driver properties.

• Rohde & Schwarz TSMQ:

o EVDO measurements can only be performed properly when a CDMA2000 channel is measured as

well. In this way, the time relationship between the different PN offsets is resolved.

• Rohde & Schwarz TSML-C:

o EVDO measurements can only be performed properly when a CDMA2000 channel is measured as

well. In this way, the time relationship between the different PN offsets is resolved.

o Simultaneous pilot scanning and spectrum scanning are not supported.


• Rohde & Schwarz TSML-G:

o Simultaneous frequency scanning and spectrum scanning are not supported.

• Rohde & Schwarz TSML-W:

o Simultaneous pilot scanning and spectrum scanning are not supported

• Rohde & Schwarz TSMW:

o If more than two technologies are measured simultaneously, the scanning device might become

unstable. Possible symptoms include the following:

� High CPU load when multiple systems are measured simultaneously. Firmware 1.09 or

later should fix the issue. It can be downloaded from

http://www2.rohde-

schwarz.com/en/products/test_and_measurement/Drive_Test_Tools/hardware/TSMW-%7C-Firmware-

%7C-23-%7C-4874.html

o In case of abnormal behavior, it is recommended to restart Nemo Outdoor. It is also recommended

to power cycle the scanning receiver.

12.4 Nemo Invex

12.4.1 General

• When shutting down the system, it is recommended to close Nemo Outdoor before turning power off from

the Nemo Invex chassis

• It is highly recommended to set the event buffer size from 100000 to 50000 when Nemo Outdoor application

is used with Nemo Invex system. This can be done via user interface properties

12.4.2 Nemo Invex USB Isolation Module

• Sierra Wireless 312/ 319 USB modem:

o After power cycling the USB modem, there have been rare occasions when the USB modem is

recognized as a hard disk drive instead of USB modem. Temporary workaround is to eject the device

via system tray. Requires remote desktop connection to UIC . Issue appears also when the USB

modem is connected directly to the USB port of the UIC module

o Device is unstable with Win 7 operating system. Issue appears with failed PDP context activations

and it also causes Windows file corruption on all processes under Windows 7 operating system. This

issue has been reported to vendor.

12.4.3 Nemo Invex UIC Module

• Nemo Invex UIC module includes preinstalled Huawei E392/ E398 driver. When plugging in Huawei E392/

E398, the OS might ask the user to install a new driver. User should choose “No” to not install a new driver in

such occasion. In case a new driver is installed, the user must do the following:


o Huawei connection manager starts up every time when device is plugged in. As a work around

connection manager .EXE file can be renamed. It still gives some reinstall warning when device is

plugged in but this can be ignored.

• When the MX scanner is used with a Nemo Invex UIC module, other devices must not be connected to

the same UIC module

• When the MX scanner is used with a Nemo Invex UIC module, it is required to wait that the

Status/Power LED of the MX scanner receiver switches to green before adding the scanner to Nemo

Invex. If the device is added to Nemo Invex before start up is completed, it can crash Nemo Invex.

12.5 Other Devices

12.5.1 GPS receivers

• In case GPS fix is lost frequently during driver test, it is advisable to turn off the car radio to see if it is

generating spurious emissions that are interfering with the GPS receiver.

12.5.2 TerraTec DMX 6Fire & Maya44 USB Sound Cards

• The sound card should be connected to a USB 2.0 port. Connecting the device to a USB 3.0 port may

cause missing MOS scores and distortion in audio, which decreases the MOS score .

• If terminals report lower than expected MOS values in Voice Quality measurements, it may result from

too high CPU usage on the computer. First of all, an Intel® Core Duo processor T2500 2.00GHz or higher

is required for voice quality measurements. If you suspect that the reported MOS values are too low

and you are using multiple terminals and a scanner simultaneously, try the following. First, if you have

many applications running on the laptop, try closing the unnecessary ones. Next, disconnect the

scanner and try testing with a single terminal to see if the MOS values improve. Proceed with testing

with 1-4 terminals without using the scanner simultaneously for optimal MOS results.

• If a sound card is used as a standalone hardware connected to a laptop, the test handsets must not be

placed close to the sound card. This applies especially to GSM.

• Turn off all sounds from the test handsets. From Windows OS, choose system sounds scheme as “No

sound”.

• Note that if there is a system that measures acceleration in the laptop and which causes the hard disk to

stop when jolted, it should be turned off. Otherwise there may be breaks in the measurement files.

With voice quality testing this can be seen with missing MOS scores, and with other test devices with

gaps in the measurement results.


Figure 25. Lenovo active protection system properties.

• Voice quality measurements using Nemo Multi Lite suitcases with Nokia terminals:

o When a Nokia terminal is placed to the holder screen facing upwards, it might cause some

interference to a sound card located at the bottom of the suitcase. This is due to the fact that the

transmitting antenna is located on the rear side of the terminal. It is recommended to place the

terminal to the holder screen facing down as seen in the picture below.

Figure 26. Nokia terminal facing down.

• Wi-Fi must be turned off from the laptop. In case stationary tests are performed, for example, in the

office, Wi-Fi base station must not be located close to the measurement system.

• With Nokia C5-03 handsets, the screen of the handset should not be activated during voice quality calls.

Activating the screen causes interference to audio and decreases MOS scores.

• Voice quality echo testing:

o The following reference sample files provided with Nemo Outdoor setup cannot be used due to too

low speech activity ratio for echo testing: 5s_nb.wav, 5s_wb.wav, 7s_nb.wav and 7s_wb.wav


12.5.3 Beceem BCS200/BCSM 250/3300 Wimax

• With some Beceem-based devices it is required to use an API version newer than the one that is by

default included in the Nemo Outdoor installation package. If a diagnostics software from Beceem

(called Kannon) or a connection manager software corresponding to the firmware of the Beceem device

is available, it is sometimes possible to use the API from one of these softwares to get the device to

work properly with Nemo Outdoor. Search for a file called libxvi010.dll in Kannon or connection

manager installation directory. Back up your existing libxvi010_524.dll in Nemo Outdoor installation

folder (C:\Program Files\Anite\Nemo Outdoor) and then overwrite it with the new version. Next, run

regsvr32 Serial_Beceem_524.dll in the Outdoor installation folder. In Nemo Outdoor select the new

device "Beceem BCS200 (524)

• RSSI & CINR values are not cleared when the level goes below -120dBm for RSSI and -32dB for CINR

• Ubee Interactive U1900 Wimax

• Connection manager software from the operator must be used to make the PS session

activation/deactivation. (FW: 5.2.3013, DRIVER: 5.2.139.0, LIB: 5.2.36. )

12.6 Applications & Protocols

• VLC media player:

o Retrieving proper error messages (streaming cause codes) is missing.

• USSD testing:

o USSD testing is not supported with Huawei and Samsung UEs.

• FTP UL data transfers:

o 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:

o Other PS data connections are not allowed at the same time with the same computer. Issue has

been reported to the vendor.

o Only one VoIP connection per CPU can be done at the moment. Issue reported to the vendor.

• With Nemo Outdoor 6.3 the required Microsoft Network Monitor version is 3.4.

• IP packet capturing does not work with Windows 7/ Windows Vista 64- bit versions at the moment. Due

to this reason, video streaming quality measurements cannot be performed with these operating

systems.

• If IP packet capturing is not required it is highly recommended to uninstall it, as it affects to the CPU

performance.

• WAP testing. The WAP protocol stack used in Nemo Outdoor supports the following contents:

o Content Type


� WMLC

� WML 1.1/1.2/1.2.1 text and binary yes

� WMLScript 1.1/1.2/1.2.1 text and binary yes

� Character Sets

� WML Char-sets

� US ASCII yes

� UTF-8 yes

� UCS-2 yes

� ISO8859-1 (Latin) yes

� ISO8859-2 to 10 (other European) yes

� ISO8859-13 to 15 (other European) yes

� SHIFT JIS (Japanese) yes

� 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

• It has been discovered that with high data rates (HSDPA 7.2Mbps), data throughput values with Nemo

Outdoor might be lower than expected. To fix the problem, it is recommended to install Windows hot

fix which is immediately available. Please see http://support.microsoft.com/kb/925681 for further

information. A too small TCP window size also lowers the maximum data throughput. By using the

TCPOptimizer utility software, it is possible to change the TCP window size and obtain better

throughputs. A good TCP window size should be 128,000 bytes. After the settings have been changed,

the computer must be rebooted to make the changes effective. The TCPOptimizer utility software can

be downloaded from the Nemo user club: (http://www.anite.com/nemo-wireless-network-

measurement-solutions-anite.html?Itemid=59) You can also request it from Nemo Helpdesk

([email protected])

• If data throughput problems are experienced with Windows Vista or Windows 7 operating systems and

you are using auto-tuning TCP receive window, please see article

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

set the auto-tuning level to highlyrestriced." Auto tuning can be restricted by running “netsh interface

tcp set global autotuninglevel=restricted” from the command prompt. We have found that the

restricted mode will often allow some of the benefits of auto tuning with a number of problematic

devices. Current auto tuning level can be shown with the command “netsh interface tcp show global”.

• With MMS testing the data transfer status can occasionally show more than 100%.


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

13 Troubleshooting Device Connectivity Issues

In general all power saving options should be disabled and high performance power settings should be used.

Battery stretch should not be used and USB port power saving option should be deselected.

Figure 27. Generic USB hub properties.


14 Troubleshooting Data Transfer Issues

14.1 PS Connection Works but No Data

14.1.1 UAC Settings

• If UAC is set to always notify it might cause issues with data testing. PS connection can be established but

data transfer cannot be done. It’s recommended to change UAC settings to “Never notify”. This can be done

via User Account Control Settings. If UAC settings cannot be changed it’s highly recommended to start Nemo

Outdoor application with administration rights by right clicking Nemo Outdoor icon and by selecting “Run as

administration”.

Figure 28. UAC settings.


14.1.2 Antivirus Filtering

Disable antivirus application and Windows firewall. If data transfer still does not work, please do the following:

• Activate PS connection (activate PDP context)

• Go to Network settings and choose appropriate connection assigned for device. Go to Connection properties

and check that antivirus NDIS filtering is unchecked.

Figure 29. Connections.

Figure 30. Antivirus NDIS Filter.

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

In case low throughput values are monitored with Nemo Outdoor and also with third-party applications, the issue can

most likely be seen by observing link adaptation parameters.

For example, low average CQI and high MAC-HS 3rd

retransmission rate indicate an area of bad coverage or high

interference. Low HS-SCCH usage rate (= high HSDPA DTX percentage ratio) points to capacity, server or transmission

problems.

In LTE networks, observe physical resource block allocation (PRB) and signal to noise ratio (SNR). PRB affects

throughput directly. Values less than maximum may indicate other users in the cell, a bottleneck in the transmission

network or not enough data to be sent (application does not need all the available bandwidth). If data throughputs in


LTE are lower than expected, it is recommended to adjust the buffer size via Nemo Outdoor user interface, for

example, to value 1024. It should be noted that buffer size must be adjusted separately for each protocol (e.g. for FTP

and HTTP).

Requested throughput much higher than the actual measured throughput may indicate that there are other users

sharing the radio resources of the cell or some other bottleneck in the network that prevents the mobile from getting

the maximum achievable throughput.

High PUSCH TX power values indicate a lack of uplink coverage.

When operating in the dynamic range of link adaptation, average BLER (PDSCH BLER) should be higher than 0, typically

10-20%, in order to achieve the gain of HARQ retransmission scheme

Residual BLER after all HARQ retransmissions should be 0%. Higher values indicate that the radio link is about to drop.

Observe the MAC downlink/uplink residual BLER (%) values.

Other things that could help troubleshooting:

• Disable any firewall and/or antivirus software that could reduce the throughput. Some HSPA USB interfaces

may also install their own software which may affect to window size settings in registry.

• Disable IP packet monitoring from the advanced properties

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


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

14.2.1 All Windows Versions

∇ How to check the TCP window size from packet logs:

Using Wireshark:

1. Check the .pcap file and look at the (non FTP-DATA) TCP traffic in the middle of the transfer. Window size value tells the current TCP window size used.

Using Nemo Outdoor:

1. Open a packet grid window in Nemo Outdoor.

2. Look at the TCP traffic in the middle of an FTP transfer with PayloadLen=0:

3. Double click the frame to get detailed frame info. Look at the Tcp tree. Window shows the current

value.

Using debug logs (for developers, help desk, etc.):

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

5. A measurement file (.nmf) does not save window size info. Packet log and/or debug log is always

needed.

14.2.2 Windows XP

Check registry value of

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpipParameters\TcpWindowSize. Windows and Nemo

Outdoor both use it if it exists. The value can be changed manually or by using TcpOptimizer software. Increase value

the value if needed. If the registry value is missing, Nemo Outdoor will use its default window size which is 256 KB.

14.2.3 Windows Vista/Windows7

Windows Vista/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 XP uses is set, Outdoor reads it and

adjusts the manual window size based on this value. In most cases, the registry has been edited by a third-party

software or a USB mobile interface driver/software. This registry entry can be removed.

If the TCP auto-tuning is disabled Nemo Outdoor will use its default window size 64 KB. Outdoor 5.40 and newer

checks the auto-tuning state and does not change any window sizes if auto-tuning is enabled.

∇ How to check TCP auto-tuning state:

1. Open command prompt by typing “CMD” to ”Search programs and files” field.

2. Type ”netsh interface tcp show global”

3. Receive Window Auto-Tuning Level shows the current state.

♦ Please note that administrator rights are required to change auto-tuning settings.


4. Open command prompt by typing “CMD” to ”Search programs and files” field. Right-click and select

Run as administrator.

Figure 32. Run as administrator.

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

6. To increase the maximum TCP window size that auto-tuning uses, type “netsh interface tcp set

global autotuning=highlyrestricted”.

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

• Windows XP fix KB943198 (http://support.microsoft.com/kb/943198) is needed when using

HSDPA category 6 or higher data transfer speeds with Nokia test terminals


14.3 Issues with HTTP Browsing Testing

Selecting “Automatic configuration” or “Proxy settings” can cause problems with HTTP browsing testing, such as,

increase the page downloading time. In such a case automatic/ proxy settings should be disabled.

Figure 33. LAN settings.

RN Nemo Outdoor 6.4.0.7 5th December 2012

Documents

Transcript of RN Nemo Outdoor 6.4.0.7 5th December 2012