TEMS Pocket 6.4 for Nokia N96

8/12/2019 TEMS Pocket 6.4 for Nokia N96

1/126

TEMSPocket 6.4

for Nokia N96

Users Manual


2/126

This manual is provided by Ericsson 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 Ericsson 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, Ericsson AB.

TEMS is a trademark owned by Telefonaktiebolaget L M Ericsson.

All other trademarks are the property of their respective holders.

Ericsson AB 2008. All rights reserved.

Publication number: LZT 108 9928 R1A


3/126

Contents

LZT 108 9928 R1A i

Contents

1. Introduction 1

1.1. Whats New in TEMS Pocket 6.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2. What Was New in TEMS Pocket 6.1. . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Overview of TEMS Pocket 3

2.1. The TEMS Pocket Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.1.1. Notes on the Nokia Test Mobile (NTM) Interface. . . . . . . . . . 4

2.2. Switching between TEMS Pocket and Other Phone Applications. . . 4

2.3. TEMS Pocket Data Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.4. TEMS Pocket Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.5. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.6. Cell Control Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.7. Command Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.8. GPS Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.9. Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.10. Storage Medium: Phone Memory vs. Internal Mass Memory . . . . . 7

2.11. Exiting the TEMS Pocket Application . . . . . . . . . . . . . . . . . . . . . . . 7

3. Data Views 8

3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.1.1. General Data View Properties . . . . . . . . . . . . . . . . . . . . . . . . 83.1.2. The Built-in Help Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.1.3. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2. Survey of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.3. W/G Cells (View No. 1.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.4. PDP Context (View No. 1.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.5. MM/GMM (View No. 1.3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.6. GPS (View No. 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.7. FTP Data (View No. 1.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19


4/126

TEMS Pocket 6.4 for Nokia N96 Users Manual

ii

3.8. Progress (View No. 1.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.9. WCDMA Cells (View No. 2.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.9.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.10. WCDMA Data (View No. 2.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.10.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.11. W/HSDPA (View No. 2.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.12. WCDMA Codec (View No. 2.4). . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.13. GSM Cells (View No. 3.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.13.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.14. GSM Cell Id (View No. 3.2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


3.15. GSM BA List (View No. 3.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


3.16. GSM Serv Cell (View No. 4.1) . . . . . . . . . . . . . . . . . . . . . . . . 34

3.17. GPRS Data (View No. 4.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


3.18. GSM AMR (View No. 4.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.19. Graph Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4. TEMS Pocket Functions in the Data View Menu 44

4.1. Show Open Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.2. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.3. Pocket Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.4. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.5. Start/Stop Command Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.5.1. Icon Used for Command Sequence. . . . . . . . . . . . . . . . . . . 45

4.6. Start/Stop Logfile Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.6.1. Filemarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.6.2. Icon Used for Logfile Recording. . . . . . . . . . . . . . . . . . . . . . 46

4.7. Start FTP Put, Start FTP Get, Cancel FTP. . . . . . . . . . . . . . . . . . . 46

4.8. About. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.9. Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5. The Pocket Menu 48

5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.2. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2.1. Lock to RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2.2. Lock Cell WCDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


5/126

Contents

LZT 108 9928 R1A iii

5.2.3. Lock ARFCN GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.2.4. Lock Band GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.2.5. Interplay between Locking Functions. . . . . . . . . . . . . . . . . . 51

5.2.6. Comparison with Locking Functions in TEMS Investigation. 52

5.2.7. Ignore Cell Barred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.3. Command Sequence Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.3.1. Defining Command Sequences . . . . . . . . . . . . . . . . . . . . . . 53

5.3.1.1. Voice Call Action Settings . . . . . . . . . . . . . . . . . . . . . 55

5.3.1.2. FTP Get Action Settings . . . . . . . . . . . . . . . . . . . . . . 55

5.3.1.3. FTP Put Action Settings . . . . . . . . . . . . . . . . . . . . . . 55

5.3.1.4. Ping Action Settings . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.3.1.5. Upload Logfile Action Settings . . . . . . . . . . . . . . . . . 56

5.3.1.6. Idle Mode Action Settings . . . . . . . . . . . . . . . . . . . . . 57

5.3.1.7. The Assembled Command Sequence. . . . . . . . . . . . 575.3.2. Deleting Command Sequences and Command Sequence

Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.4. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.4.1. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.4.1.1. Viewing the Event Log. . . . . . . . . . . . . . . . . . . . . . . . 58

5.4.1.2. Clearing the Event Log . . . . . . . . . . . . . . . . . . . . . . . 59

5.4.1.3. Enabling and Disabling Event Logging . . . . . . . . . . . 59

5.4.1.4. Shortcuts to Event Settings and Event Counters . . . 60

5.4.2. Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5.4.2.1. Viewing Event Settings . . . . . . . . . . . . . . . . . . . . . . . 60

5.4.2.2. Modifying Event Settings. . . . . . . . . . . . . . . . . . . . . . 60

5.4.3. Event Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.4.3.1. Viewing Event Counters . . . . . . . . . . . . . . . . . . . . . . 61

5.4.3.2. Resetting Event Counters . . . . . . . . . . . . . . . . . . . . . 62

5.4.4. Event Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.4.5. List of Logged Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.4.5.1. CC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.4.5.2. GMM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.4.5.3. IRAT Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.4.5.4. MM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.4.5.5. RR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.4.5.6. RRC Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.4.5.7. Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.4.5.8. SM Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.5. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.6. GPS Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.6.1. GPS Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.6.2. GPS Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


6/126


iv

5.7. FTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.7.1. FTP Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.7.2. FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.8. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.8.1. Autostart Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.8.2. Compress Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.8.3. Replay Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.8.3.1. Icons Used for Logfile Replay . . . . . . . . . . . . . . . . . . 79

5.8.3.2. Availability of Logfile Replay Function. . . . . . . . . . . . 79

5.8.4. Save Logfile To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5.8.5. Upload Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.8.5.1. Manual Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5.8.5.2. Scheduled Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5.8.6. Upload FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.9. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

5.9.1. Cell Id Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.9.2. Power Display (GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.9.3. Measure Mode Display (GSM). . . . . . . . . . . . . . . . . . . . . . . 84

5.9.4. Data View Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5.9.5. Enable End App Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5.9.6. Billable Event Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5.9.7. Display Privacy Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.9.8. Reset Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

6. Battery Charging Considerations 87

7. Controlling the Display Backlight 88

8. Notes on Nokia N96 Packet-switched Behavior 89

8.1. GMM Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

9. Support Contact Information 90

Appendix A. Parameter Values 91

A.1. Activate PDP Context Failure Cause . . . . . . . . . . . . . . . . . . . . . . . 91

A.2. CCCH Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

A.3. Channel Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92


7/126

Contents

LZT 108 9928 R1A v

A.4. Deactivate PDP Context Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

A.5. CC Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

A.6. GMM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

A.7. PDP Context Request Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 94A.7.1. Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

A.7.2. Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

A.7.3. Peak Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

A.7.4. Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

A.7.5. Mean Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

A.8. RR Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

A.9. MM Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

A.10. Routing Area Update Failure Cause. . . . . . . . . . . . . . . . . . . . . . . 97

A.11. RR Internal Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

A.12. RRC Failure Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

A.13. RRC Protocol Error Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

A.14. SM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Appendix B. Graphic Representation of ParameterValues 101

B.1. C/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

B.2. Ec/No . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101B.3. FER, RLC/LLC Decode Errors/Retransmissions . . . . . . . . . . . . . 102

B.4. RxLev, RSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

B.5. RxQual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

B.6. TxPower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Appendix C. Default Settings in TEMS PocketMenus 104

C.1. Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104C.2. Pocket Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

C.2.1. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

C.2.2. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

C.2.3. Data Views Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

C.2.4. GPS Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

C.2.5. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

C.2.6. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Index 107


8/126


vi


9/126

Chapter 1. Introduction

LZT 108 9928 R1A 1

1. Introduction

Welcome to TEMS Pocket.

TEMS Pocket is an advanced cellular network diagnostics tool built into a

Nokia or Sony Ericsson 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 6.4 as implemented in the Nokia N96

phone. If you are familiar with Sony Ericsson TEMS Pocket phones, please

note that the Nokia N96 TEMS Pocket functionality diverges in certain

respects from what you are accustomed to.

1.1. Whats New in TEMS Pocket 6.4

This section tells what is new in TEMS Pocket 6.4 for Nokia N96 compared to

TEMS Pocket 6.1 for Nokia N95/6121. (TEMS Pocket 6.3 was a SonyEricsson based release.)

Ping testing command added to command sequence tool

WCDMA Voice Codec data view

Optional automated logfile upload

Logfile upload via command sequence

Optional compression of logfiles before upload to FTP server, cutting

transfer times

1.2. What Was New in TEMS Pocket 6.1

This section tells what was new in TEMS Pocket 6.1 for Nokia N95/6121

compared to TEMS Pocket 5.3 for Nokia N75/N80. (TEMS Pocket 6.0 was a

Sony Ericsson based release.)

Command sequence for automation of voice calls and FTP sessions

Support for phone-internal GPS


10/126


2

Graph views

HSDPA capability in phone and HSDPA data view

FTP data view

GSM AMR data view

GSM BA list data view


11/126

Chapter 2. Overview of TEMS Pocket

LZT 108 9928 R1A 3

2. Overview of TEMS Pocket

2.1. The TEMS Pocket Application

The TEMS Pocket application in the Nokia N96 is run as a Symbian Series 60

application. It is not part of the phone firmware as in Sony Ericsson phones.

This means that other applications in the phone can run concurrently with

TEMS Pocket.When you turn on the Nokia N96, the TEMS Pocket application starts up

automatically. A privacy notice appears, headed For your information. Press

Yes. It is possible to suppress this notice; see section 5.9.7.

Once the application has loaded, a data view named W/G Cells appears

(see section 2.3):

On later occasions TEMS Pocket will show the last data view that was visited

the last time TEMS Pocket was run.

It is also possible to start the application manually (necessary if you have

previously turned TEMS Pocket off see section 2.11). This is done by

entering the main phone menu and navigating to Applications TEMS

Pocket:


12/126


4

2.1.1. Notes on the Nokia Test Mobile (NTM) Interface

If TEMS Pocket is started on a phone that does not have a Nokia Test Mobile

(NTM) interface, a dialog is shown notifying the user to that effect.

This dialog may also appear if for some reason the TEMS Pocket application

loses contact with the NTM interface. If you know that the phone is equipped

with the NTM interface, restart the phone to allow TEMS Pocket and the NTM

interface to resynchronize. If the phone does not have the NTM interface but

has been purchased with it, please contact TEMS Support.

2.2. Switching between TEMS Pocket and OtherPhone Applications

While the TEMS Pocket application is in the foreground, the following holds:

If you press the (Menu) button briefly, the phones main menu appears.

If you long-press the button, a task list appears containing all the

applications that are currently running.

Certain buttons used as shortcuts to other applications, such as the

camera capture button and the Multimedia button, are disabled whilethe TEMS Pocket application is in the foreground. To be able to use

these buttons, you must first switch the phone to the Standby

application. Long-press and select Standby in the task list.

If you launch the WAP browser, you must access the task list in order

to return the TEMS Pocket application to the foreground. (Unlike the

Sony Ericsson based TEMS Pocket editions, the Nokia N96 edition

does not have any special WAP browser data views.) Long-press to

access the task list, then select TEMS Pocket.


13/126


LZT 108 9928 R1A 5

If TEMS Pocket has been put in operational mode Background (see

section 4.2), the only way to bring the TEMS Pocket application back

to the foreground is through the task list. Long-press to access the

task list, then select TEMS Pocket.

2.3. TEMS Pocket Data Views

The data views exhibit most of the data displayed by TEMS Pocket. The

exception is events, which are found in the event log; see section 4.4.

Data views are divided into categories. Each data view is numbered

according to the format x.y, where x is the category and y is the position

of the data view within that category. You browse the categories by pressing

the navigation key left and right, and the data views within a category bypressing 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.

Besides these predefined text-format data views, it is possible to set up graph

views displaying user-selected data: see section 3.19.

Whatever data view is being 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.

The top section of the display also shows:

a symbol indicating that a logfile is being recorded (see section 4.6)

a symbol indicating that a logfile is being replayed, and the status of the

replay (see section 5.8.3.1)

an icon for the latest TEMS Pocket event that occurred (see section 5.4.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 mode (see section 4.2). By default TEMS Pocket is in activemode, and its data views are visible.

The data views are exhaustively described in chapter 3.

2.4. TEMS Pocket Menus

Pressing the Menu button when a TEMS Pocket data view is displayed brings

up a menu with TEMS Pocket commands:


14/126


6

Most of the commands in this menu are found only here. The menu is gone

through in chapter 4.

From the data view menu you can also access the Pocket menu, which is thechief means of configuring TEMS Pocket: see chapter 5.

2.5. Events

Eventsare 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 logis inspected and managed from the Pocket menu. See section

5.4.1. A shortcut to the event log is found in the data view menu.

2.6. Cell Control Functions

TEMS Pocket has a number of cell controlfunctions for controlling the

phones behavior in the cellular network. These include locking the phone to a

RAT, band, cell, or channel. See section 5.2for full details.

2.7. Command Sequences

TEMS Pocket offers the use of command sequencesfor automated execution

of (among other things) voice calls and FTP data sessions. Command

sequences are dealt with in section 5.3.


15/126


LZT 108 9928 R1A 7

2.8. GPS Positioning

TEMS Pocket supportspositioningof 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 5.6.

2.9. Logfile Recording

You can record data collected by TEMS Pocket in logfilesand replay these

files in TEMS Pocket itself or in TEMS Investigation or TEMS Presentation.

See sections 4.6and 5.8.

2.10. Storage Medium: Phone Memory vs. InternalMass Memory

In general it is recommendable to use the phones (large) internal mass

memoryrather than the (much smaller)phone memoryas storage medium

for logfiles, FTP downloads, etc.

It is also possible to use a memory stick for file storage (microSD up to 8 GB

supported). However, no memory stick is delivered with the Nokia N96

phone.

2.11. Exiting the TEMS Pocket Application

You turn the TEMS Pocket application off by entering the data view menu and

selecting Exit: see section 4.9.

Alternatively, you can press the End button (labeled with broken red line)

when in idle mode to exit TEMS Pocket. This function can be disabled; see

section 5.9.5.


16/126


8

3. Data Views

3.1. General

3.1.1. General Data View Properties

This description applies to the text-format data views. Regarding graph views,

see section 3.19, page 42.

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.

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

sections 3.33.17. The rules for the graphic presentation are found in

appendix B, page 101.

In the case of frequency hopping, the hopping list is shown one channel at a

time, a new channel appearing every second.

3.1.2. The Built-in Help Function

If you press More 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.


17/126

Chapter 3. Data Views

LZT 108 9928 R1A 9

To turn off the help function, press the Cbutton. Alternatively, press More

and choose Toggle help again.

3.1.3. 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 More button and

choosing Data view actions. A submenu appears listing the available actions.

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


18/126


10

3.2. Survey of Data Views

No. View Name Description Page

1.1 W/G Cells Combines WCDMA Cells(2.1) and

GSM Cells(3.1) views into a dual

mode view.

13

1.2 PDP Context Displays PDP addresses and PDP

context settings for each address.

16

1.3 MM/GMM Displays identities common to

WCDMA and GSM, including TMSI,

P-TMSI, and CGI of last registerednetwork.

17

1.4 GPS Displays GPS data: latitude, longitude,

altitude, speed, number of satellites,

and GPS time.

18

1.5 FTP Data Displays information on the current

FTP session, such as FTP server

address, throughput, and transferred

byte count.

19

1.6 Progress Displays the progress of a command

sequence and/or logfile upload while

they are executing.

21

2.1 WCDMA Cells Displays UARFCN, cell status,

scrambling code, RSCP, Ec/No, and

path loss for each cell in active set and

monitored/detected neighbor sets.

23

2.2 WCDMA Data Presents SIR target, power control

information, RRC state, and

information on uplink and downlink

RLC and transport channel

performance.

24


19/126


LZT 108 9928 R1A 11

2.3 W/HSDPA Presents partly the same generic

WCDMA parameters as the WCDMADataview (2.2), partly HSDPA-specific

data on modulation method usage,

number of HARQ processes, CQI,

required and actual transport block

sizes, retransmissions.

26

2.4 WCDMA Codec Presents partly the same generic

WCDMA parameters as the WCDMA

Dataview (2.2), partly data on

WCDMA speech codec utilization.

28

3.1 GSM Cells 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.

29

3.2 GSM Cell Id Displays ARFCN, LAC, CI, and RxLev

for the serving cell and each neighbor.

Also presents system information datafor cell access, selection, and location.

31

3.3 GSM BA List Displays the GSM BA neighbor list as

received from the network and shows

which BCCH ARFCN the list was

received from.

33

4.1 GSM Serv Cell Presents system information data on

serving cell depending on mode (idle/

connected). Note:TMSI, P-TMSI andTLLI appear in the MM/GMMdata view

(1.3).

34

4.2 GPRS Data Displays traffic channel ARFCN,

timeslots and coding schemes used,

and LLC and RLC performance on

uplink and downlink.

37



20/126


12

4.3 GSM AMR Displays GSM logical channel

information, AMR codec selected onuplink and downlink, and statistics on

AMR codec utilization.

40

5.x Graph views These views are user-configured. Each

graph view tracks one user-selected

network parameter over time.

42



21/126


LZT 108 9928 R1A 13

3.3. W/G Cells (View No. 1.1)

Screenshot

Key (not shown in this

format in the phone

display)

Lines 14show WCDMA cells and so are primarily

used in WCDMA mode. If 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

5.2.1), 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 rest of line): Inter-RAT,

WCDMA neighbor measured in GSM mode

UARFC:UARFCN, UMTS Absolute Radio

Frequency Channel Number

SC:Scrambling Code

RSCP:Received Signal Code Power (dBm),

numeric/graphic

Ec/No:Ec/No (dB), numeric/graphic

PL:Pathloss (dB); this measurement appears only

when ordered by the network

Lines 58show GSM cells and so are primarily

used in GSM mode. If GSM neighbors are

measured in WCDMA mode, these neighbors also

appear here. Note that if you have locked the

phone to WCDMA (Lock to RAT function, section

5.2.1), no GSM neighbors will ever be measured.

Line 5:GSM serving cell

Lines 68:Three strongest GSM neighbors

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


22/126


14

Screenshot

Key (not shown in thisformat in the phone

display)

Lines 68 (continued)

ARFC:ARFCN, Absolute Radio Frequency

Channel Number

BS:BSIC, Base Station Identity Code

RxLev:Received Signal Strength (unit user-

configurable: see section 5.9.2), numeric/graphic

Lines 910are 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 information 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 BSICRSS:Received signal strength, equal to RSCP for

WCDMA and RxLev for GSM; numeric/graphic

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 consists

of RNC + CI)

CI:Serving cell Cell Identity


23/126


LZT 108 9928 R1A 15


You can lock on a cell that is listed in the data

view.

Choose the cell to lock on by moving the redframe, using the navigation key. When you

have navigated to the desired item, press the

navigation key.

To unlock, enter the Data view actions menu

again and give the appropriate Unlock

command.


24/126


16

3.4. PDP Context (View No. 1.2)

There are no actions associated with this data view.

Screenshot

Key

Lines 16show 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 TS 24.008, sec. 10.5.6.4.

NSAPI:Network Service Access Point Identifier.

See 3GPP TS 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 appendixA.7.)

APN:Access Point Name (shown as scrolling text)

Lines 78are the same as the two bottom lines in

the W/G Cells view: see section 3.3.


25/126


LZT 108 9928 R1A 17

3.5. MM/GMM (View No. 1.3)


Screenshot

Key

Lines 14show 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}

T3212M: T3212, max time between location

updates {Off, 0 ... 1530 minutes}

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

RLAC:Registered LAC

RRAC:Registered RAC




26/126


18

3.6. GPS (View No. 1.4)


Screenshot

Lines 16show GPS data.

Latitude:Latitude in degrees, minutes, anddecimal minutes.

Longitude:Longitude in degrees, minutes, and

decimal minutes.

Altitude:Height above sea level in meters.

Speed:Speed in km/h.

No. of Sat:The number of satellites seen by the

GPS device. Always valid as long as a GPS device

is in use.

GPS Time:Time reported by the GPS device.




27/126


LZT 108 9928 R1A 19

3.7. FTP Data (View No. 1.5)

Screenshot

Key

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

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 (uplink)

CThpUL:Current uplink application-level FTP

throughput in bytes/s (based on the latest report

from the phone).

MThpUL:Mean uplink application-level FTPthroughput in bytes/s (calculated over the whole of

the file currently being transferred).

TotDataUL:Totalbytes 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.

Line 5 (downlink)

CThpDL:Current downlink application-level FTP

throughput in bytes/s (based on the latest report

from the phone).

MThpDL:Mean downlink application-level FTP

throughput in bytes/s (calculated over the whole of

the file currently being transferred).


28/126


20

Upon completion of each FTP file transfer, an FTP Transfer End event (see

section 5.4.5.7) is generated providing a summary of the file transfer and its

performance.


Screenshot

Key

Line 5 (downlink; continued from previous page)

TotDataDL:Totalbytes transferred on downlink

over FTP at the application level (B = bytes, K =

kilobytes, M = megabytes). This counter is reset atthe end of each file transfer.




29/126


LZT 108 9928 R1A 21

3.8. Progress (View No. 1.6)

Screenshot

Key

Lines 15 show the progress of a command

sequence that is being executed. Regarding

command sequence setup, see section 5.3.1.

Line 1

ExecNo:The value imeans that the command

sequence is being executed for the ith time (out of

the total TotExec: see below).

TotExec:The total number of times the command

sequence will be executed (Repeat no. of times +

1).

Line 2

ActNo:The index of the action being executed in

the list of actions in the command sequence.

TotAct:The total number of actions in the

command sequence.

SeqName:Name of the command sequence.

Line 3

ActName:Name of the action being executed.

Lines 45

SeqInfo: Here is shown service-specific

information for Ping:

Number of pings sent/Total number of pings to

send

Ping status (Received, Not connected, etc.)

Ping round trip time


30/126


22


Screenshot

Key

Lines 67 show the progress of an ongoing logfile

upload. How to set up logfile uploading is the

subject of section 5.8.5.

Line 6

Interval:The upload time interval set as described

in 5.8.5.2.

Line 7

UplNo:The value imeans that the ith logfile (out of

TotUpl) is being uploaded.

TotUpl:Total number of logfiles that will be

uploaded on this occasion.

Type:The type of upload currently selected (see

section 5.8.5).




31/126


LZT 108 9928 R1A 23

3.9. WCDMA Cells (View No. 2.1)


You can lock on a WCDMA 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

3.3.1.

Screenshot

Key

Up to six cells from the WCDMA active set can be

shown.

Lines 16

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/No (dB), numeric/graphic

PL:Pathloss (dB); this measurement appears only

when ordered by the network




32/126


24

3.10. WCDMA Data (View No. 2.2)

Screenshot

Key

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

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}

Lines 36report the current performance of and

some statistics on the WCDMA data transfer. All

values are combined values computed over all

used channels.

Line 3:RLC protocol level, downlink

Line 4:Transport channels, downlink

Line 5:RLC protocol level, uplink

Line 6:Transport channels, uplink

Rate: Instantaneous data transfer rate in bytes/s.

For RLC this bit rate includes AM channels only

(not TM and UM).

Err: Percentage of data blocks erroneouslydecoded (on downlink), numeric/graphic

Retr: Percentage of data blocks retransmitted (on

uplink; RLC only), numeric/graphic

TotData:Totalbytes transferred (B = bytes, K =

kilobytes, M = megabytes). You can reset these

counters as explained in section 3.10.1below.


33/126


34/126


26

3.11. W/HSDPA (View No. 2.3)

Screenshot

Key

Line 1


SIR_TG:SIR Target (dB)


graphic

Line 2

PCA:Power Control Algorithm, see 3GPP TS

25.331

PCSS:Power Control Step Size, see 3GPP TS25.331


CELL_FACH, CELL_PCH, URA_PCH, IDLE,

PASSIVE}

Line 3

General note: All data presented here applies to

the phones latest reporting period.

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 HS-

DSCH.


35/126


LZT 108 9928 R1A 27


Screenshot

Key

Lines 45, general note:

All data presented here applies to the phones

latest reporting period.

Line 4 (Min)

CQI:Minimum value of CQI (Channel Quality

Indicator). CQI values are defined in 3GPP TS

25.214, section 6A.2.

ReqSize:Minimum requested transport block size

in bits (corresponding to minimum CQI).

ActSize:Minimum actual transport block size in

bits.

Line 5 (Max; analogous to Line 4)

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.

Line 6

All of these parameters apply to the same short

and recent interval of time (though not one identical

with the phone reporting period).

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 theHS-DSCH.




36/126


28

3.12. WCDMA Codec (View No. 2.4)


Screenshot

Key

Line 1



graphic

Line 2

PCA:Power Control Algorithm, see 3GPP 25.331

PCSS:Power Control Step Size, see 3GPP 25.331


CELL_FACH, CELL_PCH, URA_PCH, IDLE,PASSIVE}

Lines 37

In these lines are shown all speech codecs in the

WCDMA 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




37/126


LZT 108 9928 R1A 29

3.13. GSM Cells (View No. 3.1)

Screenshot

Key

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)



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

C32: GPRS Cell Ranking Criterion C32


38/126


30


You can lock on a GSM cell that is listed in the view. The procedures for


3.3.1.

Screenshot

Key

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:

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}

B:BS-PA-MFRMS, number of multiframes

between paging subgroups {2 ... 9}

CB:Serving cell barred {B: Barred, : Not Barred}




39/126


LZT 108 9928 R1A 31

3.14. GSM Cell Id (View No. 3.2)

Screenshot

Key

Line 1 (GSM serving cell)


P: PBCCH, p: Hopping PBCCH

S: SDCCH, s: Hopping SDCCH



BCCH:Serving Cell BCCH ARFCN

LAC:Serving Cell Location Area Code

CI:Serving Cell IdentityRxLev:Serving Cell RxLev (unit user-


Lines 27 (GSM neighbors)

NC1 ... NC6:Neighbor Cell BCCH ARFCN of six

strongest neighbors

LAC:Neighbor Cell Location Area Code

CI:Neighbor Cell Identity

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


CB:Serving cell barred {B: Barred, : Not Barred}

SB:Serving cell band




40/126


32


You can lock on a GSM cell that is listed in the view. The procedures for


3.3.1.


41/126


LZT 108 9928 R1A 33

3.15. GSM BA List (View No. 3.3)


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

Screenshot

Key

Line 1 (serving cell)


P: PBCCH

p: Hopping PBCCH

S: SDCCH

s: Hopping SDCCH

T: TCH

t: Hopping TCH

D: PDTCH

d: Hopping PDTCH


BSIC:Base Station Identity Code (BSIC)



Lines 29 (neighbor list = BA list)

NC1 ... NC32:BCCH ARFCNs of all neighbors of

the serving cell (up to 32 cells).


42/126


34

3.16. GSM Serv Cell (View No. 4.1)

Screenshot

idle mode

Screenshot

dedicated mode

Key

Line 1

L:Logical Channel: B for BCCH

BC:BCCH ARFCN

BS:Base Station Identity Code, BSIC

RxLv:Received Signal Strength (unit user-


DSC:Downlink Signalling Counter, current value

(idle mode only)

DSM:Downlink Signalling Counter, max 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.

CN:CCCH configuration, number of BCCH/CCCH

timeslots {NC, Comb, NC2, NC3, NC4}; see

appendixA.2, page 91

BP:BS-PA-MFRMS, number of multiframes


BA:BS-AG-BLKS-RES, number of CCCH blocks

reserved for AGCH {0 ... 7}


43/126


LZT 108 9928 R1A 35

Screenshot

idle mode

Screenshot

dedicated mode

Key

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 (PDTCHARFCN). Hopping channels are shown one at a

time; see section 3.1.1.

TS:Timeslot Number

TA:Timing Advance

TX:UE Transmit Power (dBm), numeric/graphic

RLTC:Radio Link Timeout (Current)

Line 4 (dedicated mode)

C/I:Carrier-to-interference ratio in dB for the traffic

channel currently indicated by TCon 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 definedin 3GPP TS 45.008), numeric/graphic

FER:Frame Erasure Rate (FER) in %. 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


44/126


36


Screenshot

idle mode

Screenshot

dedicated mode

Key

Line 5 (dedicated mode only, except ChTyp)

ChTyp:Channel type, one of {BCCH, PBCCH,

PDTCH, SDCCH, TCH/F, TCH/H}; see appendix

A.3, page 92

ChM:Channel mode, one of {FR, EFR, HR, AFR,

AHR; D24, D48, D96, D144}:

FR = Speech, Full Rate

EFR = Speech, Enhanced Full Rate

HR = Speech, Half Rate

AFR = Speech, AMR Full Rate

AHR = Speech, 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}




45/126


LZT 108 9928 R1A 37

3.17. GPRS Data (View No. 4.2)

Screenshot

Key

Line 1






Line 2

T:Traffic Channel Type:

P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH





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

Example: means that TS 4, 5, and 7are being used on the downlink and TS 6 is used

on both uplink and downlink.


46/126


38

Screenshot

Key

Line 3

CSd: GPRS: Channel coding scheme on downlink

{CS1 ... CS4}; EGPRS: 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}; EGPRS: Modulation coding scheme

on uplink {MCS1 ... MCS9}

MSu:Modulation method on uplink (G = GMSK,

8 = 8-PSK)

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 TS 44.060, sec. 9.2.3.1


47/126


LZT 108 9928 R1A 39



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

3.10).

Screenshot

Key

Lines 58report the current performance of and

some statistics on the GPRS data transfer.

Line 5:LLC protocol level, downlink

Line 6:RLC/MAC protocol level, downlink

Line 7:LLC protocol level, uplink

Line 8:RLC/MAC protocol level, uplink

Rate: Instantaneous data transfer rate in bytes/s

Err: Percentage of data blocks erroneously

decoded (on downlink), numeric/graphic

Retr: Percentage of data blocks retransmitted (onuplink), numeric/graphic

TotData:Totalnumber of bytes transferred (B =

bytes, K = kilobytes, M = megabytes). You can

reset these counters as explained in section 3.17.1

below.




48/126


40

3.18. GSM AMR (View No. 4.3)

Screenshot

Key

Line 1






Line 2

T:Traffic Channel type:

P: PBCCH, p: Hopping PBCCH S: SDCCH, s: Hopping SDCCH





Packet Dedicated Traffic Channel (PDTCH

ARFCN). Hopping channels are shown one at a

time; see section 3.1.1.

TS:Timeslot Number


graphic

Line 3

C/I:Carrier-to-interference ratio in dB for the traffic

channel currently indicated by TCon 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.


49/126


LZT 108 9928 R1A 41


Screenshot

Key

Line 3 (continued)

RQ:Receive Bit Error Rate (RxQual; scale defined

in 3GPP TS 05.08), numeric/graphic

FE:Frame Erasure Rate (FER) in percent,

numeric/graphic

DXD:DTX rate (%) on downlink

Lines 47

In these lines are shown all speech codecs in the

GSM 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




50/126


42

3.19. Graph Views

Graph views do not appear until you have configured them. You can

configure up to ten distinct graph views. Each graph view tracks one network

measurement over time.

Proceed as follows to set up graph views:

While in a data view, press More and select

Configure graph views.

A list of graph views (as yet undefined)

appears. At the outset they are simply

numbered from 0 to 9 in the user interface; you

get the opportunity to name the views while

defining them (see below). Select a view to set

it up.

Enter a name for the graph view. It will replace

the number in the graph view listing and

appear as heading in the view itself (see the

examples at the end of this section).


51/126


LZT 108 9928 R1A 43

Below are two examples of graph views.

Select what data to graph. Check the desired

item.

Select a color to use for drawing.


52/126


44

4. TEMS Pocket Functions in the

Data View Menu

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

button while in a Pocket data view.

Note that many of the functions at the top level in this menu are found only

here and not in the submenus of the Pocket menu.

4.1. Show Open Apps.

This is a Symbian menu item that is not TEMS Pocket related.

4.2. Operational Mode Active:The TEMS Pocket application is active and stays in the

foreground. This is the default setting.

Background:If you select this, the TEMS Pocket application will remain

active but disappear from view. How to make TEMS Pocket visible again

and return the application to Active mode is explained in section 2.2.


53/126

Chapter 4. TEMS Pocket Functions in the Data View Menu

LZT 108 9928 R1A 45

4.3. Pocket Menu

This is a shortcut to the main Pocket menu; see chapter 5.

4.4. Event Log

This is a shortcut to the event log; see section 5.4.1.

4.5. Start/Stop Command Sequence

These commands are used to start and stop a command sequence. How to

set up command sequences is explained in section 5.3.

On selecting the Start command, you are prompted to select a command

sequence among those currently defined. Unless interrupted, the sequence

will be executed in its entirety the number of times specified in its properties

(see section 5.3.1).

During logfile replay these commands are not available.

4.5.1. Icon Used for Command Sequence

While a command sequence is being executed, this icon is shown onthe status bar at the top of the display.

4.6. Start/Stop Logfile Record

These commands are used for recording TEMS Pocket logfiles.

Select Start Logfile Record to begin recording a logfile.

Select Stop Logfile Record to conclude the recording and close the logfile.

If the memory on the storage medium used for logfiles is running low, or if

some error occurs, the recording is stopped automatically. You are then

notified by a message in the display.

Refer to section 5.8for all remaining details on logfile recording and handling.

During logfile replay these commands are not available.


54/126


46

4.6.1. Filemarks

The Set filemark 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 wheresomething 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 108 characters.

This command is available only while logfile recording is in progress.

4.6.2. Icon Used for Logfile Recording

While a logfile is being recorded, this icon is shown on the status bar at

the top of the display.

4.7. Start FTP Put, Start FTP Get, Cancel FTP

These commands are used to start and stop FTP sessions, including

uploading of TEMS Pocket logfiles. On selecting this command you are

prompted to select one of the FTP transfers you have defined in the relevant

direction.

How to specify FTP servers and set up FTP transfers is specified in the FTP

menu: see section 5.7.

How to set up logfile uploads is described in section 5.8.5.

While an FTP session is in progress, the two Start commands are replaced

by a single Cancel FTP command, which aborts the FTP session.

During logfile replay and during execution of a command sequence, this

command is not available.

Note: When starting an FTP session you must not have the USB cableconnected (the session will fail). If this happens, remove the USB

cable, select Cancel FTP, then start the session again.


55/126

Chapter 4. TEMS Pocket Functions in the Data View Menu

LZT 108 9928 R1A 47

4.8. About

4.9. Exit

This command exits the TEMS Pocket application.

Line 1:TEMS Pocket product version (6.4).

Line 2:Copyright information.

Line 3:Address to TEMS web site.

Lines 47

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)


56/126


48

5. The Pocket Menu

5.1. General

The Pocket menu is accessed from the data view menu. It has the following

submenus:

Cell controlmenu: Used to control phone behavior in network (lock on

RAT/band/cell etc.). See section 5.2.

Command sequencemenu: Used to define a command sequence. See

section 5.3.

Eventsmenu: Used to show and control the event log, event counters,

and event settings. See section 5.4.

Data viewsmenu: Used to control visibility of data views. See section 5.5.

GPS menu: Used to configure GPS settings. See section 5.6.

FTPmenu: Used to set up FTP sessions. See section 5.7. Logfilemenu: Used to set up logfile recording and to replay logfiles. See

section 5.8.

General settingsmenu: Used to control miscellaneous TEMS Pocket

settings. See section 5.9.

Any changes you make to the settings remain in force indefinitely unless you

change the settings again, or reset all settings (see section 5.9.8).

Note: If the phone storage medium is full, TEMS Pocket settings can no

longer be saved. You then need to remove some files to free up

memory.


57/126

Chapter 5. The Pocket Menu

LZT 108 9928 R1A 49

5.2. Cell Control Menu

In this menu are collected the functions that modify the phones behavior in

the network.

Note that any locking function that you activate here continues to apply

indefinitely, even after you power cycle the phone (unless you use the Reset

Settings command: see section 5.9.8). To release a lock, enter the

appropriate dialog again and set the lock to Off.

5.2.1. Lock to RAT

This function locks the phone to one radio access technology in idle as well

as dedicated mode. When this function is activated, the phone detaches fromthe network it is currently attached to, then attaches to the selected network.

During a voice call, locking to RAT other than the current one causes the call

to drop. Locking on the current RAT does not interfere with the call.

During an FTP session, the phone can usually be locked to any RAT (current

or other) without the session being terminated. If a RAT switch is required, the

FTP transfer is paused until the routing area update has taken place.

If the signal is too weak, the phone will go into no service (or emergency call)

mode.

Regarding interplay between locking functions, see section 5.2.5.

5.2.2. Lock Cell WCDMA

This function locks the phone to a WCDMA cell, which becomes the new

serving cell provided that the signal strength is sufficient.

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.


58/126


50

In idle mode, the locking action is executed immediately. In dedicated mode,

on the other hand, the phone will notbe locked until the call has ended.

If the signal from the cell to lock on is too weak, the phone will go into no

service mode. Note that this may happen if you issue the Lock Cell commandduring a call and then move away from the target cell before hanging up the

call.

If the cell to lock on belongs to a different network, the phone may

alternatively enter emergency call mode (this depends on the SIM).

Note that you can also lock on a cell that makes an appearance in data views.

See sections 3.3and 3.9.


5.2.3. 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 from the cell to lock on is too weak, the phone will go into no

service mode. If the cell to lock on belongs to a different network, the phonemay alternatively enter emergency call mode (this depends on the SIM).

Choose Set UARFCN/SCto 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.

Choose Offto release the lock.


59/126


LZT 108 9928 R1A 51

Note that you can also lock on a cell that makes an appearance in data views.

See sections 3.3, 3.13, and 3.14.


5.2.4. Lock Band GSM

You can order the phone to use only one of its frequency bands. This will of

course result in failed calls if you have blocked all bands that are available in

the area.

If locked to a band during a call, the phone will not be immediately forced to

the selected band. In other words, there is no forcing of handover; but as

soon as one occurs, the phone will be redirected to the selected band.


5.2.5. Interplay between Locking Functions

If you lock the phone to a cell or band (sections 5.2.2, 5.2.3, 5.2.4), the phone

is also automatically locked to the corresponding RAT. In this situation,

Choose Set ARFCNto 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 Offto release the lock.

Off:No restriction.

850, 900, 1800, 1900:The phone is locked to the

indicated band.


60/126


52

if you release the cell or band lock, the RAT lock is also automatically

released;

trying to release only the RAT lock has no effect. The phone will still be

locked to the chosen cell or band and is not allowed to switch to a differentRAT.

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.

5.2.6. Comparison with Locking Functions in TEMS

InvestigationUsers 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 Nokia 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 section 5.2.5above.)

See also the TEMS Investigation 9.0 Data Collection Users Manual, section

13.4.

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


61/126


LZT 108 9928 R1A 53

5.3. Command Sequence Menu

The command sequence supports automation of the following tasks:

Voice calls FTP data transfers

Ping

Logfile upload

Wait in idle mode

Up to ten distinct command sequences can be defined. Each sequence can

contain up to ten actions. When the sequence is executed, its actions are

performed one after another in the order they have been defined.

You start and stop a command sequence from the data view menu: see

section 4.5. The command sequence contains a parameter governing how

many times the sequence should be executed.

5.3.1. Defining Command Sequences

In this menu you define the contents of command sequences.

At the outset the command sequences are simply numbered from 0 to 9 in the

user interface; you get the opportunity to name the sequences while defining

them (see below).

Note: Running a command sequence for extended periods of time

places a high load on the phone battery.

Select a number to define the corresponding

command sequence.


62/126


54

Name:Text field for naming the command

sequence.

Repeat number of times:The number of times

the sequence should be repeated after the firstexecution. If this is set to 4, the sequence is run a

total of five times.

Actions:Select this item to define the actions the

command sequence should perform. See below.

The definable actions are listed from 0 to 9.

Select a number to define the corresponding

action.

Here you select the type of task to perform in the

action; one of:

Voice call

FTP transfer: Put

FTP transfer: Get

Ping

Upload logfile

Idle (wait in idle mode)Each of the FTP actions is visible here only if an

FTP transfer in the relevant direction has been

defined in the FTP menu. See section 5.7.1.


63/126


LZT 108 9928 R1A 55

5.3.1.1. Voice Call Action Settings

5.3.1.2. FTP Get Action Settings

5.3.1.3. FTP Put Action Settings

Dial number:Enter the number to call.

Call duration:Specify the duration in seconds ofeach voice call.

Here are listed all FTP transfers with direction Get

that are currently defined in the FTP menu (see

section 5.7.1). Select which transfer to perform.

Here are listed all FTP transfers with direction Put

that are currently defined in the FTP menu (see

section 5.7.1). Select which transfer to perform.


64/126


56

5.3.1.4. Ping Action Settings

5.3.1.5. Upload Logfile Action Settings

There are no settings for this action. If selected, what it will do is to upload all

logfiles found in the logfile storage folder (defined as described in section

5.8.4).

The FTP server uploaded to is, as always, the one currently defined in the

Logfile menu under Upload FTP Server (see section 5.8.6).

Remote address:The IP address of the server to

be pinged. This can be either an alphanumeric

string or a 12-digit number.

Number of replies:The number of replies from the

pinged address.

Data account:The data account that should be

used for the Ping session.

Connect timeout:Maximum time to connect with

the access point.

Resolve timeout:Maximum time to wait for the

DNS to resolve the address.

Send timeout:Maximum time for sending Echo

Request message.

Receive timeout:Specifies the amount of time to

wait for receipt of the Echo Reply message

corresponding to a given Echo Request message.


65/126


LZT 108 9928 R1A 57

5.3.1.6. Idle Mode Action Settings

5.3.1.7. The Assembled Command Sequence

Once you are done setting up an action, its name will appear in the action list

for the command sequence being defined.

Similarly, when you are done defining the entire command sequence, its

name will appear in the list of command sequences (one level up).

See the examples below.

5.3.2. Deleting Command Sequences and Command

Sequence Actions

To delete a command sequence, select it in the list of defined sequences

and press the Cbutton.

Similarly, to delete an action from a command sequence, select the action

in the list of defined actions and press the Cbutton.

Idle time:Specify the length of time (in seconds)

the phone should spend in idle mode.


66/126


58

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

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.

5.4.1. Event Log

5.4.1.1. Viewing the Event Log

In the Events menu, choose Event Log.

The New tab is shown, listing all events that you have not yet inspected. Thenumber 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 Norm tab shows all normal events.

When an event is selected on a tab, some information on the event is shown

beneath the event name:

Note: To have events logged at all, you must make sure that the event

mode is set to On (this is the default setting). See section

5.4.1.3.


67/126


LZT 108 9928 R1A 59

To inspect the full details of an event, select it and press View. A plain-text

screen appears:

After you have inspected an event, the event is removed from the New tab.

5.4.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 Select and choose Clear event log.

5.4.1.3. Enabling and Disabling Event Logging

Event logging is by default enabled, and the settings for the individual events

govern whether each event type is actually logged.

Note: The event log is cleared when the TEMS Pocket application is

restarted.

Event time and parameters

Event name

Event-specific parameters

Event name

CGI

Timestamp


68/126


60

While in the event log, you can disable event logging as follows: Press

Select, choose Event logging, and choose Off.

No events will then be logged regardless of how the Log option in the event

settings is set (see section 5.4.2).

5.4.1.4. Shortcuts to Event Settings and Event Counters

From the event log you can use the Select menu to go directly to the

event settings (see section 5.4.2) or event counters (see section 5.4.3).

5.4.2. Event Settings

Each type of event has a set of configurable properties.

5.4.2.1. Viewing Event Settings

From the Events menu, choose Event Settings.

Events are grouped onto tabs: one for each event category (MM, SM, GMM,

RR, IRAT, SESSION, RRC). All event types are listed and described in

section 5.4.5below.

Use the navigation key (left/right) to move between event tabs. When you

select an event, the current settings for that event are displayed beneath theevent name.

5.4.2.2. Modifying Event Settings

To change settings for an individual event, navigate to the event and

press the More button.


69/126


LZT 108 9928 R1A 61

To apply identical settings to all events in a category (on a tab), navigate

to that tab, press More and choose Select (e.g.

Select RR).

To apply identical settings to all events, press More and choose Selectall.

The following options exist:

5.4.3. Event CountersTEMS 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.)

5.4.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 5.4.2). All event types are listed and described in section 5.4.5below.

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 insection 5.4.5.

Sound:

Off means that no sound will be played when

the event occurs.

On means that, in idle mode, a sound

predefined for the event will be played when

the event occurs. The prerecorded sound files

consist of a voice announcing the event. Indedicated mode, the voice recording is

replaced by a notification beep.

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


70/126


62

Use the navigation key (left/right) to move between event tabs. When you

select an event, the current count for that event is displayed beneath the

event name.

5.4.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 (on a tab), navigate to

that tab, press More and choose Reset (e.g. Reset

RR).

To reset the counters for all events, press More and choose Reset all

counters.

5.4.4. Event Icons

An icon is shown on the display status bar for the latest event that occurred.

When you enter the event log, the currently displayed event icon disappears.

Event icons are differentiated as follows:

Each event category (tab) has its own icon. For example, MM and SM

each has its own icon.

All failure events are distinguished by a red cross.

See the examples below:

Normal event Failure event


71/126


LZT 108 9928 R1A 63

For other event categories, the appropriate text string is substituted.

For inter-RAT events, the strings 2G and 3G are added to indicate which

technology the phone is transferred to:

5.4.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 appendixA.

Here are also listed the default values for the settings described in section

5.4.2.

The Tcolumn indicates whether the event denotes a normal occurrence (N)

or some kind of failure (F).

The Defcolumn indicates the default logging, sound, and icon popup settings

(On = all settings turned on, Off = all settings turned off. In this TEMS Pocket

version and phone, all events are in fact by default set to On.)

All events have CGI as parameter; other parameters appear from the tables.

5.4.5.1. CC Events

For values of CC Cause, see appendixA.5.

Handove

Documents

TEMS Pocket 6.4 for Nokia N96