RN Nemo Outdoor 5.50 Guide

RELEASE NOTE FOR NEMO OUTDOOR 5.
50
14th of April 2010
Kiviharjunlenkki 1D | FI-90220 Oulu | Finland | tel. +358 50 395 7700 | fax +358 8 551 6183 | www.anite.com/nemo
RELEASE NOTE FOR NEMO OUTDOOR 5.50 1 2 Introduction New Features 2.1 Main New Features Support for LG LTE LT1000 chipset Support for Qualcomm HSPA+ chipset with MIMO support Support for Windows 7 (32 Bit) Enhanced PCTEL EX scanner measurement support and improved
2.1.1 2.1.2 2.1.3 2.1.4
spectrum analyzer measurement 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.1.10 2.2 Measurement report message modification with Nokia UEs (3G) GSM interference analysis Enhanced measurement pause implementation Enhanced GSM Missing Neighbor Detection WB- AMR Voice quality measurement support Measurement file checksum
User Interface Improved user parameter implementation Support for 16-bit and 28-bit presentation mode for UMTS cell identification New parameter selection control to replace drop-down combo box Improved parameter tree search function Redesigned script status window View menu command to open Windows Device Manager
2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.3 Map
2.3.1
BTS file support for LTE
Mandatory Parameters Optional Parameters 2.3.2 Enhanced BTS file format

2
2.3.3 2.3.4 2.3.5 window 2.3.6 2.4
Support for highlighting neighbor cells in the Map window Support for route planning in Indoor window Support for adding multiple map layers by multi selecting the files in the Map
Support for scatter plot graph type
Other improvements Support for multiple script synchronization groups Support for transfer aborting in script stop commands Support for exporting individual notifications Statistics for call re-establishment success/failure count
2.4.1 2.4.2 2.4.3 2.4.4 2.5
Application & Device Features Support for Nokia N97 NTM version 2.0 Support for PCTEL EX scanner firmware 02.01.02.24 Support for service numbers New call failure status values Support for voice quality testing with application tester handler Voice quality device name and channel number are displayed in the
2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 2.5.6
configuration Manager 2.5.7 3 4 Support for LAN interface with application tester handler
Version History New Devices 4.1 4.2 4.3 Terminals and USB Modems Scanning Receivers Nemo Outdoor 5.50 New Devices and Licenses
5 6
Qualcomm-Based WCDMA and CDMA2000 Terminals and Data Cards License Options 6.1 6.2 Nemo Outdoor Versions Replacement Process
7 8 9
Computer Hardware and Software Requirements Device Configuration and Workspace Files Installation 9.1 First-time Installation
3
9.2 10 11 12 13 13.1 13.2
Update/Upgrade Limitations with Windows 7 Operating System Limitations with Windows Vista Operating System File Format Changes Known Issues General & User Interface Terminals Datang terminals Nokia terminals Motorola terminals Sagem terminals Qualcomm WCDMA based terminals and data cards Qualcomm CDMA-based terminals and data cards EADS terminals
13.2.1 13.2.2 13.2.3 13.2.4 13.2.5 13.2.6 13.2.7 13.3
Scanners General PCTEL scanners Anritsu scanners Rohde & Schwarz scanners Other Devices
13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 13.4 14
Applications FAQ
1 Introduction
Nemo Outdoor is a pioneering and leading-edge network measurement and optimization 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, rollout, tuning, verification, optimization, maintenance, and benchmarking purposes. Nemo Outdoor is always among the first-to-market with support for the very latest technologies, currently supporting measurements on LTE, HSPA+, HSDPA, HSUPA, TD-SCDMA, cdmaOne, CDMA2000, 1xEV-DO (Rel. 0 and Rev. A), GSM, GPRS, EDGE, WCDMA, WiMAX, TETRA, UMA and DVB-H measurements are supported.
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 Outdoors 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 Anites post-processing tool Nemo Analyze, but also those of third-party vendors. In addition, Nemo Outdoors 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 200 test terminals and scanning receivers, a figure which is constantly on the increase to meet the rapidly changing customer needs for optimal satisfaction.
2 New Features
Nemo Outdoor 5.50 includes the following new major features. For the full list of all new features and error corrections, please the section version history, or read the readme.html file.
2.1 Main New Features

2.1.1 Support for LG LTE LT1000 chipset
Nemo Outdoor platform proudly presents support for the first LTE modem provided by LG Electronics. The handset (UE, user equipment) modem chip is based on the LG LT1000 chipset, and it complies with the 3GPP Long Term Evolution technology standards. The modem chip can theoretically support download speeds of 100Mbps and upload speeds of 50Mbps. The Nemo Outdoor platform now supports also scanning receivers for LTE technology from two different vendors. Simultaneous UE and scanning receiver support makes Nemo Outdoor a complete measurement solution for LTE. In the initial version, the following KPIs can be recorded from the LTE UE:
Cell measurement (per cell information) Physical channel measurements Link adaptation Current cell and connection information RACH procedure
For detailed information please see the LG LTE modem datasheet. Note! The LG devices based on LT1000 chipset can only be purchased directly from LG.
2.1.2 Support for Qualcomm HSPA+ chipset with MIMO support

HSPA+ R7 supports 2x2 downlink MIMO that uses two transmit antennas at the Node B to transmit orthogonal (parallel) data streams to the two receive antennas on the device. Using two antennas and additional signal processing of the receiver and the transmitter, MIMO can increase the system capacity and double user data rates without using additional Node B power or bandwidth. Additionally, MIMO beam forming provides gains for cell edge users where parallel MIMO streams may not be possible. To be most effective, parallel MIMO streams need a high signal-to-noise ratio (SNR) at the device and a rich scattering environment. High SNR ensures that the device will be able to decode the signal successfully, and a rich scattering environment ensures that the two data streams remain orthogonal. The MIMO benefit is therefore maximized in a dense urban (city) environment, as there is enough scattering and cell sizes are small (potentially high SNR at the device). In rural environments with large cell sizes and less scattering, the MIMO gains will be smaller. [1]
Reference: [1] HSPA+ for Enhanced Mobile Broadband
Nemo Outdoor 5.50 introduces the following parameters for HSPA+ MIMO:
MIMO status (enabled or disabled) HSDPA CQI type See 3GPP TS 125.214 subclause 6A.1.2.2. 1 = CQI type A 2 = CQI type B (This type is used when MIMO is not configured)
HSDPA CQI 2 An estimate of the link adaptation (transport block size, the modulation type, the number of parallel codes, and the spreading factor) required to enable correct reception with reasonable block error rate. The measured value is reported periodically to the network. This information can be used for data scheduling and link adaptation. This parameter is always n/a when CQI type B is used. See 3GPP TS 125.214 subclause 6A.2. Range: 0 14
Modulation, transport block size, effective coding, and retransmission rate per transport block size for the secondary stream RSSI, Ec/N0, and RSCP measurement results per antenna port (MIMOMEAS event)
HSDPA MIMO rank 2 request ratio HSDPA MIMO usage ratio
To be able to log measurement results per antenna port for RSSI, Ec/N0, and RSCP it requires that MIMO measurements must be enabled from advanced properties of device. By default this option is disabled.
Indication of MIMO usage is written to packet channel information event (PCHI) and channel quality indicator event (CQI). Information can be seen in different views. Nemo Outdoor is also shown information about the HSDPA MIMO request rank 2 and usage ratios. HSDPA MIMO request rank 2 ratio is the percentage of the time the UE is able to receive data from both antenna ports, whereas the HSDPA MIMO usage ratio is the percentage of the time the UE is actually using both antenna ports to receive data.
MIMO parameters can be also plotted on the map. With the MIMO Ec/N0, RSCP and RSSI parameters the best value is plotted on the map including both antenna ports. It is possible to plot and see locations, e.g. where MIMO is not used, and to see the MIMO usage ratio.
Additionally to the new MIMO parameters listed above, also the old events and parameters for HSPA have been updated accordingly to support both antenna ports. E.g., HSDPA physical layer requested throughput is calculated based on the number of CQI and transport block size from both antenna ports.
CQI values for the both antenna ports can be seen in different views as well. Distribution is shown for both antenna ports. For example, in the example below four percentage of time (200ms) CQI 9 has been used with antenna port 0 and CQI2 6 has been used for antenna port 1.
In the bar below, graph CQI can be seen for both antenna ports. CQI for antenna port 0 is on the top and bottom CQI value (CQI2) is for the second antenna port. E.g. in the example below three percentage of time (200ms) CQI value 6 has been used with antenna port 0 and CQI value 3 has been used for antenna port 1. Bars are colored based on CQI type to indentify used CQI type. CQI type A is shown in green and CQI type B is shown in red.
If more detailed information about the link adaptation is needed, it can be seen from the HSDPA link adaptation information table grid. Distribution is shown for both antenna ports from the last sample duration which is set to 200ms. E.g., four percentage of the time during the sample duration modulation for antenna port 0 has been 16QAM with transport block size 14411 bits and for the second antenna port 1 modulation was 16QAM with transport block size 12266 bits.
2.1.3 Support for Windows 7 (32 Bit)

Nemo Outdoor version 5.50 has been tested and approved with the Windows 7 operating system. The following devices have been verified with the initial version. For detailed information about the devices please see the separate document, Nemo Outdoor 5.50 Compatible Devices 2010.pdf. Additional devices and configurations will be tested later, and the updated results can be checked from the Nemo Outdoor 5.xx Compatible Devices document.
Device Nokia 6120, 6720, N85, N96, N97 Novatel Ovation 996D Sierra Wireless 309 USB modem Garmin 18 GPS Maya44 USB Sound Card
Driver version Nokia_Connectivity_Cable_Driver_7.1.17.0_eng.msi NvtlDriverAll_V2.03.11.001.msi 2.2.14.0 Na MAYA44_USB-v2_817.zip
Number of devices 5 1 1 1 1 10
2.1.4 Enhanced PCTEL EX scanner measurement support and improved spectrum analyzer measurement
The enhanced PCTEL EX scanner handler includes the following improvements: Support for spectrum analysis measurements
Spectrum analyzer measurements are supported now also with PcTel EX scanners. Please note that the scanning receiver must include the EX Spectrum Analyzer Option OP 211 (315016-02) to be able to support these measurements. Depending on the EX scanning receiver type, spectrum analyzer measurements can be done for DL or for both DL and UL directions.
Support for configuring the number of samples in spectrum scanning
With previous version of the Nemo Outdoor application, the sample count measured for the given frequency range was fixed to 551 samples. Sample count is now user-configurable with Rohde & Schwarz and PcTel EX scanning receivers.
With Anritsu MS2721B spectrum analyzer the supported frequency range is from 9 kHz to 7.1GHz. The sample count is fixed to 551 and RBW is adjusted automatically. The RBW is between 1 Hz - 3 MHz. It is automatically adjusted to the closest value of 1 Hz, 3 Hz, 10 Hz, 30Hz, 100 Hz ... 300 kHz, 1 MHz, 3 MHz.
11
With R&S scanning receivers the user can set the start and stop frequency between 80MHz and 3000MHz. Sample counts are divided to frequency range defined by the user. The TSMx device has a native frequency resolution of 12.8 KHz. It should be noted that the frequency shift cannot be lower than 12.8kHz, which sets the number of sample count max. limit to 5000 samples. In case the selected frequency range and sample count require a frequency shift lower than 12.8kHz, the number of sample count is automatically decreased. Sweep speed, resolution bandwidth and sampling rate are fixed. The sweep speed is 1 GHz / 0.1 sec, the resolution bandwidth is fixed to 30 kHz.
E.g. if start frequency is 80 MHz and stop frequency is 100 MHz, the total measured bandwidth is 20 MHz. If the sample count is set to 20, power (RMS) is measured from 1 MHz bandwidth. With frequency shift 12.8 KHz ~ 78 samples are taken from each 1 MHz bandwidth.
With PcTel EX scanning receivers internal frequency range is defined with start frequency, resolution bandwidth (RBW) and number of points. Stop frequency = start frequency + (frequency spacing) * (number of points 1). All the points need to be within the frequency range of the requested RF Band. Frequency spacing is between the center frequencies and spacing between points is half of the resolution bandwidth. The maximum number of samples (points) is 2560. As seen in the formula above, the stop frequency is calculated based on start frequency and number of points. Stop frequency set by the user is only requested value but it is not necessarily used during the measurement.
The user can set the start frequency or center frequency with bandwidth, stop frequency and sample count via Nemo Outdoors user interface. If the requested frequency range is not supported by the device, Nemo Outdoor automatically adjusts the frequency range for the device, and only frequency ranges supported by the scanning receiver is used to perform spectrum analyzer measurements. The number of samples is used only for the frequency range supported by the scanning receiver. Nemo Outdoor does not read the supported frequency range from the scanning receiver. For example, in the picture below the user has set the start and stop frequencies as defined within the red area. However, the scanning receiver supports only
12
frequency ranges within the green areas below. The number of samples is used only for green areas and the correct RBW is selected accordingly. It should be noted that the center frequency and bandwidth are always written to the measurement file as set by the user even if selected center frequency is not supported by the scanning receiver.
Based on the start and stop frequency and the number of samples (points) Nemo Outdoor calculates the correct resolution bandwidth (RBW). It should be noted that resolution bandwidths with PcTel EX scanner devices are fixed. Currently supported values are: 5, 10, 20, 40 and 80 kHz. Nemo Outdoor automatically selects the closest RBW to be used. E.g., if the calculated RWB were to be 8 kHz, RWB 10 kHz would be selected for use. The used RBW value can be seen in the measurement file. The number of time sweeps is set to 1, and linear power averaging is used by Nemo Outdoor.
Spectrum analyzer measurements can be done simultaneously either with frequency scanning or pilot scanning modes.
Support for multiple spectrum scanning frequency sets
Multiple frequency sets can be selected to be measured, and a list of used frequencies can also be saved as a predefined set.
13
2.1.5 Measurement report message modification with Nokia UEs (3G)

Measurement report message modification is done by enhancing the current UMTS HO forcing functionality. Handover/ Handoff control can be accessed during a voice call.
The previously supported cyclic handover mode has been removed. When handover forcing is activated, the UE stays in the target cell as long as forcing is active. The user can define the 3G offsets by enhancing target cell Ec/N0 and RSCP and by degrading non-target Cell Ec/N0 and RSCP. Three different mode request commands have been added, Normal mode, Handover Suppression, and Handover Forcing. If the terminal accepts the command, the corresponding button in Nemo Outdoor user interface will indicate this. If the command fails, this is notified as well. It is also possible to send the same command several times without clicking other commands (i.e. send a new Handover Forcing command with different bias values or forced UE to different scr. code, or in GSM to a different channel without first deactivating HO forcing. Example: the UE can be forced to scrambling code 6. Once the UE is locked to scrambling code 6, the user can set a new target cell and press the Handover forcing button again.
During normal mode forcing is disabled and the device makes 2G and 3G handovers normally.
14
System field shown in the Target cell is showing real time is the serving system GSM or WCDMA. When the serving system is GSM, the target cell and non- target cell settings are disabled. In case current serving system is GSM, but the wanted target cell is in WCDMA, band locking can be used first to lock the UE to WCDMA.
Once target cell settings including biasing information are defined by the user, the handover mode can be changed to Handover forcing mode by pressing the button. Handover forcing is done by biasing target and non-target cell Ec/N0 and RSCP values. Therefore, it is also possible to bias current active cell. For example, in the example below active set includes only one scrambling code. By pressing the Handover forcing button UE reports biasing Ec/N0 and RSCP values as set by the user. When the mode is changed back to normal mode, the UE starts reporting unbiased values.
15
Forced 3G handover & Measurement report modification. In the next example UE active set includes scrambling code 63 with Ec/N0 value -7.6dB seen as a brown curve. Scrambling code 6 and 255 are seen in the monitored set with colors blue and green. Scrambling code 6 is selected to be a target cell.
Once the button is pressed, scrambling code 6 is added to active set with Ec/N0 value -4.7dB. Scrambling codes seen in the monitored set are decreased -10dB. Scrambling code 6 is seen with Ec/N0 value -18.2dB (brown) and scrambling code 255 (green) is removed from the monitored set.
This situation is active as long as forcing/ biasing is enabled. UE keeps sending the measurement report to network with the biased values.
Once the mode is changed back to normal, the UE starts reporting unbiased values.
16
When the Handover suppression button is pressed, the UE is not allowed to make handovers to other cells. It should be noted that target cell biasing can be done only with WCDMA. Biasing/ measurement report message modification is not possible with GSM at the moment.
2.1.6 GSM interference analysis

In GSM mobile communication networks, system capacity is often limited by co-channel interference because of the surrounding cells using the same carrier frequency, or by adjacent channel interference when surrounding cells use a channel that is too close to the serving cell used by the terminal. The GSM recommendations state that reference interference will be achieved at a minimum C/I margin of 9 dB for cochannel interference and that the margin is -9 dB C/I for adjacent channel interference with voice. With packet switched data connection C/I margin should be much higher. The interference source can be BCCH or TCH channel or it can be also from out of band in some circumstances. ETSI 05.05 requirements for the interference rejection are:
Co- channel channel interference: z = 9 dB 200 kHz adjacent channel: z = -9dB 400 kHz adjacent channel: z = -41dB
17
600 kHz adjacent channel: z = -49dB
GSM co-channel and adjacent channel analysis is done real time during the measurement and playback with Nemo Outdoor. The user must enable interference analysis similarly to e.g. with missing neighbor detection. Interference detection is done based on GSM terminal and GSM scanner measurements and these measurements are combined together. GSM terminal continuously reports RX level, RX quality and C/I values. With RX level and RX quality, the sub values are used to make correct analysis in case DTX downlink is used.
In idle mode C/I and RX level values are used to trigger interference analysis from BCCH channel. Decent RX level with a simultaneous, poor C/I value is a clear sign of an interference situation. Once triggering is done, the power of BCCH channel used by the terminal is measured also by the scanning receiver. BCCH decoding must be enabled with the scanning receiver to decode BSIC information. The power of adjacent channels (+/ - 1) are also measured by the scanning receiver. It should be noted that C/I value is not available with all test terminals in idle mode. Due to this limit interference analysis in idle mode cannot be performed with all GSM test terminals.
During dedicated mode, the RX level sub, RX quality sub and C/I reported by the terminal are observed. The C/I value measured by the terminal is not available all the time in dedicated mode. E.g., when AMR speech codec is used, the terminal reports LQE (Link Quality Estimate) value to the network. During this time the C/I value reported by the terminal is not valid. Please note that not all test terminals report C/I value. Triggering points in dedicated mode are:
RX level sub and RX quality sub, OR RX level sub and C/I
These two combinations are observed all the time during the measurement to trigger interference analysis. The analysis is based on TCH channel numbers if valid data is available or on BCCH if no TCH channel data is found. If frequency hopping is used, C/I average value is used. The user can define triggering limits via the Nemo Outdoor user interface. Default values are:
RX Level Sub is above or equal to user-defined threshold (default value -90 dBm) RX Quality Sub is above or equal to user-defined threshold (default value 4) Channel average C/I is below or equal to user-defined threshold (default value 10 dB)
18
Following data is extracted from the terminal and written to the terminals measurement file:
Terminal serving channel number or TCH channels in case of frequency hopping Cell ID RX level sub RX quality sub C/I if its available
For each terminal serving channel number X, following data is extracted from the scanner measurement and written to the terminals measurement file:
Channel number, RX level and BSIC for channel X Channel number, RX level and BSIC for channel (X-1) Channel number, RX level and BSIC for channel (X+1)
Results are written to the IANALYSIS event, and can be displayed in different views, e.g., in a table grid and a bar graph. If a BTS file is used, also cell names for the serving and interfering cells can be seen during the measurement and during playback. Nemo Outdoor includes two predefined custom windows for GSM interference analysis. Table grid and bar graph.
19
2.1.7 Enhanced measurement pause implementation

RESUME event is written to the measurement file when measurement is resumed after a pause. The pause command no longer disconnects calls or other services, e.g. active PS data. Measurement events are no longer written to measurement file while pause is activated. E.g., RF-related parameters and events are not written to the measurement file. Context-related events, MARK, TNOTE and DATE are written also during pause mode. The following context-related events are written to the file also in pause mode:
Call events CAA,CAC,CAF,CAD Data events DAA,DAC,DAD,DREQ,DCOMP, Scanning events STARTSCAN,STOPSCAN Handover events HOA,HOS,HOF Location update events LUA,LUS,LUF Radio bearer events RRA,RRC,RRF,RRD PDP context events PAA,PAF,PAC,PAD Attached/ Detach events GAA,GAF,GAC,GAD
20
Routing area events RUA,RUS,RUF Short message events MSGA,MSGS,MSGF PPT call events PTTA,PTTF,PTTC,PTTD
When pause is activated, scripting is paused and resumed once the measurement is running again.
2.1.8 Enhanced GSM Missing Neighbor Detection

The maximum number of missing neighbors has been increased to 32. However, it is recommended to use default values to prevent false missing neighbor detection results. The user can now also set a minimum RX level threshold for missing neighbor. If the measured RX level is below the threshold, a channel is not detected as a missing neighbor.
Number of missing neighbors. Max. 32. Default 3. RX level : -50- -110dBm, default -95dBm
2.1.9 WB- AMR Voice quality measurement support

Adaptive Multi-Rate Wideband (AMR-WB) is a patented speech coding standard developed based on Adaptive Multi-Rate encoding, using similar methodology as Algebraic Code Excited Linear Prediction (ACELP). AMR-WB provides an excellent speech quality due to a wider speech bandwidth of 507000 Hz. Narrowband speech coders in general are optimized for POTS wire line quality of 3003400 Hz.
AMR-WB is codified as G.722.2, an ITU-T standard speech codec, formally known as Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB). G.722.2 AMR-WB is the same codec as the 3GPP AMR-WB. The corresponding 3GPP specifications are TS 26.190 for the speech codec and TS 26.194 for the Voice Activity Detector.
AMR-WB operates like AMR with 9 different bit rates. The lowest bit rate providing excellent speech quality in a clean environment is 12.65 kbit/s. Higher bit rates are useful in background noise conditions and for
21
music. Also lower bit rates of 6.60 and 8.85 kbit/s provide reasonable quality especially when compared to narrow-band codecs. All modes are sampled at 16 kHz (using 14 bit resolution) and processed at 12.8 kHz.
The bit rates are the following:
Mandatory multi-rate configuration 6.60 kbit/s (used for circuit switched GSM and UMTS connections; should only be used temporarily during bad radio connections and is not considered wideband speech) 8.85 kbit/s (used for circuit-switched GSM and UMTS connections; should only be used temporarily during bad radio connections and is not considered wideband speech; provides quality equal to G.722 at 48 kbit/s for clean speech) 12.65 kbit/s (main anchor bit rate; used for circuit switched GSM and UMTS connections; offers superior audio quality to AMR at and above this bit rate; provides quality equal to or better than G722 at 56 kbit/s for clean speech) Higher bitrates for speech in adverse background noise environments, combined speech and music, and multi-party conferencing. 14.25 kbit/s 15.85 kbit/s 18.25 kbit/s 19.85 kbit/s 23.05 kbit/s (not targeted for full-rate GSM channels) 23.85 kbit/s (provides quality equal to G.722 at 64 kbit/s for clean speech; not targeted for full-rate GSM channels)
When used in mobile phone networks, there are three different configurations (combinations of bitrates) that may be used for voice channels:
Configuration A: 6.6, 8.85, and 12.65 kbit/s (Mandatory multi-rate configuration) Configuration B: 6.6, 8.85, 12.65, and 15.85 kbit/s Configuration C: 6.6, 8.85, 12.65, and 23.85 kbit/s
This limitation was designed to simplify the negotiation of bit rate between the handset and the base station, thus vastly simplifying the implementation and testing. All other bitrates can still be used for other purposes in mobile phone networks, including multimedia messaging, streaming audio, etc.
The basic P.862 model provides raw scores in the range of 0.5 to 4.5. The wideband extension to [ITU-T P.862] includes a mapping function that allows linear comparisons with MOS values produced from subjective experiments that include wideband speech conditions with an audio
22
bandwidth of 50-7000 Hz. This means that direct comparisons between scores produced by the wideband extension [ITU-T P.862.2] and scores produced by baseline [ITU-T P.862] or [ITU-T P.862.1] are not possible, due to the different experimental context. In any given experiment, the way that subjects interpret the 1 5 MOS voting scale will be determined by the overall content of the experiment. For example, in a narrowband experiment a high-quality speech signal with a bandwidth of 300 3400Hz is likely to produce a MOS value in the region of 4.5, but in an experiment that also includes high-quality speech material with a bandwidth of 50 7000Hz, the same file may produce a MOS value as low as 3. This effect is called experimental context.
The ITU has standardized a universal PESQ to MOS mapping. This was created from a shared pool of subjective test results covering wireless, VoIP, fixed and codec-only conditions, including Japanese, British English, American English, French, German, Italian, Swedish, Dutch and Finnish. This mapping is continuous from PESQ 0.5 to 4.5 and MOS 1 to 4.55. It takes the form of a logistic with 4 parameters, and is shown below:
The mapping from PESQ score to P.862.1-MOS can be computed as follows:
For more information on this mapping, please see ITU-T recommendation P.862.1. ITU-T Recommendation P.862.2 specifies a wideband extension to P.862, and includes an integral mapping of the raw PESQ score onto a MOS scale. The mapping from raw wideband PESQ score to P.862.2-MOS can be computed as follows:
For more information on this mapping, please see ITU-T recommendation P.862.2
23
Nemo Outdoor 5.5 complies with the ITU-T Wideband extension Recommendation P.862.2 for the assessment of wideband telephone networks and speech codecs. Measurement file includes information about the audio quality type:
6 = PESQ WB (This is the same as P.862.2 standard)
The Nemo Outdoor application uses WB assessment (862.2) whenever the WB audio sample file is used. Detection is based on audio sample sampling rate. When sampling rate is >12kHz, WB assessment is used. Please note that it is then the user's responsibility to check that the system under test is really the WB system, for example, by observing the used codecs uplink & downlink. NOTE! Nemo Outdoor 5.50 does not include a WB-AMR reference sample file by default.
References:
[1] ITU-T Wideband extension Recommendation P.862.2 for the assessment of wideband telephone networks and speech codecs, T-REC-P.862.2-200711.pdf [2] Sample PESQ User Guide, pesquse.pdf
2.1.10 Measurement file checksum

Measurement file has a checksum that detects modifications to the measurement file after the measurement is stopped. The checksum is validated when loading measurement files for playback. The user is notified by the Nemo Outdoor user interface when opening a measurement file where modification is detected. However, measurement files are still opened normally. The last line in the measurement file is HASH events including time stamp and checksum information.
24
#HASH,14:46:49.262,1,"0360D938749FFE82B15545D3E55B75C0"
Measurement files made with Nemo Outdoor 5.4 or earlier do not include checksum information and notification is always prompted when such a file is opened with Nemo Outdoor version 5.50 or later.
2.2 User Interface

2.2.1 Improved user parameter implementation
Improved user parameter searching support now more complex searches where the search key is split across multiple rows of data. Now it is possible, for example, search and display multiple results in a single Layer 3 message. For example, in the example below pagingCause information is searched and decoded from RRC Paging Type 1 message. PagingCause information can be found from several different lines inside the same message. Search results can be seen in the parameters view. In addition to this, the performance of the user parameter searching has been improved. User parameters can be also now accessed directly from menu under View | User parameters.
25
2.2.2 Support for 16-bit and 28-bit presentation mode for UMTS cell identification
Cell identification presentation mode can be selected from user interface properties. By default, the 28-bit presentation mode is selected. It should be noted that currently the presentation mode affects only the Cell identification parameter that is received from the UE and written to channel information event (CHI). Cell ID (active) and Cell ID (monitored) values are taken directly from BTS file and presentation mode does not affect these parameters.
2.2.3 New parameter selection control to replace drop-down combo box

New parameter selection control that displays the parameter tree. This control is now used in map & indoors "Route Properties" dialogs "Route" & "Color" pages, scatter graphs properties dialog, "Notification" criteria dialog and in Script loop and if settings dialogs.
26
2.2.4 Improved parameter tree search function

User-specified search string can be used to search also parameter short names and possible alias names. Also, the string matching supports multiple search substrings separated by spaces i.e. "HSDPA BLER" search string matches "HSDPA MAC BLER downlink".
2.2.5 Redesigned script status window

New redesigned script status window shows in detail the current running line number and also the status of the script file for different commands. Also timeout time and script count is shown. Information is shown in a similar way to the way it is shown in the Script Editor window.
2.2.6 View menu command to open Windows Device Manager
27
Quick and convenient way to access the Windows device manager directly via the Nemo Outdoor user interface.
2.3 Map
2.3.1 BTS file support for LTE
LTE active cell and neighbor cell information is supported with BTS file. Mandatory Parameters
Parameter System Cell Name Keyword SYSTEM CELL Type String String Description LTE Unique identifier of the cell. If unique name for every cell is not available, Cell ID (CID) can be used
Channel Number Cell ID
CH
Integer
EARFCN number. Values range from 0 to 65535
CID
Integer
Cell identification Cell identification of the current cell. Range: 0 268435455
Physical Layer Cell ID
PCI
Integer
Values range from 0 to 503.
Antenna Direction
DIR
Integer
Values range from 0 to 360.
Optional Parameters
Parameter TAC Keyword TAC Type Integer Description Tracking area code Tracking area code of the currently used cell. See 3GPP TS 124.301 subclause 9.9.3.32. Range: 0 65535 Neighbor Cell Name NCELL_n String Unique identifier of the neighbor cell n. If unique name for every cell is not available, Cell ID (CID) can be used
Example: SYSTEM;SITE;LAT;LON;CELL;CH;CID;PCI;DIR;NCELL_1;NCELL_2;NCELL_3 LTE;Site Name 1;65.066053;25.458366;Cell Name 1;65535;26842545;96;0;NEMO1;NEMO2;NEMO3 LTE;Site Name 1;65.066053;25.458366;Cell Name 2;65535;26841545;2;0;NEMO4;NEMO5;NEMO6 LTE;Site Name 1;65.056053;25.458366;Cell Name 3;65535;26844545;4;90;NEMO7;NEMO8;NEMO9
28
Cell Search Method
Lines are drawn from the current location on a map to the active set and monitored set cells based on the following algorithm.
Cell Identification (Cell ID) (for active cell) Matching Channel number + Physical Layer Cell ID (for both active and monitored cells)
Note that if multiple matching cells are found, the closest cell is selected. The cell is matched only if distance is less than 50 km (31 miles).
2.3.2 Enhanced BTS file format

The new BTS file format version 1.09.03 can include also information about neighboring channels. Based on this information neighbor cells can be highlighted on the map. With the enhanced BTS file format it can also include custom user-defined columns. If the column name does not match one of the predefined column names specified in the Nemo BTS file format, the column data is loaded as custom data. Information about the custom information can be seen in the BTS tooltip, including the column name and the value.
GSM
Parameter Neighbor Cell Name Keyword NCELL_n Type String Description Unique identifier of the neighbor n. If unique name for every cell is not available, concatenation of LAC and CI can be used.
Example: SYSTEM;SITE;LAT;LON;CELL;CH;BSIC;CID;DIR;NCELL_1;NCELL_2;NCELL_3;NCELL4 GSM;Site Name 1;65.066053;25.458366;Cell Name 1;64;1;12500;0;NEMO1;NEMO2;NEMO3:NEMO4 GSM;Site Name 1;65.066053;25.458366;Cell Name 2;41;1;12501;90;SITE;SITE1;SITE2;SITE3 GSM;Site Name 1;65.066053;25.458366;Cell Name 3;20;1;12502;180; SITE4;SITE5;SITE6;SITE7
UMTS
Neighbor Cell Name NCELL_n String Unique identifier of the neighbor cell n. If unique name for every cell is not available, 28 bit cell ID can be used.
Example: SYSTEM;SITE;LAT;LON;CELL;CH;BSIC;CID;SCR;DIR;NCELL_1;NCELL_2;NCELL_3 UMTS;Site Name 1;65.066053;25.458366;Cell Name 1;10837;;;96;0;NEMO1;NEMO2;NEMO3 UMTS;Site Name 1;65.066053;25.458366;Cell Name 2;10837;;;2;0;NEMO4;NEMO5;NEMO6 UMTS;Site Name 1;65.056053;25.458366;Cell Name 3;10837;;;4;90;NEMO7;NEMO8;NEMO9
29
BTS tooltip window with user defined column name and value.
2.3.3 Support for highlighting neighbor cells in the Map window

Neighbor cells can be highlighted on the map if neighbor information is defined in a BTS file. The user can define a color to highlight the selected cell(s) with. Neighboring cells are highlighted with the selected color and the selected cell is shown with the same color but also with bolded outline. The tooltip shows neighbor cell names for the selected cell.
2.3.4 Support for route planning in Indoor window

Route planning was introduced originally with outdoor maps. Now the same feature is available also with indoor floor plans. It is a convenient way to plan a measurement route beforehand. The route plan can be saved and modified afterwards.
30
2.3.5 Support for adding multiple map layers by multi selecting the files in the Map window
User can select multiple map layers to be added on the map by selecting multiple map files with the "Add Map Layer" command.
2.3.6 Support for scatter plot graph type

New graph type is implemented to display correlation between two parameters in scatter plot. User can select x and y parameter and the graph window displays a dot for each x/y value pair. Values can be presented with several different point styles, e.g. cross, diamond, dot, triangle, etc. Several premade custom windows are included in the Nemo Outdoor setup.
31
2.4 Other improvements

2.4.1 Support for multiple script synchronization groups
Previously it was possible to synchronize all script files based on the loop count; i.e. scripts with the same loop count were synchronized if synchronize script repeats were selected from the user interface properties. With the latest implementation the user can define multiple synchronization script groups, and scripts in the same group are synchronized with each other. Devices can be assigned for certain script groups. By default script group is selected as <None> but user can also make new script group by selecting <New group> and typing in the new script group name to the field. Script group can be also saved with a specific name. To be able to use script groups, the synchronize script repeats must be selected from user interface properties. When a script group is selected as <None>, but synchronize script repeats is selected from the user interface properties, all script files that belong to the same <None> group are synchronized.
Script groups can be used, e.g. with multi configuration including two voice quality terminals and two USB modems performing PS data simultaneously. Script files used with voice quality terminals belong to the same script group and script files are synchronized with one another, whereas PS data scripts belong to the second script group.
32
2.4.2 Support for transfer aborting in script stop commands

With the new forced stop command it is possible to abort the current script command, e.g., a data transfer can be canceled if the serving system changes instead of waiting for its completion. It is also possible to set a time duration for data transfers. If data transfer is not completed during the user defined time, the Nemo Outdoor application will abort the data transfer automatically. Please note that in this case the data disconnection status is written as Normal data disconnect.
The forced stop command, e.g., with voice calls can be used with junction to conditional or wait commands as well. For example, if a call should be stopped when the system changes from GSM to UMTS, the forced stop command can be used to end the call immediately after the system changes. In the example below voice call is started only when serving system is GSM. Call duration is set to 120 seconds. It should be noted that the actual call duration is set with the line three Wait until system is UMTS but at most 120s. After a call is connected, the script starts waiting for the system to be changed to UMTS or at most 120 seconds. Call is ended with End a voice call (forced) with line 4 after 120 seconds or when system changes to UMTS, whichever comes first.
33
GSM voice call example. Voice call is started only in GSM and aborted when system changes to UMTS.
The forced stop command can be used also to stop active data transfers. In the example below the script waits until system changes to UMTS. Once system is in UMTS, the script waits 5 second before making a voice call followed by PDP context activation and FTP data transfer. Script stops waiting until system changes to GSM but at most for 60 seconds. If the system changes to GSM before 60 seconds, the voice call is continued normally until a 60-second call duration is reached. FTP data transfer is aborted immediately when the system changes to GSM, or after 60 seconds, which ever comes first. If line eight would be End a voice call (forced) voice call would be ended immediately when inter-RAT handover occurs.
PS data and voice call example. Data transfer is aborted when the system changes to GSM or after 60 seconds; voice call is continued. The call duration is 60 seconds.
34
PS data and voice call example. Data transfer and voice call are aborted when the system changes to GSM, or after 60 seconds, whichever comes first.
PS data and voice call example. Voice call is aborted when the system changes to GSM, or after 60 seconds, but data transfer is continued normally with the Stop FTP transfer (Normal) command.
2.4.3 Support for exporting individual notifications

With the improved export functionality it is possible to export individual custom-made notifications.
35
2.4.4 Statistics for call re-establishment success/failure count

Statistics for call re-establishment failure and success events have been added to user interface. New custom window Statistics- Call re-establishment added under Parameters grid.
2.5 Application & Device Features

2.5.1 Support for Nokia N97 NTM version 2.0
The following NTM firmware versions have been verified with Nokia N97. Nokia N97 (EMEA), NTM 64 v2.0.CH, 17-11-09, RM-505, V ICPR72_09w28.6 Nokia N97 US (NA), NTM 66 v2.0, 17-11-09, RM-507, V ICPR72_09w28.6
2.5.2 Support for PCTEL EX scanner firmware 02.01.02.24

2.5.2.1 GSM and WCDMA
For further details please see the SeeGull EX WCDMA-GSM 2 6 Release Notes Rev K.pdf available from CD provided by Anite. 2.5.2.2 Changes: Compatible with LTE June 2008 standard thru March 2009 and later Up to 24 Channels in the Channel list, or up to 24 Top-N Scans with one channel each Top N Signal Scan Remaining Capacity Element Number of Used Slots updated from 341 to 213 slots per channel (for 15 to 24 channels support respectively) RS_RP definition changed to be normalized to a single Resource Element (RE) PSCH_RP, PSCH_RQ, SSCH_RP and SSCH_RQ definition changed to be normalized to a single Resource Element (RE)
36
LTE
Compared to previous release under the same scanner input signal, RS_RP and RS_RQ reported measurement is 3dB lower. Compared to previous release under the same scanner input signal, PSCH_RP and SSCH_RP reported measurement is 10log10(62)=17.92dB lower. Compared to previous release when PSCH_RP and RS_RP are requested as operational modes the Sync Signal Data will be sorted based on PSCH_RP and Reference Signal Data will be sorted based on RS_RP level.
For further details please see the SeeGull EX LTE 1.3 Release Notes Rev Q.pdf available from the relevant CD provided by Anite Finland. 2.5.2.3 Changes: CDMA/ EVDO
Support for up to 24 carriers for Top-N scanning CDMA, and EVDO combined
For further details, please see the SeeGull EX CDMA~EVDO 1.3 Release Notes Rev D.pdf available from the relevant CD provided by Anite.
2.5.3 Support for service numbers

Nemo Outdoor support now also N11" and *N11 service numbers (such as 611). With these numbers the UE dials to a different number associated with that code in SIM card.
2.5.4 New call failure status values

Previously call attempt failure event (CAF) with cause value TCH blocking included also SDCCH drops and SDCCH releases. With the updated file format these three cases are now separated.
SDCCH release
Recorded for GSM when network releases the SDCCH channel before TCH assignment attempt. SDCCH drop
Recorded for GSM when call drops after SDCCH assignment and SETUP signaling message is received and before TCH assignment. TCH assignment failure
Recorded for GSM when TCH assignment fails (note that this status value can be written to the CAD measurement event after HANDOVER_COMPLETE, HANDOVER_FAILURE problem)
2.5.5 Support for voice quality testing with application tester handler
Voice quality testing is now also supported with the application tester handler using the common implementation. Please note that it is the user's responsibility to check and verify the correct audio settings
37
with the terminal and sound card in case the terminal is not found from the list of approved terminals for voice quality testing specified by Anite Finland. Please see the Nemo Outdoor user manual for further details for correct settings for verified terminals.
2.5.6 Voice quality device name and channel number are displayed in the configuration Manager
Voice quality device name and port are displayed in the configuration Manager. Information is also written to the header of the measurement file (#VQ). This will help to indentify the hardware type used for voice quality measurements. Information about the used channel number is also saved to the measurement file. This will help, for example, in troubleshooting whether the correct sound card channel number is selected for a specific test terminal.
2.5.7 Support for LAN interface with application tester handler

Support for LAN interface with application tester handler. The application test handler supports a special packet data connection called <LAN>. With this connection type the handler uses the existing data connection to perform application testing. This feature allows testing of application protocols in LAN environment or with WAN for troubleshooting purposes. For example, PS data script files can be tested using the LAN connection. LAN always activates the first interface with a valid IP address. This is the main LAN interface in most cases.
To be able to use the LAN connection with application tester hander, the test device must be connected to the computer, and a modem port must be defined for the device. For the packet-switched dial-up connection <LAN> must be selected.
38
3 Version History
Version 5.50.6 (12.04.2010) Added support for Windows 7 operating system. Added support for co-channel and adjacent channel interference analysis in GSM. Added support for forced end/stop commands in script. Added view menu command for Windows Device Manager. Added support for measurement file checksum verification. Added statistic parameters for UMTS measurement events. Added statistic parameters for GPRS/EDGE coding scheme distribution. Added statistic parameters for voice call re-establishment. Added support for 16/28 presentation mode for UMTS cell identification parameter. Added support for displaying average data throughput for multiple simultaneous transfers. Added statistic parameters for displaying the minimum, maximum and average value of several parameters. Added new scatter graph type. Added support for adding multiple map layers by multiselecting files in map window. Added support for highlighting neighbor cells in map window. Added support for LTE in the BTS file. Added support for neighbor channel information in BTS file. Added support for route planning in indoor window. Added support for user-defined custom information in BTS file. Added support for parameter tree in parameter selection control.
39
Added support for drawing dot on map window route when there is only one valid GPS coordinate in row. Added support for call script synchronization groups. They are used to synchronize script repeats. Added support for exporting and importing user-defined notifications separately. User can select which notifications to export. Added support for selecting GPS and series parameters for MapInfo export. Added support for configuring number of samples in spectrum scanning. Improved GSM missing neighbor detection. Improved UMTS handover forcing. Improved script status window. Improved script wait command. Improved automatic scale implementation in graphs. Improved color set parameter support in graphs. Improved voice quality device and port information display in Configuration Manager and measurement file header. Changed custom window limit to 500. Improved parameter tree search. Improved user parameter functionality. Improved scaling of column widths in grid windows. Improved MapInfo export results so the results are more readable and easier to post-process. Fixed a problem that occasionally caused a small error in average statistic parameters. Fixed a problem that caused application to crash when a large number of channels are configured for LTE frequency scanning. Fixed a problem that caused route line to be drawn incorrectly in map window when "Auto Clear Route" was deselected. Fixed a problem that caused BTS Sites to disappear in map window when measurement was stopped. Fixed a problem that caused marker sequence number to be shown incorrectly in map window. Fixed a problem that caused route tooltip to be shown incorrectly in map window in WiMAX measurements.
40
4 New Devices
For a full list of supported devices please see the separate document Nemo Outdoor 5.50 Compatible Devices.pdf.
4.1 Terminals and USB Modems

LG LTE USB modem o Based on LG L-1000 chipset Single band. Different variants UE category 3 (100Mbps DL/ 50Mbps UL)
LG VX8360 terminal o o o CDMA 850/ 1900, 1xEV-DO rel. 0 Without RUIM card Verified also with voice quality measurements
Motorola USBw 25100 o WiMAX Forum Wave 2 compliant, 5 MHz and 10 MHz channels for 2.3 GHz, 5 MHz and 10 MHz channels for 2.5 GHz 5 MHz, 7 MHz and 10MHz channels for 3.5 GHz o o Frequency band: 2496 - 2690 MHz Radio performance: Transmit: 200 mW maximum; highly sensitive receiver (>5dB better than WiMAX forum specifications), RX diversity, convolution turbo coding (CTC), omnidirectional antennas, hybrid automatic repeat request (HARQ) o OS: Windows XP (SP2/ SP3) and Vista
41
4.2 Scanning Receivers

No new devices.
4.3 Nemo Outdoor 5.50 New Devices and Licenses

Product Code UE is not available via Anite Finland Device SW version License Handler Driver Max. # of supported devices 1
LG LTE USB modem (L1000)
413125-00
LG VX8360
sw_ver: LGE_LTE_UE; rel_ver: Nov 17, 2008; compile_date: 15:42:08Feb 12 2010; dm_agent_ver: 007-11-06 12:00 VX836V02 (VX836V02 Oct 02 2008 17:51:23) FW: 5.2.2061039, DRIVER: 5.2.115.4001, LIB: 5.2.62208
LG LTE( L-1000)
LG LTE (L-1000)
LGE Setup_PcUSBDrv20 (20090522).msi
Qualcomm MSM6500 Compatible Beceem Wimax
Qualcomm EVDO
4.9.4.0
413126-01
Motorola USBw 25100
Beceem BCS200 (524)
5.2.115.4001
5 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. For example, video calls might not work. Please see the separate document Nemo Outdoor 5.50 Compatible Devices.pdf. for a list of verified Qualcomm-based CDMA and WCDMA terminals.
CDMA terminals 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.
6 License Options
NOTE! PLEASE READ THIS CAREFULLY!
Nemo Outdoor version 5.40 introduced a new license method which is not backwards compatible with the old system. Due to this change, e.g. Nemo Outdoor version 4.x cannot be used with the new dongle key, and old dongle keys cannot be used with Nemo Outdoor version 5.40 and onwards.
42
6.1 Nemo Outdoor Versions

Implementation for the new license method was first introduced with Nemo Outdoor version 5.20. Nemo Outdoor versions 5.20 and 5.30 support both the old and new license methods side by side. With Nemo Outdoor version 5.40 onwards support for the old method has been discontinued.
6.2 Replacement Process

All customers having valid technical support & maintenance agreement are entitled to get new dongle key(s) free of charge. Customers are kindly requested to contact Nemo Helpdesk (Nemo.Helpdesk@anite.com) for further details regarding the replacement process. For further details please read the New license method with Nemo Outdoor 5.40 November 2009.doc explaining how to upgrade the existing license.
7 Computer Hardware and Software Requirements

PC (Lenovo or Dell recommended) with Windows XP (32- bit) Professional or Windows 7 Professional (32- bit). (Windows XP highly recommended with Service Pack 3) 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 1024 x 768 with 256 colors, 1280 x 1024 recommended Internet Explorer 4.0 or higher for viewing the help file
43
8 Device Configuration and Workspace Files

Device configuration and workspace files made by Nemo Outdoor 5.40 are fully compatible with Nemo Outdoor 5.50.
9 Installation
9.1 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 5\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. When the Nemo Outdoor software installation is complete, you will need to restart the computer.
9.2 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 the existing Nemo Outdoor 4.x must be uninstalled before the Nemo Outdoor 5.50 installation using add/remove programs. 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 5\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. Please note that the setup will first uninstall the previous version of Nemo Outdoor 5.x and you must re-run the installation again to install the new version of Nemo Outdoor. When the Nemo Outdoor software installation is complete, you will need to restart the computer.
44
10 Limitations 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:
Devices not supporting Windows 7 operating system: Rohde & Schwarz (TSML/ TSMQ) scanning receivers PCTEL EX series PCTEL LX tri- band scanning receiver TerraTec DMX6 Fire Sound Card
Other limitations: Debug logging needs administrative privileges if UAC is enabled
Some device drivers do not work reliable with Windows 7. It is recommended to use the Windows XP operating system when doing measurements with the Nemo Outdoor application.
11 Limitations with Windows Vista Operating System

Some device drivers do not work reliable with Vista. It is highly recommended to use the Windows XP operating system when doing measurements with the Nemo Outdoor application.
12 File Format Changes

Nemo Outdoor 5.50 supports file format version 2.05 o Added new SDCCH release, SDCCH drop, and TCH assignment failure call failure reasons for GSM. (CAF, CAD) o o o Added support for HASH code calculated over the measurement. (#HASH) Added support for HSPA+ MIMO measurements. (PLAID, CQI, PCHI, MIMOMEAS) Added support for redundant retransmission rate with HSDPA. (MACRATE) The redundant retransmission happens when the network retransmits transport block even though the UE has already received it correctly. When this happens, most probably the network has not been able to correctly receive the ACK messages sent by the UE. Support for this parameters added to the all HSDPA capable UMTS FDD devices o Added support for residual BLER with HSDPA. (MACBLER) Support for this parameter added for all HSDPA UMTS FDD devices and UMTS TDSCDMA devices. The parameter is logged to the MACBLER measurement event o o Added support for serving grant utilization with HSUPA. (SGRANT) Added support for handover forcing status. (LOCK)
45
Added support for co-channel and adjacent channel interference analysis for GSM. (IANALYSIS)
Improved pause support by adding separate resume measurement and now some measurement events can be written when the measurement is paused. (PAUSE, RESUME)
o o o o
Modified Ec/I0 minimum value from -32 to -50 dBm. (CELLMEAS, FINGER, NMISS) Support for HSDPA MAC-hs residual BLER Support for band information to the CREL and HOA measurement events Support for SIB11bis UMTS RRC message
For further details, please see the file format document available on the CD and on the Nemo User Club.
13 Known Issues
13.1 General & User Interface
Nemo Handy multi measurement file (.nbl) cannot be opened directly with Nemo Outdoor if only one binary file (.nbl) is generated with Nemo Handy multi measurements using collect measurements. With Nemo Handy multi measurements it is recommended to convert the binary files first with Nemo File Manager to .nbf format. This issue will be fixed in Nemo Outdoor version 5.60. Data transfer status (in percentage) shown in the device information window disappears when downloading files with size exceeding ~100Mb It is highly recommended not to use the User Parameters functionality during multi device testing as the decoding of L3/ RRC messages will cause a high CPU load. If performance problems are found, it is recommended to remove all user parameters from the user interface If the message Server Busy is displayed on the screen, it is recommended that the packetmon.exe be killed using the task manager. Packetmon.exe is used by the Microsoft Network Monitor. Microsoft Network Monitor is needed only with the video streaming quality or IP packet capturing functionalities. If IP packet capturing or video streaming quality measurements are not required its recommended to not install Microsoft Network Monitor Windows Vista. Installing Microsoft Network Monitor prior to Nemo Outdoor 5.40 setup may cause problems during Nemo Outdoor 5.40 installation process on some computers. Currently the SEI event is written in "no service" state when the MNC or MCC changes during network scan
46
13.2 Terminals
13.2.1 Datang terminals
Datang DTM8120 known issues: SMS testing is not supported GSM FER, and BLER are not reported RLC/MAC signaling messages include UNKNOWN and also incorrect messages.
13.2.2 Nokia terminals

Nokia general issues: 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. 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 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 6720 known issues: Occasionally PDP contexts can drop or the terminal can reset itself during data transfers. 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 Terminal resets itself with MTC video calls. The problem is seen ~45- 50 minutes after a measurement has been started. The issue has been reported to the vendor. 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. Nokia 6720 (NTM v1.0) cannot perform a 3G->2G handover which leads to call drop. It occurs if both AMR-HR and DownLink DTX are activated in the target sector of 2G network. The issue will be fixed to NTM version 2.0. The estimated availability is by the end of April.
47
Nokia 612x known issues: Nokia 612x terminals with the Nokia_connectivity_cable_driver 7.1.8.0.msi has been found to be unstable. It is recommended that driver version Nokia_connectivity_cable_driver 6.86.5.0.msi be used Usage of WCDMA RLC messages will cause phone instability during high-speed HSDPA PS data activity. This is a performance restriction. By default, RLC messages are not enabled with Nemo Outdoor Occasionally when data rate is 1Mbps or higher, data transfer is stopped. With data rates lower than 1Mbps, the problem has not been encountered. If the problem occurs, PDP context must be first deactivated and then reactivated. This applies to the Nokia 6120 and 6121 terminals. The issue has been reported to the vendor. There is a Windows hot fix available that resolves this problem. Please login to http://support.microsoft.com/kb/925681 for further information Occasionally the terminal switches to offline mode by itself. The issue has been reported to the vendor. Occasionally terminal continuously reports high HSDPA BLER 20% or more which may lead to bad HSDPA radio resource utilization. This is also seen with lower data throughput. For example, the terminal can be using only 1 code channel instead of 5 codes. The issue has been reported to the vendor. HO forcing in UMTS mode: forcing is not released properly unless the call is not disconnected in UMTS. For example, if HO to GSM is performed, the UMTS HO forcing will be active in the next CS call in UMTS mode. This can be avoided by releasing the HO forcing during a CS call in UMTS mode. It is recommended to use band lock (UMTS) together with HO forcing in UMTS mode
Nokia N95 known issues: Usage of WCDMA RLC messages will cause phone instability during high speed HSDPA PS data activity. This is a performance restriction. By default RLC messages are not enabled with Nemo Outdoor Occasionally when the data rate is 1Mbps or higher, data transfer is stopped. With data rates lower than 1Mbps the problem has not been encountered. If the problem occurs, the PDP context must first be deactivated and then reactivated again. There is a Windows hot fix available which resolves this problem. Please login to http://support.microsoft.com/kb/925681 for further information
Nokia N92 DVB-H issues: Occasionally the FieldtestS60 application crashes or stops responding, in which case measuring with Nemo Outdoor must be stopped. The terminal must be power cycled
48
Nokia N80 issues: Occasionally during data transfers the Nokia N80 terminal (NTM 10.15.0001& 10.15.0002) may stop responding during routing area updates. 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
Nokia 6136 issues: Nokia 6136 test terminals with software version xx.xx.0001 RD or older are no longer supported. The required software version is NTM 10.18.0002 RD. Please contact Nemo Helpdesk (Nemo.Helpdesk@Anite.com) for further details and to arrange terminal updates
Nokia 612x, N85, N96, N97 During UE is locked to certain UMTS carrier UE do not send any measurement report in Cell DCH mode. Due to this reason UE do not make any cell changes. In idle mode or Cell FACH mode measurement reports are send normally 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
13.2.3 Motorola terminals

Motorola V9/V9 NA known issues: Forcing functions may cause handset instability After one to two hours of HSDPA testing, the terminal can overheat causing a malfunction in the charging of the terminal UMTS FER is not available The GPRS/EGRPS BLER values are reported incorrectly The RRC failure cause parameter is decoded incorrectly
13.2.4 Sagem terminals

Sagem OT490 known issues (LY5, 7D): Packet RX Quality is not reported by the terminal
Sagem OT590R known issues: No indication of incoming MMS message
49
13.2.5 Qualcomm WCDMA based terminals and data cards

Bandrich Bandluxe C320 known issues: 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.
Huawei E1820 HSPA+ known issues: o Nemo Outdoor does not currently support the NDIS interface with Huawei USB modems. Due to this reason, if modem port is used to create an internet connection via Nemo Outdoor it is possible that max. DL throughput is limited to ~5Mbps- 6Mbps. It is advised to use the Connection manager application that comes with the device to create the Internet connection. 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. It is also adviced to have around 5- 10 seconds delay between data transfer and NDIS activation. Otherwise the data transfer might fail. If the device is used with RAS connection, the delay time is not required. o Device is not suitable for multi testing due to the reason that data throughput is limited to ~1Mbps DL when more than one device is connected to the same computer The recommended operating system is Windows XP as data throughput is limited in Windows Vista No indication of incoming SMS message MMS testing not supported
Huawei E169 USB modem known issues: No indication of incoming MMS message No indication of incoming SMS message
Huawei E180 USB modem known issues: No indication of incoming SMS message 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
50
LG KF700 known issues: Multi RAB works only if connections are established in the following order: voice call connection first, then PS connection Video call (MOC) is not supported via Nemo Outdoor UI No indication of incoming SMS message LG KF700 USB driver conflicts with the LG USB driver for CDMA terminals. If both drivers are installed on the same computer, the terminals are not detected
Sierra Wireless Aircard 885 Compass known issues: Multi RAB works only if PS connection is established before voice call connection Watcher application must be running simultaneously with Nemo Outdoor in the background
Sierra Wireless USB 306/ 307/ 309 HSPA+ known issues: The Watcher application must normally be running simultaneously with Nemo Outdoor in the background. 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 Wacther application must be selected. NOTE! The option names seen in the Watcher application depend on the application version. o o Watcher auto launch must be disabled. Select No On exit, select Do nothing
MCC and MNC values reported by the device are occasionally incorrect Instabilities noticed with the GSM system; e.g., data connection fails more often in GSM. It has been noted that cell reselection from 2G to 3G does not necessary occur even when 3G coverage is very good.
51
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.
Novatel Ovation MC996D HSPA+ USB modem With multi configuration the device has been found unstable. This is seen with the high PDP context attempt activation failure ratio, and also the devices stop responding. With multi configuration it is highly recommended that script files be used with only one PDP context activation/deactivations command followed by several data transfers It is recommended to use the NvtlDriverAll_V2.03.11.001.msi driver with the device. The device can be used also with an NDIS connection with Nemo Outdoor
Novatel Ovation 930D/990D USB Modem known issues: Plug & play does not work with Dell Latitude computers. The driver must be installed first SMS & MMS testing is not supported Novatel Ovation MC990D. The device might stop responding after three hours
Option iCON 401 USB modem known issues: No indication of incoming MMS message No indication of incoming SMS message
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 International numbers starting with + do not work with Samsung terminals. It is advised to use 00 instead of +.
Huawei E220/ E270 known issues: The Huawei E220 modem stops responding when the band lock function is executed. Avoiding band locking with the device is recommended. Vodafone-labeled units work with Nemo Outdoor with the following workaround: o Connect Huawei E220 or E270 USB modem to a computer. Switch the computers power on and start Windows. Start Nemo Outdoor and add the device normally. Please note that the device cannot be added to Nemo Outdoor while Windows is running on the computer. If Windows is running while connecting device to the computer, reboot the computer and start Nemo Outdoor afterwards. The verified firmware includes:
52
Huawei E220, M6280A-KLRX-4.0.25ET (KLNC Sep 13 2006 17:36:31) Huawei E270, 11.304.02.03.00 (SKCBADZM Jul 27 2007 20:52:01).
Huawei E270 is not detected with Dell computers: Please login to http://forum.huawei.com/jive4/thread.jspa?threadID=322540&tstart=150&orderStr=8 for further details Qualcomm-based terminals do not report the L3 CHANNEL REQUEST and L3 MEASUREMENT REPORT messages With HSPA+ USB modems it is recommended that the original USB extension cable be used that comes with the device if applicable 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
13.2.6 Qualcomm CDMA-based terminals and data cards

LG KX 206 terminal. Incoming calls are not automatically answered due to a limitation of the terminal RLPRATE event might not be written correctly with all EVDO Rev. A devices Soft handover events (SHO) includes only removed pilots With EVDO Rev. A devices CS Call disconnect cause might be written with value 10 occasionally Extended System Parameters L3 message is not decoded correctly
13.2.7 EADS terminals

MER value is not reported by the terminal The terminal does not answer all incoming calls when call modes are semi duplex or duplex. Autoanswer can be enabled with the following ways with THR880i and THR880. 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.
For THR880 the procedure is identical, except that there is a slightly different menu structure: for steps. Instead of Settings | Profiles | Headset, the correct path is Profiles | Headset.
53
13.3 Scanners
13.3.1 General 13.3.2 PCTEL scanners
PCTEL EX scanner known issues: EX driver does not work with Windows Vista or Windows 7 Edgeport driver for PCTEL LX tri- band scanning receiver does not support Windows 7 Pilot scanning works only in Top-N mode. This is a device feature Timeslot scanning is not supported The channel parameter is n/a when an empty PILOTSCAN measurement event is written
PCTEL EX Wimax scanner known issues: 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 known issues: Secondary frequency scanning is not supported by the scanning receiver
PCTEL LX scanner known issues: With the GSM/WCDMA scanner, the Internal GPS receiver should be activated only in UMTS mode
13.3.3 Anritsu scanners

Anritsu MS2712B DVB-H analyzer known issues:
Device locks up in a random manner. When the problem occurs, the measurement must be stopped, and the phone switched first to offline mode and then immediately to online mode. After this, the measurement can be restarted.
54
13.3.4 Rohde & Schwarz scanners

After starting the measurement it can take up to 10- 20 seconds before the scanner receiver starts reporting the scanning results. The TSMx driver requires the following system files to be installed: (MSVCR71.DLL, MSVCP71.DLL, MFC71.DLL). This prevents using the device with the Nemo Outdoor application if the files are not located on the hard drive. These files are now included in the Nemo Outdoor 5.50 setup, but the problem might be seen with the previous versions. It is recommended that Nemo Outdoor be updated to version 5.50, or that the system files be copied to the Nemo Outdoor installation folder After starting the measurement it can take up to 10- 20 seconds before the scanning receiver starts reporting the scanning results Rohde & Schwarz scanning receivers cannot be used with Windows 7 operating system 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 reinstalling 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.
Rohde & Schwarz TSMQ known issues: 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
55
Rohde & Schwarz TSML-C known issues: 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 Simultaneous pilot scanning and spectrum scanning are not supported
Rohde & Schwarz TSML-G known issues: Simultaneous frequency scanning and spectrum scanning are not supported
Rohde & Schwarz TSML-W known issues: Simultaneous pilot scanning and spectrum scanning are not supported.
13.3.5 Other Devices

TerraTec DMX 6Fire & Maya44 USB
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.
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)
56
13.4 Applications
With Nemo Outdoor 5.50 the required Microsoft Network Monitor version must be 3.3. If IP packet capturing is not required it is highly recommended to uninstall it, as it affects the CPU performance. Streaming video quality measurement is currently supported with only one terminal due to limitations of the RealPlayer. With the Windows Vista operating system, video streaming quality measurements are not supported
WAP testing. The WAP protocol stack used in Nemo Outdoor supports the following contents: Content Type WMLC WML 1.1/1.2/1.2.1 text and binary 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 noted 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)
57
You can also request it from Nemo Helpdesk (Nemo.Helpdesk@Anite.com) 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 works 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
14 FAQ
Q: Can I use the Nemo Outdoor 4.x dongle or software license with the new Nemo Outdoor 5.50? A: No, you cannot. You need to get a new dongle for Nemo Outdoor 5.50.
Q: Can I use the Nemo Outdoor 5.x dongle or software license with the old Nemo Outdoor 4.x? A: No you cannot. Nemo Outdoor 5.x dongle is not compatible with the older version of Nemo Outdoor.
Q: Is it possible to upgrade Nemo Outdoor 4.x dongle remotely to support the new Nemo Outdoor 5.x? A: No, it is not. Please contact Nemo Helpdesk for further instructions.
Q: Is it possible to upgrade existing Nemo Outdoor 4.x software license to also support Nemo Outdoor 5.x? A: No, it is not. Software license is supported only with the Nemo Outdoor 5.40 onwards and only with playback version. Please contact Nemo Helpdesk for further instructions.
Q: I do not have a valid maintenance agreement. Can I still get the upgrade free of charge? A: No, only customers with a valid maintenance agreement are entitled to the free upgrade. Please contact Nemo sales (Nemo.Sales@anite.com) for further details.
Q: I am not sure if I have a valid maintenance agreement. How can I find this out?
58
A: Please contact Nemo Helpdesk.
Q: Where do I need to send the dongle for upgrade? A: Dongles can be upgraded in the following locations:
Global Anite Finland Ltd Kiviharjunlenkki 1 D 90220 Oulu Finland Tel. +358 50 395 7800 Fax. +358 8 551 6182
Americas 6225 N. State Hwy 161 Suite 425 Irving, TX 75038 USA Mobile +1 469 951 9105 +1 469 774 4608 (En espaol e portugus) Fax. +1 972 462 1640
APAC Anite Singapore Pte Ltd 101 Thomson Road #20-05 United Square Singapore 307591 Tel. +65 6254 9003 Fax. +65 6254 9885
Please contact the office nearest to you before sending the dongles.
Q: What does it cost? A: You only need to cover the delivery costs to the closest Anite/Nemo office. There will be no other costs for customers with a valid maintenance agreement.
Q: If I upgrade my operating system to Vista, can I still perform video streaming quality measurements? A: No, this is not possible at the moment. With XP, this is still possible.
59
Q: If I upgrade my operating system to Vista can I still do IP packet capturing? A: Yes, you can.
Q: Is it possible to post-process Nemo Outdoor 5.40 log files with Nemo Analyze 5.14? A: Yes it is. However new events and parameters are ignored.
Q: Can I playback Nemo Outdoor 5.x log files with Nemo Outdoor 4.x? A: No, this is not possible. Nemo Outdoor 5.x must be used for this purpose.
Q: Can I playback Nemo Outdoor 4.x log files with Nemo Outdoor 5.x? A: No, this is not possible. Nemo Outdoor 4.x must be used for this purpose.
Q: I am using a third-party post processing tool. Who I should contact to get more information on the new file format support? A: Please contact the post-processing tool vendor directly.
Q: Is it possible to have both Nemo Outdoor 4.x and Nemo Outdoor 5.x installed on the same computer? A: No, it is not possible.
Q: Are script files compatible between Nemo Outdoor 4.x and Nemo Outdoor 5.x? A: No, new script files must be created.
Q: Is it possible to use old Nemo Outdoor 4.x workspace, device configuration files and custom windows with Nemo Outdoor 5.x? A: No, these files are not compatible between Nemo Outdoor 4.x and Nemo Outdoor 5.x.
60

RN Nemo Outdoor 5.50 Guide

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

RN Nemo Outdoor 5.50 Guide

Enviado por

Direitos autorais:

Formatos disponíveis

RELEASE NOTE FOR NEMO OUTDOOR 5.

2.1.1 2.1.2 2.1.3 2.1.4

2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.3 Map

BTS file support for LTE

Mandatory Parameters Optional Parameters 2.3.2 Enhanced BTS file format

2.3.3 2.3.4 2.3.5 window 2.3.6 2.4

Support for scatter plot graph type

2.4.1 2.4.2 2.4.3 2.4.4 2.5

2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 2.5.6

9.2 10 11 12 13 13.1 13.2

13.2.1 13.2.2 13.2.3 13.2.4 13.2.5 13.2.6 13.2.7 13.3

13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 13.4 14

2.1 Main New Features

2.1.2 Support for Qualcomm HSPA+ chipset with MIMO support

Reference: [1] HSPA+ for Enhanced Mobile Broadband

HSDPA MIMO rank 2 request ratio HSDPA MIMO usage ratio

2.1.3 Support for Windows 7 (32 Bit)

Driver version Nokia_Connectivity_Cable_Driver_7.1.17.0_eng.msi NvtlDriverAll_V2.03.11.001.msi 2.2.14.0 Na MAYA44_USB-v2_817.zip

Support for configuring the number of samples in spectrum scanning

Support for multiple spectrum scanning frequency sets

2.1.5 Measurement report message modification with Nokia UEs (3G)

2.1.6 GSM interference analysis

600 kHz adjacent channel: z = -49dB

RX level sub and RX quality sub, OR RX level sub and C/I

2.1.7 Enhanced measurement pause implementation

2.1.8 Enhanced GSM Missing Neighbor Detection

2.1.9 WB- AMR Voice quality measurement support

The bit rates are the following:

The mapping from PESQ score to P.862.1-MOS can be computed as follows:

6 = PESQ WB (This is the same as P.862.2 standard)

2.1.10 Measurement file checksum

2.2 User Interface

2.2.3 New parameter selection control to replace drop-down combo box

2.2.4 Improved parameter tree search function

2.2.5 Redesigned script status window

2.2.6 View menu command to open Windows Device Manager

Channel Number Cell ID

EARFCN number. Values range from 0 to 65535

Cell identification Cell identification of the current cell. Range: 0 268435455

Physical Layer Cell ID

Values range from 0 to 503.

Values range from 0 to 360.

Cell Search Method

2.3.2 Enhanced BTS file format

2.3.3 Support for highlighting neighbor cells in the Map window

2.3.4 Support for route planning in Indoor window

2.3.6 Support for scatter plot graph type

2.4 Other improvements

2.4.2 Support for transfer aborting in script stop commands

2.4.3 Support for exporting individual notifications

2.4.4 Statistics for call re-establishment success/failure count

2.5 Application & Device Features

2.5.2 Support for PCTEL EX scanner firmware 02.01.02.24

2.5.3 Support for service numbers

2.5.4 New call failure status values

2.5.7 Support for LAN interface with application tester handler

4.1 Terminals and USB Modems

4.2 Scanning Receivers

4.3 Nemo Outdoor 5.50 New Devices and Licenses

LG LTE USB modem (L1000)

LGE Setup_PcUSBDrv20 (20090522).msi

Qualcomm MSM6500 Compatible Beceem Wimax