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

TEMS POCKET 7.3.
2 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 R2B
Contents
Contents
1. Introduction
1.1. Whats New in TEMS Pocket 7.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1.1. Cell Identity Presentation Improvements . . . . . . . . . . . . . . . . 1 1.2. What Was New in TEMS Pocket 7.3. . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2.1. Presentation of Cell Names . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2.2. Event-based Logfile Sifting. . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2.3. Improved Logfile Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2.4. Coexistence with MRU (Mobile Receiving Unit). . . . . . . . . . . 2 1.3. What Was New in TEMS Pocket 7.2. . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3.1. New UMTS Phones: Sony Ericsson W995/W995a . . . . . . . . 3 1.3.2. New GSM Phone: Sony Ericsson W995 EDGE . . . . . . . . . . . 3 1.3.3. Scanning (GSM and WCDMA). . . . . . . . . . . . . . . . . . . . . . . . 3 1.3.4. Command Sequence Enhancements. . . . . . . . . . . . . . . . . . . 4 1.3.5. Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.6. Passive Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.7. New GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.8. Data Upload over WiFi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.9. HSPA Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.10. WCDMA AMR Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4. What Was New in TEMS Pocket 7.0. . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4.1. Phones: Sony Ericsson C905, C905a . . . . . . . . . . . . . . . . . . 6 1.4.2. Map View and Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4.3. Data Views with Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.4. Smarter Logfile Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.5. Cell Id Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.6. Snapshots of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.7. Importing and Exporting TEMS Pocket Settings . . . . . . . . . . 8
2. Overview of TEMS Pocket
2.1. Phone Mode vs. Scan Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2. Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2.1. Data Views with Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
LZT 138 0240 R2B
TEMS Pocket 7.3.2 for Sony Ericsson W995 and W995a Users Manual
2.3. Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6. Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1. Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.2. GPS Positioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.3. Positioning by Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7. Cell Control Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8. Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9. Scan Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10. Storage Medium: Phone Memory vs. Memory Stick. . . . . . . . . . . 2.11. Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12. Turning TEMS Pocket Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 11 12 12 12 13 13 13 13 13 13 14 14
3. Data Views: General
15
15 15 16 16 18
3.1. General Data View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2. The Built-in Help Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3. The Capture Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4. Other Data View Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5. Survey of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. Data Views in Text Format
22
22 25 26 27 28 28 29 31 31 32 34 34 35 35 36 36
4.1. W/G Cells (View No. 1.1) ............................. 4.1.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2. PDP Context (View No. 1.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3. MM/GMM (View No. 1.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4. Time Log (View No. 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5. FTP Data (View No. 1.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6. GPS (View No. 1.6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7. Map (View No. 1.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8. Progress (View No. 1.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9. WCDMA Cells (View No. 2.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10. WCDMA Cell Id (View No. 2.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11. WCDMA C. (Cell) Name (View No. 2.3) . . . . . . . . . . . . . . . . . . . . 4.11.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
Contents
4.12. WCDMA Serv. Cell (View No. 2.4) . . . . . . . . . . . . . . . . . . . . . . . 37 4.13. WCDMA Channel (View No. 2.5) . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.14. WCDMA AMR (View No. 2.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.15. WCDMA Data (View No. 2.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.15.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 4.16. HSPA Data (View No. 2.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.17. GSM Cells (View No. 3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 4.17.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 4.18. GSM Cell Id (View No. 3.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 4.18.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.19. GSM Cell Name (View No. 3.3). . . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.19.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.20. GSM BA List (View No. 3.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.20.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.21. GSM Serving Cell (View No. 4.1) . . . . . . . . . . . . . . . . . . . . . . 51 4.22. GPRS Data (View No. 4.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.22.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4.23. GPRS Info (View No. 4.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 4.24. GSM C/I Info (View No. 4.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.25. GSM AMR (View No. 4.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 4.26. The WAP Browser Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 4.26.1. WCDMA WAP Browser Data View . . . . . . . . . . . . . . . . . 62 4.26.2. GPRS WAP Browser Data View . . . . . . . . . . . . . . . . . . . 64
5. Data Views with Graphs
66
5.1. W/G Serving RSSI (View No. 5.1) . . . . . . . . . . . . . . . . . . . . . . . . 67 5.2. W/G Cells (View No. 5.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 5.3. W/G Data (View No. 5.3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.4. WCDMA Serving (View No. 5.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 5.5. WCDMA SIR (View No. 5.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.6. WCDMA Cells (View No. 5.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.7. GSM Cells (View No. 5.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.8. GSM Data (View No. 5.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6. The Map View
79
6.1. Loading a Map Image into the Map View . . . . . . . . . . . . . . . . . . . . 79 6.2. Pinpointing Your Test Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 6.2.1. Setting the Map Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
LZT 138 0240 R2B
iii
6.2.2. Customizing the Appearance of Route Markers . . . . . . . . . 6.2.3. Entering Map Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.4. Pinpointing and Recording. . . . . . . . . . . . . . . . . . . . . . . . . . 6.3. Positioning the Map Geographically . . . . . . . . . . . . . . . . . . . . . . . .
80 81 81 83
7. TEMS Pocket Functions in the Activity Menu
84
84 84 85 85 85 86 87 87 88 88 88 89 89
7.1. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2. Insert Filemark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3. Start/Stop Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.1. Icons Used for Logfile Recording. . . . . . . . . . . . . . . . . . . . . 7.4. Start/Stop Logfile Replay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.1. Replay Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.2. Icons Used for Logfile Replay . . . . . . . . . . . . . . . . . . . . . . . 7.5. Tag Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7. Start FTP/Stop FTP/Stop Logfile Upload . . . . . . . . . . . . . . . . . . . . 7.8. Connect/Disconnect GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9. Start/Stop Command Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10. Pocket Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8. The Pocket Menu
90
8.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
9. Cell Control Menu
92
92 92 93 94 94 95 95 96 96 97 97
9.1. Icons Used for Cell Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2. Lock to RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3. Lock Cell WCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4. Lock ARFCN GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5. Lock Band WCDMA, Lock Band GSM . . . . . . . . . . . . . . . . . . . . . . 9.6. Interplay between Locking Functions . . . . . . . . . . . . . . . . . . . . . . . 9.7. Comparison with Locking Functions in TEMS Investigation . . . . . . 9.8. Voice Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.9. HS Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.10. Ignore Cell Barred. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.11. Reset Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Contents
10. Events Menu
98
10.1. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 10.1.1. Viewing the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 10.1.2. Clearing the Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 10.1.3. Enabling/Disabling Event Logging and Sound . . . . . . . . . . 99 10.1.4. Shortcuts to Event Settings and Event Counters . . . . . . . 100 10.2. Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 10.2.1. Viewing Event Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . 100 10.2.2. Modifying Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . 101 10.3. Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 10.3.1. Viewing Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . 102 10.3.2. Resetting Event Counters . . . . . . . . . . . . . . . . . . . . . . . . 103 10.4. Event Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 10.5. List of Logged Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 10.5.1. CC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 10.5.2. MM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 10.5.3. SM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 10.5.4. GMM Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 10.5.5. IRAT Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 10.5.6. RR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 10.5.7. RRC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 10.5.8. Session Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11. Data Views Menu 12. GPS Menu
113 114
12.1. Using GPS Units with TEMS Pocket: Introduction . . . . . . . . . . . 114 12.1.1. Using the Built-in GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 12.1.2. Using an External GPS . . . . . . . . . . . . . . . . . . . . . . . . . . 115 12.2. GPS Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 12.3. GPS Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 12.4. GPS Time Synch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
13. FTP Menu
118
13.1. FTP Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 13.2. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
LZT 138 0240 R2B
14. Logfile Menu
122
122 123 124 124 124 125 126 127 129 129 130 131 131
14.1. Logfiles in TEMS Pocket: Introduction . . . . . . . . . . . . . . . . . . . . 14.1.1. Logfile Naming Format. . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1.1.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2. Save Logfile To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3. Upload Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.1. Conflicts with Other TEMS Pocket Functions . . . . . . . . . 14.3.2. Setting an Upload Schedule . . . . . . . . . . . . . . . . . . . . . . 14.4. WiFi Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4.1. Relation to Upload over Cellular Network . . . . . . . . . . . . 14.4.2. Conflicts with Other TEMS Pocket Functions . . . . . . . . . 14.5. Compress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6. FTP Resume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15. Command Sequence Menu
132
132 133 133 135 136 137 137 138 139 139 140 140 140 140 141 141 141 141
15.1. Introduction to Command Sequences. . . . . . . . . . . . . . . . . . . . . 15.2. Defining Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.1. Global Command Sequence Settings . . . . . . . . . . . . . . . 15.2.2. Adding an Action to a Command Sequence ....... 15.2.3. Voice Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.4. Video Action Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.5. FTP Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.6. HTTP Action Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.7. Streaming Action Settings . . . . . . . . . . . . . . . . . . . . . . . . 15.2.8. Idle Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.9. Pre-guard and Post-guard Periods . . . . . . . . . . . . . . . . . 15.2.10. Saving Default Settings for an Action Type . . . . . . . . . . 15.2.11. The Assembled Command Sequence . . . . . . . . . . . . . . 15.2.12. Rearranging Actions in a Command Sequence. . . . . . . 15.2.13. Deleting an Action from a Command Sequence . . . . . . 15.3. Viewing and Editing Command Sequences . . . . . . . . . . . . . . . . 15.4. Deleting Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 15.5. Running Command Sequences . . . . . . . . . . . . . . . . . . . . . . . . .
16. Passive Measurement Menu
142
16.1. Passive Measurement Action Settings . . . . . . . . . . . . . . . . . . . . 143 16.2. Prioritization of Passive Measurements . . . . . . . . . . . . . . . . . . . 144
vi
Contents
16.3. Notes on Message Buffering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 16.3.1. Pre-guard Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 16.3.2. Post-guard Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
17. Tools Menu
146
17.1. About Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 17.2. Quick Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 17.3. Import Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 17.3.1. Importing Settings Files from TEMS Pocket Versions Older than 7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 17.4. Export Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 17.4.1. Managing Export Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 17.5. Import Cell File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
18. General Settings Menu
152
18.1. WAP Data View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 18.2. Data View Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 18.3. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 18.4. Backlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 18.5. Cell Id Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 18.6. Cell Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 18.7. Power Display (GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 18.8. Measure Mode Display (GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . 155 18.9. Auto Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 18.10. WCDMA Cell Id Q-val . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 18.11. Reset All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
19. Scanning
157
19.1. Introduction to Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 19.2. How to Enter Scan Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 19.3. Setting Up a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 19.3.1. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 19.3.2. Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 19.3.2.1. GSM Scanning Methods . . . . . . . . . . . . . . . . . . . . 158 19.3.2.2. WCDMA Scanning Methods . . . . . . . . . . . . . . . . . 159 19.3.3. Edit Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 19.3.4. Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 19.3.4.1. Advanced GSM Settings . . . . . . . . . . . . . . . . . . . . 160
LZT 138 0240 R2B
vii
19.3.4.2. Advanced WCDMA Settings . . . . . . . . . . . . . . . 19.3.5. Notes on Changing the Scan Setup. . . . . . . . . . . . . . . . . 19.4. Starting and Stopping a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5. Other TEMS Pocket Functionality Available in Scan Mode . . . . 19.5.1. Using a GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5.2. Recording Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.6. Scan Presentation: Scanner View (No. 1.1) . . . . . . . . . . . . . . . . 19.6.1. GSM Scanning Presentation . . . . . . . . . . . . . . . . . . . . . . 19.6.1.1. Whole-band Scan . . . . . . . . . . . . . . . . . . . . . . . . . 19.6.1.2. Custom List Scan . . . . . . . . . . . . . . . . . . . . . . . . . 19.6.2. WCDMA Scanning Presentation . . . . . . . . . . . . . . . . . . . 19.6.2.1. Network (Whole-band) Scan . . . . . . . . . . . . . . . . . 19.6.2.2. CPICH (Custom List) Scan . . . . . . . . . . . . . . . . . . 19.6.3. Freezing the Scanner View . . . . . . . . . . . . . . . . . . . . . . . 19.7. GPS View (No. 1.2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8. The Built-in Help Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.9. The Capture Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
160 161 161 161 161 162 162 164 164 165 165 165 166 167 167 167 167
20. Uploading TEMS Pocket Logfiles from the Phone File System 21. Battery Charging Considerations
169 171
21.1. Choice of Phone Charger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 21.2. Using the Phones Built-in GPS . . . . . . . . . . . . . . . . . . . . . . . . . 171 21.3. Using a TEMS Pocket Command Sequence . . . . . . . . . . . . . . . 171
22. Support Contact Information Appendix A. Parameter Values
173 174
174 174 175 176 177 177 177 178
A.1. Activate PDP Context Failure Cause . . . . . . . . . . . . . . . . . . . . . . A.2. Automatic Upload Failure Cause . . . . . . . . . . . . . . . . . . . . . . . . . A.3. CC Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4. CCCH Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.5. Channel Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.6. Deactivate PDP Context Cause . . . . . . . . . . . . . . . . . . . . . . . . . . A.7. GMM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8. GPRS Network Mode of Operation . . . . . . . . . . . . . . . . . . . . . . .
viii
Contents
A.9. GPS Fix Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 A.10. MM Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 A.11. PDP Context Request Parameters . . . . . . . . . . . . . . . . . . . . . . . 179 A.11.1. Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 A.11.2. Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 A.11.3. Peak Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 A.11.4. Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 A.11.5. Mean Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 A.12. Routing Area Update Failure Cause . . . . . . . . . . . . . . . . . . . . . . 181 A.13. RR Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 A.14. RR Internal Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 A.15. RRC Failure Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 A.16. RRC Protocol Error Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 A.17. SM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Appendix B. Graphic Representation of Parameter Values
185
B.1. C/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 B.2. Ec/N0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 B.3. FER, RLC/LLC BLER/Retransmissions . . . . . . . . . . . . . . . . . . . . 186 B.4. RLC DL/UL Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 B.5. RxLev, RSCP, RSSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 B.6. RxQual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 B.7. Tx Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Appendix C. Icons Used in TEMS Pocket Appendix D. Default Settings in TEMS Pocket Menus
188
190
D.1. Activity Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 D.1.1. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 D.1.2. Scanner Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 D.1.2.1. GSM Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 D.1.2.2. WCDMA Scanning . . . . . . . . . . . . . . . . . . . . . . . . . 190 D.2. Pocket Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 D.2.1. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 D.2.2. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
LZT 138 0240 R2B
ix
D.2.3. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.4. GPS Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.5. FTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.6. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.7. Command Sequence Menu. . . . . . . . . . . . . . . . . . . . . . . . D.2.8. Passive Measurement Menu. . . . . . . . . . . . . . . . . . . . . . . D.2.9. Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.10. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . .
191 191 191 191 192 193 193 193
Appendix E. Cell File Format Index
195 197
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.2 (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.
1.1.1.
Whats New in TEMS Pocket 7.3.2

Cell Identity Presentation Improvements
Cell Identity data is presented with CGI or with a cell name (in case a valid cell file has been imported), in both idle and dedicated/connected mode for both GSM and WCDMA. In case a valid CGI can not be retrieved from the network (for example in connected mode for WCDMA), ARFCN/UARFCN and BSIC/SC is used combined with a GPS position (if GPS is enabled) to be translated into Cell Identity with the help of an imported cell file. If no cell file has been imported into the TEMS Pocket application, Cell Identities (CGI) are buffered in idle mode and are then correlated with the phones position in dedicated/connected mode.
1.2.
What Was 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.
LZT 138 0240 R2B
1.2.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.2.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.
1.2.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.2.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.3.
1.3.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
1.3.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.3.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 userselected set of up to 200 ARFCNs. The ARFCNs can be picked from arbitrary bands. BSIC decoding helps identify the signal source.
LZT 138 0240 R2B
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.3.4.
Command Sequence Enhancements
The command sequence function was greatly expanded and enhanced in this release. New features were: 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.3.5.
Streaming
TEMS Pocket 7.2 can test video streaming over the RTSP protocol by means of the phones integrated media player. Data can be streamed from a userdefined 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.3.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.
1.3.7.
New GPS
The GPS that could optionally be ordered with TEMS Pocket 7.2 is the GlobalSat BT-359.
1.3.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.3.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 ETFCI, average Serving Grant Index, average transport block size, and UE happy rate.
LZT 138 0240 R2B
1.3.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.4.
(TEMS Pocket 7.1 is a Nokia-based release.)
1.4.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 8.1 megapixel camera Integrated GPS
1.4.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.4.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.4.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 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.4.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 phones position in dedicated/connected mode. The buffer is cleared when the phone is restarted.
1.4.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 users 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.
LZT 138 0240 R2B
1.4.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.
Chapter 2. Overview of TEMS Pocket
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:
LZT 138 0240 R2B
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 phones 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 combine text-format content (similar to that of ordinary data views) with a line chart showing how one or several parameters
10
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:
LZT 138 0240 R2B
11
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 phones main menu: Settings General Pocket menu. Note: TEMS Pocket settings are always saved in the phones 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 phones 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.
2.6.1.
Logfiles
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.37.4 and chapter 14.
12
2.6.2.
GPS Positioning
TEMS Pocket supports positioning of data using GPS. You can use either the phones 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 phones 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 phones 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.
LZT 138 0240 R2B
13
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.
14
Chapter 3. Data Views: General
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.
LZT 138 0240 R2B
15
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.
16
Specifics on data view actions are found in the subsequent sections.
LZT 138 0240 R2B
17
3.5.
No. 1.1
Survey of Data Views

View Name W/G Cells Description Combines the WCDMA Cells (2.1) and GSM Cells (3.1) views into a dual mode view. Displays PDP addresses and PDP context settings for each address, including NSAPI and APN. Displays identities common to WCDMA and GSM, such as TMSI, P-TMSI, and CGI of last registered network. Displays time spent by the phone in various states (MM states; idle/ dedicated). Displays information on the current FTP session, such as FTP server address, throughput, and transferred byte count. Displays essential GPS data: latitude/ longitude, altitude, speed, number of satellites, fix quality, time and date. Not a data view (but has a number). See chapter 6. Displays the progress of a command sequence that is being executed. Displays UARFCN, cell status, scrambling code, RSCP, Ec/N0, and path loss for each cell in active set and monitored/detected neighbor sets. Page 21
1.2
PDP Context
25
1.3
MM/GMM
26
1.4
Time Log
27
1.5
FTP Data
28
1.6
GPS
30
1.7 1.8
Map Progress
78 31
2.1
WCDMA Cells
33
18
No. 2.2
View Name WCDMA Cell Id
Description Displays UARFCN, scrambling code, CI, and RSCP for each cell in the active set and monitored/detected neighbor sets. Displays UARFCN, scrambling code, CI, and cell name for each cell in the active set and monitored/detected neighbor sets. Displays various items from System Information messages. Displays SIR and SIR target, power control information, RRC state, and information on transport channels used. Displays SIR and SIR target, power control information, RRC state, AMR codecs selected on uplink and downlink, and statistics on AMR codec utilization. Displays SIR and SIR target, power control information, RRC state, and information on uplink and downlink RLC and transport channel performance. Displays HSDPA CQI, requested and actual block sizes, data transfer rate, and block error rates. Also displays HSUPA E-TFCI, SGI, TBS, DTX rate, happy rate, and retransmission rate. Displays a subset of the WCDMA Data view (2.7) during WAP browsing.
Page 34
2.3
WCDMA C. Name
35
2.4 2.5
WCDMA Serv. Cell WCDMA Channel
36 38
2.6
WCDMA AMR
39
2.7
WCDMA Data
40
2.8
HSPA Data
42
WCDMA WAP browser view
61
LZT 138 0240 R2B
19
No. 3.1
View Name GSM Cells
Description Displays ARFCN, BSIC, RxLev, C1/ C31, and C2/C32 for the serving cell and each neighbor. Also presents system information data for cell access, selection, and location. Displays ARFCN, LAC, CI, and RxLev for the serving cell and each neighbor. Also presents system information data for cell access, selection, and location. Displays ARFCN, BSIC, CI, and cell name for the serving cell and each neighbor. Displays the GSM BA neighbor list as received from the network and shows which BCCH ARFCN the list was received from. Displays system information data on 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). Displays traffic channel ARFCN, timeslots and coding schemes used, and LLC and RLC/MAC performance on uplink and downlink. Displays traffic channel ARFCN, timeslots and coding schemes used, and vital GPRS/EGPRS configuration parameters. Displays C/I information for the most frequently utilized timeslot on each traffic channel in use.
Page 45
3.2
GSM Cell Id
47
3.3
GSM Cell Name
48
3.4
GSM BA List
49
4.1
GSM Serving Cell
50
4.2
GPRS Data
53
4.3
GPRS Info
56
4.4
GSM C/I Info
57
20
No. 4.5
View Name GSM AMR
Description Displays GSM logical channel information, AMR codecs selected on uplink and downlink, and statistics on AMR codec utilization. Displays a subset of the GPRS Data view (4.2) during WAP browsing. Graph displays WCDMA serving cell RSCP/GSM serving cell RxLev. Graph displays WCDMA serving cell RSCP/GSM serving cell RxLev; ditto for three strongest WCDMA/GSM neighbors. Graph displays WCDMA transport channel and GSM RLC/MAC data transfer rates. Graph displays WCDMA serving cell RSCP and UTRA Carrier RSSI. Graph displays SIR Target and actual SIR. Graph displays RSCP for serving cell and three strongest neighbors. Graph displays RxLev for serving cell and three strongest neighbors. Graph displays RLC/MAC data transfer rate.
Page 58
GPRS WAP browser view W/G Serving RSSI W/G Cells
63
5.1 5.2
66 68
5.3
W/G Data
70
5.4 5.5 5.6 5.7 5.8
WCDMA Serving WCDMA SIR WCDMA Cells GSM Cells GSM Data
71 72 73 74 76
Regarding the views shown in scan mode, see chapter 19.
LZT 138 0240 R2B
21
4.
Data Views in Text Format
4.1.
W/G Cells (View No. 1.1)

Lines 14 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 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
Screenshot
Key (used for convenience in the manual; not shown in this format in the phone display)
Ec/No: Ec/N0 (dB), numeric/graphic PL: Pathloss (dB); this measurement appears only when ordered by the network
22
Chapter 4. Data Views in Text Format
Lines 58 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 68: Three strongest GSM neighbors Screenshot (footer with CGI) G: GSM channel type for serving cell: One of B: BCCH; P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH (with values on the rest of the line): Inter-RAT, GSM neighbor measured in WCDMA mode ARFC: ARFCN, Absolute Radio Frequency Channel Number BS: BSIC, Base Station Identity Code RxLev: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic Lines 910 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} Key (footer with cell name) (U)ARFC: WCDMA: Serving cell UARFCN; GSM: Serving cell BCCH ARFCN 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
Screenshot (footer with cell name)
LZT 138 0240 R2B
23
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. Screenshot (footer with CGI) In all data views that follow, the view footer uses the CGI mode of presentation; but cell names can 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 with cell name) LAC: Serving cell Location Area Code 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)
24
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.
LZT 138 0240 R2B
25
4.2.
PDP Context (View No. 1.2)

Lines 16 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}
Screenshot
R: Reliability Class {0 ... 5} 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 78 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.
26
4.3.
MM/GMM (View No. 1.3)

Lines 14 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}
Screenshot
PTMSI: Packet TMSI (hex) 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 Lines 56 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
There are no actions associated with this data view.
LZT 138 0240 R2B
27
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)
4.4.1.
Data View Actions
You can reset all counters in this view by choosing Reset time log.
28
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).
Key
CThpUL: Current uplink application-level FTP 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.
LZT 138 0240 R2B
29
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 Lines 78 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
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. There are no actions associated with this data view.
30
4.6.
GPS (View No. 1.6)

Lines 18 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.
Screenshot
No. of satellites: The number of satellites seen by 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. Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
4.7.
Map (View No. 1.7)
See chapter 6.
LZT 138 0240 R2B
31
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 25 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 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.
Key
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.
32
Lines 25 (continued) ActionInfo (continued) For passive measurements, the possible states are: Screenshot Measurement in progress: The passive measurement is running. Guard time: Passive measurement post-guard time.
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 Lines 78 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
LZT 138 0240 R2B
33
4.9.
WCDMA Cells (View No. 2.1)

Up to eight cells from the WCDMA active set can be shown. Lines 18 W: WCDMA cell type: One of S: Serving cell A: Active set member M: Monitored neighbor D: Detected neighbor (with values on the rest of the line): Inter-RAT, WCDMA neighbor measured in GSM mode UARFC: UARFCN SC: Scrambling Code RSCP: Received Signal Code Power (dBm), numeric/graphic Ec/No: Ec/N0 (dB), numeric/graphic PL: Pathloss (dB); this measurement appears only when ordered by the network
Screenshot
Key
Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
4.9.1.
Data View Actions
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.
34
4.10.
WCDMA Cell Id (View No. 2.2)

Up to eight cells from the WCDMA active set can be shown. Lines 18 W: WCDMA cell type: One of S: Serving cell A: Active set member M: Monitored neighbor D: Detected neighbor (with values on the rest of the line): Inter-RAT, WCDMA neighbor measured in GSM mode UARFC: UARFCN SC: Scrambling Code A: (Lines 28) 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 : Unknown CI: Cell Identity, 16 bits (= C-Id: see 3GPP 25.401, section 6.1.5) RSCP: Received Signal Code Power (dBm), numeric/graphic. You can have this replaced by Ec/N0 by changing the setting WCDMA CellId qval in the Pocket menu under General settings; see section 18.10. Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot
Key
4.10.1.
Data View Actions
LZT 138 0240 R2B
35
4.11.
WCDMA C. (Cell) Name (View No. 2.3)

Up to eight cells from the WCDMA active set can be shown. Lines 18 UARFC: UARFCN SC: Scrambling Code CI: Cell Identity, 16 bits (= C-Id: see 3GPP 25.401, section 6.1.5)
Screenshot
Cell Name: Name of cell, taken from XML file; see 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. Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
Cell name presentation in help bubble
4.11.1.
Data View Actions
36
4.12.
WCDMA Serv. Cell (View No. 2.4)

Lines 12 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 {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 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 45 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
Screenshot
Key
LZT 138 0240 R2B
37
Lines 45 (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 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} Line 6 Here are shown RRC parameters; see 3GPP 25.304, sections 5.2.6.1.45. 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 78 are the same as the two bottom lines in the W/G Cells view: see section 4.1. There are no actions associated with this data view.
Screenshot
Key
38
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 38 These lines show the configuration of up to 6 transport channels:
Key
ChId: Transport Channel Id ChT/D: Transport Channel Type and Direction DLBT: Downlink BLER Target (%) Rate: Maximum transport channel bit rate (bit/s) Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
LZT 138 0240 R2B
39
4.14.
WCDMA AMR (View No. 2.6)

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 Line 3 Codec: Speech codec: AMR (narrowband) or AMR-WB (wideband)
Key
Lines 47 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. Lines 89 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
40
4.15.
WCDMA Data (View No. 2.7)

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 36 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.
LZT 138 0240 R2B
41
Screenshot
Key
4.15.1.
Data View Actions
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).
42
4.16.
HSPA Data (View No. 2.8)

Lines 13, general note: All data presented here is HSDPA data and applies to the phones 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 HSDSCH. 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.
LZT 138 0240 R2B
43
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 retransmissions). BL1: Block error rate on HS-DSCH for first retransmission. 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 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.
Screenshot
Key
44
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 view (see section 4.15) and thus valid for WCDMA R99 and HSUPA alike. Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot
LZT 138 0240 R2B
45
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 d: Hopping PDTCH BC: Serving Cell BCCH ARFCN BS: Base Station Identity Code (BSIC) RxLv: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic 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:
Screenshot
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
46
Lines 27 (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 R: Same LA, different RA L: Different LA 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} Key B: BS-PA-MFRMS, number of multiframes between paging subgroups {2 ... 9} CB: Serving cell barred {B: Barred, : Not Barred} Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot
4.17.1.
Data View Actions
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.
LZT 138 0240 R2B
47
4.18.
GSM Cell Id (View No. 3.2)

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, d: Hopping PDTCH 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 27 (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} Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
48
4.18.1.
Data View Actions
4.19.
GSM Cell Name (View No. 3.3)

Line 1 (GSM serving cell) BC: Serving Cell BCCH ARFCN BS: Base Station Identity Code (BSIC) CI: Serving Cell Identity Cell Name: Name of cell, taken from XML file; see section 17.5. Lines 28 (GSM neighbors)
Screenshot
NC1 ... NC7: Neighbor Cell BCCH ARFCN of seven strongest neighbors BS: Base Station Identity Code (BSIC) CI: Serving Cell Identity Cell Name: Name of cell, taken from XML file; see 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
LZT 138 0240 R2B
49
4.19.1.
Data View Actions
4.20.
GSM BA List (View No. 3.4)

Line 1 (serving cell) L: Logical Channel B: BCCH P: PBCCH p: Hopping PBCCH S: SDCCH s: Hopping SDCCH T: TCH t: Hopping TCH D: PDTCH d: Hopping PDTCH BCCH: Serving Cell BCCH ARFCN BSIC: Base Station Identity Code (BSIC) RxLev: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic Lines 29 (neighbor list = BA list) NC1 ... NC32: BCCH ARFCNs of all neighbors of the serving cell (up to 32 cells).
Screenshot
Key
4.20.1.
Data View Actions
You can lock on any cell that is listed as a neighbor in this view. The procedures for locking and unlocking are the same as in the W/G Cells view; see section 4.1.1.
50
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 RxLv: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic DSC: Downlink Signaling Counter, current value (idle mode only)
Screenshot idle mode
DSM: Downlink Signaling Counter, max value (= 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 dedicated mode
CN: CCCH configuration, number of BCCH/CCCH 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
LZT 138 0240 R2B
51
Line 3 (dedicated mode) L: Logical Channel P: PBCCH p: Hopping PBCCH S: SDCCH s: Hopping 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
52
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 AFR = Voice, AMR Full Rate 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} Lines 67 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot idle mode
Screenshot dedicated mode
LZT 138 0240 R2B
53
4.22.
GPRS Data (View No. 4.2)

Line 1 L: Logical Channel: B for BCCH BCCH: Serving Cell BCCH ARFCN BSIC: Base Station Identity Code (BSIC) RxLev: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic Line 2
Screenshot
T: Traffic Channel Type: P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH TC: Traffic Channel (TCH ARFCN) or Stand-alone Dedicated Control Channel (SDCCH ARFCN) or Packet Dedicated Traffic Channel (PDTCH ARFCN) Timeslots: Timeslots used on uplink and downlink. The timeslots are represented by the numbers 07, 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
Key
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
54
Line 3 C/I: Carrier-to-interference ratio in dB for the traffic channel currently indicated by TC on line 2. That is, for hopping channels the displaying of C/I values is synchronized with the traversal of the hopping list; 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
LZT 138 0240 R2B
55
Lines 58 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. Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
4.22.1.
Data View Actions
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).
56
4.23.
GPRS Info (View No. 4.3)

Lines 14 are the same as in the GPRS Data view: see section 4.22. Lines 56 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 78 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} Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
LZT 138 0240 R2B
57
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 18 ARFCN: TCH or PDTCH ARFCN (channels in hopping list)
Screenshot
C/I: C/I value in dB for this traffic channel, numeric/ graphic Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
58
4.25.
GSM AMR (View No. 4.5)

Line 1 L: Logical Channel: B for BCCH BCCH: Serving Cell BCCH ARFCN BSIC: Base Station Identity Code (BSIC) RxLev: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic Line 2
Screenshot
T: Traffic Channel type: P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH 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.
Key
TS: Timeslot Number TxPwr: UE Transmit Power (dBm), numeric/ graphic Line 3 C/I: Carrier-to-interference ratio in dB for the traffic channel currently indicated by TC on line 2. 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.
LZT 138 0240 R2B
59
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 Screenshot Lines 47 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. Lines 89 are the same as the two bottom lines in the W/G Cells view: see section 4.1. There are no actions associated with this data view.
Key
60
4.26.
The WAP Browser Data Views
While the WAP browser (activated from the phones 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.
LZT 138 0240 R2B
61
4.26.1.
WCDMA WAP Browser Data View

Line 1 UARFCN: Serving cell UARFCN SC: Scrambling Code RSSI: Serving cell RSSI (dBm) Line 2 SIR: Signal-to-Interference Ratio (dB) SIR_TG: SIR Target (dB)
Screenshot
TxPwr: UE Transmit Power (dBm) In lines 34, 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
62
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
LZT 138 0240 R2B
63
4.26.2.
GPRS WAP Browser Data View

Line 1 L: Logical Channel: B for BCCH BCCH: Serving Cell BCCH ARFCN BSIC: Base Station Identity Code, BSIC RxLev: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic MCSd: EGPRS modulation coding scheme on downlink {MCS1 ... MCS9}
Screenshot Line 2 T: Traffic Channel type: P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH 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. Timeslots: Timeslots used on uplink and downlink. The timeslots are represented by the numbers 07, 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
Key
Example: means that TS 1, 2, 3, and 4 are being used on the downlink and TS 3 is being used on the uplink. MCSu: EGPRS modulation coding scheme on uplink {MCS1 ... MCS9}
64
In lines 34, all values are combined values computed over all used channels. Line 3, left: DL (downlink, LLC) Rate: Total LLC downlink instantaneous data transfer rate in kbit/s or Mbit/s 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 transfer rate in kbit/s or Mbit/s Key BLER: Percentage of RLC/MAC downlink data blocks erroneously decoded Line 4, right: UR (uplink, RLC/MAC) Rate: Total RLC/MAC uplink instantaneous data transfer rate in kbit/s or Mbit/s Retr: Percentage of RLC/MAC uplink data blocks retransmitted
LZT 138 0240 R2B
65
5.
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.
66
Chapter 5. Data Views with Graphs
5.1.
W/G Serving RSSI (View No. 5.1)

Line 1 shows the strongest WCDMA cell. W: WCDMA cell type: One of S: Serving cell A: Active set member (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
Screenshot
RSCP: Received Signal Code Power (dBm), numeric/graphic Ec/No: Ec/N0 (dB), numeric/graphic PL: Pathloss (dB); this measurement appears only when ordered by the network Line 2 shows the strongest GSM cell: in GSM mode, the GSM serving cell; in WCDMA mode, the strongest (inter-RAT) GSM neighbor measured.
Key
L: Logical Channel B: BCCH P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH BC: Serving Cell BCCH ARFCN BS: Base Station Identity Code (BSIC) RxLv: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic
LZT 138 0240 R2B
67
Line 2 (continued) 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: C1: Pathloss Criterion C1 C2: Cell Reselection Criterion C2 Screenshot 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 Graph Green line: Received Signal Code Power, RSCP (dBm) for strongest WCDMA cell Blue line: Received Signal Strength, RxLev (dBm) for strongest GSM cell Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
68
5.2.
W/G Cells (View No. 5.2)

Line 1 shows the strongest WCDMA cell. W: WCDMA cell type: One of S: Serving cell A: Active set member (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
Screenshot
RSCP: Received Signal Code Power (dBm), numeric/graphic Ec/No: Ec/N0 (dB), numeric/graphic PL: Pathloss (dB); this measurement appears only when ordered by the network Line 2 shows the strongest GSM cell: in GSM mode, the GSM serving cell; in WCDMA mode, the strongest (inter-RAT) GSM neighbor measured.
Key
L: Logical Channel B: BCCH P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH BC: Serving Cell BCCH ARFCN BS: Base Station Identity Code (BSIC) RxLv: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic 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: C1: Pathloss Criterion C1 C2: Cell Reselection Criterion C2
LZT 138 0240 R2B
69
Line 2 (continued) 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 Graph Screenshot Green bars: Received Signal Code Power, RSCP (dBm) for strongest WCDMA cell 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) Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1. Key
70
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
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 URetr: Percentage of data blocks retransmitted on uplink, numeric/graphic
Key
Graph 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 Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
LZT 138 0240 R2B
71
5.4.
WCDMA Serving (View No. 5.4)

Lines 12 show the two strongest WCDMA cells. W: WCDMA cell type: One of S: Serving cell A: Active set member M: Monitored neighbor D: Detected neighbor (with values on the rest of the line): Inter-RAT, WCDMA neighbor measured in GSM mode UARFC: UARFCN
Screenshot
SC: Scrambling Code RSCP: Received Signal Code Power (dBm), numeric/graphic Ec/No: Ec/N0 (dB), numeric/graphic PL: Pathloss (dB); this measurement appears only when ordered by the network Graph Grey bars: Received Signal Code Power, RSCP (dBm) for strongest WCDMA cell Blue bars: UTRA Carrier RSSI (dBm) Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
72
5.5.
WCDMA SIR (View No. 5.5)

Line 1 SIR: Actual Signal-to-Interference Ratio, SIR (dB) SIR_TG: SIR Target (dB) TxPwr: UE Transmit Power (dBm), numeric/ graphic Graph Grey bars: SIR Target (dB)
Screenshot
Red line: Actual SIR (dB) Lines 23 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
LZT 138 0240 R2B
73
5.6.
WCDMA Cells (View No. 5.6)

Lines 12 show the two strongest WCDMA cells. W: WCDMA cell type: One of S: Serving cell A: Active set member M: Monitored neighbor D: Detected neighbor (with values on the rest of the line): Inter-RAT, WCDMA neighbor measured in GSM mode UARFC: UARFCN
Screenshot
SC: Scrambling Code RSCP: Received Signal Code Power (dBm), numeric/graphic Ec/No: Ec/N0 (dB), numeric/graphic PL: Pathloss (dB); this measurement appears only when ordered by the network Graph Green bars: Received Signal Code Power, RSCP (dBm) for strongest WCDMA cell Lines: Received Signal Code Power, RSCP (dBm) for three strongest WCDMA neighbors Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
74
5.7.
GSM Cells (View No. 5.7)

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, d: Hopping PDTCH BC: Serving Cell BCCH ARFCN BS: Base Station Identity Code (BSIC)
Screenshot
RxLv: Received Signal Strength (unit userconfigurable: see section 18.7), numeric/graphic 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: C1: Pathloss Criterion C1 C2: Cell Reselection Criterion C2
Key
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 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 R: Same LA, different RA L: Different LA P: PLMN not matching : Unknown
LZT 138 0240 R2B
75
Graph Blue bars: Received Signal Strength, RxLev (dBm) for GSM serving cell Lines: Received Signal Strength, RxLev (dBm) for three strongest GSM neighbors Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1. Screenshot
Key
76
5.8.
GSM Data (View No. 5.8)

Line 1 T: Traffic Channel Type: P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH T: TCH, t: Hopping TCH D: PDTCH, d: Hopping PDTCH TC: Traffic Channel (TCH ARFCN) or Stand-alone Dedicated Control Channel (SDCCH ARFCN) or Packet Dedicated Traffic Channel (PDTCH ARFCN) Timeslots: Timeslots used on uplink and downlink. The timeslots are represented by the numbers 07, 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
Screenshot
Key
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 Line 2 (RLC/MAC protocol level) 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 URetr: Percentage of data blocks retransmitted on uplink, numeric/graphic
LZT 138 0240 R2B
77
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 Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot
Key
78
Chapter 6. The Map View
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 phones 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.
LZT 138 0240 R2B
79
The image now appears in the Map view:
6.2.
6.2.1.
Pinpointing Your Test Route

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 colorcoded according to RxLev (in GSM) or UTRA Carrier RSSI (in WCDMA). The
80
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.
LZT 138 0240 R2B
81
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.
82
The logfile closes, and the pinpointing icon A zip archive is now created holding: the logfile (*.log) the image loaded into the Map view (*.jpg)
disappears.
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 Users 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.
LZT 138 0240 R2B
83
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
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.
Regarding the phone mode/scan mode distinction, see section 2.1.
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.
84
Chapter 7. TEMS Pocket Functions in the Activity Menu
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
LZT 138 0240 R2B
85
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.
86
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
LZT 138 0240 R2B
87
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. During logfile replay this command is not available.
1. The same is also true for passive measurement triggered on phone startup; 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.
88
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. During logfile replay this command is not available.
7.10.
Pocket Menu
This is a shortcut to the Pocket menu; see chapter 8.
LZT 138 0240 R2B
89
8.
The Pocket Menu
8.1.

General
The Pocket menu can be accessed from the Activity menu from the phones main menu by choosing Settings. The Pocket menu appears at the top of the General submenu.
The Pocket menu holds the following submenus: Chapter Ref. 9
Name Cell control
Function Control the phones behavior in the network: Lock on RAT/band/ frequency/cell, etc. Show and control event log, event counters, and event settings Control visibility of data views Configure GPS settings Set up FTP sessions and FTP logfile transfer Configure automated logfile transfer Define command sequences Configure passive mode measurement Import and export user-defined TEMS Pocket settings, and more
Events Data views GPS FTP Logfile Command sequence Passive measurement Tools
10 11 12 13 14 15 16 17
90
Chapter 8. The Pocket Menu
Name General settings
Function Configure miscellaneous TEMS Pocket settings
Chapter Ref. 18
LZT 138 0240 R2B
91
9.
Cell Control Menu
In this menu are collected the functions that modify the phones 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.
92
Chapter 9. Cell Control Menu
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 phones 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. Regarding interplay between locking functions, see section 9.6.
LZT 138 0240 R2B
93
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. Regarding interplay between locking functions, see section 9.6.
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.
94
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. Regarding interplay between locking functions, see section 9.6.
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.)
LZT 138 0240 R2B
95
For full details, see the TEMS Investigation 11.0 Users 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 phones HSPA capabilities as shown below.
96
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.
LZT 138 0240 R2B
97
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.
10.1.1.
Event Log
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:
98
Chapter 10. Events Menu
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:
LZT 138 0240 R2B
99
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.
100
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)
LZT 138 0240 R2B
101
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 phones 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.
102
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
For other event categories, the appropriate text string is substituted.
LZT 138 0240 R2B
103
For inter-RAT events, one of the strings 2G and 3G is added to indicate which technology the phone is transferred to: Handover Direction GSM to WCDMA Normal Events Failure Events
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 Call Attempt Call Blocked Call Dropped Call End Call Established T N F F N N Def Off On On Off Off Parameters CC Id, Call Type {MO, MT} CC Id, CC Cause CC Id, CC Cause CC Id, CC Cause CC Id
104
10.5.2.
MM Events
For values of MM Cause, see appendix A.10. Event Name Auth. Failure (Authentication Failure) Auth. Reject (Authentication Reject) LAU Attempt (Location Area Update Attempt) LAU Failure (Location Area Update Failure) LAU Reject (Location Area Update Reject) LAU Success (Location Area Update Success) MM Reg. Eq. (MM Registered Equivalent PLMN) MM Reg. Home (MM Registered Home PLMN) MM Reg. Roaming (MM Registered Roaming PLMN) MM Unregistered T F F N Def On On Off Parameters MM Cause Constant string: No SIM or IMSI not approved LA Update Type {Normal, Periodic, IMSI Attach, Combined, Invalid} MM Cause
On
On
MM Cause
Off
Previous Location Area, LA Update Type (if = Combined)
On
On
On
On
LZT 138 0240 R2B
105
10.5.3.
SM Events
For values of SM Cause, see appendix A.17. Event Name PDPCtx Act. Att. (PDP Context Activation Attempt) PDPCtx Act. Cpl. (PDP Context Activation Complete) PDPCtx Act. Rej. (PDP Context Activation Reject) PDPCtx Deact. Att. (PDP Context Deactivation Attempt) PDPCtx Deact. Cpl. (PDP Context Deactivation Complete) T N Def Off NSAPI Parameters
Off
NSAPI, IP version {4, 6}, PDP address (IPv4 only) NSAPI, SM Cause
On
Off
NSAPI
Off
NSAPI, Type {NW, UE}, SM Cause (if Type = NW)
10.5.4.
GMM Events
For values of GMM Cause, see appendix A.7. Event Name GMM Attach Att. (GMM Attach Attempt) GMM Attach Cpl. (GMM Attach Complete) GMM Attach Fail. (GMM Attach Failure) T N N F Def Off Off On Parameters Attach type: {GPRS, Combined} Attach type: {GPRS, Combined} T3310 expired or GMM Reject Cause
106
Event Name GMM Detach Att. (GMM Detach Attempt) GMM Detach Cpl. (GMM Detach Complete) RAU Attempt (Routing Area Update Attempt) RAU Complete (Routing Area Update Complete) RAU Reject (Routing Area Update Reject)
T N N N
Def Off Off Off
Parameters GMM Cause GMM Cause, Type {NW, UE} RA Update Type {Normal, Periodic, Combined} Old RA, New RA
Off
On
Timer Event {True, False}, T3330/GMM Reject Cause
LZT 138 0240 R2B
107
10.5.5.
IRAT Events
T N Def Off Parameters BCCH ARFCN, BSIC
Event Name G2U Cell Ch. Att. (GSM To UTRAN Cell Change Attempt) G2U Cell Ch. Fail. (GSM To UTRAN Cell Change Failure) G2U Cell Ch. Succ. (GSM To UTRAN Cell Change Success) G2U HO Attempt (GSM To UTRAN Handover Attempt) G2U HO Failure (GSM To UTRAN Handover Failure) G2U HO Success (GSM To UTRAN Handover Success) U2G Cell Ch. Att. (UTRAN To GSM Cell Change Attempt) U2G Cell Ch. Fail. (UTRAN To GSM Cell Change Failure) U2G Cell Ch. Succ. (UTRAN To GSM Cell Change Success) U2G HO Attempt (UTRAN To GSM Handover Attempt)
On
BCCH ARFCN, BSIC
Off
New UARFCN, New SC
Off
BCCH ARFCN, BSIC
On
BCCH ARFCN, BSIC
Off
New UARFCN, New SC
Off
UARFCN, SC
On
UARFCN, SC
Off
New BCCH ARFCN, New BSIC UARFCN, SC
Off
108
Event Name U2G HO Failure (UTRAN To GSM Handover Failure) U2G HO Success (UTRAN To GSM Handover Success)
T F
Def On
Parameters UARFCN, SC
Off
New BCCH ARFCN, New BSIC
10.5.6.
RR Events
For values of RR Cause, see appendix A.13. For values of RR Internal Cause, see appendix A.14. Event Name GPRS Pkt. Acs. Fail. (GPRS Packet Access Failure) GPRS Retrans. PRR (GPRS Retransmit Packet Resource Request) GSM Assign. Fail. (GSM Assignment Failure) GSM Datalink Timeout GSM HO Failure (GSM Handover Failure) GSM RL Timeout (GSM Radio Link Timeout) T F Def On Parameters BCCH ARFCN, BSIC, RR Cause BCCH ARFCN, BSIC
On
On
RR Cause, RR Internal Cause
F F F
On On On
Target BCCH ARFCN, BSIC, TO value BCCH ARFCN, BSIC, RR Internal Cause BCCH ARFCN, BSIC, Radio Link Timeout Counter (Max)
LZT 138 0240 R2B
109
Event Name Imm. Assign. Fail. (Immediate Assignment Failure) Imm. Assign. Rej. (Immediate Assignment Reject) RAT: GSM RAT: No Service
T F
Def On
Parameters BCCH ARFCN, BSIC, RR Internal Cause BCCH ARFCN, BSIC, RR Internal Cause
On
N F
On 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. Event Name Act. Set Upd. Fail. (Active Set Update Failure) Inter-Freq. Cell Reselection (Inter-frequency Cell Reselection) Inter-Freq. HO Failure (Inter-frequency Handover Failure) Inter-Freq. HO Success (Inter-frequency Handover Success) Phy. Ch. Est. Fail. (Physical Channel Establishment Failure) T F Def On Parameters UARFCN, SC, RRC Failure Cause New UARFCN, New SC
Off
On
UARFCN, SC
On
New UARFCN, New SC
On
UARFCN, SC
110
Event Name RAT: WCDMA RB Reconf. Fail. (Radio Bearer Reconfiguration Failure) RB Setup Fail. (Radio Bearer Setup Failure) RRC Conn. Fail. (RRC Connection Failure) RRC Prot. Error (RRC Protocol Error) RRC RL Fail. (RRC Radio Link Failure)
T N F
Def On On
Parameters
UARFCN, SC, RRC Failure Cause UARFCN, SC, RRC Failure Cause UARFCN, SC, RRC Failure Cause UARFCN, SC, RRC Protocol Error Cause UARFCN, SC
On
On
F F
On On
10.5.8.
Session Events
For values of Automatic Upload Failure Cause, see appendix A.2. Event Name Auto. Upload End (Automatic Upload End) Auto. Upload Fail. (Automatic Upload Failure) Auto. Upload Start (Automatic Upload Start) FTP Transfer End FTP Transfer Fail. (FTP Transfer Failure) T N F Def L L Parameters Upload bearer (cellular/WiFi) Automatic Upload Failure Cause, Upload bearer Upload bearer File name, File size, Duration, Bit rate UL, Bit rate DL
N N F
L On On
LZT 138 0240 R2B
111
Event Name FTP Transfer Start GPS Conn. Found (GPS Connection Found) GPS Conn. Lost (GPS Connection Lost) GPS Loc. Found (GPS Location Found) GPS Loc. Lost (GPS Location Lost) Video Call End Video Call Fail. (Video Call Failure) Video Call Start Voice Call End Voice Call Fail. (Voice Call Failure) Voice Call Start
T N N F N F N F N N F N
Def On On On On On Off Off Off Off Off Off
Parameters
112
Chapter 11. Data Views Menu
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.
LZT 138 0240 R2B
113
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.212.4 below cover the submenus of the GPS menu. You can export your GPS settings to file; they are included in the Export settings operation (Tools menu: see section 17.4).
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 builtin 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 phones 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 phones 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.
114
Chapter 12. GPS Menu
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.
LZT 138 0240 R2B
115
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 phones 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.
116
Chapter 12. GPS Menu
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.
LZT 138 0240 R2B
117
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 settings operation (Tools menu: see section 17.4).
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.
118
Chapter 13. FTP Menu
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. FTP Get parameters If the phone runs out of memory during an FTP Get 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:
LZT 138 0240 R2B
119
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. (continued on next page)
120
Chapter 13. FTP Menu
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.
LZT 138 0240 R2B
121
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.2 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.
122
Chapter 14. Logfile Menu
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.214.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 F Measurements successful 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 voice_p video_a video_p FTP_a FTP_p HTTP_a HTTP_p stream_a stream_p idle_a startup_p manual Active voice measurement Passive voice measurement Active video call measurement Passive video call measurement Active FTP measurement Passive FTP measurement Active HTTP measurement Passive HTTP measurement Active streaming measurement Passive streaming measurement Active idle measurement Passive startup measurement Manual logfile recording
LZT 138 0240 R2B
123
<Tag> tag (empty) <Date> YYYY-MM-DD: Year, month, day <Time> HH.MM.SS: Hours, minutes, seconds Tag attached by user (see section 7.5) No tag attached by user
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.
124
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
LZT 138 0240 R2B
125
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.
Step 1
Setting an Upload Schedule
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.
126
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:
LZT 138 0240 R2B
127
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.
128
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.
LZT 138 0240 R2B
129
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.
130
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.
LZT 138 0240 R2B
131
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.
132
Chapter 15. Command Sequence Menu
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. (continued on next page)
LZT 138 0240 R2B
133
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.
134
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.
LZT 138 0240 R2B
135
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.
136
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. Guard time: The time in seconds to spend in idle mode upon completion of the video call, i.e. the time to wait before starting the next action in 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. Guard time: The time in seconds to spend in idle mode upon completion of the FTP session, i.e. the time to wait before starting the next action in the sequence. Cell control: See section 15.2.3.
LZT 138 0240 R2B
137
15.2.6.
HTTP Action Settings

Data account: Select the data account that should be used for the HTTP session. Guard time: The time in seconds to spend in idle 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. Cell control: See section 15.2.3.
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.
138
15.2.7.
Streaming Action Settings
Streaming sessions are conducted over RTSP using the phones integrated media player. Data account: Select the data account that should be used for the streaming session. Guard time: The time in seconds to spend in idle 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. Cell control: See section 15.2.3.
15.2.8.
Idle Action Settings

Duration: The length of time (in seconds) the phone should spend in idle mode. Cell control: See section 15.2.3.
LZT 138 0240 R2B
139
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 phones 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.
140
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.
LZT 138 0240 R2B
141
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.
142
Chapter 16. Passive Measurement Menu
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.
LZT 138 0240 R2B
143
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.
16.3.1.
Notes on Message Buffering

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 preguard 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.
144
Chapter 16. Passive Measurement Menu
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.
LZT 138 0240 R2B
145
17.
Tools Menu
In this menu are collected miscellaneous functions and information.
17.1.
About Screen
Lines 12: Name of TEMS Pocket product package and options installed. Line 3: TEMS Pocket version. Lines 45 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)
146
Chapter 17. Tools Menu
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 instructors 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.
LZT 138 0240 R2B
147
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.
148
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.
LZT 138 0240 R2B
149
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.
150
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.
LZT 138 0240 R2B
151
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 settings operation (Tools menu: see section 17.4).
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.
152
Chapter 18. General Settings Menu
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.
LZT 138 0240 R2B
153
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.
154
Chapter 18. General Settings Menu
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.
LZT 138 0240 R2B
155
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.
156
Chapter 19. Scanning
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.
LZT 138 0240 R2B
157
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.119.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.
158
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 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.
GSM dialog
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).
LZT 138 0240 R2B
159
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).
160
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

Using a GPS
19.5.1.
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.
LZT 138 0240 R2B
161
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
162
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.119.6.2 below.
LZT 138 0240 R2B
163
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.
164
19.6.1.2. Custom List Scan
ARFCNs of channels with lowest and highest frequency Channels currently in focus Text pane glosses channels 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 Text pane glosses channels in focus: UARFCN First scrambling code decoded (if any) when this UARFCN was last scanned RSSI (dBm)
LZT 138 0240 R2B
165
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.
166
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.
LZT 138 0240 R2B
167
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.
168
Chapter 20. Uploading TEMS Pocket Logfiles from the Phone File System
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 phones 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.
LZT 138 0240 R2B
169
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.
170
Chapter 21. Battery Charging Considerations
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 Phones Built-in GPS
You need to be aware that using the phones 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 phones charging algorithm. The precise details need not bother us; however, and crucially, the
LZT 138 0240 R2B
171
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 1520 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.
172
Chapter 22. Support Contact Information
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.
LZT 138 0240 R2B
173
Appendix A. Parameter Values
This appendix lists the possible values of some parameters appearing in the views and of some event parameters.
A.1.
26 27 28 29 30 31 32 33 34 35 95 96 97 98 99 111 T3380
Activate PDP Context Failure Cause

Insufficient resources Missing or unknown APN Unknown PDP address or PDP type User authentication failed Activation rejected, unspecified Activation rejected by GGSN Service option not supported Requested service option not subscribed Service option temporarily out of order NSAPI already used Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message type not compatible with the protocol state Information element non-existent or not implemented Protocol error, unspecified Fifth expiry of T3380 timer (MS side)
A.2.
1 2 3 5 6 7
Automatic Upload Failure Cause

Compression failed, probably due to full file system User canceled upload Destination folder is incorrect No FTP account specified for automatic upload No FTP server specified for automatic upload FTP rename failed
174
8 9 11 12 13 14
FTP Put failed FTP Get failed FTP login failed, incorrect user name or password Data account assigned to the upload is invalid Connection failed, FTP server not responding No files to upload
A.3.
1 3 6 8 16 17 18 19 21 22 25 26 27 28 29 30 31 34 38 41 42 43 44 47 49 50 55 57 58
CC Cause
Unassigned (unallocated) number No route to destination Channel unacceptable Operator determined barring Normal call clearing User busy No user responding User alerting, no answer Call rejected Number changed Pre-emption Non selected user clearing Destination out of order Invalid number format (incomplete number) Facility rejected Response to STATUS ENQUIRY Normal, unspecified (not logged) No circuit/channel available Network out of order Temporary failure Switching equipment congestion Access information discarded Requested circuit/channel not available Resources unavailable, unspecified Quality of service unavailable Requested facility not subscribed Incoming calls barred within the CUG Bearer capability not authorized Bearer capability not presently available
LZT 138 0240 R2B
175
63 65 68 69 70 79 81 87 88 91 95 96 97 98 99 100 101 102 111 127
Service or option not available, unspecified Bearer service not implemented ACM equal to or greater than ACMmax Requested facility not implemented Only restricted digital information bearer capability is available Service or option not implemented, unspecified Invalid transaction identifier value User not member of CUG Incompatible destination Invalid transit network selection Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message type not compatible with protocol state Information element non-existent or not implemented Conditional IE error Message not compatible with protocol state Recovery on timer expiry Protocol error, unspecified Interworking, unspecified
A.4.
NC Comb NC2 NC3 NC4
CCCH Configuration
1 basic physical channel used for CCCH, not combined with SDCCHs 1 basic physical channel used for CCCH, combined with SDCCHs 2 basic physical channels used for CCCH, not combined with SDCCHs 3 basic physical channels used for CCCH, not combined with SDCCHs 4 basic physical channels used for CCCH, not combined with SDCCHs
176
A.5.
BCCH PBCCH PDTCH SDCCH TCH/F TCH/H
Channel Type
Broadcast Control Channel, Signalling Packet Broadcast Control Channel Packet Dedicated Traffic Channel Stand-alone Dedicated Control Channel Traffic Channel, Full Rate Traffic Channel, Half Rate
A.6.
25 26 36 37 38 39 T3390
Deactivate PDP Context Cause

LLC or SNDCP failure Insufficient resources Regular PDP context deactivation QoS not accepted Network failure Reactivation requested Fifth expiry of T3390 timer (MS side)
A.7.
2 3 6 7 8 9 10 11 12 13 14 15 16 17 20 21
GMM Cause
IMSI unknown in HLR Illegal MS Illegal ME GPRS services not allowed GPRS services and non-GPRS services not allowed MS identity cannot be derived by the network Implicitly detached PLMN not allowed Location area not allowed Roaming not allowed in this location area GPRS services not allowed in this PLMN No suitable cells in location area MSC temporarily not reachable Network failure MAC failure Synch failure
LZT 138 0240 R2B
177
22 23 40 4863 95 96 97 98 99 100 101 111
Congestion GSM authentication unacceptable No PDP context activated Retry upon entry into a new cell Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message type not compatible with the protocol state Information element non-existent or not implemented Conditional IE error Message not compatible with the protocol state Protocol error, unspecified
A.8.
GPRS Network Mode of Operation
Handling of paging in the GPRS network. I II III Mode I: All paging on GPRS channels; Gs signalling interface present Mode II: All paging on PCH; no Gs Mode III: All circuit-switched paging on PCH, all packetswitched paging on PPCH; no Gs
A.9.
0 1 2 3 4 5 6 7 8 32
GPS Fix Quality

Fix not available or invalid GPS SPS Mode, fix valid Differential GPS, SPS Mode, fix valid GPS PPS Mode, fix valid Real Time Kinematic. System used in RTK mode with fixed integers Float RTK. Satellite system used in RTK Mode, floating integers Estimated (Dead Reckoning) mode Manual Input Mode Simulator Mode Internal GPS
178
A.10.
2 3 4 5 6 11 12 13 17 22 32 33 35 38 4863 95 96 97 98 99 100 101 111
MM Cause
IMSI unknown in HLR Illegal MS IMSI unknown in VLR IMEI not accepted Illegal ME PLMN not allowed Location area not allowed Roaming not allowed in this location area Network failure Congestion Service option not supported Requested service option not subscribed Service option temporarily out of order Call cannot be identified Retry upon entry into a new cell Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message type not compatible with the protocol state Information element non-existent or not implemented Conditional IE error Message not compatible with the protocol state Protocol error, unspecified
A.11.
A.11.1.
0 1 2 3 4
PDP Context Request Parameters

Delay Class
Subscribed Delay class 1 Delay class 2 Delay class 3 Delay class 4 (best effort)
LZT 138 0240 R2B
179
A.11.2.
0 1 2 3 4 5
Reliability Class
Subscribed Acknowledged GTP, LLC, and RLC; Protected data Unacknowledged GTP; Acknowledged LLC and RLC, Protected data Unacknowledged GTP and LLC; Acknowledged RLC, Protected data Unacknowledged GTP, LLC, and RLC, Protected data Unacknowledged GTP, LLC, and RLC, Unprotected data
A.11.3.
0 1 2 3 4 5 6 7 8 9
Peak Throughput
Subscribed Up to 1000 octets/s Up to 2000 octets/s Up to 4000 octets/s Up to 8000 octets/s Up to 16,000 octets/s Up to 32,000 octets/s Up to 64,000 octets/s Up to 128,000 octets/s Up to 256,000 octets/s
A.11.4.
0 1 2 3
Precedence Class
Subscribed High priority Normal priority Low priority
A.11.5.
0 1 2 3 4
Mean Throughput
Subscribed 100 octets/h 200 octets/h 500 octets/h 1000 octets/h
180
5 6 7 8 9 10 11 12 13 14 15 16 17 18 31
2000 octets/h 5000 octets/h 10,000 octets/h 20,000 octets/h 50,000 octets/h 100,000 octets/h 200,000 octets/h 500,000 octets/h 1,000,000 octets/h 2,000,000 octets/h 5,000,000 octets/h 10,000,000 octets/h 20,000,000 octets/h 50,000,000 octets/h Best effort
A.12.
3 6 7 9 10 11 12 13 96 99 100 111 T3330
Routing Area Update Failure Cause

Illegal MS Illegal ME GPRS services not allowed MS identity cannot be derived by the network Implicitly detached PLMN not allowed Location area not allowed Roaming not allowed in this location area Invalid mandatory information IE non-existent or not implemented Conditional IE error Protocol error, unspecified Fifth expiry of T3330 timer (MS side)
A.13.
0 1 2 3
RR Cause
Normal event Abnormal release, unspecified Abnormal release, channel unacceptable Abnormal release, timer expired
LZT 138 0240 R2B
181
4 5 8 9 10 65 95 96 97 98 100 101 111
Abnormal release, no activity on the radio path Preemptive release Handover impossible, timing advance out of range Channel mode unacceptable Frequency not implemented Call already cleared Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message type not compatible with protocol state Conditional IE error No cell allocation available Protocol error, unspecified
A.14.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
RR Internal Cause
Normal release Abnormal release unspecified MAX no of random access Access barred Reject from base station No cell available No ciphering key Reestablish not allowed Data link error Establish error Ciphering algorithm not implemented PS connection aborted due to CS connection PDCH release SCH timing error or timing advance out of range L2 error Message received in invalid state IRAT U2G handover failure
A.15.
0 1
RRC Failure Cause

Configuration unsupported Physical channel failure
182
2 3 4 5 6 7 8 9 10
Incompatible simultaneous reconfiguration Protocol error Compressed mode runtime error Cell update occurred Invalid configuration Configuration incomplete Unsupported measurement MBMS session already received correctly Lower priority MBMS service
A.16.
0 1 2 3 4 5
RRC Protocol Error Cause

ASN.1 violation or encoding error Message type non-existent or not implemented Message not compatible with receiver state Information element value not comprehended Information element missing Message extension not comprehended
A.17.
8 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
SM Cause
Operator Determined Barring MBMS bearer capabilities insufficient for the service LLC or SNDCP failure (A/Gb mode only) Insufficient resources Missing or unknown APN Unknown PDP address or PDP type User authentication failed Activation rejected by GGSN Activation rejected, unspecified Service option not supported Requested service option not subscribed Service option temporarily out of order NSAPI already used (not sent) Regular deactivation QoS not accepted Network failure Reactivation required
LZT 138 0240 R2B
183
40 41 42 43 44 45 46 47 81 95 96 97 98 99 100 101 111 112
Feature not supported Semantic error in the TFT operation Syntactical error in the TFT operation Unknown PDP context Semantic errors in packet filter(s) Syntactical errors in packet filter(s) PDP context without TFT already activated Multicast group membership time-out Invalid transaction identifier value Semantically incorrect message Invalid mandatory information Message type non-existent or not implemented Message type not compatible with the protocol state Information element non-existent or not implemented Conditional IE error Message not compatible with the protocol state Protocol error, unspecified APN restriction value incompatible with active PDP context
184
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) x > 15.0 10.0 x 15.0 x 10.0 green yellow red Color
B.2.
Ec/N0
Bar length is proportional to (Value (25 dB)). Value = x (dB) x > 10 15 x 10 x 15 green yellow red Color
LZT 138 0240 R2B
185
B.3.
FER, RLC/LLC BLER/Retransmissions
Bar length is constant. Value = x (%) x=0 1 x 4 x 5 green yellow red Color
B.4.
RLC DL/UL Throughput
This is used in the Map view only (no bars). Value = x (kbit/s) x 1000 100 x 1000 10 x 100 x 10 green yellow orange red Color
B.5.
RxLev, RSCP, RSSI
Bar length is proportional to (Value (110 dBm)). Value = x (dBm) x 70 80 x 70 90 x 80 100 x 90 x 100 green light green yellow orange red Color
186
B.6.
RxQual
Bar length is constant. Value = x x=0 1 x 4 x5 green yellow red Color
B.7.
Tx Power
Bar height is proportional to (Value (30 dBm)). Value = x (dBm) x5 5 x 15 x 15 green yellow red Color
LZT 138 0240 R2B
187
Appendix C. Icons Used in TEMS Pocket
Regarding icons for cellular network events, see section 10.4. Icon 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) Meaning
188
Appendix C. Icons Used in TEMS Pocket
Icon Logfile upload starteda
Meaning
Logfile upload completeda Logfile upload faileda

a. By default not shown: see section 10.5.8.
LZT 138 0240 R2B
189
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.
D.1.1.
Active
Activity Menu
Operational Mode
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
190
D.2.
D.2.1.

Pocket Menu
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
LZT 138 0240 R2B
191
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 Guard time: 20 s Redial: Off Cell control: Nothing turned on
FTP settings Guard time: 20 s Cell control: Nothing turned on
HTTP settings Guard time: 20 s Cell control: Nothing turned on
192
Streaming settings Guard time: 20 s Audio: On Video: Show Max time: 600 s Cell control: Nothing turned on
Idle settings Duration: 10 s Cell control: Nothing turned on
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
LZT 138 0240 R2B
193
Cell presentation: CGI Power display: dBm Measure mode display: Sub Auto answer: Off WCDMA Cell Id q-val: RSCP
194
Appendix E. Cell File Format
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_LENGTH>2</MNC_LENGTH> <MNC>5</MNC> <LAC>27</LAC> <CI>7924</CI> </CGI> </WCDMA_CELL>
LZT 138 0240 R2B
195
</CELL_LIST> </WCDMA> <GSM> <CELL_LIST> <GSM_CELL> <CELLNAME SYSTEM_TYPE="GSM">My GSM Cell 1</CELLNAME> <CGI> <MCC>240</MCC> <MNC_LENGTH>2</MNC_LENGTH> <MNC>1</MNC> <LAC>5028</LAC> <CI>4362</CI> </CGI> <BSIC> <NCC>2</NCC> <BCC>2</BCC> </BSIC> <CHANNEL_INFO> <BCCH> <ARFCN>19</ARFCN> </BCCH> </CHANNEL_INFO> </GSM_CELL> <GSM_CELL> <CELLNAME SYSTEM_TYPE="GSM">My GSM Cell 2</CELLNAME> <CGI> <MCC>240</MCC> <MNC_LENGTH>2</MNC_LENGTH> <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>
196
Index
Index
Numerics
3G symbol (at top of display) 10
A
About screen 146 Activate PDP Context Failure Cause 174 active set (WCDMA) 22, 34, 35, 36, 67, 69 Activity key 11, 84 Activity menu 11, 84, 90 altitude 31 AMR codecs (GSM) active set 60 used on downlink 60 used on uplink 60 utilization of 60 AMR codecs (WCDMA) active set 40 used on downlink 40 used on uplink 40 utilization of 40 APN 26 ARFCN 23 ARQ mode (EGPRS) 55 Auto Answer dialog 156 Automatic Repeat Request Mode (EGPRS) 55 Automatic Upload Failure Cause 174
B
Backlight dialog (display backlight) 154 barred cells, accessing of 97 Base Station Identity Code 46, 49, 50, 51, 54, 59, 64, 67, 69, 75 battery charging considerations 132, 171 BCCH ARFCN 23, 46, 48, 49, 50, 51, 67, 69, 75 BEP (EGPRS) 55 BEP variance (EGPRS) 55
LZT 138 0240 R2B
197
bit error probability, mean (EGPRS) 55 bit error probability, variance (EGPRS) 55 BLER (GSM) 56, 65, 71, 77 BLER (WCDMA) 41, 62, 63, 71 BLER Target, downlink (on transport channel) 39 block retransmission rate (GSM) 56, 65, 71, 77 block retransmission rate (WCDMA) 41, 63 BS-AG-BLKS-RES 51 BSIC 23, 46, 49, 50, 51, 54, 59, 64, 67, 69, 75 BS-PA-MFRMS 47, 48, 51 bytes transferred (GSM) 56 bytes transferred (WCDMA) 41
C
C value (EGPRS) 55 C/I 52, 55, 58, 59 graphic representation 185 C1 46, 68, 69, 75 C2 46, 68, 69, 75 C31 46, 68, 70, 75 C32 46, 68, 70, 75 capture function (taking screenshots) 7, 16, 167 Carrier-to-interference ratio (C/I) 52, 55, 58, 59 CC Cause 175 CC events 104 CCCH Configuration 51, 176 cell control functions 13, 92 icon for 10, 85 Cell Control menu 92 default settings in 191 cell file format of 195 importing 151 Cell Id Format dialog 154 Cell Identity 24, 35, 36, 48, 49 improved presentation 1 presentation in dedicated/connected mode 7 cell name presentation 2, 151 Cell Presentation dialog 154 Cell Reselection Criterion (C2) 46, 68, 69, 75 Cell Reselection Hysteresis 47, 48 cell selection and reselection parameters 37 channel coding scheme (GPRS)
198
Index
on downlink 55 on uplink 55 Channel Mode 53 Channel Quality Indicator (HSDPA) 43 Channel Type 53, 177 channelization codes on HS-SCCH, number of 43 charging of phone battery 171 CI 24, 35, 36, 48, 49 presentation format 154 Ciphering Mode 53 color coding of parameter values 15 Command Sequence menu 132 default settings in 192 command sequences 13, 132 adding an action to 135 battery charging considerations 171 defining 133 deleting 141 deleting an action from 141 editing 141 FTP action 137 global settings 133 HTTP action 138 Idle action 139 introduction to 132 post-guard period 140 pre-guard period 140 rearranging actions in 140 running 89, 141 saving default settings for an action type 140 starting and stopping 89 streaming action 139 video call action 137 viewing 141 voice call action 136 Compressed Mode 39, 40, 41 compressing logfiles before upload 122, 130 Connect GPS command 88 CQI 43
D
data rate (GSM channel mode) 53 data view actions 16
LZT 138 0240 R2B
199
Data View Style dialog 153 data views 9, 15 browsing 10 categories of 10 display style 153 general properties of 15 survey of 18 taking snapshots of 7, 16, 167 updating in replay mode 85 visibility of 113 with graphs 7, 10, 66 data views in text format 9, 22 Data Views menu 113 default settings in 191 DCH, time using 28 Deactivate PDP Context Cause 177 default settings in TEMS Pocket menus 190 Delay Class (PDP Context Request) 26, 179 Disconnect GPS command 88 Downlink Signalling Counter 51 DRX Timer Max 57 DSC (Current) 51 DSC (Max) 51 DTX rate in GSM, on downlink 52, 60 in GSM, on uplink 52, 60 in HSUPA 44
E
Ec/No 22, 67, 69 graphic representation 185 E-DPCCH/E-DPDCH retransmission rate 44 EGPRS modulation coding scheme 64 EGPRS window size 57 end-of-charge state (of phone battery) 171 EoC 171 Equivalent PLMN, time registered in 28 E-TFCI 44 event counters 85, 102 resetting 103 viewing 102 event log 85, 88, 98 clearing 99
200
Index
details of individual events 99 viewing 98 event settings 100 modifying 101 viewing 100 events 12, 98, 99 enabling/disabling event logging and sound 99 event log 99 icons for 10, 103 list of 104 presentation in graphs 66 Events menu 98 default settings in 191 exiting TEMS Pocket 14 exporting TEMS Pocket settings 8, 149 managing export files 150
F
FER 52, 60 graphic representation 186 filemarks, inserting in logfiles 84 Frame Erasure Rate 52, 60 FTP duration of FTP session 29 name of transferred file 29 selecting server to upload logfiles to 131 setting up Put and Get operations 118 specifying FTP servers 120 starting and stopping FTP sessions 88 throughput 29 total bytes transferred 30 FTP Data data view (no. 1.5) 29 FTP menu 118 default settings in 191 FTP resume 131 FTP server address 29 FTP Server dialog 120, 131 FTP session, direction of (UL/DL) 29 FTP Settings dialog (command sequence) 137 FTP Transfer dialog 118 Full/Sub values (for RxLev and RxQual) 155
LZT 138 0240 R2B
201
G
General Settings menu 152 default settings in 193 GMM Attached 27 GMM Cause 177 GMM events 106 GMM State 57 GPRS Cell Ranking Criterion (C32) 46, 68, 70, 75 GPRS Data data view (no. 4.2) 54 actions in 56 GPRS Info data view (no. 4.3) 57 GPRS Network Mode of Operation 57, 178 GPRS Signal Strength Threshold Criterion (C31) 46, 68, 70, 75 GPRS timeslots 54, 64, 77 GPS 13 battery charging considerations 171 Bluetooth pairing 115 connect mode 115 connecting and disconnecting 88 date 31 fix quality 31, 178 number of satellites seen 31 requirements on external GPS device 115 selecting type of GPS device 116 synchronizing phone clock with 117 time 31 using external GPS with TEMS Pocket 115 using phones built-in GPS with TEMS Pocket 114 using while in scan mode 161 GPS Connect dialog 115 GPS data view (no. 1.6) 31 GPS Device dialog 116 GPS menu 114 default settings in 191 GPS Time Synch dialog 117 graphic presentation 15 graphic representation of parameter values 185 graphs 10 graphs in data views 7 GSM AMR data view (no. 4.5) 59 GSM BA List data view (no 3.4) actions in 50
202
Index
GSM BA List data view (no. 3.4) 50 GSM C/I Info data view (no. 4.4) 58 GSM Cell Id data view (no. 3.2) 48 actions in 49 GSM Cell Name data view (no. 3.3) 49 actions in 50 GSM Cells data view (no. 3.1) 46 actions in 47 GSM Cells data view (no. 5.7, with graph) 75 GSM Channel Type 23 GSM Data data view (no. 5.8) 77 GSM Serving Cell data view (no. 4.1) 51
H
H symbol (at top of display) 10 happy rate (HSUPA) 44 HARQ processes on HS-DSCH, number of 43 help, on-screen 15, 167 Home PLMN, time registered in 28 hopping channels 15, 23, 46, 48, 50, 52, 54, 59, 64, 67, 69, 75, 77 Hopping Sequence Number 53 HS Capability dialog 96 HSDPA actual transport block size 43 block error rate, first retransmission 44 channelization codes on HS-SCCH, number of 43 CQI 43 HARQ processes on HS-DSCH, number of 43 percentage of blocks transmitted successfully on first attempt 44 requested transport block size 43 residual block error rate 44 total number of blocks to be received 44 turning phone capability on and off 96 HSN 53 HSPA Data data view (no. 2.8) 43 HSUPA DTX rate 44 E-DPCCH/E-DPDCH retransmission rate 44 E-TFCI 44 happy rate 44 Serving Grant Index 44 transport block size on E-DCH 44 HTTP Settings dialog (command sequence) 138
LZT 138 0240 R2B
203
I
icons for cell control functions 92 for events 103 for logfile recording 85 listing of all icons used in TEMS Pocket 188 Idle mode time spent in (GSM) 28 time spent in (WCDMA) 28 Idle Settings dialog (command sequence) 139 Ignore Cell Barred dialog 97 IMEI 146 importing TEMS Pocket settings 8, 147 from previous TEMS Pocket versions 149 IMSI 146 indoor positioning by pinpointing 79 Insert Filemark command 84 interplay between locking functions 95 Inter-RAT events 108 invalid parameters, representation of 15
L
LAC 24, 48 last registered 27 presentation format 154 language support 14 latitude 31 LLC data transfer performance (GSM) 56, 65 LLC window size 57 Location Area Code 24, 48 Location Area properties 35, 47, 75 Lock ARFCN GSM dialog 94 Lock Band GSM dialog 94 Lock Band WCDMA dialog 94 Lock Cell WCDMA dialog 93 Lock GSM band 95 Lock GSM cell 25, 49, 50, 94, 95 Lock to RAT 95 GSM only setting in phone menu 93 Lock to RAT dialog 92 Lock UARFCN 25, 34, 35, 36, 95 Lock WCDMA cell 25, 34, 35, 36, 95 locking functions
204
Index
comparison with TEMS Investigation 95 interplay between 95 Logfile menu 122 default settings in 191 logfile recording 12, 122 automatic triggering of 122, 142 icon for 10 in scan mode 162 starting/stopping manual recording 85 where to save files 124 logfile replay 12, 85, 122 controlling 86 status icons for 10 logfile uploading over the cellular network 124 from phone file system 169 setting a schedule for 126 logfile uploading over WiFi 127 logfile uploading, resumption after loss of FTP connection 7, 131 logfiles naming of 2, 123 saving of 2, 134, 143 Logical Channel 46, 48, 50, 51, 52, 54, 59, 64, 67, 69, 75 longitude 31
M
MAIO 53 Map view 6, 11, 79 assigning geographical position to map image 83 color-coding of route markers 80 loading map image into 79 zoom level 80 MCC 24 last registered 27 Mean Throughput (PDP Context Request) 26, 180 Measure Mode Display dialog (GSM) 155 memory low memory condition 12, 85 memory sticks 13, 119, 122, 124, 125, 150 menus 11 default settings in 190 messages (displaying of) 153 Messages dialog 153 MM Cause 179
LZT 138 0240 R2B
205
MM events 105 MM/GMM data view (no. 1.3) 27 MNC 24 last registered 27 Mobile Allocation Index Offset 53 Mobile Country Code 24 Mobile Network Code 24 modulation coding scheme on downlink (EGPRS) 64 modulation coding scheme on uplink (EGPRS) 64 modulation method on downlink (GPRS/EGPRS) 55 modulation method on uplink (GPRS/EGPRS) 55 MRU 2, 156 MS-TXPWR-MAX-CCH 47, 48
N
naming of logfiles 123 Neighbor Cell BCCH 47, 48, 49, 75 neighbors (GSM) 23, 47, 48, 49, 50, 75 Network Mode of Operation 57 NMO 57 No Service mode, time spent in 28 NSAPI 26
O
Operational Mode 84 default 190 overview of TEMS Pocket 9
P
Packet Dedicated Traffic Channel 52, 54, 59, 64, 77 Packet Final Block Timer 57 Packet TMSI 27 Packet Uplink Assignment Timer 57 parameter values 174 Passive Measurement menu 142 default settings in 193 passive measurements 142 action settings 143 message buffering for 144 prioritization of 144 Pathloss (WCDMA) 22, 34, 67, 69, 72, 74 Pathloss Criterion (C1) 46, 68, 69, 75 PDCH, time using 28 PDP address (IPv4) 26
206
Index
PDP Context data view (no. 1.2) 26 PDP Context Request parameters 179 PDTCH 52, 54, 58, 59, 64, 77 Peak Throughput (PDP Context Request) 26, 180 phone charger, choice of 171 phone mode 9, 84 pinpointing 6, 13, 79, 80 starting 81 stopping 82 Pocket menu 12, 89, 90 positioning by GPS 13 by pinpointing 13 post-guard period 140 for passive measurements 145 Power Control Algorithm 39, 40, 41 Power Control Step Size 39, 40, 41 Power Display dialog (GSM) 155 Precedence Class (PDP Context Request) 26, 180 pre-guard period 140 for passive measurements 144 Progress data view (no. 1.8) 32 PTMSI 27
Q
QAM, usage of in HSDPA 43 Quick guide 147
R
RAC 23 last registered 27 RACo 46, 68, 69, 75 Radio Link Timeout 52 Radio Network Controller ID 24 RAT, current 23 Receive Bit Error Rate 52, 60 Reliability Class (PDP Context Request) 26, 180 replaying logfiles 85 controlling the replay 86 status icons for 87 Reset All command (General settings menu) 156 Reset Control Settings command 97 resetting all General settings 156
LZT 138 0240 R2B
207
resetting cell control settings 97 resumption of logfile upload 131 RLC data transfer performance (WCDMA) 41, 62 RLC/LLC BLER/retransmissions, graphic representation 186 RLC/MAC data transfer performance (GSM) 56, 65, 71, 77 presented in graph 71, 78 RLT 52 RNC ID 24 Roaming PLMN, time registered in 28 Routing Area Code 23 Routing Area Color 46, 68, 69, 75 Routing Area properties 35, 47, 75 Routing Area Update Failure Cause 181 RR Cause 181 RR events 109 RR Internal Cause 182 RRC events 110 RRC Failure Cause 182 RRC parameters 38 RRC Protocol Error Cause 183 RRC State 39, 40, 41 RSCP 22, 34, 35, 67, 69, 72, 74 graphic representation 186 presented in graph 68, 70, 72, 74 RSSI 62 graphic representation 186 RxLev 23, 46, 48, 50, 51, 54, 59, 64, 67, 68, 69, 75 Full/Sub values 155 graphic representation 186 presentation format 155 presented in graph 70, 76 RxQual 52, 60 Full/Sub values 155 graphic representation 187
S
Save Logfile To dialog 124 scan mode 9, 13, 84, 157 entering 157 Scanner data view 162 freezing 167 scanning 9, 13, 157 Decode BSIC setting (GSM) 160
208
Index
Ec/N0 threshold setting (WCDMA) 160 freezing the presentation 167 GSM custom list scan 158 GSM whole-band scan 158 Method setting 158 presentation of 162 GSM, custom list 165 GSM, whole band 164 WCDMA, CPICH scan (custom list) 166 WCDMA, network scan (whole band) 165 recording logfiles with scan data 162 RSSI threshold setting (WCDMA) 160 setting up a custom list of channels 159 setting up a scan 158 starting and stopping a scan 161 System setting (selection of cellular technology) 158 using a GPS 161 WCDMA CPICH scan 159 WCDMA network scan 159 scheduling logfile uploads 126 Scrambling Code 22, 23, 34, 35, 36, 67, 69, 72, 74 SDCCH 52, 54, 59, 64, 77 serving cell (GSM) 23, 46, 48, 49, 50, 51, 75 serving cell (WCDMA/GSM, always shown at bottom of display) 23 Serving Cell Barred 47, 48 Serving Cell BCCH 54, 59, 64 Serving Grant Index 44 Session events 111 SIB 3 37 SIB 5 37 SIR 39, 40, 41, 62, 73 presented in graph 73 SIR Target 39, 40, 41, 62, 73 presented in graph 73 SM Cause 183 SM events 106 snapshots of data views, taking 7, 16, 167 Sony Ericsson C905/C905a 6 Sony Ericsson W995 3 Sony Ericsson W995 EDGE 3 Sony Ericsson W995a 3 speech codec (WCDMA) 40
LZT 138 0240 R2B
209
speed 31 Stand-alone Dedicated Control Channel 52, 54, 59, 64, 77 Start Command Sequence command 89 Start FTP command 88 Start Logfile Recording command 85 Start Logfile Replay command 85 Stop Command Sequence command 89 Stop FTP command 88 Stop Logfile Recording command 85 Stop Logfile Replay command 85 Stop Logfile Upload command 88 storage medium, choice of 13 Streaming Settings dialog (command sequence) 139 Subchannel Number 53 support contact information 173 System Information Block 3 37 System Information Block 5 37
T
T3168 timer start value 57 T3192 timer start value 57 T3212 timer current value 27 T3212 timer max value 27 T3314 timer current value 57 T3314 timer start value 57 Tag Logfile command 87 TCH 52, 54, 58, 59, 64, 77 time using 28 Temporary Logical Link Identifier 27 Temporary Mobile Subscriber Identity 27 TEMS Automatic 114, 117, 122 TEMS Discovery 122 TEMS Investigation 12, 85, 86, 95, 114, 122 TEMS Pocket product package 146 TEMS Pocket version 146 TEMS Presentation 12, 85, 114, 122 throughput (GSM) 56, 65, 71, 77 presented in graph 71, 78 throughput (WCDMA) 41, 45, 62, 63, 71 presented in graph 71 Time Log data view (no. 1.4) 28 actions in 28 Timeslot Number 52, 59
210
Index
timeslots used by GPRS 54, 64, 77 Timing Advance 52, 60 TLLI 27 TMSI 27 Tools menu 146 default settings in 193 Traffic Channel 52, 54, 59, 64, 77 time using 28 Traffic Channel Type 54, 59, 77 transport block size on E-DCH (HSUPA) 44 transport channels configuration of 39 data transfer performance (WCDMA) 41, 63, 71 presented in graph 71 direction 39 downlink BLER target 39 identity 39 maximum bit rate on 39 type 39 turning TEMS Pocket off 14 Tx Power 39, 40, 41, 52, 59, 62, 73 graphic representation 187
U
UARFCN 22, 23, 34, 35, 36, 62, 67, 69, 72, 74 UE Transmit Power 39, 40, 41, 52, 59, 62, 73 Upload Logfile dialog 124 UTRA Carrier RSSI 23 presented in graph 72
V
Video Settings dialog (command sequence) 137 Voice Codec dialog 96 voice codecs 53 setting preferred 96 Voice Settings dialog (command sequence) 136
W
W/G Cells data view (no. 1.1, in text format) 22 actions in 25 W/G Cells data view (no. 5.2, with graph) 69 W/G Data data view (no. 5.3) 71 W/G Serving RSSI data view (no. 5.1) 67 WAP browser data views 61
LZT 138 0240 R2B
211
GPRS view 64 visibility of 152 WCDMA view 62 WAP Data View dialog 152 WCDMA AMR data view (no. 2.6) 40 WCDMA C. Name data view (no. 2.3) 36 actions in 36 WCDMA Cell Id data view (no. 2.2) 35 actions in 35 WCDMA Cell Id Q-val dialog 156 WCDMA Cell Type 22, 34, 35, 67, 69, 72, 74 WCDMA Cells data view (no. 2.1, in text format) 34 actions in 34 WCDMA Cells data view (no. 5.6, with graph) 74 WCDMA Channel data view (no. 2.5) 39 WCDMA Data data view (no. 2.7) 41 actions in 42 WCDMA Serv. Cell data view (no. 2.4) 37 WCDMA Serving data view (no. 5.4) 72 WCDMA SIR data view (no. 5.5) 73 what was new in TEMS Pocket 7.0 6 what was new in TEMS Pocket 7.2 3 what was new in TEMS Pocket 7.3 1 whats new in this version of TEMS Pocket 1 WiFi, logfile uploading over 127
212
www.ascom.com/tems
The TEMS Portfolio offers a complete set of trusted solutions for drive testing, benchmarking, monitoring,andanalyzingnetworkperformance. These state-of-the-art offerings facilitate the deployment,optimization,andmaintenanceofmobile networks. Wearetheindustryleader,andourproductsare suppliedtotheworldstopmobileoperators,equipmentvendors,andprofessionalserviceproviders.
Ascomreservestherighttochangespecificationswithoutnotice.Ascomacknowledgesallregisteredtrademarksappearingherein.
AscomNetworkTestingInc. 1943IsaacNewtonSquare Reston,Virginia20190|USA www.ascom.com/tems
06.2010 Ascom 2010. All rights reserved. TEMS is a trademark of Ascom . All other trademarks are the property of their respective holders.
AScoM NETwork TESTiNg lEAdS ThE world iN providiNg bEST-iN-clASS SoluTioNS To MEASurE, ANAlyzE, ANd opTiMizE MobilE NETworkS.

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

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

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

Hochgeladen von

Copyright:

Verfügbare Formate

TEMS POCKET 7.3.

2 for Sony Ericsson W995 and W995a

2. Overview of TEMS Pocket

LZT 138 0240 R2B

3. Data Views: General

4. Data Views in Text Format

5. Data Views with Graphs

6. The Map View

LZT 138 0240 R2B

7. TEMS Pocket Functions in the Activity Menu

8. The Pocket Menu

9. Cell Control Menu

10. Events Menu

11. Data Views Menu 12. GPS Menu

13. FTP Menu

13.1. FTP Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 13.2. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

LZT 138 0240 R2B

14. Logfile Menu

15. Command Sequence Menu

16. Passive Measurement Menu

17. Tools Menu

18. General Settings Menu

LZT 138 0240 R2B

22. Support Contact Information Appendix A. Parameter Values

Appendix B. Graphic Representation of Parameter Values

LZT 138 0240 R2B

191 191 191 191 192 193 193 193

Appendix E. Cell File Format Index

Whats New in TEMS Pocket 7.3.2

What Was New in TEMS Pocket 7.3

LZT 138 0240 R2B

Presentation of Cell Names

Event-based Logfile Sifting

Improved Logfile Naming

Coexistence with MRU (Mobile Receiving Unit)

What Was New in TEMS Pocket 7.2

8.1 megapixel camera Integrated GPS

New GSM Phone: Sony Ericsson W995 EDGE

Scanning (GSM and WCDMA)

LZT 138 0240 R2B

Command Sequence Enhancements

Data Upload over WiFi

HSPA Data View

LZT 138 0240 R2B

WCDMA AMR Data View

What Was New in TEMS Pocket 7.0

(TEMS Pocket 7.1 is a Nokia-based release.)

Phones: Sony Ericsson C905, C905a

Map View and Pinpointing

Data Views with Graphs

Smarter Logfile Upload

Snapshots of Data Views

LZT 138 0240 R2B

Importing and Exporting TEMS Pocket Settings

Chapter 2. Overview of TEMS Pocket

Overview of TEMS Pocket

Phone Mode vs. Scan Mode

LZT 138 0240 R2B

Data Views with Graphs

Chapter 2. Overview of TEMS Pocket

LZT 138 0240 R2B

Chapter 2. Overview of TEMS Pocket