TEMS Investigation 17.2 Help

(1)

(2)

(3)

(4)

(5)

Chapter 1. Introduction to TEMS Investigation

1. Introduction to TEMS

Investigation

Thank you for choosing TEMS Investigation – the industry-leading tool for troubleshooting, verification, optimization, and maintenance of wireless networks. Offering data collection, real-time analysis, and post-processing all in one, TEMS Investigation is a complete solution for all of a network operator’s daily network optimization tasks. This complete solution eliminates the need for multiple tools, reducing costs and saving time and effort for operations staff.

To get the most out of TEMS Investigation, please take the time to read this documentation in order to gain an in-depth understanding of the product features.

Please note that in between product releases, the most up-to-date edition of this documentation is the one found online in browsable format. A PDF version for the latest product release is available through the GLS web interface.

1.1. Fundamentals of TEMS Investigation

TEMS Investigation is an air interface test tool for cellular networks, supporting all of the following technologies:

• LTE (FDD and TDD) • WCDMA/HSPA/HSPA+ • GSM/GPRS/EGPRS

• TD-SCDMA (including interaction with LTE and GSM)

• EV-DO Rev. B/EV-DO Rev. A/EV-DO Rel. 0/cdma2000/cdmaOne • Wi-Fi

• WiMAX (scanning)

TEMS Investigation enables monitoring of a wide variety of data services over packet-switched connections, as well as CS voice and video telephony.

(6)

TEMS Investigation can be purchased with or without data collection capability (“Base Software Package” and “Replay Package” respectively). Supported cellular technologies can be freely selected and combined, except that WCDMA and GSM always come together.

Separate license options are offered for (among other things): • Data collection with devices from various vendors. • Data collection with multiple devices concurrently. • Audio quality measurement (AQM).

1.3. Regional Editions

Please be aware that the TEMS Investigation product also exists in various regional editions, all of which are covered by the present documentation but are not differentiated here. This means that descriptions of functionality and external device compatibility are not necessarily applicable in every single respect to the TEMS Investigation edition you have purchased. Any restrictions that apply to your edition are indicated in the Release Note included in the delivery.

1.4. Overview of Documentation

This documentation contains the following volumes: • Quick Guide

– Tells how to install the product, configure devices, and use the core functions of the application. This is a simple “getting started” guide which is independent of the volumes that follow.

(7)

Chapter 1. Introduction to TEMS Investigation

• Installation Guide

– Describes how to install the TEMS Investigation software, also covering PC requirements and licensing issues.

• Device Configuration Guide

– Covers the range of connectable devices and explains how to configure them for use with TEMS Investigation, along with driver installation and any other PC configuration that may be necessary. • User’s Manual

– This is a comprehensive guide to the TEMS Investigation user interface and all its functions.

• Information Elements and Events

– Provides full detail on all information elements and events presented in TEMS Investigation, with references to telecom and other

standards. Also describes all preconfigured presentation windows. • Technical Reference

– Describes various TEMS product specific file and report formats, and gives other information of a technical nature.

• Utilities

– This is a tutorial on various utilities provided along with TEMS Investigation.

Some technical issues not addressed in this documentation are dealt with in the Release Note, which is provided alongside it.

1.5. Contact Information

1.5.1. Technical Support

As a TEMS customer, you can log in to the TEMS Portal at

www.ascom.com/nt/en/index-nt/tems-support.htm in order to access the complete range of TEMS Investigation product information.

If you have a question about TEMS Investigation which is not answered in any written source, please contact TEMS technical support. Contact information is given on the page just linked.

(8)

(9)

Chapter 2. Recently Introduced Features in TEMS Investigation

2. Recently Introduced Features

in TEMS Investigation

2.1. What’s New in TEMS Investigation 17.2

2.1.1. New Supplied Device: Sony Xperia Z5 E6653

This LTE Category 6 device is VoLTE-capable (operator-specific settings needed in IMS settings app). With Ascom software installed, it computes POLQA and offers the same rich set of control functions as on previous models in the Xperia Z series.

• Frequency bands:

– LTE 2100 (Band 1), 1900 (B2), 1800+ (B3), AWS (B4), 850 (B5), 2600 (B7), 900 (B8), 700ac (B12), 700bc (B17), 800DD (B20), 700 APT (B28), TDD 2600 (B38), TDD 2300 (B40)

– WCDMA 850 (Band V), 900 (VIII), 1900 (II), 2100 (I) – GSM 850, 900, 1800, 1900

• Throughput capabilities:

– LTE Category 6 (300/50 Mbit/s)

– HSDPA Category 24 (42 Mbit/s), HSUPA Category 6 (5.8 Mbit/s) – GPRS/EDGE Class 12

• Real-time control capabilities: – RAT lock (LTE, WCDMA, GSM) – Band lock (LTE, WCDMA, GSM) – LTE EARFCN/PCI lock

– WCDMA UARFCN/SC lock

– GSM cell lock/multi-lock, cell prevention – Vocoder lock

(10)

2.1.2. New Supplied Device: Samsung Galaxy Note 5

SM-N920I

This is the first LTE Category 9 device (capable of downlink data transfer rates up to 450 Mbit/s) to be connectable in TEMS Investigation. It can compute POLQA in an ACU R2 configuration (M2M/M2F). The phone is VoLTE-capable; however, this requires special customization.

– LTE 2100 (Band 1), 1900 (B2), 1800+ (B3), AWS (B4), 850 (B5), 2600 (B7), 900 (B8), 700ac (B12), 700bc (B17), 850 (B18), 850 (B19), 850 (B26), 700 APT (B28), TDD 2300 (B40)

• Google Android 5.1.1

• WLAN 802.11a/b/g/n/ac (2.4 and 5 GHz) • Integrated GPS with A-GPS support

(11)

2.1.3. New Supplied Device: Samsung Galaxy S6

SM-G9208

This is an LTE Category 6 device intended for the APAC market. It can compute POLQA in an ACU R2 configuration (M2M/M2F). The phone is VoLTE-capable; however, this requires special customization.

– LTE TDD 2600 (Band 38), TDD 1900 (B39), TDD 2300 (B40), TDD 2500 (B41)

– WCDMA UARFCN/SC lock • Google Android 5.0.2

• Chipset/CPU: Samsung Exynos 7420, 8-core, 4x 1.5 GHz, 4x 2.1 GHz

2.1.4. Other New Connectable Devices

• Motorola VML750

2.1.5. New Supported Scanners

Mobile network scanning can now be done with the following scanners: • JDSU W1314B

(12)

2.1.6. GSM C/I from Qualcomm Chipset Devices

The GSM C/I metric, previously available with various older Sony/Sony Ericsson phones, can now be obtained with newer Qualcomm chipset based devices. Note: The “TEMS GSM C/I Report” must be turned on in the device properties.

2.1.7. Short Sequence Order Call in M2F Audio Quality

Measurement

In the M2F Dial Answer snippet, the initial Sequence Order (SO) call used to set up the connection to the Call Generator can now optionally be shorter than the subsequent MO and MT calls. The minimum duration of the SO call is 60 seconds.

2.1.8. ACU R2 Tuning for New Devices

The following additional devices have been audio-tuned for AQM in an ACU R2 setup:

• Samsung Galaxy Note 5 SM-N920I (CS/VoLTE, M2M/M2F) – see also section2.1.3

• Samsung Galaxy S6 SM-G920V (CS/VoLTE, M2M) • CMCC N1 (CS/VoLTE, M2M)

(13)

2.2. What Was New in TEMS Investigation 17.1

2.2.1. Devices

2.2.1.1. New Supplied Devices

• LG G4 VS986 with ODM software

• Samsung Galaxy S6 SM-G920F with ODM software • Samsung Galaxy S6 Edge SM-G925F with ODM software • Samsung Galaxy S6 Edge+ SM-G928P with ODM software

2.2.1.2. Other New Connectable Devices

• Sony Xperia Z4 402SO with ODM software • Apple iPhone 6S, 6S Plus

• CMCC N1

• LG G4 H815

• Samsung Galaxy Note 5 SM-N920A, SM-N920I, SM-N920T • Samsung Galaxy S6 SM-G920I, SM-G920R4, SM-G920W8 • Samsung Galaxy S6 Edge SM-G925R4

• Samsung Galaxy S6 Edge+ G928A, G928F, G928I, SM-G928T, SM-G928W8

• Samsung Galaxy S5 SM-G900W8 • ZTE T50, T60

2.2.2. Data Collection

2.2.2.1. Comprehensive On-device Testing with Samsung Galaxy S6

The SM-G920F, SM-G925F, and SM-G928P models of the Samsung Galaxy S6 now came equipped with a wide range of on-device services, including ones for testing voice, FTP, HTTP, YouTube streaming, and social media (Facebook, Instagram, Twitter), as well as Blixt™ for available bandwidth measurement. Many S6 models were already connectable in TEMS

(14)

device)

• Samsung Galaxy S5 SM-G900A with commercial firmware • Samsung Galaxy S5 SM-G900V with commercial firmware These devices target the US and Central American market.

2.2.2.3. Support for iPhone 6S/6S Plus and Simpler iPhone Data Connection Setup via NDIS

TEMS Investigation 17.1 added iPhone 6S and 6S Plus to the roster of supported iPhone models. What is more, the tethered data connection between iPhone and PC could now be set up via the NDIS interface instead of over Wi-Fi as was previously necessary. The NDIS setup is far simpler to configure.

Both the 6S models and data testing over NDIS require iOS 9.0 or later.

2.2.2.4. LTE: PDCP Throughput by QCI (Service-specific)

To get a firmer grasp of service performance in an LTE network, it is interesting to monitor throughput for different services separately. To this end, TEMS Investigation 17.1 introduced presentation of PDCP throughput by QCI, that is, according to the Quality-of-service Class Identifier which is unique to each service. Notably, conversational voice has QCI = 1, and conversational video has QCI = 2.

2.2.2.5. LTE: More Measurements on Aggregated Carriers

Carriers in CA configurations were distinguished in still more information elements: PDSCH MCS*, PDSCH Modulation*, and PDSCH Number Of Used Transport Blocks. This was implemented for Qualcomm chipset

(15)

This data further enriched the set of diagnostics available for verifying and troubleshooting carrier aggregation mechanisms, which are complex and often device-specific.

2.2.2.6. LTE: PMI Feedback, Rank Indication Feedback

The PMI (Precoding Matrix Indicator) and RI (Rank Indication) values currently in use for LTE downlink transmission have long been presented in TEMS Investigation. The 17.1 version complemented these by adding the PMI and RI feedback reported by the UE to the eNodeB, advising it on what PMI and RI values should be used according to the UE’s latest channel estimation.

2.2.2.7. HSPA Multicarrier Support

3GPP Release 11 introduced multicarrier HSPA, which uses up to four carriers on the downlink. TEMS Investigation 17.1 extended its HSPA coverage to present a range of data on such configurations:

• HS downlink serving cell count and HS session type

• HS CQI; HS-DSCH ack/nack rate, HS-DSCH DTX rate, and HS-DSCH throughput for all four carriers.

Furthermore, the use of dual carrier HSUPA (3GPP Release 9) was included in the reporting, reflected in information elements such as HS uplink serving cell count and E-DCH throughput per carrier.

2.2.2.8. More Information Elements from Samsung Chipset Devices

Many gaps were filled in with regard to information element support in Samsung chipset based devices, across all of LTE, WCDMA, and GSM.

2.2.3. Service Testing

2.2.3.1. Video Telephony and ViLTE

• The video call functionality in TEMS Investigation was revamped to enable ViLTE testing with a wide variety of Qualcomm chipset based devices as well as others. ViLTE, the video telephony counterpart of the VoLTE voice service, is slated for imminent deployment by a number of operators.

(16)

for ViLTE. Data is already obtained on lost, discarded, and corrected packets as well as on packet delay variation. Video and audio MOS scores (computed by the VQmon algorithm) will follow in a later release as soon as video call inject has been implemented in a similar manner as for voice AQM.

2.2.3.2. Twitter Testing

The rollout of social media testing capabilities continued in TEMS

Investigation 17.1 with the Twitter service. Testable operations are: loading the home timeline or that of another user, posting tweets (optionally with a photo), and searching tweets for specified contents.

Testing Twitter like a user gives you a comprehensive view of service performance, especially by correlating RF measurements with actual end-user operation success rates.

2.2.4. Presentation

2.2.4.1. KPI Report

The KPI report was a new reporting tool in TEMS Investigation 17.1. Processing logfiles continuously as soon as they have been recorded, the tool presents familiar KPIs for voice and data services in a Microsoft Excel workbook. A fundamental and pervasive feature of the KPI report is that it compares operators in terms of each computed metric.

In the report are also listed all logfiles that contributed to the KPI statistics. You can open a contributing logfile in TEMS Investigation to drill down into the drive test data.

(17)

2.2.5. Usability

2.2.5.1. Equipment Health

Equipment Health was added as a new information element indicating the current state of activated devices. As long as a device operates normally, it is declared to be “healthy”. However, the state will change if the device shows signs of failing health: for example, if it has been in no service mode for several minutes, if it has stopped sending or receiving data, or if it has ended up in a state where it needs to be restarted.

Devices’ health states are presented in a new predefined window, allowing you to continuously correlate them with measurement data and gain a better understanding of potential degradations of service performance caused by equipment.

2.2.5.2. Mapping of SIM Cards to Phone Numbers

TEMS Investigation 17.1 maintains a mapping table in the form of a text (CSV) file that keeps track of the phone number of each SIM card (IMSI) in use. For a device detected in TEMS Investigation, you can click its Phone Number field to access and edit this mapping table. You can of course also edit the CSV file externally. With this new mechanism, you can move a SIM to a new device and TEMS Investigation will still be correctly informed about the device phone number.

2.2.5.3. Deferring Parameter Definitions in Scripts

Some new syntactical features in script configuration sets allow you to put off assigning a value to a parameter until the script is to be run. On starting the script, you are then prompted to enter a value for that parameter. For now, the mechanism has been implemented for device phone numbers only.

Another possibility is to let TEMS Investigation automatically determine the parameter value when running the script. Phone numbers are retrieved by querying the device via AT.

This function allows you to reuse the same script without modification for example when a device is going to dial a series of different phone numbers.

2.2.5.4. Comment Labels for Wait Activities

Wait activities in scripts can be tagged with a free-text comment which will be displayed on the Status tab of the Service Control Designer during script

(18)

2.3.1. Devices

2.3.1.1. New Supplied Device: Samsung Galaxy Note 4 SM-N910F with ODM Software

This is a Galaxy Note 4 phone operating on LTE (FDD/TDD) and UMTS. It is a Category 6 device, thus supporting carrier aggregation. With Ascom software installed it can compute POLQA.

– LTE 2100 (Band 1), 1900 (B2), 1800 (B3), AWS 1700/2100 (B4), 850 (B5), 2600 (B7), 900 (B8), 700 (B17), 800 (B20)

– WCDMA UARFCN lock – WCDMA disable handover

(19)

• Chipset/CPU: Qualcomm APQ8084, quad-core, 2.7 GHz

2.3.1.2. New Supplied Device: Sony Xperia Z3 D6603 with ODM Software

Sony’s successor to Xperia Z2 began to be shipped with Ascom on-device software installed, including a wide repertoire of control functions, as detailed below.

– LTE 2100 (Band 1), 1900 (B2), 1800 (B3), AWS 1700/2100 (B4), 850 (B5), 2600 (B7), 900 (B8), 750 (B13), 700 (B17), 800 (B20)

– WCDMA 850 (Band V), 900 (VIII), AWS 1700/2100 (IV), 1900 (II), 2100 (I)

– GSM 850, 900, 1800, 1900 • Throughput capabilities:

– WCDMA UARFCN/SC lock

– GSM cell lock/multi-lock, cell prevention – Access class control

– Speech codec control

– Control of behavior towards barred and reserved cells • Google Android 5.0

• WLAN 802.11a/b/g/n/ac (2.4 and 5 GHz)

(20)

• SM-G920P, SM-G925P (Sprint)

• SM-G920T, SM-G925T (T-Mobile; VoLTE-capable) • SM-G920V, SM-G925V (Verizon, VoLTE-capable) • SM-G9208 (CMCC)

All Galaxy S6 phones are LTE Category 6 (300/50 Mbit/s), carrier aggregation capable devices running Google Android 5.0 (Lollipop).

2.3.1.4. PCTel SeeGull MXflex

TEMS Investigation 17.0 added connectivity for PCTel’s latest mobile network scanner, the MXflex. It has the same capabilities as the MX, while offering a more flexible configuration of frequency bands (just like the other “flex” models).

The MXflex features software-definable, field-upgradeable support of bands all the way from 130 MHz to 6 GHz. This framework makes it easy for customers to start out with whatever bands they need at one point in time, then grow the feature set as new markets, technologies and spectrum become relevant.

2.3.1.5. New Altair Chipset Supported

TEMS Investigation 17.0 upgraded its Altair chipset connectivity by supporting the new FourGee 3800 LTE chipset (FDD/TDD). This replaced the older DC-E3100 chipset previously supported.

2.3.1.6. Other New Connectable Devices

• HTC One M9 (TMO)

(21)

2.3.2. Data Collection

2.3.2.1. LTE Carrier Aggregation: Extended Logging

Further LTE logging was extended to carrier aggregation setups, with separate values being reported for the primary and secondary carriers: • PDSCH physical resource block allocation:

– PRB count (number of blocks used)

– PRB % (blocks used as percentage of maximum) – PRB start (index of first block allocated)

– PRB allocation count (number of blocks allocated over 1 s) • PDSCH SINR

2.3.2.2. LTE Carrier Aggregation: Presentation of Tertiary (Third) Carrier

For Qualcomm and Samsung chipset based devices, TEMS Investigation 17.0 presents data and measurements on all three serving cells in 3-CA carrier aggregation deployments. Cell data includes frequency band, bandwidth, PCI, and EARFCN; measurements include RSRP, RSRQ, RSSI, and CINR.

2.3.2.3. System Information Decoding in LTE Scanning (PCTel, R&S)

Decoding of System Information during LTE signal scans became supported both with PCTel scanners (EXflex, IBflex, MXflex, and MX models) and with the Rohde & Schwarz TSMW.

2.3.2.4. Network Scan with PCTel Scanners

The network scan procedure, aimed at exploring an unknown radio environment and detect any mobile network carriers present, became supported also with PCTel scanners (EXflex, IBflex, MXflex, MX). As a first step, PCTel network scanning is supported for LTE and WCDMA. (PCTel refers to this form of scanning as “blind scan”.)

For WCDMA, one detected cell is reported for each UARFCN that exhibits network activity. For LTE, multiple cells can be reported from each EARFCN, along with their E_c/I₀ readings.

(22)

2.3.3.1. ODM Digital Audio

ODM Digital Audio was added as a new function in Ascom on-device software. It taps the audio stream in digital format from the smartphone, which means the audio is minimally affected by phone settings and adjustments (as opposed to the situation after conversion to analog). This provides a more network-centric scoring which remains more stable and comparable over time as handset models are replaced with new ones. The digital audio stream can then be fed to TEMS Investigation, and AQM scores can be calculated on the PC without any need for additional hardware or cables. With the mobile devices running the voice service, it may be preferable not to burden them further with the costly AQM computation, passing on that task to the PC instead. Letting the mobile devices focus on the voice service alone brings the testing closer to real-life conditions. Devices supporting ODM Digital Audio are listed in the Device Configuration Guide, section2.6.2.

2.3.3.2. Generic AQM for Arbitrary Voice Services

As is well known, there are many voice services besides CS voice and VoLTE, including a host of OTT services like Skype, Facebook Messenger, Google Talk, and WhatsApp. TEMS Investigation 17.0 can measure audio quality for any of these. The call needs to be set up manually because of the proprietary signaling involved, but once the call is established, you can play sentences from an ACU R2 unit on the connection and collect the same AQM data as for a CS voice call.

2.3.3.3. Facebook Testing

(23)

feeds, and loading friend lists. The usual “success rate” and “average time” KPIs can be computed for each operation.

2.3.3.4. Instagram Testing

TEMS Investigation 17.0 can also test the Instagram photo sharing service. A new on-device service performs the essential operations of logging on to Instagram, loading picture feeds, searching for a hashtag, and logging off. Any Instagram account can be used for this testing: no special configuration is required. Success rates and execution times are recorded just as for Facebook.

2.3.3.5. Multiple Concurrent FTP Sessions

With the on-device FTP client, it became possible to download/upload multiple instances of the same file concurrently. This feature is a convenient means of increasing the load when testing high-speed connections.

2.3.3.6. Multi-thread FTP Download

Yet another new option for FTP download was to distribute a file transfer over multiple threads, each thread downloading a different part of the file. The point of using this option is to let you assess the performance gain achieved with multi-threading compared to single-thread download. Multiplying threads does not change the total traffic load, unlike the option discussed in section 2.3.3.5.

2.3.3.7. Streaming Quality Measurement with PEVQ-S

PEVQ is an algorithm for perceptual evaluation of video quality. It resembles PESQ and POLQA for speech in that it is a full-reference algorithm comparing the degraded video with the original, frame by frame and pixel by pixel. PEVQ models the human visual system all the way from the eye to the image-processing parts of the brain, quantifying the severity of distortions and artifacts as humans perceive them.

PEVQ-S (“S” for streaming), in addition to analyzing video frames with PEVQ, also makes use of bitstream data from which it obtains information on codec type, bit rate, frame rate, some transmission errors, and spatial/temporal shifts. PEVQ-S is therefore classified as a “hybrid” algorithm as opposed to PEVQ proper, which relies solely on an analysis of the video signal.

(24)

application layer when the retransmission succeeds).

2.3.4. Usability

2.3.4.1. TEMS Investigation Launcher

The workspace selector appearing first on start-up of TEMS Investigation morphed into an expanded view called TEMS Investigation Launcher. It encompasses the workspace selection function but also several others: • Projects: See section 2.3.4.2.

• Detector configuration: Here you can change what brands of scanners and certain other device types TEMS Investigation tries to detect. These settings existed within the main application but are mirrored in the Launcher so that they can be changed at start-up time.

• Tracing: This is a tool for resolving support issues.

2.3.4.2. TEMS Investigation Projects

Projects, a wholly new concept in TEMS Investigation 17.0, may be thought of as an extension of workspaces.

When you save a project, it will hold the workspace as one part, but also the outdoor map, indoor map set, and scripts currently loaded in the

application. Projects can be exported as compressed archives for easy distribution via Dropbox or FTP.

Working with projects allows on-the-spot configuration of TEMS Investigation with everything a tester needs, and the configuration can be done uniformly and reliably across an entire team.

(25)

2.3.4.3. Log Configurations: Keeping Down the Logfile Size

In LTE and other high-speed networks, devices will typically record a huge amount of data. For Qualcomm chipset based devices, you can control what kinds of data are written to logfiles in order to keep the file size down. What was new in the 17.0 version is that such logging configurations can be saved to file and reused. They can also be applied during script execution by means of a new script activity called “Log Configuration”.

Predefined logmasks are provided that are optimized for various forms of LTE testing: VoLTE only, data services only, and multi-RAB sessions with both VoLTE and some data service running at the same time.

For Samsung chipset devices, too, it is possible to optimize LTE logging for each of the three use cases mentioned above.

2.3.4.4. Improved Feedback on Device Detect Progress in User Interface

While a device is being detected, the progress of the detection procedure is indicated step by step in the user interface. Should the detect fail, further details are provided in a tooltip, with a hint whenever possible on how to have the device successfully detected (for example, it may need to be tethered).

2.3.4.5. Shortened Application Start-up Time

The start-up time for the TEMS Investigation application was more or less cut in half. Changing workspaces is also correspondingly quicker. The only precondition is that all necessary GLS licenses be installed on the PC, so that TEMS Investigation does not have to communicate with the license server during start-up.

2.3.4.6. New Sentinel Licensing Solution: Sentinel LDK

Sentinel LDK was introduced as a licensing solution, replacing Sentinel HASP SRM. The new solution uses hardware keys (dongles) exclusively and is thus of the “HL” variety. The hardware key is installed locally on the machine running TEMS Investigation. Unlike the old solution, Sentinel LDK is driverless, although a driver can be installed if desired (for example, to inspect what licenses are encoded in the hardware key).

(26)

– GSM uplink data (MTR) files

2.4. What Was New in TEMS Investigation 16.3

2.4.1. New Connectable Devices

• Samsung Galaxy Note 4 SM-N910F with ODM software • Samsung Galaxy Note 4 SM-N910G with ODM software • Samsung Galaxy Note 4 SM-N9100 with ODM software • Samsung Galaxy S5 SM-G900T with ODM software

• Samsung Galaxy S5 SM-G900V with ODM software and firmware version 1.0.3

• Franklin Wireless U810

• LG G3 D727 (VoLTE-capable device) • Netgear Aircard 340U

• WeTelecom M9310A • ZTE MF667

2.4.2. RouteDiary

RouteDiary is a stand-alone utility that lets you take notes on drive tests in a structured manner and link them to logfile data. RouteDiary can be launched from within TEMS Investigation and run concurrently with it during testing. The utility is equipped with its own map view where your drive test route is traced.

(27)

Reports can be generated in RouteDiary based on your entered notes, also including a summary of TEMS Investigation activities similar to that found in the Navigator pane.

2.4.3. eMBMS

Multimedia Broadcast Multicast Services (MBMS) is a standard designed to provide efficient delivery of broadcast and multicast services. When offered over LTE, it is referred to as eMBMS. Target applications include mobile TV and radio broadcasting as well as file delivery and emergency alerts.

TEMS Investigation 16.3 introduced a number of information elements and events reporting on eMBMS, including:

• Activation and deactivation of eMBMS bearer • Presence of Multicast Control Channel, MCCH

• Performance metrics for Physical Multicast Channel, PMCH: decoding success rate, received transport blocks

2.4.4. New Mode Reports for Carrier Aggregation

Mode reports are obtained from Qualcomm chipset LTE devices when secondary serving cells are activated and deactivated in an LTE network with carrier aggregation. The mode reports extract these vital facts from logs which generate huge volumes of data and are therefore unattractive to decode.

Further mode reports are obtained:

• whenever a Layer 3 message with a secondary cell configuration arrives;

• whenever a secondary cell is automatically deactivated because it has received no data traffic within a predetermined time.

2.4.5. LTE MIMO Scanning with PCTel SeeGull IBflex

LTE MIMO scanning with multiple Rx antennas, already available with the PCTel SeeGull MX scanner, became supported also with the newer IBflex model.

(28)

both scripted data collection and presentation in TEMS Investigation, as well as to user actions during drive testing.

However, if an IPsec key can be retrieved in some way, that key can be input to TEMS Investigation in runtime from version 16.3 onward, enabling the application to decrypt SIP and RTP and thus execute data testing services. It also enables real-time presentation of SIP and RTP messages as well as the calculation of metrics dependent on this signaling. When a logfile is being recorded, the IPsec key is stored in the logfile; the key is used again when you replay the file.

Alternatively, if you have run IPsec-encrypted services manually, you can input the key when replaying the logfile, so that SIP and RTP messages can be decoded and dependent metrics calculated and presented.

It is possible to input multiple IPsec keys, in which case TEMS Investigation will try them one by one.

2.4.8. Android Phone Monitor

The regular user interface of an Android phone can be accessed and interacted with through a view called Android Phone Monitor, added in TEMS Investigation 16.3 (it is opened from the context menu of a connected device in the Navigator). Tapping and swiping can be directly imitated with the mouse, whereas additional controls are provided corresponding to the device’s physical buttons. The monitor is useful especially for controlling a device connected to a PC in a remote location, or a device mounted in an equipment case or backpack.

(29)

audio quality can be judged by the POLQA algorithm using an ACU R2 test setup.

2.4.10. On-device FTP, HTTP, and Ping Testing

TEMS Investigation 16.3 extended its on-device testing repertoire with the FTP, HTTP, and Ping services, all available on the Sony Xperia Z2 D6503. The benefits of this are manifold. For one thing, an on-device client is sure to get the same QoS as a real-life user, thus capturing the true subscriber experience with greater confidence than a PC-based client. On-device testing also offloads the PC by relieving it of processing tasks that are instead handled by the devices.

2.4.11. On-device POLQA Support on Sony Xperia Z2

D6503

TEMS Investigation 16.3 supports on-device POLQA audio quality measurement on the Sony Xperia Z2 D6503.

2.4.12. Support for VoLTE Testing with Hisilicon Devices

SIP message decoding was implemented for VoLTE-capable Hisilicon devices. RTP metrics (jitter, lost packets rate, relative packet delay) are also obtained – currently for audio only.

2.4.13. New LTE Information Elements

These elements are supported by either or both of Qualcomm and Hisilicon chipset based devices.

• DRX Active Rate • eNodeB Antenna Count

• PDSCH Modulation Distribution TB0, PDSCH Modulation Distribution TB1 • PDSCH RB Allocation Count

• PDSCH TTI Allocation Count

• PSS (Primary Synchronization Signal) Peak Power, PSS Peak Position, PSS Peak Count

(30)

The updating of a number of LTE information elements supported by Qualcomm and Hisilicon chipset based devices was made configurable: the elements are updated either for each new device report or once every second.

2.4.15. New Data and Messaging Events

• FTP Service Command

• Email Receive First Data

• Email Receive Data Transfer Cutoff • Email Send First Data

• Email Send Data Transfer Cutoff • Last FIN (during TCP session) • Last RST (during TCP session) • WAP Activation Request • WAP Page First Data • WAP Page Last Data

2.5. What Was New in TEMS Investigation 16.2

2.5.1. GLS Floating Licenses

GLS (Flexnet) licenses as previously applied to TEMS Investigation were always node-locked, that is, mapped to a particular PC and locked to that machine until returned to the license pool and made available to other users.

(31)

TEMS Investigation 16.2 introduced floating GLS licenses. A floating license is borrowed by a PC for a specific duration, then returned automatically to the license pool unless the user requests an extension.

Floating licenses offer a convenient means to increase license utilization, particularly for features that are typically not in constant use but are needed from time to time. Since they are always returned within a known (and adjustable) period of time if not renewed, floating licenses are also immune to being lost indefinitely if allocated to a device that becomes unavailable for one reason or another.

Node-locked and floating licenses can coexist freely on the same PC. For example, you may want to have your fundamental TEMS Investigation license node-locked, because it will always be needed, while you map a floating license for POLQA whenever you need to do POLQA testing. Please contact your sales representative to obtain the necessary registration credentials for using GLS floating licenses.

2.5.2. New Supplied Device: Sony Xperia Z2 D6503

Sony’s Xperia Z2 D6503 model, introduced as a connectable device in TEMS Investigation 16.1, began to be supplied by Ascom with the 16.2 version.

2.5.3. New Supplied Device: Samsung Galaxy S5

SM-G900P (with ODM Software)

This is Sprint’s Galaxy S5 model with LTE (FDD/TDD) as well as CDMA/EV-DO support. Equipped with Ascom ODM software, it is capable of on-device POLQA.

– LTE 1900 (Band 25), 850 (B26), 2500 TDD (B41) – WCDMA 850 (Band V), 900 (VIII), 1900 (II), 2100 (I) – GSM 850, 900, 1800, 1900

– CDMA 800 (BC0), 1900 (BC14) • Throughput categories:

(32)

2.5.4. New Supplied Device: Samsung Galaxy S5

SM-G900A with ODM Software

The Samsung Galaxy S5 SM-G900A, previously supplied in its commercial version, was also made available with Ascom ODM (on-device

measurement) software. This software enables RAT and band lock without device reboot.

2.5.5. New Connectable Devices: iPhone 6 and

iPhone 6 Plus

Apple’s new iPhone 6 and iPhone 6 Plus models were added as connectable devices in TEMS Investigation 16.2.

2.5.6. New Connectable Device: Samsung Galaxy Avant

SM-G386T with ODM Software

The Galaxy Avant SM-G386T is a VoLTE-capable device used by T-Mobile.

2.5.7. Performance Enhancements

The memory footprint of TEMS Investigation was substantially reduced in this release.

(33)

2.6. What Was New in TEMS Investigation 16.1

2.6.1. New Supplied Devices in This Release

• LG G2 VS980

• Samsung Galaxy Note 3 SM-N900T • Samsung Galaxy S5 SM-G900A • Samsung Galaxy S5 SM-G900F • Samsung Galaxy S5 SM-G900FQ • Samsung Galaxy S5 SM-G900I • Samsung Galaxy S4 Mini SGH-I257 • PCTel SeeGull IBflex

2.6.2. Sony Xperia Z2 D6503

The Xperia Z2 D6503 from Sony is an LTE Category 4 phone spanning a generous set of E-UTRA bands. Equipped with Ascom software, it also boasts an imposing array of control functions.

– LTE 2100 (Band 1), 1900 (B2), 1800 (B3), AWS 1700/2100 (B4), 850 (B5), 2600 (B7), 900 (B8), 700c (B13), 700bc (B17), 800DD (B20) – WCDMA 850 (Band V), 900 (VIII), 1700 (IV), 1900 (II), 2100 (I) – GSM/GPRS/EDGE 850, 900, 1800, 1900

• Throughput categories:

• Real-time control capabilities applicable in TEMS Investigation: – RAT lock (LTE, WCDMA, GSM)

– Band lock (LTE, WCDMA, GSM) – LTE EARFCN/PCI lock

(34)

2.6.3. Samsung Galaxy S5 Connectivity

Samsung Galaxy S5 is an LTE Category 4 phone, handling data speeds of up to 150 Mbit/s DL and 50 Mbit/s UL. Supported frequency bands typically include a large subset of LTE FDD 700 (APT), 800, 850, 900, 1800, 1900, 2100, 2600 MHz and TDD 2300 MHz. The APT band is of particular interest as it has the potential to become an internationally accepted roaming band. At least 17 models of this phone have been launched in various regions of the world. The following are connectable in TEMS Investigation 16.1: SM-G900A*, SM-G900F*, SM-G900FQ*, SM-G900I*, SM-G9009D, SM-G901F*, and GT-I9158V. Those marked with an asterisk (*) are also supplied devices.

2.6.4. Connectivity for New VoLTE-capable Devices

As the Voice over LTE service continues to mature among operators and across markets, we keep enabling more VoLTE-capable devices for use with TEMS Investigation. In the 16.1 release we added the following:

• Samsung Galaxy S4 Mini SGH-I257 (supplied device) • Samsung Galaxy Light SGH-T399

• BenQ F5 • LG G Flex D959 • LG G2 D803

• Motorola Droid Ultra XT1080 • Sharp SG304SH

(35)

2.6.5. Other New Connectable Devices

• Samsung Galaxy S5 Mini SM-G800A

• Netgear Aircard 781S • Pantech UML295

2.6.6. New/Enhanced LTE Information Elements

(Qualcomm)

The following IEs were added to the toolbox for LTE performance analysis. They are based on Qualcomm chipset reporting.

• Specialized block error rates for physical channels PDSCH and PUSCH. These elements are updated once every second.

– Initial BLER: Percentage of first transmission attempts that failed. – Residual BLER: Percentage of transport blocks for which all

transmission attempts failed (block was not successfully delivered). • PUSCH transmission distribution: Distribution of the number of

attempts required to successfully transmit an uplink transport block (including residual “bin” for blocks where all attempts failed).

• Carrier aggregation: CQI extended to secondary carrier (“Wideband CQI”).

In addition, the following existing information elements were extended to Qualcomm devices:

• CQI Periodicity, CQI Report Mode

• DRX Enabled, DRX Inactivity Timer Enabled, DRX On Duration Timer Enabled, DRX Short Cycle Enabled

• MAC DL/UL Handover First/Last Packet Time (2 × 2 IEs), MAC UL PDU Handover Interruption Time

• PDCP UL/DL PDU Handover Interruption Time • PDSCH Resource Block Start

• PUCCH G(i)

• PUSCH Resource Block Start • RACH RNTI

(36)

2.6.8. Qualcomm Logs, Events, and Debug Messages

• Support was added for a number of Qualcomm ICD events related to call

handling, IMS, SIP, and more.

• A new setting was provided for toggling all logs and events on or off in a single action – a convenient feature since these lists may be very long. • An added reset button lets you instantly restore the default settings for

all logs and events (“On”/ “Off”).

• Qualcomm debug messages became possible to monitor in TEMS Investigation for purposes of device troubleshooting. The severity threshold for showing a message can be set at various levels, from “All messages (low)” to “Fatal and above”.

2.6.9. Copying of Configuration Sets in Service Control

Designer

In the Service Control Designer, a copying function was added for configuration sets. It creates a duplicate of the currently displayed configuration set under a new name. This is a handy time-saver whenever you want to start out from and modify a previously defined configuration set.

2.6.10. Support for Virtual Machines

In our GLS licensing system, support was added for running TEMS Investigation on the following virtual machines:

(37)

• Xen

On a virtual machine, TEMS Investigation should primarily be used for replay and analysis, but data collection is also possible as long as performance requirements are modest. Please note that large device arrays should not be used, and that Ascom does not make any guarantees regarding performance on virtual machines.

2.6.11. Other New Features

• On-device POLQA computation was implemented on these devices: – LG G2 VS980

– Samsung Note 3 SM-N900T – Samsung S4 GT-I9506 – Samsung S4 Mini SGH-I257.

• On a number of devices, LTE EARFCN/PCI lock and WCDMA UARFCN/ PSC lock were made applicable from within TEMS Investigation instead of using the TEMS Capability Control app. These include:

– Samsung S4 GT-I9506 – Samsung S4 Mini SGH-I257 – Samsung S5 SM-G900I.

• For smartphones (specifically, all devices built on the Qualcomm MSM8960 chipset), Wi-Fi was offered as an alternative method of connecting to the cellular network, side by side with NDIS and RAS. • The Airplane mode control function was extended to devices not

equipped with an AT port.

• The behavior of TEMS Investigation with respect to User Access Control (UAC) was changed to conform better to the intentions behind this Windows feature. Replay mode functionality is now fully supported regardless of UAC mode, also for non-admin Windows users. This allows staff to analyze logfiles on their regular office PCs no matter what user account rights they have, without having to resort to special test laptops or the like. Device activation and data collection, on the other hand, now always require admin privileges on the PC.

(38)

• “Airplane mode” control function

• Rohde & Schwarz enhancements: scripted scans; CGI data; LTE MIMO scanning

• Strengthened LTE reporting with Hisilicon

• Improved compatibility with TEMS Pocket indoor testing • Full IP sniffing with lower processing load

(39)

(40)

(41)

Chapter 1. Introduction

1. Introduction

This is a quick guide to using TEMS Investigation. It is not intended to be comprehensive but tells how to install the product, configure devices, and use the core functions of the application.

For the full story on all product features and their usage, please consult the

User’s Manual and the rest of the documentation.

Regarding technical support, see the Welcome part, section1.5.

What Do You Want to Do?

• Install TEMS Investigation.

• Install licenses for the product.

• Configure your PC and devices.

• Connect devices to the PC and activate them in TEMS Investigation.

• Run service testing manually.

• Run service testing using a script.

• Record logfiles.

• Load logfiles for analysis.

(42)

solution you are using. Below we describe the download procedure with GLS licensing.

• Ascom will have sent out a welcome email with a download link. When you click that link, you are taken to this login page:

• Click the Password Finder link.

• Enter your email address and press Submit.

• You will now receive another email. In that email, click the text that reads “this link”. On the web page, enter your email address (in lowercase) and your password as instructed.

(43)

Chapter 2. Installing TEMS Investigation

• In the navigation column under Entitlements, click Product List. • In the list of products, select TEMS Investigation.

• On the Product Information screen, click the version you want to download.

• On the Product Download screen, click the download link for the TEMS Investigation PC SW (bottom row in screenshot).

(44)

(45)

Chapter 3. Installing Licenses

3. Installing Licenses

Two different licensing solutions are available for TEMS Investigation 17.2: GLS and Sentinel LDK. GLS is the solution covered below.

When you start TEMS Investigation for the first time, you need to register your PC with GLS. In the process, a device ID is created for your machine. First, this dialog appears:

• Click the GLS License Control Center button.

A window titled License Control Center appears, where the PC identity is displayed in the Device ID field.

You now need to log in to GLS:

• Under Username, enter your email address.

• Under Password, enter the password you were assigned when downloading the TEMS Investigation software.

(46)

• When the message “Registration successful” appears, click Close.

Licenses Required to Use TEMS Investigation

• You must always map the TEMS Investigation base software license. • If you are upgrading from TEMS Investigation 16.x, you need to map the

add-on “TEMS Investigation 16.x to 17.x Upgrade”.

• If you are upgrading from TEMS Investigation 15.x, you need to map the add-on “TEMS Investigation 15.x to 17.x Upgrade”.

• You also need to map:

– Your license options for cellular technologies.

– The license options for the data-collecting devices you will be using. – Any license options required for particular measurements or service

testing (for example, audio quality measurement with POLQA). After completing the license installation, you are ready to start using TEMS Investigation with all functions that you have a license for.

(47)

• A node-locked license is locked to the PC until it is explicitly removed and made available to other users.

• A floating license, by contrast, is automatically returned to the license pool at regular intervals. It can also have an end date configured within GLS.

The two types of license are handled differently in the user interfaces, as detailed below.

Installing Node-locked Licenses

When installing node-locked licenses, you work mostly in the GLS web interface.

• In the GLS interface, in the navigation column under Device Management, click Search Devices.

• In the list of devices, click the ID that represents your PC.

At the bottom of the View Device screen, all licenses (“add-ons”) that you have installed on your PC are listed. The first time around, of course, this list will be empty.

(48)

What you need to do here is to map the full set of add-ons you are going to need when using TEMS Investigation.

• For each add-on, enter the number of add-ons you want to map in the Units to Configure column, then click the Map Add-Ons button. • When you are done mapping add-ons, return to the License Control

Center window (Nodelocked tab) and click the Synchronize button there. The window will then display all the licenses that are now installed on your PC.

Installing Floating Licenses

When installing floating licenses, you work mostly from the License Control Center application, interacting with a license server in GLS.

(49)

However, to this end your PC must have a special add-on called “License Server Access Token” mapped to it. This add-on is mapped to the PC through the GLS user interface, just as described in the preceding section. • Start by mapping the License Server Access Token.

• Then start License Control Center. • Click the Synchronize button.

• Switch to the Floating tab if the window does not already show it. • Click the Select License Server button. A new top section slides in, titled

Select license server instance.

• Click the Add Server button.

• In the Add License Server dialog that appears, enter a valid Instance Identity and Server Alias for the license server. This information will have been provided by your license administrator.

• Click the Add Server button in the Add License Server dialog.

• The license server appears in the list. Double-click this item to connect to the server. The “Select license server instance” section is now hidden, and the entire window fills up with a list of license options.

(50)

• Check the add-ons you want to map to your PC.

• Click the Synchronize button. When asked whether to continue, confirm by clicking Yes.

The validity period for a floating license is between 1 and 10 days, as governed by a setting in GLS. The timer is automatically reset each time TEMS Investigation is restarted, provided that the PC is connected to the Internet.

Available add-ons are tagged with a cloud icon on the left.

Add-ons that are already mapped as node-locked are tagged with a padlock.

The icons for these add-ons change to a download symbol.

Add-ons currently mapped as floating licenses are tagged with a checkmark.

(51)

Chapter 4. Configuring Your PC and Devices

4. Configuring Your PC and

Devices

Given the extremely diverse range of devices that are connectable in TEMS Investigation, it is not possible to summarize both briefly and usefully what preparations are necessary for using devices. Instead, we will pick a number of recent Sony Xperia phones and describe what needs to be done with these. Please refer to the Device Configuration Guide for full coverage of external devices.

Sony Xperia Z5 E6653

For this device you need to install a driver found in a ZIP archive delivered with TEMS Investigation. The driver is stored in the directory Sony\Z5 E6653 within that archive. When prompted, point to that directory.

• After the installation is done, enable tethering on the phone under Settings Wireless & Networks More Tethering & portable hotspot USB Tethering.

Sony Xperia Z3 D6603, Z2 D6503

Same procedure as for the Z5, except that the driver directories are named Sony\Z3 D6603 and Sony\Z2 D6503 respectively.

Sony Xperia V LT25i, Sony Xperia T LT30a

For these devices you need to obtain the driver from Sony PC Companion. • When connecting the phone, you will be presented with the option to

install Sony PC Companion software. Select Install.

• Should this dialog not be displayed, you can enable the option to display Install PC Companion on the phone as follows: Settings Xperia  Connectivity Install PC Companion. In the AutoPlay dialog that appears, Select Run Startme.exe.

(52)

• After the installation is done, enable tethering on the phone under Settings More Tethering & portable hotspot USB Tethering. • In the Device Manager, verify that the item “Sony sa0105 ADB Interface

Driver” appears. See the screenshot below.

• Important: After successfully installing the driver, you should uninstall PC Companion. This is because the PC Companion software might interfere with other devices. Do the uninstall from the Windows Control Panel as usual.

You also need to check that USB debugging is activated, so that all relevant ports are visible.

• Press the Menu button, then choose Settings Applications  Development, and make sure USB debugging is enabled. It should be by default.

(53)

Chapter 5. Connecting and Activating Devices

5. Connecting and Activating

Devices

Starting TEMS Investigation

• First off, before starting TEMS Investigation, plug the external equipment you are going to use into the PC.

You must run the application as administrator. To set this up the first time around, do as follows:

• Navigate to Start  All Programs  Ascom  TEMS Products  TEMS Investigation 17.

• Right-click the TEMS Investigation 17.2 item and choose Properties  Shortcut tab  Advanced.

• Check the Run as administrator option.

From now on, you will run TEMS Investigation as administrator by simply left-clicking the above Start menu item as usual.

TEMS Investigation Launcher

(54)

• If the PC has an Internet connection, the Launcher will connect to an Ascom server and check if there are any newer versions available of TEMS Investigation or other related software. If so, you are notified by a pop-up. Accept and install the updates. If TEMS Investigation itself is updated, the Launcher will shut down, and you then need to start TEMS Investigation once more.

• Click the Launch button to launch the main TEMS Investigation interface with the default workspace.

Detection and Activation of Devices

All devices that you have plugged into the PC and that have been detected by TEMS Investigation are listed in the top pane of the Navigator’s Equipment tab. For example, a Sony Xperia LT25i will appear as follows:

(55)

Chapter 5. Connecting and Activating Devices

• You need to activate a device in TEMS Investigation before you can use it. To this end, right-click the device on the tab shown above, and choose Activate from the context menu.

The red cross disappears from each device icon to indicate that the device is now active.

Before You Start Testing

Here is a short list of device-related matters that you need to have sorted out before you start drive testing with TEMS Investigation. The Device

Configuration Guide covers these topics in abundant detail; we condense them here to a few pieces of general advice:

• Make sure that all external devices have adequate power supply. • Make sure that appropriate drivers are installed for all external devices. • When doing data collection in LTE networks or in other scenarios that

entail a high CPU load, it is strongly recommended for performance reasons to disable non-vital PC functions that consume a lot of processing power, especially visual effects.

If you have several devices, click the Activate All button on the Navigator toolbar to activate all of them.

(56)

cases.

Manual Service Testing

Manual service testing is done from the Navigator’s Equipment tab: specifically, from its bottom pane, which has a “subtab” named Activities. Here are listed all the activities that are supported by the device currently selected at the top of the Equipment tab.

Before you can test a service, you need to define a configuration set telling the device in more detail what to do. The simplest case is voice, where you essentially just have to specify what number to call. We will take voice as an example here:

• Under the Voice node on the Activities tab, right-click the Dial item and choose Configuration Sets.

• In the dialog that appears, create a new configuration by clicking New. • Leave Call Type as-is (“Default”).

(57)

Chapter 6. Testing Services

• Give the configuration a different name if you like. You are now ready to perform voice testing:

• To place a voice call, right-click Dial on the Activities tab, choose Start, then pick the configuration set just created.

• To end the call, right-click Dial and choose Stop.

Data service testing such as FTP or streaming requires some more preparation: you must first connect to a network, and there are more parameters to fill in for the service. However, the general approach is just the same as above.

Testing Services with a Script

Scripts for automated service testing are composed in the Service Control Designer. Here you build script workflows in a graphical user interface. The range of available activities is the same as in manual testing, and the configuration sets you create are used in scripts as well.

Scripts allow you to create advanced testing setups that would be awkward or impossible to manage by operating devices manually. However, in this guide we will again content ourselves with a couple of basic examples.

Example 1: This script instructs the device to dial a call as specified in the configuration set “Voice Call Recipient 1”, then wait 10 seconds before finally hanging up.

(58)

Example 2: Below is a small glimpse of the powerful flow control mecha-nisms that are available in scripts. A branching structure is used, where two devices are placed in parallel. The EQ1 device (left) dials a call, just as in the preceding example. The receiver of this call is the EQ2 device (right), which is controlled by the same script. EQ2 is assigned an answer activity, prompting it to pick up the call when it arrives.

(59)

Chapter 6. Testing Services

Ready-made script building blocks (“snippets”), similar to the one for voice above, are provided in the application for every testable service type.

(60)

It is a good idea to start the recording before you embark on any testing. This ensures that you capture all relevant measurement data in the logfile.

Logfile recording can also be controlled by a script, using special activities named Start Recording and Stop Recording.

Click the Start Recording button on the Record toolbar. A dialog appears where you can do some optional configuration; click OK in this dialog.

After you have completed your testing tasks, click Stop Recording to end the recording and close the logfile. Once you have closed it, you cannot log any more data to the same file.

(61)

Chapter 8. Loading Logfiles for Analysis

8. Loading Logfiles for Analysis

You can load logfiles that you have recorded back into TEMS Investigation in order to analyze them. One logfile at a time can be loaded in the application. To be able to load a logfile, you must put the application in “analysis” mode as opposed to “drive testing” mode. This means that if you have external devices activated, you must first deactivate them:

Logfile loading is most conveniently controlled from the Replay toolbar: Click the Deactivate All button on the Equipment tab toolbar.

Click the Open Logfile button to open a logfile.

Click the Fast Forward button to start loading the logfile data into the presentation windows.

You can click the same button again, now labeled Stop, to halt the loading of the logfile. The data loaded thus far is then displayed in the presentation windows. Click Fast Forward once more to resume logfile loading.

When you are done analyzing a logfile, click the Close Logfile button to close it.

(62)

events, and messages, either in real time or during logfile analysis. Data is presented in essentially the same way in both cases.

A fundamental distinction can be made between two kinds of presentation windows:

• “Snapshot” windows, which show the situation at one instant in time and are constantly refreshed in drive testing mode.

• “History” windows, which accumulate information and encompass the whole testing session or the whole logfile.

All windows are synchronized.

Examples of Snapshot Windows

• Status windows, presenting information elements in tabular form.

• Bar charts, displaying successive snapshots of a selected set of information elements.

(63)

Chapter 9. Data Presentation

Examples of History Windows

• Message windows, listing things like Layer 3 messages and device-specific mode reports, as well as events generated by TEMS Investigation.

(64)

• Map windows, presenting your drive test route graphically on a background map.

(65)

(66)

(67)

Contents

Chapter 1. What’s In This Manual

1 Chapter 2. Licensing: Basics

2 Chapter 3. Product Packaging

3

3.1. Base Software Packages . . . 3 3.2. Replay Packages . . . 4 3.3. Optional Product Features . . . 4 3.3.1. Technology Options. . . 4 3.3.2. External Device Options . . . 4 3.3.2.1. Licensing for Qualcomm Chipset Based Devices . . . 5 3.3.3. Measurement and Service Testing Options . . . 5 3.3.3.1. Available Bandwidth Measurements . . . 5 3.3.3.2. AQM (PESQ/POLQA) . . . 5 3.3.3.3. HTTP Streaming with VQmon . . . 6 3.3.3.4. Iperf with Password Encryption . . . 6 3.3.3.5. ODM (On-device Measurement) . . . 6 3.3.3.6. SFTP (Secure Shell FTP) . . . 6 3.3.4. Reporting Options . . . 7 3.3.5. Logfile Load License Requirements . . . 7 3.4. Accessories . . . 7

Chapter 4. Hardware and Software Requirements

8

4.1. Requirements on TEMS Investigation PC. . . 8 4.1.1. Hardware. . . 8 4.1.2. Operating System . . . 9 4.1.3. Software . . . 10 4.1.4. Running TEMS Investigation on Virtual Machines . . . 11

(68)

4.2.7. VoIP Testing with PC-based Clients . . . 14

Chapter 5. Installing TEMS Investigation

16

5.1. Installation Procedure . . . 16 5.2. Accompanying Utilities . . . 16 5.3. Uninstalling TEMS Investigation . . . 17

Chapter 6. GLS Licensing

18

6.1. Introduction to GLS . . . 18 6.2. Prerequisites . . . 19 6.3. GLS Terminology . . . 19 6.4. Downloading TEMS Investigation Software . . . 19 6.5. Installing TEMS Investigation on Your PC . . . 21 6.6. PC Registration. . . 22 6.7. Installing TEMS Investigation Licenses: General . . . 23 6.7.1. Licenses Required for Application Use . . . 23 6.7.2. Node-locked and Floating Licenses . . . 24 6.7.3. When to Use Which License Type . . . 24 6.8. Installing Node-locked Licenses . . . 25 6.8.1. Returning Node-locked Licenses . . . 27 6.9. Installing Floating Licenses. . . 27 6.9.1. Mapping a License Server Access Token. . . 27 6.9.2. Connecting to a License Server . . . 27 6.9.3. Mapping License Add-ons. . . 28 6.9.4. Expiry and Manual Return of Add-ons . . . 29 6.10. Further Functionality in License Control Center . . . 30 6.10.1. Summary of Currently Mapped Add-ons. . . 30

(69)

Contents

6.11. Notifications in TEMS Investigation. . . 31 6.11.1. License Missing. . . 32 6.11.2. License Expiry . . . 32 6.12. Technical Notes on GLS Add-ons . . . 32 6.13. List of GLS License Add-ons for TEMS Investigation . . . 32 6.14. Creating a PC Alias in the GLS Interface . . . 35 6.15. Searching Contents of Entitlements (“Line Items”) . . . 36 6.16. Searching Mapped Add-ons . . . 37 6.17. Admin Tasks: Setting Up Floating Licenses . . . 38 6.17.1. Creating One or Several License Servers. . . 38 6.17.2. Mapping Add-ons to a License Server . . . 39 6.17.3. Inspecting What Devices Are Being Served by a License

Server . . . 39 6.18. Admin Tasks: Allocation Accounts . . . 39 6.18.1. Introduction to Allocation Accounts . . . 40 6.18.2. Creating a New Allocation Account . . . 40 6.18.3. Switching Between Allocation Accounts . . . 41 6.18.4. Transferring Entitlements Between Allocation Accounts . . . 41 6.18.4.1. Transferring a Whole Entitlement . . . 41 6.18.4.2. Transferring Parts of an Entitlement . . . 42 6.18.5. Using Allocation Accounts to Control User Privileges . . . 42 6.18.6. Moving Devices Between Allocation Accounts . . . 43 6.18.6.1. Node-locked Licenses . . . 43 6.18.6.2. Floating Licenses. . . 43

Chapter 7. Sentinel LDK Licensing

44

7.1. Using Sentinel LDK with TEMS Investigation . . . 44 7.2. Inspecting the Scope of Your Sentinel LDK License. . . 44 7.3. Updating Sentinel HL Keys . . . 47