TEMS Pocket 7.3 For Sony Ericsson W995 and W995a - User's Manual

TEMS™ Pocket 7.
3
for Sony Ericsson W995 and W995a
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 0240 R2A

Contents
Contents
1. Introduction 1
1.1. What’s New in TEMS Pocket 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1. Presentation of Cell Names . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.2. Event-based Logfile Sifting. . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.3. Improved Logfile Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.4. Coexistence with MRU (Mobile Receiving Unit). . . . . . . . . . . 2
1.2. What Was New in TEMS Pocket 7.2. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1. New UMTS Phones: Sony Ericsson W995/W995a . . . . . . . . 2
1.2.2. New GSM Phone: Sony Ericsson W995 EDGE . . . . . . . . . . . 3
1.2.3. Scanning (GSM and WCDMA). . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.4. Command Sequence Enhancements. . . . . . . . . . . . . . . . . . . 3
1.2.5. Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.6. Passive Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.7. New GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.8. Data Upload over WiFi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.9. HSPA Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.10. WCDMA AMR Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3. What Was New in TEMS Pocket 7.0. . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.1. Phones: Sony Ericsson C905, C905a . . . . . . . . . . . . . . . . . . 5
1.3.2. Map View and Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.3. Data Views with Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.4. Smarter Logfile Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.5. Cell Id Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3.6. Snapshots of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3.7. Importing and Exporting TEMS Pocket Settings . . . . . . . . . . 7
2. Overview of TEMS Pocket 8

2.1. Phone Mode vs. Scan Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2. Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1. Data Views with Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3. Map View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4. Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
LZT 138 0240 R2A i

TEMS Pocket 7.3 for Sony Ericsson W995 and W995a – User’s Manual
2.5. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6. Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.1. Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.2. GPS Positioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.3. Positioning by Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.7. Cell Control Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.8. Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.9. Scan Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.10. Storage Medium: Phone Memory vs. Memory Stick. . . . . . . . . . . 12
2.11. Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.12. Turning TEMS Pocket Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3. Data Views: General 14

3.1. General Data View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2. The Built-in Help Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3. The Capture Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4. Other Data View Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5. Survey of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4. Data Views in Text Format 21

4.1. W/G Cells (View No. 1.1) ............................. 21
4.1.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2. PDP Context (View No. 1.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3. MM/GMM (View No. 1.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.4. Time Log (View No. 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.5. FTP Data (View No. 1.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.6. GPS (View No. 1.6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.7. Map (View No. 1.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.8. Progress (View No. 1.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.9. WCDMA Cells (View No. 2.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.10. WCDMA Cell Id (View No. 2.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.10.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.11. WCDMA C. (Cell) Name (View No. 2.3) . . . . . . . . . . . . . . . . . . . . 35
4.12. WCDMA Serv. Cell (View No. 2.4) . . . . . . . . . . . . . . . . . . . . . . . 36
4.13. WCDMA Channel (View No. 2.5) . . . . . . . . . . . . . . . . . . . . . . . . . 38
ii
Contents
4.14. WCDMA AMR (View No. 2.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.15. WCDMA Data (View No. 2.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.16. HSPA Data (View No. 2.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.17. GSM Cells (View No. 3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.18. GSM Cell Id (View No. 3.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.19. GSM Cell Name (View No. 3.3). . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.20. GSM BA List (View No. 3.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.21. GSM Serving Cell (View No. 4.1) . . . . . . . . . . . . . . . . . . . . . . 50
4.22. GPRS Data (View No. 4.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.23. GPRS Info (View No. 4.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.24. GSM C/I Info (View No. 4.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.25. GSM AMR (View No. 4.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.26. The WAP Browser Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.26.1. WCDMA WAP Browser Data View . . . . . . . . . . . . . . . . . 61
4.26.2. GPRS WAP Browser Data View . . . . . . . . . . . . . . . . . . . 63
5. Data Views with Graphs 65

5.1. W/G Serving RSSI (View No. 5.1) . . . . . . . . . . . . . . . . . . . . . . . . 66
5.2. W/G Cells (View No. 5.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5.3. W/G Data (View No. 5.3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.4. WCDMA Serving (View No. 5.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.5. WCDMA SIR (View No. 5.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.6. WCDMA Cells (View No. 5.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.7. GSM Cells (View No. 5.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.8. GSM Data (View No. 5.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6. The Map View 78

6.1. Loading a Map Image into the Map View . . . . . . . . . . . . . . . . . . . . 78
6.2. Pinpointing Your Test Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.2.1. Setting the Map Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.2.2. Customizing the Appearance of Route Markers. . . . . . . . . . 79
6.2.3. Entering Map Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
LZT 138 0240 R2A iii

6.2.4. Pinpointing and Recording. . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.3. Positioning the Map Geographically . . . . . . . . . . . . . . . . . . . . . . . . 82
7. TEMS Pocket Functions in the Activity Menu 83

7.1. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.2. Insert Filemark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.3. Start/Stop Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.3.1. Icons Used for Logfile Recording. . . . . . . . . . . . . . . . . . . . . 84
7.4. Start/Stop Logfile Replay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.4.1. Replay Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.4.2. Icons Used for Logfile Replay . . . . . . . . . . . . . . . . . . . . . . . 86
7.5. Tag Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.6. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.7. Start FTP/Stop FTP/Stop Logfile Upload . . . . . . . . . . . . . . . . . . . . 87
7.8. Connect/Disconnect GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.9. Start/Stop Command Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.10. Pocket Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8. The Pocket Menu 89

8.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9. Cell Control Menu 91

9.1. Icons Used for Cell Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
9.2. Lock to RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
9.3. Lock Cell WCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
9.4. Lock ARFCN GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.5. Lock Band WCDMA, Lock Band GSM . . . . . . . . . . . . . . . . . . . . . . 93
9.6. Interplay between Locking Functions . . . . . . . . . . . . . . . . . . . . . . . 94
9.7. Comparison with Locking Functions in TEMS Investigation . . . . . . 94
9.8. Voice Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.9. HS Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.10. Ignore Cell Barred. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.11. Reset Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
iv
Contents
10. Events Menu 97

10.1. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
10.1.1. Viewing the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
10.1.2. Clearing the Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
10.1.3. Enabling/Disabling Event Logging and Sound . . . . . . . . . . 98
10.1.4. Shortcuts to Event Settings and Event Counters . . . . . . . . 99
10.2. Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
10.2.1. Viewing Event Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
10.2.2. Modifying Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . 100
10.3. Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10.3.1. Viewing Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10.3.2. Resetting Event Counters . . . . . . . . . . . . . . . . . . . . . . . . 102
10.4. Event Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
10.5. List of Logged Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.5.1. CC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.5.2. MM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
10.5.3. SM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
10.5.4. GMM Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.5.5. IRAT Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
10.5.6. RR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
10.5.7. RRC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.5.8. Session Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
11. Data Views Menu 112
12. GPS Menu 113

12.1. Using GPS Units with TEMS Pocket: Introduction . . . . . . . . . . . 113
12.1.1. Using the Built-in GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
12.1.2. Using an External GPS . . . . . . . . . . . . . . . . . . . . . . . . . . 114
12.2. GPS Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
12.3. GPS Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
12.4. GPS Time Synch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
13. FTP Menu 117

13.1. FTP Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
13.2. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
LZT 138 0240 R2A v

14. Logfile Menu 121

14.1. Logfiles in TEMS Pocket: Introduction . . . . . . . . . . . . . . . . . . . . 121
14.1.1. Logfile Naming Format. . . . . . . . . . . . . . . . . . . . . . . . . . . 122
14.1.1.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
14.2. Save Logfile To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
14.3. Upload Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
14.3.1. Conflicts with Other TEMS Pocket Functions . . . . . . . . . 124
14.3.2. Setting an Upload Schedule . . . . . . . . . . . . . . . . . . . . . . 125
14.4. WiFi Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
14.4.1. Relation to Upload over Cellular Network . . . . . . . . . . . . 128
14.4.2. Conflicts with Other TEMS Pocket Functions . . . . . . . . . 128
14.5. Compress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
14.6. FTP Resume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
14.7. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
15. Command Sequence Menu 131

15.1. Introduction to Command Sequences. . . . . . . . . . . . . . . . . . . . . 131
15.2. Defining Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 132
15.2.1. Global Command Sequence Settings . . . . . . . . . . . . . . . 132
15.2.2. Adding an Action to a Command Sequence ....... 134
15.2.3. Voice Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
15.2.4. Video Action Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
15.2.5. FTP Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
15.2.6. HTTP Action Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
15.2.7. Streaming Action Settings . . . . . . . . . . . . . . . . . . . . . . . . 138
15.2.8. Idle Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
15.2.9. Pre-guard and Post-guard Periods . . . . . . . . . . . . . . . . . 139
15.2.10. Saving Default Settings for an Action Type . . . . . . . . . . 139
15.2.11. The Assembled Command Sequence . . . . . . . . . . . . . . 139
15.2.12. Rearranging Actions in a Command Sequence. . . . . . . 139
15.2.13. Deleting an Action from a Command Sequence . . . . . . 140
15.3. Viewing and Editing Command Sequences . . . . . . . . . . . . . . . . 140
15.4. Deleting Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 140
15.5. Running Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 140
16. Passive Measurement Menu 141

16.1. Passive Measurement Action Settings . . . . . . . . . . . . . . . . . . . . 142
16.2. Prioritization of Passive Measurements . . . . . . . . . . . . . . . . . . . 143
vi
Contents
16.3. Notes on Message Buffering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

16.3.1. Pre-guard Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
16.3.2. Post-guard Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
17. Tools Menu 145

17.1. About Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
17.2. Quick Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
17.3. Import Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
17.3.1. Importing Settings Files from TEMS Pocket Versions
Older than 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
17.4. Export Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
17.4.1. Managing Export Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
17.5. Import Cell File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
18. General Settings Menu 151

18.1. WAP Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
18.2. Data View Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
18.3. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
18.4. Backlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
18.5. Cell Id Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
18.6. Cell Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
18.7. Power Display (GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
18.8. Measure Mode Display (GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . 154
18.9. Auto Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
18.10. WCDMA Cell Id Q-val . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
18.11. Reset All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
19. Scanning 156

19.1. Introduction to Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
19.2. How to Enter Scan Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
19.3. Setting Up a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
19.3.1. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
19.3.2. Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
19.3.2.1. GSM Scanning Methods . . . . . . . . . . . . . . . . . . . . 157
19.3.2.2. WCDMA Scanning Methods . . . . . . . . . . . . . . . . . 158
19.3.3. Edit Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
19.3.4. Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
19.3.4.1. Advanced GSM Settings . . . . . . . . . . . . . . . . . . . . 159
LZT 138 0240 R2A vii

19.3.4.2. Advanced WCDMA Settings . . . . . . . . . . . . . . . 159

19.3.5. Notes on Changing the Scan Setup. . . . . . . . . . . . . . . . . 160
19.4. Starting and Stopping a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
19.5. Other TEMS Pocket Functionality Available in Scan Mode . . . . 160
19.5.1. Using a GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
19.5.2. Recording Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
19.6. Scan Presentation: Scanner View (No. 1.1) . . . . . . . . . . . . . . . . 161
19.6.1. GSM Scanning Presentation . . . . . . . . . . . . . . . . . . . . . . 163
19.6.1.1. Whole-band Scan . . . . . . . . . . . . . . . . . . . . . . . . . 163
19.6.1.2. Custom List Scan . . . . . . . . . . . . . . . . . . . . . . . . . 164
19.6.2. WCDMA Scanning Presentation . . . . . . . . . . . . . . . . . . . 164
19.6.2.1. Network (Whole-band) Scan . . . . . . . . . . . . . . . . . 164
19.6.2.2. CPICH (Custom List) Scan . . . . . . . . . . . . . . . . . . 165
19.6.3. Freezing the Scanner View . . . . . . . . . . . . . . . . . . . . . . . 166
19.7. GPS View (No. 1.2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
19.8. The Built-in Help Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
19.9. The Capture Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
20. Uploading TEMS Pocket Logfiles from the

Phone File System 168
21. Battery Charging Considerations 170

21.1. Choice of Phone Charger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
21.2. Using the Phone’s Built-in GPS . . . . . . . . . . . . . . . . . . . . . . . . . 170
21.3. Using a TEMS Pocket Command Sequence . . . . . . . . . . . . . . . 170
22. Support Contact Information 172
Appendix A. Parameter Values 173

A.1. Activate PDP Context Failure Cause . . . . . . . . . . . . . . . . . . . . . . 173
A.2. Automatic Upload Failure Cause . . . . . . . . . . . . . . . . . . . . . . . . . 173
A.3. CC Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
A.4. CCCH Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
A.5. Channel Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
A.6. Deactivate PDP Context Cause . . . . . . . . . . . . . . . . . . . . . . . . . . 176
A.7. GMM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
A.8. GPRS Network Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . 177
viii
Contents
A.9. GPS Fix Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

A.10. MM Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
A.11. PDP Context Request Parameters . . . . . . . . . . . . . . . . . . . . . . . 178
A.11.1. Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
A.11.2. Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
A.11.3. Peak Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
A.11.4. Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
A.11.5. Mean Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
A.12. Routing Area Update Failure Cause . . . . . . . . . . . . . . . . . . . . . . 180
A.13. RR Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
A.14. RR Internal Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
A.15. RRC Failure Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
A.16. RRC Protocol Error Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
A.17. SM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Appendix B. Graphic Representation of

Parameter Values 184
B.1. C/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
B.2. Ec/N0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
B.3. FER, RLC/LLC BLER/Retransmissions . . . . . . . . . . . . . . . . . . . . 185
B.4. RLC DL/UL Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
B.5. RxLev, RSCP, RSSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
B.6. RxQual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
B.7. Tx Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Appendix C. Icons Used in TEMS Pocket 187
Appendix D. Default Settings in TEMS Pocket

Menus 189
D.1. Activity Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
D.1.1. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
D.1.2. Scanner Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
D.1.2.1. GSM Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
D.1.2.2. WCDMA Scanning . . . . . . . . . . . . . . . . . . . . . . . . . 189
D.2. Pocket Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
D.2.1. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
D.2.2. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
LZT 138 0240 R2A ix

D.2.3. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

D.2.4. GPS Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
D.2.5. FTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
D.2.6. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
D.2.7. Command Sequence Menu. . . . . . . . . . . . . . . . . . . . . . . . 191
D.2.8. Passive Measurement Menu. . . . . . . . . . . . . . . . . . . . . . . 192
D.2.9. Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
D.2.10. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Appendix E. Cell File Format 194
Index 197
x
Chapter 1. Introduction
1. Introduction
Welcome to TEMS Pocket.

TEMS Pocket is an advanced cellular network diagnostics tool built into a
mobile phone. TEMS Pocket is suitable for day-to-day verification,
maintenance and troubleshooting of cellular networks but is also handy for
many cell planning tasks.
This document describes TEMS Pocket 7.3 (product packages Professional
and Premium) as implemented in the Sony Ericsson W995 and W995a
phones which support both GSM and WCDMA. A separate manual is
provided for the GSM-only Sony Ericsson W995 EDGE phone.
1.1. What’s New in TEMS Pocket 7.3

TEMS Pocket 7.3 is based on the same Sony Ericsson handsets as TEMS
Pocket 7.2 (W995/W995a/W995 EDGE) and is available as an upgrade for
TEMS Pocket 7.2 users.
1.1.1. Presentation of Cell Names

In TEMS Pocket 7.3 it is possible to present cells by name in the realtime
data views. The cell names are retrieved from an XML-format cell file that the
user imports into the TEMS Pocket application; the cell presentation can then
be toggled between cell name and CGI. Two new data views listing cells by
name (one for GSM and one for WCDMA) are also introduced in order to
further amplify the overview of the network structure.
1.1.2. Event-based Logfile Sifting

This feature allows the user to set up criteria for what logfiles will be saved
during passive monitoring of user sessions, or when a command sequence is
running. For example, the user can choose to save only logfiles containing a
failure event. Storing logfiles more selectively like this allows users to focus
their analysis precisely on the data that is most relevant in the context.
LZT 138 0240 R2A 1

1.1.3. Improved Logfile Naming

The naming of logfiles recorded by TEMS Pocket has been made more
structured and elaborate, simplifying and speeding up analysis of the files.
The logfile name now indicates:
• Occurrence of failure event (if any)
• Type of measurement
• Manually added tag (if any)
• Date and time
1.1.4. Coexistence with MRU (Mobile Receiving Unit)

TEMS Pocket 7.3 can reside on a TEMS Investigation phone which also has
MRU (Mobile Receiving Unit) software installed. This has previously not been
possible.
The MRU acts as a receiver when performing voice quality (PESQ)
measurements with TEMS Investigation or TEMS Automatic. With TEMS
Pocket installed on the same device, it is possible to use TEMS Pocket
features such as lock on cell and passive voice measurement while the
device is functioning as an MRU.
1.2. What Was New in TEMS Pocket 7.2
1.2.1. New UMTS Phones: Sony Ericsson W995/W995a

TEMS Pocket 7.2 is implemented on the Sony Ericsson W995 and W995a
phones. They are the first Sony Ericsson phones that officially support
HSUPA (EUL). Some further key features of these devices are:
• GSM/GPRS quad-band (850/900/1800/1900 MHz)
• WCDMA/HSPA 7.2 Mbit/s DL, 2 Mbit/s UL
– W995: 900/2100 MHz
– W995a: 850/1900/2100 MHz
• 8.1 megapixel camera
• Integrated GPS
2
1.2.2. New GSM Phone: Sony Ericsson W995 EDGE

TEMS Pocket 7.2 is also available on the GSM-only version of the W995
phone, which is called Sony Ericsson W995 EDGE. Key features are:
• GSM/GPRS quad-band (850/900/1800/1900 MHz)
• EDGE Class 10
1.2.3. Scanning (GSM and WCDMA)

TEMS Pocket 7.2 introduced the capability of scanning GSM and WCDMA
networks.
Supported bands are as follows:
• Sony Ericsson W995: GSM 850/900/1800/1900; WCDMA 900/2100
• Sony Ericsson W995a: GSM 850/900/1800/1900; WCDMA 850/1900/
2100
• Sony Ericsson W995 EDGE: GSM 850/900/1800/1900
For GSM, RSSI scanning is done either across an entire band or of a user-
selected set of up to 200 ARFCNs. The ARFCNs can be picked from arbitrary
bands. BSIC decoding helps identify the signal source.
For WCDMA, two scanning modes are provided: network scan and CPICH
scan.
• In network scan mode, TEMS Pocket will scan a user-selected band for
UARFCNs where a CPICH can be decoded. The main purpose of this
scan mode is to detect network presence; UARFCNs found by the
network scan can be added to the CPICH scan list.
• In CPICH scan mode, the current top ten CPICHs are presented from
each scanned UARFCN. Up to 12 UARFCNs can be scanned.
The scan presentation has been carefully designed to provide a
comprehensive view of all scanned channels, ensuring that no significant
signals are overlooked, while also allowing close-up inspection of individual
channels.
1.2.4. Command Sequence Enhancements

The command sequence function was greatly expanded and enhanced in this
release. New features were:
LZT 138 0240 R2A 3

• Actions for HTTP, streaming, and idle mode. Regarding streaming, see
section 1.2.5 below.
• Multiple actions (up to 10) can be strung together in one command
sequence.
• Multiple command sequences (up to 10) can be defined.
• Default settings for each action type can be saved; new actions are
initialized with these defaults.
• Actions contain an option for applying control functions while the action is
executed, for instance locking on a band and/or cell.
• Logfile recording can be set on or off for each command sequence.
• For voice and video calls, a redial option can be activated which causes
any dropped or blocked calls to be redialed automatically.
• Logfile upload can be done after each loop through a command
sequence.
• A new data view is provided which presents the current status of a
command sequence that is being executed. The information given
includes the expected remaining duration of current action and the next
action to follow.
• All command sequence settings can be exported to file and imported.
1.2.5. Streaming
TEMS Pocket 7.2 can test video streaming over the RTSP protocol by means
of the phone’s integrated media player. Data can be streamed from a user-
defined URL through an access point that is likewise user-configurable. The
media presentation can be customized in various respects (hide/show video;
audio on/off). A new command sequence action is provided for streaming; it
lets the user put a cap on the duration of the streaming session.
Streaming performance data is displayed in the TEMS Pocket data views just
as for previously supported services such as FTP.
1.2.6. Passive Measurement

Automatic recording of logfiles was renamed “passive measurement”. This
kind of measurement is configured separately for each service type (voice,
FTP, and so on). For HTTP and streaming, a privacy option is provided which
suppresses recording of what URLs are visited.
4
1.2.7. New GPS

The GPS that could optionally be ordered with TEMS Pocket 7.2 is the
GlobalSat BT-359.
1.2.8. Data Upload over WiFi

Data upload can alternatively be done over WiFi whenever a WiFi access
point is available.
The TEMS Pocket phone is capable of searching for available WiFi networks,
and the user can select any WiFi bearer thus detected for uploading TEMS
Pocket data to an FTP server.
1.2.9. HSPA Data View

The HSDPA Data view has been expanded with HSUPA-specific information
and renamed “HSPA Data”. Among this information may be noted average E-
TFCI, average Serving Grant Index, average transport block size, and UE
happy rate.
1.2.10. WCDMA AMR Data View

A new data view (“WCDMA AMR”) has been created for showing AMR
speech codec usage in WCDMA. Both AMR-NB (narrowband) and AMR-WB
(wideband) appear in the view, which is broadly similar to the GSM AMR data
view already present.
1.3. What Was New in TEMS Pocket 7.0

(TEMS Pocket 7.1 is a Nokia-based release.)
1.3.1. Phones: Sony Ericsson C905, C905a

TEMS Pocket 7.0 is implemented on the Sony Ericsson C905 and C905a
phones. Their features include:
• GSM/GPRS quad-band
• HSDPA/WCDMA 2100 MHz (C905); 850/1900/2100 MHz (C905a)
• HSDPA 7.2 Mbit/s on downlink
LZT 138 0240 R2A 5

• 8.1 megapixel camera

• Integrated GPS
1.3.2. Map View and Pinpointing

The map view was the principal new feature in TEMS Pocket 7.0. It allows
users to pinpoint their route through a building on a floor plan. The setup is
fast and easy:
• Obtain an image of the floor plan. For example, use the camera in the
TEMS Pocket phone to take a photo of the emergency/evacuation plan
displayed in the building.
• Load the picture as a background image in the Map view.
• Start pinpointing your position in the building. A logfile will be opened
automatically. Pinpoint at regular intervals along the route and whenever
you change direction.
• When you are done with the measurement, give a “Stop pinpointing”
command. The logfile will close.
This is the full list of steps required to use the TEMS Pocket Map view. No
messy or time-consuming preparations have been left out: none are needed.
Before post-processing the data, it just needs to be anchored to a
geographical position. This is accomplished in a tick with a software utility
accompanying TEMS Pocket. The logfiles are then ready to be loaded into
TEMS Presentation or TEMS Investigation.
The map functionality is available as an option in the Professional package.
1.3.3. Data Views with Graphs

TEMS Pocket 7.0 comes equipped with a set of graph views showing how
radio parameters vary over time. These line charts were an entirely new
feature in TEMS Pocket 7.0, but they are similar to the ones found in TEMS
Investigation and TEMS Presentation. All graphs come predefined and ready
to use without any need for configuration.
1.3.4. Smarter Logfile Upload

The data upload process was improved: If the FTP connection goes down,
the upload of a logfile can optionally be resumed from where it was
6
interrupted instead of being restarted from the beginning. The new procedure
cuts upload times and saves phone battery life, enhancing the efficiency and
power of the tool.
1.3.5. Cell Id Presentation

Cell Identity data is presented in both idle and dedicated/connected mode for
both GSM and WCDMA. This is achieved by buffering Cell Identities in idle
mode and then correlating the buffered data with the phone’s position in
dedicated/connected mode. The buffer is cleared when the phone is
restarted.
1.3.6. Snapshots of Data Views

A display snapshot function was added which enables you to capture TEMS
Pocket data views in the form of bitmap images. The snapshot function is
perfect for instantly capturing your own user’s view of the network. It can also
be used to produce receipts handed in by staff to confirm completion of field
measurement tasks. This too contributes to efficiency and reduces traveling
expenses.
1.3.7. Importing and Exporting TEMS Pocket Settings

More aspects of user configuration in TEMS Pocket can be saved to file:
command sequence setups, user-configured map views, and more. Each
setup is saved in a separate file which can be imported into the application on
a later occasion. This functionality permits convenient distribution of test
setups to multiple TEMS Pocket units.
LZT 138 0240 R2A 7

2. Overview of TEMS Pocket
2.1. Phone Mode vs. Scan Mode

TEMS Pocket has two main working modes.
• Phone mode: The TEMS Pocket device acts as a regular phone, and
measurement data is collected relating to GSM and WCDMA networks
and to voice and data services in which the phone engages.
• Scan mode: The TEMS Pocket device acts as a scanner capable of
detecting GSM and WCDMA signals and decoding BSICs/CPICH
scrambling codes.
You select working mode in the Activity menu under Operational mode. See
section 7.1.
The scanning functionality is dealt with in chapter 19. Everything else in this
manual applies to phone mode, or is common to both modes. Chapter 19
explains what functions the two modes share, giving references to other parts
of the manual where appropriate.
2.2. Data Views

Most of the data displayed by TEMS Pocket is to be found in data views.
When you turn the phone on for the first time, it will display the W/G Cells
data view:
8
Chapter 2. Overview of TEMS Pocket
On later occasions, when turned on, the phone will display the data view last
inspected, provided that the TEMS Pocket operational mode is set to Active
(see section 7.1).
The data views are divided into categories from 1 to 5. Each data view is
numbered according to the format “x.y”, where “x” is the category and “y” the
position of the data view within that category. You browse the categories by
moving the navigation key left and right, and the data views within a category
by moving the navigation key up and down. TEMS Pocket remembers the
view last displayed in each category; when you return to a category, that view
is shown.
The top section of the display preserves the ordinary signal strength and
battery power level indicators as well as other symbols belonging to the
regular user interface of the phone. Among the latter are:
A “3G” symbol indicating that the phone’s current serving cell supports
WCDMA R99 (but not HSDPA).
An “H” symbol indicating that the current serving cell supports HSDPA.
The top section of the display also shows various icons related to TEMS
Pocket operation. They include:
• an icon indicating that a logfile is being recorded (see section 7.3)
• an icon indicating that a logfile is being replayed, and the status of the
replay (see section 7.4.2)
• an icon indicating that a cell control function is currently applied (see
section 9)
• an icon for the latest TEMS Pocket event that occurred (if it occurred
within the last 15 minutes; see section 10.4).
If the default phone display with the operator name appears instead of a
TEMS Pocket data view, this is because TEMS Pocket has been put in
background or inactive mode (see section 7.1). By default TEMS Pocket is in
active mode, and all of its data views are visible.
The data views are exhaustively described in chapter 3.
2.2.1. Data Views with Graphs

Data views with graphs combine text-format content (similar to that of
ordinary data views) with a line chart showing how one or several parameters
LZT 138 0240 R2A 9

vary over time. Like the text-only data views, the graph views are predefined.
They are collected in category 5.
The top section of the display has precisely the same layout and behavior as
in text-only data views. See section 2.2.
2.3. Map View

The Map view (no. 1.7) is used for pinpointing a test route on a floor plan or
other map image. See section 2.6.3.
2.4. Menus
When you press the Activity key on the phone, a tab with TEMS Pocket
commands appears on top in the Activity menu:
10
Most of the commands in this menu are found only here. The menu is gone
through in chapter 7.
From the Activity menu you can also access the Pocket menu, which is the
chief means of configuring TEMS Pocket: see chapter 8. The Pocket menu
can alternatively be accessed from the phone’s main menu: Settings →
General → Pocket menu.
Note: TEMS Pocket settings are always saved in the phone’s internal
memory. If the phone memory is full, TEMS Pocket settings can
no longer be saved. You then need to remove some files to free
up memory.
2.5. 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 Pocket menu. See section
10.1. A shortcut to the event log is found in the Activity menu.
2.6. Logfiles
2.6.1. Logfile Recording

You can record data collected by TEMS Pocket in logfiles and replay these
files in TEMS Pocket itself or in TEMS Investigation or TEMS Presentation.
See sections 7.3–7.4 and chapter 14.
LZT 138 0240 R2A 11

2.6.2. GPS Positioning

TEMS Pocket supports positioning of data using GPS. You can use either the
phone’s internal GPS or an external GPS unit that has been Bluetooth paired
with the phone. See chapter 12.
2.6.3. Positioning by Pinpointing

In an indoor environment or other location without GPS coverage, you can
use the Map view (see section 2.3) to pinpoint your test route. You load an
image of your testing area into the Map view, then indicate your route by
marking waypoints on that map. The map image can also be assigned a
geographical position. For the full details on these procedures, see chapter 6.
2.7. Cell Control Functions

TEMS Pocket has a number of cell control functions for controlling the
phone’s behavior in the cellular network. These include locking the phone to a
RAT, band, cell, or channel. See chapter 9 for full details.
2.8. Command Sequences

TEMS Pocket offers the use of command sequences for automated testing of
various services. See chapter 15.
2.9. Scan Mode

See section 2.1 above and chapter 19.
2.10. Storage Medium: Phone Memory vs. Memory

Stick
In general it is recommendable to use a memory stick rather than the phone’s
internal memory as storage medium (for logfiles, FTP downloads, etc.). This
is because the internal memory of the Sony Ericsson W995 and W995a is
fairly small. The memory stick is the default choice in all dialogs where a
storage medium needs to be selected.
12
2.11. Language Support

TEMS Pocket Sony Ericsson W995 and W995a phones support languages
as follows:
• Regular phone user interface: Arabic, Chinese (Mandarin, simplified
characters), Danish, English, French, Norwegian, Spanish, Swedish
• Pocket user interface
– Text display: English
– User input: English
2.12. Turning TEMS Pocket Off

You turn TEMS Pocket on and off by entering the Activity menu and changing
the operational mode: see section 7.1.
LZT 138 0240 R2A 13

3. Data Views: General
3.1. General Data View Properties

The data views in category 1 (numbered “1.x”) are capable of showing both
WCDMA and GSM data. Both will appear simultaneously if the phone is
making inter-RAT neighbor measurements.
The data views in category 2 chiefly contain WCDMA-specific data, and those
in category 3 and 4 chiefly contain GSM- and GPRS/EGPRS-specific data.
The data views in category 5 all include a graph. WCDMA-only, GSM-only,
and combined views are found in this category.
All data views have the same general structure in idle mode and dedicated/
active mode.
Whenever a parameter is currently not valid, this is indicated in the data view
by a dash “–” or a string of dashes.
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. These parameters are tagged “numeric/graphic” in
chapters 4 and 5. The rules for the graphic presentation are found in
appendix B, page 184.
In the case of frequency hopping, the hopping list is shown one channel at a
time, a new channel appearing every second.
3.2. The Built-in Help Function

If you press Options and select “Toggle help”, a callout box appears
describing the piece of data in the top left corner of the screen. Use the
navigation key to navigate the contents of the data view.
14
Chapter 3. Data Views: General
Help not displayed Help displayed
• To turn off the help function, press the C key. Alternatively, press Options
and choose Toggle help again.
3.3. The Capture Function

You can take screenshots of any data view. To do this, you must first turn the
screen capture function on (while in a data view) by selecting Options →
Toggle capture.
Whenever the phone is in standby mode or during a voice call, you can now
take a screenshot by pressing the Capture button. Please note that
screenshots are always stored on the memory card (under Other\Pocket\
Capture), so the phone must have one inserted.
A shutter sound is played when the screenshot is taken. Image files are
named DV<X>-<Y>_<N>.bmp, where <X>-<Y> represent the data view
number and <N> is a counter starting at 1. Up to 1000 screenshots of each
data view can be stored.
3.4. Other Data View Actions

In some data views you can perform an action relating to a piece of data
shown in the view. For example, in data views listing cells, you can lock on
one of the cells.
All data view actions are performed by pressing the Options button and
choosing Data view actions. A submenu appears listing the available actions.
LZT 138 0240 R2A 15

Specifics on data view actions are found in the subsequent sections.
16
3.5. Survey of Data Views
No. View Name Description Page
1.1 W/G Cells Combines the WCDMA Cells (2.1) and 21

GSM Cells (3.1) views into a dual
mode view.
1.2 PDP Context Displays PDP addresses and PDP 25

context settings for each address,
including NSAPI and APN.
1.3 MM/GMM Displays identities common to 26

WCDMA and GSM, such as TMSI,
P-TMSI, and CGI of last registered
network.
1.4 Time Log Displays time spent by the phone in 27

various states (MM states; idle/
dedicated).
1.5 FTP Data Displays information on the current 28

FTP session, such as FTP server
address, throughput, and transferred
byte count.
1.6 GPS Displays essential GPS data: latitude 30

and longitude, altitude and speed,
number of satellites, fix quality, time
and date.
1.7 Map Not a data view (but has a number). 78

See chapter 6.
1.8 Progress Displays the progress of a command 31

sequence that is being executed.
2.1 WCDMA Cells Displays UARFCN, cell status, 33

scrambling code, RSCP, Ec/N0, and
path loss for each cell in active set and
monitored/detected neighbor sets.
LZT 138 0240 R2A 17

2.2 WCDMA Cell Id Displays UARFCN, scrambling code, 34

CI, and RSCP for each cell in the
active set and monitored/detected
neighbor sets.
2.3 WCDMA C. Displays UARFCN, scrambling code, 35

Name CI, and cell name for each cell in the
active set and monitored/detected
neighbor sets.
2.4 WCDMA Serv. Displays various items from System 36

Cell Information messages.
2.5 WCDMA Displays SIR and SIR target, power 38

Channel control information, RRC state, and
information on transport channels
used.
2.6 WCDMA AMR Displays SIR and SIR target, power 39

control information, RRC state, AMR
codecs selected on uplink and
downlink, and statistics on AMR codec
utilization.
2.7 WCDMA Data Displays SIR and SIR target, power 40

control information, RRC state, and
information on uplink and downlink
RLC and transport channel
performance.
2.8 HSPA Data Displays HSDPA CQI, requested and 42

actual block sizes, data transfer rate,
and block error rates. Also displays
HSUPA E-TFCI, SGI, TBS, DTX rate,
happy rate, and retransmission rate.
– WCDMA WAP Displays a subset of the WCDMA Data 61

browser view view (2.7) during WAP browsing.
18
3.1 GSM Cells Displays ARFCN, BSIC, RxLev, C1/ 45

C31, and C2/C32 for the serving cell
and each neighbor. Also presents
system information data for cell
access, selection, and location.
3.2 GSM Cell Id Displays ARFCN, LAC, CI, and RxLev 47

for the serving cell and each neighbor.
Also presents system information data
for cell access, selection, and location.
3.3 GSM Cell Name Displays ARFCN, BSIC, CI, and cell 48
name for the serving cell and each
neighbor.
3.4 GSM BA List Displays the GSM BA neighbor list as 49

received from the network and shows
which BCCH ARFCN the list was
received from.
4.1 GSM Serving Displays system information data on 50

Cell serving cell depending on mode (idle/
connected). Note: TMSI, P-TMSI, and
TLLI are not found here but in the MM/
GMM data view (1.3).
4.2 GPRS Data Displays traffic channel ARFCN, 53

timeslots and coding schemes used,
and LLC and RLC/MAC performance
on uplink and downlink.
4.3 GPRS Info Displays traffic channel ARFCN, 56

timeslots and coding schemes used,
and vital GPRS/EGPRS configuration
parameters.
4.4 GSM C/I Info Displays C/I information for the most 57
frequently utilized timeslot on each
traffic channel in use.
LZT 138 0240 R2A 19

4.5 GSM AMR Displays GSM logical channel 58

information, AMR codecs selected on
uplink and downlink, and statistics on
AMR codec utilization.
– GPRS WAP Displays a subset of the GPRS Data 63

browser view view (4.2) during WAP browsing.
5.1 W/G Serving Graph displays WCDMA serving cell 66

RSSI RSCP/GSM serving cell RxLev.
5.2 W/G Cells Graph displays WCDMA serving cell 68

RSCP/GSM serving cell RxLev; ditto
for three strongest WCDMA/GSM
neighbors.
5.3 W/G Data Graph displays WCDMA transport 70

channel and GSM RLC/MAC data
transfer rates.
5.4 WCDMA Graph displays WCDMA serving cell 71

Serving RSCP and UTRA Carrier RSSI.
5.5 WCDMA SIR Graph displays SIR Target and actual 72

SIR.
5.6 WCDMA Cells Graph displays RSCP for serving cell 73

and three strongest neighbors.
5.7 GSM Cells Graph displays RxLev for serving cell 74

and three strongest neighbors.
5.8 GSM Data Graph displays RLC/MAC data transfer 76

rate.
Regarding the views shown in scan mode, see chapter 19.
20
Chapter 4. Data Views in Text Format
4. Data Views in Text Format
4.1. W/G Cells (View No. 1.1)

Lines 1–4 show WCDMA cells and are thus
primarily used in WCDMA mode. However, when
WCDMA neighbors are measured in GSM mode,
these neighbors also appear here. Note that if you
have locked the phone to GSM (Lock to RAT
function, section 9.2), no WCDMA neighbors will
ever be measured.
W: WCDMA cell type: One of
• S: Serving cell
• A: Active set member
Screenshot • M: Monitored neighbor
• D: Detected neighbor
• – (with values on the rest of the line): Inter-RAT,
WCDMA neighbor measured in GSM mode
UARFC: UARFCN, UMTS Absolute Radio
Frequency Channel Number
SC: Scrambling Code
RSCP: Received Signal Code Power (dBm),
numeric/graphic
Ec/No: Ec/N0 (dB), numeric/graphic
Key (used for
convenience in the PL: Pathloss (dB); this measurement appears only
manual; not shown in when ordered by the network
this format in the
phone display)
LZT 138 0240 R2A 21

Lines 5–8 show GSM cells and are thus primarily

used in GSM mode. If GSM neighbors are measured
while in WCDMA mode, these neighbors also appear
here. Note that if you have locked the phone to
WCDMA (Lock to RAT function, section 9.2), no
GSM neighbors will ever be measured.
Line 5: GSM serving cell
Lines 6–8: Three strongest GSM neighbors
G: GSM channel type for serving cell: One of
Screenshot (footer • B: BCCH; P: PBCCH, p: Hopping PBCCH
with CGI) • S: SDCCH, s: Hopping SDCCH
• T: TCH, t: Hopping TCH
• D: PDTCH, d: Hopping PDTCH
GSM neighbor measured in WCDMA mode
Screenshot (footer
with cell name) ARFC: ARFCN, Absolute Radio Frequency
Channel Number
BS: BSIC, Base Station Identity Code
RxLev: Received Signal Strength (unit user-
configurable: see section 18.7), numeric/graphic
Lines 9–10 are used in both WCDMA and GSM

mode, showing data on the network that the phone is
currently using. The information shown in WCDMA
and GSM mode is partly different, as detailed below.
This data is repeated in many other data views.
Key (footer with CGI) Line 9
C: Current RAT {G: GSM, W: WCDMA, –: No
service}
(U)ARFC: WCDMA: Serving cell UARFCN; GSM:
Key (footer with cell Serving cell BCCH ARFCN
name)
B: WCDMA: Serving cell Scrambling Code; GSM:
Serving cell BSIC
RSS: Received signal strength, equal to UTRA
Carrier RSSI for WCDMA and RxLev for GSM;
numeric/graphic
RAC: Serving cell Routing Area Code
22
Line 10
This line identifies the serving cell, either by means
of CGI or by cell name as defined in an imported
XML cell file. The choice of presentation mode is
made in the Pocket menu under General settings;
see section 18.6, page 153. Cell file import is done
under Pocket menu → Tools; see section 17.5, page
150.
In all data views that follow, the view footer uses the
Screenshot (footer CGI mode of presentation; but cell names can
with CGI) alternatively be displayed in any data view that has a
footer.
MCC: Serving cell Mobile Country Code
MNC: Serving cell Mobile Network Code
Screenshot (footer LAC: Serving cell Location Area Code
with cell name)
RNC: Serving cell Radio Network Controller ID
(WCDMA only; Cell Identity for WCDMA = RNC + CI)
CI: Serving cell Cell Identity, 16 bits (= C-Id: see
3GPP 25.401, section 6.1.5)
Cell Name: Name of cell, taken from XML file; see
section 17.5.
Key (footer with CGI)
Key (footer with cell

name)
LZT 138 0240 R2A 23

4.1.1. Data View Actions

• You can lock on a cell or (in WCDMA mode) a
UARFCN that is listed in the data view.
• Choose the cell or UARFCN to lock on by

moving the red frame, using the navigation key.
When you have navigated to the desired item,
press Select.
• To unlock, enter the Data view actions menu

again and give the appropriate Unlock
command.
24
4.2. PDP Context (View No. 1.2)

Lines 1–6 show data on the active PDP contexts
(up to three) and the contents of the PDP context
request.
PDP Address: IPv4 PDP address (12-digit
number). See 3GPP 24.008, sec. 10.5.6.4.
NSAPI: Network Service Access Point Identifier.
See 3GPP 24.008, sec. 10.5.6.2.
D: Delay Class {0 ... 4}
R: Reliability Class {0 ... 5}
Screenshot
K: Peak Throughput {0 ... 9}
P: Precedence Class {0 ... 3}
MT: Mean Throughput {0 ... 18, 31}
(For the meanings of values, see appendix A.11.)
APN: Access Point Name (shown as scrolling text)
Lines 7–8 are the same as the two bottom lines in

the W/G Cells view: see section 4.1.
Key
There are no actions associated with this data view.
LZT 138 0240 R2A 25

4.3. MM/GMM (View No. 1.3)

Lines 1–4 show data related to Mobility
Management/GPRS Mobility Management.
TMSI: Temporary Mobile Subscriber Identity (hex)
T3212C: T3212, current time between location
updates {Off, 0 ... 1530 minutes}. See 3GPP
24.008.
T3212M: T3212, max time between location
updates (= start value) {Off, 0 ... 1530 minutes}
PTMSI: Packet TMSI (hex)
Screenshot
GMM: GMM Attached {A: Attached, –: Not
attached}
TLLI: Temporary Logical Link Identifier (hex)
The following four parameters are updated each

time the phone performs a Location Area Update or
Routing Area Update.
RMCC: Registered MCC
RMNC: Registered MNC
Key RLAC: Registered LAC
RRAC: Registered RAC

26
4.4. Time Log (View No. 1.4)

This view shows the time (in hours, minutes, and
seconds) that the phone has spent in various
states since the latest occurrence of one of the
following:
• Phone power-on
• Entering replay mode
• Exiting replay mode
• Rewinding of logfile during replay
Screenshot MM
Home: Registered in Home PLMN
Equiv: Registered in Equivalent PLMN
Roam: Registered in Roaming PLMN
Unreg: Unregistered
(See 3GPP 21.905.)
GSM
TCH: Time using Traffic Channel (TCH)
PDCH: Time using Packet Data Channel (PDCH)
Idle: Time spent in Idle mode
WCDMA
DCH: Time using Dedicated Channel (DCH)
Idle: Time spent in Idle mode
No Service: Time spent in No Service mode (no

RAT found)

You can reset all counters in this view by choosing Reset time log.
LZT 138 0240 R2A 27

4.5. FTP Data (View No. 1.5)

Line 1
FTP Dir: FTP session type (UL or DL).
Line 2
FTP Address: IPv4 address (12-digit number) or
plain-text name of FTP server. Displayed as
scrolling text.
Line 3
Screenshot File Name: Name of file being downloaded/
uploaded over FTP. Displayed as scrolling text.
hh:mm:ss: Duration of current FTP session in
hours, minutes, and seconds.
Line 4
CThpDL: Current downlink application-level FTP
throughput in kbit/s or Mbit/s (based on the latest
report from the phone).
CThpUL: Current uplink application-level FTP
Key throughput in kbit/s or Mbit/s (based on the latest
report from the phone).
Line 5
MThpDL: Mean downlink application-level FTP
throughput in kbit/s or Mbit/s (calculated over the
whole of the file currently being transferred).a
MThpUL: Mean uplink application-level FTP
throughput in kbit/s or Mbit/s (calculated over the
whole of the file currently being transferred).a
a. Note that if the mean throughput calculation is to be correct, the file

transferred cannot be arbitrarily large; see section 13.1 for details.
28
Line 6
TotDataDL: Total bytes transferred on downlink
over FTP at the application level (B = bytes, K =
kilobytes, M = megabytes). This counter is reset at
the end of each file transfer.
TotDataUL: Total bytes transferred on uplink over
FTP at the application level (B = bytes, K =
kilobytes, M = megabytes). This counter is reset at
the end of each file transfer.
Screenshot
Key
Upon completion of each FTP file transfer, an FTP Transfer End event (see
section 10.5.8) is generated providing a summary of the file transfer and its
performance.
LZT 138 0240 R2A 29

4.6. GPS (View No. 1.6)

Lines 1–8 show GPS data.
Latitude: Latitude in degrees, minutes, and
decimal minutes.
Longitude: Longitude in degrees, minutes, and
decimal minutes.
Altitude: Height above sea level in meters.
Speed: Speed in km/h.
No. of satellites: The number of satellites seen by
Screenshot the GPS device.
Fix quality: Quality of GPS fix; see appendix A.9.
Time: Time of day, hh:mm:ss (UTC = GMT)
Date: Date, yy-mm-dd
No. of satellites and Fix quality will always be valid

as long as TEMS Pocket is connected to a GPS.

4.7. Map (View No. 1.7)

See chapter 6.
30
4.8. Progress (View No. 1.8)

This view shows the progress of a command
sequence or passive measurement that is being
executed. When a command sequence is stopped,
this view is cleared.
Line 1
MeasType: Type of measurement: either
command sequence or passive measurement
MeasName: Name of command sequence (if any)
Screenshot
Lines 2–5
Curr: Index of current action in sequence
Tot: Total number of actions in sequence
ActionName: Name of current action
TimeElaps: Time elapsed of current action,
including pre-guard time
TotalTime: Estimated total execution timea for
current action, incl. pre- and post-guards as well as
the user-set guard time; shown for passive mode if
Key the Duration parameter is set (see section 16.1)
ActionInfo: Indicates what phase of execution the
action is in.
For active measurements, the possible states are:
• Applying cell control: Configured cell control
settings are being applied.
• Executing action: The measurement is under
way (includes logfile pre- and post-guards).
• Guard time: Time to wait between actions or
after the last action.
• Releasing cell control: Cell control is being
released.
a. For voice, video, and idle actions this quantity is precisely known, since
the action run time is fixed. For streaming, FTP, and HTTP, only educated
guesses of varying quality can be made as to the total execution time.
LZT 138 0240 R2A 31

Lines 2–5 (continued)

ActionInfo (continued)
For passive measurements, the possible states
are:
• Measurement in progress: The passive
measurement is running.
• Guard time: Passive measurement post-guard
time.
Screenshot NextAction: Name of next action in command
sequence; invalid for passive measurement
Line 6
LogfileStatus: One of “Compressing”, “Uploading”
Curr: Index of logfile currently being processed
Tot: Total number of logfiles to be processed

Key
32
4.9. WCDMA Cells (View No. 2.1)

Up to eight cells from the WCDMA active set can
be shown.
Lines 1–8
• S: Serving cell
• M: Monitored neighbor
Screenshot WCDMA neighbor measured in GSM mode
UARFC: UARFCN
SC: Scrambling Code
numeric/graphic
PL: Pathloss (dB); this measurement appears only
when ordered by the network
Key Lines 9–10 are the same as the two bottom lines in

You can lock on a WCDMA cell or UARFCN that is listed in the view. The
procedures for locking and unlocking are the same as in the W/G Cells view;
see section 4.1.1.
LZT 138 0240 R2A 33

4.10. WCDMA Cell Id (View No. 2.2)

be shown.
Lines 1–8
• S: Serving cell
Screenshot WCDMA neighbor measured in GSM mode
UARFC: UARFCN
SC: Scrambling Code
A: (Lines 2–8) Location Area/Routing Area
properties compared to serving cell/strongest
active set member (found on line 1):
• =: Same LA/RA
• R: Same LA, different RA
• L: Different LA
• P: PLMN not matching
Key • –: Unknown
CI: Cell Identity, 16 bits (= C-Id: see 3GPP 25.401,
section 6.1.5)
numeric/graphic. You can have this replaced by
Ec/N0 by changing the setting “WCDMA CellId q-
val” in the Pocket menu under General settings;
see section 18.10.


see section 4.1.1.
34
4.11. WCDMA C. (Cell) Name (View No. 2.3)

be shown.
Lines 1–8
UARFC: UARFCN
SC: Scrambling Code
CI: Cell Identity, 16 bits (= C-Id: see 3GPP 25.401,
section 6.1.5)
Screenshot
section 17.5. If the cell name is too long to fit into
the column, point the help bubble at the cell name
to view the string in its entirety. See the image on
the left.

Key
Cell name
presentation in help
bubble

see section 4.1.1.
LZT 138 0240 R2A 35

4.12. WCDMA Serv. Cell (View No. 2.4)

Lines 1–2
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.
Qhy2s: Hysteresis Qhyst2s {0, 2, ..., 40} [dB]
SSR: Threshold Ssearch,RAT {–32, –30, ..., 20} [dB]
SHR: Threshold SHCS,RAT {–105, –103, ..., 91} [dB]
QqMin: Qqualmin, minimum required quality
Screenshot {–24 ... 0} [dB]
QrMin: Qrxlevmin, minimum required RxLev
{–115, –113, ..., –25} [dBm]
TRSs: Timer value Treselections {0 ... 31} [s]
MaxTxP: Maximum allowed UL TX power [dBm]
Line 3
CStat: WCDMA cell status: One of
• –: Not barred
• B: Barred
Key • 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
Lines 4–5
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
Pp-m: Power offset (“P p-m”) between the last
transmitted preamble and the control part of the
message {–5 ... 10} [dB]; see 3GPP 25.331, section
10.3.5.8
36
Lines 4–5 (continued)

Mmax: Maximum number of preamble cycles
{1 ... 32}; see 3GPP 25.331, section 10.3.6.67
BL: NB01min, lower bound for random back-off
{0 ... 50}; see 3GPP 25.331, section 10.3.6.67
BU: NB01max, upper bound for random back-off
{0 ... 50}; see 3GPP 25.331, section 10.3.6.67
Cons: Constant value [dB]; see 3GPP 25.331,
section 10.3.6.11
Screenshot
PTxP: Primary CPICH TX power {–10 ... 50} [dBm];
see 3GPP 25.331, section 10.3.6.61
ULInt: Uplink interference {–110 ... –70} [dBm]; see
3GPP 25.331, section 10.3.6.87
Regarding the following two parameters, see 3GPP
25.331, section 10.3.6.54 (“PRACH power offset”).
PwrRS: Power Ramp Step {1 ... 8} [dB]
PaRM: Preamble Retrans Max, maximum number of
preambles in one preamble ramping cycle {1 ... 64}
Key
Line 6
Here are shown RRC parameters; see 3GPP 25.304,
sections 5.2.6.1.4–5.
Srxlv: RRC Srxlev, Cell Selection Receive Level [dB]
Squal: RRC Squal, Cell Selection Quality
RSCP: RRC cell ranking criterion Rs for current
serving cell, with RSCP used as quality measure
Ec/N0: 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
Lines 7–8 are the same as the two bottom lines in the
W/G Cells view: see section 4.1.
LZT 138 0240 R2A 37

4.13. WCDMA Channel (View No. 2.5)

Line 1
SIR: Signal-to-Interference Ratio (dB)
SIR_TG: SIR Target (dB)
TxPwr: UE Transmit Power (dBm), numeric/
graphic
Line 2
PCA: Power Control Algorithm, see 3GPP 25.331
Screenshot PCSS: Power Control Step Size, see 3GPP 25.331
RRC_STATE: RRC State, one of {CELL_DCH,
CELL_FACH, CELL_PCH, URA_PCH, IDLE,
PASSIVE}
CM: Compressed Mode: 0: No, 1: Yes
Lines 3–8
These lines show the configuration of up to 6
transport channels:
ChId: Transport Channel Id
Key
ChT/D: Transport Channel Type and Direction
DLBT: Downlink BLER Target (%)
Rate: Maximum transport channel bit rate (bit/s)

38
4.14. WCDMA AMR (View No. 2.6)

Line 1
graphic
Line 2
PASSIVE}
Line 3
Codec: Speech codec: “AMR” (narrowband) or
“AMR-WB” (wideband)
Key Lines 4–7

In these lines are shown all speech codecs in the
AMR active set.
CDL: AMR codec used on downlink
DLU: Utilization (%) of this downlink AMR codec
CUL: AMR codec used on uplink
ULU: Utilization (%) of this uplink AMR codec
All codec rates for AMR narrowband are listed in
3GPP 26.101, Table 2. All codec rates for AMR-WB
are listed in 3GPP 26.201, Table 2.

LZT 138 0240 R2A 39

4.15. WCDMA Data (View No. 2.7)

Line 1
graphic
Line 2
PASSIVE}
Lines 3–6 report the current performance of and

some statistics on the WCDMA data transfer. All
values are combined values computed over all
used channels.
Key Line 3, DR: RLC protocol level, downlink

Line 4, DT: Transport channels, downlink
Line 5, UR: RLC protocol level, uplink
Line 6, UT: Transport channels, uplink
Rate: Instantaneous data transfer rate in kbit/s or
Mbit/s. For RLC this bit rate includes AM channels
only (not TM and UM).
BLER: Percentage of data blocks erroneously
decoded (on downlink), numeric/graphic
Retr: Percentage of data blocks retransmitted (on
uplink; RLC only), numeric/graphic
TotData: Total bytes transferred (B = bytes, K =
kilobytes, M = megabytes). You can reset these
counters as explained in section 4.15.1 below.
40

Screenshot
Key

You can reset all counters in this view by choosing Reset data counters. This
command also resets the counters in the GPRS Data view (see section 4.22).
LZT 138 0240 R2A 41

4.16. HSPA Data (View No. 2.8)

Lines 1–3, general note:
All data presented here is HSDPA data and applies
to the phone’s latest reporting period.
Line 1
QAM: The percentage of time 16-QAM was used
as modulation method.
NCC: Number of channelization codes used on the
HS-SCCH: minimum/average/maximum.
Screenshot
NHARQ: Number of active HARQ (Hybrid
Automatic Repeat Request) processes on the HS-
DSCH.
Line 2 (“Min”)
CQI: Minimum value of CQI (Channel Quality
Indicator). CQI values are defined in 3GPP 25.214,
section 6A.2.
ReqSize: Minimum requested transport block size
in bits (corresponding to minimum CQI).
Key ActSize: Minimum actual transport block size in
bits.
Line 3 (“Max”; analogous to Line 2)

CQI: Maximum value of CQI.
ReqSize: Maximum requested transport block size
in bits (corresponding to maximum CQI).
ActSize: Maximum actual transport block size in
bits.
42
Line 4
All of these HSDPA parameters apply to the same

short and recent interval of time (though not one
identical with the phone reporting period).
BLN: Total number of blocks to be received on the

HS-DSCH.
0RE: Percentage of blocks on HS-DSCH that were
transmitted successfully on first attempt (zero
Screenshot retransmissions).
BL1: Block error rate on HS-DSCH for first retrans-
mission.
BLR: Residual block error rate on HS-DSCH
(decoding unsuccessful after maximum number of
retransmissions).
Line 5: HSUPA data (for latest reporting period)

ETFCI: Average value of the HSUPA (EUL)
Transport Format Combination Indicator. For the
Key mapping between E-TFCI and transport block size,
see 3GPP 25.321, Annex B.
SGI: Average value of Serving Grant Index.
TBS: Average transport block size in bits on
E-DCH.
Line 6: HSUPA data (for latest reporting period)

DTX: DTX rate (%) on uplink.
HR: Happy rate (%), i.e. the percentage of TTIs
where the UE was happy, as defined in 3GPP
25.321, section 11.8.1.5.
Retr: Number of retransmissions on E-DPCCH/
E-DPDCH divided by the number of TTIs.
LZT 138 0240 R2A 43

Line 7: HSDPA
DTrChBR: Total bit rate on all downlink transport
channels; same as DT: Rate in the WCDMA Data
view (see section 4.15) and thus valid for WCDMA
R99 and HSDPA alike.
Line 8: HSUPA
UTrChBR: Total bit rate on all uplink transport
channels; same as UT: Rate in the WCDMA Data
Screenshot view (see section 4.15) and thus valid for WCDMA
R99 and HSUPA alike.

Key
44
4.17. GSM Cells (View No. 3.1)

Line 1 (GSM serving cell)
L: Logical Channel
• B: BCCH
• P: PBCCH
• p: Hopping PBCCH
• S: SDCCH
• s: Hopping SDCCH
• T: TCH
• t: Hopping TCH
• D: PDTCH
Screenshot • d: Hopping PDTCH
BC: Serving Cell BCCH ARFCN
BS: Base Station Identity Code (BSIC)
RxLv: Received Signal Strength (unit user-
R: Routing Area Color, RACo {0 ... 7}; invalid (“–”) if
GPRS not available in network
If the cell does not broadcast packet channels (no
PBCCH), the two rightmost parameters are:
Key C1: Pathloss Criterion C1
C2: Cell Reselection Criterion C2
If the cell supports packet channels (broadcasts a
PBCCH), the two rightmost parameters become:
C31: GPRS Signal Strength Threshold Criterion
C31
C32: GPRS Cell Ranking Criterion C32
LZT 138 0240 R2A 45

Lines 2–7 (GSM neighbor cells)

NC1 ... NC6: Neighbor Cell BCCH ARFCN of six
strongest neighbors
The rest is as on line 1 except for the addition of
the following comparison with the serving cell:
A: Location Area/Routing Area properties:
• =: Same LA/RA
• L: Different LA
Screenshot • P: PLMN not matching
• –: Unknown
Line 8
MT: MS-TXPWR-MAX-CCH, maximum RACH
power (dBm) {GSM 850, 900: 5 ... 39; GSM 1800:
0 ... 36; GSM 1900: 0 ... 33}
RH: Cell Reselection Hysteresis (dB) {0, 2, 3, 6, 8,
10, 12, 14}
B: BS-PA-MFRMS, number of multiframes
Key between paging subgroups {2 ... 9}
CB: Serving cell barred {B: Barred, –: Not Barred}


You can lock on a GSM cell that is listed in the view. The procedures for
locking and unlocking are the same as in the W/G Cells view; see section
4.1.1.
46
4.18. GSM Cell Id (View No. 3.2)

L: Logical Channel
• B: BCCH
• P: PBCCH, p: Hopping PBCCH
• S: SDCCH, s: Hopping SDCCH
BCCH: Serving Cell BCCH ARFCN
LAC: Serving Cell Location Area Code
Screenshot
CI: Serving Cell Identity
RxLev: Serving Cell RxLev (unit user-configurable:
see section 18.7), numeric/graphic
Lines 2–7 (GSM neighbors)

NC1 ... NC6: Neighbor Cell BCCH ARFCN of six
strongest neighbors
LAC: Neighbor Cell Location Area Code
CI: Neighbor Cell Identity
Key RxLev: Neighbor Cell RxLev
Line 8
MT: MS-TXPWR-MAX-CCH, maximum RACH
power (dBm) {GSM 850, 900: 5 ... 39; GSM 1800:
0 ... 36; GSM 1900: 0 ... 33}
RH: Cell Reselection Hysteresis (dB) {0, 2, 3, 6, 8,
10, 12, 14}
B: BS-PA-MFRMS, number of multiframes
between paging subgroups {2 ... 9}
CB: Serving cell barred {B: Barred, –: Not Barred}

LZT 138 0240 R2A 47


4.1.1.
4.19. GSM Cell Name (View No. 3.3)

section 17.5.
Lines 2–8 (GSM neighbors)

Screenshot NC1 ... NC7: Neighbor Cell BCCH ARFCN of
seven strongest neighbors
section 17.5. If the cell name is too long to fit into
the column, point the help bubble at the cell name
to view the string in its entirety. See the image on
the left.
Key Lines 9–10 are the same as the two bottom lines in
Cell name
presentation in help
bubble
48

4.1.1.
4.20. GSM BA List (View No. 3.4)

Line 1 (serving cell)
L: Logical Channel
• B: BCCH
• P: PBCCH
• S: SDCCH
• T: TCH
• t: Hopping TCH
• D: PDTCH
Screenshot • d: Hopping PDTCH
BSIC: Base Station Identity Code (BSIC)
Lines 2–9 (neighbor list = BA list)

NC1 ... NC32: BCCH ARFCNs of all neighbors of
the serving cell (up to 32 cells).
Key

You can lock on any cell that is listed as a neighbor in this view. The
see section 4.1.1.
LZT 138 0240 R2A 49

4.21. GSM Serving Cell (View No. 4.1)

Line 1
L: Logical Channel: B for BCCH
BC: BCCH ARFCN
BS: Base Station Identity Code, BSIC
DSC: Downlink Signaling Counter, current value
(idle mode only)
Screenshot
DSM: Downlink Signaling Counter, max value
idle mode
(= start value) (idle mode only)
Line 2
This line shows parameters of the GSM cell
configuration. This information remains visible in
dedicated mode as long as the same cell is used.
When handover to a new cell takes place, no
configuration information is read for the new cell
while the call is in progress, and this line is then
blanked.
Screenshot CN: CCCH configuration, number of BCCH/CCCH

dedicated mode timeslots {NC, Comb, NC2, NC3, NC4}; see
appendix A.4, page 175
BP: BS-PA-MFRMS, number of multiframes
between paging subgroups {2 ... 9}
BA: BS-AG-BLKS-RES, number of CCCH blocks
reserved for AGCH {0 ... 7}
Key
50
Line 3 (dedicated mode)

L: Logical Channel
• P: PBCCH
• S: SDCCH
• T: TCH
• t: Hopping TCH
• D: PDTCH
• d: Hopping PDTCH
Screenshot
idle mode TC: Traffic Channel (TCH ARFCN) or Stand-alone
Dedicated Control Channel (SDCCH ARFCN) or
Packet Dedicated Traffic Channel (PDTCH
ARFCN). Hopping channels are shown one at a
time; see section 3.1.
TS: Timeslot Number
TA: Timing Advance
TX: UE Transmit Power (dBm), numeric/graphic
RLTC/M: Radio Link Timeout (Current) and Radio
Link Timeout (Max = Start)
Screenshot
dedicated mode Line 4 (dedicated mode)
C/I: Carrier-to-interference ratio in dB for the traffic
channel currently indicated by TC on line 3. That is,
for hopping channels the displaying of C/I values is
synchronized with the traversal of the hopping list;
compare section 3.1. C/I is supported for the
modes TCH/F, TCH/H, and PDTCH. Numeric/
graphic presentation.
RQ: Receive Bit Error Rate (RxQual; scale defined
in 3GPP 05.08), numeric/graphic
Key FER: Frame Erasure Rate (FER) in percent.

Calculated taking DTX into account, i.e. the figure
is based only on blocks actually transmitted.
Numeric/graphic presentation.
DXU: DTX rate (%) on uplink
DXD: DTX rate (%) on downlink
LZT 138 0240 R2A 51

Line 5 (dedicated mode only, except ChTyp)

ChTyp: Channel type, one of {BCCH, PBCCH,
PDTCH, SDCCH, TCH/F, TCH/H}; see appendix
A.5, page 176
ChM: Channel mode, one of {FR, EFR, HR, AFR,
AHR; D24, D48, D96, D144}:
• FR = Voice, Full Rate
• EFR = Voice, Enhanced Full Rate
• HR = Voice, Half Rate
Screenshot • AFR = Voice, AMR Full Rate
idle mode • AHR = Voice, AMR Half Rate
• D24 = Data 2.4 kbit/s, etc. (downlink data rate)
SU: Subchannel Number {0 ... 7}
HS: Hopping Sequence Number {0 ... 63}
MA: MAIO, Mobile Allocation Index Offset
{0 ... 63}
CiMd: Ciphering Mode, one of {A5/1, A5/2, GEA/1,
GEA/2}

Screenshot the W/G Cells view: see section 4.1.
dedicated mode
Key
52
4.22. GPRS Data (View No. 4.2)

Line 1
Line 2
Screenshot T: Traffic Channel Type:
TC: Traffic Channel (TCH ARFCN) or Stand-alone
ARFCN)
Timeslots: Timeslots used on uplink and downlink.
The timeslots are represented by the numbers 0–7,
Key and those currently in use are replaced by arrows
as follows:
• Upward arrow: Timeslot used on uplink
• Downward arrow: Timeslot used on downlink
• Double-headed arrow: Bidirectional timeslot
used on both uplink and downlink
Example: means that TS 1, 2, 3, and 4

are being used on the downlink and TS 3 is being
used on the uplink.
Techn: Technology supported in cell: “EDGE” or
“GPRS”
LZT 138 0240 R2A 53

Line 3
compare section 3.1. Numeric/graphic
presentation. Note: C/I for circuit-switched also
appears here; there is no differentiation of C/I with
respect to data bearer type (CS/PS).
Screenshot CSd: GPRS: Channel coding scheme on downlink

{CS1 ... CS4}; EDGE: Modulation coding scheme
on downlink {MCS1 ... MCS9}
MSd: Modulation method on downlink (G = GMSK,
8 = 8-PSK)
CSu: GPRS: Channel coding scheme on uplink
{CS1 ... CS4}; EDGE: Modulation coding scheme
on uplink {MCS1 ... MCS9}
MSu: Modulation method on uplink (G = GMSK,
8 = 8-PSK)
Key Line 4
C: EGPRS C Value {0 ... 63}
MBEP: EGPRS mean bit error probability (BEP)
BEPV: EGPRS BEP variance
ARQ: Automatic Repeat Request Mode {ARQ1,
ARQ2}: see 3GPP 44.060, sec. 9.2.3.1
54
Lines 5–8 report the current performance of and

some statistics on the GPRS data transfer.
Line 5, “DL”: LLC protocol level, downlink
Line 6, “DR”: RLC/MAC protocol level, downlink
Line 7, “UL”: LLC protocol level, uplink
Line 8, “UR”: RLC/MAC protocol level, uplink
Rate: Instantaneous data transfer rate in kbit/s or
Mbit/s
Screenshot
BLER: Percentage of data blocks erroneously
decoded (on downlink), numeric/graphic
Retr: Percentage of data blocks retransmitted (on
uplink), numeric/graphic
TotData: Total number of bytes transferred (B =
bytes, K = kilobytes, M = megabytes). You can
reset these counters as explained in section 4.22.1
below.

Key the W/G Cells view: see section 4.1.

You can reset all counters in this view by choosing Reset data counters. This
command also resets the counters in the WCDMA Data view (see section
4.15).
LZT 138 0240 R2A 55

4.23. GPRS Info (View No. 4.3)

Lines 1–4 are the same as in the GPRS Data view:
see section 4.22.
Lines 5–6
EWSd: EGPRS window size on downlink
{64 ... 1024}
LWSd: LLC window size (for data) on downlink
{1 ... 255}
EWSu: EGPRS window size on uplink {64 ... 1024}
Screenshot
LWSu: LLC window size (for data) on uplink
{1 ... 255}
Lines 7–8
G: GMM State {I: Idle, R: Ready, S: Standby, –: No
GPRS available}
T3314C: T3314 timer value (GMM Ready Timer),
current value; see 3GPP 24.008, sec. 4.7.2
T3314S: T3314 timer value (GMM Ready Timer),
start value; see 3GPP 24.008, sec. 4.7.2
Key
T3168: T3168 timer start value (Packet Uplink
Assignment Timer), see 3GPP 44.060, sec. 13.1
{value in deciseconds, assigned in System
Information}
T3192: T3192 timer start value (Packet Final Block
Timer) in ms, assigned in System Information; see
3GPP 44.060, sec. 13.1 {0, 80, 120, 160, 200, 500,
1000, 1500}
NMO: Network Mode of Operation {I, II, III}; see
appendix A.8, page 177
DX: DRX Timer Max, see 3GPP 44.060, sec.
5.5.1.5 {0, 1, 2, 4, 8, 16, 32, 64}

56
4.24. GSM C/I Info (View No. 4.4)

This view shows the carrier-to-interference ratio,
C/I, for the most frequently utilized timeslot on each
GSM traffic channel in use. Up to eight channels
can be shown, sorted by worst C/I.
Lines 1–8
ARFCN: TCH or PDTCH ARFCN (channels in
hopping list)
C/I: C/I value in dB for this traffic channel, numeric/
Screenshot graphic

Key
LZT 138 0240 R2A 57

4.25. GSM AMR (View No. 4.5)

Line 1
Line 2
Screenshot T: Traffic Channel type:
time; see section 3.1.
TS: Timeslot Number
Key
graphic
Line 3
compare section 3.1. C/I is supported for the
modes TCH/F, TCH/H, and PDTCH. Numeric/
graphic presentation.
58
Line 3 (continued)
RQ: Receive Bit Error Rate (RxQual; scale defined
in 3GPP 45.008, sec. 8.2), numeric/graphic
FE: Frame Erasure Rate (FER) in percent,
numeric/graphic
DXD: DTX rate (%) on downlink
DXU: DTX rate (%) on uplink
Lines 4–7
Screenshot
In these lines are shown all speech codecs in the
AMR active set.
CDL: AMR codec used on downlink
DLU: Utilization (%) of this downlink AMR codec
CUL: AMR codec used on uplink
ULU: Utilization (%) of this uplink AMR codec
All codec rates for AMR narrowband are listed in
3GPP 26.101, Table 2. All codec rates for AMR-WB
Key are listed in 3GPP 26.201, Table 2.

LZT 138 0240 R2A 59

4.26. The WAP Browser Data Views

While the WAP browser (activated from the phone’s main menu → Internet)
is running, TEMS Pocket can show selected air interface information in the
bottom part of the screen. Two WAP browser data views are provided, one for
WCDMA and one for GPRS. You toggle between the views by briefly
pressing the up and down arrow buttons on the left side of the phone. (These
buttons also control the media player volume if the media player is running.)
The WAP browser data views are by default visible.
• During a WAP session, you can hide the data views by pressing Options
and choosing Hide data view. To show them again, press Options and
choose Show data view.
• You can also turn these data views on and off from the Pocket menu; see
section 18.1.
The WAP browser can alternatively be viewed in “landscape” fashion. The
data view then still appears at the bottom (that is, along the left edge of the
phone display when the phone is held in the normal manner). The data view
contents and layout remain unchanged.
There are no actions associated with the WAP browser data views.
60
4.26.1. WCDMA WAP Browser Data View

Line 1
UARFCN: Serving cell UARFCN
SC: Scrambling Code
RSSI: Serving cell RSSI (dBm)
Line 2
Screenshot
TxPwr: UE Transmit Power (dBm)
In lines 3–4, all values are combined values

computed over all used channels.
Line 3, left: “DR” (downlink, RLC)

Rate: Total RLC downlink instantaneous data
transfer rate in kbit/s or Mbit/s
BLER: Percentage of RLC downlink data blocks
erroneously decoded
Key
LZT 138 0240 R2A 61

Line 3, right: “UR” (uplink, RLC)

Rate: Total RLC uplink instantaneous data transfer
rate in kbit/s or Mbit/s
Retr: Percentage of RLC uplink data blocks
retransmitted
Line 4, left: “DT” (downlink, transport channels)

Rate: Total instantaneous data transfer rate on
downlink transport channels in kbit/s or Mbit/s
Screenshot
BLER: Percentage of downlink transport channel
data blocks erroneously decoded
Line 4, right: “UT” (uplink, transport channels)

Rate: Total instantaneous data transfer rate on
uplink transport channels in kbit/s or Mbit/s
(no retransmissions shown for uplink transport
channels)
Key
62
4.26.2. GPRS WAP Browser Data View

Line 1
BSIC: Base Station Identity Code, BSIC
MCSd: EGPRS modulation coding scheme on
downlink {MCS1 ... MCS9}
Screenshot
Line 2
T: Traffic Channel type:
Key time; see section 3.1.
and those currently in use are replaced by arrows
as follows:

used on the uplink.
MCSu: EGPRS modulation coding scheme on
uplink {MCS1 ... MCS9}
LZT 138 0240 R2A 63

In lines 3–4, all values are combined values

computed over all used channels.
Line 3, left: “DL” (downlink, LLC)

Rate: Total LLC downlink instantaneous data
BLER: Percentage of LLC downlink data blocks
erroneously decoded
Screenshot Line 3, right: “UL” (uplink, LLC)

Rate: Total LLC uplink instantaneous data transfer
rate in kbit/s or Mbit/s
Retr: Percentage of LLC uplink data blocks
retransmitted
Line 4, left: “DR” (downlink, RLC/MAC)

Rate: Total RLC/MAC downlink instantaneous data
BLER: Percentage of RLC/MAC downlink data
Key blocks erroneously decoded
Line 4, right: “UR” (uplink, RLC/MAC)

Rate: Total RLC/MAC uplink instantaneous data
Retr: Percentage of RLC/MAC uplink data blocks
retransmitted
64
Chapter 5. Data Views with Graphs
5. Data Views with Graphs
The data views in category 5 all contain a graph showing how one or several
parameters evolve over time. In other respects, these data views are similar
to the text-only data views covered in chapter 4.
The unit “m” on the x-axis of each graph means “minutes”.
Events are indicated as vertical lines in graphs. However, an event appears
only if logging is currently turned on for that type of event (see sections 10.1.3
and 10.2).
Data views with graphs have no actions associated with them.
LZT 138 0240 R2A 65

5.1. W/G Serving RSSI (View No. 5.1)

Line 1 shows the strongest WCDMA cell.
• S: Serving cell
SC: Scrambling Code
Screenshot
numeric/graphic
Line 2 shows the strongest GSM cell: in GSM

mode, the GSM serving cell; in WCDMA mode, the
strongest (inter-RAT) GSM neighbor measured.
L: Logical Channel
Key • B: BCCH
66
Line 2 (continued)
C1: Pathloss Criterion C1
Screenshot PBCCH), the two rightmost parameters become:
C31
Graph
Green line: Received Signal Code Power, RSCP
(dBm) for strongest WCDMA cell
Blue line: Received Signal Strength, RxLev (dBm)
for strongest GSM cell
Key
LZT 138 0240 R2A 67

5.2. W/G Cells (View No. 5.2)

Line 1 shows the strongest WCDMA cell.
• S: Serving cell
SC: Scrambling Code
Screenshot
numeric/graphic
Line 2 shows the strongest GSM cell: in GSM

mode, the GSM serving cell; in WCDMA mode, the
strongest (inter-RAT) GSM neighbor measured.
L: Logical Channel
Key • B: BCCH
68
Line 2 (continued)
PBCCH), the two rightmost parameters become:
C31
Graph
Green bars: Received Signal Code Power, RSCP
Screenshot
Blue bars: Received Signal Strength, RxLev
(dBm) for strongest GSM cell
Lines: WCDMA: RSCP of three strongest
neighbors (dBm); GSM: RxLev of three strongest
neighbors (dBm)

Key
LZT 138 0240 R2A 69

5.3. W/G Data (View No. 5.3)

Line 1 (WCDMA transport channels)
DRate: Instantaneous downlink data transfer rate
in kbit/s or Mbit/s
DBLER: Percentage of data blocks erroneously
decoded on downlink, numeric/graphic
URate: Instantaneous uplink data transfer rate in
kbit/s or Mbit/s
Line 2 (GSM RLC/MAC protocol level)

Screenshot
in kbit/s or Mbit/s
kbit/s or Mbit/s
URetr: Percentage of data blocks retransmitted on
uplink, numeric/graphic
Graph
Key
Note that the unit in the graph is Mbit/s, while the
prefix in the data rate text fields is either “k” or “M”.
Red line: WCDMA downlink transport channel
data transfer rate in Mbit/s
Light red line: WCDMA uplink transport channel
data transfer rate in Mbit/s
Green line: GSM RLC/MAC downlink data transfer
rate in Mbit/s
Light green line: GSM RLC/MAC uplink data
transfer rate in Mbit/s

70
5.4. WCDMA Serving (View No. 5.4)

Lines 1–2 show the two strongest WCDMA cells.
• S: Serving cell
UARFC: UARFCN
Screenshot SC: Scrambling Code
numeric/graphic
Graph
Grey bars: Received Signal Code Power, RSCP
Key
Blue bars: UTRA Carrier RSSI (dBm)

LZT 138 0240 R2A 71

5.5. WCDMA SIR (View No. 5.5)

Line 1
SIR: Actual Signal-to-Interference Ratio, SIR (dB)
graphic
Graph
Grey bars: SIR Target (dB)
Screenshot Red line: Actual SIR (dB)

Key
72
5.6. WCDMA Cells (View No. 5.6)

Lines 1–2 show the two strongest WCDMA cells.
• S: Serving cell
UARFC: UARFCN
Screenshot SC: Scrambling Code
numeric/graphic
Graph
Green bars: Received Signal Code Power, RSCP
Key
Lines: Received Signal Code Power, RSCP (dBm)
for three strongest WCDMA neighbors

LZT 138 0240 R2A 73

5.7. GSM Cells (View No. 5.7)

L: Logical Channel
• B: BCCH
Screenshot
Key PBCCH), the two rightmost parameters become:
C31
Line 2 (Strongest GSM neighbor)

NC: Neighbor Cell BCCH ARFCN
The rest is as on line 1 except for the addition of:
A: Location Area/Routing Area properties:
• =: Same LA/RA
• L: Different LA
• P: PLMN not matching
• –: Unknown
74
Graph
Blue bars: Received Signal Strength, RxLev
(dBm) for GSM serving cell
Lines: Received Signal Strength, RxLev (dBm) for
three strongest GSM neighbors

Screenshot
Key
LZT 138 0240 R2A 75

5.8. GSM Data (View No. 5.8)

Line 1
T: Traffic Channel Type:
Screenshot ARFCN)
and those currently in use are replaced by arrows
as follows:

Key
used on the uplink.
Techn: Technology supported in cell: “EDGE” or
“GPRS”
Line 2 (RLC/MAC protocol level)

in kbit/s or Mbit/s
kbit/s or Mbit/s
URetr: Percentage of data blocks retransmitted on
uplink, numeric/graphic
76
Graph
Note that unit in the graph is kbit/s, while the prefix
in the data rate text fields is either “k” or “M”.
Green line: GSM RLC/MAC downlink data transfer
rate in kbit/s
Light green line: GSM RLC/MAC uplink data
transfer rate in kbit/s

Screenshot the W/G Cells view: see section 4.1.
Key
LZT 138 0240 R2A 77

6. The Map View
The Map view 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.
Note that in order to use the pinpointing function, you must have a memory
card with sufficient free space installed on the phone. This is because all
logfile-related data is copied to the memory card in connection with creating
the zip archive. (Other methods of recording a logfile do not require a memory
card.)
6.1. Loading a Map Image into the Map View

• First you need to obtain an image of the environment that is going to be
covered during measurement. For example, use the phone’s camera to
photograph the emergency or evacuation plan for the relevant floor. The
best image quality is obtained if the camera is set in black-and-white
mode. Also avoid using the flash. If you are using an image from a
different source, it must be in JPEG format.
• Load your image as a background image in the Map view: While in this
view, press Options and select Data view actions → Load map. Locate
the file you want to load, and press Select.
78
Chapter 6. The Map View
The image now appears in the Map view:
6.2. Pinpointing Your Test Route
6.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.
• In the Map view, press Options and select Data view actions → Map
properties → Zoom. Set the zoom level as appropriate.
6.2.2. Customizing the Appearance of Route Markers

The waypoints that you mark on the map will always be colored blue.
The markers tracing your route between waypoints will by default be color-
coded according to RxLev (in GSM) or UTRA Carrier RSSI (in WCDMA). The
LZT 138 0240 R2A 79

color coding is explained in appendix B, page 184. You can change to a

different parameter as follows:
• Press Options and select Data view actions → Value element.
• Select the desired parameter.

(“RLC DL”/“RLC UL” means RLC throughput for
WCDMA and RLC/MAC throughput for GSM.)
6.2.3. Entering Map Properties

You can set some text attributes for the map image. The purpose of supplying
this information is to enable geographical positioning of the map image using
the TEMS Pocket Positioning Tool: see section 6.3.
• Press Options and select Data view actions → Map properties.
• Latitude, Longitude: Enter the coordinates of

the top left corner of the map image.
• Address, Building, Floor: Enter the relevant
information.
The parameters are written to an XML file; see section 6.2.4.
6.2.4. Pinpointing and Recording

• To initiate a measurement, press Options and select Data view actions →
Start pinpointing. A crosshair symbol becomes visible, and a logfile is
opened automatically. The fact that the pinpointing is in progress is
indicated by an icon at the top of the display.
80
Chapter 6. The Map View
• To pinpoint a spot on the map, move the crosshairs to the desired

position, then press the Select button.
Note: The screen capture function must be turned off, otherwise the
right soft button will be labeled Capture instead.
• Continue pinpointing at regular intervals along the route, and whenever

you change direction. Consecutive waypoints are automatically
connected by route markers.
• You can undo the latest pinpointing action at any time by pressing the C
button.
• When you are done with the measurement, press Options and select Data
view actions → Stop pinpointing.
LZT 138 0240 R2A 81

The logfile closes, and the pinpointing icon disappears.

A zip archive is now created holding:
• the logfile (*.log)
• the image loaded into the Map view (*.jpg)
• a file where the pinpointed route is recorded (*.ppf)
• the map properties covered in section 6.2.3 (*.xml)
• an index file detailing the archive contents (.xml).
Please note that such zip archives cannot be replayed as-is in TEMS Pocket.
(They resemble ordinary logfiles in the phone file system, since the phone
does not show file extensions.)
6.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 and TEMS Presentation.
Before post-processing the data, however, it needs to be anchored to a
geographical position. This is accomplished by processing the zip archive
with a software utility called TEMS Pocket Positioning Tool, which is installed
along with TEMS Investigation as well as TEMS Presentation. It is launched
from the Start menu by selecting Programs → Ascom → TEMS Products →
Utilities → TEMS Pocket Positioning Tool. For further details on this topic,
consult the TEMS Pocket Positioning Tool User’s Manual.
The intended way of working is to position the map using the coordinates
provided in the map properties in TEMS Pocket: see section 6.2.3.
After being positioned, the logfiles are ready to be loaded into TEMS
Investigation or TEMS Presentation.
82
Chapter 7. TEMS Pocket Functions in the Activity Menu
7. TEMS Pocket Functions in the

Activity Menu
A number of TEMS Pocket functions are accessed by pressing the Activity

key. This is the button labeled .
Note that many of these functions are found only in the Activity menu and not
among the submenus of the Pocket menu. They are placed here to be
conveniently accessible regardless of what TEMS Pocket functions or other
phone functions you are using.
7.1. Operational Mode

Regarding the phone mode/scan mode distinction, see section 2.1.
Active: TEMS Pocket is in phone mode, and all
functions in that mode are active.
Background: TEMS Pocket is in phone mode; no
data views are displayed, but all other functions are
active.
Scanner: TEMS Pocket is in scan mode.
Inactive: No TEMS Pocket functions are active.
7.2. Insert Filemark

This command inserts filemarks (text strings) in a logfile while it is being
recorded. You can use filemarks to tag segments 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).
On selecting this command you are prompted to type the filemark text. It may
consist of up to 127 characters.
This command is available only while logfile recording is in progress.
LZT 138 0240 R2A 83

7.3. Start/Stop Logfile Recording

This command is used for manual recording of TEMS Pocket logfiles. (Logfile
recording can also be automated, using a variety of trigger conditions. This is
done from the Passive Measurement menu; see chapter 16. Regarding
logfile recording by pinpointing, see section 6.2.)
You can insert filemarks in a logfile during recording; see section 7.2.
If the memory on the storage medium used for logfiles is running low (only
1 MB left), or if some error occurs, the recording is stopped. You are then
notified by a message in the display.
Refer to chapter 14 for all remaining details on logfile recording and handling.
During logfile replay this command is not available.
7.3.1. Icons Used for Logfile Recording
While a logfile is being recorded, this icon is shown on the status bar at
the top of the display.
7.4. Start/Stop Logfile Replay

This command is used to start and stop replay TEMS Pocket logfiles in TEMS
Pocket itself. Note that you can also replay the logfiles in TEMS Investigation
and TEMS Presentation and make use of the powerful presentation facilities
in these tools.
On giving this command you are taken to the file system of the logfile storage
medium (see section 14.2) in order to select a logfile for replay. Regardless of
storage medium, the directory is named Other\Pocket\Pro. A filter is applied
so that only files with extension .log are visible.
Once you have selected a logfile, the TEMS Pocket user interface (data
views, event log, event counters) is cleared, and the logfile replay is put on
standby. The actual replay does not begin until you select Play; see section
7.4.1 below.
During replay, the user interface is updated by the logfile content exactly as in
live mode, that is, exactly as if the data were being received from the network.
The cell control icon (see section 9.1) does not appear during replay, nor can
the Cell Control menu be accessed while a logfile is being replayed. It is
therefore not possible in TEMS Pocket to inspect the exact cell control
84
settings that were in force at a particular point while recording the logfile. This
can however be done by replaying the logfile in TEMS Investigation and
studying certain information elements exhibited in that application (“Band
Control”, “Serving Cell List Active”, and others).
In both TEMS Pocket and TEMS Investigation, events reflecting the
application of cell control functions at recording time will appear during replay,
just like any other events.
If you rewind the logfile, the TEMS Pocket user interface (data views, event
log, event counters) is once again cleared. The same thing happens when
you exit replay mode.
During logfile recording, during execution of a command sequence, and
during FTP sessions the replay command is not available.
7.4.1. Replay Control Functions

Play: Replays the logfile at approximately live
speed. While the replay is in progress the button is
relabeled Pause, and pressing the button in that
situation pauses the replay. Press the button once
more (now named Play again) to resume the
replay from the point where it was paused.
Step: Reads one more phone message from the
logfile and then pauses the replay. You may have
to step several times to see any changes in the
data.
Options: Pressing this button gives access to
further replay control functions; see below.
Rewind: Rewinds the logfile to the beginning and

clears the TEMS Pocket user interface. Press Play
to start the replay once more.
Exit replay mode: Aborts the logfile replay, closes
the logfile, and returns TEMS Pocket to live mode.
LZT 138 0240 R2A 85

When the replay has reached the end of the logfile, the buttons are once
again relabeled, now with the choices in the Options menu (above):
Options: Toggle on-screen help mode; toggle

capture on/off.
Rewind: See above.
Exit: Exit replay mode; see above.
During logfile replay, all other TEMS Pocket control functions (all other
commands in the Activity menu and all commands in the Cell Control, FTP,
Logfile, and Command Sequence menus) are disabled.
If an incoming call is received during logfile replay, you can choose either to
answer the call, aborting the replay, or to ignore the call and proceed with the
replay. In the latter case a busy tone will be sent to the calling party.
7.4.2. Icons Used for Logfile Replay

The following icons are displayed on the status bar to indicate the status of
the replay:
Replay in progress at normal speed (following Play command)
Replay paused (following Pause or Step command)
Replay stopped. This means that the logfile has been replayed to the
end.
7.5. Tag Logfile

This function lets you attach a tag to a logfile that is being recorded. The tag
is used as a criterion for logfile saving in the course of command sequence
execution or passive measurement (“Store logfiles with” setting: see sections
15.2.1 and 16.1). Note that for the Tag Logfile command to be available in
these situations, the Tag option must have been selected in the dialogs just
86
referred to. In contrast, when recording a logfile manually, the Tag Logfile
command is always available.1
Tagging a logfile also adds the string tag_ to the logfile name, which enables
you to consider tags when doing logfile post-processing of your own.
7.6. Event Log

This is a shortcut to the event log; see section 10.1.
7.7. Start FTP/Stop FTP/Stop Logfile Upload

These commands are used to conduct FTP sessions, including uploading of
TEMS Pocket logfiles if you prefer to do these uploads manually. The
command takes you to a list of the FTP Get and FTP Put operations you have
defined. How to perform FTP operations and how to connect to FTP servers
is specified in the FTP menu: see chapter 13.
The start command always reads “Start FTP”, while the stop command is
named “Stop logfile upl.” for a logfile upload and “Stop FTP” for other FTP
sessions.
A series of events is generated in connection with each FTP session: see
section 10.5.8.
During logfile replay and during execution of a command sequence, this
command is not available.
7.8. Connect/Disconnect GPS

This command connects or disconnects a GPS (phone-internal or external).
For further information on using GPS devices with TEMS Pocket, see chapter
12.
The command is visible only if you have selected manual connect; see
section 12.2. While a connect operation is in progress, the menu item reads
“Connecting” and is grayed.
1. The same is also true for passive measurement triggered on phone start-
up; but the “Store logfiles with” criterion is absent for this type of
measurement anyway (see section 16.1) – the logfile is always stored.
Even so, you can tag the logfile for purposes of your own.
LZT 138 0240 R2A 87

7.9. Start/Stop Command Sequence

This command starts and stops a command sequence. How to set up
command sequences is covered in chapter 15.
• Select one of the command sequences that are

defined, then press the Select button.
• The selected sequence will execute indefinitely
unless you stop it. To stop the sequence,
choose Stop Command Sequence from the
Activity menu.
If a passive measurement (see chapter 16) is in progress when you start a

command sequence, TEMS Pocket halts the passive measurement and runs
the command sequence instead. In this case, when the sequence has been
stopped, passive measurement is re-enabled according to the previous
settings for that function.
7.10. Pocket Menu

This is a shortcut to the Pocket menu; see chapter 8.
88
Chapter 8. The Pocket Menu
8. The Pocket Menu
8.1. General
The Pocket menu can be accessed
• from the Activity menu
• from the phone’s main menu by choosing Settings. The Pocket menu
appears at the top of the General submenu.
The Pocket menu holds the following submenus:
Chapter
Name Function
Ref.
Cell control Control the phone’s behavior in 9

the network: Lock on RAT/band/
frequency/cell, etc.
Events Show and control event log, event 10

counters, and event settings
Data views Control visibility of data views 11
GPS Configure GPS settings 12
FTP Set up FTP sessions and FTP 13

logfile transfer
Logfile Configure automated logfile 14

transfer
Command sequence Define command sequences 15
Passive measurement Configure passive mode 16

measurement
Tools Import and export user-defined 17

TEMS Pocket settings, and more
LZT 138 0240 R2A 89

Chapter
Name Function
Ref.
General settings Configure miscellaneous TEMS 18

Pocket settings
90
Chapter 9. Cell Control Menu
9. Cell Control Menu
In this menu are collected the functions that modify the phone’s behavior in
the network.
Note that cell control functions can also be activated as options in command
sequences; see section 15.2.
9.1. Icons Used for Cell Control

Whenever at least one cell control function is active, this icon appears
on the status bar.
This icon does not appear during logfile replay.
9.2. Lock to RAT

This function locks the phone to one radio access technology in idle mode. It
does not have any effect on RAT selection in dedicated mode; however, an
ongoing FTP session will be terminated, so the function should not be used
while an FTP session is in progress.
When this function is activated, the phone detaches from the network it is
currently attached to, and the message “No netw. coverage” appears in the
phone display. The phone then attaches to the selected network.
If the signal is too weak, the phone will go into no service mode.
LZT 138 0240 R2A 91

Off: No forcing of network selection.

WCDMA: The phone is forced to camp on a
WCDMA network whenever one is available.
GSM: The phone is forced to camp on a GSM
network whenever one is available.
Regarding interplay between locking functions, see section 9.6.
Note: In the phone’s main menu (Settings → Connectivity → Mobile

networks → GSM/3G networks) it is possible to make a choice
between “GSM and 3G” and “GSM only”. It is recommended not
to use this function in conjunction with TEMS Pocket, since the
Cell Control icon (see section 9.1) will then not be displayed, and
the GSM lock operation will not be registered in the logfile if you
are recording one (compare section 7.4).
9.3. Lock Cell WCDMA

This function locks the phone to a WCDMA cell, which will immediately
become the serving cell provided that the signal strength is sufficient. If the
signal is too weak, the phone will go into no service mode.
• Choose Set UARFCN/SC to lock on a cell. You

will be asked to enter a UARFCN and SC.
These values will then appear beneath the
menu item when selected.
• Alternatively, you can lock on a UARFCN while
disregarding scrambling codes. This is done by
not entering a SC.
• Choose Off to release the lock.
Note that you can also lock on a cell that makes an appearance in data views.
See sections 4.1 and 4.9.
92
9.4. Lock ARFCN GSM

This function locks the phone to an ARFCN in a GSM network. If there exists
an available GSM cell using that ARFCN, the phone will be immediately
handed over to that cell provided that the signal strength is sufficient. If the
signal is too weak, the phone will go into no service mode.
• Choose Set ARFCN to lock on a cell. You will

be asked to enter an ARFCN number. This
ARFCN will then appear beneath the menu
item when selected.
• Choose Off to release the lock.
Note that you can also lock on a cell that makes an appearance in data views.
See sections 4.1, 4.17, and 4.18.
9.5. Lock Band WCDMA, Lock Band GSM

You can lock the phone to a particular WCDMA or GSM frequency band. Note
that this operation will result in no service if you prevent the use of all bands
that are available in the area.
Off: Function not applied.

850 (V), etc.: The phone will be locked to the
indicated WCDMA band. The set of bands
supported differs between the phone models.
LZT 138 0240 R2A 93

Off: Function not applied.

850, etc.: The phone will be locked to the indicated
GSM band.
The phone cannot be band-locked while a voice or video call is in progress.

9.6. Interplay between Locking Functions

If you lock the phone to a cell, UARFCN, or band (sections 9.3, 9.4, 9.5), the
phone is also automatically locked to the corresponding RAT. In this situation,
• if you release the cell or band lock, the RAT lock is also automatically
released;
• if you release the RAT lock, the cell or band lock is not released but
remains. This is useful if you want to test inter-RAT handover to and from
a specific cell or band in one RAT.
All locking commands have equal priority in the sense that no command can
be inhibited by one previously given. For example, if you lock the phone to
WCDMA with Lock to RAT and then issue a Lock ARFCN GSM command,
the WCDMA lock is released and the phone is RAT-locked to GSM instead.
9.7. Comparison with Locking Functions in TEMS

Investigation
Users familiar with TEMS Investigation should note that the relationship
between the locking functions in that product is partly different. In TEMS
Investigation, the RAT Control setting for Sony Ericsson UMTS phones has
priority over all technology-specific settings, so that (for example) trying to
lock on a frequency band in GSM has no effect if the phone is currently
locked to WCDMA. To be able to lock on a GSM band, you must first
manually release the RAT lock. (Compare with section 9.6 above.)
94
For full details, see the TEMS Investigation 11.0 User’s Manual, section
16.2.1.
9.8. Voice Codec

This function is used to modify the list of preferred GSM and WCDMA voice
codecs that the phone reports to the network. In the dialog are shown all
GSM and WCDMA voice codecs that the phone supports.
You cannot deselect all codecs in the dialog; at least one codec must remain
selected at all times.
It should be emphasized that this function does not provide ultimate control of
which voice codec is actually used during a call; this decision always remains
with the network.
Codecs used in GSM

AMR-WB: Adaptive Multi Rate – Wideband
AMR-FR: Adaptive Multi Rate – Full Rate
EFR: Enhanced Full Rate
FR: Full Rate
AMR-HR: Adaptive Multi Rate – Half Rate
HR: Half Rate
Codecs used in WCDMA

UMTS AMR: UMTS Adaptive Multi Rate
UMTS AMR2: This codec behaves as a FR AMR
codec in the uplink and as a UMTS AMR codec in
the downlink (3GPP 23.153 section 5.6.1).
UMTS AMR-WB: UMTS Adaptive Multi Rate –
Wideband
9.9. HS Capability
You can enable or disable the TEMS Pocket phone’s HSPA capabilities as
shown below.
LZT 138 0240 R2A 95

Note that this function does not affect the behavior of the “3G”/“H” status bar
symbol (see section 2.2). The latter is governed entirely by the capabilities of
the current serving cell.
Off: Only WCDMA R99 is enabled.

HSDPA: HSDPA is enabled, but HSUPA is not.
HSPA: Both HSDPA and HSUPA are enabled.
9.10. Ignore Cell Barred

This function governs whether the phone is allowed to access a barred cell.
Off: The phone will make no attempt to access

barred cells.
On: The phone will ignore barring of cells.
9.11. Reset Control Settings

This command undoes any changes made from the default in the Cell control
menu. The reset operation does not affect the General settings and Events
menus.
• In the Cell control menu, choose Reset control settings and press Yes to
confirm.
If you have not changed anything from the default, the Reset control settings
choice is disabled and grayed.
The Cell control settings revert to their defaults when the phone is turned off.
96
Chapter 10. Events Menu
10. Events Menu
Events are inspected in the event log. (The term “log” as used in this section
has got nothing to do with recording of TEMS Pocket logfiles; regarding the
latter, see section 7.3.)
Under Event counters, you can check how many times each type of event
has occurred.
Under Event settings, you configure settings for events: logging, counting,
audio signals, and displaying of icons.
Note: To have events logged at all, you must make sure that Event
logging is not set to “Off”. See section 10.1.3.
10.1. Event Log
10.1.1. Viewing the Event Log

• In the Events menu, choose Event Log.
The New tab is shown, listing all events that have occurred since the last time
you inspected the New tab. The number of new events is shown in the tab
title.
The All tab shows all events, including those not yet viewed (i.e. those
remaining on the New tab).
The Fail tab shows all failure events.
The Normal tab shows all normal events.
When an event is selected on a tab, the most important parameters of the
event are shown beneath the event name:
LZT 138 0240 R2A 97

Event name
Event time and parameters
To inspect the full details of an event, select it and press View. A plain-text
screen appears:
Event name
Timestamp
CGI
Event-specific parameters
10.1.2. Clearing the Event Log

A maximum of 100 events can be stored in the event log. Once the log is full,
the oldest log entry is removed whenever a new event is entered. The event
log can also be cleared manually:
• To clear the event log, press Options and choose “Clear event log”. Press
Yes to confirm.
10.1.3. Enabling/Disabling Event Logging and Sound

While in the event log, you can configure some general aspects of event
logging as follows:
98
• Press the Options button and choose Event logging.
On: Event logging and event sounds are enabled.

Silent: Event logging is enabled, but event sounds
are disabled.
Off: Event logging and event sounds are disabled.
The selection made here overrides all settings
made for individual event types (see section 10.2).
10.1.4. Shortcuts to Event Settings and Event Counters

• From the event log you can use the Options menu to go directly to the
event settings (see section 10.2) or event counters (see section 10.3).
10.2. Event Settings

Each type of event has a set of configurable settings.
You can export your event settings to file; they are included in the Export
settings operation (Tools menu: see section 17.4).
10.2.1. Viewing Event Settings

• From the Events menu, choose Event Settings.
Events are grouped into submenus: one for each event category (CC, MM,
SM, GMM, IRAT, RR, RRC, Session). All event types are listed and described
in section 10.5 below.
Use the navigation key (left/right) to move between event submenus. When
you select an event, the current settings for that event are displayed beneath
the event name.
LZT 138 0240 R2A 99

10.2.2. Modifying Event Settings

• To change settings for an individual event, navigate to the event and
press the Select button.
• To apply identical settings to all events in a category (submenu), navigate
to that submenu, press Options and choose “Select <category name>”
(e.g. “Select RR”).
• To apply identical settings to all events, choose Options and choose
“Select all”.
The following options exist:
Log: Turns logging on and off for the event or

event category. Turning off logging also turns off
Sound and Icon popup (below).
If you select an event category, or all events, a third
option appears which is named Default. This
restores the default logging settings listed in
section 10.5.
(continued on next page)
100
Sound:
• “Off” means that no sound will be played when
the event occurs.
• “Default” means that, in idle mode, the
predefined sound for the event will be played
when the event occurs. The prerecorded sound
files consist of a voice announcing the event. In
dedicated mode, the voice recording is
replaced by a notification beep.
• “User set” directs you to a directory in the
phone’s file system where you can store sound
files of your own and associate them with
events. Supported file formats are MIDI, MP3,
and AMR. (The prerecorded sound files are not
accessible in the phone file system.)
Note, however, that if Event logging is set to Silent
(see section 10.1.3), all event sounds will be muted
regardless of the settings made here.
Icon popup: If turned on, the icon associated with

an event will be shown in the status bar each time
the event occurs. The icons used are reproduced in
section 10.5.
10.3. Event Counters

TEMS Pocket keeps track of the number of times each type of event has
occurred. This function is always active and cannot be turned off while the
application is in Active mode. The counters are however reset whenever you
enter or exit logfile replay mode.
10.3.1. Viewing Event Counters

• From the Events menu, choose Event Counters.
The events are divided into the same categories as in the event settings (see
section 10.2). All event types are listed and described in section 10.5 below.
LZT 138 0240 R2A 101

Use the navigation key (left/right) to move between event submenus. When
you select an event, the current count for that event is displayed beneath the
event name.
10.3.2. Resetting Event Counters

• To reset the counter for an event, navigate to the event and press the
Reset button.
• To reset the counters for all events in a category (submenu), navigate to
that submenu, press Options and choose “Reset <category name>” (e.g.
“Reset RR”).
• To reset the counters for all events, press Options and choose “Reset all”.
10.4. Event Icons

An icon is shown on the display status bar for the latest event that occurred. If
no event whatsoever occurs within 15 minutes, the icon disappears.
Event icons are differentiated as follows:
• Each event category distinguished under Event settings and Event
counters has its own icon (for example, CC and MM; see section 10.2).
• All failure events are distinguished by a red cross.
See the examples below:
Normal event Failure event
102
For other event categories, the appropriate text string is substituted.

For inter-RAT events, one of the strings “2G” and “3G” is added to indicate
which technology the phone is transferred to:
Handover Direction Normal Events Failure Events
GSM to WCDMA
WCDMA to GSM
10.5. List of Logged Events

This section lists all the events saved in the event log and their parameters.
Some of the event parameters are described in more detail in appendix A.
Here are also listed the default values for the settings described in section
10.2.
The T column indicates whether the event denotes a normal occurrence (N)
or some kind of failure (F).
The Def column indicates the default logging, sound, and icon popup settings
(On = all settings turned on, L = only logging turned on, Off = all settings
turned off).
All events have CGI as parameter; other parameters appear from the tables.
10.5.1. CC Events
For values of CC Cause, see appendix A.3.
Event Name T Def Parameters
Call Attempt N Off CC Id, Call Type {MO, MT}
Call Blocked F On CC Id, CC Cause
Call Dropped F On CC Id, CC Cause
Call End N Off CC Id, CC Cause
LZT 138 0240 R2A 103

Call Established N Off CC Id
10.5.2. MM Events
For values of MM Cause, see appendix A.10.
Auth. Failure F On MM Cause

(Authentication Failure)
Auth. Reject F On Constant string: “No SIM or

(Authentication Reject) IMSI not approved”
LAU Attempt N Off LA Update Type {Normal,

(Location Area Update Periodic, IMSI Attach,
Attempt) Combined, Invalid}
LAU Failure F On MM Cause

(Location Area Update
Failure)
LAU Reject F On MM Cause

(Location Area Update
Reject)
LAU Success N Off Previous Location Area, LA

(Location Area Update Update Type (if = Combined)
Success)
MM Reg. Eq. N On –
(MM Registered
Equivalent PLMN)
MM Reg. Home N On –
(MM Registered Home
PLMN)
104
MM Reg. Roaming N On –
(MM Registered Roaming
PLMN)
MM Unregistered N On –
10.5.3. SM Events
For values of SM Cause, see appendix A.17.
PDPCtx Act. Att. N Off NSAPI

(PDP Context Activation
Attempt)
PDPCtx Act. Cpl. N Off NSAPI, IP version {4, 6}, PDP

(PDP Context Activation address (IPv4 only)
Complete)
PDPCtx Act. Rej. F On NSAPI, SM Cause

(PDP Context Activation
Reject)
PDPCtx Deact. Att. N Off NSAPI

(PDP Context
Deactivation Attempt)
PDPCtx Deact. Cpl. N Off NSAPI, Type {NW, UE}, SM

(PDP Context Cause (if Type = NW)
Deactivation Complete)
LZT 138 0240 R2A 105

10.5.4. GMM Events

For values of GMM Cause, see appendix A.7.
GMM Attach Att. N Off Attach type: {GPRS,

(GMM Attach Attempt) Combined}
GMM Attach Cpl. N Off Attach type: {GPRS,

(GMM Attach Complete) Combined}
GMM Attach Fail. F On “T3310 expired” or GMM

(GMM Attach Failure) Reject Cause
GMM Detach Att. N Off GMM Cause

(GMM Detach Attempt)
GMM Detach Cpl. N Off GMM Cause, Type {NW, UE}

(GMM Detach Complete)
RAU Attempt N Off RA Update Type {Normal,

(Routing Area Update Periodic, Combined}
Attempt)
RAU Complete N Off Old RA, New RA

(Routing Area Update
Complete)
RAU Reject N On Timer Event {True, False},

(Routing Area Update T3330/GMM Reject Cause
Reject)
106
10.5.5. IRAT Events
G2U Cell Ch. Att. N Off BCCH ARFCN, BSIC

(GSM To UTRAN Cell
Change Attempt)
G2U Cell Ch. Fail. F On BCCH ARFCN, BSIC

(GSM To UTRAN Cell
Change Failure)
G2U Cell Ch. Succ. N Off New UARFCN, New SC

(GSM To UTRAN Cell
Change Success)
G2U HO Attempt N Off BCCH ARFCN, BSIC

(GSM To UTRAN
Handover Attempt)
G2U HO Failure F On BCCH ARFCN, BSIC

(GSM To UTRAN
Handover Failure)
G2U HO Success N Off New UARFCN, New SC

(GSM To UTRAN
Handover Success)
U2G Cell Ch. Att. N Off UARFCN, SC

(UTRAN To GSM Cell
Change Attempt)
U2G Cell Ch. Fail. F On UARFCN, SC

(UTRAN To GSM Cell
Change Failure)
U2G Cell Ch. Succ. N Off New BCCH ARFCN, New

(UTRAN To GSM Cell BSIC
Change Success)
U2G HO Attempt N Off UARFCN, SC

(UTRAN To GSM
Handover Attempt)
LZT 138 0240 R2A 107

U2G HO Failure F On UARFCN, SC

(UTRAN To GSM
Handover Failure)
U2G HO Success N Off New BCCH ARFCN, New

(UTRAN To GSM BSIC
Handover Success)
10.5.6. RR Events
For values of RR Cause, see appendix A.13.
For values of RR Internal Cause, see appendix A.14.
GPRS Pkt. Acs. Fail. F On BCCH ARFCN, BSIC, RR

(GPRS Packet Access Cause
Failure)
GPRS Retrans. PRR F On BCCH ARFCN, BSIC

(GPRS Retransmit
Packet Resource
Request)
GSM Assign. Fail. F On RR Cause, RR Internal Cause

(GSM Assignment
Failure)
GSM Datalink Timeout F On Target BCCH ARFCN, BSIC,

TO value
GSM HO Failure F On BCCH ARFCN, BSIC, RR

(GSM Handover Failure) Internal Cause
GSM RL Timeout F On BCCH ARFCN, BSIC, Radio

(GSM Radio Link Link Timeout Counter (Max)
Timeout)
108
Imm. Assign. Fail. F On BCCH ARFCN, BSIC, RR

(Immediate Assignment Internal Cause
Failure)
Imm. Assign. Rej. F On BCCH ARFCN, BSIC, RR

(Immediate Assignment Internal Cause
Reject)
RAT: GSM N On –
RAT: No Service F On –
10.5.7. RRC Events

For values of RRC Failure Cause, see appendix A.15.
For values of RRC Protocol Error Cause, see appendix A.16.
Act. Set Upd. Fail. F On UARFCN, SC, RRC Failure

(Active Set Update Cause
Failure)
Inter-Freq. Cell N Off New UARFCN, New SC

Reselection
(Inter-frequency Cell
Reselection)
Inter-Freq. HO Failure F On UARFCN, SC

(Inter-frequency
Handover Failure)
Inter-Freq. HO Success N On New UARFCN, New SC

(Inter-frequency
Handover Success)
Phy. Ch. Est. Fail. F On UARFCN, SC

(Physical Channel
Establishment Failure)
LZT 138 0240 R2A 109

RAT: WCDMA N On –
RB Reconf. Fail. F On UARFCN, SC, RRC Failure

(Radio Bearer Reconfig- Cause
uration Failure)
RB Setup Fail. F On UARFCN, SC, RRC Failure

(Radio Bearer Setup Cause
Failure)
RRC Conn. Fail. F On UARFCN, SC, RRC Failure

(RRC Connection Cause
Failure)
RRC Prot. Error F On UARFCN, SC, RRC Protocol

(RRC Protocol Error) Error Cause
RRC RL Fail. F On UARFCN, SC

(RRC Radio Link Failure)
10.5.8. Session Events

For values of Automatic Upload Failure Cause, see appendix A.2.
Auto. Upload End N L Upload bearer (cellular/WiFi)

(Automatic Upload End)
Auto. Upload Fail. F L Automatic Upload Failure

(Automatic Upload Cause, Upload bearer
Failure)
Auto. Upload Start N L Upload bearer

(Automatic Upload Start)
FTP Transfer End N On File name, File size, Duration,

Bit rate UL, Bit rate DL
FTP Transfer Fail. F On –

(FTP Transfer Failure)
110
FTP Transfer Start N On –
GPS Conn. Found N On –

(GPS Connection Found)
GPS Conn. Lost F On –

(GPS Connection Lost)
GPS Loc. Found N On –

(GPS Location Found)
GPS Loc. Lost F On –

(GPS Location Lost)
Video Call End N Off –
Video Call Fail. F Off –

(Video Call Failure)
Video Call Start N Off –
Voice Call End N Off –
Voice Call Fail. F Off –

(Voice Call Failure)
Voice Call Start N Off –
LZT 138 0240 R2A 111

11. Data Views Menu
From this menu you control what data views should be visible as you browse
through them. In the menu, the data views are organized in a multi-tab
structure with one tab for each data view category.
Toggle: Press this button to toggle the visibility for

the selected data view on and off.
Go to: Press this bottom to immediately display the
selected data view and exit the Data Views menu.
The Set all command (at the bottom of each tab) sets the visibility for all data
views in the group. Note that this command never has a preset value: the
submenu with the choices On and Off has no radio buttons.
If you perform the Go to action for a data view whose visibility is currently set
to Off, the view is shown just this once; if you browse to a different view and
then back again, the hidden view will be skipped. To make the view
permanently visible again you must press Toggle to set its visibility to On.
If you turn off visibility for all data views, one data view will still remain visible
as you exit the menu system, namely the one you last accessed. If you do in
fact want to hide all data views, you should not edit these settings but rather
put TEMS Pocket in background or inactive mode: see section 7.1.
112
Chapter 12. GPS Menu
12. GPS Menu
12.1. Using GPS Units with TEMS Pocket:

Introduction
Using a GPS device with TEMS Pocket enhances compatibility with products
such as TEMS Investigation and TEMS Automatic/TEMS Presentation by
allowing TEMS Pocket data to be presented on maps.
The GPS menu is used to control the choice of GPS device and various
aspects of how to interact with it. Sections 12.2–12.4 below cover the
submenus of the GPS menu.
You can export your GPS settings to file; they are included in the Export
12.1.1. Using the Built-in GPS

The Sony Ericsson W995 and W995a phones have a built-in GPS, and
TEMS Pocket can make use of this device for positioning. Access to the built-
in GPS is included in the TEMS Pocket standard package.
To be available to TEMS Pocket, the built-in GPS must be enabled in the
regular phone user interface. In the phone’s main menu, navigate to Location
services → Settings and check that the third item in this submenu reads
“Disable GPS”, i.e. the GPS is currently enabled. (It is by default.) If
necessary, enable the GPS.
Whenever the built-in GPS is active, this icon from the regular phone
interface appears at the top of the display.
By default the phone also has the option Location services → Settings →
“Assisted start” activated. This means that the phone will use the Assisted
GPS (A-GPS) technology to reduce the time taken to obtain a first GPS fix.
The positioning accuracy, on the other hand, does not change.
Since the phone’s use of A-GPS involves contacting a Sony Ericsson specific
“assistance server”, the phone must have a functioning data account defined,
in the same way as for WAP.
LZT 138 0240 R2A 113

The built-in GPS consumes a large amount of power and thus requires
frequent charging of the phone battery. See section 21.2 for some further
specifics on this matter.
12.1.2. Using an External GPS

TEMS Pocket can also connect to an external (Bluetooth) GPS. This
functionality, too, is part of the standard TEMS Pocket package.
You can connect to any Bluetooth GPS device that uses Bluetooth version
1.1 or later, SPP (Serial Port Profile) version 1.1, and NMEA-0183 version 2.2
or later. Bluetooth pairing is handled from within TEMS Pocket: see section
12.3.
The “Assisted start” option (see section 12.1.1) cannot be combined with an
external GPS.
12.2. GPS Connect

Manual: At the outset no GPS is connected. This is
the default setting. You can connect the phone
manually to a GPS (internal or external) by using
the command in the Activity menu (see section
7.8). If a manual connect fails, an error message is
displayed.
Automatic: When you switch from Manual to
Automatic, the following applies: If “GPS device”
(see section 12.3) is set to Internal, or if “GPS
device” is set to Bluetooth and you successfully
paired a GPS with the phone when you last did a
Bluetooth device search, then the phone will
immediately try to connect to the selected GPS.
The same thing will happen later on each time the
phone is power cycled.
If an automatic connect fails, the phone will do a
retry once every minute until it succeeds. No error
messages are given in this case.
Note that you must choose your “GPS device” setting while “GPS connect” is
set to Manual (see section 12.3).
Switching between the options Manual and Automatic disconnects a GPS
that is currently connected.
114
Chapter 12. GPS Menu
12.3. GPS Device

Here you select what kind of GPS device TEMS
Pocket should use. If you have selected Automatic
under “GPS connect”, however (see section 12.2),
the GPS device dialog is not accessible.
Internal: TEMS Pocket will use the phone’s
internal GPS.
Bluetooth: When you select this, TEMS Pocket
will start searching for available Bluetooth devices.
The found devices are listed on the screen shown
below.
Here are listed all Bluetooth devices that have

been found in the search. Note: In the list may
appear all kinds of Bluetooth compatible devices,
i.e. also devices other than GPS units.
• Among the devices found, select the GPS you
want to connect to. The phone will then attempt
Bluetooth pairing with the selected device. You
will be asked for a passcode.
The Connect GPS command in the Activity menu
(see section 7.8) will always apply to the Bluetooth
device last paired with the phone as just described.
If you want to refresh the search for Bluetooth
devices, you can do so at any time by selecting the
Bluetooth option again.
LZT 138 0240 R2A 115

12.4. GPS Time Synch

If this is set to On, the phone clock will be
synchronized with the GPS time. This is useful for
instance if you are going to upload TEMS Pocket
logfiles to a TEMS Automatic database.
Note: For this synchronization to work, it is vital
that the time zone has been correctly set on the
phone.
116
Chapter 13. FTP Menu
13. FTP Menu
In this menu you specify FTP servers that the phone is going to interact with
(whether for FTP testing or for logfile upload). Here you also set up FTP Put/
Get operations to perform during testing.
You start and stop FTP testing from the Activity menu: see section 7.7.
You can export your FTP settings to file; they are included in the Export
13.1. FTP Transfer

Here you define FTP Put and FTP Get operations. Up to ten operations can
be defined. At the outset they are simply numbered from 1 to 10 in the user
interface; you get the opportunity to name the operations while defining them
(see below).
• Select a number to define the corresponding

FTP operation.
LZT 138 0240 R2A 117

Name: Text field for labeling the FTP operation.

Direction: Select FTP Put or FTP Get. The
remaining parameters are partly different for the
two types of operation:
FTP Put Specific Parameters

Local file: Browse to select the file to be uploaded.
Remote directory: Name of directory where the
file should be stored on the FTP server.
FTP Put parameters
FTP Get Specific Parameters
Remote file: Path describing the location of the file
to get on the FTP server. A leading slash may be
used as root symbol but is not mandatory.
Save file to: The downloaded file can be written
either to the phone memory or to the memory stick.
In either case, files are stored in the directory
Other.
If the phone runs out of memory during an FTP Get
FTP Get parameters operation, the operation will complete, but no file
will be stored in the phone file system.
Common Parameters
FTP server: Specify the FTP server to interact
with: one of those defined in the FTP server
submenu (see section 13.2).
Note that the file used for upload or download must not be larger than about
500 MB, or the FTP Data view (see section 4.5) will not show correct values
for the mean data transfer rate.
Once you are done setting up an FTP operation, its name and direction, the
server to interact with, and the file to put/get will appear in the FTP transfer
list:
118
Chapter 13. FTP Menu
13.2. FTP Server

Here you specify FTP servers and how to access them. Up to ten FTP
servers can be defined. At the outset they are simply numbered from 1 to 10
in the user interface; you get the opportunity to name the servers while
defining them (see below).
• Select a number to define the corresponding

FTP server.
Name: Text field for labeling the FTP server.

Remote address: The IP address or host name of
the FTP server. The address may not contain a
path to a subdirectory.
Port: The FTP server port. The default is 21.
FTP user: User name on the FTP server, if
required.
FTP password: User password on the FTP server,
if required.
LZT 138 0240 R2A 119

Remote directory: This parameter applies to

logfile upload only; it names the directory where the
logfiles should be stored on the FTP server. When
you perform a manual FTP Put operation, this
parameter is overridden by the identically named
parameter in the FTP Put command (see section
13.1).
Data account: Select the data account that should
be used for the FTP session.
Fixed timeouts (not user-configurable) are used when establishing the dialup
connection (60 s) and when setting up the FTP session itself (60 s). Failure to
obtain a response from the FTP server within the latter time period results in
“FTP session error”.
120
Chapter 14. Logfile Menu
14. Logfile Menu
14.1. Logfiles in TEMS Pocket: Introduction

TEMS Pocket can record its measurements in logfiles, containing the same
richness of detail as logfiles recorded with TEMS Automatic test units or with
terminals connected to TEMS Investigation.
Logfiles are stored either in the internal phone memory or on a memory stick
(see section 14.2 below). Logfiles are ordinary files in the phone file system
and can be handled from the File manager.
You can record logfiles manually in the following ways:
• By using commands in the Activity menu. See section 7.3.
• In connection with pinpointing in the Map view. See chapter 6.
You can also configure TEMS Pocket to trigger automatic recording of
logfiles in a number of situations. This is known as “passive measurement”
and is covered in chapter 16.
Regarding logfile naming, see section 14.1.1.
TEMS Pocket has a logfile replay function, described in section 7.4. Other
ways to study TEMS Pocket 7.3 logfiles are to transfer them to a PC and
open them in other TEMS products:
• TEMS Investigation, version 11.0 or later
• TEMS Automatic, version 8.1 or later/TEMS Presentation, version 2.1 or
later
• TEMS Discovery, version 2.0 or later.
TEMS Pocket is capable of uploading logfiles to an FTP server, using the
built-in FTP client, in the following ways:
• Over the cellular network. See section 14.3.
• Over WiFi. See section 14.4.
In order to reduce FTP transfer times, you can opt to compress logfiles prior
to upload. This is dealt with in section 14.5.
LZT 138 0240 R2A 121

It is of course also possible to transfer logfiles via USB or Bluetooth, or to

send them as attachments to e-mail.
You can export all logfile-related settings to file; they are included in the
Export settings operation (Tools menu: see section 17.4).
Sections 14.2–14.7 below cover the submenus of the Logfile menu.
14.1.1. Logfile Naming Format

All logfiles recorded by TEMS Pocket are named according to the syntax
<Status>_<Type>_[<Tag>_]<Date>_<Time>.log
where the components have the following meanings:
<Status>
S Measurements successful
F Measurements failed
No status is given for manually recorded logfiles or for logfile recordings

triggered at phone startup (since in these cases there are no particular
measurements associated with the recording).
<Type>
voice_a Active voice measurement
voice_p Passive voice measurement
video_a Active video call measurement
video_p Passive video call measurement
FTP_a Active FTP measurement
FTP_p Passive FTP measurement
HTTP_a Active HTTP measurement
HTTP_p Passive HTTP measurement
stream_a Active streaming measurement
stream_p Passive streaming measurement
idle_a Active idle measurement
startup_p Passive startup measurement
manual Manual logfile recording
122
<Tag>
tag Tag attached by user (see section 7.5)
– (empty) No tag attached by user
<Date>
YYYY-MM-DD: Year, month, day
<Time>
HH.MM.SS: Hours, minutes, seconds
14.1.1.1. Examples
• f_voice_p_2010-02-03_16.53.02.log
• manual_2010-02-03_16.53.02.log
• startup_2010-02-03_16.53.02.log
• s_FTP_a_tag_2010-02-03_16.53.02.log
14.2. Save Logfile To

Phone memory: Logfiles are saved to the phone
memory, directory Other\Pocket\Pro.
Memory stick: Logfiles are saved to the memory
stick, directory Other\Pocket\Pro, provided that the
phone has got a memory stick installed. Sony
Ericsson phones support Memory Stick M2.
14.3. Upload Logfile

Here you configure automated uploading of logfiles over the cellular network,
using the FTP protocol, to an FTP server. What server to upload to is
selected in the FTP server submenu: see section 14.7.
Upload over cellular may be regarded as the “standard” logfile upload method
in TEMS Pocket. Alternatively, it is possible to upload files over WiFi if a WiFi
access point is available. See section 14.4.
LZT 138 0240 R2A 123

Immediate: Selecting this does not literally trigger

an upload immediately. Rather, the setting has this
effect:
• The next time you record a logfile, the logfile
will be uploaded immediately at that time, along
with any other logfiles that are stored on the
storage medium.
• Subsequently, as long as Immediate remains
selected, every new logfile will be uploaded as
soon as it has been recorded.
Schedule: Logfiles are uploaded according to a
schedule that you define here. Select this option to
go to the Start time screen, then turn to section
14.3.2.
Each time an upload is performed, all logfiles are
transferred that have not yet been transferred
(logfiles created since the last upload, plus any
older logfiles that may remain because you aborted
uploading of these files).
Off: No automated uploading. Logfiles are simply
stored in the phone memory or on the memory
stick as long as free space is available. Use this
setting if you prefer to upload logfiles manually
using the FTP Put command (see section 7.7).a
a. There is yet another way to upload logfiles manually, using a command

accessed from the phone file system. See chapter 20.
A set of events is provided reporting on the progress and outcome of each

upload. See section 10.5.8.
14.3.1. Conflicts with Other TEMS Pocket Functions

While a command sequence is executing, logfiles cannot be uploaded in any
of the ways described in section 14.3. Logfile uploads may however still
occur, namely if initiated by the command sequence itself (Upload flag set in
command sequence settings: see section 15.2.1). Like any other upload, an
upload governed by a command sequence will transfer all logfiles stored in
124
the logfile folder, including any remaining older files that were not produced
by the command sequence.
While logfile replay is in progress, no logfile uploads can occur.
If, during command sequence execution or logfile replay, a logfile upload
comes due according to the upload schedule defined, the upload is
postponed until the conflicting activity has ended. Afterwards the phone
reverts to following the upload schedule.
14.3.2. Setting an Upload Schedule

Step 1
Now: Choose this option to perform the first upload

right away (as soon as you are done setting up the
schedule). Skip to Step 3 below.
00:00: Choose this option to specify a time of day
when the first upload should be performed.
Step 2
If you chose “00:00” in Step 1, set the upload time

here.
LZT 138 0240 R2A 125

Step 3
Set the interval between uploads. None means

that only a single upload will be performed.
Press Select to complete the schedule setup. If you
chose Now in Step 1, the upload will start
immediately; otherwise it will start at the scheduled
time.
You can abort an upload in progress by using the
Stop FTP Put command in the Activity menu (see
section 7.7). If you abort an upload, the files that
were not transferred will be included in the next
upload.
14.4. WiFi Upload

As an alternative to uploading via the cellular network, it is possible to
perform logfile upload over a WiFi access point if one is available. The
protocol used is FTP in this case as well.
The TEMS Pocket phone is capable of searching for available WiFi networks.
• To enable WiFi upload, navigate to Menu → Settings → Connectivity →
WiFi, select the WiFi network you want to connect to, and press Options
→ Connect.
• After connecting, the choice “Auto connect” becomes available. Choosing
that option causes the phone to connect automatically to this WiFi access
point on future occasions.
To make use of WiFi for logfile upload, you then need to enter the WiFi upload
menu and make the appropriate selection:
126
Immediate: Selecting this does not literally trigger

an upload immediately. Rather:
• If the phone has a WiFi connection, and you
record a new logfile, the logfile will be uploaded
immediately at that time, along with any other
logfiles that are stored on the storage medium.
• If the phone does not have a WiFi connection,
but later finds a WiFi network and connects to
it, then all logfiles stored on the storage
medium will be uploaded immediately at that
time.
Subsequently, as long as Immediate remains
selected and the WiFi connection is maintained,
every new logfile will be uploaded over WiFi as
soon as it has been recorded. In this situation, WiFi
upload always has priority over upload via the
cellular network.
Once: This choice has the following effect:

• If the phone has a WiFi connection when you
select Once, a logfile upload will be performed
immediately, transferring all logfiles that are
stored on the storage medium.
• As long as Once remains selected, one logfile
upload will be performed each time a new
connection to a WiFi network is made.
All other uploads, however, will take place over the
cellular network.
The “Once” mechanism can for example be used to
have logfiles automatically uploaded whenever you
return from a drive testing session to the office and
the coverage of the office WLAN.
Off: No logfile uploading will be done over WiFi.
A set of events is provided reporting on the progress and outcome of each

upload. See section 10.5.8.
LZT 138 0240 R2A 127

14.4.1. Relation to Upload over Cellular Network

If you initiate WiFi uploading while an upload over the cellular network is in
progress, the upload over cellular is not affected.
If a schedule for upload over cellular is in place (defined according to section
14.3.2), and you set “WiFi upload” to Immediate, TEMS Pocket will switch to
WiFi upload as described in section 14.4, but it will also continue to keep
track of the timer for upload over cellular. This allows TEMS Pocket to fall
back on the upload-over-cellular schedule in case the WiFi connection is lost.
If upload over cellular and WiFi upload are both set to Immediate, WiFi
uploading will take precedence, as pointed out in section 14.4. However, after
each WiFi upload, an upload over cellular will follow. The latter will be
noticeable only as an “Auto. Upload Fail” event with cause = “No files to
upload” (see section 10.5.8 and appendix A.2), provided that the WiFi upload
completed normally. On the other hand, if the WiFi upload was for some
reason aborted before all logfiles had been transferred, the upload over
cellular will take care of transferring the remaining files.
14.4.2. Conflicts with Other TEMS Pocket Functions

While a command sequence is executing, the only logfile uploads that can
occur are ones initiated by the command sequence itself (Upload flag set in
command sequence settings: see section 15.2.1). Like any other upload, an
upload governed by a command sequence will transfer all logfiles stored in
the logfile folder, including any remaining older files that were not produced
by the command sequence currently running.
While logfile replay is in progress, no logfile uploads can occur.
128
14.5. Compress
If set to On, logfiles will be compressed using a
Huffman coding algorithm before they are
uploaded.a
If compression is turned on, it will take place
regardless of the upload bearer chosen and the
upload settings made (see sections 14.3 and 14.4).
However:
• After an automatic upload, the original
uncompressed logfile (as well as the
compressed version) will be deleted from the
phone file system.
• After a manual upload initiated by a Start FTP
command (section 7.7), the original logfile will
remain on the phone.
a. Compressed logfiles receive the extension .LZZ; this is a TEMS-specific

extension recognized by the automated logfile handling in TEMS
Presentation. If you wish to unpack uploaded logfiles manually on the
FTP server, for example using gzip, replace “.LZZ” by “.log.gz” in each
file. (Replaying TEMS Pocket logfiles in TEMS Investigation currently
requires the logfiles to be unpacked.)
It should be pointed out that compression of large logfiles takes considerable

time and that all logfiles to be uploaded in the same batch are compressed
before any uploading begins. (It is possible to abort an upload at any time.)
If the FTP transfer fails, for example because the FTP transfer setup in TEMS
Pocket is faulty, then the logfiles will remain compressed and included in the
first subsequent upload that succeeds.
LZT 138 0240 R2A 129

14.6. FTP Resume

If set to On, then if a logfile upload is interrupted
because the FTP connection goes down, the
upload will be resumed from the point where it was
interrupted.
If set to Off, an interrupted logfile upload will be
restarted from the beginning.
For the function to work, the FTP server must
support resume functionality.
14.7. FTP Server

Here you select a FTP server to upload logfiles to.
The servers listed are those that you define in the
FTP menu (see section 13.2). Note that the
Remote directory parameter must have a valid
value for any server that is going to be used for
logfile uploads.
130
Chapter 15. Command Sequence Menu
15. Command Sequence Menu
15.1. Introduction to Command Sequences

Command sequences are used to automate testing of services. The
following services and tasks are supported by the command sequence
function:
• Voice calls
• Video calls
• FTP data transfers (Put/Get)
• HTTP data transfers
• Video streaming
• Wait in idle mode
You can have the execution of a command sequence recorded automatically
in a logfile. It is also possible to have that logfile uploaded automatically, over
either the cellular network or WiFi, every time the sequence has completed.
Cell control functions can be activated by a command sequence for the
duration of the sequence. The effects of these control functions are precisely
the same as when the functions are activated manually (see chapter 9).
You start and stop a command sequence from the Activity menu: see
section 7.9. When the command sequence is executed, its actions are
performed one after another in the order they have been defined. Once
started, the sequence repeats until you stop it, unless some event such a low
battery condition occurs.
Command sequence setups can be exported to file and imported back into
the application. The setups are included in the Export settings operation
(Tools menu: see section 17.4).
Note: Running a command sequence for extended periods of time

places a high load on the phone battery. See section 21.3 for
advice on how to ensure that the battery is not drained.
LZT 138 0240 R2A 131

15.2. Defining Command Sequences

In this menu you define the contents of command sequences. Up to ten
sequences can be defined. At the outset they are simply numbered from 1 to
10 in the user interface; you get the opportunity to name the sequences while
defining them (see below)
• Press Edit to define a new command sequence.
15.2.1. Global Command Sequence Settings

These settings apply to the command sequence as a whole.
Name: Text field for naming the command

sequence.
Record: This option governs whether to record the
execution of the command sequence in logfiles. If
the option is set, a new logfile is recorded for each
action that is run.
Upload: If you set this to On, a logfile upload will
be performed after each execution of the command
sequence. If the Record option is turned off, the
Upload option is disabled and grayed, and no
uploads will take place.
132
Store logfiles with: These settings control

whether logfiles recorded when running the
command sequence will be saved or not.
• Success: Save logfiles where the measurement
succeeded.
• Failure: Save logfiles where the measurement
failed.
• Abort: Save logfiles where the measurement
was aborted by the user.
• Tag: Save logfiles that are manually tagged by
the user. Note: The tagging function (see
section 7.5) will be enabled during command
sequence execution only if you check this
option. Therefore, a tagged logfile will always
be saved.
The first three conditions are mutually exclusive,
and they are jointly in an OR relationship with the
Tag condition. For example, if you check Failure
and Tag, a logfile will be saved if the measurement
failed or the logfile has been tagged.
GPS: This option has an effect only if “GPS

connect” is set to “Manual” in the GPS menu (see
section 12.2). If that is so, the option described
here governs whether to make use of a GPS
device. If the option is set, and no GPS is
connected as the command sequence starts,
TEMS Pocket will connect to the GPS for the
duration of the sequence, then disconnect the GPS
after the sequence has stopped.
If “GPS connect” is set to “Automatic” in the GPS
menu, any GPS that is present will always be
connected, and the command sequence option has
no effect.
Actions: Select this item to define the actions the

command sequence should perform. See below.
LZT 138 0240 R2A 133

15.2.2. Adding an Action to a Command Sequence

• Select <Add action> to define a new action.
Here you select the type of task to perform in the

action; one of:
• Voice call
• Video call
• FTP transfer (Put or Get)
• HTTP
• Streaming
• Idle (wait in idle mode)
The new action is added to the sequence.

• With the new action selected, press Select to
configure settings for the action.
The settings for the various action types are
covered in the subsections that follow.
134
15.2.3. Voice Action Settings

Dial number: The number to call. Valid characters
are: +, #, *, 0, ..., 9, and p (for pause).
Call duration: The duration in seconds of the voice
call.
Guard time: The time in seconds to spend in idle
mode upon completion of the voice call, i.e. the
time to wait before starting the next action in the
sequence. During the guard time, no logfile
recording occurs.
Redial: If this is set On, the phone will
automatically redial mobile-originated calls that
were abnormally disconnected (neither party
intentionally ended the call).a
Cell control: Here you can specify one or several
cell control functions, for example band and/or cell
lock, that will apply for the duration of the action
and then be released. This works exactly the same
way as manual cell control (except for the scope
being limited in time); see chapter 9 for details.
a. In case of a blocked call, up to three retries are made, provided that at

least 10 s remain of the specified call duration. If a call is dropped, it is
retried repeatedly as long as at least 10 s remain of the call duration.
LZT 138 0240 R2A 135

15.2.4. Video Action Settings

Dial number: The number to call. Valid characters
are: +, #, *, 0, ..., 9, and p (for pause).
Call duration: The duration in seconds of the
video call.
mode upon completion of the video call, i.e. the
sequence.
Redial: If this is set On, the phone will
automatically redial mobile-originated calls that
were abnormally disconnected (neither party
intentionally ended the call).a
Cell control: See section 15.2.3.
a. In case of a blocked call, up to three retries are made, provided that at

least 10 s remain of the specified call duration. If a call is dropped, it is
retried repeatedly as long as at least 10 s remain of the call duration.
15.2.5. FTP Action Settings

Transfer ID: Selecting this item takes you to a new
dialog listing all FTP transfers that are currently
defined in the FTP menu (see section 13.1). Select
which transfer to perform.
mode upon completion of the FTP session, i.e. the
sequence.
136
15.2.6. HTTP Action Settings

be used for the HTTP session.
mode upon completion of the HTTP session, i.e.
the time to wait before starting the next action in
the sequence.
URL: The URL or IP address of the HTTP server to
download from. The maximum URL length is 255
characters.
Not all web pages are suitable for HTTP testing. Very large pages should be
avoided, as should pages that contain many Java scripts. The reason is that
with such pages the browser will spend most of its time parsing HTML and
stylesheets or running Java scripts instead of downloading data, which
means that the average throughput will be very low. In addition, the parsing
and script execution may take such a long time that TEMS Pocket aborts the
action1, or the browser may run out of memory and abort the download.
1. This is governed by an internal timeout which is not user-configurable.
LZT 138 0240 R2A 137

15.2.7. Streaming Action Settings

Streaming sessions are conducted over RTSP using the phone’s integrated
media player.
be used for the streaming session.
mode upon completion of the streaming session,
i.e. the time to wait before starting the next action in
the sequence.
URL: The URL or IP address of the streaming
server to download from. The maximum URL
length is 255 characters.
Audio: You can mute the audio from the media
player during the streaming session by choosing
Off here.
Video: Here you select whether to show or hide
the media player during the streaming session.
Max time: The maximum duration of the streaming
session.
15.2.8. Idle Action Settings

Duration: The length of time (in seconds) the
phone should spend in idle mode.
138
15.2.9. Pre-guard and Post-guard Periods

For all action types except Idle, pre-guard and post-guard periods of fixed
length (both 10 s) are inserted before and after the measurement,
respectively. These guard periods are included in the logfile, and their
purpose is to capture the signaling taking place in connection with service
setup and termination.
15.2.10. Saving Default Settings for an Action Type

Pressing the “Save def.” button in an action settings dialog saves the current
settings as defaults for this action type. The next time you define an action of
the same type, the dialog will be populated with the default settings.
Default settings for actions are saved in the phone’s internal memory.
Note that you do not have to press the “Save def.” button for the action itself
to be saved. That is taken care of automatically, without the need for any
special user operation. If you press Back and return later to edit the action,
the settings you last made remain in the dialog.
15.2.11. The Assembled Command Sequence

• Once you are done setting up an action, simply press Back to return to the
list of actions in the command sequence. See the example below.
15.2.12. Rearranging Actions in a Command Sequence

• To move an action to a different position in a command sequence, select
the action, press Options, and select Move. Then use the navigation key
to move the action up or down in the sequence. When the action has
reached the desired position, press End Move to leave it there.
LZT 138 0240 R2A 139

15.2.13. Deleting an Action from a Command Sequence

• To delete an action from a command sequence, select the action, press
Options, and select Delete. Alternatively, you can press the C button on
the keypad. You will be prompted to confirm removal of the action.
15.3. Viewing and Editing Command Sequences

Once you have defined a command sequence, when you return to the Cmd
sequences dialog and select that sequence, the middle soft button will read
“View” instead of “Edit”. Pressing View displays an overview of the selected
command sequence in the format shown below.
To edit a command sequence, select it and press View to access the

overview screen; then press Edit. See section 15.2 for all details on settings.
15.4. Deleting Command Sequences

• To delete a command sequence, select it in the Cmd sequences dialog
and press Delete. Alternatively, you can press the C button on the keypad.
You will be prompted to confirm removal of the command sequence.
15.5. Running Command Sequences

Command sequences are run from the Activity menu. See section 7.9.
140
Chapter 16. Passive Measurement Menu
16. Passive Measurement Menu
You can configure logfile recording to start and stop automatically in certain
situations. This mode of measurement is referred to as passive mode, since
the measurement is triggered by user actions in the regular phone interface
rather than being initiated actively by TEMS Pocket.
Below it is indicated when the passive measurement terminates. With the
exception of passive measurements triggered by the Startup option, you
cannot stop the logfile recording manually from the Activity menu (see section
7.3).
Startup: Logfile recording starts automatically when

the phone is powered on and continues until it is
powered off.
Voice: Logfile recording starts automatically at the
start of a voice call and stops at the end of that call.
Video: Logfile recording starts automatically at the
start of a video call and stops at the end of that call.
FTP: Logfile recording starts automatically at the
beginning of an FTP testing session (initiated by the
Start FTP command in the Activity menu: see
section 7.7) and stops at the end of that session.
(Recording is not triggered by uploading logfiles via
FTP.)
HTTP: Logfile recording starts automatically at the
beginning of an HTTP session (initiated by the user
launching the web browser) and stops at the end of
that session.
Streaming: Logfile recording starts automatically at
the beginning of a streaming session (initiated by
the user clicking a streaming video link or selecting
a bookmark containing such a link) and stops at the
end of that session.
LZT 138 0240 R2A 141

• Press Mark to check an action type.

• Press Unmark to uncheck an action type that is currently checked.
• Select an action type and press Edit to configure settings for that action
type. See section 16.1 below.
16.1. Passive Measurement Action Settings

These settings are provided for all actions:
• Duration: Specify the maximum duration (in seconds) of the passive
measurement. If the call or session progresses beyond this point, the
measurement is terminated. The call or session itself continues
undisturbed.
• GPS: This option governs whether to capture positioning data from a GPS
device (see chapter 12). If this option is set, and no GPS is connected as
the passive measurement is triggered, TEMS Pocket will connect to the
GPS for the duration of the measurement. When the passive
measurement has stopped, the GPS will be disconnected again.
This setting is provided for all actions except Startup:

• Store logfiles with: These settings control whether logfiles recorded
during passive measurement will be saved or not.
– Success: Save logfiles where the measurement succeeded.
– Failure: Save logfiles where the measurement failed.
– Abort: Save logfiles where the measurement was aborted by the user.
– Tag: Save logfiles that are manually tagged by the user. Note: The
tagging function (see section 7.5) will be enabled during passive
measurement only if you check this option. Therefore, a tagged logfile
will always be saved.
The first three conditions are mutually exclusive, and they are jointly in an
OR relationship with the Tag condition. For example, if you check Failure
and Tag, a logfile will be saved if the measurement failed or the logfile has
been tagged.
This setting is provided for HTTP and streaming:

• Privacy: If you set this to On, no information on what URLs are visited
appears in the Session Reports recorded in logfiles.
142
Chapter 16. Passive Measurement Menu
16.2. Prioritization of Passive Measurements

Passive measurements are conducted on a “first come, first served” basis.
This means that (leaving aside the Startup option) the first service that is
started will trigger a measurement, and that measurement will continue until
the same service is taken down. Only then will any notice be taken of the use
of other services: the next service started after that point will trigger another
passive measurement, and so on.
One special limitation needs to be mentioned: If you want to make passive
measurements for streaming, you cannot also have HTTP selected as a
trigger of passive measurements. This is because the only way for the phone
user to start a streaming session is from the web browser (by selecting a
bookmark or by clicking a streaming link on a web page), and as soon as the
web browser is launched, that occurrence will trigger passive measurement
for HTTP. The streaming service will thus never be in a position to trigger
measurement, because of the “first come, first served” principle just
explained. To conduct streaming measurements, you need to deselect HTTP.
16.3. Notes on Message Buffering
16.3.1. Pre-guard Period

If at least one of the options other than Startup is checked in the “Passive
measurement” dialog, then the phone will continuously maintain a buffer
holding the most recent signaling (up to 10 seconds’ worth of it). This is to
ensure that when passive measurement is triggered, the file will capture as
much as possible of the signaling leading up to the establishment of the call
or data session. The arrangement thus serves the same purpose as the pre-
guard period set in TEMS Automatic work order actions. In TEMS Pocket the
length of the pre-guard cannot be customized; the exact period of time
spanned by the message buffering depends on the amount of signaling that
has occurred.
The buffering makes the logfile more complete not only for mobile-terminated
(MT) but also for mobile-originated (MO) calls and data sessions. This is
because in the MO case, the recording does not begin instantly as the user
initiates the service from the phone keypad, but only after a certain delay (the
exact details being service-specific).
Selecting the Startup option does not trigger buffering of messages.
LZT 138 0240 R2A 143

Message buffering is furthermore associated with passive measurement only.

The buffer will be kept up-to-date whenever passive measurement actions
are selected as described above, but if you record a logfile manually (see
section 7.3), the buffer contents are not logged.
16.3.2. Post-guard Period

When the trigger condition for stopping a passive measurement action is
satisfied, a post-guard time of 10 seconds is added before the recording is
stopped and the logfile closed. The purpose of the post-guard period is to
capture signaling taking place in connection with termination of the service.
Exception: The above does not apply to the Startup option and power-off.
144
Chapter 17. Tools Menu
17. Tools Menu
In this menu are collected miscellaneous functions and information.
17.1. About Screen

Lines 1–2: Name of TEMS Pocket product package
and options installed.
Line 3: TEMS Pocket version.
Lines 4–5
IMSI: International Mobile Subscriber Identity of the
SIM card used. It is made up of
• Country Code (3 digits)
• Network Code (2 digits)
• Identification Number (at most 10 digits)
IMEI: International Mobile Equipment Identity of the
phone. It is made up of
• Type Approval Code (6 digits)
• Final Assembly Code (2 digits)
• Serial Number (6 + 1 digits)
LZT 138 0240 R2A 145

17.2. Quick Guide

This is a collection of tutorials in WAP page format
explaining various aspects of how TEMS Pocket
works. Audio recordings featuring an instructor’s
voice are included.
17.3. Import Settings

TEMS Pocket settings previously exported to files (see section 17.4) can be
imported into TEMS Pocket using this function. Note that the import will erase
all settings currently defined in the application. A message will appear
warning you about this.
• From the Tools menu, select Import settings. Then select the storage
medium where the settings files reside, and locate the files.
• Leave checked all categories of settings that you want to import. Uncheck
the rest, using the Unmark option.
Note: Be aware that FTP settings contain data account definitions.

Importing FTP settings will cause all of these data accounts to be
created on the TEMS Pocket phone. Existing data accounts with
identical name and APN will be overwritten.
146
• Press Import.
• A warning message appears; press Yes to continue.
• The import is then performed, overwriting all TEMS Pocket settings

currently in force. The outcome of each file import operation is reported as
shown below.
LZT 138 0240 R2A 147

17.3.1. Importing Settings Files from TEMS Pocket

Versions Older than 7.2
The following holds with regard to importing settings from older Sony
Ericsson TEMS Pocket releases:
• Events and General settings apply in exactly the same way as settings
made in TEMS Pocket 7.2 and higher.
• Logfile settings apply, except the “autostart logfile” options which will be
ignored (since this functionality was replaced by the passive
measurement function in TEMS Pocket 7.2).
• FTP settings apply, except that data account settings may be insufficient
since they are handled differently in older versions compared to TEMS
Pocket 7.2 and higher. After importing FTP settings from an older TEMS
Pocket version, you need to verify that all data accounts referred to in the
FTP server configurations are in fact defined on the phone. This is
because in older TEMS Pocket versions, an FTP server configuration only
contains a reference to a data account; it does not include an explicit data
account definition. An FTP server configuration referencing a data
account that is lacking on the phone is of course useless for that phone.
• Command sequence settings cannot be imported, since the command
sequence function was completely reworked in TEMS Pocket 7.2.
17.4. Export Settings

You can export to file all user-configured settings for command sequences,
events, FTP, logfiles, and passive measurement, as well as everything in the
General settings menu.
For each of the categories just mentioned, a single export file is created. For
command sequences, one file lists the default values for all action types, and
one further file is created for each command sequence defined, holding the
full settings for that sequence.
• To perform an export, enter the Tools menu and select Export settings.
148
Phone memory: The settings files are saved to the

phone memory.
Memory stick: The settings files are saved to the
memory stick, provided that the phone has got one
installed.
Regardless of the choice of storage medium, the
settings files are stored in the directory
Other\Pocket\Settings.
• You are prompted to create a folder for the export files:
After you select one of the options, the export is performed automatically.
Note: Settings exported from TEMS Pocket version 7.2.1 or later

cannot be imported into a TEMS Pocket 7.2.0 or older TEMS
Pocket phone.
17.4.1. Managing Export Files

If you perform multiple exports, you need to create a separate folder for each
set of settings files. If you export to a folder already in existence, the settings
in that folder will be overwritten. The same applies if you copy settings files
from a PC to the TEMS Pocket phone: each set of files needs to be put in a
folder of its own.
LZT 138 0240 R2A 149

17.5. Import Cell File

You can import a cell file into TEMS Pocket in order to display cells by name
(rather than by CGI) in data views. See sections 4.1, 4.11, and 4.19. Cell files
are in XML format, and relevant aspects of their syntax is described in
appendix E.1
When you select this menu item, you are prompted to locate and select your
cell file in the phone file system.
To have cells presented by name, you must also select the “Name” option
under General settings → Cell presentation; see section 18.6.
1. The file format is the same as in TEMS Investigation and contains a wide
range of data, most of which is currently not used in TEMS Pocket.
150
Chapter 18. General Settings Menu
18. General Settings Menu
In this menu you specify various aspects of TEMS Pocket behavior and of the
data presentation:
• Visibility of WAP data views
• Data view style
• Displaying of messages
• Backlight
• Cell Id format: decimal or hexadecimal
• Cell presentation: by CGI or by name
• Power unit: GSM units or dBm (RxLev)
• Full/Sub values (RxLev, RxQual)
• Auto answer
• Choice of signal quality indicator in WCDMA Cell Id data view (RSCP or
Ec/N0)
The settings made here remain in force until you modify them again or reset
them with the Reset All command (see section 18.11).
You can export the General settings to file; they are included in the Export
18.1. WAP Data View

When you are running WAP services you can have a TEMS Pocket data view
displayed at the bottom of the WAP browser. Two data views are selectable,
one for WCDMA and one for GPRS. See section 4.26.
LZT 138 0240 R2A 151

Choosing On activates the WAP data views.
For information on how to prepare the phone for WAP and getting started
using the service, please consult the user manual for the phone.
18.2. Data View Style

Default: The data views with text in black are
displayed against a white background.
Themed: The data views are displayed against the
background specified by the theme set on the
phone (main menu → Settings → Display →
Theme).
18.3. Messages
Normal: All phone messages are displayed as usual.
Minimized: Some phone messages are modified or
removed in order not to disturb the inspection of
TEMS Pocket data views. Specifically:
• The “call in progress” message box, normally
displayed throughout calls, is removed.
• The “calling” and “incoming call” message boxes
are shown, but the message box size is shrunk to
a minimum.
• All other messages are displayed as usual.
152
18.4. Backlight
Normal: The display backlight is dimmed after
about 15 seconds and turned off after about 25
seconds of user inactivity.
1 minute, etc.: The display backlight is dimmed
after about 15 seconds as usual but remains in that
state for the duration selected, without being turned
off, even if there is no user input.
18.5. Cell Id Format

Hex: LAC and CI are displayed in hexadecimal
digits.
Decimal: LAC and CI are displayed in decimal
digits.
18.6. Cell Presentation

CGI: Cells are presented by CGI.
Name: Cells are presented by name.
LZT 138 0240 R2A 153

18.7. Power Display (GSM)

dBm: RxLev is displayed in dBm.
GSM: RxLev is displayed in GSM units. (Not
applicable to graphs.)
18.8. Measure Mode Display (GSM)

Sub: RxLev and RxQual are presented in the form
of Sub values.
Full: RxLev and RxQual are presented in the form
of Full values.
154
18.9. Auto Answer

On: The phone will automatically answer an
incoming call (after a period of time equivalent to
two standard ring signals).
Off: No automatic answering of calls.
If MRU (Mobile Receiving Unit) software is installed

on the TEMS Pocket phone, a third option “MRU
replay” appears here. Selecting that option causes
the phone to start functioning as an MRU, which
means that it will automatically answer every
incoming call and play prerecorded speech
sentences for the purpose of audio quality
measurement (AQM). AQM calls are normally
disconnected by the AQM module used in TEMS
Automatic or TEMS Investigation. If the call is not
disconnected by the AQM module within one hour,
the MRU itself disconnects the call to protect
against network malfunctions and fraud calls.
18.10. WCDMA Cell Id Q-val

This setting governs the choice of signal quality
indicator in the WCDMA Cell Id data view (see
section 4.10): RSCP or Ec/No.
18.11. Reset All

This command restores all settings in the General settings menu to their
defaults. See appendix D, page 189 for a listing of the default settings.
LZT 138 0240 R2A 155

19. Scanning
19.1. Introduction to Scanning

TEMS Pocket is capable of scanning GSM and WCDMA carriers. One
technology at a time can be scanned.
The scanning function is wholly separate from the rest of TEMS Pocket. To
perform scanning you put the application in a special scan mode, as
described in section 19.2 below. While performing a scan, the TEMS Pocket
device ceases to behave like a mobile phone; it cannot make or receive calls,
nor can it engage in data services. Furthermore, the phone-mode TEMS
Pocket functions are not available in scan mode, with the following
exceptions:
• A GPS can be connected.
• Logfiles can be recorded.
A special “Scanner” view presents the results of the scanning. The TEMS
Pocket data views shown in phone mode are not available in scan mode,
except the GPS view where GPS data can be inspected.
19.2. How to Enter Scan Mode

Press the Activity key to enter the Activity menu.
• Select “Operational mode”, then select Scanner. Compare section 7.1.
The view “Scanner 1.1” appears. However, no scan is started automatically
(even if a scanning setup has been specified on a previous occasion).
• How to set up a scan is covered in section 19.3.
• How to start and stop scanning is described in section 19.4.
• To exit scan mode, you simply make a different selection under
Operational mode. Again, see section 7.1 for details.
156
Chapter 19. Scanning
19.3. Setting Up a Scan

To configure scanning settings, do as follows:
Press the Activity key.

• Select “Scanner menu”. This menu holds a number of submenus, which
are gone through in sections 19.3.1–19.3.4 below.
19.3.1. System
Here you select whether to perform GSM or
WCDMA scanning.
19.3.2. Method
19.3.2.1. GSM Scanning Methods

GSM scanning is always done in the frequency domain, measuring RSSI for
ARFCNs. You can scan:
• a whole GSM band, or
• a user-specified set of ARFCNs (“Custom list”).
“850”, etc.: Select this to scan the indicated

frequency band.
Custom list: Select this to set up your own list of
ARFCNs to scan. In that list you can mix channels
from different bands. Be aware, however, that
mixing ARFCNs from different bands will affect
scanning performance.
LZT 138 0240 R2A 157

19.3.2.2. WCDMA Scanning Methods

For WCDMA the following scanning methods are available:
• network scan of an entire WCDMA band, searching for UARFCNs where
a CPICH can be detected and measuring the RSSI of these UARFCNs
• CPICH scan, measuring RSCP of scrambling codes (“Custom list”).
19.3.3. Edit Scan List

If you have chosen Custom list under Method
(section 19.3.2), this is where you specify the list of
items to scan.
In GSM, up to 200 ARFCNs can be scanned.
In WCDMA, up to 12 UARFCNs can be CPICH
scanned.
• To add a channel to the scan list, press Add.
You are taken to a new dialog where you enter
the channel number. If that channel number
GSM dialog occurs on several frequency bands, you are
prompted to also specify the band in order to
uniquely identify the channel.
• To remove a channel from the scan list, select
the channel number and press Options →
Delete (or press the C button).
• To blank the scan list, press Options → Delete
all.
WCDMA dialog
Note that you can also add to the scan list by picking a channel in the
Scanner view; see sections 19.6.1.1 and 19.6.2.1.
The scan lists will persist in memory when you exit scan mode (and in fact
also when the phone is turned off).
158
19.3.4. Advanced
19.3.4.1. Advanced GSM Settings

Decode BSIC: Setting this on causes TEMS
Pocket to decode the BSIC (Base Station Identity
Code) whenever possible. It should be noted that
BSIC decoding is computationally costly and
considerably reduces the sample rate of the scan.
19.3.4.2. Advanced WCDMA Settings

Ec/N0 threshold: Cell Ec/N0 threshold for cell
detection within a detected carrier. Valid for all
WCDMA scanning.
This threshold should be high enough to minimize
the false detection rate, yet not so high that cells
actually present may go undetected. The risk of the
latter is particularly pronounced in the case of
overlapping carriers, where all cells will be
significantly disturbed.
The default setting is –26 dB, which should be
suitable in most situations.
The path Ec/N0 threshold is automatically set 2 dB
lower than the cell Ec/N0 threshold.
RSSI threshold: RSSI threshold for CPICH

detection. Valid for network (whole-band) scanning
only.
The default setting is –94 dB, reflecting a trade-off
between the desire to detect all networks in
operation and the wish to avoid spurious “hits”.
Setting the threshold too low results in a very long
search time (e.g. several minutes at –100 dB).
LZT 138 0240 R2A 159

Note: To input the minus sign, press the * or # key after typing the digits.
For example, to type “-95”, press {9, 5, *} or {9, 5, #}.
19.3.5. Notes on Changing the Scan Setup

It is possible to edit scanning settings while a scan is in progress. If the
changes made to the settings do not affect the ongoing scan (for example,
changing the GSM custom list while a GSM whole-band scan is being
conducted), the scan will continue uninterrupted. However, if your changes
do have bearing on the current scan, the scan will be halted, and a new scan
according to the new settings will be started.
19.4. Starting and Stopping a Scan

• While in the Scanner 1.1 view, press Start.
When you start scanning, the signal strength indicator in the top left corner of
the screen will go down to zero.
• To stop the scan, press Stop.
19.5. Other TEMS Pocket Functionality Available in

Scan Mode
19.5.1. Using a GPS

A GPS can be connected just as in phone mode: the Activity menu includes a
command “Connect GPS”/“Disconnect GPS”. See section 7.8. Refer to
chapter 12 for general information on using GPS units with TEMS Pocket.
Note: GPS settings must be configured while in phone mode, as

detailed in chapter 12. In scan mode, these settings cannot be
accessed.
160
The “GPS” data view is accessible in scan mode. For a description of this
view, turn to section 4.6.
19.5.2. Recording Logfiles

Logfiles can be recorded manually in scan mode the same way as in phone
mode. That is, the following commands are available in the Activity menu:
• Start logfile rec./Stop logfile rec.
• Insert filemark (visible while recording is in progress)
What is said about manual recording in sections 7.2 and 7.3 holds true for
scan mode also.
Logfile transfer via FTP is not available in scan mode; you need to switch
TEMS Pocket to phone mode before you can transfer logfiles. Once the
application is in phone mode, you can transfer scanning logfiles just like any
others. See sections 7.7, 14.3, and 14.4.
Replay of scan data is not supported in TEMS Pocket. However, you can
study your TEMS Pocket scanning logfiles by loading them into other TEMS
products:
• TEMS Investigation, version 10.1 or later
• TEMS Automatic, version 8.0 or later
• TEMS Presentation, version 2.0 or later
19.6. Scan Presentation: Scanner View (No. 1.1)

The results of any scan, regardless of technology and other settings, are
presented in a bar chart in the Scanner view.
The Scanner view always fits the entire set of channels scanned (whether a
band of contiguous channels or a collection of handpicked ones) into a single
screen width. This mode of presentation allows you to continuously monitor
all channels of interest and ensures that you will not miss out on any
significant signals as the radio environment changes.
If the total number of scanned channels is large, it may not be possible to
display every channel individually; rather, each bar will then represent a
group of channels. To allow inspection of individual channels, a “magnifying
glass” feature is provided: as you scroll through the channel range, a block of
channels centered around your current position is enlarged, so that each
channel in that block is drawn separately. The enlarged segment appears
LZT 138 0240 R2A 161

within a sliding frame. See the sequence of screenshots below, where the
user is scrolling from left to right:
magnifying frame
Further examples of this feature appear in subsections 19.6.1–19.6.2 below.
162
19.6.1. GSM Scanning Presentation
19.6.1.1. Whole-band Scan

When a frequency band is being scanned, the Scanner view shows the entire
frequency band.
GSM band with first and last ARFCNs

indicated
Magnifying frame
Channels currently in focus
Channel that can be added to scan list
Text pane glosses channels in focus:

ARFCN
BSIC (where decoded)
RSSI (dBm)
The magnifying frame (black with rounded corners) encloses the channels
currently in focus. Within the frame, five ARFCNs are displayed individually;
these are also tabulated in the text pane at the bottom. Press the left and right
navigation keys to move the magnifying frame and scroll through the
frequency band.
For the channels in focus, the following holds:
• The bar height encodes the RSSI of the corresponding ARFCN.
• A green bar means that BSIC has been decoded for this ARFCN.
• A red bar means that no BSIC has been decoded for this ARFCN.
The center ARFCN among the channels in focus (bar with black contour) can
be added to the custom scan list by pressing Options → “Add to scan list”.
This function lets you pick channels of particular interest and monitor only
those.
For channels out of focus, each bar may represent several ARFCNs (how
many depends on the total number of channels in the band):
• The bar height encodes the maximum RSSI in the ARFCN group.
• A green bar means that BSIC has been decoded for at least one ARFCN.
• A red bar means that no BSIC has been decoded for any of the ARFCNs.
LZT 138 0240 R2A 163

19.6.1.2. Custom List Scan
ARFCNs of channels with lowest and

highest frequency
Channels currently in focus

ARFCN
BSIC (where decoded)
RSSI (dBm)
The set of ARFCNs scanned are sorted in order of ascending channel

frequency, not by the ARFCN itself.
The magnifying frame (black with rounded corners) encloses the channels
currently in focus. It works the same way as for the whole-band scan. The bar
height and color, too, have the same interpretation as for the whole-band
scan. See section 19.6.1.1.
19.6.2. WCDMA Scanning Presentation
19.6.2.1. Network (Whole-band) Scan
WCDMA band with first and last UARFCNs

Each bar represents a UARFCN where at
least one CPICH has been detected.
Channel that can be added to CPICH scan

UARFCN
First scrambling code decoded (if any)
when this UARFCN was last scanned
RSSI (dBm)
164
The magnifying frame is present here just as for GSM scanning. In the above
example, however, the frame encompasses the entire bar chart because
fewer than five UARFCNs have been detected. If more than five UARFCNs
appear, you can move the magnifying frame by using the left and right
navigation keys.
The bar height encodes the UARFCN RSSI. All bars are colored green.
The center UARFCN among those in focus (bar with black contour) can be
added to the custom scan list. This function lets you pick out the UARFCNs
where traffic occurs and subject these to a CPICH scan.
• Select the UARFCN of interest.
• Press Options → “Add to scan list”.
19.6.2.2. CPICH (Custom List) Scan
Lowest and highest UARFCNs scanned
Each bar represents one UARFCN.
UARFCN currently in focus
Strongest detected scrambling codes

UARFCN in focus, and its RSSI (dBm)
SC index, RSCP (dBm), and Ec/N0 (dB)
of each detected scrambling code on the
UARFCN in focus
In this presentation, only one UARFCN at a time is in focus (green bar framed
in black). For that UARFCN, the strongest scrambling codes detected (up to
six)1 are drawn in shades of blue on top of the UARFCN bar. Use the left and
right navigation keys to scroll through the UARFCNs presented.
• The bar height encodes the RSSI of the corresponding UARFCN.
• A green bar means that at least one scrambling code has been detected
on this UARFCN.
• A red bar means that no scrambling code has been detected on this
UARFCN.
1. In the logfile, up to 12 scrambling codes are recorded.
LZT 138 0240 R2A 165

19.6.3. Freezing the Scanner View

• To freeze the Scanner view without exiting it, press Pause. This action
simply halts the updating of the Scanner view; the scanning itself
continues without interruption, even though no new samples are
presented, and so does the logfile recording if that function is active.
• Press Resume to resume updating of the scan presentation.
19.7. GPS View (No. 1.2)

The GPS data view is the same as in phone mode. See section 4.6.
19.8. The Built-in Help Function

If you press Options and select “Toggle help”, a callout box appears
describing a piece of data on the screen. Use the navigation key to navigate
the contents of the data view.
Help not displayed Help displayed
• To turn off the help function, press the C key. Alternatively, press Options
and choose Toggle help again.
19.9. The Capture Function

You can take screenshots of data views in scan mode just as in phone mode.
To do this, you must first turn the screen capture function on (while in a data
view) by selecting Options → Toggle capture. You can now take a screenshot
of the Scanner or GPS view at any time by pressing the Capture button.
166
Image files are named SC<X>-<Y>_<N>.bmp, where <X>-<Y> represent the

data view number and <N> is a counter starting at 1. Other details are the
same as in phone mode; see section 3.3.
LZT 138 0240 R2A 167

20. Uploading TEMS Pocket

Logfiles from the Phone File
System
Besides the TEMS Pocket internal logfile upload functions, covered in

sections 7.7, 14.3 and 14.4, a further FTP upload command is available. This
command is separate from the TEMS Pocket user interface but is
nonetheless a feature specific to TEMS Pocket phones.
• In the phone’s main menu, navigate to Organiser → File manager →
Other → Pocket → Pro and select the logfile(s) you want to upload.
– To select a single logfile, just navigate to that file. Then press Send.
– To select multiple logfiles, choose Options → Mark → “Mark several”,

then check the files that are to be uploaded. Alternatively, choose
“Mark all” to check all files in the directory. Then choose Options →
Send.
168
Chapter 20. Uploading TEMS Pocket Logfiles from the Phone File System
• In either case, a menu of send options now appears. From that menu,
select “Via FTP”. (This option is not found in commercial phones. It can
only be used to transfer TEMS Pocket logfiles; if a file other than a TEMS
Pocket logfile has been selected, the Via FTP option does not appear.).
• You are now taken to the list of FTP servers you have defined in TEMS
Pocket; see section 13.2. Select the FTP server you want to upload to.
• The upload starts.
After a logfile has been uploaded by this method, it is deleted from the phone
file system.
LZT 138 0240 R2A 169

21. Battery Charging

Considerations
Running several tasks in parallel on the Sony Ericsson W995 and W995a
places a heavy load on the phone battery. It may in fact happen that the
battery charger cannot keep up with the power consumption, so that the
battery will eventually be drained even if the charger is connected all the time.
This situation may arise for example if the phone is more or less constantly
using one service or another while at the same time having its display fully lit.
Some specific advice on battery charging related matters is given below.
21.1. Choice of Phone Charger

When engaging the phone in highly power-consuming tasks, you should
always use the regular phone charger. The USB charger which is also
provided with the phone is only about one third as powerful, which will often
be vastly insufficient when running TEMS Pocket.
21.2. Using the Phone’s Built-in GPS

You need to be aware that using the phone’s internal GPS with TEMS Pocket
very considerably increases the power consumption and hence the risk that
the battery charger cannot keep up.
21.3. Using a TEMS Pocket Command Sequence

If you are using the command sequence function in TEMS Pocket, you must
take special steps to ensure that the phone battery is not drained.
To understand why it is first necessary to explain how the battery charging in
the Sony Ericsson W995 and W995a works.
First we need to define the end-of-charge (EoC) state for the battery. This is a
state where the battery is regarded as fully charged by the phone’s charging
algorithm. The precise details need not bother us; however, and crucially, the
170
Chapter 21. Battery Charging Considerations
method of testing whether the EoC state has been reached is to measure the
average current flowing to/from the battery over a period of time.
Now, if TEMS Pocket is continuously executing a command sequence (say,
making voice calls), the phone will be switching frequently between idle and
dedicated mode. This in turn means that the current to the battery will not be
constant enough for the EoC state ever to be reached. Even if the battery
charge level remains high at all times (for example, above 90%), the charging
algorithm will never consider the battery to be fully charged.
Since prolonged charging of the battery increases the risk of battery failure,
the charging algorithm has a safety timer that disables the charger after four
hours if the battery has failed to reach the EoC state within this time. If this
happens, the phone will run on batteries until the charger is disconnected and
reconnected, or until the phone is power cycled. If neither of these actions is
performed, and a command sequence is running, the battery will be drained
in a fairly short time.
For example, suppose that the following command sequence is executed:
• One action, voice call (see section 15.2.3)
• Call duration = 15 s
• Guard time = 60 s
The phone performs charging in idle mode only, unless the battery charge is
low. In the above case, the phone is idle about 50% of the time, so after about
4 × 2 = 8 hours the safety timer expires and the charger is disabled. After that
the phone runs on battery power only, and tests using a battery in near mint
condition have shown that the battery is then drained in about 4 hours.
To prevent this situation from arising, you have two options:
• One way is to disable the command sequence for a while (before the
safety timer expires) to give the phone an unbroken stretch of time in idle
mode and allow the battery to reach the EoC state. Note, however, that
the length of the break required depends on the settings in the command
sequence and on the general condition of the battery. In the above test
case, an idle mode period of 15–20 minutes was required, but in other
circumstances more time may be needed. (You must halt the command
sequence manually, as described in section 7.9.)
• Another approach is simply to make sure you disconnect the battery
charger physically from the phone (or unplug the charger from its power
source) before the battery is drained, and then reconnect the charger.
The latter option is the only completely safe one, and it is therefore
recommended.
LZT 138 0240 R2A 171

22. 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.
172
Appendix A. Parameter Values
This appendix lists the possible values of some parameters appearing in the
views and of some event parameters.
A.1. Activate PDP Context Failure Cause

26 Insufficient resources
27 Missing or unknown APN
28 Unknown PDP address or PDP type
29 User authentication failed
30 Activation rejected, unspecified
31 Activation rejected by GGSN
32 Service option not supported
33 Requested service option not subscribed
34 Service option temporarily out of order
35 NSAPI already used
95 Semantically incorrect message
96 Invalid mandatory information
97 Message type non-existent or not implemented
98 Message type not compatible with the protocol state
99 Information element non-existent or not implemented
111 Protocol error, unspecified
T3380 Fifth expiry of T3380 timer (MS side)
A.2. Automatic Upload Failure Cause

1 Compression failed, probably due to full file system
2 User canceled upload
3 Destination folder is incorrect
5 No FTP account specified for automatic upload
6 No FTP server specified for automatic upload
7 FTP rename failed
LZT 138 0240 R2A 173

8 FTP Put failed

9 FTP Get failed
11 FTP login failed, incorrect user name or password
12 Data account assigned to the upload is invalid
13 Connection failed, FTP server not responding
14 No files to upload
A.3. CC Cause
1 Unassigned (unallocated) number
3 No route to destination
6 Channel unacceptable
8 Operator determined barring
16 Normal call clearing
17 User busy
18 No user responding
19 User alerting, no answer
21 Call rejected
22 Number changed
25 Pre-emption
26 Non selected user clearing
27 Destination out of order
28 Invalid number format (incomplete number)
29 Facility rejected
30 Response to STATUS ENQUIRY
31 Normal, unspecified (not logged)
34 No circuit/channel available
38 Network out of order
41 Temporary failure
42 Switching equipment congestion
43 Access information discarded
44 Requested circuit/channel not available
47 Resources unavailable, unspecified
49 Quality of service unavailable
50 Requested facility not subscribed
55 Incoming calls barred within the CUG
57 Bearer capability not authorized
58 Bearer capability not presently available
174
63 Service or option not available, unspecified

65 Bearer service not implemented
68 ACM equal to or greater than ACMmax
69 Requested facility not implemented
70 Only restricted digital information bearer capability is available
79 Service or option not implemented, unspecified
81 Invalid transaction identifier value
87 User not member of CUG
88 Incompatible destination
91 Invalid transit network selection
98 Message type not compatible with protocol state
100 Conditional IE error
101 Message not compatible with protocol state
102 Recovery on timer expiry
127 Interworking, unspecified
A.4. CCCH Configuration

NC 1 basic physical channel used for CCCH, not combined with
SDCCHs
Comb 1 basic physical channel used for CCCH, combined with
SDCCHs
NC2 2 basic physical channels used for CCCH, not combined with
SDCCHs
SDCCHs
SDCCHs
LZT 138 0240 R2A 175

A.5. Channel Type

BCCH Broadcast Control Channel, Signalling
PBCCH Packet Broadcast Control Channel
PDTCH Packet Dedicated Traffic Channel
SDCCH Stand-alone Dedicated Control Channel
TCH/F Traffic Channel, Full Rate
TCH/H Traffic Channel, Half Rate
A.6. Deactivate PDP Context Cause

25 LLC or SNDCP failure
36 Regular PDP context deactivation
37 QoS not accepted
38 Network failure
39 Reactivation requested
A.7. GMM Cause

2 IMSI unknown in HLR
3 Illegal MS
6 Illegal ME
7 GPRS services not allowed
8 GPRS services and non-GPRS services not allowed
9 MS identity cannot be derived by the network
10 Implicitly detached
11 PLMN not allowed
12 Location area not allowed
13 Roaming not allowed in this location area
14 GPRS services not allowed in this PLMN
15 No suitable cells in location area
16 MSC temporarily not reachable
17 Network failure
20 MAC failure
21 Synch failure
176
22 Congestion
23 GSM authentication unacceptable
40 No PDP context activated
48–63 Retry upon entry into a new cell
101 Message not compatible with the protocol state
A.8. GPRS Network Mode of Operation

Handling of paging in the GPRS network.
I Mode I: All paging on GPRS channels; Gs signalling interface

present
II Mode II: All paging on PCH; no Gs
III Mode III: All circuit-switched paging on PCH, all packet-
switched paging on PPCH; no Gs
A.9. GPS Fix Quality

0 Fix not available or invalid
1 GPS SPS Mode, fix valid
2 Differential GPS, SPS Mode, fix valid
3 GPS PPS Mode, fix valid
4 Real Time Kinematic. System used in RTK mode with fixed
integers
5 Float RTK. Satellite system used in RTK Mode, floating integers
6 Estimated (Dead Reckoning) mode
7 Manual Input Mode
8 Simulator Mode
32 Internal GPS
LZT 138 0240 R2A 177

A.10. MM Cause
2 IMSI unknown in HLR
3 Illegal MS
4 IMSI unknown in VLR
5 IMEI not accepted
6 Illegal ME
11 PLMN not allowed
17 Network failure
22 Congestion
38 Call cannot be identified
48–63 Retry upon entry into a new cell
A.11. PDP Context Request Parameters
A.11.1. Delay Class

0 Subscribed
1 Delay class 1
2 Delay class 2
3 Delay class 3
4 Delay class 4 (best effort)
178
A.11.2. Reliability Class

0 Subscribed
1 Acknowledged GTP, LLC, and RLC; Protected data
2 Unacknowledged GTP; Acknowledged LLC and RLC,
Protected data
3 Unacknowledged GTP and LLC; Acknowledged RLC,
Protected data
4 Unacknowledged GTP, LLC, and RLC, Protected data
5 Unacknowledged GTP, LLC, and RLC, Unprotected data
A.11.3. Peak Throughput

0 Subscribed
1 Up to 1000 octets/s
5 Up to 16,000 octets/s
A.11.4. Precedence Class

0 Subscribed
1 High priority
2 Normal priority
3 Low priority
A.11.5. Mean Throughput

0 Subscribed
1 100 octets/h
2 200 octets/h
3 500 octets/h
4 1000 octets/h
LZT 138 0240 R2A 179

5 2000 octets/h
6 5000 octets/h
7 10,000 octets/h
8 20,000 octets/h
9 50,000 octets/h
10 100,000 octets/h
11 200,000 octets/h
12 500,000 octets/h
13 1,000,000 octets/h
14 2,000,000 octets/h
15 5,000,000 octets/h
16 10,000,000 octets/h
17 20,000,000 octets/h
18 50,000,000 octets/h
31 Best effort
A.12. Routing Area Update Failure Cause

3 Illegal MS
6 Illegal ME
7 GPRS services not allowed
9 MS identity cannot be derived by the network
10 Implicitly detached
11 PLMN not allowed
99 IE non-existent or not implemented
A.13. RR Cause
0 Normal event
1 Abnormal release, unspecified
2 Abnormal release, channel unacceptable
3 Abnormal release, timer expired
180
4 Abnormal release, no activity on the radio path

5 Preemptive release
8 Handover impossible, timing advance out of range
9 Channel mode unacceptable
10 Frequency not implemented
65 Call already cleared
98 Message type not compatible with protocol state
101 No cell allocation available
A.14. RR Internal Cause

0 Normal release
1 Abnormal release unspecified
2 MAX no of random access
3 Access barred
4 Reject from base station
5 No cell available
6 No ciphering key
7 Reestablish not allowed
8 Data link error
9 Establish error
10 Ciphering algorithm not implemented
11 PS connection aborted due to CS connection
12 PDCH release
13 SCH timing error or timing advance out of range
14 L2 error
15 Message received in invalid state
16 IRAT U2G handover failure
A.15. RRC Failure Cause

0 Configuration unsupported
1 Physical channel failure
LZT 138 0240 R2A 181

2 Incompatible simultaneous reconfiguration

3 Protocol error
4 Compressed mode runtime error
5 Cell update occurred
6 Invalid configuration
7 Configuration incomplete
8 Unsupported measurement
9 MBMS session already received correctly
10 Lower priority MBMS service
A.16. RRC Protocol Error Cause

0 ASN.1 violation or encoding error
2 Message not compatible with receiver state
3 Information element value not comprehended
4 Information element missing
5 Message extension not comprehended
A.17. SM Cause
8 Operator Determined Barring
24 MBMS bearer capabilities insufficient for the service
25 LLC or SNDCP failure (A/Gb mode only)
27 Missing or unknown APN
28 Unknown PDP address or PDP type
29 User authentication failed
30 Activation rejected by GGSN
31 Activation rejected, unspecified
35 NSAPI already used (not sent)
36 Regular deactivation
37 QoS not accepted
38 Network failure
39 Reactivation required
182
40 Feature not supported

41 Semantic error in the TFT operation
42 Syntactical error in the TFT operation
43 Unknown PDP context
44 Semantic errors in packet filter(s)
45 Syntactical errors in packet filter(s)
46 PDP context without TFT already activated
47 Multicast group membership time-out
81 Invalid transaction identifier value
112 APN restriction value incompatible with active PDP context
LZT 138 0240 R2A 183

Appendix B. Graphic
Representation of Parameter Values
This appendix describes the bar length and color coding used to visualize
parameter values in data views.
B.1. C/I
Bar length is proportional to (Value – (–5.0 dB)).
Value = x (dB) Color
x > 15.0 green
10.0 ≤ x ≤ 15.0 yellow
x < 10.0 red
B.2. Ec/N0
Bar length is proportional to (Value – (–25 dB)).
Value = x (dB) Color
x > –10 green
–15 < x ≤ –10 yellow
x ≤ –15 red
184
Appendix B. Graphic Representation of Parameter Values
B.3. FER, RLC/LLC BLER/Retransmissions

Bar length is constant.
Value = x (%) Color
x=0 green
1≤x≤4 yellow
x≥5 red
B.4. RLC DL/UL Throughput

This is used in the Map view only (no bars).
Value = x (kbit/s) Color
x ≥ 1000 green
100 ≤ x < 1000 yellow
10 ≤ x < 100 orange
x < 10 red
B.5. RxLev, RSCP, RSSI

Bar length is proportional to (Value – (–110 dBm)).
Value = x (dBm) Color
x ≥ –70 green
–80 ≤ x < –70 light green
–90 ≤ x < –80 yellow
–100 ≤ x < –90 orange
x < –100 red
LZT 138 0240 R2A 185

B.6. RxQual
Bar length is constant.
Value = x Color
x=0 green
1≤x≤4 yellow
x≥5 red
B.7. Tx Power
Bar height is proportional to (Value – (–30 dBm)).
Value = x (dBm) Color
x<5 green
5 ≤ x < 15 yellow
x ≥ 15 red
186
Appendix C. Icons Used in TEMS Pocket
Appendix C. Icons Used in TEMS

Pocket
Regarding icons for cellular network events, see section 10.4.
Icon Meaning
GPS connected
GPS disconnected
GPS location found
GPS location lost
Logfile recording in progress
Pinpointing in progress
Cell control function(s) active
Application of cell control function(s) failed
FTP transfer started
FTP transfer completed
FTP transfer failed
Replay in progress at normal speed
Replay paused
Replay stopped (end of logfile reached)
LZT 138 0240 R2A 187

Icon Meaning
Logfile upload starteda
Logfile upload completeda
Logfile upload faileda
a. By default not shown: see section 10.5.8.
188
Appendix D. Default Settings in TEMS Pocket Menus
Appendix D. Default Settings in

TEMS Pocket Menus
This appendix lists the defaults for all settings editable from the Activity and
Pocket menus.
D.1. Activity Menu
D.1.1. Operational Mode

Active
D.1.2. Scanner Menu

(visible in scan mode only)
• System: GSM
D.1.2.1. GSM Scanning

• Method: 900
• Advanced
– Decode BSIC: On
D.1.2.2. WCDMA Scanning

• Method: 2100 (I)
• Advanced
– Ec/N0 threshold: –26 dB
– RSSI threshold: –94 dBm
LZT 138 0240 R2A 189

D.2. Pocket Menu
D.2.1. Cell Control Menu

• All locking functions are by default turned off.
• Voice codec: All codecs checked
• HS capability: HSPA
• Ignore cell barred: Off
Note: Unlike settings in other menus, these settings revert to their

defaults when the phone is powered off and on.
D.2.2. Events Menu

• Event logging: Silent
• Event counters: On for all events
• Event settings: See section 10.5
D.2.3. Data Views Menu

All views visible (including the Map view)
D.2.4. GPS Menu

• GPS connect: Manual
• GPS device: Internal
• GPS time synch: Off
D.2.5. FTP Menu

• FTP transfer
– Save file to (FTP Get): Memory stick
D.2.6. Logfile Menu

• Save logfile to: Memory stick
190
• Upload logfile: Off

• WiFi upload: Off
• Compress: Off
• FTP resume: Off
D.2.7. Command Sequence Menu

Bear in mind that these defaults only apply until you save an action definition
as a template for that action type; see section 15.2.10.
• Global settings
– Upload: On
– Store logfiles with: Success, Failure, Tag
– Record: On
– GPS: Off
• Voice settings
– Call duration: 10 s
– Guard time: 20 s
– Redial: Off
– Cell control: Nothing turned on
• Video settings
– Call duration: 10 s
– Redial: Off
• FTP settings
• HTTP settings
LZT 138 0240 R2A 191

• Streaming settings
– Audio: On
– Video: Show
– Max time: 600 s
• Idle settings
– Duration: 10 s
D.2.8. Passive Measurement Menu

No actions (triggers) selected.
The following defaults are set for all action types:
• Duration: Off
• GPS: Off
Settings for all actions except Startup:
• Store logfiles with: Success, Failure, Tag
Settings for HTTP and streaming actions:
• Privacy: Off
D.2.9. Tools Menu

• Import settings: Memory stick
• Export settings: Memory stick
D.2.10. General Settings Menu

• WAP data view: On
• Data view style: Themed
• Messages: Minimized
• Backlight: 5 minutes
• Cell Id format: Hex
192
• Cell presentation: CGI

• Power display: dBm
• Measure mode display: Sub
• Auto answer: Off
• WCDMA Cell Id q-val: RSCP
LZT 138 0240 R2A 193

Appendix E. Cell File Format
An XML cell file imported into TEMS Pocket must include the tags shown in
the example below. The tag names are all self-explanatory; in this example,
two cells each are defined for GSM and WCDMA. This data is a subset of the
XML cell file format used in TEMS Investigation; see TEMS Investigation 11.0
Technical Reference, chapter 3.
Please note that TEMS Pocket can only display characters from the
Extended ASCII set. Characters outside that set will appear as question
marks “?” in the TEMS Pocket user interface.
Required Cell File Content
<TEMS_CELL_EXPORT>
<WCDMA>
<CELL_LIST>
<WCDMA_CELL>
<CELLNAME SYSTEM_TYPE="WCDMA">My WCDMA Cell 1</CELLNAME>
<UARFCN_DL>10787</UARFCN_DL>
<SC>124</SC>
<CGI>
<MCC>240</MCC>
<MNC_LENGTH>2</MNC_LENGTH>
<MNC>5</MNC>
<LAC>27</LAC>
<CI>60001</CI>
</CGI>
</WCDMA_CELL>
<WCDMA_CELL>
<CELLNAME SYSTEM_TYPE="WCDMA">My WCDMA Cell 2</CELLNAME>
<UARFCN_DL>10787</UARFCN_DL>
<SC>23</SC>
<CGI>
<MCC>240</MCC>
<MNC>5</MNC>
<LAC>27</LAC>
<CI>7924</CI>
</CGI>
</WCDMA_CELL>
194
Appendix E. Cell File Format
</CELL_LIST>
</WCDMA>
<GSM>
<CELL_LIST>
<GSM_CELL>
<CELLNAME SYSTEM_TYPE="GSM">My GSM Cell 1</CELLNAME>
<CGI>
<MCC>240</MCC>
<MNC>1</MNC>
<LAC>5028</LAC>
<CI>4362</CI>
</CGI>
<BSIC>
<NCC>2</NCC>
<BCC>2</BCC>
</BSIC>
<CHANNEL_INFO>
<BCCH>
<ARFCN>19</ARFCN>
</BCCH>
</CHANNEL_INFO>
</GSM_CELL>
<GSM_CELL>
<CELLNAME SYSTEM_TYPE="GSM">My GSM Cell 2</CELLNAME>
<CGI>
<MCC>240</MCC>
<MNC>1</MNC>
<LAC>5028</LAC>
<CI>5001</CI>
</CGI>
<BSIC>
<NCC>2</NCC>
<BCC>2</BCC>
</BSIC>
<CHANNEL_INFO>
<BCCH>
<ARFCN>20</ARFCN>
</BCCH>
</CHANNEL_INFO>
</GSM_CELL>
</CELL_LIST>
</GSM>
</TEMS_CELL_EXPORT>
LZT 138 0240 R2A 195

196
Index
Index
Numerics
3G symbol (at top of display) 9
A
About screen 145
Activate PDP Context Failure Cause 173
active set (WCDMA) 21, 33, 34, 35, 66, 68
Activity key 10, 83
Activity menu 10, 83, 89
altitude 30
AMR codecs (GSM)
active set 59
used on downlink 59
used on uplink 59
utilization of 59
AMR codecs (WCDMA)
active set 39
used on downlink 39
used on uplink 39
utilization of 39
APN 25
ARFCN 22
ARQ mode (EGPRS) 54
Auto Answer dialog 155
Automatic Repeat Request Mode (EGPRS) 54
Automatic Upload Failure Cause 173
B
Backlight dialog (display backlight) 153
barred cells, accessing of 96
Base Station Identity Code 45, 48, 49, 50, 53, 58, 63, 66, 68, 74
battery charging considerations 131, 170
BCCH ARFCN 22, 45, 47, 48, 49, 50, 66, 68, 74
BEP (EGPRS) 54
BEP variance (EGPRS) 54
LZT 138 0240 R2A 197

bit error probability, mean (EGPRS) 54

bit error probability, variance (EGPRS) 54
BLER (GSM) 55, 64, 70, 76
BLER (WCDMA) 40, 61, 62, 70
BLER Target, downlink (on transport channel) 38
block retransmission rate (GSM) 55, 64, 70, 76
block retransmission rate (WCDMA) 40, 62
BS-AG-BLKS-RES 50
BSIC 22, 45, 48, 49, 50, 53, 58, 63, 66, 68, 74
BS-PA-MFRMS 46, 47, 50
bytes transferred (GSM) 55
bytes transferred (WCDMA) 40
C
C value (EGPRS) 54
C/I 51, 54, 57, 58
graphic representation 184
C1 45, 67, 68, 74
C2 45, 67, 68, 74
C31 45, 67, 69, 74
C32 45, 67, 69, 74
capture function (taking screenshots) 7, 15, 166
Carrier-to-interference ratio (C/I) 51, 54, 57, 58
CC Cause 174
CC events 103
CCCH Configuration 50, 175
cell control functions 12, 91
icon for 9, 84
Cell Control menu 91
default settings in 190
cell file
format of 194
importing 150
Cell Id Format dialog 153
Cell Identity 23, 34, 35, 47, 48
presentation in dedicated/connected mode 7
cell name presentation 1, 150
Cell Presentation dialog 153
Cell Reselection Criterion (C2) 45, 67, 68, 74
Cell Reselection Hysteresis 46, 47
cell selection and reselection parameters 36
channel coding scheme (GPRS)
on downlink 54
198
Index
on uplink 54
Channel Mode 52
Channel Quality Indicator (HSDPA) 42
Channel Type 52, 176
channelization codes on HS-SCCH, number of 42
charging of phone battery 170
CI 23, 34, 35, 47, 48
presentation format 153
Ciphering Mode 52
color coding of parameter values 14
Command Sequence menu 131
command sequences 12, 131
adding an action to 134
battery charging considerations 170
defining 132
deleting 140
deleting an action from 140
editing 140
FTP action 136
global settings 132
HTTP action 137
Idle action 138
introduction to 131
post-guard period 139
pre-guard period 139
rearranging actions in 139
running 88, 140
saving default settings for an action type 139
starting and stopping 88
streaming action 138
video call action 136
viewing 140
voice call action 135
Compressed Mode 38, 39, 40
compressing logfiles before upload 121, 129
Connect GPS command 87
CQI 42
D
data rate (GSM channel mode) 52
data view actions 15
Data View Style dialog 152
LZT 138 0240 R2A 199

data views 8, 14
browsing 9
categories of 9
display style 152
general properties of 14
survey of 17
taking snapshots of 7, 15, 166
updating in replay mode 84
visibility of 112
with graphs 6, 9, 65
data views in text format 8, 21
Data Views menu 112
DCH, time using 27
Deactivate PDP Context Cause 176
default settings in TEMS Pocket menus 189
Delay Class (PDP Context Request) 25, 178
Disconnect GPS command 87
Downlink Signalling Counter 50
DRX Timer Max 56
DSC (Current) 50
DSC (Max) 50
DTX rate
in GSM, on downlink 51, 59
in GSM, on uplink 51, 59
in HSUPA 43
E
Ec/No 21, 66, 68
E-DPCCH/E-DPDCH retransmission rate 43
EGPRS modulation coding scheme 63
EGPRS window size 56
end-of-charge state (of phone battery) 170
EoC 170
Equivalent PLMN, time registered in 27
E-TFCI 43
event counters 84, 101
resetting 102
viewing 101
event log 84, 87, 97
clearing 98
details of individual events 98
200
Index
viewing 97
event settings 99
modifying 100
viewing 99
events 11, 97, 98
enabling/disabling event logging and sound 98
event log 98
icons for 9, 102
list of 103
presentation in graphs 65
Events menu 97
exiting TEMS Pocket 13
exporting TEMS Pocket settings 7, 148
managing export files 149
F
FER 51, 59
filemarks, inserting in logfiles 83
Frame Erasure Rate 51, 59
FTP
duration of FTP session 28
name of transferred file 28
selecting server to upload logfiles to 130
setting up Put and Get operations 117
specifying FTP servers 119
starting and stopping FTP sessions 87
throughput 28
total bytes transferred 29
FTP Data data view (no. 1.5) 28
FTP menu 117
FTP resume 130
FTP server address 28
FTP Server dialog 119, 130
FTP session, direction of (UL/DL) 28
FTP Settings dialog (command sequence) 136
FTP Transfer dialog 117
Full/Sub values (for RxLev and RxQual) 154
LZT 138 0240 R2A 201

G
General Settings menu 151
GMM Attached 26
GMM Cause 176
GMM events 106
GMM State 56
GPRS Cell Ranking Criterion (C32) 45, 67, 69, 74
GPRS Data data view (no. 4.2) 53
actions in 55
GPRS Info data view (no. 4.3) 56
GPRS Network Mode of Operation 56, 177
GPRS Signal Strength Threshold Criterion (C31) 45, 67, 69, 74
GPRS timeslots 53, 63, 76
GPS 12
battery charging considerations 170
Bluetooth pairing 114
connect mode 114
connecting and disconnecting 87
date 30
fix quality 30, 177
number of satellites seen 30
requirements on external GPS device 114
selecting type of GPS device 115
synchronizing phone clock with 116
time 30
using external GPS with TEMS Pocket 114
using phone’s built-in GPS with TEMS Pocket 113
using while in scan mode 160
GPS Connect dialog 114
GPS data view (no. 1.6) 30
GPS Device dialog 115
GPS menu 113
GPS Time Synch dialog 116
graphic presentation 14
graphic representation of parameter values 184
graphs 9
graphs in data views 6
GSM AMR data view (no. 4.5) 58
GSM BA List data view (no. 3.4) 49
actions in 49
202
Index
GSM C/I Info data view (no. 4.4) 57

GSM Cell Id data view (no. 3.2) 47
actions in 48
GSM Cell Name data view (no. 3.3) 48
actions in 49
GSM Cells data view (no. 3.1) 45
actions in 46
GSM Cells data view (no. 5.7, with graph) 74
GSM Channel Type 22
GSM Data data view (no. 5.8) 76
GSM Serving Cell data view (no. 4.1) 50
H
H symbol (at top of display) 9
happy rate (HSUPA) 43
HARQ processes on HS-DSCH, number of 42
help, on-screen 14, 166
Home PLMN, time registered in 27
hopping channels 14, 22, 45, 47, 49, 51, 53, 58, 63, 66, 68, 74, 76
Hopping Sequence Number 52
HS Capability dialog 95
HSDPA
actual transport block size 42
block error rate, first retransmission 43
channelization codes on HS-SCCH, number of 42
CQI 42
HARQ processes on HS-DSCH, number of 42
percentage of blocks transmitted successfully on first attempt 43
requested transport block size 42
residual block error rate 43
total number of blocks to be received 43
turning phone capability on and off 95
HSN 52
HSPA Data data view (no. 2.8) 42
HSUPA
DTX rate 43
E-DPCCH/E-DPDCH retransmission rate 43
E-TFCI 43
happy rate 43
Serving Grant Index 43
transport block size on E-DCH 43
HTTP Settings dialog (command sequence) 137
LZT 138 0240 R2A 203

I
icons
for cell control functions 91
for events 102
for logfile recording 84
listing of all icons used in TEMS Pocket 187
Idle mode
time spent in (GSM) 27
time spent in (WCDMA) 27
Idle Settings dialog (command sequence) 138
Ignore Cell Barred dialog 96
IMEI 145
importing TEMS Pocket settings 7, 146
from previous TEMS Pocket versions 148
IMSI 145
indoor positioning by pinpointing 78
Insert Filemark command 83
interplay between locking functions 94
Inter-RAT events 107
invalid parameters, representation of 14
L
LAC 23, 47
last registered 26
language support 13
latitude 30
LLC data transfer performance (GSM) 55, 64
LLC window size 56
Location Area Code 23, 47
Location Area properties 34, 46, 74
Lock ARFCN GSM dialog 93
Lock Band GSM dialog 93
Lock Band WCDMA dialog 93
Lock Cell WCDMA dialog 92
Lock GSM band 94
Lock GSM cell 24, 48, 49, 93, 94
Lock to RAT 94
GSM only setting in phone menu 92
Lock to RAT dialog 91
Lock UARFCN 24, 33, 34, 35, 94
Lock WCDMA cell 24, 33, 34, 35, 94
204
Index
locking functions
comparison with TEMS Investigation 94
interplay between 94
Logfile menu 121
logfile recording 11, 121
automatic triggering of 121, 141
icon for 9
in scan mode 161
starting/stopping manual recording 84
where to save files 123
logfile replay 11, 84, 121
controlling 85
status icons for 9
logfile uploading over the cellular network 123
from phone file system 168
setting a schedule for 125
logfile uploading over WiFi 126
logfile uploading, resumption after loss of FTP connection 6, 130
logfiles
naming of 2, 122
saving of 1, 133, 142
Logical Channel 45, 47, 49, 50, 51, 53, 58, 63, 66, 68, 74
longitude 30
M
MAIO 52
Map view 6, 10, 78
assigning geographical position to map image 82
color-coding of route markers 79
loading map image into 78
zoom level 79
MCC 23
last registered 26
Mean Throughput (PDP Context Request) 25, 179
Measure Mode Display dialog (GSM) 154
memory
low memory condition 11, 84
memory sticks 12, 118, 121, 123, 124, 149
menus 10
messages (displaying of) 152
Messages dialog 152
LZT 138 0240 R2A 205

MM Cause 178
MM events 104
MM/GMM data view (no. 1.3) 26
MNC 23
last registered 26
Mobile Allocation Index Offset 52
Mobile Country Code 23
Mobile Network Code 23
modulation coding scheme on downlink (EGPRS) 63
modulation coding scheme on uplink (EGPRS) 63
modulation method on downlink (GPRS/EGPRS) 54
modulation method on uplink (GPRS/EGPRS) 54
MRU 2, 155
MS-TXPWR-MAX-CCH 46, 47
N
naming of logfiles 122
Neighbor Cell BCCH 46, 47, 48, 74
neighbors (GSM) 22, 46, 47, 48, 49, 74
Network Mode of Operation 56
NMO 56
No Service mode, time spent in 27
NSAPI 25
O
Operational Mode 83
default 189
overview of TEMS Pocket 8
P
Packet Dedicated Traffic Channel 51, 53, 58, 63, 76
Packet Final Block Timer 56
Packet TMSI 26
Packet Uplink Assignment Timer 56
parameter values 173
Passive Measurement menu 141
passive measurements 141
action settings 142
message buffering for 143
prioritization of 143
Pathloss (WCDMA) 21, 33, 66, 68, 71, 73
Pathloss Criterion (C1) 45, 67, 68, 74
PDCH, time using 27
206
Index
PDP address (IPv4) 25

PDP Context data view (no. 1.2) 25
PDP Context Request parameters 178
PDTCH 51, 53, 57, 58, 63, 76
Peak Throughput (PDP Context Request) 25, 179
phone charger, choice of 170
phone mode 8, 83
pinpointing 6, 12, 78, 79
starting 80
stopping 81
Pocket menu 11, 88, 89
positioning
by GPS 12
by pinpointing 12
post-guard period 139
for passive measurements 144
Power Control Algorithm 38, 39, 40
Power Control Step Size 38, 39, 40
Power Display dialog (GSM) 154
Precedence Class (PDP Context Request) 25, 179
pre-guard period 139
for passive measurements 143
Progress data view (no. 1.8) 31
PTMSI 26
Q
QAM, usage of in HSDPA 42
Quick guide 146
R
RAC 22
last registered 26
RACo 45, 67, 68, 74
Radio Link Timeout 51
Radio Network Controller ID 23
RAT, current 22
Receive Bit Error Rate 51, 59
Reliability Class (PDP Context Request) 25, 179
replaying logfiles 84
controlling the replay 85
status icons for 86
Reset All command (General settings menu) 155
Reset Control Settings command 96
LZT 138 0240 R2A 207

resetting all General settings 155

resetting cell control settings 96
resumption of logfile upload 130
RLC data transfer performance (WCDMA) 40, 61
RLC/LLC BLER/retransmissions, graphic representation 185
RLC/MAC data transfer performance (GSM) 55, 64, 70, 76
presented in graph 70, 77
RLT 51
RNC ID 23
Roaming PLMN, time registered in 27
Routing Area Code 22
Routing Area Color 45, 67, 68, 74
Routing Area properties 34, 46, 74
Routing Area Update Failure Cause 180
RR Cause 180
RR events 108
RR Internal Cause 181
RRC events 109
RRC Failure Cause 181
RRC parameters 37
RRC Protocol Error Cause 182
RRC State 38, 39, 40
RSCP 21, 33, 34, 66, 68, 71, 73
presented in graph 67, 69, 71, 73
RSSI 61
RxLev 22, 45, 47, 49, 50, 53, 58, 63, 66, 67, 68, 74
Full/Sub values 154
RxQual 51, 59
Full/Sub values 154
S
Save Logfile To dialog 123
scan mode 8, 12, 83, 156
entering 156
Scanner data view 161
freezing 166
208
Index
scanning 8, 12, 156

Decode BSIC setting (GSM) 159
Ec/N0 threshold setting (WCDMA) 159
freezing the presentation 166
GSM custom list scan 157
GSM whole-band scan 157
Method setting 157
presentation of 161
GSM, custom list 164
GSM, whole band 163
WCDMA, CPICH scan (custom list) 165
WCDMA, network scan (whole band) 164
recording logfiles with scan data 161
RSSI threshold setting (WCDMA) 159
setting up a custom list of channels 158
setting up a scan 157
starting and stopping a scan 160
System setting (selection of cellular technology) 157
using a GPS 160
WCDMA CPICH scan 158
WCDMA network scan 158
scheduling logfile uploads 125
Scrambling Code 21, 22, 33, 34, 35, 66, 68, 71, 73
SDCCH 51, 53, 58, 63, 76
serving cell (GSM) 22, 45, 47, 48, 49, 50, 74
serving cell (WCDMA/GSM, always shown at bottom of display) 22
Serving Cell Barred 46, 47
Serving Cell BCCH 53, 58, 63
Serving Grant Index 43
Session events 110
SIB 3 36
SIB 5 36
SIR 38, 39, 40, 61, 72
presented in graph 72
SIR Target 38, 39, 40, 61, 72
SM Cause 182
SM events 105
snapshots of data views, taking 7, 15, 166
Sony Ericsson C905/C905a 5
Sony Ericsson W995 2
Sony Ericsson W995 EDGE 3
LZT 138 0240 R2A 209

Sony Ericsson W995a 2

speech codec (WCDMA) 39
speed 30
Stand-alone Dedicated Control Channel 51, 53, 58, 63, 76
Start Command Sequence command 88
Start FTP command 87
Start Logfile Recording command 84
Start Logfile Replay command 84
Stop Command Sequence command 88
Stop FTP command 87
Stop Logfile Recording command 84
Stop Logfile Replay command 84
Stop Logfile Upload command 87
storage medium, choice of 12
Streaming Settings dialog (command sequence) 138
Subchannel Number 52
support contact information 172
System Information Block 3 36
System Information Block 5 36
T
T3168 timer start value 56
T3212 timer current value 26
T3212 timer max value 26
T3314 timer current value 56
Tag Logfile command 86
TCH 51, 53, 57, 58, 63, 76
time using 27
Temporary Logical Link Identifier 26
Temporary Mobile Subscriber Identity 26
TEMS Automatic 113, 116, 121
TEMS Discovery 121
TEMS Investigation 11, 84, 85, 94, 113, 121
TEMS Pocket product package 145
TEMS Pocket version 145
TEMS Presentation 11, 84, 113, 121
throughput (GSM) 55, 64, 70, 76
throughput (WCDMA) 40, 44, 61, 62, 70
210
Index
Time Log data view (no. 1.4) 27

actions in 27
Timeslot Number 51, 58
timeslots used by GPRS 53, 63, 76
Timing Advance 51, 59
TLLI 26
TMSI 26
Tools menu 145
Traffic Channel 51, 53, 58, 63, 76
time using 27
Traffic Channel Type 53, 58, 76
transport block size on E-DCH (HSUPA) 43
transport channels
configuration of 38
data transfer performance (WCDMA) 40, 62, 70
direction 38
downlink BLER target 38
identity 38
maximum bit rate on 38
type 38
turning TEMS Pocket off 13
Tx Power 38, 39, 40, 51, 58, 61, 72
U
UARFCN 21, 22, 33, 34, 35, 61, 66, 68, 71, 73
UE Transmit Power 38, 39, 40, 51, 58, 61, 72
Upload Logfile dialog 123
UTRA Carrier RSSI 22
V
Video Settings dialog (command sequence) 136
Voice Codec dialog 95
voice codecs 52
setting preferred 95
Voice Settings dialog (command sequence) 135
W
W/G Cells data view (no. 1.1, in text format) 21
actions in 24
W/G Cells data view (no. 5.2, with graph) 68
LZT 138 0240 R2A 211

W/G Data data view (no. 5.3) 70

W/G Serving RSSI data view (no. 5.1) 66
WAP browser data views 60
GPRS view 63
visibility of 151
WCDMA view 61
WAP Data View dialog 151
WCDMA AMR data view (no. 2.6) 39
WCDMA C. Name data view (no. 2.3) 35
actions in 35
WCDMA Cell Id data view (no. 2.2) 34
actions in 34
WCDMA Cell Id Q-val dialog 155
WCDMA Cell Type 21, 33, 34, 66, 68, 71, 73
WCDMA Cells data view (no. 2.1, in text format) 33
actions in 33
WCDMA Cells data view (no. 5.6, with graph) 73
WCDMA Channel data view (no. 2.5) 38
WCDMA Data data view (no. 2.7) 40
actions in 41
WCDMA Serv. Cell data view (no. 2.4) 36
WCDMA Serving data view (no. 5.4) 71
WCDMA SIR data view (no. 5.5) 72
what was new in TEMS Pocket 7.0 5
what was new in TEMS Pocket 7.2 2
what’s new in this version of TEMS Pocket 1
WiFi, logfile uploading over 126
212
TEMS™ Optimization Solutions – the number one choice for operators
worldwide. For every stage of a wireless network’s life cycle and supporting
all major technologies, the TEMS portfolio helps operators maximize their
Quality of Service and get the most out of their network investment.
The experience and technological leadership of TEMS gives network

operators the strong partnership they need and a commitment to quality,
accuracy, and success.
TEMS Optimization Solutions – Making Wireless Better.

TEMS Pocket 7.3 For Sony Ericsson W995 and W995a - User's Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TEMS Pocket 7.3 For Sony Ericsson W995 and W995a - User's Manual

Uploaded by

Copyright:

Available Formats

TEMS™ Pocket 7.

© Ascom 2010. All rights reserved.

Publication number: LZT 138 0240 R2A

2. Overview of TEMS Pocket 8

LZT 138 0240 R2A i

3. Data Views: General 14

4. Data Views in Text Format 21

4.14. WCDMA AMR (View No. 2.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5. Data Views with Graphs 65

6. The Map View 78

LZT 138 0240 R2A iii

6.2.4. Pinpointing and Recording. . . . . . . . . . . . . . . . . . . . . . . . . . 80

7. TEMS Pocket Functions in the Activity Menu 83

8. The Pocket Menu 89

9. Cell Control Menu 91

10. Events Menu 97

11. Data Views Menu 112

12. GPS Menu 113

13. FTP Menu 117

LZT 138 0240 R2A v

14. Logfile Menu 121

15. Command Sequence Menu 131

16. Passive Measurement Menu 141

16.3. Notes on Message Buffering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

17. Tools Menu 145

18. General Settings Menu 151

19. Scanning 156

LZT 138 0240 R2A vii

19.3.4.2. Advanced WCDMA Settings . . . . . . . . . . . . . . . 159

20. Uploading TEMS Pocket Logfiles from the

21. Battery Charging Considerations 170

22. Support Contact Information 172

Appendix A. Parameter Values 173

A.9. GPS Fix Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Appendix B. Graphic Representation of

Appendix C. Icons Used in TEMS Pocket 187

Appendix D. Default Settings in TEMS Pocket

LZT 138 0240 R2A ix

D.2.3. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Appendix E. Cell File Format 194

Welcome to TEMS Pocket.

1.1. What’s New in TEMS Pocket 7.3

1.1.1. Presentation of Cell Names

1.1.2. Event-based Logfile Sifting

LZT 138 0240 R2A 1

1.1.3. Improved Logfile Naming

1.1.4. Coexistence with MRU (Mobile Receiving Unit)

1.2. What Was New in TEMS Pocket 7.2

1.2.1. New UMTS Phones: Sony Ericsson W995/W995a

1.2.2. New GSM Phone: Sony Ericsson W995 EDGE

1.2.3. Scanning (GSM and WCDMA)

1.2.4. Command Sequence Enhancements

LZT 138 0240 R2A 3

1.2.6. Passive Measurement

1.2.7. New GPS

1.2.8. Data Upload over WiFi

1.2.9. HSPA Data View

1.2.10. WCDMA AMR Data View

1.3. What Was New in TEMS Pocket 7.0

1.3.1. Phones: Sony Ericsson C905, C905a

LZT 138 0240 R2A 5

• 8.1 megapixel camera