You are on page 1of 36

TEMS Discovery 23.4.

0 Release Note
Release Note

NT14-30479, 0.1, 12/24/2021 1


Contents

1 About This Release 3

2 Supported Measurement Formats 3

3 Supported OS, SQL and .NET versions 4

4 TEMS Release Alignment Matrix 4

5 Supported Virtual Machines 5

6 Installation And Configuration Notes 5

7 Selected New Features (Summary) 6

8 Selected New Features (Details) 21

9 Corrected Bugs 23.4.0 33

10 Known Bugs and Limitations 34

11 Contact Information 36

2 NT14-30479, 0.1,12/24/2021
1 About This Release
Release date: December 24th 2021

2 Supported Measurement Formats


• TEMS Investigation versions 14.0 up to 23.4
• TEMS Pocket versions 11.0 up to 23.2
• TEMS Director\Analytics versions 1.0 up to 5.3
• TEMS Paragon versions 1.0 up to 5.4
• TEMS Sense versions 1.0 up to 5.3
• TEMS Voyager versions 1.0 up to 2.3.1
• TEMS Data Hub versions 12.0 up to 13.2.1
• TEMS Automatic versions 9.2 up to 12.2.5
• TEMS Symphony Suite up to version 8.1.9
• TEMS Monitor Master trace files up to version 12.3
• NEMO up to file format version 2.46 for selected information elements
• SwissQual up to version 21.2 for selected information elements
• Rohde & Schwarz ROMES up to file format version 21.2 limited to selected
TS995X, GSM_MOBILE, WCDMA_MOBILE, LTE_MOBILE, DQA and
TSMU/TSMW information elements
• JDSU E6474A/RANAdvisor up to file format version 21.0 for selected
information elements
• PCTEL scanner (.dtr) up to file format version 4.3 for selected Line Type Ids
• 5G Qualcomm .dlf and .qraw trace files for standard TEMS information
elements
• LTE Qualcomm .dlf trace files for selected information elements up to revision
AH
• WCDMA/HSPA Qualcomm .dlf trace files for selected information elements up
to revision YC
• GSM Qualcomm .dlf trace files for selected information elements up to revision
P
• CDMA 1x/1xEV-DO Qualcomm .dlf trace files for selected information elements
up to revision YG
• ZK CellTest file format version 6.27 for GSM and WCDMA
• Anritsu scanner regular and short (.dat) format
• CALi FTP and HTTP LTE/WCDMA
• Huawei GENEX GSM text import

NT14-30479, 0.1, 12/24/2021 3


3 Supported OS, SQL and .NET versions
• Microsoft Windows 11 NEW
• Microsoft Windows 10
• Microsoft Windows 8
• Microsoft Windows Server 2019 64 bits (GUI/Desktop Experience mode)
• Microsoft Windows Server 2016 64 bits (GUI/Desktop Experience mode)
• Microsoft Windows Server 2012 R2
• Microsoft SQL Server 2019 Enterprise NEW
• Microsoft SQL Server 2019 Standard
• Microsoft SQL Server 2017 Enterprise
• Microsoft SQL Server 2017 Standard
• Microsoft SQL Server 2012 Enterprise
• Microsoft SQL Server 2012 Standard
• Microsoft .NET Framework 4.8

4 TEMS Release Alignment Matrix


Investigation

Discovery
Director |
Analytics
Paragon

Voyager
Pocket

Sense
TEMS

TEMS

TEMS

TEMS

TEMS

TEMS

TEMS

23.4 23.2 5.4 2.3.1 5.3 5.3 23.4.0 12/24/2021


23.3.1 23.2 5.3.1 2.3.1 5.2.2 5.2 23.3.1 11/25/2021
23.3 23.2 5.3 2.3.1 5.2.1 5.2 23.3.0 11/05/2021
23.2.1 23.2 5.2.1 2.3.1 5.2 5.2 23.2.1 10/01/2021
23.2 23.1 5.2 2.3.1 5.1 5.1 23.2.0 08/13/2021
23.1 23.1 5.1 2.3.1 5.1 5.1 23.1.0 07/16/2021
23.0.1 23.0 5.0 2.3.1 5.0 5.0 23.0.1 04/09/2021
23.0 22.3 5.0 2.3.1 5.0 5.0 23.0.0 03/26/2021
22.3.3 22.3 4.3 2.3.1 4.3.2 4.3.2 22.3.3 04/01/2021
22.3.2 22.2.1 4.3 2.3.1 4.3.1 4.3.2 22.3.1 02/11/2021
22.3 22.2 4.3 2.3.1 4.3.1 4.3.2 22.3.0 12/21/2020
22.2.1 22.2 4.2 2.3.1 4.3 4.3.1 22.2.1 11/20/2020
22.2 22.1.2 4.1.1 2.3.1 4.2.2 4.1 22.2.0 11/03/2020
22.1.4 22.1.1 4.1 2.3.1 4.2 4.1 22.1.4 09/29/2020
22.1.3 22.1 4.1 2.3.1 4.1 4.1 22.1.3 08/19/2020
22.1.1 22.1 4.1 2.3.1 4.1 4.1 22.1.0 06/27/2020
22.0.1 22.0.1 4.0 2.3.1 4.0 4.0 22.0.1 05/15/2020
22.0 22.0 4.0 2.3.1 4.0 4.0 22.0.0 04/03/2020
21.2.4 21.3.1 3.2 2.3.1 3.2.1 3.2.1 21.2.4 02/24/2020
21.2.3 21.3 3.2 2.3.1 3.2 3.2.1 21.2.3 12/31/2019
21.2.2 21.2.2 3.2 2.3.1 3.2 3.2.1 21.2.2 12/06/2019

4 NT14-30479, 0.1,12/24/2021
5 Supported Virtual Machines
• Hyper-V
• WMware
• Xen

6 Installation And Configuration Notes


• To install TEMS Discovery software double click on Setup.exe file.
• TEMS.Core.dll is manipulated for anti-piracy reasons and may be falsely
detected by some antivirus programs as Trojan. It is recommended to explicitly
exclude it from any antivirus program.
• Floating license .lpp license profile path is specified in _td.config file as of TDE
version 12.0.3. If no parameter is defined, default location
C:\ProgramData\TEMS\TEMS Mediator\LicenseControlCenter\LicenseProfiles
will be used.
• During installation SQL collation must be set to
SQL_Latin1_General_CP1_CI_AS.
• ENUx64SQLSysClrTypes.msi and ENUx64SharedManagementObjects.msi will
not be installed automatically if SQL Server and TEMS Discovery Enterprise are
installed in different machines and need to be ran manually (x86 version of msi
files should be installed on 32bit machines).

NT14-30479, 0.1, 12/24/2021 5


7 Selected New Features (Summary)
Data format updates

• TEMS updates
o Support for additional NR measurements:
o NR SDAP throughput (23.4.0)
o NR PDSCH spectral efficiency achieved (23.4.0)
o LTE Rank 3 and 4 (Feedback) percentages (23.4.0)
o NR MR-DC MAC and RLC throughput (23.3.0)
o NR PDCCH grant count DL and UL (23.3.0)
o NR PDSCH and PUSCH slot allocation percentage (23.3.0)
o NR SRS Tx power (23.3.0)
o NR Strongest SSB Beam measurements (23.2.0)
o NR PDSCH physical throughput per CW (23.2.0)
o Google Drive measurements and events (23.2.0)
o NR MR-DC cell measurements (23.1.0)
o NR neighbor cell measurements (23.0.0)
o Cell grouped NR scanner and UE measurements (23.3.0)
o Allows identification of strongest beam scanner measurements per cell
carrier
o Allows for tracking of cell carrier measurements regardless of beam
allocation for UE devices
o Support for additional TEMS events:
o (First) Chunk Downloaded/Uploaded for Dropbox, Google Drive, HTTP and
YouTube (23.3.0)
o NR SA handover events (23.0.0)
o TEMS proprietary ‘Vendor Header’ and ‘Cell Info’ information added to L3
signaling output (23.1.0)
o Integrate TEMS proprietary ‘Vendor Header’ and ‘Cell Info’ (bulk)
information into Script Builder (23.2.1)

• NEMO updates
o Support for NR NAS signaling (23.4.0)
o Support for NR Buffer Status Report (23.3.0)
o Support for NR PUSCH Power Headroom (23.3.0)
o Support for NR PDCP DL and UL throughput per RB (23.0.0)
o Support for NR RLC DL and UL throughput per RB (23.0.0)
o Support for NR MAC DL residual BLER and residual errors (23.0.0)
o Support for NR PDSCH and PUSCH spectral efficiency (23.0.0)
o Support for NR PUSCH and PUCCH pathloss (23.0.0)
o Support for NR PMI (23.0.0)
o Support for NRARFCN DL and UL point A (23.0.0)
o Support for DSS LTE carrier offset and bandwidth (23.0.0)

6 NT14-30479, 0.1,12/24/2021
o Support for Equipment status reporting (23.0.0)

New Analytics Options

• VoNR analytics pack (23.1.0)


o Comprehensive analytics package designed for VoNR service acceptance
and evaluation.
o New VoNR analytics pack includes VoNR_KPIs script delivering all VoNR
relevant events and metrics and built-in ‘VoNR KPI Report’ template
providing ready-made VoNR performance overview.
o Additional speech quality focused events and metrics provided via pre-
defined VoNR_SpeechQuality_KPIs script.
o VoNR events and metrics available in the following categories:
o VoNR call events and metrics
o NR handover
o SRVCC handover to EUTRAN and reselection back to NR
o NR EPS fallback
o NR radio link failures
o NR random access
o NR RRC setup, release and reestablishment
o IMS and 5GC registration
o RTP
o Speech quality
o ‘VoNR KPI Report’ template provides detailed performance overview in the
following categories:
o Accessibility
o Retainability
o Speech quality
o VoNR mobility
o Inter system mobility
o Registration
o NR RRC

NT14-30479, 0.1, 12/24/2021 7


• Enhanced cell configuration scripting options (23.0.0)
o Cell configuration selection added to GetSectorParameter built-in script
function for additional flexibility in custom analytics.
o GetSectorParameter function output previously based on default cell
configuration.
o New function argument allows cell configuration selection by (1) dataset
name matching, (2) cell configuration index and (3) cell configuration name
in addition to the original default cell configuration selection.
o Dataset name matching gives additional flexibility in SSV sector filtering in
automated reporting setups.
o User scripts using GetSectorParameter function should be unselected from
metric import configuration to avoid generating script output before relevant
cell configuration is imported in ADP setup.

8 NT14-30479, 0.1,12/24/2021
• Support for NR neighbor cells added to ‘Spider Move’ option (23.4.0)
o Support for visualization of NR neighbor cells.
o ‘Neighbor’ cell type check box and color selection were added to ‘Sector vs.
Data Point > NR’ tab of ‘Map View Options’.
o NR neighbor cell visualization requires that ‘Spider Move’ 'Use Phone Data'
option to be selected.

• NR Point Details default configurations (23.0.0)


o Pre-defined NR Point Details configurations added for a convenient way of
examining selected measurement data point.
o NR Point Details default Configuration and Tooltip available for selection.
o NR Point Details side table and tooltip window updated for the current
system view data point selection.
o Further customization available through Configuration | Point Detail
Settings.

NT14-30479, 0.1, 12/24/2021 9


New Automation Options

• ADP project-accumulated batch-triggered report generation (23.3.0)


o Automated benchmarking of multiple drive test iterations.
o New ‘Accumulated data’ data grouping option allows users to generate
output for the entire (accumulated) project or dataset selection when
triggered by closure of the most recent batch.
o The use case requires that drive test iterations (batches) are separated by
device attribute filters created automatically by use of distinct drive test
iteration file naming.

• Hide non-serving site and carrier labels in ASC Sector Id coloring (23.2.0)
o Declutter automated sector coloring report output by keeping serving carrier
labels only.

10 NT14-30479, 0.1,12/24/2021
o New ‘Serving/Measured network layer labels only’ option will allow users to
restrict label display to serving/measured network sub-layers when ‘Sector
Id coloring’ is used (applies both to standard and ‘Serving/Measured sectors
only’ sub-options).

• ADP output triggered on file processing completion (23.0.0)


o Increased frequency of automated output generation required by certain
applications.
o New option allows for per file output generation including reporting content,
tabular export, map export, etc.
o Per dataset batch granularity still supported.
o Per file output generation suitable for application requiring
near-real time response (e.g. online dashboards).
o Per log file generated output files will use <Project>_<File
Name>_<MMddyyy>[_<Device>]_<hhmmssfff> naming format.
o New option available in Enterprise ADP setup only.

NT14-30479, 0.1, 12/24/2021 11


• Cell configuration selection by dataset name matching (23.0.0)
o Dataset name matching cell configuration selection for additional flexibility in
automated reporting setups.
o New option allows selection of cell configuration by name matching it with
the selected dataset.
o Name matching selection may be particularly useful in automated SSV
reporting setup when multiple sites are loaded to the same project.
o ADP monitored sub-folder and respective cell configuration names need to
be identical for successful match.

• ADP Tabular Export column order and incidence options (23.0.0)


o Added flexibility in automated tabular export.
o New ADP Tabular Export options were added to allow users to better
control order and rendering of per measurement columns.

12 NT14-30479, 0.1,12/24/2021
o ‘Alphanumerical order’ option will ensure that export columns are sorted by
alphanumerical order of measurement names.
o ‘Alphanumerical order’ option will be unlocked for new configurations only
as sorting method can’t be changed for existing configurations.
o ‘Export available IEs’ option will populate only export columns with
measurements available in the given dataset.

NT14-30479, 0.1, 12/24/2021 13


New Reporting Options

• Map print area modified to include serving sites (23.3.0)


o Provides additional context by ensuring that serving sites are included in
map report output.
o New option controlled through ‘Serving Sites Bounding Rectangle’ check
box
o Enabling the new option will adjust map print area (zoom level) to include
serving sites along with measurement data points.
o Metric added last to ‘Map View’ report element (the key metric) will be used
to determine RAT and measurement device type (UE or scanner) of sector
matching proxy metric.
o ‘Size Change (%)’ number associated with the new ‘Serving Sites Bounding
Rectangle’ option will allow users to increase effective resulting bounding
rectangle size (by specified relative percentage point) for additional buffer
around serving sites.

• Customizable cell configuration pie outline weight and color (23.3.0)


o Added flexibility in cell configuration visualization.
o New option allows customization of sector border color and line weight in
map system view and report output including Automated Sector Coloring.
o Map system view implementation:
o ‘Pie Border Color’ and ‘Pie Border Weight’ settings under 'Cell
Configuration - View Options' Pie tab may be used for customization
of sector border color and line weight in Map system view with user-
defined settings applied and stored per cell configuration.

14 NT14-30479, 0.1,12/24/2021
o Pie border user-defined settings will not be applicable if ‘Render
solid pie’ or manual sector coloring ('Show sector/carrier parameter'
or 'Show sector statistic calculated data based on..' options) are
enabled.
o Pie border color and weight customization will be applied to non-
serving/non-measured network layers only if standard ASC is
enabled (‘Serving/Measured sectors only’ sub-option disabled).
o Pie border color and weight customization will be applied to non-
serving/non-measured sectors only if ‘Serving/Measured sectors
only’ ASC sub-option is enabled.

o Report Builder implementation:


o ‘Pie Border Color’ and ‘Pie Border Weight’ options will be made
available under 'Overwrite cell configuration view settings'
configuration section of Report Builder 'Map View' report type to
allow their customization.
o Pie border user-defined settings will be stored and applied per map
report element.
o Original cell configuration formatting will be reused if 'Overwrite cell
configuration view settings' or its individual options are disabled.
o Pie border user-defined 'Overwrite cell configuration view settings'
configuration will be irrelevant if ASC ‘Render solid pie’ setting is
enabled. Project level 'Render solid pie’ setting will still be applicable
if report element ASC is off.
o Pie border color customization will be irrelevant if ‘Fixed sector
coloring’ or ‘SSV Sector Id coloring’ ASC options are enabled.
o Pie border color and weight customization will only be applied to
non-serving/non-measured network layers if standard ASC is
enabled (‘Serving/Measured sectors only’ sub-option disabled).

NT14-30479, 0.1, 12/24/2021 15


o Pie border color and weight customization will only be applied to
non-serving/non-measured sectors if ‘Serving/Measured sectors
only’ ASC sub-option is enabled.

• Separate map legend image in MS Word and Power Point reporting (23.1.0)
o Added flexibility in MS Word and Power Point reporting layout.
o Existing ‘Independent Image’ map legend option now applicable
to MS Word and Power Point output.
o Map legend image is referred in MS Word or Power Point template
by appending ‘-Legend’ qualifier to Unique ID map reference.
o 'Two Content' slide layout type used in MS Power Point to
arrange map and legend image placement.

16 NT14-30479, 0.1,12/24/2021
• MS Power Point two content top-down layout (23.0.0)
o Added flexibility in MS Power Point reporting layout.
o Previously two content per slide was allowed in left-right layout only.
o New layout option still requires MS Power Point 'Two Content' slide layout
type to be used.
o For top-down 'Two Content’ arrangement an additional ‘:horizontal’ identifier
needs to be added after Unique ID reference.

NT14-30479, 0.1, 12/24/2021 17


System views enhancements

System views enhancements

• Enhanced representation of numerical metrics defined with textual plotband


(23.4.0)
o Plotband textual description used instead of generic numerical values in
'Histogram' and 'Time-series Chart' system views for improved analysis
context.
o New implementation is applicable to metrics using pre-defined and user-
defined plotbands.
o Plotband needs to have all Description fields populated with text.
o Numerical-range and textual-range metrics as well as multiple textual-range
metrics cannot be combined in the same system sub-view.

• Time-series Chart average and maximum value options (23.0.0)


o Average and maximum reference provided to facilitate measurements by
time analysis.
o New average value line and maximum value options added to Time-series
Chart view.
o New options can be turned on and off from ‘View Option’ and ‘View Option
Shortcuts’ selections of Time-series Chart view.
o Average and maximum values calculated over the entire dataset.
o Average and maximum line and font colors automatically adjusted to
respective metric color change.

18 NT14-30479, 0.1,12/24/2021
Enterprise System Enhancements

• Use Private Data Folder as Public Data Folder (23.3.0)


o Enhanced access to TDE FM server data .
o New option allows that TDE Private Data Folder is designated as Public
Data Folder for direct access by remote TDP users.
o The main benefits of the new approach are direct access to Enterprise
server data (no need to setup manual or scheduled transfers of data from
TDE Private Data Folder to Public Data Folder), no need to invest into
additional Public Data Folder storage and no need for periodical Public Data
Folder clean ups.
o Download option will be enabled on remote side only if all data import for
selected hierarchical level (project, dataset, log file) is completed.
o Download initiated on any given hierarchy level will trigger data transfer
attempt for drive test log files of selected hierarchy level, Scenario and UDR
files of the parent DT project and all of the GeoArea files. Download transfer
attempt will be executed if selected item is absent from remote client side or
selected item Windows date/timestamp on the source side is newer than the
one on the remote client side.

NT14-30479, 0.1, 12/24/2021 19


• Added support for MS SQL Server 2019 Standard (23.0.0) and 2019 Enterprise
(23.3.0)

• Added support for MS Windows Server 2019 OS (23.0.0)

Documentation updates

• The latest documentation is available under


http://online.mytemscloud.com/TD/TD_23.4/index.html

20 NT14-30479, 0.1,12/24/2021
8 Selected New Features (Details)
Data format updates

• New TEMS information elements added:


o Data Service Application Layer Downlink (23.1.0)
o UE Application Layer Throughput Downlink (kbps)
o Data Service Application Layer Uplink (23.1.0)
o UE Application Layer Throughput Uplink (kbps)
o GSM Received Signal Level (23.1.0)
o Cell Name
o Cell Name Algorithm
o Cell Distance (m)
o Equipment Status (23.3.0)
o Equipment Battery Temperature (C)
o Equipment Battery Status
o Equipment Status (23.2.1)
o Equipment Thermal Mitigation
o EVS Codec Rate Usage - DL (23.3.0)
o EVS Codec Channel Aware Offset
o LTE Band RSSI Scan (23.4.0)
o Sc RSSI Count
o LTE Resource Blocks (23.0.0)
o PUSCH Resource Block Allocation Carrier 1 (%)
o PUSCH Resource Block Allocation Carrier 2 (%)
o PUSCH Resource Block Allocation Carrier 3 (%)
o PUSCH Resource Block Allocation Carrier 4 (%)
o PUSCH Resource Block Allocation Carrier 5 (%)
o PUSCH Resource Block Start Carrier 1
o PUSCH Resource Block Start Carrier 2
o PUSCH Resource Block Start Carrier 3
o PUSCH Resource Block Start Carrier 4
o PUSCH Resource Block Start Carrier 5
o LTE Cell Scan - All EARFCNs (23.4.0)
o Sc Cell Count Per Carrier
o Sc Cell Count Total
o Sc EARFCN Count
o LTE CQI Summary (23.4.0)
o Rank 3 Feedback Percentage Carrier 1
o Rank 3 Feedback Percentage Carrier 2
o Rank 3 Feedback Percentage Carrier 3
o Rank 3 Feedback Percentage Carrier 4
o Rank 3 Feedback Percentage Carrier 5
o Rank 3 Percentage Carrier 1
o Rank 3 Percentage Carrier 2

NT14-30479, 0.1, 12/24/2021 21


o Rank 3 Percentage Carrier 3
o Rank 3 Percentage Carrier 4
o Rank 3 Percentage Carrier 5
o Rank 4 Feedback Percentage Carrier 1
o Rank 4 Feedback Percentage Carrier 2
o Rank 4 Feedback Percentage Carrier 3
o Rank 4 Feedback Percentage Carrier 4
o Rank 4 Feedback Percentage Carrier 5
o Rank 4 Percentage Carrier 1
o Rank 4 Percentage Carrier 2
o Rank 4 Percentage Carrier 3
o Rank 4 Percentage Carrier 4
o Rank 4 Percentage Carrier 5
o LTE Enhanced Power Scan Setting (23.4.0)
o Enhanced Power Scan Frequencies Count
o MR-DC Cell Measurements (23.1.0)
o MR-DC_Channel_PCI
o MR-DC Cell Channel
o MR-DC Cell PCI
o MR-DC Cell Type
o MR-DC Cell Technology
o MR-DC Cell Band
o MR-DC Cell Name
o MR-DC Cell Distance (m)
o MR-DC Cell RSRP (dBm)
o MR-DC Cell RSRQ (dB)
o MR-DC Cell SINR (dB)
o MR-DC Cell Index
o MR-DC Cell Count
o MR-DC Cell 1 Band
o MR-DC Cell 1 Channel
o MR-DC Cell 1 PCI
o MR-DC Cell 1 RSRP (dBm)
o MR-DC Cell 1 RSRQ (dB)
o MR-DC Cell 1 SINR (dB)
o MR-DC Cell 1 Technology
o MR-DC Cell 1 Type
o MR-DC Cell 2 Band
o MR-DC Cell 2 Channel
o MR-DC Cell 2 PCI
o MR-DC Cell 2 RSRP (dBm)
o MR-DC Cell 2 RSRQ (dB)
o MR-DC Cell 2 SINR (dB)
o MR-DC Cell 2 Technology
o MR-DC Cell 2 Type
o MR-DC Cell 3 Band
o MR-DC Cell 3 Channel
o MR-DC Cell 3 PCI
o MR-DC Cell 3 RSRP (dBm)

22 NT14-30479, 0.1,12/24/2021
o MR-DC Cell 3 RSRQ (dB)
o MR-DC Cell 3 SINR (dB)
o MR-DC Cell 3 Technology
o MR-DC Cell 3 Type
o MR-DC Cell 4 Band
o MR-DC Cell 4 Channel
o MR-DC Cell 4 PCI
o MR-DC Cell 4 RSRP (dBm)
o MR-DC Cell 4 RSRQ (dB)
o MR-DC Cell 4 SINR (dB)
o MR-DC Cell 4 Technology
o MR-DC Cell 4 Type
o MR-DC Cell 5 Band
o MR-DC Cell 5 Channel
o MR-DC Cell 5 PCI
o MR-DC Cell 5 RSRP (dBm)
o MR-DC Cell 5 RSRQ (dB)
o MR-DC Cell 5 SINR (dB)
o MR-DC Cell 5 Technology
o MR-DC Cell 5 Type
o MR-DC Cell 6 Band
o MR-DC Cell 6 Channel
o MR-DC Cell 6 PCI
o MR-DC Cell 6 RSRP (dBm)
o MR-DC Cell 6 RSRQ (dB)
o MR-DC Cell 6 SINR (dB)
o MR-DC Cell 6 Technology
o MR-DC Cell 6 Type
o MR-DC Cell 7 Band
o MR-DC Cell 7 Channel
o MR-DC Cell 7 PCI
o MR-DC Cell 7 RSRP (dBm)
o MR-DC Cell 7 RSRQ (dB)
o MR-DC Cell 7 SINR (dB)
o MR-DC Cell 7 Technology
o MR-DC Cell 7 Type
o MR-DC Cell 8 Band
o MR-DC Cell 8 Channel
o MR-DC Cell 8 PCI
o MR-DC Cell 8 RSRP (dBm)
o MR-DC Cell 8 RSRQ (dB)
o MR-DC Cell 8 SINR (dB)
o MR-DC Cell 8 Technology
o MR-DC Cell 8 Type
o MR-DC Data Radio Bearer (23.3.0)
o LTE DRB RLC DL Throughput (kbps)
o LTE DRB RLC DL Throughput (Mbps)
o LTE DRB RLC UL Throughput (kbps)
o LTE DRB RLC UL Throughput (Mbps)
o MR-DC DRB Logical Channel Group

NT14-30479, 0.1, 12/24/2021 23


o MR-DC MAC DL Throughput Total (kbps)
o MR-DC MAC UL Throughput Total (kbps)
o MR-DC MAC DL Throughput Total (Mbps)
o MR-DC MAC UL Throughput Total (Mbps)
o MR-DC DRB PDCP DL Throughput (Mbps)
o MR-DC DRB PDCP UL Throughput (Mbps)
o MR-DC DRB PDCP DL Throughput Total (Mbps)
o MR-DC DRB PDCP UL Throughput Total (Mbps)
o MR-DC DRB RLC DL Throughput (kbps)
o MR-DC DRB RLC UL Throughput (kbps)
o MR-DC DRB RLC DL Throughput (Mbps)
o MR-DC DRB RLC UL Throughput (Mbps)
o MR-DC DRB RLC DL Throughput Total (kbps)
o MR-DC DRB RLC UL Throughput Total (kbps)
o MR-DC DRB RLC DL Throughput Total (Mbps)
o MR-DC DRB RLC UL Throughput Total (Mbps)
o NR DRB RLC DL Throughput (kbps)
o NR DRB RLC DL Throughput (Mbps)
o NR DRB RLC UL Throughput (kbps)
o NR DRB RLC UL Throughput (Mbps)
o MR-DC Data Radio Bearer (23.1.0)
o MR-DC DRB PDCP DL Throughput (kbps)
o MR-DC DRB PDCP DL Throughput Total (kbps)
o MR-DC DRB PDCP UL Throughput (kbps)
o MR-DC DRB PDCP UL Throughput Total (kbps)
o NR Cell Measurements (23.4.0)
o Serving Cell Time Alignment Timer
o NR Cell Measurements (23.3.0)
o Serving Cell Carrier NRARFCN_CI
o Serving Cell Carrier NRARFCN DL
o Serving Cell Carrier Cell Identity
o Serving Cell Carrier Cell Type
o Serving Cell Carrier RSRP (dBm)
o Serving Cell Carrier RSRQ (dB)
o Serving Cell Carrier SINR (dB)
o Serving Cell RRC Cell Identity (CI Part)
o Serving Cell RRC Cell Identity (gNB Part)
o NR Cell Measurements (23.2.0)
o Strongest SSB Beam Cell Identity
o Strongest SSB Beam Index
o Strongest SSB Beam NRARFCN
o Strongest SSB Beam NRARFCN_CI_BI
o Strongest SSB Beam RSRP (dBm)
o Strongest SSB Beam RSRQ (dB)
o Strongest SSB Beam SINR (dB)
o Strongest SSB Beam Type
o NR Cell Measurements (23.0.0)
o Neighbor Cell NRARFCN_CI_BI

24 NT14-30479, 0.1,12/24/2021
o Neighbor Cell NRARFCN
o Neighbor Cell Identity
o Neighbor Cell SS RSRP (dBm)
o Neighbor Cell SS RSRQ (dB)
o Neighbor Cell SS SINR (dB)
o Neighbor Cell Best Beam Index
o Neighbor Cell Count
o Neighbor Cell <i> Cell Identity, i = 1 to 8
o Neighbor Cell <i> NRARFCN, i = 1 to 8
o Neighbor Cell <i> Best Beam Index, i = 1 to 8
o Neighbor Cell <i> SS RSRP (dBm), i = 1 to 8
o Neighbor Cell <i> SS RSRQ (dB), i = 1 to 8
o Neighbor Cell <i> SS SNR (dB), i = 1 to 8
o NR Cell Scan - All NRARFCNs (23.4.0)
o Sc Cell Count Per Carrier
o Sc Cell Count Total
o Sc NRARFCN Count
o NR Cell Scan - All NRARFCNs (23.3.0)
o Sc Strongest Beam NRARFCN_CI
o Sc Strongest Beam NRARFCN
o Sc Strongest Beam GSCN
o Sc Strongest Beam Cell Identity
o Sc Strongest Beam PSS RP (dBm)
o Sc Strongest Beam PSS RQ (dB)
o Sc Strongest Beam PSS SINR (dB)
o Sc Strongest Beam SSS RP (dBm)
o Sc Strongest Beam SSS RQ (dB)
o Sc Strongest Beam SSS SINR (dB)
o NR Cell Scan - All NRARFCNs (23.2.0)
o Sc TAC
o NR Cell Scan - All NRARFCNs (23.0.0)
o Sc Mobile Country Code
o Sc Mobile Network Code
o Sc RRC Cell Identity
o NR MAC Throughput DL (23.3.0)
o MAC DL Throughput (Mbps)
o MAC DL Scheduled Throughput (Mbps)
o MAC DL Throughput Total (Mbps)
o NR MAC Throughput UL (23.3.0)
o MAC Logical Channel Group
o MAC Power Headroom (dB)
o MAC UL Buffer Size Average (MB)
o MAC UL Throughput (Mbps)
o MAC UL Scheduled Throughput (Mbps)
o MAC UL Throughput Total (Mbps)
o NR Modulation PDSCH (23.4.0)
o PDSCH Spectral Efficiency Achieved CW0 (bit/s/hz)

NT14-30479, 0.1, 12/24/2021 25


o PDSCH Spectral Efficiency Achieved CW1 (bit/s/hz)
o NR PDCCH DCI Format (23.3.0)
o PDCCH Grant Count DL
o PDCCH Grant Count UL
o NR PDCP Throughput DL (23.3.0)
o PDCP DL Throughput (Mbps)
o PDCP DL Throughput Total (Mbps)
o NR PDCP Throughput UL (23.3.0)
o PDCP UL Throughput (Mbps)
o PDCP UL Throughput Total (Mbps)
o NR PDSCH Resource Blocks (23.3.0)
o PDSCH Slot Allocation TDD (%)
o PDSCH Slot Allocation Total (%)
o NR PHY Throughput PDSCH (23.3.0)
o PDSCH Phy Throughput (Mbps)
o PDSCH Phy Throughput CRC OK (Mbps)
o PDSCH Phy Throughput Scheduled (Mbps)
o PDSCH Phy Throughput CW0 (Mbps)
o PDSCH Phy Throughput CW1 (Mbps)
o PDSCH Phy Throughput CRC OK CW0 (Mbps)
o PDSCH Phy Throughput CRC OK CW1 (Mbps)
o PDSCH Phy Throughput Total (Mbps)
o PDSCH Phy Throughput CRC OK Total (Mbps)
o NR Phy Throughput Multi-RAT DL (Mbps
o NR PHY Throughput PDSCH (23.2.0)
o PDSCH Phy Throughput CW0 (kbps)
o PDSCH Phy Throughput CW1 (kbps)
o PDSCH Phy Throughput CRC OK CW0 (kbps)
o PDSCH Phy Throughput CRC OK CW1 (kbps)
o NR PHY Throughput PUSCH (23.3.0)
o PUSCH Phy Throughput (Mbps)
o PUSCH Phy Throughput Scheduled (Mbps)
o PUSCH Phy Throughput New Tx (Mbps)
o PUSCH Phy Throughput Total (Mbps)
o PUSCH Phy Throughput New Tx Total (Mbps)
o NR Phy Throughput Multi-RAT UL (Mbps))
o NR PHY Throughput PUSCH (23.2.0)
o PUSCH Phy Throughput New Tx (kbps)
o PUSCH Phy Throughput New Tx Total (kbps)
o NR PUSCH Resource Blocks (23.3.0)
o PUSCH Slot Allocation TDD (%)
o PUSCH Slot Allocation Total (%)
o NR RLC Throughput DL (23.3.0)
o RLC DL Throughput (Mbps)
o RLC DL Throughput Total (Mbps)
o NR RLC Throughput UL (23.3.0)

26 NT14-30479, 0.1,12/24/2021
o RLC UL Throughput (Mbps)
o RLC UL Throughput Total (Mbps)
o NR SDAP Throughput (23.4.0)
o SDAP DL Throughput Total (kbps)
o SDAP DL Throughput Total (Mbps)
o SDAP UL Throughput Total (kbps)
o SDAP UL Throughput Total (Mbps)
o NR UE Tx Power (23.3.0)
o SRS Tx Power (dBm)
o Social Media (23.2.0)
o Google Drive Download Success Ratio
o Google Drive Operation Success Ratio
o Google Drive Upload Success Ratio
o WCDMA PSC Scanning Sort by Ec/Io - All UARFCNs (23.4.0)
o Sc Cell Count Per Carrier
o Sc Cell Count Total
o Sc UARFCN Count

• New TEMS events added (TEMS_Collectors_Events metric group under


‘.Advanced Metric & Event (Pre-defined)’):
o .Common (23.0.0)
o Serving Cell Changed
o Data FTP (23.0.0)
o FTP Download Session Time
o FTP Upload Session Time
o Data Google Drive (23.2.0)
o Google Drive Operation Attempt
o Google Drive Operation End
o Google Drive Operation Error
o Google Drive Operation Start
o Google Drive Operation Success
o Data Dropbox (23.3.0)
o Dropbox Chunk Downloaded
o Dropbox Chunk Uploaded
o Dropbox First Chunk Downloaded
o Dropbox First Chunk Uploaded
o Data Google Drive (23.3.0)
o Google Drive Chunk Downloaded
o Google Drive Chunk Uploaded
o Google Drive First Chunk Downloaded
o Google Drive First Chunk Uploaded
o Data HTTP (23.3.0)
o HTTP Get Chunk Downloaded
o HTTP Get First Chunk Downloaded
o HTTP Post Chunk Uploaded
o HTTP Post Chunk Uploaded

NT14-30479, 0.1, 12/24/2021 27


o Data Streaming (23.3.0)
o Streaming Advertisement Request
o YouTube Chunk Downloaded
o YouTube First Chunk Downloaded
o YouTube PEVQ-S Chunk Downloaded
o YouTube PEVQ-S First Chunk Downloaded
o Data Streaming (23.2.0)
o Streaming Advertisement End
o Streaming Advertisement Start
o IRAT - Idle (23.4.0)
o Inter-System Cell Reselection To NR
o NR Call (23.4.0)
o Serving Cell EN-DC Not Supported
o Serving Cell EN-DC Supported
o NR Handover (23.0.0)
o NR Inter-frequency Handover
o NR Inter-frequency Handover Attempt
o NR Inter-frequency Handover Failure
o NR Intra-frequency Handover
o NR Intra-frequency Handover Attempt
o NR Intra-frequency Handover Failure

• New TEMS service metrics (TEMS_Service_KPIs metric group under


‘.Advanced Metric & Event (Pre-defined)’):
o HTTP (23.3.0)
o First_DNS_Request_to_HTTP_Get_First_Chunk_Downloaded_ms
o First_DNS_Request_to_HTTP_Post_First_Chunk_Uploaded_ms
o SMS (23.1.0)
o SMS_Over_IMS_Sent_Text
o SMS_Over_IMS_Sent_Destination
o SMS_Over_IMS_Sent_Duration_ms
o SMS_Over_IMS_Sent_SCTS
o SMS_Over_IMS_Sent_Submit_Report_Delay_ms
o SMS_Over_IMS_Sent_Status_Report_Requested
o SMS_Over_IMS_Sent_TP_MR
o SMS_Over_IMS_Sent_Sender_Phone_Number
o SMS_Over_IMS_Sent_Access_Network_Information
o SMS_Over_IMS_Sent_Total_Duration_ms
o SMS_Over_IMS_Received_Text
o SMS_Over_IMS_Received_Service_Status
o SMS_Over_IMS_Received_Source
o SMS_Over_IMS_Received_SCTS
o SMS_Over_IMS_Received_Duration_ms
o SMS_Over_IMS_Received_Sender_Phone_Number
o SMS_Over_IMS_Received_Access_Network_Information

• New NEMO information elements added:

28 NT14-30479, 0.1,12/24/2021
o Equipment Status (23.0.0)
o Equipment Battery Level (%)
o Equipment Battery Temperature (C)
o Equipment Battery Status
o Equipment Device Status
o Equipment Battery Current (A)
o Equipment CPU Usage (%)
o Equipment CPU Temperature (C)
o LTE Cell Info Scanning (23.0.0)
o Sc MBSFN Subframe Ratio (%)
o LTE Serving Cell Identities (23.0.0)
o Primary serving cell MBSFN subframe ratio (%)
o Secondary serving cell MBSFN subframe ratio (%)
o NR AMR Codec Usage (Nemo) (23.3.0)
o Active Codec Set DL
o Active Codec Set UL
o NR Bandwidth Part (23.3.0)
o SSB Periodicity (ms)
o NR Bandwidth Part (23.0.0)
o Cell Type
o SSB Band
o SSB NRARFCN
o PCI
o NR-ARFCN DL point A
o NR-ARFCN UL point A
o DSS LTE Carrier Offset (Hz)
o DSS LTE Carrier Bandwidth
o NR Bandwidth Part Distribution (23.0.0)
o PDSCH BWP Dist Current Count
o PUSCH BWP Dist Current Count
o NR Buffer Status Report (23.3.0)
o BSR Avg (bytes)
o BSR Min (bytes)
o BSR Max (bytes)
o NR Cell Scan - All NRARFCNs (23.0.0)
o Sc Frequency Offset (Hz)
o NR MAC Throughput DL (23.0.0)
o MAC DL BLER Residual (%)
o MAC DL Residual Errors
o NR Modulation PDSCH (23.0.0)
o PDSCH Spectral Efficiency
o PDSCH Max Spectral Efficiency
o NR Modulation PUSCH (23.3.0)
o UL Type
o NR Modulation PUSCH (23.0.0)
o PUSCH Spectral Efficiency

NT14-30479, 0.1, 12/24/2021 29


o PUSCH Max Spectral Efficiency
o NR PDCP Throughput DL (23.0.0, obsoleted in 23.1.0)
o RB ID
o PDCP DL Mode
o PDCP DL RB Type
o PDCP DL Blocks
o PDCP DL Throughput (kbps)
o NR PDCP Throughput UL (23.0.0, obsoleted in 23.1.0)
o RB ID
o PDCP UL Mode
o PDCP UL RB Type
o PDCP UL Blocks
o PDCP UL Throughput (kbps)
o NR PDSCH Resource Blocks (23.0.0)
o PDSCH BWP ID
o NR PHY Throughput PUSCH (23.3.0)
o UL Type
o NR Precoding Matrix Indication (23.0.0)
o Serving Cell Type
o PMI i11 Count
o PMI i12 Count
o PMI i13 Count
o PMI i2 Count
o NR PUSCH Resource Blocks (23.0.0)
o PUSCH BWP ID
o NR RACH Information (23.3.0)
o UL Type
o NR RLC Throughput DL (23.0.0)
o RLC DL Logical Channel Identity
o RLC DL Mode
o RLC DL RB Type
o RLC DL Blocks
o RLC DL BLER
o RLC DL Throughput (kbps)
o NR RLC Throughput UL (23.0.0)
o RLC UL Logical Channel Identity
o RLC UL Mode
o RLC UL RB Type
o RLC UL Blocks
o RLC UL Retransmission Rate
o RLC UL Throughput (kbps)
o NR RRC States (23.0.0)
o Band
o SSB NRARFCN
o PCI
o NR UE Tx Power (23.3.0)

30 NT14-30479, 0.1,12/24/2021
o PUSCH Power Headroom (dB)
o UL Type
o NR UE Tx Power (23.0.0)
o PUCCH Pathloss (dB)
o PUSCH Pathloss (dB)

• New Nemo event-based metrics added (Nemo_Events metric group under


‘.Advanced Metric & Event (Pre-defined)’):
o Data connection failed (23.0.0)
o DAF_iPerf2_cause
o DAF_Viber_cause
o Data disconnect (23.0.0)
o DAD_iPerf2_cause
o DAD_Viber_cause
o Data transfer completed (22.1.0)
o DCOMP_iPerf2_cause
o DCOMP _Viber_cause
o Data transfer request (23.0.0)
o DREQ_Line_operation
o DREQ_Google_Drive_operation
o DREQ_RTT_packet_size
o DREQ_RTT_rate
o DREQ_RTT_timeout
o RACH message (23.0.0)
o RACHSM_RACH grant bytes
o RACHSM_RACH_MSG1_SCS
o RACHSM_TC_RNTI

Metric/event definition updates


• LTE PDCP Throughput DL, LTE PDCP Throughput DL, NR PDCP Throughput DL,
NR PDCP Throughput UL (23.1.0)
o Data frames are no longer populated for TEMS log files, aggregated PDCP
throughput is reported under ‘MR-DC Data Radio Bearer’ data frame
instead
• LTE Resource Blocks - PUSCH (23.0.0)
o Aggregated ‘PUSCH Resource Block Allocation’ and ‘PUSCH Resource
Block Start’ replaced with per carrier reporting for TEMS log file format

Pre-defined script updates

• Version updates:
o Discovery_Events
o Support for auxiliary CSFB scenarios (23.1.0)
o NR_SA_Mobility_and_EPS_Fallback
o NR SA handover reporting correction (23.1.0)

NT14-30479, 0.1, 12/24/2021 31


o RATStateForPlot
o RadioAccessTechnology and MultiRATConnectivityMode reporting updates
(23.1.0)
o TEMS_Service_KPIs
o SMS over IMS event metrics added (23.1.0)
o Added handling for repeated SMS submit attempts
o VoLTE_KPIs
o Improved handling of missing SIP messages in Nemo (23.1.0)

32 NT14-30479, 0.1,12/24/2021
9 Corrected Bugs 23.4.0
o SF00378073: SupportedSRS message details not present in 'LTE RRC UE
Capability' information
o SF00378601: “Frozen” low level SSB Beam RSRP reporting
o SF00379853: "Properties of cell site" option inconsistencies
o SF00383292; PLMN reporting inconsistencies (T-Mobile United States)
o SF00384602: PDCP throughput reporting spikes
o SF00455448: NR RSRQ and RSSI measurements not reported for MTP x60
device
o SF00455554: No warning provide when cell configuration data fails to import
o SF00457968: LTE RRC CI information missing from report output
o SF00459512: VoLTE completed calls reported as failed

NT14-30479, 0.1, 12/24/2021 33


10 Known Bugs and Limitations
• Time-series chart textual y-axis labels will be displayed on a best effort basis. In
case when there is no sufficient space due to limited chart dimensions or use of
multiple sub-views, some of the labels may be omitted. NEW
• ‘ADP output triggered on file processing completion’ option introduced in TD
version 23.0.0 was primarily developed for Enterprise FM setup. In case the
option is used in Enterprise SQL DBM setup, user will need to set output
generation delay sufficiently high to ensure that per file output is not triggered
before DB extraction is completed.
• Windows 7 OS is not supported as of TD version 22.3.3.
• It is recommended that users unselect ‘Equipment Time’ data frame from
custom metric import configurations made prior to 22.1.0 version to avoid
performance degradation and generation of unnecessary high volume
measurement data. Users may also add ‘Equipment Status’ data frame to pre-
22.1.0 custom metric import configurations to enable new device status
measurements.
• Test device measurements based on Altair, Datang, DRT, EMP, iDEN,
TravelPilot, Venture, LG, VIA and Sequans chipsets are not supported as of
version 22.0.0
• Due to an Excel limitation, ‘Remove Map view area if no data’ reporting option
will fail whenever area set for removal includes merged cells. In such case
empty report area will remain in generated report output.
• Due to 3rd party spreadsheet engine limitation, inserted image definition will be
disabled if .xlsx template is saved directly in Report Builder. In case report
template is already saved in Report Builder user may re-open template in Excel,
cut and paste back as picture all of the previously inserted images and save
template directly in Excel to restore images in report output.
• Log files may fail to import on first attempt following installation with
Unity.Exceptions.ResolutionFailedException exception indicated in system log.
The workaround is to reimport log files.
• TDE statistics DB will be disabled after TDE File Mode upgrade from 21.0.x to
21.1.x due to removal of dependency to SQL. User will need to manually enable
statistics and log file DB under Configuration | Options, save the changes and
restart TDE.
• Official support for Microsoft Windows Server 2008 and Microsoft SQL
Enterprise 2008 was discontinued as of TD version 21.0.0.
• Random log files may rarely fail to import with ‘RouteReaderInternalException:
Unable to open logfile: No license to open specified file’ exception. Suggested
workaround is to reimport log file in question.
• Data points may not be fully aligned with GIS layer when covering large area
due to the fact that GIS and online map use different projections and data is
aligned to the latter. This area will be revisited for improvements following major
release 20.0.

34 NT14-30479, 0.1,12/24/2021
• ‘Download TerraServer Image/Maps’ option access is limited to OpenStreetMap
and ‘United States Elevation Data (NED) (10m Resolution)’ data sources due to
GlobalMapper licensing limitations.
• Oracle VirtualBox virtual machines are not supported with GLS licensing.
• Due to updates in internal data mapping all log files imported in version 12.1.0
will need to be re-imported to maintain EcIo reporting in 'WCDMA Cell
Measurements' data frame in versions 12.1.1 and later
• Support for TEMS Pocket and TEMS Automatic MTU .log files was removed in
TD 11.1.5 version. Support for TEMS Investigation.log fles (version 13.x and
older) was removed in TD 10.0.8.
• Starting with version 12.0.3 file reference will be removed from Task Window
after successful import via ADP in order to improve UI responsiveness. All log
files that fail to import will remain in Task Window.
• Support for QMDL data format removed as of TD 11.1.10 version. Users may
convert QMDL file to DLF format before data import.
• Pre-defined metric import configurations are made read only as of TD version
11.1.8. Any customization made to pre-defined metric import configurations
should be saved with user defined name to prevent loss of information.
• Support for obsolete MTU and Pocket logfile formats (LZM, LZZ and TPZ) is
discontinued as of TD 11.1.5 version
• 'Google Earth Standalone' feature removed in 11.1.0 due to incompatibility with
Google earth plugin
• TDManagementConsole feature removed in 11.1.0; ‘Log File Execution
History’, ‘Log File Execution History via SMTP’ and ‘TDE Event Log’ features
may be used instead
• Support for Nokia devices is discontinued as of TD 10.0.8
• ‘TD top menu in Russian’ feature is supported for 64-bit Windows OS only
• Import of WAV files is no longer supported after switching from 32b to 64b
application version
• Report output including scanner data may be populated for non-scanner
devices due to internal data sharing between devices; The workaround is to
deploy device based filtering for non-scanner device.
• TEMS Pocket log files not including IP trace data will generate false Service
setup failure event.
• SR00068616: Report cannot be generated completely if the template was last
saved in Report Template Builder:
The third-party component used by TEMS Discovery 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 window during the import of GIS data may
cause the application to pause GIS data import.
• RAN Tuning Reports may show blank fields if the IEs defined in the reports are
not available from data sources.

NT14-30479, 0.1, 12/24/2021 35


• 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 service
testing are not impacted of this limitation

11 Contact Information
For customer support contact information, please visit our website:
https://www.infovista.com/products/tems-portfolio

36 NT14-30479, 0.1,12/24/2021

You might also like