Pocket 7.3 For W995 - User - S Manual

TEMS Pocket 7.
2 for Sony Ericsson W995 and W995a

Users 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 2009. All rights reserved. Publication number: LZT 138 0240 R1A
Contents
Contents
1. Introduction
1.1. Whats New in TEMS Pocket 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1.1. New UMTS Phones: Sony Ericsson W995/W995a . . . . . . . . 1 1.1.2. New GSM Phone: Sony Ericsson W995 EDGE . . . . . . . . . . . 2 1.1.3. New GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.4. HSPA Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2. What Was New in TEMS Pocket 7.0. . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2.1. Phones: Sony Ericsson C905, C905a . . . . . . . . . . . . . . . . . . 2 1.2.2. Map View and Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2.3. Data Views with Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2.4. Smarter Logfile Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2.5. Cell Id Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2.6. Snapshots of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.7. Importing and Exporting TEMS Pocket Settings . . . . . . . . . . 4
2. Overview of TEMS Pocket
2.1. Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.1. Data Views with Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.2. Map View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.4. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.5. Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.5.1. Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.5.2. GPS Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.5.3. Positioning by Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.6. Cell Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.7. Command Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.8. Storage Medium: Phone Memory vs. Memory Stick . . . . . . . . . . . . . 9 2.9. Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
LZT 138 0240 R1A
TEMS Pocket 7.2 for Sony Ericsson W995 and W995a Users Manual
3. Data Views: General
10
10 10 11 11 12
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
16
16 18 20 21 22 22 23 25 25 26 26 27 27 28 30 31 32 33 36 37 38 39 39 39 40 43 45 46 47 48
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. WCDMA Cells (View No. 2.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9. WCDMA Cell Id (View No. 2.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10. WCDMA Serv. Cell (View No. 2.3) . . . . . . . . . . . . . . . . . . . . . . . 4.11. WCDMA Channel (View No. 2.4) . . . . . . . . . . . . . . . . . . . . . . . . . 4.12. WCDMA Data (View No. 2.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.13. HSPA Data (View No. 2.6) ........................... 4.14. GSM Cells (View No. 3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.14.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.15. GSM Cell Id (View No. 3.2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.15.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16. GSM BA List (View No. 3.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.17. GSM Serving Cell (View No. 4.1) ...................... 4.18. GPRS Data (View No. 4.2) ........................... 4.18.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.19. GPRS Info (View No. 4.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.20. GSM C/I Info (View No. 4.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.21. GSM AMR (View No. 4.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
Contents
4.22. The WAP Browser Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.22.1. WCDMA WAP Browser Data View . . . . . . . . . . . . . . . . . 51 4.22.2. GPRS WAP Browser Data View . . . . . . . . . . . . . . . . . . . 53
5. Data Views with Graphs
55
5.1. W/G Serving RSSI (View No. 5.1) . . . . . . . . . . . . . . . . . . . . . . . . 56 5.2. W/G Cells (View No. 5.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 5.3. W/G Data (View No. 5.3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.4. WCDMA Serving (View No. 5.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 5.5. WCDMA SIR (View No. 5.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 5.6. WCDMA Cells (View No. 5.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.7. GSM Cells (View No. 5.7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 5.8. GSM Data (View No. 5.8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6. The Map View
68
6.1. Loading a Map Image into the Map View . . . . . . . . . . . . . . . . . . . . 68 6.2. Pinpointing Your Test Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 6.2.1. Setting the Map Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 6.2.2. Customizing the Appearance of Route Markers. . . . . . . . . . 69 6.2.3. Entering Map Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.2.4. Pinpointing and Recording . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.3. Positioning the Map Geographically . . . . . . . . . . . . . . . . . . . . . . . . 72
7. TEMS Pocket Functions in the Activity Menu
73
7.1. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 7.2. Insert Filemark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 7.3. Start/Stop Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 7.3.1. Icons Used for Logfile Recording . . . . . . . . . . . . . . . . . . . . . 74 7.4. Start/Stop Logfile Replay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 7.4.1. Replay Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . 75 7.4.2. Icons Used for Logfile Replay . . . . . . . . . . . . . . . . . . . . . . . 76 7.5. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 7.6. Start/Stop FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 7.7. Connect/Disconnect GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 7.8. Start/Stop Command Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 7.9. Pocket Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
LZT 138 0240 R1A
iii
8. The Pocket Menu
78
8.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 8.2. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 8.2.1. Icons Used for Cell Control . . . . . . . . . . . . . . . . . . . . . . . . . 79 8.2.2. Lock to RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 8.2.3. Lock Cell WCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 8.2.4. Lock ARFCN GSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 8.2.5. Lock Band WCDMA, Lock Band GSM . . . . . . . . . . . . . . . . . 81 8.2.6. Interplay between Locking Functions. . . . . . . . . . . . . . . . . . 82 8.2.7. Comparison with Locking Functions in TEMS Investigation 82 8.2.8. Voice Codec GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 8.2.9. HS Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 8.2.10. Ignore Cell Barred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8.2.11. Reset Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8.3. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8.3.1. Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 8.3.1.1. Viewing the Event Log . . . . . . . . . . . . . . . . . . . . . . . 85 8.3.1.2. Clearing the Event Log . . . . . . . . . . . . . . . . . . . . . . . 86 8.3.1.3. Enabling/Disabling Event Logging and Sound . . . . . 86 8.3.1.4. Shortcuts to Event Settings and Event Counters . . . 86 8.3.2. Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 8.3.2.1. Viewing Event Settings . . . . . . . . . . . . . . . . . . . . . . . 86 8.3.2.2. Modifying Event Settings. . . . . . . . . . . . . . . . . . . . . . 87 8.3.3. Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 8.3.3.1. Viewing Event Counters . . . . . . . . . . . . . . . . . . . . . . 88 8.3.3.2. Resetting Event Counters . . . . . . . . . . . . . . . . . . . . . 89 8.3.4. Event Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 8.3.5. List of Logged Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 8.3.5.1. CC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 8.3.5.2. MM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.3.5.3. SM Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 8.3.5.4. GMM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 8.3.5.5. IRAT Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.3.5.6. RR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 8.3.5.7. RRC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 8.3.5.8. Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 8.4. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 8.5. GPS Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 8.5.1. GPS Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 8.5.2. GPS Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 8.5.3. GPS Time Synch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
iv
Contents
8.6. FTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 8.6.1. FTP Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 8.6.2. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 8.7. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 8.7.1. Save Logfile To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 8.7.2. Autostart Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 8.7.2.1. Notes on Message Buffering: Pre-guard Period . . . 107 8.7.2.2. Post-guard Period . . . . . . . . . . . . . . . . . . . . . . . . . . 107 8.7.3. Upload Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 8.7.3.1. Setting an Upload Schedule . . . . . . . . . . . . . . . . . . 109 8.7.4. Compress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 8.7.5. FTP Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 8.7.6. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 8.8. Command Sequence Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 8.8.1. Voice Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 8.8.2. Video Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 8.8.3. FTP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 8.9. Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 8.9.1. About Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 8.9.2. Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 8.9.3. Import Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 8.9.4. Export Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 8.10. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 8.10.1. WAP Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 8.10.2. Data View Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 8.10.3. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 8.10.4. Backlight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 8.10.5. Cell Id Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 8.10.6. Power Display (GSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 8.10.7. Measure Mode Display (GSM) . . . . . . . . . . . . . . . . . . . . . 119 8.10.8. Auto Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 8.10.9. Reset All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
9. Uploading TEMS Pocket Logfiles from the Phone File System 10. Battery Charging Considerations
121 123
10.1. Choice of Phone Charger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 10.2. Using the Phones Built-in GPS. . . . . . . . . . . . . . . . . . . . . . . . . . 123 10.3. Using a TEMS Pocket Command Sequence . . . . . . . . . . . . . . . 123
LZT 138 0240 R1A
11. Support Contact Information Appendix A. Parameter Values
125 126
126 126 127 128 129 129 129 130 130 131 131 131 132 132 132 132 133 133 134 134 135 135
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 . . . . . . . . . . . . . . . . . . . . . . . A.9. GPS Fix Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.10. MM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.11. PDP Context Request Parameters. . . . . . . . . . . . . . . . . . . . . . . A.11.1. Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.11.2. Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.11.3. Peak Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.11.4. Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.11.5. Mean Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.12. Routing Area Update Failure Cause. . . . . . . . . . . . . . . . . . . . . . A.13. RR Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.14. RR Internal Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.15. RRC Failure Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.16. RRC Protocol Error Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.17. SM Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix B. Graphic Representation of Parameter Values
137
137 137 138 138 138 139 139
B.1. C/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2. Ec/N0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3. FER, RLC/LLC BLER/Retransmissions . . . . . . . . . . . . . . . . . . . . B.4. RLC DL/UL Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.5. RxLev, RSCP, RSSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.6. RxQual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.7. TX Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
Contents
Appendix C. Default Settings in TEMS Pocket Menus
140
C.1. Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 C.2. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 C.3. Events Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 C.4. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 C.5. GPS Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 C.6. FTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 C.7. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 C.8. Command Sequence Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 C.9. Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 C.10. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Index
143
LZT 138 0240 R1A
vii
viii
Chapter 1. Introduction
1.
Introduction
Welcome to TEMS Pocket. TEMS Pocket is an advanced cellular network diagnostics tool built into a Sony Ericsson or Nokia 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.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.
Whats New in TEMS Pocket 7.2
TEMS Pocket 7.2 is a Sony Ericsson based release, the successor to TEMS Pocket 7.0. (TEMS Pocket 7.1 is a Nokia-based release.)
1.1.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
LZT 138 0240 R1A
1.1.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.1.3.
New GPS
The GPS that can optionally be ordered with TEMS Pocket 7.2 is the GlobalSat BT-359.
1.1.4.
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 the UE happy rate.
1.2.
1.2.1.
What Was New in TEMS Pocket 7.0

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.2.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:
Chapter 1. Introduction
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.2.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.2.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.2.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
LZT 138 0240 R1A
dedicated/connected mode. The buffer is cleared when the phone is restarted.
1.2.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.
1.2.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.
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:
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.
LZT 138 0240 R1A
The top section of the display also shows: a symbol indicating that a logfile is being recorded (see section 7.3) a symbol indicating that a logfile is being replayed, and the status of the replay (see section 7.4.2) a symbol indicating that a cell control function is currently applied (see section 8.2) an icon for the latest TEMS Pocket event that occurred (if it occurred within the last 15 minutes; see section 8.3.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.1.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 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.1.
2.2.
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.5.3.
2.3.
Menus
When you press the Activity key on the phone, a tab with TEMS Pocket commands appears on top in the Activity menu:
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.
LZT 138 0240 R1A
2.4.
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 8.3.1. A shortcut to the event log is found in the Activity menu.
2.5.
2.5.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.3, 7.4, and 8.7.
2.5.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 section 8.5.
2.5.3.
Positioning by Pinpointing
In an indoor environment or other location without GPS coverage, you can use the Map view (see section 2.2) 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.6.
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 section 8.2 for full details.
2.7.
Command Sequence
TEMS Pocket offers the use of a command sequence for automated testing of various services. See section 8.8.
2.8.
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.
2.9.
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
LZT 138 0240 R1A
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 137. 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.
10
Chapter 3. Data Views: General
To turn off the help function, press the C key. Alternatively, press Options and choose Toggle help again.
3.3.
The Capture Function
You can take screenshots of any data view. To do this, you must first turn the screen capture function on (while in a data view) by selecting Options Toggle capture. Whenever the phone is in standby mode or during a voice call, you can now take a screenshot by pressing the Capture button. Please note that screenshots are always stored on the memory card (under Other\Pocket\ Capture), so the phone must have one inserted. A shutter sound is played when the screenshot is taken. Image files are named DV<X>-<Y>_<N>.bmp, where <X>-<Y> represent the data view number and <N> is a counter starting at 1. Up to 1000 screenshots of each data view can be stored.
3.4.
Other Data View Actions
In some data views you can perform an action relating to a piece of data shown in the view. For example, in data views listing cells, you can lock on one of the cells. All data view actions are performed by pressing the Options button and choosing Data view actions. A submenu appears listing the available actions.
LZT 138 0240 R1A
11
Specifics on data view actions are found in the subsequent sections.
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. Page 16
1.2
PDP Context
20
1.3
MM/GMM
21
1.4
Time Log
22
1.5
FTP Data
23
12
No. 1.6
View Name GPS
Description Displays essential GPS data: latitude and longitude, altitude and speed, number of satellites, fix quality, time and date. Not a data view (but has a number). See chapter 6. Displays UARFCN, cell status, scrambling code, RSCP, Ec/N0, and path loss for each cell in active set and monitored/detected neighbor sets. Displays UARFCN, scrambling code, CI, and RSCP for each cell in 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, 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.5) during WAP browsing.
Page 25
1.7 2.1
Map WCDMA Cells
68 26
2.2
WCDMA Cell Id
27
2.3 2.4
WCDMA Serv. Cell WCDMA Channel
28 30
2.5
WCDMA Data
31
2.6
HSPA Data
33
WCDMA WAP browser view
51
LZT 138 0240 R1A
13
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 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. Displays GSM logical channel information, AMR codec selected on uplink and downlink, and statistics on AMR codec utilization.
Page 36
3.2
GSM Cell Id
38
3.3
GSM BA List
39
4.1
GSM Serving Cell
40
4.2
GPRS Data
43
4.3
GPRS Info
46
4.4
GSM C/I Info
47
4.5
GSM AMR
48
14
No. 5.1 5.2
View Name GPRS WAP browser view W/G Serving RSSI W/G Cells
Description 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 53 56 58
5.3
W/G Data
60
5.4 5.5 5.6 5.7 5.8
WCDMA Serving WCDMA SIR WCDMA Cells GSM Cells GSM Data
61 62 63 64 66
LZT 138 0240 R1A
15
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 8.2.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
16
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 8.2.2), no GSM neighbors will ever be measured. Line 5: GSM serving cell Lines 68: Three strongest GSM neighbors Screenshot 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 Key RxLev: Received Signal Strength (unit userconfigurable: see section 8.10.6), numeric/graphic Lines 910 are used in both WCDMA and GSM mode, showing information 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. C: Current RAT {G: GSM, W: WCDMA, : No service} (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
LZT 138 0240 R1A
17
Lines 910 (continued) RAC: Serving cell Routing Area Code MCC: Serving cell Mobile Country Code MNC: Serving cell Mobile Network Code LAC: Serving cell Location Area Code RNC: Serving cell Radio Network Controller ID (WCDMA only; Cell Identity for WCDMA = RNC + CI) Screenshot CI: Serving cell Cell Identity, 16 bits (= C-Id: see 3GPP 25.401, section 6.1.5)
Key
4.1.1.
Data View Actions

You can lock on a cell or (in WCDMA mode) an UARFCN that is listed in the data view.
18
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 R1A
19
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} 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.
Screenshot
Key There are no actions associated with this data view.
20
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 R1A
21
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.
22
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 8.6.1 for details.
LZT 138 0240 R1A
23
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 8.3.5.8) is generated providing a summary of the file transfer and its performance. There are no actions associated with this data view.
24
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. 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.
Screenshot
4.7.
Map (View No. 1.7)
See chapter 6.
LZT 138 0240 R1A
25
4.8.
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.8.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.
26
4.9.
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 Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot
Key
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.
LZT 138 0240 R1A
27
4.10.
WCDMA Serv. Cell (View No. 2.3)

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
28
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 Screenshot 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.
Key
LZT 138 0240 R1A
29
4.11.
WCDMA Channel (View No. 2.4)

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.
30
4.12.
WCDMA Data (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 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.12.1 below.
LZT 138 0240 R1A
31
Lines 78 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Screenshot
Key
4.12.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.18).
32
4.13.
HSPA Data (View No. 2.6)

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. 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).
Screenshot
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 R1A
33
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). 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). 0RE: Percentage of blocks on HS-DSCH that were transmitted successfully on first attempt (zero retransmissions). BLN: Total number of blocks to be received on the HS-DSCH. 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
34
Line 7: HSDPA DTrChBR: Total bit rate on all downlink transport channels; same as DT: Rate in the WCDMA Data view (see section 4.12) 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.12) 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 R1A
35
4.14.
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 8.10.6), 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
36
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.14.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 R1A
37
4.15.
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 CI: Serving Cell Identity RxLev: Serving Cell RxLev (unit user-configurable: see section 8.10.6), 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
Screenshot
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.
38
4.15.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.
4.16.
GSM BA List (View No. 3.3)

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 8.10.6), 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.16.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.
LZT 138 0240 R1A
39
4.17.
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 8.10.6), 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 128 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
40
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 TC: Traffic Channel (TCH ARFCN) or Stand-alone Dedicated Control Channel (SDCCH ARFCN) or Packet Dedicated Traffic Channel (PDTCH ARFCN). Hopping channels are shown one at a time; see section 3.1. TS: Timeslot Number TA: Timing Advance TX: UE Transmit Power (dBm), numeric/graphic RLTC/M: Radio Link Timeout (Current) and Radio Link Timeout (Max = Start) Screenshot dedicated mode Line 4 (dedicated mode) C/I: Carrier-to-interference ratio in dB for the traffic channel currently indicated by TC on line 3. That is, for hopping channels the displaying of C/I values is synchronized with the traversal of the hopping list; compare section 3.1. C/I is supported for the modes TCH/F, TCH/H, and PDTCH. Numeric/ graphic presentation. RQ: Receive Bit Error Rate (RxQual; scale defined in 3GPP 05.08), numeric/graphic Key FER: Frame Erasure Rate (FER) in percent. Calculated taking DTX into account, i.e. the figure is based only on blocks actually transmitted. Numeric/graphic presentation. DXU: DTX rate (%) on uplink DXD: DTX rate (%) on downlink
LZT 138 0240 R1A
41
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 129 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 dedicated mode
42
4.18.
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 8.10.6), 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
LZT 138 0240 R1A
43
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
44
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.18.1 below. Lines 910 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
4.18.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.12).
LZT 138 0240 R1A
45
4.19.
GPRS Info (View No. 4.3)

Lines 14 are the same as in the GPRS Data view: see section 4.18. 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 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 130 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.
Key
46
4.20.
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.
LZT 138 0240 R1A
47
4.21.
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 8.10.6), 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.
48
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 Lines 89 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
LZT 138 0240 R1A
49
4.22.
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 8.10.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.
50
4.22.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
LZT 138 0240 R1A
51
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 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)
Screenshot
Key
52
4.22.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 8.10.6), 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}
LZT 138 0240 R1A
53
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
54
Chapter 5. Data Views with Graphs
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 8.3.1.3 and 8.3.2). Data views with graphs have no actions associated with them.
LZT 138 0240 R1A
55
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
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 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 8.10.6), numeric/graphic
56
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
LZT 138 0240 R1A
57
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
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 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 8.10.6), 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
58
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
LZT 138 0240 R1A
59
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
Screenshot
Line 2 (GSM 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
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.
60
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
LZT 138 0240 R1A
61
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
62
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
LZT 138 0240 R1A
63
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) RxLv: Received Signal Strength (unit userconfigurable: see section 8.10.6), 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 If the cell supports packet channels (broadcasts a PBCCH), the two rightmost parameters become: C31: GPRS Signal Strength Threshold Criterion C31 Line 2 (Strongest GSM neighbor) NC: Neighbor Cell BCCH ARFCN The rest is as on line 1 except for the addition of: A: Location Area/Routing Area properties: =: Same LA/RA R: Same LA, different RA L: Different LA P: PLMN not matching : Unknown
Screenshot
Key
64
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
LZT 138 0240 R1A
65
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
66
Graph Note that unit in the graph is kbit/s, while the prefix in the data rate text fields is either k or M. Green line: GSM RLC/MAC downlink data transfer rate in kbit/s Light green line: GSM RLC/MAC uplink data transfer rate in kbit/s Screenshot Lines 34 are the same as the two bottom lines in the W/G Cells view: see section 4.1.
Key
LZT 138 0240 R1A
67
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.
68
Chapter 6. The Map View
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
LZT 138 0240 R1A
69
color coding is explained in appendix B, page 137. 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.
70
Chapter 6. The Map View
To pinpoint a spot on the map, move the crosshairs to the desired position, then press the Select button. Note: The screen capture function must be turned off, otherwise the right soft button will be labeled Capture instead.
Continue pinpointing at regular intervals along the route, and whenever you change direction. Consecutive waypoints are automatically connected by route markers.
When you are done with the measurement, press Options and select Data view actions Stop pinpointing.
LZT 138 0240 R1A
71
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.
72
Chapter 7. TEMS Pocket Functions in the Activity Menu
7.
TEMS Pocket Functions in the Activity Menu
A number of TEMS Pocket functions are accessed by pressing the Activity key. This is the button labeled . Note that many of these functions are found only in the Activity menu and not among the submenus of the Pocket menu. They are placed here to be conveniently accessible regardless of what TEMS Pocket functions or other phone functions you are using.
7.1.
Operational Mode
Active: All TEMS Pocket functions are active. Background: No data views are displayed, but all other TEMS Pocket functions are active. Inactive: No TEMS Pocket functions are active.
7.2.
Insert Filemark
This command inserts filemarks (text strings) in a logfile while it is being recorded. You can use filemarks to tag segments of special interest in the logfile. For example, you might want to note down the location where something particular happened (helpful if you are not using a GPS of any kind). On selecting this command you are prompted to type the filemark text. It may consist of up to 127 characters. This command is available only while logfile recording is in progress.
LZT 138 0240 R1A
73
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 Logfiles menu; see section 8.7.2. 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 section 8.7 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 8.7.1) 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 8.2.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
74
settings that were in force at a particular point while recording the logfile. This can however be done by replaying the logfile in TEMS Investigation and studying certain information elements exhibited in that application (Band Control, Serving Cell List Active, and others). In both TEMS Pocket and TEMS Investigation, events reflecting the application of cell control functions at recording time will appear during replay, just like any other events. If you rewind the logfile, the TEMS Pocket user interface (data views, event log, event counters) is once again cleared. The same thing happens when you exit replay mode. During logfile recording, during execution of a command sequence, and during FTP sessions the replay command is not available.
7.4.1.
Replay Control Functions

Play: Replays the logfile at approximately live speed. While the replay is in progress the button is relabeled Pause, and pressing the button in that situation pauses the replay. Press the button once more (now named Play again) to resume the replay from the point where it was paused. Step: Reads one more phone message from the logfile and then pauses the replay. You may have to step several times to see any changes in the data. Options: Pressing this button gives access to further replay control functions; see below. Rewind: Rewinds the logfile to the beginning and clears the TEMS Pocket user interface. Press Play to start the replay once more. Exit replay mode: Aborts the logfile replay, closes the logfile, and returns TEMS Pocket to live mode.
LZT 138 0240 R1A
75
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.
Event Log
This is a shortcut to the event log; see section 8.3.1.
7.6.
Start/Stop FTP
This command is used to conduct FTP sessions, including uploading of TEMS Pocket logfiles if you prefer to do these uploads manually. The
76
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 section 8.6. A series of events is generated in connection with each FTP session: see section 8.3.5.8. During logfile replay and during execution of a command sequence, this command is not available.
7.7.
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 section 8.5. The command is visible only if you have selected manual connect; see section 8.5.1. While a connect operation is in progress, the menu item reads Connecting and is again grayed. During logfile replay this command is not available.
7.8.
Start/Stop Command Sequence
This command starts and stops a command sequence. How to set up command sequences is explained in section 8.8. When starting the command sequence, you are prompted to select which action it should perform: voice, video, or FTP. The action you select must have been previously defined in order for the command sequence to execute; again, see section 8.8. During logfile replay this command is not available.
7.9.
Pocket Menu
This is a shortcut to the Pocket menu; see chapter 8.
LZT 138 0240 R1A
77
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 tab. Cell control menu: Used to control the phones behavior in the network (lock on RAT/band/frequency/cell etc.). See section 8.2. Events menu: Used to show and control the event log, event counters, and event settings. See section 8.3. Data views menu: Used to control visibility of data views. See section 8.4. GPS menu: Used to configure GPS settings. See section 8.5. FTP menu: Used to set up FTP sessions and FTP logfile transfer. See section 8.6. Logfile menu: Used to configure automated logfile transfer. See section 8.7. Command sequence menu: Used to define a command sequence. See section 8.8. Tools menu: Used for various purposes, including import and export of user-defined TEMS Pocket settings. See section 8.9. General settings menu: Used to control miscellaneous TEMS Pocket settings. See section 8.10.
The Pocket menu has the following submenus:
78
Chapter 8. The Pocket Menu
8.2.
Cell Control Menu
In this menu are collected the functions that modify the phones behavior in the network.
8.2.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.
8.2.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. 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 8.2.6.
LZT 138 0240 R1A
79
Note: In the phones main menu (Settings Connectivity tab 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 8.2.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).
8.2.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.8. Regarding interplay between locking functions, see section 8.2.6.
8.2.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.
80
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.14, and 4.15. Regarding interplay between locking functions, see section 8.2.6.
8.2.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.
Off: Function not applied. 850, etc.: The phone will be locked to the indicated GSM band.
LZT 138 0240 R1A
81
The phone cannot be band-locked while a voice or video call is in progress. Regarding interplay between locking functions, see section 8.2.6.
8.2.6.
Interplay between Locking Functions
If you lock the phone to a cell, UARFCN, or band (sections 8.2.3, 8.2.4, 8.2.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.
8.2.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 8.2.6 above.) For full details, see the TEMS Investigation 10.0 Data Collection Users Manual, section 15.2.1.
8.2.8.
Voice Codec GSM
This function is used to modify the list of preferred GSM voice codecs that the phone reports to the network. In the dialog are shown all GSM voice codecs that the phone supports. You cannot deselect all codecs in the dialog; at least one codec must remain selected at all times.
82
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. 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
8.2.9.
HS Capability
You can enable or disable the TEMS Pocket phones HSPA capabilities as shown below. Note that this function does not affect the behavior of the 3G/H status bar symbol (see section 2.1). 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.
LZT 138 0240 R1A
83
8.2.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.
8.2.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.
8.3.
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 8.3.1.3.
84
8.3.1.
8.3.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:
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
LZT 138 0240 R1A
85
8.3.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.
8.3.1.3.
Enabling/Disabling Event Logging and Sound
While in the event log, you can configure some general aspects of event logging as follows: 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 8.3.2).
8.3.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 8.3.2) or event counters (see section 8.3.3).
8.3.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 8.9.4).
8.3.2.1.
Viewing Event Settings
From the Events menu, choose Event Settings.
86
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 8.3.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.
8.3.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 8.3.5. (continued on next page)
LZT 138 0240 R1A
87
Sound: Off means that no sound will be played when the event occurs. Default means that, in idle mode, the sound predefined 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 8.3.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 8.3.5.
8.3.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.
8.3.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 8.3.2). All event types are listed and described in section 8.3.5 below. 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.
88
8.3.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.
8.3.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 8.3.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 R1A
89
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 WCDMA to GSM Normal Events Failure Events
8.3.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 8.3.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.
8.3.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
90
8.3.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 R1A
91
8.3.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)
8.3.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) GMM Detach Att. (GMM Detach Attempt) T N N F N Def Off Off On Off Parameters Attach type: {GPRS, Combined} Attach type: {GPRS, Combined} T3310 expired or GMM Reject Cause GMM Cause
92
Event Name 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
Def Off Off
Parameters 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
8.3.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)
On
BCCH ARFCN, BSIC
Off
New UARFCN, New SC
Off
BCCH ARFCN, BSIC
On
BCCH ARFCN, BSIC
LZT 138 0240 R1A
93
Event Name 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) U2G HO Failure (UTRAN To GSM Handover Failure) U2G HO Success (UTRAN To GSM Handover Success)
T N
Def Off
Parameters New UARFCN, New SC
Off
UARFCN, SC
On
UARFCN, SC
Off
New BCCH ARFCN, New BSIC UARFCN, SC
Off
On
UARFCN, SC
Off
New BCCH ARFCN, New BSIC
8.3.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) T F Def On Parameters BCCH ARFCN, BSIC, RR Cause
94
Event Name 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) 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
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) BCCH ARFCN, BSIC, RR Internal Cause BCCH ARFCN, BSIC, RR Internal Cause
On
On
N F
On On
8.3.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.
LZT 138 0240 R1A
95
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) 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 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
N F
On On
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
96
8.3.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) 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 T N F Def L L Automatic Upload Failure Cause File name, File size, Duration, Bit rate UL, Bit rate DL Parameters
N N F N N F N F N F N N
L On On On On On On On Off Off Off Off
LZT 138 0240 R1A
97
Event Name Voice Call Fail. (Voice Call Failure) Voice Call Start
T F N
Def Off Off
Parameters
8.4.
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.
98
8.5.
GPS Menu
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. You can export your GPS settings to file; they are included in the Export settings operation (Tools menu: see section 8.9.4).
Using the Built-in GPS

The Sony Ericsson W995 and W995a have a built-in GPS, and TEMS Pocket can make use of this device for positioning. Access to the built-in GPS is included in the TEMS Pocket standard package. To be available to TEMS Pocket, the built-in GPS must be enabled in the regular phone user interface. In the 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. The built-in GPS consumes a large amount of power and thus requires frequent charging of the phone battery. See section 10.2 for some further specifics on this matter.
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.
LZT 138 0240 R1A
99
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 as described in section 8.5.2. The Assisted start option (see Using the Built-in GPS above) cannot be combined with an external GPS.
8.5.1.
GPS Connect
Off: The phone will not connect to any GPS (whether internal or external), and the Connect GPS item in the Activity menu (section 7.7) is hidden. If a GPS unit is currently connected, choosing this option will disconnect it. If a connect is in progress, it will be aborted. Manual: The phone can be connected manually to a GPS (internal or external) by using the command in the Activity menu (see section 7.7). If a manual connect fails, an error message is displayed. Automatic: If GPS device (see section 8.5.2) 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 try to connect to the selected GPS automatically as soon as the phone is turned on. 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. Switching between the options Manual and Automatic disconnects a GPS that is currently connected.
100
8.5.2.
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 8.5.1), 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.7) will always apply to the Bluetooth device last paired with the phone as just described. If you want to refresh the search for Bluetooth devices, you can do so at any time by selecting the Bluetooth option again.
LZT 138 0240 R1A
101
8.5.3.
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 in the phone.
8.6.
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.6. You can export your FTP settings to file; they are included in the Export settings operation (Tools menu: see section 8.9.4).
8.6.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.
102
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 8.6.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 R1A
103
8.6.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 of the FTP server. This can be either an alphanumeric string, without ftp:// at the beginning (for example, ftp.myftpserver.com), or a 12-digit number. 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. FTP password: User password on the FTP server. (continued on next page)
104
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 8.6.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.
8.7.
Logfile Menu
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 ordinary files in the phone file system and can be handled from the File manager. Logfiles are stored either in the internal phone memory or on a memory stick (see section 8.7.1 below). Sony Ericsson phones support Memory Stick M2. 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: see section 8.7.2. TEMS Pocket has a logfile replay function, described in section 7.4. You can also transfer the logfiles to a PC and replay them in TEMS Investigation (version 10.0.3 or later) or import them into the database of a TEMS Automatic system (version 8.0 or later). The file transfer can be done through a USB cable or via Bluetooth. It is also possible to upload logfiles to an FTP server using the built-in FTP client (see sections 8.7.3 and 8.7.6), or to send logfiles as attachments to e-mail. To reduce FTP transfer times, you can opt to compress logfiles prior to upload. This is dealt with in section 8.7.4.
LZT 138 0240 R1A
105
You can export all logfile-related settings to file; they are included in the Export settings operation (Tools menu: see section 8.9.4).
8.7.1.
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.
8.7.2.
Autostart Logfile
You can configure logfile recording to start automatically in certain situations. Below it is indicated when the automatic recording terminates if you do not stop the recording manually from the Activity menu (which is always possible; 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.6) and stops at the end of that session. (Recording is not triggered by uploading logfiles via FTP.) Press Mark to check an option. Press Unmark to uncheck an option that is currently checked. Press Save to confirm your selections.
106
8.7.2.1.
Notes on Message Buffering: Pre-guard Period
If at least one of the options Voice, Video, and FTP is checked in the Autostart logfile 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 logfile recording is triggered, the file will capture as much as possible of the signaling leading up to the establishment of the call or data session. The arrangement thus serves the same purpose as the pre-guard period set in TEMS Automatic work order actions. In TEMS Pocket the length of the pre-guard cannot be customized; the exact period of time spanned by the message buffering depends on the amount of signaling that has occurred. The buffering makes the logfile more complete not only for mobile-terminated (MT) but also for mobile-originated (MO) calls and data sessions. This is because in the MO case, the recording does not begin instantly as the user initiates the service from the phone keypad, but only after a certain delay (the exact details being service-specific). Selecting the Startup option does not trigger buffering of messages. Message buffering is furthermore associated with automatic logfile recording only. The buffer will be kept up-to-date whenever autostart options are selected as described above, but if you record a logfile manually (see section 7.3), the buffer contents are not logged.
8.7.2.2.
Post-guard Period
When the trigger condition for stopping an automatic logfile recording 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 R1A
107
8.7.3.
Upload Logfile
Here you configure uploading of logfiles via FTP to an FTP server. What server to upload to is selected in the FTP server submenu: see section 8.7.6. Immediate: Each logfile is uploaded as soon as it has been recorded. Schedule: Logfiles are uploaded according to a schedule that you define here. Select this option to enter the Start time screen, then turn to section 8.7.3.1. Each time an upload is performed, all logfiles are sent that have not yet been uploaded (logfiles created since the last upload, plus any older logfiles that may remain because you aborted uploading of these files). Off: No 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.6).a
a. There is yet another way to upload logfiles manually, using a command accessed from the phone file system. See chapter 9.
Logfiles cannot be uploaded while a command sequence is executing or during logfile replay. If a logfile upload comes due (according to the upload schedule defined) while one of these tasks is in progress, that upload is simply canceled. Uploads are resumed (again following the upload schedule) after the command sequence or replay has been ended. A set of events is provided reporting on the progress and outcome of each automatic upload. See section 8.3.5.8.
108
8.7.3.1. 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.
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.6). If you abort an upload, the files that were not transferred will be included in the next upload.
LZT 138 0240 R1A
109
8.7.4.
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 procedure chosen (automatic or manual: see section 8.7.3). 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.6), 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.
110
8.7.5.
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.
8.7.6.
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 8.6.2). Note that the Remote directory parameter must have a valid value for any server that is going to be used for logfile uploads.
8.8.
Command Sequence Menu
TEMS Pocket supports automation of voice calls, video calls, and FTP data sessions using the command sequence. The command sequence can only run one service at a time; it is not possible to mix, for example, voice and FTP in the sequence. You start and stop the command sequence from the Activity menu: see section 7.8. While the command sequence is executing it will repeat the action defined for it over and over again.
LZT 138 0240 R1A
111
Note: Running a command sequence for extended periods of time places a high load on the phone battery. See section 10.3 for advice on how to ensure that the battery is not drained. You can export your command sequence setups to file; they are included in the Export settings operation (Tools menu: see section 8.9.4).
8.8.1.
Voice Settings
Dial number: Enter the number to call. Valid characters are: +, #, *, 0, ..., 9, and p (for pause). Call duration: Specify the duration in seconds of each voice call. Guard time: Specify the duration in seconds of the idle interval between voice calls.
8.8.2.
Video Settings
Dial number: Enter the number to call. Valid characters are: +, #, *, 0, ..., 9, and p (for pause). Call duration: Specify the duration in seconds of each video call. Guard time: Specify the duration in seconds of the idle interval between video calls.
112
8.8.3.
FTP Settings
FTP transfer: Select the FTP transfer to perform: one of those you have defined in the FTP menu (see section 8.6.1). Guard time: Specify the duration in seconds of the idle interval between FTP transfers.
8.9.
Tools Menu
In this menu are collected miscellaneous functions and information.
8.9.1.
About Screen
Line 1: Name of TEMS Pocket product package. Line 2: TEMS Pocket version. Lines 34 IMSI: International Mobile Subscriber Identity of the SIM card used. It is made up of Country Code (3 digits) Network Code (2 digits) Identification Number (at most 10 digits)
IMEI: International Mobile Equipment Identity of the phone. It is made up of Type Approval Code (6 digits) Final Assembly Code (2 digits) Serial Number (6 + 1 digits)
LZT 138 0240 R1A
113
8.9.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.
8.9.3.
Import Settings
TEMS Pocket settings previously exported to files (see section 8.9.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. Then press Import.
114
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.
After importing FTP settings, you should verify that all data accounts referred to in the FTP server configurations are in fact defined in the phone. An FTP server configuration referencing a data account that is lacking in the phone is of course useless for that phone.
8.9.4.
Export Settings
You can export to file all user-configured settings for command sequences, events, FTP and logfiles, as well as everything in the General settings menu. A separate file is created for each of the categories just mentioned. The settings files are stored in the directory Other\Pocket\Settings (regardless of the choice of storage medium; see below). From the Tools menu, select Export settings.
LZT 138 0240 R1A
115
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.
You are prompted to create a folder for the export files (or, if applicable, select an existing folder):
After you select one of the options, the export is performed automatically.
8.10.
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 Power unit: GSM units or dBm (RxLev) Full/Sub values (RxLev, RxQual) Auto answer
116
The settings made here remain in force until you modify them again or reset them with the Reset All command (see section 8.10.9). You can export the General settings to file; they are included in the Export settings operation (Tools menu: see section 8.9.4).
8.10.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.22, page 50. 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.
8.10.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 in the phone (main menu Settings Display tab Theme).
LZT 138 0240 R1A
117
8.10.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.
8.10.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.
8.10.5.
Cell Id Format
Hex: LAC and CI are displayed in hexadecimal digits. Decimal: LAC and CI are displayed in decimal digits.
118
8.10.6.
Power Display (GSM)

dBm: RxLev is displayed in dBm. GSM: RxLev is displayed in GSM units. (Not applicable to graphs.)
8.10.7.
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.
8.10.8.
Auto Answer
If On is chosen, the phone will automatically answer an incoming call (after a period of time equivalent to two standard ring signals).
LZT 138 0240 R1A
119
8.10.9.
Reset All
This command restores all settings in the General settings menu to their defaults. See appendix C, page 140 for a listing of the default settings.
120
Chapter 9. Uploading TEMS Pocket Logfiles from the Phone File System
9.
Uploading TEMS Pocket Logfiles from the Phone File System
Besides the TEMS Pocket internal logfile upload functions, covered in sections 7.6 and 8.7.3, 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 R1A
121
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 8.6.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.
122
Chapter 10. Battery Charging Considerations
10.
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.
10.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.
10.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.
10.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 R1A
123
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: Voice call (see section 8.8.1) 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.8.) 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.
124
Chapter 11. Support Contact Information
11.
Support Contact Information
For support in using TEMS Pocket, please contact Ascom according to the directions found at www.ascom.com/tems 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 R1A
125
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
126
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 R1A
127
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
128
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 R1A
129
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.
I II III
GPRS Network Mode of Operation

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
Handling of paging in the GPRS network.
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
130
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 R1A
131
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
132
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 R1A
133
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
134
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 R1A
135
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
136
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 R1A
137
B.3.
FER, RLC/LLC BLER/Retransmissions
Bar length is constant. Value = x (%) x=0 1x4 x5 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
138
B.6.
RxQual
Bar length is constant. Value = x x=0 1x4 x5 green yellow red Color
B.7.
TX Power
Bar height is proportional to (Value (30 dBm)). Value = x (dBm) x<5 5 x < 15 x 15 green yellow red Color
LZT 138 0240 R1A
139
This appendix lists the defaults for all settings editable from the Activity and Pocket menus.
C.1.
Operating Mode
Active mode
C.2.

Cell Control Menu
All locking functions are by default turned off. Voice codec GSM: All codecs checked HS capability: On Ignore cell barred: Off Note: Unlike settings in other menus, these settings revert to their defaults when the phone is powered off and on.
C.3.

Events Menu
Event logging: Silent Event counters: On for all events Event settings: See section 8.3.5
C.4.
Data Views Menu
All views visible (including the Map view)
140
C.5.

GPS Menu
GPS connect: Off GPS device: Internal GPS time synch: Off
C.6.

FTP Menu
Save file to (FTP Get): Memory stick
FTP transfer
C.7.

Logfile Menu
Save logfile to: Memory stick Autostart logfile: No options checked Upload logfile: Off Compress: Off FTP resume: Off
C.8.

Command Sequence Menu

Call duration: 10 s Guard time: 20 s Call duration: 10 s Guard time: 20 s Guard time: 20 s
Voice settings
Video settings
FTP
C.9.

Tools Menu
Import settings: Memory stick Export settings: Memory stick
LZT 138 0240 R1A
141
C.10.

General Settings Menu
WAP data view: On Data view style: Themed Messages: Minimized Backlight: 5 minutes Cell Id format: Hex Power display: dBm Measure mode display: Sub Auto answer: Off
142
Index
Index
Numerics
3G symbol (at top of display) 5
A
About screen 113 Activate PDP Context Failure Cause 126 active set (WCDMA) 16, 26, 27, 56, 58 Activity key 7, 73 Activity menu 7, 73, 78 altitude 25 AMR codecs active set 49 used on downlink 49 used on uplink 49 utilization of 49 APN 20 ARFCN 17 ARQ mode (EGPRS) 44 Auto Answer dialog 119 Automatic Repeat Request Mode (EGPRS) 44 Automatic Upload Failure Cause 126 Autostart Logfile dialog 106
B
Backlight dialog (display backlight) 118 barred cells, accessing of 84 Base Station Identity Code 36, 39, 40, 43, 48, 53, 56, 58, 64 battery charging considerations 123 BCCH ARFCN 17, 36, 38, 39, 40, 56, 58, 64 BEP (EGPRS) 44 BEP variance (EGPRS) 44 bit error probability, mean (EGPRS) 44 bit error probability, variance (EGPRS) 44 BLER (GSM) 45, 54, 60, 66 BLER (WCDMA) 31, 51, 52, 60
LZT 138 0240 R1A
143
BLER Target, downlink (on transport channel) 30 block retransmission rate (GSM) 45, 54, 60, 66 block retransmission rate (WCDMA) 31, 52 BS-AG-BLKS-RES 40 BSIC 17, 36, 39, 40, 43, 48, 53, 56, 58, 64 BS-PA-MFRMS 37, 38, 40 bytes transferred (GSM) 45 bytes transferred (WCDMA) 31
C
C value (EGPRS) 44 C/I 41, 44, 47, 48 graphic representation 137 C1 36, 57, 58, 64 C2 36, 57, 58, 64 C31 36, 57, 59, 64 C32 36, 57, 59 capture function (taking screenshots) 4, 11 Carrier-to-interference ratio (C/I) 41, 44, 47, 48 CC Cause 127 CC events 90 CCCH Configuration 40, 128 cell control functions 8, 79 icon for 6, 74 Cell Control menu 79 Cell Id Format dialog 118 Cell Identity 18, 27, 38 presentation in dedicated/connected mode 3 Cell Reselection Criterion (C2) 36, 57, 58, 64 Cell Reselection Hysteresis 37, 38 cell selection and reselection parameters 28 channel coding scheme (GPRS) on downlink 44 on uplink 44 Channel Mode 42 Channel Quality Indicator (HSDPA) 33 Channel Type 42, 129 channelization codes on HS-SCCH, number of 33 charging of phone battery 123 CI 18, 27, 38 presentation format 118 Ciphering Mode 42 color coding of parameter values 10
144
Index
command sequence 9, 111 battery charging considerations 112, 123 for FTP sessions 113 for video calls 112 for voice calls 112 starting and stopping 77 Command Sequence menu 111 Compressed Mode 30, 31 compressing logfiles before upload 105, 110 Connect GPS command 77 CQI 33
D
data rate (GSM channel mode) 42 data view actions 11 Data View Style dialog 117 data views 5, 10 browsing 5 categories of 5 display style 117 general properties of 10 survey of 12 taking snapshots of 4, 11 updating in replay mode 74 visibility of 98 with graphs 3, 6, 55 data views in text format 5, 16 Data Views menu 98 DCH, time using 22 Deactivate PDP Context Cause 129 default settings in TEMS Pocket menus 140 Delay Class (PDP Context Request) 20, 131 Disconnect GPS command 77 Downlink Signalling Counter 40 DRX Timer Max 46 DSC (Current) 40 DSC (Max) 40 DTX rate in GSM, on downlink 41, 49 in GSM, on uplink 41, 49 in HSUPA 34
LZT 138 0240 R1A
145
E
Ec/No 16, 26, 56, 58, 61, 63 graphic representation 137 E-DPCCH/E-DPDCH retransmission rate 34 EGPRS modulation coding scheme 53 EGPRS window size 46 end-of-charge state (of phone battery) 123 EoC 123 Equivalent PLMN, time registered in 22 E-TFCI 34 event counters 74, 88 resetting 89 viewing 88 event log 74, 76, 85 clearing 86 details of individual events 85 viewing 85 event settings 86 modifying 87 viewing 86 events 8, 86 enabling/disabling event logging and sound 86 event log 86 icons for 6, 89 list of 90 presentation in graphs 55 Events menu 84 exporting TEMS Pocket settings 4, 115
F
FER 41, 49 graphic representation 138 filemarks, inserting in logfiles 73 Frame Erasure Rate 41, 49 FTP duration of FTP session 23 name of transferred file 23 selecting server to upload logfiles to 111 setting up Put and Get operations 102 specifying FTP servers 104 starting and stopping FTP sessions 76 throughput 23 total bytes transferred 24
146
Index
FTP Data data view (no. 1.5) 23 FTP menu 102 FTP resume 111 FTP server address 23 FTP Server dialog 104, 111 FTP session, direction of (UL/DL) 23 FTP Settings dialog (command sequence) 113 FTP Transfer dialog 102 Full/Sub values (for RxLev and RxQual) 119
G
General Settings menu 116 GMM Attached 21 GMM Cause 129 GMM events 92 GMM State 46 GPRS Cell Ranking Criterion (C32) 36, 57, 59 GPRS Data data view (no. 4.2) 43 actions in 45 GPRS Info data view (no. 4.3) 46 GPRS Network Mode of Operation 46, 130 GPRS Signal Strength Threshold Criterion (C31) 36, 57, 59, 64 GPRS timeslots 43, 53, 66 GPS 8 battery charging considerations 123 Bluetooth pairing 100 connect mode 100 connecting and disconnecting 77 date 25 fix quality 25, 130 number of satellites seen 25 requirements on external GPS device 100 selecting type of GPS device 101 synchronizing phone clock with 102 time 25 using external GPS with TEMS Pocket 99 using phones built-in GPS with TEMS Pocket 99 GPS Connect dialog 100 GPS data view (no. 1.6) 25 GPS Device dialog 101 GPS menu 99 GPS Time Synch dialog 102 graphic presentation 10
LZT 138 0240 R1A
147
graphic representation of parameter values 137 graphs 6 graphs in data views 3 GSM AMR data view (no. 4.5) 48 GSM BA List data view (no 3.3) 39 actions in 39 GSM C/I Info data view (no. 4.4) 47 GSM Cell Id data view (no. 3.2) 38 actions in 39 GSM Cells data view (no. 3.1) 36 actions in 37 GSM Cells data view (no. 5.7, with graph) 64 GSM Channel Type 17 GSM Data data view (no. 5.8) 66 GSM Serving Cell data view (no. 4.1) 40
H
H symbol (at top of display) 5 happy rate (HSUPA) 34 HARQ processes on HS-DSCH, number of 33 help, on-screen 10 Home PLMN, time registered in 22 hopping channels 10, 17, 36, 38, 39, 41, 43, 48, 53, 56, 58, 64, 66 Hopping Sequence Number 42 HS Capability dialog 83 HSDPA actual transport block size 33 block error rate, first retransmission 34 channelization codes on HS-SCCH, number of 33 CQI 33 HARQ processes on HS-DSCH, number of 33 percentage of blocks transmitted successfully on first attempt 34 requested transport block size 33 residual block error rate 34 total number of blocks to be received 34 turning phone capability on and off 83 HSN 42 HSPA Data data view (no. 2.6) 33 HSUPA DTX rate 34 E-DPCCH/E-DPDCH retransmission rate 34 E-TFCI 34 happy rate 34
148
Index
Serving Grant Index 34 transport block size on E-DCH 34
I
icons for cell control functions 79 for events 89 for logfile recording 74 Idle mode time spent in (GSM) 22 time spent in (WCDMA) 22 Ignore Cell Barred dialog 84 IMEI 113 importing TEMS Pocket settings 4, 114 IMSI 113 indoor positioning by pinpointing 68 Insert Filemark command 73 interplay between locking functions 82 Inter-RAT events 93 invalid parameters, representation of 10
L
LAC 18, 38 last registered 21 presentation format 118 language support 9 latitude 25 LLC data transfer performance (GSM) 45, 54 LLC window size 46 Location Area Code 18, 38 Location Area properties 27, 37, 64 Lock ARFCN GSM dialog 80 Lock Band GSM dialog 81 Lock Band WCDMA dialog 81 Lock Cell WCDMA dialog 80 Lock GSM band 82 Lock GSM cell 18, 39, 80, 82 Lock to RAT 82 GSM only setting in phone menu 80 Lock to RAT dialog 79 Lock UARFCN 18, 26, 27, 82 Lock WCDMA cell 18, 26, 27, 82
LZT 138 0240 R1A
149
locking functions comparison with TEMS Investigation 82 interplay between 82 Logfile menu 105 logfile recording 8, 105 automatic triggering of 105, 106 icon for 6 starting/stopping manual recording 74 where to save files 106 logfile replay 8, 74, 105 controlling 75 status icons for 6 logfile uploading via FTP 108 from phone file system 121 resumption after loss of FTP connection 3, 111 Logical Channel 36, 38, 39, 40, 41, 43, 48, 53, 56, 58, 64 longitude 25
M
MAIO 42 Map view 2, 6, 68 assigning geographical position to map image 72 color-coding of route markers 69 loading map image into 68 zoom level 69 MCC 18 last registered 21 Mean Throughput (PDP Context Request) 20, 132 Measure Mode Display dialog (GSM) 119 memory low memory condition 7, 74 memory sticks 9, 103, 105, 106, 108, 116 menus 7 default settings in 140 messages (displaying of) 118 Messages dialog 118 MM Cause 131 MM events 91 MM/GMM data view (no. 1.3) 21 MNC 18 last registered 21 Mobile Allocation Index Offset 42 Mobile Country Code 18
150
Index
Mobile Network Code 18 modulation coding scheme on downlink (EGPRS) 53 modulation coding scheme on uplink (EGPRS) 53 modulation method on downlink (GPRS/EGPRS) 44 modulation method on uplink (GPRS/EGPRS) 44 MS-TXPWR-MAX-CCH 37, 38
N
Neighbor Cell BCCH 37, 38, 64 neighbors (GSM) 17, 37, 38, 39, 64 Network Mode of Operation 46 NMO 46 No Service mode, time spent in 22 NSAPI 20
O
Operational Mode 73 overview of TEMS Pocket 5
P
Packet Dedicated Traffic Channel 41, 43, 48, 53, 66 Packet Final Block Timer 46 Packet TMSI 21 Packet Uplink Assignment Timer 46 parameter values 126 Pathloss (WCDMA) 16, 26, 56, 58, 61, 63 Pathloss Criterion (C1) 36, 57, 58, 64 PDCH, time using 22 PDP address (IPv4) 20 PDP Context data view (no. 1.2) 20 PDP Context Request parameters 131 PDTCH 41, 43, 47, 48, 53, 66 Peak Throughput (PDP Context Request) 20, 132 phone charger, choice of 123 pinpointing 2, 8, 68, 69 starting 70 stopping 71 Pocket menu 7, 77, 78 positioning by GPS 8 by pinpointing 8 Power Control Algorithm 30, 31 Power Control Step Size 30, 31 Power Display dialog (GSM) 119
LZT 138 0240 R1A
151
Precedence Class (PDP Context Request) 20, 132 PTMSI 21
Q
QAM, usage of in HSDPA 33 Quick guide 114
R
RAC 18 last registered 21 RACo 36, 57, 58, 64 Radio Link Timeout 41 Radio Network Controller ID 18 RAT, current 17 Receive Bit Error Rate 41, 49 Reliability Class (PDP Context Request) 20, 132 replaying logfiles 74 controlling the replay 75 status icons for 76 Reset All command (General settings menu) 120 Reset Control Settings command 84 resetting all General settings 120 resetting cell control settings 84 resumption of logfile upload 111 RLC data transfer performance (WCDMA) 31, 51 RLC/LLC BLER/retransmissions, graphic representation 138 RLC/MAC data transfer performance (GSM) 45, 54, 60, 66 presented in graph 60, 67 RLT 41 RNC ID 18 Roaming PLMN, time registered in 22 Routing Area Code 18 Routing Area Color 36, 57, 58, 64 Routing Area properties 27, 37, 64 Routing Area Update Failure Cause 133 RR Cause 133 RR events 94 RR Internal Cause 134 RRC events 95 RRC Failure Cause 134 RRC parameters 29 RRC Protocol Error Cause 135 RRC State 30, 31
152
Index
RSCP 16, 26, 27, 56, 58, 61, 63 graphic representation 138 presented in graph 57, 59, 61, 63 RSSI 51 graphic representation 138 RxLev 17, 36, 38, 39, 40, 43, 48, 53, 56, 57, 58, 64 Full/Sub values 119 graphic representation 138 presentation format 119 presented in graph 59, 65 RxQual 41, 49 Full/Sub values 119 graphic representation 139
S
Save Logfile To dialog 106 Scrambling Code 16, 17, 26, 27, 56, 58, 61, 63 SDCCH 41, 43, 48, 53, 66 serving cell (GSM) 17, 36, 38, 39, 40, 64 serving cell (WCDMA/GSM, always shown at bottom of display) 17 Serving Cell Barred 37, 38 Serving Cell BCCH 43, 48, 53 Serving Grant Index 34 Session events 97 SIB 3 28 SIB 5 28 SIR 30, 31, 51, 62 presented in graph 62 SIR Target 30, 31, 51, 62 presented in graph 62 SM Cause 135 SM events 92 snapshots of data views, taking 4, 11 Sony Ericsson C905/C905a 2 Sony Ericsson W995 1 Sony Ericsson W995 EDGE 2 Sony Ericsson W995a 1 speed 25 Stand-alone Dedicated Control Channel 41, 43, 48, 53, 66 Start Command Sequence command 77 Start FTP command 76 Start Logfile Recording command 74 Start Logfile Replay command 74
LZT 138 0240 R1A
153
Stop Command Sequence command 77 Stop FTP command 76 Stop Logfile Recording command 74 Stop Logfile Replay command 74 storage medium, choice of 9 Subchannel Number 42 support contact information 125 System Information Block 3 28 System Information Block 5 28
T
T3168 timer start value 46 T3192 timer start value 46 T3212 timer current value 21 T3212 timer max value 21 T3314 timer current value 46 T3314 timer start value 46 TCH 41, 43, 47, 48, 53, 66 time using 22 Temporary Logical Link Identifier 21 Temporary Mobile Subscriber Identity 21 TEMS Automatic 99, 102, 105 TEMS Investigation 8, 74, 75, 82, 99, 105 TEMS Pocket product package 113 TEMS Pocket version 113 TEMS Presentation 8, 74, 99 throughput (GSM) 45, 54, 60, 66 presented in graph 60, 67 throughput (WCDMA) 31, 35, 51, 52, 60 presented in graph 60 Time Log data view (no. 1.4) 22 actions in 22 Timeslot Number 41, 48 timeslots used by GPRS 43, 53, 66 Timing Advance 41, 49 TLLI 21 TMSI 21 Tools menu 113 Traffic Channel 41, 43, 48, 53, 66 time using 22 Traffic Channel Type 43, 48, 66 transport block size on E-DCH (HSUPA) 34
154
Index
transport channels configuration of 30 data transfer performance (WCDMA) 31, 52, 60 presented in graph 60 direction 30 downlink BLER target 30 identity 30 maximum bit rate on 30 type 30 TX Power graphic representation 139 TxPower 30, 31, 41, 48, 51, 62
U
UARFCN 16, 17, 26, 27, 51, 56, 58, 61, 63 UE Transmit Power 30, 31, 41, 48, 51, 62 Upload Logfile dialog 108 UTRA Carrier RSSI 17 presented in graph 61
V
Video Settings dialog (command sequence) 112 Voice Codec GSM dialog 82 voice codecs 42 setting preferred in GSM 82 Voice Settings dialog (command sequence) 112
W
W/G Cells data view (no. 1.1, in text format) 16 actions in 18 W/G Cells data view (no. 5.2, with graph) 58 W/G Data data view (no. 5.3) 60 W/G Serving RSSI data view (no. 5.1) 56 WAP browser data views 50 GPRS view 53 visibility of 117 WCDMA view 51 WAP Data View dialog 117 WCDMA Cell Id data view (no. 2.2) 27 WCDMA Cell Type 16, 26, 27, 56, 58, 61, 63 WCDMA Cells data view (no 5.6, with graph) 63 WCDMA Cells data view (no. 2.1, in text format) 26 actions in 26, 27 WCDMA Channel data view (no. 2.4) 30
LZT 138 0240 R1A
155
WCDMA Data data view (no. 2.3) actions in 32 WCDMA Data data view (no. 2.5) 31 WCDMA Serv. Cell data view (no. 2.3) 28 WCDMA Serving data view (no. 5.4) 61 WCDMA SIR data view (no. 5.5) 62 what was new in TEMS Pocket 7.0 2 whats new in TEMS Pocket 7.2 1
156
TEMS Optimization Solutions the number one choice for operators worldwide. For every stage of a wireless networks life cycle and supporting all major technologies, the TEMS portfolio helps operators maximize their Quality of Service and get the most out of their network investment. The experience and technological leadership of TEMS gives network operators the strong partnership they need and a commitment to quality, accuracy, and success. TEMS Optimization Solutions Making Wireless Better.

Pocket 7.3 For W995 - User - S Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pocket 7.3 For W995 - User - S Manual

Uploaded by

Copyright:

Available Formats

TEMS Pocket 7.

2 for Sony Ericsson W995 and W995a

2. Overview of TEMS Pocket

LZT 138 0240 R1A

3. Data Views: General

4. Data Views in Text Format

5. Data Views with Graphs

6. The Map View

7. TEMS Pocket Functions in the Activity Menu

LZT 138 0240 R1A

8. The Pocket Menu

LZT 138 0240 R1A

11. Support Contact Information Appendix A. Parameter Values

Appendix B. Graphic Representation of Parameter Values

Appendix C. Default Settings in TEMS Pocket Menus

LZT 138 0240 R1A

Whats New in TEMS Pocket 7.2

New UMTS Phones: Sony Ericsson W995/W995a

8.1 megapixel camera Integrated GPS

LZT 138 0240 R1A

New GSM Phone: Sony Ericsson W995 EDGE

HSPA Data View

What Was New in TEMS Pocket 7.0

Map View and Pinpointing

Data Views with Graphs

Smarter Logfile Upload

LZT 138 0240 R1A

dedicated/connected mode. The buffer is cleared when the phone is restarted.

Snapshots of Data Views

Importing and Exporting TEMS Pocket Settings

Chapter 2. Overview of TEMS Pocket

Overview of TEMS Pocket

LZT 138 0240 R1A

Data Views with Graphs

Chapter 2. Overview of TEMS Pocket

LZT 138 0240 R1A

Cell Control Functions

Chapter 2. Overview of TEMS Pocket

Storage Medium: Phone Memory vs. Memory Stick

LZT 138 0240 R1A

Data Views: General

General Data View Properties

The Built-in Help Function

Chapter 3. Data Views: General

The Capture Function

Other Data View Actions

LZT 138 0240 R1A

Specifics on data view actions are found in the subsequent sections.

Survey of Data Views

Chapter 3. Data Views: General

View Name GPS

Map WCDMA Cells

WCDMA Serv. Cell WCDMA Channel

WCDMA WAP browser view

LZT 138 0240 R1A

View Name GSM Cells

GSM Serving Cell

GSM C/I Info

Chapter 3. Data Views: General

No. 5.1 5.2

5.4 5.5 5.6 5.7 5.8

LZT 138 0240 R1A