tems discovery device 10.0.5 release note

8/9/2019 TEMS Discovery Device 10.0.5 Release Note

http://slidepdf.com/reader/full/tems-discovery-device-1005-release-note 1/7

NT14-30479, 0.1, 8/16/2014 1

TEMS Discovery Device 10.0.5

Release Note



2 NT14-30479, 0.1,8/16/2014

Contents

1 About This Release 3

2 Supported Measurement Formats 3

3 Supported Operating Systems 3

4 Selected New Features 4

5 Corrected Bugs (Selected) 6

6 Known Bugs and Limitations 7

7 Contact Information 7



NT14-30479, 0.1, 8/16/2014 3

1 About This Release

Release date: August15th2014

2 Supported Measurement Formats

TEMS Investigation versions 7.0 up to 16.1

TEMS Automatic versions 5.0 up to 10.1

TEMS Pocket versions 6.0 up to 14.1

TEMS Symphony Suite up to version 7.4

TEMS Monitor Master tracefiles up to version 10.1

WCDMA UETR trace support up to Ericsson W14A

LTE UETR trace support up to Ericsson L14A

NEMO up to version 5.2 (file format version 2.14)

JSDU E6474A 16.1

PCTelscanner up to version 3.0.0

CDMA 1x/1xEV-DO 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 version 6.27 for GSM and WCDMA)

Rohde&Schwarz ROMES GSM/WCDMA up to file format version 4.72

Huawei GENEX GSM text import

3 Supported Operating Systems

Microsoft Windows 7

Microsoft Windows 8



4 Important Upgrade Information

TEMS Discovery Device and TEMS Discovery Enterprise – Device Moduleversion 10.0.4 and later contain updated IE’s and Event’s names that aligns

with Ascom data collection probes.

Due to this alignment, customized script and reports based on theTEMS_Collector_Events and TEMS_Service_KPI may need to be updated.

This change may in addition requires TEMS Discovery Enterprise and TEMSDiscovery Device users to re-import log files to ensure data integrity.

Please verify your scripts and reports prior to upgrading to version10.0.4 and later.

The scripts and reports that come with TEMS Discovery Device and andTEMS Discovery Enterprise – Device Module version 10.0.4 and later arealready modified to accommodate for this changes.



NT14-30479, 0.1, 8/16/2014 5

5 Selected New Features

Multi-thread report generation added to reduce processing time

Log file execution history added to evaluate ADP import performance MT Call Setup Time added to frame TA UL CallEvents

Mobile-to-mobile file matching improved to identify missing call attempt on MT side

Blixt engineering report added

New data frames added:

o LTE MAC Config Reason

o LTE MAC Config DL

o LTE MAC Config UL

o LTE MAC Config LC Info

o LTE MAC ConfigeMBMS



6 NT14-30479, 0.1,8/16/2014

6 Corrected Bugs (Selected)

o SR127898:HS UL HICH ACK/NACK metric discrepancies

o SR167115:EARFCN 38100 scanner data not available for Nemo log file

o SR167459: Selected metrics missing in ‘GSM Received Signal Level’ dataframe

o SR167707: Indoor map default print area to include entire map

o SR167981: License picker feature disabled in non-GLS version

o SR168797: ‘System’ metric does not fill up all route on map view

o SR169201: Indoor mapping inconsistencies between TEMS Discovery andTEMS Investigation

o SR169326: Selected metrics missing in ‘LTE Serving Cell Signal Quality’ dataframe for TP 14.1 Lite log f iles

o SR170442: "Enable Qualcomm Timestamp Adjustment" not effective forWCDMA NAS Paging Response message

o SR170454:TEMS Discovery Enterprise start-up issues due to TEMSDiscoveryMonitor and TEMS DiscoveryMain Instance conflict

o SR170843: Mediator fails to return valid GLS-based license in TEMSDiscovery10.0.4

o SR171629:ADP parallel processes do not revive after crash reducing thenumber of active threads

o SR171717: Unable to load the traces UETR and CTR or load the CM bulk files

o SR171969: Discrepancyin dropped calls between Discovery_EventsandTems_Colectors_Eventsdata frames

o SR172017: TCP port conflict for TD10.0.4.1 in Data networking feature

o SR172237:Spider Move feature issues when used with online map

o SR173045: EARFCN decoding issues

o SR174967: CQI decoding issues

o Values of VoLTE KPI user-defined parameters always get replaced with defaultvalue after TDE restart

o LTE physical resource block calculation incorrect at times if number of transportblock info for a given subframe is 3 (rare occasion)



NT14-30479, 0.1, 8/16/2014 7

7 Known Bugs and Limitations

.

TEMS Pocket log files not including IP trace data will generate falseService setup failure event.

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

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

The third-party component used by TEMS Discovery Deviceis not fullycompatible with *.xlsx files. Therefore, it is recommended that the user save areport template with MS Excel.

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

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

If YouTube testing is performed using HTTPS the some data is encrypted andall KPIs can not be calculated

False Call Blocked eventwith type Unknown reported at times

False Call End event instead of Call Dropped event is reported at times whenradio bearer is lost

TEMS Pocket 14.0 and 14.1 logfiles including time based HTTP and FTP

service testing will not generate KPI events. File based HTTP and FTP servicetesting are not impacted of this limitation

8 Contact Information

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

tems discovery device 10.0.5 release note

Documents