• No results found

TEMS Pocket 11.2 Xperia ARC UserManual

N/A
N/A
Protected

Academic year: 2021

Share "TEMS Pocket 11.2 Xperia ARC UserManual"

Copied!
114
0
0

Loading.... (view fulltext now)

Full text

(1)

for Sony Ericsson Xperia arc, Sony Ericsson Xperia

Play CDMA, Samsung Galaxy S 4G

(2)

errors or inaccuracies in current information, or improvements to programs and/or equipment may be made by Ascom Network Testing AB at any time without notice. These changes will, however, be incorporated into new editions of this manual.

No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of the copyrighted owner, Ascom Network Testing AB.

TEMS is a trademark of Ascom.

All other trademarks are the property of their respective holders.

© Ascom 2011. All rights reserved.

(3)

Contents

1. Introduction

1

1.1. What’s New in TEMS Pocket 11.2 . . . 1

1.1.1. New Phones . . . 1

1.1.2. CDMA Support . . . 2

1.1.3. Logfile Replay. . . 2

1.1.4. Manual Logfile Recording. . . 2

1.1.5. Cell File Support. . . 2

1.1.6. Multi-RAB Service Testing (Concurrent Voice and Data). . . . 3

1.1.7. Plotting of Measurements in Indoor Map View. . . 3

1.1.8. Simplified Map Set Reuse . . . 3

1.1.9. Using TEMS Pocket with DRT Test Transmitter . . . 3

1.2. What Was New in TEMS Pocket 11.1. . . 3

1.2.1. Indoor Map . . . 3

1.2.2. Pre-planned Indoor Routes . . . 4

1.2.3. Support for MapInfo TAB Files . . . 4

1.2.4. RACH Analysis Data Views . . . 4

1.2.5. Logfile Tags . . . 4

1.2.6. Event Log . . . 4

1.3. What Was New in TEMS Pocket 11.0. . . 5

1.3.1. New UMTS Phones: Sony Ericsson Xperia arc . . . 5

1.3.2. Main Features of TEMS Pocket 11.0 . . . 5

2. Overview of TEMS Pocket

6

2.1. Prerequisites for Running TEMS Pocket. . . 6

2.2. Launching the TEMS Pocket Application . . . 6

2.3. TEMS Pocket User Interface. . . 7

2.3.1. Top-level TEMS Pocket Screen . . . 7

2.3.2. Data View Header . . . 7

2.3.3. Indoor Map View . . . 8

2.3.4. Scripts . . . 8

(4)

ii 2.3.6. Logfiles. . . 8 2.3.6.1. Logfile Recording . . . 8 2.3.6.2. GPS Positioning . . . 9 2.3.7. Positioning by Pinpointing . . . 9 2.3.8. Cell Files . . . 9

2.3.9. Cell Control Functions (Samsung Galaxy S 4G only) . . . 9

2.3.10. TEMS Pocket Menus . . . 10

2.4. TEMS Pocket File Storage Locations . . . 10

2.5. Language Support . . . 10

2.6. General Advice on Using TEMS Pocket . . . 11

2.6.1. Controlling the Phone’s Choice of Bearer . . . 11

2.6.2. Configuring Other Phone Settings . . . 11

2.6.3. TEMS Pocket vs. TEMS Investigation . . . 11

2.7. Exiting TEMS Pocket . . . 12

3. Data Views

13

3.1. General Data View Properties . . . 13

3.2. Survey of Data Views . . . 13

3.3. Data View Header. . . 16

3.3.1. Data View Header for GSM . . . 16

3.3.2. Data View Header for WCDMA . . . 17

3.3.3. Data View Header for CDMA . . . 18

3.4. Data View Body . . . 19

3.4.1. Top-level Data View Categories . . . 19

3.4.2. Idle Data Views . . . 20

3.4.2.1. GSM Cell List Data View. . . 20

3.4.2.2. WCDMA Cell List Data View . . . 21

3.4.2.3. CDMA Cell List Data View . . . 22

3.4.3. Dedicated Data Views . . . 23

3.4.3.1. GSM RACH Analysis Data View . . . 23

3.4.3.2. GSM Dedicated Mode Data View . . . 25

3.4.3.3. WCDMA RACH Analysis Data View . . . 26

3.4.3.4. WCDMA Dedicated Mode Data View . . . 27

3.4.3.5. CDMA/EVDO Perform Data View . . . 28

3.4.4. “Data” Data Views . . . 29

3.4.4.1. “GPRS/EDGE Data” Data View . . . 29

3.4.4.2. “HSPA Data” Data View . . . 30

3.4.4.3. “CDMA/EVDO Data” Data View . . . 32

3.4.5. Test Status Data Views . . . 33

(5)

3.4.6. Location Data Views. . . 38

3.4.6.1. Indoor Map View . . . 38

3.4.6.2. GPS Data View . . . 38

4. Events

39

4.1. Event Log . . . 39

4.1.1. Refreshing the Event Log. . . 39

4.1.2. Clearing the Event Log. . . 40

4.2. List of Logged Events . . . 40

4.2.1. Script Events . . . 40

4.2.2. Session Events. . . 40

4.2.2.1. Success Criteria for “Voice + Data” Action . . . 42

4.2.3. Logfile Recording Events . . . 42

5. The Indoor Map View

43

5.1. The Map Editor . . . 43

5.1.1. Creating Map Sets . . . 43

5.1.2. Specifying Map Set Properties . . . 44

5.1.3. Managing Maps in a Map Set. . . 45

5.2. Loading a Map Set into the Indoor Map View . . . 46

5.3. Pinpointing Your Test Route . . . 47

5.3.1. Fundamentals of Pinpointing . . . 47

5.3.2. Coexistence with Other TEMS Pocket Functions. . . 47

5.3.3. Plotting Route Markers with RF Data . . . 47

5.3.4. Manual Pinpointing. . . 48

5.3.5. Pinpointing According to Planned Route . . . 51

5.4. Unloading a Map Set. . . 53

6. Scripts

54

6.1. Introduction to Scripts . . . 54

6.2. Composing Scripts . . . 55

6.2.1. FTP Action Settings . . . 56

6.2.2. HTTP Action Settings . . . 57

6.2.3. Voice Action Settings . . . 57

6.2.4. Voice + Data Settings. . . 58

6.2.5. Idle Settings . . . 59

6.2.6. Control Function Settings . . . 59

(6)

iv

6.2.9. The Assembled Script . . . 61

6.2.10. Rearranging and Deleting Actions in a Script . . . 61

6.2.11. Deleting Scripts . . . 62

6.3. Starting and Stopping a Script . . . 62

6.3.1. Guard Times . . . 63

7. Logfiles

64

7.1. Logfiles in TEMS Pocket: Overview . . . 64

7.2. Recording Logfiles Manually. . . 64

7.2.1. Limitations of Manual Logfile Recording . . . 65

7.3. Replaying Logfiles. . . 65

7.3.1. Coexistence with Other Phone and TEMS Pocket Functions . . . 67

7.4. Post-processing of Logfiles. . . 67

7.4.1. Compatibility with Other TEMS Products. . . 68

8. Cell Files

69

9. Cell Control Functions (Samsung Galaxy

S 4G only)

70

9.1. RAT Lock . . . 71

9.2. WCDMA Cell Lock . . . 72

9.3. GSM Cell Lock . . . 73

9.4. WCDMA Band Lock, GSM Band Lock . . . 74

9.5. Interplay between Cell Control Functions . . . 75

9.6. Coexistence with Other TEMS Pocket Functions . . . 75

9.7. Resetting All Cell Control Functions . . . 75

10. About Screen

76

11. Battery Charging Considerations

77

11.1. Choice of Phone Charger . . . 77

(7)

12. Configuration of DRT Transmitter

78

12.1. Setting Up the Transmitter . . . 78

12.1.1. Changing between Ethernet and Wi-Fi Network Configuration Modes . . . 80

12.2. Configuring the PC for Direct Connection . . . 80

12.3. Configuring the PC for LAN Connection . . . 81

12.4. Verifying the Configuration . . . 82

12.5. Configuring Transmitter Cell Information. . . 82

12.5.1. Configuring the Transmitter Using Nome . . . 82

12.5.2. Configuring the Transmitter Using Web Interface . . . 84

13. Support Contact Information

86

13.1. Technical Support . . . 86

13.2. TEMS Bulletins . . . 86

Appendix A. Graphic Representation of Data

87

A.1. GSM Data . . . 87

A.2. WCDMA Data . . . 87

A.2.1. HSPA Data. . . 88

A.3. CDMA Data. . . 88

A.4. GPS Data . . . 88

Appendix B. Value Elements Presentable in

Indoor Map View

89

B.1. GSM Value Elements . . . 89

B.2. WCDMA Value Elements . . . 89

B.3. CDMA Value Elements . . . 89

Appendix C. Default Settings in TEMS Pocket

90

C.1. Script Editor . . . 90

C.1.1. Global Settings . . . 90

C.1.2. FTP Action Settings . . . 90

C.1.3. Voice Action Settings. . . 90

C.1.4. Idle Action Settings . . . 90

(8)

vi

Appendix D. Cell File Format

91

Appendix E. Cell Identification

94

(9)

1.

Introduction

Welcome to TEMS Pocket.

TEMS Pocket is an advanced cellular network diagnostics tool built into a mobile phone. TEMS Pocket is suitable for day-to-day verification, maintenance and troubleshooting of cellular networks but is also handy for many cell planning tasks.

This document describes TEMS Pocket 11.2 as implemented on the following phones:

• Sony Ericsson Xperia arc (GSM/WCDMA) • Sony Ericsson Xperia Play CDMA • Samsung Galaxy S 4G (GSM/WCDMA).

1.1.

What’s New in TEMS Pocket 11.2

1.1.1.

New Phones

• Sony Ericsson Xperia Play CDMA

– CDMA2000 EV-DO Rev. A, up to 3.1 Mbit/s – CDMA 800/1900 MHz

– 4.0 inch, 854 480 pixel, capacitive multi-touch display

– 5 megapixel camera with 800 480 pixel, 30 fps video recording – Google Android 2.3

– Qualcomm 1 GHz MSM8655 chipset – Integrated GPS with A-GPS support • Samsung Galaxy S 4G (model SGH-T959V)

(10)

2

– WCDMA 2100 MHz (Band I), 1900 MHz (Band II), 2100/1700 MHz AWS (Band IV)

– GSM/GPRS/EDGE quad-band, 850/900/1800/1900 MHz – 4.0 inch, 800 480 pixel, capacitive multi-touch display – 5 megapixel camera with 720p, 30 fps video recording – Google Android 2.3

– ST Ericsson 1 GHz Hummingbird chipset

– TEMS Pocket control functions: RAT/band/channel/cell lock – Integrated GPS with A-GPS support

1.1.2.

CDMA Support

TEMS Pocket 11.2 is the first Android TEMS Pocket release to be implemented on a CDMA device (Sony Ericsson Xperia Play CDMA). CDMA data presentation includes cell list, radio link and data throughput performance data views. The presentation is similar to corresponding data views in the TEMS Pocket 8.x releases built on the Windows Mobile platform.

1.1.3.

Logfile Replay

Logfiles from TEMS Pocket 11.2 can be replayed in TEMS Pocket itself. The presentation of logfile data is exactly the same as in live mode.

1.1.4.

Manual Logfile Recording

Logfile recording can now also be initiated manually, as opposed to being controlled by a script. The manual recording function is wholly separate from the scripting.

1.1.5.

Cell File Support

A cell file can be imported in TEMS Pocket, enabling presentation of network cells by name in the TEMS Pocket user interface. Network cell parameters (GSM: ARFCN and BSIC; WCDMA: UARFCN and SC; CDMA: RF channel and PN offset) are matched with entries in the cell file, and if the phone has its GPS enabled its geographical position is also considered.

(11)

1.1.6.

Multi-RAB Service Testing (Concurrent Voice and

Data)

An action type for concurrent CS voice and PS data testing is introduced in this version of TEMS Pocket. Either FTP or HTTP can be chosen as data service. This action permits convenient testing of multi-RAB operation.

1.1.7.

Plotting of Measurements in Indoor Map View

Measurement data can be plotted along testing routes in the Indoor Map view in the form of color-coded route markers.

1.1.8.

Simplified Map Set Reuse

If you have a TEMS Pocket logfile containing an indoor map set, you can reuse that map set in TEMS Pocket by simply placing the logfile in the map set directory on the phone’s memory card.

1.1.9.

Using TEMS Pocket with DRT Test Transmitter

TEMS Pocket 11.2 can be used in conjunction with a DRT4302A+ test transmitter. Such a device can be included in the TEMS Pocket 11.2 product package.

The DRT test transmitter is controlled from a PC, to which it can be connected directly by means of a cable, over a local area network, or via Wi-Fi.

1.2.

What Was New in TEMS Pocket 11.1

1.2.1.

Indoor Map

The indoor map function enables import of maps and positioning of

measurements in indoor locations and other places where GPS coverage is lacking. The positioning is done by pinpointing the test route in the Indoor Map view, thereby creating a logfile archive that contains the measurements, the waypoints of the route, and the map image.

(12)

4

1.2.2.

Pre-planned Indoor Routes

Routes pinpointed on an indoor map can be saved and reused as predetermined routes for the user to follow. This allows quicker and easier navigation and pinpointing using only three keys, eliminating the need to pan and zoom to insert new waypoints.

This feature can be used to create walk route instructions for teams in the field and in particular to ensure that the same route is followed on each occasion during recurring tests, for example, before and after implementing changes in the network.

1.2.3.

Support for MapInfo TAB Files

Supplying a MapInfo TAB file together with a floor plan allows automatic positioning of the floor plan. This eliminates a manual step that is otherwise required when post-processing unpositioned floor plans, saving the user time and effort.

MapInfo is a widely used format, which enables more efficient ways of working with other solutions, for instance in-building project management tools such as iBwave Design.

1.2.4.

RACH Analysis Data Views

These new data views display parameter settings and data related to RACH signaling and paging in GSM and WCDMA. The views reveal, among other things, how the latest RACH procedure unfolded and how changes in the radio environment affect the RACH procedure.

1.2.5.

Logfile Tags

When setting up a script in TEMS Pocket, you can define a tag that will be added to the name of each logfile produced by that script. This feature can be used together with the advanced scripting functions in TEMS Discovery to pre-process files tagged with customer-specific metadata, e.g. team, area, or campaign name. Tags can also be used to help sort and organize logfiles.

1.2.6.

Event Log

The event log displays events pertaining to the execution of scripts and actions within them. Events carry service-dependent performance data, such

(13)

as mean throughput for data sessions. Events are helpful in troubleshooting services and their settings.

1.3.

What Was New in TEMS Pocket 11.0

TEMS Pocket 11.0 was the first TEMS Pocket Professional release on the Google™ Android™ operating system.

1.3.1.

New UMTS Phones: Sony Ericsson Xperia arc

TEMS Pocket 11.0 is implemented on the Android-based Sony Ericsson Xperia arc smartphone, which comes in two models: LT15i and LT15a. Some of their key features are as follows:

• WCDMA/HSPA 7.2 Mbit/s DL (Category 8), 5.76 Mbit/s UL (Category 6) – LT15i: 900/2100 MHz

– LT15a: 800/850/1900/2100 MHz

• GSM/GPRS/EDGE quad-band, 850/900/1800/1900 MHz • 8.1 megapixel camera with 720p HD video recording

• 4.2 inch, 854 480 pixel, capacitive multi-touch display with Sony Mobile Bravia™ Engine™

• Google Android 2.3

• Qualcomm 1 GHz MSM8255 chipset • Integrated GPS

1.3.2.

Main Features of TEMS Pocket 11.0

• Suite of data views for real-time monitoring

• Intuitive graphical presentation of data • RF KPIs presented as LED-style indicators

• Scripting of service testing: Voice, HTTP, FTP UL/DL, Idle • Automatic logfile recording and upload

• GPS positioning of recorded measurements • Over-the-air software upgrades

(14)

6

2.

Overview of TEMS Pocket

2.1.

Prerequisites for Running TEMS Pocket

The phone must have a memory card and a SIM card installed. (The latter requirement does not of course apply to the Xperia Play device.)

2.2.

Launching the TEMS Pocket Application

Note: After running the update service/firmware update, you need to ensure that the phone has a valid data connection. If no data connection is established, TEMS Pocket will fail in downloading the license and refuse to start up. If this occurs, you will be notified by a popup message.

• Launch TEMS Pocket by tapping the TEMS Pocket icon in the phone’s application launcher.

This screen appears while TEMS Pocket is starting up.

(15)

2.3.

TEMS Pocket User Interface

2.3.1.

Top-level TEMS Pocket Screen

2.3.2.

Data View Header

In the topmost part of the data view is always shown a set of general data related to the cellular technology currently in use.

See also section3.3.

The indicators and symbols at the very top of the screen are the same as in the commercial phone.

Once TEMS Pocket has initialized, it will display a screen that holds the top-level data view categories.

Everything about the data views is covered in chapter3. Indicators of radio quality Current RAT Measurements and parameters for current RAT

Cell Global Id (CGI) of serving cell

(16)

8

2.3.3.

Indoor Map View

The Indoor Map view is used for pinpointing a test route on a floor plan or other map image. See chapter5.

2.3.4.

Scripts

TEMS Pocket offers the use of scripts for automated testing of various services. See chapter6.

2.3.5.

Events

When you run a script in TEMS Pocket, events are logged pertaining to the progress and outcome of the scripted actions. See chapter4.

2.3.6.

Logfiles

2.3.6.1. Logfile Recording

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 chapter7.

(17)

2.3.6.2. GPS Positioning

TEMS Pocket supports positioning of data in logfiles using the phone’s built-in GPS.

2.3.7.

Positioning by Pinpointing

In an indoor environment or other location without GPS coverage, you can use the Indoor Map view (see chapter5) to pinpoint your test route. You load an image of your testing area into the Indoor Map view, then indicate your route by marking waypoints on that map. The map image can also be assigned a geographical position.

2.3.8.

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. See chapter8.

2.3.9.

Cell Control Functions (Samsung Galaxy S 4G

only)

TEMS Pocket 11.2 as implemented on the Samsung Galaxy S 4G phone has a number of cell control functions for controlling the phone’s behavior in the cellular network. These include locking the phone to a RAT, band, cell, or channel. See chapter9 for full details.

(18)

10

2.3.10.

TEMS Pocket Menus

2.4.

TEMS Pocket File Storage Locations

TEMS Pocket related files are stored on the phone’s memory card in the following locations:

• Cell files: /sdcard/pocket/private/cellfiles/ • Logfiles: /sdcard/pocket/logfiles/

• Map sets (image files and TAB files): /sdcard/pocket/private/mapsets/ • Scripts: /sdcard/pocket/private/scripts/

• Waypoints: /sdcard/pocket/private/waypoints/ • This user’s manual: /sdcard/pocket/

Please note that these locations are not accessible through the TEMS Pocket user interface (nor from the phone’s standard user interface; a third-party Android app is required). Naturally you can always view the memory card directory structure by connecting the phone to a PC.

2.5.

Language Support

The TEMS Pocket 11.2 phones support languages as follows:

• Regular phone user interface: Same as in the commercial phone release. If you press the Menu button on the phone (the button on the right) while a data view or the overview screen is displayed, a menu with TEMS Pocket commands appears at the bottom. From here you can perform all of the actions and configuration tasks referred to in

section2.3 and also inspect some categories of data.

(19)

• TEMS Pocket user interface – Text display: English – User input: English

2.6.

General Advice on Using TEMS Pocket

2.6.1.

Controlling the Phone’s Choice of Bearer

When running a service, the TEMS Pocket phone always uses the best available bearer, which could mean Wi-Fi. This behavior cannot be controlled from the TEMS Pocket application. To force the phone to communicate over a cellular network, you need to deactivate Wi-Fi on the phone: Settings

Wireless & networksWi-Fi.

2.6.2.

Configuring Other Phone Settings

• For the phone’s GPS to be available to TEMS Pocket, it must be enabled in the phone: Under Settings Location & security, make sure Use

GPS satellites is checked.

• Also make sure that data traffic is enabled: Under SettingsWireless

& networksMobile 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 & networksMobile networks, by checking the Data

roaming checkbox.

2.6.3.

TEMS Pocket vs. TEMS Investigation

When a phone possesses a license for both TEMS Pocket and TEMS Investigation, the two applications cannot coexist on the device. For the Sony Ericsson phones, this means that:

Note: There is no support for inputting non-ASCII characters. When entering text strings, only use characters from the ASCII set.

(20)

12

• if you have your TEMS Pocket phone connected to a PC and you start TEMS Investigation on that PC, the TEMS Pocket application will shut down;

• if you connect your TEMS Pocket phone to a PC where TEMS Investigation is running, you cannot start the TEMS Pocket application.

2.7.

Exiting TEMS Pocket

You exit the TEMS Pocket application by pressing the Menu button and then tapping Exit. See section2.3.10.

(21)

3.

Data Views

3.1.

General Data View Properties

Many data views in TEMS Pocket are RAT-specific; there exist, for example, separate cell list data views for each supported RAT. Which views can appear is of course dependent on the range of technologies supported by the phone; which view is shown at a given instant is governed by the RAT the phone is currently using. The switching between views is automatic.

All data views have the same general structure in idle mode and dedicated/ active mode. The presentation combines textual and graphical elements. Whenever a parameter is currently not valid, this is indicated in the data view by a dash “–”.

3.2.

Survey of Data Views

The data views are divided into the categories found on the overview page (section2.3.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. TEMS Pocket

remembers which data view was last displayed in each category; when you return to a category, that view is shown.

The Indoor Map view is included in the Location category, and you can navigate to it by swiping as just described, although it is not a data view in the strict sense.

There is no wraparound when browsing through data views and data view categories (i.e. neither horizontally nor vertically).

(22)

14

Data View Name Displayed Contents Ref.

Idle category

GSM Cell List ARFCN, BSIC, RxLev, C1, and C2 for GSM serving cell and neighbors.

3.4.2.1 WCDMA Cell List UARFCN, scrambling code,

Ec/N0, and RSCP for WCDMA serving cell/active set and neighbors.

3.4.2.2

CDMA Cell List RF channel number, PN offset, Ec/I0, and Ec for CDMA active, candidate, and neighbor sets.

3.4.2.3

Dedicated category GSM Dedicated Mode

GSM dedicated mode radio parameters. 3.4.3.2

WCDMA Dedicated Mode

WCDMA dedicated (connected) mode radio parameters.

3.4.3.4 GSM RACH

Analysis

Parameters and data related to RACH signaling in GSM.

3.4.3.1 WCDMA RACH

Analysis

Parameters and data related to RACH signaling in WCDMA.

3.4.3.3 CDMA/EVDO

Perform

CDMA and EV-DO active mode radio parameters.

3.4.3.5 Data category

GPRS/EDGE Data Parameters and data related to GPRS/ EDGE.

3.4.4.1 HSPA Data Parameters and data related to HSPA. 3.4.4.2 CDMA/EVDO Data Parameters and data related to CDMA/

EV-DO data transfer.

(23)

Data Views by Phone Test Status category

Script Progress Progress data for a script that is being executed. Also shows action-specific information (for FTP, HTTP, voice, etc.).

3.4.5

Location category

Indoor Map See chapter5.

GPS GPS positioning data. 3.4.6.2

Data View Name

Sony Ericsson Xperia Samsung Galaxy S

4G arc Play

CDMA

GSM Cell List WCDMA Cell List CDMA Cell List GSM Dedicated Mode WCDMA Dedicated Mode GSM RACH Analysis WCDMA RACH Analysis CDMA/EVDO Perform GPRS/EDGE Data HSPA Data CDMA/EVDO Data Script Progress Indoor Map GPS

(24)

16

3.3.

Data View Header

In the topmost part of the data view is always shown a set of general data related to the cellular technology currently in use.

3.3.1.

Data View Header for GSM

All data shown in the header pertains to the current serving cell.

ARFCN: Absolute Radio Frequency Channel NumberRxLev: Received Signal Level (dBm)

BSIC: Base Station Identity Code

CGI data (shown if no cell file is loaded)

MCC: Serving cell Mobile Country CodeMNC: Serving cell Mobile Network CodeLAC: Serving cell Location Area Code

CI: Serving cell Cell Identity, 16 bits (= 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.

Indicators (see color key below)

TxPwr: UE Transmit PowerRxQual: Received Signal QualityRxLev: Received Signal Level

RLT: Radio Link Timeout, Current/Max ratio

(25)

Indicator Color Key

3.3.2.

Data View Header for WCDMA

All data shown in the header pertains to the current active set.

UARFCN: UARFCN, UMTS Absolute Radio Frequency Channel NumberRSSI: Received signal strength, equal to UTRA Carrier RSSI

SC: Scrambling Code of serving cell (idle mode) or strongest active set member (connected mode)

CGI data (shown if no cell file is loaded)

MCC: Serving cell Mobile Country CodeMNC: Serving cell Mobile Network CodeLAC: Serving cell Location Area Code

CI: Serving cell Cell Identity, 16 bits (= 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 in order to display CGI instead. The presentation reverts to cell name once you release your finger.

Indicators (see color key below)

Measurement Green Yellow Red

TxPower (dBm) 0 ... 9 10 ... 19 20 ... 31

RxQual 0 1 ... 4 5 ... 7

RxLev (dBm) –75 ... –10 –94 ... –76 –120 ... –95

RLT Curr/Max (%) 100 91 ... 99 0 ... 90

(26)

18

Ec/N0: Carrier-to-noise ratio, Ec/N0RSCP: Received Signal Code PowerBLER: Block Error Rate

Indicator Color Key

3.3.3.

Data View Header for CDMA

All data shown in the header pertains to the current active set. • Channel: RF channel number

RxPwr: Receive Power (dBm)

PN: PN Offset of serving cell (idle mode) or strongest active set member (active mode)

SID and NID (shown if no cell file is loaded)

System ID: System Identification (SID)Network ID: Network Identification (NID)

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.

Measurement Green Yellow Red

TxPower (dBm) –31 ... 0 1 ... 9 10 ... 50 Ec/N0 (dB) –10 ... 0 –15 ... –11 –34 ... –16 RSCP (dBm) –85 ... –15 –99 ... –86 –140 ... –100

BLER (%) 0 ... 20 21 ... 49 50 ... 100

(27)

Indicators (see color key below)

TxPwr: Transmit Power

Ec/Io: Signal-to-noise ratio for strongest active set memberFER: Frame Erasure Rate (%); CDMA specific

PER: Packet Error Rate (%); EV-DO specific Indicator Color Key

3.4.

Data View Body

3.4.1.

Top-level Data View Categories

Measurement Green Yellow Red

TxPwr (dBm) –31 ... 0 1 ... 9 10 ... 50

Ec/Io (dB) –9 ... 0 –23 ... –10 –32 ... –24

FER (%) 0 ... 2 3 ... 5 6 ... 100

PER (%) 0 ... 2 3 ... 5 6 ... 100

On startup, TEMS Pocket displays a screen holding the top-level data view categories: • Idle

• Dedicated • Data • Test Status • Location

They are gone through in the subsections that follow.

You can always return to this screen by pressing the Back button (possibly several times if you are navigating the menu system).

(28)

20

3.4.2.

Idle Data Views

3.4.2.1. GSM Cell List Data View

For the header, see section3.3.1.

The view displays the serving cell (always on top) and up to seven neighbors (in order of descending signal strength).

S: Serving cellN: Neighbor cell.

ARFCN: ARFCN, Absolute Radio Frequency Channel Number.

BSIC: BSIC, Base Station Identity Code. RxLev: Received Signal Level.

C1: Pathloss Criterion C1. 3GPP 45.008, section 6.4

C2: Cell Reselection Criterion C2. 3GPP 45.008, section 6.4

If a cell file is loaded, a string with the following information appears on a separate line below each line of cell data:

Name: Cell name and cell identity according to cell file.

(29)

3.4.2.2. WCDMA Cell List Data View

For the header, see section3.3.2.

Up to eight cells are displayed, each belonging to one of the following categories:

S: Serving cell (idle mode)

A: Active set member (connected mode)M: Monitored neighbor

D: Detected neighbor.

The categories are prioritized as listed above, cells from lower-ranking categories being displayed as far as space allows. Within each category, cells are sorted by descending Ec/N0.

UARFCN: UARFCN, UMTS Absolute Radio Frequency Channel Number.

SC: Scrambling Code.

Ec/No: Ec/N0 (dB), signal-to-noise ratio measured according to 3GPP 25.215, section 5.1.5.

RSCP: Received Signal Code Power (dBm). If a cell file is loaded, a string with the following information appears on a separate line below each line of cell data:

Name: Cell name and cell identity according to cell file.

(30)

22

3.4.2.3. CDMA Cell List Data View

For the header, see section3.3.3.

Up to eight cells are displayed, each belonging to one of the following categories:

A: Active setC: Candidate setN: Neighbor set.

The categories are prioritized as listed above, cells from lower-ranking categories being displayed as far as space allows. Within each category, cells are sorted by descending Ec/I0.

Channel: RF channel number. PN: PN offset.

Ec/Io: Ec/I0 (dB), signal-to-noise ratio. Ec: Received signal code power (dBm). If a cell file is loaded, a string with the following information appears on a separate line below each line of cell data:

(31)

3.4.3.

Dedicated Data Views

3.4.3.1. GSM RACH Analysis Data View

For the header, see section3.3.1.

The view displays parameters and data related to RACH signaling and paging in GSM. Establish Cause: Establishment cause in Channel Request message. 3GPP 44.018, section 9.1.8

Random Reference: Random Reference in Channel Request message. 3GPP 44.018, section 9.1.8

Max TxPower: The maximum TX power level an MS may use when accessing on a Control Channel, CCH. 3GPP 44.018, table 10.5.2.4.1, MS-TXPWR-MAX-CCH

Max Retransm: Maximum number of retrans-missions. 3GPP 44.018, table 10.5.2.29.1 Reestablish: Call reestablishment allowed/not allowed in the cell. 3GPP 44.018, table 10.5.2.29.1

Tx Integer: Number of slots used to spread the transmission. 3GPP 44.018, table 10.5.2.29.1 CCCH Group / PCCCH Group: The former of these appears for CS and the latter for PS data.

• CS data: Mobiles in a specific CCCH group will listen for paging messages and make random accesses only on the specific CCCH to which the CCCH group belongs.

3GPP 45.002, section 6.5.2, CCCH_GROUP • PS data: Same mechanism, but with

“CCCH” replaced by “PCCCH”. 3GPP 45.002, section 6.5.6, PCCCH_GROUP

(32)

24

(continued)

Paging Group: The mobile’s paging group. 3GPP 45.002, sections 6.5.2, 6.5.6,

PAGING_GROUP

Paging Multiframe: Paging multiframe: 3GPP 45.002, section 6.5.3

Paging Blk Idx: Paging block index: 3GPP 45.002, section 6.5.3

BS_PA_MFRMS: Number of 51-multiframes between transmission of paging messages to mobiles of the same paging group {2 ... 9}.

(33)

3.4.3.2. GSM Dedicated Mode Data View

For the header, see section3.3.1.

Channel Mode: GSM channel mode, one of: • FR = Voice, Full Rate

• EFR = Voice, Enhanced Full Rate • HR = Voice, Half Rate

• AFR = Voice, AMR Full Rate • AHR = Voice, AMR Half Rate • CSD = Circuit-switched data • SIG = Signaling only

TCH ARFCN: Traffic Channel (TCH ARFCN) or Stand-alone Dedicated Control Channel (SDCCH ARFCN) or Packet Dedicated Traffic Channel (PDTCH ARFCN). Hopping channels are shown one at a time.

RLT Ratio: Radio Link Timeout, ratio of current value to maximum (= start) value, expressed in percent. 3GPP 45.008, section 5.2

RxQual: Receive Bit Error Rate, RxQual; scale defined in 3GPP 45.008, section 8.2.

Timeslots: List of timeslots in use, e.g. “157” meaning timeslots 1, 5, and 7.

Timing Adv: Timing Advance. TxPower: UE Transmit Power (dBm). Channel Type: Channel type, one of {BCCH, PBCCH, PDTCH, SDCCH, TCH/F, TCH/H}. Subchannel: Subchannel Number {0 ... 7}. Ciphering: Ciphering Mode, one of {A5/1, A5/2, A5/3, GEA/1, GEA/2}. 3GPP 43.020 Hopping: Use of frequency hopping: On/Off. HSN: Hopping Sequence Number {0 ... 63}. MAIO: MAIO, Mobile Allocation Index Offset {0 ... 63}. 3GPP 45.002

(34)

26

3.4.3.3. WCDMA RACH Analysis Data View

For the header, see section3.3.2.

The view displays parameters and data related to RACH signaling in WCDMA.

The WCDMA random access procedure is comprehensively described in 3GPP 25.214, section 6.1.

Init Tx Power: Preamble_Initial_Power, transmit power of first RACH preamble (dBm). Msg Tx Power: Transmit power of RACH preamble to which a response was obtained (dBm).

Max Tx Power: Maximum allowed transmit power of RACH preamble (as well as overall; dBm).

Preamble Count: Number of preambles used in this preamble ramping cycle.

Max Preamble: Preamble Retrans Max, maximum number of preambles in one preamble ramping cycle.

Preamble Offset: Power Ramp Step, power increase between consecutive preambles (dB).

(35)

3.4.3.4. WCDMA Dedicated Mode Data View

For the header, see section3.3.2.

RRC State: RRC State, one of {CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH, Idle}. SIR: Signal-to-Interference Ratio (dB). TxPower: UE Transmit Power (dBm).

PCA: Power Control Algorithm: 3GPP 25.331 TPC UL: Transmit Power Control on uplink over the last 0.5 seconds: percentage of power control commands that were “increase” commands.

TPC Step Size: Transmit Power Control Step Size (dB). 3GPP 25.331

TPC DL: Transmit Power Control on downlink over the last 0.5 seconds: percentage of power control commands that were “increase” commands.

(36)

28

3.4.3.5. CDMA/EVDO Perform Data View

For the header, see section3.3.3.

This view is common to CDMA and EV-DO.

RF Mode:

For CDMA: “<technology> <phone state>”, where

• <technology> = “CDMA” • <phone state> = one of

“Init”, “Idle”, “Access”, “Traffic”.

For EV-DO: “<technology> <AT state>”, where • <technology> = “1xEV-DO”

• <AT state> = one of

“Inactive”, “Acquisition”, “Sync”, “Idle”, “Access”, “Connected”.

FER: Frame Erasure Rate (%). CDMA specific. PER: Packet Error Rate (%). EV-DO specific. RxPwr: Receive Power (dBm).

TxPwr: Transmit Power (dBm).

Ec/Io: Signal-to-noise ratio for strongest active set member (= topmost PN in CDMA Cell List data view, section3.4.2.3; unit dB).

Finger SUM: Finger Sum, total signal-to-noise ratio (Ec/Io) for all Rake fingers (dB).

(37)

3.4.4.

“Data” Data Views

3.4.4.1. “GPRS/EDGE Data” Data View

For the header, see section3.3.1.

All data shown here pertains to the phone’s latest reporting period, unless otherwise noted. TS’s used: Timeslots used on uplink and downlink.

CS used: (updated for each multiframe) • GPRS: Channel coding scheme on

downlink/uplink {CS1 ... CS4}. • EDGE: Modulation coding scheme on

downlink/uplink {MCS1 ... MCS9}. BEP: EDGE mean bit error probability. BEP Variance: EDGE bit error probability variance.

Link Adaptation: Automatic Repeat Request Mode {ARQ1, ARQ2}. 3GPP 44.060, section 9.2.3.1

C-Value: EDGE C Value {0 ... 63}.

Own/Other data: Own data/Other data ratio during last multiframe.

Cell data support: Technology supported in cell: GPRS or EDGE.

Bitrate UL/DL: IP and RLC/MAC level throughputs on uplink and downlink. All of these figures are updated once every second. Rx/Tx error: RLC level only. Updated once every second.

Rx error: Percentage of data blocks erroneously decoded on downlink.1 • Tx error: Percentage of data blocks

retransmitted on uplink.1

(38)

30

3.4.4.2. “HSPA Data” Data View

For the header, see section3.3.2.

All data shown here pertains to the phone’s latest reporting period, unless otherwise noted.

HS-DSCH:

Act block size (bits): Actual HS-DSCH transport block size in bits: minimum/ average/maximum.

Req block size (bits): Requested transport block size in bits (corresponding to minimum CQI): minimum/average/ maximum.

CQI: Minimum/average/maximum value of CQI (Channel Quality Indicator). CQI values are defined in 3GPP 25.214, section 6A.2.

Codes: Number of channelization codes used on the HS-DSCH: minimum/average/ maximum. Obtained with Samsung Galaxy S 4G only; not logged by Sony Ericsson phones.

Blocks fail: Block error rate on HS-DSCH for first retransmission. Updated once every second.

Blocks success: Percentage of blocks on HS-DSCH that were transmitted

successfully on first attempt (zero retrans-missions). Updated once every second. • Blocks/s: Total number of blocks to be

received on the HS-DSCH during the latest one-second period.

HARQ processes: Number of active HARQ (Hybrid Automatic Repeat Request) processes on the HS-DSCH.

(39)

For the header, see section3.3.2.

(continued)

HSDPA QAM rate: The percentage of time 16-QAM was used as modulation method.

E-DCH:

DTX: DTX rate (%) on uplink.Retransmission: Number of

retrans-missions on E-DPCCH/E-DPDCH divided by the number of TTIs.

Happy: Happy rate (%), i.e. the percentage of TTIs where the UE was happy, as defined in 3GPP 25.321, section 11.8.1.5. • Avg. Grant index: Average value of

Serving Grant Index.

Avg. Tx block size: Average transport block size in bits on E-DCH.

Bitrate UL/DL: IP- and RLC-level throughputs on uplink and downlink. All of these figures are updated once every second.

Rx/Tx Error: (RLC level only; updated once every second)

Rx Error: Percentage of data blocks erroneously decoded on downlink. • Tx Error: Percentage of data blocks

(40)

32

3.4.4.3. “CDMA/EVDO Data” Data View

For the header, see section3.3.3.

Chart “RLP Throughput Distribution”

This histogram shows the distribution of RLP-level data throughput on uplink (blue) and downlink (red).

To reset the statistics:

Press the Menu button and choose

ActionsClear History.

The histogram is cleared automatically when you start a script, as well as when you start and stop logfile replay.

Charts “RLP UL Throughput”, “RLP DL Throughput”

These line charts track RLP-level data throughput over time: uplink (blue), downlink (red). They behave the same way as the line charts in the Script Progress data view: see section3.4.5.1.

(41)

3.4.5.

Test Status Data Views

3.4.5.1. Script Progress Data View

For the header, see sections 3.3.1–3.3.3.

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 top part of the view (beneath the header) gives general information on script progress, independent of the type of action being run. The bottom part contains action-specific progress and service performance data. For certain action types, a graph is plotted which scrolls from right to left in real time. The numeric labels in the graph denote the time (in seconds) that has elapsed since the

corresponding value was measured.

The graph always shows the latest 60 seconds of execution time for the type of action that is currently running (e.g. FTP), even if actions of other types have intervened (e.g. HTTP, Voice).

How to compose scripts is explained in chapter6.

general

(42)

34

3.4.5.1.1. General Script Information and Progress

Script Name: The name of the script that is currently running.

GPS/Recording: Use of GPS / Use of logfile recording.

Iterations: Total number of completed script iterations.

Success/Failure: Total number of successfully completed script actions (all iterations) / Total number of failed script actions (all iterations). Runtime: Total elapsed script execution time (all iterations).

Actions: Index of current action in list of actions / Total number of actions in script. Elapsed Time: Elapsed execution time for current action (reset at start of new action). Current Action: Type of current action: FTP, HTTP, Voice, etc.

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).

(43)

3.4.5.1.2. FTP Action Progress

3.4.5.1.3. HTTP Action Progress

FTP Server URL: Name and full path of file being uploaded/downloaded over FTP. The server can be specified by an IPv4 address (12-digit number) or a plain-text name. Direction: FTP session type (UL or DL). Port: The FTP server port used. Throughput: Current uplink/downlink application-level FTP throughput.

Graph

Line chart of uplink/downlink application-level FTP throughput.

For the setup, see section6.2.1.

HTTP URL: The URL of the web page being downloaded.

Transfer Time: Duration of the current HTTP session in seconds.

Throughput: Current downlink application-level HTTP throughput.

Graph

Line chart of downlink application-level HTTP throughput.

(44)

36

3.4.5.1.4. Voice Action Progress

3.4.5.1.5. Voice + Data Action Progress

Dialed number: The number called.

Setup Time: Call setup time in seconds. The call setup time is calculated at the application layer, so it can differ slightly from the call setup time indicated when replaying the file in TEMS Investigation.

Retries: Total number of retries made during the current call.

For the setup, see section6.2.3.

This view is a composite of the voice action progress view (section3.4.5.1.4) and the FTP or HTTP progress view, depending on which data service is run (sections 3.4.5.1.2, 3.4.5.1.3; the graph, however, is not included here).

(45)

3.4.5.1.6. Idle Action Progress

3.4.5.1.7. Logfile Upload Action Progress

3.4.5.1.8. Other Actions

The Control Function and Wait actions do not have a progress screen.

Remaining Time: Execution time remaining of the idle action (in seconds).

For the setup, see section6.2.5.

Logfile in transfer: Name of logfile currently being uploaded.

Files: Number of logfiles uploaded / Total number of logfiles to be uploaded.

Progress: Upload progress, stated as the percentage of logfiles in the current batch that have been uploaded.

(46)

38

3.4.6.

Location Data Views

3.4.6.1. Indoor Map View

This view is not a regular data view, but it is included in the Location category. See chapter5.

3.4.6.2. GPS Data View

This view always presents data from the phone’s internal GPS.

For the header, see sections 3.3.1–3.3.3.

Number of Satellites: The number of satellites the GPS currently sees.

Latitude, Longitude: Latitude and longitude given in decimal degrees.

Speed: Speed in meters per second. Altitude: Height above sea level in meters. Hdop: Horizontal dilution of precision, HDOP. Qual: Reads “GPS fix” if GPS fix obtained, otherwise left blank (“-”).

Date: Date (“yy-mm-dd”).

(47)

4.

Events

Events in TEMS Pocket 11.2 are related to the execution of scripts.

4.1.

Event Log

To view events that have occurred, press the Menu button, then tap

SettingsEvent Log.

4.1.1.

Refreshing the Event Log

To refresh the event log, press the Menu button, then tap Refresh. 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 “HTTP End” event in the screenshot.

You refresh the event log manually as described in section4.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 section4.1.2.

(48)

40

4.1.2.

Clearing the Event Log

To clear the event log, press the Menu button, then tap Clear.

4.2.

List of Logged Events

This section lists all the types of event that are saved in the event log, along with their parameters where applicable.

4.2.1.

Script Events

4.2.2.

Session Events

Among the session events, “End” events imply successful completion of the session.

Event Name Parameters/Notes

Script End Script execution time, Number of iterations, Number of successful actions, Number of failed actions

Script Iteration Sequence number of the iteration started (No parameters)

Script Start Script name

Event Name Parameters/Notes

FTP End Direction (UL/DL), Avg. throughput,

Duration of session

FTP Error Direction (UL/DL), Cause

Note: This event is also generated during a Voice + Data action when an FTP session is terminated on voice call end. FTP Start Direction (UL/DL), FTP server host name,

File name, FTP port, User name on FTP server

(49)

HTTP End Avg. throughput, Duration of session

HTTP Error Cause

Note: This event is also generated during a Voice + Data action when an HTTP session is terminated on voice call end.

HTTP Start URL

Idle End (No parameters)

Idle Error Time remaining of configured duration when error occurred

Idle Start Configured session duration

Upload End (No parameters)

Upload Error Number of logfiles uploaded when error occurred

Upload Start Number of logfiles to be uploaded

Voice End (No parameters)

Voice Error Cause

Voice Start Dialed number

VoiceData End (No parameters)

Success criteria for the Voice + Data action are given in section4.2.2.1 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 section4.2.2.1.

(50)

42

4.2.2.1. Success Criteria for “Voice + Data” Action

The outcome of the Voice + Data action depends crucially on how the Stop at

voice end flag (see section6.2.4) is set:

4.2.3.

Logfile Recording Events

VoiceData Start (No parameters)

Stop at Voice End Voice Result Data Result Voice + Data Result

On Success Success Success

after voice finished Running1

1. That is, the data session is still running when the voice call completes. Success

Failure Failure Failure Don’t care Failure

Off Success Success Success

after both finished Failure Don’t care Failure

Don’t care Failure Failure

Event Name Parameters/Notes

Logfile Start (No parameters)

Generated for all types of logfile recording.

Logfile Stop (No parameters)

Generated for all types of logfile recording.

(51)

5.

The Indoor Map View

The Indoor Map function enables import of maps and positioning of

measurements in indoor locations and other places where GPS coverage is lacking. The positioning is done by pinpointing the test route in the Indoor Map view.

5.1.

The Map Editor

You use the Map Editor to create and configure TEMS Pocket map sets.

5.1.1.

Creating Map Sets

• First you need to obtain images of the environment that is going to be covered during measurement. For example, use the phone’s camera to photograph the emergency or evacuation plan for the relevant floor(s) of the building. The best image quality is obtained if the camera is set in black-and-white mode. Also avoid using the flash. If you are using an image from a different source, it must be in JPEG, PNG, or BMP format.

Press the Menu button and select Settings. • From the Settings menu, select Map Editor.

Press the Menu button and select New Map Set. • Tap Name and enter a name for the new map set. • Then tap Indoor Maps.

Note: The Indoor Map view and the pinpointing function require a special license option. The Indoor Map icon on the top-level screen (see section2.3.1) is grayed if no such license is present.

(52)

44

Press the Menu button and select Add Indoor Map.

• You are now taken to the storage location for images. 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.

Map sets are saved as files with extension .pms (Pocket map sets). These files are self-contained and can easily be transferred to other devices. Map sets are saved to the phone’s memory card as specified in section2.4. It is also possible to store a logfile containing a map set (file extension .tpz) in the map set directory, and then load it into the Indoor Map view just like a map set (*.pms), as described in section5.2.

5.1.2.

Specifying Map Set Properties

You can set some position properties and other metadata for the map set. If you are not already in the Map Editor:

Press the Menu button and select Settings. • From the Settings menu, select Map Editor.

A list of the map sets you have already created appears.

• Tap Indoor Maps. A list appear of all the images included in this map set.

You can set properties:

– for an individual image by tapping that image, or

– for all images at once by pressing the Menu button and selecting

Edit all.

• Tap the map set you want to define properties for, or:

Create a new map set by pressing the Menu button and selecting New Map

(53)

The map properties are as follows:

When the Edit all function is used, the properties marked with an asterisk (*) above can be assigned to all maps in a map set in one action. The other properties must be set for each map individually (for obvious reasons).

In Edit all mode, if some properties differ between different maps in the map

set, the string “<Multiple values>” is shown for those properties.

5.1.3.

Managing Maps in a Map Set

If you tap and hold a map in a map set, a menu with the choices Move up,

Move down, and Delete appears.

Map file: Name of the map image file.

Tab file: TAB file associated with the map

image, if any. See section7.4. A TAB file present in the same directory as the map image and identically named will appear automatically in this field. Section2.4 gives the path to the map set directory.

Waypoint files: Planned routes associated

with this map image, if any. See section 5.3.5. Tap this field to select from a list of available waypoint files. Note that several waypoint files can be associated with the same map.

Latitude*, Longitude*: Enter the

coordinates of the top left corner of the map image. Format for latitude: N | S dd.dddd; format for longitude: E | W ddd.dddd (decimal degrees in both cases). These coordinates enable geographical positioning of the map set using TEMS Pocket Positioning Tool (see section7.4) in case no TAB file is available.

Address*, Building*, Floor*: Enter the

relevant information. The Floor tag, if applicable, naturally needs to be edited for each image individually.

(54)

46

• 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.

5.2.

Loading a Map Set into the Indoor Map View

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: Press the Menu button and select Actions. • Select Load Map Set.

• Select the desired map set and tap Load.

The map set now loads in the Indoor Map view. If the map set contains several images, the first is shown.

You flip through the maps by tapping the arrows appearing in the top left and right corners of the Indoor Map view. The map sequence wraps around as you browse to the first or last map. The bar indicator in the top left portion of the view indicates the position of the currently displayed map in the map set sequence.

When the Indoor Map view is zoomed in (zoom level > 1.0), any dragging action results in panning the currently visible map. When the view is zoomed out (zoom level = 1.0), swiping right will take you to the next view in the Location group, i.e. the GPS view (section 3.4.6.2), and swiping up or down will take you to a different data view group.

position of map in map set

arrows for browsing

(55)

5.3.

Pinpointing Your Test Route

5.3.1.

Fundamentals of Pinpointing

You can perform pinpointing in either of two ways:

Manually, marking waypoints freely on the map. See section5.3.4. • According to a predetermined planned route. See section5.3.5. Your route will be recorded in a logfile. Logfile recording starts automatically when you start pinpointing and is ended when you stop pinpointing.

5.3.2.

Coexistence with Other TEMS Pocket Functions

• 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 you are recording a logfile manually, pinpointing is disabled. • While pinpointing is active, you cannot swap maps; that is, you cannot

move from one image in the map set to another.

5.3.3.

Plotting Route Markers with RF Data

You can optionally have markers plotted along your route which are color-coded according to a selected piece of RF data (“value element”). The color coding of the markers is the same as that used for the value element in data views; it is explained in appendixA.

By default, no value element markers are plotted. The feature is activated and customized as follows:

Press the Menu button and select Actions.

(56)

48

The waypoints that you mark on the map are always indicated by pin symbols colored blue, and the straight-line segments connecting them are drawn in black. Neither of these colors is affected by the Select Value Element command.

Route markers are plotted also during logfile replay (covered in section7.3).

5.3.4.

Manual Pinpointing

Press the Menu button and select Actions.

• From the list that appears, pick the value element you want to show. The full list is also given in appendixB.

• Tap OK.

From now on, all pinpointed routes will be traced by dot-shaped markers whose color encodes the value element as measured at each point.

If you want to plot a different value element, simply make a new selection as described above. Note, however, that if you do this in the middle of pinpointing a route, the value element markers already plotted will be erased.

(57)

• Select Start Pinpoint.

• Pan the map to position the crosshairs correctly. It may also be helpful to use the zoom function; pinch and spread to zoom the map image in and out. Alternatively, you can double-tap to zoom out to normal. The current magnification is indicated numerically in the top right corner.

• Tap Add pinpoint to place a waypoint at

the spot marked by the crosshairs. The waypoint is marked by a pin symbol and labeled with a sequence number.

• Pan the map to position it for the next waypoint, then tap Add pinpoint again. A new pin is drawn and joined to the previous one by a connecting line. (No value element is plotted in the example shown here.)

• Continue pinpointing at regular intervals along the route, and whenever you change direction.

(58)

50

Below is an example of value element plotting (see section5.3.3):

When you have completed your route:

Press the Menu button and select Actions. • Select Stop Pinpoint.

After you stop pinpointing, a TEMS Pocket logfile with extension .tpz (in fact a ZIP archive containing multiple files) is created and stored in the location stated in section2.4.

• If you want to undo a pinpointing action, tap the relevant pin. The pin turns red, and the map is re-centered around it. Confirm by tapping Delete pinpoint at the top of the view. Connecting lines are redrawn and the numbering is adjusted automatically.

To cancel the delete action, just tap the pin once more. Its color then reverts to blue.

Route markers are drawn along each route segment as soon as it has been completed, that is, when you mark a new waypoint ending the segment. A maximum of 10 route markers are drawn between two waypoints.

(59)

Logfiles can be replayed in TEMS Pocket itself, as detailed in section7.3. You can also transfer the logfiles to a PC and open them in TEMS

Investigation or TEMS Discovery. For the latter purpose, the logfiles must be geographically positioned; see section7.4.

5.3.5.

Pinpointing According to Planned Route

At present there is no explicit function in TEMS Pocket for designing planned routes. However, you can easily construct one by pinpointing your planned route manually according to section5.3.4 and then reusing that route. The simplest procedure is to store the pinpointing logfile archive (*.tpz) in the TEMS Pocket map set directory (see section2.4) and then load the logfile using the Load Map Set command as described in section5.2. This method lets you reuse both the map set and the waypoints from the logfile. The operation needs to be performed from the PC, unless you have a file manager app installed on the phone.

Alternative Procedure with Explicit Handling of Waypoint File

Alternatively, you may extract the waypoint file (*.ppf) from the logfile ZIP archive (*.tpz), using a program such as WinZip, and store that waypoint file on the phone’s memory card in the TEMS Pocket waypoint directory given in section2.4. You can then load the waypoint file back into TEMS Pocket as an independent entity:

• Load the map set you are going to use, if it is not loaded already. • Add the waypoint file to your map set by editing the map set’s Waypoint

files property as described in section5.1.2.

Then press the Menu button and select Actions. • Select Load Waypoints.

(60)

52

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:

• Go to the physical location marked by the first waypoint (highlighted in red).

Press the Menu button and select

Actions, then select Start Pinpoint.

• A panel with three buttons appears, and the map is centered around the first waypoint. Tap the Commit button to indicate that you are currently in that location.

• Tap Next to proceed to the next waypoint. The highlighting in red then switches to that waypoint, and the map is re-centered around it.

• Walk in a straight line and at a steady pace towards the spot marked by the highlighted waypoint. When you have reached it, tap

Commit. The route segment just

(61)

When you have completed the route:

Press the Menu button and select Actions. • Select Stop Pinpoint.

You can unload the waypoint file as follows: Press the Menu button and select Actions. • Select Unload Waypoints.

The waypoints and the planned route vanish from the Indoor Map view.

5.4.

Unloading a Map Set

There is no explicit function for unloading a map set from the Indoor Map view. However, to use a different map set, you only have to load it into the Indoor Map view. It will replace the map set currently loaded if there is one.

• Continue in this fashion until you have finished the route.

(It is possible to move backwards along the route by tapping the Previous button.)

(62)

54

6.

Scripts

6.1.

Introduction to Scripts

Scripts are used to automate testing of services. The following services and tasks are supported by the script function:

• FTP upload/download • HTTP

• Voice (mobile-originated calls)

• Voice + data (concurrent CS and PS sessions: multi-RAB) • Idle

• Control function • Logfile upload • Wait.

You can have the execution of a script recorded automatically in a logfile. It is also possible to have that logfile uploaded automatically to an FTP server. The latter is accomplished with the script action Logfile upload.

You start and stop a script with menu commands: see section6.3. When a script is executed, its actions are performed one after another in the order they come in the script definition. Once started, the script repeats until you stop it, or until the memory card fills up.

Script setups are stored on file, as detailed in section2.4. Such files can be transferred to other TEMS Pocket units.

Note: Running a script for extended periods of time places a high load on the phone battery. See chapter11 for advice on how to ensure that the battery is not drained.

(63)

To be able to load TEMS Pocket 11.2 logfiles in other TEMS products, you need to process them with a Windows application called TPZ Converter. See section7.4.

6.2.

Composing Scripts

To access the script editing function, press the Menu button, then tap

SettingsScript Editor.

To add an action to the script, press the Menu button, then tap New Any scripts already defined are listed here.

To define a new script, press the Menu button and tap New Script.

On this screen you define general script settings.

Name: Enter a name for the script here.

Logfile tag: Here you can define a tag that will

be added to the name of each logfile. By default, logfile names consist only of date and time (format: “yyyy-mm-dd_hh.mm.ss.tpz”).

Logfile recording: Governs whether to record

logfiles during script execution.

GPS positioning: Governs whether or not to

make use of the phone’s GPS during script execution.

After editing these settings, tap Actions to define the actions the script should perform.

References

Related documents

The response of constant recovery stress was associated with there being zero stress in the Eyring arm; the recovery stress was then equated with the total applied stress, and

Společnost OZO Ostrava s.r.o. v rámci péče o své zaměstnance poskytuje příspěvek na penzijní připojištění nebo na doplněk penzijního spoření. V případě, že

This book shows that the evangelical Wesleyan tradition recognizes the need for engaging Christian theology with contemporary science, and it sees its founder, John Wesley, as one

The design allows for simple cgroup usage, such as setting a few parameters for specific tasks in a single hierarchy, such as one with just the cpu and memory subsystems attached..

[r]

Government’s decisions regarding the existence of the policy, I wondered how much class teachers in an inner-city school which had benefited from the ‘Excellence in

Once placed on the list, a school remains on it for two more years, even if it becomes Exemplary in those years — even though it meets the two different standards of state and

PBX 2G BTS 3G Node B Legacy FAX SOHO/ Residential ONT IAD OLT or DLC DWDM ADM T1/E1 BSC/RNC Wireless Networks Metro Core PDH Networks PON Networks SONET/ SDH SONET/ SDH MSPP