9/17/2013 1

TEMS Discovery Device 10.0.1

Release Notes

2 9/17/2013

© Ascom. All rights reserved.

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

9/17/2013 3

Contents

1 About This Release 4

2 Supported Measurement Formats 4

3 Selected New Features 5

4 Removed Features 5

5 Corrected Bugs 6

6 Known Bugs and Limitations 7

7 Contact Information 7

4 NT13-21322, 0.2,9/17/2013

1 About This Release

Release Date: September 17th, 2013

2 Supported Measurement Formats

TEMS Investigation versions 7.x, 8.x, 9.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.0, 15.1, 15.2

TEMS Automatic versions 5.x, 6.x, 7.x, 8.x, 9.0, 9.1

TEMS Pocket versions 6.x, 7.x, 8.x, 10.x, 11.x, 12.x, 13.0, 13.1 including TEMS Pocket Lite

TEMS Symphony Suite (QVoice) up to 7.1

TEMS Monitor Master trace files up to version 9.1

WCDMA UETR trace support up to Ericsson W12B-Evo

LTE UETR trace support up to Ericsson L12B

NEMO up to version 5.2 (File format version 2.14)

JSDU E6474A 16.1

PCTel Scanner up to version 3.0.0

CDMA 1x/1xEV Qualcomm trace files up to Version N

WCDMA/HSPA Qualcomm trace files up to Version G

LTE Qualcomm trace files up to Version K

ZK CellTest (File format V6.27 for GSM and WCDMA)

Rohde & Schwarz ROMES GSM/WCDMA up to file format V4.72

Huawei GENEX GSM text import

9/17/2013 5

3 Selected New Features

Support of iPhone

New automated iPhone engineering pack with analysis and reporting functionality.

Support of log files collected from TEMS Investigation 15.1 and 15.2.

Support of Global License Server (GLS)

Support of import of newer version of Atoll XML cell configuration files (SR000121055).

Support of LTE RRC OTA Packet version 3 for Qualcomm chipset-based device.

Added multiple predefined scripts:

o Scanner-based “LTE_Interference_Analysis”: for LTE MOD3, MOD6 and MOD30 PCI collision analyses.

o “Scanner_Top1_Metrics_By_Operators_LTE”: for separating scanner metrics by Operators according to user-defined EARFCN values

o “Get_SIM_Operators”: Automatic filling of Operator attribute according to IMSI information.

o “Populate_Test_Type_Attibutes_for_TA_Single_Call_Log_Files”

Enhancements to “Scanner_Top1_Metrics_By_Operators_GSM” pre-defined script – user can now define up to four frequency blocks for up to six operators.

Added support of a new type of RTP Messages not previously decoded.

4 Removed Features

None.

6 NT13-21322, 0.2,9/17/2013

5 Corrected Bugs

SR000119258 GSM Scanning Metric Issue (band information 1900 instead of 1800, also corrected in TEMS Discovery 4.0.13 build June 13, 2013)

SR000120928: Missing GPS position for PCTel Scanner device for the log files with abnormal starting timestamp.

SR000121858: Low number of samples for system plot

SR000122715: The number of LTE Tracking Area Update not consistent with layer 3 signaling for some log files.

SR000123305: Wrong GPX export in TEMS Discovery Device 10.0.

SR000124639: TEMS Discovery Professional 4.0.12 lost some sample counts during data imported.

SR000124940: Missing GSM Scanner Data.

Handling of abnormal EVDO Rx Tx Power values recorded in certain Qualcomm chipset based device.

9/17/2013 7

6 Known Bugs and Limitations

.

Certain log files created by TEMS Pocket 12.3 are corrupt and cannot be imported by TEMS Discovery Device. Users should upgrade to TEMS Pocket 12.4 and recollect the data.

Qualcomm LTE traces stored in QMD log files may not contain data for all LTE subframes so the throughput values calculated may not be correctly. It is strongly recommended to direct use “LTE Throughput from Data Collectors” for QMD log files

SR 68616: Report cannot be generated completely if the template was last saved in Report Template Builder:

The third-party component used by TEMS Discovery Device is not fully compatible with *.xlsx files. Therefore, it is recommended that the user save a report template with MS Excel.

Attempt of resizing TEMS Discovery Device window during the import of GIS data may cause the application to pause the GIS data import.

RAN Tuning Reports may show blank fields if the IEs defined in the reports are not available from data sources.

7 Contact Information

For customer support contact information, please visit our website: www.ascom.com/networktesting