TEMS Discovery Data Hub 12.

1 Release
Note

1. About This Release

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

2. Important Information
2.1. Upgrade
To note, is that, to some of the database tables additional information has been added,
hence, if it is required to keep previous imported data, the information has to be moved
from old tables unto the new tables.
A SQL script performing the above task for the default database tables is provided as
part of the installation of the product. If a customized import configuration file has been
used, this is to be considered as a customization, and has to be handled on a case by
case basis.

2.2. Route Reader Version

Route Reader version used for TDDH 12.1 is mainly based upon ‘TEMS Route Reader
12.1.1’.

3. Supported System Software

3.1. Supported Operating System
Microsoft Windows Server 2012 R2

3.2. Supported SQL Server Editions

Microsoft SQL Server 2012 Enterprise Edition
Microsoft SQL Server 2012 Business Intelligence Edition
Microsoft SQL Server 2014 Enterprise Edition
Microsoft SQL Server 2014 Business Intelligence Edition
Microsoft SQL Server 2016 Standard Edition
Microsoft SQL Server 2016 Enterprise Edition

NT16-60064, 0.2, 11/30/2016 1

 4. TEMS Discovery Data Hub 12.1
4.1. New Features

4.1.1. Support for SQL 2016

Support for Microsoft SQL Server 2016, Enterprise Edition and Standard Edition.
Note! For Standard Edition, there is a 16 GB limitation on the maximum utilization of
Tabular memory.

4.1.2. Statistical support for Social Media services performance

indicators
Adding statistical support for social media services.

4.1.2.1. Supported Social Media services

- Dropbox
- Facebook
- Instagram
- Netflix
- Skype
- Twitter
- WhatsApp

4.1.2.2. Social Media Measures

- Logon Attempt Count
- Logon Duration Count/Average/Max/Min
- Logon Failure Ratio/Count
- Logoff Attempt Count
- Logoff Duration Count/Average/Max/Min
- Logoff Failure Ratio/Count
- Operation Attempt Count
- Operation Duration Count/Average/Max/Min
- Operation Failure Ratio/Count
- Operation Average Round Trip Time Count/Average/Max/Min
- Operation Throughput Count/Average/Max/Min

NT16-60064, 0.2, 11/30/2016 2

 4.1.2.3. Social Media Dimensions
- Social Media Operation Type, e.g. Upload Photo, Load Feeds, Post Tweet, etc.
- Social Media Type, i.e. service type, e.g. Dropbox, Facebook, etc.
- Call Client Type, to filter out voice/video call KPI’s for Skype and WhatsApp
from 2G/3G/4G calls
- Streaming Client, to filter out streaming KPI’s for Netflix from Youtube sessions
o Streaming Service Access Time / Failure Ratio, Streaming Video IP
Service Access Time / Failure Ratio, Streaming Reproduction Start
Delay, Streaming Video Play Start Time / Failure Ratio, Streaming Video
Playout Cutoff Ratio, Streaming Session Failure Ratio, Streaming Video
Session Time, Streaming Impairment Free Video Session Ratio,
Streaming Session Average Throughput, Streaming Low Throughput
Event Ratio/Count
- HTTP Browser, to filter out HTTP KPI’s for Dropbox from other HTTP client
sessions
o HTTP DL/UL IP Service Access Time / Failure Ratio, HTTP DL/UL Data
Transfer Time / Cutoff Ratio, HTTP DL/UL Mean Data Rate, HTTP
DL/UL Low Throughput Event, HTTP DL/UL Session Failure Ratio

4.1.3. Result from ‘user defined activities’

‘User defined activities’ was introduced in TEMS Investigation 18.1.
The TDDH 12.1 release now give statistical support for the result from such ‘user
defined activites’ (scripts).

4.1.3.1. Scripting Measures

- Scripting Floating Point Value Count/Average/Max/Min/StdDev
- Scripting String Value Count

4.1.3.2. Scripting Dimensions

- Scripting Floating Point Name
- Scripting Floating point Unit
- Scripting Floating Point Transaction
- Scripting String Name
- Scripting String Value
- Scripting String Transaction

4.1.4. Pre-defined benchmarking report

A table view based benchmarking report that provides a comprehensive set of KPI’s for
voice, HTTP and streaming services, as well as ping (delay) tests.
The report is based upon TDDH statistical (Tabular) database.

NT16-60064, 0.2, 11/30/2016 3

 4.1.5. Call Detail Records
A new license option that is providing database tables structured to support details on
all test calls, as well as data validation is provided.
This is providing a call details both on service KPI’s and RF KPI’s

4.1.6. Additional KPI’s

- Area attribute as dimension
- Phone model as dimension, including support of import of phone model file
through management console. The phone model file is TAC based and can be
created and customized by user
- Group HTTP PrePause Time as dimension
- Group Voice Speech Path Delay
- Updated, Streaming Impairment Free Video Session, is by default having a
minimum duration of 1000 ms to impact the KPI. This minimum duration is
possible to configure

4.1.7. Import of ‘zone’ polygons

If ‘zone’ polygon information is available in log-file, the ‘zone’ polygon will be imported
into the measurement database

4.1.8. User defined statistical database name

It is now possible for the user to name the statistical database during statistical
deployment

4.1.9. Improved M2M matching

Additional check on Call Attempt event for Mobile-to-Mobile matching added.
This will enable M2M matching also when no call script has been executed.

4.1.10. Changed handling of recovered log-files

Previously, recovered log-files has not been imported into TDDH measurement
database.
This have now changed, a recovered log-file will now be imported, however with
processing state ‘recovered’ (‘6’). So recovered log-files will not by default contribute to
statistics. Processing state will be needed to be changed explicitly if recovered files
should contribute to statistics

4.1.11. Handling of log-files with only partial GPS positioning included

For log-files with missing GPS positioning in parts of the files.

NT16-60064, 0.2, 11/30/2016 4

 Previously; Only if last known position and first position when GPS positioning
recovered is available in log-file, an interpolation of positioning for the measurements
will be done.
Now; If enabled (see below) and in addition to above, for log-files where the first part or
the last part of the measurements are not having GPS positioning, measurements with
no position will be given the last known position (if missing in end) or the first valid GPS
position in file (if missing in beginning)

4.2. Corrected Bugs

- TFS 162041: AMR Codec Usage logged from MSM8996 chipset devices
- TFS 171525: Faulty blocked call indication (No Traffic Channel Assignment)
- TFS 156943: Streaming Video Interruption Duration reports wrong duration
- TFS 168718: Streaming Reproduction Cutoff Ratio missing in some trp files
(SR000251568)
- TFS 168980: Faulty dropped call indication after packet cell change failure
(SR000256712)

4.3. Known Bugs and Limitations

- For certain environments, when running statistical deployment wizard, an error
might occur when ‘Perform pre-check’

- It will be possible to ‘bypass’ this with comment out parts of

TEMS.LogfileRouter.DeploymentWizard.exe.xml configuration file [can be found
under [C:\Program Files (x86)\Ascom\TEMS Products\TEMS Discovery Data
Hub\12.1.0\Assemblies], see below (so the parts between <!-- and --> should
be commented out)

NT16-60064, 0.2, 11/30/2016 5

 5. TEMS Discovery Data Hub 12.0.6
5.1. New Features
-

5.2. Corrected Bugs

- SR000250753: High DCR reported
- SR000253260: LTE DL Bandwidth issues
- SR000256289: GSM Rxlev reporting issues
- SR000257349: Missing FTP DL Application Layer Throughput (TP)
- SR000255437: No data available due to tabular data processing failed
- SR000253196: Data (files) fails to import into LogfileStorage for SQL 2014
- SR000257396: Cross joining ‘Area’ table with other services compromise
performance

6. TEMS Discovery Data Hub 12.0.5

6.1. New Features
-

NT16-60064, 0.2, 11/30/2016 6

 6.2. Corrected Bugs
- Call Index is increased in middle of call setup (by Answer activity)

7. TEMS Discovery Data Hub 12.0.4

7.1. New Features
-

7.2. Corrected Bugs

- SR000251838: Dropped call faulty generated on new call
- SR000254394: Missing Video Play Start Time values

8. TEMS Discovery Data Hub 12.0.3

8.1. New Features
-

8.2. Corrected Bugs

- SR000251925: Very long call durations for iPhone
- SR000252219: Call marked as dropped call, when it succeeded
- SR000252571: Technical drop, but not end user affecting
- SR000251586: Youtube streaming, high number of interruptions

9. TEMS Discovery Data Hub 12.0.2

9.1. New Features
-

9.2. Corrected Bugs

Correction made when importing slightly larger IP/Data Services log-files. Deficiency in
code caused timeout during import.

NT16-60064, 0.2, 11/30/2016 7

 10. TEMS Discovery Data Hub 12.0.1
10.1. New Features

10.1.1. Call Setup Time (M2M)

Start trigger for ‘Call Setup Time (M2M)’ KPI has changed from ‘Call Attempt’ (signaling
based) to ‘Dial’ (user triggered call attempt)

10.1.2. Voice Qualifier KPI

Voice Call Qualified Ratio [%], and Voice Call Non-Qualified Count, measures has
been added.
A voice call is not qualified if the call is a blocked call, a dropped call or the call setup
time is above 15 seconds, or non-sustainable (speech quality).
Also a dimension Voice (Call) Qualified is added, where the voice calls can be filtered
upon if qualified or not

10.1.3. ‘Multi Socket Test’ dimension

Dimension to be able to filter upon if a HTTP / HTTP Post service test(s) has been a
single socket or multi socket test has been added

10.1.4. Dimensions, ‘Group Streaming Average Throughput’ and ‘Group

PDP Context Activation Time’
The group dimensions (value ranges) has been added for streaming average
throughput and PDP context activation time

10.1.5. Pre-pause before HTTP services

Indication if pre-pause (‘Wait’ activity) has been executed before HTTP / HTTP Post
service test has been added.
This has been added as event properties to HTTP Start and HTTP Post Start events;
- PrePause : Indicates if ‘Wait’ actitivity has been executed before service
actitivity or not (Boolean)
- PrePauseTime : If PrePause (true), this gives the ‘Wait’ time executed
Note! Only in measurement database, not yet support as statistical dimension

10.1.6. VoLTE Call ID

VoLTE call id has been added as event property to call attempt event (available in
measurement database)

NT16-60064, 0.2, 11/30/2016 8

 10.2. Corrected Bugs
SR000248885/SR000248970 : M2M matching fails when Current Call Index equals
‘null’ (for Dial Start event)
SR000249234 : UE on LTE when call intitiated, but falling off LTE before CSFB call
attempts

11. TEMS Discovery Data Hub 12.0

11.1. New Features

11.1.1. Voice KPI’s

- Speech Quality Non Sustainability measures (in statistics), a speech quality
non-sustainable call is detected if; Two consecutive speech samples (DL-UL or
UL-DL) with MOS below threshold, or two consecutive speech samples in the
same direction (DL-DL or UL-UL) with MOS below threshold, or silence
- Call Setup Time (User) as measures (in statistics), start trigger ‘Dial’ (send
button pushed on UE), same end trigger as Call Setup Time (UE)
- Call Failure Ratio as measure (in statistics), failure ratio for Calls, independent
of the failure has been blocked call or dropped call, i.e. the call has not
successfully been established or completed
- Speech Codec as dimension (in statistics), this dimension can be used both for
filter on speech codec used for all AQM score (POLQA SWB/NB, PESQ)
samples, as well as filter on speech codec used per call (for the entire call, if
changed during the call, it will be indicated as mixed)
- CSFB Target Technology as dimension (in statistics)
- SRVCC Handover Ratio measures (in statistics), percentage of number of calls
where SRVCC handover occurred based upon all calls started as VoLTE calls
- Median value for AQM scores as measure (in statistics)
- IMS Registration Type added as dimension (in statistics), ‘Power Up’ or ‘De-
registration’
- Call Re-established, EUTRAN Reselection Time After CSFB Call, EUTRAN
RRC Connection Release Redirected Attempt/Success/Failure added in default
import configuration file

11.1.2. Streaming Service KPI’s

- Streaming Session HD-Share measures (in statistics), including Full HD-
Resolution dimension, indicates the percentage of sessions that was using full
HD resolution during the whole session
- Streaming Session Average Resolution measures (in statistics), the average
resolution during a session

NT16-60064, 0.2, 11/30/2016 9

 - Streaming Qualified KPI (B3) added as measures and dimension (in statistics),
this KPI, in addition to other streaming impaired KPI, also consider timer
thresholds during the different phases of the streaming session, as well as
interruption thresholds
- Streaming Player Session Time and Streaming Player Session Failure Ratio as
measures (in statistics), KPI’s during ‘Player’ phase
- Streaming Session Average Throughput as measure (in statistics)
- Streaming Service Access (pre-download) Time and Failure Ratio as measures
(in statistics), measured over ‘Player’ phase and video IP service access phase
- Note! Previous Streaming Service Access Time has been renamed to
Streaming Video IP Service Access Time (in statistics)
- Streaming Video IP Service Access Failure measures (in statistics)
- Also, Streaming Player Service IP Access Time / Failure, Streaming Player
Download Data Transfer Time / Failure, Streaming Buffering Time / Streaming
Video Download Data Transfer Failure, Streaming Session Time added in
default import configuration file
- Additional properties in Streaming End event; Video Session Interruption
Number Of, Video Session Interruption Duration (Sum, Max), Clip Length,
Player Size, Video Size, Video Buffer Size, Client IP addess, Client Type,
Streaming Video, [Qualified, HD Resolution, Average Session Resolution]
- Additional properties in DNS Host Name Resolution Time event; DNS Service
Type (Streaming Player / Streaming Video)

11.1.3. (Other) Data KPI’s

- Standard Deviation for User Mean Data Rate measures (in statistics)
- 10 %-ile and 90 %-ile for User Mean Data Rate measures (in statistics) for
HTTP DL/UL
- Time binning for Application Layer Throughput
- Indication if HTTP DL/UL session has been performed as single socket or multi
socket test (as property in HTTP End / HTTP Post End). Note! Populated when
ODM HTTP File Download and File Upload performed (not for PC based
solution or UE WebKit)
- Web Compression Ratio, (as property in HTTP End). Note! Requires that call
script providing expected payload (for static web page, such as e.g. Kepler)

11.1.4. Service Independent KPI’s

- TCP Handshake Time as measure (in statistics), for HTTP and FTP, including
support for First/Other dimension
- PDP Context Activation Time and Failure Ratio as measures (in statistics)
- PDP Context Cutoff Ratio as measures (in statistics)

NT16-60064, 0.2, 11/30/2016 10

 - Attach Time and Failure Ratio as measures (in statistics), including support for
Attach Type dimension

11.1.5. Scanner
- Possibility to group EARFCN’s, UARFCN’s and ARFCN’s to be associated with
specific Operator Names, scanner measures will then be possible to filter
accordingly using current ‘SIM Operator’ dimension (in statistics)
- ARFCN (GSM) dimension (in statistics)

11.1.6. Session Statistics

RF/RAN statistics calculated per session
For LTE;
- CQI, Carrier 1,2,3 (avg, min, max)
- CQI Code Word 0/1 Averaged (avg)
- Rank Indicator, RI (avg, min, max)
- PDSCH MSC0/1, Carrier 1,2,3 (avg, min, max)
- PUSCH MSC (avg, min, max)
- PDSCH Resource Block, Carrier 1,2,3 (avg, min, max)
- PUSCH Resource Blocks (avg, min, max)
- PDCP DL Throughput (avg, min, max)
- PDSCH Phy Throughput (avg, min, max)
- PDSCH Phy Throughput, Carrier 1,2,3 (avg, min, max)
- PUSCH Phy Throughput (avg, min, max)
- PDSCH BLER (avg. min, max)
- PUSCH BLER (avg. min, max)
- PDSCH Resource Block (%), Carrier 1,2,3 (avg, min, max)
- PUSCH Resource Block (%), (avg, min, max)
- Number of handovers (intra-frequency, inter-frequency)
- Modulation TB0 / TB1, QPSK, 16QAM, 64QAM, 256QAM percentage of time
for each modulation
- PDSCH Transmission, Distribution, percentage of each number of
transmissions - 1st Transmission, 1st Retransmission, 2nd Retransmission, 3rd
Retransmission ...
- PUSCH Transmission, Distribution, same as above
- Serving Cell RSRP (avg. min, max)
- Serving Cell RSRQ (avg. min, max)
- Serving Cell RS CINR (avg, min, max)
- Serving Cell RSSI (avg, min, max)

NT16-60064, 0.2, 11/30/2016 11

 - UE TX Power (avg. min, max), also PUCCH, PUSCH, SRS
- RACH Number of Preambles
- RACH Preamble Power when eNode B answered
- Timing Advance (avg)
- Timing Advance (meters) (avg)
- Serving Cell DL Bandwidth (session usage)
- Serving Cell RRC Cell Identity (session usage)

For WCDMA/HSPA;
- HS CQI (average), Carrier 1,2 (PC, 1st 2nd Carrier) (min, max, mean)
- Data Mode DL, GPRS/EGPRS/HSDPA/R99 percentage of time for each mode
- Modulation, Carrier 1,2 QPSK, 16QAM, 64QAM percentage of time for each
modulation
- # of Codes, (max, avg)
- HS-DSCH Throughput Total (min, max, avg)
- HS-DSCH Throughput, Carrier 1,2 (min, max, avg)
- HS-DSCH BLER Residual (avg)
- HS-DSCH DTX Rate, Carrier 1,2 (avg)
- HS-DSCH NACK Rate, Carrier 1,2 (avg)
- HS-DSCH Retransmission Rate (avg)
- HS-SCCH Decoding Success Rate (avg)
- HS-DSCH No of HARQ Processes, Carrier 1,2 (avg)
- Soft Handover, percentage of time in SHO
- HS UL Happy Rate (avg, max)
- HS UL Average Serving Grant (avg)
- HS UL Retransmission Rate (avg)
- HS UL BLER Residual (avg)
- HS UL E-DCH TTI (session usage)
- DL UARFCN (session usage)
- CPICH RSCP (avg,min, max)
- CPICH Ec/No (avg, min, max)
- TX Power (avg, min, max)
- SF UL (session usage)

NT16-60064, 0.2, 11/30/2016 12

 11.1.7. Social Media
Skype, Twitter, WhatsApp, Facebook and Instagram related information added in
default import configuration file.

11.1.8. Handover
Statistical support for Handover From EUTRAN (support for other handover types will
be added in coming releases)
- Handover Failure measures
- Handover Interruption Time (Control Plane) measures
- Handover Interruption Time (User Plane) measures
- Handover Type dimension

11.1.9. RRC Connection

RRC Connection (LTE) related information added:
- RRC Connection Drop with cause values, RF Category and reported RSRP and
RSRQ values
- RRC Connection Re-establishment (successful) with cause values and
response delay
- RRC Connection Setup (Establishment) Failure with cause values, response
delay and RF Category
- For RRC (Connection) Established event, setup delay has been added
- RRC Connection Request events and misc. RRC failure events also added in
default import configuration file.

11.1.10. RF Categorization for Failure Events

A categorization of the RF environment at the time of certain failure events has been
added. The following categories has been defined:
- Handover
- Cell Border
- Low Downlink Coverage
- Neighbor Interference
- Downlink Interference (other)
- Uplink Interference
- Low Uplink Coverage
- Other
Note! That certain thresholds can be adjusted to ‘fine tune’ the categorization for
specific networks.
The failure scenarios supported are accessibility and retainability failures for voice, ftp
DL/UL, and HTTP DL/UL services.

NT16-60064, 0.2, 11/30/2016 13

 11.1.11. Misc
- Added Building Id/Name and provided as hierarchical structure for floorplans

11.1.12. Failure Report

TDDH 12.0 are providing two default Stored Procedures to support Failure Report
feature in TEMS Discovery Dashboard 12.0.
The main part of the information to those store procedures comes from a newly added
event group (database table) in the import configuration – Failure Report Metrics.
The two Stored Procedures are called FailureReport.GetBlockedCallReport and
FailureReport.GetDroppedCallReport.
The FailureReport.GetBlockedCallReport is providing for each Blocked Call;
- Date/Time
- Latitude/Longitude
- Radio Technology
- RF Category (see above)
- Block Type
- CC Cause / RR Cause / MM Cause / EMM Cause
- SIP Response Code / SIP Reason Phrase
- Call Blocked Trigger Delay / CSFB Call Blocked Trigger Delay
- Media Type
- Serving Cell Identity / EARFCN / RSRP / RSRQ / SINR / RSSI / Tx Power
(LTE)
- UARFCN / Best Cell SC / CPICH RSCP / CPICH EcNo / Tx Power (WCDMA)
- Serving Cell Identity / Freq. Band / RxLev / Rx Qual / Tx Power (GSM)

The FailureReport.GetDroppedCallReport is providing for each Dropped Call;

- Date/Time
- Latitude/Longitude
- Radio Technology
- RF Category (see above)
- Drop Type
- CC Cause / RR Cause
- Serving Cell Identity / EARFCN / RSRP / RSRQ / SINR / RSSI / Tx Power
(LTE)
- UARFCN / Best Cell SC / CPICH RSCP / CPICH EcNo / Tx Power (WCDMA)
- Serving Cell Identity / Freq. Band / RxLev / Rx Qual / Tx Power (GSM)

NT16-60064, 0.2, 11/30/2016 14

 11.2. Corrected Bugs
- SR000245716; FTP Download/Upload KPI’s Missing from G928M device
- SR000245526; Related to missing SRVCC handover event
- SR000243980; M2M Matching Data related
- SR000243305; Serving Operator – MNC Incorrectly Displayed
- SR000243294; Service Bearer - Reports Mixed and WCDMA for Phone
Camped on LTE Network

12. TEMS Discovery Data Hub 11.2

12.1. New Features

12.1.1. Mobile-to-Mobile (M2M) Matching

Support for Mobile-to-Mobile (M2M) matching is added, and is enabled by a license
option in TDDH.
 The requirement for M2M matching to work, is;
 ‘TDDH-M2M’ license option is available (part of 11.2 base package)
 A call script has been used during data collection, (i.e. no ‘manual’
calling).
 ‘Own Phone Number’ is defined/available for the applicable devices
used by the data collection probe.
 The matching criteria is fulfilled by looking at the phone numbers – called number
(MO side) and own number (MT side) – and the timing of the call.
 There is a possibility for the user to update a ‘IMSI – Phone Number’ mapping
table, that will be used if no ‘Own Phone Number’ available in log-file (see above).
 Time window on matching the timing of the call is by default 60 seconds (before
and after dial on MO side). Note! The time (search) window can be changed by the
tool administrator.
 It is also possible for the tool administrator to turn off the M2M matching service, (by
default it is on).

12.1.2. Call Setup Time (M2M)

Additional call setup time, calculated only for M2M calls.
The Call Setup Time (M2M) is calculated as, ‘Call Established Time’ (MO side) – ‘Call
Answer Delay’ (MT side), where ‘Call Established Time’ is time from start trigger call
attempt until end trigger ‘Connect’ message (call established), and ‘Call Answer Delay’
is start trigger ‘Alerting’ message and stop trigger ‘Connect’ message.
Statistical support for Call Setup Time (M2M) is provided.

NT16-60064, 0.2, 11/30/2016 15

 12.1.3. Additional M2M related statistical support
 Dimension: Call Domain Path; Provides the possibility to filter voice KPI’s
dependent on combination of call domain for each side of a M2M call. That is, “PS-
PS”, PS-CS”, “CS-CS”, “CSFB-PS”, “CSFB-CSFB”, “CSFB-CS”.
 Dimension: Call System Path; Provides the possibility to filter voice KPI’s
dependent on combination of radio access technology for each side of a M2M call.
That is, “4G-4G”, “4G-3G”, “4G-2G”, “4G-4G CSFB”, “4G CSFB-4G CSFB”, “4G
CSFB-3G”, “4G CSFB-2G”, “3G-3G”, “3G-2G”, “2G-2G”.
 Dimension: Other Logfile Lookup; Supporting use case to provide both log-files in
‘contributing log-files’ download from TEMS Discovery Dashboard.

12.2. Corrected Bugs

 ‘Macro Cell Ingress’ is not aggregated for the correct carrier.
 For Q.850 cause 41, in SIP BYE Request, no Dropped Call is triggered (for VoLTE
calls).
 SR000227282, if no ‘180 Ringing’ (SIP) available, end trigger for ‘Call Setup Time’
will be ‘183 Session Progress’ (SIP) with in-band signalling.
 SR000233863, error in analysis server caused by recovered log-file with future
timestamp

13. TEMS Discovery Data Hub 11.1

13.1. New Features

13.1.1. Support for scanner data

 Import of scanner data in default import configuration file – By default scanner data
is now imported into TEMS Discovery Data Hub.
 Time binning of scanner data – Binning Time is configurable in the Management
Console.
 Statistical support for scanner data – A comprehensive set of different scanner
based measures are supported for LTE, WCDMA and GSM technologies.

13.1.2. In-building (Walk Test)

 Handling of ‘floorplans’ – Floorplans are now imported into the TEMS Discovery
Data Hub database.
 Statistical processing of ‘Walk Test’ data into 2x2 meter geo-bins – In-building /
walk test log-files, (determined by a floorplan included in trp container), are
processed into 2x2 meter geo-bins (parcels)
 Support for ‘Small Cell Indication’ and ‘Macro Ingress’ measures – Two specific in-
building / walk test KPI’s are supported, ‘Small Cell Indication’, which indicates if the

NT16-60064, 0.2, 11/30/2016 16

 serving cell / scanned cell are part of the in-building system or not, and ‘Macro
Ingress’, indicating the interference levels from other (than in-building / small cells)
cells, i.e. ‘macro cells’, onto the in-building cell (small cell).
 Support for ‘Zone’ filtering (dimension) – Buildings and other venues can be divided
into certain areas, so called ‘Zones’ (defined in IB Wave planning tool). TEMS
Discovery Data Hub supports this as an filtering option (dimension).

13.1.3. Voice/ViLTE/VoLTE
 Support for media type filtering (dimension) – Adds possibility to filter (VoLTE) KPI’s
based upon if Video or Audio calls.
 Support for Video Percentage usage – Measure to indicate how much time (in
percentage) calls has been Video calls.
 Information on Call Blocked Type and Cause values for VoLTE calls added – Now,
response code and reason phrase, received from IMS client or IMS server, are
included as Blocked Call Cause information
 Statistical support for Speech Path Delay – Delay measurement on audio path.

13.1.4. Carrier Aggregation

 Possibility to filter on Carrier Aggregation usage, provided as dimension – The
dimension is giving ‘Serving Cell Count’ (number of carriers) averaged over time
during session.

13.1.5. PEVQ-S
 Statistical support for PEVQ-S measure – Quality measure for Streaming Service.
 Note! PEVQ-S has replaced previous streaming audio/video MOS score as quality
measure for Streaming Service.

13.1.6. Additional (other) statistical support

 Statistical support for UE Transmit Power
 Carrier (EARFCN/UARFCN) filter as dimension
 Scrambling Code and PCI as measure (evaluated as used most / most samples)
 Data services ‘Error Cause’ filtering as dimension

13.2. Corrected Bugs

 Setting for SSIS Database: ‘Recovery Model = Full’, causing server to run out of
disk space – changed to ‘Recovery Model = Simple’. (SR000225703)
 Request for SQL Agent Jobs installed when measurement database is created,
caused requirement on SQL Server BI Edition. (SR000224993)
 Rule Engine Jobs runs even if unchecked (not enabled). (SR000224412)

NT16-60064, 0.2, 11/30/2016 17

  Settings in meta.Geobase and Logfile Table has no effect on statistical processing.
(SR000224412)

14. TEMS Discovery Data Hub 11.0.1

14.1. New Features

14.1.1. Support for HASP licensing

Licensing of TEMS Discovery Data Hub can as an option use HASP licenses.
Previously was only GLS licensing supported.

14.2. Corrected Bugs

 Handling of duplicate Streaming End events from TEMS Pocket 15.2 (related to
staitistical processing), (TFS 134724)
 TDDH Data Hub Service Monitor no longer restarts the Data Hub Service
(SR000221284)

15. Known Bugs and Limitations

-

16. Contact Information

Please visit our website at  www.ascom.com/nt/en/index-nt/.
For customer support contact information, see the page
 www.ascom.com/nt/en/index-nt/tems-support.htm.

NT16-60064, 0.2, 11/30/2016 18