TEMS Pocket Users Manual
TEMS Pocket Users Manual
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. 2006 Ericsson AB. All rights reserved. Publication number: LZT 108 8815 R1A
Contents
Contents
1. Introduction
1.1. Whats New in TEMS Pocket 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2. What Was New in TEMS Pocket 5.0. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview
3. Data Views
3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1.1. General Data View Properties . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1.2. The Built-in Help Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1.3. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Survey of Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3. PDP Context (View No. 1.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. MM/GMM (View No. 1.2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.5. Time Log (View No. 1.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.5.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.6. GPS (View No. 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.7. GSM Cells (View No. 2.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.7.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.8. GSM Cell Id (View No. 2.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.8.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.9. GSM BA List (View No. 2.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.9.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.10. GSM Serving Cell (View No. 3.1) . . . . . . . . . . . . . . . . . . . . . . 18 3.11. GPRS Data (View No. 3.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.11.1. Data View Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.12. GPRS Info (View No. 3.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.13. GSM C/I Info (View No. 3.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.14. GSM AMR (View No. 3.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.15. The WAP Browser GPRS Data View . . . . . . . . . . . . . . . . . . . . . . 28
31
31 31 32 32 32 32 33 33
4.1. Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2. Insert Filemark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3. Start/Stop Logfile Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5. Start/Stop FTP Put, Start/Stop FTP Get . . . . . . . . . . . . . . . . . . . . . 4.6. Connect/Disconnect GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7. Start/Stop Call Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8. Pocket Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
34 35 35 35 36 36 37 37 37 38 38 39 39 39 39 40 41 41 41 42 42 43 43 44 45
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2. Cell Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1. Lock ARFCN GSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.2. Lock Band GSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.3. Ignore Cell Barred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.4. Reset Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1. Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1.1. Viewing the Event Log . . . . . . . . . . . . . . . . . . . . . . . 5.3.1.2. Clearing the Event Log . . . . . . . . . . . . . . . . . . . . . . . 5.3.1.3. Enabling and Disabling Event Logging . . . . . . . . . . . 5.3.1.4. Shortcuts to Event Settings and Event Counters . . . 5.3.2. Event Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.2.1. Viewing Event Settings . . . . . . . . . . . . . . . . . . . . . . . 5.3.2.2. Modifying Event Settings. . . . . . . . . . . . . . . . . . . . . . 5.3.3. Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.3.1. Viewing Event Counters . . . . . . . . . . . . . . . . . . . . . . 5.3.3.2. Resetting Event Counters . . . . . . . . . . . . . . . . . . . . . 5.3.4. Event Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5. List of Logged Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5.1. CC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5.2. MM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5.3. SM Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5.4. GMM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5.5. RR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
Contents
5.3.5.6. Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 5.4. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 5.5. GPS Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 5.5.1. GPS Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 5.5.2. GPS Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 5.5.3. GPS Time Synch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.6. FTP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.6.1. FTP Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.6.2. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 5.7. Logfile Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.7.1. Save Logfile To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.7.2. Autostart Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 5.7.3. Upload Logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 5.7.3.1. Setting an Upload Schedule . . . . . . . . . . . . . . . . . . . 54 5.7.4. FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.8. Call Sequence Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 5.9. Info Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 5.10. General Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 5.10.1. WAP Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 5.10.2. Data View Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 5.10.3. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 5.10.4. Backlight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.10.5. Cell Id Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.10.6. Power Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.10.7. Measure Mode Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.10.8. Auto Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.10.9. Redial Disconnected Calls . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.10.10. Reset All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
62
64 65
iii
A.2. CCCH Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3. Channel Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4. Deactivate PDP Context Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . A.5. CC Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.6. GMM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.7. GPRS Network Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . A.8. PDP Context Request Parameters. . . . . . . . . . . . . . . . . . . . . . . . . A.8.1. Delay Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8.2. Reliability Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8.3. Peak Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8.4. Precedence Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8.5. Mean Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.9. RR Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.10. MM Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.11. RR Internal Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.12. SM Cause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.13. GPS Fix Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65 66 66 66 68 68 69 69 69 69 70 70 70 71 72 72 73
76
76 76 76 76 77 77 77
C.1. Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.2. Cell Control Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.3. Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.4. Data Views Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.5. GPS Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.6. Logfile Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.7. General Settings Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Chapter 1. Introduction
1.
Introduction
Welcome to TEMS Pocket. TEMS Pocket 5.1 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 5.1 as implemented in the Sony Ericsson K790i and K790a phones.
1.1.
TEMS Pocket 5.1 is implemented in each of the following mobile phones: Sony Ericsson K790i, K790a, and K800i Nokia N80
New features include: Support for EGPRS on the 850, 900, 1800, and 1900 MHz bands Sony Ericsson K790i: 900/1800/1900 MHz Sony Ericsson K790a: 850/1800/1900 MHz Nokia N80: 850/900/1800/1900 MHz
Support for GPS positioning of data with Bluetooth GPS Compatibility with TEMS Investigation 8.0 versions of the supported phones Improved and automated logfile and FTP features Call sequences (voice) C/I measurements in GSM networks Filemarks Time log data view
1.2.
(The 5.0 version was built into a Sony Ericsson W900i phone.) WCDMA network parameters, air interface measurements, and events Many new GSM events, including call events Event counting Combined data views showing both WCDMA and GSM (both simultaneously when inter-RAT neighbor measurements are being made) Possible to record logfiles that can be replayed in TEMS Investigation and TEMS Automatic Possible to set up and run FTP sessions (Get and Put) using Pocket functionality Improved on-screen help (callout boxes)
Chapter 2. Overview
2.
Overview
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 the first time it will display the PDP Context data view (after you have selected Start phone from the Start-up menu):
On later occasions, when turned on, the phone will display the data view last inspected, provided that the Pocket functions are activated. The data views are divided into categories. 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. However, it also shows an icon for the latest TEMS Pocket event that occurred (see section 5.3.4) and a symbol indicating that a logfile is being recorded (see section 4.3). 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 4.1). By default TEMS Pocket is in active mode, and its data views are visible. The data views are exhaustively described in chapter 3.
2.2.
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 4. From the Activity menu you can also access the Pocket menu, which is the chief means of configuring TEMS Pocket: see chapter 5. The Pocket menu can alternatively be accessed from the phones main menu: Settings General Pocket menu. Note: If the phone memory is full, TEMS Pocket settings can no longer be saved. Remove some files to free up memory.
The Pocket menu is also used to inspect and manage the event log (see section 5.3.1). A shortcut to the event log is found in the Activity menu.
3.
Data Views
3.1.
3.1.1.
General
General Data View Properties
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.15. The rules for the graphic presentation are found in appendix B, page 74. 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.
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.
To turn off the help function, press the Return key More and choose Toggle help again.
. Alternatively, press
3.1.3.
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.
3.2.
No. 1.1
2.1
GSM Cells
2.2
GSM Cell Id
2.3
GSM BA List
3.1
3.2
GPRS Data
No. 3.3
Description 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 for each ARFCN in use. Displays GSM logical channel information, AMR codec selected on uplink and downlink, and statistics on AMR codec utilization. Displays a subset of the GPRS Data view (3.2) during WAP browsing.
3.4
3.5
GSM AMR
3.3.
Screenshot
R: Reliability Class {0 ... 5} K: Peak Throughput {0 ... 9} P: Precedence Class {0 ... 3} MT: Mean Throughput {0 ... 18, 31} (For the meanings of values, see appendix A.8.) APN: Access Point Name Lines 78 show information on the network that the phone is currently using. This information is repeated in many other data views. C: Current RAT {G: GSM, : No service} ARFC: Serving cell BCCH ARFCN B: Serving cell BSIC RSSI: Serving cell Received Signal Strength Indicator (= RxLev), 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 CI: Serving cell Cell Identity
Key
3.4.
Screenshot
GMM: GMM Attached {A: Attached, : Not attached} TLLI: Temporary Logical Link Identifier (hex) The following four parameters are updated each time the phone performs a Location Area Update or Routing Area Update. RMCC: Registered MCC RMNC: Registered MNC
Key
RLAC: Registered LAC RRAC: Registered RAC Lines 56 are the same as the two bottom lines in the PDP Context view: see section 3.3.
10
3.5.
MM
Home: Registered in Home PLMN Equiv: Registered in Equivalent PLMN Roam: Registered in Roaming PLMN Screenshot Unreg: Unregistered (See 3GPP TS 21.905.)
GSM
TCH: Time using Traffic Channel (TCH) PDCH: Time using Packet Data Channel (PDCH) Idle: Time spent in Idle mode No Service: Time spent in No Service mode
3.5.1.
You can reset all counters in this view by choosing Reset time log.
11
3.6.
This view is shown only if the GPS option has been purchased with the product. Lines 16 show GPS data. Latitude: Latitude in degrees, minutes, and decimal minutes. Longitude: Longitude in degrees, minutes, and decimal minutes. Altitude: Height above sea level in meters. Speed: Speed in km/h. Screenshot No. of satellites: The number of satellites seen by the GPS device. Fix quality: Quality of GPS fix; see appendix A.13. The last two parameters will always be valid as long as the phone is connected to the GPS. Lines 78 are the same as the two bottom lines in the PDP Context view: see section 3.3. There are no actions associated with this data view.
12
3.7.
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
13
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 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} Key CB: Serving cell barred {B: Barred, : Not Barred} Lines 910 are the same as the two bottom lines in the PDP Context view: see section 3.3.
Screenshot
3.7.1.
14
Choose the cell 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 select the unlock command.
15
3.8.
Screenshot
CI: Serving Cell Identity RxLev: Serving Cell RxLev (unit user-configurable: see section 5.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
Key
RxLev: Neighbor Cell RxLev Line 8 MT: MS-TXPWR-MAX-CCH, maximum RACH power (dBm) {GSM 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 PDP Context view: see section 3.3.
16
3.8.1.
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 GSM Cells view; see section 3.7.1.
3.9.
Screenshot
Key
3.9.1.
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 GSM Cells view; see section 3.7.1.
17
3.10.
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 appendix A.2, page 65 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
18
Line 3 (dedicated mode) L: Logical Channel P: PBCCH p: Hopping PBCCH S: SDCCH s: Hopping SDCCH T: TCH t: Hopping TCH D: PDTCH d: Hopping PDTCH Screenshot idle mode TC: Traffic Channel (TCH ARFCN) or Stand-alone Dedicated Control Channel (SDCCH ARFCN) or Packet Dedicated Traffic Channel (PDTCH ARFCN). Hopping channels are shown one at a time; see section 3.1.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) 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 TS 05.08), numeric/graphic Key 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
19
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 66 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} Lines 67 are the same as the two bottom lines in the PDP Context view: see section 3.3.
20
3.11.
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 4, 5, and 7 are being used on the downlink and TS 6 is used on both uplink and downlink. Techn: Technology supported in cell: EDGE or GPRS
21
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 TS 44.060, sec. 9.2.3.1
22
Lines 58 report 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 Screenshot Err: 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 3.11.1 below. Lines 910 are the same as the two bottom lines in the PDP Context view: see section 3.3. Key
3.11.1.
You can reset all counters in this view by choosing Reset data counters.
23
3.12.
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 TS 24.008, sec. 4.7.2 T3314S: T3314 timer value (GMM Ready Timer), start value; see 3GPP TS 24.008, sec. 4.7.2 T3168: T3168 timer start value (Packet Uplink Assignment Timer), see 3GPP TS 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 TS 44.060, sec. 13.1 {0, 80, 120, 160, 200, 500, 1000, 1500} NMO: Network Mode of Operation {I, II, III}; see appendix A.7, page 68 DX: DRX Timer Max, see 3GPP TS 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 PDP Context view: see section 3.3.
Key
24
3.13.
Screenshot
25
3.14.
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.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.
26
Line 3 (continued) RQ: Receive Bit Error Rate (RxQual; scale defined in 3GPP TS 05.08), numeric/graphic FE: Frame Erasure Rate (FER) in %, 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. CUL: AMR codec used on uplink ULU: Utilization (%) of this uplink AMR codec CDL: AMR codec used on downlink DLU: Utilization (%) of this downlink AMR codec Lines 89 are the same as the two bottom lines in the PDP Context view: see section 3.3.
Key
27
3.15.
While the WAP browser (activated from the phones main menu Internet Services) is running, TEMS Pocket can show selected air interface information in the bottom part of the screen. The WAP browser data view is by default visible. During a WAP session, you can hide the data view by pressing More and choosing Hide data view. To show it again, press More and choose Show data view. You can also turn this data view on and off from the Pocket menu; see section 5.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 side of the phone display when the phone is held in the normal manner). The data view contents and layout remain unchanged.
28
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 5.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.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 4, 5, and 7 are being used on the downlink and TS 6 is used on both uplink and downlink. MCSu: EGPRS modulation coding scheme on uplink {MCS1 ... MCS9}
29
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 bytes/s Err: Percentage of LLC downlink data blocks erroneously decoded Screenshot Line 3, right: UL (uplink, LLC) Rate: Total LLC uplink instantaneous data transfer rate in bytes/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 bytes/s Key Err: 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 bytes/s Retr: Percentage of RLC/MAC uplink data blocks retransmitted There are no actions associated with the WAP browser data view.
30
4.
A number of TEMS Pocket functions are accessed by pressing the Activity key. This is the button below the C 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.
4.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.
4.2.
Insert Filemark
This command inserts filemarks 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 happened (if you are not using a GPS). The filemark text is user-editable and may consist of up to 127 characters. The Insert filemark command is visible only while logfile recording is in progress.
31
4.3.
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 5.7.2.) You can insert filemarks in a logfile during recording; see section 4.2. If the phone runs out of memory during logfile recording, or if some other error occurs, the recording is stopped and you are notified by a message in the display. Note that if the memory is full, it is no longer possible to edit TEMS Pocket settings; you then need to remove some files to free up memory. While a logfile is being recorded, this icon is shown on the status bar at the top of the display. Refer to section 5.7 for all remaining details on logfile recording and handling.
4.4.
Event Log
4.5.
These commands are used to conduct FTP sessions, including uploading of TEMS Pocket logfiles. How to perform FTP operations and how to connect to FTP servers is specified in the FTP menu: see section 5.6.
4.6.
Connect/Disconnect GPS
This command connects or disconnects a Bluetooth GPS. For further information on using GPS devices with TEMS Pocket, see section 5.5. The menu item is visible only if you have selected manual connect; see section 5.5.1. If there are no GPS devices to connect to (the list in section 5.5.2 is empty), the menu item is grayed. While a connect operation is in progress, the menu item reads Connecting and is again grayed.
32
4.7.
This command starts and stops a call sequence. How to set up call sequences is explained in section 5.8.
4.8.
Pocket Menu
33
5.
5.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.
The Pocket menu has the following submenus: Cell control menu: Used to control phone behavior in network (lock on band/frequency/cell etc.). See section 5.2. Events menu: Used to show and control the event log, event counters, and event settings. See section 5.3. Data views menu: Used to control visibility of data views. See section 5.4. GPS menu: Used to configure GPS settings. Available only if the GPS option is installed. See section 5.5. FTP menu: Used to set up FTP sessions and FTP logfile transfer. See section 5.6. Logfile menu: Used to configure automated logfile recording and transfer. See section 5.7. Call sequence menu: Used to define a call sequence. See section 5.8. Info menu: Used to inspect some hardware and software data. See section 5.9. General settings menu: Used to control miscellaneous TEMS Pocket settings. See section 5.10.
34
5.2.
In this menu are collected the functions that modify the phones behavior in the network.
5.2.1.
This function locks the phone to an ARFCN in a GSM network. If there exists an available GSM cell using that ARFCN, the phone will be immediately handed over to that cell provided that the signal strength is sufficient. If the signal is too weak, the phone will go into no service mode. Choose Set ARFCN to lock on a cell. You will be asked to enter an ARFCN number. This ARFCN will then appear beneath the menu item when selected. Choose Off to release the lock.
Note that you can also lock on a cell that makes an appearance in data views. See sections 3.7 and 3.8.
5.2.2.
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. Off: No restriction. 850, 900, 1800, 1900: The phone is locked to the indicated band. (The set of bands displayed depends on the phone.)
35
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.3.
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.
5.2.4.
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.
36
5.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 4.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 the event mode is set to On (this is the default setting). See section 5.3.1.3.
5.3.1.
5.3.1.1.
Event Log
Viewing the Event Log
The New tab is shown, listing all events that you have not yet inspected. 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:
37
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.3.1.2.
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 More and choose Clear event log. Press Yes to confirm.
5.3.1.3.
Event logging is by default enabled, and the settings for the individual events govern whether each event type is actually logged. While in the event log, you can disable event logging as follows: Press More, choose Event logging, and choose Off.
38
No events will then be logged regardless of how the Log option in the event settings is set (see section 5.3.2).
5.3.1.4.
From the event log you can use the More menu to go directly to the event settings (see section 5.3.2) or event counters (see section 5.3.3).
5.3.2.
Event Settings
5.3.2.1.
Events are grouped into submenus: one for each event category (CC, MM, SM, GMM, RR, IRAT, RRC, Session). All event types are listed and described in section 5.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.
5.3.2.2.
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 More and choose Select <category name> (e.g. Select RR).
39
To apply identical settings to all events, press More 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 5.3.5. 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 file system.)
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.3.5.
5.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.)
40
5.3.3.1.
The events are divided into the same categories as in the event settings (see section 5.3.2). All event types are listed and described in section 5.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.
5.3.3.2.
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 More and choose Reset <category name> (e.g. Reset RR). To reset the counters for all events, press More and choose Reset all counters.
5.3.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 appearing on the event log tabs has its own icon (for example, CC and MM each has its own icon, although these two event categories are grouped together on one tab). All failure events are distinguished by a red cross.
41
Normal event
Failure event
5.3.5.
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 5.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 turned on, Off = all turned off). All events have CGI as parameter; other parameters appear from the tables.
5.3.5.1.
CC Events
For values of CC Cause, see appendix A.5. Event Name Blocked Call Call Attempt Call End Call Established Dropped Call T F N N N F Def On Off Off Off On Parameters CC Id, CC Cause CC Id, Call Type {MO, MT} CC Id, CC Cause CC Id CC Id, CC Cause
42
5.3.5.2.
MM Events
For values of MM Cause, see appendix A.10. Event Name Auth Fail (Authentication Failure) Auth Reject (Authentication Reject) LAU Attempt (Location Area Update Attempt) LAU Fail (Location Area Update Failure) LAU Reject (Location Area Update Reject) LAU Success (Location Area Update Success) MM Service Mode 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) MM Service Mode {Registered Home, Registered Equivalent PLMN, Registered Roaming, Full Service, Limited Service}
On
5.3.5.3.
SM Events
For values of SM Cause, see appendix A.12. Event Name PDP Ctx Activ Attempt (PDP Context Activation Attempt) T N Def Off NSAPI Parameters
43
Event Name PDP Ctx Activ Compl (PDP Context Activation Complete) PDP Ctx Activ Reject (PDP Context Activation Reject) PDP Ctx Deact Attempt (PDP Context Deactivation Attempt) PDP Ctx Deact Compl (PDP Context Deactivation Complete)
T N
Def Off
Parameters NSAPI, IP version {4, 6}, PDP address (IPv4 only) NSAPI, SM Cause
On
Off
NSAPI
Off
5.3.5.4.
GMM Events
For values of GMM Cause, see appendix A.6. Event Name GMM Attach Attempt GMM Attach Complete GMM Attach Reject GMM Detach Attempt GMM Detach Complete RAU Attempt (Routing Area Update Attempt) T N N F N N N Def Off Off On Off Off Off Parameters Attach type: {GPRS, Combined} Attach type: {GPRS, Combined} T3310 expired or GMM Reject Cause GMM Cause GMM Cause, Type {NW, UE} RA Update Type {Normal, Periodic, Combined}
44
Event Name RAU Complete (Routing Area Update Complete) RAU Reject (Routing Area Update Reject)
T N
Def Off
On
5.3.5.5.
RR Events
For values of RR Cause, see appendix A.9. For values of RR Internal Cause, see appendix A.11. Event Name Assignment Fail (Assignment Failure) Data Link TO (Data Link Timeout) HO Fail (Handover Failure) Imm. Ass. Failure (Immediate Assignment Failure) Imm. Ass. Reject (Immediate Assignment Reject) Pkt Access Fail (Packet Access Failure) Radio Link Timeout T F F F F Def On On On On Parameters RR Cause, RR Internal Cause Target BCCH ARFCN, BSIC, TO value BCCH ARFCN, BSIC, RR Internal Cause BCCH ARFCN, BSIC, RR Internal Cause BCCH ARFCN, BSIC, RR Internal Cause BCCH ARFCN, BSIC, RR Cause BCCH ARFCN, BSIC, Radio Link Timeout Counter (Max)
On
F F
On On
45
T F
Def On
5.3.5.6.
Session Events
T N F N N F N F N F N Def On On On On On On On Off Off Off Parameters
Event Name FTP Transfer End FTP Transfer Failed FTP Transfer Start GPS Connected GPS Disconnected GPS Location Found GPS Location Lost Voice Call End Voice Call Failed Voice Call Start
5.4.
In this menu you control the visibility of each data view. The data views are organized in a multi-tab structure with one tab for each data view category. The Toggle button sets the visibility for the selected data view. The Set all command 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.
46
To immediately display a data view, select it and press the Goto button. If the visibility is currently set to Off for this view, 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.
5.5.
GPS Menu
TEMS Pocket can connect to a Bluetooth GPS. This functionality is not part of the standard TEMS Pocket package but is available as an option. The GPS menu is visible only if you have purchased the GPS option. Using a GPS device with TEMS Pocket enhances compatibility with products such as TEMS Investigation and TEMS Automatic by allowing TEMS Pocket data to be presented on maps. 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 by the regular Bluetooth functions in the phone. Other means of controlling interaction with the GPS device are found in the GPS menu. See below.
47
5.5.1.
GPS Connect
Off: The phone cannot connect to a GPS, and the Connect GPS item in the Activity menu (section 4.6) 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 by using the command in the Activity menu (see section 4.6). If a manual connect fails, an error message is displayed. Automatic: If a GPS of the type selected in the GPS device submenu (see section 5.5.2) is present, the phone will try to connect to that 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 does not disconnect a GPS that is currently connected.
5.5.2.
GPS Device
Here are listed all GPS devices that have been Bluetooth paired with the phone. Select which GPS to connect to. Note: The list may contain further device types besides these, including devices other than GPS units.
48
5.5.3.
5.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 4.5.
5.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.
49
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:
Common Parameters
FTP server: Specify the FTP server to interact with: one of those defined in the FTP server submenu (see section 5.6.2).
5.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).
50
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. 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 5.6.1). Data account: Select the data account that should be used for the FTP session. Timeout: This timeout relates to the establishment of the dialup connection, not to the FTP session itself. For the latter, a fixed timeout of 120 s (not user-configurable) is used; failure to obtain a response from the FTP server within that time results in FTP session error. If you set Timeout to 0, no timer is started and no timeout will ever occur.
51
5.7.
Logfile Menu
TEMS Pocket can record its measurements in logfiles, containing the same richness of detail as logfiles recorded with TEMS Automatic MTUs 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 card (see section 5.7.1 below). Sony Ericsson phones support Memory Stick Duo or Memory Stick Micro cards; Nokia phones support miniSD cards. Memory cards up to 2 GB can be used, which is enough to accommodate several hours of continuous logging. You can record logfiles manually by using commands in the Activity menu: see section 4.3. You can also configure TEMS Pocket to trigger automatic recording of logfiles in a number of situations: see section 5.7.2 below. There is no replay function in TEMS Pocket, but you can transfer the logfiles to a PC and replay them in TEMS Investigation (version 7.1 or later) or import them into the database of a TEMS Automatic system (version 5.0 or later). The file transfer can be done through a USB cable or via infrared or Bluetooth. It is also possible to upload logfiles to an FTP server using the built-in FTP client, or send logfiles as attachments to e-mail. See sections 5.7.3 and 5.7.4 below.
5.7.1.
Save Logfile To
Phone memory: Logfiles are saved to the phone memory, directory Other. When the phone is connected to a PC, the phone memory is represented in Explorer as a Removable disk with the directory Other located at the root level. MemoryStick: Logfiles are saved to the memory stick, provided that the phone has got one installed. A similar directory structure is created on the memory stick, including a directory Other to which the logfiles are written. When the phone is connected to a PC, the memory stick is represented in Explorer as a second Removable disk, again with the directory Other located at the root level.
52
5.7.2.
Autostart Logfile
You can configure logfile recording to start automatically in a number of 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 4.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. FTP: Logfile recording starts automatically at the beginning of an FTP testing session (initiated by the Start FTP Put or Start FTP Get command in the Activity menu: see section 4.5) and stops at the end of that session. (Recording is naturally 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.
53
5.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 5.7.4. 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 5.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 remain because you aborted uploading of these files). Off: No uploading. Logfiles are simply stored in the phone memory or memory stick as long as free space is available.
5.7.3.1. Step 1
Now: Choose this option to perform the first upload right away (as soon as you are done setting up the schedule). Skip to Step 3 below. 00:00: Choose this option to specify a time of day when the first upload should be performed.
54
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 4.5). If you abort an upload, the files that were not transferred will be included in the next upload.
5.7.4.
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 5.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.
55
5.8.
TEMS Pocket supports automation of voice calls with a simple call sequence:
You start and stop the call sequence from the Activity menu: see section 4.7. While the call sequence is executing it will repeat the call defined for it over and over again.
5.9.
Info Menu
Entering this menu causes a splash to appear showing the TEMS Pocket version as well as IMSI and IMEI: IMSI: International Mobile Station 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
5.10.
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 Redialing of abnormally disconnected calls
The settings made here remain in force until you modify them again or reset them with the Reset All command (see section 5.10.10).
5.10.1.
When you are running WAP services you can have a TEMS Pocket data view displayed at the bottom of the WAP browser. See section 3.15, page 28. 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.
57
5.10.2.
5.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.
58
5.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.
5.10.5.
Cell Id Format
Hex: LAC and CI are displayed in hexadecimal digits. Decimal: LAC and CI are displayed in decimal digits.
5.10.6.
Power Display
dBm: RxLev is displayed in dBm. GSM: RxLev is displayed in GSM units.
59
5.10.7.
5.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).
5.10.9.
60
61
6.
The TEMS Pocket functions in the phone do not include commands for connecting to and disconnecting from the packet-switched network. This is not needed, since such basic packet-switched behavior is implicitly governed by some menu settings that are in the commercial phone.
6.1.
GMM Attach/Detach
To control GMM attach and detach, proceed as follows: In the phones main menu, choose Settings and navigate to the Connectivity tab. Scroll down to Data communication and press Select. In the Data communication menu, select Preferred service.
If PS and CS (the default setting) is chosen, the phone will automatically attach to the packet-switched network. If this setting is active when you turn on the phone, it will perform a GMM attach as soon as you have entered your PIN code. If a packet-switched connection is up and you change the setting to CS only, the phone will immediately detach from GMM.
62
6.2.
PDP contexts are handled automatically for all data services. When you start an FTP Get or FTP Put session (section 4.5), TEMS Pocket automatically sets up a PDP context as part of the dialup procedure (specified under Data account in the FTP setup: see section 5.6). When the FTP session terminates, the PDP context is deactivated. A PDP context is likewise activated automatically when you start the WAP browser (see the phone user manual for details). When you exit the WAP menu, the WAP connection is closed, deactivating the PDP context.
63
7.
For support in using TEMS Pocket, please contact Ericsson according to the directions found at www.ericsson.com/tems under the link Contact TEMS. 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.
64
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
A.2.
NC
CCCH Configuration
1 basic physical channel used for CCCH, not combined with SDCCHs Comb 1 basic physical channel used for CCCH, combined with SDCCHs NC2 2 basic physical channels used for CCCH, not combined with SDCCHs
65
NC3 NC4
3 basic physical channels used for CCCH, not combined with SDCCHs 4 basic physical channels used for CCCH, not combined with SDCCHs
A.3.
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.4.
25 26 36 37 38 39 T3390
A.5.
1 3 6 8 16 17 18 19 21 22 25
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
66
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 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
67
A.6.
2 3 6 7 8 9 10 11 12 13 14 15 16 17 20 21 22 23 40 4863 95 96 97 98 99 100 101 111
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 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.7.
Handling of paging in the GPRS network. I II Mode I: All paging on GPRS channels; Gs signalling interface present Mode II: All paging on PCH; no Gs
68
III
Mode III: All circuit-switched paging on PCH, all packet-switched paging on PPCH; no Gs
A.8.
A.8.1.
0 1 2 3 4
A.8.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.8.3.
0 1 2 3 4 5 6 7 8 9
Peak Throughput
Subscribed Up to 1 000 octet/s Up to 2 000 octet/s Up to 4 000 octet/s Up to 8 000 octet/s Up to 16 000 octet/s Up to 32 000 octet/s Up to 64 000 octet/s Up to 128 000 octet/s Up to 256 000 octet/s
69
A.8.4.
0 1 2 3
Precedence Class
Subscribed High priority Normal priority Low priority
A.8.5.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 31
Mean Throughput
Subscribed 100 octet/h 200 octet/h 500 octet/h 1 000 octet/h 2 000 octet/h 5 000 octet/h 10 000 octet/h 20 000 octet/h 50 000 octet/h 100 000 octet/h 200 000 octet/h 500 000 octet/h 1 000 000 octet/h 2 000 000 octet/h 5 000 000 octet/h 10 000 000 octet/h 20 000 000 octet/h 50 000 000 octet/h Best effort
A.9.
0 1 2 3 4 5
RR Cause
Normal event Abnormal release, unspecified Abnormal release, channel unacceptable Abnormal release, timer expired Abnormal release, no activity on the radio path Preemptive release
70
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.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
71
A.11.
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.12.
8 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
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
72
Reactivation required 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
A.13.
0 1 2 3 4 5 6 7 8
73
This appendix describes the bar length and color coding used to visualize parameter values.
B.1.
C/I
Bar length 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.
Bar length is constant. Value = x (%) x=0 1x4 x5 green yellow red Color
74
B.3.
RxLev (= RSSI)
Bar length 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
B.4.
RxQual
Bar length is constant. Value = x x=0 1x4 x5 green yellow red Color
B.5.
TxPower
Bar height proportional to (Value (30 dBm)). Value = x (dBm) x<5 5 x < 15 x 15 green yellow red Color
75
This appendix lists the defaults for all settings editable from the Activity and Pocket menus.
C.1.
Operating Mode
Active mode
C.2.
Note: Unlike settings in other menus, these settings revert to their defaults (Off/Normal) when the phone is powered off and on.
C.3.
Events Menu
Event logging: On for all events Event counting: On for all events Event settings: See section 5.3.5
C.4.
76
C.5.
GPS Menu
C.6.
Logfile Menu
C.7.
WAP data view: On Data view style: Default Messages: Minimized Backlight: 5 minutes Cell Id format: Hex Power display: dBm Measure mode display: Sub Auto answer: Off Redial disconnected: Off
77
78
Index
A
Activate PDP Context Failure Cause 65 Activity key 4, 31 Activity menu 4, 31, 34 altitude 12 AMR codecs active set 27 used on downlink 27 used on uplink 27 utilization of 27 APN 9 ARQ mode (EGPRS) 22 Auto Answer 60 Automatic Repeat Request Mode (EGPRS) 22 Autostart Logfile 53
B
Backlight (in display) 59 barred cells, accessing of 36 Base Station Identity Code 13, 17, 18, 21, 26, 29 BCCH ARFCN 9, 13, 16, 17, 18 BEP (EGPRS) 22 BEP variance (EGPRS) 22 bit error probability, mean (EGPRS) 22 bit error probability, variance (EGPRS) 22 BS-AG-BLKS-RES 18 BSIC 9, 13, 17, 18, 21, 26, 29 BS-PA-MFRMS 14, 16, 18
C
C value (EGPRS) 22 C/I 19, 22, 25, 26 graphic presentation 74 C1 13 C2 13 C31 13 C32 13 call sequence 56 starting and stopping 33 Call Sequence menu 56 Carrier-to-interference ratio (C/I) 19, 22, 25, 26 CC Cause 66 CC events 42
79
CCCH Configuration 18, 65 Cell Control menu 35 Cell Id (Cell Identity) presentation format 59 Cell Identity 9, 16 Cell Reselection Criterion (C2) 13 Cell Reselection Hysteresis 14, 16 channel coding scheme on downlink (GPRS) 22 channel coding scheme on uplink (GPRS) 22 Channel Mode 20 Channel Type 20, 66 CI 9, 16 presentation format 59 Ciphering Mode 20 color coding of parameter values 5
D
data rate 20 data view actions 6 data views 3, 5 browsing 3 categories of 3 display style 58 general properties of 5 survey of 7 visibility of 46 Data Views menu 46 Deactivate PDP Context Cause 66 Delay Class (PDP Context Request) 9, 69 Downlink Signalling Counter 18 DRX Timer Max 24 DSC (Current) 18 DSC (Max) 18 DTX rate on downlink 19, 27 DTX rate on uplink 19, 27
E
EGPRS modulation coding scheme 29 EGPRS window size 24 Equivalent PLMN, time registered in 11 event counters 40 resetting 41 viewing 41
80
Index
event log 4, 32, 37 clearing 38 details of individual events 38 viewing 37 event settings 39 modifying 39 viewing 39 events 38 enabling and disabling of logging 38 event log 38 icons for 3, 41 list of 42 Events menu 37
F
FER 19, 27 graphic presentation 74 filemarks, inserting in logfiles 31 Frame Erasure Rate 19, 27 FTP selecting server to upload logfiles to 55 setting up Put and Get operations 49 specifying FTP servers 50 starting and stopping FTP sessions 32 FTP menu 49 Full/Sub values (for RxLev and RxQual) 60
G
General Settings menu 57 GMM Attach, controlling 62 GMM Attached 10 GMM Cause 68 GMM Detach, controlling 62 GMM events 44 GMM State 24 GPRS block decode error rate 23 GPRS block retransmission rate 23 GPRS Cell Ranking Criterion (C32) 13 GPRS Data data view (no. 3.2) 21 actions in 23 GPRS data transfer rate 23 GPRS Info data view (no. 3.3) 24 GPRS Network Mode of Operation 24, 68
81
GPRS Signal Strength Threshold Criterion (C31) 13 GPRS timeslots 21, 29 GPRS, total bytes transferred 23 GPS Bluetooth pairing 47 connect mode 48 connecting and disconnecting 32 fix quality 12, 73 number of satellites seen 12 requirements on GPS device 47 selecting device to connect to 48 synchronizing phone clock with 49 using with TEMS Pocket 47 GPS data view (no. 1.4) 12 GPS menu 47 graphic presentation 5 details 74 GSM AMR data view (no. 3.5) 26 GSM BA List data view (no 2.3) 17 actions in 17 GSM C/I Info data view (no. 3.4) 25 GSM Cell Id data view (no. 2.2) 16 actions in 17 GSM Cells data view (no. 2.1) 13 actions in 14 GSM Serving Cell data view (no. 3.1) 18
H
help, on-screen 5 Home PLMN, time registered in 11 hopping channels 5, 13, 16, 17, 19, 21, 26, 29 Hopping Sequence Number 20 HSN 20
I
icons for events 41 for logfile recording 32
82
Index
Idle mode time spent in (GSM) 11 Ignore Cell Barred 36 IMEI 56 IMSI 56 Info menu 56 invalid parameters, representation of 5
L
LAC 9, 16 last registered 10 presentation format 59 latitude 12 LLC protocol 23, 30 LLC window size 24 Location Area Code 9, 16 Location Area properties 14 Lock ARFCN 35 Lock GSM band 35 Lock GSM cell 14, 17, 35 Lock WCDMA cell 14 Logfile menu 52 logfile recording 52 automatic triggering of 53 icon for 3 starting/stopping manual recording 32 where to save files 52 logfile uploading via FTP 54 Logical Channel 13, 16, 17, 18, 19, 21, 26, 29 longitude 12
M
MAIO 20 MCC 9 last registered 10 Mean Throughput (PDP Context Request) 9, 70 Measure Mode Display 60 memory cards 52 memory full 4, 32 menus 4 default settings in 76 messages (displaying of) 58 MM Cause 71
83
MM events 43 MM/GMM data view (no. 1.2) 10 MNC 9 last registered 10 Mobile Allocation Index Offset 20 Mobile Country Code 9 Mobile Network Code 9 modulation coding scheme on downlink (EGPRS) 29 modulation coding scheme on uplink (EGPRS) 29 modulation method on downlink (GPRS/EGPRS) 22 modulation method on uplink (GPRS/EGPRS) 22 MS-TXPWR-MAX-CCH 14, 16
N
Neighbor Cell BCCH 14, 16 neighbors (GSM) 14, 16, 17 Network Mode of Operation 24 NMO 24 No Service mode time spent in 11 NSAPI 9
O
Operational Mode 31
P
Packet Dedicated Traffic Channel 19, 21, 26, 29 Packet Final Block Timer 24 Packet TMSI 10 Packet Uplink Assignment Timer 24 packet-switched behavior of phone, controlling 62 parameter values 65 Pathloss Criterion (C1) 13 PDCH, time using 11 PDP address (IPv4) 9 PDP Context data view (no. 1.1) 9 PDP Context handling 63 PDP Context Request parameters 69 PDTCH 19, 21, 25, 26, 29 Peak Throughput (PDP Context Request) 9, 69 Pocket menu 4, 33, 34 Power Display 59 Precedence Class (PDP Context Request) 9, 70 PTMSI 10
84
Index
R
RAC 9 last registered 10 RACo 13 Radio Link Timeout 19 RAT, current 9 Receive Bit Error Rate 19, 27 Received Signal Strength Indicator 9 Redial Disconnected Calls 60 Reliability Class (PDP Context Request) 9, 69 Reset All 61 resetting all General settings 61 resetting cell control settings 36 RLC/LLC Decode Errors/Retransmissions, graphic presentation 74 RLC/MAC protocol 23, 30 RLT 19 Roaming PLMN, time registered in 11 Routing Area Code 9 Routing Area Color 13 Routing Area properties 14 RR Cause 70 RR events 45 RR Internal Cause 72 RSSI 9 graphic presentation 75 RxLev 9, 13, 16, 17, 18, 21, 26, 29 Full/Sub values 60 graphic presentation 75 presentation format 59 RxQual 19, 27 Full/Sub values 60 graphic presentation 75
S
Save Logfile To 52 SDCCH 19, 21, 26, 29 serving cell (GSM) 13, 16, 17, 18 Serving Cell Barred 14, 16 Serving Cell BCCH 21, 26, 29 Session events 46 SM Cause 72 SM events 43 speech codec 20
85
speed 12 Stand-alone Dedicated Control Channel 19, 21, 26, 29 Subchannel Number 20 support contact information 64
T
T3168 timer start value 24 T3192 timer start value 24 T3212 timer current value 10 T3212 timer max value 10 T3314 timer current value 24 T3314 timer start value 24 TCH 19, 21, 25, 26, 29 time using 11 Temporary Logical Link Identifier 10 Temporary Mobile Subscriber Identity 10 TEMS Pocket version 56 throughput (GPRS) 23 Time Log data view (no. 1.3) 11 actions in 11 Timeslot Number 19, 26 timeslots used by GPRS 21, 29 Timing Advance 19, 27 TLLI 10 TMSI 10 Traffic Channel 19, 21, 26, 29 time using 11 Traffic Channel Type 21, 26 TxPower graphic presentation 75
U
UE Transmit Power 19, 26 Upload Logfile 54
W
WAP browser data views visibility of 57 WAP browser GPRS data view 28 what was new in TEMS Pocket 5.0 2 whats new in TEMS Pocket 5.1 1
86
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. Ericssons experience and technological leadership give network operators the strong partnership they need and a commitment to quality, accuracy, and success. TEMS Optimization Solutions Making Wireless Better.