TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.
2 Important Information
2.1 Rohde & Schwarz TSMW Firmware Upgrade
All customers using Rohde & Schwarz TSMW scanners must upgrade to firmware version 1.13. This is to match ViCom software interface version 14.75, which is what is supplied with TEMS Investigation 15.0.
Please refer to www.rohde-schwarz.com/en/firmware/tsmw for R&S firmware download and release notes describing how to upgrade the firmware.
3 New Features
3.1 New Features in TEMS Investigation 15.0
3.1.1 Available Bandwidth Measurements: Blixt™
Ascom has devised a method of available bandwidth measurement (ABM) in state-of-the-art wireless networks such as LTE. The patent-pending ABM algorithm, trademarked as “Blixt”, helps operators track the bandwidth being offered to their subscribers with great precision and millisecond resolution. It has also been carefully designed for minimum intrusiveness, that is to say, to have the smallest possible impact on the quality-of-experience of paying network users.
What creates the need for a novel ABM algorithm is the rapid evolution of recent mobile telecom technologies such as LTE and HSPA, with their vastly higher data rates and complex configuration options. For these technologies, traditional ABM methods are no longer adequate; what is required are metrics and measurement techniques designed specifically for the wireless environment.
Ascom’s Blixt technology for ABM is characterized by:
High peak load – low average load. Test data is sent in short, intense bursts (“chirps”) with much longer pauses in between. The peak load is high enough to hit the network’s theoretical maximum, while the average load is kept low. This scheme allows sounding out the available bandwidth while still making minimum use of network resources.
Fast adaptation in time domain. The data bursts that probe the network are short enough to track changes in radio conditions on a millisecond time scale. In this way a high-resolution profile of the available bandwidth is obtained.
Adaptation to network configuration. The amount of data sent is adjusted according to the network’s maximum throughput (for example, when the UE moves between LTE and HSPA networks), while keeping the level of intrusiveness to a minimum at all times.
Server-based design. The device that is performing ABM communicates with a server which reflects the packets back to the device, including timestamps and other data in the packets. That means it is easy to test different parts of the network by having the device access different servers. Please contact TEMS support to obtain ABM server IP addresses. A timestamping protocol called TWAMP is used.
3.1.2 New Supplied Device: Sony Xperia V LT25i
This is an Android smartphone operating on LTE, WCDMA, and GSM networks. Equipped with TEMS software, it offers extensive control functionality for all of these technologies, including LTE RAT lock and LTE band lock.
The casing of the Xperia V LT25i is water-resistant, making the phone less susceptible to moisture damage in wet or damp environments.
Huawei E3276 (LTE Category 4 device, downlink throughput up to 150 Mbit/s)
Samsung Galaxy S III SPH-L710
Samsung Mpower TV SCH-S239
Cellient MX200
ZTE AC2738
3.1.5 Video Streaming over HTTP
TEMS Investigation has long supported streaming over RTP, both live and on-demand. The 15.0 release adds HTTP streaming to the repertoire, enabling testing of (for example) video upload websites. Behind the scenes, HTTP streaming relies on Internet Explorer 9 and Flash.
Besides a host of other information elements diagnostic of streaming session performance, the viewer-perceived streaming quality is evaluated using the VQmon algorithm. Developed by Telchemy, VQmon bases its scoring on a parametric model taking IP sniffing data (among other things) as input. The algorithm is content-sensitive, which means that it allows properties of the streamed video to influence the quality scores, preventing inexpertly shot or edited footage from unduly biasing the
NT13-20774, 1.0, 5/21/2013 4
scores. For example, VQmon detects blank or frozen images as well as suspiciously blurry footage that might result from the camera not being properly controlled.
3.1.6 RouteFinder
RouteFinder is a stand-alone utility for searching logfiles in TRP format recorded with TEMS products. Logfiles can be searched according to a wide variety of criteria, including:
Originating TEMS products and data-collecting devices
Date of recording
Location where the recording was made
Services tested or measurements performed in the logfile
Events and messages occurring in the logfile
Information elements having valid values in the logfile.
So this means you can now very easily and speedily retrieve from your storehouse of logfiles such things as: all logfiles recorded with your recently acquired Samsung S III device; all logfiles from the downtown leg of last Thursday’s drive test; all logfiles where audio quality was measured; or all logfiles containing dropped calls in that rural area with known coverage issues.
No matter what logfile data you want to lay your hands on, RouteFinder lets you sift the gold from the grit, potentially saving you massive amounts of time otherwise spent trawling manually through your collected data.
3.1.7 RouteUtility
This is another logfile-related utility introduced with TEMS Investigation 15.0. It enables you to split a TEMS product TRP logfile into several self-contained logfiles according to various criteria:
Data-collecting devices used
Date and time
Location
The benefit brought by RouteUtility is that it permits a more relaxed approach to logfile recording: if you wish you can simply turn recording on at the start of your drive test, then divide your data into more manageable chunks later.
3.1.8 Voice Call Sequence: MT Voice Call Support
Testing voice by trading calls back and forth between a mobile device and a fixed-side Call Generator is a long-standing feature of TEMS Automatic and TEMS Symphony. Such call sequences can now be set up in TEMS Investigation as well. A new scripting construct (“Synchronized Call Sequence”) is provided in the Service Control Designer, looping mobile-terminated and mobile-originated voice calls in alternating fashion and measuring voice quality with POLQA or PESQ.
NT13-20774, 1.0, 5/21/2013 5
3.1.9 IMAP Email Retrieval Testing
In the Email Receive script activity, IMAP has been added as an option alongside POP3. The IMAP (Internet Message Access) protocol for email retrieval is a refinement of POP3, which it is gradually supplanting.
3.1.10 HTTP Post
The HTTP Post script activity offers an alternative route to testing uplink performance, with a Web server at the other end instead of an FTP server.
3.1.11 LTE Tx Antenna Diagnostics
A new information element indicates the difference in transmit power between the Tx antennas of an eNodeB. These measurements can be used to determine in real time if a newly deployed site has a problem with one of the Tx antennas. Compared to traditional methods of diagnosis, this feature can reduce turnaround time by several days.
3.1.12 IPv6 Support
TEMS Investigation 15.0 fully supports the IPv6 address space, which is now being increasingly deployed in practical use by Internet providers. This secures uninterrupted data service testing as traffic flows between the IPv6 and IPv4 domains.
3.1.13 Usability Improvements
Apart from the RouteFinder and RouteUtility tools, TEMS Investigation 15.0 boasts these usability-enhancing features:
Simplified voice dial. Scripting of voice calls, both CS and VoIP, has been streamlined and simplified in the user interface. A single set of dial, answer, and hang up commands now controls any voice call, regardless of bearer.
GPX-format planned routes. TEMS Investigation 15.0 is capable of loading planned routes for drive testing created in the XML-based GPX (GPS Exchange) format. The point of doing that is to have the routes displayed in a Map window as a driving aid, so that you do not have to rely on your GPS to follow the correct route. One tool that can be used to create GPX files is Garmin’s freeware application Basecamp; another is Google Maps.
4 Corrected Bugs
4.1 Bugs Corrected in TEMS Investigation 15.0
WCDMA information element E-DCH TTI wrongly described in documentation as not supported by Sony Ericsson W995 and similar phone models.
Logfile recording failed during execution of scripted SMS Send activity.
Inadequate instructions in documentation on how to enter LTE cell identities in XML cell file. – Description of LOCALCELLID revised.
NT13-20774, 1.0, 5/21/2013 6
GSM/WCDMA scanning with PCTel MX failed in TEMS Investigation 14.6.2.
In logfiles exported in MapInfo TAB format, route segments with no GPS coverage (tunnels) were assigned incorrect positions. – The problem was that the GPS internally reports positions (lat, long) = (0, 0) while lacking coverage and indicates these positions as valid. TEMS Investigation now disregards such positions.
LTE: PMI (Precoding Matrix Indicator) from Qualcomm devices always presented as zero.
Spurious call blocks indicated by TEMS Investigation 14.6.2, associated with timeouts in call setup procedure.
Spurious call drops indicated by TEMS Investigation 14.6.2, associated with timeouts in call re-establishment procedure.
No Dropped Call events generated in TEMS Investigation 14.6.2 for drops in GSM where the UE released the radio connection due to poor downlink quality.
LTE logfiles failed to open in TEMS Investigation 14.6.2.
Huawei E392 USB modem was not detected by TEMS Investigation. – UEDescription.xml modified to cover the firmware version used by the device (PID="151B").
5 Removed Features
5.1 Features Removed in TEMS Investigation 15.0
Windows XP support withdrawn
NT13-20774, 1.0, 5/21/2013 7
6 Known Bugs and Limitations
6.1 PC Application Related
6.1.1 Installation and Start-up
The PC must have a working Internet connection when executing the TEMS Investigation EXE file, since various software components will be retrieved over the Internet. This includes .NET 4.5 in case the PC does not already have it installed.
When installing TEMS Investigation for the first time, it may take 10–20 minutes for the installation to complete if .NET Framework 4.5 was not already present on the PC. On some PCs, a reboot may take place after the .NET Framework installation.
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.)
UAC must be set to the lowest level (i.e. turned off) for the TEMS Investigation automatic software update to work. If an error dialog stating “The requested operation requires elevation” appears upon start-up of TEMS Investigation, that indicates there is a problem with the UAC level. A workaround is to start TEMS Investigation using the “Run as administrator” option.
NT13-20774, 1.0, 5/21/2013 8
6.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 9.
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 hub (USB 2.0 or later) 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:\path\tmp, where the path is defined by the environment variable TMP). 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 abnormally, this might not happen. The files must then be removed manually.
When using the pinpointing function in the Map window, 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 toolbar buttons) while pinpointing in the Map window. (However, as soon as you pinpoint close to the edge of the 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,
NT13-20774, 1.0, 5/21/2013 9
and it may be necessary to start recording of a new logfile once every hour or at even shorter intervals to prevent RAM usage from becoming excessive.
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.
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.
Service Control Designer: The Wait For example in the User’s Manual, section 13.10.6.2 does not work, since a Wait For activity cannot be triggered by another activity that is inside a (different) while loop.
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 should preferably be locked on WCDMA.
SMS and MMS testing with Service Control scripts does not work for devices that do not support AT commands.
Streaming over HTTP requires admin rights on the PC, since it needs a successful IP trace to be able to execute.
At high throughput rates, the application layer throughput as presented in TEMS Investigation is more spiky and unstable than the throughput in lower protocol layers. Most probably, this phenomenon is caused by the buffering in the third-party FTP client used by TEMS Investigation. By contrast, CPU load or buffering capacity are unlikely causes of the application throughput fluctuations.
UDP upload testing tends to cause very high CPU load, especially when multiple users are running UDP concurrently.
During CS voice testing, PESQ is not computed for the AMR-WB speech codec. (This limitation does not apply to VoIP.)
When doing on-device testing with ODM Call Control, a Wait of at least 3 seconds needs to be inserted after each dial/answer/hangup activity to enable slower phones to execute.
Only one Synchronized Voice Call Sequence snippet can be in use at a time.
At the end of a Synchronized Voice Call Sequence, be sure not to abort the Sequence Cancel call (which is not visible in the Service Control Designer). If you do abort it, the device will keep receiving calls from the Call Generator.
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 14.13.
NT13-20774, 1.0, 5/21/2013 10
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.
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.
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 “LTE Total RS Power” is valid only for the bandwidths 5 MHz and 10 MHz.
The information element “Frequent AQM Score Downlink” is not populated when loading a logfile where uplink PESQ data has been merged in.
6.1.3 Windows 7 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.
6.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.
NT13-20774, 1.0, 5/21/2013 11
6.2 Device Related: General
6.2.1 Network Connect
Some LTE devices must be connected to the network manually using their connection managers, or by means of tethering, rather than automatically in the Service Control script. See the User’s Manual, section 13.16.3.2.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.
6.2.2 TCP Settings
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”.
6.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 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
NT13-20774, 1.0, 5/21/2013 12
6.3 User Terminal Related
6.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.
When the device is used for highly demanding tests of extended duration (for example, LTE data transfer), it may happen that the charging cannot keep up with the power consumption, so that the battery eventually will be drained even if continuously recharged (by whatever method).
6.3.2 Sony Ericsson Android Phones (Qualcomm Chipset Based)
6.3.2.1 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: ...\Drivers\Sony Ericsson\x10\Win64.
Click Next.
Repeat the procedure for the remaining “SEMC HSUSB Device” items.
6.3.2.2 Other
Xperia T LT30a: Streaming and SMS send/receive are not supported.
Xperia T LT30a: If a CS call is ongoing and you stop the script before it reaches the Hang Up activity, then the call will not be hung up.
Xperia arc S, arc, X10: 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.
Xperia arc, 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,
NT13-20774, 1.0, 5/21/2013 13
the Network Connect activity in the TEMS Investigation script, which tries to set the APN, will fail.)
When using an Xperia arc S for multi-RAB testing with CS voice and a data service in parallel, it is necessary to establish the voice call before initiating the data session and to conclude the data session before hanging up the voice call. In other words, the Service Control script needs to be structured as follows: Dial > Network Connect > [data service activities] > Network Disconnect > Hang Up.
To run the SMS Send script activity on an Xperia arc S, you must set the parameter Request Delivery Report to False. If the default setting True is retained, sending of SMS messages will not work.
6.3.3 Sony Ericsson R13 Phones (W995, etc.)
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 11.7.
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.
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
NT13-20774, 1.0, 5/21/2013 14
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).
6.3.4 Qualcomm Chipset Based Phones and PC Cards
(Notes specific to Sony/Sony Ericsson Xperia models are found in section 6.3.2)
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:
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.
LTE data service testing at high throughput rates (above 50 Mbit/s) with a Qualcomm chipset based device requires a very powerful processor, for example a 2nd generation Intel Core i5 or comparable Intel Core i7. Please note that this limitation is not TEMS Investigation related.
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>\Application\Configuration\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.
NT13-20774, 1.0, 5/21/2013 15
For some Qualcomm chipset based devices that support band lock, the following problem can be seen: If you exit TEMS Investigation after applying a band lock, and you do not reboot the device before next time you start TEMS Investigation, then the band lock dialog will show the band(s) you locked on as the device’s band capabilities.
For Anydata ADU-895, the connection manager must be started once after each device insertion to have device ports installed in Windows. After this, the connection manager can be terminated.
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 transitions.
On the Samsung Galaxy S III GT-I9305, if a CS or VoLTE call is ongoing and you stop the script before it reaches the Hang Up activity, then the call will not be hung up.
Samsung Galaxy S III GT-I9305 does not support SMS send/receive, MMS send/receive, or streaming over RTP (but it does support HTTP streaming).
Samsung Galaxy S III SPH-L710 reboots itself after the RAT lock setting has been changed.
Samsung Metro GT-S5350 does not support video call dialing; however, it does have the capability to answer a video call. 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.
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:
NT13-20774, 1.0, 5/21/2013 16
1) Inspect the phone IMEI in TEMS Investigation (Navigator, bottom pane, Information tab, “Identity”).
2) In the configuration file <TEMS Investigation install dir>\Application\ Configuration\Investigation.RecurringImei.config, replace the default IMEI with the phone IMEI. Save the file.
6.3.5 Samsung Devices Based on Samsung Chipset
The event IP Interruption Time cannot be generated for Samsung chipset based devices.
6.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.
6.3.7 Samsung Devices Based on Samsung and Via Chipsets
On the Samsung Stratosphere SCH-I405, if a VoLTE call is ongoing and you stop the script before it reaches the Hang Up activity, then the call will not be hung up.
6.3.8 Samsung Devices Based on ST-Ericsson Chipset
To run the SMS Send script activity on a Samsung Galaxy S 4G, you must set the parameter Request Delivery Report to False. If the default setting True is retained, sending of SMS messages will not work.
6.3.9 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.
6.3.10 Altair Chipset Based Devices
After installing the drivers (not supplied with TEMS Investigation), you need to correct an error in the file C:\Program Files\Altair Semiconductor\ALT3100\Tools\ Internals\LogCreator\RunLogCreator.bat. On the line starting with LogCreator.exe -SA -FN:"50", remove the line break before -TCP. The command should read:
For Via chipset based devices to be detected by TEMS Investigation, the following must be installed on the PC: Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update (for x86). Go to the page
NT13-20774, 1.0, 5/21/2013 17
www.microsoft.com/en-us/download/details.aspx?id=26368 and download the file vcredist_x86.exe. Knowledge Base reference: KB2538243.
6.3.12 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).
The video call capability of the Nokia C7-00 is not supported in TEMS Investigation.
6.4 ACU R2 Related
Any GSM phones need to be kept at a minimum distance of 15 cm from the ACU R2 box, otherwise they will interfere with measurements.
For the answering party, a 3 s Wait before the Voice Quality activity is recommended in order to prevent any possible problems with the calculation of the first AQM score. This Wait duration is suitable for two phones of identical make and model; if two different phones are used, the duration may need to be modified.
6.5 ACU TerraTec Related
This section relates to the TerraTec box Audio Capturing Unit.
USB 3.0 should not be used in conjunction with the ACU, since it introduces noise into the recordings and degrades AQM scores.
6.6 AQM Module Related
This section relates to AQM modules used in combination with a Call Generator or MRU.
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.
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 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.
6.7 Scanner Related
6.7.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. See also the User’s Manual, section 13.10.4.3.
Scripting of scanning tasks is supported for PCTel, Sony Ericsson, and Transcom devices.
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
10 MHz bandwidth: available channels 2795–3405
15 MHz bandwidth: available channels 2817–3383
20 MHz bandwidth: available channels 2840–3360
NT13-20774, 1.0, 5/21/2013 19
6.7.2 Sony Ericsson R13 Phones (W995, etc.)
When composing a script for RSSI scanning with a Sony Ericsson R13 phone, it is necessary to add a Wait (30 seconds) after the Stop RSSI Scan activity if the device is to proceed with some other activity. The reason is that the device must be given sufficient time to reset.
6.7.3 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 SRU with adequate power. Plug the Y-USB cable into an externally powered USB hub, and also connect the SRU’s power cable with its accompanying 12 V adapter to a power source. Connecting the Y-USB cable directly to USB ports on the PC does not give sufficient power.
To prevent problems detecting the SRU in TEMS Investigation, stop the Mobile Broadband Service and preferably set startup type to “disable”.
When installing an SRU whose firmware has been upgraded, or when installing an SRU on a PC where a TEMS Device Manager already exists, the TEMS Device Manager needs to be upgraded. Please follow the readme document supplied on the driver CD in the folder TEMS SRU.
6.7.4 Anritsu ML8780A
Scanning with the Anritsu ML8780A has only been tested on Windows 7 (English-language version).
Only one measurement unit in the Anritsu ML8780A scanner is supported.
6.7.5 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.
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.
6.7.6 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. Note especially that the EX LTE scanner may take 10–15 seconds to boot up and become fully operational. If you insert the USB cable too soon, it may happen that the scanner is detected OK by TEMS Investigation and appears responsive but does not respond to scan commands.
NT13-20774, 1.0, 5/21/2013 20
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.
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.
For Enhanced signal scan (RF Path and Subband options) in TD-LTE, the measurement bandwidths 15 MHz and 20 MHz are not supported.
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.
6.7.7 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).
NT13-20774, 1.0, 5/21/2013 21
6.7.8 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.
6.7.9 Rohde & Schwarz TSMW
Rohde & Schwarz TSMW scanners must have firmware version 1.13 installed.
6.7.10 Transcom
The Transcom scanner is not capable of scanning more than one LTE band at a time.
Transcom’s “Eagle” PC software cannot run concurrently with TEMS Investigation.
6.8 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.
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.
6.9 Call Generator Related
The Call Generator installation requires an English-language edition of Windows.
If the Call Generator PC is not running Windows Server 2008 R2, make sure that you have Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0) installed. To check what version you have, run a command prompt as administrator and type $host.version. This command should return “Major” = 2. If it does not, download the correct software version via Windows Update or by following this link: support.microsoft.com/kb/968929. – In PowerShell, also check that Get-ExecutionPolicy returns “RemoteSigned”. If you get a different response, run the command Set-ExecutionPolicy RemoteSigned.
6.10 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.
Please visit our website at www.ascom.com/networktesting.
For customer support contact information, see the page www.ascom.com/en/index/support/support-tems.htm.
8 Appendices
8.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 sourceforge.net/apps/trac/libusb-win32/wiki. 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 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.
8.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.
