TEMS Pocket 8.2 User's Manual

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

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

TEMS is a trademark of Ascom.

All other trademarks are the property of their respective holders.

© Ascom 2010. All rights reserved.

Publication number: LZT 138 0361 R2A

Contents

Contents

1. Introduction 1

2. Overview of TEMS Pocket 2

2.1. Launching of the TEMS Pocket Application . . . . . . . . . . . . . . . . . . . 22.2. Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.3. Graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.4. Scripts and Task Status Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.5. General Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.6. Logfiles Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.7. Map View and Positioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.8. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.9. TEMS Pocket Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.10. Connecting the TEMS Pocket Phone to a PC. . . . . . . . . . . . . . . . . 72.11. Exiting the TEMS Pocket Application . . . . . . . . . . . . . . . . . . . . . . . 72.12. Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.13. Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3. TEMS Pocket View Header 9

3.1. Header Symbols in Recording Mode. . . . . . . . . . . . . . . . . . . . . . . . . 93.2. Header Symbols in Replay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3. Displayable RAT States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4. TEMS Pocket Views: General 11

4.1. Overview of TEMS Pocket Views . . . . . . . . . . . . . . . . . . . . . . . . . . 114.2. General Data View Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.3. Display of Basic RF Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.3.1. GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.3.2. WCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.3.3. CDMA/EV-DO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

LZT 138 0361 R2A i

TEMS Pocket 8.2 User’s Manual

4.4. Plotting Data View Items in the Graph . . . . . . . . . . . . . . . . . . . . . . 154.5. Plotting a Data View Item in the Map View . . . . . . . . . . . . . . . . . . . 174.6. Setting Radio Alerts in Data Views . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.6.1. Setting a Channel Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.6.2. Setting a Code Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.7. Freezing the Phone Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.8. Taking Screen Captures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.9. Maximizing Charts in Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . 204.10. Portrait vs. Landscape Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5. Data Views in Detail: GSM 21

5.1. Cell List Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.2. BA List Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.3. IP Thr.put DL Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.4. IP Thr.put UL Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.5. Rx Qual Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.6. AMR Usage Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.7. Inter RAT Info Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.8. Time Log Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.9. GPS Location Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6. Data Views in Detail: WCDMA 27

6.1. Cell List Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276.2. Serving Cell Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.3. IP Thr.put DL Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.4. IP Thr.put UL Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.5. Block Error Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.6. AMR Usage Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.7. Inter RAT Info Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.8. Time Log Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.9. GPS Location Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7. Data Views in Detail: CDMA/EV-DO 33

7.1. Cell List Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.2. IP Thr.put DL Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.3. IP Thr.put UL Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.4. Frame Erasure Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ii

Contents

7.5. Packet Error Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357.6. Speech Quality Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.7. CDMA Perform Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.8. EVDO Perform Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.9. Time Log Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.10. GPS Location Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

8. Status View 39

9. Task Status Views 41

9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.1.1. Task Status View Subcategories . . . . . . . . . . . . . . . . . . . . . 419.1.2. Colored Dot Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

9.2. FTP Task Status Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.2.1. FTP (1/2): Current Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.2.2. FTP (2/2): Overall Results . . . . . . . . . . . . . . . . . . . . . . . . . . 43

9.3. HTTP Task Status Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449.3.1. HTTP (1/2): Current Task. . . . . . . . . . . . . . . . . . . . . . . . . . . 449.3.2. HTTP (2/2): Overall Results . . . . . . . . . . . . . . . . . . . . . . . . . 45

9.4. Ping Task Status Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469.4.1. Ping (1/2): Current Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469.4.2. Ping (2/2): Overall Results . . . . . . . . . . . . . . . . . . . . . . . . . . 47

9.5. SMS Task Status Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489.5.1. SMS (1/2): Current Task . . . . . . . . . . . . . . . . . . . . . . . . . . . 489.5.2. SMS (2/2): Overall Results. . . . . . . . . . . . . . . . . . . . . . . . . . 49

9.6. Speech Task Status Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509.6.1. Speech (1/2): Current Task . . . . . . . . . . . . . . . . . . . . . . . . . 509.6.2. Speech (2/2): Overall Results . . . . . . . . . . . . . . . . . . . . . . . 51

9.7. WAP Task Status Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529.7.1. WAP (1/2): Current Task . . . . . . . . . . . . . . . . . . . . . . . . . . . 529.7.2. WAP (2/2): Overall Results . . . . . . . . . . . . . . . . . . . . . . . . . 53

9.8. Plotting Items from Task Status Views in the Graph or Map View . 53

10. The Map View 54

10.1. Google Maps Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5410.2. Indoor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

10.2.1. Loading an Indoor Location into the Map View . . . . . . . . . 55

LZT 138 0361 R2A iii


10.2.2. Pinpointing Your Test Route . . . . . . . . . . . . . . . . . . . . . . . 5610.2.2.1. Setting the Map Zoom. . . . . . . . . . . . . . . . . . . . . . . 5610.2.2.2. Customizing the Appearance of Route Markers . . . 5710.2.2.3. Pinpointing and Recording . . . . . . . . . . . . . . . . . . . 5710.2.2.4. Contents of Logfiles Holding Pinpointing Data . . . . 5810.2.2.5. Replay of Logfiles with Pinpointing Data. . . . . . . . . 58

10.2.3. Positioning the Map Geographically . . . . . . . . . . . . . . . . . 5910.3. Overview of Map Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

11. Control Functions 60

11.1. Lock on RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6011.1.1. Lock on RAT for GSM/WCDMA. . . . . . . . . . . . . . . . . . . . . 6011.1.2. Lock on RAT for CDMA 1x/1xEV-DO . . . . . . . . . . . . . . . . 6111.1.3. Indication of RAT Lock. . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

11.2. Lock on Band (GSM/WCDMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

12. The TEMS Pocket Menu: General 64

13. Logfiles 65

13.1. Recording Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6513.1.1. Adding Filemarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6613.1.2. Memory Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

13.2. Replaying Logfiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6613.2.1. Replaying Logfiles in TEMS Investigation . . . . . . . . . . . . . 69

13.3. Logfile Transfer via FTP (Result Upload) . . . . . . . . . . . . . . . . . . . 6913.3.1. Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6913.3.2. Uploading Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

14. Scripts 73

14.1. Introduction to Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7314.2. Composing a Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

14.2.1. Global Script Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7414.2.2. Creating a New Task in the Script . . . . . . . . . . . . . . . . . . . 7514.2.3. Speech Task Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

14.2.3.1. Call Window and Call Duration Parameters . . . . . . 7614.2.4. HTTP Task Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7714.2.5. Ping Task Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7714.2.6. FTP Task Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

iv

Contents

14.2.7. WAP Task Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7914.2.8. SMS Task Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8014.2.9. Idle Task Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8014.2.10. Random Idle Task Settings . . . . . . . . . . . . . . . . . . . . . . . 8114.2.11. Saving a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8114.2.12. Adding More Tasks to a Script . . . . . . . . . . . . . . . . . . . . . 8214.2.13. Rearranging Tasks in a Script . . . . . . . . . . . . . . . . . . . . . 8214.2.14. Deleting Tasks from a Script . . . . . . . . . . . . . . . . . . . . . . 83

14.3. Editing a Previously Saved Script . . . . . . . . . . . . . . . . . . . . . . . . . 8314.4. Duplicating an Entire Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8314.5. Deleting a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8314.6. Running a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

15. Radio Alerts 85

15.1. Introduction to Radio Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8515.2. GSM and WCDMA Radio Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . 8615.3. CDMA Radio Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

16. Events 87

16.1. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8716.2. Audio Alerts for Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8716.3. List of Logged Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

16.3.1. GSM/WCDMA Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8816.3.1.1. CC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8816.3.1.2. IRAT Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8816.3.1.3. MM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8816.3.1.4. RR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8916.3.1.5. RRC Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8916.3.1.6. SM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8916.3.1.7. Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9016.3.1.8. Application Events. . . . . . . . . . . . . . . . . . . . . . . . . . 9016.3.1.9. Radio Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9116.3.1.10. Other Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

16.3.2. CDMA/EV-DO Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9116.3.2.1. Network Generated Events . . . . . . . . . . . . . . . . . . . 9116.3.2.2. Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9316.3.2.3. Application Events. . . . . . . . . . . . . . . . . . . . . . . . . . 9316.3.2.4. Radio Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9316.3.2.5. Other Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

LZT 138 0361 R2A v


17. Indoor Locations 95

17.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9517.2. Creating an Indoor Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

18. Settings 98

18.1. Application Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9818.2. Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9918.3. Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10018.4. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10118.5. GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

18.5.1. Using the Built-in GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . 10218.5.2. Using an External GPS . . . . . . . . . . . . . . . . . . . . . . . . . . 102

18.6. Wireless File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10318.7. Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10418.8. Exporting and Importing Settings . . . . . . . . . . . . . . . . . . . . . . . . 10418.9. Default Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

18.9.1. Application Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10518.9.2. Data Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10518.9.3. Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10518.9.4. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10518.9.5. GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10518.9.6. Wireless File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . 10618.9.7. Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

19. Thematics 107

20. License Info 108

21. About Screen 109

22. Using TEMS Pocket Tools 110

22.1. Installing TEMS Pocket Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 11022.2. Using TEMS Pocket Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

22.2.1. Using TEMS Pocket Tools to Compose Scripts. . . . . . . . 11122.2.2. Using TEMS Pocket Tools to Define Indoor Locations . . 113

vi

Contents

22.2.3. Other Functions of TEMS Pocket Tools . . . . . . . . . . . . . . 11422.3. Using TEMS Pocket TMZ Decoder to Convert Logfiles . . . . . . . 115

22.3.1. Converting Individually Selected Logfiles. . . . . . . . . . . . . 11522.3.2. Converting All Logfiles in a Folder . . . . . . . . . . . . . . . . . . 116

22.4. Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

23. Support Contact Information 117

Appendix A. File Types Specific to TEMS Pocket 8.2 118

Index 119

LZT 138 0361 R2A vii


viii

Chapter 1. Introduction

1. Introduction

Welcome to TEMS Pocket.

TEMS Pocket 8.2 is an advanced cellular network diagnostics tool for UMTS (GSM and WCDMA) as well as CDMA (1x and 1xEV-DO) networks. The product is implemented as an application that runs on a Windows Mobile device. 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 8.2 as implemented for the HTC Imagio, HTC Touch Pro 2, HTC Touch Pro, and HTC Tilt 2 phones. Please note that the range of cellular technologies supported differs between these phone models (and, in the case of HTC Touch Pro 2, between different versions of the same model).

LZT 138 0361 R2A 1


2. Overview of TEMS Pocket

For best performance, it is recommended that you do not run any other applications on the phone while running TEMS Pocket.

All screenshots that follow are taken from the HTC Touch Pro 2 phone. Please be aware that the appearance of TEMS Pocket screens may be slightly different on other supported devices. The Windows Mobile user interface may also differ, since not all supported devices use the same version of the Windows Mobile OS.

2.1. Launching of the TEMS Pocket Application

TEMS Pocket will by default be launched automatically when you start up the phone.

A splash screen appears while TEMS Pocket is starting up.

2

Chapter 2. Overview of TEMS Pocket

If you have disabled autostart of the TEMS Pocket application (as described in section 18.1), do as follows to start the application manually:

TEMS Pocket then displays the Cell List data view.

• On the stand-by screen of the phone, tap the Windows icon in the top left corner.

(As noted in the introduction of this chapter, please be aware that the precise details of navigating the Windows Mobile interface may vary depending on the device.)

LZT 138 0361 R2A 3


2.2. Data Views

Most of the data displayed by TEMS Pocket is to be found in the data views. Some data views are text-only, while others combine text-format content with one or several charts. All data views are predefined.

You browse the data views by finger navigation (left and right).1 You can also use the overview of data views (see section 4.1) to navigate to the desired view. The views come in the same sequence as they are listed in chapters 5 and 7.

The top section of the display holds system status indicators as well as other symbols belonging to the regular user interface of the phone. Please refer to Windows Mobile documentation for descriptions of these.

The header of the TEMS Pocket data view, besides indicating the data view title, also displays symbols relating to TEMS Pocket operation. See chapter 3.

The data views are exhaustively described in chapters 4–7.

• In the list of installed programs, finger scroll (or use the scroll bar) to locate the TEMS Pocket icon and tap it.

Tip: To avoid having to scroll for a program in this list, you can move the program icon to the top of the list. This is done by long-pressing the program icon and choosing “Move to Top” from the popup menu that appears.

1. Browsing can alternatively be done by means of the left and right keys on the slide-out keyboard. However, since this is a cumbersome method, it will not be mentioned further in this manual.

4


2.3. Graphs

You can pick data from a data view and visualize it in a graph. See section 4.4.

2.4. Scripts and Task Status Views

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

Task status views appear when executing a script: separate views for each task in the script (for example, voice call and FTP download). See chapter 9.

2.5. General Status View

A status view with general information is always visible, showing the current status of the TEMS Pocket application: what script (if any) is currently being run, what logfile is being recorded, and more. See chapter 8.

2.6. Logfiles Recording

You can record data collected by TEMS Pocket in logfiles (section 13.1). Such files can be replayed in TEMS Pocket itself (section 13.2); you can also transfer the logfiles to a PC and study them in TEMS Investigation, version 11.0 or later.

LZT 138 0361 R2A 5


2.7. Map View and Positioning

The Map view is used for plotting a test route on a background map. Data from data views can be visualized in the form of color-changing route markers.

• With a functioning network connection, the map data is furnished by Google Maps. For route plotting, GPS coverage is required, or at least the availability of cell location data1. The GPS unit can be either the phone’s internal GPS or an external unit. See section 10.1.

• In the absence of a network connection and GPS coverage, data can be pinpointed manually on a floor plan or other map of an indoor location. See section 10.2.

2.8. Events

Events are generated and logged by TEMS Pocket to indicate that something interesting and worthy of note has occurred in the phone’s interaction with the cellular network.

The event log is inspected and managed from the TEMS Pocket menu. See chapter 16.

1. The latter possibility exists in CDMA networks only.

6


2.9. TEMS Pocket Menu

When you tap the Menu button, a menu with TEMS Pocket commands appears:

From here you perform a variety of actions and configuration tasks. They are gone through in chapters 12–21.

2.10. Connecting the TEMS Pocket Phone to a PC

The Windows Mobile device uses Microsoft’s ActiveSync software for connecting to a PC. The device comes with ActiveSync installed; however, you need to install it yourself on the PC.

2.11. Exiting the TEMS Pocket Application

You exit TEMS Pocket by tapping the Exit button that is present in every data view.

Note: If USB or Wi-Fi is present, data measurements will not be made over the cellular technology air interface. Therefore you may not be able to perform data service testing as intended while you have the TEMS Pocket phone connected to your PC.

LZT 138 0361 R2A 7


2.12. Language Support

The TEMS Pocket 8.2 phones support languages as follows:

• Regular phone user interface: Same languages as in the commercial phone release.

• Pocket user interface

– Text display: English

– User input: English

2.13. Accessories

The following accessories can be purchased with TEMS Pocket 8.2:

• External GPS (see section 18.5)

• Car kit

8

Chapter 3. TEMS Pocket View Header

3. TEMS Pocket View Header

A number of indicators and symbols are used in TEMS Pocket 8.2 to indicate various application states. These items always appear in the TEMS Pocket data view header.

3.1. Header Symbols in Recording Mode

Logfile recording in progress (see

section 13.1)

Screen freeze indicator: whitewhen screen is not frozen,red when screen is frozen

(see section 4.7)

Current RAT; flashes when the RAT changes (which is possible only when no RAT lock is applied)

RAT lock applied (see section 11.1)

Screenshot function enabled

LZT 138 0361 R2A 9


3.2. Header Symbols in Replay Mode

3.3. Displayable RAT States

This is the full list of RAT states that are distinguished in the view header:

• GSM, GPRS, EDGE

• WCDMA, HSDPA, HSUPA

• CDMA, Rev.0, Rev.A

Logfile replay drop-down menu (see

section 13.2)

Current timestamp in logfile

Current RAT; flashes when the RAT changes (which is possible only when no RAT lock is applied)

Screenshot function enabled

10

Chapter 4. TEMS Pocket Views: General

4. TEMS Pocket Views: General

This chapter deals with general aspects of TEMS Pocket views.

Data views are gone through in chapters 5–7.

The general Status view is covered in chapter 8, task status views in chapter 9, and the Map view in chapter 10.

4.1. Overview of TEMS Pocket Views

You can access an overview of all TEMS Pocket views that are available for the current RAT by long-pressing anywhere on the screen. Icons are used to represent the TEMS Pocket views, and they come in the same order as in the finger scrolling sequence. See the table below. Elsewhere in this manual, each icon also appears in the section dealing with the view that the icon represents.

After a script has been started, additional status views for tasks in the script appear in this overview after the data views, for example “Ping (1/2)” + “Ping (2/2)” (see chapter 9).

Icon ViewChapter/Section Ref.

GSM WCDMA CDMA

Cell List data view 5.1 6.1 7.1

BA List data view 5.2 – –

Serving Cell data view – 6.2 –

IP Thr.put DL data view 5.3

LZT 138 0361 R2A 11


IP Thr.put UL data view 5.4

Frame Erasure data view 5.5 – 7.4

Block Error data view – 6.5 –

Packet Error data view – – 7.5

AMR Usage data view 5.6 6.6 –

Speech Quality data view – – 7.6

CDMA Perform data view/EVDO Perform data view

– –7.77.8

Inter RAT Info data view 5.7 6.7 –

Time Log data view 5.8 7.9

GPS Location data view 5.9

Map view 10

Status view 8

Graph 4.4

Settings menu 18

Icon ViewChapter/Section Ref.

GSM WCDMA CDMA

12


Task Status Views

4.2. General Data View Properties

All data views have the same general structure in idle mode and dedicated/connected/active mode.

Whenever a parameter is currently not valid, this is indicated in the data view by a dash “–”.

Certain parameters are presented both numerically and graphically, the number appearing on top of a colored bar whose length and color depend on the parameter value. The rules for the graphic presentation are displayed under Menu Thematics: see chapter 19.

4.3. Display of Basic RF Data

A selection of fundamental RF data appears in the top section of all data views:

Icon ViewChapter/Section

Ref.

FTP (1/2): Current TaskFTP (2/2): Overall Results

9.2.19.2.2

HTTP (1/2): Current TaskHTTP (2/2): Overall Results

9.3.19.3.2

Ping (1/2): Current TaskPing (2/2): Overall Results

9.4.19.4.2

SMS (1/2): Current TaskSMS (2/2): Overall Results

9.5.19.5.2

Speech (1/2): Current TaskSpeech (2/2): Overall Results

9.6.19.6.2

WAP (1/2): Current TaskWAP (2/2): Overall Results

9.7.19.7.2

LZT 138 0361 R2A 13


4.3.1. GSM

4.3.2. WCDMA

4.3.3. CDMA/EV-DO

• Tx Pwr: Transmit Power (dBm)

• RxLev: Received Signal Level (dBm)

• BSIC: Received Signal Code Power (dBm); value on line 2, below the string “BSIC”

• MCC: Mobile Country Code

• MNC: Mobile Network Code

• ARFCN: Absolute Radio Frequency Channel Number


• RSCP: Received Signal Code Power (dBm)

• SC: Scrambling Code; value on line 2, below the string “SC”

• MCC: Mobile Country Code

• MNC: Mobile Network Code

• UARFCN: UMTS Absolute Radio Frequency Channel Number


• Cell ID: Cell Identity

• SID: System Identification; value on line 2, below “SID”

• Rx Pwr: Receive Power (dBm)

• RF Ch: RF Channel number

MCC MNC

MCC MNC

14


4.4. Plotting Data View Items in the Graph

The operations shown below can be performed in any data view.

• Tap any measurement value shown in the data view.

• To plot that item in the graph, select Graph from the popup menu that appears.

The selected parameter is plotted against time. At the top of the screen, the parameter name and current value are given.

• Tap anywhere on the screen to close the graph and return to the data view.

LZT 138 0361 R2A 15


In live mode, a snowflake is present beneath the top section of the screen. Tapping the snowflake will freeze the graph. Tap the snowflake once more (it is now colored red) to unfreeze the graph. The freeze function works the same way as in data views; compare section 4.7.

You can add another item to the graph by tapping that item in the data view. The graph then reappears with both parameters plotted.

You can repeat this action to add further items to the graph, jumping back and forth between the data view and the graph. Up to eight data items can be drawn, provided that they use no more than two different units (one scale on the left and, when needed, one on the right).

Note that if you add one data item too many according to the criteria just mentioned, all previously plotted items will be removed from the graph and replaced by the item you added.

To remove a data item from the graph, tap the “close” box for that item on the right.

16


4.5. Plotting a Data View Item in the Map View

This operation can be performed in any data view.

• Tap any value in the data view.

• To plot that item in the Map view, select Map from the popup menu that appears.

For a full treatment of the Map view, turn to chapter 10.

LZT 138 0361 R2A 17


4.6. Setting Radio Alerts in Data Views

Radio alerts can be set either in data views or from the TEMS Pocket menu. See chapter 15 for a description of the latter method and for a general explanation of radio alerts. The two ways of creating radio alerts are equivalent.

4.6.1. Setting a Channel Alert

You can set a channel alert in any data view that contains a channel field:

• (GSM) ARFCN or BCCH

• (WCDMA) UARFCN

• (CDMA) RF Ch.

Do as follows:

• Tap the channel you want to set an alert for (one of the fields marked in the screenshot).

• From the popup that appears, select the Set ... Alert command. A channel alert will now be associated with the currently displayed channel.

When the channel you have set the alert for becomes the current channel, the channel field is tagged with a bell symbol in all data views that contain this field. See the screenshot on the left.

• To remove the alert, tap the channel once more in the channel column and choose the command Clear ... Alert.

18


4.6.2. Setting a Code Alert

4.7. Freezing the Phone Screen

In live mode, you can freeze the TEMS Pocket user interface to study the data displayed at that point at your leisure.

To freeze the screen, tap the snowflake in the top right corner. The snowflake turns red. (A camera symbol may also appear; see section 4.8.)

A code alert is associated with a Base Station Identity Code (BSIC) in GSM, with a scrambling code (SC) in WCDMA and with a Pseudo Noise code (PN) in CDMA.

You can set a code alert in the Cell List data view, which displays a list of codes, each representing one cell (see sections 6.1, 7.1).

• Tap the code you want to set an alert for (one of the fields marked in the screenshot). From the popup menu that appears, choose the Set ... Alert command. The alert is associated with the code currently displayed at the tapped position (not with the position as such).

Whenever the code you have set an alert for is present in the cell list, that code is tagged with a bell symbol in the Cell List data view. See screenshot.

• To remove the alert, tap the code once more in the code column and choose the command Clear ... Alert.

LZT 138 0361 R2A 19


To unfreeze the screen, tap the snowflake once more. Its color reverts to white. (Another way to undo the freezing is to navigate to a different view.)

4.8. Taking Screen Captures

Freezing the screen also allows you to take screenshots of the data view displayed. This requires that you have enabled the screen capture function under Menu Settings Data Views; see section 18.2.

If the screen capture function is enabled, then when you tap the snowflake in the top right corner, a camera symbol appears to the left of it:

• Tap the camera symbol to take a screenshot of the data view currently displayed.

4.9. Maximizing Charts in Data Views

You can enlarge a chart in a data view to full screen by tapping the view and choosing Maximize. Tap again to revert to the regular data view presentation.

Note that this function is available for charts in data views, not for the graphs drawn on a black background (the latter are already maximized).

4.10. Portrait vs. Landscape Mode

TEMS Pocket supports both portrait screen mode (depicted in this manual) and landscape mode. The contents of the TEMS Pocket user interface are mostly the same in landscape mode, whereas the layout may differ considerably.

You enter landscape mode by sliding out the keyboard. To revert to portrait mode, slide the keyboard back in.

20

Chapter 5. Data Views in Detail: GSM

5. Data Views in Detail: GSM

5.1. Cell List Data View

5.2. BA List Data View

Header: See chapter 3.Lines 1–2: See section 4.3.1.

Main data grid

The cells appearing here are the current serving cell (S) and the six strongest neighbor cells (N).

CID: Cell Identity

BCCH: Broadcast Control Channel

BSIC: Base Station Identity Code

RxLev: Received Signal Level (dBm)


List

Here is shown the BCCH Allocation (BA) list.

LZT 138 0361 R2A 21


5.3. IP Thr.put DL Data View

5.4. IP Thr.put UL Data View


Chart “IP Throughput DL Distribution”

This histogram shows the distribution of IP-level downlink data throughput.

To reset the statistics, tap anywhere in the chart and choose “Reset Distribution” from the popup that appears. You can also have the chart automatically reset for each data session/call and when a new logfile is started; see section 18.2.

Chart “IP Cur. DL”

This line chart tracks IP-level downlink data throughput over time.

Each chart can be viewed in full screen format; see section 4.9.


Chart “IP Throughput UL Distribution”

This histogram shows the distribution of IP-level uplink data throughput.

Resetting the statistics is done the same way as in the IP Thr.put DL view; see section 5.3.

Chart “IP Cur. UL”

This line chart tracks IP-level uplink data throughput over time.


22


5.5. Rx Qual Data View

5.6. AMR Usage Data View


Chart “RxQual Distribution”

This histogram shows the RxQual distribution.

To reset the statistics, tap anywhere in the chart and choose “Reset Distribution” from the popup that appears. You can also have the chart automatically reset for each data session/call and when a new logfile is started; see section 18.2.

Chart “RxQual”

This line chart tracks RxQual over time.



Codec: Currently used AMR speech codec.

Codec Mode: The grid that follows shows the usage distribution for the various narrowband (NB) and wideband (WB) AMR speech codecs. NB and WB together add up to 100%.

LZT 138 0361 R2A 23


5.7. Inter RAT Info Data View


Lines 3–5: Current serving cell (GSM)

Cell ID: Cell Identity



Lines 6–10: Measured WCDMA neighbors

UARFCN: The UARFCN on which neighbors are measured

Status: “N” if a neighbor appears on this line, otherwise “-”

SC: Scrambling Code

Ec/Io: Signal-to-noise ratio (dB)

RSCP: Received Signal Code Power (dBm)

24


5.8. Time Log Data View


Lines 3–11

Here is shown the time (in hours, minutes, and seconds) that the phone has spent in various states since the latest occurrence of one of the following:

• TEMS Pocket start-up

• Entering of replay mode

• Exit from replay mode

MM section

Home: Registered in home network

Roam: Registered in roaming network

Unreg: Unregistered

GSM section

TCH: Time using Traffic Channel (TCH)

PDCH: Time using Packet Data Channel (PDCH)

Idle: Time spent in Idle mode

WCDMA section

DCH: Time using Dedicated Channel (DCH)


No Service section

No Service: Time spent in No Service mode (no RAT found)

LZT 138 0361 R2A 25


5.9. GPS Location Data View

Regarding configurable GPS settings in TEMS Pocket, see section 18.5. In particular, units in the GPS Location data view are switchable between metric and English. The date format is not affected but can be changed via the phone’s locale setting; please consult Windows Mobile documentation for detailed instructions.


Lines 3–8

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

Altitude: Height above sea level in meters or feet.

Speed: Speed in km/h or mph.

UTC Time: Date and time of day; format governed by the phone’s location settings

Status:

• Disabled: The GPS is currently disabled.

• <n> Satellites: The GPS is enabled and currently sees the indicated number of satellites.

Chart, left

Signal strength of 6 strongest satellites seen.

Chart, right

Positions of all satellites seen.

(These charts cannot be maximized.)

26

Chapter 6. Data Views in Detail: WCDMA

6. Data Views in Detail: WCDMA



Main data grid

Here are listed all scrambling codes currently in the Active (A) and Neighbor (N)a sets, along with the UARFCN, Ec/Io, and Received Signal Code Power (RSCP) for each scrambling code.

a. Monitored and detected neighbors are not distinguished.

LZT 138 0361 R2A 27


6.2. Serving Cell Data View


Lines 3–6

Here are shown cell selection and reselection parameters from System Information Block 3. See 3GPP 25.331, section 10.3.2.3, and 3GPP 25.304.

Qhyst2s: Hysteresis Qhyst2s {0, 2, ..., 40} [dB]

SSR: Threshold Ssearch,RAT {–32, –30, ..., 20} [dB]

SHR: Threshold SHCS,RAT {–105, –103, ..., 91} [dB]

QqualMin: Qqualmin, minimum required quality {–24 ... 0} [dB]

QrxLevMin: Qrxlevmin, minimum required RxLev {–115, –113, ..., –25} [dBm]

TRSs: Timer value Treselections {0 ... 31} [s]

Max TxP: Maximum allowed UL TX power [dBm]

Line 7

Cell Stat: WCDMA cell status: One of• –: Not barred• B: Barred• O: Reserved for operator use

IntraMQ: Intra-frequency measurement quantity from System Information Block 11, e.g. “EcN0”; see 3GPP 25.331, section 14.1.1

(continued on next page)

28


Lines 8–12

Here are shown parameters from System Information Block 5.

PICH: Paging Indication Channel power offset {–10 ... 5} [dB]; see 3GPP 25.331, section 10.3.6.50

AICH: Acquisition Indication Channel power offset {–22 ... 5} [dB]; see 3GPP 25.331, section 10.3.6.3

P p-m: Power offset between the last transmitted preamble and the control part of the message {–5 ... 10} [dB]; see 3GPP 25.331, section 10.3.5.8

Mmax: Maximum number of preamble cycles {1 ... 32}; see 3GPP 25.331, section 10.3.6.67

NB01min: Lower bound for random back-off {0 ... 50}; see 3GPP 25.331, section 10.3.6.67

NB01max: Upper bound for random back-off {0 ... 50}; see 3GPP 25.331, section 10.3.6.67

Const: Constant value [dB]; see 3GPP 25.331, section 10.3.6.11

CPICH TxP: Primary CPICH TX power {–10 ... 50} [dBm]; see 3GPP 25.331, section 10.3.6.61

UL Int: Uplink interference {–110 ... –70} [dBm]; see 3GPP 25.331, section 10.3.6.87

Line 13

Regarding these parameters, see 3GPP 25.331, section 10.3.6.54 (“PRACH power offset”).

Pwr RS: Power Ramp Step {1 ... 8} [dB]

Prea.RMax: Preamble Retrans Max, maximum number of preambles in one preamble ramping cycle {1 ... 64}


LZT 138 0361 R2A 29



See section 5.3; the description of this view is RAT-independent.



Lines 14–16

Here are shown RRC parameters; see 3GPP 25.304, sections 5.2.6.1.4–5.

SrxLev: RRC Srxlev, Cell Selection Receive Level [dB]

Squal: RRC Squal, Cell Selection Quality

Crit.RSCP: RRC cell ranking criterion Rs for current serving cell, with RSCP used as quality measure

Crit.EcNo: RRC cell ranking criterion Rs for current serving cell, with Ec/N0 used as quality measure

H-Val: RRC quality level threshold criterion Hs for current serving cell

30


6.5. Block Error Data View

6.6. AMR Usage Data View


Chart “BLER Distribution”

This histogram shows the block error rate distribution.

To reset the statistics, tap anywhere in the chart and choose “Reset Distribution” from the popup that appears. You can also have the chart automatically reset for each data session and when a new logfile is started; see section 18.2.

Chart “DL DCH BLER”

This line chart tracks the downlink DCH block error rate (BLER) in percent over time.



Codec: Currently used AMR speech codec.

Codec Mode: The grid that follows shows the usage distribution for the various narrowband (NB) and wideband (WB) AMR speech codecs. NB and WB together add up to 100%.

LZT 138 0361 R2A 31


6.7. Inter RAT Info Data View


Same contents and layout as for GSM; see section 5.8.




Lines 3–6: Current WCDMA serving cell

Cell ID: Cell Identity

Scr. Code: Scrambling code

RSCP: Received Signal Code Power

Ec/Io: Signal-to-noise ratio (dB)

Lines 7–10: Measured GSM neighbors

Status: “N” if a neighbor appears on this line, otherwise “-”



32

Chapter 7. Data Views in Detail: CDMA/EV-DO

7. Data Views in Detail: CDMA/EV-DO







Main data grid

Here are listed PNs currently in the Active (A), Candidate (C), and Neighbor (N) sets, along with the Ec/Io and RSCP (Receive Signal Code Power) for each PN.

The total number of neighbors is indicated; there may be more of them than can be accommod-ated in the data view.

LZT 138 0361 R2A 33


7.4. Frame Erasure Data View

This data view holds 1x information but is visible also when the current RAT is 1xEV-DO.


Chart “FER”

This line chart tracks the Frame Erasure Rate in percent over time.

Chart “Finger SUM”

This line chart tracks the Finger Sum (total Ec/Io for all Rake fingers taken together).


34


7.5. Packet Error Data View

This data view holds 1x information but is visible also when the current RAT is 1xEV-DO.


Chart “PER Distribution”

This histogram shows the packet error rate distribution.

To reset the statistics, tap anywhere in the chart and choose “Reset Distribution” from the popup that appears. You can also have the chart automatically reset for each data session and when a new logfile is started; see section 18.2.

Chart “PER”

This line chart tracks the Packet Error Rate (PER, in percent) over time.


LZT 138 0361 R2A 35


7.6. Speech Quality Data View

7.7. CDMA Perform Data View


Chart “SQI”

This line chart tracks the Speech Quality Index (SQI-MOS, value on MOS scale) over time.

Chart “Link Quality Assessment”

This line chart tracks the Link Quality over time. The Link Quality score is an estimation of the current RF performance and is based on FER/PER, Rx Power, and Tx Power.


This data view is shown when the current RAT is 1x.

Header: See chapter 3.

FER: Frame Erasure Rate (%)

RxP: Receive Power (dBm)

TxP: Transmit Power (dBm)

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

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

36


7.8. EVDO Perform Data View

This data view is shown when the current RAT is 1xEV-DO.

Header: See chapter 3.

PER: Packet Error Rate (%)

RxP: Receive Power (dBm)

TxP: Transmit Power (dBm)

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

SINR: Signal to Interference-plus-Noise Ratio (dB)

LZT 138 0361 R2A 37






Lines 3–10

Here is shown the time (in hours, minutes, and seconds) that the phone has spent in various states since the latest occurrence of one of the following:

• TEMS Pocket start-up

• Entering of replay mode

• Exit from replay mode

MM section

Home: Registered in home network

Roam: Registered in roaming network

CDMA (1x) section

Voice: Time using voice service

Data: Time using data service


EVDO section

Data: Time using data service


No Service section

No Service: Time spent in No Service mode (no RAT found)

38

Chapter 8. Status View

8. Status View

The Status view gives some general information on the current status of the TEMS Pocket application. This view is always visible and comes after the Map view in the finger scrolling sequence (see section 4.1). All contents of the Status view, except the top two lines, are independent of RAT.

Header: See chapter 3.Lines 1–2: See section 4.3.

TMZ Name: The name of the logfile being recorded or replayed, if any.

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

Current Turn: The current turn of the script being executed.

Current Task: The type of script task currently being executed.

Current State: One of:

• Measuring

• Voice call states: Dial, In Call, Hang Up

• IP related states: Connect, Disconnect

• DNS Lookup

• FTP states: FTP Connect, Authenticate, Prepare Xfer, Transfer, Quit

• HTTP/WAP states: Request Page, Load Page

• Ping states: Send Ping, Wait Answer


LZT 138 0361 R2A 39


Current State (continued)

• SMS states: Sending SMS, In Guard Time

• In Pause

Progress: The percentage completed of the current task.

Time Left: Execution time remaining for the current script (shown if the script has a duration limit set: see section 14.2.1).

Turns Left: Number of turns remaining of the current script (shown if the script has a limit set on the number of turns: see section 14.2.1).

40

Chapter 9. Task Status Views

9. Task Status Views

9.1. General

These views appear after starting a script. How to set up and run scripts is gone through in chapter 14.

A unique set of task status views is provided for most task types, as detailed in the present chapter. When a script is started, the status views for a particular task type appear as soon as the first task of that type starts. All status views thus displayed remain visible until you start a new script.

When scrolling through all TEMS Pocket views, you reach the task status views after the last data view (GPS Location; see section 4.1).

9.1.1. Task Status View Subcategories

There are two kinds of task status views:

• Views reporting on the current task being executed. These are reset every time a new task of the same type begins.

• Views displaying overall results for a task type. These views show overall statistics for the currently active script and are reset (and at least temporarily hidden) when a new script is started.

The contents of all task status views, except the top two lines, are all RAT-independent.

9.1.2. Colored Dot Indicator

The colored dot appearing on line 3 beneath the header has the following interpretation:

• Green dot: A task of this type (e.g. Ping, FTP) is currently being run.

• Yellow dot: At least one task of this type has been run before, and the script is still running, but some other task is currently being executed.

• Gray dot: At least one task of this type has been run before, but the script has stopped.

LZT 138 0361 R2A 41


9.2. FTP Task Status Views

For the setup of FTP tasks, see section 14.2.6.

9.2.1. FTP (1/2): Current Task

Header: See chapter 3.Lines 1–2: See section 4.3.Line 3: See section 9.1.2.

Lines 4–10

URL: URL of the FTP server that the phone interacts with.

File Size: Size of file transferred.

Bytes Transf.: Number of bytes transferred.

Direction: Upload or Download.

Current State: Same information as in the general Status view; see chapter 8.

Last Server Response: Text of latest message received from the FTP server.

Lines 11–14

These lines show throughput figures: uplink throughput for FTP upload, and downlink throughput for FTP download.

Current: Current throughput.

Min: Lowest throughput measured for the current task.

Mean: Mean throughput for the current task.

Max: Highest throughput measured for the current task.

42


9.2.2. FTP (2/2): Overall Results


DL/UL

These lines show downlink and uplink throughput figures: uplink throughput for FTP upload, and downlink throughput for FTP download.

Min: Lowest throughput measured.

Mean: Mean throughput.

Max: Highest throughput measured.

Task Statistics

Total: Total number of executed FTP tasks. This equals the number of attempted FTP transfers, since only one file is transferred per task.

Success: Total number of successful FTP tasks = number of successfully completed FTP transfers.

Failed: Total number of failed FTP tasks = number of FTP transfers that failed to complete.

LZT 138 0361 R2A 43


9.3. HTTP Task Status Views

For the setup of HTTP tasks, see section 14.2.4.

9.3.1. HTTP (1/2): Current Task


Lines 4–8

URL: The URL of the HTTP server being downloaded from.

Page Size: Size of web page downloaded.

# of Files: Number of files downloaded so far for this web page (including HTML file).

Download Time: Total download time spent so far.


Lines 9–12

These lines show downlink throughput figures.





44


9.3.2. HTTP (2/2): Overall Results





Task Statistics

Total: Total number of executed HTTP tasks. This equals the number of attempted web page downloads, since only one download is performed in each task.

Success: Total number of successful HTTP tasks = number of successfully completed web page downloads.

Failed: Total number of failed HTTP tasks = number of web page downloads that failed to complete.

LZT 138 0361 R2A 45


9.4. Ping Task Status Views

For the setup of Ping tasks, see section 14.2.5.

9.4.1. Ping (1/2): Current Task


Lines 4–8

Destination: IP address or host name of server pinged.

Msg. Size: Size of Ping message payload.

Msg. Count: Number of Pings sent.

Msg. Transf.: Number of Pings successfully transferred (Ping response obtained).

Msg. Lost: Number of Pings that failed to reach their destination (no Ping response obtained).

Lines 9–13: Delay

Current: Delay of last Ping sent.

Min, Mean, Max: Shortest Ping delay, mean Ping delay, and longest Ping delay measured so far for the current task.

46


9.4.2. Ping (2/2): Overall Results


Delay

Min: Shortest Ping delay measured.

Mean: Mean Ping delay.

Max: Longest Ping delay measured.

Task Statistics

Total: Total number of Ping tasks executed.

Success: Total number of successful Ping tasks. A Ping task is counted as successful as long as at least one Ping response has been received.

Failed: Total number of failed Ping tasks (no responses received).

LZT 138 0361 R2A 47


9.5. SMS Task Status Views

For the setup of SMS tasks, see section 14.2.8.

9.5.1. SMS (1/2): Current Task


Lines 4

SMS Sent/Received: Number of SMS messages sent; number of SMS messages received.

Lines 5–9

These lines show SMS send time information.

Current: Time taken to send the latest SMS.

Min: Shortest SMS send time measured for the current task.

Mean: Mean SMS send time for the current task.

Max: Longest SMS send time measured for the current task.

Lines 10–14

These lines show information on the SMS end-to-end time. This quantity can be measured because in performing the SMS task the device always sends messages to itself; the end-to-end time extends from the moment when sending begins until the SMS is received.

Current, Min, Mean, and Max are analogous to the send time information (see lines 5–9 above).

48


9.5.2. SMS (2/2): Overall Results


Send Statistics

Success: Total number of successful SMS send operations (ACK received).

Failed: Total number of failed SMS send operations (no ACK received).

Success Rate: Percentage of SMS messages that were successfully sent.

Retrieve Statistics

Success: Total number of successfully received SMS messages (the SMS sent earlier arrives while the task is still running).

Failed: Total number of SMS messages not successfully received.

Success Rate: Percentage of SMS messages that were successfully received.

LZT 138 0361 R2A 49


9.6. Speech Task Status Views

For the setup of speech tasks, see section 14.2.3.

9.6.1. Speech (1/2): Current Task


Called Party: Phone number called.

Call Window: The percentage of the call window that has elapsed. See section 14.2.3 for an explanation of this concept.

Call Duration: The percentage of the call duration that has elapsed. Again, see section 14.2.3 for a precise definition.

Pause Duration: The percentage that has elapsed of the pause between call retries (“Pause between Att.” parameter in section 14.2.3).

Last Marker: Information from latest call event. See the event listings in section 16.3, and compare the presentation of events in the event log (section 16.1).

50


9.6.2. Speech (2/2): Overall Results


Call Statistics

CCR: Call completion rate

CSSR: Call setup success rate

Call Attempts: Number of call attempts made.

Completed Calls: Number of completed calls.

Failed Calls: Number of call attempts where the call did not connect.

Dropped Calls: Number of calls that dropped.

LZT 138 0361 R2A 51


9.7. WAP Task Status Views

For the setup of WAP tasks, see section 14.2.7.

9.7.1. WAP (1/2): Current Task


Lines 4–8

URL: The URL of the WAP server being downloaded from.

Page Size: Size of WAP page downloaded.

Load Time: Total WAP download time spent so far.


Lines 9–12

These lines show downlink throughput figures.





52


9.7.2. WAP (2/2): Overall Results

9.8. Plotting Items from Task Status Views in the Graph or Map View

You can plot certain items from task status views in the graph and in the Map view, just like items in data views. For instructions, see section 4.4. The items eligible for plotting are:

• FTP: All throughput values

• HTTP: All throughput values (current, min, max, mean, including overall)

• Ping: All delay values

• SMS: All send time and end-to-end time values

• Speech: (None)

• WAP: All throughput values





Task Statistics

Total: Total number of executed HTTP tasks. This equals the number of attempted web page downloads, since only one download is performed in each task.

Success: Total number of successful HTTP tasks = number of successfully completed web page downloads.

Failed: Total number of failed HTTP tasks = number of web page downloads that failed to complete.

LZT 138 0361 R2A 53


10. The Map View

The Map view is used for plotting test routes. The view has two modes:

• Google Maps mode. See section 10.1.

• Indoor mode. See section 10.2.

10.1. Google Maps Mode

In this mode the background map data is furnished by Google Maps. A network connection is therefore required. A further requirement for plotting is the availability of valid GPS positions, or alternatively that the current cell broadcast its location (supported in CDMA networks only). In the latter case, if no GPS data is available, the map only shows the current cell location, and the map is then centered around the current cell.

The route is by default plotted as a trail of dots. A red dot with black border marks the current position.

If cell locations are obtained, they too are drawn on the map in the form of antenna symbols. The current cell is colored red, and all other cells seen at some point are colored black. The precise location of the cell site on the map is at the base of the antenna symbol.

Antenna symbols are accompanied by callouts showing the Cell IDs of all cells located at that site.

current position and cell

cellsroute

54

Chapter 10. The Map View

In CDMA and GSM, if you bring up the Map view while the phone is in a call, the Map view will turn white. This is because simultaneous use of voice and data services is not supported by these technologies, so that no map data can be transferred if a voice call is in progress. (In WCDMA, where voice and data can be run concurrently, the above is not a problem.)

10.2. Indoor Mode

The Map view also enables recording of positions for measurements in indoor locations and other places where GPS coverage is not available. The positioning is done by pinpointing the test route in the Map view.

10.2.1. Loading an Indoor Location into the Map View

• First you need to obtain an image of the environment that is going to be covered during measurement, and define an indoor location encapsulating that image. See chapter 17.

• Load your indoor location into the Map view:

You can also present data along the route by selecting an item in a data view or task status view. How to do this is described in sections 4.5 and 9.8 respectively. When a data item has been selected, the route is made up of dot-shaped markers. Each marker encodes, by means of its color, the parameter value at that point along the route. Just as in the trail-only plot, a red dot with black border marks the current position.

The color coding of route markers is described in the map legend, which appears as soon as route data is displayed on the map. The legend in turn reproduces the relevant information from Menu Thematics; see chapter 19.

If you select a different data item for plotting, the new item will replace the old one on the map.

Note: The indoor functionality requires a special license option.

route with data presentation

legend

LZT 138 0361 R2A 55


Tap the indoor icon to enter indoor mode.

Tap the folder icon to select the desired indoor location.

• Locate the file you want to load, and tap the Select button.

• The image now appears in the Map view:

10.2.2. Pinpointing Your Test Route

10.2.2.1. Setting the Map Zoom

You can start pinpointing as soon as the map is loaded. However, before getting started on your test route, it is a good idea to adjust the zoom level of the Map view so that the pinpointing actions can be performed conveniently.

Tap the zoom controls to change the map zoom.

Note: While a logfile is recording (compare section 10.2.2.3), you can select an indoor location file only once. If you want to load a different indoor location, you must first stop the recording.

56


10.2.2.2. Customizing the Appearance of Route Markers

Each route marker that you place on the map will initially be colored red to mark your current position. When the marker is no longer the current one, it will by default be redrawn in light blue. This color is used if you do not select a value element to display in the route markers.

On the other hand, if you do select a value element for plotting on the map (performed in a data view or task status view: see sections 4.5, 9.8), that value element will appear in indoor mode as well. You can make such a selection at any time; any route markers already plotted on the map will then be re-colored according to the value element selected.

10.2.2.3. Pinpointing and Recording

To place a new route marker, simply tap the spot on the map corresponding to your current position. It is a good idea to use the phone stylus in order to achieve greater precision. Continue pinpointing at regular intervals along the route, and whenever you change direction. Your route between consecutive markers is automatically filled in (interpolated as a straight line) on the map by means of additional route markers at one-second intervals.

The pinpointing does not trigger logfile recording but is performed independently of it. All the pinpoints that you perform while recording will be saved in the logfile so that the measurements can be positioned. When you are done with the measurement, just close the logfile as usual.

Below is an example of a pinpointed route, with and without a value element encoded:

Note: The navigation function must not be turned on, since any tapping actions in the map view will then have the effect of panning the map. See section 10.3. In other words, the Navigation button must be blue (“navigation off”). If you need to pan the map during pinpointing, remember to toggle navigation off afterwards.

LZT 138 0361 R2A 57


10.2.2.4. Contents of Logfiles Holding Pinpointing Data

A logfile that includes pinpointing data receives the same extension .TMZ as other TEMS Pocket 8.2 logfiles, and it is stored in the same location. See section 13.1.

However, when you decode such a logfile using TEMS Pocket TMZ Decoder as described in section 22.3, a zip archive is created which contains:

• the measurement data (*.LOG)

• the image loaded into the Map view (*.gif, *.jpg, or *.png)

• the indoor location properties covered in section 17.2 (*.xml)

• a file where the pinpointed route is recorded (*.ppf)

• an index file detailing the archive contents (*.xml).

10.2.2.5. Replay of Logfiles with Pinpointing Data

Logfiles that hold pinpointing data can be replayed in TEMS Pocket 8.2 just like any other logfile. See section 13.2.

No value element plotted Ec/Io of strongest cell plotted

58


10.2.3. Positioning the Map Geographically

The description of the test route furnished by pinpointing can be utilized when viewing TEMS Pocket logfiles in other TEMS tools such as TEMS Investigation.

Before the data is post-processed, however, it needs to be anchored to a geographical position. This is accomplished by processing the logfile zip archive with a software utility called TEMS Pocket Positioning Tool, which is installed along with TEMS Investigation. It is launched from the Start menu by selecting Programs Ascom TEMS Products Utilities TEMS Pocket Positioning Tool. Using this tool you indicate the coordinates of the map image so as to allow all data points to be positioned. For further details on this topic, consult the TEMS Pocket Positioning Tool User’s Manual.

After being positioned, the logfiles are ready to be loaded into TEMS Investigation.

10.3. Overview of Map Controls

The Map view is equipped with the following controls:

Indoor button: Used to enter indoor mode.

While the Map view is in indoor mode, the Indoor button has the arrow reversed. Tapping the button again returns the Map view to Google Maps mode.

Folder button: Used to select an indoor location for display.

Navigation button: Used to pan the map. Tapping this button enables navigation mode (the button turns red), and you can then tap and drag in the map view to move the map around.

Zoom controls: Used to zoom the map in and out.

LZT 138 0361 R2A 59


11. Control Functions

11.1. Lock on RAT

This function locks the phone to one radio access technology out of a set of available technologies.

The function works differently for GSM/WCDMA on one hand and CDMA 1x/1xEV-DO on the other; the two cases are therefore covered in separate subsections.

11.1.1. Lock on RAT for GSM/WCDMA

When the function is activated, the phone will detach from the network it is currently attached to and then attach to the selected network. No reboot occurs. However, if the signal from the RAT to be locked on is too weak, the phone will go into no service mode.

To lock on a RAT, do as follows:

• Tap the current RAT indicator to the left of the data view title.

• From the popup menu that appears, choose Change. A dialog appears:

Network Type

Auto: No forcing of network selection.

GSM: The phone will be forced to camp on a GSM network whenever one is available.

WCDMA: The phone will be forced to camp on a WCDMA network whenever one is available.

(Regarding the band lock function, see section 11.2.)

60

Chapter 11. Control Functions

• Finish by tapping Done.

11.1.2. Lock on RAT for CDMA 1x/1xEV-DO

When the function is activated, the phone will detach from the network it is currently attached to, reboot, and then attach to the selected network. If the signal from the RAT to be locked on is too weak, the phone will go into no service mode.

Since a reboot will take place, you should stop any currently running script and/or logfile recording before issuing a lock on RAT command.

To lock on a RAT, do as follows:

• Tap the current RAT indicator to the left of the data view title. A popup appears:

No Lock: No forcing of network selection.

CDMA 1x: The phone will be forced to camp on an 1x network whenever one is available.

EVDO: The phone will be forced to camp on a 1xEV-DO network whenever one is available.

LZT 138 0361 R2A 61


11.1.3. Indication of RAT Lock

When the RAT lock is engaged, a padlock symbol is displayed to the left of the RAT designation (see also chapter 3):

11.2. Lock on Band (GSM/WCDMA)

Within GSM/WCDMA, the phone can lock on certain subsets of frequency bands.

• Tap the current RAT indicator (“GSM” or “WCDMA”; see chapter 3) to the left of the data view title. A dialog appears:

A prompt appears, informing you that locking to a RAT will trigger a reboot of the phone. Tap Yes to proceed.

62

Chapter 11. Control Functions

• Finish by tapping Done.

“Band Frequency” section

Auto: No forcing of band selection.

The remaining choices indicate band combinations that the phone can be locked on.

LZT 138 0361 R2A 63


12. The TEMS Pocket Menu: General

The Pocket menu is accessed by tapping Menu while in a data view, status view, or Map view.

It contains the following items and submenus:

Name FunctionChapter/ Section

Start/Stop Logging Record logfiles 13.1

Open/Close Logfile Replay logfiles 13.2

Scripts Compose and run scripts 14

Result Upload Upload logfiles via FTP 13.3

Radio Alerts Set radio alerts 15

Events Inspect events 16

Indoor Maps Set up indoor locations 17

Settings Configure TEMS Pocket settings 18

Thematics Inspect color coding of parameters 19

License Info Inspect TEMS Pocket license information

20

About Inspect information on phone and on TEMS Pocket software

21

64

Chapter 13. Logfiles

13. Logfiles

13.1. Recording Logfiles

This command is used for manual recording of TEMS Pocket logfiles.

Logfile recording can also be configured to start automatically:

• as soon as TEMS Pocket is launched; this is governed by a setting described in section 18.1;

• as soon as you manually start a script; see section 18.3.

Logfiles are stored as files with extension .TMZ in the phone file system under \My Documents\TEMS\Results or, if a memory card is inserted, under \Storage Card\TEMS\Results. The storage location is not user-configurable.

• Choose the Start Logging command to start recording of a logfile.

If you have selected manual naming of logfiles, you are prompted to name the file. The logfile naming format is set under Menu Settings Logging: see section 18.3.

While recording is in progress, a special symbol is displayed in the data view header (see also chapter 3):

• When you want to stop the recording, tap Menu again and choose Stop Logging.

Upon ending the recording, you can have the logfile automatically uploaded to an FTP server, or you can configure TEMS Pocket to ask each time whether to upload the file. This behavior is specified under Menu Settings Wireless File Transfer; see section 18.6. How to set up logfile uploading (FTP server details) is explained in section 13.3.

LZT 138 0361 R2A 65


13.1.1. Adding Filemarks

You can insert filemarks in a logfile during recording in order to mark points of special interest in the logfile. For example, you might want to note down the location where something special happened (helpful if you are not using a GPS of any kind).

To add a filemark:

• Tap Menu Logfile Write Filemark.

• On the screen that appears, enter filemark text or select a previously entered filemark from the list. If you enter a new filemark string, it will be added to the list.

13.1.2. Memory Usage

During logfile recording, if the phone memory or memory card is running low (only 5 MB left), or if some error occurs, you are notified by an alert on the Events screen. Regarding the Events screen, see chapter 16.

13.2. Replaying Logfiles

The Open Logfile command is used to replay TEMS Pocket logfiles in TEMS Pocket itself.1

• Choose Menu Open Logfile.

1. Note that you can also replay the logfiles in TEMS Investigation. See section 13.2.1.

66


• From the list, select the logfile you want to replay. Note that the list may contain more items than can be accommodated on the screen; use the scroll bar (or finger scrolling) if necessary to browse the entire list.

• Tap Select.

The TEMS Pocket data views are now populated with the first data recorded in the logfile, and the logfile replay is put on standby. The actual replay does not begin until you tap the Play button (see below).

A timestamp is displayed at the top of the screen, next to the Windows icon. At the outset, when you have just opened a logfile, the time shown is that when the recording began.

• To get started with the replay, tap the small triangle in the top right corner of the data view. This opens a panel of replay controls. See next screenshot.

LZT 138 0361 R2A 67


Replay not started

Replay in progress

At the top of the panel is a progress bar showing how far into the logfile the replay has proceeded. See the bottom screenshot on the left.

The buttons have the following functions:

Go to beginning of logfile

Step one second back

Jump to timestamp (a selection dialog opens; see below)

Step one second forward

Go to end of logfile

Faster backward (jumps one minute at a time)

Fast backward

Play (at normal speed)/Pause

Fast forward

Faster forward (jumps 1 min at a time)

When you tap this button, the screen shown on the left appears. Here you enter an instant in time to jump to. Finish by tapping OK.

68


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.

You can use any of the phone’s 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.

If you choose Open Logfile during logfile recording and/or execution of a script, the recording and/or script will stop, and the application will go into replay mode.

To exit replay mode, you simply close the logfile: Menu Close Logfile. The TEMS Pocket views are then cleared, after which they will once again fill up with live data.

13.2.1. Replaying Logfiles in TEMS Investigation

You can transfer the logfiles to a PC and replay them in TEMS Investigation (version 10.0 or later). This requires a file conversion which can be accomplished with the TEMS Pocket Tools PC utility; see section 22.3. The file transfer can be done via FTP (see section 13.3), or by other means such as USB or Bluetooth.

13.3. Logfile Transfer via FTP (Result Upload)

Logfiles can be uploaded to a designated FTP server, using the built-in FTP client in the phone.

13.3.1. Server Settings

In this menu you specify FTP servers to which the TEMS Pocket phone is going to upload logfiles.

• Select Menu Result Upload Server Settings.

LZT 138 0361 R2A 69


13.3.2. Uploading Logfiles

This section describes logfile upload that you initiate manually. You can also configure TEMS Pocket to automatically upload logfiles in a number of situations. These settings are described in section 18.6.

The FTP servers already defined (if any) are listed.

• To add a server, tap the “+” bar, or select Menu Add Server. In either case, a new bar named “New Server” appears.

• To delete a server, tap it, then select Menu Delete Server.

• Tap the “New Server” bar to set up the parameters for the new server (if they are not already displayed). See below.

• Tap the title bar to replace the default server label “New Server” by a name of your choice.

The settings are as follows:

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

Server Port: The FTP server port. The default port number is 21.

FTP Mode: Active or Passive, as defined in IETF RFC 959.

Username, Password: User name and password on the FTP server, if required.

Remote Directory: The directory where the logfiles should be stored on the FTP server. The directory must already exist on the server.

70


• To upload one or more logfiles, select Menu Result Upload Upload Files:

• A list of logfiles stored on the phone appears. Note that the list may contain more items than can be accommodated on the screen; use the scroll bar (or finger scrolling) if necessary to browse the entire list. Check the logfiles you want to upload by tapping the appropriate boxes.

• When you have selected the desired files, tap Select. This takes you to the next screen, where you select the upload destination.

• Choose a server from the list.

• Tap Select.

LZT 138 0361 R2A 71


A screen showing the progress and outcome of the upload is displayed.

You can abort the upload by tapping Cancel.

If the upload fails, a button labeled Retry will appear, and you can retry the upload by tapping that button.

72

Chapter 14. Scripts

14. Scripts

14.1. Introduction to Scripts

Scripts are used to automate service testing in TEMS Pocket. Tasks can be defined in scripts for all of the following services:

• Voice calls (“Speech”)

• Ping

• FTP data transfers (upload/download)

• HTTP

• WAP

• SMS

• Idle mode period, fixed duration

• Idle mode period, random duration

There is no limit on the number of scripts that can be defined or on the number of tasks in each script. When the script is executed, its tasks are performed one after another in the order they have been defined. You specify in the script setup how many times the script as a whole should be run.

It is possible to have a selected script executed automatically when TEMS Pocket starts up. See section 18.1.

14.2. Composing a Script

This section tells how to compose scripts directly in the TEMS Pocket user interface. Scripts can also be composed using the PC utility TEMS Pocket Tools. Regarding the latter, see section 22.2.

LZT 138 0361 R2A 73


• Choose Menu Scripts Edit.

14.2.1. Global Script Settings

• The bar with the plus sign represents a new and as yet undefined script. Tap that bar to open a section where you define global settings for the script. See next screenshot.

If you have previously defined and saved other scripts, they too will be listed on this screen. Compare section 14.3.

Script Name: Enter a name for the script. (You can leave that for later; see section 14.2.11.)

Run Limit: Here you choose what kind of criterion should govern when to stop the script.

• Infinite: The script will run indefinitely, until you stop it manually or you exit the TEMS Pocket application.

• Limited number of turns: The script will be run a fixed number of times, as specified in the Number of Turns field.

• Limited time: The script will be run for a fixed length of time. A Duration field appears where you enter this. When the duration expires, the script will finish its current task and then stop.

Now proceed to define a task that the script should perform. See section 14.2.2.

74

Chapter 14. Scripts

14.2.2. Creating a New Task in the Script

14.2.3. Speech Task Settings

• Tap the bar labeled “+” (beneath Global Settings) to define a task to be performed by the script. Alternatively, you can choose Menu Insert Task, which opens the same submenu as shown in the screenshot on the left.

The available task types are gone through one by one in the subsections that follow.

You can define multiple tasks in one script; see section 14.2.12.

Phone Number: The phone number to be dialed in the voice call. Valid characters are:+, #, *, 0, ..., 9.

Call Window, Call Duration: See section 14.2.3.1 below.

Num. of Attempts: The maximum number of times the voice call may be attempted. That is, the maximum number of retries in case of blocked calls is one less than the number entered here.a

Pause between Att.: Idle interval in seconds between call attempts.

DTMF keep-alive: If set to Yes, the phone will play a DTMF tone every 4 seconds to keep the call active.


a. For a blocked call to be retried, the time remaining of the call window must be larger than Call Duration + Pause between Att.

LZT 138 0361 R2A 75


14.2.3.1. Call Window and Call Duration Parameters

The diagrams below make clear the meanings of the parameters Call Window and Call Duration. Briefly, Call Window is the time window within which TEMS Pocket attempts to place the call, and Call Duration is the length of time the call will last after it has been set up.

First call setup attempt successful

First call setup attempt failed, second attempt successful

Redial on drop call: If set to Yes, the phone will automatically redial calls that were abnormally disconnected (neither party intentionally ended the call) as well as calls intentionally ended by the other party.a

a. A dropped call is retried repeatedly until it succeeds, or until no more than 2 s remain of the call window.

76

Chapter 14. Scripts

14.2.4. HTTP Task Settings

14.2.5. Ping Task Settings

URL: The URL or IP address of the HTTP server to download from. The http:// prefix is not required.

Timeout: Timeout of the whole download process. The timer is started when the data connection has been set up.a If the timeout is exceeded, the task is aborted as failed. Be sure to allot enough time to the task.

Proxy: Proxy server hostname and port, for example 123.45.67.89:8080. The use of a proxy is optional; leave the field empty if no proxy is used.

a. TEMS Pocket always reconnects to the data network for each new task.

Destination: The IP address or host name of the server to be pinged.

Size: Size in bytes of each Ping packet (ICMP payload).

Count: Number of Pings to send.

Timeout: Specifies the length of time to wait for receipt of the Echo Reply message corresponding to a given Echo Request message. If this time is exceeded, the message is counted as lost.

Pause: Waiting time between Ping messages. The pause starts when the reply is received or when the timer expires.

LZT 138 0361 R2A 77


14.2.6. FTP Task Settings

Server: Server host name or IP address.

Port: The FTP server port to use. The default is port 21.

FTP Mode: Active or Passive, as defined in IETF RFC 959.

Direction: Download or Upload.

Timeout: Timeout for the FTP task as a whole. The timer is started when the data connection has been set up.a If the timeout is exceeded, the task is aborted as failed. Be sure to allot enough time for the task.

Username, Password: User name and password on the FTP server, if required.

Remote Path:

• If Direction = Download: File to download from the FTP server. The file must exist. A leading slash is mandatory.

• If Direction = Upload: Path indicating where to store the file on the FTP server, followed by the name of the file to upload (the latter only if Gen. File Name = No: see below). The specified directory must exist; any existing file with the same name in that directory will be overwritten.

Example: /public/pocket/test.bin

Gen. File Name: Used for upload only. If set to Yes, TEMS Pocket will generate a file to be uploaded. In this case, do not enter a file name at the end of Remote Path.



78

Chapter 14. Scripts

Files downloaded over FTP are not saved to the phone. Therefore the operation cannot run out of memory. However, for technical reasons, download of files larger than 2 GB should be avoided.

14.2.7. WAP Task Settings

File Type, File Size: These parameters are used for upload only, and only if Gen. File Name is set to Yes. In this case you select here what type of file TEMS Pocket should generate:

• Binary: Randomly generated binary file.

• Text: Text file containing characters only.

• JPEG: Part of a JPEG image.

• Zip: Part of a zip file.

The size can be set in the range 1 … 10,000 kB. The default is 30 kB.

URL: The URL or IP address of the WAP page to be downloaded.

Timeout: Timeout of the whole download process. The timer is started when the data connection has been set up.a If the timeout is exceeded, the task is aborted as failed. Be sure to allot enough time to the task.

Proxy Address: The IP address of the WAP proxy. Mandatory field.

Proxy Port: The WAP proxy port number. The default is 8080. Mandatory field.


LZT 138 0361 R2A 79


14.2.8. SMS Task Settings

14.2.9. Idle Task Settings

Phone Number: The phone number to send SMS messages to, i.e. the TEMS Pocket phone’s own number (since the SMS task always consists of the phone sending messages to itself).a

Number of SMS: The number of messages to send.

Pause between SMS: Duration in seconds of pause between SMS messages.

Message Length: Number of characters in SMS message.

Guard Time: Time in seconds that has to elapse before SMS statistics are collected. The purpose of the guard time is to ensure that all sent messages have been received before statistics are calculated.

a. The reason the phone number needs to be entered manually is that on certain phones it is not possible to retrieve the number from the phone’s API.

This task consists of the phone spending a fixed length of time in idle mode.

Duration: Length of the idle mode period in seconds.

80

Chapter 14. Scripts

14.2.10. Random Idle Task Settings

14.2.11. Saving a Script

• On completing the settings for a task, you are prompted to save your script. This dialog appears:

This task consists of the phone spending a variable length of time in idle mode. The duration is randomly selected on each occasion within the interval Minimum ... Maximum.

Minimum: Minimum length of idle mode period in seconds.

Maximum: Maximum length of idle mode period in seconds.

File name: Type the name under which to save the script file. If you already entered a name in the global script settings, that name will be filled in here. The file will be saved with extension .QCG in the internal phone memory under \My Documents\TEMS.

Existing names: In this box are listed the names of all scripts already stored on the phone.

Finish by tapping OK in the screen footer.

LZT 138 0361 R2A 81


14.2.12. Adding More Tasks to a Script

• In the list of scripts, double-tap the script you want to add a task to. Alternatively, single-tap the script and choose Menu Edit.

14.2.13. Rearranging Tasks in a Script

• Tap the bar at the bottom labeled “+”, or alternatively tap Menu Insert Task, then select the type of task you want to add.

• To duplicate an existing task with all of its settings, tap the task to select it, then tap Menu Duplicate Task. The duplicate will be added beneath the original in the list of tasks.

• To move a task to a different position in the task list, tap Menu Move Tasks.

The script editor now enters “move mode” where you can move tasks to a different position by drag and drop. The Move Tasks item in the menu is tagged with a checkmark.

When you are done rearranging tasks, tap Menu Move Tasks again to exit move mode. The checkmark next to the Move Tasks menu item then disappears.

82

Chapter 14. Scripts

14.2.14. Deleting Tasks from a Script

14.3. Editing a Previously Saved Script

• To edit a script that you have previously saved, choose Menu Scripts Edit and double-tap the script you want to edit. Please refer to section 14.2 for all details on settings.

14.4. Duplicating an Entire Script

• To create a duplicate of an existing script, complete with all its tasks and settings, choose Menu Scripts Edit, then tap the script you want to duplicate and choose Menu Duplicate. A copy of the existing script is then added to the list of scripts.

14.5. Deleting a Script

• To delete an entire script, choose Menu Scripts Edit, then tap the script you want to delete and choose Menu Delete. You will be prompted to confirm deletion of the script.

• To delete a task, select it in the task list, then tap Menu Delete Task. You will be prompted to confirm this action before the task is deleted.

LZT 138 0361 R2A 83


14.6. Running a Script

• To run a script, choose Menu Scripts Start, then select the script you want to run.

• To stop a script that is running, choose Menu Scripts Stop.

The number of times or the duration for which the script will run is set in the global script settings, as described in section 14.2.1. You can always stop the script manually at any time with the Stop command.

You can configure TEMS Pocket to start a particular script automatically at application start-up. This is done under Menu Settings Application Start; see section 18.1.

When a script is started, the task status views for all task types represented in the script will appear. See chapter 9 for detailed information on task status views.

Note: Running a script for extended periods of time places a heavy load on the phone battery.

84

Chapter 15. Radio Alerts

15. Radio Alerts

15.1. Introduction to Radio Alerts

A radio alert is an audio message that is played:

• when the phone switches to or from a specific channel, or

• when a specific code enters or leaves the active set. The active set is displayed in the Cell List data view: see sections 6.1 and 7.1.

For precise definitions of “channel” and “code” for each cellular technology, see section 4.6. The meanings of these terms are also clear from sections 15.2–15.3 below.

You can set radio alerts for an arbitrary channel or code by selecting Menu Radio Alerts. How to accomplish this is covered in sections 15.2–15.3. Alternatively, you can set an alert for a channel or code that appears in a data view, by performing an action in the data view; see section�4.6.

When a radio alert is set and the relevant condition changes, an audio message is played, for example: “Channel Active”, “PN Not Active”. These messages also appear as events in the Events list (GSM/WCDMA: section 16.3.1.9; CDMA: section 16.3.2.4).

A bell symbol is used in data views to indicate the channel or code that is targeted by an alert (whenever this particular channel or code appears in the view). Again, see section 4.6 for details.

LZT 138 0361 R2A 85


15.2. GSM and WCDMA Radio Alerts

15.3. CDMA Radio Alerts

Channel Alert

• Tap the “enabled” checkbox to activate the channel alert function.

• In the box, select the ARFCN/UARFCN that should trigger the channel alert.

BSIC Alert (GSM)/SC Alert (WCDMA)

• Tap the “enabled” checkbox to activate the BSIC/SC alert function.

• In the box, select the code that should trigger the code alert.

Channel Alert

• Tap the “enabled” checkbox to activate the channel alert function.

• In the box, select the RF channel that should trigger the channel alert.

PN Alert

• Tap the “enabled” checkbox to activate the PN alert function.

• In the box, select the PN that should trigger the PN alert.

86

Chapter 16. Events

16. Events

Most events in TEMS Pocket are generated at crucial junctures in the phone’s interaction with the cellular network. A few events pertain to the phone’s internal operation.

16.1. Event Log

• To view events that have occurred, select Menu Events.

16.2. Audio Alerts for Events

TEMS Pocket can be configured to play an audio alert for each event that occurs. You activate this function under Menu Settings Events: see section 18.4.

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

Events are listed in chronological order.

To view details of an event, tap it in the event log. The log item is then expanded to also display event parameters: see screenshot.

The event log is cleared:

• every time you start TEMS Pocket

• when you open a logfile for replay

• when you close an open logfile.

LZT 138 0361 R2A 87


16.3.1. GSM/WCDMA Events

16.3.1.1. CC Events

16.3.1.2. IRAT Events

16.3.1.3. MM Events

Event Name Parameters

Blocked Call Call typea

a. Call type is one of: Mobile-originated, Mobile-terminated, or Undefined call type.

Call Attempt Call typea

Call End Call typea; Call duration in seconds (or “No Answer”)

Call Established Call setup time in ms

Dropped Call Call typea; Call duration in seconds


Handover From UTRAN Failure

–

Handover To UTRAN Failure

–


Authentication Failure –

Authentication Reject –

MM Service Home –

88

Chapter 16. Events

16.3.1.4. RR Events

16.3.1.5. RRC Events

16.3.1.6. SM Events

MM Service Roaming –

No Service –


GSM Handover Failure –


UMTS Access Attempt –

UMTS Access Success –

UMTS Connection Failure –


PDP Context Activation: Attempt

–

PDP Context Activation: Complete

–

PDP Context Activation: Reject

–

PDP Context Deactivation: Attempt

–


LZT 138 0361 R2A 89


16.3.1.7. Session Events

16.3.1.8. Application Events

PDP Context Deactivation: Complete

–

PDP Context Deactivation: Failure

–


FTP Transfer Start –

FTP Transfer End –

FTP Transfer Fail –

Voice Call Start (Call Attempt)

–

Voice Call End –

Voice Call Failed (Call Failed)

–


GPS Connected Internal/External

GPS Disconnected Internal/External

GPS Location Found –

GPS Location Lost –


90

Chapter 16. Events

16.3.1.9. Radio Alerts

16.3.1.10. Other Events

16.3.2. CDMA/EV-DO Events

16.3.2.1. Network Generated Events


Set BSIC Alert, Active Old BSIC, New BSIC

Set BSIC Alert, Not Active Old BSIC, New BSIC

Set GSM Channel Alert, Active

Old ARFCN, New ARFCN

Set GSM Channel Alert, Not Active

Old ARFCN, New ARFCN

Set Scrambling Code Alert, Active

Old SC, New SC

Set Scrambling Code Alert, Not Active

Old SC, New SC

Set WCDMA Channel Alert, Active

Old UARFCN, New UARFCN

Set WCDMA Channel Alert, Not Active

Old UARFCN, New UARFCN


Low Disk Space Memory left in MB on internal memory or memory card


Call Access Timeout Call typea

LZT 138 0361 R2A 91


EVDO Connection Failure Causes

• Connection deny received with Deny reason = General

• Connection deny received with Deny reason = Network Busy

• Connection deny received with Deny reason = Authentication or billing failure

• Maximum access probes

• System lost (supervision failures)

• Not preferred (SD told OVHD to switch systems, QC redirect, Access network ID)

Call Attempt Call typea

Call Attempt Retry Call typea

Call End Call typea; Call duration in seconds (or “No Answer”)

Call Established Call setup time in ms

Call Setup Call typea; Call setup time in ms

No Service Mode –

Dropped Call Call typea; Call duration in seconds

Blocked Call Call typea

EVDO Access Success Sector (PN) sending ACAck message; Sector (PN) sending TCA message

EVDO Connection Failure Failure cause; see listing below this table

EVDO Connection Success

–

Handoff Failure –

a. Call type is one of: Mobile-originated, Mobile-terminated, or Undefined call type.


92

Chapter 16. Events

• Redirect (ALMP received a redirect message)

• Connection setup timeout

• Power down received

• Offline received

• NAM change received

• User abort

• Access handoff

• Unknown

16.3.2.2. Session Events

16.3.2.3. Application Events

16.3.2.4. Radio Alerts


FTP Transfer Start –

FTP Transfer End –

FTP Transfer Fail –


GPS Connected Internal/External

GPS Disconnected Internal/External

GPS Location Found –

GPS Location Lost –


Set Channel Alert, Active Old RF channel, New RF channel

LZT 138 0361 R2A 93


16.3.2.5. Other Events

Set Channel Alert, Not Active

Old RF channel, New RF channel

Set PN Alert, Active Old PN, New PN

Set PN Alert, Not Active Old PN, New PN


Low Disk Space Memory left in MB on internal memory or memory card


94

Chapter 17. Indoor Locations

17. Indoor Locations

17.1. Introduction

An indoor location is an entity containing a map on which you can manually pinpoint data. Creating an indoor location is useful when doing testing indoors or in other locations with no GPS coverage. For example, you can use the phone’s camera to photograph a blueprint or evacuation plan for the relevant floor of a building.

Once created, the indoor location is displayed in the regular Map view, which can be put in a special indoor mode. For all details on these matters, as well as on the pinpointing procedure, see section 10.2.

17.2. Creating an Indoor Location

The procedure of creating an indoor location can alternatively be performed on the PC, using the TEMS Pocket Tools utility: see section 22.2.2. The map can then be transferred to the phone. An advantage of this method is that you do not have to think about limiting the map image size (in bytes), since TEMS Pocket Tools automatically lowers the image resolution as required by TEMS Pocket.

If you prefer to create your indoor location from within TEMS Pocket, do as follows:

• Tap Menu Indoor Maps.

Note: The indoor functionality requires a special license option.

LZT 138 0361 R2A 95


Any indoor locations that you have previously created appear on this screen. In the screenshot on the left, however, no previous maps exist.

• Tap Menu, then tap Create.

For the map image you can use either a pre-existing file stored on the phone or a picture that you take with the phone camera.

• If you choose From File, browse to select your file. The formats GIF, JPG, and PNG are supported.

• If you choose From Camera, the phone goes into camera mode. Take a picture, then tap the return arrow button to return to TEMS Pocket. Note: The picture should not be larger than about 1 megapixel.

96

Chapter 17. Indoor Locations

This concludes the definition of the indoor location. It is now ready to be displayed in the Map view: see section 10.2.

In either case, a screen listing image file attributes now appears.

Id: Identity number of the indoor location (generated by TEMS Pocket).

File Name: Name of the file embodying the indoor location, stored with extension .loc in the phone memory or on the memory card under \My Documents\TEMS.

Image: Image dimensions in pixels (width × height).

Type, ..., Description: These are free-text fields which you can fill in as you see fit.

LZT 138 0361 R2A 97


18. Settings

From the Settings menu you configure various properties of TEMS Pocket.

Settings can be exported to file and re-imported from such a file; see section 18.8.

18.1. Application Start

Auto-start Pocket: If set to On, TEMS Pocket will launch automatically when you turn on the phone.

Time sync: If set to On, TEMS Pocket will automatically sync its time with the cellular network at application start-up (provided of course that the phone is in coverage).

Start logging: If set to On, TEMS Pocket will begin logfile recording immediately on start-up. Compare section 13.1.

Start script: Selecting a script here will cause that script to be run automatically at application start-up. The drop-down box holds all scripts that are currently defined (see chapter 14). Select “<None>” if you do not wish to activate this function.

Repeat script: If set to On, the script that is run automatically at start-up will be repeated (subject to the limit on number of turns or duration that may be defined in the script itself: see section 14.2.1). Each time the script has finished, the logfile is closed. Then, after a pause as long as specified by the Idle betw. scripts setting, a new logfile is opened and the script is run again.

98

Chapter 18. Settings

18.2. Data Views

These settings pertain to all TEMS Pocket views and to the graph.

Screen Theme

• Default: Data views: black on white. Graph: white/color on black. (That is, everything appears as depicted in this manual.)

• Day: Black on white everywhere.

• Night: White/color on black everywhere.

Reset Distributions: Here you specify when distribution charts should be reset: at TEMS Pocket start-up, when a logfile is opened, or for each task that is run.

Chart Zoom Level: The zoom level of the chart, expressed as the length of time to which one screen width corresponds (in portrait mode). One of 6, 12, 30, 60, or 120 seconds.

Enable Screenshot: This setting governs the function of the snowflake icon appearing in data view headers. Tapping the snowflake always freezes the screen.

• If the Enable Screenshot option is set Off, this action has no further effect.

• If the option is set On, tapping the snowflake also brings up a camera icon next to it. Tapping that icon takes a screenshot.

See also sections 4.7–4.8.


LZT 138 0361 R2A 99


18.3. Logging

Force Backlight

• If set to On, the screen backlight always stays on even if there is no user activity. Warning: This setting will cause the phone battery to drain very quickly. Please ensure that the phone is connected to a charger at all times.

• If set to Off, the screen backlight times out as specified in the phone settings under Start Settings All Settings System Power, tabs “Backlight” and “Advanced”.

Start with Script: If set to On, logfile recording will be started automatically if you manually start a script (and logging is not already started). The logging will also be stopped once the script has finished.

Logfile name: Here you select the naming format for logfiles.

• Date & time

• Date & device & number

• Manual: You are invited to name the logfile on starting to record it; compare section 13.1.

100


18.4. Events

18.5. GPS

Play audio alerts: If set to On, an audio alert will be played for each event that occurs. The message consists of the event name being spoken.

Here you select what kind of GPS device TEMS Pocket should use, if any.

GPS in use:

• None: No use will be made of any GPS.

• Internal: The phone’s internal GPS will be used.

• External: When you select this, TEMS Pocket will start searching for external Bluetooth GPS units. If one is found, TEMS Pocket will try to connect to that GPS. If no external GPS is found, the internal GPS will be used instead.

See also sections 18.5.1 and 18.5.2 below.

Units: This setting governs the choice of units in the GPS Location data view: metric or English (see section 7.10). The setting does not affect any other parts of the TEMS Pocket user interface.

LZT 138 0361 R2A 101


18.5.1. Using the Built-in GPS

Access to the phone’s built-in GPS is included in the TEMS Pocket 8.2 product package.

Please note that the built-in GPS consumes a large amount of power and thus requires frequent charging of the phone battery.

18.5.2. Using an External GPS

TEMS Pocket can alternatively connect to an external Bluetooth GPS. This capability, too, is part of the TEMS Pocket 8.2 product package and does not require any separate option. The GPS itself, however, must be purchased separately from Ascom as an accessory (see section 2.13). Please note that this is the only external GPS device supported by TEMS Pocket 8.2.

To use a Bluetooth GPS, power on the GPS before starting the TEMS Pocket application on the phone. TEMS Pocket will then find and connect to the GPS device automatically.

If the connection to the Bluetooth GPS is temporarily lost, TEMS Pocket will automatically reconnect to the GPS once it has become accessible again.

If you set GPS in use to “External”, and TEMS Pocket fails to find an external Bluetooth GPS, then TEMS Pocket will automatically resort to the internal GPS and keep using that device as long as the application remains in live mode. After you do some logfile replay and then close the logfile to return TEMS Pocket to live mode, TEMS Pocket will again check whether an external GPS is available and if possible connect to it.

Once TEMS Pocket has connected to a certain external GPS, it will on future occasions first try to reconnect to that unit before searching for any other available GPS units.

The external GPS does not need to be Bluetooth paired with the TEMS Pocket phone.

102


18.6. Wireless File Transfer

Automatic Transfer: Here you specify the behavior of the logfile upload function. See section 13.3 for instructions on how to do the basic setup of logfile uploading.

• Disabled: No automatic logfile uploads.

• Ask when log closed: When logfile recording ends, a prompt appears asking you if you want to upload the file.

• Always when log closed: When logfile recording ends, the file is immediately uploaded.

Default Server: This setting determines how to select the FTP server to upload to.

• <Always ask>: You will be prompted to select an FTP server on each upload occasion.

• Names of defined FTP servers: All FTP servers currently defined under Menu Result Upload Server Settings (see section 13.3.1) are listed here. If you select one of these servers, logfiles will always be uploaded to that server.

• <Add/remove>: This choice takes you to the dialog where you define FTP servers: Menu Result Upload Server Settings. Again, refer to section 13.3.1 for instructions.

LZT 138 0361 R2A 103


18.7. Software Update

18.8. Exporting and Importing Settings

Check for updates:

• Check & notify: When the TEMS Pocket application is closed, the TEMS Pocket OTA server is checked for a software update, and if one is available you are asked if you want to install the new version.

• Check & install: When the TEMS Pocket application is closed, the TEMS Pocket OTA server is checked for a software update, and if one is available it is installed automatically.

• No check: No checks for software updates are done.

• Disable updates: Warning: If you select this, the Software Update settings will disappear entirely, which means that no further updates can ever be done over the air.

Check now: Tap the link to immediately check the TEMS Pocket OTA server for software updates.

• While in the Settings menu, tap Menu. The choices Export Settings and Import Settings appear.

• For either operation, indicate the folder you want to export to or import from. This is always a folder under \My Documents\TEMS\Settings. In the case of export, you can optionally create a new folder for the purpose.

104


18.9. Default Settings

This section lists the default settings in the Settings menu.

18.9.1. Application Start

• Auto-start Pocket: On

• Time Sync: Off

• Start Logging: Off

• Start Script: None

• Repeat Script: Off

18.9.2. Data Views

• Screen Theme: Default

• Reset Distributions: Pocket start-up

• Chart Zoom Level: 30 sec

• Enable Screenshot: On

• Force Backlight: Off

18.9.3. Logging

• Start with Script: Off

• Logfile Name: Date & time

18.9.4. Events

• Play Audio Alerts: On

18.9.5. GPS

• GPS in Use: External

• Units: Metric

LZT 138 0361 R2A 105


18.9.6. Wireless File Transfer

• Automatic Transfer: Disabled

• Default Server: Always ask

18.9.7. Software Update

• Check for Updates: Check & notify

106

Chapter 19. Thematics

19. Thematics

This is a legend showing how measurement values are color-coded in the TEMS Pocket data views. All information presented here is read-only.

GSM and WCDMA

CDMA

Min, Max: Endpoints of parameter range.

Green, Red: Thresholds governing color coding of measurements in data views.

• Parameter values better than the Green threshold are color-coded in green.

• Parameter values between the Green and Red thresholds are color-coded in yellow.

• Parameter values worse than the Red threshold are color-coded in red.

What is meant by “better” and “worse” will be obvious in each case (see screenshots).

LZT 138 0361 R2A 107


20. License Info

Customer ID: A unique ID for each customer, assigned by Ascom.

System ID: A unique number for each TEMS Pocket device, assigned by Ascom.

Device ID: A unique hardware ID for the TEMS Pocket device.

Email: There is normally no need to use this field.

Comment: This field can contain arbitrary text. It is intended to help identify the TEMS Pocket device.

Renew License button: This button normally does not need to be used.

When a valid TEMS Pocket license is installed, the string “License valid” is displayed at the bottom of the screen, as shown in the screenshot.

108

Chapter 21. About Screen

21. About Screen

The About screen shows:

• User name

• ESN of TEMS Pocket device

• Customer ID and System ID (compare chapter 20)

• License type

• License options

• TEMS Pocket software version

LZT 138 0361 R2A 109


22. Using TEMS Pocket Tools

With TEMS Pocket 8.2 is delivered a PC software utility called TEMS Pocket Tools. This utility is used for:

• composing TEMS Pocket 8.2 scripts; see section 22.2.1

• defining TEMS Pocket 8.2 indoor locations; see section 22.2.2

• converting TEMS Pocket 8.2 logfiles to a format readable by TEMS Investigation; see section 22.3.

22.1. Installing TEMS Pocket Tools

The TEMS Pocket Tools software is contained in a regular Microsoft Windows installation package (MSI). Supported operating systems are Windows XP and older. The PC must have .NET Framework 2.0 installed.

If you have an older version of TEMS Pocket Tools installed on the PC, it is recommended to uninstall that version first.

• Install TEMS Pocket Tools by double-clicking the installation file.

After installation, two icons will appear on the desktop:

• TEMS Pocket Tools. This is the application used to create scripts and indoor locations.

• TEMS Pocket TMZ Decoder. This application handles conversion of TMZ files into logfiles that can be read by TEMS Investigation.

The installation also adds the following items to the Start menu under All Programs Ascom TEMS Products:

• TEMS Pocket Tools

• TEMS Pocket TMZ Decoder

• TEMS Pocket TMZ Decoder (whole directory)

The difference between the two latter items is that one operates on individual files and the other operates on all files in a folder. See section 22.3.

110

Chapter 22. Using TEMS Pocket Tools

22.2. Using TEMS Pocket Tools

• Start the TEMS Pocket Tools application either by clicking the desktop shortcut or by choosing Start All Programs Ascom TEMS Products TEMS Pocket Tools.

22.2.1. Using TEMS Pocket Tools to Compose Scripts

Regarding scripts in general and how to compose them directly in the TEMS Pocket user interface, see chapter 14. Also please turn to this chapter for explanations of all script settings.

• In TEMS Pocket Tools, choose File New Script.

• Fill in the global settings.

• To add a task, click the button labeled with a plus sign. A drop-down menu appears from which you select the desired task type.

LZT 138 0361 R2A 111


• Each task has its specific parameters. They are exactly the same as when defining scripts in the TEMS Pocket user interface; please refer to section 14.2 for details. Below is an example showing the setup dialog for FTP tasks.

• Use the “up” and “down” buttons to move a task up or down through a script. Use the button with a cross to delete a task from a script.

• Scripts can be saved with file extension .qcg and transferred to the TEMS Pocket phone. This is done by clicking the Save button (see screenshot

112


below). Store your scripts under \My Documents\TEMS in the phone file system.

22.2.2. Using TEMS Pocket Tools to Define Indoor Locations

You can use TEMS Pocket Tools for defining an indoor location. You first need to procure the file to use as map image; then you can point to that file and define properties of the indoor location, just as can be done in TEMS Pocket itself (see section 17.2).

• In TEMS Pocket Tools, choose File New Indoor Location.

• A file dialog opens. Locate and select the image file you want to use as a map.

• Fill in the properties of the indoor location:

• Now save the indoor location. The file receives the extension .loc. Store this file under \My Documents\TEMS in the phone file system.

LZT 138 0361 R2A 113


22.2.3. Other Functions of TEMS Pocket Tools

• It is possible to have multiple scripts and indoor locations open. By default a distinct dialog tab is created for each:

• You select the item to work with by clicking the desired tab label, or alternatively by selecting the desired item from the Window menu:

• To hide a tab, right-click it and choose Hide. If you want to show the tab again, just select it from the Window menu.

• You can undock any tab so that it appears in a separate window. This is done by right-clicking the tab label and choosing the Floating option. To redock the window, right-click the window title bar and click on “Floating” once more so that the option is unchecked. See the images that follow.

114


22.3. Using TEMS Pocket TMZ Decoder to Convert Logfiles

The format in which TEMS Pocket 8.2 records its logfiles (extension .TMZ) is not immediately readable by TEMS Investigation. A file conversion is therefore necessary.

Section 13.2.1 lists the TEMS Investigation versions that are capable of reading the converted files.

22.3.1. Converting Individually Selected Logfiles

To convert selected logfiles that reside on the PC hard drive:

• Double-click the desktop shortcut TEMS Pocket TMZ Decoder, or choose Start All Programs Ascom TEMS Products TEMS Pocket TMZ Decoder.

• Select the files to convert and start the process. Alternatively, you can double-click one file to have it converted. In either case, a progress view appears.

The converted files will be saved in the same folder but with the extension .LOG.

If pinpointing was performed during recording, the output from the conversion is a zip archive with contents as detailed in section 10.2.2.4. This zip archive includes the *.LOG file.

LZT 138 0361 R2A 115


22.3.2. Converting All Logfiles in a Folder

To convert all logfiles in a folder:

• Choose Start All Programs Ascom TEMS Products “TEMS Pocket TMZ Decoder (whole directory)”.

• Select the folder containing the files to convert and start the process.

All logfiles in the folder are now converted and saved with the extension .LOG in the same folder.

22.4. Help Menu

The Help menu in TEMS Pocket Tools provides access to this User’s Manual in the form of a PDF file. The manual is also stored in the root directory of the TEMS Pocket phone’s memory card.

116

Chapter 23. Support Contact Information

23. Support Contact Information

For support in using TEMS Pocket, please contact Ascom according to the directions found at www.ascom.com/networktesting under the link “TEMS Sales & Support”.

To sign up for the TEMS on-line subscription service, please go to the same web site and click the link “TEMS Subscription Service”. This free service includes e-mail notification of TEMS product launches, version upgrades and patches, as well as on-line TEMS News.

LZT 138 0361 R2A 117

http://www.ascom.com/networktesting


Appendix A. File Types Specific to TEMS Pocket 8.2

Extension File Type

.LOC TEMS Pocket 8.2 indoor location

.LOG Logfile in TEMS Pocket 8.2 indoor measurement zip archive (which is itself contained in a .TMZ file)

.PPF TEMS Pocket 8.2 waypoint file

.QCG TEMS Pocket 8.2 measurement configuration file

.TMZ TEMS Pocket 8.2 logfile

118

Index

Index

AAbout screen 109Absolute Radio Frequency Channel Number 14active set (CDMA) 33active set (WCDMA) 27ActiveSync 7altitude 26AMR speech codecs

in GSM 23WCDMA 31

AMR Usage data view (GSM) 23AMR Usage data view (WCDMA) 31Application Start settings 98ARFCN 14, 18audio alerts

for events 87, 101for radio alerts 85

auto-start of TEMS Pocket at phone power-on 98

BBA list 21BA List data view 21backlight, forcing 100band lock (GSM/WCDMA) 62Base Station Identity Code 14, 19, 21battery charging considerations 84BCCH 18, 21, 24, 32BCCH Allocation list 21BLER 31Block Error data view (WCDMA) 31Block Error Rate (WCDMA) 31Bluetooth 69Bluetooth GPS, using 102Broadcast Control Channel 21, 24, 32BSIC 14, 19, 21

LZT 138 0361 R2A 119


BSIC alerts, setting from the TEMS Pocket menu 86

Ccandidate set (CDMA) 33capturing TEMS Pocket data views 20car kit 8CDMA Perform data view 36Cell Identity 54Cell Identity (CDMA) 14Cell Identity (GSM) 21, 24Cell Identity (WCDMA) 32Cell List data view (CDMA) 33Cell List data view (GSM) 21Cell List data view (WCDMA) 27cell locations, presentation in Map view 54cell selection and reselection parameters (WCDMA) 28channel alerts

setting from the TEMS Pocket menu 86setting in data views 18

Close Logfile command 69color coding of parameter values 13, 55, 107control functions in TEMS Pocket 60converting logfiles to TEMS Investigation format 115

Ddata service, time using

CDMA 38EV-DO 38

data throughput (IP level)data uplink 22downlink 22uplink 22

data views 4browsing 4details of individual views 33

GSM 21WCDMA 27

general properties of 13overview of 11settings for 99zoom level of charts 99

Data Views settings 99date formats 26

120

Index

DCH (WCDMA), time using 25Dedicated Channel (WCDMA), time using 25default settings in TEMS Pocket 105distribution charts

automatic resetting of 99resetting manually 22, 23, 31, 35

drive test route, presentation in Map view 54

EEc/Io (CDMA) 33, 36, 37

total for all fingers 34Ec/Io (WCDMA) 24, 27, 32EVDO Perform data view 37event log 6, 87events 6, 87

application events 93audio alerts for 87, 101list of event types

CDMA/EV-DO 91GSM/WCDMA 88

network generated 91settings for 101

exporting TEMS Pocket settings 104

FFER (CDMA) 34, 36file types specific to TEMS Pocket 118filemarks 66finger navigation 4finger scrolling 4Finger Sum (CDMA) 34, 36Frame Erasure data view (CDMA) 34Frame Erasure Rate (CDMA) 34, 36freezing the screen 9, 16, 19FTP server settings for logfile upload 69FTP states 39FTP task settings 78FTP task status views 42, 53

GGoogle Maps 6, 54GPS 6

number of satellites seen 26positions of satellites seen 26

LZT 138 0361 R2A 121


settings for 101signal strength of satellites seen 26status of 26time 26using an external (Bluetooth) GPS 101, 102using the phone’s internal GPS 101, 102

GPS Location data view 26, 38units used in 101

graph 5plotting data view items in 15plotting task status view items in 53

graphic presentation 13GSM neighbors measured in WCDMA mode 32

Hheader of TEMS Pocket views 4, 9home network, time registered in (CDMA) 38home network, time registered in (GSM/WCDMA) 25HTTP states 39HTTP task settings 77HTTP task status views 44, 53

IIdle mode, time spent in

CDMA 38EV-DO 38GSM 25WCDMA 25

Idle task settings 80importing TEMS Pocket settings 104indoor locations 55, 95

creating 95defining in TEMS Pocket Tools 113loading into Map view 55

indoor map 6indoor positioning by pinpointing 55Inter RAT Info data view (GSM) 24Inter RAT Info data view (WCDMA) 32invalid parameters, representation of 13IP related states 39IP Thr.put DL data view 22IP Thr.put UL data view 22

122

Index

Llandscape screen mode 20language support 8latitude 26launching of the TEMS Pocket application 2launching TEMS Pocket manually 3legend in Map view 55License Info dialog 108Link Quality (CDMA) 36Lock on band (GSM/WCDMA) 62Lock on RAT 60

for CDMA 61for GSM/WCDMA 60

logfile recording 5, 65adding filemarks 66automatic on start-up 98automatic when script is started manually 100in conjunction with route pinpointing 57low memory condition 66manual 65memory usage 66naming format for logfiles 100symbol for 9, 65

logfile replay 66controls for 67drop-down menu for 10in TEMS Investigation 69

logfile transfer via FTP 69logfile upload 5, 65

configuring 69FTP server settings for 69manual 70selecting which configuration (FTP server) to use 103specifying behavior of 103

logfiles, converting to TEMS Investigation format 115Logging settings 100longitude 26

MMap view 6, 54

controls in 59customizing appearance of route markers 57Google Maps mode 54

LZT 138 0361 R2A 123


indoor mode 55loading map image into 55manually assigning geographical position to map image 59navigating in 56, 59panning 56, 59plotting a data view item in 17plotting task status view items in 53zoom level 56zooming 59

maximizing charts in data views 20MCC 14menu of TEMS Pocket application 7, 64MNC 14Mobile Country Code 14Mobile Network Code 14

Nneighbor cells

GSM neighbors measured in WCDMA mode 32WCDMA neighbors measured in GSM mode 24

neighbor cells (GSM) 21neighbor set (CDMA) 33neighbor set (WCDMA) 27No Service mode, time spent in

CDMA 38GSM/WCDMA 25

OOpen Logfile command 66overview of TEMS Pocket 2

PPacket Data Channel (GSM), time using 25Packet Error data view (CDMA) 35Packet Error Rate (CDMA) 35, 37panning the Map view 56, 59PDCH (GSM), time using 25PER (CDMA) 35, 37Ping states 39Ping task settings 77Ping task status views 46, 53pinpointing 56

contents of logfile with pinpointing data 58

124

Index

plotting data view itemsin the graph 15in the Map view 17

plotting task status view itemsin the graph 53in the Map view 53

PN 19, 33PN alerts

setting from the TEMS Pocket menu 86setting in data views 19

portrait screen mode 20positioning of data

by manual pinpointing 6using GPS 6

Rradio alerts 85

events generated in event log (CDMA) 93events generated in event log (GSM/WCDMA) 91for CDMA 86for GSM/WCDMA 86setting from the TEMS Pocket menu 85setting in data views 18

Random Idle task settings 81RAT indicator 9, 10RAT lock 9, 60

indication of 62RAT states 10Receive Power (CDMA) 14, 36, 37Received Signal Code Power (WCDMA) 14, 24, 27, 32Received Signal Level 14, 21, 24, 32recording logfiles 5, 65replay controls 67replaying logfiles 66

in TEMS Investigation 69Result Upload menu 69RF Channel number 14, 18RF data in top section of data views 13roaming network, time registered in

CDMA 38GSM/WCDMA 25

route, presentation in Map view 54RRC parameters 30

LZT 138 0361 R2A 125


RSCP (CDMA) 33RSCP (WCDMA) 14, 24, 27, 32Rx Power (CDMA) 14, 36, 37Rx Qual data view (GSM) 23RxLev 14, 21, 24, 32

SSC 14, 19, 27SC alerts

setting from the TEMS Pocket menu 86scrambling code 14, 19, 24, 32screen captures

enabling 99taking 20

scripts 5, 11, 41, 73adding more tasks to 82composing in TEMS Pocket user interface 73composing with TEMS Pocket Tools 111creating a new task in 75deleting 83deleting tasks from 83duplicating 83duplicating a task in 82editing 83global settings for 74naming 74rearranging tasks in 82run limit for 74running automatically on start-up 98running manually 84saving 81services supported by 73tasks in 75

serving cell (GSM) 21Serving Cell data view (WCDMA) 28settings

exporting 104importing 104

Settings menu 98SIB 3 28SIB 5 29SID 14signal to interference-plus-noise ratio (SINR) (CDMA) 37

126

Index

signal-to-noise ratio (CDMA) 36, 37signal-to-noise ratio (WCDMA) 24, 32SINR (CDMA) 37SMS states 40SMS task settings 80SMS task status views 48, 53snowflake symbol (screen freeze indicator) 19Software Update settings 104Speech Quality data view (CDMA) 36Speech Quality Index (CDMA) 36speech service, time using (CDMA) 38Speech task settings 75Speech task status views 50, 53speed 26SQI (CDMA) 36Start/Stop Logging commands 65Status view (showing general information) 5, 39Stop Logging command 65support contact information 117System Identification 14System Information Block 3 28System Information Block 5 29system status indicators in phone display 4

Ttask status views 5, 41

colored dot indicator 41for FTP 42for HTTP 44for Ping 46for SMS 48for speech 50for WAP 52overview of 13plotting items from in graph or Map view 53settings for 99showing current task 41showing overall results 41

tasks in scripts 75TCH (GSM), time using 25TEMS Investigation 5, 66, 69, 115TEMS Pocket Positioning Tool 59

LZT 138 0361 R2A 127


TEMS Pocket TMZ Decoder utility 110using to convert logfiles to TEMS Investigation format 115

TEMS Pocket Tools utility 69, 110accessing this User’s Manual from 116composing scripts with 111defining indoor locations in 113installing 110

Thematics 107theme for TEMS Pocket views 99Time Log data view (CDMA) 38Time Log data view (GSM/WCDMA) 25time synchronization with cellular network 98TMZ file extension 65Traffic Channel (GSM), time using 25Transmit Power (CDMA) 14, 36, 37Transmit Power (GSM) 14Transmit Power (WCDMA) 14Tx Power (CDMA) 14, 36, 37Tx Power (GSM) 14Tx Power (WCDMA) 14

UUARFCN 14, 18, 24, 27UMTS Absolute Radio Frequency Channel Number 14units (metric vs. English) 26, 101unregistered (time spent without being registered in a network) 25uploading logfiles 5

configuring 69selecting which configuration (FTP server) to use 103specifying behavior of 103

using an external (Bluetooth) GPS 8

Vviews in TEMS Pocket, overview of 11voice call states 39voice service, time using (CDMA) 38

WWAP states 39WAP task settings 79WAP task status views 52, 53WCDMA neighbors measured in GSM mode 24Windows Mobile 1, 4Wireless File Transfer settings 103

128

Index

Zzoom level of data view charts 99zooming the Map view 59

LZT 138 0361 R2A 129

www.ascom.com/tems

06

.20

10

© A

scom

20

10

. All

righ

ts r

eser

ved.

TEM

S is

a t

rade

mar

k of

Asc

om .

All

othe

r tr

adem

arks

are

the

pro

pert

y of

the

ir r

espe

ctiv

e ho

lder

s.

Ascom Network Testing Inc.1943 Isaac Newton SquareReston, Virginia 20190 | USAwww.ascom.com/tems

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

AScoM NETwork TESTiNg lEAdS ThE world iN

providiNg bEST-iN-clASS SoluTioNS To

MEASurE, ANAlyzE, ANd opTiMizE MobilE

NETworkS.

The TEMS™ Portfolio offers a complete set of

trusted solutions for drive testing, benchmarking,

monitoring, and analyzing network performance.

These state-of-the-art offerings facilitate the

deployment, optimization, and maintenance of mobile

networks.

We are the industry leader, and our products are

supplied to the world’s top mobile operators, equip-

ment vendors, and professional service providers.

http://www.ascom.com/tems