TEMS™ SERVICE CONTROL SCRIPT DESIGNER

This manual is provided by Ascom Network Testing AB without any kind of

warranty. Improvements and changes in this description due to typographical
errors or inaccuracies in current information, or improvements to programs
and/or equipment may be made by Ascom Network Testing AB at any time
without notice. These changes will, however, be incorporated into new
editions of this manual.
No part of this publication may be reproduced, transmitted, stored in a
retrieval system, nor translated into any human or computer language, in any
form or by any means, electronic, mechanical, magnetic, optical, chemical,
manual or otherwise, without the prior written permission of the copyrighted
owner, Ascom Network Testing AB.
TEMS is a trademark of Ascom.
All other trademarks are the property of their respective holders.

© Ascom 2014. All rights reserved.

Document number: NT12-10833 ver 4.0

 Contents

Contents

1. Introduction 1
1.1. Scope of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2. Fundamentals of TEMS Service Control Script Designer . . . . . . . . . 1
1.3. Supported Activities by TEMS Product . . . . . . . . . . . . . . . . . . . . . . . 2

2. Tutorial 4
2.1. User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Basics of Creating Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Setting Up a Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4. Setting Up a Data Service Activity. . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5. Stand-alone PS Attach and Detach. . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6. Snippets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.7. Script Control Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.7.1. Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.7.2. If–Else Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7.3. While Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.4. Parallel Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.7.4.1. Example: Concurrent Activities on the Same Device 17
2.7.5. Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.7.6. Wait For . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.7.6.1. Waiting For a Scheduled Point in Time . . . . . . . . . . . 19
2.7.6.2. Waiting For a Given Outcome of an Activity . . . . . . . 20
2.7.7. Terminate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.8. Editing Scripts and Script Settings . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.9. Activity Properties That Control Execution . . . . . . . . . . . . . . . . . . . 23
2.10. Control Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.11. Validation of Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.12. Suppressing Parts of a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

NT12-10833 ver 4.0 i

TEMS Service Control Script Designer User’s Manual

3. Activities (Reference Chapter) 26

3.1. Control Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.1. AT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.2. Band Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.3. Channel Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.4. Filemark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.5. Radio Access Technology Lock. . . . . . . . . . . . . . . . . . . . . . 27
3.1.6. Start Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.7. Stop Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2. Control Flow Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.1. If–Else . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.2. While . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.3. Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.4. Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.5. Configuration Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.6. Measurement Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.7. Synchronized Call Sequence. . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.8. Terminate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.9. Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.10. Wait For . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3. IP Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.1. Network Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.2. Network Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.3. PS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.4. PS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.5. Start IP Sniffing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.6. Stop IP Sniffing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.7. FTP Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.8. FTP Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.3.9. HTTP Get. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.3.10. HTTP Post . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.3.11. Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.12. Network Bandwidth (Iperf Testing). . . . . . . . . . . . . . . . . . . 45
3.3.12.1. Recommendations for Iperf Testing . . . . . . . . . . . . 46
3.3.12.2. Setting up Multiple Iperf Servers . . . . . . . . . . . . . . . 47
3.3.13. Predefined Snippets for IP . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.4. Messaging Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4.1. Email Send. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4.2. Email Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4.3. MMS Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.4.4. MMS Receive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

ii
 Contents

3.4.5. SMS Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.4.6. SMS Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.4.7. Predefined Snippets for Messaging . . . . . . . . . . . . . . . . . . . 52
3.5. Scan Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.5.1. Predefined Snippets for Scanning . . . . . . . . . . . . . . . . . . . . 53
3.6. Video Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.6.1. Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.7. Voice Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.7.1. Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.7.2. Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.7.3. Hang Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.7.4. Voice Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.7.5. Predefined Snippets for Voice . . . . . . . . . . . . . . . . . . . . . . . 57
3.7.5.1. Synchronized Voice Call Sequence Snippet . . . . . . . 58
3.8. General Activity Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.8.1. Activity Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.8.2. Failure Handling Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.9. Configuration Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4. Saving and Sharing Scripts 62

4.1. Saving a Script to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1.1. Tutorial on Porting Scripts between PCs . . . . . . . . . . . . . . . 62
4.2. Saving a Script as an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5. Further Functionality in the TEMS Service Control

Script Designer 64
5.1. Context Menu in Workflow Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.2. Zooming the Workflow Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

6. GSM Scanning 65
6.1. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.1.1. Setup of RSSI Scan: General Settings. . . . . . . . . . . . . . . . . 65
6.1.2. Setup of RSSI Scan: PCTel . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.2. Spectrum Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.2.1. Setup of Spectrum Analysis Scan . . . . . . . . . . . . . . . . . . . . 66
6.2.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.2.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

NT12-10833 ver 4.0 iii

TEMS Service Control Script Designer User’s Manual

7. WCDMA Scanning 68
7.1. Pilot Scanning (with SCH Scanning). . . . . . . . . . . . . . . . . . . . . . . . 68
7.1.1. Setup of Pilot Scan: General . . . . . . . . . . . . . . . . . . . . . . . . 68
7.1.2. Setup of Pilot Scan: PCTel . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.2. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.2.1. Setup of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.2.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.2.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.3. Spectrum Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.3.1. Setup of Spectrum Analysis Scan . . . . . . . . . . . . . . . . . . . . 71
7.3.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.3.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

8. LTE Scanning 73
8.1. LTE Signal Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8.1.1. Setup of LTE Signal Scan: General . . . . . . . . . . . . . . . . . . . 73
8.1.2. Setup of LTE Signal Scan: PCTel . . . . . . . . . . . . . . . . . . . . 73
8.2. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.2.1. Setup of RSSI Scan: General . . . . . . . . . . . . . . . . . . . . . . . 75
8.2.2. Setup of RSSI Scan: PCTel . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.3. Spectrum Scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.3.1. Setup of Spectrum Scan: General . . . . . . . . . . . . . . . . . . . . 76
8.3.2. Setup of Spectrum Scan: PCTel . . . . . . . . . . . . . . . . . . . . . 76
8.4. Enhanced Power Scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
8.4.1. Setup of Enhanced Power Scan: General . . . . . . . . . . . . . . 76
8.4.2. Setup of Enhanced Power Scan: PCTel . . . . . . . . . . . . . . . 77

Index 79

iv
 Chapter 1. Introduction

1. Introduction

1.1. Scope of This Document

This document describes the TEMS Service Control Script Designer tool
contained in TEMS Automatic 10.1 and TEMS Symphony 7.4.1

1.2. Fundamentals of TEMS Service Control

Script Designer
The TEMS Service Control Script Designer tool (“Service Control Designer”
for short) is used to create workflow scripts. In TEMS Automatic, a workflow
script is referenced in an action which is part of a work order sent to an RTU.
In TEMS Symphony, scripts are assigned as-is to measurement devices.
Very briefly summarized, service testing has the following scope:
• Circuit-switched voice calls are supported.
• Data service testing encompasses the following services and protocols:
email, FTP, HTTP, Ping, Network Bandwidth (TCP and UDP testing
towards Iperf server), video streaming, SMS, and MMS. For differences
between TEMS Automatic and TEMS Symphony, see section 1.3.
• Scanning can be scripted for PCTel EX/EXflex and MX scanners.

Special activities are available:

• for recording data in logfiles
• for applying various control functions to devices, such as RAT lock and
band lock
• for AT commands.

1. The Service Control Designer in TEMS Investigation is similar but not

identical; for a description of the latter, please refer to TEMS Investigation
documentation.

NT12-10833 ver 4.0 1

TEMS Service Control Script Designer – User’s Manual

1.3. Supported Activities by TEMS Product

The table that follows details activities supported by the TEMS
Automatic 10.1 and TEMS Symphony 7.4 software. The precise range of
activities supported by individual hardware devices used in these products
may differ from what is stated here.
At the TEMS product software level, support for all of these activities is RAT-
independent, wherever it exists.

TEMS TEMS
Service Control Activity Automatic Symphony
10.1 7.4
Control activities
AT  
Band Lock  
Channel Lock1 
Filemark 
Radio Access Technology Lock  
Start/Stop Recording2 
Control Flow activities
Configuration Sequence 
If–Else  
Measurement Sequence 
Parallel  
Sequence  
Synchronized Call Sequence  
Terminate  
Wait  
Wait For  
While  
IP activities
FTP Download/Upload  
HTTP Get/Post with TEMS browser  

2
 Chapter 1. Introduction

TEMS TEMS
Service Control Activity Automatic Symphony
10.1 7.4
HTTP Get/Post with Internet Explorer  
Network Bandwidth (Iperf): TCP 
Network Bandwidth (Iperf): UDP  
Network Connect/Disconnect  
Ping  
PS Attach/Detach 
Start/Stop IP Sniffing  
Messaging activities
Email Send/Receive  
MMS Send/Receive 
SMS Send/Receive 
Scan activities (all)  
Video activities
Streaming over HTTP (and TCP)  
Other video activities
Voice activities (all)3  
1. Present in TEMS Symphony user interface, but not supported by any
device in TEMS Symphony 7.4.
2. Logfile recording in TEMS Automatic cannot be controlled in this way.
3. Only circuit-switched supported in TEMS Automatic 10.1 and TEMS
Symphony 7.4, not VoIP.

NT12-10833 ver 4.0 3

TEMS Service Control Script Designer – User’s Manual

2. Tutorial

2.1. User Interface

The TEMS Service Control Script Designer user interface has the following
design:

• The Activity pane is a palette holding all script building blocks: for
running services, for controlling devices, and for execution 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 with (the one currently selected in the Workflow pane).

4
 Chapter 2. Tutorial

• In the Configuration Sets pane you define various entities that can be
reused in any script, for example all the details of accessing a particular
FTP server.
In the Properties and Configuration Sets panes, items can either be grouped
into categories or be listed in alphabetical order; use the buttons at the top to
toggle between the two display modes. At the bottom of each pane is a box
showing an explanation for the item currently selected.
The rest of this chapter is organized as follows. First comes a hands-on
tutorial on how to build and run scripts, with numerous screenshots and
examples (sections 2.2–2.12). Then follows a reference part cataloging all
script activity types with their properties and associated configuration sets
(chapter 3). Finally some additional features of the TEMS Service Control
Script Designer tool are covered, and some reference material is provided
(chapters 4–5).

2.2. Basics of Creating Scripts

This section covers the fundamentals of creating a complete and valid script
that is ready to be run. For purposes of illustration we will build a very simple
script that dials single voice calls. Video calls are handled in similar fashion.
• Add a voice dial activity to the script. To this end, expand the Voice node
in the Activity pane and drag the Dial item to the empty script. (The
cross-reference here, just like others that follow, points to the reference
chapter 3.)

• The Dial box is tagged by an exclamation mark. This means that the
activity is not yet properly configured. A similar exclamation mark in the
Properties pane indicates the property that is undefined: “Configuration”.

NT12-10833 ver 4.0 5

TEMS Service Control Script Designer – User’s Manual

• What we need to do is to define a configuration set for the Dial activity.

This is done in the Configuration Sets pane. For a voice dial, the
configuration consists simply of the phone number to call. (In other cases
it can be more complex, as will be seen later.)
• Give the configuration a suitable name, such as one identifying the
subscription having this number. The example below uses a neutral
designation “Voice Call Recipient 1”, for which you will probably want to
substitute something more specific.
• Finish by clicking the Apply button.

• The Properties and Workflow panes are now updated with the
configuration data.

6
 Chapter 2. Tutorial

When just dialing a call like this, it will not have a duration. The call will be
established and then immediately hung up (since the script has run to
completion). To give duration to a call, use the Wait activity: compare
section 2.7.5.
• Drag the Wait activity to a position just below the voice dial box. The
graphical user interface helps you position the Wait box correctly by
means of guiding symbols and text.

• Set the duration of the wait in the Properties pane:

• Finally, add a Hang Up activity after the wait.

NT12-10833 ver 4.0 7

TEMS Service Control Script Designer – User’s Manual

2.3. Setting Up a Network Connection

This section shows how to set up a network connection, which is a necessary
preparation for running data services.
• Expand the IP node in the Activity pane and add a Network Connect
activity to the script.

• Again you will be notified that a matching configuration is missing:

8
 Chapter 2. Tutorial

• A configuration for a data connection is created in the same way as one

for voice, only it contains many more parameters. In particular, you need
to specify whether to use RAS or NDIS. See section 3.3.1 for full details.

• Once you have the configuration down, point to it from the Configuration
field in the activity properties. Later on, if you have multiple network
connect configurations defined, you can pick and choose among them.

2.4. Setting Up a Data Service Activity

In this section, we will set up an FTP download as an example of a data
service activity. We will use the data connection configuration created in
section 2.3.
• First add a Network Connect activity. Associate it with the
“W995_Dialup_1” configuration set created in section 2.3.
• Then add a Network Disconnect activity at the bottom of the script. The
disconnect operation will take down the network connection. This activity
needs no particular configuration, so you do not need to associate it with a
configuration set.

NT12-10833 ver 4.0 9

TEMS Service Control Script Designer – User’s Manual

• The FTP session itself is handled by the FTP Download activity. Insert an
activity of this type between network connect and disconnect:

• For the FTP Download activity, you need to create a configuration set
representing the FTP server and how to access it. Again this is done in
similar fashion as for previously created configurations.

10
 Chapter 2. Tutorial

• After completing the definition of the FTP server configuration, reference it

from the FTP Download activity in the same manner as before.

2.5. Stand-alone PS Attach and Detach

In this section we will perform explicit PS attach and detach operations in
isolation. One reason for doing this could be to measure the time taken by
these operations, particularly for the purpose of computing KPIs. We will
reuse the configuration sets and activities from sections 2.3 and 2.4.
• We begin with the FTP download script from section 2.4.
• At the start of this script, add a PS Detach and a PS Attach activity, in that
order (they are found in the IP category). This will detach the device from
the PS network and then reattach the device.

NT12-10833 ver 4.0 11

TEMS Service Control Script Designer – User’s Manual

See also section 2.6.

2.6. Snippets
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.
Predefined snippets for all supported services are provided in the Activity
pane. For an example of such a predefined snippet in use, see section 2.7.4.
The predefined snippets are also tailored to produce all data required to
compute KPIs.
You can also save an arbitrary activity sequence as a user-defined snippet:
• Select all of the activities by dragging the mouse pointer, then enter the
File menu and select Save as Snippet. You are prompted to name and
describe the snippet.
Example: The detach-and-attach procedure in section 2.5 could be a good
candidate for a user-defined snippet, since it will recur in any script where you
want to detach and then reattach to the PS network.

12
 Chapter 2. Tutorial

2.7. Script Control Structures

The Control Flow node in the Activity pane contains a number of logical
constructs and timers for controlling the script execution flow.

2.7.1. Sequences
You can formally define a group of activities in a script as a sequence. This is
handy if you want to apply some operation to all of these activities – for
example, to enable or disable them.
• Suppose your script includes PS detach followed by PS attach as
described in section 2.5. Suppose further that you want a convenient
means of turning the detach/attach activities on and off. You can then
encapsulate the PS Detach and PS Attach activities within a sequence.
• Expand the Control Flow node and from it drag a Sequence activity to a
position immediately above the PS Detach activity:

• Select the PS Detach and PS Attach activities by holding Ctrl and clicking
each activity, then drag them both (using the PS Detach box as handle)
into the sequenceActivity1 box. You can now enable and disable the
detach–attach sequence as a whole:

NT12-10833 ver 4.0 13

TEMS Service Control Script Designer – User’s Manual

Compare section 2.12. For full details on the Sequence activity, see
section 3.2.4.

2.7.2. If–Else Constructs

An if–else construct is used to split the execution flow into several branches
based on the outcome of a previous activity.
Here is an example. Suppose the phone is on a WCDMA network and is
instructed to do an FTP download. Now if the phone is handed over to GSM,
so that the throughput is sharply reduced, then we want to abandon the
download, i.e. the activity should terminate. (This is accomplished by
imposing a “terminate on event” condition on the activity; see section 2.9.)
After a handover to GSM has occurred, we want to proceed with a voice call
(which does not require a large bandwidth). If on the other hand the phone
remains on WCDMA, then after the FTP download has completed we want to
continue with a video streaming session.
To this end we use an if–else construct in the following manner:
• First add a Network Connect activity, and then an FTP Download activity
with the Abort property set to On Event and “Handover from UTRAN”
selected as event type:

• Then add an If–Else activity below the FTP download:

14
 Chapter 2. Tutorial

– For the left-hand branch (“ifElseBranchActivity1”), set Condition Type

to Activity Result, and set the associated attributes as follows: Activity
= the name of the FTP download activity, by default
“ftpDownloadActivity1”, Operator = Equals, Result = Stopped by
Event. See next screenshot.
– For the right-hand branch (“ifElseBranchActivity2”), set Condition
Type to Any. This always evaluates to true, so that the right-hand
branch will be executed whenever the condition in the left-hand
branch is false. (Not shown in the screenshot below.)

• Add a voice dial activity on the left (to the node “sequenceActivity1”) and a
streaming activity on the right (to the node “sequenceActivity2”), as
described in the introduction of this subsection. This is done just as in
sections 2.2 and 2.4 and is not detailed here.
See section 3.2.1 for full details on the If–Else activity.

2.7.3. While Loops

While loops are used to repeat a sequence of activities a predetermined
number of times.

NT12-10833 ver 4.0 15

TEMS Service Control Script Designer – User’s Manual

• Suppose we want to execute an FTP download five times over.

• Begin by dragging While activity to the start of the script. (Just as with
sequences – compare section 2.7.1 –, you first add the empty While
construct to the script, then fill it with the desired contents.)
• In the Properties pane, set the number of times you want to iterate the
while loop. Below, by entering the value 5, we stipulate that the loop
should be run five times in total.

• Now drag the predefined FTP download snippet into the while loop,
dropping it onto “sequenceActivity1” in the indicated spot (“Drop
Activities Here”):

• It may be desirable to insert a brief pause after each pass through the
while loop. You can accomplish this by appending a Wait activity at the
end of the FTP snippet:

16
 Chapter 2. Tutorial

• Set the duration of the wait in the Properties pane:

For example, if you set Duration to 10 s, the script will perform five FTP
downloads in succession with a 10 s idle interval between downloads.
See section 3.2.2 for full details on the While activity.

2.7.4. Parallel Activities

All scripts so far have been written for a single device engaged in one activity
at a time. However, a script can also control parallel activities to the same
device.

2.7.4.1. Example: Concurrent Activities on the Same Device

The Parallel structure can also be used to run multiple activities concurrently
on the same device, even multiple activities of the same type, provided that
the device supports it. The activities concerned are those for FTP download/
upload, HTTP, email, and Ping.
The script shown below lets one device perform two concurrent FTP
downloads. All instances of the FTP Download activity use the same
configuration set; however, to prevent file write conflicts, each activity adds a
unique prefix to the target file name (refer to section 3.3.7 for details).

NT12-10833 ver 4.0 17

TEMS Service Control Script Designer – User’s Manual

When assigning multiple scanning activities to the same device, it is best not
to start all of the scans at the exact same time. Insert short waits as
appropriate to stagger the start times, as exemplified in the following
screenshot (branch 1: no Wait; branch 2: Wait with duration 2 s; branch 3:
Wait with duration 4 s).

2.7.5. Wait
The Wait activity basically does nothing, and it temporarily halts the execution
of the workflow branch it is located in – for all devices, not just the device the

18
 Chapter 2. Tutorial

Wait is assigned to. After the wait time has expired, the execution proceeds to
the next activity.
When following a (voice) Dial, Video Dial, or Start ... Scan activity, the Wait
has the apparent effect of giving duration to that activity, and this construction
is the most convenient method of controlling the duration. The Wait activity
also comes in useful whenever some tasks need to be cleanly separated in
time for one reason or other.
For some usage examples, see sections 2.2 and 2.7.3.
See section 3.2.9 for full details on this activity.

2.7.6. Wait For

The Wait For activity can be used to:
• Wait for a scheduled point in time. The schedule can be set up in a
number of ways. See section 2.7.6.1 below.
• Wait for another activity to finish with a predetermined outcome. See
section 2.7.6.2.
• Wait for a particular kind of event to occur. This is straightforward; see the
reference section 3.2.10 for the fine points.

2.7.6.1. Waiting For a Scheduled Point in Time

Suppose we want a device to dial a short voice call once every 10 minutes.
This can be accomplished by putting the voice call inside a while loop which
also contains a Wait For activity, providing a timing mechanism.
• Create a While loop and set its termination condition to whatever you like.
• At the top of the loop, put a Wait For with Trigger = Schedule.
– If you just want to start the dialing as soon as the script starts, set
Start to Immediately.
– Alternatively, you can specify that the calls should begin at the turn of
the hour (“On the Hour”) or at an arbitrary time (“Time of Day”).
• To make the loop execute with the desired frequency, continue by setting
Repeat to Yes and Repeat Interval to 10 minutes. The loop will then
pause at the Wait For activity each time until 10 minutes have passed
since the previous turn. This pattern will repeat until the while loop
terminates.

NT12-10833 ver 4.0 19

TEMS Service Control Script Designer – User’s Manual

• Add activities for the voice call (Dial, Wait, Hang Up) just as in section 2.2.
In the screenshots below, the call duration has been set to 2 minutes.

Left: While loop controlled by Wait For with Start = Immediately.

Right: While loop controlled by Wait For with Start = Time of Day.

2.7.6.2. Waiting For a Given Outcome of an Activity1

Instead of collecting data continuously, an alternative (“event-driven”)
approach to data collection is to wait until something interesting happens and
trigger recording only then.
Again taking CS voice as a simple use case, suppose that the voice service is
tested by dialing one call after another. If a call proceeds normally, we do not
log any data, but if a call is blocked, we want to start a logfile recording to
capture what happens over the following one-minute period.
• Create a Parallel structure with two branches.

1. This construct is currently not functional. Please see the product Release
Note for further details.

20
 Chapter 2. Tutorial

• In the left-hand branch, insert a While loop repeating voice calls.

Configure the Dial activity to abort if the call is blocked (Abort property set
to On Event with “Blocked Call” selected as trigger).
• In the right-hand branch, put a Wait For activity at the top monitoring the
voice calls. Set the Trigger property to Activity Result and stipulate that
it should equal “Stopped by Event”. Then add activities for logfile
recording beneath the Wait For: Start Recording followed by a Wait with
Duration = 1 min and finally Stop Recording.

If any call failures are of interest, and not only blocks, then set Activity
Result to the catch-all value “Failed” instead. Recording will then be triggered
by any voice call that does not complete normally.

2.7.7. Terminate
The Terminate activity simply kills the whole script immediately and uncondi-
tionally. One possible application of this activity is to combine it with Wait For
to stop a script at a fixed time of day. The Wait For should then have Trigger
= Schedule and Start = “Time of Day”. For example, suppose the script

NT12-10833 ver 4.0 21

TEMS Service Control Script Designer – User’s Manual

contains a while loop; the sequence depicted below might then be inserted in
the while loop to stop execution at 3 p.m.

2.8. Editing Scripts and Script Settings

Note: A script currently in use in a work order cannot be edited and

saved with the same name.

You can move activities around in the script by clicking and dragging.
You can also edit scripts using the Cut, Copy, and Paste commands found in
the Edit menu of the TEMS Service Control Script Designer window. The
same operations can be performed from the window toolbar or from the
context menu that appears when right-clicking a workflow item. The editing
commands work in standard Windows fashion.
A few points merit special comment:
• You can select multiple activities to move, cut, or copy by holding Ctrl and
clicking. The activities do not have to be adjacent in the script but can be
picked arbitrarily.
• If you are selecting a number of consecutive activities and wish to
preserve their ordering after they are moved or pasted, Ctrl-click the
activities from top to bottom in the same order as they come in the script.
• When dragging a selection to a new position in the sequence, use the
topmost activity as handle to preserve the ordering of activities.
(Whatever activity you use as handle will end up on top.)

22
 Chapter 2. Tutorial

• The destination of a pasted item depends on what, if anything, is currently

selected in the script:

Item(s) Selected in Script Paste Destination

None Bottom of script

One or more arrows, no activity Above arrow first selected

One or more activities1 Below activity first selected

Sequence activity Bottom of sequence

If–Else, While, or Parallel activity – (cannot paste)

1. Any except the ones mentioned in subsequent table rows.

2.9. Activity Properties That Control Execution

All activities have some general properties governing their execution:
• If an activity fails, you can choose to skip that activity, retry the activity, or
terminate the entire script (On Failure property).
• You can have an activity aborted after a fixed length of time, or if a specific
event occurs (Abort property).
For full details, see section 3.8.2.

2.10. Control Functionality

For the RAT lock and band lock functions, it must be noted that the script
activities are inevitably generic in nature, since when composing a script it is
not known what devices the activities will apply to. Therefore, the Band Lock
activity has bands from every supported technology selectable. In conclusion,
a control activity in a script can be executed only if the target device is
capable of the operation in question.
See section 3.1 for full details on the control activities.

NT12-10833 ver 4.0 23

TEMS Service Control Script Designer – User’s Manual

2.11. Validation of Scripts

The validation function found in the Script menu is not supported in either
TEMS Automatic 10.1 or TEMS Symphony 7.4. Rather, work orders/scripts
are validated automatically in both products when assigned to devices.

2.12. Suppressing Parts of a Script

It may happen that you want to run only certain parts of a script and exclude
others. You can easily disable any individual activity by right-clicking it or by
changing the Enabled flag in the Properties pane, as shown below.

An activity that is currently disabled appears dimmed in the workflow pane.

For example, suppose we want to skip the initial detach/attach procedure.
After disabling the sequence comprising the first two activities, the flowchart
looks like this:

24
 Chapter 2. Tutorial

Note: Be sure not to disable an activity that another activity is

dependent on. For example, do not suppress an activity whose
outcome is used to evaluate a subsequent If–Else condition (see
section 2.7.2).

To re-enable a disabled activity, just set the Enable property to True again.

NT12-10833 ver 4.0 25

TEMS Service Control Script Designer – User’s Manual

3. Activities (Reference Chapter)

This chapter also explains all activity-specific properties found in the

Properties pane: that is, those not covered in section 3.8. Not all activities
have unique properties.

3.1. Control Activities

3.1.1. AT
Sends an AT command.
• AT Timeout property: Time (“hh:mm:ss”) to wait for an AT response from
the device.
• AT Command property: AT command string. (Define a configuration for
each AT command you want to send.)

3.1.2. Band Lock

Locks the device to a subset of frequency bands.
• Bands property: Specify band or bands to lock on. You can select one or
several bands within one specific technology at a time for a band lock
activity. Bands from different technologies can thus not be set simulta-
neously. Note also that using Band Lock activity does not require a prior
Radio Access Technology Lock activity.
On the other hand, if Radio Access Technology Lock is used (with a
specific technology selected) prior to Band Lock, the latter must be
applied to bands within the RAT you have locked to.
Supported technologies:
– TEMS Automatic 10.1: GSM, WCDMA, and LTE.
– TEMS Symphony 7.4: GSM, WCDMA, LTE, and CDMA.

26
 Chapter 3. Activities (Reference Chapter)

Locking to a subset of frequency bands might take a while, depending on the

network configuration, so consider adding a Wait activity before the actual
measurement activity to ensure that the band lock has been performed.

3.1.3. Channel Lock

Locks the device to one or several radio channels.
The Channel Lock activity does not control GSM BSIC or WCDMA
scrambling code selection.
• Channels property: Specify the channel or channels to lock on for each
technology of interest. A channel lock takes effect only after the device
has entered the associated RAT.

3.1.4. Filemark
Enables automatic filemarks. Filemarks are text strings which can be inserted
automatically in a logfile in order to tag interesting segments in the file.
• Filemark property: Filemark text string.

3.1.5. Radio Access Technology Lock

Locks the device to a particular radio access technology (RAT).
• Technology property: Specify the RAT to lock on. The choice “Not
locked” releases a lock that has been previously applied. Supported RATs
are:
– TEMS Automatic 10.1: GSM, WCDMA, and LTE.
– TEMS Symphony 7.4: GSM, WCDMA, LTE, and CDMA.

Please note that if the measurements will be performed on LTE (Technology

property set to LTE), or if they might be performed on such a network (no RAT
lock set, but an LTE network is present), then the PS Attach activity at the
beginning of the script should be preceded by a specification of the APN to be
used. Do this by means of an AT activity containing the following string in the
AT Command property:
AT+CGDCONT=1,"IP","<yourAPN.com>"
Locking to a particular RAT might take a while, depending on the network
configuration, so consider adding a Wait activity before a subsequent

NT12-10833 ver 4.0 27

TEMS Service Control Script Designer – User’s Manual

measurement activity to ensure that the RAT lock takes effect before the
measurement begins.

3.1.6. Start Recording

Starts recording of a logfile. A Start Recording activity must be paired with a
Stop Recording activity that concludes the recording and closes the logfile.
• Prefix property: You can add a descriptive prefix to the default logfile
name. The following characters are ignored if entered in this field: \ /
: * ? ' < > |
• Buffer length property: Length in seconds of buffered content prepended
to the logfile. Min.: 0 s. Max.: 40 s. Default: 0 s.
• Subject, Description, and Tags properties: These are metadata fields
that you can write to the logfile. However, the fields are not used for
anything in particular in TEMS Symphony.

3.1.7. Stop Recording

Concludes the recording of a logfile initiated by a Start Recording activity and
closes the logfile.
• Recording Activity property: Here you select which Start Recording
activity to stop, identified by its name (e.g. “startRecordingActivity1”).

3.2. Control Flow Activities

For a hands-on tutorial on how to use these activities, please turn to
section 2.7.

3.2.1. If–Else
This activity splits the workflow into two or more branches, with a condition
attached to each branch. Each condition (except the catch-all “Any”: see
below) is based on the outcome of a previous activity. Evaluation of
conditions proceeds from left to right.
At the top level, the If–Else activity does not have any unique properties.
Each branch of the construct, however, is constituted by an “if–else branch”
activity which has the following property:

• Condition Type property:

28
 Chapter 3. Activities (Reference Chapter)

To define a non-trivial, yet simple condition, set Condition Type to Activity

Result. The following attributes then become visible:

Activity: The activity (identified by its name in the script) whose

outcome will determine the truth value of the condition.
Operator: Relational operator: “Equals” or “NotEquals”.
Result: The activity result that you want to match. One of: Succeeded,
Failed, Stopped by User, Stopped by Duration, Stopped by Event.

You can also set up a more complex condition in the form of a boolean
expression involving multiple activity result conditions, each composed as
described above. To this end, set Condition Type to Combined. The
following attributes then appear (the structure can be expanded
recursively):

• Condition 1: A subcondition of type Activity Result, or another

Combined condition.
• Operator: Boolean operator: And or Or.
• Condition 2: A subcondition of type Activity Result, or another
Combined condition.

Finally, setting Condition Type to Any creates a trivial condition that

always evaluates to true. This value should always be used as a catch-all
condition for the rightmost if–else branch. (The If–Else construct is set up
in that way by default.)

For an example of usage, see section 2.7.2.

NT12-10833 ver 4.0 29

TEMS Service Control Script Designer – User’s Manual

3.2.2. While
This activity constitutes a while loop.
• Condition Type property:

Count: Fixed number of iterations.

Time: Fixed execution time. When this duration expires, the while loop
does not terminate immediately; rather, the current turn is completed
first. (The running time is compared to the limit before a new turn
begins.)
Event: The while loop is terminated when any of the selected events is
reported by the selected equipment.
Combined: Select this to define a more complex termination condition
in the form of a boolean expression combining instances of the other
available criteria. Additional fields appear as follows; the structure can
be expanded recursively:
• Condition 1: A subcondition of type Count, Time or Event, or
another Combined condition.
• Operator: Boolean operator: And or Or.
• Condition 2: A subcondition of type Count, Time or Event, or
another Combined condition.

While loops can be nested arbitrarily.

For an example of usage, see section 2.7.3.

3.2.3. Parallel
This activity splits the workflow unconditionally into two or more branches.
There is no hard limit on the number of branches. A device can participate in
more than one branch, provided that the device supports concurrent
execution of the services involved (or several sessions using the same
service).
Each of the parallel branches is encapsulated within a Sequence activity.
This activity has no unique properties.
For a usage example, see section 2.7.4.

30
 Chapter 3. Activities (Reference Chapter)

3.2.4. Sequence
This control structure formally defines a sequence of activities as a unit,
allowing it to be treated as such. (For example, the entire sequence can be
enabled or disabled in a single action, as exemplified in section 2.7.1.)
This activity has no unique properties.

3.2.5. Configuration Sequence1

This control structure formally defines a sequence of activities as pertaining
to device configuration (as opposed to measurement).
By default, a new script has Configuration Sequence activities placed at the
beginning and at the end. The former is intended for device configuration that
is needed to prepare for measurement, and the latter for restoring the device
to its prior state after it has finished measuring.
Locking activities in the Control category (see section 3.1) must be placed
inside a Configuration Sequence activity. For example, you may want to lock
the device to a RAT prior to measurement, and then release the RAT lock
after the measurement has concluded.
This activity has no unique properties.

3.2.6. Measurement Sequence1

This control structure formally defines a sequence of activities as pertaining
to measurement (as opposed to configuration of devices).
By default, a new script has a Measurement Sequence activity placed in the
middle, between the two Configuration Sequence activities. Everything that
relates to measurement should be put inside the Measurement Sequence.
This activity has no unique properties.

3.2.7. Synchronized Call Sequence

This activity is intended solely for use in the snippet bearing the same name.
See section 3.7.5.1.

1. Please note that these activities are not present in the tutorial in
chapter 2.

NT12-10833 ver 4.0 31

TEMS Service Control Script Designer – User’s Manual

3.2.8. Terminate
This activity terminates the entire script immediately. It has no unique
properties.
For an example of usage, see section 2.7.7.

3.2.9. Wait
The Wait activity basically does nothing at all, and in effect it temporarily halts
the execution of the workflow branch where it is located. After the wait time
has expired, the execution proceeds to the next activity.
When following a (voice) Dial activity, the Wait has the apparent effect of
giving duration to the call, and this construction is the most convenient
method of controlling the call length. The situation with Start ... Scan
activities is similar. Furthermore, the Wait activity comes in useful whenever
some other tasks need to be separated in time.
• Configuration property:

Mode:
• Normal: The wait time is constant and is specified in the Duration
field. This is the default mode.
• Random: The wait time is randomly selected on each occasion
from the range Min duration ... Max duration and is uniformly
distributed within that range.

For usage examples, see sections 2.2 and 2.7.3.

3.2.10. Wait For

This is a conditional wait which lasts until a given condition is satisfied.
• Trigger property: This property determines what to wait for.

Event: Not supported in TEMS Automatic 10.1 or TEMS

Symphony 7.4.

32
 Chapter 3. Activities (Reference Chapter)

Schedule: Wait for a point in time determined by a schedule (which is

unrelated to any device activity). Additional fields Start, Time, Repeat,
and Repeat Interval appear where you set up the schedule.
• Start = Immediately: No wait. This option is intended to be used in
while loops together with the Repeat option. Its use is best illus-
trated by an example; see section 2.7.6.1.
• Start = On The Hour: Wait for a new hour to begin. Equivalent to
Time of Day with Time = hh:00:00; see below.
• Start = Time of Day: Wait for a specified time of day (Time), stated
in the format hh:mm:ss. An example is given in section 2.7.6.1.
• Repeat: This option is intended to be used in while loops and has
an effect only within such a structure. What it does is to reiterate
the “wait for” procedure at regular intervals whose length is defined
by Repeat Interval. See the example in section 2.7.6.2. If Repeat
is set to No, there will be no repetitions.

Activity Result: Wait for a particular outcome of another activity in the

script. Additional fields Activity, Operator, Result appear where you
detail the required outcome: for example, “ftpDownloadActivity1
Equals Failed”.
• Result = Succeeded: The activity completed normally.
• Result = Failed: The activity failed for whatever reason.
• Result = Stopped by User: In TEMS Symphony 7.4, this condition
is met if the user clicks the “stop script” button in TEMS Local
Probe Control. Not supported in TEMS Automatic 10.1.
• Result = Stopped by Duration: The activity was aborted because
its maximum duration expired. This can happen only if the activity
has its Abort property set to On Timeout: see section 3.8.2.
• Result = Stopped by Event: The activity was aborted because a
specific event occurred (Abort property set to On Event; again,
see section 3.8.2).
• Result = Stopped by Equipment Restart: The activity was aborted
because the device executing it was restarted.
• (Result = Stopped by Application Restart: This option is not used.)
You must yourself ensure that the monitored activity has a position in
the workflow where it will in fact complete to terminate the Wait For
activity. This is not considered during validation.
For usage examples, see section 2.7.6.

NT12-10833 ver 4.0 33

TEMS Service Control Script Designer – User’s Manual

Combined: Select this to define a more complex trigger in the form of

a boolean expression combining instances of the other available
criteria. Additional fields appear as follows; the structure can be
expanded recursively:
• Condition 1: A subcondition of type Schedule or Activity Result,
or another Combined condition.
• Operator: Boolean operator: And or Or.
• Condition 2: A subcondition of type Schedule or Activity Result,
or another Combined condition.

3.3. IP Activities

3.3.1. Network Connect

Establishes a data service connection. In the packet-switched case, a PDP
context is activated (LTE, UMTS); in the circuit-switched case, the device
performs a dial-up.
Whether NDIS or RAS is used is governed by the Mode parameter, as
detailed under Configuration below. NDIS can be chosen for packet-
switched only, whereas RAS can be used with both PS and CS.
A side-effect of the Network Connect activity is to start a restricted form of IP
sniffing that is performed continuously for the sake of collecting input to KPI
calculations. (This IP sniffing collects only data needed for KPIs and is distinct
from the full-scale variety which is initiated by the Start IP Sniffing activity.)
• Configuration property:

Mode: Technology to use for connecting to the network: NDIS or RAS.

If “Best available” is chosen, NDIS is first and RAS is second priority.
For an NDIS connection to be establishable, the device must of course
support NDIS.

34
 Chapter 3. Activities (Reference Chapter)

Succeed If Already Connected: This parameter governs what will

happen if the device already has a network connection (a valid IP
address) set up by other means when the Network Connect activity is
run, for example using an external connection manager.
• If set to True, the Network Connect activity will count as successful
anyway. This setting is useful if you want to be able to run Network
Connect without full knowledge of the device’s previous activities,
and you wish to avoid triggering a failure just because the device
was already connected.
• If set to False, the Network Connect activity will count as a failure.

UMTS/LTE APN: The Access Point Name to use for UMTS and LTE
networks. The parameter is not applicable to other cellular
technologies. Leave this field empty if an APN is specified in the device
(always needed for NDIS) or for the modem in Windows.
RAS Phone Number: Phone number to use when performing a RAS
dial. For UMTS this is usually *99#; however, if a CID other than 1 is to
be used you need to specify that value, as follows: *99***n#.
NDIS CID: The CID (Connection Identifier) to connect with when NDIS
is used.

User Name, Password: Certain operators require authentication in

order to establish a data service connection. If this is the case for you,
enter user and password here.
IP Address: Local IP address. Leave blank if the IP address is
provided automatically by the operator.

Primary DNS: IP address of the primary domain name server. Leave

blank if this is provided automatically by the operator.
Secondary DNS: IP address of the secondary domain name server.
Leave blank if this is provided automatically by the operator.

Use Header Compression: Use of header compression for packet-

switched. (Property of PS bearer.) Not applicable to circuit-switched.
Use Data Compression: Use of data compression for packet-
switched. (Property of PS bearer.) Not applicable to circuit-switched.

NT12-10833 ver 4.0 35

TEMS Service Control Script Designer – User’s Manual

3.3.2. Network Disconnect

Terminates a data service connection. In the packet-switched case a PDP
context is deactivated (LTE, UMTS); in the circuit-switched case the device
performs a hang-up.
If the device is already disconnected, this activity has no effect, but it still
counts as successful. (Same behavior as for Network Connect with Succeed
If Already Connected set to True.)
This activity has no unique properties.

3.3.3. PS Attach
Performs a packet service attach.
Note that this activity may not be needed for those devices that may have
automatically attached to a PS network when powered on. If you are
uncertain as to whether or not the device performs such an automatic attach,
simply insert a PS Attach activity at the beginning of the script. This ensures
that the device will attach and that logging of Layer 3 messages will be
initiated.
After the measurements, at the end of the script, insert a PS Detach activity to
detach from the PS network.
Please note that in case the measurements will be performed on LTE (RAT
lock set with Technology = “LTE”), or if they might be performed on such a
network (no RAT lock set, but an LTE network is present), then the PS Attach
should be preceded by a specification of the APN to be used. Do this by
means of an AT activity containing the following string in the AT Command
property:
AT+CGDCONT=1,"IP","<yourAPN.com>"
This activity has no unique properties.

3.3.4. PS Detach
Performs a packet service detach.
This activity should take place at the end of the script if PS Attach has been
done earlier.
PS Detach may also be useful as an initial operation to make sure that the
phone is not attached to the packet service when starting a measurement (for
example, if it has attached automatically at power-on).

36
 Chapter 3. Activities (Reference Chapter)

This activity has no unique properties.

3.3.5. Start IP Sniffing

Starts capture of IP packets.
Note that you do not have to use this command to obtain the data required for
KPIs; such data is collected automatically.
• Configuration property:

Client:
• PC: The IP sniffer built into the TEMS product software is used.
• ODM: An on-device IP sniffing service is used.

Packet Size: Determines how many bytes of each message will be

presented. If you choose a fixed packet size, any further bytes in the
message will be truncated. If you choose Full packet size, all
messages are presented in full and the entire header is always
decoded. (For ODM, 1500 bytes is regarded as “full packet size”, and
any bytes in excess of that number are truncated.)

Filter: Type of filtering to apply to IP packets.

• Optimized Performance: Capture of IP packets is reduced to the
minimum needed to compute KPIs. (Packets are filtered with
respect to IP address, protocol [TCP/UDP], and port.) – Not
supported for ODM.
• Headers Only: The first 54 bytes of every IP packet are captured.
• None: No filtering of IP packets. Note: This means that all packets
belonging to any service used by the PC will be captured; packets
are filtered with respect to IP address only.

3.3.6. Stop IP Sniffing

Stops capture of IP packets initiated by the Start IP Sniffing activity.

NT12-10833 ver 4.0 37

TEMS Service Control Script Designer – User’s Manual

• Configuration property:

Client:
• PC: The IP sniffer built into the TEMS product software is used.
• ODM: An on-device IP sniffing service is used.

3.3.7. FTP Download

Downloads a file from an FTP server.
Please be aware that paths and file names must have correct case
throughout.
Note also that you can conduct TCP load tests with the Network Bandwidth
activity.
• Configuration property:

Source File: The path and name of the file residing on the FTP server,
e.g. srcdir/srcfile.dat. No explicit root symbol is used (no leading
slash); if the file is in the root directory, type the file name only. Note
that the correct orientation of the slashes is dependent on the FTP
server operating system.
Target File: Leave blank. No files are stored locally.

Server Address: The IP address or host name of the FTP server. No

ftp:// prefix is to be used. The address may not contain a path to a
subdirectory.
Server Port: The port on which the FTP server listens for requests.
The default port number is 21.
Firewall Mode: PASV or PORT, enabling or disabling passive FTP as
defined in  IETF RFC 959. Note that it is essential to set this
correctly.
Local Data Port: The data port the client will use for FTP download.
Visible only when Firewall Mode = PORT.

38
 Chapter 3. Activities (Reference Chapter)

Use SFTP: If set to Yes, file transfer will be done over SFTP (SSH File
Transfer Protocol, “Secure FTP”) rather than FTP proper.
Note that no KPI data is logged for SFTP. Also be aware that the
throughput may be reduced compared to regular FTP. Therefore, do
not use SFTP in stress tests aimed at determining the maximum data
throughput.

User: User name on the FTP server, if required.

Password: User password on the FTP server, if required.
Account: Account name on the FTP server, if applicable.
End Session After Time: If set to True, the FTP session is ended
automatically after a user-specified length of time. Enter the desired
session duration in the Time field. The duration is counted from the
moment the first FTP packet is received from the server.
Max Allowed Network Idle Time: If the TCP connection is idle for a
longer time than this, a “TCP Connection Max Idle Time Exceeded”
event is triggered. Setting this to zero means that infinite idle time is
allowed without the event being triggered.

3.3.8. FTP Upload

Uploads a file to an FTP server.
Please be aware that paths and file names must have correct case
throughout.

NT12-10833 ver 4.0 39

TEMS Service Control Script Designer – User’s Manual

• Configuration property:

Target File: Path and file name describing where and how to store the
file on the FTP server, e.g. targdir/targfile.dat. No explicit root symbol is
used; if you type a file name only, the file will be written to the root
directory. Note that the correct orientation of the slashes is dependent
on the FTP server operating system.
A session ID (integer) is prefixed to the file name. If multiple FTP
Upload activities execute in parallel, multiple files are created, each
with a unique session ID prefixed to prevent conflicts, e.g.:
0targfile.dat, 1targfile.dat.
Source File: Not used. A temporary file is created for uploading (see
also Use Temporary File).
Size to Upload: Size of the file to upload (only valid if Use Temporary
File = True). It is possible to specify the unit as follows: B = byte, K =
kilobyte, M = megabyte, G = gigabyte, T = terabyte. Alternatively,
lowercase letters can be used with no difference in meaning. If you do
not specify a unit, the number you enter is interpreted as a byte count.
Use Temporary File: Must be set to True. In both TEMS Automatic
and TEMS Symphony, the measurement device creates a temporary
file holding the data to upload.
Delete Uploaded File: If set to True, the target file is deleted after
successful upload. If set to False, the target file is not deleted.

Server Address: The IP address or host name of the FTP server. No

ftp:// prefix is to be used. The address may not contain a path to a
subdirectory.
Server Port: The port on which the FTP server listens for requests.
The default port number is 21.
Firewall Mode: PASV or PORT, enabling or disabling passive FTP as
defined in  IETF RFC 959. Note that it is essential to set this
correctly.
Local Data Port: The data port the client will use for FTP upload.
Visible only when Firewall Mode = PORT.

40
 Chapter 3. Activities (Reference Chapter)

Use SFTP: If set to Yes, file transfer will be done over SFTP (SSH File
Transfer Protocol, “Secure FTP”) rather than FTP proper.
Note that no KPI data is logged for SFTP. Also be aware that the
throughput may be reduced compared to regular FTP. Therefore, do
not use SFTP in stress tests aimed at determining the maximum data
throughput.
User: User name on the FTP server, if required.
Password: User password on the FTP server, if required.
Account: Account name on the FTP server, if applicable.
End Session After Time: If set to True, the FTP session is ended
automatically after a user-specified length of time. Enter the desired
session duration in the Time field. The duration is counted from the
moment the first FTP packet is received from the server.
Max Allowed Network Idle Time: If the TCP connection is idle for a
longer time than this, a “TCP Connection Max Idle Time Exceeded”
event is triggered. Setting this to zero means that infinite idle time is
allowed without the event being triggered.

3.3.9. HTTP Get

Downloads a URL from an HTTP server.
• Configuration property:

Browser Client: Web browser used to conduct HTTP sessions.

• TEMS Browser: The Web browser built into the TEMS product
software is used.
• Internet Explorer: Internet Explorer 9 is used.
• UE Download: An on-device HTTP client similar to the TEMS
Browser is used.
• UE Webkit: An on-device Web browser is used.
Regarding concurrency limitations, see below.

NT12-10833 ver 4.0 41

TEMS Service Control Script Designer – User’s Manual

Client Threads: (TEMS browser) Number of concurrent threads to be

used by the client in handling the HTTP session. Note that the main
URL (specified under URL) is downloaded only once, regardless of the
number of threads.
URL: Main URL to download. – In post-processing, the HTTP Get
session will be classified as “File Transfer” if the downloaded file has
one of the following extensions: .7z, .avi, .bmp, .jpg, .mp3, .mpg, .png,
.rar, .txt, .wav, or .zip. If the file has some other extension, the session
will count as “Web Browsing”.

Terminate All Internet Explorer Processes: (Internet Explorer) If set

to True, all Internet Explorer processes will be killed whenever no
HTTP Get activity is executing. This ensures that no ghost processes
are left running and consuming resources; on the other hand, it also
prevents you from doing Web browsing with Internet Explorer while
HTTP testing is in progress. If you turn this option on, use some other
browser for Web browsing.

The following proxy settings are available for the TEMS browser and
for Internet Explorer.
Use Proxy Server: Select whether to use a proxy server for this
connection.
Proxy Server Address: Proxy server address.
Proxy Server Port: Proxy server port.

End Session After Time: If set to True, the HTTP session is ended
automatically after a user-specified length of time, indicated in the
Time field. The duration is counted from the moment the first HTTP
packet is received from the server.
Max Allowed Network Idle Time: Maximum allowed time with no
activity on the network connection before the activity is terminated and
regarded as failed. The value zero means that any amount of idle time
is tolerated.
End Session After Payload Size: If set to True, the HTTP session is
ended automatically after a user-specified amount of data has been
downloaded. Enter the number of bytes to download in the Payload
Size field.

42
 Chapter 3. Activities (Reference Chapter)

Limitations on HTTP Session Concurrency

Internet Explorer and the TEMS browser cannot run concurrently on the
same device.
On the other hand, when either Internet Explorer alone or the TEMS browser
alone is used, there are no restrictions on HTTP session concurrency, neither
for a single device nor for multiple devices.

3.3.10. HTTP Post

Uploads a file via HTTP to a URL.
The HTTP Post activity does not support HTTPS.

Note: This activity requires an upload script (*.aspx) to be present on

the HTTP server. For details, please see the document “HTTP
Upload Server Installation Guide”.

• Configuration property:

Browser Client: Web browser used to conduct HTTP Post sessions.

• TEMS Browser: The Web browser built into the TEMS product
software is used.
• Internet Explorer: Internet Explorer 9 is used.
• UE HTTP: An on-device HTTP client similar to the TEMS Browser
is used.
No particular concurrency limitations apply to the HTTP Post activity.

URL: The URL of the web page to which the file will be uploaded.

Terminate All Internet Explorer Processes: (Internet Explorer) If set

to True, all Internet Explorer processes will be killed whenever no
HTTP Post activity is executing. This ensures that no ghost processes
are left running and consuming resources; on the other hand, it also
prevents you from doing Web browsing with Internet Explorer while
HTTP testing is in progress. If you turn this option on, use some other
browser for Web browsing.

NT12-10833 ver 4.0 43

TEMS Service Control Script Designer – User’s Manual

Use Proxy Server: Select whether to use a proxy server for this
connection.
Proxy Server Address: Proxy server address.
Proxy Server Port: Proxy server port.

End Session After Time: If set to True, the HTTP session is ended
automatically after a user-specified length of time, indicated in the
Time field. The duration is counted from the moment the first HTTP
packet is received from the server.
Max Allowed Network Idle Time: (TEMS browser, Internet Explorer)
Maximum allowed time with no activity on the network connection
before the activity is terminated and regarded as failed. The value zero
means that any amount of idle time is tolerated.
Amount of Data to Upload: Size of the file to upload to the URL. A
temporary data file of the specified size will be created. It is possible to
indicate the unit as follows: B = byte, K = kilobyte, M = megabyte, G =
gigabyte, T = terabyte. Alternatively, lowercase letters can be used
with no difference in meaning. If you do not specify a unit, the number
you enter is interpreted as a byte count.

3.3.11. Ping
Initiates a sequence of pings.
• Configuration property:

Ping Type:
• PC: The Ping client built into the TEMS product software is used.
• UE: An on-device Ping client is used.
Remote Address: The IP address or host name of the server to be
pinged.
Packet Size: Size in bytes of the packet sent with the Ping activity. The
maximum size is 2000 bytes.
Interval Time: Time between consecutive pings. Given in the format
hh:mm:ss.ddd... .
Number of Pings: The number of pings to send. There is no upper
limit.

44
 Chapter 3. Activities (Reference Chapter)

Max Response Time: Maximum time to wait for each ping response.
Given in the format hh:mm:ss.ddd... . Note: This parameter should not
be set lower than 1 s.
Allow Fragmentation: Set this to True to allow Ping packets to be
fragmented. False means that fragmentation of Ping packets is not
allowed.

3.3.12. Network Bandwidth (Iperf Testing)

This activity measures maximum TCP and UDP bandwidth performance by
interacting with an Iperf server. Measuring over TCP is comparable to
assigning multiple concurrent FTP activities to a device; see the example in
section 2.7.4.1.
Before you can use this activity, you must install the Iperf software on the
machine that is to act as Iperf server. Iperf version 3 is used; it is included in
the TEMS product software package, and it is necessary to use this Ascom
supplied software. On the Iperf server machine, you need to run the installer
IPerf3Beta5Ascom.msi, which will install Iperf files to the directory
C:\Program Files (x86)\Ascom\TEMS Products\IPerf3Beta5Ascom. Iperf is
then started by running the file IperfWatcher.exe.
Further information on how to install the Iperf 3 server software is found in the
document “Iperf 3 Server Installation Guide”, doc. no. NT13-18478.
TEMS products have been verified with Iperf 3 running on a Windows server:
specifically, Windows Server 2008 R2 and Windows 7. Iperf 3 on a Linux/Unix
server has not been part of the verification.
• Configuration property:
General section

Iperf Version: Iperf software version: 2 or 3.

Remote Address: The IP address or host name of the Iperf server.
Protocol: The protocol to use for Iperf testing: TCP or UDP. In TEMS
Symphony 7.4, only UDP is supported.

Direction:
• Send: The client sends data to the server.
• Receive: The server sends data to the client.
• Full Duplex: Data is sent in both directions concurrently.

NT12-10833 ver 4.0 45

TEMS Service Control Script Designer – User’s Manual

Port 1: Iperf server port number to use for Direction = Send (also
used for Direction = Full Duplex).
Port 2: Iperf server port number to use for Direction = Receive (also
used for Direction = Full Duplex). For Full Duplex, different port
numbers should be assigned to Port 1 and Port 2.

Duration: The duration of the Iperf testing session (hh:mm:ss).

Retry count: Maximum number of times to retry the Network
Bandwidth activity if the Iperf server is busy.
Retry interval: Time interval between retries.

Telnet/SSH2 section (not used in TEMS Symphony 7.4)

Connection Client: Only Telnet is supported as protocol; SSH2 is not

supported in TEMS Automatic 10.1.
Port: Port on the remote server.
User: User name on the remote server.
Password: Password on the remote server.
Path: Path to Iperf on the remote server.

UDP section (used for UDP only)

Bandwidth: Estimated available UDP bandwidth (throughput) in bit/s.

Note: Setting this value too high for a slow network connection will
lead to failures.
Buffer Size: UDP buffer size in kilobytes.
Packet Size: UDP packet size in bytes.

3.3.12.1. Recommendations for Iperf Testing

• The Iperf server does not support multiple concurrent connections. For
this reason, observe the following:
– The IperfWatcher monitoring tool should have one Iperf server per
device and data transfer direction.
– Do not run the same script on all devices; rather, you need to use
different port numbers for different devices in order to prevent
spurious failures.

46
 Chapter 3. Activities (Reference Chapter)

– For Direction = Full Duplex, two different port numbers should be

assigned (as noted above).
See also section 3.3.12.2 below.
• The value of Duration in the Iperf activity should correspond to the
RetryCount and RetryInterval settings on the Iperf server.
Example: Suppose that IperfWatcher is configured with RetryCount = 3 s
and RetryInterval = 10 s. You should then set Duration to less than
3  10 = 30 s to prevent the Iperf server from being restarted by
IperfWatcher while the activity is still running, something which would
cause spurious failures.
• For best measurement accuracy, Iperf activities with different Bandwidth
values should be run.
• It is advisable to set the Abort failure handling property (see
section 3.8.2) to On Timeout with some suitable time period specified.

3.3.12.2. Setting up Multiple Iperf Servers

To enable multiple TEMS product users to do Iperf testing concurrently
against the same Iperf server machine, multiple Iperf server instances must
be defined on that machine. This is accomplished by editing the file
ConfigInfo.xml in the Iperf installation directory (see above for the path). By
default, this file has a single “IPerfServer” line:
<IPerfServer IP="127.0.0.1" Port="5001"/>
To set up multiple server instances, add more such lines with the same IP and
with Port incremented by one each time: 5002, 5003, etc. (Make sure these
ports are available on the server machine.) When IperfWatcher.exe is run, it
will start all Iperf server instances defined in ConfigInfo.xml.

3.3.13. Predefined Snippets for IP

One snippet is provided for each data service related activity; all with the
following structure: Network Connect  <data service activity>  Network
Disconnect.

NT12-10833 ver 4.0 47

TEMS Service Control Script Designer – User’s Manual

3.4. Messaging Activities

3.4.1. Email Send

Sends an email to an SMTP server.
When composing an email script controlling both sender and receiver, it is
best to use a sequence structure with a waiting period: Email Send  Wait
 Email Receive.
• Configuration property:

From: Email address of sender.

To: Email address of recipient.
Subject: Content of email Subject field.
Body Text File: Leave blank.
Attachment: Leave blank.

Server Address: The IP address or host name of the SMTP server.

Server Port: The port on which the SMTP server listens for requests.
User: User name of email account.
Password: Password for email account.

Security:
• None: No security is applied.
• SSL/TLS: SSL or TLS is used during the whole email session.
• STARTTLS: The initial communication is not encrypted, but a
STARTTLS command is issued later on to set up a secure session.

3.4.2. Email Receive

Receives an email from an IMAP or POP3 server.
When composing an email script controlling both sender and receiver, it is
best to use a sequence structure with a waiting period: Email Send  Wait
 Email Receive.

48
 Chapter 3. Activities (Reference Chapter)

• Configuration property:

Email Protocol: The email retrieval protocol to use: IMAP4 or POP3.

Server Address: The IP address or host name of the IMAP or POP3
server.
Server Port: The port on which the IMAP or POP3 server listens for
requests.
User: User name of email account.
Password: Password for email account.

Storage Location: Leave blank.

Delete Retrieved Files: Not used.

Security:
• None: No security is applied.
• SSL/TLS: SSL or TLS is used during the whole email session.
• STARTTLS: The initial communication is not encrypted, but a
STARTTLS command is issued later on to set up a secure session.

3.4.3. MMS Send

Sends an MMS.
When composing an MMS script controlling both sender and receiver, it is
best to use a Parallel structure. See sections 2.7.4 and 3.2.3.
• Configuration property:
Connection section

Connection Mode: One of CO (Connection-oriented), CL

(Connectionless), or WP-HTTP (Wireless Profiled HTTP).
• CO and CL are used by WAP 1.x and require a WAP gateway. The
difference between the modes is essentially this: With CO, the
device first contacts and performs a handshake with the WAP
gateway before starting to request WAP pages, whereas with CL
this is not done.
• WP-HTTP is used by WAP 2.0. This WAP version may use a WAP
proxy, but this is optional.

NT12-10833 ver 4.0 49

TEMS Service Control Script Designer – User’s Manual

Gateway section

Address: (Appears when Connection Mode = CO or CL) The IP

address of the operator’s WAP gateway.
Port: (Appears when Connection Mode = CO or CL) The WSP port on
the server. The default port numbers are 9201 (CO), 9200 (CL).
User, Password: Login credentials for WAP gateway, if required.

MMS Content section

To: The phone number(s) or email address(es) to send the MMS to.
Multiple recipients can be specified, separated by semicolons. The
receiving device can be identical with the sender.
Text of MMS Message: Free text field containing the text message of
the MMS (if any).
File to Attach to the MMS: The file to send. A wide variety of file
types, including plain-text files and frequently used image file formats,
is supported. A file with an extension unknown to TEMS Service
Control Script Designer will be sent as an attachment to the MMS
(content type “application/octet-stream”).
Please note that operators generally impose a limit on the MMS file
size. If you encounter problems sending MMS messages, try sending
very small files to find out whether the size limit is causing the problem.

MMS Message Center section

URL: The URL of the MMS Center (usually beginning with http://).
User, Password: Login credentials for MMS Center, if required.

Proxy section

Proxy Address: (Appears when Connection Mode = WP-HTTP;

optional) The IP address of the WAP proxy.
Proxy Port: (Appears when Connection Mode = WP-HTTP; optional)
The WAP proxy port number. The default is 8080.
User, Password: Login credentials for WAP proxy, if required.

50
 Chapter 3. Activities (Reference Chapter)

3.4.4. MMS Receive

Receives an MMS.
Note that the device acting as recipient must not have automatic MMS
download turned on (where the device retrieves the MMS message from the
MMS Center automatically as soon as it receives a notification).
• Configuration property:
Connection Parameters section: Same as for Network Connect. The
MMS Receive activity needs its own connection parameters since logging
in to the MMS Center frequently requires connecting to a different APN.
Connection Settings, Gateway, and Proxy sections: These are WAP
settings, the same as for the MMS Send activity.

3.4.5. SMS Send

Sends an SMS.
• Configuration property:

Receiving Device: The phone number or email address to send the

SMS to. The receiving device may be identical with the sender.
SMS Message: SMS message string.
Request Delivery Report: Set this to True if you want the device to
request a delivery report from the SMS Center.
Delivery Report Timeout: Time to wait for the delivery report.
Use Custom SMS Center: Set this to True if you want to make use of
an SMS Center other than the one specified on the SIM. To stick with
the SMS Center indicated on the SIM, set this parameter to False.
SMS Center: Phone number to the SMS Center.

NT12-10833 ver 4.0 51

TEMS Service Control Script Designer – User’s Manual

3.4.6. SMS Receive

Receives an SMS.
• Configuration property:

Match Type:
• Regular expression: Enter regular expression under Message
Match Pattern to match whole message text. The syntax is that of
.NET Framework regular expressions. Reference:
 msdn.microsoft.com/en-us/library/hs600312(v=VS.90).aspx
• Starts with: Enter string under Message Match Pattern to match
beginning of message text.
• Ends with: Enter string under Message Match Pattern to match end
of message text.
Message Match Pattern: The pattern to use for matching incoming or
stored messages. If the field is left empty, any message will match.

Search Text Messages:

• Radio only: The device is not searched for matching SMS
messages. Instead, the activity immediately starts waiting for a
matching message to be received.
• Device first – then radio: SMS messages stored on the device are
searched for matching messages. The point of doing this is to
catch a message already received by the device before it performs
the SMS Receive activity. If no match is found, the activity
subsequently waits for a matching message to arrive.
• Device only: SMS messages stored on the device are searched for
matching messages. If no match is found, the activity terminates
without waiting for a matching message.
• Device only – then clear SMS inbox: Same as “Device only”,
except that once the search is done, the device’s SMS inbox is
cleared.

3.4.7. Predefined Snippets for Messaging

One snippet is provided for each messaging activity; all with the following
structure: Network Connect  <data service activity>  Network
Disconnect.

52
 Chapter 3. Activities (Reference Chapter)

3.5. Scan Activities

A scan activity starts or stops a scan task of a specified type. Use a Wait
activity between Start and Stop to specify the duration of the scan.
• Scanner property: Here you select the type of scanner to use. The choice
made here determines the contents of the Configuration property.
Please note that if you add a scan activity to the script, and no configu-
rations have yet been defined for that activity type, then you need to make
a selection in the Scanner drop-down box to enable the Configuration
Sets pane.
• Configuration property: Scan configuration. These are all described in
chapters 6–8. Below is a full list of the scan activities, keyed to their
configuration descriptions:

Ref. to
Scan Activity Technology Config.
Descr.

Start/Stop CPICH Scan WCDMA 7.1

Start/Stop Enhanced Power Scan LTE 8.4

Start/Stop RSSI Scan GSM 6.1

WCDMA 7.2

LTE 8.2

Start/Stop Signal Scan LTE 8.1

Start/Stop Spectrum Scan GSM 6.2

WCDMA 7.3

LTE 8.3

3.5.1. Predefined Snippets for Scanning

One snippet is provided for each scan type. All of these have the following
structure: Start ... Scan  Wait  Stop ... Scan.

NT12-10833 ver 4.0 53

TEMS Service Control Script Designer – User’s Manual

3.6. Video Activities

3.6.1. Streaming
Downloads streaming video from a streaming server and plays it in an
external video player.
Streaming is always done over HTTP. A number of parameters currently
visible in the user interface are not used, as detailed below.
• Configuration property:

Streaming Type: One of:

• RTP PC: Not supported.
• HTTP PC: Streaming over HTTP using an external, PC-based
video player.
• HTTP UE: Streaming over HTTP using an on-device video player.
The set of further configuration options is different in each case.

54
 Chapter 3. Activities (Reference Chapter)

For HTTP streaming using a PC client, the following options appear:

Streaming URL: URL to use for streaming.
Video Quality: This setting is not used (video quality measurement is
however conducted).
Use Proxy Server: If set to True, the streaming server will be
accessed through a proxy server. Enter its IP address or host name
under Proxy Address. Under HTTP Port, enter the HTTP port used
on the proxy server. The default port number is 8080.
Streaming Duration: The maximum duration of the streaming
session. When this time has expired, the activity will terminate, even if
the whole stream has not yet been played.
Max Interruption Count: Maximum number of interruptions allowed
during the streaming session. If this number is exceeded, the session
is aborted.
Max Single Interruption Length: Maximum duration (in seconds) of a
single interruption. If this duration is exceeded, the session is aborted.
Max Total Interruption Length: Maximum total duration (in seconds)
of all interruptions. If this duration is exceeded, the session is aborted.
Consider Interruption Abort as Failed Measurement: This flag
governs whether a Streaming activity will count as failed if aborted
because of excessive interruption, according to any of the criteria
above.

For HTTP streaming using an on-device client, the following options

appear:
Streaming URL: URL to use for streaming.
Streaming Duration: The maximum duration of the streaming
session. When this time has expired, the activity will terminate, even if
the whole stream has not yet been played.

NT12-10833 ver 4.0 55

TEMS Service Control Script Designer – User’s Manual

3.7. Voice Activities

3.7.1. Dial
Dials a phone number and sets up a (circuit-switched) voice call.
You may instruct the device to retry the call if the call setup fails. The retry
behavior is governed by the On Failure property; see section 3.8.2.
The call duration is specified:
• in a subsequent Voice Quality activity, if voice quality is measured;
• otherwise, most conveniently by means of a subsequent Wait activity.

• Configuration property:

Call Type: In TEMS Symphony 7.4 and TEMS Automatic 10.1, this is
always Default.

Phone Number: The complete phone number to the other call party,
including country code. Valid characters are: +, #, *, 0, ..., 9, and p (for
pause).

3.7.2. Answer
Waits for an incoming (circuit-switched) voice call to arrive and answers it
when it arrives.
• Configuration property:

Call Type: In TEMS Symphony 7.4 and TEMS Automatic 10.1, this is
always Default.

3.7.3. Hang Up
Hangs up a (circuit-switched) voice call.
• Configuration property:

Call Type: In TEMS Symphony 7.4 and TEMS Automatic 10.1, this is
always Default.

56
 Chapter 3. Activities (Reference Chapter)

3.7.4. Voice Quality

Performs audio quality measurement (AQM) including PESQ/POLQA:
• Configuration property:

Algorithm: The algorithm to use for audio quality measurement.

• Nonintrusive: (This option loads the channel with speech, but
currently does not produce any unique measurements.)
• PESQ P862.1: PESQ.
• POLQA P863 Narrowband: POLQA for narrowband speech.
• POLQA P863 Super Wideband: POLQA for super wideband
speech.

Audio Source: The source of the audio whose quality is to be

measured. When this source is external to the PC, the device
physically connected to the PC is meant.
For TEMS Symphony 7.4, this is always Ascom MTP4.
For TEMS Automatic 10.1, this is either Device Digital Audio or
Ascom RMU (the latter option is used with an MDU as well).
The other options are not used.

Call Type:
• M2M: Mobile to mobile. Not supported in TEMS Symphony 7.4.
• M2F: Mobile to fixed.

Duration: The length of time (hh:mm:ss) for which to collect voice

quality measurements.
Store AQM Files: The purpose of this option is to allow you to save
audio files that have received poor MOS scores. Enter the threshold
value under MOS Limit. If the MOS score is lower than or equal to this
threshold, the audio file will be saved along with the logfiles.

3.7.5. Predefined Snippets for Voice

• Synchronized Voice Call Sequence snippet: See section 3.7.5.1.

NT12-10833 ver 4.0 57

TEMS Service Control Script Designer – User’s Manual

3.7.5.1. Synchronized Voice Call Sequence Snippet

This snippet conducts a sequence of voice calls, alternatingly mobile-
terminated (MT) and mobile-originated (MO), between a TEMS product data-
collecting device and a CallGenerator.
At the top level the snippet consists of a sole Synchronized Call Sequence
activity, which in turn encloses the voice call sequence structure. The
Synchronized Call Sequence activity differs from a regular Sequence in that it
imposes various constraints on its contents, as dictated by the requirements
of the voice call sequence.

Sequence Order Call

The snippet starts with a Dial activity making a Sequence Order (SO) call to
the Call Generator. The function of the SO call is to order MT calls from the
CallGenerator and to inform it about the requested call sequence structure as
embodied in the rest of the snippet. These parameters are sent by DTMF
signaling and include:
• Device phone number
• Number of MT calls
• Number of MO calls
• Duration of voice quality measurements
• Interval between voice calls
Voice quality is measured during the SO call itself.

Outer While Loop

The SO call hang-up is followed by an outer while loop which contains two
further while loops inside it: one for MT calls and one for MO calls.

MT Call Loop
The device picks up each MT call by means of the Answer activity, then runs
a Voice Quality activity, which also determines the duration of the call.

MO Call Loop
The device places each MO call by means of the Dial activity and measures
voice quality just as for MT calls.

58
 Chapter 3. Activities (Reference Chapter)

Termination of Call Sequence

When the snippet terminates, for example when the script is stopped, a
Sequence Cancel call is placed to the CallGenerator so that it stops calling.
Unlike the Sequence Order (SO) call, the Sequence Cancel call requires no
configuration of any kind and is not visible in the user interface.

Note: Do not manually abort the Sequence Cancel call; if you do, the
device will keep receiving calls from the CallGenerator.

Constraints on Syntax and Configuration

It is strongly recommended to stick to the Synchronized Voice Call Sequence
snippet and its associated container activity in setting up voice call
sequences, since the setup is somewhat complex and the framework
provided takes care of all necessary validation. The following constraints
apply:
• The Dial activities must (obviously) have the same recipient phone
number, namely, that of the CallGenerator.
• All Voice Quality activities must have identical parameter setups.
• The SO call must come first, then the MT loop, and finally the MO loop.
The MT loop is mandatory; the MO loop, on the other hand, is optional
and can be omitted.
• The MT and MO call loops must take the same total amount of time.
Specifically, MT Voice Quality Duration + MT Wait Duration + 10 s
(estimated time taken by Answer activity) must be equal to MO Voice
Quality Duration + MT Wait Duration.
What you may want to do in terms of modification is to add activities for logfile
recording to the snippet. Besides the activity types found in the predefined
snippet, the following further activities are allowed within the Synchronized
Call Sequence activity:
• Start Recording, Stop Recording

Failure Cases
• If the SO call fails, it is retried practically indefinitely (On Failure 
Retries is set to 10000).
• If an expected MT call from the CallGenerator does not arrive, the snippet
keeps running until the Answer activity has timed out three times, and

NT12-10833 ver 4.0 59

TEMS Service Control Script Designer – User’s Manual

then terminates. If the script has the snippet enclosed within a further
while loop, the snippet will start over with a new SO call.

If the snippet terminates because of some error condition, a Sequence

Cancel call is made to the CallGenerator to inhibit MT calls.

3.8. General Activity Properties

These properties are common to all or many activity types.
Activity-specific properties are covered in sections 3.1–3.5 in connection with
their respective activities.

3.8.1. Activity Section

• Name: Name given to the activity. (Only appears for certain non-editable
activities such as the “root” activity at the bottom of the script.)
• Configuration: Reference to a configuration set of the type associated
with this activity. For example, for FTP Download, an FTP server
configuration set needs to be selected here. The combo box is populated
with all existing configuration sets that fit the activity; if no such
configuration set exists, you need to create one in the Configuration Sets
pane.
• Equipment: The EQ to which the activity is assigned.
• Enabled: True or False. If set to False, the activity is disabled and will not
be performed when the script is run. This is indicated by the activity being
dimmed by a semi-transparent greenish box in the flowchart.

3.8.2. Failure Handling Section

• Abort: This property determines under what conditions the activity will be
aborted.
– Disabled: The activity will execute as long as it takes to complete.
– On Timeout: The activity will be aborted after a fixed period of time,
unless it has already completed before that time. What you indicate
here is thus a maximum duration for the activity.
– On Event: The activity will be aborted if and when one of the specified
events occurs; otherwise it will run to completion.

60
 Chapter 3. Activities (Reference Chapter)

– On Timeout and/or Event: Select this to create a more complex abort

condition in the form of a boolean expression combining On Timeout
and On Event criteria as defined above. Additional fields Condition 1,
Operator (AND/OR), and Condition 2 appear for defining the
boolean expression, which can be expanded recursively.
Note that this property is also possessed by the root activity, in which case
it applies to the entire script.
Compare the Terminate activity, which aborts the whole script with
immediate effect.

• On Failure: This property determines what will happen if an activity fails

(when first attempted).
– Continue Script Execution: If an activity fails, the activity is
abandoned, and the execution proceeds to the next activity in the
workflow branch in question.
– Stop Script Execution: If an activity fails, the activity is abandoned,
and the whole script is terminated.
– Retry: If an activity fails, it will be retried. When you choose this
option, a set of further parameters appear: Retries – the number of
retries; Delay – the time to wait before each retry; On Failure – what
action to take if all retries fail (continue or stop script).

3.9. Configuration Sets

All types of configuration set are associated with a particular service. For that
reason, each configuration set is described in chapter 3 in conjunction with
the activity or activities that use it.

NT12-10833 ver 4.0 61

TEMS Service Control Script Designer – User’s Manual

4. Saving and Sharing Scripts

4.1. Saving a Script to File

To save a script to file, click the Save button on the TEMS Service
Control Script Designer toolbar.

The file will receive the extension .tsc (for “TEMS Service Control”).
The Save Script dialog contains the following options:
• Description: Free-text field where you can optionally enter a description
of the script.
• Format: You can save the script either with or without the configuration
sets it uses.
– Standard: No configuration sets are saved with the script. This means
that changes to a configuration set will automatically propagate to all
scripts that reference it. Choose this option if you are going to use the
script on one PC only. (This is the default setting.)
– Redistributable: All configuration sets referenced in a script are
saved with the script, making the TSC file a self-contained and
independent entity that can be immediately reused on a different PC.
Choose this option if you are going to use the script on several
computers.
To open an existing script stored on file, click the Load button on the
TEMS Service Control Script Designer toolbar.

4.1.1. Tutorial on Porting Scripts between PCs

Follow these steps to share a script and its related configuration sets between
two computers:
• On the “sender” PC:
– Save your script with Format set to Redistributable.
– Export your configuration sets.

62
 Chapter 4. Saving and Sharing Scripts

• On the “receiver” PC (with the above data from the sender available on
some suitable storage medium):
– Import the configuration sets exported from the sender.
– Launch the TEMS Service Control Script Designer.
– Open the sender’s script. The script can now be freely modified on the
receiver PC.

4.2. Saving a Script as an Image

• You can also save the contents of the workflow pane as an image. To this
end, choose File  Save As Image in the TEMS Service Control Script
Designer and select the desired image file format.

NT12-10833 ver 4.0 63

TEMS Service Control Script Designer – User’s Manual

5. Further Functionality in the

TEMS Service Control Script
Designer

5.1. Context Menu in Workflow Pane

The context menu that appears when you right-click in the workflow pane has
functionality that is mostly mirrored in other places: in the regular window
menu and in the Properties pane. The rest is standard Windows functionality,
except the Move Left and Move Right commands which you can use to
change the ordering of activities in a script.
The context menu is especially useful for changing properties (for example
on-failure behavior) of several activities at once. This is most conveniently
done from the context menu:
• Select all of the activities you want to modify by Ctrl + click, then right-click
the selection and choose the desired command from the context menu.

5.2. Zooming the Workflow Pane

In the workflow pane, the mouse pointer by default has the usual point-and-
click function. You can however switch the mouse to zoom mode, where
mouse pointing actions have the effect of zooming the workflow pane in or
out.
After you click the Zoom In button on the window toolbar, mouse clicks
in the workflow pane will magnify its contents in predefined steps. You
can also click and drag to select a portion of the workflow pane that you
want to enlarge.
To reverse the mouse-click zoom function, click the Zoom Out button
on the window toolbar.
To return the mouse to pointing mode, click the Pointer button.

64
 Chapter 6. GSM Scanning

6. GSM Scanning

A note on terminology: GSM radio frequency carriers are sometimes referred

to below as channels for simplicity, although this is a slight abuse of the term.

6.1. RSSI Scanning

6.1.1. Setup of RSSI Scan: General Settings

Technology Set this to “GSM” for GSM scanning.

Band GSM frequency band or bands to scan.

Channels ARFCNs to scan on the selected band. Select all

channels to scan the entire band. There is no limit to
the selectable number of channels.

6.1.2. Setup of RSSI Scan: PCTel

Bandwidth Select whether to perform a regular GSM signal scan

(“Normal”) or a Continuous Wave scan (“CW”). This
setting applies to all channels you select for
scanning. It is not possible to specify the type of scan
for each channel separately.
• Normal: Bandwidth 200 kHz.
• CW: Bandwidth 30 kHz.

BSIC Setting this to Yes causes the phone to decode the

Base Station Identity Code whenever possible. It
should be noted that BSIC decoding is computa-
tionally costly and considerably reduces the sample
rate of the scan.

NT12-10833 ver 4.0 65

TEMS Service Control Script Designer – User’s Manual

C/I Measure- Setting this to Yes causes a subset of the “C/I”

ments information elements to be updated.

System Setting this to Yes causes the scanner to decode

Information System Information messages for the strongest cell.
The scanner must suspend the regular scan in order
to read System Information, and this is therefore
done only once each time the strongest cell changes.

Dwelling Time The length of time the scanner dwells on each BCCH
trying to decode System Information blocks, before
moving on to the next BCCH. Given as a multiple of
12 GSM frames, which translates to 12 × 120 / 26 ≈
55.38 ms. The default is 17 ≈ 941.5 ms.

6.2. Spectrum Analysis

This scanning method shows downlink signal strength as a function of
frequency.

6.2.1. Setup of Spectrum Analysis Scan

6.2.1.1. General Settings

Technology Choose “GSM” for GSM scanning.

Band GSM frequency band to scan.

Start Frequency Low end of the frequency range to be swept by the

scan. Given in MHz.

Stop Frequency High end of the frequency range to be swept by the

scan. Given in MHz.

Resolution Interval between successive scan samples in Hz, the

Bandwidth highest selectable resolution being 5000 Hz. In the
presentation window, the legend pane will list all
samples; the chart, on the other hand, can of course
only distinguish the samples as far as the screen
resolution permits.

66
 Chapter 6. GSM Scanning

6.2.1.2. Context Settings

Number of The number of sweeps on which to base the

Sweeps presented average Rx level. The minimum number
is 1, and the maximum is 16.

NT12-10833 ver 4.0 67

TEMS Service Control Script Designer – User’s Manual

7. WCDMA Scanning

7.1. Pilot Scanning (with SCH Scanning)

This method scans CPICH control channels, scrambled with cell-specific
scrambling codes. Several UARFCNs can be scanned at a time. UARFCNs
and scrambling codes are selected independently of one another.
Where supported, the same method also scans primary and secondary
synchronization channels (P-SCH, S-SCH).

7.1.1. Setup of Pilot Scan: General

Type of The set of scrambling codes to scan on each

Scanning UARFCN is composed in one of two ways:
• Scan selected: Choose this to scan a static set
of scrambling codes on all frequencies defined
under Channels. The same scrambling codes
will be scanned on the CPICH and on the P-SCH
and S-SCH. Up to 128 scrambling codes can be
selected.
• Scan strongest: Choose this to have the N
strongest scrambling codes reported from the
chosen UARFCNs. The scanner automatically
finds the strongest scrambling codes.

Technology Always “WCDMA” for WCDMA scanning.

Band WCDMA frequency band to scan.

Channels Here you set the UARFCNs of the frequencies on

which to scan the CPICH. The allowed range is
dependent on the frequency band.

68
 Chapter 7. WCDMA Scanning

7.1.2. Setup of Pilot Scan: PCTel

Number of Pilots This field appears if Type of Scanning is set to

“Scan strongest”. To scan the N strongest scrambling
codes, enter the value N here (N ≤ 32).

Selected This field appears if Type of Scanning is set to

Numbers “Scan selected”. Enter the scrambling codes you
want to scan.

PN Threshold This is a signal code power threshold (in dB) used for
the Aggregate Ec/Io and Delay Spread
measurements.
If the PN threshold is set too low, the Aggregate Ec/Io
and Delay Spread values will be affected by random
noise more than may be desired. By raising the
threshold you reduce the influence of random noise
correlations, and you will thus be able to discern
multipath and fading effects more accurately. The
setting –20 dB is recommended.

Data Mode It is possible to reduce the amount of data that is

presented and recorded:
• Full means no reduction.
• Sub means that some data is not presented or
recorded.
It should be noted that choosing “Sub” results in a
much faster updating of scan presentations. The
precise meaning of “Sub” depends on the scope of
the scan:
• For “Scan selected”, Time Offset, P-SCH Ec/Io,
S-SCH Ec/Io, and Rake Finger Count are
excluded, as is SIR. (The “SIR” field is disabled in
this case.)
• For “Scan strongest”, only P-SCH Ec/Io and
S-SCH Ec/Io are excluded.

SIR Setting this to Yes causes the scanner to deliver

signal-to-interference ratio (SIR) measurements.

NT12-10833 ver 4.0 69

TEMS Service Control Script Designer – User’s Manual

System Set this to Yes to decode System Information blocks

Information (continuously). With this option selected, a maximum
of 16 scrambling codes can be scanned.
From the SIB decoding, lists of intra-frequency
neighbors can be extracted.

Measurement There are two choices, High Speed and High

Mode Dynamic. These are two algorithms with different
priorities:
• High Dynamic puts the emphasis on accuracy.
Each sample reported by the scanner is typically
based on a measurement 20 ms in length.
• High Speed is faster and accordingly less
accurate. Each reported sample is typically based
on a 10 ms measurement.

Dwelling Time The length of time the scanner dwells on each

scrambling code (cell) trying to decode System
Information blocks, before moving on to the next cell.
Given as a multiple of 40 ms. The default is 50 =
2000 ms.

7.2. RSSI Scanning

7.2.1. Setup of RSSI Scan

7.2.1.1. General Settings

Technology Always “WCDMA” for WCDMA scanning.

Band WCDMA frequency band to scan.

Channels UARFCNs to scan (up to 255). The allowed

UARFCN range is dependent on the band.

70
 Chapter 7. WCDMA Scanning

7.2.1.2. Context Settings

Bandwidth Select whether to perform a regular WCDMA signal

scan (“Normal”) or a Continuous Wave scan (“CW”).
This setting applies to all channels you select for
scanning.
• Normal: Bandwidth 3.84 MHz.
• CW: Bandwidth 200 kHz.

7.3. Spectrum Analysis

This scanning method shows downlink signal strength as a function of
frequency.

7.3.1. Setup of Spectrum Analysis Scan

7.3.1.1. General Settings

Technology Choose “WCDMA” for WCDMA scanning.

Band WCDMA frequency band to scan.

Start Frequency Low end of the frequency range to be swept by the

scan. Given in MHz.

Stop Frequency High end of the frequency range to be swept by the

scan. Given in MHz.

Resolution Interval between successive scan samples in Hz, the

Bandwidth highest selectable resolution being 5000 Hz. In the
presentation window, the legend pane will list all
samples; the chart, on the other hand, can of course
only distinguish the samples as far as the screen
resolution permits.

NT12-10833 ver 4.0 71

TEMS Service Control Script Designer – User’s Manual

7.3.1.2. Context Settings

Number of The number of sweeps on which to base the

Sweeps presented average RSSI. The minimum number is 1,
and the maximum is 16.

72
 Chapter 8. LTE Scanning

8. LTE Scanning

8.1. LTE Signal Scanning

The LTE air interface uses OFDM as modulation method on the downlink.
Synchronization Channels are used for service detection and synchro-
nization, and Reference Signals (RS’s) are used for channel estimation
purposes.
The LTE signal scan provides the following metrics:
• SCH (PCI, PCIG, P-SCH RSSI, S-SCH RSSI, SCHRQ)
• RS (RSRP, RSRQ)
• CINR (SCH CINR, RS CINR)
• CFO
• Time Offset

8.1.1. Setup of LTE Signal Scan: General

Technology Always “LTE”.

Band LTE band to scan.

Channels EARFCNs to scan within the selected LTE band.

Each EARFCN is specified as a number representing
the center frequency of the channel. Up to 12
EARFCNs can be selected.

8.1.2. Setup of LTE Signal Scan: PCTel

With PCTel only Top-N scanning is supported, not scanning of a fixed cell list.

Bandwidth The bandwidth to scan. The bandwidth must be

selected manually.

NT12-10833 ver 4.0 73

TEMS Service Control Script Designer – User’s Manual

Carrier RSSI The RS and SS measurements will be performed

Threshold only if measured Carrier RSSI is above this
threshold.

Top N Here you specify how many cells the scanner should
report; setting the field to N causes the scanner to
return the N strongest cells.

Number of Tx The number of Tx antenna ports to measure on

Antennas (multiple ports for MIMO). The scanner is capable of
detecting this automatically (“Auto Detect”).

Cyclic Prefix The type of cyclic prefix used in OFDM, e.g. “Normal
15 kHz”. The scanner is capable of detecting this
automatically (“Auto Detect”).

Sync Signal Only Synchronization Signal (SS) measurements

Measurement above this threshold will be reported.
Threshold

Reference Only Reference Signal (RS) measurements above

Signal this threshold will be reported.
Measurement
Threshold

Measurement Signal scan measurement mode. One of:

Mode • Wideband
• Wideband + Subband
• Wideband + RF Path
• Wideband + Subband + RF Path
The RF Path option means multipath (MIMO)
scanning. It populates the MIMO scanning
information elements with “Tx1” ... “Tx4” in their
names.
The Subband option refers to subband scanning,
which does not populate any special information
elements. However, all subband measurements
appear in the plain-text decoded scan reports. If this
option is included, the subband settings that follow
become visible in the property grid.

74
 Chapter 8. LTE Scanning

Subband Start Subband start index within the measurement

bandwidth. Must be in the range 0 ... Number of
Subbands – 1.

Number of Number of subbands to divide the measurement

Subbands bandwidth into.

With PCTel SeeGull MX scanners, multiple concurrent LTE signal scans can
be performed, for example on different bands. The output to information
elements remains exactly the same with this setup: All scanned EARFCNs
are presented within the information element range “1st” … “12th”. If a total of
more than 12 EARFCNs are scanned, only the first 12 selected for scanning
are presented.

8.2. RSSI Scanning

8.2.1. Setup of RSSI Scan: General

Technology Always “LTE”.

Band LTE band to scan.

Channels EARFCNs to scan within the selected LTE band.

Each EARFCN is specified as a number representing
the center frequency of the channel. Up to
255 EARFCNs can be scanned.

8.2.2. Setup of RSSI Scan: PCTel

Bandwidth Bandwidth to scan; select a bandwidth from the list.

8.3. Spectrum Scanning

A spectrum scan shows downlink signal strength as a function of frequency.

NT12-10833 ver 4.0 75

TEMS Service Control Script Designer – User’s Manual

8.3.1. Setup of Spectrum Scan: General

Technology Always “LTE”.

Band Select the LTE frequency band to scan.

Start Frequency Low end of the frequency range to be swept by the

scan. Given in MHz.

Stop Frequency High end of the frequency range to be swept by the

scan. Given in MHz.

Resolution Interval between successive scan samples in Hz, the

Bandwidth highest selectable resolution being 5000 Hz. In the
presentation window, the legend pane will list all
samples; the chart, on the other hand, can of course
only distinguish the samples as far as the screen
resolution permits.

8.3.2. Setup of Spectrum Scan: PCTel

Number of The number of sweeps on which to base the

Sweeps presented average RSSI. The minimum number is 1,
and the maximum is 16.

8.4. Enhanced Power Scanning

Compared to the spectrum scan, the enhanced power scan is a higher-
performance scan that provides selective power measurements in the time
and frequency domains.

8.4.1. Setup of Enhanced Power Scan: General

Technology Always “LTE”.

Band LTE band to scan.

Channel EARFCN to scan within the selected LTE band.

76
 Chapter 8. LTE Scanning

8.4.2. Setup of Enhanced Power Scan: PCTel

Bandwidth Bandwidth to scan. One of:

CW: 100 kHz
Normal: 1.4 MHz
Wide Type 2: 3 MHz
Wide Type 3: 5 MHz
Wide Type 4: 10 MHz
Wide Type 5: 15 MHz
Wide Type 6: 20 MHz

Time Period Specifies whether the EARFCN given under Channel

Reference is the minimum, center, or maximum frequency of the
band to be scanned.

Timing Period The scan will start on the nearest Timing Period Mark
Mark with the Timing Period Mark Offset specified. Given
in units of 50 μs. Max: 20000.

Timing Period Time offset in units of 50 μs. Must be less than or

Mark Offset equal to Timing Period Mark.

Measurement Measurement window size in units of 50 μs. Must be

Window larger than 100, or else set to zero which means that
the choice of window size is made by the scanner for
optimal measurement performance.

Number of Bins The number of measurements to make within the

specified band.
If Time Period Reference is set to Center, then the
number of bins must be odd.

Resolution Resolution bandwidth.

Bandwidth

Frequency Step Frequency step size.

Size

NT12-10833 ver 4.0 77

TEMS Service Control Script Designer – User’s Manual

78
 Index

Index

A
Answer activity in scripts
for voice call 56
AQM
for VoIP
obtaining AQM data in TEMS Investigation 57
AT activity in scripts 26
B
Band Lock activity in scripts 26
C
Channel Lock activity in scripts 27
Configuration Sequence activity in scripts 31
control structures in scripts 13
D
Dial activity in scripts
for voice call 56
E
editing settings in 22
Email Receive activity in scripts 48
Email Send activity in scripts 48
enhanced power scanning (LTE) 76
F
Filemark activity in scripts 27
FTP Download activity in scripts 38
FTP Upload activity in scripts 39
G
GSM scanning 65
H
Hang Up activity in scripts
for voice call 56
HTTP Get activity in scripts 41

NT12-10833 ver 4.0 79

TEMS Service Control Script Designer – User’s Manual

HTTP Post activity in scripts 43

I
If--Else activity in scripts 28
IP sniffing
with on-device clients 37, 38
with TEMS product software 37, 38
K
Key Performance Indicators 12
KPIs (Key Performance Indicators) 12
L
LTE scanning 73
M
Measurement Sequence activity in scripts 31
MMS Receive activity in scripts 51
MMS Send activity in scripts 49
N
Network Bandwidth activity in scripts 45
Network Connect activity in scripts 34
Network Disconnect activity in scripts 36
P
Parallel activity in scripts 30
PCTel scanners
WCDMA pilot scanning with 69
pilot scanning (WCDMA) 68
Ping activity in scripts 44
PS Attach activity in scripts 36
PS Detach activity in scripts 36
R
Radio Access Technology Lock activity in scripts 27
RAT lock 27
RSSI scanning
GSM 65
LTE 75
WCDMA 70
S
scanning, GSM 65
RSSI scanning 65
spectrum analysis 66

80
 Index

System Information decoding 66

scanning, LTE 73
enhanced power scanning 76
LTE signal scanning 73
RSSI scanning 75
spectrum scanning 75
scanning, WCDMA 68
CPICH scanning 68
of synchronization channels (SCHs) 68
RSSI scanning 70
spectrum analysis 71
SCH scanning 68
script designer
fundamentals of 1
scripts 22
Answer activity (for voice call) 56
AT activity 26
Band Lock activity 26
basics of creating 5
Channel Lock activity 27
Configuration Sequence activity 31
context menu in workflow pane 64
Control activities 26
Control Flow activities 28
control structures 13
copy--paste 22
data services, setting up 9
Dial activity (for voice call) 56
editing scripts 22
Email Receive activity 48
Email Send activity 48
failure handling properties 60
Filemark activity 27
FTP Download activity 38
FTP Upload activity 39
general activity properties 60
Hang Up activity (for voice call) 56
HTTP Get activity 41
HTTP Post activity 43
If--Else activity 28
if--else constructs 14
IP activities 34

NT12-10833 ver 4.0 81

TEMS Service Control Script Designer – User’s Manual

Measurement Sequence activity 31

Messaging activities 48
MMS Receive activity 51
MMS Send activity 49
moving activities in 22
Network Bandwidth activity 45
Network Connect activity 34
network connection, setting up 8
Network Disconnect activity 36
Parallel activity 30
parallel construct 17
Ping activity 44
porting between PCs 62
PS attach 11
PS Attach activity 36
PS detach 11
PS Detach activity 36
Radio Access Technology Lock activity 27
saving script as image 63
saving to file 62
Scan activities 53
Sequence activity 31
sequences 13
sharing 62
SMS Receive activity 52
SMS Send activity 51
snippets 12
Start IP Sniffing activity 37
Start Logfile Recording activity 28
Stop IP Sniffing activity 37
Stop Logfile Recording activity 28
Streaming activity 54
suppressing parts of 24
Synchronized Call Sequence activity 31
Synchronized Voice Call Sequence snippet 58
Terminate activity 21, 32
UE control 23
validation of 24
Video activities 54
Voice activities 56
Voice Quality activity 57
Wait activity 18, 32

82
 Index

Wait For activity 19

While activity 30
while loops 15
zooming the workflow pane 64
Sequence activity in scripts 31
SFTP
testing setup 39, 41
SMS Receive activity in scripts 52
SMS Send activity in scripts 51
snippets in scripts 12
spectrum scanning
LTE 75
WCDMA 71
Start IP Sniffing activity in scripts 37
Start Logfile Recording activity in scripts 28
Stop IP Sniffing activity in scripts 37
Stop Logfile Recording activity in scripts 28
Streaming activity in scripts 54
Synchronized Call Sequence activity in scripts 31
Synchronized Voice Call Sequence snippet in scripts 58
T
Terminate activity in scripts 32
U
user interface 4
V
Voice Quality activity in scripts 57
W
Wait activity in scripts 32
WCDMA scanning 68
While activity in scripts 30

NT12-10833 ver 4.0 83

   www.ascom.com/tems 

Ascom Network Testing leads the world in

providing best-in-class solutions to
measure, analyze, and optimize mobile
networks.

© Ascom 2014. All rights reserved. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.
The TEMS™ Portfolio offers a complete set of
trusted solutions for drive testing, benchmarking,
monitoring, and analyzing network performance.
These state-of-the-art offerings facilitate the
deployment, optimization, and maintenance of mobile
networks.
We are the industry leader, and our products are
supplied to the world’s top mobile operators, equip-
ment vendors, and professional service providers.

Ascom reserves the right to change specifications without notice. Ascom acknowledges all registered trademarks appearing herein.

Ascom Network Testing Inc.

1943 Isaac Newton Square
Reston, Virginia 20190 | USA
www.ascom.com/tems