Anda di halaman 1dari 25

TEMS Investigation 14.

4 Release Note
1 About This Release

Ascom (2012). All rights reserved.

TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.


New Features
New Features in TEMS Investigation 14.4
Automatic Neighbor Relation (ANR) Diagnostics

ANR, Automatic Neighbor Relation detection, is an automated mechanism for adding neighbor cell relations that are missing in the network with a view to achieving better handover performance and a lower session drop rate. The actual measurements involved in scouting for new neighbor candidates are delegated to the UEs, which report their findings to the fixed side. On the basis of this data, neighbor lists are then supplemented as appropriate. TEMS Investigation 14.4 comes with an ANR status window holding a set of new information elements that are diagnostic of ANR usage in a network. From this data you learn: Whether ANR is enabled in the network. This is useful in benchmarking contexts. Whether a given device is capable of performing ANR measurements. If ANR activity is taking place: What cells the device is instructed to measure on and where these cells are located (intra-frequency, inter-frequency, inter-RAT). What cells the device actually reports.


Emergency Call Success/Failure Events

Success and failure events have been implemented for emergency calls. For an emergency call to be deemed successful, it must stay connected long enough that it is certain a position fix has been obtained. The duration threshold is set at 35 seconds.


New Connectable User Terminals

The range of supported Samsung Galaxy S III models is further expanded with the Samsung Galaxy S III SGH-T999, which is a UMTS (42 Mbit/s HSPA+) device.

NT12-13416, 1.0, 11/6/2012


New Features in TEMS Investigation 14.3

On-device Measurement: Voice over LTE

TEMS Investigation 14.3 introduced a completely new methodology for service testing: on-device measurement (ODM). What defines on-device measurement is precisely what the term says: The software (service) performing the measurement resides on a connected device rather than being part of the TEMS Investigation PC software. The 14.3 release offered voice over LTE (VoLTE) as a first instance of on-device service testing, with more services to follow in later releases. What benefits can be reaped with an on-device test setup? Well, here are a few: On-device testing infuses the old slogan Test like a user with fresh meaning. Narrowing the discussion to VoLTE for the moment, we can state that a terminalbased VoLTE client will cope better in the LTE network. When running VoLTE over a PC client, the voice call will not be prioritized in the network as would be appropriate for a real-time service, but dealt with on a best effort basis only. A device-based VoLTE client, on the other hand, is sure to be assigned a VoLTE logical channel with high priority (QoS class). What this means is that the service performance will not suffer from any limitations inherent in the test setup, and it will therefore reflect real-world subscriber experience in a way that cannot be fully achieved with a PC-based VoLTE client. A client embedded in device firmware will have been adapted to and optimized for that particular device. This too gives a performance edge over PC-based clients (independent of channel assignment/traffic prioritization as described in the preceding bullet), even a PC-based client from the same vendor. For certain measurement tasks, an on-device client implementation is desirable or even indispensable in order to obtain sufficient accuracy: communicating with a PC client would cause excessive delay. Yet another advantage of on-device service testing is that it offloads the PC by distributing the processing across multiple devices.

The data obtained from on-device VoLTE testing is similar to that obtained with a PCbased VoIP client. This includes: SIP and RTP signaling; jitter and jitter buffer information; MTSI KPIs (success rates, session timers); and end-to-end POLQA or PESQ speech quality scores. In TEMS Investigation 14.3, on-device measurement was implemented on the Samsung R820 phone, with others to follow in upcoming releases.


CDMA Code Domain Scanning

CDMA systems make use of Walsh codes to keep individual user transmissions apart (orthogonal). A base station in CDMA must be able to accurately control the power in individual Walsh codes, both in order to achieve proper handling of multiple user links with varying RF losses and in order to ensure interference-free transmissions. To allow users to inspect the distribution of channel power across the range of Walsh codes, TEMS Investigation 14.3 introduced a new CDMA scan method called code domain scanning. The entire Walsh code range, or a subset thereof, can be swept for up to 12 different PN offsets. Separate information elements crucially: Walsh code
NT12-13416, 1.0, 11/6/2012

numbers and their Ec and Ec/I0 readings and presentation charts are provided for each selected PN. Code domain scanning is supported on IS-95 and IS-2000 networks using PCTEL CDMA LX scanners.


New Equipment Case and Backpack Carrying Up to 8 Phones

In the past, a succession of hard cases and backpacks have been offered with TEMS Investigation for effortless carrying and managing of field-test equipment. For TEMS Investigation 14.3, this offering was once again upgraded in the form of a reconfigured TC-2450 equipment case and a redesigned TEMS Investigation Backpack, both accommodating up to eight phones (doubling the capacity of previous models such as the TC-1520 equipment case series). Depending on the number of phones installed, one or more scanners (PCTEL, DRT, or SRU) can also be mounted. The sales offering gives perfect flexibility in that the choice between hard case and backpack is simply an option that is specified for each unit ordered. Internal components such as mounting brackets are shared between the two types of carrying unit and can easily be moved from one to the other. The case and backpack come preconfigured with one or two ACUs (Audio Capturing Units), each supporting four phones. If there is no need to conduct audio quality measurement, the ACUs can be replaced by PCUs (Phone Control Units), which do not house any audio capturing modules but provide additional high-powered USB ports. The Audio Capturing Units were themselves new in this release, designed in-house and complementing the TerraTec ACUs that are part of the audio quality measurement solution offered in recent releases.


New Connectable User Terminals

Among the user terminals added in the 14.3 release, the ones from Samsung deserve special mention. As the current No. 1 user equipment vendor, Samsung is obviously of paramount importance to cellular operators worldwide, and Ascom acknowledged this fact by adding connectivity for two new top-of-the-line Samsung Galaxy devices, both equipped with LTE capability: Samsung Galaxy S III SGH-I747 (LTE/UMTS) Samsung Galaxy S III SCH-R530M (LTE/EV-DO)

This is not to say that other equipment vendors were neglected; on the contrary, TEMS Investigation 14.3 made these further devices connectable: Quanta 1K31 (LTE) ZTE MF821D (LTE FDD/WCDMA/GSM)


Support for PCTEL TD-LTE Scanners

Two TD-LTE scanners from PCTEL were added to the offering, forming a competitively priced and globally available solution for TD-LTE scanning: PCTEL SeeGull EX TD-LTE PCTEL SeeGull EX mini TD-LTE,

NT12-13416, 1.0, 11/6/2012

covering LTE Bands 38, 39, 40, and 41. Extending PCTEL support to this technology also added a missing piece to Ascoms coverage of the PCTEL scanner range, which is now more or less complete.


Pinpointing on Unpositioned Images

The Pinpoint Window previously required the maps used in it to be geographically positioned. In TEMS Investigation 14.3, however, it became possible to load unpositioned images into this window. This allows you to put any floor plan image to immediate use for pinpointing without having to position it first saving you time and removing an item from your list of necessary preparations. When a route is recorded on an unpositioned floor plan, route waypoints are stored simply as image pixel coordinates for the time being. Naturally, the image needs to be georeferenced later on to enable geographical positioning of the routes; this can be done for example in TEMS Discovery.


Scripted Channel Lock (Lock to UARFCN)

A new Channel Lock activity was introduced in the Service Control scripting tool. What this activity does is to lock the device to a subset of channels, for example, to a UARFCN or a set or UARFCNs in WCDMA. In TEMS Investigation 14.3, the Channel Lock activity is supported for the smartphones Sony Ericsson Xperia arc S, Samsung Galaxy S 4G, Samsung Infuse 4G, and well as for the older Sony Ericsson W995. The ability to force a device to a particular channel is perhaps the most important single time-saver among all device control features, and making the function scriptable renders it maximally easy and convenient to apply. The W995 was included in the implementation scope because of its enduring importance as a drive test device.


TD-SCDMA/TD-LTE Dual-mode Testing

Support was added for Hisilicon chipset based terminals with dual-mode TDSCDMA/TD-LTE capability. This combination of technologies is found chiefly in China.


Support for TEMS Pocket TPZ Logfile Format

TEMS Pocket logfiles in TPZ format were rendered directly readable in TEMS Investigation 14.3, without any need for file conversion using the TPZ Converter tool. This made TEMS Pocket data even more readily accessible to you as a TEMS Investigation user and integrated the two products still more tightly with each other.


New Features in TEMS Investigation 14.2

New Connectable Device: Sharp 105SH

TEMS Investigation 14.2 adds support for Sharp 105SH as a connectable device. To show only selected WCDMA bands and UARFCNs in the TEMS Investigation cell lock dialog for this device, store a file with the following format under C:\Users\<user>\ Documents\TEMS Product Files\TEMS Investigation 14.2\Settings, where <user> is the Windows user name:

NT12-13416, 1.0, 11/6/2012

?xml version='1.0' encoding='UTF-8' standalone='yes' ?> <!-- NOTE: This file must be placed in C:\Users\<user>\Documents\TEMS Product Files\TEMS Investigation 14.2\Settings (where <user> is the Windows user name), named UarfcnList.xml. All UARFCNs in the UarfcnList section must be on the same band. --> <List> <UarfcnList> <Band>I</Band> <Uarfcn>10763,10788,10812,10837</Uarfcn> </UarfcnList> <UarfcnList> <Band>XI</Band> <Uarfcn>3712,3737</Uarfcn> </UarfcnList> <UarfcnList> <Band>VIII</Band> <Uarfcn>3038</Uarfcn> </UarfcnList> </List>


New Features in TEMS Investigation 14.1

LTE Cell Frame Timing IEs

Inter-cell synchronization is a central concept in LTE networks. For TD-LTE in particular with its unpaired spectrum, the same frequency being used on both uplink and downlink, accurate synchronization between cells is crucial. Compared to FDD there is also a more complex range of interference issues to handle, including interference between UEs in adjacent cells and between eNodeBs. Still, even for FDD, synchronization is necessary within a site owing to the overlap between its cells; it is also highly beneficial between sites, since this enables the use of techniques such as CoMP (coordinated multipoint), scheduling traffic in an efficient way among multiple cells. TEMS Investigation 14.1 presents cell frame timing data in newly constructed information elements for the current LTE serving cell and neighbors. This information can for example be used to: Verify and troubleshoot synchronization in the network. Compare and evaluate synchronization techniques. Optimize heterogeneous cell deployment: for example, adjust timing in a pico cell to a surrounding macro cell, taking into account the propagation delay from the macro cell eNodeB. Identify co-sited cells (having identical or nearly identical timing offsets) in an unknown network. Estimate distance to a site and determine its position by triangulation.

NT12-13416, 1.0, 11/6/2012


Extended Control Functionality and Logging for Sony Ericsson Xperia arc S

In TEMS Investigation 14.1, Sony Ericsson Xperia arc S supports audio quality measurement, including PESQ and POLQA. See also section 2.4.3. The following additional control functions have been implemented for the Xperia arc S phone, taking smart measurements with this device several steps further: Access class control modify access class settings PLMN control lock on MCC + MNC combination BLER target control modify BLER target assigned by network Speech codec control redefine set of speech codecs enabled in phone

The data collection and presentation have also been augmented in various respects, notably: UARFCN and SC indicated for each SIB C/I per TCH computed for GSM circuit-switched services SIR target presented


POLQA for CS Voice

The state-of-the-art POLQA algorithm for speech quality assessment, previously introduced for VoIP, is now available also for circuit-switched voice. POLQA can be computed for both narrowband and super-wideband speech. POLQA is obtained in the ACU (TerraTec) audio quality measurement configuration.


Cell Whitelists

A common constraint in testing of cellular networks is to restrict tests to a predefined set of cells: for example, verifying a new or reconfigured cell cluster, or performing some procedure that would disturb regular network operation unless it is limited to cells that have been specially configured for the purpose. In TEMS Investigation 14.1 it is possible to enter a list of allowed cells (whitelist) and have it converted into a user-defined event. This event can then be used in a script to trigger some action whenever the tester is in an allowed cell. A periodic flag was added as a new property of user-defined events, so that a cell whitelist event can be generated repeatedly and continuously listened for by a script. Making use of these features lets the user conduct rigorously selective network testing in a minimum of time and without any extra effort in the field.


Scripted Scanning

Scanning tasks can be scripted instead of being run manually from the Navigator pane. Controlling scanning from a script brings the same benefits of convenience and automation as for other testing activities. In TEMS Investigation 14.1, scan scripting is limited to a subset of the supported scanner brands; see section 5.6.1 for details.

NT12-13416, 1.0, 11/6/2012


Manual Pinpointing Mode in Pinpoint Window

In the Pinpoint Window, routes can alternatively be traced manually while walking, as opposed to being planned in advance and followed during the walk. The manual mode is similar to the pinpointing function in the Map window. Offering both modes in the Pinpoint Window tool adds further to its flexibility and usefulness.


Hisilicon LTE Chipset Support

The accessibility of LTE network testing was further broadened as TEMS Investigation 14.1 added support for Hisilicon chipset based LTE devices.


Via CDMA/EV-DO Chipset Support

TEMS Investigation 14.1 introduced support for devices equipped with a Via CDMA/EV-DO chipset.


New Connectable User Terminals

Axesstel MV610VR (Gateway R90, Net1, EV-DO Rev. B) Huawei E398S (Hisilicon chipset based)


New Connectable Scanners

A TD-LTE scanner from Transcom Instruments is offered as a cost-efficient solution for scanning of TD-LTE networks. Supported LTE bands are: TDD 1900 MHz (Band 39) TDD 2300 MHz (Band 40) TDD 2600 MHz (Band 38)


LTE RRC Redirection Events

The LTE RRC connection redirection events were extended to cover redirection to EVDO (HRPD/eHRPD).


New LTE Information Elements

PDSCH BLER and ack/nack counters for Transport Blocks 0 and 1 separately, giving a more fine-grained view of retransmission statistics. PUSCH ack/nack counters. Rank Indication counters showing incidence of values RI = 1 and RI = 2, useful for studies of MIMO channel properties.


Misc. Enhancements

Support added for scanning LTE Band 25 with DRT4301 scanner. Multiple concurrent LTE scans of the same type can now be assigned to PCTel MX scanners. 7

NT12-13416, 1.0, 11/6/2012

With firmware version installed on the Xperia arc S, it is no longer necessary to avoid having APNs defined in the phone. Compare the Getting Started Manual, section 10.4. When using PJSIP as VoIP client, the Route: header can optionally be removed from SIP messages addressed to VoIP servers. To remove these headers, set UseRouteHeader to false in the file <TEMS Investigation install dir\Application\ Configuration\Investigation.Voip.config.


Corrected Bugs
Bugs Corrected in TEMS Investigation 14.4

Filemark events missing when exporting logfile in MapInfo Tab format. Information elements in the Media Quality category did not display in Map window.


Bugs Corrected in TEMS Investigation 14.3

Last few messages missing in the presentation when loading a logfile in TEMS Investigation 14.0. Faulty presentation in TEMS Investigation 13.1 of logfiles with RSSI scan data recorded with DRT scanner. The reason was that the logfile recording was started only after the scanning was begun; this did not work with DRT scanners in TEMS Investigation 13.1. This limitation was removed in TEMS Investigation 14.0. Script branching with the IfElse activity was broken, with the Any branch being executed all the time. Problem with GPS position accuracy for NMEA device in TEMS Investigation 14.0. The reason was that other device detectors interfered with detection of NMEA devices; bug fixed. In TEMS Investigation 14.0, when exporting a logfile containing Pinpoint Window routes in text format, the positioning data was not included. PUSCH Modulation reported as 64-QAM although the device did not support this modulation scheme. Inter-RAT neighbor measurements not always cleared in the presentation when they are no longer updated (i.e. after those particular measurements have ceased). Incorrect timestamping of service start/stop events such as HTTP Start. When this occurred, it was due to incorrect start/stop times for the logfile recording as a whole. Problems with low throughput and dropped connections during LTE and UMTS data collection with multiple UEs engaged in concurrent data sessions. Decoding of Qualcomm report LTE ML1 radio link monitoring (0xB18A) not supported. TEMS Export tool crashed when user tried to exit. Power Control Indication DL/UL information elements not obtained from Sony Ericsson W995. 8

NT12-13416, 1.0, 11/6/2012

Service session events duplicated in logfile report. GSM C/I for hopping channels in dedicated mode was not displayed with Nokia C7. RRC state sometimes incorrect. Logic for RRC state updating refined, now also taking into account Cell Update Confirm messages. Problems detecting SRU in TEMS Investigation. 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. HTTP download sometimes failed due to illegal characters in URL. Bug fixed in HTML parsing. In *.trp file name timestamp, the hour part (2 digits) was given in 12-hour format, so that AM and PM hours could not be distinguished. Naming changed to use 24hour format. Uplink data and Frequent AQM missing after exporting merged AQM logfile as text. TEMS Investigation software update function not working when Use automatic configuration script setting was active in Internet Explorer. Incomplete decoding of some LTE messages, including Attach Request where some capabilities were missing. Application crashed on loading a map with file name consisting of a single digit, for example 1.tif.


Bugs Corrected in TEMS Investigation 14.2


Bugs Corrected in TEMS Investigation 14.1

Events and their accompanying extra information were garbled in text-format logfile export whenever one message gave rise to multiple events. SAN (Serving/Active Set + Neighbor) information elements such as CPICH RSCP and Ec/Io supplied as extra information with various events even if the IE values had not changed. Blocked Call event erroneously generated when receiving voice call on URA_PCH. Channel Release message not decoded correctly in TEMS Investigation. CS Fallback message MobilityFromEUTRACommand (3GPP 36.331) not fully decoded by TEMS Investigation 13.1. LTE information elements not selectable for labeling of bar chart x-axis. GSM RSSI Scan bar chart modified to show channels from different bands side by side instead of toggling between the bands. Network Bandwidth (Iperf) testing modified so that throughput is obtained even if IP sniffing has been turned off or is not supported by the device. Specifically, if the IP sniffer is not active, the time of the first packet is determined from the first Iperf client report instead. 9

NT12-13416, 1.0, 11/6/2012

RRC State always shown as Camping for Sequans UE, even when the device was in fact in state Connected. Updating of RRC State modified for Sequans devices (RRC State value in NAS Info ignored). WCDMA UE Tx Power information element not updated for Xperia arc S. Logging added in TEMS Investigation for new type of WCDMA AGC report used by the arc S device to communicate this data. Some Blocked Call events not visible in text-format logfile export. TEMS Investigation behavior changed to allow inclusion in the text export of events triggered by an invisible (undecoded) message.

Removed Features

No features have been removed in any of the releases TEMS Investigation 14.114.4.


Known Bugs and Limitations

PC Application Related
Installation and Start-up

When installing TEMS Investigation for the first time, it may take 1020 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. 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 applications 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 publishers certificate revocation and click Apply.

(This procedure can be automated by the use of Group Policies.)

NT12-13416, 1.0, 11/6/2012


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.


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 8. 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 (34 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; 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

NT12-13416, 1.0, 11/6/2012


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, 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. 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>\Application\Investigation.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. 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 CDMA devices that do not support AT commands. 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

NT12-13416, 1.0, 11/6/2012


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 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 Users Manual, section 9.1.12. 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. 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.

NT12-13416, 1.0, 11/6/2012


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.


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.


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. The CounterPath VoIP client cannot be run under 32-bit Windows Vista.


Device Related: General

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 Users Manual, section, 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.


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_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\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 103 s = 1,800,000 bits, or 1,800,000 / 8 = 225,000 bytes

NT12-13416, 1.0, 11/6/2012


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.


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_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ Parameters\Interfaces\<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).

NT12-13416, 1.0, 11/6/2012


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


User Terminal Related


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.


Sony Ericsson Android Phones (Qualcomm Chipset Based)

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.


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, the Network Connect activity in the TEMS Investigation script, which tries to set the APN, will fail.) 16

NT12-13416, 1.0, 11/6/2012

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.


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

NT12-13416, 1.0, 11/6/2012


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


Qualcomm Chipset Based Phones and PC Cards

(Notes specific to Sony Ericsson Xperia models are found in section 5.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 Users Manual, section 8.3.4 for details on how to operate this utility. 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. 18

NT12-13416, 1.0, 11/6/2012

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 Users Manual, section 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. 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. 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 5.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 1020 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 phones 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>\Application\ Configuration\Investigation.RecurringImei.config, replace the default IMEI with the phone IMEI. Save the file.


Samsung Devices Based on Samsung Chipset

The event IP Interruption Time cannot be generated for Samsung chipset based devices.

NT12-13416, 1.0, 11/6/2012



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.


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.


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.


Via Chipset Based Devices

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 and download the file vcredist_x86.exe. Knowledge Base reference: KB2538243.


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

NT12-13416, 1.0, 11/6/2012

The video call capability of the Nokia C7-00 is not supported in TEMS Investigation.


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 powercycling it. The AQM module then needs to be paired once again with its phone. This is done from the Navigators 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.


ACU Related

This section relates to the Audio Capturing Unit (TerraTec box). USB 3.0 should not be used in conjunction with the ACU, since it introduces noise into the recordings and degrades AQM scores.


Scanner Related

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 Users Manual, section 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):

NT12-13416, 1.0, 11/6/2012


RSSI scan: 100 kHz bandwidth; available channels 27503449

Signal scan: 1.4 MHz bandwidth: N/A 3 MHz bandwidth: N/A 5 MHz bandwidth: available channels 27723428 10 MHz bandwidth: available channels 27953405 15 MHz bandwidth: available channels 28173383 20 MHz bandwidth: available channels 28403360


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.



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


Anritsu ML8780A

Scanning with the Anritsu ML8780A has only been tested on Windows 7 (Englishlanguage version). Only one measurement unit in the Anritsu ML8780A scanner is supported.


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.

NT12-13416, 1.0, 11/6/2012


Firmware versions 02.03.xx and later are not compatible with TEMS Investigation 12.0.x and earlier.


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 1015 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. 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 Navigators 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 and later, be sure to install the driver delivered with TEMS Investigation. Do not install any driver provided on PCTels web site. The reason is as follows: If you have PCTels 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.

NT12-13416, 1.0, 11/6/2012



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


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.


Rohde & Schwarz TSMW

Rohde & Schwarz TSMW scanners must have firmware version 1.10 installed.



The Transcom scanner is not capable of scanning more than one LTE band at a time. Transcoms Eagle PC software cannot run concurrently with TEMS Investigation.


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


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: In PowerShell, also check that Get-ExecutionPolicy returns RemoteSigned. If you get a different response, run the command Set-ExecutionPolicy RemoteSigned. 24

NT12-13416, 1.0, 11/6/2012


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.

Contact Information

Please visit our website at For customer support contact information, see the page


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


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.

NT12-13416, 1.0, 11/6/2012