Tems investigation 13.1 release note

TEMS Investigation 13.1
Release Note

Prepared by: Date: Document:
Ascom Network Testing 4 November 2011 NT11-21089

© Ascom (2011)
All rights reserved. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.

Contents
1 About This Release ................................................... 1

2 Important Information ............................................... 1

3 New Features.............................................................. 1
3.1 Alternative Mobile-to-mobile AQM Solution ...........................1
3.2 CS Fallback Events and Information .......................................1
3.3 Extended Set of LTE RACH Information Elements .................2
3.4 Improved Handling of Qualcomm-based LTE Devices ..........2
3.5 CDMA/EV-DO Rev. B Measurement and Analysis ..................2
3.6 New Connectable User Terminals ...........................................2
3.7 WCDMA Scanning with Rohde & Schwarz..............................3
3.8 CDMA/EV-DO Scanning with PCTel SeeGull MX ....................3
3.9 New Connectable Scanners .....................................................4

4 Corrected Bugs .......................................................... 4

5 Enhancements ........................................................... 4

6 Removed Features ..................................................... 4

7 Known Bugs and Limitations ................................... 5
7.1 PC Application Related ............................................................5
7.1.1 Installation and Start-up ..............................................................5
7.1.2 Application Use...........................................................................6
7.1.3 Windows 7 Specific.....................................................................9
7.1.4 Windows Vista Specific ...............................................................9
7.2 Device Related: General ...........................................................9
7.2.1 Network Connect ........................................................................9
7.2.2 TCP Settings ............................................................................10
7.2.3 MTU Size ..................................................................................11
7.3 User Terminal Related ............................................................11
7.3.1 General.....................................................................................11
7.3.2 Sony Ericsson (Android) ...........................................................12
7.3.3 Sony Ericsson (R13) .................................................................12
7.3.4 Qualcomm Chipset Based Phones and PC Cards ....................13
7.3.5 Samsung Devices Based on Samsung Chipset ........................15
7.3.6 Samsung Devices Based on Samsung and Qualcomm
Chipsets ...................................................................................15
7.3.7 Sequans Devices Based on Sequans Chipset ..........................15
7.3.8 Nokia NTM3 Phones.................................................................16

© Ascom (2011) Document:
NT11-21089

7.4 AQM Module Related ..............................................................16
7.5 Scanner Related......................................................................17
7.5.1 General.....................................................................................17
7.5.2 SRU ..........................................................................................17
7.5.3 Anritsu ML8780A ......................................................................18
7.5.4 DRT 4301/4301A/4301A+ .........................................................18
7.5.5 PCTel SeeGull LX/EX ...............................................................18
7.5.6 PCTel SeeGull MX....................................................................19
7.5.7 PCTel SeeGull PCT ..................................................................19
7.6 GPS Related ............................................................................19
7.7 Call Generator Related ...........................................................20
7.8 TEMS UDP Server Related .....................................................20

8 Contact Information ................................................. 20

9 Appendices............................................................... 20
9.1 Open Source Licensing Information .....................................20
9.2 AQM with TerraTec ACU: Certification and Standard
Compliance .............................................................................21

NT11-21089

1 About This Release
Release date: 4 November 2011

2 Important Information
All customers using DRT 4301A+ scanners for LTE or WiMAX
measurements must upgrade to firmware version 02.03.02 or later.
Customers are referred to the DRT 4301A+ Miniature Receiving System
manual for installation instructions. Contact DRT support for additional
information regarding upgrading to newer firmware.
Also note the following restrictions on compatibility:
 Firmware versions 02.02.xx and earlier are not compatible with TEMS
Investigation 12.1.x and later.
 Firmware versions 02.03.xx and later are not compatible with TEMS
Investigation 12.0.x and earlier.

3 New Features
3.1 Alternative Mobile-to-mobile AQM Solution
This is a cost-efficient solution for mobile-to-mobile audio quality
measurement. Two or four mobile devices, which call each other in pairs,
are connected to an Audio Capturing Unit (ACU) which relays the audio to
the PC. The PESQ calculation is done by the PC itself, so that no separate
processing power is required in the Audio Capturing Unit. Since the voice
calls are made between the mobiles, there is also no Call Generator or
similar component in this AQM configuration.
The activities of the devices are completely controlled from TEMS
Investigation by means of a Service Control script, just as in the existing
TEMS Investigation AQM setup.
The mobile-to-mobile AQM solution is in principle RAT-independent. In
TEMS Investigation 13.1 it has been implemented for the following phones:
Sony Ericsson Xperia arc, Sony Ericsson W995, Nokia C7-00
(GSM/WCDMA); Huawei C8600 (CDMA).
Regarding the Huawei C8600 phone, see also section 7.3.4 of this
document.

Note: Error in Getting Started Manual, section 16.4 – For Huawei
C8600, the correct WAVEPLAY volume setting is –27 dB.

3.2 CS Fallback Events and Information
The “circuit-switched fallback” mechanism allows a user terminal connected
to EUTRAN to access the CS domain via GERAN or UTRAN. A number of

NT11-21089 1(21)

events – some new, some expanded in scope – report on the resulting
interaction between the terminal and networks.
Event categories:
 Call setup events
 Inter-RAT events
 Attach events

3.3 Extended Set of LTE RACH Information
Elements
A collection of new information elements deals with the RACH procedure in
LTE: RACH Type, RACH Reason, RACH Result, Preamble Step Size,
RACH Preamble Responses with PUSCH Resource, MME Group Id, and
MME Code.

3.4 Improved Handling of Qualcomm-based LTE
Devices
Network connect can now be performed for Qualcomm chipset-based LTE
devices from within TEMS Investigation, that is, without using an external
connection manager.
TEMS Investigation now also permits connection of multiple Qualcomm-
based LTE devices.

3.5 CDMA/EV-DO Rev. B Measurement and Analysis
Rev. B of the EV-DO (TIA-856) standard introduces multicarrier data
transfer in EV-DO. TEMS Investigation 13.1 allows connection of devices
built on a range of Qualcomm CDMA/EV-DO Rev. B chipsets. The
implementation has been verified with the Huawei EC367-2 device.
Presented information elements subdivide into three categories:
 Basic radio parameters
 Multicarrier serving channel information
 Forward link multicarrier RLP throughput

3.6 New Connectable User Terminals
 Sequans TD-LTE USB modem SQN3010A-USB-M1, operating on LTE
Band 40 (2300–2400 MHz) and based on TD-LTE-capable chipset
SQN3010
 Samsung Galaxy S 4G
 Android-based
 WCDMA/HSPA 1700/2100 and 2100 (Bands IV, I)

NT11-21089 2(21)

 GSM/EDGE 850/900/1800/1900
 HSUPA Category 6 (5.76 Mbit/s), HSDPA Category 14 (21 Mbit/s)
 Advanced control functionality
 Sierra Wireless AirCard 319U
 Dual-Carrier HSPA+ USB modem from Sierra Wireless
 WCDMA/HSPA+ 850/900/1900/2100 (Bands V, VIII, II, I)
 GSM/EDGE 850/900/1800/1900
 HSUPA Category 6 (5.76 Mbit/s), HSDPA Category 24 (42 Mbit/s)
 Other new LTE devices:
 BandLuxe C501
 Huawei E392
 Sierra Wireless AirCard 313U
 Other new UMTS devices:
 Huawei E367
 Huawei E372
 Novatel Option MC996D
 New CDMA devices:
 Huawei C8600
 Huawei EC367-2
 Huawei M860
 Kyocera S1350
 LG KV600
 LG KV755
 Samsung SCH-R720
 ZTE AC8710

3.7 WCDMA Scanning with Rohde & Schwarz
WCDMA pilot (Top N) scanning can be undertaken with Rohde & Schwarz
TSMW scanners. There are no restrictions on supported frequency bands
(30 MHz to 6 GHz).

3.8 CDMA/EV-DO Scanning with PCTel SeeGull MX
Support has been added for CDMA/EV-DO scanning (PN scan, RSSI scan)
with PCTel SeeGull MX.

NT11-21089 3(21)

3.9 New Connectable Scanners
 PCTel SeeGull MX LTE 800/900/1800/2600 + WCDMA 900/2100 +
GSM 900/1800
 PCTel SeeGull MX WCDMA 850/1900/2100 AWS + GSM 850/1900 +
CDMA/EV-DO 850/1900/2100 AWS
 Anritsu ML8780A WCDMA 2100/1500

4 Corrected Bugs
 Relationship between and band lock and cell lock functions for Sony
Ericsson phones not fully explained in documentation. – Clarifying notes
added in User’s Manual, section 19.2.2.6 “GSM Cell Selection” and
section 19.2.2.13 “WCDMA Cell Selection”.
 X-axis labels shifted in bar chart window, with a spurious zero label
appearing on the far left.
 Radio Link Timeout not displayed for Nokia phones. – Bug fixed in
decoding of Nokia phone messages.
 Non-existent message “Tracking Area Update Reject” displayed in
decoding of Samsung LTE modem signaling. – Decoding of LTE
ESM/EMM signaling corrected to agree with latest spec.
 Application locked up during recording that involved SIB scanning. –
Pre-processing of SIB scan messages for presentation improved in
TEMS Investigation software.
 Too high Tx Power presented for Qualcomm LTE UEs.

5 Enhancements
Regarding support for new devices, please see chapter 3.

6 Removed Features
None

NT11-21089 4(21)

7 Known Bugs and Limitations
7.1 PC Application Related

7.1.1 Installation and Start-up
 When installing TEMS Investigation for the first time, it may take 10–20
minutes for the installation to complete (if .NET Framework 4.0 was not
already present on the PC). On some PCs, a reboot may take place
after the .NET Framework installation.
 In the course of the TEMS Investigation 13.1 installation, if the HASP
key contains HASP SRM version 4 firmware, it will be upgraded to SRM
version 5. While the upgrade is in progress, this is indicated by the
HASP key LED blinking. If the blinking does not stop within one minute,
the firmware upgrade has failed. You then need to restart the Sentinel
HASP License Manager service in Windows, or reboot the PC.
 The application start-up time may be prolonged if slow network shares
are mounted on the machine.
 For the license attach/detach mechanism in the Admin Control Center
to work correctly, the Sentinel HASP License Manager on the license
server and client machines must be of the same version. Always
crosscheck the versions manually to avoid attach/detach failures.
 If TEMS Investigation takes a long time to start up (more than about 45
seconds), the delay may be caused by the OS trying unsuccessfully to
check the application’s Verisign certificate. If a network has been
detected, the OS will try to contact Verisign to verify that the certificate
is not on the Certificate Revocation List (CRL). TEMS Investigation will
not continue until this procedure times out.
There are two ways to remedy this:
1) Open up your proxy to enable access to the Certificate Revocation
List. The details of how to accomplish this may vary between
countries.
2) Turn off the certificate revocation check in Internet Explorer:
 Open Internet Explorer, and from the Tools menu select Internet
Options.
 On the Advanced tab, under Security, uncheck the option “Check
for publisher’s certificate revocation” and click Apply.
(This procedure can be automated by the use of Group Policies.)
 When installing TEMS Investigation under Chinese or Japanese
Windows, TEMS Investigation will not recognize file paths such as
C:User<user name>..., where <user name> contains Chinese or
Japanese characters. This will prevent proper use of the application.
(Similar problems may occur with other non-ASCII characters.)

NT11-21089 5(21)

7.1.2 Application Use

Note: PC settings and hardware capabilities that are checked by the
Computer Diagnostics utility are not covered here. See the Getting
Started Manual, chapter 7.

 User-created workspaces from previous versions of TEMS Investigation
need to be recreated. New workspaces are supplied with the
application.
 When using the Copy Worksheet function, any Map settings will be lost.
 When many devices are used for data collection, the number of
windows in the workspace should be kept to a minimum to lower the
CPU load. It is also advisable to start a new logfile recording at least
once every hour in order to reduce RAM consumption.
 The XML cell file format permits only “YYYY-MM-DD” as date format.
 A separately powered USB 2.0 hub is strongly recommended for drive
tests. That is, the USB hub should not be powered through the USB
port alone. Depending on the type and number of devices connected,
the hub may otherwise not be able to deliver sufficient power. It needs
also to be stressed that an uninterrupted USB connection between PC
and device is vital for successful recording of realtime measurement
data.
 Some GPS units may be erroneously identified in Windows as an “MS
Serial Ballpoint” device. If this occurs, perform the following steps:
1) With Administrator privileges on the PC, choose Start > Run >
regedit.
2) Navigate to HKEY_LOCAL_MACHINE > System > Current Control
Set > Services > sermouse.
3) Locate the entry “Start” and double-click on it.
4) Change the value Data from 3 to 4. This will prevent Windows from
identifying the GPS device as a mouse. Note, however, that leaving
the setting Data = 4 will prevent you from identifying new mouse
devices until you change the value back to 3.
 During logfile recording as well as during logfile replay, temporary files
are created by the application to enable the user to browse the history
of the logfile. These files can become very large (3–4 times the logfile
size), the exact size depending on the number of devices activated in
the application at recording time. The temporary files are named
according to the format “temsn” and created in the Windows temp
directory (default: C:pathtmp, where the path is defined by the
environment variable TMP; in Windows XP, the TMP variable can be
modified from the Control Panel: System Properties > Advanced >
Environment Variables). Make sure there is plenty of space on the disk
where the temp directory resides. The temporary files are removed
when you exit the application; however, if the application terminates

NT11-21089 6(21)

abnormally, this might not happen. The files must then be removed
manually.
 When using the pinpointing function, you must click the Pinpoint button
before starting logfile recording, not the other way around.
 You cannot zoom or manually pan the map (using the Map window
toolbar buttons) while pinpointing. (However, as soon as you pinpoint
close to the edge of the Map window, the map will scroll automatically.)
 When turning on all extended logs for Sony Ericsson and Qualcomm
chipset based devices (without turning off something else), the data
volume logged will be huge, and it may be necessary to swap logfiles
more often than once every hour to prevent RAM usage from becoming
excessive.
 Whenever possible, logfile swapping should be done in idle mode.
 The Swap Logfiles function does not work properly if used during
scanning.
 If you swap logfiles while running the Status Control Monitor, the Logfile
Progress indicator turns red, and the message “No records written to
file” appears. After a few updates, Logfile Progress is indicated
correctly.
 Logfiles merged with uplink data (MTR) files may contain internal
reports with erroneous timestamps.
 TEMS Pocket 8.x (HTC) logfiles are not positioned correctly using the
TEMS Pocket Positioning Tool, so that the TAB file cannot be opened in
TEMS Investigation. The workaround is to create a new TAB file
manually in TEMS Investigation using the Position Map function.
 When a Network Connect activity is executed in a Service Control
script, a restricted form of IP sniffing is started which is performed
continuously for the sake of collecting input to KPI calculations. If your
data collecting device is unable to perform the IP sniffing (example:
Sierra Wireless USB 306/307 connected via NDIS under Windows 7),
you can work around the problem by editing a line in the file <TEMS
Investigation install dir>ApplicationInvestigation.exe.config, which by
default reads: <dataServicesConfiguration ipSniffEnabled="true"
ignoreIPSniffError="false" />. You can either disable IP sniffing by
setting ipSniffEnabled="false" (and consequently miss out on KPI data),
or you can ignore failure to start IP sniffing and go ahead with the
execution anyway: ignoreIPSniffError="true". By the latter method you
obtain KPIs normally for all devices where the IP sniffing does not fail.
 Service Control Designer: To copy, cut, and paste material in text fields,
use the context menu in the text field. The keyboard accelerators
Ctrl + C, etc. cannot be used for this purpose.
 Service Control Designer: In a script workflow, it is not possible to
collapse the individual branches (Sequence activities) of a Parallel
activity. Only the Parallel activity as a whole can be collapsed.

NT11-21089 7(21)

 Service Control Designer: If multiple Service Control Designers are
open simultaneously, a script run from one of them could fail.
 When you save a Service Control script to file, any user names and
passwords (e.g. for FTP or HTTP servers) given in commands are
saved with the file (encrypted). Note that another user who runs your
script will be accessing the server using the same user name and
password.
 When running video telephony from a Service Control script, the phone
needs to be locked on WCDMA.
 SMS and MMS testing with Service Control scripts does not work for
CDMA devices that do not support AT commands.
 UDP upload testing causes very high CPU load.
 During VoIP testing with CounterPath, PESQ drops which do not
correlate to radio or other network problems may sometimes occur.
 During CS voice testing, PESQ is not computed for the AMR-WB
speech codec. (This limitation does not apply to VoIP.)
 The phone must be locked to GSM when performing GSM Channel
Verification with a WCDMA capable phone. How to set this lock (on
Radio Access Technology) is described in the User’s Manual,
section 8.1.6.
 The Channel Verification tool causes the Sony Ericsson W600i phone to
be deactivated, and moreover it cannot be reactivated until the
application has been restarted.
 IP packet capture/analysis may stop after less than one minute when
using multiple CDMA phones.
 During video streaming, if stripes appear in the picture, try changing the
color setting to 16 colors in the Windows display settings.
 If Iperf is installed on a Linux/Unix server, the network port on that
server must be mapped to terminal vt100.
Map the port by editing a line in /etc/profile:
tset -I -Q -m network:vt100
An incorrect mapping will cause the following error:
tset: unknown terminal type network
Terminal type?
 If Iperf is installed on a Linux/Unix server, the PS1 variable must be
changed to PS1=”>” in the Unix shell Bash in order for Iperf information
to be correctly displayed.
 If Iperf is installed on a Linux/Unix server, then to enable the use of
passwords in Iperf testing, make sure the default setting for passwords
(PasswordAuthentication yes) is used in the configuration file on the
SSH server /etc/ssh/sshd_config.
 The waveform in Network Bandwidth line charts will be jagged and not
smooth, due to the low resolution of the Iperf process.

NT11-21089 8(21)

 Full IP sniffing can only be done with one device at a time. If full IP
sniffing with more than one device is attempted, TEMS Investigation will
stop working correctly.
 IP sniffing (unless restricted using the “Optimized Performance” option)
cannot be turned on while doing data service testing at throughputs
above 25 Mbit/s. If turned on, it will cause TEMS Investigation to crash.
The “Full” IP sniffing option is not recommended at all at such high
throughputs.
 When using the serving cell indication in the Map window to show the
strongest scanned CPICH, this works only for the 1st UMTS frequency
(the one decoded into the information elements named “1st”).
 The information element “PDN Connection IPv6 Address” is currently
not displayed.
 The information element “LTE Total RS Power” is valid only for the
bandwidths 5 MHz and 10 MHz.

7.1.3 Windows 7 Specific
 Under 64-bit Windows 7 (x64), the Investigation.exe file must be
excluded from virus scanning to avoid a known issue with the Sentinel
HASP driver. The problem does not arise with 32-bit (x86) Windows 7
installations.
 User Access Control needs to be turned off to allow IP trace. It may also
need to be disabled for other reasons, depending on its configuration.

7.1.4 Windows Vista Specific
 User Access Control needs to be turned off to allow IP trace. It may also
need to be disabled for other reasons, depending on its configuration.
 When starting the GeoSet Manager, an error message about writing to
the Windows registry appears; however, .gst files can still be created.

7.2 Device Related: General

7.2.1 Network Connect
 Some LTE devices must be connected to the network manually, using
their connection managers, rather than automatically in the Service
Control script. See the User’s Manual, section 18.17.3.1, where this is
detailed for a range of devices.
Note that when the network connect is performed manually, a Network
Connect activity must still be included in the Service Control script for the
subsequent data service activities to execute correctly.

NT11-21089 9(21)

7.2.2 TCP Settings
 In Windows XP, some issues with poor uplink and downlink throughput
can be resolved by manually adjusting the TCP window size. This
setting is found in the registry under:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip
Parameters
The ideal TCP window size for a given maximum bit rate is dependent
on the network delay. Here is an example showing how to do the
calculation.
Suppose that:
Maximum bit rate = 3.6 Mbit/s
Network delay = 500 ms
Maximum Segment Size (MSS) = Maximum Transmission Unit (MTU) –
header size = 1500 – 40 = 1460 bytes
Then:
Bandwidth-delay product (BDP) = 3.6 × 106 bit/s × 500 × 10–3 s =
1,800,000 bits, or 1,800,000 / 8 = 225,000 bytes
Unscaled TCP Receive Window (RWIN) = floor(Max Buffer Size / MSS)
= floor(65,535 / 1460) = 44.
That is, 44 segments totaling 44 × 1460 = 64,240 bytes is a good
configuration for a connection with MTU = 1500 and MSS = 1460.
To obtain the optimum scaled RWIN, multiply the unscaled RWIN by 2
repeatedly until the BDP is reached:
64,240 × 2 = 128,480 (< BDP)
128,480 × 2 = 256,960 (> BDP).
Thus, given the above assumptions, the optimum RWIN = TCP Receive
Window is 256,960 bytes.
You will need to restart Networking in Windows XP for the new TCP
window size to take effect.

 Windows Vista and Windows 7 have a function for automatic tuning of
TCP settings. Check whether that function is enabled as follows:
1) Open a Command Prompt using the Run As Administrator option
(right-click the Command Prompt item on the Start menu).
2) Type netsh interface tcp show global and inspect the value returned
for Receive Window Auto-Tuning Level.
3) If this parameter is disabled, give the command netsh interface tcp
set global autotuninglevel=<autotunelevel> to enable it. The value of
<autotunelevel> should be “highlyrestricted” if the server you are
contacting does not have RFC1323 implemented or does not
support the TCP receive window scaling factor. Otherwise,
<autotunelevel> should have the value “normal”.

NT11-21089 10(21)

7.2.3 MTU Size
For LTE operation it may be necessary to adjust the MTU (Maximum
Transmission Unit) size, that is, the maximum IP packet size in bytes. The
optimum MTU size depends on the network bandwidth and other factors,
so it is impossible to give a universally valid recommendation. In general,
however, the faster the LTE network, the more important it is to choose a
good MTU setting to be able to approach the maximum achievable
throughput.
Here is how to change the MTU size:
 Windows XP:
1) In the registry, browse to
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
TcpipParametersInterfaces<Adapter ID>,
where <Adapter ID> is the network adapter identity.
2) In the right-hand panel, create a new DWORD named “MTU” and
assign to it the desired value in decimal.
 Windows Vista, Windows 7:
1) Open a Command Prompt using the Run As Administrator option
(right-click the Command Prompt item on the Start menu).
2) Run the command netsh interface ipv4 show interfaces and note the
identity of the relevant interface.
3) Run the command netsh interface ipv4 set subinterface <interface id
from step 2> mtu=<desired MTU setting> store=persistent.
Example: netsh interface ipv4 set subinterface 25 mtu=1460
store=persistent

7.3 User Terminal Related

7.3.1 General
 If you intend to use a USB hub for connecting multiple devices, install
the devices one at a time to avoid problems with driver mix-up in
Windows. It is wise to do this in the office, before starting TEMS
Investigation. When all devices have installed, start TEMS Investigation
and check that all devices are detected properly and can be activated in
the application.
 If the connection manager of a device is started automatically at device
insertion, it will block the AT interrogation performed by TEMS
Investigation, and the device will show up as “Unknown”. To resolve
this, terminate the connection manager, and click the Refresh button in
TEMS Investigation to repeat the autodetect procedure.
 Certain connectable devices respond to very few AT commands. One
example is the Samsung SPH-M320.

NT11-21089 11(21)

7.3.2 Sony Ericsson (Android)
General instructions for Xperia arc and Xperia X10:
 Make sure no APN is set in the phone: Press the Menu button, then
choose Settings > Wireless & networks > Mobile networks > Access
Point Names, and make sure nothing is set. (If an APN is already
present in the phone, the Network Connect activity in the TEMS
Investigation script, which tries to set the APN, will fail.)
 Activate USB debugging so that all relevant ports become visible: Press
the Menu button, then choose Settings > Applications > Development,
and make sure USB debugging is enabled.
Instructions for driver installation:
 Connect the Xperia phone to the PC. Windows will try to find drivers;
when the automatic driver installation fails, open the Device Manager on
your computer.
 Locate the Xperia phone with missing drivers under Device Manager >
Other devices.
 Right-click the first “SEMC HSUSB Device” and select Update Driver
Software > Browse my computer for driver software.
 Browse all the way to the directory where the applicable driver for your
operating system is stored; note that 32-bit and 64-bit Windows must be
distinguished. Example of path: ...DriversSony Ericssonx10Win64.
 Click Next.
 Repeat the procedure for the remaining “SEMC HSUSB Device” items.

7.3.3 Sony Ericsson (R13)
 Avoid mixing USB 2.0 (High Speed) and USB 1.1 (Full Speed) Sony
Ericsson phones, as doing so will cause some SEMC devices not to
communicate correctly over AT with TEMS Investigation. See also the
Getting Started Manual, section 10.4.
 USB 1.1 default Sony Ericsson phones are: Z750, C702 and W760.
 USB 1.1 and 2.0 changeable Sony Ericsson phones are: C905 and
W995.
 In Windows Vista, device drivers can take a while to get running after
you plug in a Sony Ericsson phone, so that the detect may take some
time to complete. (Look at the status indicator on the Navigator’s
Equipment tab to view the current detect status for the device.)
 When connecting a USB hub with Sony Ericsson phones to a Windows
Vista PC, the phone with the lowest port number in the USB hub is
sometimes not detected. This is solved by unplugging and reinserting
the phone.

NT11-21089 12(21)

 When using a USB hub with a Windows Vista PC for connecting Sony
Ericsson phones, we recommend that you plug the phones into the USB
hub one at a time.
 The driver software for the memory stick needs to be installed on the
PC to avoid problems when connecting a phone that is turned off. If the
K790/K800 has a memory stick, do as follows when first connecting the
phone:
1) Insert the USB cable.
2) Wait for drivers to install.
3) Unplug and insert again to make the memory stick driver install.
 If a Sony Ericsson TEMS Pocket phone is activated in TEMS
Investigation and the USB cable is pulled, TEMS Pocket will remain
disabled until either 1) the phone is restarted, or 2) the phone is
activated again in TEMS Investigation and then deactivated normally in
the application.
 When AMR-WB speech coding is used, the Sony Ericsson phone is
unable to measure GSM C/I.
 When locking the phone on a WCDMA cell, the signal strength
measurements will become invalid for other cells.
 GSM channel verification: 1) The phone must be on GSM before start of
test, otherwise the test will stall and after 20 seconds an error “BCCH
Lost” will be displayed. 2) The channel verification function attempts to
disable handover on the phone, but this does not work for phones prior
to W760i and C702.
 Sony Ericsson K600/W600: If CKPD is going to be used to execute
video calls, it is necessary to disable the keylock first.
 When sending SMS messages from Sony Ericsson phones such as
Z750 and W760, the number of characters is severely limited (worst
case: max 23 characters).
 The phone must have been activated at least once in TEMS
Investigation for the message tree to be fully populated in the device
properties, Layer 3 Messages item (from where you can discard
messages of selected types).

7.3.4 Qualcomm Chipset Based Phones and PC Cards
 Some Qualcomm chipset based commercial UEs may not have test
reporting activated. The device may then be impossible to activate in
TEMS Investigation, or seem to be locked to GSM, and/or only deliver
low-level reports. Please contact the UE vendor; Ascom is not
authorized to change this behavior.
 Certain Qualcomm chipset based LTE devices that require the use of a
connection manager do not start reporting LL1 and Layer 3 signaling
until an explicit PS Attach has been performed. A workaround is as
follows:

NT11-21089 13(21)

1) Activate the device in TEMS Investigation.
2) Execute the Service Control activities PS Detach and PS Attach.
3) Connect the device using the connection manager.
4) In TEMS Investigation, execute the Network Connect activity. The
device is now ready for data service testing.
 Care needs to be taken when using the NV interface to write to a
Qualcomm chipset based device, since an inappropriate NV write may
damage the device.
 The hardware information and the number of devices used are
sometimes missing in the logfile information (accessed by clicking the
Information [“i”] button on the Replay toolbar).
 AT commands in Service Control scripts are not always executed by
Qualcomm chipset based devices.
 When an Ericsson Fixed Wireless Terminal is activated, it is not
possible to do data service testing with any other devices at the same
time.
 To enable detection of the Ericsson Fixed Wireless Terminals,
uncomment the line containing "QualcommNetworkDetector" in the file
<TEMS Investigation install dir>ApplicationConfiguration
Investigation.Equipment.config. If TEMS Investigation is running, you
must restart the application for the change to take effect.
 If a Qualcomm chipset based device is not detected by TEMS
Investigation, although it is built on a supported chipset, you can run the
Manual UE Configuration utility to help TEMS Investigation recognize
the device. See the User’s Manual, section 7.3.4 for details on how to
operate this utility.
 The PS Detach and PS Attach commands do not work with Bandluxe
devices.
 No Layer 3 messages are obtained from Bandluxe devices in LTE
mode.
 HTC Touch Pro2 phones with TCP router need special configuration to
be usable with TEMS Investigation. See the User’s Manual,
section 7.3.3.4.
 LG LTE modems sometimes take a long time (more than 30 seconds)
to perform inter-RAT cell reselection between 3G (UMTS or EV-DO)
and 4G (LTE). This has been observed for both 4G > 3G and 3G > 4G.
 For Samsung Metro GT-S5350, video call dialing is not supported;
however, answering a video call is possible. SMS Send works, but may
generate error messages.
 Samsung Omnia II does not answer incoming voice or video calls.
 FTP does not work with Samsung Omnia SCH-i910.
 Service testing with Samsung SPH-M320 does not work.

NT11-21089 14(21)

 IP sniffing does not work with Sierra Wireless devices such as USB
306/307. The best course of action is to set ignoreIPSniffError="true" in
the file <TEMS Investigation install dir>Application
Investigation.exe.config; see section 7.1.2.
 Sierra Wireless AC319U: Repeated network connects/disconnects must
be avoided for this device. The Network Connect activity must therefore
not be placed inside a loop in a Service Control script; rather, it should
be performed only once at the beginning.
 Sierra Wireless AC503 stops sending RF logs after 10–20 minutes of
dual data session testing. To restore RF data delivery you need to
disconnect and reconnect the device.

Notes on Huawei C8600 supporting AQM with TerraTec ACU
 For the Huawei C8600 to be able to perform data calls governed by
TEMS Investigation, the Data Service option in the NetManager
application must be turned off. To accomplish this, turn off the “up-
arrow/down-arrow” button on the phone’s top-level menu. Alternatively,
go to Applications > NetManager and deselect the “Data Service”
option. Note that by default, the Data Service option is turned on.
 This instruction applies to prototype Huawei C8600 devices sharing the
same IMEI. If you connect two such devices to the PC, and the detect in
TEMS Investigation fails, do as follows:
1) Inspect the phone IMEI in TEMS Investigation (Navigator, bottom
pane, Information tab, “Identity”).
2) In the configuration file <TEMS Investigation install dir>
ApplicationConfigurationInvestigation.RecurringImei.config, replace
the default IMEI with the phone IMEI. Save the file.

7.3.5 Samsung Devices Based on Samsung Chipset
 The event IP Interruption Time cannot be generated for Samsung
chipset based devices.

7.3.6 Samsung Devices Based on Samsung and Qualcomm
Chipsets
 For Samsung Android based LTE devices using a Samsung chipset for
LTE and a Qualcomm chipset for CDMA (such as SCH-R920, SCH-
i510), each chipset is seen by Windows as a separate device.
Depending on which RAT mode the device is in, it will expose either its
LTE ports or its CDMA ports in the Windows Device Manager, but never
both sets of ports at the same time.

7.3.7 Sequans Devices Based on Sequans Chipset
 The Sequans daemon service occasionally stops during data transfer,
so that no further RF signaling is obtained from the Sequans device.

NT11-21089 15(21)

7.3.8 Nokia NTM3 Phones
 When the Nokia phone switches from GSM to WCDMA, GSM values
remain in TEMS Investigation presentation windows. These are old
values and linger because Nokia NTM3 phones stop reporting on GSM
after the switch.
 If you encounter problems activating a Nokia NTM3 phone in TEMS
Investigation, there is a need for a power reboot of the phone.
 When locking the Nokia phone on a band, this action should be
preceded by disabling the band lock. If you click OK between selections
of different bands, the phone will lock on all bands that you have
selected at some point.
 When WCDMA band lock is enabled, any attempt to access a cell on
any other WCDMA band will result in that cell being barred for
approximately 20 minutes. Therefore you cannot immediately go back
to the band you were on before applying the band lock (or to a cell on
that band). Furthermore, if the phone is locked on a WCDMA band and
you lock on a different band, then release that lock, you will get no
substantial phone logs for 20 minutes. For the above reasons, if you do
not want to wait through the 20-minute period, it is recommended that
you restart the phone before locking on a different WCDMA band or
releasing the band lock.
 To run the SMS Send script activity on a Nokia 6720, you must set the
parameter Request Delivery Report to False. If the default setting True
is retained, sending of SMS messages will not work.
 High data throughput may cause the Nokia C7-00 phone to reboot (see
Nokia release notes). Also, the video call capability of the Nokia C7-00
is not supported in TEMS Investigation.

7.4 AQM Module Related
 If the USB connection is broken during AQM measurement, the PC
application may need to be restarted to enable reactivation of phones.
 When running AQM measurements, it is recommended to use the Start
Recording and Stop Recording activities in the script to ensure that
each logfile contains a full call sequence. Automatic swapping of logfiles
is not recommended, as this can cause the merge mechanism to fail.
 PESQ calls may fail with error message “3 AQM Module errors”. This
message is shown when the PC application has tried to contact the
AQM module three times and failed on all occasions. This can be
caused for example by the module being physically disconnected from
the USB port or by the module not responding. The proper procedure
when this happens is either to reset the AQM module using the reset
button located on the back of the module, or to restart the module by
power-cycling it. The AQM module then needs to be paired once again
with its phone. This is done from the Navigator’s Equipment tab (bottom

NT11-21089 16(21)

pane, Activities “subtab”) by right-clicking the PESQ Device Pairing item
and choosing the correct AQM module in the setup dialog.
Failures of this kind are also recorded in the logfile in the form of error
messages indicating that the connection to the AQM module has been
lost. If such failures occur frequently, this indicates a bad USB
connection or power cable.

7.5 Scanner Related

7.5.1 General
 Starting several scans in rapid succession (e.g. pilot scan and RSSI
scan) may cause TEMS Investigation to stop updating scan data, and
possibly even hang the application. The workaround is to wait until one
scan starts returning data before starting another.
 LTE scanning:
1) For RSSI scans, the bandwidth must always be set to 100 kHz.
2) For all LTE scanning methods, the set of channel numbers available
for scanning is dependent on the bandwidth selected, and some
bandwidths may not be at all applicable to the band in question.
Example (EUTRA Band 7):
RSSI scan:
 100 kHz bandwidth; available channels 2750–3449
Signal scan:
 1.4 MHz bandwidth: N/A
 3 MHz bandwidth: N/A
 5 MHz bandwidth: available channels 2772–3428

7.5.2 SRU
 Always install new drivers from the TEMS Investigation driver
installation CD and not from the internal SSD drive, which may hold
older drivers.
 It is crucial to supply the SRUs with adequate power. It may be
necessary to use the accompanying 12 V adapter.
To prevent problems detecting the SRUs in TEMS Investigation, stop
the Mobile Broadband Service and preferably set startup type to
"disable".

NT11-21089 17(21)

7.5.3 Anritsu ML8780A
 Scanning with the Anritsu ML8780A is only guaranteed to work under
32-bit Windows (tested on Windows 7, English-language version).
 Only one measurement unit in the Anritsu ML8780A scanner is
supported.
 Testing has only been done with a single Anritsu ML8780A scanner
connected to the PC.
 The scanner firmware Ascom has had access to and has used for
testing is version 1 (ML8780A 01.01). TEMS Investigation will probably
be compatible with later scanner firmware versions, but no guarantees
can be given in this regard.

7.5.4 DRT 4301/4301A/4301A+
 The DRT scanner will reboot after a period of time if it is connected via
a LAN and is detected by multiple TEMS Investigation users. The
scanner API does not support multiple connections.
 Swap logfile cannot be used while scanning with a DRT scanner, since
each logfile must contain a scan start.
 Restrictions on compatibility:
 Firmware versions 02.02.xx and earlier are not compatible with
TEMS Investigation 12.1.x and later.
 Firmware versions 02.03.xx and later are not compatible with TEMS
Investigation 12.0.x and earlier.

7.5.5 PCTel SeeGull LX/EX
 Start up the scanner without the USB cable connected. Wait until the
LED turns green before plugging the USB cable into the scanner.
 If you need to power cycle the scanner during use, pull the USB cable
before doing so, and do not reconnect it until the scanner has started up
again (green LED).
 If you do not deactivate the scanner properly in TEMS Investigation,
problems may arise when you try to activate it again. For example, if
you remove the cable from the serial port without first deactivating the
scanner in the application, measurements will continue to run in the
scanner, and when it is connected to the port again the activation might
fail. To solve the problem, turn the scanner off and on and the activation
function will work again.
 When plugging in a PCTel SeeGull LX scanner that uses a serial
connection, click the Refresh button on the Navigator’s Equipment tab
to ensure that the scanner is detected.

NT11-21089 18(21)

 With some PCTel scanners only 2560 measurement points can be
allocated for spectrum scanning, even though the scanner in fact has
more measurement points available.
 The PCTel scanners may sometimes report many scan drop messages.
The scanner uses this message to tell the host how many scan data
messages were dropped and not delivered through the data link. Scan
data is dropped automatically when the scanner is scanning faster than
the data can be delivered through the data link, causing the pipeline to
overfill.
 For EV-DO scanners, the “Use Pilot Increment” option is not available.
 When setting up a follow phone scan in CDMA, all fields in the setup
dialog must have some value set, otherwise you cannot click OK. Enter
dummy values in the dialog as needed.
 For the PCTel SeeGull EX scanner, version 2.0.1.0 and later, be sure to
install the driver delivered with TEMS Investigation. Do not install any
driver provided on PCTel’s web site. The reason is as follows: If you
have PCTel’s own driver installed, then if the scanner is activated in
TEMS Investigation and you pull its cable, the scanner port will not
disappear from Windows and thus not from the TEMS Investigation user
interface either. The driver delivered with TEMS Investigation contains a
modification that removes the scanner port in the situation just
described.
 When a PCTel LX MM2 scanner is connected to TEMS Investigation
you cannot use the Activate All function; rather, you must activate each
device separately.

7.5.6 PCTel SeeGull MX
Detection of PCTel SeeGull MX scanner:
 After the driver has installed and Windows has detected the device for
the first time, the scanner should be rebooted.
 Always wait for the scanner to boot completely (LED turns dark green)
before starting TEMS Investigation. This can take up to 90 seconds
(during which time the LED is pale green or orange).

7.5.7 PCTel SeeGull PCT
 PCTel SeeGull PCT scanner may not be detected on some PCs. If this
problem occurs, disable the “Intel Active Management Technology –
SOL” driver if it exists on the PC, then restart TEMS Investigation.

7.6 GPS Related
 To activate the Nokia LD-3W Bluetooth GPS device, first start up TEMS
Investigation. Then connect the GPS logically in Windows, outside of
the TEMS Investigation application. Only after this can the GPS be
successfully activated on the Navigator’s Equipment tab.

NT11-21089 19(21)

 If the power is lost on a Bluetooth GPS device, you may need to restart
TEMS Investigation to be able to activate the device in the application.
 If a Bluetooth GPS cannot be found, try to restart the GPS. Wait for the
application and computer to establish the pairing. A “Refresh
equipment” operation may be needed in the Navigator if the device still
does not appear.

7.7 Call Generator Related
 The Call Generator installation requires an English-language edition of
Windows.
 For the Call Generator Windows Server 2003 to function correctly,
make sure you have Powershell installed. With Administrator privileges
on the PC, choose Start > Run > Powershell. If the tool is not installed,
download and install Windows Management Framework Core package
(Windows PowerShell 2.0 and WinRM 2.0) from Microsoft (download
link: support.microsoft.com/kb/968930).

7.8 TEMS UDP Server Related
 If the following error message appears when the server is starting up:
“Error 1053: The service did not respond to the start or control request
in a timely fashion”, do one of the following (the two procedures have
the same effect):
1) Remove the internet cable. Start the service. Plug in the internet
cable.
2) Open a command prompt and type ipconfig/release. Start the
service. At the command prompt, type: ipconfig/renew.

8 Contact Information
For customer support contact information, please visit our website on the
Internet: www.ascom.com/networktesting

9 Appendices
9.1 Open Source Licensing Information
The USB driver (libusb0) used for the AQM module is part of the open
source libusb Windows project. This project can be found on the Internet at
http://libusb-win32.sourceforge.net. The libusb-win32 project retains all
rights and copyrights to the libusb-win32 code. The library (DLL) is
distributed under the terms of the GNU Lesser General Public License
(LGPL) and the driver is distributed under the terms of the GNU General
Public License (GPL). The LGPL and GPL license text can be found on

NT11-21089 20(21)

TEMS Investigation driver installation CD. The source code for libusb-win32
is freely available and can be found on the TEMS Investigation driver
installation CD.

9.2 AQM with TerraTec ACU: Certification and
Standard Compliance
All system components used in the TEMS Investigation AQM configuration
with TerraTec ACU are declared to be CE compliant by the corresponding
manufacturers. Additionally, Ascom Network Testing tested the entire
abovementioned AQM configuration to ensure that no additional emission
resulted from interconnecting the individual components. The TEMS
Investigation AQM configuration was found to comply with the
EN55022:2006 A1:2007 standard for a Class B device. Tests were
performed by a certified laboratory, and the test reports are available upon
request.

NT11-21089 21(21)

Tems investigation 13.1 release note

More Related Content

What's hot

Viewers also liked

Similar to Tems investigation 13.1 release note

Recently uploaded

Tems investigation 13.1 release note