Académique Documents
Professionnel Documents
Culture Documents
User's Manual
Contents
Contents
Chapter 1. Introduction
10
10
10
11
11
11
11
12
13
13
14
15
15
16
16
17
17
18
18
18
18
19
19
19
19
20
20
21
21
21
22
22
23
23
24
ii
Contents
35
iii
iv
44
45
46
47
48
50
51
51
53
54
56
57
58
59
60
60
61
61
62
63
64
65
66
67
67
68
68
69
70
70
71
72
74
75
76
78
79
80
81
81
83
84
Contents
Chapter 5. Events
105
128
vi
108
108
108
109
110
114
115
115
116
117
117
118
120
122
122
124
124
124
124
125
126
126
126
127
127
128
128
129
129
130
132
132
132
133
133
134
134
135
Contents
141
Chapter 8. Scripts
148
vii
Chapter 9. Logfiles
181
viii
164
166
166
167
167
169
170
170
170
171
171
172
172
173
175
176
177
178
178
178
179
180
181
182
182
183
183
183
184
187
187
188
Contents
189
205
210
ix
13.2. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3. Setting Up a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4. Connecting the Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5. Running a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6. Recording Scan Data in Logfiles. . . . . . . . . . . . . . . . . . . . . . . . .
212
212
212
213
213
214
210
210
211
211
211
214
214
214
215
216
216
217
217
217
217
218
218
218
219
220
221
222
Contents
224
232
242
xi
248
248
248
249
249
249
249
251
251
252
252
253
254
254
254
255
255
256
258
259
260
xii
260
260
261
261
261
262
Contents
265
269
272
xiii
273
Index
xiv
277
Chapter 1. Introduction
1.
Introduction
1.1.
Tablets
1.2.
Please note that the TEMS Pocket product also exists in various regional
editions, all of which are covered by the product documentation (including this
manual) but are not differentiated there. This means that descriptions of
functionality and external device compatibility are not necessarily applicable
in every single respect to the TEMS Pocket edition you have purchased. Any
restrictions that apply to your edition are indicated in the Release Note
included in the delivery.
1.3.
2.
2.1.
2.1.1.
2.1.2.
YouTube Testing
You can now test download and replay of YouTube video clips in TEMS
Pocket. A newly created action takes care of this task, presenting the footage
in a special free-floating view nailed to the foreground.
A host of new value elements report on the performance of the HTTP
streaming, and a freshly designed progress view keeps you updated on the
unfolding of the YouTube session.
2.1.3.
A new data view displays parameters and data related to RACH signaling
and paging in LTE. It is similar to existing RACH views for WCDMA and
GSM and indicates, among other things:
Preamble settings such as initial Tx Power, power ramping step size, and
maximum number of preambles; during preamble transmission, Tx Power
for current preamble.
2.1.4.
2.1.5.
Cell identities are reported rather infrequently from the network, and only for
serving cells. A new cell caching function in TEMS Pocket makes the
presentation of cell identities more comprehensive by storing all cells that
the device comes across, so that when the same cell reappears later on, its
identities can be displayed immediately. This function operates in both LTE,
WCDMA, and GSM networks.
2.1.6.
2.1.7.
2.1.8.
When testing FTP upload, you can have each transferred file named
dynamically and uniquely instead of using an unchanging static name.
Dynamic file names are composed of the current date and time concatenated
with the device serial number.
2.2.
2.2.1.
TEMS Pocket 13.2 introduced a unique in-building solution for highperformance, multi-technology scanning using an external scanner from
DRT (model name: DRT4311B). This solution offers a significant reduction in
weight and power consumption compared to traditional scanners, and it
removes the need for a cumbersome laptop-based configuration. Simply
hook up the lean and lightweight scanner via USB directly to your TEMS
Pocket smartphone or tablet for a discreet and super-portable scanning
setup, ideal for todays heterogeneous networks and for small-cell/DAS
deployments.
As a first step, TDD and FDD LTE Reference Signal scanning was offered in
TEMS Pocket 13.2. Scans can be either manual or scripted; in either case, as
it is handled by a separate device, the scanning is completely independent
of other TEMS Pocket activities and can run in parallel with any of these.
2.2.2.
Frequency bands:
Throughput categories:
2.2.3.
VoLTE Support
2.2.4.
2.2.5.
2.2.6.
The RAT lock control function was refined in TEMS Pocket 13.2 to permit
locking of the TEMS Pocket device to a subset of multiple radio access
technologies, not just to a single technology. For example, the device can be
allowed to camp on GSM and WCDMA while being prevented from accessing
LTE.
For band lock, the option of locking on more than one band already existed
for LTE and WCDMA but was introduced for GSM as well.
2.2.7.
More ample use is made of cell file data in TEMS Pocket 13.2:
When selecting a cell to lock on, you can search the cell file for parameter
values as well as arbitrary text in cell names. The latter is especially
helpful when you need to identify a cell based on its location. A cell
turned up by the search can be picked as a lock target by a single-tap
operation.
In the RAT lock dialog it is shown for each RAT how many bands and
cells the device supports for that technology. Similarly, for the band lock
function, a cell count is given for each supported band.
2.2.8.
The current RAT string in the data view header was supplemented with an
indication of data mode, meaning the type of bearer currently being used for
data transfer. This can be either a mobile network bearer or Wi-Fi.
The TEMS Pocket data mode indication is much more fine-grained than the
one given on the Android status bar: to give just one example, within WCDMA
it distinguishes all of the following: 3G (non-HS), HSPA, HSPA DC (dual
carrier), HSPA+, HSPA+ MIMO, HSPA+ DC, and HSPA+ DC MIMO.
2.2.9.
2.2.10.
HTTP Post
2.3.
2.3.1.
Frequency bands:
LTE 800 (Band 20), 850 (B5), 900 (B8), 1800 (B3), 2100 (B1), 2600
(B7)
WCDMA 850 (Band V), 900 (VIII), 1900 (II), 2100 (I)
Throughput categories:
GPRS/EDGE Class 12
2.3.2.
Frequency bands:
WCDMA 850 (Band V), 900 (VIII), 1900 (II), 2100 (I)
Throughput categories:
GPRS/EDGE Class 12
2.3.3.
Frequency bands:
WCDMA 850 (Band V), 900 (VIII), 1900 (II), 2100 (I)
Throughput categories:
GPRS/EDGE Class 12
2.3.4.
An external antenna kit is offered with TEMS Pocket on the Sony Xperia
LT25i phone. The device is then permanently fitted with SMA female
connectors on the back of the phone.
With an external antenna you can easily verify previously deployed antenna
solutions, or find faulty cables, using only a mobile device. The antenna kit
also includes a mini-antenna for normal handheld use; the phones internal
antenna, on the other hand, is permanently disabled in this configuration.
The external antenna solution is available with TEMS Pocket Professional
and TEMS Pocket Standard.
2.3.5.
TEMS Pocket 13.1 saw the introduction of a new TEMS Pocket Remote
package on the Android platform. A TEMS Pocket running in Remote
mode can be used as an unattended probe tasked with (for example)
monitoring or benchmarking. The device is then controlled remotely from
Ascoms Fleet Manager and does not expose the regular TEMS Pocket user
interface.
The behavior of a TEMS Pocket Remote device as an autonomous probe can
be flexibly configured on-screen, for example with regard to registration
procedures and measurement data upload.
2.3.6.
10
you populate piece by piece with a mosaic of the value elements you want to
monitor.
You build these custom views from the same types of graphical elements that
make up the predefined views:
Value bars whose length and color represent the current value of a
parameter or measured quantity. The value and unit are also printed as
text on top of the bar.
2.3.7.
The file naming of scripts and map sets created in TEMS Pocket was
changed to a more human-readable format to make files easier to find.
2.3.8.
From TEMS Pocket 13.1 onward, script actions are equipped with maximum/
minimum timers which can optionally be used to control the action
duration. If the action duration reaches the stipulated maximum, the action is
immediately ended. On the other hand, if the action completes in less than
the minimum execution time, TEMS Pocket will wait until the minimum timer
expires and only then continue.
2.4.
The most pervasive change from TEMS Pocket 12.x to 13.0 was that a range
of new phones running Android 4 replaced older phones.
2.4.1.
Frequency bands:
WCDMA 850 (Band V), 900 (Band VIII), 1900 (Band II), 2100 (Band I)
11
Throughput categories:
GPRS/EDGE Class 12
2.4.2.
Frequency bands:
LTE 700 (Band 17), 850 (Band 5), 1700/2100 (Band 4), 1900 (Band 2)
Throughput categories:
GPRS/EDGE Class 12
12
2.4.3.
Frequency bands:
CDMA 800 (BC 0), 1900 (BC 14), 1700/2100 (BC 15)
Throughput categories:
2.4.4.
Frequency bands:
Throughput categories:
13
2.4.5.
14
Frequency bands:
LTE 2100 (Band 1), 1800 (Band 3), 850 (Band 5), 2600 (Band 7), 800
(Band 20)
Throughput categories:
GPRS/EDGE Class 12
Vocoder lock
2.4.6.
Frequency bands:
WCDMA 850 (Band V), 900 (Band 8), 1900 (Band 2), 2100 (Band 1)
Throughput categories:
GPRS/EDGE Class 12
2.4.7.
15
2.4.8.
The Sony Xperia LT25i and LT30a models come with the capability to lock on
one LTE EARFCN (also known as LTE carrier lock). This function further
expands the range of market-unique capabilities which continues to save
TEMS product users untold hours in their daily work.
As operators are beginning to deploy additional carriers in their LTE networks
in order to grow their capacity, LTE EARFCN lock enables them to do so
more accurately, efficiently, and unobtrusively than is possible with alternative
solutions.
Just like previously introduced control functions, the EARFCN lock can be
applied in real time to an individual EARFCN (carrier). One initial reboot of the
device is required to put the device in a state where it prevents or allows
handovers, but when applying the function itself no reboot is needed
unlike other similar solutions, which require a reboot for every EARFCN
change. TEMS Pocket allows the user to combine the locking capabilities
with automated service tests, greatly increasing operational efficiency.
Note: The LTE EARFCN lock offered in TEMS Pocket 13.0 works differently
compared to the WCDMA and GSM carrier lock features.
2.4.9.
Sony Xperia LT25i and LT30a handsets are capable of controlling what
access classes (ACs) they are members of. This feature allows the device
to simulate an AC other than the one originally assigned to the USIM. In this
way, a network can easily be evaluated with devices belonging to different
ACs.
Access classes range from 0 to 15. Of these, 09 are default classes,
whereas membership of ACs 1015 entitles a device to make access
attempts in various special situations: for example, NW access emergency
calls (class 10) and Security service (class 12).
16
In TEMS Pocket, the user can simply check a box for each access class the
device should be included in. Alternative ways to test the full range of ACs
would require multiple different SIM cards and manual configuration of the
handset, and would take significantly longer to set up and test reliably.
2.4.10.
For more than a decade now, the TEMS portfolio has been able to provide a
unique type of locking functionality, designed and developed by Ascom with
network testing specifically in mind. This is something unique in the industry.
In TEMS Pocket 13.0, WCDMA Cell Lock (UARFCN and SC) control
capabilities were introduced on the Sony Xperia LT25i and LT30a phones.
Like other control functions, this one can be applied in real time, and unlike
those offered by some other solutions, its use does not require a reboot of
the device.
It must be noted that in connected mode, WCDMA Cell Lock on Sony Xperia
LT25i/LT30a works somewhat differently than on Sony Xperia arc S LT18i/a
and other older TEMS Pocket devices. In idle mode, on the other hand, the
function is similar. See section 11.6 for further details.
2.4.11.
Mobile-to-mobile POLQA
The entire mobile solution can travel with the user, measuring according
to local conditions.
17
2.4.12.
2.4.13.
Super-Wideband POLQA
From version 13.0 onward, TEMS Pocket calculates POLQA scores for
wideband and super-wideband voice codecs, such as AMR-WB. A 48 kHz
sample rate is applied for all codecs operating with a sample rate higher than
8 kHz.
2.4.14.
Custom events were expanded with boolean logic, which lets the user
combine simple value element conditions (of the form RSSI < 90 dBm) into
complex AND/OR expressions up to five levels deep. A new graphical user
interface is provided for assembling and visualizing event expressions.
Any event can be used to trigger a script, as explained in section 2.4.15.
Custom-made events can thus be set up to have scripts executed, for
example, at specific times of day or in a particular geographical area. All RF
and data throughput value elements are likewise available as building blocks
in custom events.
2.4.15.
18
With scripts configured to run when given conditions are satisfied, TEMS
Pocket can operate in a more unattended manner, allowing users to
automate more of their testing.
2.4.16.
Filemarks
2.4.17.
Map Legend
TEMS Pocket 13.0 displays a color legend on both indoor and outdoor
maps, indicating what measurement is being plotted and the color ranges
used to encode its numerical values. This greatly enhances convenience and
usability.
2.4.18.
Users can access a Quick Guide directly from the Help menu in TEMS
Pocket. This Quick Guide walks new users through fundamental tasks such
as how to record logfiles and navigate in-building environments, and includes
helpful tips on how to operate TEMS Pocket efficiently. In this way beginning
users are able to get started quickly with minimal training.
The TEMS Pocket Quick Guide is available in the same mobile-friendly
format as the embedded Users Manual.
2.4.19.
The TEMS Pocket menu system was reorganized in this release. The new
design reflects Android design guidelines and best practices, and dovetails
with the trend toward fewer or no hardware buttons on recent smartphones.
An action bar with buttons appears at the top of the screen, giving easy
access to the most fundamental and frequently used functions such as script
start/stop, logfile recording, and pinpointing.
19
2.4.20.
In both indoor and outdoor map plotting, RAT-specific value elements are
automatically swapped as the TEMS Pocket 13.0 device switches to a
different RAT. This adaptation takes place with four basic measurement
categories: signal quality, signal strength, RSSI, and physical uplink/downlink
throughput. Specifically, the presentation alternates between the following
value elements:
Technology
Signal
Quality
Signal
Strength
Signal
RSSI
Physical
DL/UL
Throughput
GSM
RxQual
RxLev
RxLev
RLC DL/UL
WCDMA
Ec/N0
RSCP
RSSI
RLC DL/UL
LTE
RSRQ
RSRP
RSSI
PDSCH/PUSCH
CDMA/EV-DO
Ec/I0
Ec
RxPwr
RLP DL/UL
The automatic switching spares TEMS Pocket users the hassle of manually
changing value elements in map plots. Yet another time-saver, this
convenient feature also helps increase the users understanding of the
network technologies.
2.4.21.
All Samsung Galaxy S III TEMS Pocket 13.0 phones1 come with accessories
from the market leader in phone protection. The Otterbox Defender series
offers:
1. Also offered with Samsung Galaxy S4 from TEMS Pocket 13.1 onward.
20
2.4.22.
The following TEMS Pocket 12.x devices are no longer supported from
TEMS Pocket 13.0 onward, being replaced by the new devices in this
release (see sections 2.4.22.4.5 above):
Samsung Galaxy S 4G
Samsung Infuse 4G
HTC Rezound
HTC Vivid
2.5.
2.5.1.
21
2.5.2.
Separate progress view for each testable service; overall progress view
with service status indicators
Audio alerts, popup messages, and map/line chart markers for events and
Layer 3 messages
IP packet capture
2.5.3.
22
Predefined scripts and example map set supplied with TEMS Pocket
2.5.4.
(This release introduced new devices that have since been superseded.)
2.5.5.
23
3.
3.1.
3.1.1.
Data Connection
After running the update service/firmware update, you need to ensure that the
device has a valid data connection. If no data connection is established,
TEMS Pocket will fail to download the license and refuse to start up. If this
occurs, you will be notified by a popup message.
For TEMS Pocket to be able to automatically retrieve product licenses, your
device firewall must allow traffic towards the following hosts:
ascomtems-odm.appspot.com, port 80
ascomtems-g4.appspot.com, port 80
3.1.2.
SIM/CSIM Card
For all TEMS Pocket functions except Wi-Fi scanning and data transfer, the
TEMS Pocket device must have a SIM or CSIM card installed. The
application will start up even if no SIM/CSIM card is present, and some data
(for example, on detected network cells) may appear in the user interface, but
of course no mobile network related services can be used in this situation.
3.2.
The Standard package does not include logfile recording, nor can it be
combined with the indoor pinpointing option. In other respects, the
Standard package is identical with Professional.
24
3.3.
TEMS Pocket also exists in a variety called TEMS Pocket Lite, currently
offered within the Professional product package. TEMS Pocket Lite differs
from the regular TEMS Pocket in that it collects less detailed measurements:
specifically, basic RF and data measurements available from the smartphone
operating system (Android). On the other hand, TEMS Pocket Lite can be
installed on any Ascom-approved and tested Android device.
TEMS Pocket Lite is covered in a separate Users Manual; please refer to this
document for further information on TEMS Pocket Lite.
3.4.
3.5.
Testing using a secure connection through SSL. The SSL license option
is under embargo restrictions and can only be sold to certain countries.
25
3.6.
26
3.6.1.
TEMS Pocket can be configured to launch automatically after the device has
started up. How to do this is described in section 16.1.1.
27
3.7.
3.7.1.
3.7.2.
Action Bar
At the top of the screen, immediately below the Android status bar, is an
action bar with a number of buttons.1 The set of buttons that appears is in
part context-dependent.
From here you can perform all of the actions and configuration tasks referred
to in section 3.7 and also inspect some categories of data.
3.7.3.
In the topmost part of the data view is always shown a set of general data
related to the cellular technology currently in use, as well as a column of
icons reflecting the current status of TEMS Pocket.
1. The action bar replaces the menu accessed from the Menu button in pre13.0 versions of TEMS Pocket.
28
Current RAT
and data mode
Measurements and
parameters for current RAT
CGI or corresponding
data for serving cell
Indicators of
radio quality
TEMS Pocket
status icons
3.7.4.
29
3.7.5.
3.7.6.
Scripts
TEMS Pocket offers the use of scripts for automated testing of various
services. See chapter 8.
3.7.7.
Events
When you run a script in TEMS Pocket, events are generated pertaining to
radio (Layer 3 signaling), device operation, script progress, and more. See
chapter 5.
3.7.8.
Logfiles
You can record data collected by TEMS Pocket in logfiles and replay these
files in TEMS Pocket itself or in TEMS Investigation or TEMS Discovery. See
chapter 9.
3.7.9.
GPS Positioning
TEMS Pocket supports positioning of data in logfiles using either the devices
built-in GPS or an external GPS.
30
3.7.10.
Cell Files
You can import a cell file into TEMS Pocket in order to display cells by name
(rather than by CGI) in data views as well as in the Outdoor Map view. See
chapter 10.
3.7.11.
Control Functions
3.7.12.
TEMS Pocket as implemented on the Samsung Galaxy Note 10.1 LTE (GTN8020) tablet has the same functionality as the mobile phone based TEMS
Pocket applications. However, to make good use of the larger screen, the
tablet user interface is organized differently in some respects. Please turn to
chapter 18 for details.
3.8.
3.8.1.
Logfiles
TEMS Pocket logfiles can be stored either on the internal memory card of the
device (/sdcard) or on an external memory card, if the device has one
inserted. The choice is made in the Settings menu; see section 16.1.4.
Internal storage locations are as follows.
Remote: /sdcard/pocket/logfiles/remote
Agent: /sdcard/pocket/logfiles/
31
3.8.2.
Other Files
Other TEMS Pocket related files are always stored on the internal memory
card, in the following locations:
Routes: /sdcard/pocket/private/waypoints/
Scripts: /sdcard/pocket/private/scripts/
Please note that this file structure cannot be browsed through the TEMS
Pocket user interface (nor from the devices standard user interface; a thirdparty Android app is required). Naturally you can always view the directory
structure by connecting the device to a PC.
3.9.
Language Support
32
3.10.
3.10.1.
Also make sure that data traffic is enabled: Under Settings Wireless
& networks Mobile networks, the Data enabled checkbox must be
checked. (This is the default setting.)
You may need to enable data roaming. This is done under Settings
Wireless & networks Mobile networks, by checking the Data
roaming checkbox.
When you connect a TEMS Pocket device running Android 4.2.2 or later
to the PC, a dialog titled Allow USB debugging? will pop up on the
device screen. Check the box Always allow from this computer, and
tap OK.
3.10.2.
33
3.10.3.
When a device possesses a license for both TEMS Pocket and TEMS
Investigation, the two applications cannot coexist on the device. This means
that:
3.10.4.
License Handling
This section applies to the Sony Xperia phones only. For these devices, a
TEMS Pocket license file resides on the internal memory card. The file is
named TEMS_v1.lic and stored in the root.
For other devices, the internal memory card is unrelated to license handling.
3.11.
You exit the TEMS Pocket application by tapping the Overflow button
and then tapping Exit. See section 3.7.2.
34
4.
Data Views
4.1.
4.2.
You can take screenshots of the data views using the built-in screen capture
function. Whenever you use this function, snapshots are taken of all data
views as well as the currently shown data view header.
Tap the Screenshot button on the action bar twice in rapid succession.
After the first tap, the button turns blue; after the second tap, the device
vibrates briefly, and the screenshots are taken.
Screenshots are transparent, that is, they do not include the on-screen
spider web background. This is in order to minimize the size of the image
files.
Screenshot image files are named according to the pattern yyyy-mmdd_hh.mm.ss_<data view category><sequence no.>_screenshot.png, for
example 2013-03-19_14.28.57_Data1_screenshot.png.
If you take screenshots while a logfile is being recorded, you can opt to save
the screenshots in the logfile (*.trp) along with its other contents. You are
35
4.3.
In some data views you can perform an action relating to a piece of data
shown in the view. For example, in data views listing cells, you can lock on
one of the cells.
Specifics on data view actions are found in sections 4.74.13.
4.4.
The data views are divided into the categories found on the overview page
(section 3.7.1). On entering a data view, you can browse the data views
within the same category by swiping left and right. You can also browse to an
adjacent data view category by swiping up or down; the name of the target
category then appears briefly at the bottom of the screen. TEMS Pocket
remembers which data view was last displayed in each category; when you
return to a category, that view is shown.
There is no wraparound when browsing through data views and data view
categories (i.e. neither horizontally nor vertically).
The arrays of indicators along the top and left-hand edges of the data view
are used to show the position of the current view in the category structure just
explained. The vertical indicator shows what data view category you are
currently in, and the horizontal indicator shows the position of the current data
view within that category, counting only views that belong to the cellular
technology the device is currently using. See the example below.
36
The list that follows covers all TEMS Pocket 13.3 data views that exist; please
note that most TEMS Pocket devices do not display all of these, since most
devices do not support all of the technologies involved. Refer to section 4.4.1
for details.
Data View Name
Displayed Contents
Ref.
Idle category
GSM Cell List
4.7.1
4.7.2
4.7.3
4.7.4
4.7.5
37
Displayed Contents
Ref.
4.7.6
LTE Cell
Configuration
4.7.7
4.7.8
4.7.9
GSM Dedicated
Mode
4.8.1
GSM RACH
Analysis
4.8.2
WCDMA Dedicated
Mode
4.8.3
WCDMA RACH
Analysis
4.8.4
LTE Dedicated
Mode
4.8.5
4.8.6
CDMA Perform
4.8.7
EV-DO Perform
4.8.8
Dedicated category
38
Displayed Contents
Ref.
Scanning Status
4.9.1
4.9.2
GPRS/EDGE Data
4.10.1
GPRS/EDGE RLC
Throughput
4.10.2
HSPA Data
4.10.3
HSPA RLC
Throughput
4.10.4
HSDPA Modulation/
Packet Data
Performance
4.10.5
LTE Data
4.10.6
LTE PHY
Throughput
4.10.7
PDP Context
Information
4.10.8
RLP Throughput
4.10.9
Script Progress
4.11.1
AQM Progress
4.11.2
Scanning category
Data category
39
Displayed Contents
Ref.
Email Progress
4.11.3
FTP Progress
4.11.4
HTTP DL Progress
4.11.5
HTTP UL Progress
4.11.6
Logfile Upload
Progress
4.11.7
Ping Progress
4.11.8
SMS Progress
4.11.9
Voice MO Progress/
Voice MT Progress
4.11.10
YouTube Progress
4.11.11
Location category
Indoor Map
See chapter 6.
Outdoor Map
See chapter 7.
GPS
4.12.3
Wi-Fi
4.13.1
4.13.2
Wi-Fi category
Custom category
(Five empty
placeholders)
User-customized views.
4.14
Layer 3 category
Layer 3 Messages
40
4.15.1
4.4.1.
Samsung
H.
L.
Idle category
GSM Cell List
GSM Cell Line Chart
WCDMA Cell List
WCDMA Cell Line Chart
LTE Cell List
LTE Cell Configuration
LTE Cell Line Chart
Scanning category
Scanning Status
LTE scan views
41
Sony
Samsung
H.
L.
Data category
GPRS/EDGE Data
GPRS/EDGE RLC Thput
HSPA Data
HSPA RLC Throughput
HSDPA Mod./Pkt Data Prf.
LTE Data
LTE PHY Throughput
PDP Context Information
RLP Throughput
4.5.
In the topmost part of the view is always shown a selection of data related to
the cellular technology and data bearer currently in use.
42
4.5.1.
The leftmost part of the header displays two strings. On the right, in upright
(non-italic) type, is a RAT indicator showing what radio access technology the
device is currently using. On the left, written smaller and in italics, is shown
the current data mode, meaning the type of bearer being used for data
transfer. The latter can be either a mobile network bearer or Wi-Fi.
Here is the full list of RAT and data mode designations that can appear:
4.5.1.1.
4.5.1.2.
Data Modes
GPRS
EDGE
HSPA
HSPA+
HSPA+ MIMO
HSPA+ DC
HSPA+ DC MIMO
RATs
4G
1X (1xRTT)
43
4.5.2.
All data shown in the header pertains to the current serving cell.
CI: Serving cell Cell Identity, 16 bits, decimal (= C-Id: 3GPP 25.401,
section 6.1.5)
If a cell file is loaded, the CGI parameters are replaced by the cell name. You
can then tap and hold this section of the screen (or, better, to the left or right
of it to avoid obstructing the view) in order to display CGI instead. The
presentation reverts to cell name once you release your finger.
You can change the display format for some of these parameters by longpressing them; see section 16.2.
Indicators (see also color key below)
44
4.5.3.
Green
Yellow
Red
0 ... 9
10 ... 19
20 ... 31
1 ... 4
5 ... 7
75 ... 10
94 ... 76
120 ... 95
100
91 ... 99
0 ... 90
All data shown in the header pertains to the current serving cell or active set.
SC: Scrambling Code of serving cell (idle mode) or strongest active set
member (connected mode)
CI: Serving cell Cell Identity, 28 bits, decimal (= UC-Id: 3GPP 25.401,
section 6.1.5)
If a cell file is loaded, the CGI parameters are replaced by the cell name. You
can then tap and hold this section of the screen in order to display CGI
instead. The presentation reverts to cell name once you release your finger.
You can change the display format for some of these parameters by longpressing them; see section 16.2.
45
BLER: Block Error Rate in percent, average taken over all downlink
transport channels (DCH only)
Green
Yellow
Red
TxPower (dBm)
31 ... 0
1 ... 9
10 ... 50
Ec/N0 (dB)
10 ... 0
15 ... 11
34 ... 16
85 ... 15
99 ... 86
0 ... 20
21 ... 49
50 ... 100
RSCP (dBm)
BLER (%)
4.5.4.
All data shown in the header pertains to the current serving cell.
46
CI: Serving cell Cell Identity, 28 bits, decimal (= UC-Id: 3GPP 25.401,
section 6.1.5)
If a cell file is loaded, the CGI parameters are replaced by the cell name. You
can then tap and hold this section of the screen in order to display CGI
instead. The presentation reverts to cell name once you release your finger.
You can change the display format for some of these parameters by longpressing them; see section 16.2.
Indicators (see also color key below)
Green
Yellow
Red
30 ... 10
9 ... 14
15 ... 30
30 ... 10
9 ... 14
15 ... 30
9 ... 0
23 ... 10
30 ... 24
RSRP (dBm)
70 ... 40
99 ... 71
BLER DL (%)
0 ... 20
21 ... 49
50 ... 100
RSRQ (dB)
4.5.5.
All data shown in the header pertains to the current active set.
47
PN: PN Offset of serving cell (idle mode) or strongest active set member
(active mode)
If a cell file is loaded, the SID and NID parameters are replaced by the cell
name. You can then tap and hold this section of the screen in order to display
SID/NID instead. The presentation reverts to cell name once you release your
finger.
Indicators (see also color key below)
Green
Yellow
Red
TxPwr (dBm)
31 ... 0
1 ... 9
10 ... 50
Ec/Io (dB)
9 ... 0
23 ... 10
32 ... 24
15 ... 10
24 ... 16
64 ... 25
FER (%)
0 ... 2
3 ... 5
6 ... 100
PER (%)
0 ... 2
3 ... 5
6 ... 100
FES (dBm)
4.5.6.
A column of icons appears on the far right in the data view header. These
icons give a quick overview of:
48
script execution
GPS status
logfile recording
Generally speaking, the icons give an indication of what last happened. They
do not provide comprehensive information but should be seen as a
complement to the data views.
Script Icon
Symbol
Meaning
green
red
yellow
No script is running.
GPS Icon
Symbol
Meaning
green
red
The GPS selected for use with TEMS Pocket is currently not
delivering valid coordinates.
yellow
Meaning
green
red
yellow
49
Control Icon
This icon appears only on devices where TEMS Pocket offers control
functions.
Symbol
Meaning
green
red
yellow
When no TEMS Pocket data view is being displayed, those icons that are red
or green will instead appear on the status bar at the top of the screen. When
you swipe down from the status bar, a drop-down notification (reading simply
TEMS Pocket) appears for each icon.
4.6.
You can always return to this screen by tapping the Back button
(possibly several times if you are navigating the menu system).
50
4.7.
4.7.1.
S: Serving cell
N: Neighbor cell.
Lock on one or several cells listed in this view. The device is then
restricted to camping on these cells alone.
Prevent one or several cells listed in this view. The device is then
prevented from camping on these cells.
Tap and hold a cell to bring up a context menu
with data view actions.
51
You can add more cells to the set locked on or prevented. Just tap and hold
any cell in the list as shown above.
Any actions applied in this way are also immediately reflected in the control
function settings, described in chapter 11.
If a cell that you locked on has disappeared from the GSM Cell List view, and
you want to release that lock, you can always do this from the Control
Functions menu as described in section 11.7.2.
52
4.7.2.
53
4.7.3.
M: Monitored neighbor
D: Detected neighbor.
You can lock on a cell or UARFCN that is listed in this view. The phone is
then restricted to camping on that cell/UARFCN.
Tap and hold a cell to bring up a context menu
with data view actions.
54
UARFCN lock
Any action applied in this way is also immediately reflected in the control
function settings, described in chapter 11.
55
4.7.4.
56
4.7.5.
S: Serving cell
M: Measured neighbor.
57
4.7.6.
58
4.7.7.
59
4.7.8.
A: Active set
C: Candidate set
N: Neighbor set.
4.7.9.
This view has exactly the same contents as the CDMA Cell List view (see
section 4.7.8) but for EV-DO cells.
60
4.8.
4.8.1.
61
4.8.2.
62
(continued)
Paging Group: The mobiles paging group.
3GPP 45.002, sections 6.5.2, 6.5.6,
PAGING_GROUP
4.8.3.
63
4.8.4.
64
4.8.5.
65
4.8.6.
66
4.8.7.
<technology> = CDMA
4.8.8.
<technology> = EV-DO
67
4.9.
4.9.1.
68
4.9.2.
69
4.10.
4.10.1.
70
4.10.2.
Line chart
This line chart tracks RLC/MAC-level data
throughput over the past 60 seconds: uplink
(blue), downlink (red).
The value on the far left indicates the
maximum value on the y-axis. The values on
the right are those of the latest data points
plotted.
71
4.10.3.
72
(continued)
QPSK/16/64QAM: Percentage distribution of
downlink modulation scheme usage: QPSK
(left), 16-QAM (center), 64-QAM (right).
Updated once every second.
E-DCH:
73
4.10.4.
Line chart
This line chart tracks RLC-level data
throughput over the past 60 seconds: uplink
(blue), downlink (red).
The value on the far left indicates the
maximum value on the y-axis. The values on
the right are those of the latest data points
plotted.
74
4.10.5.
75
4.10.6.
Port5 SISO
76
(continued)
Timing Advance: Timing Advance; 3GPP
36.321, section 5.2. Multiply this value by 16 to
determine the Timing Advance Index, which
has the range {0 ... 63}: 3GPP 36.213, section
4.2.3. Each Timing Advance Index increment
represents 0.52 s.
PDSCH BLER: Block error rate on Physical
Downlink Shared Channel.
PDSCH Resource Blocks: Number of
resource blocks on PDSCH.
PDSCH MCS CW 0: Modulation Coding
Scheme for code word 0 on PDSCH. The
range is {0 ... 31}, with higher values indicating
larger transport block size and higher-order
modulation. 3GPP 36.213, section 7.1.7.1
PDSCH MCS CW 1: Modulation Coding
Scheme for code word 1 on PDSCH.
PDSCH Throughput: Throughput on Physical
Downlink Shared Channel. Updated once
every second.
PUSCH Throughput: Throughput on Physical
Uplink Shared Channel. Updated once every
second.
PUSCH MCS CW: Modulation Coding Scheme
on PUSCH. The range is {0 ... 31}, with higher
values indicating larger transport block size
and higher-order modulation. 3GPP 36.213,
section 7.1.7.1
77
4.10.7.
Line chart
This line chart tracks PUSCH throughput (blue)
and PDSCH throughput (red) over the past 60
seconds.
The value on the far left indicates the
maximum value on the y-axis. The values on
the right are those of the latest data points
plotted.
78
4.10.8.
NSAPI/EBI:
LTE
For the header, see sections
4.5.24.5.4.
79
Note: PDP context data is not reported on a regular basis, but only in
connection with PS attach. Since the device performs this attach
at power-on whenever possible, it will already have taken place
when TEMS Pocket is launched, and the above data view will
then not display any information. However, one way to elicit PDP
context data in this view is to switch the device to flight mode and
then back.
4.10.9.
80
4.11.
This data view shows the progress of the script that is currently running, if
any. When you stop the script, this view is cleared, and all counters are reset.
The other data views in this category contain action-specific progress and
service performance data. For certain action types, a graph is plotted
which scrolls from right to left in real time.
Line charts always show the latest 60 seconds of execution time for the
action type in question.
How to compose scripts is explained in chapter 8.
4.11.1.
81
(continued)
Repetitions: Index of current repetition of
action / Total number of repetitions to perform
(Repeat action parameter in script setup).
Next Action: Next action in script (no
wraparound: - is shown while last action is
executed).
Script action type buttons
Tap one of these buttons to jump to an actionspecific progress view (they are described in
sections 4.11.24.11.10). When an action of a
particular type is executing, the corresponding
button is tagged with a play symbol.
Furthermore, the buttons are color-coded in a
similar way as the status icons (described in
section 4.5.6):
82
4.11.2.
83
4.11.3.
Inactive
Preparing
Connecting
Logging In
Sending
Quitting
Finished
Aborting
84
4.11.4.
4.11.5.
85
4.11.6.
4.11.7.
86
4.11.8.
87
4.11.9.
88
89
90
(continued)
Bytes Received: Total number of bytes
received at TCP level. (The sum is taken over
all video streaming data streams and can vary
between different replays of the same video.)
Average/System Max Bitrate: Average and
maximum downlink TCP throughput. The
maximum is only shown at session end.
Graph
Line chart of downlink TCP throughput.
4.12.
4.12.1.
This view is not a regular data view, but it is included in the Location category.
See chapter 6.
4.12.2.
This view is not a regular data view, but it is included in the Location category.
See chapter 7.
91
4.12.3.
In a script, the use or non-use of GPS data is set in the general script
properties; see section 8.2.1.
Manually, you can turn the GPS on and off by tapping the Actions
button and selecting Turn On GPS or Turn Off GPS.
Regarding GPS use with TEMS Pocket generally, see chapter 15.
92
4.13.
4.13.1.
93
4.13.2.
S: Serving
N: Neighbor.
94
4.14.
This data view category holds empty data views whose contents you pick and
choose yourself in any way you like. With the exception of bar charts, custom
views are built from the same types of graphical elements that make up
predefined views: line charts, value bars, values in text format, and static
(descriptive) text labels.
Up to five custom views can be populated.
4.14.1.
A grid of cells becomes visible. This grid is just an editing aid and is hidden
again when you leave edit mode.
95
96
4.14.1.1.
Chart Settings
4.14.1.2.
Label Settings
97
4.14.1.3.
4.14.1.4.
98
4.14.2.
Example
In this custom view, a selection of HSDPA and
HSUPA value elements have been assembled,
with the FTP server IP used for testing added
at the bottom.
All types of custom view building blocks are
represented here (most of them more than
once):
1. Chart (with legend, grid, and labeled
axes)
2. Value bar
3. Value label (with prepended value
element name)
4. Label
4.14.3.
Tap the Actions button and toggle Edit View on, if it is not turned on
already.
To edit the contents of a building block, simply tap it and the applicable
dialog in section 4.14.1 will appear.
To delete a building block, tap it in the
view, then tap the Delete button in the
top right corner of the settings dialog.
99
4.14.4.
100
4.15.
4.15.1.
101
Message category
Message
direction:
uplink
downlink
4.15.1.1.
Timestamp, 1 ms
resolution
Channel on which
message was sent
LTE
102
CDMA
Note: These designations are channel types, but are displayed on the
far right as message categories. The channel field in the middle is
empty for CDMA.
EV-DO
Authentication
Encryption
Idle State
Key Exchange
Physical Layer
Route Update
Security
103
Stream
Stream0
Stream1
Stream2
Stream3
Virtual Stream
4.15.1.2.
When you tap a Layer 3 message, its contents are displayed in plain-text
decoded format.
In all mobile phone implementations of TEMS
Pocket, the plain-text decoding is displayed
inline as an expansion of the Layer 3 message
list item. On tablets, however, the plain-text
decoding is displayed separately to the right of
the message list (see chapter 18).
4.15.1.3.
To clear the message list, tap the Actions button and select Clear
History.
The message list can hold up to 1,000 messages. After this number is
exceeded, the oldest message drops out as a new one enters. While the view
is frozen, up to 999 messages can be buffered for later presentation. Any
messages in excess of that number will not appear when the view is released
(but in a logfile, all messages are always recorded).
104
Chapter 5. Events
5.
Events
Radio events
Custom events
5.1.
Event Log
To view events that have occurred, tap the Settings button and select
Event Log.
Events are listed in chronological order with
the most recent event on top.
To view details of an event, tap it in the event
log. The log item is then expanded to also
display event parameters: see the FTP Start
event in the screenshot.
You refresh the event log manually as
described in section 5.1.1. There is no
automatic refresh.
The event log can hold a maximum of 500
events. After this number has been reached,
the oldest event is deleted from the log
whenever a new event occurs.
The event log is cleared automatically every time you start TEMS Pocket. You
can also clear the event log manually at any time: see section 5.1.2.
105
5.1.1.
To refresh the event log, tap the Overflow button and select Refresh
log.
5.1.2.
To clear the event log, tap the Overflow button and select Clear log.
5.2.
Besides being listed in the event log, events can be presented in a number of
other ways. This is configured in the Event Configuration menu.
The same range of additional presentation options are in fact also available
for Layer 3 messages (that is, besides listing them in the Layer 3 Messages
data view).
Tap the Settings button and select Event Configuration.
106
Chapter 5. Events
Each of these presentation options (other than the event log) is exemplified in
the subsections that follow.
To revert to the default settings for all events, do the following at the top level
in the Event Configuration menu:
Tap the Overflow button and select Reset.
5.2.1.
5.2.2.
5.2.3.
5.2.4.
107
5.3.
This section lists all events that are predefined in TEMS Pocket, along with
their parameters where applicable. More detailed descriptions are provided
for call events and other events that require it.
5.3.1.
Radio Events
5.3.1.1.
Call Events
Description/Parameters
Call abnormally ended prior to Call Established
event (for example because all traffic channels
were busy).
Parameters: CC cause
Call Attempt
Call End
Call Established
Call Setup
108
Chapter 5. Events
Event Name
Dropped Call
Description/Parameters
Call ended abnormally after Call Established
event.
Parameters: Cause
5.3.1.2.
Event Name
Cell Changed
Description/Parameters
The device changed to a different cell within the
same RAT and on the same channel/carrier.
Parameters:
Channel Changed
System Changed
109
5.3.2.
Session Events
Among these events, all End events imply successful completion of the
session.
Event Name
Parameters/Notes
AQM Start
AQM End
AQM Error
Cause
Email Start
Email End
Email Error
FTP events: These are triggered both by FTP service testing and by logfile
upload over FTP.
FTP Start
FTP End
FTP Error
URL
HTTP End
110
Chapter 5. Events
Event Name
HTTP Error
Parameters/Notes
Cause
Note: This event is also generated during a
Voice + Data action when an HTTP session is
terminated on voice call end.
HTTP Upload events: These are triggered both by HTTP Post service
testing and by logfile upload over HTTP.
HTTP Upload Start
Idle Start
Idle End
(No parameters)
Idle Error
IP Capture Start
(No parameters)
IP Capture End
Logfile Start
(No parameters)
Generated for all types of logfile recording.
Logfile Stop
(No parameters)
Generated for all types of logfile recording.
Parallel Execution
Start
Parallel Execution
End
Parallel Execution
Error
111
Event Name
Parameters/Notes
Ping Start
Ping End
Ping Error
Scan Start
Connect method
Scan End
(No parameters)
Scan Error
Cause
Script Start
Script name
Script Iteration
Script End
SMS Start
SMS End
SMS Error
Cause
Upload Start
Upload End
(No parameters)
Upload Error
112
Chapter 5. Events
Event Name
Parameters/Notes
Voice Start
Dialed number
Voice End
(No parameters)
Voice Error
Cause
VoiceData Start
(No parameters)
VoiceData End
(No parameters)
Success criteria for the Voice + Data action are
given in section 5.3.2.2 below.
VoiceData Error
Cause
Note: This event is (of course) not generated
when Stop at voice end is set and the data
session terminates prematurely although the
latter occurrence does trigger an FTP Error/HTTP
Error event. See also the table in section 5.3.2.2.
Voice MT Start
Voice MT End
Call duration
Voice MT Error
Voice MT Call
Received
Caller id
Wi-Fi Enable
(No parameters)
Wi-Fi Disable
(No parameters)
YouTube Start
Video id
Generated at start of action.
YouTube End
(No parameters)
YouTube Error
Cause
113
Event Name
YouTube Video Start
Parameters/Notes
(No parameters)
If the script action points to a non-existent
YouTube video, the cause is stated as Internal
error.
(No parameters)
5.3.2.1.
The outcome of the Parallel action depends on how the Abort condition
parameter is set (see section 8.4.2) and on the outcomes of the individual
services run:
Abort Condition
Service Result
Parallel Result
No failures
Success
Failure
Success
Failure
Success
Failure
No service succeeded
Failure
No failures
Success
Failure
114
Chapter 5. Events
5.3.2.2.
The outcome of the Voice + Data action depends crucially on how the Stop at
voice end flag (see section 8.4.1) is set:
Stop at Voice End
Voice Result
Data Result
On
Success
Success
Success
Running1
Success
Failure
Failure
Failure
Dont care
Failure
Success
Success
Success
Failure
Dont care
Failure
Dont care
Failure
Failure
Off
after voice
finished
after both
finished
1. That is, the data session is still running when the voice call completes.
5.3.3.
System Events
Description/Parameters
Battery Low
External Scanner
Connected
External Scanner
Disconnected
GPS Connected
GPS Disconnected
115
Event Name
Description/Parameters
5.3.4.
Event Name
Filemark
116
Description/Parameters
The user inserted a filemark into the logfile being
recorded. The filemark text is carried as an event
parameter. See section 9.5.
Chapter 5. Events
5.4.
Custom Events
Besides the predefined events, you can create your own custom-made
events which are based on TEMS Pocket value elements satisfying given
conditions. Such conditions can be combined into complex boolean
expressions.
5.4.1.
117
5.4.1.1.
118
When the value element goes above the threshold, the event is triggered
once at that time.
Chapter 5. Events
The function of the hysteresis is to introduce a degree of inertia into the event
generation, avoiding a profusion of events (ping-pong effect) in case of
rapidly fluctuating measurement values.
See the diagram below for an illustration.
Event trigger condition: ve > thr with hysteresis Hyst
ve
thr
thr Hyst
no more events
event
triggered
once
time
event reenabled
event
triggered
once
In more complex event trigger expressions, like the ones created in section
5.4.1.2, the application of the hysteresis is somewhat less straightforward.
Section 5.4.2 discusses this issue further.
119
5.4.1.2.
A single value element condition like the one set up in section 5.4.1.1 is a
perfectly valid custom event in its own right. However, it is also possible to
build more complex event triggers in the form of boolean expressions
involving multiple conditions. The supported boolean operators are AND and
OR.
To expand a condition C1 into a boolean expression of the form (C1
<boolean operator> C2), where C2 is another condition, select the
condition C1 and tap the Make sub button.
The boolean operator is by default set to AND,
and the new condition (red) is appended below
the existing one.
If you nest boolean expressions, the operator
at the next level will default to OR, the third to
AND, etc., automatically building the
alternating pattern of a boolean expression that
contains no redundancy. (However, if you edit
an operator later on, other operators in the
event expression will not adjust automatically
in any way.)
To change an operator, tap it, then tap
Edit and make a new selection.
Proceed to define the new condition just as in
section 5.4.1.1.
120
Chapter 5. Events
By repeatedly applying the Add and Make sub operations you can assemble
any AND/OR expressions you like, up to a maximum depth of five nested
boolean operators. Wherever the maximum depth has been reached, the
Make sub button is grayed out.
Below is an example of a composite event expression:
Stated informally, we want to trigger this event
if the device is on either LTE or WCDMA, and
the signal quality and the throughput are both
too low; but only if this occurs before 6 p.m.
121
It is worth noting that if you like, you can construct the entire logical structure
first, and then proceed to fill in the conditions:
In this screenshot we have begun defining the
event trigger by setting up the same boolean
expression as in the previous example. What
remains is to enter a value element condition in
each of the red fields.
5.4.1.3.
5.4.1.4.
122
Chapter 5. Events
123
In this last example, if you delete the AND operator instead, the whole AND
subexpression will go away. Moreover, once again the OR will lose one of its
operands, so the OR will be removed as well. Only a lone WCDMA condition
will remain in this case.
5.4.1.5.
5.4.2.
5.4.2.1.
5.4.2.2.
After a composite event expression has evaluated to true and triggered its
event, the event will not be triggered again until the expression has turned
false and then true once more. Note carefully that this applies to the
expression as a whole; for example, if a composite expression has an OR at
124
Chapter 5. Events
the top level and has just evaluated to true, its event triggering will not be reenabled until after both members of the OR expression have been false at the
same time at some point.
true
false
C1
C2
C
time
event
triggered
once
5.4.2.3.
event reenabled
event
triggered
once
When the total expression becomes true, all conditions that are logically
true at this point have their hystereses enabled, so that they do count in
evaluating the conditions. Each hysteresis remains enabled until the
hysteresis criterion is satisfied at some point (x < y Hyst or the
equivalent thereof). After this has occurred, that particular hysteresis is
disabled (independently of all other hystereses).
The above process begins anew after the total expression has toggled to
false and then back to true again.
125
5.4.3.
The same range of presentation options exist for custom events as for
predefined events. See section 5.2.
In the event log, a custom event take as parameters the value element or
elements that caused the event expression to become true, and their values
at that time. Below is an example.
5.4.4.
5.5.
You can export the current presentation settings (covered in section 5.2) for
events and Layer 3 messages. The export also includes the definitions of any
custom events currently defined (see section 5.4).
The export always encompasses all events and messages; it cannot be done
selectively.
When TEMS Pocket is upgraded, a settings export is done automatically
before the old version is uninstalled. After installation of the new version, the
settings are imported back into the application.
126
Chapter 5. Events
5.5.1.
Exporting Settings
5.5.2.
Importing Settings
Note: When you import settings, all of the old settings are overwritten.
You are warned about this by an on-screen message. Note
especially that any existing custom events are deleted and
replaced by those present in the .pes file (if any).
To perform the import:
Tap the Settings button and select Event Configuration.
Tap the Overflow button and select Import.
The event settings files stored on the device
are listed. Select which one of them to import.
127
6.
Note: The Indoor Map view and the pinpointing function require a
special license option.
6.1.
You use the Map Editor to create and configure TEMS Pocket map sets.
6.1.1.
128
Map set
B1
B2
...
Bn
Buildings
Maps
6.1.2.
6.1.3.
Tap Name and enter a name for the new map set.
Now for each building to be covered by the map set, do the following:
Tap Buildings.
Tap the Overflow button and select Add Building.
You are now invited to pick an image to use as a map. Select your floor
plans or other background images that you want to use. The selected
image files are added to the map set. A map set can contain up to 99
images.
129
Map sets are saved in the iBwave container format (extension .ibwc). These
files are self-contained and can easily be transferred to other devices. Map
sets are saved to the directory specified in section 3.8.
It is also possible to store a logfile (*.trp) containing a map set in the map set
directory, and then load it into the Indoor Map view just like a map set
(*.ibwc), as described in section 6.2.
6.1.4.
You can set some position properties and other metadata for the map set.
If you are not already in the Map Editor:
Tap the Settings button and select Map Editor.
A list of the map sets you have already created appears.
130
131
6.1.4.1.
Reference points in TAB files must be at least three in number and must not
lie in a straight line. For best accuracy, the points should be distributed in
such a way that they span as large an area as possible. Choosing points that
are near-collinear or very close together may introduce a large source of error
in the positioning. To achieve accurate positioning of measurements, it is of
course also essential that the mapping between pixel coordinates and
latitude/longitude values in the TAB file be carefully done.
6.1.5.
If you tap and hold a map in a map set, a menu with the choices Move up,
Move down, and Delete appears.
Use the move commands to move the map one step up or down in the
map set.
Use the Delete command to delete this map from the map set.
6.2.
At the outset the Indoor Map view is empty. A grid is drawn in the view when
no map set is loaded.
Here is how to load a map set into the Indoor Map view:
Tap the Actions button and select Load Map Set.
132
Select the desired map set and tap Load. The map set now loads in the
Indoor Map view.
6.3.
6.3.1.
Fundamentals of Pinpointing
133
6.3.2.
While a script is running, pinpointing is disabled. You must stop the script
first. (On the other hand, you can start a script while the pinpointing
function is active; however, the logfile recording normally triggered by the
script is then suppressed. Only the pinpointing function will produce a
logfile in this case.)
While pinpointing is active, you cannot swap maps; that is, you cannot
move from one image in the map set to another.
6.3.3.
You can optionally have markers plotted along your route which are colorcoded according to a selected piece of RF data or throughput rate (value
element). The route markers constitute a separate map layer which can be
shown or hidden; see section 6.5.
The color coding of the markers is the same as that used for the value
element in data views. The range of colors employed is shown in the map
legend (see section 6.4); a complete listing of value element color ranges is
given in appendix B.
What you select for map plotting is a family of value elements, one for each
radio access technology, where all elements denote the same fundamental
quantity such as signal strength. As the TEMS Pocket device switches
between technologies, the map presentation automatically follows suit,
always showing the value element that belongs to the currently used
technology.
The feature is customized as follows:
Tap the Actions button and select Select Value Element.
134
Tap Select.
6.3.4.
Manual Pinpointing
135
136
6.3.5.
6.3.5.1.
Load the map set you are going to use, if it is not loaded already.
A dialog appears with the message Save all mapset changes and start
route editor?. Tap Yes.
The user interface now switches to the Indoor Map view, and you proceed to
create your planned route by placing waypoints exactly as when doing
137
manual pinpointing (see section 6.3.4). The only difference consists in how
the task is concluded:
When you have completed your route, tap the Actions button and
select Save Route Changes.
The new route is now stored with the map as a file with extension *.ppf.
(Selecting Discard Route Changes instead will discard all the route
waypoints that you have just defined. The route itself remains, but it will
contain no waypoints.)
The new route appears in the list of route files associated with the map.
6.3.5.2.
Select the desired route file from the list that appears, and tap Load.
Pinpointing Procedure
Regardless of which method you used to load
your planned route, the route is drawn in dark
red on the map. Waypoints are marked by pin
symbols.
To pinpoint according to this route, do as
follows:
138
139
6.4.
6.5.
You can turn the visibility on and off for various map layers individually.
Tap the Actions button and select Select Map Layers.
6.6.
140
7.
The Outdoor Map view is intended for outdoor drive testing with access to
GPS coverage. The view uses Google Maps imagery in the form of roadmaps
and/or satellite images.
Routes can be plotted in live mode as well as in replay mode.
When a cell file is loaded, cell sites can be displayed from that file, and cells
currently being used can be pointed out.
In live mode, for obvious reasons, all plotting that relates to the devices
current position is possible only when GPS data is available.
The Outdoor Map view does not require any special license option.
7.1.
The map content supported is limited to the basics, and most options found in
Google Maps are disabled. For example, Street View is not supported. You
can however switch between map types, as described in section 7.7.4.
7.2.
141
The same value elements are selectable as in the Indoor Map view. See
appendix C, and compare what is said in section 6.3.3. By default, Signal
Strength is plotted.
Up to 10,000 route markers can be plotted in the Outdoor Map view.
To clear all route markers from the Outdoor Map view:
Tap the Actions button and select Clear History.
7.3.
Events are displayed in the Outdoor Map view as text labels pointing to a
route marker. See section 5.2.1.
7.4.
Cell sites can be displayed in the Outdoor Map view according to a cell file
that you have loaded into TEMS Pocket. See chapter 10.
Each cell of a site is visualized as a cyan-colored sector extending from the
sites position and covering an angle that corresponds to the cell beam width
as indicated in the cell file. The innermost part of a site is drawn in black to
indicate the site position more distinctly.
Cells are marked with a letter representing the radio access technology:
G = GSM, W = WCDMA, L = LTE, C = CDMA.
When the TEMS Pocket device has an active network connection, a line is
drawn from the devices current position to the serving cell or to each cell in
the active set. An extension of the cell sector, reaching out to the devices
position, is drawn as an overlay in a semi-transparent yellow color. The radii
of the sector are further extended by means of dashed lines all the way out to
the edge of the map view. The purpose of these lines are to indicate the angle
within which it is reasonable for a device to be served by this cell.
142
A maximum of 1,000 cells (not sites, please note) will be plotted in the
Outdoor Map view. If you zoom out so far as to view an area comprising more
than 1,000 cells, all sites are replaced by small black squares in the
presentation. If the number of in-view cells exceeds 10,000, all presentation
of cells is disabled. These limits are imposed for readability and performance
reasons.
143
7.5.
A value element legend appears in the Outdoor Map view. It looks the same
and provides the same information as in the Indoor Map view; see
section 6.4. The legend can be hidden, as described in section 7.6.
7.6.
You can turn the visibility on and off for various map layers individually.
Tap the Actions button and select Select Map Layers.
144
7.7.
Map Controls
This section deals with the buttons located at the top of the Outdoor Map
view.
7.7.1.
Follow
When the Follow function is on, the map will autopan as you
move around, so that it is always centered around your
current position. You can zoom the map by pinching and
spreading. This is the default setting.
As soon as you activate the Follow function, Panning is
automatically turned off if currently active. (Automatic
panning and manual panning obviously cannot coexist.)
When the Follow function is off, there is no automatic
panning of the map, even if the device moves out of the area
displayed. You need to pan manually using the Panning
function.
7.7.2.
Panning
When this function is on, swiping actions in the map view will
pan the map. Pinching and spreading will zoom the map.
When you turn the Panning function on, Follow is
automatically turned off if currently active. Compare
section 7.7.1.
When this function is off, swiping in the map view does not
affect the map but takes you to a different data view, as
described in section 4.4. Furthermore, the map cannot be
zoomed by pinching and spreading in this state. This is the
default setting.
145
7.7.3.
7.7.4.
Map Type
Roadmap: Displays the default road map view.
Terrain: Displays a physical map based on terrain data.
Satellite: Displays Google Earth satellite images.
Hybrid: Displays a composite of the roadmap and satellite
views.
Roadmap
146
Terrain
Satellite
Hybrid
147
8.
Scripts
8.1.
Introduction to Scripts
YouTube
Ping
SMS1
Parallel
Other Actions
Control Function
Idle
IP Capture
148
Chapter 8. Scripts
Logfile Upload
Wait
8.2.
149
150
Chapter 8. Scripts
8.2.1.
151
8.2.2.
In each case you are taken to the Event Configuration menu (covered in
section 5.2) to make the selection. Only one start and one stop event can be
selected.
When a script is triggered, it will override any other script that may be
running. That script will be stopped, and the triggered script will start
executing instead.
8.2.3.
To add an action to the script, tap the Overflow button and select New
Action.
152
Chapter 8. Scripts
8.3.
8.3.1.
Authentication Method:
153
(continued)
Message text: This field is enabled if Message
text type is set to Custom text. Enter the
email message body text here.
Random text length: This field is enabled if
Message text type is set to Random text and
specifies the length of the generated text.
Message attachments: You can add one or
several attachments to the email message.
Each attachment can be either a file stored on
the device (see section 3.8) or a randomly
generated file. In the latter case, you are
prompted for the desired file size. Note that
binary files are base 64 encoded, which means
that the volume of data actually transmitted will
be larger than the total file size of the
attachments.
Number of emails: The number of emails to
send (all identical and defined by the above
parameters). The maximum is 99.
Preguard, Postguard: Guard periods
automatically inserted before and after the
measurement task, respectively. The purpose
of the guard periods is to ensure that the
signaling setting up and taking down the
service session is recorded to the logfile and
made available for post-processing. For this
reason, they should not be set too short; the
default for both is 10 s (see appendix D.5).
Repeat action: Total number of times to
execute the action before the script proceeds to
the next action. The maximum is 99. All
repetitions are recorded in the same logfile.
(continued on next page)
154
Chapter 8. Scripts
(continued)
Wi-Fi association: By setting this to Disabled,
you prevent the device from connecting to a
Wi-Fi access point (even if a Wi-Fi network is
available) and force it to run the session over a
cellular network instead. Note that the default
Android behavior is always to use Wi-Fi if it is
the best available bearer. The option provided
here eliminates the need to deactivate Wi-Fi
manually in the devices regular settings to
achieve the same effect.
Minimum duration: If you enter a value here
(in seconds), the action will run for at least the
time specified. If the task is completed quicker
than this, TEMS Pocket will idle until the
minimum duration has been completed, and
only then will the action end. By default this
setting is disabled.
Maximum duration: If you enter a value here
(in seconds), it puts a cap on the action
duration. If the task is not completed within the
maximum time allowed, the action is terminated
anyway.
The duration parameters are useful if you want
to keep the duration of actions (more or less)
uniform, for example in a benchmarking
scenario where all devices should perform
actions at a similar pace and thus collect a
similar total amount of data.
Advice on Email Size
Please bear in mind that most SMTP servers have an email message size
limit, typically on the order of 10 MB.
Note also that for TEMS Pocket to be able to send an email, there must be
sufficient free space on the internal memory card for the temporary file that is
created in the process.
155
8.3.2.
156
Chapter 8. Scripts
8.3.3.
157
(continued)
Additional parameters: Here it is possible to
add or edit key-value pairs to be sent with the
HTTP Post request. Tapping this field takes
you to the list of existing key-value pairs.
Additional parameters: Keyvalue pairs displayed
158
Chapter 8. Scripts
8.3.4.
159
8.3.5.
160
Chapter 8. Scripts
(continued)
Override default SMSC: Governs whether to
override the default SMS center (entered as a
setting in Android) and send messages to a
different SMS center.
SMSC phone number: This field becomes
editable when Override default SMSC is set
to Enabled. Enter the phone number to your
custom SMSC here. If the field is left empty,
the default SMSC number will be used anyway.
Preguard, Postguard: See section 8.3.1.
Repeat action: Total number of times to
execute the action before the script proceeds
to the next action. The maximum is 99. All
repetitions are recorded in the same logfile.
Durations: See section 8.3.1.
8.3.5.1.
161
The SMS technical specifications are found in 3GPP 23.040. Please note
that SMS is not supported for CDMA.
8.3.6.
8.3.6.1.
162
The device should always have TEMS VoLTE mode enabled in TEMS
Capability Control: see appendix G.2.
Chapter 8. Scripts
The device must have the setting Call VoLTE Feature enabled.
8.3.7.
163
(continued)
Audio path filtering: Use of device-specific
audio-enhancing functions such as noise
suppression, audio stretch, comfort noise, and
gain control. Currently, this option is always
enabled (not configurable).
Preguard, Postguard: See section 8.3.1.
Repeat action: Total number of times to
execute the action before the script proceeds
to the next action. The maximum is 99. All
repetitions are recorded in the same logfile.
Durations: See section 8.3.1.
8.3.8.
This action handles voice calls during which audio quality measurement
(AQM) is performed. It is supported with the subset of TEMS Pocket devices
listed in section 12.2.1. Audio quality measurement can be set up in several
different ways; the full range of possible configurations is detailed in sections
12.2.212.2.5. In one configuration, the receiving device is controlled by a
Voice MT action, which is covered in section 8.3.7.
For the answering party in a two-way mobile-to-mobile AQM configuration
(see section 12.2.4), a number of settings are not valid and are ignored.
These are marked with an asterisk (*) below.
As a general rule, the answering party should have no other actions than the
AQM action running.
164
Chapter 8. Scripts
165
8.3.9.
Example 1: http://www.youtube.com/
watch?v=sPkmeJunie4
Example 2: http://www.youtube.com/
watch?v=sPkmeJunie4&feature=c4overview&list=UUak5EU8HFAuRA7zqJIk8Zuw
Preguard, Postguard: See section 8.3.1.
Repeat action: Total number of times to
execute the action before the script proceeds
to the next action. The maximum is 99. All
repetitions are recorded in the same logfile.
Wi-Fi association, Durations: See
section 8.3.1.
8.3.9.1.
In the YouTube app you can turn on the option High quality on mobile to get
video streams with higher resolution when testing with TEMS Pocket. Be
aware that doing so may increase the prebuffering time.
166
Chapter 8. Scripts
8.4.
8.4.1.
Voice settings
Voice action type: Currently always Voice.
Edit voice settings: Same settings as for the
Voice action: see section 8.3.6.
Data settings
Data action type: FTP or HTTP.
Edit data settings: Same settings as for the
chosen data action type: see sections 8.3.2
(FTP), 8.3.3 (HTTP).
Common settings
Stop at voice end: If enabled, the data action
will be aborted when the voice action ends. If
disabled, the data action will be unaffected by
the voice action terminating.
Preguard, Postguard: See section 8.3.1.
(continued on next page)
167
(continued)
Repeat action: Total number of times to
execute the action before the script proceeds
to the next action. The maximum is 99. Note
that this setting refers to repetition of the
Voice + Data action as a whole; the Data part
has its own Repeat setting and can therefore
be repeated independently of what is selected
here. The Voice part, however, is always run
only once for each repetition of the Voice +
Data action.
The total number of separate logfiles created
by the Voice + Data action type is equal to its
Repeat action setting.
Durations: See section 8.3.1. These settings
are applied to the Voice + Data action as a
whole, not to its constituent parts.
168
Chapter 8. Scripts
8.4.2.
Common settings
169
8.5.
8.5.1.
8.5.2.
170
Chapter 8. Scripts
8.5.3.
8.5.3.1.
Device modem IP data is obtained only when the modem is in use, that is,
when running data services over a mobile network (as opposed to Wi-Fi).
171
The IP data obtained from the device modem is mostly equivalent to that
captured from the Android IP stack. VoLTE, however, is an exception, since
the IMS client (unlike clients for other data services) is built into the modem.
For this reason, VoLTE can be run over the device modem only, and IP data
for this service does not propagate to the Android IP stack. Therefore you
must capture device modem IP data to provide input (SIP signaling, RTP
packets) to the computation of VoLTE KPIs during post-processing, whether
using TEMS Discovery or some other tool.
On the other hand, device modem IP capture is not suitable for high
throughput tests since it affects the performance of the device.
8.5.4.
Logfiles can be uploaded via either FTP or HTTP(S). This is governed by the
Type setting.
Whenever this action executes, TEMS Pocket tries to upload all logfiles found
in the folder specified in section 3.8, and then deletes all files successfully
uploaded. However, no more than 500 logfiles will be uploaded at a time. If
there are files left after this action terminates, they will be taken care of the
next time a Logfile Upload action is executed.
8.5.4.1.
172
Chapter 8. Scripts
8.5.4.2.
173
(continued)
174
Chapter 8. Scripts
8.5.5.
175
Selecting No bands scanned in the band settings will stop any scan that
is in progress. The action is subtitled Stop scan: <device type> in the
script action list.
To give duration to the scan, you must interpose some other action between
the start scan and stop scan actions. See section 13.3 for further
instructions.
8.5.6.
176
Chapter 8. Scripts
8.5.7.
To give duration to Wi-Fi scanning, you must interpose some other action
between the enable and disable actions. See section 14.1 for further
instructions.
For clarity, it may be remarked that this action is unrelated to the Wi-Fi
association setting in data service actions (about which see section 8.3.1).
177
8.6.
Editing a Script
8.6.1.
Once you are done setting up an action, simply tap the Back button to
return to the list of actions in the script.
In this list the new action appears on top of
those previously defined. Here is an example
where multiple actions have been set up. The
addition (3) after HTTP action means that
this action will be executed three times backto-back (Repeat action parameter, see
section 8.3.3).
You can add one more action to the script by
again tapping the Overflow button, selecting
New Action, and proceeding as described
above.
8.6.2.
To delete an action from a script, longpress the action and select Delete.
178
Chapter 8. Scripts
8.7.
The Test Status data views detail the outcome of the script execution: see
section 4.11.
To stop a script that is running, do as follows:
Tap the Quick Access button and select Stop Script.
179
8.8.
Deleting Scripts
To delete a script:
Tap the Settings button and select
Script Editor.
Note: When you delete a script, the script file is permanently removed
from the devices file system.
180
Chapter 9. Logfiles
9.
Logfiles
9.1.
TEMS Pocket can record its measurements in logfiles, containing the same
richness of detail as logfiles recorded with TEMS Automatic/TEMS
Symphony test probes or with terminals connected to TEMS Investigation.
The same TRP format is used as in these other TEMS products.
Logfiles are stored on the devices internal memory card, or alternatively on
an external memory card (see section 3.8), as regular files in the device file
system.
You can record logfiles manually in the following ways:
In connection with pinpointing in the Indoor Map view. See section 6.3.
181
9.2.
All logfiles recorded by TEMS Pocket are named according to the syntax
[<script name>]yyyymmddThhmmssZ.trp, where the timestamp indicates at
what time the recording started. In case of manual logfile recording, the
<script name> part is absent.
9.3.
182
Chapter 9. Logfiles
The IP capture settings are the same as in the IP Capture script action and
are described in more detail in section 8.5.3.
9.3.1.
9.4.
A logfile recording in progress will stop if the free memory on the chosen
storage media drops below 10 MB.
9.5.
Filemarks
You can insert a filemark in a logfile that is being recorded in order to tag a
segment of particular interest in the file, or just to note down some pertinent
fact related to the recording. Multiple filemarks can be inserted in the same
logfile.
Whenever logfile recording is active, the Filemark button is visible on
the action bar. Tap this button to add a filemark at the current position
in the logfile.
183
Next time you enter the dialog, the text box will
hold the text of the previous filemark with an
underscore and sequence number appended.
If the previous filemark already had a
sequence number, the number is incremented.
9.6.
Replaying Logfiles
This function is used to replay TEMS Pocket logfiles in TEMS Pocket itself.1
Note that you can also load logfiles into TEMS Investigation and TEMS
Discovery and make use of the powerful presentation facilities in these tools.
During replay, the TEMS Pocket views are updated by the logfile content
exactly as in live mode, that is, exactly as if the data were being received from
the network.
To load a logfile:
Tap the Actions button and select Load Logfile.
1. Please note that it is not possible to replay TRP logfiles from other TEMS
products in TEMS Pocket. (For one thing, TEMS Investigation TRP
logfiles may contain data from multiple devices, something which cannot
be presented in TEMS Pocket.)
184
Chapter 9. Logfiles
185
186
Chapter 9. Logfiles
9.6.1.
You can use any of the devices regular functions while replaying a logfile, for
example take an incoming call or write an SMS. Such actions do not interfere
with the replay in any way.
On the other hand, while at least one of the TEMS Pocket functions logfile
recording, script execution, and pinpointing is active, logfile replay is
disabled.
9.7.
187
10.
Cell Files
You can import a cell file into TEMS Pocket in order to display cells by name
(rather than by CGI) in data views. Cell file data is also searched as an aid to
target selection for cell and channel lock, and cell counts are shown in
connection with RAT and band lock. For details, see the various sections of
chapter 11.
Cell files are in XML format, and relevant aspects of their syntax are
described in appendix E.1
To import a cell file, do as follows:
Tap the Actions button and select Load Cellfile.
For the storage location on the internal memory card, see section 3.8.
Once you have imported a cell file, network cells will be presented by name in
TEMS Pocket data views and in the Outdoor Map view (as detailed in
sections 4.74.13 and chapter 7) whenever they can be matched with an
entry in the cell file.
When you restart TEMS Pocket, the cell file that was last loaded in the
application (if any) is automatically reloaded.
1. The file format is the same as in TEMS Investigation and contains a wide
range of data, most of which is currently not used in TEMS Pocket.
188
11.
Control Functions
11.1.
The following TEMS Pocket devices are equipped with control functions:
189
Control Function/Device
11.2.
11.3
11.3
11.4
11.4
11.5
11.6
11.7
11.9
11.10
11.11
11.12
190
11.3.
RAT Lock
This function locks the device to a subset of its supported radio access
technologies when in idle mode. The function does not have any effect on
RAT selection in dedicated mode.
When a RAT lock is applied, and this results in the device being forced away
from the network it is currently attached to, the device will detach from that
network and subsequently try to attach to some other network that is allowed
by the RAT lock. If this fails, the device will go into no service mode.
191
11.3.1.
In the regular user interface of Sony and Samsung devices, under Settings
Wireless and networks Mobile networks Network mode, it is
possible to make a choice between GSM/WCDMA/LTE, GSM only,
WCDMA only, and LTE only (or similar). It is recommended not to use
this function in conjunction with TEMS Pocket.
11.4.
You can lock the device to a subset of its supported frequency bands on LTE,
WCDMA, or GSM. Note that this operation will result in no service if you
prevent the use of all bands that are available at the current location.
192
Conversely, checking all bands is equivalent to Off (that is, no lock applied)
and is automatically converted to that setting.
If a cell file is loaded, then for each band, the number of cells on that band
listed in the cell file is indicated beneath the band name.
The device cannot be band-locked while a voice call is in progress.
11.4.1.
11.4.2.
193
11.4.3.
11.5.
194
The EARFCN lock function has a permanent effect in idle mode only. When
the device goes into connected mode and engages in data transfer, it will
switch to a different EARFCN if ordered to do so by the network. However, a
separate Ascom device app is available for disabling LTE inter-frequency
(that is, inter-EARFCN) handover. Regarding this app, see appendix G.
If you attempt to lock on an EARFCN that the device does not support, the
control function will fail. Note that this behavior is different from the
corresponding WCDMA and GSM locking functions, where the device goes
into no service mode in this situation.
11.6.
This function singles out one cell (UARFCN + scrambling code combination)
or simply one UARFCN that the device should use.
195
The same function can alternatively be applied from the WCDMA Cell List
data view to a cell or UARFCN that appears there. Any action that you
perform from the Control Functions menu is also immediately reflected by
means of highlighting (in green) in the WCDMA Cell List data view. See
section 4.7.3 for full details.
The WCDMA Cell Lock function can be described in general terms thus:
In idle mode, the function forces the device to camp on the selected cell
or some cell on the selected UARFCN.
The device encourages the network to include the selected cell (or
any cell on the selected UARFCN, if no scrambling code has been
specified) in the active set when the device comes close enough to
measure on the cell.
Once a desired cell has entered the active set, the device keeps it
there until the connection drops. That is, no further soft or softer
handovers are performed adding cells to the active set.
A good way to use this function is as follows: Apply the function while the
device is in idle mode to lock it to the cell or UARFCN you want to test. Then
run your service testing. Only the desired cell, or cells on the desired
UARFCN, will then be admitted to the active set.
11.6.1.
After the function has been applied, the device will still search on all
UARFCNs, but will accept only the selected UARFCN or UARFCN + SC
combination. It may therefore take some time from the moment the control
function is applied until the device finds an acceptable cell.
11.6.2.
196
11.7.
Lock on one or several cells. The device is then restricted to using these
cells alone.
Prevent one or several cells. The device is then prevented from using
these cells.
11.7.1.
197
11.7.2.
198
To release all applied lock or prevent functions, use the Reset command
as explained in section 11.2.
11.8.
This section applies to both LTE, WCDMA, and GSM cell lock. If no cell file is
loaded, the search described below will simply never return any hits.
What you type into the Free-text Search field is
matched with the following tags in the cell file
(whose format is described in appendix E):
<EARFCN_DL> (LTE)
<ARFCN> (GSM).
199
11.9.
Vocoder Lock
Off: Function not applied.
GSM codecs, UMTS codecs: Check the
codecs that the device should report as
supported to the network:
11.10.
UMTS AMR
UMTS AMR2
This function lets you alter the devices behavior with respect to barred,
reserved, and other cells.
200
11.11.
This function allows you to manipulate access class settings ( 3GPP 22.011,
chapter 4).
201
11.12.
202
11.13.
You can apply multiple intra-technology functions at the same time; for
example, both a WCDMA band lock and a WCDMA cell lock.
203
11.14.
204
12.
Audio quality can be measured in TEMS Pocket using the POLQA algorithm.
12.1.
Handling of new and complex types of distortions that arise from todays
convergence and coexistence of voice, data, and multimedia application
services. One example is the effects of packet loss and of packet loss
concealment.
Performance for CDMA speech codecs and hence for CDMA networks in
general.
205
12.2.
12.2.1.
Please note that AQM requires a special license option. For the details on
license requirements, turn to section 3.5.
12.2.2.
AQM Setups
AQM scores calculated at one end (by the calling party), or:
12.2.3.
In this setup, the two TEMS Pocket devices have distinct roles. One device
plays back a succession of speech sentences to the other, which records the
206
sentences and computes AQM scores. The device tasked with the AQM
computation is the party that dials the call.
For the calling party, set AQM mode to POLQA <codec> DL - mobile to
mobile. As explained in section 12.2.2, <codec> can be either NB or
SWB.
The receiving party does not compute any AQM scores and is controlled
by a Voice MT script action: see section 8.3.8.
Answering party:
TEMS Pocket device B
AQM action
Voice MT action
AQM score
#1 computed
AQM sentence
#1 sent
AQM score
#2 computed
AQM sentence
#2 sent
etc.
etc.
...
...
...
Call answered
...
Call dialed
Call hangup
time
12.2.4.
In this setup, both TEMS Pocket devices are controlled by an AQM script
action. The devices take turns sending and receiving speech sentences, and
AQM scores are computed by both devices.
For the calling party, set AQM mode to POLQA <codec> DL_UL - mobile
to mobile. (The calling party starts by receiving a sentence [DL], then
sends the same sentence back [UL], as shown in the diagram below.)
For the answering party, set AQM mode to POLQA <codec> UL_DL mobile to mobile. (The answering party first sends a sentence [UL],
then receives a sentence [DL].)
207
Answering party:
TEMS Pocket device B
AQM action
AQM action
Call dialed
Call answered
AQM score
#1 computed
AQM sentence
#1 sent
AQM score
#1 computed
AQM sentence
#1 sent back
AQM sentence
#2 sent
AQM score
#2 computed
AQM score
#2 computed
...
etc.
...
etc.
...
...
AQM sentence
#2 sent back
Call hangup
time
The microphone in each device will be muted while the AQM action executes.
Avoid making sound-related adjustments on the device during AQM testing.
12.2.5.
Mobile-to-fixed AQM
In this setup, a TEMS Pocket device dials a CallGenerator, which plays back
speech sentences so that TEMS Pocket can calculate AQM scores.
Note: This setup is supported for CS only, not for VoLTE.
208
The communication flow in this configuration is similar to one-way mobile-tomobile AQM (section 12.2.3), as depicted in the following diagram.
Calling party:
TEMS Pocket device
Answering party:
CallGenerator
AQM action
AQM score
#1 computed
AQM sentence
#1 sent
AQM score
#2 computed
AQM sentence
#2 sent
etc.
etc.
...
...
...
Call answered
...
Call dialed
Call hangup
time
209
13.
TEMS Pocket has the ability to conduct scanning of mobile networks with a
connected external DRT4311B scanner, and to present the results of such
scans. This scanning can be either manual or scripted.
The scanning is completely independent of other TEMS Pocket activities and
never conflicts with any of these. The data view header is unaffected by
scanning activities.
13.1.
Scope of Scanning
13.2.
Prerequisites
The TEMS Pocket device needs to have an app from DRT installed which
is named DRT Mpg Scanner Service. This app is installed automatically
by the TEMS Pocket installer.
13.3.
Setting Up a Scan
210
to insert an Idle action of the desired length. Note that the Wait action cannot
be used for this purpose (compare section 8.5.6).
A manual scan is set up in the following way:
Tap the Settings button and select Settings Scanning.
The parameters in the dialog that appears are exactly the same as for a
scripted scan. Configure them according to section 8.5.5.
13.4.
When you connect the scanner for the first time, a message will appear
saying: Open Drt Mps Service Application when this accessory is
connected? Check the box Use by default for this USB accessory and
tap OK. The message will now no longer appear on future occasions when
you connect the scanner. The DRT app launches.
Whenever the scanner is connected and TEMS Pocket is running, you can do
(manual) scanning while using other TEMS Pocket functions at the same
time, except that you cannot start a script or start pinpointing.
13.5.
Running a Scan
To run a scripted scan, simply execute the prepared script as usual: see
section 8.7.
To run a scan manually, do as follows:
Tap the Quick Access button and select Start Scan.
The scan currently configured as described in section 13.3 will now start
and will execute indefinitely until it is halted.
To stop the scan, tap the Quick Access button once more and select
Stop Scan. (Alternatively, you can change the band selection to No
bands scanned in the scan settings.)
13.6.
When logfile recording is active, it will capture mobile network scan data (just
like any other network testing data) whenever such scanning is in progress.
211
14.
Wi-Fi Scanning
Wi-Fi availability and Wi-Fi scanning can be controlled from within TEMS
Pocket. The effect of activating Wi-Fi scanning is exactly the same as when
turning on Wi-Fi in the devices regular user interface.
14.1.
14.2.
The output from Wi-Fi scanning is presented in the data views described in
sections 4.13.1 and 4.13.2.
212
14.3.
When logfile recording is active, it will capture Wi-Fi scan data whenever such
scanning is in progress.
14.4.
As explained in section 8.5.7, if you wish to test data transfer over Wi-Fi, it
may be appropriate to turn off Wi-Fi scanning in TEMS Pocket during this
time to prevent it from impinging on data transfer performance. If repeated
continually, as is done by TEMS Pocket, the scanning will have a substantial
negative effect on the data throughput. Most of the time, therefore, it may be
suitable to have the Scan for cells option turned on (scanning allowed in WiFi idle mode) but the Scan during measurement option turned off.
Also remember that in script actions, the Wi-Fi association parameter must
be set to Enabled for Wi-Fi to be allowed as data bearer. See section 8.3.1.
213
15.
This chapter deals with using the devices built-in GPS or an external GPS
with TEMS Pocket.
15.1.
Make use of cell file look-up to present cells by name in data views and in
the Outdoor Map view.
15.2.
GlobalSat BT-359
15.3.
214
Type:
15.3.1.
215
15.4.
Scripts in TEMS Pocket have a setting that governs GPS use, as explained in
section 8.2.1.
When you record a logfile manually, you are prompted to decide whether to
include GPS data in the logfile. See section 9.3.
TEMS Pocket also has commands for manually turning the GPS on and off.
These commands are useful if you are doing tests without running a script.
All of the operations mentioned in this section apply to any GPS, whether
internal or external.
15.5.
GPS Events
216
16.
Settings Menu
From the Settings menu, a number of aspects of TEMS Pocket behavior are
configured.
To access this menu, tap the Settings button and select Settings.
A number of subcategories are found, as detailed in this chapter.
All of these settings are preserved when upgrading TEMS Pocket, for
instance using the TEMS Pocket installer.
16.1.
General Settings
16.1.1.
16.1.2.
GPS Settings
Here you indicate what type of GPS device TEMS Pocket should use: an
internal or an external one. See section 15.3.
217
16.1.3.
Script Settings
Triggers enabled: This must be checked to
allow events to trigger starting and stopping of
scripts. Compare section 8.2.1.
16.1.4.
16.1.5.
Cell identities are reported infrequently from the network, and only for the
current serving cell, not for neighbors. As a result, no recently reported cell
identity is typically available for most cells in the cell list views. Even for the
serving cell, it may take a while until the cell identity is obtained.1
The cell caching function remedies this situation by storing all cells that are
detected by TEMS Pocket in a look-up table. As a result, whenever such a
cell reappears in the list later on, its identity can be presented immediately,
without the need to wait until it is reported from the network. Such a deduced
cell identity is shown in italics in the data views.
1. That is, unless a cell file and GPS positioning data are available, in which
case TEMS Pocket can look up cell identities in the cell file instead. The
cell caching function is aimed at improving the presentation in the
absence of a cell file.
218
16.2.
219
16.3.
Scanning Settings
220
17.
Help Menu
Legal information
This users manual and the TEMS Pocket Quick Guide in HTML format.
To access the Help menu, tap the Overflow button and select Help.
License: The type of license purchased, e.g.
TEMS Pocket Professional.
Version: TEMS Pocket version, e.g.
13.3.1.<build number>.
Legal: Provides a link to the text of the TEMS
Pocket software license agreement.
Open Source Legal: Provides a link to license
agreements for open-source software
components used in TEMS Pocket.
Quick Guide: Opens the TEMS Pocket Quick
Guide in the devices web browser. Document
number: NT13-27468 ver 1.0
User Manual: Opens the present document in
the devices web browser. Document number:
NT13-27466 ver 1.0
221
18.
The TEMS Pocket user interface on tablets is generally similar to the mobile
phone user interface. The differences that do exist are described here.
Below is a screenshot of the tablet user interface:
Header
Data view
Data view
The data view category icons (found on the top-level screen on phones)
are permanently visible on the tablet, in a column on the far left. Compare
section 3.7.1.
Data views are shown two at a time, side by side, in the main screen area.
These are adjacent views in the currently selected data view category.
Scrolling between data views is done in the usual manner.
The pinpointing and logfile replay controls appear on the right-hand side
of the screen for easy access when holding the tablet:
222
The GPS data view is augmented with a graph (GPS Line Chart)
showing the vehicle speed and the number of satellites seen:
223
19.
Configuration of DRT
Transmitter
19.1.
Before you begin, you need to install the Nome application, which functions
as the transmitters user interface, on the PC. Along with it, another
application Yukon4k is installed which is used for configuring the
transmitters network connection.
1. After installing the above software, start Yukon4k. This application will
find the DRT transmitter automatically and present its name as shown
in the screenshot below.
224
2. On the IP Address tab you can set IP addresses for Ethernet and WiFi. The adapter for Ethernet is eth0 and by default uses the IP address
192.168.1.100. The Wi-Fi adapter is called eth1 and uses the default
IP address 192.168.2.100.
3. If you are going to connect to the transmitter via Ethernet, then for
Adapter = eth0 you need to select Obtain an IP Address
automatically and click the Set Unit IP Configuration button.
Compare section 19.3.
4. To be able to access the transmitter over Wi-Fi, enter appropriate
settings on the WiFi Settings tab:
When you are done entering the parameters, click the Set Wireless
Configuration button.
225
19.1.1.
19.2.
The DRT transmitter is shipped configured for a direct connection, with the
static IP address 192.168.1.100 assigned to its Ethernet (eth0) adapter. The
PCs Ethernet adapter must likewise have its TCP/IP address configured as
static and in the range 192.168.1.nnn, where nnn is any number between 1
and 255 except 100.
Follow these steps:
226
3. In the box below This connection uses the following items:, select:
19.3.
227
19.4.
19.5.
There are two ways to connect to the DRT transmitter and set up its cell
information: through Nome or through a web interface.
19.5.1.
1. Start Nome and wait for the application to find the DRT transmitter.
When found, it appears in the list box.
228
2. Select the DRT transmitter in the list, and click Connect. A new screen
appears where you configure transmitter settings.
229
4. Protocol Specific section (E): Here you set what band and (U)ARFCN
to use, along with other cell parameters.
19.5.2.
The web browser used to access the DRT transmitter interface must support
Ajax, for example: Internet Explorer 8 or later, Firefox 3.0.17, Firefox 3.6.3.
1. Connect to the transmitter with a web browser by entering the URL
http://drt4302snaaaa, where aaaa is the serial number of the device.
Alternatively, you can also enter the IP address for the transmitter: by
default, http://192.168.1.100 for Ethernet or http://192.168.2.100 for WiFi.
2. The web browser interface looks somewhat different from the Nome
application. Click the Tx Configuration link to set transmission
parameters (left-hand screenshot below); compare section 19.5.1,
step 3. Clicking the Unit Status link displays device status information,
as shown in the screenshot on the right.
230
231
20.
20.1.
If your TEMS Pocket device was purchased with a Remote-only license, it will
show only the user interface described in this chapter.
If, on the other hand, your TEMS Pocket was purchased with both
Professional and Remote license options, you can switch between the two
modes as described in chapter 22. Note that TEMS Pocket Remote must be
offline to permit this transition: see section 20.2.2.
20.2.
20.2.1.
Remote: These are data views unique to TEMS Pocket Remote. They
are described in sections 20.2.220.2.4.
232
20.2.2.
This data view shows the current status of the TEMS Pocket Remote
application in terms of its activities and its communication with the Fleet
Manager.
Online:
Green: The client is active and will communicate with the configured Fleet Manager
Endpoint and collect measurements (if
configured to do so).
Registered:
Green: The client has completed registration with the Fleet Manager.
233
(continued)
234
(continued)
235
20.2.3.
This data view shows Fleet Manager settings and some information on
logfiles recently recorded.
Fleet Manager section
Configured Endpoint: Fleet Manager URL
accessed by the client.
User Name: User identity for logging in to the
Fleet Manager.
Client Name: Name of the client in the Fleet
Manager.
Secure Connection: Use of secure (SSL)
connection: Yes/No. Equivalent to Fleet
Manager URL starting with https.
Proxy Used: Use of proxy server: Yes/No.
Last Successful Sync: Date and time when
the client last performed a wholly successful
synchronization to the Fleet Manager (all steps
succeeding).
Running Web Service Action: Task currently
being performed as part of the interaction
between the client and the Fleet Manager.
Logfiles section
Remote Logfiles: Number of TEMS Pocket
Remote logfiles currently stored on the client in
the location given in section 3.8 (files not yet
uploaded). Any files recorded in Professional
mode are not included in the count. If the
number of Remote logfiles exceeds 500, the
string 500+ is displayed.
Last Recorded: Date and time when the latest
logfile was recorded.
236
20.2.4.
This data view shows information on what content the client has downloaded
from the Fleet Manager, and on the measurement it is currently undertaking.
Local Content section
Active Campaigns: A measurement
campaign is an entity that encompasses one or
several scripts. Campaigns are what is
downloaded by the client. Here is shown the
number of campaigns that are associated with
the client and have been configured as active
in the Fleet Manager.
Total Campaigns: Total number of campaigns
associated with and downloaded by the client.
Active Scripts: Number of downloaded scripts
that are currently active, that is, allowed to be
run. Inactive scripts are ones that belong to an
inactive campaign, or that have their Run
checkbox unchecked in the Fleet Manager.
Total Scripts: Total number of scripts
downloaded by the client.
Last Updated: Date and time when the
campaigns and scripts were last updated
(during synchronization with the Fleet
Manager).
Active Measurement section
Campaign Name: Name of the measurement
campaign that the client is currently running.
Script Name: Name of the currently executing
script.
Script File: File name of the currently
executing script.
More information about the executing script
can be found in the Test Status category of
data views (see section 4.11).
237
20.3.
20.3.1.
238
20.3.2.
Client Settings
Registration Reattempt Interval: This setting
governs how frequently the client will retry
registration with the Fleet Manager in case the
registration fails.
Sync Interval (Idle): The interval at which the
client synchronizes with the Fleet Manager
when in idle mode. The timer is reset when the
client returns to Idle state (from Measuring).
Sync Interval (Measuring): The interval at
which the client should ideally synchronize with
the Fleet Manager when measuring, that is,
while executing a script. However, after the
sync interval times out, the client first finishes
the current script iteration before syncing, then
pauses the script to do the synchronization.
After the sync is complete, the script resumes,
embarking on the next iteration.
If the sync interval times out a second time
during the same iteration, the entire script is
stopped. A sync is performed, but afterwards
the client goes into Idle state without resuming
the script. In practice, therefore, this parameter
provides an additional mechanism (besides the
stop trigger in the script) for limiting the script
execution time. It can also be used to abort a
script that might unintentionally have been
configured as to never finish. In this way you
become able to reconfigure the invalid script
from the Fleet Manager and push the corrected
script to the client within twice the time interval
configured here.
Go Offline Sync Timeout: The length of time
to wait for an acknowledgment from the Fleet
Manager after the Go Offline command has
been given (see section 20.2.2). If no acknowledgment arrives within this time, the client
goes offline anyway.
(continued on next page)
239
(continued)
Initial Registration Required: If set to
Enabled, successful registration with the Fleet
Manager is required before the client is
allowed to run scripts it has already
downloaded (that is, on some previous
occasion when the client was registered).
Sync After Measurement: If set to Enabled,
the client will perform an extra synchronization
each time it has finished a script normally (the
scripts stop trigger evaluated to true, or the
maximum number of script iterations was
completed).
20.3.3.
20.4.
If trigger conditions are satisfied for several scripts simultaneously, one script
is picked for execution, while the others are placed in a queue. The first script
is run to completion, and then the other scripts are executed in turn. However,
if the scripts stop trigger becomes true while the script is waiting in the
queue, that script is not executed at all.
240
The general advice that can be given here is to take care to compose triggers
that make good sense and do not conflict unnecessarily.
20.5.
241
21.
This chapter describes the features and functionality of the TEMS Pocket
multi-device configuration.
21.1.
System Overview
Agents
242
21.2.
21.2.1.
Professional
Standard
Lite
Controller
Included
Optional
Optional
Agent
Included
Optional
Remote
Included
Note especially that the controller can be a TEMS Pocket Lite device. Using a
Lite license for the controller allows it to run on any tablet, and not only on
TEMS Pocket Professional tablets.
Compare section 3.2 regarding product packages generally.
21.2.2.
The controller can be either active or inactive, and the following actions can
be performed in each state:
An agent can likewise be active or inactive, and the following actions can be
performed in each state:
243
21.3.
Initial Configuration
21.3.1.
Tap the Menu button on the device to open the Bluetooth settings menu at
the bottom of the screen.
244
21.3.2.
Turn on Bluetooth:
245
You may want to give the controller a user-defined Bluetooth name just
like the agents. This is done in the same way as described in
section 21.3.1.
Tap the Start button and select Start Discovery to find the agents.
Wait a few seconds until the agents show up in the Found Devices list.
Please note that all Bluetooth devices that are within range will appear in
this list, not just your TEMS Pocket agents.
When you have added all agents, tap the Start button and select Stop
Discovery.
The Controlled Agents view is populated with the agents you have added.
If you have added an agent that you are not going to use any more, you can
remove it as follows:
246
21.4.
Select the agent in the Controlled Agents view to expand the agent list
item.
21.5.
Select the agent in the Controlled Agents view to expand the agent list
item.
21.6.
Composing Scripts
247
What needs to be kept in mind, however, is that the controller lets you
compose any type of script action, while running that action on an agent
requires that the agent a) support the action type and b) have the appropriate
license for it. You need to keep track of this yourself. If an agent is unable to
execute an action, the action will simply fail.
21.7.
From the controller you can either assign a common script to be run on all
agents, or you can assign script to agents individually.
21.7.1.
21.7.2.
248
21.8.
You can start measurement on all agents at the same time by tapping
the Start button, then selecting Start Measuring. Each agent will then
begin to execute its assigned script (whether the scripts are different or
a common script is used by all agents).
Stopping measurement on all agents is done analogously by tapping
the Start button and selecting Stop Measuring.
How to start a script on a single agent is described in section 21.7.2. To stop
the script, perform the same actions once more and tap the Stop button that
will appear in this situation.
21.9.
21.9.1.
This view is covered in general terms in section 21.4. See also section
21.9.2.
21.9.2.
The Controlled Agents view displays a number of status icons for each
agent:
Meaning
Green
Yellow
Red
249
Meaning
Green
Yellow
Red
Meaning
Green
Yellow
Red
Meaning
Green
Yellow
No script is running.
Red
Meaning
Green
Yellow
Red
250
21.9.3.
This view holds signal strength charts for all cellular technologies supported
by the agents. Data is displayed from all agents side by side.
21.9.4.
Tap the Test Status button to access an overview of the testing the
agents are performing.
For each agent, a subset is shown of the information given in the Agent Script
Progress view (see section 21.9.5).
251
21.9.5.
21.10.
Agents exhibit the following views, which show various aspects of their
current status and configuration.
252
Configuration:
253
21.11.
Pinpointing
21.11.1. Preparations
What you need to do in terms of preparations is a) to load a map set and b) to
select a script to run.
First make sure that all agents are connected. See section 21.4.
On the controller device, tap the Location icon. The Indoor Map view
appears.
Tap Load. The map is loaded into the Indoor Map view.
254
Then assign scripts to the agents: either a common script to all of them, or a
unique script to each agent. Turn to section 21.7 for details.
Next, start the script you want to run. (You must defer this until after
starting pinpointing, for the reasons explained in section 6.3.2.)
Tap the Start button and select Start Measuring.
Now walk your route and mark waypoints in the Location view as you go,
just as in Local mode. Please refer to section 6.3.
The waypoints are distributed to all agents, so that they all receive identical
positioning data. You cannot do any pinpointing directly on the agents;
however, the waypoints received from the controller are shown in each
agents Location view.
When you have completed your route, tap the Start button and select
Stop Pinpointing. This will also unload the map set from the agents.
To stop your script, tap the Start button and select Stop Measuring.
21.12.
Storing of Logfiles
Logfiles recorded by the agents are stored locally on each agent device, as
indicated in section 3.8. There is no automatic transfer of logfiles from the
agents to the controller (this would be very slow and time-consuming over
Bluetooth). However, you can use the Logfile Upload script action (see
section 8.5.4) to transfer logfiles wherever you wish, just as in Local mode.
255
22.
If your TEMS Pocket device is equipped with license options that give access
to multiple product packages and/or work modes, you can switch between
these as described here. All such switching is done without restarting the
TEMS Pocket application.
Tap the Overflow button, then tap Pocket Mode.
Top section
Bottom section
256
Local: Regular TEMS Pocket with full realtime diagnostics user interface, as
described in this manual outside of
chapters 20 and 21.
To be able to switch modes, the TEMS Pocket device must be basically idle.
That is:
The Pocket Mode menu option is visible only if the device is equipped with
license options allowing it to actually switch between settings: for example,
between {Professional, Local} and {Professional, Remote}. Otherwise, the
Pocket Mode option is hidden. If it is present, the dialog may still contain
fewer choices that the full set shown above, again as dictated by the license
options on the device.
257
23.
23.1.
Technical Support
23.2.
Follow Us
Our monthly newsletter TEMS News contains articles on new TEMS product
releases and their features, general information about the TEMS portfolio,
and much more. To sign up for this free service, go to www.ascom.com/nt/
en/index-nt/nt-news.htm and click the TEMS News link. In this section of our
website you can also read our press releases and find out about upcoming
events where Ascom Network Testing will participate.
You can also follow Ascom Network Testing on Facebook, LinkedIn and
YouTube, as well as subscribe to our RSS feed. Links are provided in the
Follow Us section at www.ascom.com/networktesting.
258
Certain Ascom Network Testing products use FCC approved mobile phones
as test probes. When integrated with certain Ascom products, the Ascom
mobile test probes have been retested to ensure that the test probe continues
to comply with applicable FCC requirements.
Ascom mobile test probes are intended for use in cellular network testing
only.
Ascom mobile test probes should be professionally installed, and only
Ascom-specified external antennas should be used as part of the test
configuration.
No Wi-Fi1, Bluetooth or NFC (Near-Field Communication) features of the
mobile test probe should be used when using Ascom mobile test probe
products.
This equipment radiates radio frequency energy and, if not installed and used
in accordance with these instructions, may cause harmful interference to
radio communications.
Users assume full responsibility for performance and possible interference if
these instructions are not followed.
259
Appendix B. Graphic
Representation of Data
This appendix describes the color coding used to visualize value elements in
data views.
B.1.
GSM Data
Quantity
Green
Yellow
Red
75 ... 149
0 ... 74
100
91 ... 99
0 ... 90
75 ... 10
94 ... 76
120 ... 95
1 ... 4
5 ... 7
0 ... 9
10 ... 19
20 ... 31
Green
Yellow
Red
BLER (%)
0 ... 20
21 ... 49
50 ... 100
Ec/N0 (dB)
10 ... 0
15 ... 11
34 ... 16
0 ... 999
0 ... 499
RSCP (dBm)
85 ... 15
99 ... 86
RSSI (dBm)
45 ... 0
80 ... 46
120 ... 81
40 ... 60
not used
0 ... 39,
61 ... 100
B.2.
WCDMA Data
Quantity
260
Quantity
Green
Yellow
Red
40 ... 60
not used
0 ... 39,
61 ... 100
TxPower (dBm)
31 ... 0
1 ... 9
10 ... 50
Green
Yellow
Red
50 ... 100
21 ... 49
0 ... 20
E-DCH Retransmission
Rate (%)
50 ... 100
21 ... 49
0 ... 20
Green
Yellow
Red
BLER DL (%)
0 ... 20
21 ... 49
50 ... 100
CINR (dB)
8 ... 30
0 ... 7
40 ... 1
0 ... 3659
30 ... 10
9 ... 14
15 ... 30
0 ... 1829
30 ... 10
9 ... 14
15 ... 30
RSRP (dBm)
70 ... 40
99 ... 71
RSRQ (dB)
9 ... 0
23 ... 10
30 ... 24
RSSI (dBm)
70 ... 10
100 ... 71
Green
Yellow
Red
9 ... 0
23 ... 10
32 ... 24
B.2.1.
B.3.
LTE Data
Quantity
B.4.
CDMA/EV-DO Data
Quantity
Ec/I0 (dB)
261
Quantity
Green
Yellow
Red
0 ... 2
3 ... 5
6 ... 100
FES (dBm)
15 ... 10
24 ... 16
64 ... 25
15 ... 10
24 ... 16
64 ... 25
0 ... 2
3 ... 5
6 ... 100
0 ... 99
0 ... 99
RxPower (dBm)
30 ... 0
59 ... 31
120 ... 60
TxPower (dBm)
31 ... 0
1 ... 9
10 ... 50
Green
Yellow
Red
3.5 ... 5
0 ... 2.5
Green
Yellow
Red
4 ... 12
0 ... 2
FER (%)
PER (%)
B.5.
POLQA
Quantity
POLQA score
B.6.
GPS Data
Quantity
262
This appendix lists the families of value elements that can be selected for
route plotting in the Indoor Map view (see section 6.3.3) and Outdoor Map
view (see section 7.2).
C.1.
RSSI
GSM: RxLev
WCDMA: RSSI
LTE: RSSI
CDMA/EV-DO: RxPwr
C.2.
Signal Strength
GSM: RxLev
WCDMA: RSCP
LTE: RSRP
CDMA/EV-DO: Ec
C.3.
Quality
GSM: RxQual
WCDMA: Ec/N0
LTE: RSRQ
CDMA/EV-DO: Ec/I0
263
C.4.
Physical DL Throughput
C.5.
Physical UL Throughput
264
This appendix lists default values for a selected editable settings in TEMS
Pocket. Defaults that are not very interesting in themselves (for example, the
default body text in emails) are omitted.
D.1.
General Settings
D.2.
D.3.
Indoor Map
D.4.
Outdoor Map
265
D.5.
Script Editor
D.5.1.
General Settings
These defaults are the same for all actions in which they occur:
Preguard: 10 s
Postguard: 10 s
D.5.2.
D.5.3.
Port: 25
Security: None
Number of emails: 1
D.5.4.
Command: Get
D.5.5.
Idle duration: 10 s
D.5.6.
IP Capture Settings
No options selected.
266
D.5.7.
Timeout: 1 s
Number of pings: 10
Interval: 1000 ms
D.5.8.
Number of SMS: 1
Delivery timeout: 60 s
Send timeout: 60 s
D.5.9.
Call duration: 30 s
D.5.10.
D.5.11.
Wait duration: 10 s
D.6.
Control Functions
D.7.
267
268
An XML cell file imported into TEMS Pocket must include the tags shown in
the example below. Position data is syntactically optional, but is of course
required for plotting of cells in the Outdoor Map view.
The tag names are all self-explanatory; in this example, one cell each is
defined for GSM, WCDMA, LTE, and CDMA1. This data is a subset of the
XML cell file format used in TEMS Investigation; see TEMS Investigation
Technical Reference, chapter Format of XML Cell File.
Please note that TEMS Pocket can only display characters from the
Extended ASCII set. Characters outside that set will appear as question
marks ? in the TEMS Pocket user interface.
Cell File Content
<TEMS_CELL_EXPORT>
<GSM>
<CELL_LIST>
<GSM_CELL>
<CELLNAME>My GSM Cell #1</CELLNAME>
<CGI>
<MCC>240</MCC>
<MNC_LENGTH>2</MNC_LENGTH>
<MNC>1</MNC>
<LAC>5028</LAC>
<CI>4362</CI>
</CGI>
<BSIC>
<NCC>2</NCC>
<BCC>2</BCC>
</BSIC>
<CHANNEL_INFO>
<BCCH>
1. No EV-DO specific data is given in the cell file; the <CDMA> data serves
for EV-DO as well.
269
<ARFCN>19</ARFCN>
</BCCH>
</CHANNEL_INFO>
<!-- OPTIONAL CONTENT -->
<POSITION>
<GEODETIC_DATUM>WGS84</GEODETIC_DATUM>
<LATITUDE>47.949722</LATITUDE>
<LONGITUDE>-17.355278</LONGITUDE>
</POSITION>
<!-- END OPTIONAL CONTENT -->
</GSM_CELL>
</CELL_LIST>
</GSM>
<WCDMA>
<CELL_LIST>
<WCDMA_CELL>
<CELLNAME>My WCDMA Cell #1</CELLNAME>
<UARFCN_DL>10787</UARFCN_DL>
<SC>124</SC>
<CGI>
<MCC>240</MCC>
<MNC_LENGTH>2</MNC_LENGTH>
<MNC>5</MNC>
<LAC>27</LAC>
<CI>60001</CI>
</CGI>
<!-- OPTIONAL CONTENT -->
<POSITION>
<GEODETIC_DATUM>WGS84</GEODETIC_DATUM>
<LATITUDE>55.949722</LATITUDE>
<LONGITUDE>-9.355278</LONGITUDE>
</POSITION>
<!-- END OPTIONAL CONTENT -->
</WCDMA_CELL>
</CELL_LIST>
</WCDMA>
<LTE>
<CELL_LIST>
<LTE_CELL>
<CELLNAME>My LTE Cell #1</CELLNAME>
<EARFCN_DL>5206</EARFCN_DL>
<POSITION>
<GEODETIC_DATUM>WGS84</GEODETIC_DATUM>
<LATITUDE>51.137990700</LATITUDE>
<LONGITUDE>-9.943741439</LONGITUDE>
270
</POSITION>
<PCI>1</PCI>
<PCIG>10</PCIG>
<!-- OPTIONAL CONTENT -->
<LTE_CGI>
<MCC>193</MCC>
<MNC>11</MNC>
<TAC>18</TAC>
<CI>123456789</CI>
</LTE_CGI>
<!-- END OPTIONAL CONTENT -->
</LTE_CELL>
</CELL_LIST>
</LTE>
<CDMA>
<CELL_LIST>
<CDMA_CELL>
<CELLNAME>My CDMA Cell #1</CELLNAME>
<PN_OFFSET>60</PN_OFFSET>
<CDMA_CHANNEL_INFO>
<BAND>CDMA 800</BAND>
<CHANNEL>384</CHANNEL>
</CDMA_CHANNEL_INFO>
<!-- OPTIONAL CONTENT -->
<POSITION>
<GEODETIC_DATUM>WGS84</GEODETIC_DATUM>
<LATITUDE>46.949722</LATITUDE>
<LONGITUDE>-17.355278</LONGITUDE>
</POSITION>
<!-- END OPTIONAL CONTENT -->
</CDMA_CELL>
</CELL_LIST>
</CDMA>
</TEMS_CELL_EXPORT>
271
Try to match cell parameters in the cell file, also considering the
geographical position of the sample. Specifically:
If multiple matches are found within a 100 km radius, the closest cell is
picked.
272
G.1.
273
G.2.
274
275
276
Index
Index
Numerics
3GPP band number 59
A
access class lock 201
action bar 28
active set (CDMA) 60
active set (WCDMA) 54
Agent Configuration data view 254
Agent Overview data view 253
Agent Script Progress data view 252
Agent Serving Cells data view 251
Agent Test Status data view 251
agents (in multi-device TEMS Pocket configuration) 242
altitude 92
APN 79
AQM 205
implementation in TEMS Pocket 206
licensing for 25
AQM action settings (in script) 164
AQM Progress data view 83
ARFCN 44, 51
ARQ mode (EDGE) 70
attachments to email, storage location for 32
audio quality measurement
See AQM
Automatic Repeat Request Mode (EDGE) 70
autostart of TEMS Pocket 217
B
battery charging considerations 33, 149
bit error probability, mean (EDGE) 70
bit error probability, variance (EDGE) 70
BLER (GPRS/EDGE) 70
BLER (HSDPA) 73
277
BLER (LTE) 47
BLER (WCDMA) 46, 56, 75
block error rate (GPRS/EDGE) 70
block error rate (HSDPA) 73
block error rate (LTE) 47
block error rate (WCDMA) 46, 56, 75
block retransmission rate (GPRS/EDGE) 70
block retransmission rate (HSUPA) 73
BS PA MFRMS (GSM RACH) 63
BSIC 44, 51
C
C value (EDGE) 70
C1 (GSM) 51
C2 (GSM) 51
Call Reestablishment (GSM RACH) 62
candidate set (CDMA) 60
capture function 35
carrier-to-noise ratio (Ec/No) (WCDMA) 46
CCCH Group (paging) 62
CDMA Cell List data view 60
CDMA Perform data view 67
cell barred lock 200
cell data support (GPRS/EDGE) 70
cell files 31, 188
format of 269
importing 188
storage location for 32
cell identification, algorithms for 272
Cell Identity 44, 45, 47
cell lock
GSM 197
applying from cell list 51
WCDMA
applying from cell list 54
cell name presentation 44, 45, 47, 48, 51, 54, 57, 60
cell prevent
GSM 197
applying from cell list 51
Cell Reselection Criterion (C2) 51
cell selection control 189
GSM 197
cell sites, displaying in Outdoor Map view 142
278
Index
D
Data data views 70
data mode indication 43
data roaming, enabling in phone 33
data traffic, enabling in phone 33
data view actions 36
data views 35
browsing 36
by phone 41
Custom category 95
Data category 70
Dedicated category 61
general properties of 35
279
header of 42
CDMA 47
GSM 44
LTE 46
WCDMA 45
Idle category 51
Layer 3 category 101
Location category 91
Scanning category 68
survey of 36
Test Status category 81
top-level categories of 50
updating in replay mode 185
Wi-Fi category 93
date 92
dedicated mode data views 61
default settings in TEMS Pocket 265
detected neighbors (WCDMA) 54
display format settings for value elements 219
DL bandwidth (LTE) 59
DL frequency (LTE) 59
DRT transmitter, configuration of 224
DRT4311B scanner 210
DTX rate (HSUPA) 73
E
EARFCN 57
EBI 79
Ec (CDMA) 60
Ec/Io (CDMA) 48, 60, 67
Ec/No (WCDMA) 46, 54
E-DPCCH/E-DPDCH retransmission rate 73
email
advice on message size 155
licensing for email testing 153
storage location for email attachments 32
Email action settings (in script) 153
Email Progress data view 84
EPS Bearer ID 79
Establishment Cause (Channel Request, GSM) 62
E-UTRA Carrier RSSI 58, 69
EV-DO Cell List data view 60
EV-DO Perform data view 67
280
Index
F
fast dormancy 202
FER (CDMA) 48, 67
FES (CDMA) 48
file storage locations in TEMS Pocket 31
filemarks, inserting into logfiles 183
Finger Sum (CDMA) 67
Frame Erasure Rate (CDMA) 48, 67
frequency hopping, use of (GSM) 61
FTP action settings (in script) 156
FTP Progress data view 85
G
Google Maps content supported in Outdoor Map 141
GPRS/EDGE Data data view 70
GPRS/EDGE RLC Throughput data view 71
GPS 30, 214
activating in phone 33
281
H
handover control 189
GSM 197
happy rate (HSUPA) 73
HARQ processes on HS-DSCH, number of 72
HDOP 92
header of data view 28, 42
CDMA 47
GSM 44
LTE 46
WCDMA 45
Help menu 221
Hopping Sequence Number 61
hopping, use of (GSM) 61
horizontal dilution of precision 92
HSDPA
actual transport block size 72
block error rate, first retransmission 72
channelization codes on HS-DSCH, number of 72
CQI 72
HARQ processes on HS-DSCH, number of 72
percentage of blocks transmitted successfully on first attempt 72
requested transport block size 72
total number of blocks to be received 72
282
Index
I
Idle action settings (in script) 170
idle mode data views 51
Indoor Map view 29, 128
layers, showing and hiding 140
legend 140
licensing for 25
loading map image into 132
pinpointing in 133
indoor positioning by pinpointing 128
Init Tx Power (WCDMA RACH) 64
Initial Tx Power (LTE RACH) 66
interplay between locking functions 203
invalid parameters, representation of 35
IP Capture action settings (in script) 171
IP data transfer performance (GPRS/EDGE) 70
L
LAC 44, 45
language support 32
latitude 92
launching the TEMS Pocket application 26
Layer 3 messages
audio alerts for 107
categories of 102
exporting settings for 126
importing settings for 126
283
284
Index
uploading 181
longitude 92
LTE band lock 192
LTE Cell Configuration data view 59
LTE Cell Line Chart data view 58
LTE Cell List data view 57
LTE Data data view 76
LTE Dedicated Mode data view 65
LTE EARFCN lock 194
LTE PHY Throughput data view 78
LTE RACH Analysis data view 66
LTE scan data views 69
M
MAC-hs throughput 75
MAIO 61
Map Editor 128
map sets
creating 129
loading into Indoor Map view 132
managing maps in 132
specifying properties for 130
storage location for 32
structure of 128
unloading from Indoor Map view 140
Max Tx Power (WCDMA RACH) 64
MCC 44, 45, 46
measured neighbors (LTE) 57
MME Code 59
MME Group ID 59
MNC 44, 45, 46
Mobile Allocation Index Offset 61
Mobile Country Code 44, 45, 46
Mobile Network Code 44, 45, 46
mobile network scanning 210
modulation coding scheme (EDGE)
on downlink 70
modulation coding scheme (LTE)
on downlink 65
on uplink 65
modulation scheme usage (HSDPA) 73, 75
monitored neighbors (WCDMA) 54
Msg Tx Power (WCDMA RACH) 64
285
MS-TXPWR-MAX-CCH 62
multi-device TEMS Pocket 25, 242
agent status icons 249
assigning scripts to agents 248
availability in product packages 243
composing scripts for 247
connecting to agents in controller 247
disconnecting from agents in controller 247
initial configuration 244
of agents 244
of controller 245
licensing for 25
monitoring agents from controller 249
pinpointing 254
starting and stopping scripts on agents 249
status views displayed on agents 252
storing of logfiles 255
work modes 243
N
neighbor set (CDMA) 60
neighbors (GSM) 51
neighbors (LTE) 57
neighbors (WCDMA) 54
neighbors (Wi-Fi) 94
Network Identification 48
NID 48
NSAPI 79
O
Outdoor Map view 30, 141
displaying cell sites in 142
displaying events in 142
Follow function 145
Google Maps content type 146
layers, showing and hiding 144
legend 144
map controls in 145
Online/Offline Mode 146
Panning function 145
plotting routes in 141
overview of TEMS Pocket 24
Own/Other data ratio (GPRS/EDGE) 70
286
Index
P
Packet Dedicated Traffic Channel 61
Packet Error Rate (CDMA) 48, 67
Paging Block Index (GSM) 63
Paging Group (GSM) 63
Paging Multiframe (GSM) 63
Parallel action settings (in script) 169
Parallel action, success criteria for 114
Pathloss Criterion (C1) 51
PCA 63
PCAP files 171, 182
storage location for 31
PCCCH Group (paging) 62
PCI 57, 69
PCIG 59
PDN address 79
PDP address (IPv4) 79
PDP Context Information data view 79
PDP context state 79
PDSCH BLER (LTE) 77
PDSCH modulation coding scheme (LTE) 77
PDSCH resource blocks (LTE) 65, 77
PDSCH throughput (LTE) 77, 78
PDTCH 61
PER (CDMA) 48, 67
phones supported 1
Phy Cell ID Group 59
Phy ID 59
Ping action settings (in script) 159
Ping Progress data view 87
pinpointing 29, 133
according to planned route 133, 137
coexistence with other TEMS Pocket functions 134
licensing for 25
manual 133, 135
plotting route markers with RF data
selectable value elements 263
plotting route markers with value elements 134
planned routes 137
PN offset 48, 60
POLQA 205
implementation in TEMS Pocket 165
287
positioning
by GPS 30
by pinpointing 29
Power Control Algorithm (WCDMA) 63
Power Ramp Step (WCDMA RACH) 64
Preamble count (WCDMA RACH) 64
Preamble offset (WCDMA RACH) 64
Preamble step size (LTE RACH) 66
Preambles, maximum number of (LTE RACH) 66
Preambles, maximum number of (WCDMA RACH) 64
Preambles, number of transmitted (LTE RACH) 66
Premium product package 25
prerequisites for running TEMS Pocket 24
preventing cells
GSM 51, 197
product packages for TEMS Pocket 24, 256
Professional product package 24
PUCCH Tx Power 65
PUSCH modulation coding scheme (LTE) 77
PUSCH throughput (LTE) 77, 78
PUSCH Tx Power 65
R
RACH latency (LTE RACH) 66
RACH procedure result (LTE RACH) 66
RACH procedure type (LTE RACH) 66
RACH signaling reason (LTE RACH) 66
Radio Link Timeout 44, 61
Random Reference (Channel Request, GSM) 62
Rank 1/2 (LTE) 76
RAT indication 43
RAT lock 191
in phones regular user interface 192
Receive Bit Error Rate (RxQual) 44, 53, 61
Receive Power (CDMA) 48, 67
Received Signal Code Power (CDMA) 60
Received Signal Code Power (WCDMA) 46, 54, 56
Received Signal Level (RxLev) 44, 51, 53
Reference Signal Received Power (LTE) 47, 57, 69
Reference Signal Received Quality (LTE) 47, 57, 69
Remote product package 25, 232
replaying logfiles 184
Retransmissions, maximum number of (GSM RACH) 62
288
Index
RF channel 48, 60
RF Mode (CDMA) 67
RLC/MAC data transfer performance (GPRS/EDGE) 70
RLP Throughput data view 80
RLT 44, 61
route files 131
storage location for 32
RRC State (LTE) 76
RRC State (WCDMA) 63
RSCP (WCDMA) 46, 54, 56
RSRP (LTE) 47, 57, 58, 69
RSRQ (LTE) 47, 57, 69
RSSI (Wi-Fi) 94
Rx Power (CDMA) 48, 67
RxLev (GSM) 44, 51, 53
RxQual (GSM) 44, 53, 61
S
Samsung Galaxy Note GT-N8020 1
control functions supported 190
data views supported 41
Samsung Galaxy Note II SCH-I605 1
data views supported 41
Samsung Galaxy Note II SGH-I317 1
control functions supported 190
data views supported 41
Samsung Galaxy S III GT-I9305 1
control functions supported 190
data views supported 41
Samsung Galaxy S III SCH-R530M 1
data views supported 41
Samsung Galaxy S III SGH-I747 1
control functions supported 190
data views supported 41
Samsung Galaxy S III SPH-L710 1
data views supported 41
Samsung Galaxy S4 GT-I9505 1
control functions supported 190
data views supported 41
Scan action settings (in script) 175
scanning
of mobile networks 210
licensing for 25
289
290
Index
T
TAB files 131
tablets
supported 1
TEMS Pocket user interface on 31, 222
TAC 46
tags, adding to logfile name 151
TCH 61
TEMS Automatic 181
TEMS Capability Control app 273
TEMS Discovery 30, 184
loading logfiles in 137
291
292
Index
U
UARFCN 45, 54
UE Transmit Power (GSM) 44, 53, 61
UE Transmit Power (WCDMA) 46, 56, 63
user interface of TEMS Pocket 28
UTRA Carrier RSSI 45, 56
V
value elements presentable in Indoor Map view 263
vocoder lock 200
Voice + Data action
settings for 167
success criteria for 115
Voice action settings (in script) 162
Voice MO/Voice MT Progress data view 89
Voice MT action settings (in script) 163
W
Wait action settings (in script) 176
WCDMA band lock 192
WCDMA Cell Line Chart data view 56
WCDMA Cell List data view 54
WCDMA cell lock 195
WCDMA Dedicated Mode data view 63
WCDMA RACH Analysis data view 64
what was new in TEMS Pocket 12.0 23
what was new in TEMS Pocket 12.1 23
what was new in TEMS Pocket 12.2 22
what was new in TEMS Pocket 12.3 22
what was new in TEMS Pocket 12.4 21
what was new in TEMS Pocket 13.0 11
what was new in TEMS Pocket 13.1 8
what was new in TEMS Pocket 13.2 5
whats new in this version of TEMS Pocket 3
Wi-Fi action settings (in script) 177
Wi-Fi Cell List data view 94
Wi-Fi data view 93
Wi-Fi scanning 212
work modes in TEMS Pocket 256
293
Y
YouTube action settings (in script) 166
YouTube app settings 166
YouTube Progress data view 89
294
www.ascom.com/tems
Ascom reserves the right to change specifications without notice. Ascom acknowledges all registered trademarks appearing herein.
Ascom 2014. All rights reserved. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.