TEMS Investigation 17 Training - VPNT

TEMS™ INVESTIGATION 18
1
TEMS INVESTIGATION 18
Module 1: Introduction
2
[ INTRODUCTION]
Objectives
After completing this module you will be able to:

• Describe the general functionalities of TEMS Investigation
• Understand the different licensing solutions available
• Identify the different devices used in TEMS Investigation
3
[ INTRODUCTION ]
WHAT IS TEMS INVESTIGATION?
Data collection and

real-time troubleshooting
On-screen
post-processing
Reporting
4
[ DATA COLLECTION ]
SOURCES OF DATA (1/2)
 TEMS Investigation receives information from a number

of different sources
 Phones and UEs
 Scanners and phone-based scanners
 PC cards and USB modems
 AQM module
 GPS receivers
 Cell definition files
 Logfiles
6
[ DATA COLLECTION ]
SOURCES OF DATA (2/2)

 There are differences between devices
 Phones, Scanners, PC cards, USB
from different vendors and between
modems, and Fixed Wireless
models from the same vendor
 Terminals provides TEMS Investigation
 The correct device license is required on
with information about the Radio Access
the license key to connect a specific
Network
 Connected via USB, serial or Ethernet port*
device
 Auto detection of devices
 Data communication via RAS and NDIS*
7
[ LICENSING ]
LICENSING
 Licensing is based on the HASP technology

 Hardware-based (HASP HL)
 Software-based (HASP SL)
License type based on GLS
 GLS (Global Licensing System)
8
[ LICENSING ]
Global License Server - Concept
Account Members
GLS Account Entitlements
(License Options)
Customer Account
Account Devices
Allocation group 1
Allocation group 2
(Project X)
(Project Y)
9
[ DATA COLLECTION ]
AUTO DETECTION OF EQUIPMENT
 Auto detection of equipment

 Nearly all of the devices that are connectable in TEMS Investigation
are detected and enabled automatically
 Some few devices have to be enabled manually
 Non-verified equipment can be manually added to the auto detection
list via the manual UE configuration utility
 Devices that have been detected by TEMS Investigation

appear in the Equipment Configuration window
Connect and GO!

10
TEMS™ INVESTIGATION 18.X
TEMS Investigation User Interface
[ THE INDUSTRY-LEADING AIR INTERFACE TEST TOOL ]
11
[ TEMS INVESTIGATION USER INTERFACE ]
Objectives
 After completing this module you will be able to:

 Understand the user modes of TEMS Investigation.
 Describe the TEMS Investigation user interface.
 Use predefined workspaces and configure new ones.
 Load maps into your workspace.
 Load cell files into your workspace.
12
TEMS Investigation User Modes
 TEMS Investigation can be run in two different modes:

 Drive testing mode: Information presented on the screen is obtained from
devices connected to the PC and activated in TEMS Investigation. New logfiles
can be recorded in this mode.
 Analysis mode: Information presented on the screen is read from a logfile. This
mode is used for inspection and analysis. This is referred to as Replay mode
previously
 User modes are mutually exclusive.
TEMS Investigation User Interface
 Workspace
 Worksheets
 Navigator
 Toolbars
 Menu Bar
 Status Bar
14
Workspaces and Worksheets
 Workspace is the entity that stores

all windows and settings used in a
working session.
 Only one workspace open at a
time.
 Handled from File and View toolbar
or File menu.
 Worksheets are divisions of the
workspace to manage windows
more smoothly.
 Up to ten worksheets can be active
simultaneously.
 Handled from the Worksheet menu
Navigator
 Allows to setup and manage

your workspace and external
equipment.
 It has the following tabs:

 Equipment tab.
 Menu tab.
 Info Element tab.
 Worksheets tab.
 Logfile tab.
16
Logfile Tab Under Navigator (1/2)
17
Logfile Tab Under Navigator (2/2)
18
Presentation Windows
 Line Charts
 Bar Charts
 Status Windows
 Message Windows
 Event Counter windows
 Map
19
Control Windows
 Service Control Designer

 Service Control Monitor
20
Configuration Windows
 Audio Indications
 Event Definition
 File Transfer
 General
21
Loading Maps
 A GeoSet is a special type

of workspace used for map
layers.
 GeoSets are constructed
using the GeoSet Manager.
 TAB files are used to
construct a GeoSet.
 Once the GeoSet is created
it can be opened as a map
in the Map Window.
22
Loading Cell Files
 Cell Files
 Text format (.cel)*
 XML format (.xml)
 Load cell files using the
General Window
 Add Cell Layer Themes in
the Map Window
 Cell Theme
 Cell Line Theme
 Cell Color Theme
* GSM and UMTS only
23
Cell Files
 Cell Files
 Text format (.cel)*
 XML format (.xml)
 Cell file editor
 C:\Program Files (x86)\Ascom\TEMS Products\TEMS
Investigation 16\XML Schema
Pinpoint Window
•Using IBWave Technology

• Pinpointing can be
1. Manual
2. Predefined
25
TEMS™ INVESTIGATION 18.x
Module 4: Connecting Equipment
26
[ CONNECTING EQUIPMENT ]
Objectives

 Activate/deactive equipment in TEMS Investigation.
 Manually run services and apply control functions.
 View and modify certain properties of devices.
 Use the Manual UE Configuration utility.
27
How to Sony LT25i detectable
 USB Debugging ON
 Settings – Developer Options
 Check USB Debugging
 USB tethering ON
 More…
 Tethering & Portable hotspot
 Check USB tethering
28 TEMS Investigation 16.x

How to Samsung S5 detectable
 USB Debugging ON
 Settings – Developer Options
 Check USB Debugging
 USB tethering ON
 More…
 Tethering & Portable hotspot
 Check USB tethering

Equipment tab of the Navigator
 External devices are automatically

detected and listed in the top pane of
the Navigator’s Equipment tab.
 Each device is represented by a
number “EQ” item.
 You need to activate a device before
you can use it for data collection.
 Activate/Deactivate a detected device
from its context menu (right-clicking it).
 Activate/Deactivate all devices clicking
the Activate All/Deactivate All buttons
on the Equipment tab toolbar.
30
TEMS Investigation 16.x
Running services and applying control functions manually
 Manually run services on a device

from the Activities subtab.
 Manually apply control functions to
a device.
 Right-click specific activity to enable
context menu, then select activity
and associated Configuration Set
where required.
 A Configuration Set defines settings
for a particular activity.
 Configuration Sets created here
can later be used for scripts.
31
Equipment Properties
 You can view and modify certain

properties of devices from TEMS
Investigation.
 Device properties vary by phone
model.
 Right-click the device in the top pane
of Navigator’s Equipment tab and
select “Properties…”
 Click Apply after changing properties
for changes to take effect.
32
Summary
 External devices are automatically detected and listed in the top pane of the
Navigator’s Equipment tab.
 To Activate/Deactivate a detected device, right-click it on the Navigator’s Equipment
tab and choose Activate/Deactivate from the context menu.
 You can Activate/Deactivate all devices by clicking the Activate All/Deactivate All
buttons on the Equipment tab toolbar.
 You can manually run services on a device and apply control functions to it from the
Activities subtab.
 You can view and modify certain properties of devices from TEMS Investigation.
Device properties vary by phone model.
 The Manual UE Configuration utility helps TEMS Investigation recognize a device
that is not detected properly.

Module 5: Service Control Designer and Service Control Monitor
TEMS Investigation 16.x 34

[ SERVICE CONTROL DESIGNER AND SERVICE CONTROL MONITOR ]
Objectives

 Understand how to compose and configure scripts.
 Understand how to validate and run scripts.
 Understand how to save and load scripts and snippets.
35
The Service Control Designer
 The Service Control Designer

window is used to compose service
control workflows (scripts).
 Panes:
 Activity pane
 Workflow pane
 Properties pane
 Configuration Sets pane
36
Composing and configuring scripts (1/13)
 Script that dials single voice calls.

 Add voice call activity to the script.
 Dial box and Properties pane are
tagged with exclamation mark,
activity is not properly configured
yet.
 Define a configuration set for the
Dial activity in the Configuration
Sets pane.
 Properties and Workflow panes are
updated with the configuration data.
 To specify duration of the call we
use the Wait activity.
37
 Drag the Wait activity just below

the voice dial box.
 Set the duration in the Properties
pane.
 Add the Hang Up activity after the
wait.
38
 Setting Up a Network Connection

 Add Network Connect activity to the
script.
 Exclamation marks indicate that
configuration is missing.
Network Connect activity.
 Select the configuration set in the
Properties pane
39
 Setting Up a Data Service activity

(FTP download)
 Add a Network Connect activity and
associate it with an existing
configuration set
 Then add a Network Disconnect
activity at the bottom of the
workflow.
 Insert an FTP Download activity
between the network connect and
disconnect.
FTP Download activity and select it
in the Properties pane.
40
 Explicit PS attach and detach

operations.
 To measure the time taken by these
operations for the purpose of
computing KPIs.
 Add a PS Detach and a PS Attach
activity in that order at the beginning
of a workflow.
41
 Snippets.
 A snippet is fixed sequence of
activities defined as a building block.
 Can be reused, saving time and
effort creating new scripts.
 Predefined snippets for all supported
services are provided.
 Predefined snippets are tailored to
produce all data required for KPI
computation.
 An arbitrary activity sequence can
also be saved as a user-defined
snippet.
42
 Activity properties that control

execution.
 On Failure: Determines what
happens if an activity fails.
 Abort: Used to abort an activity after
a fixed length of time or if a
particular event occurs.
43
 Sequence Activity.
 Defines a sequence of activities as a
unit, allowing it to be treated as
such.
 This activity has no unique
properties.
44
 If-Else Activity.
 Used to split the execution flow into
several branches based on outcome
of previous activity.
 Evaluation of conditions proceeds
from left to right.
 Each branch is constituted by an “if-
else branch” activity.
45
 While Activity.
 Used to repeat a sequence of
activities a predetermined number of
times.
 While loops can be nested
arbitrarily.
46
 Wait Activity.
 The function depends on its position
in the workflow.
 Following a Dial or Video Dial
activity, gives duration to the call.
 Appearing elsewhere, it temporarily
suspends the execution of the
workflow branch where it is located.
 The Duration property governs how
long to wait.
47
 Parallel Activity.
 Causes the workflow to split
unconditionally into two or more
branches (no hard limit).
 Each branch must involve different
devices.
 Each parallel branch is
encapsulated within a Sequence
activity.
 This activity has no unique
properties.
48
 UE Control functionality.
 Control functions accessible from
the Equipment Tab of the Navigator
can be applied in a script as
activities.
 RAT lock and Band lock activities
are more generic than the manual
control functions.
 UE control activity in a script can
only be executed if the target device
is capable of the operation in
question.
49
Validating and Running Scripts (1/5)
 Validating Scripts.
 To ensure a script is syntactically
correct.
 To make sure it does not assign
tasks that you devices don’t support
.
 A non-trivial issue when building
complex scripts.
 Also crucial for UE control
functionality.
 Scripts are automatically validated
when started.
 Can be validated in advance.
50
 Running Scripts – General aspects.

 Scripts can be run from the Service Control Designer or Service Control
Monitor.
 Devices involved in a script execute their assigned activities independently of
one another with the following exceptions:
 When devices engage in a service where they interact.
 When devices are involved in different workflow branches that converge. In
this case, all branches are synchronized before the execution proceeds
past the point of convergence.
 The script will not work properly if the keylock function is activated in any of the
phones.
 It is recommended that you disable IPv6 for all device modems in Windows 7
and Vista.
51
 Running Scripts from the Service

Control Monitor.
 Click the Open Script button to
select your script.
 Click the Run Script button to start
the script.
 Click the Stop Script button to stop
script execution.
 Status tab shows current status for
each device.
 Summary tab shows statistics on
the outcome of each activity type.
52
 Running Scripts from the Service

Control Designer.
 Enter the script menu and choose
Run.
 The Status and Summary tabs
replace the usual contents of the
window.
 Click the Stop Script button to stop
script execution.
 Click the Return to Designer button
to return to the Service Control
Designer window.
53
 Suppressing parts of a script.

 To run only certain parts of a script
and exclude others, you can
disable any individual activity.
 Right-click and deselect
Enabled from the context
menu.
 Change Enable flag to False
in Properties pane.
 Activity currently disabled appears
dimmed in the workflow pane.
54
Saving and Loading Scripts
 To save a script to file, click the Save button on the Service Control
Designer toolbar.
 Extension of the file is .tsc (for TEMS Service Control).
 The Save Script dialog contains the following options:
 Description. Free-text field.
 Format. Standard or Redistributable.
 You can save the script as a snippet.
 You can save the script as an image.
 To open an existing script stored on file, click the Open button on the
Service Control Designer toolbar.
55
Summary (1/2)
 The Service Control Designer window is used to compose service control workflows (scripts).
 The Activity pane is a palette holding all script building blocks: for running services, for
controlling devices, and for executing flow control.
 The Workflow pane is the area where you assemble your script graphically in the form of a
flowchart.
 The Properties pane contains properties of the activity that you are currently working .
 In the Configuration Sets pane you define various entities that can be reused in any script, for
example all the details for accessing a particular FTP server.
 An exclamation mark in the activity box means that the activity is not yet properly configured.
 To give a duration to a call, we need to use the Wait activity.
 A Network Connection is a necessary preparation for running data services.
 Explicit PS attach and PS detach operations are used to measure the time taken by these
operations, particularly for the purpose of computing KPIs.
 A snippet is a fixed sequence of activities that is defined as a building block and can be reused
as such, saving time and effort when creating new scripts.
 The predefined snippets are tailored to produce all data required to compute KPIs. The KPI
computation itself is done using TEMS Discovery.
56
Summary (2/2)
 The Sequence activity formally defines a sequence of activities as a unit, allowing it to be
treated as such.
 An If-Else activity is used to split the execution flow into several branches based on the
outcome of a previous activity.
 While loops are used to repeat a sequence of activities a predetermined number of times.
 The function of the Wait activity depends on its position in the workflow. Following a Dial or
Video Dial activity, gives duration to the call. Appearing elsewhere, temporarily suspends the
execution of the workflow branch where it is located.
 The Parallel activity causes the workflow to split unconditionally into two or more braches, each
of which must involve different devices. There is no hard limit on the number of branches.
 A number of control functions accessible from the Navigator (Equipment tab, bottom part,
Activities tab) can also be applied in a script in the form of activities.
 Before a script is run, it needs to be validated to ensure that it is syntactically correct and does
not assign tasks that your devices do not support.
 You can run a script either from the Service Control Designer or from the Service Control
Monitor.
 To run only certain parts of a script and exclude others, you can disable any individual activity
 Extension of the script file is .tsc (for TEMS Service Control).
57
Module 6: Collecting and Analyzing Data

[ COLLECTING AND ANALYZING DATA ]
Objectives

 Generate logfile recordings in TEMS Investigation.
 Replay logfiles in TEMS Investigation.
 Display Information Elements and Events on the Map window.
59
Recording Logfiles (1/2)
 Logfiles can be recorded in the following ways:

 From the Record toolbar or Logfile menu
 Using keyboard shortcuts. F6
 From within scripts.
 All procedures produce an output file with extension .trp.
 The default naming is in the form of a timestamp:
mmddhhmmss.trp (month, day, hours, minutes,seconds).
 From the Record toolbar, Logfile menu or using keyboard shortcuts
you can Start/Stop a recording, Insert Filemarks.
60
Recording Logfiles (2/2)
 Recording logfiles from within scripts:

 Control activity Start Recording starts a
logfile recording.
 Control activity Stop Recording stops a
logfile recording.
 Logfiles always record data from all
activated devices, not only devices that
participate in the script.
 While recording governed by a script is
ongoing, using the Record toolbar can
still manipulate the recording.

Displaying IEs and Events on the Map window (1/3)
 Presentation layers are used to

present network data on the map.
 Themes are created and added to the
presentation layers.
 Information Element (IE) themes
 Event themes
 Theme Settings are accessed from
the Map window toolbar.
 A set of presentation layers is already
supplied, you can modify them or
create new ones.

 To present information elements,

create “Information Element
Themes” (IE Themes).
 They govern the appearance of
markers plotted on the map in terms
of color, size and shape (symbol).
 Colors, sizes and symbols used in
the map are the default ones, set on
the Info Element tab of the
Navigator.
 To create a new IE theme, select a
layer and click Add Theme.
 To present events, create “Event

Themes”.
 To create a new Event theme, select
the Event layer and click Add
Theme.

The Right-hand Pane of the Map Window
 The Info Tab shows data

represented by a single theme
marker selected on the map
window.
 The Legend tab gives an overview
of presentation themes displaying
full details of theme settings.
 The Graph tab shows basic
statistic data in the form of
histograms for each IE contained
in a group of selected theme
markers.

Summary
 Logfiles can be recorded from the Record toolbar, Logfile menu, using keyboard shortcuts or
from within scripts.
 From the Record toolbar, Logfile menu and using keyboard shortcuts, you can Start/Stop a
recording.
 From within scripts, you use the control activities Start Recording and Stop Recording.
 Presentation layers are used to present network data on the map, themes are created and
added to the presentation layers.
 To present information elements, you create “Information Element Themes” (IE Themes).
 To present events, you create “Event Themes”.
 The right-hand pane of the map window is used to view information from theme markers
selected on the map (IEs, Events, Cells).

Module 7: Reports and Exports

[ REPORTS AND EXPORTS ]
Objectives

 Generate reports in TEMS Investigation.
 Export logfiles in other formats from TEMS Investigation.
68
Generating Logfile Reports (1/8)
 You can generate a report in HTML

format from one or several logfiles
which summarizes the data in the
logfiles.
 Logfiles to be included in the report
must be closed.
 External devices must be deactivated
for the report generation to work
properly.
 Click the Generate Report button on
the Report toolbar to open the report
wizard.
69
 To add logfiles on which to base the

report, click the Add button and
browse for the files.
 Specify a path for the Output directory
or browse for one.
 To assemble the contents of the
report, click the Properties button.
70
 The report can compare information

element values with thresholds.
 A number of thresholds are
predefined but you can also create
your own thresholds.
 On the IE tab select the thresholds
you wish to use
 In the report, it is indicated for each
threshold:
 How many times the value of the IE
has crossed the threshold
 How long the peaks/dips have lasted
on average
71
 The report has a section with event

statistics.
 On the Events tab you choose what
events to include in these statistics.
 Only failure events should be
checked in this step. This is the
default setting.
72
 In the Mobiles tab you select the

external devices whose data you
want to include in the report.
73
 In the Scan Channels tab, you

choose what scan data to present in
the report.
 Settings in this tab are applicable only
if your logfiles contain scan data.
 Define channels to populate the
“Available” box.
 Move items that you wish to present
to the “Selected” box.
74
 In the User Details tab, specify a user

name and a report number to be
printed in the report header.
 You can save the report setup for
future use. A file with extension .rpt is
created.
 To generate the report, click Finish in
the Report Wizard.
75
 Report Contents:
 Header
 Logfile information
 Worst cell indication
 Thresholds
 Events
 Scan data
 Distribution charts for thresholded
parameters
 Distribution charts for scan data (if
any)
76
Exporting Logfiles (1/2)
 Logfiles can be exported in the following

formats from TEMS Investigation:
 Text file
 MapInfo 3.0 (Interchange or Tab format)
 ArcView Shapefile
 Marconi Planet DMS 3.1
 Ethereal
 MDM (CDMA)
 Preparing an Export Order
 From the Logfile menu, select Export
Logfile.
 Click Add.
77
Exporting Logfiles (2/2)
 Specifying the contents of Export

Files.
 Click the Setup button to open a
dialog to specify the IEs to include in
the report.
 You choose each IE separately.
 IEs with arguments are picked one
component at a time.
 The chosen item is exported from all
devices that report it by default.
 Start the export from the Export Logfile
window.
78
Summary
 You can generate a report in HTML format from one or several logfiles which summarizes the
data in the logfiles.
 Logfiles to be included in the report must be closed.
 External devices must be deactivated for the report generation to work properly.
 The report can compare information element values with thresholds. A number of thresholds
are predefined but you can also create your own thresholds.
 You can include event statistics in the report.
 You can generate the report using data from specific devices only.
 You can include scan data in your report if its available in your logfiles.
 You can save the report setup for future use.
 In most cases, you can specify what IEs to export and from what device.
79
General Options
•Meant for Interpolation of

Pinpointing cache size
messages

Recording Options
•Quick Recording
•Enable message count
•Enable time Interval
threshold

SUMMARY

[ SUMMARY ]
SUMMARY
 Data collection and real-time troubleshooting

 Support for a variety of terminals and scanners
 Multi-technology capabilities
 Data collection as well as service testing
 Drive testing and indoor data collection
 On-screen post-processing
 Multiple means of presentation and total flexibility
 Single logfile replay as well as post-processing of multiple logfiles
 Reporting
 HTML based report generator
All in one tool!

LEGAL DISCLAIMER
This document contains specific forward-looking statements, e.g. statements including terms like
“believe”, “expect” or similar expressions. Such forward-looking statements are subject to known and
unknown risks, uncertainties and other factors which may result in a substantial divergence between
the actual results, financial situation, development or performance of Ascom and those explicitly
presumed in these statements.
Against the background of these uncertainties readers should not rely on forward-looking
statements. Ascom assumes no responsibility to update forward-looking statements or adapt them to
future events or developments.

THANK YOU!

TEMS Investigation 17 Training - VPNT

Uploaded by

Copyright:

Available Formats

TEMS Investigation 17 Training - VPNT

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TEMS Investigation 17 Training - VPNT

Uploaded by

Copyright:

Available Formats

TEMS™ INVESTIGATION 18

After completing this module you will be able to:

WHAT IS TEMS INVESTIGATION?

Data collection and

SOURCES OF DATA (1/2)

 TEMS Investigation receives information from a number

SOURCES OF DATA (2/2)

 Licensing is based on the HASP technology

Global License Server - Concept

AUTO DETECTION OF EQUIPMENT

 Auto detection of equipment

 Devices that have been detected by TEMS Investigation

Connect and GO!

[ THE INDUSTRY-LEADING AIR INTERFACE TEST TOOL ]

 After completing this module you will be able to:

TEMS Investigation User Modes

 TEMS Investigation can be run in two different modes:

TEMS Investigation User Interface

Workspaces and Worksheets

 Workspace is the entity that stores

 Allows to setup and manage

 It has the following tabs:

 Service Control Designer

 A GeoSet is a special type

Loading Cell Files

* GSM and UMTS only

•Using IBWave Technology

[ THE INDUSTRY-LEADING AIR INTERFACE TEST TOOL ]

 After completing this module you will be able to:

How to Sony LT25i detectable

28 TEMS Investigation 16.x

How to Samsung S5 detectable

29 TEMS Investigation 16.x

Equipment tab of the Navigator

 External devices are automatically

Running services and applying control functions manually

 Manually run services on a device

 You can view and modify certain

33 TEMS Investigation 16.x

[ THE INDUSTRY-LEADING AIR INTERFACE TEST TOOL ]

TEMS Investigation 16.x 34

 After completing this module you will be able to:

The Service Control Designer

 The Service Control Designer

Composing and configuring scripts (1/13)

 Script that dials single voice calls.

Composing and configuring scripts (2/13)

 Drag the Wait activity just below

Composing and configuring scripts (3/13)

 Setting Up a Network Connection

Composing and configuring scripts (4/13)

 Setting Up a Data Service activity

Composing and configuring scripts (5/13)

 Explicit PS attach and detach

Composing and configuring scripts (6/13)

Composing and configuring scripts (7/13)

 Activity properties that control

Composing and configuring scripts (8/13)

Composing and configuring scripts (9/13)