TEMS™ INVESTIGATION 14.

1 USER'S MANUAL

This manual is provided by Ascom Network Testing AB without any kind of warranty. Improvements and changes in this description due to typographical errors or inaccuracies in current information, or improvements to programs and/or equipment may be made by Ascom Network Testing AB at any time without notice. These changes will, however, be incorporated into new editions of this manual. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of the copyrighted owner, Ascom Network Testing AB. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders. © Ascom 2012. All rights reserved. Document number: NT12-7002 ver 1.0

Contents

Contents

1. Introduction

1

1.1. Fundamentals of TEMS Investigation 14.1 . . . . . . . . . . . . . . . . . . . . 2 1.1.1. Package Options – Licensing. . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.2. Connectable Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. What’s in This Manual (and What’s Not) . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2. Recently Introduced Features in TEMS Investigation

8

2.1. What’s New in TEMS Investigation 14.1 . . . . . . . . . . . . . . . . . . . . . . 8 2.1.1. LTE Cell Frame Timing IEs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.1.2. Extended Control Functionality and Logging for Sony Ericsson Xperia arc S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1.3. POLQA for CS Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1.4. Cell Whitelists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1.5. Scripted Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1.6. Manual Pinpointing Mode in Pinpoint Window . . . . . . . . . . . 10 2.1.7. Hisilicon LTE Chipset Support . . . . . . . . . . . . . . . . . . . . . . . 10 2.1.8. Via CDMA/EV-DO Chipset Support . . . . . . . . . . . . . . . . . . . 10 2.1.9. New Connectable User Terminals . . . . . . . . . . . . . . . . . . . . 10 2.1.10. New Connectable Scanners. . . . . . . . . . . . . . . . . . . . . . . . 11 2.1.11. LTE RRC Redirection Events. . . . . . . . . . . . . . . . . . . . . . . 11 2.1.12. New LTE Information Elements . . . . . . . . . . . . . . . . . . . . . 11 2.2. What Was New in TEMS Investigation 14.0 . . . . . . . . . . . . . . . . . . 11 2.2.1. Control Functions for Smartphones . . . . . . . . . . . . . . . . . . . 11 2.2.2. New Logfile Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.3. Speech Quality Measurement with POLQA . . . . . . . . . . . . . 13 2.2.4. Searching, Filtering, and Highlighting in Message Windows. .13 2.2.5. Expansion of Scanning Capabilities . . . . . . . . . . . . . . . . . . . 13 2.2.6. Improved Service Testing Capabilities . . . . . . . . . . . . . . . . . 14 2.2.7. Logfile Export Enhancements . . . . . . . . . . . . . . . . . . . . . . . 14

NT12-7002 ver 1.0

i

TEMS Investigation 14.1 User’s Manual

2.2.8. Improved HASP Soft License Handling . . . . . . . . . . . . . . . . 14 2.2.9. New Connectable User Terminals in TEMS Investigation 14.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3. What Was New in TEMS Investigation 13.1 . . . . . . . . . . . . . . . . . . 16 2.3.1. Alternative Mobile-to-mobile AQM Solution . . . . . . . . . . . . . 16 2.3.2. CS Fallback Events and Information . . . . . . . . . . . . . . . . . . 16 2.3.3. Extended Set of LTE RACH Information Elements . . . . . . . 16 2.3.4. Improved Handling of Qualcomm-based LTE Devices . . . . 17 2.3.5. CDMA/EV-DO Rev. B Measurement and Analysis . . . . . . . 17 2.3.6. New Connectable User Terminals in TEMS Investigation 13.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.3.7. WCDMA Scanning with Rohde & Schwarz . . . . . . . . . . . . . 18 2.3.8. CDMA Scanning with PCTel SeeGull MX . . . . . . . . . . . . . . 19 2.3.9. New Connectable Scanners in TEMS Investigation 13.1 . . 19 2.3.10. Software Update Service . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.3.11. Enhancements in TEMS Investigation 13.1.1 . . . . . . . . . . 19 2.3.12. Enhancements in TEMS Investigation 13.1.2 . . . . . . . . . . 20 2.4. What Was New in TEMS Investigation 13.0 . . . . . . . . . . . . . . . . . . 21 2.4.1. TD-LTE Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4.2. Data Service Performance Verification with Generic Device. 21 2.4.3. Selection of Preferred Workspace at Startup. . . . . . . . . . . . 22 2.4.4. New Utility for Sharing Script Configuration Settings . . . . . . 22 2.4.5. New LTE Information Elements . . . . . . . . . . . . . . . . . . . . . . 22 2.4.6. New Connectable Equipment in TEMS Investigation 13.0 . 22 2.4.6.1. UMTS Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.4.6.2. LTE Scanner: Rohde & Schwarz TSMW . . . . . . . . . 23 2.4.7. Support for SSH2 Protocol in Iperf Testing . . . . . . . . . . . . . 23 2.4.8. Support for 64-bit Windows 7. . . . . . . . . . . . . . . . . . . . . . . . 23 2.4.9. Performance Improvements. . . . . . . . . . . . . . . . . . . . . . . . . 24 2.4.10. Additional New Features . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.4.11. New Features in TEMS Investigation 13.0.1 . . . . . . . . . . . 24

3. Basics of TEMS Investigation

26
26 26 26 26

3.1. Recommended Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2. Installing TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3. Starting TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4. Quick Guide to the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . .

ii

Contents

4. User Interface

29

4.1. User Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.2. Workspaces and Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2.1. Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2.1.1. Opening Workspaces from a Command Prompt. . . . 31 4.2.1.2. Predefined Workspaces . . . . . . . . . . . . . . . . . . . . . . 31 4.2.2. Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.3. The Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.1. Record Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.2. Replay Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.3.3. Report Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.3.4. File and View Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.4. The Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.4.1. Help Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.4.2. “Play” Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.4.3. “Record” Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.5. The Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.6. Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5. The Navigator

36

5.1. Equipment Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.2. Menu Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.3. Info Element Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.3.1. Presentation Attributes of Information Elements . . . . . . . . . 37 5.3.2. Editing the Color Ranges of Information Elements . . . . . . . 37 5.3.2.1. Automatic Setup of Color Ranges . . . . . . . . . . . . . . . 38 5.3.2.2. Manual Setup of Color Ranges . . . . . . . . . . . . . . . . . 39 5.3.3. Editing the Marker Sizes and Symbols of Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.4. Logfile Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.5. Worksheets Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6. Cell Data

41

6.1. Creating a Cell File in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.2. Creating a Cell File in CEL Format . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.3. Loading Cell Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.4. Loading Cell Data from Mentum CellPlanner . . . . . . . . . . . . . . . . . 42

NT12-7002 ver 1.0

iii

TEMS Investigation 14.1 User’s Manual

6.5. Use of Cell Data in Presentations . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7. Managing External Equipment: General

44

7.1. Connectable Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.2. Overview of User Interface Components Dealing with External Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8. Activating External Equipment

46
46 47 47 47 48 48 48 48 48 48 49 50 50 50 51 51 51 51 51 52 52 53 55 56 57 58 58 58 59

8.1. Plugging In External Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1. Plugging In Phones and Data Cards . . . . . . . . . . . . . . . . . . 8.1.2. Plugging In Ericsson Fixed Wireless Terminals . . . . . . . . . . 8.1.3. Plugging In Scanners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.4. Plugging In GPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.5. Plugging In Equipment Cases . . . . . . . . . . . . . . . . . . . . . . . 8.1.6. Plugging In Stand-alone AQM Modules. . . . . . . . . . . . . . . . 8.2. Starting TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3. The Navigator Equipment Tab: Basics . . . . . . . . . . . . . . . . . . . . . . 8.3.1. Top Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.1.1. Device Context Menu . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2. Bottom Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2.1. “Activities” Subtab . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2.2. “Information” Subtab . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.3. Detection of Equipment: Special Cases. . . . . . . . . . . . . . . . 8.3.3.1. Detection of PCTel SeeGull EX Scanner . . . . . . . . . 8.3.3.2. Detection of PCTel SeeGull MX Scanner . . . . . . . . . 8.3.3.3. Detection of DRT Scanners and Rohde & Schwarz TSMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.3.4. Detection of HTC Touch Pro2 Phones . . . . . . . . . . . 8.3.3.5. Detection of Equipment Not Covered by License . . . 8.3.3.6. Detection of Network Adapters . . . . . . . . . . . . . . . . . 8.3.4. User-assisted Detection of Devices . . . . . . . . . . . . . . . . . . . 8.3.4.1. Mapping Device Ports to Interfaces . . . . . . . . . . . . . 8.3.4.2. Qualcomm Devices with LTE/TD-LTE Capability . . . 8.3.4.3. LG and Samsung Devices with LTE Capability. . . . . 8.3.4.4. Data Service Testing with Arbitrary Devices . . . . . . . 8.4. Activating and Deactivating External Equipment in TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.1. Activating External Equipment . . . . . . . . . . . . . . . . . . . . . . . 8.4.2. Deactivating External Equipment . . . . . . . . . . . . . . . . . . . . .

iv

Contents

8.5. Managing GPS Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 8.6. Further Features of the Navigator’s Equipment Tab . . . . . . . . . . . . 61 8.6.1. The Refresh Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 8.6.2. Re-pairing Phones with AQM Modules . . . . . . . . . . . . . . . . 61 8.6.2.1. Details and Limitations of the Re-pairing Function . . 62 8.6.3. Device Detection Properties. . . . . . . . . . . . . . . . . . . . . . . . . 62 8.7. Saving of the Equipment Configuration. . . . . . . . . . . . . . . . . . . . . . 63

9. Operating and Controlling External Equipment Manually

64

9.1. Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 9.1.1. Control Function Support by Device. . . . . . . . . . . . . . . . . . . 65 9.1.2. Functions of Dialog Buttons . . . . . . . . . . . . . . . . . . . . . . . . . 66 9.1.3. Access Class Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 9.1.4. AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 9.1.5. Band Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 9.1.6. BLER Target (WCDMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 9.1.7. Cell Barred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 9.1.8. Cell Lock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 9.1.8.1. Cell Lock in GSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 9.1.8.2. Cell Lock in WCDMA. . . . . . . . . . . . . . . . . . . . . . . . . 70 9.1.9. Nonvolatile Item Read/Write. . . . . . . . . . . . . . . . . . . . . . . . . 72 9.1.10. PESQ Device Pairing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 9.1.11. PLMN Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 9.1.12. Radio Access Technology Lock (Lock on RAT) . . . . . . . . . 74 9.1.12.1. RAT Lock vs. Technology-specific Control Functions: Sony Ericsson . . . . . . . . . . . . . . . . . . . . . . . . . 76 9.1.12.2. RAT Lock vs. Technology-specific Control Functions: Nokia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 9.1.13. RRC WCDMA Capability Control . . . . . . . . . . . . . . . . . . . . 77 9.1.14. Speech Codec Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 9.2. Voice/Video Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 9.3. Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 9.3.1. Presentation of Data Service Testing. . . . . . . . . . . . . . . . . . 78 9.4. Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

10. The Status Control Monitor

80

10.1. Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 10.2. Positioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

NT12-7002 ver 1.0

v

TEMS Investigation 14.1 User’s Manual

10.3. Service Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4. Computer Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5. Logfile Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.6. Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

81 82 82 82

11. Logfiles

83

11.1. Recording Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 11.1.1. Inserting Filemarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 11.1.2. Further Recording Options. . . . . . . . . . . . . . . . . . . . . . . . . 85 11.1.3. Positioning Logfiles by Pinpointing in the Map Window . . . 86 11.1.3.1. Basic Pinpointing Procedures . . . . . . . . . . . . . . . . . 87 11.1.3.2. Advice on Pinpointing and Recording . . . . . . . . . . . 88 11.1.4. Buffering in Connection with Logfile Recording . . . . . . . . . 88 11.2. Loading Logfiles for Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 11.2.1. Opening a Logfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 11.2.2. Logfile Metadata and Statistics . . . . . . . . . . . . . . . . . . . . . 90 11.2.2.1. “General” Subtab . . . . . . . . . . . . . . . . . . . . . . . . . . 90 11.2.2.2. “Equipment” Subtab . . . . . . . . . . . . . . . . . . . . . . . . 91 11.2.2.3. “Activities” Subtab . . . . . . . . . . . . . . . . . . . . . . . . . . 92 11.2.2.4. “Statistics” Subtab . . . . . . . . . . . . . . . . . . . . . . . . . . 93 11.2.3. Loading Logfile Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 94 11.2.3.1. Play Section of Status Bar . . . . . . . . . . . . . . . . . . . 94 11.3. Loading Logfiles from Other Sources . . . . . . . . . . . . . . . . . . . . . . 94 11.4. Viewing Logfile Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 11.5. Logfile Transfer via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 11.5.1. Setting Up Logfile Transfers . . . . . . . . . . . . . . . . . . . . . . . 95 11.5.1.1. FTP Server Settings . . . . . . . . . . . . . . . . . . . . . . . . 96 11.5.1.2. Logfile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 11.5.1.3. Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 11.5.1.4. Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 11.5.2. Starting Logfile Transfers. . . . . . . . . . . . . . . . . . . . . . . . . . 98 11.6. Exporting Logfiles in Other Formats . . . . . . . . . . . . . . . . . . . . . . . 98 11.6.1. Preparing an Export Order. . . . . . . . . . . . . . . . . . . . . . . . . 99 11.6.2. Specifying the Contents of Export Files . . . . . . . . . . . . . . 100 11.6.2.1. Selecting Information Elements to Export . . . . . . . 100 11.6.2.2. Text File Specific Settings. . . . . . . . . . . . . . . . . . . 102 11.6.2.3. MapInfo Specific Settings . . . . . . . . . . . . . . . . . . . 104 11.6.2.4. ArcView Specific Settings . . . . . . . . . . . . . . . . . . . 105 11.6.2.5. Marconi Planet Specific Settings. . . . . . . . . . . . . . 106 11.6.2.6. Ethereal (Wireshark) Specific Settings . . . . . . . . . 106

vi

Contents

11.6.2.7. MDM Specific Settings . . . . . . . . . . . . . . . . . . . . . 106 11.6.2.8. Saving and Loading Export Setups . . . . . . . . . . . . 106 11.6.3. Executing Export Orders . . . . . . . . . . . . . . . . . . . . . . . . . 107 11.6.4. Command Line Controlled Logfile Export. . . . . . . . . . . . . 107 11.6.4.1. Mandatory Command Line Switches. . . . . . . . . . . 107 11.6.4.2. Optional Command Line Switches . . . . . . . . . . . . 108 11.6.4.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 11.7. Merging Uplink AQM Data into Logfiles (UMTS). . . . . . . . . . . . . 110 11.7.1. Retrieving Uplink AQM Data . . . . . . . . . . . . . . . . . . . . . . 110 11.7.2. Preparing and Performing a Merge . . . . . . . . . . . . . . . . . 111 11.8. Generating Logfile Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 11.8.1. IE Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 11.8.2. Events Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 11.8.3. Mobiles Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 11.8.4. Scanned Channels Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 116 11.8.5. User Details Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 11.8.6. Saving and Loading Report Setups . . . . . . . . . . . . . . . . . 118 11.8.7. Generating the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 11.8.8. Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

12. The Pinpoint Window

120

12.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 12.2. Creating Planned Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 12.2.1. Opening a Map Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 12.2.1.1. Supported File Formats Holding Map Sets . . . . . . 120 12.2.1.2. Map Set Metadata Shown in Pop-out Pane . . . . . 121 12.2.2. Map Handling and Controls . . . . . . . . . . . . . . . . . . . . . . . 122 12.2.3. Creating a New Route . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 12.2.4. Editing a Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 12.2.5. Deleting a Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 12.2.6. Unloading a Map Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 12.3. Walking Planned Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 12.3.1. Loading and Walking a Route . . . . . . . . . . . . . . . . . . . . . 126 12.3.2. Repeating Parts of a Route . . . . . . . . . . . . . . . . . . . . . . . 129 12.3.3. Skipping Waypoints of a Route . . . . . . . . . . . . . . . . . . . . 130 12.4. Pinpointing Without a Planned Route . . . . . . . . . . . . . . . . . . . . . 130 12.5. Relation to Other TEMS Investigation Functions . . . . . . . . . . . . 132 12.5.1. Data Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 12.5.2. Coexistence Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

NT12-7002 ver 1.0

vii

. 13. Setup of Pilot Scan: Sony Ericsson. . . . Scanning Methods and Capabilities . . . . .3. . . . . . . . . . . . Recording Scan Data Manually . . . . . . . . . . . . . . 15. . . . . . . . . . . . WCDMA Scanning 144 144 146 146 146 148 150 151 152 153 153 154 157 15. . 13. 14.2. . . . . . . . . . . . 14. . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . .10.2. . .1. Setup of Pilot Scan: General . . . . . . . . . . . . . . . . . . . . . . .9. . . . . . . . . Setup of RSSI Scan: Sony Ericsson. . . . 13. . . .TEMS Investigation 14. . . . . . . Presenting Scan Data . . . . . . . . . 14. . Presentation: “CPICH Data” Status Windows . .2. . . . . . . .2. . . . 15. .2. . . . RSSI Scanning . 13. . . Presentation: Synch Channel Data Window . . . . . . . .1. . . . . . . . . . . . . . . .2. .3. . . . . 13. . . . .2. . 13. .2. . . . . . . . . Setup of Pilot Scan: Anritsu . . viii . . . . .5. .5. . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . 14. . . Notes on GPS Units in Scanners . . . . . . . . . .1. . . . . .3. . . . 15. . .2. . . . . . . .2. . . . . . . . . . . . . . . Setup of Pilot Scan: Rohde & Schwarz TSMW . . . . . . . . . . . . . . . . . . . . . . .3. . Spectrum Analysis .5. .8. . . . . . . . . . . . . . . .4. . . . . . . . . . . . . Notes on Scanner Multitasking . . . . . . . . 14. . . .1. . . . . . Presentation: “CPICH Scan” Bar Charts . . . . .2. . . . . . . .6. . .2. . . . . . . . . . . . . . . SRU . . GSM Scanning 139 139 140 140 140 141 142 143 143 14. . . . . . . . . . . . . . . . .2. . . . DRT Scanners . . . . .5. . . . . 13. . . . . . . . . . . . . .2. . Scanning: General 134 134 135 135 135 136 136 136 137 137 137 137 138 138 13.1 User’s Manual 13. . . . . . .4. . . . 15. . . . Scanning Methods and Capabilities . . . 15. .2. 15. . Setup of Pilot Scan: PCTel . . Setting Up a Scan Manually.1. . . . . . 15. . . 15. . . . Rohde & Schwarz TSMW . . 15. . . . . . . . . . . . . . . . . . . . . . . Setup of RSSI Scan: PCTel SeeGull . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . Presentation: General . . . . . . Technical Data on Scanning Devices . . . . . . . . . . . . . . . SRU . . . . . . . . . . . . .5.2. . . .4. . Setup of RSSI Scan: General Settings . .3. . . . Pilot Scanning (with SCH Scanning). . .5. . . . . .2. . . . . Manual Scanning . . . . . . . 13. . . . . . . . 13. . . . . . . . . . . . . . Setup of RSSI Scan: Rohde & Schwarz TSMW . 13. .5. . . . . . . . . . . . . 14. . .2. . . Scripted Scanning. . . .2.1.2. . .2. .1. 15. . 13. . Presentation: “CPICH Scan” Line Charts. . . . . . . . . . . . Performing a Scan Manually .2. . . . . Sony Ericsson Phones and SRUs . . 15. .2. 13. . . . . . . . . . . . . 14. . .6. . . . . . . . .7. . . . .3. . . . . . . . 15. . . PCTel Scanners. . . 14. . . . . . . . . . . . Presentation of RSSI Scanning . . .

. 166 16. . . . . . . . . .2. . . 168 16. . . . . . . .2. . . . . . . . . . . . . . . Customizing the Presentation . . . . . . . . . . . . . . . 177 16. .1. .8. . . . . . . . SCH Timeslot Scanning . . . . . . . . . . . . .5.6. Setup of SCH Timeslot Scan . . . . . . . . .3.2. . .2. .3. .5. . . . . . . . . . . . . . . . Presentation: Spectrum Analysis Bar Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . .1. . . .1. . 176 16. . . . . . 168 16. . .1. . . 158 15. . . . . . . . . . .6. . 159 15.3. . . . . . . . . 165 15. . . 163 15. . . .1. . . . . . . . . . . . . . .Contents 15. . . . . . . 164 15.1. .6.1. . .2. . . . . . . . .13. . . . . . . . . . . . .4. . . . . . . . Presenting Scrambling Codes from Multiple UARFCNs . . . . . . . . . . 163 15. . . . . 158 15. . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 16. . RSSI Scanning . . . . . . . . . . . . . . .1. . . . . . . . . . .2. . . . Context Settings . . . .6. . . . . . .5. . . . . . . . . .4. . . . . . . . Customizing the Presentation . . 174 16.1. . . . 162 15. . . . . . . . . . . . . . Setup of LTE Signal Scan: General . . . . . . . . 159 15. 161 15. . 158 15. . . . . . . . . . .2. Presentation: BCH Scanning . . . . . . .2.6. . . . . . . . . . . . . . . . . .1.2. . . . 2. 165 15. . Setup of LTE Signal Scan: Andrew . . . . . . LTE Scanning 167 16.13. . . . Setup of LTE Signal Scan: Rohde & Schwarz TSMW . . . .2. .1. . . Spectrum Analysis. . . . Setup of RSSI Scan . . . . . . . .3. .5. . . . . . . . . Setup of LTE Signal Scan: Transcom . .1. . . . . . . . . . . . . . . . Presentation of LTE Signal Scan . . . .2. . General Settings . . 160 15. .4. . Presentation: RSSI Scan Bar Chart . . . . . . . . . 175 16. . . . . . . . . . .2. . . . . . . . . . . . . .1. . . . . . .1. . . . . Context Settings . . . . .4. . . . . . . Presentation: SCH Timeslot Scan Bar Chart . . 159 15. . .2. . 169 16. . . . . . . . . . . General Settings . . . . . Sorting of Cells . . . . . . . . .2. UARFCN Ranges (“Interval 1.2. . .2. . . . . . . . . . . . . . . Context Settings . . . . . . 163 15. .1. . .5. . . . Setup of Network Scan. . . . . . . . .12. .2. . 159 15.11.1. . . . . . Presentation: Network Search Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . . 177 NT12-7002 ver 1. . . . . . . . .0 ix . . Sorting of Scrambling Codes. . .4. 160 15. . . . . . . . Context Settings . .1.2.1. . . . . 3”) . . .3. . . . . . . . . . . .6. . . 161 15. . . . .2. . General Settings . 162 15. . . . . . . . .5. . . . . . Presentation: “Finger Info” Status Windows. . . . . .2. . 158 15. . . . . . . . .2. . . .4. . . . . . . . . . . . . . . . . . . . . .2. . 165 15. . . . . Scanning Methods and Capabilities . . . . . 161 15. . .8. . .2. . . . . . .13. . . . . . . . .1. .1. . . 165 15. LTE Signal Scanning. . . . . . . . . . . . . . .6. . . . . . . Setup of LTE Signal Scan: PCTel . . . . . . . Network Scanning .1. . 172 16. . . . . . 169 16. . . . . . . .3. 164 15. . . . . . . . . . . General Settings . Setup of Spectrum Analysis Scan . . . . . . . . . . 163 15. . . . . . . . Setup of LTE Signal Scan: DRT. . . . . . . . . .2.

. . . . . . . . . . Pilot Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . Presentation of Enhanced Power Scan . RSSI Scanning . . 16. . . . . . . . . . . . . . . . . . . . .4. . . . . 17. . . . . . . . .4. Customizing the Presentation . . . . .3. . . . .3. . . .3. Setup of RSSI Scan: General . . . . . .4. . . 18. . . . . . . . 18. . . .1 User’s Manual 16. . .3. . .1. . .5. . . . . . . 18. . . .1. . . .2.1. . . . 18. . . .2. . .2. . . . . . . . . . . . . . . . . . . 16. . .1. . . . . . . . . Setup of RSSI Scan: DRT . . . . . . . . 177 177 178 178 178 178 178 178 179 179 179 179 180 180 180 180 181 17. . . . . . . . Enhanced Power Scanning.3. . . 16. . 16. . . 17. . . . . . . . . . General Scan Settings .5. . . .TEMS Investigation 14. Sorting of Pilots . . . . . 16. . . . . . . . . . . . . . . . . . . . . . . . .4. . . .2. . Scanning Methods . . . . . . . . . . . . . . Setup of Spectrum Scan: DRT. . . . . . 16.3. . . . .1. . 16. . . . . . . . . . . . . Setup of RSSI Scan . . . . . . . . . . .4. . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17. . . . . . . . . . Setup of RSSI Scan: PCTel . . . .4. . . . . . . . .4. . . . . . .2. . . . 18. . .3.5. . . . . . . . . . . . . . . . . . . Spectrum Scan Presentation .3. . . Setup of Pilot Scan . Spectrum Scanning. . 18. Setup of Spectrum Scan: General . . . . . 17. . . . . . 18. . . . . . . .5. . . .3. General Scan Settings . . . . . . . . . . . . . . . . . . . . . . . . .1. . . .3. . . . Sorting of Cells .4. . . . . . . . . . . . . . . . . . . . . . . . CDMA Scanning 186 186 187 187 187 188 192 192 192 192 18. . . . . . 16. . . . .5. . . . . . . . . . . Pilot Scanning . . . . . . .2. . . Setup of Spectrum Scan: PCTel . . . . . . . .3. . . . . .2. . . . . . . . .3. . . . . . 16. . . Setup of RSSI Scan: Transcom . . . . . . . . . Presentation: Strongest Scanned PN Bar Chart . . . . . . . . . . . . . . . . 18. .3. . Presentation: “PN Scan” Bar Charts . . . . . 17. . . x . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . 16. . .4. . . . . . . . . . . . . . . . . . TD-SCDMA Scanning 182 182 182 183 183 184 184 185 185 185 17. . Scanning Methods . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . Presentation of RSSI Scan . . . . . . . 17. . . . . . . . . . . . .3. . 16. . . Setup of Enhanced Power Scan . . Setup of Enhanced Power Scan: General . . . . . .1. . . . Setup of Spectrum Scan: Andrew . 16. .3. . . . . . . . . . . . . . . . . . . . .2. . . . .5. Presentation of Pilot Scan . . . . . . . . . . . .5. . .4. . . . . . . . . . . . . . . . . . . . . . . . .5. . . . .6. . . 18. . Presentation of RSSI Scan . . . . . . . . . . . . . 17. . . . . . . . . . . . . . .4. . . . . . Setup of Spectrum Scan: Transcom . . . . . . .3. . . . .3. . . . . . . . . . . . 16. . . . . . . . . . . . .3. . . . .2. . . RSSI Scanning .3.4. . . . . . . . . . . . . . . . . . . . . 16. . . . Setup of Pilot Scan: PCTel . . . . . . . . . . . . . . . 17. . . . . . . . . . . . . .1. .3. . . . Setup of Pilot Scan: Andrew . . . . . 16. . 16. . . . . .

. . . . . . . . . . . . . . . . . . . .1.10. . .5. . . . . . . . . . . . . 198 19. .6. . . . . . . . . . Spectrum Analysis. .5. . . . . Setup of Spectrum Analysis Scan . . . .Contents 18. . . . . . . . . . . .2. . . . . . . . . . . . . . .6. . . . . . .2. . 194 18. RSSI Scanning . . 194 18. . . . . . . . . . Presentation: RSSI Scan Bar Chart . . . . . . . . . . . . 212 20. . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . Presentation of Spectrum Analysis Scan . . . . . . . . 210 20. . . . . . . . . . . . . . . . .1. . . . . . . . . . . . 201 20. . . Supported Services by Cellular Technology . . . .5. . . . .6. . . . .1. . . . . . . .10.8. . . . . . . . . . . . 194 18. . . . . .1. . . . Context Settings . . .3. . 193 18. . . . . . . . . . . . . . . Setting Up a Network Connection . 194 18. . . Setup of Spectrum Analysis Scan . . . .7. . . . . .3. 193 18. . . . . . . . . . . . . . Preamble Scanning . . . . . . . . . . . . . . .1. . . . Setup of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scanning Methods. . . . . . . . . . . . . . . 196 19. Service Control 203 20. . . . . . . .1. . . . . . . . . . . .1. . . Basics of Creating Scripts (with Voice) .1. 201 19. . . . . . . . . . . . . . . . . . . . . 203 20. . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . 197 19. . . . 213 20. . . . . .1. . . . . . . . . . . . . . . . . . 195 18. . . . 204 20. . . . . . . . Presentation . . . . . . Setup of RSSI Scan .4. . . . . . . . . . . . . . . . . . . . Workflow Control Structures . . .9. . . . . . . . . . . . . . . . . . . 201 19. . . . . Introduction to Service Control . . . . . . . . . . . . . . .1. . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 20. . . . . . .2. . . . . .4. . RSSI Scanning . . .1. . . . . . . . . .5. . 203 20. .2. . . . . . . .0 xi . . . . . . . . . . . . . . . Interference Offset.5. . . . . . . . . . . . . . . . . .6. . Context Settings . . . Snippets . . Sequences . . . . . 201 19. . .5. . . . . Spectrum Analysis. . . . . 194 18. . . . General Settings . . . Setting Up a Data Service Activity. . . . .6. . . . . . . . . General Scan Settings . 204 20. . .1. . . . . . . . . . . . . . . . . . . . . . . . . . .5. .6. . 196 18. . . . . . . . . 214 NT12-7002 ver 1. . . . . . . . . . . . . . . . . . . . Setup of Narrowband Interference Scan . . . . . . .2. . . . . . . . . . . . . . . . . .2. . . . . . . .4. 198 19. . . . . . . .4.1. . . . . . . . . . Narrowband Interference Scanning. . . . . . . . . . . . . . . . . . . . . . . 193 18. . . . . . .2. . 195 18. . . . . . . . . . . .5. General Settings . . . . . .4. . . . . . . . Stand-alone PS Attach and Detach. . . Capabilities of Devices . . . .3. . . Setup of Preamble Scan . . . . . . . . . . . . . . 201 19. . . . . 197 19. . . . . . . . . . . . 209 20. . . . . 194 18. . . . . .5. . . . . WiMAX Scanning 197 19. . The Service Control Designer . . . . . 214 20. . . . . . .1. . . . . Presentation: Narrowband Interference Scan Bar Chart . . . . . . . . . .6. 195 18.

5. . . . . . . . . . . . . 20. . . . . .16.1. . . . Waiting For a Given Outcome of an Activity . . . .15. . . . . Example 2: Concurrent Activities on Different Devices . . .3. . . .1. . . . . . . . . . . . . . . . . . . .11. . . . . . . . . 20. . . . . . . 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20. . . . . . . . .10. Waiting For a Scheduled Point in Time. . .10. . . . .4. . .12. 20.15. Wait For . .10. . . . . . . . . . . .6. . . . . . . . . . . . . .1. . . 20. 20. .1. . . . . . . .3. .8. . . . . Suppressing Parts of a Script . . . .4. . 20. . . . . .14. . Deactivate . . . . . . . . . . . . . . Windows 7/Windows Vista and IPv6. . . . . . . . 20. . Editing Workflows and Script Settings . . . . . .10. . . . . . . . 215 216 218 218 219 224 225 226 226 227 228 229 230 230 231 231 232 232 232 233 233 233 233 234 234 235 236 236 236 236 236 236 237 237 237 237 237 238 xii .1. . . .16. . . .5. .16. .7. . . . .2. . . . . . . . . . . . . . . .9. . . 20. . . 20. . . 20. . . . . . . . . . .3. . .2. . . . . . . . . Wait For with Periodic Events . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . .10. . .1.16. . . . . .2. . . . . 20. . . . . . . . . . . . . .1. . . . . . Parallel Activities . . . . . . .1. . 20. . . . 20. . . . . . .1. . . . . . Monitoring Equipment Status . . .16. . . . 20. . . . . Activity Properties That Control Execution . . 20.6.6. . . 20. . . . . . . . . . . . . . . . . . . . .4. 20. . 20. . .6. . . . .4. . . . 20. . .1. Notes on Script-controlled Logfile Recording . . . . .10. . . .8. .3. . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . .10. Start Recording . . . 20. . . . . . . . . . . . . . . . . . . . . . . . .3. . . Example 1: CS Voice/Video – Caller and Receiver . . . 20. . . . . . . .10. . . . . . Validating Scripts . . . . . . .1. . .2. . . . . . . Presentation of Data Service Testing . . .10. . . . . . .16. .15. . . . . . . . . . . . . . . . Run Script . . .16. General Aspects of Script Execution . .16. . . Preparations. . . Wait . . .7. 20. . . . . . . . . . Example 3: Concurrent Activities on the Same Device . . . .15. . . . . . . . . . . . . .5. . . . .1.1. . . . . . . . . . . Band Lock . . .13. . . . Terminate. . . . . . . . . . . . . . . . . . . . . . . . .16. . . . . . .15.TEMS Investigation 14. . .3. . . . . . . .10. . . . Control Activities . . . . . . . . . . 20. . . . . . . . . . . . . . . . . . . . . .15. . . . . . . Filemark . . . . Running Scripts from the Service Control Designer . . . . . . . .15. . . . . . . . . 20. . . Activate . .6. . . . . . . . .16. . . . . . . . . . . . . . . . . . 20. . . . Running Scripts from the Service Control Monitor . AT . While Loops . . 20. . . . .1 User’s Manual 20. . . . . . . . . 20. 20.15. . .2. . . . .15. . . . . . . . . . . . . . 20. . . . . . .15. . . . Stop Recording . . . . . . . . . . . . . If–Else Constructs .10. . . . . UE Control Functionality . . . . . . . . . . . . . . . . . . . . . . . .1. . . . 20. . . . . . . . .3. . . . . . . . . . .6. 20. . . 20. . . . . . . . . . . Running Scripts. .4. . . 20.16. . . . . .4. . . Radio Access Technology Lock . . . . . . . . . . . . . . . . . . . . Activities (Reference Section). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20. . . . . . .2. . . . . . . Viewing Statistics on Script Execution . . . . . .1. . . . . . 20.10. . . .10. .

.4. .16. . . . . . . . Ping . . . 247 20. . . . . . . . .1. . . . . 239 20. . . . . . . MMS Send. . . . . . . . . . . Predefined Snippets for Scanning. . . . . FTP Upload . . E-mail Send. . . . . . . . . . . . . . . . . . . . SIP Unregister . 258 20. . .6. . . . . . . . 258 20. . E-mail Receive . . .16. . . . . . . . .2. . . . . . .7. . . Predefined Snippets for Messaging . . . . . . . . . . . . . .13.16. . . . . .16.8. . . . . . . . . . . . . . . . . . . . . . . .2. . Start IP Sniffing .3. . . 250 20.2. . . . . .16. . Parallel . . . . . . . . . . . . . . . . . . . . . . . .2. . .15. . .16. . . . . . .12. . . . . . . . . . . . . . . . . . .16.14. . 243 20. . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . .5. . . . . . . . . . . . . Network Bandwidth (Iperf Testing) . . . 240 20. . . . . . .7. .3.7. . 261 20. . . . . . .3. . 262 20. . .3. . 248 20. . . 264 20. . . UDP. 238 20. .16. Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16. .16. . . .3. . . . . . . . . 264 20. . . . .16. . . .2. . . . . . . . . . . . . . . . . . . Messaging Activities. . . .3. . .16. . . . . . . . . 240 20.16. 264 20. . Network Disconnect . WAP Streaming. . . . . . 252 20. . . . . . . . . . . .2. . . . . . .4. . . . . . .16. . . . . . .4. .3. . . . . . . . . . . . . . . . . . .3. . . . . . . . .16.3. . . . .5. . .4. . . . . . . SMS Receive. .4. . . . . . . . . . . . .5. . . . . . . . . . . . . . . . . 260 20. SMS Send . . . . . . . . . . . .4. Stop IP Sniffing .0 xiii .5. . . . . . . . . .16. .16. . . .3. . . . . . .16. . . . . . . . . . . . . . . . . . 240 20. . . . 262 20. . . Control Flow Activities . . . . IP Activities. .16. . .4. . . .16. . . . . . . . . . . . . . . .16. . 262 20. . . . . . . . . . .6. . . . . . .2. . . Terminate . . . . . . . . . . Video Dial . . .3. . WAP Get . . . . . . . .16. . . . . . . .6. . .16. . .8. . . . . . . . . . .16. . . 247 20. . . . . . . . .2. . 249 20. .16. Video Activities . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . .9.3. . . . . . . . . . . . . . . . . . . . 264 20. . . . . . . . . . . . . .1. . . . . . . .1. . . 238 20. . . . . .16. . . . 254 20. .4. . . . 248 20. . . . . .16. .3. . . . . . . . . . . . . . . .4. . . Network Connect. Streaming . . .2. . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . 265 NT12-7002 ver 1. .16.16. . . . . . . . .16. .3. . . . . .1. . . . . . . . . . .4. . . . . . . . . . . . . . . . . . FTP Download. . . . . 240 20. . . . . . . . . . . . . . 264 20. HTTP Get . . . . . . . . . .4. . . . . . . . . . . . . . . .2.2. . . . . . . . . . . .16. . . . . . . . . . .5. .16.3. .16.4. . . . . . 253 20. . . . . .16.16.Contents 20. . . . .3. . . . . .6. . . . . . .6. 239 20. . .3. . . . . . . . . . . . . .11. .5. . . 254 20. . .16. . . .16. . . PS Detach . . . . . . . . . . . . . . . . . . . . . 258 20. . . . . . . . . . . . 243 20. . . . . . . . . . . . . . . Sequence . . . . . . Hang Up . . . . . . . .3. . . . . . . . . . . . . . . . PS Attach . .16. . . . . . 248 20. . . . . . . . . . . .3. . .16. . . . . . . . . .16. . . . . . . . 256 20. . . .2. . 247 20. Run Script . . . . . . . . . . MMS Receive . . .6.6.16. . .16. . . . . . 259 20. . . . . . . . . . . . . . Scan Activities . . . . . .1. . . . . . . . . . . . . . . . . 249 20. . . . . 240 20. . . . . If–Else . . . . . . . . . . . . . . . . . . . . .16. . . . . . . . . . . . . . . . . . While . 264 20. . . . . .6. . . . . . . . . . .3. . . . . . . Wait For. . . . . . SIP Register . . . . . . 259 20. . . . . . .10. . . . . Answer . Predefined Snippets for IP . .

. 274 20. . . . . . . . . . . Overview of Properties by Device.1. . . . . . . . .7.18. . . . . . . .7. . . . . 21. .6. . 268 20. . . . . . . . . 273 20. . . . . . . Configuration Sets . . . . . . .7. . . . . .20. . . . .10. . . .2. . . Importing Configuration Sets. . . . . . . . . . . VoIP Dial . . .2. . GSM Cell Selection . . . . . . . . . . . . . .7. .20. Exporting Configuration Sets . . . . . . . . 275 21. . .1. .2. . 270 20. . . .19. . . . . . . . . . . . . . GSM Barred Cells . . . . . . . . . . . . . . 270 20. . .3. . . . . . 21. . . .18. . .6. . . Descriptions of Configuration Sets. . .18. . . . . . . . . . . . . 266 20. . .2. . . . . Dial . . . . . . .16.3. 269 20. . . . . . . . . . . .16. . . . . Hang Up . Voice Activities.16. . . . . . .17. .2.8.2. . .3. . .18.16.16. . . . .1. 269 20. . General Activity Properties . . . . .2. . .2. . . . . . . . . . . . . . . . . . .2. .5. Activity Filter. . .16.16. . . . . .2. . . . . . . . . . . . . How to Set Up VoIP Testing .1. . . . . . Failure Handling Section . GSM Adjacent Scan .2. . . . . . . . 270 20. . . . . . . . . . . . . . 272 20. . . . . . .19. . .20. . . . . . . . . . .2.7. . . . . . . . . 271 20. . . . . . . .1. . VoIP Voice Quality .7. . . . . . . .16. . . .2. .2. . . . . Device Properties 277 277 279 279 279 280 280 280 281 282 282 283 21. . . .20. . .17. . . . . .9. . . . . . . . . . . . .2. . . . . . . . . . . . Properties of ST-Ericsson Chipset Based Phones . . . . . . . VoIP Answer .6. . . .4. . . . . . . . .2. . Answer . . . . . . .1. VoIP Hang Up . . . . . . . . . . . . . . . . . . . . 21. . . . . . . . .2. .1. . . . . . . . . . . . . . . . . . .18. . . . . . .3. . . . . . . . . . . . . 267 20. . . . . . . . . . . . .18. . . . . . . .16. . . . . . . . . . . . xiv . . . . . . . . . . .2.5. . . . . . . . . . . . . . . . 267 20. . . . . . . . . .2. . . . .2. . .TEMS Investigation 14. . . Managing Configuration Sets. . Further Functionality in the Service Control Designer Window . . . . . . 21. . . .2.2. . . Saving Workflow as Image . .19. . . . . . . . Predefined Snippets for Voice. . . . . . . . 21. 266 20. . . . . . . . . . . . . . . . 275 20. . . . . . . . .7. . . . .7. . . .7. 21. Extended Reports . . . . . . . . . . . . . . . . . .7. . 275 20. . . . . 271 20. . . . . . . . . . .2. . . . .7. . . . . . . . . Activity Section. . . . . . . . . . . . . .2. Zooming the Workflow Pane . . . . . . . . . . . . . . Tutorial on Porting Scripts between PCs . . . . . . . . Context Menu in Workflow Pane . . . CAS Access Class . . . . . 272 20. . . . . . . . . . . 266 20. . 274 20. . . . 21. . . . . . . . . . . .2. . GSM EDGE Capability . . . . . . . . . . . . . 275 20. . . . . . CAS Speech Codec .17. . . . 268 20. .2. . . . . .6. . . . . . . . Deleting Configuration Sets . . . . . . . . . . . . . .1 User’s Manual 20. . . .1. . . . . . . . . . . . . . . 21. .16. . . . . . 21. . . .16. .16. . . . . . . . . . . . . . . . . . . . . . .4. . . 271 20. . .2. . . Common Controls . . . . . . . . CAS Lock on PLMN . . . . . . . . .7. . . . . . . . AQM Measurement . . . . . . . . . Saving and Loading Scripts . . .7. . . . . . . 268 20. . .1. .2. . . . . . . . . . . . . . . 273 20. . . Predefined Snippets for Video . 266 20. . . . . . . . . . . . . . . . . . . . 268 20. . . . . 21. . .

. . .2. . . . . . . . . . . . . . . . . . 293 22. . . . . . 290 22. . Audio Indications for Events . 287 21. . . . . . . .4. . . Generating Cell Whitelist Events. . . . . . . . . . . . .9. . . 283 21. . . . WCDMA RRC Radio Capability .2. .4. . . . . . . GSM Tx Power . . . .3. . 287 21. . . . . . . . . . . 299 22. . . . . . .1. . . . . . . . . . . . . . . . . . .14. . . Predefined and User-defined Events . . . .1. . .2. . .3. . . .11. . . . . . . . . .3. . . 292 22. . . . . . . . . . 284 21. . .3. . . . . . . . . . . . . . .5. . . 285 21. . . . . . . . . . . . . Activating Audio Indications . . . . . . . . WCDMA Cell Selection . Properties of GPS Units . . .2. . . . . . . . . . . WCDMA Barred Cells . Properties of Qualcomm Chipset Based Devices . Properties of Samsung LTE Modems . .5. . . . . . . . . . . . . . .3. . . . GSM Cell Barring Control. . . . . . . . . . . . . . . . . . .7. . . . . . .7. . . . . 293 22. . 299 22. . . . .13. . . . . . . . . . . . . Adding an Event to the Event Expression . . . . .1. . 300 NT12-7002 ver 1. . . . . . . . . . . . . .5. . . .12. . . 299 22. . . . . . . . . . . . . . . . . . . . .3. 293 22.0 xv . . . . 284 21. . . Muting All Audio Indications . .1. . . . . . . . . .5. . . . . . .3. . . . . . . 297 22. . . . . . 286 21. . . . . . . . . . . . . .3. . . . 292 22. . 287 21. WCDMA BLER Target. . Adding an Information Element Criterion to the Event Expression. . . . Deleting Audio Indications . . . . .5. .5. . . . 289 21. . 285 21. . . . . . Setting Up a User-defined Event. . . . . . . . . . . .3. . . . . Channel Lock Control (GSM) . .1. . . . . . . . . . . .5. Layer 3 Messages . . .3. . . . . . . . .4. 289 22. . . . 284 21. . . . . . . . . . . . . . . . . . 299 22. . . . . .5. . . . . . Example of User-defined Event . .2. . . . Saving and Loading Audio Indications . Adding Audio Indications .2. . . . . . . . . . Presentation of Events . . . . . Editing User-defined Events. . . . Properties of Nokia Phones (NTM3) . . . . . 294 22. Adding a Layer 3 Message to the Event Expression . . . . . . . . . . . .2. . . . .Contents 21. . . . . . . . . . . . . . Deleting User-defined Events. . .2. 290 22. . Properties Specific to Sony Ericsson Xperia arc S. .2. .2. . . . . . . . . . . .3. . . . . . . . .8. . . . . . . . . . . . . . . 287 21. . . . Deactivating Audio Indications . . . . .6. . . . . . . .2. . . . . . . . . . . . . . . .2. . . . . . . .5. . . . . . 299 22.3. . . . . . . . . . . . . . 288 21. . . . .3. . . . . . . . . . . . 297 22. . . . .3. . . .6.2. . . . . . . . . . 288 21. .2. . . . . . 293 22. . GSM Handover . . . . . . . . . . . . . . . 290 22. . . . . . . . . . . . . . Sector Lock Control (WCDMA) . .2.3.2. . . . . . . . . . . . . . . . . Adding an Operator/Delimiter to the Event Expression . . . . . . Editing Audio Indications .10. . 295 22. . .5. . . . . . . . . Events 290 22. . . .4. . . .4. . . . . . . .2. . . . . . . . . .5. .2.6. . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23. . . . .6. . . . . . . . 23. . . . . . . . . . Other Window Properties . . . . . . . . . . . . . . . . . . . . . 24. . . . . . . . . . . . . . . . . . . . 24. .6. . . . . .2. . . . . 23. . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . .2. General Tab . . 25. . . . . . . . .7. . . . . . . .2. Events Tab.4. . . . . . . . General Tab . . . .1. . . . 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages Tab .7. . . . . . . . . . . . .1. . . . Presented Data . . . . . . . Changing Status Window Properties . . .7. . . . . . .2. . . “Set Equipment Number” Function . . . . . . . . . . . . . . . . . . . . . Color Ranges . .1. . . . . . . . . . . . . . . . . Resetting Event Counter Windows . . . . . 24. . . . . . . . . Setting Up Status Window Contents. . Message Windows 317 317 317 318 318 26. Types of Presentation Window . . . . . . Changing Message Window Contents and Properties . . . . . . . . Events Tab. . . . . . Window Tabs . . . . . . . . . .1. . . . . . 24. . . .1. . 23. . . . . . . .5. . . xvi . . .1. . . . . . . . . . Changing Event Counter Window Contents and Properties . . . . . . .3. . . . Window Properties . . . 23. . . . . . . . . . . . . . . . . Presentation: Basics 301 301 301 302 302 303 303 304 304 304 304 23. . . . . . . . . . . . Export/Import of Presentation Windows . . . . . . . . . . . . Status Windows 305 305 305 309 312 312 313 313 314 314 24. . . . . . . . . . Import. . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25. . Window Updating and Synchronization .1. Repeating Columns in Multiple Groups . . . . . . . . . . .1. . . . . . . . . . . . . .3. . . . . . . . . . . . .6. . . . Export. . . . Copying Window Contents . . . . . . . 26. . . . . . . . . . 23. . . . . . . . . . . . . . . . 24. . Changing the Status Window Font Size . . . . . . . . . . . . . . . . . . . . . 24.1. . . . . . . . . . 26. . . . . . . . .1. . . . . . 25.1. . . . . . . . . . . . . .2. . . . . . . . . . . . 26. Event Counter Windows 315 315 315 316 316 316 316 25. . . . . . . . .4. . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . .5. . . . . . . 23.1 User’s Manual 23. . . . . . . . . . . .3. . . . . . . 26. . . . . . 24. . .3. . . . . . . . . . . . . .6. . . . . . 25. . . . . . . . .4. .TEMS Investigation 14. . . . . . . . . 23. . . Non-standard Status Windows . . . . . . .4. . .2. . . . . . . . 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TD-SCDMA Physical Channel Monitor . . . . . CDMA Finger Info . . . . . 25. Device Channels: MS/DC/PS . . . . . . .3. . General . 25. . . . . . . . . . .2. . .1. . . . . . . 24. . . . .

.4. . . . Deleting a Chart . . . . . . . . . . . . . . . . . . . . . . . 325 27. . . . . . . . . 322 26. . . Changing Line Chart Contents and Properties . . . . . . . . . . . . Message Window Catch-up . . . . . . . . . . . . 319 26. . . . . . . . . . .0 xvii . . .4. . 336 29. . . . . . . . . . Exporting the Line Chart Window .3. . . .1. . Troubleshooting Video Streaming . 319 26. . . . . . . . . . . . .3. The Video Monitor . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . 332 29. . .6. . . . . . . . . . 318 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . Changing GPS Window Properties . . 319 26. . . . . . . . . . . . . . . . Freezing a Message Window . . . 327 29. . .7. . . . . . . . . . 331 29. . . . . 323 26. . . 319 26. . 336 NT12-7002 ver 1. . . . . . . . . . . . . .1. . 332 29. . . . . .1. 326 28. . . . . . . . . . . . . . Filtering.4. . . . .4. . . . 325 27. . . . . . . . 323 27.7. .4. . . . . Searching. . . . . . . . . . . . . . . . .5. . . . . . . . . . 324 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . .4.3. . . . . . . . . . . . .7. . . . . . .3. . . . . . . . . . .8. . Presentation of Discarded Messages . 330 29. . . . . . . . . 329 29. .7. . . . . . . . . . . . . . . . . . . . Time Scale . . . . . .1. . . . . . 326 27. . . . . . . . . . . . . . . Presenting Data from a Different Device . . . Evaluating Video Streaming Performance . . . . . . . . . . . Mode Reports Window . . . . . . . . . . .8. . . . . . . . . . . . . . . . . . . . 320 26. . . . . . . . . . . Line Charts 329 29.Contents 26. .5. . . . . . Plain-text Message Decoding . . . . . . . . . . . The GPS Window 327 28. . . 320 26. . . . .5. . . . . 320 26. .4. How to Test Video Streaming . . . . . . . 332 29. . . . . .2. . . . . . . . Search Functions . . Window-specific Features . . . . . . Organization of the Line Chart Window. . . . Properties of the Video Monitor . . . .4. . Message Window Synchronization . . . . and Highlighting in Message Windows. . . . . . Contents of the Line Chart Panes . . . . . . . . . .2. . . . . . . . . Editing the Contents of a Chart . . . . . . . . . . . . . . . Highlighting Functions . . . Video Streaming and the Video Monitor 324 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 29. .1. . . .2. . . . . . . Editing General Properties of a Chart . . . . . . . . . . . 336 29. .2.2. . . . . . . . . . .3. . . . . . .1. Columns Tab . . . . . . . . . . . . Filtering Functions . . . . .1. . . . 321 26. . Adding Charts. . . . .4. . .

. . . . . . Data. . . . . . . . . . . . . . . . . . . . . . Map Concepts. . .6. . . . . . . .3.5. . . . . . . . . . . . .6. . . . . . . . 30. . . . . . . . . . . Additional Information .5. . . . . . . 31.5. . . . . .4. . . . . . Presenting Data from a Different Device . . . . . Presenting Cell Information . . .5. . . . . . . . . . . . . . . . Colors . . 31. . 30. . . . . . . 30. 30. . . . . Setting Up General Bar Chart Properties . . . . . .3. . 30. . . . . Organization of the Bar Chart Window . . . . .3. . .5. . . 30. .5. . . . . 30. . . . . . 31. . . . 31. Positioning Bitmap and TIF Maps . . . . . . . . . . . . .1. . . . . . . . . .5. . .1. . . . . Specifying the Map Position. . .3. . . Presenting Information Elements . . . . . . . . 30. . . . . 30. . . .1. . . . . . . Presentation Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31. . . . . . . . Setting the Map’s North Direction . . . Map Windows 356 356 356 357 359 359 359 360 360 360 361 362 364 365 366 367 370 373 375 377 31. . . . . . . . . . . . . . . . . Exporting the Bar Chart Window. . . . . . . . . .3. .4. . . . . . . . . The Cell Line Theme. . . . . . . . . . . . . . . . . . .5. .4. . .5. . . . . . . . .4. 30. Adding Charts . . . .2. . . . . . . . The Cell Color Theme . . . . . .4. . . . . . xviii . .3. . . . . . . . . . . . .4. . . . Presenting Pinpointing . . . . . . . . . . . . . . .2. . . . . . Themes and Theme Types .2.3. . . 31. . . . . . . . . . . . 31. . . . . . Highlights of This Chapter. . . . .TEMS Investigation 14. . . Multiple IE Components Presentation Mode. . . . . . . . . . . . . . . . . .1 User’s Manual 30. . 31. . . .5. . .5. . . . . . . . . . . . .5. . . . . . . .3. . . . . Contents of the Bar Chart Panes . Presenting Data: Themes . . . . Presenting Events .1. .1. . . . .4. . . . . 31. . . . . . . . . 30. . . . . . . . . 30. . . The Cell ARFCN Theme (GSM) .1. . . . . Parallel Coordinates/Stacked Bar Chart Presentation Mode . . . . . . . . 31. . . . . 31. . . . . . . . . .4. . . . . . . .4. . .1. Presentation Mode. . .4. . . . . . . . . . . .5. . . . . . Specifying the Map Scale . . . . . . . . . Notes on Route Plotting and Updating . . . .2. . . . . . . . . . . . . . . . . . The Cell Theme. . . . . . .4. . . . . . . . . . . Constructing a GeoSet from Map Files. . . . . . . . . . . . . . . . . Deleting a Chart . . . . . .2. . . . . . . . 31.3. 31. . . . . . . . . Single IE Presentation Mode.4. . . . . . .4. .5. 31. . . . . . . . . 31. . .5. . . . . . . .4. . . . . . . . . . . . . . . .1. Editing General Properties of a Chart . . . . . . . . . . . . 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. 31. . . . . . . . .1. . . 30.1.5. . . . . . . Setting Up Bar Chart Contents . . . . . .3. . . . . . . Examples of Bar Chart Presentations. . . . . . .3. . 31. . . . . . .3. . . . . .1. . . . . 31. . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . .2. .2. . . Interval and Labeling . . . . . . .5. . Bar Charts 337 338 339 340 340 340 341 341 342 343 344 347 351 352 352 353 355 30. .5. . . . . . . . .1. . . . 30. . . . . . . 31.

. . . . . 381 31. . . SQI for CDMA . . . . . . . 389 33. . . . . . . 390 33. . . . . . . 383 31. . .1. . . . . . . . . . . . . . . . . . . 384 31. . .1. . . . . . . . . . . 381 31. . . . . . . . . . . 384 31. . . . . . . . . . . . . . . . 378 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . Adding Presentation Layers . . . . . . . . . . .2. . . . . . . . . . . . . . . . .0 xix . . Layer Control . . . . . . Background . . . . . . . 378 31.1. . . . . . . . . . . . . . .8. . . .2. . . . . . .5. . . .2. . 382 31. . . . 383 31. The Map Window Toolbar . . . . . . .8. . . . . . . . . . . . . . . . . . . . . . . . . 391 NT12-7002 ver 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrity. . . . . . . . . . . . . . . . . . . Previous View. . .6. . . . . . . . . . .3. . . . . .7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . .2. . . . . . . . . . . . .7. . . . . . . .2. . . . .9. . . . . . 383 31. . . . . . . . . . . .10. . . The General Window 33. . . . . . . . . . . . . . . . . . Retainability . . . Accessibility . . GeoSet Manager . . .Contents 31. Theme Statistics (Info and Graph Tabs) . . . . . . . . . . . . . 389 33. . . . Reordering Themes . . . .3. . . General Procedure . .1. . .10. . . . . . . . . . . . . . . . . . . . . . Layer Control . . . . . . . . . . . . . . . .8. . . . . . Key Performance Indicators – KPIs (UMTS) 387 388 33. .6.1. . . . . Setting the Map Projection .5. . Obtaining Significant KPI Statistics . . . . Deleting Themes . . . . . 389 33. 378 31. . . . . 388 33. . . . . The Right-hand Pane .10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. 385 31. . . . . . . . . . . . . . . . 377 31. . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . .7. Visibility of Themes . . . . . . . . . . . SQI for UMTS. . . . . Theme Legend (Legend Tab). . . .4. The Scale Bar. . .2. .2. . . . . . . . . . . . . . 378 31. . 391 34. . . . . . 390 34. . “Events of KPI Type” . . . . . . Information on Single Theme Markers (Info Tab). 384 31. . . . . 386 31. . . . . . .6. . . . . . .2. . . . .5. . . . . . . . . 391 34. . . . . . . . . . . . . .1. . . . .3. . . . . . . . . Obtaining KPIs with TEMS Products. . . . .3. . . . 389 33. . . . . . . . . . . 389 33. . . . 386 32.1. . . . . Editing Themes . . . . . . . . . .8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . Projections . . .9. .1. . . . . . . . . Speech Quality Index – SQI 391 34. . . . . . . . . . . . . . . . . .1. . . . . . . . .8. . . . . . . . . . .1. . . . . . . . . .1. . . . . .1. . . . . . . . . . . . . . . Purpose of KPIs . . . . . . Layers . . . . . .2. . . . . Map Context Menu . . . .2. . . . . . . . . . . . . . . . . . .8. . . . . . .10. . . . . . . . . . . . . 381 31. 377 31. . . . 380 31.7. . . . . View Entire Layer . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .3. . 403 36. . . . 407 37. 406 37. . . . . . . . . . . . . . . . . . 402 36. . . . . . . . . . . . . . . . . . . . . . . . . . . 406 37. . . . Alignment of SQI-MOS and PESQ . . .3. . . .1 User’s Manual 34. Input to the SQI-MOS Algorithm . AQM with Call Generator/MRU 399 36. . . . . . . . . . . . . . Comparison with Other Radio Parameters . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . .3. . . . . Prerequisites . . . The PESQ Algorithm. . . . . . . 34. . . . 392 392 393 393 394 394 394 395 396 35. . .2. . . . SQI-MOS Output. . . .1. . Presentation of AQM Data . . SQI-MOS vs. . . . . Notes on AQM Scores Obtained with Individual Phone Models. . . . . . . . Audio Quality Measurement (AQM): General 397 35. 397 35. . . . . .1. . . . . . . .2. . . . . . Preparations. 397 35. . . . . . . .1. . . . . . . . . . . 402 36. . . . . 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34. . . . . . . Notes on PESQ for Wideband (UMTS) . . AQM with Audio Capturing Unit (ACU) 405 37. . . 409 xx . . . . . . .5. . . . .1. . . . . Recording AQM Data. . 408 37. . . . . . . . . . . . . . . . . . . 403 36. . .1. . . . Obtaining AQM Data. . . Mobile-to-mobile Audio Quality Measurement with MRU . . . . . . . . . . . . . . CDMA . . . . . . . . . . . .2. . . . . . . . . . . . . . . .1. . . . .1.3. . . . . 406 37. . . . . Practical Considerations . . . . . .2. . . . . . . . . 34. . . . . . . . . . 34. . . . . . . . . Wideband SQI-MOS (UMTS) . . . . .1. . . . . . . . . . . .5. . . . . . PESQ Key Performance Indicator . . . .TEMS Investigation 14. . . . . . . . . . . . . . . . . . . . . .5. . . . . . . .3. 405 37. .3. . . 398 36.3.1. .4. . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . Presentation of AQM Data . . . . 34. . . . . . 34. . . . .1. . . . .1. UMTS. Recording AQM Data. . . . . . . . . . . . . . . . .2. . . . .3. .2. 34. . . . . . . . . . . Old SQI (UMTS) . . . . . .2. . . . . Narrowband vs. . . . . 401 36. . . . .2.3. . . . . . .1. . . . . . . . . Merging Uplink AQM Data into Logfiles . . Information Elements . . . Obtaining AQM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 36. . . . . . . .2. . . . . . . . . . . . . .3. . . Measurement Setups in TEMS Investigation . . . . . . . . . . . . .4.2. . . . 404 37. . . The POLQA Algorithm . .1. . . .2. . .5. . . Mobile-to-fixed Audio Quality Measurement with Call Generator. . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . 403 36. . . . . .3. . . . .2. . . . . . . Prerequisites . 402 36. Information Elements . . 408 37. . . . . . Recommended Structure of AQM Scripts . . . .399 36. . . . . . . . . . . . . . . .

. . . . . . . . . 414 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . Accuracy . What VTQI Is Based On . . . 423 43.4. . Dynamic (Realtime) VSQI . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . 420 43. . . . . . . . . AQM for VoIP 410 38. . .2. . . . . . Requirements on a Robust C/I Measure . . . . Automatic vs. . . . . . . . . . . . . Editing and Removing Test Cases . . 413 39. . . .4. . . . . . . . . . . . . . 415 40. . . . . . . . . . . . . . . . . . . . . Manual Verification . .1.0 xxi . . General Properties of VSQI. . . . . . . . . . . . Why Measure C/I?. . . . . . . . . . . . 415 40. . . What VTQI Does Not Consider . An Example . . . . . . . . . . . . . . . . . 422 43. . . . . . . . . . . . . . . . 411 38. . . . . . . . . Activating Phones . . . .Contents 38. . . . . . . . . . . . . .2. . . . . . . Static VSQI. . . . . . . . . . 415 40. . . . . . . General Properties of VTQI. . . . . . . 412 39. . . . . . . . . . . . . . . Video Streaming Quality Index – VSQI 414 40. . 411 39. . . . . . . . . . . . . Video Telephony Quality Index – VTQI 412 39. . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . 413 40. . . 424 43. . . . . .1.2. . . . . . . . . . . . . . . . 420 42. . . . . 416 41. . . . . . . . . . . .1. . . . Update Rate . . . . . . . . . . 414 40. . . . . . . . . . Adding a Test Case. . Presentation of AQM Data . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . 412 39. . . . . The GSM Channel Verification Window . . 426 NT12-7002 ver 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C/I Measurement (GSM) 418 419 42. . . . GSM Channel Verification 422 43.5. . . . . Details on C/I Measurements . . . . . . . . . . .4. . . .2. . . . . . . . . . . . . . . . . . . What VSQI Is Based On . . . . 424 43. . . . . . . . . . .3. . Static and Dynamic VSQI . . . 420 42. . . . . Mobile TV Quality Index – MTQI 42. . . . . . . . . . . . . . . . .5.2. . . Obtaining AQM Data . . . . . . . . . . . . 419 42. . . 419 42. . . . .3. . . . . . . . .1. .2.4. . . . . . . What VSQI Does Not Consider . . . . . . . . . .

. . . . Summary of Test Case Status Values . .2. . 43. . . . . . . . . . . . Equipment Handling . . . . . . . . . 439 C. . . Command Sequences. . . . . 440 C. . . 43. . . . .1. . A. . . . . . . . . . . . . .TEMS Investigation 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving and Opening Tests . . 43. . . . . . . . . .11. . Running the Test. . Keyboard Shortcuts 433 433 433 434 434 A. . . .3. . . . . . . . . . . . . . . . 43. . . . . .9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes on Performance . . 43. . . . .7.2. . . . . .10. 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . .6. . . . . . Manual Verification . . . . .1 User’s Manual 43. . . . . . . . . . . . . . . . . . . . . . . 43. . . .6.6. . . . General Shortcuts. . . . . . . Example . . . . . . . . Appendix B. . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the Test . . . . A. . . . . . . . Resetting a Test Case . . . Getting Started. . 427 427 427 428 428 429 429 429 430 431 431 431 Appendix A. . Automatic Verification . . . . 43. . . . . . . . . . . . . . . . . . . Creating Test Reports. . . . . . . . .6. . . . . . . . . . . . Error Conditions . . . . . . . . . . . . 43. . . . . . . . . . . . . . Drive Testing Shortcuts . . . . . . 441 Index 443 xxii . . . . . . . . . . . . . . . Shortcuts for Active Window. . . . . . . . . . . . . . .13. Comparison with Pre-12. . . . . . . . . . .6. . . . . . . . . . .3. . . . . . Logfile Load Shortcuts . . . . . . . . . . . . . . .8. . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . .0 User Interface 437 439 C. 43. .2. . . . . . . . Service Control vs. . . . . . . . . . . . . . . . . . A. . . . . . . . . . .4. . . . . . File Types in TEMS Investigation Appendix C. . . 43. . . . . . “Data” Category Information Elements. . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . .1. . . . . . . .12. . . . . . .

Offering data collection. optimization. all of which are covered by the product documentation but are not differentiated there.Chapter 1. reducing costs and saving time and effort for operations staff. please take the time to read this user manual in order to gain an in-depth understanding of the product features. real-time analysis. This means that descriptions of functionality and external device compatibility are not necessarily applicable in every single respect to the TEMS Investigation edition you have purchased. Any restrictions that apply to your edition are indicated in the Release Note included in the delivery. To get the most out of TEMS Investigation.0 1 . Note: Please note that the TEMS Investigation product exists in various editions. NT12-7002 ver 1. This complete solution eliminates the need for multiple tools. Introduction 1. TEMS Investigation is a complete solution for all of a network operator’s daily network optimization tasks. and maintenance of wireless networks. Introduction Thank you for choosing TEMS Investigation – the industry-leading tool for troubleshooting. and post-processing all in one. verification.

supporting all of the following technologies: • • • • • • GSM/GPRS/EGPRS WCDMA/HSPA/HSPA+ LTE (FDD and TDD) TD-SCDMA (including interaction with GSM) cdmaOne/cdma2000/EV-DO Rel. and other measurement devices. The application also boasts a vast array of windows for presentation of logfile data.1 User’s Manual 1.1 TEMS Investigation 14. 1. 2 . separately for chipsets with different capabilities. TEMS Investigation is primarily a tool for data collection and real-time analysis.1. The Base Software Package provides the ability to collect data with Sony Ericsson phones in UMTS networks and with Qualcomm chipset based terminals in CDMA networks. Other phones are licensed separately for each supplier or. logfile reports. A/EV-DO Rev. B WiMAX (scanning only) TEMS Investigation enables monitoring of voice and video telephony as well as a variety of data services over packet-switched and circuit-switched connections.1 is an air interface test tool for cellular networks. It interfaces with phones. 0/EV-DO Rev. logfile export).1. Customers who dispense with TEMS Investigation data collection are still able to use the non-realtime functions of the application (analysis of a single logfile. Package Options – Licensing TEMS Investigation can be purchased with or without data collection capability (“Base Software Package” and “Replay Package” respectively). data cards. except that WCDMA always comes with GSM support included.TEMS Investigation 14. scanners. Fundamentals of TEMS Investigation 14. Supported cellular technologies can be freely selected and combined. Still more powerful post-processing facilities are provided by the product TEMS Discovery.1. in the case of Qualcomm. it collects data and records it in logfiles.

is likewise sold as a separate option. Sequans. DRT. TD-SCDMA. and ZTE. The number of external devices that can be connected simultaneously in the application is dependent on many factors.1.1 supports a wide variety of user terminals. including ones from Sony Ericsson.2. ST-Ericsson. section 10. Introduction The Base Software Package permits data collection with one phone at a time. For indoor environments. LG. and WiMAX scanning. Together they allow comprehensive monitoring of UMTS. Sequans.Chapter 1. HTC. Sierra Wireless. Connectable Equipment TEMS Investigation 14. CDMA. such as whether a data service is being run. 1. See the Getting Started Manual. Anritsu.0 3 . LTE. Rohde & Schwarz. A variety of devices are supported for GSM. Audio quality measurement (AQM). It also lists and describes all preconfigured presentation windows. Qualcomm. GERAN–UTRAN–E-UTRAN inter-RAT handover). These terminals are built on chipsets from Altair. Samsung.2. and CDMA networks and of interaction among them (for example. Novatel Wireless. and Transcom. LTE. GCT. WCDMA. Audio quality measurement is supported for GSM. WCDMA. Pantech. The Information Elements and Events volume provides full details on all IEs and events found in the application.1. This option includes all required hardware as well as the ability to connect that hardware to TEMS Investigation.1 for further details on the range of connectable equipment. positioning by pinpointing (either manual or according to planned routes) is supported. Hisilicon. The manual gives a comprehensive account of all functions in the application. including ones from Ascom. Huawei. See the Release Note for further information. including PESQ/POLQA. and CDMA. NT12-7002 ver 1. GPS units can be connected for geographical positioning. TD-SCDMA. and Via. 1. What’s in This Manual (and What’s Not) This book describes the user interface of TEMS Investigation 14. Option. A separate license option is available for collecting data with multiple phones concurrently. Leadcore. It concentrates on how to use that application once it has been installed and all external devices are connected and ready for use. PCTel. Nokia.

a Getting Started Manual is provided which covers all preliminaries. 4 . however. These.htm.ascom.com/en/index/support/supporttems/technical-support/tems-investigation. and control external equipment is described in the present document. The same applies to all other third-party products mentioned in the manuals. External Equipment The basics on external devices are covered in the Getting Started Manual. and other information of a technical nature.TEMS Investigation 14. Equipment Cases The TEMS equipment cases. sometimes refer to TEMS Investigation documentation. please refer to the documentation accompanying the phones. Besides the above reference manuals. In the remainder of this book.1 User’s Manual The Technical Reference volume contains file and report format descriptions. are not covered here but have their own manuals.pdf which is found in the TEMS Investigation installation folder. The manual does not describe the full range of functions and capabilities of the connectable phones. operate. For exhaustive information. crucially the following: • • • • Configuring the PC for TEMS Investigation Installing the TEMS Investigation software Licensing issues Configuring the PC and phones for data services How to activate. designed to accommodate phones and other equipment during drive tests. FAQ Many questions regarding TEMS Investigation are answered in the FAQ sections found on the Web at www. Release Note Some technical issues not addressed in this manual are dealt with in the file ReleaseNote. external devices are discussed further whenever certain capabilities are required in order for a function in TEMS Investigation to be supported. chapter 10.

1. Introduction Technical Support If you have a question about TEMS Investigation which is not answered in any of the manuals nor in any of the other sources mentioned above. TEMS Bulletins TEMS Bulletins contain updates on new TEMS product releases. Data Services This term refers to services requiring a data connection (either circuitswitched or packet-switched).ascom.0 5 . User-defined events are specified by logical expressions which trigger the event when they evaluate to true. Along with this material you will also receive our customer magazine. TEMS News.Chapter 1. All information NT12-7002 ver 1. Besides these. You can also obtain up-to-date details on patch releases. either in the cellular network or in connected equipment.com/networktesting and. All predefined events are found in Information Elements and Events.ascom. you can define events of your own. To sign up for this free service.3. as opposed to voice calls.com/networktesting under the link “TEMS Support”. Information Element Information elements are pieces of numeric or text-format data that are presentable in the TEMS Investigation user interface. These expressions can contain predefined events. please contact technical support. click the link “Register for TEMS Bulletins”. go to www. A number of events are predefined. and conditions involving information elements. under the heading “TEMS Bulletins”. Layer 3 messages. and general information about the TEMS portfolio. Event An event is generated by the TEMS Investigation software in order to indicate that something worthy of note has occurred. chapter 7. Definitions This section explains a number of central concepts in TEMS Investigation which are frequently referred to in this user manual. Contact information is given on the Web at www. events.

most often a Layer 3 message. rather than phones. Complete details on the arguments of information elements are given in Information Elements and Events. Argument of Many information elements contain an array of values rather than a single value. To pick one item from the array. 6 . etc. the term “route” refers to a planned route created in that window. however (chapter 26).TEMS Investigation 14. a suitable qualifier is prefixed. may list either air interface messages. “Sony Ericsson GSM phone”. etc. “Samsung LTE modem”. Route In connection with the Pinpoint Window. or events. without any difference in meaning from the point of view of TEMS Investigation. you must specify an argument in the form of a neighbor index between 1 and 32.). USB modems. Phone The term “phone” covers user terminals from all supported technologies. When a subset is meant. “LG UE”. the GSM information element Neighbor RxLev contains the signal strengths of all neighboring channels (there may be up to 32). Message The term “message” in this user manual generally denotes an air interface message described in the wireless technology specifications. To present the signal strength of a particular neighbor channel. Mode Report A mode report is a status or measurement report generated by a phone. Information Element. A “message window”. and/or a more precise term is used (“GSM phone”. the word is used more loosely. or mode or error reports produced by phones. chapter 3. an argument is used. “Sierra Wireless CDMA data card”. Some user terminals supported by TEMS Investigation are in fact data cards. Outside of that context. The word “terminal” is therefore sometimes used instead of “phone”. chapter 3. For instance. or messages from various protocols.1 User’s Manual elements handled by TEMS Investigation are found in Information Elements and Events.

NT12-7002 ver 1. Introduction Scanner The term “scanner” denotes a device dedicated to scanning. Track A track is a walk along a planned route in the Pinpoint Window.Chapter 1. Phones with scanning capabilities are not referred to as scanners.0 7 . for example a PCTel scanner.

Optimize heterogeneous cell deployment: for example.1. scheduling traffic in an efficient way among multiple cells. TEMS Investigation 14. taking into account the propagation delay from the macro cell eNodeB. What’s New in TEMS Investigation 14. Recently Introduced Features in TEMS Investigation 2.1.1 presents cell frame timing data in newly constructed information elements for the current LTE serving cell and neighbors. Compare and evaluate synchronization techniques. For TD-LTE in particular with its unpaired spectrum. adjust timing in a pico cell to a surrounding macro cell.1. Compared to FDD there is also a more complex range of interference issues to handle. accurate synchronization between cells is crucial. 2. Still. the same frequency being used on both uplink and downlink. synchronization is necessary within a site owing to the overlap between its cells. Identify co-sited cells (having identical or nearly identical timing offsets) in an unknown network.TEMS Investigation 14. since this enables the use of techniques such as CoMP (coordinated multipoint). it is also highly beneficial between sites.1 User’s Manual 2.1 LTE Cell Frame Timing IEs Inter-cell synchronization is a central concept in LTE networks. even for FDD. Estimate distance to a site and determine its position by triangulation. This information can for example be used to: • • • Verify and troubleshoot synchronization in the network. including interference between UEs in adjacent cells and between eNodeBs. • • 8 .

Cell Whitelists A common constraint in cellular network testing is to restrict tests to a predefined set of cells: for example. Recently Introduced Features in TEMS Investigation 2. or to perform some procedure that would disturb regular network operation unless it is limited to cells that have been specially configured for the purpose.4.3. Extended Control Functionality and Logging for Sony Ericsson Xperia arc S Sony Ericsson Xperia arc S now supports audio quality measurement. See also section 2. This event can then be used in a script to trigger some action whenever the tester is in NT12-7002 ver 1. including PESQ and POLQA.1.Chapter 2.3.1.1. is now available also for circuit-switched voice. POLQA for CS Voice The state-of-the-art POLQA algorithm for speech quality assessment.2. In this version of TEMS Investigation it is possible to enter a list of allowed cells (“whitelist”) and have it converted into a user-defined event. POLQA can be computed for both narrowband and super-wideband speech.1.0 9 . previously introduced for VoIP. 2. to verify a new or reconfigured cell cluster. notably: • • • UARFCN and SC indicated for each SIB C/I per TCH computed for GSM circuit-switched services SIR target presented 2. taking smart measurements with this device several steps further: • • • • Access class control – modify access class settings PLMN control – lock on MCC + MNC combination BLER target control – modify BLER target assigned by network Speech codec control – redefine set of speech codecs enabled in phone The data collection and presentation have also been augmented in various respects. The following additional control functions have been implemented for the Xperia arc S phone. POLQA is obtained in the ACU (TerraTec) audio quality measurement configuration.

A “periodic” flag has been added as a new property of userdefined events. 2.1.1. The manual mode is similar to the pinpointing function in the Map window. • • New Connectable User Terminals Axesstel MV610VR (Gateway R90. Scripted Scanning Scanning tasks can be scripted instead of being run manually from the Navigator pane.8. 2. Via CDMA/EV-DO Chipset Support TEMS Investigation 14. 2.1 User’s Manual an allowed cell.1. 2.5. B) Huawei E398S (Hisilicon chipset based) 10 .7. Controlling scanning from a script brings the same benefits of convenience and automation as for other testing activities.1 introduces support for devices equipped with a Via CDMA/EV-DO chipset. as opposed to being planned in advance and followed during the walk.9.1. Offering both modes in the Pinpoint Window tool adds further to its flexibility and usefulness. Hisilicon LTE Chipset Support The accessibility of LTE network testing is further broadened as TEMS Investigation 14. EV-DO Rev. so that a cell whitelist event can be generated repeatedly and continuously listened for by a script. Manual Pinpointing Mode in Pinpoint Window In the Pinpoint Window.TEMS Investigation 14. 2. Making use of these features lets the user conduct rigorously selective network testing in a minimum of time and without any extra effort in the field.1 adds support for Hisilicon chipset based LTE devices.6.1. Net1. routes can now alternatively be traced manually while walking.

Recently Introduced Features in TEMS Investigation 2. This is a Qualcomm chipset based device running under Android.2. giving a more fine-grained view of retransmission statistics. and it obeys the following control commands: • • • • • Lock to RAT Lock to band (WCDMA and GSM) Control cell selection and handover (WCDMA and GSM) Set cell barred behavior (WCDMA and GSM) Enable/Disable HS capability NT12-7002 ver 1. 2.0 continued and reinforced this tradition by adding the Sony Ericsson Xperia arc S smartphone as a connectable device.1.2.1. useful for studies of MIMO channel properties. What Was New in TEMS Investigation 14. LTE RRC Redirection Events The LTE RRC connection redirection events have been extended to cover redirection to EV-DO (HRPD/eHRPD). New Connectable Scanners A TD-LTE scanner from Transcom Instruments is offered as a cost-efficient solution for scanning of TD-LTE networks. TEMS Investigation 14. PUSCH ack/nack counters.0 11 .12. Rank Indication counters showing incidence of values RI = 1 and RI = 2.1. 2.0 Control Functions for Smartphones TEMS products have a long tradition of offering unique device control capabilities that rely on advanced measurement capabilities in the device hardware. • • • New LTE Information Elements PDSCH BLER and ack/nack counters for Transport Blocks 0 and 1 separately. Supported LTE bands are: • • • TDD 1900 MHz (Band 39) TDD 2300 MHz (Band 40) TDD 2600 MHz (Band 38) 2.11. 2.1.Chapter 2.10.

you can tag logfiles with metadata which can serve as an aid to locating. The activities of one device can be recorded in any number of logfiles simultaneously. The new format embodies a more flexible and versatile framework for recording of measurement data: • Multiple logfiles can be recorded in parallel.log) is of course maintained. sorting. Activity statistics: Total/succeeded/failed/aborted. and more) but also: • A list of the participating devices with accompanying key properties (capabilities.2. and their outcomes. hardware identifiers. The chronology can be grouped by device or activity type. and more). • • Full compatibility with the old logfile format (*. New Logfile Format The old logfile format (*. • • • When loading a completed logfile into TEMS Investigation later on for analysis. each recording being wholly independent of the others. Here you can view not only general information (time and space coordinates. descriptive metadata added at recording time.2.0 by a new format with extension . 12 .TEMS Investigation 14. supports all of the above commands as well as the following: • • • • Control access class Control PLMN Control speech codec usage Enable/Disable EDGE capability 2. A complete chronology of the activities performed by all devices. In logfile recording controlled by a script.log) was replaced in TEMS Investigation 14. Some of this metadata is also visible in Windows Explorer. At creation time. extensive information about the file appears on a new Navigator tab called the Logfile tab. likewise new as a connectable device in TEMS Investigation 14. or filtered to show only one device or one type of activity. and categorizing the files later on. The logfile size is significantly reduced compared to the LOG format.0.1 User’s Manual The Samsung Infuse 4G smartphone (ST-Ericsson chipset based).trp. you can hide data from selected devices in the logfile presentation. presented in the same way as in live mode. you can opt to record only a subset of the activated devices. If you wish.

2. static ARFCN set RSSI scanning: BSIC decoding RSSI scanning: C/I measurement.3. A “find next/find previous” feature is included for easy stepping back and forth between hits (can be done with the keyboard arrow keys). The search functions essentially correspond to the Find in Logfile feature in pre14.0 product versions.2. The POLQA (Perceptual Objective Listening Quality Analysis) algorithm is designed along similar lines as PESQ.863 standard. filtering. Highlight selected types of messages in unique colors.2. 3G and 4G/LTE. Optionally.0.4. See chapter 35. Show only messages of a selected type. Recently Introduced Features in TEMS Investigation 2.5. Speech Quality Measurement with POLQA POLQA. The handling of scanning configuration sets was relaxed. Searching. is the successor of PESQ.0 13 . • • LTE: TDD and FDD pilot scans can be run in parallel on Rohde & Schwarz TSMW. and visual highlighting were implemented in message windows in order to accelerate analysis. Hide messages of a selected type. 2. NT12-7002 ver 1. allowing multiple devices to scan concurrently using different configuration sets.Chapter 2. POLQA was introduced in TEMS Investigation 14. and VoIP. Filtering. • Expansion of Scanning Capabilities GSM scanning capabilities of Rohde & Schwarz TSMW were made available for use with TEMS Investigation: – – – RSSI scanning. which was removed in TEMS Investigation 14. • • • 2.2. You can: • Find arbitrary text in message headers.0 as a speech quality measurement algorithm for VoIP. the full message contents can be searched. and Highlighting in Message Windows New functions for searching. being specially developed for HD voice. defined in the ITU P. Case and whole-word matching is available.

All of these features help you manage logfile export more smoothly and save time. which can be installed under Windows 7 or Windows Server 2008/2003.2. Cell files can be included when exporting logfiles.6. multiple concurrent FTP download sessions with one device simply by putting the sessions in parallel branches in your script. Flow control in scripting was rendered more powerful with the new Wait For activity.TEMS Investigation 14. Logfile Export Enhancements The logfile export tool was repackaged into a separate executable which can alternatively be run from a Windows command prompt. the license server administrator assigns to each TEMS Investigation user the products 14 . 2.7. Improved Service Testing Capabilities TEMS Investigation 14. There is no need to pass special session concurrency parameters with the FTP testing activity. 2. facilitating management of network licenses and adding traceability. You can use this activity to halt execution: • • • until a given time of day (with optional subsequent repetition of activities that are placed in a loop with the Wait For activity) until a given event (or one event from a defined set) occurs until an activity in another workflow branch concludes with a stipulated outcome. In this Web-based portal.0 introduced the option of using Internet Explorer 9 for HTTP download testing instead of TEMS Investigation’s built-in Web browser. Two new HTTP information elements were provided (regardless of browser used): total document size and download time. Improved HASP Soft License Handling A license manager portal was introduced.8.2. Command-line controlled export can be scheduled with the generic scheduling functionality in Windows. This means that you can set up.).2. etc. Command line switches are provided for all aspects of the export setup that are configurable from within TEMS Investigation. This affects exported information elements and events in precisely the same way as cell files loaded in TEMS Investigation enrich the presentation in the application user interface (populating information elements that require cell file data. The Parallel (workflow branching) structure was amplified in one important respect: Within such a structure you can assign multiple activities of the same type to the same device. for example.1 User’s Manual 2.

2. a client license manager with a graphical user interface is provided. From this utility. Recently Introduced Features in TEMS Investigation they are allowed to detach and sets a maximum detach duration.4 Mbit/s). HSUPA Category 6 (5.1 regarding control functions – – – – – – • • WCDMA/HSPA 900/2100 MHz (LT18i) WCDMA/HSPA 800/850/1900/2100 MHz (LT18a) GSM/GPRS/EDGE 850/900/1800/1900 MHz Google Android 2.4 GHz) HSDPA Category 10 (14.2. Reports on license usage can be generated and also exported in comma-separated (CSV) format.Chapter 2. Further constraints such as license expiry dates can be defined. The client works over a VPN. Side by side with the license manager portal.2.0 15 . New Connectable User Terminals in TEMS Investigation 14. and the main benefit it brings is that it greatly reduces the risk of detaching the wrong license by mistake.3 Qualcomm Snapdragon MSM8255 (1.76 Mbit/s) Huawei E353 LG P505 NT12-7002 ver 1.0 LTE Devices • • • • • • • Huawei M920 LG LS840 (LG Viper) LG MS840 (LG Connect 4G) LG P936 (LG Optimus) Samsung SCH-R920 Samsung SCH-R940 ZTE N910 UMTS Devices • Sony Ericsson Xperia arc S: See also section 2.9. users detach licenses to their local machines. “Category” fields are provided for convenient grouping of users.

which call each other in pairs.1 User’s Manual • • LG P509 Sharp 006SH 2. Nokia C7-00 (GSM/WCDMA). What Was New in TEMS Investigation 13.3.3. RACH Result. Huawei C8600 (CDMA). 2. Event categories: • • • Call setup events Inter-RAT events Attach events 2.1 it was implemented for the following phones: Sony Ericsson Xperia arc. Sony Ericsson W995. The mobile-to-mobile AQM solution is in principle RAT-independent. In TEMS Investigation 13. some expanded in scope – report on the resulting interaction between the terminal and networks. there is also no Call Generator or similar component in this AQM configuration.1. RACH Reason. so that no separate processing power is required in the Audio Capturing Unit. Preamble Step Size. A number of events – some new. are connected to an Audio Capturing Unit (ACU) which relays the audio to the PC.1 Alternative Mobile-to-mobile AQM Solution This is a cost-efficient solution for mobile-to-mobile audio quality measurement.2.TEMS Investigation 14.3. The PESQ calculation is done by the PC itself. CS Fallback Events and Information The “circuit-switched fallback” mechanism allows a user terminal connected to EUTRAN to access the CS domain via GERAN or UTRAN.3. just as in the existing TEMS Investigation AQM setup. Since the voice calls are made between the mobiles.3. The activities of the devices are completely controlled from TEMS Investigation by means of a Service Control script. Two or four mobile devices. 2. Extended Set of LTE RACH Information Elements A collection of new information elements deals with the RACH procedure in LTE: RACH Type. RACH 16 .

that is.6. and MME Code. B Measurement and Analysis Rev.4.1 allows connection of devices built on a range of Qualcomm CDMA/EV-DO Rev. HSDPA Category 14 (21 Mbit/s) Advanced control functionality • NT12-7002 ver 1. B of the EV-DO (TIA-856) standard introduces multicarrier data transfer in EV-DO. • New Connectable User Terminals in TEMS Investigation 13.5. The implementation was verified with the Huawei EC367-2 device.1 Sequans TD-LTE USB modem SQN3010A-USB-M1. CDMA/EV-DO Rev.3.76 Mbit/s).3. TEMS Investigation 13. 2. Improved Handling of Qualcomm-based LTE Devices Network connect can be performed for Qualcomm chipset-based LTE devices from within TEMS Investigation.Chapter 2. operating on LTE Band 40 (2300–2400 MHz) and based on TD-LTE-capable chipset SQN3010 Samsung Galaxy S 4G – – – – – Android-based WCDMA/HSPA 1700/2100 and 2100 (Bands IV. MME Group Id. Presented information elements subdivide into three categories: • • • Basic radio parameters Multicarrier serving channel information Forward link multicarrier RLP throughput 2. B chipsets. I) GSM/EDGE 850/900/1800/1900 HSUPA Category 6 (5.3.0 17 . Recently Introduced Features in TEMS Investigation Preamble Responses with PUSCH Resource. 2. without using an external connection manager. TEMS Investigation also permits connection of multiple Qualcomm-based LTE devices.

76 Mbit/s).7. HSDPA Category 24 (42 Mbit/s) BandLuxe C501 Huawei E392 Sierra Wireless AirCard 313U Huawei E367 Huawei E372 Novatel Option MC996D Huawei C8600 Huawei EC367-2 Huawei M860 Kyocera S1350 LG KV600 LG KV755 Samsung SCH-R720 ZTE AC8710 • Other new LTE devices: – – – • Other new UMTS devices: – – – • New CDMA devices: – – – – – – – – 2. VIII.TEMS Investigation 14.1 User’s Manual • Sierra Wireless AirCard 319U – – – – Dual-Carrier HSPA+ USB modem from Sierra Wireless WCDMA/HSPA+ 850/900/1900/2100 (Bands V. I) GSM/EDGE 850/900/1800/1900 HSUPA Category 6 (5. WCDMA Scanning with Rohde & Schwarz WCDMA pilot (Top N) scanning can be undertaken with Rohde & Schwarz TSMW scanners. There are no restrictions on supported frequency bands (30 MHz to 6 GHz). 18 .3. II.

NT12-7002 ver 1.0 19 . RSSI scan) with PCTel SeeGull MX.10.1. Software Update Service A TEMS Investigation software update service was introduced. This service checks for new patch releases on a regular basis. • Enhancements in TEMS Investigation 13. 2. Support added for Anydata ADU-895A (CDMA/EV-DO Rev. HS Transport Block Size (Median). B.3. CDMA Scanning with PCTel SeeGull MX Support was added for CDMA scanning (PN scan. HS MIMO Transport Block Size (Min).3.1 PCTel SeeGull MX LTE 800/900/1800/2600 + WCDMA 900/2100 + GSM 900/1800 PCTel SeeGull MX WCDMA 850/1900/2100 AWS + GSM 850/1900 + CDMA/EV-DO 850/1900/2100 AWS Anritsu ML8780A 2. 450 MHz). 2. HS Transport Block Size (Max).3. • • • New Connectable Scanners in TEMS Investigation 13. This feature is a time-saver that reduces the hours you have to spend on drive testing. all with arguments for primary carrier and secondary carrier.9.Chapter 2. HS MIMO Transport Block Size (Max). Min/max/median versions of HS transport block size IEs introduced: – HS Transport Block Size (Min). The new feature streamlines administration processes and minimizes waiting time. one PN scan on a cdma2000 frequency and one on an EV-DO frequency.3. all with arguments for stream 0 and stream 1. Recently Introduced Features in TEMS Investigation 2.1 Multiple concurrent PN scans can be performed with PCTel MX and EX scanners: for example. • – • • • Support added for Samsung Galaxy S II LTE. Support added for Novatel Ovation MC551 4G LTE USB modem (Band 13). HS MIMO Transport Block Size (Median).11.8.

3. inter-frequency. or after downloading a specified amount of data. Support added for Altair DC-E3100 chipset (no devices commercially available at the time of releasing TEMS Investigation 13. which incorporate building and floor plan information as well as the planned routes you create.1 User’s Manual • Support added for Huawei U6100 (HSPA). and inter-RAT). The point of pre-planning routes is to render route walks as simple as possible.TEMS Investigation 14. • Enhancements in TEMS Investigation 13. Support added for the following devices: – – – – Datang/Leadcore LC8143 HTC Vivid (PH39100) LG MS695 Quanta LU220 • • • • 20 .12. are saved in the iBwave Design container format (*.2).1. discontinuous reception (DRX). Logfiles recorded when walking planned routes are saved in regular TEMS Investigation logfiles. step forward to the next waypoint. and sounding reference signals (SRS).ibwc). Support added for GSM scanning with Rohde & Schwarz TSMW.2 The existing indoor measurement solution was complemented with a new Pinpoint Window. • A large number of new LTE information elements have been introduced. and step backward to the previous waypoint in case you want to repeat a part of the route. The buttons are generously sized to permit easy and accurate tapping on a touch screen while walking around. where you create and walk pre-planned indoor test routes. Indoor map sets. DCI format usage on PDCCH. promoting an efficient work process and saving time and money. Indoor testing with the Pinpoint Window is fully aligned and compatible with TEMS Pocket (which likewise supports pre-planned routes) as well as with post-processing in TEMS Discovery. User actions are reduced to the clicking of three buttons: commit to a waypoint on reaching it. To the HTTP Get script activity have been added two new options: terminate session after a specified duration. These relate mainly to: cell reselection parameter settings and measurements (intra-frequency. 2.1.

USB modems. and SCH CINR.4.0 21 . Layer 3) is not obtained with this kind of testing. Using a Rohde & Schwarz TSMW Universal Radio Network Analyzer. etc.4. Any LTE frequency band can be scanned. embedded modules. This feature can be used to verify application layer performance for arbitrary devices. 2. or a wide variety of network cards. RSRQ. Any IPbased activity in the Service Control Designer.Chapter 2. 2. data service testing can be undertaken with any off-the-shelf device as long as it comes with Windows drivers that enable an IP data connection – for example. Layer 2.0 version. as well as video streaming. and all IP information elements will then be populated.4.0 introduced scanning support also for the TDD mode. TEMS Investigation 13. The data set obtained is similar to FDD and includes RSRP. NT12-7002 ver 1.2. Recently Introduced Features in TEMS Investigation – – – – Samsung SCH-R920 (Chief) Samsung SGH-I727 (Galaxy S II Skyrocket) Samsung SGH-I997 (Galaxy S Infuse 4G) ZTE X500 2. Please note that lower-layer data (RF. Up until the 13. as will be desirable prior to launching them in the network. it is possible to do Top-N LTE signal scanning in both TDD and FDD mode. known as TD-LTE.0 version.0 TD-LTE Support The LTE standard allows both frequency division duplex (FDD) and time division duplex (TDD) operation.0 expanded the concept of data service testing.1. taking it to a whole new level of genericity. LTE support in TEMS Investigation was restricted to FDD. What Was New in TEMS Investigation 13. can be run on such a device. Data Service Performance Verification with Generic Device TEMS Investigation 13. iPhone or BlackBerry units. With the 13. however.

you are invited to select what workspace to use: one recently used. such a file may contain all details of how to perform an LTE Reference Signal scan with a PCTel MX scanner. a range of additional LTE information elements are obtained. See section 4.3. New Connectable Equipment in TEMS Investigation 13.4.4.2. 2. and PUSCH BLER. The utility can also be seen as a complement to the script saving function in the Service Control Designer.TEMS Investigation 14. many LTE elements previously available only with LG devices are also obtainable with Qualcomm devices.2. or a new one that is empty. which creates files specifying the activities to perform during testing. using TEMS Investigation 13. Furthermore.4.6.0 UMTS Terminals 2. The TEMS Settings Manager boosts usability by enabling easy distribution of configuration data among users and among instances of TEMS Investigation. • – – – Sony Ericsson Xperia arc (Android-based smartphone): GSM/EDGE 850/900/1800/1900 WCDMA/HSPA 900/2100 (LT15i) WCDMA/HSPA 800/850/1900/2100 (LT15a) 22 . 2.0.18.0. or all the parameters needed to access and interact with a particular FTP server.1.4.1 User’s Manual 2.4. See section 20. New Utility for Sharing Script Configuration Settings The TEMS Settings Manager is a utility which lets you save to file any service and scanner settings that are used for service testing. 2. For example.4.5.6. Selection of Preferred Workspace at Startup When you start TEMS Investigation 13. including PDSCH Transmission Distribution. New LTE Information Elements With LG devices. PBCH BLER. some other existing workspace.

Support for 64-bit Windows 7 TEMS Investigation 13. LTE Scanner: Rohde & Schwarz TSMW The R&S TSMW Universal Radio Network Analyzer enables TD-LTE measurements in TEMS Investigation 13. Unlike the Telnet protocol.0 Mbit/s) Nokia C7-00 HTC Imagio 2. HSUPA Category 5 (2. see section 2. 2. and support for these is planned for inclusion in future releases of TEMS Investigation. which sends logins and passwords in plain text.76 Mbit/s) WCDMA/HSPA 850/900/1700/1900/2100 MHz GSM/GPRS/EDGE 850/900/1800/1900 MHz HSDPA Category 9 (10.8.0 onward. since it is subject to export restrictions due to its use of strong encryption.4. Support for SSH2 Protocol in Iperf Testing The SSH2 protocol (Secure Shell version 2) is offered as an alternative to Telnet as connection client when doing Network Bandwidth testing with Iperf. Recently Introduced Features in TEMS Investigation – • – – – • HSDPA Category 8 (7.4. Scanner capabilities include: • • Support for all LTE frequency bands: 30 MHz to 6 GHz Top N LTE signal scanning for TDD as well as FDD The R&S TSMW scanner handles a range of other technologies.Chapter 2. Update to this text: GSM and WCDMA scanning is supported with R&S TSMW from TEMS Investigation 14.7.0 23 .2 Mbit/s). Compare section 2. SSH2 uses cryptography to authenticate the remote computer and therefore renders the Iperf server less vulnerable to hacker attacks.16.1.1 2. HSUPA Category 6 (5.2 Mbit/s).3. SSH2 requires a separate license option and installation package.7.6.3. 1.2.0 can be run under 64-bit Windows 7.15. See section 20.4.0.4. Such technology expansions will then be possible to do remotely by means of a scanner software upgrade. NT12-7002 ver 1.

GT-B3740 LTE/UMTS dual-technology devices. More LTE information elements obtainable with Qualcomm chipset based devices: MAC PDU Handover Interruption Time. MTSI Session Setup Failure Ratio (%). • • Additional New Features Internal GPS of PCTel MX available as data source in TEMS Investigation. PUSCH Phy Throughput. UMTS network connect can be done from within TEMS Investigation with Samsung GT-B3730. Possible to select AMR-NB or AMR-WB as VoIP speech codec. 2. The KPI computation itself is done in TEMS Discovery or TEMS Automatic. Position of Minimum k Distribution. PBCH BLER. MTSI Session Setup Time (s).0 generates lower CPU load than previous versions. • • 24 . MTSI Session Completion Failure Ratio (%). Underruns. Special Subframe Configuration.10. Other improvements include better memory management and reduced start-up time. 2. TEMS Investigation 13.11. – – – • TD-LTE information elements introduced: Ack Reporting Mode.4. PDSCH Transmission Distribution elements. Np and Np+1 Distribution. Size Increase (frequency of jitter buffer size increases).0. nCCE Average/Min/Max.9. Extensive set of VoIP jitter buffer metrics obtained as information elements: RFC 1889 Jitter. Average/Min/Max Playout Delay. Performance Improvements For any given device configuration and test setup. Decoding Errors. Overruns.TEMS Investigation 14. HSUPA: New information element “HS UL E-DCH TTI (ms)” indicating TTI length (2 ms or 10 ms). Events generated enabling computation of the following VoIP KPIs: MTSI Registration Failure Ratio (%). MTSI Registration Time (s).4. UL/DL Configuration.1 Improved VoIP testing: PJSIP VoIP client added as alternative to CounterPath.4. Lost Packets.1 User’s Manual 2. Possible to select AMR speech codec rate. • – – New Features in TEMS Investigation 13. UL/DL Configuration Type. PCFICH CFI Information.

Support added for ZTE AL621. Support added for Qualcomm TD9200 TDD. Support added for Samsung SCH-I510. Support added for Sierra Wireless AC320U. Support added for Samsung SGH-A307 (LTE part). Support added for ZTE MF682. Support added for LG FM300. Support added for ZTE AL611. Support added for LG MN270. Support added for Samsung SCH-R380.0 25 . NT12-7002 ver 1.Chapter 2. Recently Introduced Features in TEMS Investigation • • • • • • • • • • • • Timestamps given with 1 ms resolution in message windows and logfile text format export. Support added for Vodafone K5005.

TEMS Investigation 14. Recommended Skills Since TEMS Investigation is a Windows application. • Choose Start  Programs  Ascom  TEMS Products  TEMS Investigation 14.2.1 User’s Manual 3. To obtain a genuine understanding of the presented information. In Windows Vista and Windows 7 you must run the application as administrator. Quick Guide to the User Interface This section gives a quick overview of the TEMS Investigation user interface. familiarity with Windows is useful.4. Installing TEMS Investigation See the Getting Started Manual.1. you need a working knowledge of the wireless technologies concerned. This option is selected by right-clicking the Start menu item above and choosing Properties  Shortcut tab  Advanced. Basics of TEMS Investigation This chapter guides you through some fundamentals of TEMS Investigation. 3. Note: We recommend that you plug the external equipment you are going to use into the PC before starting TEMS Investigation. The overall structure of the user interface is described in more detail in chapters 4 and 5.2. 3. 3. 26 . Starting TEMS Investigation Once installed.1. 3. chapter 5 and section 8.3. TEMS Investigation can be launched from the Start menu.

and manage your worksheets. Navigator From the Navigator you manage your connected equipment or view information on the currently loaded logfile. Only one workspace can be open at a time. Basics of TEMS Investigation Toolbars Menu bar Worksheet Navigator Status bar Workspace and Worksheets The entity that stores all the windows and settings used in a working session is called the workspace. From here you also open presentation windows. Up to ten worksheets can be active simultaneously.Chapter 3. Most of the toolbar buttons are mirrored in the menus. NT12-7002 ver 1. particularly those relating to logfile recording and analysis.0 27 . Toolbars The toolbars provide shortcuts to certain functions in the application. you can divide your workspace into several worksheets. change the mode of presentation of information elements. To manage your windows more smoothly.

1 User’s Manual Menu Bar The menus mirror the toolbars as well as the Navigator’s Menu and Worksheets tabs.TEMS Investigation 14. Status Bar The status bar displays various messages that indicate the current status of the application. 28 .

4. see section 8.0 29 . Deactivating all external devices returns the application to analysis mode. the application is in analysis mode.4.1. you must close it before you can activate external devices. User Interface 4. NT12-7002 ver 1. User Interface This chapter goes through the user interface in more detail. it switches to drive testing mode and remains in this mode as long as some external device is activated. At the beginning of a session.Chapter 4.4. however. This means that: • • If you have a logfile open. Note: You do not set the working mode explicitly in the user interface. • The two modes are mutually exclusive. and can be seen as an expanded version of section 3. nor is the current mode shown there. you must first deactivate all currently active external devices.) In drive testing mode you can record new logfiles. User Modes TEMS Investigation can be run in two different modes. (Regarding the “activate” operation. As soon as you activate external equipment. To be able to open a logfile. The terminology is used in the manual to clarify how things work. one for testing and recording. and one for logfile analysis: • Drive testing mode: The information presented on the screen is obtained from data-collecting devices connected to the PC and activated in TEMS Investigation. Analysis mode: The presented information is read from a logfile which you have loaded in order to inspect and analyze it.

empty workspace. The dialog cannot be opened again. The workspace selection dialog closes automatically after 10 seconds if there is no user interaction. the default workspace (identified in the dialog) is opened. A timer in the lower left corner indicates the remaining time. Click OK and TEMS Investigation will start with the chosen workspace.2. where it is automatically selected. later on. 4.2.1 User’s Manual 4. Settings include information on connected external devices. Only one workspace can be open at a time. When you start TEMS Investigation. If you click OK without making any selection in the dialog shown above. Workspaces and Worksheets Workspaces The environment that stores all the windows and settings used in a working session is called the workspace. where you browse the file system to select a workspace file. you handle workspaces 30 . a workspace selection dialog opens: • • • Open a Recent Workspace: Here you can open an existing workspace by selecting it from a list of recently used workspace files (*.TEMS Investigation 14.tdc). The chosen workspace is added to the workspace list in the dialog above.1. Archived Material: This option takes you to the regular open workspace dialog. Create a New Workspace: This option creates a new.

you can divide your workspace into several worksheets. Worksheets To manage your windows more smoothly.Chapter 4.tdc To start the application with the most recently used workspace.2. you can launch TEMS Investigation with that workspace loaded by giving the following command: investigation. give the following command: investigation. whether predefined or user-created.1.2.2.exe <workspace name>. To save your modifications. • If you know the exact name of the workspace you want to use.3. User Interface from the File and View toolbar (see section 4. This is already done in the default workspace. give the following command: investigation. 4.1. as shown by their designations. TEMS Investigation 14. They all normally reside in the following directory: • • Windows 7.exe -recent To start the application without loading any existing workspace. some further predefined workspaces are supplied.exe -newwksp • • 4.2.0 31 .1 cannot load workspaces from older TEMS Investigation versions.1\Workspaces Windows XP: C:\Documents and Settings\<user>\My Documents\TEMS Product Files\TEMS Investigation 14. NT12-7002 ver 1. Opening Workspaces from a Command Prompt Alternatively. 4.2. you can use the Command Prompt to launch TEMS Investigation with a specific workspace.1\Workspaces Note: You cannot save changes to the predefined workspaces.4 for further details). Windows Vista: C:\Users\<user>\Documents\TEMS Product Files\TEMS Investigation 14. Predefined Workspaces Besides the default workspace. which has a number of worksheets dedicated to different purposes. All of the commands that follow need to be executed from the directory <TEMS Investigation install dir>\Application. or alternatively from the File menu.1. save the workspace under a different name. Up to ten worksheets can be active simultaneously.

1.2. “MS1” is replaced by “MS2”.1.2. The Toolbars The toolbars in the main window give speedy access to some of the most central functions of TEMS Investigation.1. For a full description of the recording function. See section 11. the logfile is closed. When you stop the recording. Equipment handling is done from the Equipment tab of the Navigator.3. Recording properties are set from the Logfile menu. Record Toolbar Start/Stop Recording: Start/stop recording a logfile. 4. The toolbars are mirrored in the menus (see section 4. Note that this operation only presents logfile metadata. See section 11. Open/Close Logfile: Open a logfile/Close the logfile that is currently open.3. 4. see section 11. Fast Forward/Stop: Start or resume loading of the opened logfile/Stop loading of the opened logfile. 32 . Insert Filemark: Insert a filemark in the logfile.TEMS Investigation 14. see chapters 7–9.3. the device channel (“MS”/“DC”) index is incremented in all windows: for example. not the full contents of the file. which can also be accessed by right-clicking in a worksheet.5). When you copy a worksheet. This allows you to instantly duplicate a worksheet for a different device.1 User’s Manual Worksheets are handled from the Worksheet menu. 4. Replay Toolbar This toolbar is accessible in analysis mode.2.

NT12-7002 ver 1.2.Chapter 4.4. The Status Bar The status bar at the bottom of the main window displays symbols and short messages concerning the current status of the application and of external devices. Compare section 11. File and View Toolbar New Workspace: Create a new workspace. “Play” Section This section is active in analysis mode. Print: Print the selected window. 4. It is divided into the following sections: 4. During loading of a logfile. Save Workspace: Save a workspace. Toggle Full Screen: Toggle between full screen and normal mode.4.3. Open Workspace: Open a saved workspace. Help Section Shows a help text when you point to a button or combo box on the main window toolbars.8. See section 11. otherwise directs you to the online help: 4. User Interface 4.0 33 . Report Toolbar Generate Report: Generate a report from one or several logfiles.4.4.3. the progress bar shows what proportion of the logfile has been loaded. 4.1.3.2. Print Preview: Show a preview of the window printout.

Compare section 11. 11.5.1. 34 .4.1. Control. a rolling progress bar is displayed here. When some form of logfile recording is ongoing. Worksheet Menu From this menu you manage your worksheets. and to the about page.2.TEMS Investigation 14. View Menu From here you choose which toolbars and which other tools should be visible. Logfile Menu The Logfile menu mirrors the Record and Replay toolbars. The Full Screen mode hides the Navigator. export logfiles. File Menu The Menu Bar Apart from holding some standard File menu commands.1 User’s Manual 4.3. containing the same information as this manual.8 respectively). and Configuration Menus These menus mirror the Menu tab of the Navigator. 4. From here you can also set recording properties. this menu mirrors part of the File and View toolbar. Help Menu Gives access to online help. and generate logfile reports (see sections 11. and 11. Window Menu This is a standard window manager. “Record” Section This section is active in drive testing mode.6. Presentation.

can also be performed from the keyboard. NT12-7002 ver 1.0 35 . A list of keyboard shortcuts is found in appendix A. User Interface 4.6. Keyboard Shortcuts A number of central operations in TEMS Investigation.Chapter 4. as well as many standard file and edit operations.

Equipment Tab See chapters 7–9. Menu Tab The Menu tab lists most types of windows that are available in the application. located on the left in the TEMS Investigation main window. used for equipment handling: section 5.2. or drag the symbol from the Navigator to the worksheet where you want it. showing information on the logfile currently loaded: section 5. The Navigator has the following tabs: • • • • • the Equipment tab. How the windows work and how they can be configured is covered in the present document: see chapters 23– 31.1 the Menu tab.2 the Info Element tab. giving an overview of your current workspace configuration: section 5. chapter 8 for descriptions of the contents of individual presentation windows. The Navigator The Navigator pane. Control. 5.3 the Logfile tab. You can hide the Navigator by switching to full screen mode (done from the View menu or from the File and View toolbar). listing the types of windows provided: section 5. allows you to set up and manage your workspace and your external equipment.4 the Worksheets tab. double-click the corresponding symbol. listing information elements: section 5. 36 . and Configuration. They are divided into the categories Presentation. All Navigator windows can also be opened from the menu bar. To open a window.1. 5.5.1 User’s Manual 5. See Information Elements and Events.TEMS Investigation 14.

see section 23. right-click the element in the Navigator and select Add  Color.5). Info Element Tab The Info Element tab lists all the information elements handled by TEMS Investigation. Size: Range of plot marker sizes encoding the IE value in Map windows. The Navigator The control and configuration windows are also described in this volume. these settings are automatically used unless you have specified a different usage in that particular window (possible only with colors in certain window types. • Editing the Color Ranges of Information Elements If you want to add color ranges to an information element. NT12-7002 ver 1. those not of type “Text”) can be defined presentation attributes which determine the graphical presentation of the element as a function of its numeric value. see Information Elements and Events. When you add an information element to a presentation window. others do not. The attributes are: • • • Color: Range of colors used to encode the IE value (in a variety of presentation windows).3.3. Regarding information element categories. 5. 5.2. Symbol: Range of plot marker shapes (symbols) encoding the IE value in Map windows.2. Presentation Attributes of Information Elements For all numeric information elements (that is. see section 5. 5.1. Some numeric elements have such presentation attributes defined by default.3. The attributes are edited from the Info Element tab. Please use the alphabetical index to locate them.Chapter 5.0 37 .3.

38 .TEMS Investigation 14.3. continue as follows: 5.2.1 User’s Manual • If you want to edit the default color ranges of an information element. Under From Color and To Color. • Automatic Setup of Color Ranges This is the easiest way to set up color ranges. then double-click Color.1. In either case. double-click the information element to expand it and show the presentation attributes. choose colors for the extremes of the value range. Click Auto Setup. • • Set the number of intervals.

3. 5. follow these steps: • To add an interval. The Navigator • Check the Via Color box if you want to use a specific color in the middle of the range. the intermediate color is chosen automatically based on the “From” and “To” colors. When you click OK. and make your changes. and choose a color.4.3. click Add.3. set the endpoints of the interval.2. If you delete parts of the color range so that no color is defined for some values. Manual Setup of Color Ranges If you prefer to assemble your color range interval by interval.2 above. click Edit.0 39 . If you do not check the Via Color box. A single remaining interval cannot be deleted. a color range is created automatically with evenly sized intervals and suitable intermediate colors. nor can the color range as a whole be removed. 5. these values will be drawn in black. select it and click Delete. Logfile Tab See section 11. NT12-7002 ver 1. Editing the Marker Sizes and Symbols of Information Elements Ranges for map plot marker sizes and symbols are edited in exactly the same way as color ranges. To delete an interval.3. select it. • • To edit an interval. 5.2.2. See section 5.Chapter 5.

1 User’s Manual 5.5. Worksheets Tab The Worksheets tab lists the worksheets currently active in the workspace. 40 . You can rearrange windows from this tab by dragging them between the worksheet folders.TEMS Investigation 14. Each worksheet is represented by a folder containing the windows in this worksheet. Double-clicking on a symbol will make that particular window (and the worksheet it is placed on) active.

xsd defines TEMS-specific XML data types.0 41 . TEMS Investigation specific format (*. it is possible to draw cells on maps and to display cell names in various windows. Cell data is also made use of in logfile reports.Chapter 6.xml) whose format is common to several TEMS products: See section 6. CDMA cell files in TEMS Investigation CDMA CSV format can be converted to the XML format using TEMS Discovery. section 4. A full description of the XML format is found in the Technical Reference. In particular. relying on the data types in TEMSDataTypes.cel). chapter 4.3. • The most convenient way of composing XML-format cell files is to load the above schemas into a suitable XML development tool. GSM and WCDMA cells can be mixed in one file. derived from the fundamental data types set down in the XML specification. Creating a Cell File in XML Format The XML-format cell file uses two XML schemas.2.1. Cell Data TEMS Investigation can present information on individual cells in cellular networks. see the Technical Reference. which are found in the directory XMLSchema beneath the TEMS Investigation installation directory: • The schema TEMSDataTypes. See section 6. Regarding TEMS Investigation CDMA CSV cell files in general. 6.xsd. The schema TEMSCell.1. Cell data can be provided in two ways: • • in a plain-text XML file (*. This format is for UMTS only. Cell Data 6.xsd defines XML attributes and elements that embody cell and site data. in a file with a plain-text. NT12-7002 ver 1. and fill in the data from there.

5. • • • • • From the Navigator’s Menu tab.5. 6. if you load both CEL and XML files. it must be loaded in the General window.5. and 31. chapter 3. Otherwise. If multiple files of the same type (CEL or XML) are loaded. When you are done selecting cell files to load. Loading Cell Data from Mentum CellPlanner Mentum CellPlanner uses the XML format for cell data.4.5.5. 6. 6. To remove a cell file from the list.3. Loading Cell Files To make a cell file active.3. be sure to save them in tab-delimited plain text format. open the General window. click the Add button and browse to select your file.1. click OK. If you use a spreadsheet application to edit CEL files. You can have several cell files loaded in the application at the same time.5. In the General window. To add a cell file. The cell file is added in the list box. the information in all files is correlated in the presentation. Creating a Cell File in CEL Format The CEL format is a unified version allowing both GSM and WCDMA cells in the same file. the following functions become available in the application: • Drawing of cells and indication of neighbor relations and channel usage on the map. See sections 31.TEMS Investigation 14.1 User’s Manual 6. select it and click Remove. XML cell files created with Mentum CellPlanner can be loaded into TEMS Investigation. It is described exhaustively in the Technical Reference.5. To remove all cell files. 31.2. However. rather. no attempt is made to correlate CEL and XML cell information. The set of loaded cell files can be modified at any time. 42 . cell information is presented separately from each type of file.4. unwanted characters might be inserted which prevent TEMS Investigation from interpreting the file correctly. double-click the item Cellfile Load. Use of Cell Data in Presentations Once cell data has been loaded. click Remove all.

See Information Elements and Events. Line charts: section 29.0 43 .3.2–24. In logfile reports: Association of statistics with individual cells.2.5. Bar charts: section 30. Cell Data • • • Serving cell and handover indication on the map. • • • • NT12-7002 ver 1. Best server indication on the map. See section 31.4. Presentation of cell data on the Info tab of a Map window. See the Technical Reference. Indication of distance from current position to current serving cell. See section 31.3. Configuration of status windows is covered in sections 24.5. See section 31. based on scan data. chapter 3 (“Cell Distance” IEs). Generation of events detecting (probable) missing neighbors. line charts.Chapter 6. and bar charts.3.2.6.5. chapter 7.4. Presentation of cell names in status windows. See Information Elements and Events.5. section 10. Computation of cell ranking based on these statistics.

Provides shortcut to device properties. 7.2. chapter 10. The in-focus device can be changed with a context menu command. which is covered in chapter 20. and many more besides. Managing External Equipment: General This chapter summarizes how external equipment is handled in TEMS Investigation.1 User’s Manual 7. See chapter 21. Activities tab: From here you can manually apply various commands to and perform various actions with the selected device. Connectable Equipment The range of equipment that is compatible with TEMS Investigation is given in the Getting Started Manual. See chapter 9.1. The functionality here relates to the device that is currently selected in the top pane. Overview of User Interface Components Dealing with External Equipment Equipment tab of Navigator: • Top pane: – Shows the devices currently plugged into the PC and has controls for activating and deactivating the devices in TEMS Investigation. – – • Bottom pane: – – 44 . One device at a time is in focus in this pane. 7. Full details follow in chapters 8–10. See chapter 8. All of these tasks.TEMS Investigation 14. can be automated using the Service Control tool.

turn to chapter 10. Status Control Monitor: This window gives a quick overview of the status of current tasks.Chapter 7.3. of equipment connected.0 45 . NT12-7002 ver 1. The information shown in this window can be found in other places in the application or can be retrieved with the Computer Diagnostics tool. See section 8. and of the PC. Managing External Equipment: General – Information tab: Shows some basic data on the selected device. its purpose is to give an at-a-glance overview of vital data in one place. For further information.

Scan scanner Rohde & Schwarz TSMW scanner GS Chapter 11 12 13 14 8. For some devices. 46 .1. The only exceptions to this rule are handled using the Manual UE Configuration utility. see the Getting Started Manual. Plugging In External Equipment Note first of all that devices may be mounted in an equipment case.1 User’s Manual 8. section 7. section 10. so that they will not be plugged directly into the PC.1. External devices supported by TEMS Investigation are automatically detected by the application after they have been plugged into the PC.6. see the Getting Started Manual. Activating External Equipment This chapter describes how to activate external devices in TEMS Investigation for the purpose of data collection. special configuration of both device and PC is required. Special PC and Device Configuration Requirements Regarding device-specific preparations for running data services. These steps are covered in the Getting Started Manual as follows: Device Ericsson Fixed Wireless Terminal DRT scanner Andrew i.TEMS Investigation 14.

Rohde & Schwarz TSMW and DRT scanners connect to an Ethernet port. EX. either directly on the PC or via a local area network. • Plugging In Scanners SRUs connect via USB. (See the Getting Started Manual. a 100Base-T crossover cable is used for this purpose. Anritsu ML8780A scanners connect via USB. NT12-7002 ver 1. Andrew i. LX MM2. Workaround: Restart the TEMS Device Manager service in Windows. chapter 11. Flashing red: The SRU does not have sufficient power to start up the scanning module.Scan. and so no startup command is sent to the scanning module. – If the scanner is connected directly to the PC. so that the SRU’s scanning module has started up.3. the black one must always be connected. 8. while the red one can optionally be used to power supply the device (the other option is to use an external 12 V power source).) 8.) Flashing green: The SRU has sufficient power. but the TEMS Device Manager has not started or cannot detect the SRU. A single USB cable connects the USB port on the device to a USB port on the PC.1.0 47 . Other PCTel SeeGull LX scanners connect to a COM port.2.1. The device has two USB plugs. or connect the power connector of the SRU cable to an external 12 V power source. Plugging In Phones and Data Cards Most supported phones and data cards connect to the PC via USB.1. and PCTel PCT scanners connect via USB. Plugging In Ericsson Fixed Wireless Terminals An Ericsson Fixed Wireless Terminal is connected to the PC by means of a LAN cable.Chapter 8. (All OK. and the Windows service “TEMS Device Manager” has detected the SRU. Activating External Equipment 8.1. Plug in the red USB plug. The “Status” LED on the SRU front panel is interpreted as follows: – Steady green: The SRU has sufficient power. Anritsu ML8720 scanners connect to a COM port. – – • • • • • PCTel SeeGull MX.

1.5. Plugging In Stand-alone AQM Modules The stand-alone AQM module connects to the PC via USB.1. In Windows 7 and Windows Vista you must run the application as administrator. 8. Plugging In GPS Units Supported GPS units connect via USB or Bluetooth. both should be connected to local area network ports with normal 100Base-T cables.TEMS Investigation 14. The Navigator Equipment Tab: Basics Top Pane All devices detected by TEMS Investigation are listed in the top pane of the Navigator’s Equipment tab. or to a COM port. An audio cable is connected between the AQM module and its associated phone.1. This option is selected by right-clicking the Start menu item above and choosing Properties  Shortcut tab  Advanced. 8. The AQM module also requires a separate 12 V power supply (the voltage provided through the USB connector is insufficient). 8.1.1 User’s Manual – If the scanner and PC are to communicate over a local area network.4. 8. 8. Plugging In Equipment Cases All supported equipment cases connect via USB.6. In the example below. a Sony Ericsson Z750i phone has been autodetected.3.3.1. 48 . • Starting TEMS Investigation Launch the application as follows: Choose Start  Programs  Ascom  TEMS Products  TEMS Investigation 14.2. 8.

Device Context Menu If you right-click an EQ item.3.3.0 49 .Chapter 8. Change Equipment: Select a number to change the device’s EQ index to that number. Activating External Equipment Each device is represented by a numbered “EQ” item.3.1. a context menu pops up containing the following commands: • • Activate. external devices are represented by their channels (“MS”/“DC”/“PS”).5 8. • NT12-7002 ver 1. Properties: This menu item takes you to the device properties. Deactivate: How to activate and deactivate devices is explained in section 8. See section 23. It is possible to select an index that is already taken by another device.3.1.5 Device is selected as preferred GPS: see section 8.1. Please note that in presentation windows.4. You can change the EQ index assigned to the device: see section 8. the two devices will then swap indices.3. see chapter 21. device string is red Earth symbol Device is activated Device is deactivated Device activation or deactivation is in progress Device has no license: see section 8.1. The icon to the left of each device shows the status of the device in TEMS Investigation: No symbol added Red cross Hourglass Prohibited sign and label “NL”.

3. A phone number retrieved by an AT command will always override a manually entered number.1. Bottom Pane “Activities” Subtab See chapter 9. or because the phone did not respond properly to the AT command. PESQ. 8. the number of the phone must be known to TEMS Investigation. the autodetect procedure sends an AT command to it in order to find out the phone number. It will also be used on future occasions when the phone is plugged in. The number you enter will be used for this phone from now on. unless the AT command succeeds at that time.3. which is usually stored on the SIM card. Editable field. Examples of identification strings: • • • • IMEI for UMTS phones (in the EQ row) ESN for CDMA phones (in the EQ row) serial number for DRT scanners (in the EQ row) the identity of an AQM module paired with the phone (in the MS row). Data.2. If this operation succeeds. Device identity. If a phone is going to measure AQM in a Call Generator/MRU configuration. If no phone number shows.2.3. 50 . In such cases you need to enter the phone number manually in this field. this may be because no phone number is defined on the SIM. The phone number of a user terminal. Examples: IP Sniff.1 User’s Manual 8.2. Position.TEMS Investigation 14.2. Air Interface. When you plug in a phone. the phone number will display here. “Information” Subtab Capabilities of the device. Capabilities Identity IMSI Phone Number Shows the IMSI of a UMTS phone’s subscription. 8.

8. etc. and do not reconnect it until the scanner has started up again (green LED). Detection of DRT Scanners and Rohde & Schwarz TSMW For technical reasons.1). Verizon branded.0 51 . AT&T branded. 8. Below.Chapter 8.3.4. Therefore. 8.).3. If you need to power cycle the scanner during use. TEMS Investigation attempts detection of DRT and R&S scanners only at startup and when you click the Refresh button on the Navigator’s Equipment tab (see section 8.3. Always wait for the scanner to boot completely (LED turns dark green) before starting TEMS Investigation.6.3.3. pull the USB cable before doing so. This can take up to 90 seconds (during which time the LED is pale green or orange). a brief description is given of what needs to be done. you need to click the Refresh button to have it detected. • • Detection of PCTel SeeGull MX Scanner After installing the driver. 8. On all phones you need to activate tethering via USB while the phone is connected to the PC by the USB cable. • • Detection of Equipment: Special Cases Detection of PCTel SeeGull EX Scanner Start up the scanner without the USB cable connected. if you plug in one of those scanners after starting TEMS Investigation. 8.3. and Windows has detected the device for the first time.3. Detection of HTC Touch Pro2 Phones HTC Touch Pro2 phones (including HTC Imagio) need some configuring before TEMS Investigation can detect them. the scanner should be rebooted.3.3.3. Activating External Equipment Ports Ports exposed by the device.3.1.2. Wait until the LED turns green before plugging the USB cable into the scanner. The details of the configuration differ depending on the phone (unbranded. Tethering means using a mobile device as a modem to provide Internet access to an unconnected device – in NT12-7002 ver 1.

This is provided by Ascom in the form of a CAB file. On all HTC Touch Pro2 phones except Verizon branded ones. only one phone at a time can be used with TEMS Investigation.3.TEMS Investigation 14.5.3.3. IP sniffing needs to be disabled. That means that KPI data cannot be collected with these phones. it cannot of course be activated in TEMS Investigation. activate “Internet Sharing”. as granted by your TEMS Investigation license.3. the PC on which TEMS Investigation is running. Of phones having the “Internet Sharing” function.1. When a device has no license.3. In each case. On other HTC Touch Pro2 phones. For instructions. However. and the icon will be tagged with a “prohibited” sign and accompanied by the text “NL” (for “No License”): The same thing will happen if by plugging in a device you exceed the number of devices with which you can do simultaneous data collection. 8. WLAN) is by default disabled.3. For HTC Touch Pro2 phones generally. activate the “Modem link”. See the Getting Started Manual. this operation creates ports in Windows that TEMS Investigation can detect. please refer to section 20. Detection of Network Adapters Detection of network adapters (LAN. the text for this device will be red. section 3.1 User’s Manual this case. This limitation does not apply to the Verizon branded phones.6. it will still appear on the Navigator’s Equipment tab. The terminology used to refer to tethering differs between phones: • • On a Verizon branded phone. This is to prevent an inordinate number of devices from appearing in TEMS Investigation when you are doing data collection with multiple devices.16. 8. Detection of Equipment Not Covered by License If you plug in a type of device for which you have no license. you also need to install TCP Router software. 52 .1.

Chapter 8. The Device Configuration tab is the most commonly used.3). User-assisted Detection of Devices If a device is not detected properly by TEMS Investigation. Alternatively.1. section 7. On the Equipment tab of the Navigator. see the Getting Started Manual.4. • On the Port Configuration tab you create an entry that is directly mapped to a COM port number on the PC. You must restart the application for the change to take effect. It creates an entry for the device that can be reused independently of the actual COM port number used for the device.2. 8. see section 11.exe. section 7.1. You must enable network adapter detection if you want to transfer logfiles over a LAN or WLAN connection. The Port Configuration tab is mainly used for Datang devices. The tool Manual UE Configuration has two tabs where you create different kinds of entries used in the detection phase: Device Configuration and Port Configuration.6. Activating External Equipment • To enable detection of network adapters. then you can run the Manual UE Configuration utility to help TEMS Investigation recognize the device.3.5. Normally there is no need to do this.0 53 . you can launch this utility by running the file <TEMS Investigation install dir>\Application\ManualUEConfig. set the Network Card device to enabled in the Device Detection Properties dialog (see section 8. although it is supported. • NT12-7002 ver 1. click the button Start Manual UE Config. there are however certain devices for which you must use Manual UE Configuration as an aid to detection – see the Getting Started Manual.

click OK.3. You can change this assignment by modifying the selections in the combo boxes.1–8. A dialog titled Select your device appears. choose the correct device type according to its capabilities. In the Ports section. • • • Under Name. click the New button to create a new entry. In the tree view. Then click OK. • • 54 .4.4. (The string does not show anywhere else in TEMS Investigation. Finally. Click Save and Close.) Under Type. • The Manage Device dialog appears. all ports of the device are listed. In the combo boxes on the right is indicated the functional assignment of each port in TEMS Investigation. Select the type of device to use and map each available port on the device to its function. select the device root node that contains the ports of interest.3. The device is added to the list in the main window.TEMS Investigation 14.4.1 User’s Manual • On the Device Configuration tab. Ports that do not have a mapping can be left blank or undefined. enter a name for the device. See also sections 8.

The TYPE tag is mapped towards the interfaces. Mapping Device Ports to Interfaces If it is not clear which port should be mapped to which interface. (If you are running the Manual UE Configuration utility independently. the entries in the existing UEDescription.0 55 .1.) Below are some examples of mappings in UEDescription.xml file (found under <TEMS Investigation install dir>\Application) may give an indication.4. This is necessary to update TEMS Investigation with the device configuration just defined.3. Activating External Equipment Click the Refresh button in the Navigator.) 8. (See the XML code excerpt below. TEMS Investigation will update itself automatically with this data when launched.xml: LG LTE LTE DM – AT Ndis Samsung LTE LTE DM – AT Ndis Function Air Interface Data Interface AT Interface Ethernet Interface Qualcomm Diag:xxx Data Modem AT Ndis ST Ericsson Modem Data Modem Device Management Ndis For a Samsung LTE modem (third column above) this corresponds to the following selections in the Manage Device dialog: NT12-7002 ver 1.Chapter 8. and the DESCRIPTION tag is the name displayed in the tool.

select the appropriate chipset family. click OK. pair each available port to the correct port type as shown in the screenshot below. 56 . Qualcomm Devices with LTE/TD-LTE Capability These are devices built on the Qualcomm MDM9x00 chipset families (TEMS Investigation license options “Qualcomm E” and “Qualcomm F”).4.TEMS Investigation 14.xml itself the following entry appears: <PRODUCT NAME="This name is not displayed anywhere" PID="6889" FAMILY="SAMSUNG"> <DEVICE DESCRIPTION="Samsung USB LTE Adapter" SETUPCLASS="Net" TYPE="Ndis" /> <DEVICE DESCRIPTION="Samsung LTE Control Port" SETUPCLASS="Ports" TYPE="AT"/> </PRODUCT> 8. In the Manage Device dialog. Launch the Manual UE Configuration utility and select your device as described in the introduction of section 8. do as follows.2.1 User’s Manual In the file UEDescription. Finally.4. in the Ports section. Under Type. 1.3.3. Then. 2.

4. 8.3.4. set Type to “Samsung LTE Modem”. If the device has a “Samsung LTE Control Port” that answers to AT commands. LG and Samsung Devices with LTE Capability 1. Activating External Equipment 3. USB NDIS” (or similar) to the “Ethernet Interface” function. Also identify and map the ports to use for air interface messages (“Air Interface”) and AT communication (“AT Interface”).0 57 . 3. set Type to “LG Electronics LTE Modem”. 2. assign the port named “. NT12-7002 ver 1. TEMS Investigation will detect the Qualcomm device as being of the type you selected in step 2. From now on..3. assign that port to “AT Interface”.Chapter 8. Click Save and then Close. For an LG device. assign the port named “Samsung USB LTE Adapter” to the “Ethernet Interface” function.3. Under Ports. The device is added to the list in the main dialog window. Launch the Manual UE Configuration utility and select your device as described in the introduction of section 8. Under Ports. For a Samsung device..

3.1 User’s Manual 4. provided that it comes with Windows drivers enabling an IP data connection. Below is an example. Map the device ports as appropriate.4. 8. set Type to “Data Only Device” in the Manage Device dialog.4.TEMS Investigation 14. 8.4. • • If you want to use a device that is not officially supported. 58 . All IP-based services can be tested (as well as video streaming).4. Activating and Deactivating External Equipment in TEMS Investigation Activating External Equipment 8. The device is added to the list in the main dialog window. Click Save and then Close.1. and all IP-related information elements will then be populated. You need to activate a device in TEMS Investigation before you can use it for data collection. Data Service Testing with Arbitrary Devices Data service testing in TEMS Investigation can be done with any applicable device (even if not officially supported by Ascom).

Limitations for Particular Devices • If the device connection must be set up using an external connection manager application. but deactivate it in TEMS Investigation for the time being. see chapter 9.4. do as follows: • Right-click the device on the Equipment tab and choose Deactivate from the context menu. and a GPS device starts reporting positions.2. NT12-7002 ver 1. right-click it on the Navigator’s Equipment tab and choose Activate from the context menu. you must close it to be able to activate equipment. Once the device has an APN.6. Activating External Equipment Note: If you have a logfile open. The red cross disappears from each device icon to indicate that the device is now active. click the Activate All button on the Navigator toolbar. a phone device starts delivering idle mode reports. when you select an activated device in the Navigator top pane. Furthermore. On being activated. Note: A device that is going to use an NDIS data connection must have an APN assigned to it. Deactivating External Equipment If you want to leave an external device plugged into the PC. • 8.Chapter 8.3. Of HTC Touch Pro2 phones having an “Internet Sharing” function and requiring installation of TCP Router software. Compare section 8. the Activities tab in the bottom pane is populated with the operations that you can perform manually on this device.4.0 59 . section 10. Regarding these operations. To activate all detected devices. you can activate it in TEMS Investigation. only one phone at a time can be activated in TEMS Investigation. See the Getting Started Manual. only one such device at a time can be activated in TEMS Investigation (unless the connection manager supports multiple devices).3. • To activate a detected device.1.

then all detected GPS units are activated but the currently preferred GPS remains preferred (and only this one will update positioning data in the application). only one at a time can update the positioning-related information elements in TEMS Investigation. 8.TEMS Investigation 14. and you click the Activate All button. The device responsible for this will be the one tagged with an “earth” symbol on the Navigator’s Equipment tab. the “Preferred” setting cannot be changed. If no GPS is activated.1 User’s Manual To deactivate all active devices: Click the Deactivate All button on the Equipment tab toolbar. If no GPS is activated in TEMS Investigation.5.1 However. and they will then all be detected by TEMS Investigation. This includes GPS units built into scanners. are currently not recognized by TEMS Investigation. As long as a GPS or some other device is activated in TEMS Investigation. It is referred to as the current Preferred GPS. while multiple GPS units can be detected and activated. While a logfile is being recorded. the “Preferred” setting cannot be changed. GPS units in phones. on the other hand. that GPS automatically becomes the preferred one. Managing GPS Units It is possible to have several positioning devices plugged into the PC. and you activate one GPS. • • 1. as shown in the tooltip: The following rules apply: • • • The first GPS unit detected automatically becomes the preferred one and remains as such even if further GPS units are plugged in and detected. 60 .

first deactivate any devices that are activated and stop logfile recording if applicable. This function operates the same way whether your AQM modules are standalone or mounted in an equipment case.6. the text “UE not paired” will be displayed in the PESQ Device Pairing dialog.4.1. If the devices you connected to the PC were not detected properly (for whatever reason). The earth symbol and “Preferred GPS” tag will then be transferred to that GPS.6. NT12-7002 ver 1. At any time. mappings between phone IMEIs and AQM module identities are stored by TEMS Investigation in the Windows registry. If a device could not be matched with an AQM module. 8.6. see section 8. Further Features of the Navigator’s Equipment Tab The Refresh Function 8. on the Activities tab. Click the Re-pair Phones with AQM Modules button at the top of the Equipment tab.10.Chapter 8. Re-pairing Phones with AQM Modules When you match phones with AQM modules manually as described in section 9. 8.1. Note that for this to work. then right-click the desired GPS in the Navigator and choose Preferred GPS from the context menu. you can inspect which AQM module is matched with a device by right-clicking the PESQ Device Pairing item under the Control node.2. you can recreate the same pairings automatically in TEMS Investigation. Note that you must always do a refresh after using the Manual UE Configuration utility. you can start the detection procedure over from scratch. When plugging the same phones and AQM modules into the PC on a later occasion. To do this: Click the Refresh button at the top of the Equipment tab.1. the pairing must not have been undone using the Reset function (see section 9. Activating External Equipment • To select a different GPS as the preferred one.10) before the phone was deactivated.3.0 61 .

Note that normally there is no need to do this. the dialog is provided mainly for the purpose of troubleshooting in cases of conflicts during device detection. 62 .1 User’s Manual 8.3. If several phones have previously (at different times) been using the same AQM module. if you are using an equipment case and let two phones swap places. it is a good idea to label the phones and AQM modules in some suitable manner to ensure that each phone is always hooked up to the same AQM module. Each AQM module can only be paired with a single phone. Device Detection Properties The Device Detection Properties dialog can be used to enable and disable detection of various device categories. If you have been working with different equipment configurations connected at various times to the same PC.TEMS Investigation 14.2. only one of them will be paired with it. To prevent this. Details and Limitations of the Re-pairing Function The re-pairing function assumes that the phone-to-AQM-module mappings found in the Windows registry are still valid. the re-pairing will be incorrect for these phones and the AQM data will be garbage. To open this dialog: Click the Device Detection Properties button at the top of the Equipment tab. For example.1.6. 8. the following holds: • • Only AQM modules that are physically present when you click the button will be paired.6. No check is performed that the physical connections are in fact still the same.

you need to restart TEMS Investigation for the change to take effect. 8.7. which would be undesirable most of the time. The latter is disabled because otherwise the PC’s network adapter. The saving extends to all devices whose hardware permits a reliable identification. Saving of the Equipment Configuration When you exit TEMS Investigation. as well as other network adapters accessible via LAN/WLAN. Such devices include phones with their IMEIs. This means that the mappings between devices and EQ items are stored in the Windows registry. As a result. that device will again be mapped to EQ3 the next time it is plugged into the same PC with the same Windows user logged in. By default. would always be detected as EQs in the application. Activating External Equipment The checkbox in the Enabled column determines if detection of a device type is enabled. the configuration on the Navigator’s Equipment tab is automatically saved.3. Compare section 11. you must enable the “Network Card” item. NT12-7002 ver 1.0 63 .5.1. that if you wish to upload logfiles over FTP using the PC network card. If you make changes in this dialog. TEMS Investigation does not save any information on equipment configuration in the workspace. detection is enabled for all device types listed except “Network Card”. however. Note. if a device is represented at one time by (say) EQ3.Chapter 8.

right-click the desired item on the Activities tab and choose Start from the context menu. 64 . • • To execute an operation.TEMS Investigation 14. 9. which covers device property dialogs that provide further means of controlling devices. Operating and Controlling External Equipment Manually From the Navigator’s Equipment tab (bottom pane.1 User’s Manual 9. To stop the operation. For all manual device operations. you double-click the desired item on the Activities tab to open the setup dialog associated with it. Control Functions See also chapter 21. right-click and choose Stop. When operating devices manually. These operations are the subject of the present chapter. you can manually run various services on a device and manually apply control functions to it (as opposed to controlling the device with a script). and particularly the reference material in section 20. you make use of the same configuration sets that you refer to in scripts. Compare chapter 20. Activities “subtab”).1.16.

Samsung Galaxy S 4G Xperia arc S* (Qualc. Regarding other control functions.1. access control BLER target control (WCDMA) Cell lock (+ prevent) PLMN control RAT lock Reserved cells. Note that for devices other than Xperia arc S. Z750i K800i. Sony Ericsson C702/C905*/W760i/W995* Sams.) K790i/a. Supported for Qualcomm chipset based UMTS devices.1.0 Nokia NTM3 65 .3.Chapter 9. see the table below. access control NT12-7002 ver 1. See the Getting Started Manual. Control Function Support by Device The following control functions are independent of cellular technology: Control Function AT commands Nonvolatile item read/write PESQ device pairing Supported By Supported for all connectable devices. WCDMA Barred cells.1. Operating and Controlling External Equipment Manually 9. Supported for devices capable of audio quality measurement using Call Generator/MRU. See chapter 21. these functions are in many instances implemented as device properties instead. section 10. K600i Access class control Band lock. W600i Control Function Samsung Infuse 4G TM506. No. GSM Band lock.

2. Z750i K800i.011.1. Access Class Control Here you can manipulate access class settings ( 3GPP 22.) K790i/a. just like OK. but without exiting the dialog.3.2.1 User’s Manual Sony Ericsson C702/C905*/W760i/W995* Sams. the control function dialogs contain an Apply button. The Set Default Access Class option causes the phone to revert to its default access class settings. No. They are explained in section 21.TEMS Investigation 14. The latter transfers the current dialog settings to the device.1. 66 Nokia NTM3 . Samsung Galaxy S 4G Xperia arc S* (Qualc. K600i RRC WCDMA capability control Speech codec control 9.1.2. 9. chapter 4). W600i Control Function Samsung Infuse 4G TM506. Functions of Dialog Buttons Besides OK and Cancel.

If no AT configuration set exists. see section 21.4. the P-900 band cannot be selected.5.12. you need to create one.1. Click either OK or Apply.1. Each AT command is specified in a configuration set which is identical to that referenced by an AT activity in a Service Control script.2 for details. 9. Operating and Controlling External Equipment Manually 9.0 67 .2. whereas Apply keeps it open. For details. AT Commands The AT item is used to issue AT commands manually.6.16.Chapter 9. BLER Target (WCDMA) This function overrides the BLER target set for the phone by the network. Clicking OK will close the dialog.1. The Default option causes the phone to revert to its default BLER target.1. 9. See section 20. • • Check the bands that the phone should be allowed to use. Band Lock You can restrict the phone’s use of frequency bands. Sony Ericsson Specific Limitations If you make selections under GSM. Only one 900 band at a time can be selected. NT12-7002 ver 1. you need to be aware of the following limitations: • • If the 850 band is selected. What frequency bands appear here depends on what the phone has support for.2. Use the Lock option to change the BLER target to the value selected in the combo box.

2. it can be used to control both cell selection and handover behavior. and it has an effect in idle as well as dedicated (connected) mode.1 User’s Manual 9.8. and other cells.5 (GSM) and 21.2.2.1. The options are the same as in sections 21.1.1. The phone is then restricted to using only these cells. Cell Barred Here you can modify the phone’s behavior with respect to accessing of barred. reserved.1. 68 . The phone is then prevented from using these cells. 9.2. In other words.TEMS Investigation 14.11 (WCDMA). 9. This is the Prevent option in the Cell Lock dialog. • • Cell Lock in GSM For GSM you can do the following: Lock the phone on one or several cells1. Prevent one or several cells.8. Cell Lock The Cell Lock function spans both GSM and WCDMA.7. This is the Allow option in the Cell Lock dialog.

Operating and Controlling External Equipment Manually • To configure the set of cells to which the lock or prevent function should apply. The word “cell” is used somewhat loosely here to mean either an ARFCN or an ARFCN + BSIC combination. NT12-7002 ver 1. click the Add button: • Band selection: Here you specify a GSM band from which to select ARFCNs. 1. See below.0 69 .Chapter 9.

A complete list of BSICs from 00 to 77 is displayed for devices that support BSIC selection. 1. Under Range selection. The phone is then restricted to using only these cells/UARFCNs.1.1 You can define additional items as shown above to extend the ARFCN set. clicking the Add button each time. 134. 9.TEMS Investigation 14.8. or both. Below is an example of a GSM Cell Lock setup. The phone is then prevented from using these cells/UARFCNs. you pick a single ARFCN and one or several BSICs. • • Cell Lock in WCDMA For WCDMA you can do one of the following: Lock the phone to one or several cells and/or UARFCNs. Prevent one or several cells and/or UARFCNs. • To remove an item from the list box. Under Channel selection. The BSIC box is empty in the above screenshot because BSIC selection is not supported for the phone in question. the phone is locked to the ARFCN set {132 . 137} on the GSM 850 MHz band. The ARFCN and the BSIC set are joined by an implicit AND. select it and click Remove..1 User’s Manual • • • Range selection and Channel selection: You can define either of these. 70 . Here. you specify a range of ARFCNs as extending from Start Channel to Stop Channel..2.

0 71 . Range selection is not used for WCDMA. The UARFCN and the SC set are joined by an implicit AND. Under Channel selection.Chapter 9. Operating and Controlling External Equipment Manually • To configure the set of cells/UARFCNs to which the lock or prevent function should apply. NT12-7002 ver 1. click the Add button: • • • Band selection: Here you specify a WCDMA band from which to select UARFCNs. you pick one UARFCN and one or several SCs.

1. Here. 72 .1 User’s Manual You can define additional items as shown above to extend the cell/UARFCN set. select it and click Remove. 5}. the phone is locked on the Band I (2100 MHz) cells having UARFCN 10565 and SCs {3. Nonvolatile Item Read/Write The Nonvolatile Item functions allow you to inspect and modify settings for Qualcomm chipset based UMTS devices by reading and writing items over the Qualcomm NV interface.9. • To remove an item from the list box. 9. The dialog is limited to 4 bytes. Specifics on the NV interface are vendor proprietary and must be obtained from the vendor. this is however sufficient to cover most basic NV items. clicking the Add button each time.TEMS Investigation 14. 4. Below is an example of a WCDMA Cell Lock setup.

You are always prompted to confirm an NV command before it is executed. • NT12-7002 ver 1. Clicking OK will close the dialog. The PESQ Device Pairing item is selectable only for devices supporting audio quality measurements (these are listed in the Getting Started Manual. a read is always performed at the same address. this is how you select the AQM module with which a given EQ should interact. which holds all available AQM modules. indicating that the device has not yet been paired with an AQM module. section 10. Operating and Controlling External Equipment Manually WARNING: It is possible to corrupt the phone’s calibration parameters or otherwise damage the phone by writing the wrong value to the wrong address. identified by their serial numbers.3. and consequently it is deactivated in TEMS Investigation. the string “UE not paired” is displayed. Before an NV write. All traffic over the NV interface is logged in internal protocol reports. After an NV write the phone is always automatically reset. Click either OK or Apply.1. Selecting this item opens the PESQ Device Pairing dialog: • • At the outset.0 73 . PESQ Device Pairing If you are going to do audio quality measurement with a Call Generator or MRU.1). select the appropriate AQM module in the combo box. AQM modules do not themselves appear as EQs on the Equipment tab.10. 9. so if you are recording a logfile in TEMS Investigation it should be possible to recover the previous values of parameters by studying these reports. To accomplish pairing.Chapter 9. whereas Apply keeps it open.

The RAT lock function works only in idle mode.TEMS Investigation 14. you can use the re-pairing function (see section 8. PLMN Control This function locks the device on a PLMN. Two-digit MNC are entered in the first two combo boxes. On later occasions. For example.1 User’s Manual You need to pair off your EQs and AQM modules manually like this the first time around. you can no longer use the re-pairing function. click the Reset button.2) to recreate the same pairing automatically. 74 .6. specified by an MCC and MNC combination just as in section 21.2. provided that the physical connections between phones and AQM modules are unchanged.2. the two-digit MNC “01” is entered like this: On the other hand. Radio Access Technology Lock (Lock on RAT) Certain devices can be locked to a particular radio access technology. Note that if you unpair the devices in this way. There is however one difference compared to the device property setting: The control function allows you to distinguish two-digit and three-digit MNCs. the three-digit MNC “001” (formally distinct from the preceding!) is entered as follows: 9. 9. • If you want to undo the pairing so that the device is no longer associated with any AQM module.1.2. with the third box set to “-”.11.1.12.

Chapter 9. Operating and Controlling External Equipment Manually

The Lock on technology combo box shows the phone’s current RAT lock state. You also use the same combo box to perform RAT lock actions by selecting a new RAT lock state to be applied and then clicking the OK or the Apply button. Clicking OK will close the dialog, whereas Apply keeps it open. Note that the lock on RAT procedure may take some time to complete. The items in the “Lock on technology” combo box have the following meanings: • Not locked – – • – – • – – State: No forcing of UE network selection will occur. Action: Releases a previously applied RAT lock. State: The phone is locked to GSM, that is, the phone is forced to camp on a GSM network whenever one is available. Action: Locks the phone to GSM. State: The phone is locked to WCDMA, that is, the phone is forced to camp on a WCDMA network whenever one is available. Action: Locks the phone to WCDMA.

GSM

WCDMA

NT12-7002 ver 1.0

75

TEMS Investigation 14.1 User’s Manual

9.1.12.1.

RAT Lock vs. Technology-specific Control Functions: Sony Ericsson

This section also applies to the Qualcomm chipset based Sony Ericsson Xperia arc S. The RAT lock setting takes priority over all technology-specific locking functions (channel, cell, and band lock) covered in sections 9.1.5, 21.2.2.6, and 21.2.2.13. On the assumption that both types of network (GSM and WCDMA) are available to the phone, this has the following implications: • If the RAT lock is set to “WCDMA”, the phone will be locked to WCDMA indefinitely1; specifying GSM bands or channels to lock on will not by itself force the phone into GSM mode. Analogously, if the RAT lock is set to “GSM”, the phone will be locked to GSM indefinitely1; specifying WCDMA UARFCNs or cells to lock on will not by itself force the phone into WCDMA mode. In order to force immediate use of GSM, you must set the RAT lock to “GSM”; the phone will then be locked to a GSM network indefinitely, and any GSM-specific settings you have made will take effect. The same holds for WCDMA.

Note again that the RAT lock function has an effect in idle mode only. If no RAT lock is applied, the phone will camp on whatever network the fixed side prescribes (as it normally does). Whatever technology-specific settings you have made will be in force while the phone is using that technology; however, these settings will not interfere with the choice of RAT made by the fixed side.

9.1.12.2.

RAT Lock vs. Technology-specific Control Functions: Nokia

If you lock a Nokia phone on a RAT, then try to apply a locking function for a different RAT, the phone will go into No service mode. For example, this will be the result if you lock the phone to GSM, then attempt to lock on a WCDMA cell. However, the technology-specific setting is remembered and will come into effect after the RAT lock has been released. In the above example, when you
1. Except if you put the phone in scanning mode, in which case it ceases to behave like a phone at all.

76

Chapter 9. Operating and Controlling External Equipment Manually

release the GSM RAT lock, the phone will immediately switch to WCDMA and lock on the WCDMA cell you selected.

9.1.13.

RRC WCDMA Capability Control

This function lets you modify the phone’s reported HSPA capabilities. The options are the same as in the device properties described in section 21.2.2.14.

9.1.14.

Speech Codec Control

This function lets you redefine the set of speech codecs that should be enabled in the phone and change the default order of priority between these codecs. The user interface is the same as in section 21.2.2.3. The Set Default Speech Codecs option causes the phone to revert to its default speech codec settings.

9.2.

Voice/Video Calls

Under the Voice and Video nodes are found various operations related to CS voice and video telephony. They use the same types of configuration sets as the corresponding Service Control activities, which are covered in sections 20.16.6 and 20.16.7. Which a CS voice or video call is ongoing, its progress is displayed on the Navigator’s Equipment tab immediately beneath the device engaged in the call.

NT12-7002 ver 1.0

77

TEMS Investigation 14.1 User’s Manual

9.3.

Data Services

Under the IP and Messaging nodes are found operations for running PS data service sessions. Again these operations correspond in one-to-one fashion to activities in Service Control scripts. All configuration details are covered in the Service Control chapter, sections 20.16.3–20.16.6. For example, if you want to conduct a manual FTP download, you first need to set up a network connection using IP  Network Connect, and then you can do the actual download by initiating an IP  FTP Download operation. This assumes that you already have configurations defined for each operation. If not, then right-click the operation on the Activities tab, choose Configuration Sets, and create a configuration by clicking New in the dialog that appears. Progress indicators are shown for data service sessions in the same way as for CS voice/video; compare section 9.2. Note: If you run multiple concurrent data service sessions using multiple devices, avoid starting all of these in very rapid succession. It is better to start one session at a time with at least a few seconds in between. Compare the note at the end of section 20.10.4.

9.3.1.

Presentation of Data Service Testing

Testing data services will produce the following output: Information elements in the Data category: see Information Elements and Events, section 3.8. Selections of these elements are by default presented in the data service oriented line charts. See Information Elements and Events, chapter 8. A number of events pertaining to various services, and more: see Information Elements and Events, sections 7.2 and 7.4. These are by default presented in the data service oriented line charts. KPI-related events in the message window Events of KPI Type: see Information Elements and Events, sections 7.4 and 8.8. Messages in the Data Reports message window: see Information Elements and Events, section 8.8.

• •

78

Chapter 9. Operating and Controlling External Equipment Manually

9.4.

Scanning

Under the Scan node you can set up and execute scanning sessions. This can alternatively be done from Service Control scripts, as described in section 20.16.5. General aspects of scanning are covered in chapter 13. For complete details on scanning setups for each supported cellular technology, see chapters 14– 19. The configuration is done in the same way whether the scanning is manual or script-controlled.

NT12-7002 ver 1.0

79

TEMS Investigation 14.1 User’s Manual

10.

The Status Control Monitor

The Status Control Monitor provides at-a-glance information on: • • • • the status of devices connected to the PC, including positioning equipment service execution PC performance logfile recording.

The window is found in the Control category on the Navigator’s Menu tab. Generally speaking, the Status Control Monitor indicates what last happened: it does not provide comprehensive coverage but should be seen as a complement to other parts of the user interface. Each “LED”-style indicator is accompanied by a text string that details the significance of the indicator’s current color.

10.1.

Equipment Connection

This indicator relates to the status of data collecting devices other than positioning equipment. Symbol green yellow red no color Meaning A new device (EQ) has been activated in TEMS Investigation. A device which is activated has stopped delivering data. A device has been deactivated in TEMS Investigation. No devices detected.

Compare the Navigator’s Equipment tab: see section 8.3.

80

Chapter 10. The Status Control Monitor

10.2.

Positioning

This indicator reflects the status of the currently preferred positioning device. (Regarding the definition of “preferred”, see section 8.5.) Symbol green red no color Meaning The preferred positioning device is delivering valid data. The preferred positioning device has stopped delivering valid data. No positioning device detected.

Compare the Navigator’s Equipment tab: see section 8.3.

10.3.

Service Status

This indicator relates to service usage. It covers both service sessions that are initiated manually (from the bottom pane of the Navigator’s Equipment tab: see sections 9.2, 9.3) and service sessions controlled by a script (see chapter 20). However, if you initiate a service directly on the device, using the device keypad, such an action does not affect this indicator. Symbol green yellow red no color Meaning Last service execution OK, everything in order. Service execution failed once or twice. Service execution failed repeatedly (at least three times in a row). No service executing.

NT12-7002 ver 1.0

81

TEMS Investigation 14.1 User’s Manual

10.4.

Computer Performance

This information is taken from Windows. Memory usage for all tasks, not only TEMS Investigation, is indicated. Symbol green yellow red Meaning CPU and memory usage both below 75%. CPU and/or memory usage above 75%, but both below 95%. CPU and/or memory usage above 95%.

10.5.

Logfile Progress

This indicator relates to logfile recording only, not to logfile analysis. Symbol green red Recording active. One of the following: • • no color Size of logfile not increasing due to an error. Device deactivated. Meaning

No recording in progress.

Compare the status bar, Recording section: see section 4.4.3.

10.6.

Context Menu

You can record all text messages printed in the Status Control Monitor to a text file. Right-click in the Status Control Monitor, and a context menu will appear; from that menu you can start and stop the logging of the window contents. By default the message recording is turned off.

82

Chapter 11. Logfiles

11.

Logfiles

This chapter explains: • • • • • • • • how to log information received from external devices to file (section 11.1) how to load a logfile for analysis (section 11.2). loading of logfiles from sources outside TEMS Investigation (section 11.3) viewing of logfile contents (section 11.4) transferring of logfiles via FTP (section 11.5) logfile export (section 11.6) merging of uplink AQM data into logfiles (section 11.7) generation of logfile reports (section 11.8).

The chapter also describes:

11.1.
• •

Recording Logfiles

Logfile recording can be initiated in the following ways: Manually from the Record toolbar or Logfile menu. Such a logfile will always include all activated devices. By starting a walk, either along a planned route or unguided, in the Pinpoint Window: see section 12.3. Here, too, all activated devices are included. By a script that is executing. In this case the logfile can record devices selectively, as specified in the script setup. For full instructions on how to configure scripted recording, turn to sections 20.16.1.7–20.16.1.9.

Several logfiles can be recorded concurrently, and each recording is then completely independent of the others. The activities of one device (EQ) can be recorded in multiple logfiles. Regardless of the method used to record a logfile, the output is always a single file with extension .trp.

NT12-7002 ver 1.0

83

TEMS Investigation 14.1 User’s Manual

The rest of the present section deals with manual recording, which is most conveniently handled from the Record toolbar. To initiate recording of a logfile: Click the Start Recording button on the Record toolbar. This dialog appears:

File name

The default naming is in the form of a timestamp: mmddhhmmss.trp (month, day, hours, minutes, seconds). Here you can enter free text characterizing the logfile. This attribute is also visible in Windows Explorer1 (select the Subject column for viewing). Use this field to categorize the logfile with suitable keywords. A tag is defined simply by being entered here. Valid keyword separators are comma (,) and semicolon (;). The Tags attribute can also be inspected in Windows Explorer1 (select the Tags column for viewing). Free-text field for describing the logfile.

Subject

Tags

Description

1. Note: This feature is temporarily disabled in TEMS Investigation 14.1.

Now activate your equipment if you have not already done so. (By starting the recording first you ensure that you capture all of the relevant measurement data in the logfile.)

84

Chapter 11. Logfiles

Perform the desired tasks with your external equipment. After you have completed all of these tasks, click Stop Recording to end the recording and close the logfile. Once you have closed it, you cannot log any more data to the same file.

Alternatively, you can control the recording with the corresponding commands in the Logfile menu.

11.1.1.

Inserting Filemarks

Filemarks are text strings which can be inserted automatically or manually in a logfile in order to tag interesting segments in the file. They are treated as events and appear as such in presentation windows. Filemarks can be searched for in message windows, as explained in section 26.7.2. In Service Control scripts, you can use the Filemark activity to have filemarks inserted automatically. See section 20.16.1.5. To add a filemark manually: Click the Insert Filemark button and enter the filemark text (up to 50 characters).

A Filemark event is written to the logfile for each filemark.

11.1.2.

Further Recording Options

Some additional options are available when recording logfiles. From the Logfile menu, choose Recording Properties.

NT12-7002 ver 1.0

85

11. meaning that you indicate your exact positions as you walk around measuring. the history buffer in TEMS Investigation is automatically cleared on reaching a size of 410. an internal history buffer (providing quick access to logfile data) is cleared every time you start recording a new logfile. the Pinpoint Window. The pinpointing described here is done in the Map window and is manual. 86 . To prevent out-of-memory issues.1.1 User’s Manual Default recording folder Clear history buffer at start of new logfile Here you can change the default directory where logfiles will be saved. If you check this box. where you can either pinpoint manually or plan and create your route in advance and then walk it in a simplified fashion. This reduces the consumption of disk space as well as the CPU load during recording. Pinpointing is useful in environments where GPS coverage is lacking. The Pinpoint Window is dealt with in chapter 12.TEMS Investigation 14. This function is automatic. TEMS Investigation also has another pinpointing tool. Positioning Logfiles by Pinpointing in the Map Window This section describes how to use the pinpointing technique for positioning logfile data. and you cannot view or edit any settings controlling this behavior.000 messages.3.

1. • Basic Pinpointing Procedures First. To record positions for measurements. the corresponding position is registered in the logfile as a waypoint along your route. click the Pinpoint button.4. On the Map window toolbar. the measurement reports received between the two points are drawn as theme symbols distributed uniformly along the new route segment (and assigned the corresponding positions in the logfile). A GPS can be physically plugged in without disabling the pinpointing function. 2 1 3 4 5 Route Waypoints (pinpoint markers) Measurement data points NT12-7002 ver 1.3. but it cannot be activated in the TEMS Investigation application. See sections 31. You must do this before starting the logfile recording. you need to position it. clicks on the map will be interpreted as pinpointing actions.1. you cannot activate a GPS in TEMS Investigation. If the image file is unpositioned.0 87 .Chapter 11. Each time you pinpoint. Now click the Start Recording button on the main window toolbar. and a new route segment in the form of a straight line is drawn to it from the preceding waypoint. Then. Logfiles Note: If you activate a GPS in TEMS Investigation. you indicate your position by clicking on the map at regular intervals. while pinpointing is in progress. load your floor plan or other image to be used for pinpointing into a Map window.3–31. pinpointing in the Map window is disabled. As long as a phone is activated. The waypoint is marked with a black diamond. Conversely. 11. This is indicated by the cursor changing into an upward arrow whenever it enters the Map window.

2.TEMS Investigation 14.3. is dropped). Consider a script where voice calls are repeated in a while loop and a new logfile is recorded in each turn. When logfile recording is started (by any of the available methods). To 88 . 11. Buffering in Connection with Logfile Recording For each connected device. to obtain equal data densities in different locations.3.000 messages. for example. whichever is less. If the Start Recording and Stop Recording activities are put first and last in the loop.1 it is clear that in order for the recorded route to agree well with the actual one.3.5) and avoid having other presentation windows open at the same time unless you really need them. Advice on Pinpointing and Recording From section 11. When you are done with your measurement session. Please note that this mechanism may cause unexpected and possibly unwanted data to appear at the beginning of a logfile. (Note that this is in fact not the case in the figure in section 11.1 User’s Manual The waypoints themselves are stored in the logfile as “Pinpoint” messages which appear by default in the Events window. 11. It is wise not to replace the map during recording.) If you pinpoint close to the edge of the Map window. To optimize the performance of the Map window. the map will scroll automatically. • Pinpoint one last time to ensure that all data is accurately positioned. Click Stop Recording to end the recording and close the logfile. Therefore the waypoints and connecting lines appear also when the logfile is loaded for analysis later on. then any two consecutive logfiles will overlap.4. you should pinpoint every time you change direction.1. TEMS Investigation continuously maintains an internal buffer with the latest signaling: up to 15 seconds’ worth of it or up to 1.1. and this duplication of data will skew any statistics that are computed based on it. This is potentially useful in order to capture as much as possible of the context surrounding a device activity. you should try to maintain approximately the same speed throughout your route. Now if a call fails (e. the failure will likely be registered in both logfiles.1.1.1. where the tester has increased his speed considerably between waypoints 3 and 4. you should remove all unused themes (see section 31. Furthermore. finish as follows: Deactivate the phone.g. the contents of this buffer are inserted at the start of the logfile. the signaling leading up to the establishment of the call or data session.

The remaining space on the Logfile tab is divided into subtabs whose contents are detailed in the subsections that follow. for instance by clicking the Selection Tool button on the Map window toolbar (see section 31. The name or entire path of the logfile can be copied to the Windows clipboard by right-clicking in the logfile name box and selecting the appropriate command: Copy filename to clipboard or Copy full path to clipboard. TEMS Discovery is used. Opening a Logfile Click the Open Logfile button to open a logfile.2.2. if you have been pinpointing in the Map window. not the full contents of the file (that is.2. the measurement data).Chapter 11. One logfile at a time can be loaded in TEMS Investigation.0 89 .16.9. Furthermore. turn to section 11. insert Wait activities in your script. Loading Logfiles for Analysis Note: To be able to load a logfile.3. Regarding the latter. you can open a logfile by drag-and-drop from Windows Explorer.1. Opening a logfile only loads logfile metadata into the application. Logfiles prevent logfiles from overlapping.9). you must deactivate your external equipment. The file must then be dropped onto the Logfile tab of the Navigator. The metadata is displayed on the Navigator’s Logfile tab. For multi-logfile analysis. 11.1. you must also exit Pinpoint mode there. Logfile loading is controlled from the Replay toolbar or from the Logfile menu. 11. NT12-7002 ver 1. Alternatively. This tab shows the logfile name at the top. The quickest method is to use the toolbar buttons. see section 20.

Recovered: A failure occurred during recording of this logfile.2. see section 11. Date and time when the recording started.0) logfiles. 90 . but it might just as well be.2. Unknown: Value displayed for old (pre-14. This can be a version of TEMS Investigation.2.2. Description Start Time Stop Time Probe Shows the contents of these fields as defined at logfile creation time. TEMS product or component used to record the logfile. Please note that the file may be corrupt. Status Bounding Box The smallest area (defined by min/max latitude and longitude) that encompasses the route traveled in the logfile.1 User’s Manual 11. Tags. Date and time when the recording concluded.1.1. Normal: The logfile was recorded normally. Logfile Metadata and Statistics “General” Subtab Subject.TEMS Investigation 14. for example. a TEMS Automatic RTU or a TEMS Pocket release. 11. and an attempt was made to recover the file.

) just as is done in live mode for active devices on the Navigator’s top-level Equipment tab (Information subtab: see section 8.3.Chapter 11. NT12-7002 ver 1.2. Logfiles 11. etc.2. Selecting a device populates the fields at the bottom (Capabilities.0 91 . No data from that device will then be loaded into the presentation windows when you load the full logfile contents.2. The Revision field contains miscellaneous device information such as firmware revision. You can right-click a device and choose Deactivate to hide data from that device in the logfile presentation. Each device appears with the same EQ number assigned as it had at the time of recording.2).2. “Equipment” Subtab This subtab holds all devices that were activated in TEMS Investigation during recording of the logfile.

You can group and/or filter the contents in various ways: Group by Not Grouped: The chronology is given in a single table. 92 .TEMS Investigation 14.).2.1 User’s Manual 11. Failed. Activity: The chronology is broken into separate tables for each type of activity performed.2. You can show all activities or only those of a particular type. Result: The chronology is broken into separate tables for each possible outcome (Succeeded. Filter by Equipment Filter by Activity You can show all activities or only those of a single EQ. “Activities” Subtab This tab gives a complete chronology of the activities (whether scripted or executed manually) performed by all devices in the course of the logfile recording. etc.3.

Chapter 11.2. Logfiles Clicking an activity link opens a detailed description of the configuration. • Click the Back link to return to the activity listing.0 93 .4. Below are shown a couple of extracts from the description of an FTP Download activity.2. “Statistics” Subtab NT12-7002 ver 1. which shows equipment status and the outcome of the last activity performed during the execution of a script. 11. execution.3.1). Compare the Service Control Monitor (section 20. and outcome of the activity.15.

6.x1.x.x1. The data loaded thus far is then displayed in the presentation windows. click the Close Logfile button to close it. 8. which computes similar statistics in testing mode while a script is executing. Filter by Equipment You can show statistics for all devices taken together or for one selected device.2).x 2 94 .1. 11. Play Section of Status Bar While a logfile is being loaded.15.x TEMS Investigation EDGE 1. 11.3.3.1 User’s Manual This tab provides statistics on the outcomes of activities performed by the devices during recording. 5.x. You can click the same button again.x (GSM logfiles) TEMS Pocket 12. See section 4. Click Fast forward once more to resume logfile loading.TEMS Investigation 14. to halt the loading of the logfile. • • • • • • TEMS Investigation 6.x1. Compare the Service Control Monitor (section 20. the Play section of the status bar shows the name of the file and indicates the percentage of the file that has been loaded. Loading Logfiles from Other Sources TEMS Investigation can load and analyze logfiles from the TEMS products listed below. 3.4.x. 7. When you are done analyzing a logfile. 10. 11. 4.x1. 2.x.3.2.x and later TEMS Investigation GSM 5.2. 11. Loading Logfile Contents Click the Fast forward button to load the logfile measurement data into the presentation windows.x.x TEMS DriveTester GSM–TDMA 1.x TEMS Investigation WCDMA 3. now labeled Stop.3.

x (any MTU and TEMS Pocket Remote logfiles) TEMS Automatic 5.x (any MTU logfiles) TEMS Automatic 4. choose Configuration  File Transfer.1. Logfiles • • • • TEMS Automatic 9.5.x logfiles cannot be loaded in TEMS Investigation. NT12-7002 ver 1. see the Informations Elements and Events volume. 7.4. 2.0 95 .0.x. In the window that appears.5 TEMS Investigation can also read • • • • EFEM logfiles from Motorola phones MDM logfiles from Qualcomm chipset based devices logfiles from Anritsu ML8720 scanners (i.2.7.x. click the Settings button.10) 11. 6.e. 2.Chapter 11. described in section 26. files logged by the scanner itself) MTR files (GSM. 11. section 3. • • Setting Up Logfile Transfers To set up FTP logfile transfers. Note especially the search functions in message windows. on the Menu tab of the Navigator. Viewing Logfile Contents Everything about data presentation is dealt with in chapters 23–31. TEMS Pocket 9. 8.5. Logfile Transfer via FTP TEMS Investigation has a function for uploading logfiles via FTP according to preconfigured FTP server settings.x (MTU logfiles recorded with GSM-only MTUs) TEMS Automatic 3. Please note that logfiles from these TEMS Pocket versions must first be converted using a PC utility that is delivered with that version. 1. 11.x.

Path to the directory on the FTP server where the uploaded logfiles will be stored (in a subdirectory named according to the current date). The logfile names are augmented with a timestamp indicating the time of upload: _tfu__hh_mm_ss (“tfu” means “TEMS file upload”). Password Server Address Port Server Logfile Directory Local Logfile Directory 96 . User.1 User’s Manual 11. FTP Server Settings User name and password on the FTP server. if required. The FTP server port to use. The local directory on the PC from which logfiles will be uploaded.TEMS Investigation 14.1. IP address or host name of FTP server.1.5.

If the option is not checked.1. or over an Ethernet or WLAN connection. this behavior is preselected and cannot be changed.2.. 11. you need to supply parameters for connecting to the network. The parameters of this configuration are gone through in section 20. Note: Transfer over Ethernet or WLAN requires that detection of network adapters be enabled (it is disabled by default). NT12-7002 ver 1. Logfiles 11.5. • • Delete: After logfiles have been uploaded.3. For a cellular network device.3. If Start transfer when logfile is closed is checked.1. Equipment Here you select the device to use for logfile transfer.] files after transfer Generate MD5 checksum If checked.16.3. Using some suitable third-party software. Note that you do not need to have the device activated in TEMS Investigation to be able to transfer files. logfiles that have been uploaded are moved to a subdirectory Complete that is created automatically for the purpose.0 97 . you can then compute the checksum for the uploaded file and confirm that it agrees with that of the original. TEMS Investigation will generate an MD5 checksum (128-bit hash value) for each logfile to be transferred and send that value as a text file along with the logfile.. Click the Connection parameters button to open the dialog for creating a Network Connect configuration set. Logfile Options If this is checked. Start transfer when logfile is closed [.5.6. Move: Within the local directory.Chapter 11. you initiate transfers manually as described in section 11. they are deleted from the local directory.1. The transfer can be done over a cellular network. every logfile will be transferred immediately after the recording has ended. See section 8.5.2.3.

2. can be exported in this format. chapter 9 for details. 11.2 Marconi Planet DMS 3. 11. TEMS Automatic logfiles. In the File Transfer window.5.5. In this case you start the logfile transfer manually on each occasion. too. • • In the File Transfer Settings dialog.TEMS Investigation 14. select it in the list box and click Load. Starting Logfile Transfers This section is applicable only when the option Start transfer when logfile is closed described in section 11. • Exporting Logfiles in Other Formats Logfiles can be exported in the following formats: Text file with tab delimited data (suitable for processing in. (If the file transfer is automatic. for example. To load a previously saved setup. then click OK.6. select it in the list box and click Delete.5.1.1. MapInfo 3. The setup is added in the list box. define or select the setup you want to use.0 (Interchange or Tab format) ArcView Shapefile: about version. chapter 8. • • • To save a setup.2 is not set. click the Start button.) The progress bar will indicate the progress of the transfer. type a name for it in the Name box and click Save. there is no explicit handling of setup files. Setup You can save all settings made in this dialog as a file transfer setup.1 Ethereal (Wireshark) MDM • • • • • Some of these formats contain multiple files for each logfile. The text export format is described in detail in the Technical Reference. 98 . see the Technical Reference. To delete a setup. The setups are maintained in the dialog. a spreadsheet application).1 User’s Manual 11.4. section 9. this button is named Auto and grayed out. See the Technical Reference.

see section 11. If there is no positioning information in the logfile. The Add Export Order dialog appears: Format Select the output format for your logfiles. the export file will contain only a header and no route data.0 99 . Logfiles Note: Export in MapInfo.1. (This is not a logfile export format in the strict sense. Logfile export can be done either from the TEMS Investigation user interface or from a Command Prompt. A separate window named TEMS Export is launched. From the Logfile menu. NT12-7002 ver 1. In the TEMS Export window. For the latter possibility.6. • • Preparing an Export Order First.7. see section 11.Chapter 11. ArcView.) Input files Type or select the logfile or logfiles you want to export. or Planet format requires that the data be positioned.4. choose Export Logfile. Regarding the choice PESQ merge.6. deactivate any external devices that are currently activated. 11. click Add. This is necessary in order for the export to work properly.

2. all logfiles will be merged into a single set of export files. and the export file set simply retains the name of the logfile. To the export file name you can optionally add a descriptive prefix. Editable only for certain formats. chapter 9. (Logfiles are simply concatenated.6. To the export file name you can optionally add a descriptive suffix. a dialog appears whose contents partly depend on the format chosen. Selecting Information Elements to Export The Information Elements tab is common to many of the formats.). Specifying the Contents of Export Files On clicking the Setup button.1 User’s Manual Cell files Click this button to include one or several cell files in the export. • Now click the Setup button to specify details of the export. 11. This will have exactly the same effect on information elements and events as having cell files loaded in the TEMS Investigation application itself (populating IEs that require cell file data. Here you select which information elements to include in the export: 100 .TEMS Investigation 14.6. each logfile is exported separately. File extension for export file. as described in the Technical Reference. etc.2.1.) The name given to the export files depends on the ordering of logfiles in the Input files box. including the plain-text format. there is no sorting of messages by timestamps.6.2 below. Export to other formats produces files with fixed extensions. Merge output Directory Prefix Suffix Extension The directory where the export files are written. see section 11. 11. If you are exporting several logfiles and this option is checked. If the Merge output option is unchecked.

By default a chosen item is exported from all devices that report it. To export the item only from specified phones. select the item and click “<”. but only the component with the lowest argument. By default the items selected are picked from all phones. choose that category in the combo box in the Available IEs section. select the desired item and click the Edit button above the box. click “>” again. To export an information element from a different category (e.g. or change the IE argument (where one exists). For all export formats except tab-delimited text.Chapter 11. To clear the entire Selected IEs box. For all export formats. you must edit the item. click “<<”. you do not get the whole element at once. • To export an element. you can also edit the following settings: NT12-7002 ver 1. select it in the Available IEs list and click the “>” button to move it to the Selected IEs list. the Data category).0 101 . you can restrict the export of a selected IE to a single device. The Edit IE dialog appears. Logfiles You choose each individual element separately. • • • Editing the Selected Items To edit an information element: • In the Selected IEs box. see Editing the Selected Items below. If the element has arguments. To select the component with the next higher argument. From information elements with arguments you pick one component at a time. Repeat for all components you want to export. To remove an item from the Selected IEs box. Elements from different categories can be freely mixed in export files.

Text File Specific Settings Besides your chosen information elements.6. (You might want to make this string shorter. it will be written in the export file whenever the IE does not have a valid value. By default.2. Arranging Items in the Export Files The order of the items in the Selected IEs list will also be the order in which they come in the export files. “999”. “-1”). The choice is made on the Options tab: 102 . whereas for the remaining formats the string must be numeric (e. the export can be reduced in order to decrease the duplication of data and the number of lines in the export file. but in different files.2.g. There are no user settings relating to the event data. Note also that the NAME and NODATA settings are not saved along with other logfile export settings. For Planet. You can rearrange the items by selecting them and moving them using the Up and Dn buttons.6. By default the text export file also contains message information. the column heading string consists of the IE name.) NODATA field: If you enter a string here.2. any string is accepted. 11.1 User’s Manual • NAME field: This is the IE column heading in the export file. the IE name is preceded by an asterisk (*) in the Selected IEs box. • As long as these settings have not been edited. See section 11. including user-inserted filemarks.TEMS Investigation 14. Optionally. the text export file always contains data on events.8.

. all IE values are written for every message. If the box is not checked. and Hexadecimal String are excluded from the export file. Message ID. Message ID. If you check Show changed IE values only. Logfiles Full message information. (The Event column is kept.Chapter 11. NT12-7002 ver 1. Check a column to include it.0 103 . The export file is reduced in two ways: • The columns Frame Number.) Messages not triggering an event and containing no changed IE values are wholly excluded. Events and filemarks only. • Event information Governs whether the Event Info column is included in the export.. The following columns are optional: Message Type. as is the Event Info column provided that the Event information checkbox below is checked. All messages are kept. IE values are written out only if they have changed since the previous message. This makes for a considerable reduction of the export file size.. see the Technical Reference. In addition there will be one column for each selected IE or IE component. chapter 8.. and Hexadecimal String. All other standard columns are always included.

the Options tab looks like this: Reports to export data from This setting governs what types of report from the phone are included in the export files: • • • all reports only Layer 3 reports only mode reports.2.TEMS Investigation 14.6. Layer 3 messages.txt. and phones’ mode reports exported as unabridged plain text to a common separate file whose name ends in _textexp.1 User’s Manual Message options Check the relevant boxes in order to have Layer 2 messages. By default all reports are exported. 11.3. MapInfo Specific Settings For MapInfo export (whether to Interchange or Tab format). 104 .

0 105 ..... Events This setting governs the export of events.2.1..Chapter 11.: Events are exported. uplink.. see the Technical Reference.. see the Technical Reference. but no event-specific symbol is used in MapInfo when plotting on a map. Export events but do not plot. downlink) Message name Hexadecimal string Extension (containing cause values) Do not export events: No event information is exported. Check this to include information on Layer 3 and Layer 2 messages in the export files.. The following data is added (one column for each item): • • • • Message direction (internal. Check this to include information on Layer 3 and Layer 2 messages in the export files. section 9. 11. Note. section 9. ArcView Specific Settings Export message information. however. that there is no differentiation of event types. The following data is added (one column for each item): • • • Message direction (internal.6. • • • Include file name in file Check this to include the file name in the export files. Logfiles Export message information. For details on MapInfo output. Export events and plot. and a unique symbol is used when plotting in MapInfo to distinguish events from other data.4.2.: Events are exported. NT12-7002 ver 1. uplink. downlink) Message name Hexadecimal string For details on ArcView output. and that the symbol used is not one of the default TEMS Investigation event symbols.

2. Check this to include information on Layer 3 and Layer 2 messages in the export file. The file extension will depend on the format (for example. Ethereal (Wireshark) Specific Settings The export encompasses all of the logfile content. otherwise the output files will be empty. click Load and locate the setup file.6.4.2.TEMS Investigation 14. 11.6. The export encompasses all Qualcomm-specific air interface messages in the logfile. • 106 . you may want to save the setup for future use.1 User’s Manual 11. For details on Ethereal output. • In the Setup dialog. otherwise the output file will be empty. .7.2.tex for a text-format export setup).5. uplink. MDM Specific Settings MDM export is intended for logfiles recorded with Qualcomm chipset based devices.5. The following data is added (one column for each item): • • Message direction (internal. click Save and store the file where appropriate. section 9. section 9.6. Marconi Planet Specific Settings Export message information.3.2. 11. The Export message information checkbox must be checked. downlink) Message name For details on Marconi Planet output. see the Technical Reference. see the Technical Reference. To load a previously saved setup in the Setup dialog... The Export message information checkbox must be checked. Saving and Loading Export Setups When you are done specifying the export. section 9. 11.8.6.6. see the Technical Reference. For details on MDM output.

exe.6. 11. Use semicolons (.0 107 . Logfiles However. Mandatory Command Line Switches /IF (or: /InputFiles) Equivalent to Input files field in logfile export dialog. where optional parts are placed within square brackets [ ]: TEMS. /IF and /InputFiles can be used interchangeably.Chapter 11. They are instead written to DBF files that are found in the Settings directory beneath the TEMS Investigation installation directory. A summary of the export execution appears in a popup window (“Export Result”).ExportTool.exe /IF "<logfile name(s)>" [/OD "<output directory path>"] [/CFG "<configuration file name>"] [/CF "<cell file name(s)>"] [/EF "<export format>"] [/P "<prefix>"] [/S "<suffix>"] [/E "<extension>"] [/MO] [/V] Each of the command line switches has an abbreviated as well as a full form. • • To start executing the export orders.) to separate files.6. the NAME and NODATA settings for information elements (see the introduction of section 11. 11. right-click and choose Start from the context menu (or click the Start button in the window). Executing Export Orders All the export orders you have defined are listed in the Export Logfile window.2) are not saved in the above-mentioned files. 11.4. right-click and choose Abort from the context menu. which is found under <TEMS Investigation install dir>\Application.ExportTool. for example.6.3. To abort the execution of the export orders. Wildcards can be used in the file name in regular DOS fashion.4.6. Command Line Controlled Logfile Export Logfile export can alternatively be initiated from a Command Prompt by running the file TEMS.1. NT12-7002 ver 1. The command has the following syntax.

" Exports all TEMS Investigation logfiles found in the specified directory.trp" Exports the logfiles listed.6.mex" /EF "MapInfo Tab-file" /CFG "C:\Path\filename. If you do not specify an output directory.2.2.mex" /EF "ArcView shape-file" /CFG "C:\Path\filename.avx" /EF "Marconi Planet-file" /CFG "C:\Path\filename.4. a configuration file is required to have any information element values exported.trp" Exports all TEMS Investigation logfiles found in directories ExpTest1 and ExpTest2 as well as those in directory ExpTest3 matching the given file name pattern. • /IF "C:\ExpTest\*. This parameter is optional but strongly recommended for all export formats that have a configuration. 11.6. the location where the export files are written is indicated in a file batch_result.1. /CFG (or: /ConfigurationFile) Logfile export configuration file. 108 . Optional Command Line Switches /OD (or: /OutputDirectory) Full path of output directory.C:\ExpTest2\*. • /IF "C:\ExpTest1\*. created by saving a setup in the logfile export dialog as described in section 11.1 User’s Manual Examples: • /IF "C:\ExpTest\0825_01.C:\ExpTest3\0825_*1.tex" /EF "MapInfo Interchange (mif)" /CFG "C:\Path\filename. Here is how configuration file types match up with export formats (/EF): • • • • • /EF "Text file" /CFG "C:\Path\filename.6.2.trp.pex" No configuration file exists for export to MDM or Ethereal. Most importantly.txt which is found in the Temp directory of your Windows user (for example.8.C:\ExpTest\0825_02. Equivalent to Directory field in logfile export dialog. under Windows 7: C:\Users\<user name>\AppData\Local\Temp).TEMS Investigation 14. nor for PESQ uplink data merge. compare section 11.

Logfiles /CF (or: /CellFiles) Equivalent to selecting cell files by clicking the Cell files button in the logfile export dialog. /S (or: /Suffix) Equivalent to Suffix field in logfile export dialog. If you specify several cell files. /MO (or: /MergeOutput) Including this switch is equivalent to checking the Merge output checkbox in the logfile export dialog. If this parameter is omitted.0 109 . the export is done in text format. The possible values are those seen in the Format combo box: "Text file" "MapInfo Interchange (mif)" "MapInfo Tab-file" "ArcView shape-file" "Marconi Planet-file" "Export to Ethereal" "Export to MDM" "Pesq Merge" /P (or: /Prefix) Equivalent to Prefix field in logfile export dialog. NT12-7002 ver 1. use semicolon (.Chapter 11. /E (or: /Extension) Equivalent to Extension field in logfile export dialog. The format string needs to be enclosed within double quotes (" "). the name of each exported logfile will be printed in the Command Prompt window. /EF (or: /ExportFormat) Equivalent to Format setting in logfile export dialog. /V (or: /Verbose) If you include this switch. Note again that for some export formats you cannot override the default extension.) as delimiter.

Note: When downloading the uplink data files it is important to preserve the Call Generator directory structure.2. Retrieving Uplink AQM Data The uplink AQM data is stored as XML files on the Call Generator PC.trp format) that includes both uplink and downlink AQM data.TEMS Investigation 14. This uplink data needs to be inserted in each logfile (*.trp) recorded with TEMS Investigation.exe /IF "C:\ExpTest\0825*" /OD C:\ExpTest\Export /V /CFG "C:\ExpTest\GsmN. Merging Uplink AQM Data into Logfiles (UMTS) As described in chapter 35.3.tex" This command exports in text format all logfiles found in C:\ExpTest that were recorded on August 25 (we are assuming here that the default logfile naming has been retained). The output is stored under C:\ExpTest\Export. for example: • • • by setting up access to the Call Generator output directory as a network drive by downloading the uplink data files via FTP by copying the files onto a USB stick or a CD/DVD. No special tool is currently provided in TEMS Investigation for accessing the uplink AQM data.7. since the merge algorithm relies on this structure to locate the correct files. To perform the data merge.1 User’s Manual 11.7. The XML files are given random four-digit numbers as names. by default under C:\TIPESQ in a subfolder named <yyyymmdd><phone number>.4. Example Below is an example of a logfile export command: TEMS. the files must be collected manually from the Call Generator.tex.7.1. you need to export the TEMS Investigation logfile with Format set to PESQ merge. This could be done in a number of ways.6. See the screenshot in section 11. 110 . uplink AQM data is computed by a Call Generator and output in XML files. 11. using the setup described in the configuration file GsmN. The output is a new logfile (still in *.ExportTool. 11.

. Execute the AQM export order from the Export Logfile window as described in section 11. Click OK to exit the Add Export Order dialog. Click Add. The Add Export Order dialog appears.6. Be sure not to check the Merge output option.5 s backwards in time so that each score aligns with the speech sentence for which it was computed. Back in the Add Export Order dialog. A dialog appears in which you point out where the uplink AQM data files are located (one XML file for each AQM call). You are now ready to perform the merge. select PESQ merge.0 111 . To this end. You also need to specify where the merged output files should be written.1.” button and locate the root directory holding all XML files (the level above the directories named by date). To compensate for the delay in computing the AQM data. Logfiles 11. all entries being sorted by their timestamps. the logfile export function also moves the downlink data 5. Click the “.75 s NT12-7002 ver 1.2. Click the Setup button next to the Format combo box.3. then OK once more. (Exception: The first score in each pair of Frequent AQM scores needs to be moved a further 2. select the TEMS Investigation logfiles (*. choose Export Logfile.7.trp) containing the downlink AQM data. What happens during the merge is that the uplink AQM data is integrated into the logfile.1. under Input files. • Preparing and Performing a Merge From the Logfile menu. The name of each output logfile will consist of the original name plus the suffix “-AQM”.6. Compare section 11. • • • The output files will remain TEMS Investigation logfiles with extension . See section 11.trp. An example is shown below: UL AQM root directory • • • Click OK. • • Under Format.7.Chapter 11.. click the Browse dir button next to the Directory box and navigate to the desired directory.

25 s in total. From one or several logfiles you can generate a report in HTML format which summarizes the data in the logfiles. This dialog appears: 112 . see the Technical Reference. close it. For in-depth coverage of the computation of AQM data.) The uplink data is simply inserted into the logfiles at the correct points in time.1 User’s Manual backwards.8. If any external devices are activated. No duplication of data in the output logfile will result from this: the logfile export function processes each AQM call only once. chapter 10. deactivate them. see the document “AQM in TEMS Products (Including PESQ and POLQA)” which is found on the installation CD in the subdirectory Documents. For full details of logfile report contents and format. If one of these files is currently open.TEMS Investigation 14. including timing issues. Generating Logfile Reports Note: Reporting functions are also available in TEMS Discovery. click the Generate Report button on the Report toolbar. This is necessary in order for the report generation to work properly. or 8. It is possible to perform a merge with an incomplete set of uplink data files. To prepare a logfile report. and to repeat the merge procedure later on with further uplink data supplemented. 11. • • The logfiles to be included in the report cannot be open while the report is generated.

.0 113 . Click Add and browse for the files.1. Specify an output directory for the report. Those that you choose are listed in the Files box. IE Tab NT12-7002 ver 1. or click the button labeled “.Chapter 11. choose the logfile or logfiles on which to base the report. Now click Properties to assemble the contents of the report.” to browse your file system. Logfiles • • • First.8. 11. A multi-tab dialog appears.. Enter a path.

you can also define your own thresholds. All thresholded information elements listed will also have their distributions visualized in bar charts. click the Add button. A number of thresholds are predefined in the dialog.TEMS Investigation 14. Adding User-defined Thresholds • To add a pair of thresholds. 114 . In the report.1 User’s Manual The report can compare information element values with thresholds. It will contain statistics of the type “Percentage of measurement points with Active Set CPICH Ec/No below –15 dB”. • • • Choose an information element. Specify the two thresholds. Each item in the list represents a set of two thresholds for an information element value: or Whether peaks or dips are counted depends on the information element and cannot be changed. Check those that you wish to use. and uncheck the others. Choose an argument (where applicable). Check a cellular technology to use all thresholds defined for that technology. it is indicated for each threshold • • how many times the value of the information element has crossed the threshold (changed from a more normal value to a more extreme one) how long these peaks/dips have lasted on average. as is seen in the above screenshot.

By default no ranges are set. Logfiles • • Click Add to add this threshold pair to the list and keep the Add Threshold dialog open. Customizing Value Ranges The Ranges column is used to customize the drawing of distribution charts (see the Technical Reference.2. 11. and the distribution charts are drawn in a preconfigured manner.4). Editing Thresholds • To edit a threshold. select it and click the Delete button.Chapter 11. Click the Edit Range button. Deleting Thresholds • To delete a threshold pair. double-click it and enter the desired new value.8. If you set up your own value ranges for an IE. NT12-7002 ver 1.0 115 . On this tab you choose what event types to include in these statistics. Click OK to add this threshold pair to the list and close the Add Threshold dialog. Modify the value ranges in the dialog that appears. double-click it and enter the desired new value. the distribution chart will be drawn with one bar for each range: • • • Select the desired information element. Events Tab The report has a section with event statistics. section 10. Editing Arguments • To edit the argument of the information element (where one exists).

By default all device channels (“MS1”. In this step you choose what scan data to present in the report.8. Therefore. if available. Note: The ranking of cells in the report (“Worst Cell Indication”) is partially based on the number of events occurring in the cell. This dialog appears: 116 . not only those signifying failures. “DC1”. This is also the default setting. • Mobiles Tab Check the external devices whose data you want to include in the report. Scanned Channels Tab Note: The settings on this tab are applicable only if your logfiles contain scan data.8. etc. GPS data.TEMS Investigation 14. Press Ctrl + A to select all events. 11.3. “MS2”. and leave the rest unchecked. The algorithm counts all events. • First.) used to record the logfile will be checked. is included implicitly. 11.4. in order for the cell ranking to make sense. only failure events should be checked in this step. click the Define channels button in order to populate the “Available” box. press Ctrl + A again to deselect all events.1 User’s Manual • Check the events you want to include.

0 117 . The cell selection applies to all EARFCNs within the chosen range. For WCDMA. It might look like this: The “Available” list box now lists the selected channels in the following format: • • GSM: m[p] means ARFCN m on the p MHz band. The PN selection applies to all RF channels within the chosen range. then check the desired Cell Identities in the list box. The CPI selection applies to all UARFCNs within the chosen range. specify a UARFCN range under “Lower limit” and “Upper limit”. specify an EARFCN range under “Lower limit” and “Upper limit”. NT12-7002 ver 1. WCDMA: m[f] means scrambling code m on UARFCN f. For LTE. For CDMA. just check the desired ARFCNs in the list box. – – – • Click OK to return to the Report Properties dialog. then check the desired PNs in the list box. select the band of interest. specify a UARFCN range under “Lower limit” and “Upper limit”. Logfiles • In the combo box at the top.Chapter 11. The scrambling code selection applies to all UARFCNs within the chosen range. then check the desired CPIs in the list box. For TD-SCDMA. then check the desired scrambling codes in the list box. – – For GSM. specify an RF channel range under “Lower limit” and “Upper limit”.

CDMA: m[f] means PN m on RF channel f. The report will be stored under [My] Documents\TEMS Product Files\TEMS Investigation 14. • • In the Report Properties dialog.1 User’s Manual • • • • LTE: m[f] means Cell Identity m on EARFCN f.8.8.1\GeneratedReports. • Generating the Report In the Report wizard. The file extension is . TD-SCDMA: m[f] means CPI m on UARFCN f. click Finish. click Save and store the file where appropriate. Report Contents The logfile report has the following main sections (see the Technical Reference. median. 11. The averaging takes place in the mW domain. Saving and Loading Report Setups When you are done specifying the report contents. 11.6. 11. User Details Tab Here you can type a user name and a report number which will be printed in the report header.5. 11. To load a previously saved setup into the Report Properties dialog.8.8. chapter 10 for a complete description): • • Header: Date. click Load and locate the setup file. Time. Prepared by Logfile information: Logfile names and used equipment 118 . max) and a bar chart. min.rpt. For each selected item. Move the items that you wish to present from the Available box to the Selected box.TEMS Investigation 14.8. you may want to save the setup for future use. the report will contain signal strength statistics (mean.7.

Chapter 11.0 119 . Logfiles • • • • • • Worst cell indication: Ranking of cells based on thresholds crossed and events triggered Thresholds: Detailed statistics on how often and in what cells each threshold has been crossed Events: Statistics on events Scan data: Statistics on the signal strength of scanned channels (if any) Distribution charts for thresholded parameters Distribution charts for scan data (if any) The output involving cell data naturally requires a cell file in order to be generated. NT12-7002 ver 1.

1.3). the iBwave format is always used. When you save a map set that you have modified in the Pinpoint Window (by defining planned routes in it). 120 .1. but please note that image files larger than 75 MB (pixel width × pixel height × 4 > 7. 12.1 User’s Manual 12.TEMS Investigation 14. Logfiles that you record in the Pinpoint Window are created in regular TEMS Investigation format (*.1.2.2. while others may include a map set in addition to their regular contents. similar to those in TEMS Pocket 11.trp).1.5 × 107) will be displayed at reduced resolution in the Pinpoint Window. Introduction The Pinpoint Window is designed to further facilitate pinpointing of indoor routes by enabling the construction and use of pre-planned routes. 12. Please note that the Pinpoint Window is not a subtype of the Map window (see chapter 31) but distinct from it.1. Supported File Formats Holding Map Sets Some of these file types are pure map set formats.x and later. The operations in the Pinpoint Window are also wholly distinct from the pinpointing performed in a Map window. Alternatively. 12.2. Map images of arbitrary size can be loaded. The Pinpoint Window supports loading of map sets in the iBwave container format (as does TEMS Pocket) and in a number of other formats. which is always manual (see section 11. The Pinpoint Window 12. you can also pinpoint manually in this window. • Creating Planned Routes Opening a Map Set Click the Open button and browse to select a map set file. Such logfiles incorporate the map set used.

Chapter 12. The Pinpoint Window

• • • • • •

TEMS Investigation logfile (*.trp, version 14.0 and later) created during a previous route walk in the Pinpoint Window iBwave collection (*.ibwc): used as map set format in TEMS Pocket 11.3 and later TEMS Pocket 11.0–11.2 map set file (*.pms) TEMS Pocket 11.x logfile (*.tpz, *.zip) TEMS Pocket 7.3 logfile (*.zip) MapInfo TAB file (*.tab)

Please note that image files in map sets must be positioned; specifically, a TAB file with WGS84 coordinates must be present.

12.2.1.2.

Map Set Metadata Shown in Pop-out Pane

After you have loaded a map set, the pop-out pane on the right is populated with the following metadata: • Building: Expand this item to show a list of the buildings contained in the map set. For each building is indicated: – Lat, Long: Coordinates of the top left corner of the layout plans for each building.

Layout Plan: Expand this item to show the layout plans defined for the selected building. For each layout plan are indicated: – – – The layout plan name The number of routes currently defined for this layout plan The dimensions (in pixels) of the layout plan image.

When you click a layout plan, it is displayed in the map view.

NT12-7002 ver 1.0

121

TEMS Investigation 14.1 User’s Manual

Route: This item holds the routes defined for the plan currently selected under Layout Plan. – – – – – – For each route is stated the number of waypoints it contains. When you click a route, it is plotted on the map. Click the button next to a route to modify the route. See section 12.2.4. Click the button next to a route to delete it from the map set. Click the Add Route button to create a new route. See section 12.2.3. The No Route item is used for manual, “freehand” pinpointing without a planned route. See section 12.4.

12.2.2.
• •

Map Handling and Controls

You can pan the map by dragging. The slider on the left is a zoom control. The current zoom level is indicated by the figure below the slider. You can also zoom in and out using the mouse scroll wheel. Click the “home” button to set the zoom to native map size (zoom level = 1.0) and place the map image in the top left corner of the Pinpoint Window.

122

Chapter 12. The Pinpoint Window

12.2.3.

Creating a New Route

Click the Add Route button.

A new route appears in the route list, provisionally named “Unnamed Route <n>”. At the outset, of course, it contains no waypoints. Click this button next to the route to start creating it. The contents of the pop-out pane are replaced.

In the Route Name field, enter a name for the new route.

The route is created as a chain of waypoints. The Add Waypoints button is toggled “ON” in this situation to indicate that you are currently in “edit route” mode. • • Pan and zoom the map if necessary to locate the spot where you want to place your first pinpoint. To add a waypoint, just click in the desired location. The waypoint is marked by a pin symbol and labeled with a sequence number, starting at “1”.

NT12-7002 ver 1.0

123

TEMS Investigation 14.1 User’s Manual

Keep adding waypoints to trace your planned route. Each time you place a new waypoint, it is joined to the previous one by a connecting straight line.

It is appropriate to place waypoints no further than 10–20 s apart in terms of walking time. Also add a waypoint wherever the walking direction changes. Most importantly, of course, the waypoints should be located in such a way that the entire route (as defined by the connecting line segments) is “walkable”. In other words, the planned route should not pass through walls or other impassable obstacles, since measurements will then subsequently be positioned incorrectly along those segments. • • When you are done creating your planned route, click the Done button. Click Save to save the new route as well as any other changes you have made to the map set. The target format is always *.ibwc (iBwave collection).

How to modify your route in the course of creating it is the topic of the next section.

12.2.4.

Editing a Route

If the route you want to edit is not already loaded in the window, click the “pencil” button next to it in the pop-out pane. The route is then loaded. • To move a waypoint to a new location, just click and drag the pin where you want it. When a pin is selected, it is highlighted by a shaded bounding box, and its head turns blue.

124

Chapter 12. The Pinpoint Window

(If Add Waypoints is “ON”, you must take care not to release the mouse button without dragging, since such an action will add a new waypoint instead. It is most convenient to turn Add Waypoints “OFF” before rearranging waypoints.) • To add waypoints at the end of the route, toggle the Add Waypoints button “ON”. Then click on the map where you wish to place the new waypoints. The first new waypoint is automatically connected to the last waypoint of the existing route. When you have finished, click the Done button to exit “edit route” mode.

To insert a new waypoint somewhere along the existing route, you can choose between two methods: – One method is to right-click the waypoint nearest to the spot of interest, then select Insert Before or Insert After from the context menu that appears. The other method is to select the relevant waypoint and then click one of the buttons Insert Before or Insert After in the pop-out pane.

A new waypoint is now added halfway between the selected one and the one preceding or following it. Adjust the position of the new waypoint by dragging it.

To delete a waypoint, you can again proceed in two ways: – – Right-click the waypoint and choose Delete from the context menu, or: Make sure Add Waypoints is toggled “OFF”, then select the waypoint of interest and click the Delete Selected button.

NT12-7002 ver 1.0

125

TEMS Investigation 14.1 User’s Manual

The delete operation removes the pin symbol from the map view, and the waypoints adjacent to the one deleted are joined by a new connecting line.

• •

To delete all waypoints, click the Delete All button. You can edit the route name in the Route Name field.

Please note that it is currently not possible to edit a route while walking it, that is, during recording (see section 12.3.1).

12.2.5.

Deleting a Route

To delete a route from the map set, click the “trash can” button next to the route in the pop-out pane.

12.2.6.

Unloading a Map Set

There is no explicit function for unloading a map set. When you load a new map set, the previous one is unloaded automatically.

12.3.

Walking Planned Routes

This section tells how to walk a pre-planned route. A recorded walk along a planned route is referred to as a track in TEMS Investigation parlance. It should be pointed out straight away that a track can be less complex, or more complex, than the route it follows. This is because you can skip waypoints or, conversely, visit some waypoints more than once. The logfile of the track records all of your movements as reflected by your commit actions.

12.3.1.

Loading and Walking a Route

Load the desired map set by clicking the Open button.

126

Chapter 12. The Pinpoint Window

Next, select the planned route of interest among those defined in the map set.

The planned route is drawn in red between waypoints whose pins are likewise colored red. The map is centered around the first waypoint, which is enclosed within a shaded bounding box.

• •

Go to the physical location marked by the first waypoint. Click the Start button to start recording your track. You are asked where to save the resulting logfile. This file is created in the regular TEMS Investigation logfile format (*.trp), which also accommodates the auxiliary pinpoint data.

The following controls appear in the pop-out pane: Control Function Forward button: Advance to the next waypoint without committing to the current one.

Back button: Retreat to the previous waypoint without committing to the current one.

NT12-7002 ver 1.0

127

TEMS Investigation 14.1 User’s Manual

Control

Function Commit button: Commit to the current waypoint (whose sequence number labels the button) and move on to the next waypoint. When you perform the commit action, all measurements collected since your last commit are positioned in a straight line between this waypoint and the one you last committed to. The first time you commit, all measurements collected so far are positioned at that waypoint. You should therefore always commit to the first waypoint immediately on starting logfile recording. If you skip one or several waypoints, they are left out of account when data is positioned; see also section 12.3.3. Clicking the Commit button triggers the Pinpoint Added event. Stop button: Stop the test walk and close the track. If you click Start again with the same route still loaded, you will begin a new track which is saved as a distinct logfile (unless you choose to overwrite the previous one).

As soon as you have started recording, click the Commit button to indicate that you are currently in the highlighted location (“#1”). The pinhead turns green and the pin is redrawn “pressed down” (shorter) to indicate that you have visited this spot. The highlighting switches to the next waypoint, and the map is re-centered around it.

Walk in a straight line and at a steady pace towards the waypoint now highlighted. When you have reached that waypoint, click the Commit button again (now labeled “#2”). • Continue in this fashion until you have completed the route. Below the Commit button in the pop-out pane is a stack of boxed items representing

128

Chapter 12. The Pinpoint Window

your latest commits. For each commit action is shown at what waypoint it occurred, and when (“hh:mm:ss”).

12.3.2.

Repeating Parts of a Route

It is possible to backtrack along the route using the Back button, and commit to the same waypoint multiple times. Doing so simply adds more data to the logfile, and the positioning of measurements is always based on your movements between waypoints (regardless of how you retrace your steps). No previously recorded data is ever deleted from the logfile, and committing once again to a waypoint does not in any way override the previous commit action. If for some reason you need to take a break during a test walk, it is best to proceed as follows: • • Walk up to the next waypoint of the route and commit to it before taking your break. When resuming your test walk, click Back and commit to the same waypoint once more before you continue.

This procedure ensures that the measurements collected during the pause and along the next route segment to follow will be positioned accurately. To avoid these complications, it is advisable not to take extended pauses while walking and recording a track.

NT12-7002 ver 1.0

129

The logfile is created in the regular TEMS Investigation logfile format (*.3. Please bear in mind.trp).3 on the preparation of planned routes. using the Back and Forward buttons. Pinpointing Without a Planned Route In the Pinpoint Window you can alternatively place waypoints manually to indicate your trajectory as you go. which also accommodates the auxiliary pinpoint data. A “shortcut” might thus be created that goes through walls or other obstacles – compare the advice given in section 12. however.TEMS Investigation 14. for instance because it is behind a locked door.1. without following a planned route. and you are prompted for a location in which to save it. This is useful if you cannot get to a waypoint. • Click the Start button. Here is how to do manual pinpointing: • • Load the map set you want to use by clicking the Open button. This “freehand” pinpointing is similar to the procedure used in a Map window (described in section 11. This initiates recording of a logfile. The following controls appear in the pop-out pane: 130 .1 User’s Manual 12. 12. Skipping Waypoints of a Route You can skip waypoints without committing to them.4. Instead of selecting a route. except that it always involves logfile recording. the measurements will be positioned along a straight line between the adjacent retained waypoints.3).3. that this effectively removes the waypoint from the track when it comes to the positioning of the recorded data. click the “No Route” item.2.

all measurements collected since your previous commit are positioned in a straight line between the two waypoints. they do not affect the positioning itself or how it is represented in the logfile. (When you perform a commit. click the Crosshair button.Chapter 12.0 131 . then click the Commit button to place a waypoint there. A pin with a green head is drawn in the map view to mark the spot. You may of course need to pan the map first to bring the relevant part of it into view. You can toggle between the two modes at any time. Commit button: Place a waypoint at the current position. All measurements collected so far are positioned at that waypoint. These modes are just two different methods of placing waypoints. As soon as you have started recording. NT12-7002 ver 1. pinpoint once to indicate your starting position. The Pinpoint Window Control Function The Mouse and Crosshair buttons are used to select pinpointing mode. and the map is recentered around it. The waypoint is automatically committed. Crosshair: In this mode. a large redheaded pin with a crosshair appears at a fixed position in the map view. • • The default pinpointing mode is Mouse. you simply click a spot on the map to place a waypoint in that spot. The button is then always labeled with the sequence number of the next waypoint to be added. If you prefer Crosshair mode instead. Also keep a steady pace between waypoints. pinpointing at regular intervals and whenever you change direction. Pan the map so that the pin marks your current position. Stop button: Stop pinpointing and close the logfile. Mouse: In this mode. This button is used only in Crosshair mode. as explained above.) • Each time you place a new waypoint it is highlighted. Continue along your intended trajectory.

If you do. the following applies: 132 . Currently there is no presentation of information elements or other measurement data in the Pinpoint Window.1.2. the new route will appear in the popout pane listing as “Unnamed Route <n>”. Below the Commit button in the pop-out pane is a stack of boxed items representing your latest waypoints.5. Relation to Other TEMS Investigation Functions Data Presentation 12. Coexistence Issues While you are recording a logfile in the Pinpoint Window (whether pinpointing manually or walking along a pre-planned route).5. This closes the logfile. in live mode as well as during analysis. its sequence number and time of creation (“hh:mm:ss”) are displayed. a Pinpoint Added event is triggered. 12. For each waypoint.TEMS Investigation 14. you can of course have any presentation windows open side by side with the Pinpoint Window and inspect measurement data there. You are also asked whether you want to save the waypoints you have placed as a route in the map set. Note also that you can have your walked track plotted in a Map window. Naturally you can change that name if desired. • When you are done with your test. However. 12.5.1 User’s Manual Each time you place a new waypoint. click Stop.

The Pinpoint Window • You can start recording of other logfiles by other means (using the manual controls or running a script). The ongoing recording will not be affected. A Start Recording activity in a script will start a new logfile. Having a GPS activated in TEMS Investigation does not affect the Pinpoint Window in any way.Chapter 12. so that any subsequent recordings initiated while the pinpointing is still active will be positioned according to the pinpointing data. starting to record in the Pinpoint Window automatically redefines the preferred positioning source as pinpointing. • • • Conversely. but the positioning source is not unique to each recording. However. it will keep the positioning source that was preferred in TEMS Investigation when the recording began. and not by any other source. but note again that the positioning will be governed by your actions in the Pinpoint Window. all methods of logfile recording can be used independently without restrictions. However. NT12-7002 ver 1. In summary. Clicking Stop Recording on the main window toolbar has no effect on the Pinpoint Window. these recordings will automatically be positioned according to the Pinpoint Window waypoints.0 133 . Scripts can run independently of what is done in the Pinpoint Window. while logfile recording initiated by other means is in progress. it is possible to start another recording in the Pinpoint Window.

or as an activity in a Service Control script.1 User’s Manual 13. however.Scan . Scripted Scanning Scripted scanning works just like scripting of other activities and does not require special comment. and they are gone through in chapters 14–19. please refer to chapter 20 (the scan activities are listed in section 20. that scripted scanning is currently available for a subset of supported scanning devices: R&S TSMW Manual Scripted 13. 134 Transcom Anritsu PCTel SRU DRT Scanning Type/ Scanning Device Sony Ericsson Andrew i.16.TEMS Investigation 14. Note. The configuration dialogs are the same in both cases.5). Scanning: General Scanning can be done either • • manually from the Navigator’s Equipment tab.1.

1. the Activities subtab is populated. Once the device has been activated. See chapter 8. On the Activities subtab.2. Expand this node to view a list of the scanning methods that this device supports. and from the context menu select the desired configuration set among those in existence.2. expand the Scan node. 13. you need to activate the device you want to scan with (if it is not already activated). select the device to scan with. All details are covered in subsequent chapters (14–19). and select Configuration Sets from the context menu. to be able to access the scanning configuration dialogs.2. This opens a dialog where you define a setup for the selected scanning method. the available activities will include ones collected under a Scan node. Right-click the scanning method you want to use. • First. you can initiate a scan manually as follows: • • • • On the Navigator’s Equipment tab. • • Right-click the scanning method you want to use. The dialog contents depend on the technology and scanning method chosen as well as on the make and model of the scanning device. Performing a Scan Manually With suitable configuration sets already defined. Right-click the scanning method item again. from the Activities subtab in the bottom pane. Manual Scanning Setting Up a Scan Manually Scanning tasks can be set up manually on the Navigator’s Equipment tab.2. specifically. and from the context menu select Start. For a scanning-capable device.0 135 . 13. Scanning: General 13. NT12-7002 ver 1.Chapter 13.

you are free to present it in any presentation window. For band support in connectable scanning devices. For example. Under the Scan node. Frequency band support is determined by the scanning device and by the antennas.2.3.1 User’s Manual While the scan is ongoing. • • Technical Data on Scanning Devices A Sony Ericsson phone cannot act as a regular phone while it is scanning. It cannot engage in voice/video calls or data services during this time. Detailed data on the scanning capabilities and performance of Sony Ericsson phones is provided in the technical paper “Scanning with Sony Ericsson TEMS Devices”. • 136 .TEMS Investigation 14. 13. However. scan data can be displayed in status windows of your own design. and the output from all of these can be displayed in parallel.4. Presenting Scan Data The output of scans is primarily intended to be displayed in a suite of readymade bar charts and other windows. right-click the scanning method being executed. included on the installation CD in the subdirectory Documents. The scanning presentation windows are fully synchronized with the rest of the application. go to the Activities subtab again.4.1. it will be indicated in the top pane of the Equipment tab for the device that is busy scanning. 13.3. Recording Scan Data Manually To record data from a manually initiated scan. How to build a status window is covered in chapter 24. see the Getting Started Manual. It is possible to scan with several devices simultaneously. 13. create a new logfile as described in section 11. The information elements of interest are all found in the Information Elements and Events volume.1. and select Stop. • To stop scanning. since all scan data is available in information elements. section 10.

please consult documentation from the respective suppliers. DRT Scanners For a DRT scanner. For further information on third-party scanning devices.5. Notes on Scanner Multitasking PCTel Scanners Within a cellular technology.3. Scanning: General • Some technical data on PCTel scanners and antennas used with them is provided in the Getting Started Manual.1. The resource percentage selected is the minimum that the scan task is guaranteed to get when executed. 13.5.5.Chapter 13. If the scan tasks that are running have a combined resource allocation of less than 100% in their setups.) Again the limit is expressed in terms of measurement points. Only the scanner measurement capacity places a limit on the possibilities of handling several scanning tasks in parallel. It is therefore not possible when setting up scan tasks to allocate more than 100% of resources in total. 13.2.0 137 . 13. section 10. (The DRT scanner can produce more data than this. Rohde & Schwarz TSMW The TSMW scanner uses a form of automatic load balancing to make the best possible use of the scanner’s measurement capacity.5.) NT12-7002 ver 1. TEMS Investigation sets a limit on the amount of scan data it will accept. so that it cannot perform any other tasks at the same time. and they can be run concurrently by PCTel scanners. A PCTel scanner’s measurement capacity is indicated as a number of measurement points. a WCDMA SCH timeslot scan at maximum resolution may require the full resources of the PCTel scanner.7. then the actual resource use will be raised automatically if the scan tasks require it.2. 13. scanning methods are conceptually independent. For example. and the setup dialog keeps track of the number of measurement points that remain to be allocated.5. but the data volume would then become unmanageably large. As you set up the scanning tasks. you are continuously notified in the setup dialog of how many measurement points that remain. (There is no inverse mechanism treating the selected resource percentages as “opening bids” that can be pared down at execution time.

Sony Ericsson Phones and SRUs Sony Ericsson phones and SRUs do not handle concurrent execution of multiple scanning methods.6.5. 13.TEMS Investigation 14.5. 13. 138 .4.1 User’s Manual R&S recommends that each scan task should be allocated at least 20% of resources in the setup dialog. Notes on GPS Units in Scanners The internal GPS in a scanner equipped with such a device will deliver data only if it is selected as Preferred GPS and activated in TEMS Investigation. See section 8.

1. For specifics.0 139 . Built on Ericsson hardware. chapter 14. NT12-7002 ver 1. 1. For more information about connectable scanners with GSM scanning capability. A note on terminology: GSM radio frequency carriers are sometimes referred to below as channels for simplicity. see the Getting Started Manual. Please note that for a scanning method to be actually available in TEMS Investigation.4. 2.1.1.1. GSM Scanning 14. How to configure the R&S scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual. section 4. supported using the various devices as indicated. Scanning Methods and Capabilities TEMS Investigation offers these GSM scanning methods. 14. see Information Elements and Events. although this is a slight abuse of the term. the device must have been purchased with the relevant option (wherever applicable). section 10.Chapter 14. GSM Scanning TEMS Investigation supports scanning of GSM radio frequency carriers with the following kinds of device: • • • • Sony Ericsson phones1 SRUs (Scanning Receiver Units)2 PCTel scanners Rohde & Schwarz TSMW scanner.

2.1.2. SRU Setting this to Yes causes the phone to decode the Base Station Identity Code whenever possible.3 14. There is no limit to the selectable number of channels. 14. static ARFCN set RSSI scanning: BSIC decoding RSSI scanning: C/I measurement RSSI scanning: Sys Info decoding Spectrum analysis R&S TSMW 14. Technology Band Channels 14. GSM frequency band or bands to scan.2. SRU .TEMS Investigation 14. RSSI Scanning Setup of RSSI Scan: General Settings Set this to “GSM” for GSM scanning. Select all channels to scan the entire band.2 14. It should be noted that BSIC decoding is computationally costly and considerably reduces the sample rate of the scan.2 14.1 User’s Manual Sony Ericsson PCTel SeeGull GSM Scanning Capability/ Scanning Device RSSI scanning.3 14.3 14.2. BSIC Setup of RSSI Scan: Sony Ericsson.2.2. ARFCNs to scan on the selected band. 140 Section Ref.

Regardless of the choice made here. PCTel scanners can be purchased with or without the C/I scanning function enabled.Chapter 14.5. If available. GSM Scanning 14. It should be noted that BSIC decoding is computationally costly and considerably reduces the sample rate of the scan. Setup of RSSI Scan: PCTel SeeGull Select whether to perform a regular GSM signal scan (“Normal”) or a Continuous Wave scan (“CW”). the function can be turned on and off in the dialog.2. etc.1. section 3. C/I Measurements Setting this to Yes causes a subset of the “C/I” information elements to be updated. This setting applies to all channels you select for scanning. the measurements are extracted to the same information elements (Scanned RxLev. NT12-7002 ver 1.1.3. in the “GSM” category). It is not possible to specify the type of scan for each channel separately. as described in Information Elements and Events. Setting this to Yes causes the phone to decode the Base Station Identity Code whenever possible.0 141 . Bandwidth Remaining Measurement Points BSIC See section 13. Check the Device Inquiry mode report from the scanner to find out whether it is capable of decoding BSIC. check the Device Inquiry mode report from the scanner to find out whether it has this capability (“GSM BCCH C/I”). PCTel scanners supplied with older versions of TEMS Investigation may lack BSIC decoding capability.

The measurement tasks are manually distributed on the built-in front-ends. and this is therefore done only once each time the strongest cell changes. Setup of RSSI Scan: Rohde & Schwarz TSMW Average measurement rate (in millihertz) shared between all selected channels. Resource Allocation (%) 142 .4. Resources allocated on the specified front-end. This can produce many more power results for C0 carriers than the SCH measurement. Whenever System Information is read. • • Channels: Channels to scan. C/I (DL): Enables carrier-to-interference measurement.3.1 User’s Manual SI on Strongest Setting this to Yes causes the scanner to decode System Information messages for the strongest cell. Dummy Burst Removal (DL): Enables detection of dummy bursts and removal of dummy bursts from the GSM signal before further analysis.2. SCH Power (DL): Enables SCH-related measurements such as SCH power.5. the information element Neighbor (SI) ARFCN is updated. BSIC. Measurement Rate (mHz) Measurement Details • • • RF Front-end Front-end on which to schedule measurements. 14. and GSM frame number. Dummy Burst Power (DL): Enables power measurement for dummy bursts. This is only valid for SCH-related measurements. The scanner must suspend the regular scan in order to read System Information. See also section 13. ETS power.TEMS Investigation 14.

2. NT12-7002 ver 1. Spectrum Analysis The setup for spectrum analysis is the same as for WCDMA (except that Technology = GSM). Presentation of RSSI Scanning The main vehicle for presenting GSM RSSI scan data is the GSM RSSI Scan Bar Chart: The top chart by default shows the strongest scanned channels sorted by decreasing signal strength. GSM Scanning 14.5. See section 15.0 143 .1. The bottom chart by default shows all scanned channels in order of ascending ARFCN. Regarding the bar chart window itself.3. 14.5.Chapter 14. see chapter 30.

chapter 14. WCDMA Scanning TEMS Investigation supports scanning of WCDMA carriers with the following kinds of device: • • • • • Certain Sony Ericsson phones operating in scan mode SRU (Scanning Receiver Unit) PCTel scanner Rohde & Schwarz TSMW scanner Anritsu scanner. How to configure the R&S scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual. see the Getting Started Manual. the device must have been purchased with the relevant option (wherever applicable).1 User’s Manual 15.1. 144 . supported using the various devices as indicated.4. Scanning Methods and Capabilities TEMS Investigation offers these WCDMA scanning methods. Please note that for a scanning method to be actually available in TEMS Investigation.TEMS Investigation 14.1. 15. section 10. For more information about connectable devices with WCDMA scanning capability.1.

of UARFCNs SCH timeslot scanning RSSI scanning Spectrum analysis Network scanning 1.2 15. WCDMA Scanning Sony Ericsson.4 15.0 145 Section Ref.2 15. Anritsu ML8720: 1 or 2 depending on physical configuration.2.6 NT12-7002 ver 1.3 15.2 15.3 15.5 15.2.Chapter 15. R&S TSMW PCTel PCT WCDMA Scanning Capability/ Scanning Device PCTel SeeGull MX PCTel SeeGull EX PCTel SeeGull LX Anritsu ML8780A Anritsu ML8720 . Top N Pilot: SIB decoding (continuous) Pilot: SIB decoding (snapshot) Pilot: High Speed/High Dynamic Pilot: P-SCH + S-SCH Pilot: Max. 12 1 15. no.2 8 4 12 12 12 12 15. SRU Pilot scanning. static SC set Pilot scanning.2 15.2 15.

Setup of Pilot Scan: General Always “WCDMA” for WCDMA scanning. UARFCNs and scrambling codes are selected independently of one another. S-SCH).2. scrambled with cell-specific scrambling codes. Pilot Scanning (with SCH Scanning) This method scans CPICH control channels. SRU Setup options are as follows: Scan selected: A user-defined. Optional snapshot SIB decoding. static set of scrambling codes (common to all UARFCNs) scanned. the same method also scans primary and secondary synchronization channels (P-SCH.2. WCDMA frequency band to scan. 15. Scan strongest: Strongest scrambling codes scanned (“Top N”). Optional snapshot SIB decoding.1 User’s Manual 15. Where supported. Here you set the UARFCNs of the frequencies on which to scan the CPICH. Unconditional and continuous SIB decoding.2.TEMS Investigation 14. Several UARFCNs can be scanned at a time.2. BCH scanning: User-defined.1. The choice is made under Type of Scanning in the setup dialog. • • • Setup of Pilot Scan: Sony Ericsson. Technology Band Channels 15. 146 . The allowed range is dependent on the frequency band. static set of scrambling codes (common to all UARFCNs) is scanned.

BCH scanning: If you choose this option. The threshold should be adjusted to ensure detection of cells actually present while keeping the false detection rate down. Scrambling Codes NT12-7002 ver 1. Scan Strongest This field is enabled if you have chosen “Scan strongest” under Type of Scanning.Chapter 15. Enter the scrambling codes you want to scan. The processing time freed up in this way is instead used to continuously decode System Information Blocks (SIBs). you select scrambling codes in the same way as for Scan selected. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under Channels.0 147 . This decoding is furthermore continuous. and the same scan data will be collected. WCDMA Scanning Type of Scanning See also the introduction of this section. However. The default is –26 dB. enter the value N here (N  40). This field is enabled if you have chosen “Scan selected” or “BCH scanning” under Type of Scanning. the updating frequency will be considerably lower. • Cell Noise Floor Ec/Io threshold for accepting a signal on the CPICH as a detected cell. and the sensitivity of the scrambling code detection may be lower as well. To scan the N strongest scrambling codes. • Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs. The scanner automatically finds the strongest scrambling codes. unlike that governed by the System Information option (which see).

148 . Only settings supported by the connected scanner are displayed in the dialog. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under Channels. the phone reverts to regular pilot scanning. It then refers not to snapshot SIB decoding but to the continuous SIB decoding performed by that method. Type of Scanning See also the introduction of this section.1. Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs. static set of scrambling codes. SIBs will be decoded again for that cell. On completing the SIB decoding. To scan the N strongest scrambling codes. Setup of Pilot Scan: PCTel The set of scrambling codes to scan on each UARFCN is composed in one of two ways: • • user-defined. • Number of Pilots This field appears if Type of Scanning is set to “Scan strongest”. 15. For BCH scanning. Up to 128 scrambling codes can be selected.TEMS Investigation 14. If the strongest cell does not change within two minutes. this option is always set to Yes. The same scrambling codes will be scanned on the CPICH and on the P-SCH and S-SCH. The scanner automatically finds the strongest scrambling codes. common to all UARFCNs strongest scrambling codes (“Top N”) What settings are supported by the various PCTel SeeGull models appears from the table in section 15.1 User’s Manual System Information If this option is set to Yes for Scan selected or Scan strongest.3. enter the value N here (N  32).2. a “snapshot” SIB decoding will be done once every time a new cell has become the strongest (unless that cell has previously appeared as the strongest during the last two minutes).

By raising the threshold you reduce the influence of random noise correlations.10). P-SCH Ec/Io. Enter the scrambling codes you want to scan. It is possible to reduce the amount of data that is presented and recorded: • • Full means no reduction. • SIR Setting this to Yes causes the scanner to deliver the information elements “Sc . S-SCH Ec/Io. NT12-7002 ver 1.8 and 15. and you will thus be able to discern multipath and fading effects more accurately. Sub means that some data is not presented or recorded (compare sections 15.2.2. and Rake Finger Count are excluded. Time Offset.5.Chapter 15. The precise meaning of “Sub” depends on the scope of the scan: • For “Scan selected”. It should be noted that choosing “Sub” results in a much faster updating of scan presentations. (The “SIR” field is disabled in this case. only P-SCH Ec/Io and S-SCH Ec/Io are excluded.. as is SIR. This is a signal code power threshold (in dB) used for the Aggregate Ec/Io and Delay Spread measurements (see section 15. SIR”.0 149 . The setting –20 dB is recommended. If the PN threshold is set too low.2.1..) For “Scan strongest”. Remaining Measurement Points Data Mode See section 13. WCDMA Scanning Selected Numbers PN Threshold This field appears if Type of Scanning is set to “Scan selected”.7). the Aggregate Ec/Io and Delay Spread values will be affected by random noise more than may be desired.

4. Each reported sample is typically based on a 10 ms measurement. • Dwelling Time The length of time the scanner dwells on each scrambling code (cell) trying to decode System Information blocks. With this option selected. Each sample reported by the scanner is typically based on a measurement 20 ms in length.TEMS Investigation 14. See also section 13. From the SIB decoding are extracted the information elements “Sc 1st (2nd.1 User’s Manual System Information Set this to Yes to decode System Information blocks (continuously).2. High Speed and High Dynamic. These are two algorithms with different priorities: • High Dynamic puts the emphasis on accuracy. a maximum of 16 scrambling codes can be scanned. Measurement Mode There are two choices. Setup of Pilot Scan: Rohde & Schwarz TSMW High Speed or High Dynamic. The default is 50 = 2000 ms. before moving on to the next cell. 15. Average measurement rate (in millihertz) shared between all selected channels. High Speed is faster and accordingly less accurate. Measurement Mode Measurement Rate (mHz) RF Front-end Resource Allocation (%) 150 . These are two algorithms with different priorities. High Dynamic puts the emphasis on accuracy. whereas High Speed is faster and accordingly less accurate. Given as a multiple of 40 ms.5. The measurement tasks are manually distributed on the two built-in front-ends. 4th) Intra-freq Cells”.3. Resources allocated on the specified front-end. 3rd. Front-end (processor) on which to schedule measurement.

The scanner automatically finds the strongest scrambling codes.5. (ML8720 only) Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs (“Top N”). For example. The default is 4 dB. where Nch is the number of UARFCNs entered under Channels. enter the value N here. up to 13 SCs can be scanned on each. common to all UARFCNs. 15.2. or strongest scrambling codes (“Top N”) Type of Scanning See also the introduction of this section. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under “UARFCN” below. • Number of Pilots This field appears if Type of scanning is set to “Scan strongest”. The maximum number of pilots that can be scanned is equal to floor(40/Nch). Up to 32 scrambling codes can be selected. This threshold (value in dB) determines how high above the noise floor a scrambling code must reach in order to be accepted as valid by the scanner.Chapter 15. To scan the N strongest scrambling codes. The same scrambling codes will be scanned on the CPICH and on the P-SCH and S-SCH. static set of scrambling codes. Setup of Pilot Scan: Anritsu The set of scrambling codes to scan on a UARFCN is composed in one of two ways: • • user-defined. Selective Level NT12-7002 ver 1.0 151 . WCDMA Scanning Resource Available (%) Read-only field indicating the remaining available resources on the processor selected under RF Frontend. if 3 UARFCNs are selected.

) This mode is useful especially for troubleshooting of transmitters. If you select two UARFCNs. This setting governs the choice of cell search method in Top N scan mode (“Scan strongest” option).TEMS Investigation 14. This is more suitable for drive testing and is the default setting in TEMS Investigation. this threshold governs how many Rake fingers will contribute to the signal. however.7) the CPICH Scan Data status window (section 15. The default is 20 dB.2. • • • Presentation: General Pilot scan data is presented in the CPICH Scan bar charts (section 15.8) the CPICH Scan line charts (section 15.2. Search Method (ML8720) BCH Scan (ML8780A) If selected.2.2. for a given scrambling code. as explained above. • If P-CPICH is selected. the scanner will perform continuous SIB decoding. If you are scanning two UARFCNs it is the only option.9) 152 . In other words. 15.6. only CPICH channels will be scanned to find scrambling codes. (For all scrambling codes detected in this way. • If SCH is selected. the scanner will search for scrambling codes that use P-SCH and S-SCH. The P-CPICH mode cannot be used if two UARFCNs are to be scanned. the scanner will measure and report on the P-SCH and S-SCH as well.1 User’s Manual Rake Threshold This threshold (value in dB) determines. This can only be done on one UARFCN at a time (only one is selectable under Channels when the BCH Scan option is set). the P-CPICH radio button is grayed. Setting the threshold at n dB means that a signal path must not be more than n dB weaker than the strongest one. how strong a signal path must be (in relation to the strongest signal path for that scrambling code) in order to be accepted as valid.

10).2.2.13.8. 15. Regarding data sorting. the updating rate is also greatly affected by the size of this set. Presentation: “CPICH Data” Status Windows The CPICH Data and CPICH Best UARFCN Data status windows both contain a large number of columns with scan data.1.2.0 153 . whereas for the “Top N” scan the number N is only marginally important (since all scrambling codes have to be searched regardless of N). They differ only with respect to sorting: CPICH Data is sorted first by UARFCN. whereas CPICH Best UARFCN Data is sorted by Aggr Ec/Io regardless of UARFCN.8) for each scrambling code found.7. WCDMA Scanning Synchronization channels are presented in the Synch Channels window (section 15. see section 15. One predefined bar chart is provided for each UMTS frequency scanned. For a manually selected set of scrambling codes. Each bar chart by default presents peak Ec/Io (see section 15.2. The updating rate is chiefly dependent on the number of live signals encountered in the network.2. Presentation: “CPICH Scan” Bar Charts The CPICH Scan bar charts present CPICH scan data. 15.Chapter 15. The columns have the following meanings: NT12-7002 ver 1.

the difference between them in dB.e. Ranges from 0 to 38399. The aggregate code power is a measure of the total signal power (distributed around the main peak due to multipath propagation) that is above the PN threshold (settable in the PCTel scanner: see section 15. This is a measure of the signal spreading due to multipath propagation. Measured on DPCCH.1 User’s Manual SC Peak Ec/Io Scrambling code number.TEMS Investigation 14.e. The aggregate code power of the scrambling code in dBm. 15. See Information Elements and Events. the difference between them in dB. section 3. given in chips from a 1/100th second time mark aligned with GPS time. Presentation: “CPICH Scan” Line Charts The default configuration of this window is as follows: 154 . Rake receiver gain. The aggregate code power of the scrambling code relative to the total signal power in the channel (Io).2. i.2. Time in chips from the first to the last Ec/Io peak that is above the PN threshold. Rake finger count. i. Difference in dB between the aggregate code power (Ag Ec) and peak code power (Peak Ec). Peak Ec Ag Ec/Io Ag Ec Aggr–Peak Ec Delay Spread RFC Time Offset SIR All of these are identical with information elements having similar names but beginning with “Sc”.2.3). The peak code power of the scrambling code in dBm. the number of Ec/Io peaks (multipath components) that are above the PN threshold. i. The peak code power of the scrambling code (Ec) relative to the total signal power in the channel (Io).9.e. Signal-to-interference ratio of the scrambling code in dB. i. The time offset of the radio frame on the CPICH.e.

The top chart shows Aggr Ec (in dBm) and the bottom chart shows Aggr Ec/Io (in dB).0 155 . Please note that the IEs described here are no longer present by default in this window. NT12-7002 ver 1. WCDMA Scanning Chart Panes The charts present the five strongest scrambling codes.1 • Poss No Of AS Members: The active set (AS) is defined as the set of scrambling codes (SCs) associated with channels that are assigned to a particular subscriber unit. Additional Information Pane The Additional Information pane (bottom right) shows the CPICH pilot pollution situation. you need to add them manually. Legend Pane The Legend pane (bottom left) glosses either of the two charts. right-click and choose the desired chart from the context menu. Here an SC is regarded as a possible active set member if it is sufficiently 1. To switch to the other chart.Chapter 15.

Example: If the argument is 3 (default value).e. 2. Ec values in mW). all SCs with a code power not more than 3 dB below that of the strongest SC will be counted.TEMS Investigation 14. there are three such SCs. for “Max 2 SCs”. and 4 SCs respectively. 3. SC code power Strongest SC Distance to threshold. otherwise it is simply the sum of the code powers of all possible active set members.. In the above figure. • Other/Own . For “Max N SCs”. 156 . “Other” is the sum of the code powers of all remaining SCs.1 User’s Manual strong compared to the strongest SC. The relative code power threshold is determined by the argument within square brackets []. In the example below. only the strongest of the three is included in “Own”. if the number of possible members is at least N. “Own” is the sum of the code powers of the N strongest possible active set members. indicated by argument Threshold for possible AS members (which are included in “Own”) Own power. However. max 2 SCs SC Other power. there are three other SCs reaching above the threshold which is set relative to the strongest SC.. based on the power threshold described above (again given as argument to each information element) and on different assumptions about the number of possible active set members. Note that one cannot know for sure (on the basis of the scan data alone) whether the possible members actually do belong to the active set. The four “Other/Own” elements represent the assumptions that there is desired signal power on 1. : These are estimated ratios between polluting signal power and desired signal power. so the active set is judged to have a total of four possible members. max 2 SCs The “Other/Own” ratios are of course calculated from absolute code power values (i.

Presentation: Synch Channel Data Window This window presents scan data on the synchronization channels P-SCH and S-SCH. NT12-7002 ver 1.10. obtained with the Pilot scanning method. The presented data can be freely rearranged.3.0 157 . SC P-SCH Ec P-SCH Ec/Io Scrambling code number.e. The peak power of the Primary Synchronization Channel. the difference between them in dB. WCDMA Scanning Note: The arguments should be kept the same for all five information elements. The peak power of the P-SCH (Ec) relative to the total signal power in the channel (Io). S-SCH (in dBm). the difference between them in dB.Chapter 15.2. The peak power of the S-SCH (Ec) relative to the total signal power in the channel (Io). “Changing Status Window Properties”. i. as described in section 24. It is of course possible to set each argument to any of the permissible values.e. S-SCH Ec S-SCH Ec/Io By default the scrambling codes are sorted by signal power with the strongest on top. P-SCH (in dBm). The peak power of the Secondary Synchronization Channel. but with different arguments for different elements you cannot really draw any useful conclusions. 15. i.

2.1. Presentation: BCH Scanning All scan data collected using the options Scan selected and Scan strongest are obtained for BCH scanning also (though less frequently).TEMS Investigation 14.13. see Information Elements and Events. Sorting of Scrambling Codes You can sort scrambling codes in scanning information elements in a number of different ways.7–15. section 3. 15. Presentation: “Finger Info” Status Windows These windows present Rake finger information obtained during Pilot scanning.11 above regarding the presentation of this data. Customizing the Presentation 15. Sort by decreasing Aggr Ec/Io (default) Sort by increasing Aggr Ec/Io A dialog appears with these sorting options: 158 . where the guiding principle of scheduling is to provide (as far as possible) all UEs with all the resources they need while also making sure that the total uplink interference does not exceed the accepted maximum. The sorting order is set in the General window. decoded System Information Blocks are output in the Layer 3 Messages window at a greatly enhanced rate. Another piece of data found in SIBs is an uplink interference measurement. See Information Elements and Events.13. This is particularly interesting for HSUPA.2.2.12. For definitions of the information elements. see sections 15.1 User’s Manual 15. No special presentation windows are provided for BCH scanning. but they are also extracted as information elements. • • • • Open the General window from the Navigator.2.2.2. 15. section 3.11.2. see Information Elements and Events. Double-click the item “WCDMA”. The uplink interference measurements can of course be inspected in the plain-text SIB decoding. One form of refined TEMS Investigation output that can be based on SIBs is the Missing WCDMA Neighbor event which warns about missing neighbors in WCDMA.2. section 7. However.2.

and this sorting order is unchangeable. section 3. 15. that is. • 15. SCH Timeslot Scanning This method scans timeslot-length intervals.3.Chapter 15. It should be pointed out that this scan is wholly separate from the P-SCH and S-SCH scans included in the Pilot scanning method (section 15. WCDMA Scanning • Sort by fixed position: Scrambling codes are sorted by index and are always assigned the same argument indices. 15.3. 15.13. the code with the lowest index appears at argument index 1.1.0 159 . on a Primary Synchronization Channel (P-SCH). intervals 2560 chips long. These elements are sorted by signal strength (Aggr Ec/Io) in descending order. Sort by scrambling code: Scrambling codes are sorted by index.2. It is useful for monitoring synchronization reference signals sent on this channel. i.2.3. etc.1.e. UARFCN to scan.1. scrambling code n is always found at argument index n + 1. WCDMA frequency band to scan. Use these elements in order to view scan data from several UARFCNs in one window. Presenting Scrambling Codes from Multiple UARFCNs In the “Sc Best” information elements. Setup of SCH Timeslot Scan General Settings Always “WCDMA” for WCDMA scanning. the code with the next higher index appears at argument index 2.2) is fixed and is not affected by the General window settings.2). Note: The sorting order of the “Sc Best” elements (see Information Elements and Events. Technology Band Channels NT12-7002 ver 1. all scrambling codes found on all UMTS frequencies are collected in a single array.

3. Each SCH signal will show up as a spike on the trace. etc.3.1. 4.5. the height of the spike reflecting the strength of the signal in terms of Es/Io. Compression Rate Remaining Measurement Points See section 13. The legend pane gives 160 . 15. 15. Presentation: SCH Timeslot Scan Bar Chart The bar chart displays an Es/Io trace for the latest timeslot scanned (2560 chips).2. means that the peak (not average) power is reported for successive segments 2. Every 2.TEMS Investigation 14.1. Context Settings The time resolution of the scan: • • Every means that a power value is reported for every chip in the timeslot. or 8 chips in length.1 User’s Manual Center Frequency The center frequency of the UARFCN chosen.2.

no conclusions can be drawn about the value of T_Cell. Provided that the base station clock is synchronized with GPS time. WCDMA frequency band to scan. the parameters “Time diff 1-2” and “Time diff 2-3” are given: • • “Time diff 1-2” indicates the time separation in chips between the strongest peak and the second strongest. Since the SCH signals are repeated every timeslot. the spikes will normally remain in the same positions as the trace is updated. RSSI Scanning Setup of RSSI Scan General Settings Always “WCDMA” for WCDMA scanning. the T_Cell parameter can be determined: the spike will be positioned approximately at T_Cell + 140 chips. “Time diff 2-3” indicates the time separation in chips between the second strongest peak and the third strongest.Chapter 15.2. if the compression rate is set to “Every 4”. 15. the offset being due to delay in the scanner.1. or 8 chips. depending on the setup. 15. From this the time separation between the sectors can be determined.g. The updating rate is dependent on the compression rate and on network conditions. In the lower right pane. The position of a spike shows at what point a new timeslot begins in the current transmission.4.1.4.1. the updating interval will be on the order of 1 s. and 512 chips). one for each sector. These parameters are identical with the information elements SCH TS Sc Time Diff 1-2 and SCH TS Sc Time Diff 2-3. Determining the time separation naturally does not require synchronization of the base station with GPS time. If the base station is not synchronized with GPS time. The SCH timeslot scan will then display multiple spikes within a timeslot. see section 15. 256. 15.4. or peak Es/Io for every 2. however. However. 4. In a WCDMA cell with multiple sectors.1.0 161 . see Information Elements and Events. section 3. 0.3. Technology Band NT12-7002 ver 1. each sector will transmit/receive at a different time offset (e. WCDMA Scanning Es/Io for each chip.

The allowed UARFCN range is dependent on the band.1.2. 15. Regardless of the choice made here. etc. the measurements are extracted to the same information elements (CW Sc RSSI. in the “WCDMA” category). 162 . 15.2.5.4. Remaining Measurement Points See section 13.1 User’s Manual Channels UARFCNs to scan (up to 255).4. This setting applies to all channels you select for scanning.1. Presentation: RSSI Scan Bar Chart This bar chart displays RSSI for each UARFCN scanned.TEMS Investigation 14. Bandwidth Context Settings Select whether to perform a regular WCDMA signal scan (“Normal”) or a Continuous Wave scan (“CW”).

Spectrum Analysis This scanning method shows downlink signal strength as a function of frequency. The minimum number is 1. Adapt the resolution to the width of the frequency range.2. Interval between successive scan samples in kHz.5. Technology Band Start Frequency Stop Frequency Resolution Bandwidth 15. the legend pane will list all samples.5. See section 13. the highest selectable resolution being 5 kHz. the chart. on the other hand.1.0 163 . Given in MHz. Given in MHz.5.5.Chapter 15. High end of the frequency range to be swept by the scan.1. WCDMA Scanning 15.1. 15. 15. Low end of the frequency range to be swept by the scan. can of course only distinguish the samples as far as the screen resolution permits.1.1. Number of Sweeps Context Settings The number of sweeps on which to base the presented average RSSI. In the presentation window.5. Setup of Spectrum Analysis Scan General Settings Choose “WCDMA” for WCDMA scanning. Note that the spectrum analysis is prone to consume a large number of measurement points. WCDMA frequency band to scan. Remaining Measurement Points NT12-7002 ver 1. and the maximum is 16.

one for the downlink (Spectrum Analysis Bar Chart) and one for the uplink (Spectrum Analysis Uplink Bar Chart). 850 MHz.5. Network Scanning This function is highly useful for obtaining a bird’s-eye view of an unfamiliar WCDMA radio environment. Uplink spectrum analysis is currently not supported by any currently connectable devices. On each carrier. once it has found a WCDMA carrier. In contrast.TEMS Investigation 14. overlapping or not. A mobile phone in regular phone mode. It will detect WCDMA carriers (UARFCNs) that are in use on each of the WCDMA bands 2100 MHz. thus allowing faulty frequency allocations to be easily found and rectified. but the chart is retained to allow displaying of such data from old logfiles. 1.1 They both display RSSI as a function of frequency.6. 15. automatically assumes that there are no further UARFCNs within ±3 MHz of the detected carrier and is therefore unable to spot overlapping carriers. Presentation: Spectrum Analysis Bar Charts Two charts are provided. 1900 MHz.2. a Sony Ericsson phone in scan mode is usually able to identify all carriers. 164 . one cell (scrambling code) is detected and presented.1 User’s Manual 15. In network scanning mode it is also possible to detect inappropriate allocation of UARFCNs resulting in carrier overlap.

1.4.1. Interval <n> enabled Band Set the flag to Yes if you want to define this UARFCN range.2. If you want the UARFCN range to be identical to an entire WCDMA frequency band.6. If you want the UARFCN range to consist of a portion of a band.1.0 165 . From.4.3–5.3.6. sections 5.Chapter 15.) If this option is checked. (See  3GPP 25. Custom range. 3) to scan in the network.101. set Custom range to Yes.6. WCDMA Scanning 15.4 for details on the two kinds of channel. Technology 15. Additional channels have UARFCNs that are completely different from the general channels. 3”) You can set up three separate UARFCN ranges (Interval 1. UARFCN Ranges (“Interval 1. Include additional channels Context Settings Check this to include additional channels on the 1900 or 850 MHz band. To 15. 15.6. select that band here. 2. Additional fields “From” and “To” appear. in which you specify the endpoints of the UARFCN range. all additional channels that lie within the frequency range you have specified in the dialog (whole band or UARFCN range) will be included in the scan.1. Setup of Network Scan General Settings Choose “WCDMA” for WCDMA scanning. Each range can be located on any of the supported frequency bands. NT12-7002 ver 1. 2.1.

the center frequency of each detected WCDMA carrier.6. This threshold should be high enough to minimize the false detection rate.TEMS Investigation 14. 166 . 15.2. UARFCNs from all WCDMA frequency bands are listed in the same column. reflecting a trade-off between the desire to detect all networks in operation and the wish to avoid spurious “hits”. yet not so high that cells actually present may go undetected.1 User’s Manual Cell Ec/No threshold Ec/No threshold for cell detection within a detected carrier. One scrambling code (cell) is displayed for each UARFCN. Setting the threshold too low results in a very long search time (e. that is.g. where all cells will be significantly disturbed. The risk of the latter is particularly pronounced in the case of overlapping carriers. RSSI threshold RSSI threshold for detecting carriers. several minutes at –100 dBm). Presentation: Network Search Window The result of the network scan is output in the Network Search window. It lists all UARFCNs found. which should be suitable in most situations. The default setting is –26 dB. The default setting is –94 dBm.

1.Chapter 16. 16. see the Getting Started Manual. section 10. LTE Scanning 16. Please note that for a scanning method to be actually available in TEMS Investigation.1. supported using the various devices as indicated. For more information about connectable devices with LTE scanning capability. What needs doing is covered in the Getting Started Manual.0 167 . LTE Scanning TEMS Investigation supports scanning of LTE carriers with the following kinds of device: • • • • • Andrew scanner DRT scanner PCTel scanner Rohde & Schwarz TSMW scanner Transcom scanner.4. It is possible to run several of these scanning methods concurrently. NT12-7002 ver 1. the device must have been purchased with the relevant option (wherever applicable).1. Certain scanners require special configuration of the device itself as well as the PC to prepare them for use with TEMS Investigation. chapters 12–14. Scanning Methods and Capabilities TEMS Investigation offers these LTE scanning methods.

TEMS Investigation 14.2. RS CINR) CFO Time Offset 16.2 16.1. Setup of LTE Signal Scan: General Always “LTE”.5 16. P-SCH RSSI.3 16.Scan PCTel SeeGull MX PCTel SeeGull EX .1 User’s Manual R&S TSMW Signal scanning Enhanced signal scanning RSSI scanning Spectrum scanning Enhanced power scanning Transcom DRT 16. LTE band to scan. Technology Band 168 Section Ref. PCIG. LTE Signal Scanning The LTE air interface uses OFDM as modulation method on the downlink. Synchronization Channels are used for service detection and synchronization. RSRQ) CINR (SCH CINR. S-SCH RSSI.2.4 16. and Reference Signals (RS’s) are used for channel estimation purposes. SCHRQ) RS (RSRP.2 16. LTE Scanning Capability/ Scanning Device Andrew i. The LTE signal scan provides the following metrics: • • • • • SCH (PCI.

5 dB is indicated as –65. For example. you can optionally record a logfile with scan data on the MMC as well.1 dB increments. Setup of LTE Signal Scan: DRT • Targeted Scan: Select this if you wish to scan a fixed set of cells. Up to 12 EARFCNs can be selected.2. If you are using a DRT scanner with the optional multimedia card (MMC).3. Scan Rate Report Threshold 16. regardless of how this parameter is set. Top N: Select this if you wish to scan the strongest cells. None: Do not log to MMC. the scan data is always recorded in regular TEMS Investigation logfiles (*. Scan Type • Logging Mode When using a DRT scanner purchased with TEMS Investigation.e.2. Set the number of cells the scanner should report under Top N.2.) The MMC must have been formatted and inserted into the scanner before the scanner is powered on. Epss/Io detection threshold (i. (This logging has got nothing to do with TEMS Investigation.trp). –6. Specify the cells under Cell Index List. LTE Scanning Channels EARFCNs to scan within the selected LTE band. Each EARFCN is specified as a number representing the center frequency of the channel. given in 0. • • MMC: Log to MMC. Min: –240 = –24 dB. Max: 0 = 0 dB.Chapter 16. for Primary Synchronization Channel).0 169 . Setup of LTE Signal Scan: Andrew Minimum time for scan in ms. 16. NT12-7002 ver 1.

Max: 0 dB. Here you specify the indices of the cells to scan (up to 16 cells for each EARFCN. This field is editable if you have set Scan Type to “Targeted”. Threshold (in negative dB) for detection of Primary Synchronization Channel. Min: –30 dB. Here you specify how many cells the scanner should report. Calculation of CINR. Measurement of Reference Signal (RSRP. setting the field to N causes the scanner to return the N strongest cells (N  16). The carrier is the desired signal. Min: –30 dB. Threshold (in negative dB) for detection of Secondary Synchronization Channel. Measurement of BCH received power. S-SCH RSSI. and SCHRQ.TEMS Investigation 14. Max: 0 dB. i. and the interference can be either noise or co-channel interference or both. Cell Index List Primary Detection Threshold (dB) Secondary Detection Threshold (dB) Decoding Threshold (dB) Enable SCH Enable BCH RP Enable RS Enable CINR Enable CFO 170 . Measurement of Synchronization Channels: P-SCH RSSI. Carrier to Interference-plusNoise Ratio for SCH and RS. Min: –30 dB.e. RSRQ). Not supported by currently connectable scanners. up to 16 × 12 = 192 cells in total). Measurement of Center Frequency Offset. Max: 50 dB.1 User’s Manual Top N This field is editable if you have set Scan Type to “Top N”. Not supported by currently connectable scanners. CINR threshold for attempting to decode the MIB/ SIB.

Cyclic Prefix Detection Mode Duplexing Detection Mode • • • Enable ECP This should be turned on if the network uses Extended Cyclic Prefixes. • If you choose Auto-select.2. Automatic: Duplexing method used by detected cells is automatically detected. For this to work.211. 15. TDD: Time Division Duplexing assumed. 10. that bandwidth will always be scanned. It is a slower scan mode. table 6. or 20 MHz). Observations Average Detection Mode NT12-7002 ver 1. FDD: Frequency Division Duplexing assumed. the scanner will itself detect the bandwidth in use.0 171 . If you know what the implemented bandwidth is. If you choose a fixed bandwidth (1.4. Robust mode: This mode uses lower detection thresholds and increased averaging to detect lower-level signals. Normal: Normal prefix assumed. 3. Extended: Extended prefix assumed. LTE Scanning Bandwidth The bandwidth to scan. a valid LTE signal with strength greater than the detection thresholds is required.Chapter 16. • • • Automatic: Cyclic prefix used by detected cells is automatically detected. simply select it.3-1 Number of LTE frames over which to average scan measurements.  3GPP 36. • • Fast mode: This mode offers reasonable sensitivity with a fast scan rate. • Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. since otherwise high-level signals may saturate the receiver and cause errors. It should normally be enabled. 5.

The bandwidth must be selected manually. Number of Antenna Ports Cyclic Prefix Sync Signal Measurement Threshold Reference Signal Measurement Threshold 172 . Only Synchronization Signal (SS) measurements above this threshold will be reported. The type of cyclic prefix used in OFDM. The scanner is capable of detecting this automatically (“Auto Detect”).g. 16. e. The number of antenna ports to measure on (multiple ports for MIMO). The RS and SS measurements will be performed only if measured Carrier RSSI is above this threshold. Here you specify how many cells the scanner should report. Setup of LTE Signal Scan: PCTel With PCTel only Top-N scanning is supported. with separate RS symbols per Tx port. setting the field to N causes the scanner to return the N strongest cells.TEMS Investigation 14.4. The scanner is capable of detecting this automatically (“Auto Detect”). Only Reference Signal (RS) measurements above this threshold will be reported.2. “Normal 15 kHz”. If the eNodeB is using MIMO transmission. the scanner can detect each of the different RS’s and is then able to measure each Tx signal separately. Bandwidth Carrier RSSI Threshold Top N The bandwidth to scan. not scanning of a fixed cell list.1 User’s Manual Number of Tx The number of Tx signals to be detected by the scanner.

Subband start index within the measurement bandwidth. which does not populate any special information elements. It populates the MIMO scanning information elements with “Tx1” . multiple concurrent LTE signal scans can be performed. for example on different bands. If a total of more than 12 EARFCNs are scanned. Subband Count – 1. One of: • • • • Wideband Wideband + Subband Wideband + RF Path Wideband + Subband + RF Path The RF Path option means multipath (MIMO) scanning. all subband measurements appear in the plain-text decoded scan reports.. However.1. Equal to Bandwidth/Subband Size.Chapter 16.. The output to information elements remains exactly the same with this setup: All scanned EARFCNs are presented within the information element range “1st” … “12th”. If this option is included. NT12-7002 ver 1. Number of subbands to divide the measurement bandwidth into. The RF Path and Subband options are referred to collectively as “Enhanced signal scanning” in section 16. The Subband option refers to subband scanning.. LTE Scanning Measurement Mode Signal scan measurement mode.0 173 . the subband settings that follow become visible in the property grid. stated as a number of resource blocks. Subband Count With PCTel SeeGull MX scanners.. “Tx4” in their names. only the first 12 selected for scanning are presented. Must be in the range 0 . Subband Size Subband Start Size of subband.

TEMS Investigation 14. which will then give rise to multiple instances of the RS-CINR measurement. Each selected value corresponds to a measurement where the 1080 kHz segment is divided into the specified number of equal-sized sections.1 User’s Manual 16. It is possible to run FDD and TDD signal scan tasks concurrently.5. You can select several values. uplink and downlink transmitters use separate frequency bands.2. The output to information elements remains exactly the same with this setup: All scanned EARFCNs are presented within the information element range “1st” … “12th”. and if TDD. If a total of more than 12 EARFCNs are scanned. If FDD. Specifies the type of LTE signal to assume for RS-CINR measurements. Cyclic Prefix Frame Structure Measurement Rate (Hz) RS-CINR Carrier Sections Average number of 100 ms blocks to measure per second. Seven (7) OFDM symbols (15 kHz) can be transmitted per slot if normal prefix length is used and 6 OFDM symbols per slot if extended prefix length is used. The final output is a single RS-CINR value. RS-CINR Noise Reduction 174 . each dividing the 1080 kHz into a different number of sections. Enables RS-CINR measurement within the innermost 1080 kHz around the center frequency of the LTE channel. Channel frame structure. which is what is presented in TEMS Investigation. RS-CINR being measured for each such section separately. The scanner is capable of detecting this automatically (“Auto Detect”). only the first 12 selected for scanning are presented. Setup of LTE Signal Scan: Rohde & Schwarz TSMW The type of cyclic prefix used in OFDM. a single frequency band is shared between uplink and downlink. A signal matching filter reducing scanner-internal interference will be applied if this parameter is set.

LTE Scanning TDD Frame Configurations Specifies uplink–downlink configurations to try when performing reference signal measurements on TDD channels. S-SCH to P-SCH Ratio Settings Ratio Type Specifies either a list of ratios or a range in which the power ratio between the primary and secondary synchronization channel must reside. Lower limit for ratio between primary and secondary synchronization channel. NT12-7002 ver 1.0 175 . Read-only field indicating the remaining available resources on the processor selected under RF Frontend. Upper limit for ratio between primary and secondary synchronization channel.3. Setup of LTE Signal Scan: Transcom Please note that the Transcom scanner is not capable of scanning more than one band at a time. What cells will appear depends on the selected sorting order (Sort Cells By parameter).2. The measurement tasks are manually distributed on the two built-in front-ends. Lower Ratio Limit (dB) Upper Ratio Limit (dB) Fixed Ratios (dB) RF Front-end Resource Allocation (%) Resource Available (%) 16. Resources allocated on the specified front-end. List of power ratios between the primary and secondary synchronization channels. Cell Coverage Scan: Scan only the EARFCNs selected under Channels. See also section 13.6. LTE Signal Scan Type • • Top Number Full Band Scan: Scan the full band selected under Band.Chapter 16. Number of cells to include in the presentation (up to 32). Front-end (processor) on which to schedule measurement.5.

RP. Use of Reference Signal measurement with Rx1 antenna. 16.2-1. Channel frame structure. Use of Primary Synchronization Signal measurement. Use of Secondary Synchronization Signal measurement. Timing. RQ. or RS. If TDD. Frame Structure Type Subframe Configuration PSS Measurement SSS Measurement RS0 Measurement RS1 Measurement Timeslot Measurement BCH Measurement Co-Channel Detection Measurement Bandwidth Bandwidth to scan. uplink and downlink transmitters use separate frequency bands. Use of Reference Signal measurement with Rx2 antenna. SSS.3. or CINR for one of the signals PSS. If FDD. See Information Elements and Events.211. Presentation of LTE Signal Scan LTE signal scans are presented in a suite of predefined charts and status windows. Use of co-channel detection. section 8. One of RSSI. Use of BCH measurement. Does not exist for FDD. Use of timeslot measurement.2.3.1 User’s Manual Sort Cells By Parameter by which to sort cells in presentation windows. 176 . table 4. a single frequency band is shared between uplink and downlink.7. TDD special subframe configuration:  3GPP 36. “Unsorted” means that the cells will be listed in the order they are scanned.TEMS Investigation 14.

Note: The sorting order of the “Sc Best” elements (see Information Elements and Events.Chapter 16.8. etc. Up to 255 EARFCNs can be scanned.1. a cell with Cell Identity n is always found at argument index n.8. section 3. LTE Scanning 16. EARFCNs to scan within the selected LTE band. Technology Band Channels NT12-7002 ver 1. Customizing the Presentation Sorting of Cells You can sort LTE cells in scanning information elements in a number of different ways. the cell with the next higher Cell Identity appears at argument index 2. Sort by decreasing RSRQ (Es/Io) (default) Sort by increasing RSRQ (Es/Io) Sort by fixed position: Cells are sorted by Cell Identity and are always assigned the same argument indices.3) is fixed and is not affected by the General window settings. RSSI Scanning Setup of RSSI Scan: General Always “LTE”. LTE band to scan.2.3. Double-click the item “LTE”.2. the cell with the lowest Cell Identity appears at argument index 1. that is.0 177 . A dialog appears with these sorting options: • 16.1. 16. Each EARFCN is specified as a number representing the center frequency of the channel. The sorting order is set in the General window. 16.3. Sort by Cell Identity: Cells are sorted by Cell Identity. • • • • • Open the General window from the Navigator.

Spectrum Scanning A spectrum scan shows downlink signal strength as a function of frequency.3.3. 16. 16.3.1.4.2. select a bandwidth from the list. Bandwidth Remaining Measurement Points 16. Setup of RSSI Scan: Transcom • • Full Band Scan: Scan the whole LTE band selected under Band. section 8. Bandwidth to scan.3. See section 13.1. Presentation of RSSI Scan RSSI scans are presented in a suite of predefined charts.2. RSSI Scan Type Measured Bandwidth Bandwidth to scan.TEMS Investigation 14.3.4. fixed at 100 kHz. Technology 178 .5. Setup of RSSI Scan: DRT See section 16.3. Channel Scan: Scan only the EARFCNs selected under Channels. Setup of Spectrum Scan: General Always “LTE”. Logging Mode Bandwidth 16.3.5. select a bandwidth from the list.4. Setup of RSSI Scan: PCTel Bandwidth to scan.3. See Information Elements and Events.1 User’s Manual 16. 16.

Low end of the frequency range to be swept by the scan. Number of Sweeps NT12-7002 ver 1.1. however.4. Currently. 16. Setup of Spectrum Scan: Andrew Minimum time for scan in ms. Setup of Spectrum Scan: DRT The DRT-specific settings are the same as for WiMAX. Note.4. Setup of Spectrum Scan: Transcom The number of sweeps on which to base the presented average RSSI. Interval between successive scan samples in kHz. the only value supported is 1. the chart.0 179 .4.3. Setup of Spectrum Scan: PCTel The PCTel-specific settings are the same as for WCDMA. 16. Scan Rate 16. on the other hand. can of course only distinguish the samples as far as the screen resolution permits. it will come into play only if you are using the LTE scanner to search for WiMAX presence.5. 16. Given in MHz. Given in MHz. LTE Scanning Band Start Frequency Stop Frequency Resolution Bandwidth Select the LTE frequency band to scan. In the presentation window. the legend pane will list all samples. High end of the frequency range to be swept by the scan.2. that is. see section 19.Chapter 16.5.4.4. that the Triggered Scan option is still associated with WiMAX frames. See section 15.5.

16. Given in units of 50 μs.6.5. The scan will start on the nearest Timing Period Mark with the Timing Period Mark Offset specified. 16.1 User’s Manual 16.2. Technology Band Channel 16. center. EARFCN to scan within the selected LTE band. or maximum frequency of the band to be scanned. Time offset in units of 50 μs. section 8. Setup of Enhanced Power Scan: General Always “LTE”.3.5.4. LTE band to scan. Max: 20000. the enhanced power scan is a higherperformance scan that provides selective power measurements in the time and frequency domains. 180 . Setup of Enhanced Power Scan Bandwidth to scan. Must be less than or equal to Timing Period Mark.TEMS Investigation 14. Enhanced Power Scanning Compared to the spectrum scan. One of: CW: 100 kHz Normal: 1.4 MHz Wide Type 2: 3 MHz Wide Type 3: 5 MHz Wide Type 4: 10 MHz Wide Type 5: 15 MHz Wide Type 6: 20 MHz Bandwidth Time Period Reference Timing Period Mark Timing Period Mark Offset Specifies whether the EARFCN given under Channel is the minimum.3.5.1. Spectrum Scan Presentation Spectrum scans are presented in a predefined bar chart. See Information Elements and Events.

LTE Scanning Measurement Window Measurement window size in units of 50 μs.5.5 kHz.3.1. NT12-7002 ver 1. then the number of bins must be odd.Chapter 16...3. 16. The number of measurements to make within the specified band. or else set to zero which means that the choice of window size is made by the scanner for optimal measurement performance. If Time Period Reference is set to Center. section 8.5 kHz. 8000. Presentation of Enhanced Power Scan Enhanced power scans are presented in a predefined bar chart. Valid range: 2 . See section 13. Number of Bins Resolution Bandwidth Frequency Step Size Remaining Measurement Points Resolution bandwidth in units of 2. Must be larger than 100. See Information Elements and Events.5. Frequency step size in units of 2.3.0 181 .

1. For more information. which is indispensable for the TD (Time Division) component of the TD-SCDMA technology.TEMS Investigation 14. TD-SCDMA Scanning TEMS Investigation supports scanning of TD-SCDMA UARFCNs with PCTel scanners. TD-SCDMA UARFCNs to scan within the selected band.4. 17. you need to set the following: Technology Band Channels Always “TD-SCDMA” for TD-SCDMA scanning.3): Top N RSSI scanning (section 17.1 User’s Manual 17. Each UARFCN is specified as a number representing the center frequency of the channel. section 10. Up to 12 UARFCNs can be selected for pilot scanning.1. • • Scanning Methods Pilot scanning (section 17. see the Getting Started Manual. This is because a GPS signal is needed for time synchronization. As for other cellular technologies. and up to 255 UARFCNs for RSSI scanning. TD-SCDMA band or bands to scan.2. 182 . General Scan Settings Regardless of scanning method. TEMS Investigation can make use of GPS data from the scanner’s internal GPS.4) 17. Note: You must have GPS coverage to obtain TD-SCDMA scan data.2.

different parts of the TD-SCDMA frame are measured. which is located just before the first switching point in the Guard Period (GP) and after Timeslot 0.3. Midamble Top N Pilot Scanning This mode measures the Primary Common Control Physical Channel (P-CCPCH). the UE acquires the timing of the DwPTS by correlating with the SYNC-DL code transmitted in the DwPTS. enter the value N here (N  32). 17. The midamble is used as a training sequence for channel estimation. table 6. The scanner automatically finds the strongest CPIs. NT12-7002 ver 1. During the cell search procedure. The switching points are used to manage the transition between uplink and downlink (since TD-SCDMA utilizes TDD to separate uplink and downlink). section 7.223-840.0 183 . which is transmitted in Timeslot 0 (TS0).1.3. as explained further below. TD-SCDMA Scanning 17. To this end it scans the TS0 midamble (144 chips). SyncDL Top N Pilot Scanning This mode measures the Downlink Pilot Timeslot (DwPTS). The value N is determined by the Number of Pilots parameter.3. • • Pilot Scanning TD-SCDMA pilot scanning can be done in two different modes: Midamble Top N mode Sync DL Top N mode Depending on the mode. power measurements. and synchronization. The DwPTS is used for downlink synchronization. Number of Pilots To scan the N strongest CPIs. The mapping between Cell Parameter Identity (CPI) and the Basic Midamble Code used is given in  3GPP 25. Type of Scanning Setup of Pilot Scan • Scan strongest: The N strongest CPIs will be reported from the chosen UARFCNs.Chapter 17. located between the two data sections.

2.4.3.3.5.3. section 8. Ec/Io will not be reported. Double-click the item “TD-SCDMA”. so that a cell with CPI n is always found at argument index n + 1.3. See Information Elements and Events. Sort by decreasing Midamble Ec/Io (default) Sort by increasing Midamble Ec/Io Sort by fixed position: To each cell is assigned the argument that corresponds to its CPI. Presentation of Pilot Scan Pilot scans are presented in a suite of predefined charts and status windows.1 User’s Manual PN Threshold Remaining Measurement Points Measurement Mode If the Ec/Io value is below the PN threshold. Select “Midamble Top N” or “SyncDL Top N”. See section 13.2. so that the cell with the lowest CPI appears at argument index 1. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events. • • • • • Open the General window from the Navigator.1. etc.4) is fixed and is not affected by the General window settings. 17. A dialog appears with these sorting options: • 184 .1.TEMS Investigation 14. 17. Sort by Cell Parameter Id: Cells are sorted in order of ascending CPI. the cell with the next higher CPI appears at argument index 2. The modes are described in the introduction of section 17. Sorting of Cells You can sort TD-SCDMA cells in scanning information elements in a number of different ways. section 3. The sorting order is set in the General window.

Scanners with both TD-SCDMA and GSM capability can do an RSSI scan on either of these technologies. See Information Elements and Events.2. NT12-7002 ver 1.4.4.0 185 . Setup of RSSI Scan What UARFCNs to scan is set in the General settings. section 8.1. You make the selection under General settings  Technology. Bandwidth Remaining Measurement Points Bandwidth to scan: either “Normal” (wideband) or “CW” (narrowband).3. TD-SCDMA Scanning 17. RSSI Scanning The RSSI scan returns narrowband or wideband channel aggregate power. The GSM RSSI scan is configured in the usual manner as described in section 14.2.Chapter 17.2. 17. 17. see section 17. See section 13.1. Presentation of RSSI Scan RSSI scans are presented in a suite of predefined charts.4.5.4.

3 18. IS-95) RF channels with Andrew and PCTel scanners.3. Follow UE option not supported. See also the Getting Started Manual.1. the device must have been purchased with the relevant option (wherever applicable).1. section 10. Scanning Methods TEMS Investigation offers these CDMA scanning methods. supported using the various devices as indicated. . PCTel MX CDMA Scanning Capability/ Scanning Device 1 18.5 18. Andrew i. 18.4.TEMS Investigation 14.Scan PCTel LX/EX Pilot scanning RSSI scanning Narrowband interference scanning Spectrum analysis 1. CDMA Scanning TEMS Investigation supports scanning of CDMA (IS-2000.Scan scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual.4 18.6 186 Section Ref. Please note that for a scanning method to be actually available in TEMS Investigation. How to configure the Andrew i. IS-856. chapter 13.1 User’s Manual 18.

Setup of Pilot Scan: Andrew Minimum time for scan in ms. Scan Rate Report Threshold Number of Top N PN Increment Correlation Length NT12-7002 ver 1. Max: 32.2. Pilot Scanning This method scans pilots.Chapter 18. CDMA Scanning 18. Max: 16. Min: 512. scrambled with cell-specific PN sequence offsets.1.3. CDMA RF channels to scan within the selected band. The PN increment. 18. Min: –24. EV-DO: Scan correlation length in slots. Must be divisible by 128. Up to 12 RF channels can be selected.3. CDMA: Scan correlation length in chips. Max: 2048. 18.3. Max: 0. Entering the number N means scan the N strongest pilots. General Scan Settings The following settings are common to all or most of the scanning methods: Technology One of: • • • Band Channels CDMA One (IS-95) CDMA2000 EV-DO CDMA band or bands to scan.0 187 .2. Min: 1. Each channel is specified as a number representing the center frequency of the channel. Min: 1. Ec/Io detection threshold in dB. Compare the discussion of the corresponding parameters in section 18.

i. common to all selected RF channels. General Settings (Not Technology-dependent) Type of Scanning The set of pilots (PNs) to scan on each RF channel is composed in one of the following ways: • Scan selected: User-defined. one PN scan on a CDMA2000 frequency and one on an EV-DO frequency. By raising the threshold you reduce the influence of random noise correlations. The setting –20 dB is recommended. no restriction on number of pilots). up to N = 32) on each RF channel.1 User’s Manual 18. • Selected Numbers Number of Pilots This field is visible if Type of Scanning is set to “Scan selected”. If a total of more than 12 frequencies are scanned. Entering the number N means scan the N strongest pilots. Scan strongest: The strongest pilots (“Top N”. The output to information elements remains exactly the same with this setup: All scanned frequencies. Min: 1. or the 32 strongest pilots on the RF channel currently used by a CDMA phone that is also activated in the application. static set of pilots (up to 512. The latter option is activated by setting “Follow UE” to Yes. Here you pick the pilots you want to scan. This field is visible if Type of Scanning is set to “Scan strongest”. the scanner automatically finds the strongest pilots.3. PN Threshold 188 . only the first 12 selected for scanning are presented. the Delay Spread values will be affected by random noise more than may be desired. are presented within the information element range “1st” … “12th”. Max: 32. regardless of technology. If the PN threshold is set too low.2. Setup of Pilot Scan: PCTel With PCTel SeeGull MX and EX scanners. In either case. multiple concurrent PN scans can be performed: for example. This is a signal code power threshold (in dB) used for the Delay Spread measurements.e. and you will thus be able to discern multipath and fading effects more accurately.TEMS Investigation 14.

6. Wide (128 chips). or Wider (256 chips). 3. are applicable only in “Scan selected” mode. Start Pilot Pilot Increment Max Cell Radius The index of the first PN allocated. Search Window Size Normal (64 chips). The maximum pilot window length supported by the scanning receiver is 64. Selection of Measurements to Perform On the rows that follow you specify whether to measure each of the following (at least one item must be set to Yes): Ec/Io The peak pilot Ec/Io value. The maximum radius within which to detect pilots. This is also the default and recommended setting.0 189 .. CDMA Scanning Remaining Measurement Points See section 13. of the time window in which the pilot is searched. only the PNs 0. Settings Specific to CDMA One (IS-95) and CDMA2000 (IS-2000) Use Pilot Increment This refers to the inter-sector pilot PN increment used by the access network in assigning PN offsets to sectors.. will appear in the list. This parameter. NT12-7002 ver 1. The PN increment. . along with Start Pilot and Pilot Increment.5.1.Chapter 18. Settings Specific to EV-DO (IS-856) Pilot Window Length This parameter indicates the length. in chips. TEMS Investigation will filter the list of selectable PNs: for example. if Start Pilot = 0 and Pilot Increment = 3. If a pilot increment is used.

This measurement does not appear as an information element. These are two algorithms with different priorities. High Dynamic puts the emphasis on accuracy. it is only found in scanner reports.1 The number of chips between the first and last pilot Ec/Io peak above the PN threshold. Each reported sample is typically based on a 10 ms measurement. 190 . High Speed is faster and accordingly less accurate. Remaining Options Measurement Mode (EX only) There are two choices. 1. Each sample reported by the scanner is typically based on a measurement 20 ms in length.1 User’s Manual Pilot Delay Aggregate Ec/Io Delay Spread The number of chips between the expected arrival time and the actual arrival time of the signal. The sum of all peak pilot Ec/Io values above the PN threshold.TEMS Investigation 14. High Speed and High Dynamic.

and 3072 for IS-856. CDMA Scanning Timing Mode Here you select by what method the scanner should synchronize to the base station’s transmissions. • • • GPS Only: The scanner will rely exclusively on its internal GPS for timing. Pilot synchronization allows the scanner to operate in indoor environments where GPS coverage is lacking. Pilot Sync Only: The scanner will rely exclusively on the Pilot and Sync channels for timing.Chapter 18. NT12-7002 ver 1. When the phone switches to a different RF channel. Without the Sync Channel Timing option. The band. This setting is enabled only if the scanner has been purchased with the Sync Channel Timing option. Integration (Chips) This is the number of chips over which each signal energy value is integrated. not for IS-856. Follow UE. Selected UE If this is set to On. Setting this parameter high improves the accuracy and reliability of the output but also slows the scan down. GPS Preferred: The scanner will use its internal GPS for timing whenever possible and resort to the Pilot and Sync channels in other cases. a further field “Selected UE” appears where you select which CDMA phone the scanner should follow. If you choose this option. protocol. all other controls in the dialog are disabled. the scanner follows along automatically. the scanner can only use its GPS for timing.0 191 . The default and recommended value is 2048 for IS-2000 and IS-95. and RF channel information is taken from the phone. The Timing mode setting is applicable for IS-95 and IS-2000 only. The scan will then cover the 32 strongest pilots on the RF channel that the selected phone is currently using.

Presentation: Strongest Scanned PN Bar Chart This bar chart shows the strongest pilots scanned.3. Sort by decreasing Ec/Io (default). The sorting order is set in the General window. etc. the pilot with the lowest index appears at argument index 1. 18. the pilot with the next higher index appears at argument index 2.2) is fixed and is not affected by the General window settings. whereas for the “Top N” scan the number N is only marginally important (since all pilots have to be searched regardless of N). Sort by fixed position: Pilot PNs are sorted by index and are always assigned the same argument indices.TEMS Investigation 14.5. that is. Pilots are sorted by ascending PN offset. 18. Double-click the item “CDMA”. regardless of RF channel.3. Presentation: “PN Scan” Bar Charts The PN Scan bar charts present pilot scan data. • • • • • Open the General window from the Navigator. pilot PN n is always found at argument index n + 1.3.5.4. 18.1 User’s Manual 18.3. Sort by increasing Ec/Io. section 3.1.3. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events. One predefined bar chart is provided for each RF channel scanned. A dialog appears with these sorting options: • 192 . Customizing the Presentation Sorting of Pilots You can sort pilots in scanning information elements in a number of different ways. Each bar chart by default presents peak Ec/Io for each pilot found. The updating rate is chiefly dependent on the number of live signals encountered in the network. For a manually selected set of pilots. Sort by Pilot PN: Pilot PNs are sorted by index. the updating rate is also greatly affected by the size of this set.

Chapter 18.. n + 13]. RF channels [n – 13 . NT12-7002 ver 1. If you choose this option. n + 26] if 79  n  275. all other controls in the dialog are disabled.4. etc.4. Remaining Measurement Points Follow UE See section 13.2288 MHz. For the PCS (1900) band. 18... RSSI Scanning Setup of RSSI Scan Select Normal or Continuous Wave (“CW”).0 193 . protocol and RF channel information are taken from the phone. For the cellular (800) band. bandwidth 1. 1. RF channels [n – 26 .. This setting applies to all channels you select for scanning.. • • Normal: CDMA band. the measurements are extracted to the same information elements (Scanned RSSI. the scanner follows along automatically. Choose Yes to scan the RF channel that the CDMA phone in the combo box is currently using (plus a number of adjacent RF channels). n + 33]. Bandwidth Regardless of the choice made here.2. on the 450 MHz band. This option is not available for EV-DO.1.. on the 1900 MHz band.. n + 21]. in the “CDMA” category). Presentation: RSSI Scan Bar Chart This bar chart displays RSSI for each RF channel scanned. the bandwidth is 50 kHz.1 When the phone switches to a different RF channel. the bandwidth is 30 kHz. CDMA Scanning 18.4.. otherwise [n – 33 .1. The band. Specifically (n = phone’s RF channel number): on the 800 MHz band. 18.5. RF channels [n – 21 . CW: “Condensed” or CW band.

Context Settings See section 13. This is a threshold governing how strong an RF channel must be in order to be regarded as an interferer.2. identifying other sufficiently strong RF channels as interferers.3. For the cellular (800) band the scanned bandwidth is 30 kHz.1. 18. Remaining Measurement Points 18. 18. The narrowband interference scan has lower resolution than the spectrum analysis scan (see section 18.1.5.5. 18.1 User’s Manual 18.TEMS Investigation 14.1.1. 18. As regards the rest. and for the PCS (1900) band it is 50 kHz. an in-band RF channel is considered to be an interferer if its strength exceeds the average in-band RSSI by an amount at least equal to Interference Offset.5.5.2.5.1. you can proceed to perform a spectrum analysis in the relevant frequency range. enter the Interference Offset in dB. Specifically.6) but is considerably faster.5.2.1. you select a single RF channel around which to scan. Presentation: Narrowband Interference Scan Bar Chart The results from this scanning method are presented in the CDMA Narrowband Interference Scan Bar Chart: 194 . Once you have done a narrowband interference scan to identify interferers. see section 18. Narrowband Interference Scanning In this mode the scanner scans a narrow band centered around a specific RF channel. In the dialog that appears. Setup of Narrowband Interference Scan General Settings Under Channels. thereby obtaining an even clearer view of the problematic signals.5. • • Interference Offset Open the General window and double-click the CDMA item.

0 195 . Setup of Spectrum Analysis Scan General Settings Choose the relevant CDMA technology.3.1). Technology Band NT12-7002 ver 1. 18. Green: The RF channel is not an interferer according to the Interference Offset criterion. CDMA Scanning Each bar in this chart represents an RF channel. 18. See Information Elements and Events.6. 18. An event “Narrowband Interference” is reported when an in-band interferer is detected.6.6. section 7. This chart uses a special.Chapter 18. Spectrum Analysis This scanning method shows downlink signal strength as a function of frequency.1. predefined color coding: • • Yellow: The RF channel is an interferer according to the Interference Offset threshold criterion entered (see section 18.5. CDMA frequency band to scan.1.1.

can of course only distinguish the samples as far as the screen resolution permits.1. See section 15. the legend pane will list all samples.2. Given in MHz.6. High end of the frequency range to be swept by the scan. the highest selectable resolution being 5 kHz. See section 16.4. In the presentation window. Presentation of Spectrum Analysis Scan Spectrum scans are presented in a predefined bar chart.TEMS Investigation 14. the chart. 196 . 18. The PCTel-specific settings are the same as for WCDMA.1.5. section 8.5. 18.2. See Information Elements and Events. Given in MHz.1 User’s Manual Start Frequency Stop Frequency Resolution Bandwidth Low end of the frequency range to be swept by the scan. Interval between successive scan samples in kHz.6.3. on the other hand.2. • • Context Settings The Andrew-specific settings are the same as for LTE.

1. chapter 12. you need to set the following: Band WiMAX band to scan: one of the bands (WiMAX RF Profiles) supported by the scanner. Always “WiMAX” at present.0 197 . see the Getting Started Manual. Channels Technology NT12-7002 ver 1. 19. and the associated OFDMA bandwidth.1. WiMAX Scanning TEMS Investigation has the ability to scan WiMAX carriers with a DRT scanner. WiMAX Scanning 19.1.4. Regarding band support. How to configure the DRT scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual. section 10.2. Each channel is specified as a number representing the center frequency of the channel. • • • Scanning Methods WiMAX scanning methods are as follows: WiMAX preamble scan RSSI scan Spectrum analysis 19. see section 19.Chapter 19. WiMAX channels to scan within the selected band. Up to 1500 channels can be selected. For more information. General Scan Settings Regardless of scanning method.4.

3. Up to 100 preambles can be tracked simultaneously.TEMS Investigation 14. The preamble is used for synchronization and channel estimation purposes. • • MMC: Log to MMC. Preamble Scanning The WiMAX air interface uses OFDM as modulation method. Set the number of preambles to report under Top N. 198 . Calculation of CINR. Enable Preamble Power Enable Preamble CINR Calculation of preamble power. the scan data is always recorded in regular TEMS Investigation logfiles (*.1. The carrier is the desired signal. Carrier to Interference-plusNoise Ratio. Top N: Select this if you wish to scan the strongest preambles. Specify the preambles under Preamble Index List. and the interference can be either noise or co-channel interference or both. WiMAX RF Profile.e. each subframe is preceded by a preamble.) The MMC must have been formatted and inserted into the scanner before the scanner is powered on. you can optionally record a logfile with scan data on the MMC as well. regardless of how this parameter is set. currently either 5 or 10 MHz). Scan Type • Logging Mode When using a DRT scanner purchased with TEMS Investigation. If you are using a DRT scanner with the optional multimedia card (MMC).1 User’s Manual 19. None: Do not log to MMC. Within an OFDM frame. 19. The bandwidth scanned during preamble scanning is that of the selected band (i.trp). (This logging has got nothing to do with TEMS Investigation.3. Setup of Preamble Scan • Targeted: Select this if you wish to scan a fixed set of preambles.

Measurement of downlink MAP pilot CINR. NT12-7002 ver 1. Measurement of downlink MAP pilot power. cluster size N = 1 will be used for CINR measurement. Measurement of channel response in time domain. CINR will be measured over all segments. cluster size N = 3 will be used for CINR measurement. WiMAX Scanning Enable CFO Enable Delay Spread Enable Absolute Delay Enable DL-MAP Pilot CINR Enable DL-MAP Pilot Power Enable DL-MAP Data Power Use N=3 for CINR Measurements Measurement of Carrier Frequency Offset. Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. Robust mode. One of Fast mode. CINR will be measured for each segment. since otherwise high level signals may saturate the receiver and cause errors. or Rogue mode. If set to True. Measurement of downlink MAP data power. Measurement of delay relative to GPS. It should normally be enabled. that is. that is. Measurement Mode Enable Channel Response: Time Domain Enable Channel Response: Frequency Domain Measurement of channel response in frequency domain. Measurement of multipath delay spread.Chapter 19.0 199 . If set to False.

Preamble Index List Detect Threshold Decode Threshold Enable Statistical Information Number of Samples for Stats Enable Frame Prefix Decoding Enable Downlink Map Decoding Enable Uplink Map Decoding Enable DCD Decoding 200 . Decoding of uplink MAP messages.TEMS Investigation 14. Here you specify the indices of the preambles to scan. section 3.6).1 User’s Manual Top N This field is editable if you have set Scan Type to “Top N”. Compare Enable Downlink Map Decoding. These include the burst profile for each user. the actual number of samples used may be smaller. Decoding of downlink MAP messages. Here you specify how many preambles the scanner should report. The Frame Prefix specifies the modulation type and number of symbols associated with one or several downlink bursts that follow the FCH. This must be set on for measurement statistics (mean and standard deviation for RSSI. which defines the modulation and coding scheme used on the downlink. The number of samples on which to base each computation of measurement statistics. as reported in the “Samples Taken” information elements (see Information Elements and Events. However. This field is editable if you have set Scan Type to “Targeted”. Threshold (in negative dB) below which no preamble detection is reported. Threshold (in dB) below which data is not decoded. Decoding of Downlink Channel Descriptor (a message containing information about downlink characteristics). setting the field to N causes the scanner to return the N strongest preambles. CINR) to be computed. Decoding of downlink Frame Prefix (DLFP).

Presentation WiMAX scans are presented in a suite of predefined charts and status windows. Logging Mode Average Time Triggered Scan Offset Time (µs) Block Time (µs) Measurement Points 19. Bandwidth to scan. Length of time for block averaging in μs. The number of measurement points left to allocate.5. Setup of Spectrum Analysis Scan See section 19.1. Logging Mode Bandwidth 19.3. 19.3. select a bandwidth from the list.6. WiMAX Scanning Enable UCD Decoding Decoding of Uplink Channel Descriptor (a message containing information about uplink characteristics). Setting this to Yes means that the scanning will be triggered at the start of a new WiMAX frame. Spectrum Analysis A spectrum scan shows downlink signal strength as a function of frequency. Valid for triggered scan only.5. Offset from start of frame in μs.1. NT12-7002 ver 1. 19. 19. Length of time for total averaging in μs. section 8.1.4.6.Chapter 19. See Information Elements and Events.4.0 201 . RSSI Scanning Setup of RSSI Scan See section 19. Valid for triggered scan only.

1 User’s Manual The purpose of having views that are grouped by preamble index. or find crossed feeders. is to provide information about all the sectors of a site. is to provide information that is helpful in determining coverage. rather than by RSSI or CINR. best server.TEMS Investigation 14. 202 . The purpose of having views sorted by RSSI or CINR. and handover targets for neighbor lists. without any grouping by segment. This can help identify improperly aimed antennas.

trp). HTTP. MMS. However. • Special activities are available • • • 20.1. it is not possible to do data service testing with any other devices at the same time. 1. SMS. Which of these are testable for particular cellular technologies is tabulated in section 20. Ping.1 Scanning can be scripted for all devices indicated in the introduction of chapter 13.3. Capabilities of Devices Apart from technology-related restrictions as noted in section 20. Service Control 20. Data service testing encompasses the following services and protocols: e-mail. Service Control 20.0 203 . Introduction to Service Control The Service Control tool is used to control the actions of devices that you activate in the application. for recording data collected while executing the scripts. UDP. and WAP.Chapter 20. NT12-7002 ver 1.2.1. • • Circuit-switched voice and video calls are supported. See the Getting Started Manual. phone devices sold with TEMS Investigation 14. for applying various control functions to devices. section 10. multiple data connections can be maintained concurrently. The recordings will be regular logfiles (extension . FTP. TCP. VoIP.1 (listed in the Getting Started Manual. With multiple devices activated. chapter 11 regarding preconfiguration of Fixed Wireless Terminals.1) normally support all types of script activities. video streaming. if an Ericsson Fixed Wireless Terminal is activated.2. such as RAT lock and band lock for AT commands.

3. there are no technology-related restrictions. The Service Control Designer The Service Control Designer window is where you compose service control workflows (scripts): 204 CDMA UMTS Service/Technology LTE . and Ping. 20.TEMS Investigation 14. it should be noted that data service testing with Ericsson Fixed Wireless Terminals is limited to FTP.1 User’s Manual Regarding other connectable devices.4. What scanning devices can have their actions scripted is stated in chapter 13 (introduction). 20. HTTP. Supported Services by Cellular Technology TD-SCDMA CS voice calls CS video calls E-mail FTP HTTP MMS Ping SMS UDP Video streaming VoIP WAP For scanning.

First comes a hands-on tutorial on how to build and run scripts. use the buttons at the top to toggle between the two display modes. for controlling devices. In the Properties and Configuration Sets panes. The rest of this chapter is organized as follows. The Properties pane contains properties of the activity that you are currently working with (the one currently selected in the Workflow pane).16–20. Then follows a reference part cataloging all script activity types with their properties and associated configuration sets (sections 20. with numerous screenshots and examples (sections 20. items can either be grouped into categories or be listed in alphabetical order.18).15). Finally some additional features of the Service NT12-7002 ver 1. and for execution flow control. In the Configuration Sets pane you define various entities that can be reused in any script. for example all the details of accessing a particular FTP server. At the bottom of each pane is a box showing an explanation for the item currently selected.Chapter 20.0 205 . Service Control Properties pane Workflow pane Activity pane Configuration Sets pane • • • • The Activity pane is a palette holding all script building blocks: for running services. The Workflow pane is the area where you assemble your script graphically in the form of a flowchart.5–20.

TEMS Investigation 14. 20.1 User’s Manual Control tool are covered.19–20. Video calls are handled in similar fashion. (The cross-reference here. • Add a voice dial activity to the script. For purposes of illustration we will build a very simple script that dials single voice calls. This means that the activity is not yet properly configured. Basics of Creating Scripts (with Voice) This section covers the fundamentals of creating a complete and valid script that is ready to be run. To this end. expand the Voice node in the Activity pane and drag the Dial item to the empty workflow.16. just like others that follow. A similar exclamation mark in the Properties pane indicates the property that is undefined: “Configuration”. 206 . points to the reference section 20.20).) 1 2 • The Dial box is tagged by an exclamation mark.5. and some reference material is given (sections 20.

The call will be established and then immediately hung up (since the script has run to NT12-7002 ver 1. Finish by clicking the Apply button. as will be seen later. This is done in the Configuration Sets pane.) Give the configuration a suitable name.Chapter 20. such as one identifying the subscription having this number. (In other cases it can be more complex. For a voice dial. When just dialing a call like this.0 207 . the configuration consists simply of the phone number to call. for which you will probably want to substitute something more specific. it will not have a duration. Service Control • What we need to do is to define a configuration set for the Dial activity. The example below uses a neutral designation “Voice Call Recipient 1”. • • • The Properties and Workflow panes are now updated with the configuration data.

add a Hang Up activity after the wait. 1 2 • Set the duration of the wait in the Properties pane: • Finally. • Drag the Wait activity to a position just below the voice dial box. use the Wait activity: compare section 20.5.TEMS Investigation 14. 208 .1 User’s Manual completion). The graphical user interface helps you position the Wait box correctly by means of guiding symbols and text. To give duration to a call.10.

3.Chapter 20. Setting Up a Network Connection This section shows how to set up a network connection. See section 20. you need to specify whether to use RAS or NDIS.1 for full details. NT12-7002 ver 1.16. turn to section 20.4 for guidance.6. In particular.10. only it contains many more parameters. • Again you will be notified that a matching configuration is missing: • A configuration for a data connection is created in the same way as one for voice. Service Control If you want the script to control both caller and receiver. which is a necessary preparation for running data services. • Expand the IP node in the Activity pane and add a Network Connect activity to the script. 20.0 209 .

Later on.6. so you do not need to associate it with a configuration set. We will use the data connection configuration created in section 20.1 User’s Manual • Once you have the configuration down. 210 . point to it from the Configuration field in the activity properties. if you have multiple network connect configurations defined. Associate it with the “W995_Dialup_1” configuration set created in section 20. Then add a Network Disconnect activity at the bottom of the workflow. 20. Setting Up a Data Service Activity In this section. • • First add a Network Connect activity. This activity needs no particular configuration.TEMS Investigation 14. The disconnect operation will take down the network connection.6. we will set up an FTP download as an example of a data service activity.7. you can pick and choose among them.

0 211 . NT12-7002 ver 1. Service Control 1 2 • The FTP session itself is handled by the FTP Download activity.Chapter 20. Insert an activity of this type between network connect and disconnect: • For the FTP Download activity. you need to create a configuration set representing the FTP server and how to access it. Again this is done in similar fashion as for previously created configurations.

1 User’s Manual We will download the file My_10_MB_File.7. reference it from the FTP Download activity in the same manner as before. 20.7.8. logging in as user “TEMS_User”. in that order (they are found in the IP category).6 and 20.dat from the FTP server with address 123. • After completing the definition of the FTP server configuration. This will detach the device from the PS network and then reattach the device.67.TEMS Investigation 14. Stand-alone PS Attach and Detach In this section we will perform explicit PS attach and detach operations in isolation. particularly for the purpose of computing KPIs. 212 . At the start of this workflow.45.89. add a PS Detach and a PS Attach activity. One reason for doing this could be to measure the time taken by these operations. We will reuse the configuration sets and activities from sections 20. • • We begin with the FTP download workflow from section 20.

9. see section 20.) Compare chapter 33. Snippets A snippet is a fixed sequence of activities that is defined as a building block and can be reused as such.0 213 . saving time and effort when creating new scripts.10. Service Control PS detach PS attach See also section 20. NT12-7002 ver 1. Example: The detach-plus-attach procedure in section 20. then enter the File menu and select Save as Snippet. For an example of such a predefined snippet in use. You are prompted to name and describe the snippet. The predefined snippets are also tailored to produce all data required to compute KPIs. You can also save an arbitrary activity sequence as a user-defined snippet: • Select all of the activities by dragging the mouse pointer.9. 20.4. Predefined snippets for all supported services are provided in the Activity pane.8 could be a good candidate for a user-defined snippet.Chapter 20. since it will recur in any script where you want to detach and then reattach to the PS network. (The KPI computation itself is done using TEMS Discovery or TEMS Automatic.

8. Suppose further that you want a convenient means of turning the detach/attach activities on and off.10.1 User’s Manual 20. Expand the Control Flow node and from it drag a Sequence activity to a position immediately above the PS Detach activity: • • Select the PS Detach and PS Attach activities by holding Ctrl and clicking each activity. Workflow Control Structures The Control Flow node in the Activity pane contains a number of logical constructs and timers for controlling the script execution flow. Sequences You can formally define a group of activities in a script as a sequence. You can then encapsulate the PS Detach and PS Attach activities within a sequence. to enable or disable them.TEMS Investigation 14. This is handy if you want to apply some operation to all of these activities – for example. • Suppose your script includes PS detach followed by PS attach as described in section 20. then drag them both (using the PS Detach box as handle) into the sequenceActivity1 box. You can now enable and disable the detach–attach sequence as a whole: 214 . 20.10.1.

Suppose the phone is on a WCDMA network and is instructed to do an FTP download.) After a handover to GSM has occurred. 20. (This is accomplished by imposing a “terminate on event” condition on the activity.12.2. see section 20. For full details on the Sequence activity.e.5. To this end we use an if–else construct in the following manner: • First add a Network Connect activity.16. Service Control Compare section 20.Chapter 20.10. i. the activity should terminate. then we want to abandon the download. If–Else Constructs An if–else construct is used to split the execution flow into several branches based on the outcome of a previous activity. then after the FTP download has completed we want to continue with a video streaming session. we want to proceed with a voice call (which does not require a large bandwidth). and then an FTP Download activity with the Abort property set to On Event and “Handover from UTRAN” selected as event type: • Then add an If–Else activity below the FTP download: NT12-7002 ver 1. Now if the phone is handed over to GSM.5. If on the other hand the phone remains on WCDMA.0 215 . see section 20. so that the throughput is sharply reduced. Here is an example.2.15.

1 for full details on the If–Else activity.16. set Condition Type to Any. While Loops While loops are used to repeat a sequence of activities a predetermined number of times. 216 . as described in the introduction of this subsection.10.2.3. For the right-hand branch (“ifElseBranchActivity2”). set Condition Type to Activity Result. 20. (Not shown in the screenshot below.) – • Add a voice dial activity on the left (to the node “sequenceActivity1”) and a streaming activity on the right (to the node “sequenceActivity2”).7 and is not detailed here. See section 20. This is done just as in sections 20. by default “ftpDownloadActivity1”. so that the right-hand branch will be executed whenever the condition in the left-hand branch is false.5 and 20. Result = Stopped by Event. This always evaluates to true. Operator = Equals.TEMS Investigation 14. See next screenshot.1 User’s Manual – For the left-hand branch (“ifElseBranchActivity1”). and set the associated attributes as follows: Activity = the name of the FTP download activity. • Suppose we want to execute an FTP download five times over.

Chapter 20. (Just as with sequences – compare section 20. Service Control • Begin by dragging a While activity to the start of the workflow. then fill it with the desired contents. set the number of times you want to iterate the while loop. • • Now drag the predefined FTP download snippet into the while loop.0 217 . by entering the value 5. dropping it onto “sequenceActivity1” in the indicated spot (“Drop Activities Here”): • It may be desirable to insert a brief pause after each pass through the while loop. Below. we stipulate that the loop should be run five times in total.10.) In the Properties pane. you first add the empty While construct to the workflow.1 –. You can accomplish this by appending a Wait activity at the end of the FTP snippet: NT12-7002 ver 1.

1. caller and receiver must be put in parallel.10.4. See section 20. a script can also control the activities of multiple devices. where EQ1 calls EQ2: 218 . To create a branching structure for these concurrent tasks.2 for full details on the While activity.1 User’s Manual • Set the duration of the wait in the Properties pane: For example. Parallel Activities All scripts so far have been written for a single device engaged in one activity at a time. the script will perform five FTP downloads in succession with a 10 s idle interval between downloads. if you set Duration to 10 s. Example 1: CS Voice/Video – Caller and Receiver For example. or assign multiple parallel activities to the same device. we use the Parallel activity from the Control Flow category. 20. See the screenshot below.10.16. if one phone is to place a voice or video call to another.2.TEMS Investigation 14. one dialing and the other answering. However. 20.4.

Chapter 20. NT12-7002 ver 1. as detailed in this section.0 219 . Service Control A parallel structure is also recommended for MMS send/receive. 20. Suppose that we want to control three UEs in parallel. This will become an outer loop repeating the various activities that will be included in it. • First add a While activity and set it to run 10 times. one performing downloads over FTP and the other two looping short voice calls. For this purpose we need to build a somewhat more complicated workflow.2. Example 2: Concurrent Activities on Different Devices Next is a slightly more complicated example.4.10.

(The Sequence activity is created automatically. The structure is now expanded with a third branch: 220 . but in this case we do not need it at the topmost level – compare the steps that follow.) Drop a Parallel activity inside the while loop. we need to add one more. To this end.1 User’s Manual • Remove “sequenceActivity1” by selecting it and pressing Delete. • • Since the Parallel construct by default provides only two branches.TEMS Investigation 14. right-click the “parallelActivity1” box and choose Add Branch from the context menu.

After these steps. Add a voice call snippet (a predefined one is found in the Activity pane) to each while loop.Chapter 20. Let us begin with the voice calls: • • • Add while loops to branches 2 and 3 and set each to execute 5 times.0 221 . Service Control It is now time to define the service-related activities. Set the wait time to 10 seconds. To assign the activities to the correct devices. we need to change the equipment (EQ) parameter to EQ2 and EQ3 in branch 2 and branch 3 respectively. branches 2 and 3 of the workflow should have the following structure: NT12-7002 ver 1. This is done in the Properties pane or from the context menu for each activity.

222 . 1. All you need to do here is to add an FTP download snippet to branch 1 and associate it with a functional configuration. define the FTP task for device no. In the screenshot that follows.1 User’s Manual • Next. the voice sequences have been collapsed to clarify the overall structure of the workflow.TEMS Investigation 14.

(No such Waits are present in the above example.0 223 . Insert Wait activities as appropriate to achieve this. See section 20.) NT12-7002 ver 1. Service Control This script will conduct a total of 10 FTP downloads and 2 × 5 × 10 = 100 voice calls.2.Chapter 20. It is better to let the sessions start one at a time. Note: When composing a script for multiple concurrent data service sessions using multiple devices.3 for full details on the Parallel activity.16. it is wise to make sure that these sessions are not all initiated simultaneously. allowing at least a few seconds between successive initiations. which contains only one data service session.

Example 3: Concurrent Activities on the Same Device The Parallel structure can also be used to run multiple activities concurrently on the same device. e-mail. provided that the device supports it.16. All instances of the FTP Download activity use the same configuration set. 224 .4. as exemplified in the following screenshot (branch 1: no Wait. The activities concerned are those for FTP download/ upload. even multiple activities of the same type.3. it is best not to start all of the scans at the exact same time. to prevent file write conflicts. Insert short waits as appropriate to stagger the start times. branch 3: Wait with duration 4 s).10. each activity adds a unique prefix to the target file name (refer to section 20. When assigning multiple scanning activities to the same device.10.9 for details). Compare the similar advice in section 20.4. however. HTTP.TEMS Investigation 14. The script shown below lets one device perform two concurrent FTP downloads.1 User’s Manual 20.2.3. branch 2: Wait with duration 2 s. and Ping.

Scan activity. NT12-7002 ver 1. When following a (voice) Dial. see sections 20. After the wait time has expired.2.9. 20.5.16. and 20.4.5. The Wait activity also comes in useful whenever some tasks need to be cleanly separated in time for one reason or other.7 for full details on this activity. and it temporarily halts the execution of the workflow branch it is located in.. and this construction is the most convenient method of controlling the duration.16.10.1. Video Dial.10..3. See section 20. 20.Chapter 20.2. the execution proceeds to the next activity. the Wait has the apparent effect of giving duration to that activity.0 225 .10. or Start . Wait The Wait activity basically does nothing. Service Control 20. For some usage examples.

– – • If you just want to start the dialing as soon as the script starts. • 226 .6.6.TEMS Investigation 14. 20. put a Wait For with Trigger = Schedule.8 for the fine points.2. • • Create a While loop and set its termination condition to whatever you like. Wait for a particular kind of event to occur. Wait For The Wait For activity can be used to: • • • Wait for a scheduled point in time.10.16.10. A special case is Wait For with periodic events: see section 20. Wait. the call duration has been set to 2 minutes. At the top of the loop. To make the loop execute with the desired frequency. Wait for another activity to finish with a predetermined outcome.10.1.6. This pattern will repeat until the while loop terminates. set Start to Immediately. you can specify that the calls should begin at the turn of the hour (“On the Hour”) or at an arbitrary time (“Time of Day”). See section 20.6. Waiting For a Scheduled Point in Time Suppose we want a device to dial a short voice call once every 10 minutes. Alternatively.1 User’s Manual 20.10. See section 20.3. In the screenshots below.1 below.5.10. The loop will then pause at the Wait For activity each time until 10 minutes have passed since the previous turn. Add activities for the voice call (Dial. This can be accomplished by putting the voice call inside a while loop which also contains a Wait For activity. Hang Up) just as in section 20. continue by setting Repeat to Yes and Repeat Interval to 10 minutes. see the reference section 20. The schedule can be set up in a number of ways. providing a timing mechanism. This is straightforward.2.6.

we want to start a logfile recording to capture what happens over the following one-minute period.2. Then add activities for logfile recording beneath the Wait For: Start Recording followed by a Wait with Duration = 1 min and finally Stop Recording. 20. If a call proceeds normally. In the right-hand branch.10. • NT12-7002 ver 1. insert a While loop repeating voice calls. we do not log any data. but if a call is blocked.6.0 227 . an alternative (“event-driven”) approach to data collection is to wait until something interesting happens and trigger recording only then. In the left-hand branch. Configure the Dial activity to abort if the call is blocked (Abort property set to On Event with “Blocked Call” selected as trigger). Again taking CS voice as a simple use case. suppose that the voice service is tested by dialing one call after another. • • Create a Parallel structure with two branches.Chapter 20. Right: Loop controlled by Wait For with Start = Time of Day. Waiting For a Given Outcome of an Activity Instead of collecting data continuously. Set the Trigger property to Activity Result and stipulate that it should equal “Stopped by Event”. Service Control Left: Loop controlled by Wait For with Start = Immediately. put a Wait For activity at the top monitoring the voice calls.

228 . a script is written containing a while loop. Next. at the start of which a Wait For activity listens for the periodic event. 20. If such an event is generated. signifying that the user is currently camping on an allowed cell. The rest of the loop contains the task to be performed.1 User’s Manual If any call failures are of interest. Recording will then be triggered by any voice call that does not complete normally. We can then construct a user-defined event for the condition and make that event periodic. then set Activity Result to the catch-all value “Failed” instead. and not only blocks. which means that it is generated repeatedly at fixed intervals as long as the condition is true (see section 22. In this case.4. the script proceeds through the rest of the while loop.10.6. etc.3). Wait For with Periodic Events Suppose we want to perform some kind of task whenever a given condition is satisfied. See section 22. One natural application of this construction is to cell whitelists.3. so that the device performs its task once. Then a new whitelist check is done. the Wait For activity waits for a whitelist event.TEMS Investigation 14.

See the image below.1 20. 1.7. Please note in this connection that for the user-defined events to appear in the Events drop-down list. simply drag a new Wait For activity into the script flowchart and use that one instead. If you add the Wait For first and create the userdefined events only later. Service Control Note that user-defined events are prefixed with the string “User Defined:” in the Events drop-down box. NT12-7002 ver 1.9). and it may be preferable if you want to organize your scripts in modular fashion. Run Script The Run Script activity is a reference to another script and consists in executing the whole of that script at the given point in the workflow.10. Left: While loop with Wait For having event as trigger.0 229 . To resolve. Using Run Script can be regarded as an alternative to saving and reusing snippets (see section 20. keeping down the complexity of each individual script. Right: Selection of whitelist events (one for each RAT) as Wait For triggers. the events will not show in the drop-down list for that particular Wait For instance.Chapter 20. they must exist when you add the Wait For activity to the script.

When dragging a selection to a new position in the sequence. You can also edit workflows using the Cut.) The destination of a pasted item depends on what. If you are selecting a number of consecutive activities and wish to preserve their ordering after they are moved or pasted.m.10. One possible application of this activity is to combine it with Wait For to stop a script at a fixed time of day. The activities do not have to be adjacent in the workflow but can be picked arbitrarily. The Wait For should then have Trigger = Schedule and Start = “Time of Day”. cut.1 User’s Manual 20. (Whatever activity you use as handle will end up on top.8. The editing commands work in standard Windows fashion. suppose the script contains a while loop. 20. For example. Terminate The Terminate activity simply kills the whole script immediately and unconditionally. A few points merit special comment: • You can select multiple activities to move. the sequence depicted below might then be inserted in the while loop to stop execution at 3 p. or copy by holding Ctrl and clicking. Copy. is currently selected in the workflow: • • • 230 . use the topmost activity as handle to preserve the ordering of activities. Ctrl-click the activities from top to bottom in the same order as they come in the workflow. The same operations can be performed from the window toolbar or from the context menu that appears when right-clicking a workflow item. if anything. and Paste commands found in the Edit menu of the Service Control Designer window.TEMS Investigation 14.11. Editing Workflows and Script Settings You can move activities around in the workflow by clicking and dragging.

0 231 . Service Control Item(s) Selected in Workflow None One or more arrows. Therefore. it must be noted that the script activities are inevitably more generic in nature than the manual control functions. Regarding editing of text input fields in the Properties and Configuration Sets panes. 20.. The keyboard shortcuts Ctrl + C. 20. retry the activity.Chapter 20. UE Control Functionality A number of control functions accessible from the Navigator (Equipment tab. or Parallel activity 1. use the context menu in the text field. you can choose to skip that activity. note the following: • To copy. whereas the manual band lock function in the Navigator (acting as it does on a specific device of a well-defined make NT12-7002 ver 1. or terminate the entire script (On Failure property).17. You can have an activity aborted after a fixed length of time.2. since when composing a script it is not known what devices the activities will apply to. etc. and paste material in text fields.1) can also be applied in a script in the form of activities. or if a specific event occurs (Abort property). For full details. For the RAT lock and band lock functions. bottom part. While. see section 20. cannot be used for this purpose. • • Activity Properties That Control Execution All activities have some general properties governing their execution: If an activity fails. the Band Lock activity has bands from every supported technology selectable.12. Activities tab: see section 9. Any except the ones mentioned in subsequent table rows.13. no activity One or more activities1 Paste Destination Bottom of workflow Above arrow first selected Below activity first selected Bottom of sequence – (cannot paste) Sequence activity If–Else. cut.

5. How to run only parts of a script is described in section 20. it needs to be validated to ensure that it is syntactically correct and does not assign tasks that your devices do not support. a UE control activity in a script can be executed only if the target device is capable of the operation in question. A script is automatically validated when you start it. 20. If the script passes validation.15.16.13). this may seem trivial.15. 20. You can also explicitly have a script validated in advance: • • Enter the Script menu and choose Validate. See section 20. and when devices are involved in different workflow branches that converge. General Aspects of Script Execution • The devices involved in a script will execute their assigned activities independently of one another. For uncomplicated scripts like our first example in section 20. Running Scripts You can run a script either from the Service Control Monitor or from the Service Control Designer.14 on validation). you will receive a notification “Script validation succeeded”. when building more complex scripts involving multiple devices and control logic.14. 20. However. The script is then ready to be run.1 for full details on the UE control activities.15.1.5. • 232 . See section 20. the validation becomes a non-trivial issue. You will be presented with the results.1 User’s Manual and model) can only lock on the bands supported by the device.TEMS Investigation 14. Validating Scripts Before a script is run. Validation is also crucial for UE control functionality (see section 20. In conclusion. In the latter case.15. You will be notified if this is not the case (see section 20. all branches are synchronized before the execution proceeds past the point of convergence. except when the devices engage in a service where they interact.

3. Monitoring Equipment Status On the Status tab of the Service Control Monitor.15. If it is.tsc).2.1. however. Click the Run Script button to start the script.3. you should wait until the receiving device has received the message before restarting the script. • • 20. one line is printed for each session. Preparations 20. Otherwise. NT12-7002 ver 1. this is not recommended. section 8. the current status for each device is displayed.) When executing a script.2.1. the script will not work properly.15. 20. the keylock function must not be activated in any of the phones.0 233 . See the Getting Started Manual.2. If you stop a script while an SMS or MMS message is being transferred. 20.15. Windows 7/Windows Vista and IPv6 In Windows 7 and Windows Vista.15. it is recommended that you disable IPv6 for all device modems.Chapter 20. Running Scripts from the Service Control Monitor Click the Open Script button and select your script (file extension . Service Control • It is possible in the application to run several scripts at the same time. unpredictable behavior may result. (The script validation does not extend to such usage.1 for further details and instructions. Click the Stop Script button to stop script execution.15. If a device is engaged in multiple concurrent service sessions.

Click the Return to Designer button to return to the Service Control Designer window.TEMS Investigation 14.3). aborted.2. statistics are given on the outcome of each activity type (number of succeeded. Click the Stop Script button to stop script execution. Clicking an underlined number in this table brings up a summary of each activity that has been run.15. 234 . Running Scripts from the Service Control Designer • Enter the Script menu and choose Run.4.1 User’s Manual 20.3. Below is an example (UDP with full duplex tested): 20.15. and failed activities).15. Viewing Statistics on Script Execution On the Summary tab of the Service Control Monitor. The tab holding the usual contents of the window is now hidden and replaced by Status and Summary tabs which are identical with those in the Service Control Monitor (see section 20.

For example.Chapter 20.15. as shown below. Service Control 20. You can easily disable any individual activity by right-clicking it or by changing the Enabled flag in the Properties pane. Suppressing Parts of a Script It may happen that you want to run only certain parts of a script and exclude others.0 235 . An activity that is currently disabled appears dimmed in the workflow pane. suppose we want to skip the initial detach/attach procedure.5. the flowchart looks like this: NT12-7002 ver 1. After disabling the sequence comprising the first two activities.

1. 20. For example.16. Activate Activates the device so that it can be used in TEMS Investigation. 20.TEMS Investigation 14. (Define a configuration for each AT command you want to send.2. do not suppress an activity whose outcome is used to evaluate a subsequent If–Else condition (see section 20.5. 236 . The details are analogous to the manual band lock function on the Navigator’s Equipment tab.1. Not all activities have unique properties.1. This activity has no unique properties.10. • Bands property: Specify band or bands to lock on.3.2).1. just set the Enable property to True again. Control Activities 20. those not covered in section 20.6.15.16.1.16. 20. 20. AT Sends an AT command.3.16. Activities (Reference Section) This section also explains all activity-specific properties found in the Properties pane: that is. see section 9.16. Band Lock Locks the device to a subset of frequency bands. To re-enable a disabled activity.) 20.1 User’s Manual Note: Be sure not to disable an activity that another activity is dependent on. Presentation of Data Service Testing See section 9.1.17. • AT Command property: AT command string.1.

1.16. The choice “No Technology” releases a lock that has been previously applied.6. Stop Recording Concludes the recording of a logfile initiated by a Start Recording activity (see section 20.7) and closes the logfile. device channels cannot be distinguished (for example.1. and Tags properties: These correspond to the identically named metadata fields that you can define when recording a logfile manually. • Filemark property: Filemark text string. By default all EQs are selected. • Equipment property: Here you select which devices to include in the recording. or else manually from the Navigator – see section 8.1. 20. Description. NT12-7002 ver 1. 20.16. Subject. The selection is made at the EQ level. See section 11. A Start Recording activity must be paired with a Stop Recording activity (see section 20.1.1.4.1).1.8) that concludes the recording and closes the logfile.4.1. The following characters are ignored if entered in this field: \ / : * ? ' < > | Directory property: The directory where logfiles produced by the script will be stored.16.16. Prefix property: You can add a descriptive prefix to the default logfile name.1.1.16. Start Recording Starts recording of a logfile.8. see section 11. Deactivate Deactivates the device so that it can no longer be used in TEMS Investigation until you activate it again (using Activate. • • • 20. This activity has no unique properties.1.16.5.16.Chapter 20.0 237 .7. Radio Access Technology Lock Locks the device to a particular radio access technology (RAT). Service Control 20. 20. Filemark Enables automatic filemarks. recording MS but not DC for a particular device). • Technology property: Specify the RAT to lock on.

in a loop that begins with Start Recording and ends with Stop Recording.1 User’s Manual • Recording Activity property: Here you select which Start Recording activity to stop.10. 20. The following attributes are then visible: 238 . Other methods of recording are independent of scripted recording and do not affect a script that is executing. please turn to section 20. 20. however. Each condition (except the catch-all “Any”: see below) is based on the outcome of a previous activity. Each branch of the construct. Notes on Script-controlled Logfile Recording Note that logfiles always record data from all activated devices. insert Wait activities (of duration 15 s) as needed in your script to separate Stop Recording activities from Start Recording activities that will follow immediately in the execution flow. See section 11. identified by its name (e. Control Flow Activities For a hands-on tutorial on how to use these activities.1.9.1. At the top level the If–Else activity does not have any unique properties. insert a Wait at the end.TEMS Investigation 14.2. Evaluation of conditions proceeds from left to right. If–Else This activity splits the workflow into two or more branches.16. not only the devices that participate in the script (i. with a boolean condition attached to each branch. If you want to avoid this. set Condition Type to Activity Result.e.1. For example. “startRecordingActivity1”).2.1. is constituted by an “if–else branch” activity which has the following property: • Condition Type property: To define a non-trivial condition.4.g. The automatic data buffering in TEMS Investigation may result in overlap between logfiles. as explained in section 11. those that have some device-specific activity assigned to them).16. 20.16.

Parallel This activity splits the workflow unconditionally into two or more branches.) For an example of usage. Time: Fixed execution time. see section 20. One of: Succeeded.3.16. Failed.2. provided that the device supports concurrent execution of the services involved (or several sessions using the same service). While This activity constitutes a while loop.2. For an example of usage.10. 20. This activity has no unique properties.3.2. Stopped by Event. 20. Result: The activity result that you want to match.16.2.0 239 . Setting Condition Type to “Any” creates a condition that always evaluates to true. A device can participate in more than one branch. While loops can be nested arbitrarily.2. the while loop does not terminate immediately. Each of the parallel branches is encapsulated within a Sequence activity (see section 20. When this duration expires. • Condition Type property: Count: Fixed number of iterations. This value should always be used as a catch-all condition for the rightmost if–else branch.Chapter 20. the current turn is completed first. Service Control Activity: The activity (identified by its name in the workflow) whose outcome will determine the value of the boolean expression.16.5).10. rather. Operator: Boolean operator: “Equals” or “NotEquals”. (The running time is compared to the limit before a new turn begins. NT12-7002 ver 1. There is no hard limit on the number of branches. see section 20. (The If–Else construct is set up in that way by default. Stopped by Timeout. Stopped by User.) Event: The while loop is terminated when any of the selected events is reported by the selected equipment.

Terminate This activity terminates the entire script immediately. 20.5. and 20. as exemplified in section 20.10. Furthermore. see section 20.16.10. 20. allowing it to be treated as such. For an example of usage.7. It has no unique properties.16. 240 .4. See also section 20.8. 20. Sequence This control structure formally defines a sequence of activities as a unit.5. (For example. and in effect it temporarily halts the execution of the workflow branch where it is located.2.1. Scan activities is similar. 20.10. see sections 20.1 User’s Manual For usage examples.16. • Script to Run property: Browse for the script file (*.1. When following a (voice) Dial or Video Dial activity. 20. and this construction is the most convenient method of controlling the call length.TEMS Investigation 14.2.) This activity has no unique properties.16.10. the Wait has the apparent effect of giving duration to the call.7. the Wait activity comes in useful whenever some other tasks need to be separated in time. For usage examples.3.4.6. Run Script This activity calls another script and is equivalent to inserting the whole of that script in its place.10. The Duration property governs how long to wait.2.10.tsc) that you want to call.. It should be stored in the same directory as the calling script.8. 20. see section 20. The situation with Start . Wait For This is a conditional wait which lasts until a given condition is satisfied.2.. the execution proceeds to the next activity.2.4. the entire sequence can be enabled or disabled in a single action.16. After the wait time has expired.2. 20.9. Wait The Wait activity basically does nothing at all.16.

An implicit OR relationship holds among devices as well as among events. there will be no repetitions. Additional fields Start.1. What it does is to reiterate the “wait for” procedure at regular intervals whose length is defined by Repeat Interval. Schedule: Wait for a point in time determined by a schedule (which is unrelated to any device activity). Repeat: This option is intended to be used in loops and has an effect only within such a structure. Time. see below.6. Event: Wait for an event to occur. • • • NT12-7002 ver 1.1. the wait will end as soon as any of the devices reports any of the events.Chapter 20. An example is given in section 20. If Repeat is set to No.6. This option is intended to be used in loops together with the Repeat option. if you specify multiple devices and/or multiple events.10. and Repeat Interval appear where you set up the schedule. stated in the format hh:mm:ss. Equivalent to Time of Day with Time = hh:00:00. Its use is best illustrated by an example.10. That is. Additional fields Equipment and Events appear where you specify the desired event(s) and the device(s) that should report it.6. • Start = Immediately: No wait. Repeat. Start = On The Hour: Wait for a new hour to begin. see section 20. See the example in section 20.2.0 241 .10. Service Control • Trigger property: This property determines what to wait for. Start = Time of Day: Wait for a specified time of day (Time).

Result = Failed: The activity failed for whatever reason (other than termination by the TEMS Investigation user). “Stopped by User” equates to the user right-clicking the activity in the Navigator and choosing Stop. This can happen only if the activity has its Abort property set to On Timeout: see section 20. 242 . If the activity is executed manually from the Navigator as described in chapter 9. Operator. “ftpDownloadActivity1 Equals Failed”.1 Result = Stopped by Duration: The activity was aborted because its maximum duration expired. • You must yourself ensure that the monitored activity has a position in the work flow where it will in fact complete to terminate the Wait For activity. see section 20. • • • • Result = Succeeded: The activity completed normally.17.TEMS Investigation 14.10. This is not considered during validation. Result = Stopped by User: The activity was stopped by the user clicking the Stop Script button.1 User’s Manual Activity Result: Wait for a particular outcome of another activity in the script. again.2. Result = Stopped by Event: The activity was aborted because a specific event occurred (Abort property set to On Event.17. see section 20.2).6. Result appear where you detail the required outcome: for example. For usage examples. 1. Additional fields Activity.

using their connection manager applications. If an Network Connect has previously succeeded but the connection goes down later on.16. you must still include a Network Connect activity in your script. – For other LTE devices. in the circuit-switched case. Note: For certain devices. Be aware that in these cases. A side-effect of the Network Connect activity is to start a restricted form of IP sniffing that is performed continuously for the sake of collecting input to KPI calculations.3.1 below for specifics in this regard on various devices and device categories.1. no KPI data can be collected. (This IP sniffing collects only data needed for KPIs and is distinct from the full-scale variety which is initiated by the Start IP Sniffing activity. you can work around that problem by editing a line in the file <TEMS Investigation install dir>\Application\Investigation.) If your data collecting device is unable to perform the IP sniffing.3. as detailed under Configuration below.16. Please note that in either case.1.16. rather than automatically in the Service Control script. Ericsson Fixed Wireless Terminals must use an NDIS data connection. – Some LTE devices must be connected to the network manually. Service Control 20.exe. or you can ignore failure to start IP sniffing and go ahead with the execution anyway: ignoreIPSniffError="true". NDIS can be chosen for packetswitched only.Chapter 20. Network Connect Establishes a data service connection.0 243 . In the packet-switched case.config.) NT12-7002 ver 1. See section 20. IP Activities 20.3. whereas RAS can be used with both PS and CS. which by default reads: <dataServicesConfiguration ipSniffEnabled="true" ignoreIPSniffError="false" /> You can either disable IP sniffing by setting ipSniffEnabled="false". the phone works like an ordinary modem and performs a dial-up. a PDP context is activated (UMTS) or a PPP session established (CDMA). the connection manager must be started to enable the Network Connect activity in scripts. setting up an NDIS connection requires prior configuration using a software application delivered with the device. Whether NDIS or RAS is used is governed by the Mode parameter. (NDIS only. a Network Connection Lost event is generated.

1. The parameter is not applicable to other cellular technologies. if a CID other than 1 is to be used you need to specify that value. and you wish to avoid triggering a failure just because the device was already connected. If “Best available” is chosen. you cannot run the Network Connect activity twice without an intervening Network Disconnect. however. • If set to True. section 10. For CDMA/EV-DO. the second Network Connect will fail. This setting is useful if you want to be able to run Network Connect without full knowledge of the device’s previous activities. as follows: *99***n#. For TD-SCDMA.1 User’s Manual • Configuration property: Mode: Technology to use for connecting to the network: NDIS or RAS. for example using an external connection manager. Succeed If Already Connected: This parameter governs what will happen if the device already has a network connection (a valid IP address) set up by other means when the Network Connect activity is run.6. the Network Connect activity will count as successful anyway. 244 . Leave this field empty if an APN is specified in the device (always needed for NDIS) or for the modem in Windows. RAS Phone Number: Phone number to use when performing a RAS dial. see the Getting Started Manual. • No matter how this parameter is set. For an NDIS connection to be establishable. NDIS is first and RAS is second priority. and on the Summary tab of the Service Control Monitor it will be noted that a connection was already available. For UMTS this is usually *99#. NDIS CID: The CID (Connection Identifier) to connect with when NDIS is used. If set to False. UMTS/LTE APN: The Access Point Name to use for UMTS and LTE networks. the Network Connect activity will count as a failure.TEMS Investigation 14. enter #777. the device must of course support NDIS. If you do. enter *98*1#. Regarding devices for which the APN must be configured differently.

) Not applicable to circuit-switched. enter user and password here. If this is the case for you. Secondary DNS: IP address of the secondary domain name server. Leave blank if the IP address is provided automatically by the operator. the shorthand “CM” is used below for convenience.1. MS840. VL600. (Property of PS bearer. Leave blank if this is provided automatically by the operator.) Not applicable to circuit-switched. G13. LG Generic: If the device is detected as “LG Generic”. MS910. Network Connect Prerequisites for Various Devices This subsection details the behavior and requirements of a variety of devices with respect to the Network Connect (and Network Disconnect) activities. and preconnected Network Connect will be used. (Property of PS bearer.16. Examples of models: LS840. LG Android LTE smartphones using an NDIS connection require tethered network connection setup from the device menu system and preconnected Network Connect. IP Address: Local IP address. • NT12-7002 ver 1. Use Header Compression: Use of header compression for packetswitched. Leave blank if this is provided automatically by the operator. For “connection manager”. Use Data Compression: Use of data compression for packetswitched. LD611.3. 20. FM300. Network Connect performed from within TEMS Investigation is referred to as “scripted Network Connect”.Chapter 20. The Network Connect activity that is run in TEMS Investigation in cases where the connection setup needs assistance from outside the application is referred to below as “preconnected Network Connect”. do not use a CM. P936. Password: Certain operators require authentication in order to establish a data service connection. G7. Service Control User Name. Doing so will cause a port conflict. Primary DNS: IP address of the primary domain name server.0 245 . the connection must be set up either from a CM or from the device menu system. LG LTE Devices • • For LG LTE USB modems.1. Examples of models: AD600.

no CM should be used with any such devices. GT-B3710: Some older firmware of this device without an AT port requires that the CM should be running. R940. Examples of models: I510. Samsung LTE Devices • General procedure: If an AT port exists for the device. and TEMS Investigation will use preconnected Network Connect instead. R920. GT-B3730. TEMS Investigation will try to open that port and use it to control the network connection. ZTE Z006Z. a tethered connection must be set up. 246 . TEMS Investigation then communicates with the CM to control the connection. Qualcomm Android LTE smartphones generally require preconnected Network Connect. R910. GT-B3740: Samsung GT-B3730 and Samsung devices with AT support on the LTE Control Port (such as GT-B3740) have support for scripted Network Connect. provided they are detected as Sierra Wireless devices in TEMS Investigation. R820.TEMS Investigation 14. These NDIS devices should likewise not require use of a CM: Huawei E1820. If no AT port is present in the operating system. You cannot have the CM running when executing the Network Connect and Network Disconnect activities. No CM should then be used. Huawei E353. Huawei M920. If the device firmware exposes an AT port. then start the CM or enable tethering from the device menu system. With newer firmware. Samsung Android LTE smartphones do not have a CM accompanying them. If scripted Network Connect fails. or if the port is blocked. ZTE N910. the device behaves like GT-B3730/3740: see next paragraph. • • • Qualcomm HSPA+ Devices and Other Devices • • Sierra Wireless devices should not need to have a CM running. TEMS Investigation will use that port to perform a scripted Network Connect. Novatel MC996D. and a preconnected Network Connect will be performed. If no AT port is available.1 User’s Manual Qualcomm LTE Devices (MDM9x00 Chipsets) • • • Normally. then the device must be configured using a CM. since a port conflict will then occur (both TEMS Investigation and the CM communicate with AT commands over the LTE Control Port). R900. or tethering must be enabled in the device menu system (preconnected Network Connect performed in either case).

this activity has no effect. Note that this activity may not be needed since the device may have automatically attached to a PS network when powered on. 20. it is still necessary to include a Network Disconnect activity in the script. 20. This activity may be useful to make sure that the phone is not attached to the packet service when starting a measurement (for example. This activity has no unique properties. • • For Qualcomm devices using a RAS connection. For certain NDIS-capable devices. an NDIS connection must be terminated using the PC application accompanying the device (compare the Network Connect activity. but it still counts as successful on the Summary tab of the Service Control Monitor. Note that in such cases. Service Control If scripted Network Connect fails.Chapter 20. Network Disconnect Terminates a data service connection. In the packet-switched case a PDP context is deactivated (UMTS) or a PPP session ended (CDMA). no CM should ever be needed.3. if it has attached automatically at power-on). NT12-7002 ver 1.16.2. and scripted Network Connect should work fine. and TEMS Investigation will use preconnected Network Connect instead.16.) This activity has no unique properties.1). section 20. Devices not mentioned in the foregoing generally require preconnected Network Connect.3.4. If the device is already disconnected. 20. (Same behavior as for Network Connect with Succeed If Already Connected set to True. you can start the CM or enable tethering from the device menu system.16. PS Detach Performs a packet service detach.3.3.16. in the circuit-switched case the phone performs a hang-up. This activity has no unique properties.0 247 . PS Attach Performs a packet service attach.3.

248 . Password: Password for the server account.3.16.6. 20. Domain: The domain to register with. This activity has no unique properties. such data is collected automatically.5. May be omitted. SIP Unregister Causes the device to unregister from a SIP or IMS server used for VoIP. see sections 20. If Proxy is not used. Note that you do not have to use this command to obtain the data required for KPIs.16.5.3. 20. • Configuration property: Proxy: The proxy server to use. SIP Register Causes the device to register with a SIP or IMS server.6.7. 20. A user account must exist on the server. User Name: User name of account on the server.16.7. a valid server name must be entered here. Start IP Sniffing Starts capture of IP packets.TEMS Investigation 14.1 User’s Manual 20. This is a necessary preparation for a VoIP call.16.3.7. Compare chapter 33.16.

20.16. Note: This means that all packets belonging to any service used by the PC will be captured. NT12-7002 ver 1. Please be aware that paths and file names must have correct case throughout. None: No filtering of IP packets. FTP Download Downloads a file from an FTP server.16. Stop IP Sniffing Stops capture of IP packets initiated by the Start IP Sniffing activity. Service Control • Configuration property: Packet Size: Determines how many bytes of each message will be presented.Chapter 20.15).) • • The information element TCP Packet Loss and the event IP Interruption Time require that the Filter parameter not be set to “Optimized Performance”. This is frequently the preferable setting.3. all messages are presented in full and the entire header is always decoded.3.8.16.9. If you choose a fixed packet size. (Packets are filtered with respect to IP address only. protocol [TCP/UDP]. 20. Note also that you can conduct TCP load tests with the Network Bandwidth activity (see section 20. (Packets are filtered with respect to IP address. and port.) Headers Only: The first 54 bytes of every IP packet are captured.3. This activity has no unique properties. any further bytes in the message will be truncated. Filter: Type of filtering to apply to IP packets. • Optimized Performance: Capture of IP packets is reduced to the minimum needed to compute KPIs.0 249 . If you choose Full packet size.

path. Note that it is essential to set this correctly. Valid only when Firewall Mode = PORT. no files are stored. Note that the correct orientation of the slashes is dependent on the FTP server operating system. if required. No explicit root symbol is used (no leading slash). Server Address: The IP address or host name of the FTP server. e. Target File: Drive letter. Local Data Port: The data port the client will use for FTP download. 250 . No ftp:// prefix is to be used. User: User name on the FTP server. C:\targdir\targfile. Password: User password on the FTP server. if required. The address may not contain a path to a subdirectory. Firewall Mode: PASV or PORT.dat. Account: Account name on the FTP server. and file name describing where to store the file on your computer. e. FTP Upload Uploads a file to an FTP server.g. enabling or disabling passive FTP as defined in  IETF RFC 959. if applicable.dat. The default port number is 21. A session ID (integer) is prefixed to the file name. multiple files are created. srcdir/srcfile.dat.dat. If multiple FTP Download activities execute in parallel.g. e.g. Server Port: The port on which the FTP server listens for requests.10. type the file name only. each with a unique session ID prefixed to prevent conflicts.: 0targfile. 1targfile.3. If the Target File field is left blank. 20.TEMS Investigation 14. this is the default setting. The drive letter must be included.16. Please be aware that paths and file names must have correct case throughout.1 User’s Manual • Configuration property: Source File: The path and name of the file residing on the FTP server. if the file is in the root directory.

if required.dat.dat. C:\srcdir\srcfile. Source File: Drive letter. It is possible to specify the unit as follows: B = byte. M = megabyte. Size to Upload: Size of the file to upload (only valid if Use Temporary File = True). if required. however. Service Control • Configuration property: Target File: Path and file name describing where and how to store the file on the FTP server. a temporary file is created holding the data to upload. the number you enter is interpreted as a byte count. No explicit root symbol is used. Server Port: The port on which the FTP server listens for requests. targdir/targfile. e. 1targfile.dat. the file will be written to the root directory. G = gigabyte. K = kilobyte. enabling or disabling passive FTP as defined in  IETF RFC 959. Valid only when Firewall Mode = PORT.0 251 . and file name identifying the file to be uploaded. No ftp:// prefix is to be used. NT12-7002 ver 1. that if multiple instances of TEMS Investigation installed on different PCs are uploading to the same server. The default port number is 21.Chapter 20. path. Alternatively. If set to False.g. no file is created. Note that it is essential to set this correctly. Note that the correct orientation of the slashes is dependent on the FTP server operating system. T = terabyte. e. If multiple FTP Upload activities execute in parallel.g. each with a unique session ID prefixed to prevent conflicts. Note. Server Address: The IP address or host name of the FTP server. Local Data Port: The data port the client will use for FTP upload. lowercase letters can be used with no difference in meaning. multiple files are created. User: User name on the FTP server. A session ID (integer) is prefixed to the file name. If you do not specify a unit. if you type a file name only. The address may not contain a path to a subdirectory. Password: User password on the FTP server.dat. each instance must use a unique target file name. e. if applicable.g. Use Temporary File: If set to True. Account: Account name on the FTP server.: 0targfile. Firewall Mode: PASV or PORT. The drive letter must be included.

Internet Explorer: Internet Explorer 9 is used. The time is counted from the moment the first HTTP packet is received from the server.3. Proxy Server Port: Proxy server port.11. Client Threads: Number of concurrent threads to be used by the client in handling the HTTP session. • • TEMS Browser: The internal Web browser in TEMS Investigation is used. 252 . This is supported under Windows 7 and Vista. Use Proxy Server: Select whether to use a proxy server for this connection. HTTP Get Downloads a URL from an HTTP server.16. Internet Explorer use is limited to one device at a time running one HTTP Get activity. Therefore. TEMS Investigation can only make use of a single Internet Explorer session running on the PC. Limitations on HTTP Session Concurrency At any given time. regardless of the number of threads.1 User’s Manual 20. that device cannot execute any other HTTP Get activities at all. End Session After Payload Size: The HTTP session is ended automatically after a user-specified amount of data has been downloaded. but not under Windows XP. • Configuration property: Browser Client: Web browser used to conduct HTTP sessions. Proxy Server Address: Proxy server address. see below. Enter the number of bytes to download in the Payload Size field that appears. Note that the main URL (specified under URL) is downloaded only once. An additional field Time appears for entering the desired session duration. that is. URL: Main URL to download. in a Service Control script. Regarding concurrency limitations. Other devices can however employ the TEMS browser to run HTTP Get while Internet Explorer is in use.TEMS Investigation 14. End Session After Time: The HTTP session is ended automatically after a user-specified length of time. not even with the TEMS browser. While using Internet Explorer.

16. The default port numbers are 9201 (CO). Gateway Port: (Appears when Connection Mode = CO or CL) The WSP port on the server. optional) The WAP proxy port number. Note that WAP pages that redirect the user to a different page cannot be downloaded. but this is optional. • Gateway Address: (Appears when Connection Mode = CO or CL) The IP address of the operator’s WAP gateway. The WAP server can be specified as an IP address or host name. • CO and CL are used by WAP 1. Connection Mode: One of CO (Connection-oriented). WAP Get Downloads a page from a WAP server. the phone first contacts and performs a handshake with the WAP gateway before starting to request WAP pages.Chapter 20. there are no restrictions on HTTP session concurrency. The difference between the modes is essentially this: With CO. This WAP version may use a WAP proxy. Proxy Address: (Appears when Connection Mode = WP-HTTP. neither for a single device nor for multiple devices. 20. CL (Connectionless). Proxy Port: (Appears when Connection Mode = WP-HTTP. or WP-HTTP (Wireless Profiled HTTP). The default is 8080. NT12-7002 ver 1. 9200 (CL).12. the http:// prefix is optional.3. • Configuration property: URL: URL of WAP page to download. Service Control When the TEMS browser alone is used. optional) The IP address of the WAP proxy.0 253 . WP-HTTP is used by WAP 2.x and require a WAP gateway. whereas with CL this is not done.0.

UDP is more suitable than TCP for this purpose.4. There is no upper limit. The application will then start out at a low throughput rate and gradually increase the throughput until the packet loss becomes excessive. found on the installation CD in 254 .) Example of User Agent string (for Sony Ericsson W995): User-Agent: SonyEricssonW995/R1DB Browser/NetFront/3.1 20.3.. How to install and configure this software is described in the document “TEMS UDP Server User’s Manual”. Max Response Time: Maximum time to wait for each ping response. 20. • Configuration property: Remote Address: The IP address or host name of the server to be pinged. .ddd.ddd. Given in the format hh:mm:ss. Packet Size: Size in bytes of the packet sent with the Ping activity..13.1 JavaPlatform/JP-8.1 Configuration/CLDC-1. .16. among other things. (Some WAP portals adapt their contents to the devices accessing them..3.16.1 User’s Manual User Agent: This is a string indicating. Ping Initiates a sequence of pings. even if the service does not require these safeguards.4 Profile/ MIDP-2.TEMS Investigation 14.. since the rigorous acknowledgement and retransmission mechanisms of TCP (designed to guarantee full data integrity) will always slow down data throughput. Number of Pings: The number of pings to send.14. the make and model of the device and what WAP software it has installed. UDP Data transfer tests using the UDP protocol is a good way to determine the optimum data throughput rate for services that tolerate a given degree of data loss. Interval Time: Time between consecutive pings. The maximum size is 2000 bytes. You can let TEMS Investigation run the UDP test in an automated fashion. Given in the format hh:mm:ss. UDP testing is done against a PC that is running the application TEMS UDP Server.

• Direction: • • • Send: The client sends UDP data to the server.Chapter 20. see the introductory text above. If you select manual mode. you specify the parameter values yourself. Throughput (kbit/s): The UDP throughput rate that will be used. The TEMS Investigation application has a UDP client built into it which interacts with this server. Please note that you cannot test Full Duplex in automatic mode. The packet and throughput parameters work as follows. Service Control the subdirectory Documents. Packets per Second: Number of UDP packets to send or receive per second. NT12-7002 ver 1. Full Duplex: Data is sent in both directions concurrently. using the parameters below. Specify the TCP control port to use here. Duration (sec): The duration of the UDP session. TCP Control Port: The TCP protocol is used in setting up the UDP session and also to communicate the test results after the session has concluded. Receive: The server sends UDP data to the client. UDP Mode: • Automatic: The TEMS Investigation UDP client will automatically determine the optimum data rate. the parameters from Packets Per Second onward (see below) are set automatically and are not editable.0 255 . If you select automatic mode. • Configuration property: Remote Address: The IP address or host name of the UDP server. Manual: You specify the data rate and packet rate yourself. Packet Size: The UDP packet size (in bytes) that will be used. all parameters are set by the application and cannot be edited. However. when you change one parameter the others will be adjusted so that the above equation still holds true. this is the packet rate in each direction. For Full Duplex mode. In this case. since the parameters are constrained by the relation (packets per second)  (packet size) = throughput.

is comparable to assigning multiple concurrent FTP activities to a device. when the packet loss rate becomes nonnegligible. just as for other service sessions. on the other hand. They do not indicate the amount successfully transferred to the server. It must be kept in mind that the uplink UDP information elements in the category Data. you must download the Iperf software and install it on the desired machine. the UDP Upload Throughput information element is no longer reliable.3. In contrast. section 3. which are updated continuously in the course of the UDP session (see Information Elements and Events. 20.8) only indicate the amount of data sent.1 User’s Manual Further Notes on UDP Testing Statistics on completed UDP sessions are output on the Summary tab of the Service Control Monitor. the UDP Download Throughput is always accurate. • Configuration property: 256 . see section 20.14.10.16. Measuring over TCP.3. UDP testing with the Network Bandwidth activity is similar to the UDP activity.4. See section 20.6 for details. Network Bandwidth (Iperf Testing) This activity measures maximum TCP and UDP bandwidth performance by interacting with an Iperf server.TEMS Investigation 14.2. section 5. To find out what percentage of packets was actually received by the UDP server. The client uses TCP to obtain this information from the server after the UDP session has concluded.3. you need to check the summary statistics in the Service Control Monitor. see the example in section 20. Therefore.3. Before you can use this activity.15. See the Getting Started Manual.15.16.

Service Control General section Remote Address: The IP address or host name of the remote server. Protocol: The protocol to use for Iperf testing: TCP or UDP. section 5. Receive: The server sends data to the client.2. UDP section (used for UDP only) Bandwidth: UDP bandwidth (throughput) in Mbit/s.6. Duration: The duration of the Iperf testing session (hh:mm:ss). no such port is specified. Port: Port on the remote server. Password: Password on the remote server. Buffer Size: UDP buffer size in kilobytes.Chapter 20. User: User name on the remote server. Direction: • • • Send: The client sends data to the server. Port: The port on which the Iperf server listens for requests. NT12-7002 ver 1. Listen Port: See above. Packet Size: UDP packet size in bytes.0 257 . If you set the parameter to False. Path: Path to Iperf on the remote server. Use Listen Port: True or False. Telnet/SSH2 section Connection Client: Either Telnet or SSH2 can be used as protocol. set this parameter to True and enter the port under Listen Port. Please note that SSH2 requires a special TEMS Investigation license option. see the Getting Started Manual. Full Duplex: Data is sent in both directions concurrently. If you want to specify a port on which TEMS Investigation should listen for data (not required).

16. all with the following structure: PS Detach  PS Attach  Network Connect  <data service activity>  Network Disconnect. 258 .TEMS Investigation 14. but a STARTTLS command is issued later on to set up a secure session. STARTTLS: The initial communication is not encrypted.4. 20.16. Password: Password for e-mail account. SSL/TLS: SSL or TLS is used during the whole e-mail session. Subject: Content of e-mail Subject field. • Configuration property: From: E-mail address of sender. To: E-mail address of recipient. Messaging Activities 20.4. Security: • • • None: No security is applied.1 User’s Manual 20. it is best to use a sequence structure with a waiting period: E-mail Send  Wait  E-mail Receive. User: User name of e-mail account.16.3. Server Port: The port on which the SMTP server listens for requests.1. Predefined Snippets for IP One snippet is provided for each data service related activity. E-mail Send Sends an e-mail to an SMTP server. Body Text File: Name of file containing e-mail body text. Server Address: The IP address or host name of the SMTP server. When composing an e-mail script controlling both sender and receiver.16. Attachment: (Optional) Name of file to enclose with the e-mail as attachment.

• Configuration property: Gateway section These are WAP settings. When composing an MMS script controlling both sender and receiver.10. 20.Chapter 20. Password: Password for e-mail account.2.0 259 . All e-mail contents are written to a single file: header fields. body text. • Configuration property: Server Address: The IP address or host name of the POP3 server. Server Port: The port on which the POP3 server listens for requests.4 and 20.4.16. MMS Send Sends an MMS.16. Store Location: Full path to directory in which to store e-mails.2. E-mail Receive Receives an e-mail from a POP3 server. but a STARTTLS command is issued later on to set up a secure session. see section 20.3.16. Service Control 20. Security: • • • None: No security is applied. it is best to use a sequence structure with a waiting period: E-mail Send  Wait  E-mail Receive.3. NT12-7002 ver 1. and attachments (if any). SSL/TLS: SSL or TLS is used during the whole e-mail session.3.4. the same as for the WAP Get activity. STARTTLS: The initial communication is not encrypted. User: User name of e-mail account.12. See sections 20.16. it is best to use a Parallel structure. When composing an e-mail script controlling both sender and receiver.

the same as for the WAP Get activity. including plain-text files and frequently used image file formats. Attachment: The file to send.3. The MMS Receive activity needs its own connection parameters since logging in to the MMS Center frequently requires connecting to a different APN.16. see section 20. Please note that operators generally impose a limit on the MMS file size. If you encounter problems sending MMS messages.3. Password: Login credentials for MMS Center.4.TEMS Investigation 14. try sending very small files to find out whether the size limit is causing the problem. MMS Receive Receives an MMS.16. 260 . The receiving device can be identical with the sender. 20.1 User’s Manual MMS Content section To: The phone number(s) or e-mail address(es) to send the MMS to. Note that the phone acting as recipient must not have automatic MMS download turned on (where the phone retrieves the MMS message from the MMS Center automatically as soon as it receives a notification).16.12. A file with an extension unknown to TEMS Investigation will be sent as an attachment to the MMS (content type “application/octet-stream”). Gateway section: These are WAP settings.4. if required. Message: Free text field containing the text message of the MMS (if any). separated by semicolons. is supported. User. A wide variety of file types.1. see section 20. MMS Message Center section URL: The URL of the MMS Center (usually beginning with http://). Multiple recipients can be specified. • Configuration property: Connection Parameters section: Same as for Network Connect.

set this parameter to False.0 261 . For SMS Send activities to work. The SMS service is implemented with AT commands. SMS Message: SMS message string. SMS Send Sends an SMS. Configuration property: Receiving Device: The phone number or e-mail address to send the SMS to. NT12-7002 ver 1. To stick with the SMS Center indicated on the SIM. SMS Center: Phone number to SMS Center.Chapter 20. AT+CMGW.4. Use Custom SMS Center: Set this to True if you want to make use of an SMS Center other than the one specified on the SIM. Delivery Report Timeout: Time to wait for the delivery report. CDMA: AT+MODE. Service Control 20. Request Delivery Report: Set this to True if you want the device to request a delivery report from the SMS Center.5. the phone must therefore support the following AT commands: • • • UMTS: AT+CMGF with format 0 or 1 and AT-CMGS. The receiving device may be identical with the sender.16. and AT+CMSS.

TEMS Investigation 14.4. If no match is found. 262 . • • Message Match Pattern: The pattern to use for matching incoming or stored messages. The choice made here determines the contents of the Configuration property.90).16. and no configurations have yet been defined for that activity type.7. Reference:  msdn. Predefined Snippets for Messaging One snippet is provided for each messaging activity.16. SMS messages stored in the device will be searched for matching messages.1 User’s Manual 20.4. The syntax is that of . 20.NET Framework regular expressions. Use a Wait activity between Start and Stop to specify the duration of the scan. • Scanner property: Here you select the type of scanner to use.6. 20.aspx Starts with: Enter string under Message Match Pattern to match beginning of message text. Scan Activities A scan activity starts or stops a scan task of a specified type. The point of doing this is to catch a message already received by the device before it performs the SMS Receive activity.microsoft. • Configuration property: Match Type: • Regular expression: Enter regular expression under Message Match Pattern to match whole message text. the activity waits for a matching message to arrive. SMS Receive Receives an SMS. all with the following structure: PS Detach  PS Attach  Network Connect  <data service activity>  Network Disconnect. If the field is left empty. Please note that if you add a scan activity to the workflow. Ends with: Enter string under Message Match Pattern to match end of message text. Search Text Messages in Device: If set to True. any message will match.16.5.com/en-us/library/hs600312(v=VS. then you need to make a selection in the Scanner drop-down box to enable the Configuration Sets pane.

5 18.5 16. keyed to their configuration descriptions: Ref. These are all described in chapters 14–19.5 15.3 17.0 263 .4 14.3 18.3 19.3 Scan Activity Start/Stop CPICH Scan Start/Stop Enhanced Power Scan Start/Stop Narrowband Interference Scan Start/Stop Network Scan Start/Stop Pilot Scan Start/Stop PN Scan Start/Stop Preamble Scan Start/Stop RS Scan Start/Stop RSSI Scan Technology WCDMA LTE CDMA WCDMA TD-SCDMA CDMA WiMAX LTE GSM WCDMA LTE TD-SCDMA CDMA WiMAX Start/Stop Spectrum Scan GSM WCDMA LTE CDMA WiMAX Start/Stop Timeslot Scan WCDMA NT12-7002 ver 1.4 18. identical to that for a manually initiated scan.6 19.Chapter 20.3 15. Descr.2 15.5 15.2 16. to Config.2 14.4 18. Below is a full list of the scan activities.4 19. Service Control • Configuration property: Scan configuration.4 16. 15.6 17.3 16.

16. All of these have the following structure: Start .6.2.5. The retry behavior is governed by the On Failure property..16. see section 20. #.17. This activity has no unique properties. 9. 20.7. Scan. For a general discussion of video streaming testing..16. Streaming Download streaming video from a streaming server and play it in TEMS Investigation. 20. the device waits for the event Call Established. *.16. After dialing. Valid characters are: +.1 User’s Manual 20. see section 20. • Configuration property: Phone Number: The complete phone number (including country code) to call. This activity has no unique properties.. see chapter 27. Scan  Wait  Stop .4. Video Activities 20. 264 . . Hang Up Hangs up a video call.16..2.. 20. Predefined Snippets for Scanning One snippet is provided for each scan type.2. 20. The call duration is most conveniently specified by means of a subsequent Wait activity..16.1.. Video Dial Dials a phone number and sets up a video call.3. 0. If this event does not occur. the device may retry the call.6.6.1.16. and p (for pause).6. Answer Waits for an incoming video call to arrive and answers it when it arrives.TEMS Investigation 14.6.

Use Proxy Server: Specify whether to access the streaming server through an RTSP proxy server. Streaming Mode: “Normal” means downloading a video clip of known length (on-demand streaming). Target File: Name and storage location for received streaming file.6. “Live” means tapping into a live stream or repeating playlist delivered by a streaming server. Proxy Address: The IP address or host name of the RTSP proxy. File To Stream: The file name of the video clip or streaming session description to be downloaded from the streaming server. Prebuffer Length: Length (in seconds) of segment to buffer during initial buffering. specify the duration of the streaming session here. By default ports 5004–5007 are used.3gp. 20. When this time has expired. Streaming Duration: For Streaming Mode = “Live”. The default port number is 554. Service Control • Configuration property: RTSP Port: The RTSP port on the streaming server. The port entered and the three following ports will be allocated to RTP data. RTP Port: Here you specify ports to use for RTP on your PC. Streaming Server: The IP address or host name of the streaming server.5.Chapter 20. Min: 1 s.16. Min: 1 s.0 265 . WAP Streaming This activity is used to do streaming via a WAP page. the activity terminates. NT12-7002 ver 1. The format is . Rebuffer Length: Length (in seconds) of segment to buffer during rebuffering. Max: 20 s. Max: 20 s.

266 . RTSP Port . 20..7.3.1.3.16. URL . *. 0.2. After dialing. Predefined Snippets for Video • • Video Call snippet: Video Dial  Wait  Hang Up. section 20. The retry behavior is governed by the On Failure property.6.1 User’s Manual • Configuration property: Streaming Link: The text string of the WAP page RTSP link to the stream that is to be downloaded.TEMS Investigation 14.16. 20.12. Answer Waits for an incoming CS voice call to arrive and answers it when it arrives.7. • Configuration property: Phone Number: The complete phone number (including country code) to call. the device waits for the event Call Established.6.16. Dial Dials a phone number and sets up a circuit-switched voice call. see section 20. For AQM measurement.2.17. 9. you may instruct the device to retry the call.2. The call duration is most conveniently specified by means of a subsequent Wait activity. This activity has no unique properties.. Streaming Mode: See the Streaming activity. see section 20.6.. . section 20.16..16.7. WAP Streaming snippet: PS Detach  PS Attach  Network Connect  WAP Streaming  Network Disconnect. If this event does not occur. 20. #.16.. and p (for pause)..16. User Agent: See the WAP Get activity. Valid characters are: +. this should be the number to the Call Generator or MRU: see section 36..7.3.4. Voice Activities 20.

See chapters 35–37. Service Control 20.0 267 .16. M2M DL + UL: Mobile-to-mobile audio quality measurement using Audio Capturing Unit (ACU). POLQA NB. Please note that POLQA can only be measured in the ACU configuration (Measurement Type = “M2M DL + UL”). Measurement Type: • • • M2F DL + UL: Mobile-to-fixed audio quality measurement using Call Generator. Hang Up Hangs up a CS voice call.Chapter 20. Channel4: Channel for phone connected to LINE IN 4/ LINE OUT 4. otherwise has the value “None”): • • • • Channel1: Choose this channel for the phone connected to LINE IN 1/LINE OUT 1 on the ACU. This activity has no unique properties.7. Channel2: Channel for phone connected to LINE IN 2/ LINE OUT 2. • Configuration property: Algorithm: One of PESQ.16. NT12-7002 ver 1. during a CS voice call.7.4. Audio Channel (only used for M2M DL + UL. and POLQA SWB. 20. Channel3: Channel for phone connected to LINE IN 3/ LINE OUT 3. M2M DL: Mobile-to-mobile audio quality measurement using Mobile Receiving Unit (MRU). including PESQ/POLQA. AQM Measurement Performs audio quality measurement (AQM).3. AQM Duration: The length of time for which to collect audio quality measurements (hh:mm:ss).

6.9. 20.TEMS Investigation 14. section 3. • Configuration property: Codec: Voice codec.9.7. 20. This activity has no unique properties.7. See also section 20. Codec: Voice codec. The point of this mechanism is to have poor quality files automatically saved for further study.16.1 User’s Manual Recording Threshold (only used for M2M DL + UL): All audio files (*. 20.16.711 A-law. See chapter 38.7. VoIP Answer Waits for an incoming voice-over-IP call to arrive and answers it when it arrives.8. • Configuration property: Phone Number: The phone number to call.16. 268 .16. AMR-WB.16. 20.7. VoIP Dial Dials a voice-over-IP call.9. one of: G.16.pcm) with an AQM value worse than this threshold value will be stored under My Documents\TEMS Product Files\TEMS Investigation 14.711 A-law. Codec Rate: Voice codec rate. or AMR-NB.7. VoIP Voice Quality Performs audio quality measurement (AQM) including PESQ/POLQA. one of: G.7. VoIP Hang Up Hangs up a voice-over-IP call.5.7. Note that the measurements are found in the Media Quality information element category: see Information Elements and Events. or AMR-NB. AMR-WB. Codec Rate: Voice codec rate. See also section 20.1\PESQ\Recordings.

16. How to Set Up VoIP Testing A number of things must be observed when setting up and running VoIP scripts.10. see section 20.1\PESQ.7.0 269 . so that it can be controlled which side hangs up the call. 20. one for the caller and one for the callee.16. Both caller and callee must register with the SIP or IMS server to be used for VoIP.7. both fixed and wireless. Store AQM files: Yes or No. NT12-7002 ver 1. Below is a summary of the salient points. nor any other internet connections in parallel. Predefined VoIP snippets are provided. You must not have any other measurement devices plugged into either PC when doing VoIP testing. the audio file will be saved under [My] Documents\TEMS Product Files\TEMS Investigation 14.10.Chapter 20. Furthermore. This setup is necessary to enable audio quality measurement for VoIP. found on the installation CD in the subdirectory Documents. MOS limit: If the MOS value for an audio file is lower than or equal to this threshold. • • • • • 20. each running an instance of TEMS Investigation. • The calling device and called device must be connected to different PCs. Caller and callee must use the same speech codec.7. The callee script must therefore complete its SIP Register activity before the caller script reaches VoIP Dial. All network interfaces except the testing device must be disabled. Predefined Snippets for Voice • Voice Call snippet (CS): Dial  Wait  Hang Up. Service Control • Configuration property: Duration: The length of time for which to collect voice quality measurements. For a full tutorial on testing VoIP. You cannot have an Ethernet cable connected either.16. Two scripts must be prepared. see the technical paper “VoIP Testing with TEMS Investigation”. The Duration parameter should be set differently for caller and callee.9. the callee must be registered before the caller places the call.

if no such configuration set exists. you need to create one in the Configuration Sets pane.TEMS Investigation 14. For example.17. the activity is disabled and will not be performed when the script is run. • • 20. and the whole script is terminated. the activity is abandoned. 20.1.17. Equipment: The EQ to which the activity is assigned. Activity Section • • Name: Name given to the activity. for FTP Download. Stop Script Execution: If an activity fails. Enabled: True or False.1 User’s Manual • VoIP Dial snippet: Network Connect  SIP Register  VoIP Dial  VoIP Voice Quality  VoIP Hang Up  SIP Unregister  Network Disconnect. an FTP server configuration set needs to be selected here. • 20.16 in connection with their respective activities. and the execution proceeds to the next activity in the workflow branch in question.2. If set to False. VoIP Answer snippet: Network Connect  SIP Register  VoIP Answer  VoIP Voice Quality  SIP Unregister  Network Disconnect.17. General Activity Properties These properties are common to all or many activity types. – Continue Script Execution: If an activity fails. Failure Handling Section • On Failure: This property determines what will happen if an activity fails (when first attempted). The combo box is populated with all existing configuration sets that fit the activity.) Configuration: Reference to a configuration set of the type associated with this activity. This is indicated by the activity being dimmed by a semi-transparent greenish box in the flowchart. the activity is abandoned. (Only appears for certain non-editable activities such as the “root” activity at the top and bottom of the workflow. – 270 . Activity-specific properties are covered in section 20.

Configuration Sets 20.18. – Note that this property is also possessed by the root activity. On Failure – what action to take if all retries fail (continue or stop script).0 271 . it will be retried. Descriptions of Configuration Sets All types of configuration set are associated with a particular service.16 in conjunction with the activity or activities that use it. Compare the Terminate activity. For that reason each configuration set is described in section 20. otherwise it will run to completion. – – Never: The activity will execute as long as it takes to complete. Managing Configuration Sets You can manage configuration sets using the Settings Manager utility.2. Delay – the time to wait before each retry. What you indicate here is thus a maximum duration for the activity.1.18. see section 20.19. 20. • To launch the Settings Manager utility. Service Control – Retry: If an activity fails. When you choose this option. On Timeout: The activity will be aborted after a fixed period of time.Chapter 20. which aborts the whole script with immediate effect. unless it has already completed before that time. For a tutorial on how to use these functions in conjunction with script saving/loading in order to port scripts between PCs. • Abort: This property determines under what conditions the activity will be aborted.18. On Event: The activity will be aborted if and when one of the specified events occurs. in which case it applies to the entire script. 20. NT12-7002 ver 1. a set of further parameters appear: Retries – the number of retries. choose File  Manage Settings.1.

2. Select the configuration sets you want to import by clicking them in the list. in standard Windows fashion.. you use the Import tab. Each configuration set is now exported as a file named according to the format TEMS. Exporting Configuration Sets To export configuration sets you use the Export tab.config. Now select where to export the configuration sets. • 272 . in Windows.1 User’s Manual Alternatively.TEMS Investigation 14. Shift + click and Ctrl + click can also be used.1 Service Settings. Click the Target button and point to the desired directory. Importing Configuration Sets To import previously exported configuration sets.1. To perform the export.2.<.<service name>Settings. • Select the configuration sets you want to export by clicking them in the list.2.>. in standard Windows fashion.18. click the Export button. • Click the Source button and browse to the directory you want to import from. The window is populated with all configuration sets found in that directory.. right-click in the list and choose Select All/Unselect All. To select/deselect all sets. choose Start  [All] Programs  Ascom  TEMS Products  Utilities  TEMS Investigation 14.Settings.18. This window appears: 20. To select/unselect all sets.Services. right-click in the list and choose Select All/Unselect All. All configuration sets currently known to the application are listed in the window. • • 20. Shift + click and Ctrl + click can also be used.

• To restore configuration sets from a backup. From the Tools menu you can delete all configuration sets by choosing Clear Settings. click the Import button. NT12-7002 ver 1. • 20. click the Save button on the Service Control Designer toolbar. a backup of the configuration sets will be created whenever you use the Clear Settings command. If the Enable Backup option is selected. Format: You can save the script either with or without the configuration sets it uses. The Save Script dialog contains the following options: • • Description: Free-text field where you can optionally enter a description of the script. Deleting Configuration Sets You can delete a configuration set from TEMS Investigation by selecting it on the Export tab and clicking the Delete button.2. Note that configuration sets can also be saved separately: see section 20. The file will receive the extension .0 273 . select the backup of interest from the list. Saving and Loading Scripts To save a script to file. select it and click Clear.tsc (for “TEMS Service Control”). and click the Restore button. 20.Chapter 20. Service Control • To perform the import. To delete a backup. choose Tools  Manage Backups.2.18.3.19.18.

Open the sender’s script.1 User’s Manual – Standard: No configuration sets are saved with the script. To open an existing script stored on file. To this end. Export your configuration sets. The script can now be not only run but also freely modified on the receiver PC.19. (This is the default setting. 274 . Open the sender’s workspace.) Redistributable: All configuration sets referenced in a script are saved with the script. Saving Workflow as Image • You can also save the contents of the workflow pane as an image. 20.19.1. Choose this option if you are going to use the script on several computers. Start TEMS Investigation.TEMS Investigation 14. On the “receiver” PC (with the above data from the sender available on some suitable storage medium): – – – – Import the configuration sets exported from the sender.2. Choose this option if you are going to use the script on one PC only. Tutorial on Porting Scripts between PCs Follow these steps to share a script and its related configuration sets between two computers: • On the “sender” PC: – – – • Save your workspace. Save your script with Format set to Redistributable. choose File  Save As Image in the Service Control window and select the desired image file format. click the Load button on the Service Control Designer toolbar. – 20. making the TSC file a self-contained and independent entity that can be immediately reused on a different PC. This means that changes to a configuration set will automatically propagate to all scripts that reference it.

Zooming the Workflow Pane In the workflow pane.20. Activity Filter The Activity Filter combo box at the top of the Activity pane can be used to filter the list of activities so that it shows only the activity types supported by a particular device.20. You can however switch the mouse to zoom mode. on-failure behavior) of several activities at once. where mouse pointing actions have the effect of zooming the workflow pane in or out. By default all activities are shown (“All”).3.20. the mouse pointer by default has the usual point-andclick function. After you click the Zoom In button on the window toolbar. This is most conveniently done from the context menu: • Select all of the activities you want to modify by dragging the mouse pointer or by Ctrl + click.Chapter 20. Context Menu in Workflow Pane The context menu that appears when you right-click in the workflow pane has functionality that is mostly mirrored in other places: in the regular window menu and in the Properties pane. except the Move Left and Move Right commands which you can use to change the ordering of activities in a workflow.1. 20. The context menu is especially useful for changing properties (EQ assignment. The Refresh button to the right of the Activity Filter combo box updates the activity list with any new user-defined snippets that have been created since the list was last refreshed. Service Control 20. Further Functionality in the Service Control Designer Window 20. The rest is standard Windows functionality. mouse clicks in the workflow pane will magnify its contents in predefined steps. then right-click the selection and choose the desired command from the context menu. You NT12-7002 ver 1.0 275 . 20.20.2.

click the Zoom Out button on the window toolbar.TEMS Investigation 14. click the Pointer button. To return the mouse to pointing mode. To reverse the mouse-click zoom function.1 User’s Manual can also click and drag to select a portion of the workflow pane that you want to enlarge. 276 .

0 277 .Chapter 21. Choose Properties from the context menu.1. NT12-7002 ver 1. Other supported devices share little or none of the control functionality listed here. To access the property dialog of a device. Some devices have Navigator control functions that correspond to device properties for other devices. see section 9. these instances are marked with an “N” (for “Navigator”) in the table below. do as follows: • • Right-click on the device on the Navigator’s Equipment tab.1. and Samsung phones. Overview of Properties by Device This overview covers certain Sony Ericsson. Regarding control functions applied from the Navigator. Device Properties From TEMS Investigation you can view and modify certain properties of devices.1.8) are labeled “CL” in the table. Device properties that correspond to aspects of the Cell Lock control function in the Navigator (described in section 9. Device Properties 21. 21. For clarity. Nokia.

See chapter 43. prevent handover to specified cells.TEMS Investigation 14. 2 N N N N N N N N N N N N N N N N N N N N N N N RRC WCDMA capability control N 2. 278 Nokia NTM3 K790i/a W600i K800i K600i .) Control Function Samsung Infuse 4G TM506/Z750i Access class control Barred cells. access control Speech codec control3 TxPower control (GSM) 1. No.1 User’s Manual Sony Ericsson C702/C905*/W760i/W995* Sams. 3. access control BLER target control (WCDMA) C/A measurements (GSM) Channel verification (GSM)1 Disable handover CL EDGE capability control L3 messages. That is. discard/ignore Lock on ARFCN CL Lock on BSIC CL Lock on PLMN Lock on SC CL Lock on UARFCN CL Prevent handover CL Reserved cells. Changing order of priority between codecs is supported for C905*/ W995* only. Samsung Galaxy S 4G Xperia arc S* (Qualc.

section 6. To activate a control function.0 279 . Regarding “TPC Info Per Cell”. 21. You can turn the reporting on and off for each item listed. without exiting the dialog.2.2. like OK. which means no alteration of regular phone behavior. NT12-7002 ver 1.1. you must switch the corresponding “Default/Modified” field to Modified (can be done by double-clicking the value). At the outset this field has the value Default everywhere. listing messages and mode reports delivered by the phone. It is also applicable to the subset of those properties exhibited by the Samsung Galaxy S 4G. the phone retrieves all settings you have specified for it. Extended Reports This item appears for certain Sony Ericsson phones. Common Controls Each of the nodes in the property grid contains a field Default/Modified. Note the following: • • “Path Searcher Report (A2)” must be checked for the Finger Info information elements (WCDMA) to be valid. Functions of Dialog Buttons Besides OK and Cancel. 21.Chapter 21.2.1. but without exiting the dialog. Any changes to the properties will apply as long as the phone remains activated in TEMS Investigation. Restore Defaults resets all settings to their defaults.2. Device Properties 21. see Information Elements and Events. These buttons have the following functions: • • Apply saves all changes made to settings. the Properties dialog contains the buttons Restore Defaults and Apply. and the Samsung Galaxy S 4G and Infuse 4G models. then proceed to set the other parameters as desired according to the subsections below. When you activate the phone in the application. Properties of ST-Ericsson Chipset Based Phones This section deals with viewable and editable properties of ST-Ericsson chipset based phones: Sony Ericsson phones except Xperia arc S.

You can change the default allocation here. chapter 4).1.2. Classes 10 .1) you can both define a subset of codecs that should be enabled and change the default order of priority between the selected codecs.2..” button in the right-hand field listing codecs.. 9 Every phone is by default allocated randomly to one of these classes. 280 .2.2.2.3. the phone will go into limited service mode.TEMS Investigation 14.011. Speech codecs When you click the “. MNC Define the target PLMN here. CAS Speech Codec For certain phone models (indicated in section 21. Classes 0 .1 User’s Manual 21.. 21. Note that this function can be meaningfully applied only if the SIM supports multiple PLMNs.2. CAS Access Class Here you can manipulate access class settings ( 3GPP 22. MCC.. Membership of these classes entitles a phone to make access attempts in various special situations. the user interface shown below appears..2. Check the classes that you want the phone to be a member of. If you lock on a PLMN that is not available. CAS Lock on PLMN You can lock the phone on a PLMN.. 15 21. specified by an MCC and MNC combination.

Number of adjacent channels Specify one or two channels.4. this is done in a regular property grid. Device Properties • Use the arrow buttons in the middle to move any codecs you want to disable from the Selected box to the Available box.0 281 . • For other phone models you can only select which codecs should be enabled. 21. NT12-7002 ver 1. By default all codecs are enabled.Chapter 21.2. GSM Adjacent Scan Phones capable of C/A measurements on hopping channels can be set to measure either one channel or two channels on each side of the carrier. see above. Those that you leave in the Selected box will remain enabled. Then use the arrow buttons on the right to adjust the order of priority for the selected codecs.2.

Normal: No effect on default behavior.5).TEMS Investigation 14.5. If the “barred” flag is set for a cell.1. ignoring cell barring.2. The inverted operation is also possible. Note: To apply this kind of lock.1 User’s Manual 21. 21. GSM Barred Cells Here you can alter the phone’s behavior in GSM idle mode with respect to barred cells. namely to prevent reselection to a specified channel set.2. Mode Normal: The phone will not camp on barred cells. Lock: The phone will be locked to the set of channels checked under ARFCNs. GSM Cell Selection When the phone is in idle mode. All cells allowed: The phone will camp on any cell. 282 .2. it can be locked to one channel or to a set of channels. this normally prevents the phone from accessing it. you must first lock the phone to the GSM RAT (see section 9.6.2. This inhibits all reselections to other channels. Prevent: The phone will be prevented from camping on the channels checked under ARFCNs.1. ARFCNs Control mode Check the channels you want to lock on or exclude. Only barred cells allowed: The phone will camp only on barred cells.12) and to a GSM band (see section 9. regardless of the signal strength and quality of neighboring cells.

7. Disable handover: The phone will be prevented from performing any handovers at all. Selecting a single channel forces handover to that channel. Force handover to a specified channel. The phone will then report no RxLev for these channels.Chapter 21. 21.2.2. you can do one of the following: • • Prevent handover to specified channels. Normal: No effect on default behavior. Specifically. This function can be used to force data transfer over GPRS rather than EDGE. The phone will then report a very high RxLev for any such cell. GSM EDGE Capability For EDGE-capable phones you can choose to disable the EDGE capability. GSM Handover When the phone is in dedicated mode. • NT12-7002 ver 1. Prevent: The phone will be prevented from performing handover to the channels checked under ARFCNs.8. Lock: The phone will be able perform handover only to the set of channels checked under ARFCNs. Disable handover altogether. ARFCNs Control mode Check the channels you want to prevent handover to or restrict handover to. No: EDGE disabled.0 283 . EDGE allowed Yes: EDGE enabled.2. a very low RxLev for the serving cell. Device Properties 21. and no RxLev for other neighboring cells.2. you can manipulate its handover behavior. or restrict handovers to a chosen channel set.

10.2. Click the browse button (marked “. see section 26. WCDMA Barred Cells Here you can modify the phone’s behavior with respect to accessing of barred. Discarded messages are colored red in the Layer 3 Messages window and tagged with a special note in the plain-text decoding.2.. Note: The UE must have been activated at least once for the full tree of Layer 3 message types to appear here.2. The phone can store up to 10 message types in its memory. In the dialog that appears. reserved.2.. Tx Power GSM 850 (dBm) (etc. select Discard here. 284 . Default/Discard Loaded Message types To enable the function. section 4. 21.TEMS Investigation 14. Regarding the latter. see  3GPP 45.1.005. check the types of Layer 3 message that you want to discard. and other cells: Normal No change from normal cell barring behavior. Number of Layer 3 message types selected under Message types.3.) Enter the desired new Tx Power in dBm for the GSM 850 MHz band.”). GSM Tx Power For each GSM frequency band you can specify a Tx Power value which will override the network allocated Tx Power.11.2.2.9. 21.1 User’s Manual 21. Layer 3 Messages For certain Sony Ericsson UEs you can discard Layer 3 messages of specified types.

Lock: The phone will be locked to the set of UARFCNs/scrambling codes that you select in the UARFCNs and Scrambling codes fields. NT12-7002 ver 1.2. WCDMA Cell Selection Here you can lock the UE to selected UARFCNs or scrambling codes in WCDMA.12. see  3GPP 25. WCDMA BLER Target For certain Sony Ericsson UEs you can override the BLER target set for the UE by the network. Only barred: The phone will only access barred cells. 21. Regarding the format of this value.2. 21. Only reserved for operator use: The phone will only access cells that are reserved for operator use.13. Control mode Normal: No effect on default behavior. also barred and reserved ones.2.331. Device Properties Mode All cells allowed: The phone will access any cell.0 285 . Only barred or reserved: The phone will only access cells that are barred or reserved.Chapter 21. in idle mode as well as connected mode.2. Only reserved for future use: The phone will only access cells that are reserved for future use. Only reserved: The phone will only access reserved cells. BLER Target value The BLER target for the UE will change to the value you set here.

2. These categories are defined in  3GPP 25. If HSUPA is enabled. Note: To apply this kind of lock.1a.12) and to a WCDMA band (see section 9.1. or all of HSPA. These categories are defined in  3GPP 25. you must first lock the phone to the WCDMA RAT (see section 9.1.1 User’s Manual Scrambling codes Lists the scrambling codes to lock on.2. you can set here what HSDPA (HS-DSCH) category the phone should report. Up to 32 target UARFCNs can be specified. Up to 32 SCs can then be listed as targets.14.5). you can enable or disable these capabilities. you must first have selected a single target UARFCN. even if the phone supports it). UARFCNs Check the UARFCN you want to lock to. If you have specified multiple target UARFCNs. table 5. 21.TEMS Investigation 14. WCDMA RRC Radio Capability For phones supporting HSDPA. you cannot add any target SCs (the Scrambling codes field is grayed). table 5. To be able to specify target SCs. However. HSUPA category 286 . note that if you list more than one UARFCN. you can set here what HSUPA (E-DCH) category the phone should report.306. HSDPA: HSDPA is enabled (but not HSUPA. Allowed technologies R99 only: Only WCDMA R99 is enabled. HSDPA category If HSDPA is enabled. you cannot also select scrambling codes as targets.1g. HSDPA + HSUPA: Both HSDPA and HSUPA are enabled.306.

The channel lock function works in idle mode only.3.0 287 .Chapter 21. Cell barring Normal: The phone will not camp on barred cells. 21. 21. GSM Cell Barring Control This setting governs how the phone behaves with respect to barred cells in GSM. 21.1. The phone will be locked to the chosen UARFCN and scrambling code. NT12-7002 ver 1. Reversed: The phone will camp only on barred cells. Specify the band containing the channel you want to lock on. Sector Lock Control (WCDMA) These settings apply in WCDMA mode. Enable sector lock UARFCN Scrambling code Set this to Yes to enable the sector lock function.3. Specify the UARFCN to lock on.3. ignoring cell barring. you can lock the phone to a single ARFCN.2. Properties of Nokia Phones (NTM3) Channel Lock Control (GSM) In GSM mode. Specify the ARFCN of the channel to lock on. Device Properties 21.3.3. Ignored: The phone will camp on any cell. Specify the scrambling code to lock on. Enable channel lock Band ARFCN Set this to Yes to enable the channel lock function.

TEMS Investigation 14. However. Please note that with this device. Properties of Qualcomm Chipset Based Devices Properties of Qualcomm chipset based devices are mostly limited to enabling and disabling of various logs. Regarding the NV (Nonvolatile) interface. you must enable all logs with “Vocoder Packet” in their names.4. see section 9.1. The “WCDMA RRC State” log must be turned on for the WCDMA RRC State element to receive a value at device connect/start of logfile. no RRC State is presented until the state changes. as explained in section 9.1 User’s Manual 21. If the log is turned off. 21. • • 288 . Properties Specific to Sony Ericsson Xperia arc S Sony Ericsson Xperia arc S has a log category “TEMS” containing some logs that affect the population of information elements: • The “GSM C/I” log must be turned on for the “C/I” family of elements in the GSM category to be populated. RAT lock and band lock functions are available. The “WCDMA SIR Target” log must be turned on for the WCDMA SIR Target element to be populated. C/I is obtained only for circuit-switched. This is true for the Sony Ericsson Xperia arc S as well.9.1. for certain devices such as Option data cards and Sierra Wireless UMTS data cards. not for packet-switched data. for this device all control functions are applied from the Navigator.1. For speech codec information elements to be populated.4.

Device Properties 21.Chapter 21. (The settings you make here do not affect the scope of All enabled. which always means all messages without restriction. LTE For each of these top-level message categories.) Please note that if you disable everything here. Properties of Samsung LTE Modems For Samsung LTE modems.6. NT12-7002 ver 1. no reports from the MS device channel will be displayed in TEMS Investigation. All disabled: All messages are disabled. Common. various message categories can be enabled and disabled. Select messages: When this option is chosen.5. 21. What properties are editable depends on what product you are using. Properties of GPS Units You can inspect and change some properties of a GPS unit.0 289 . the following options exist: All enabled: All messages are enabled. further fields appear which allow you to enable or disable various subcategories of messages.

chapter 7.4) as symbols and vertical lines in line charts (see section 29. Events TEMS Investigation generates events to indicate noteworthy occurrences in the cellular network. Regarding this window. see Information Elements and Events. Events can also be presented: • • • as symbols on the map (see section 31.1. in addition to these.4) as audio signals (see section 22.2. A number of events are predefined. • Setting Up a User-defined Event Open the Event Definition window. section 8. These expressions can contain: • • • Layer 3 messages other events conditions involving information elements. Presentation of Events Events that occur are listed in the Events window. 22. Click Add.1 User’s Manual 22. which trigger the event when they evaluate to true.8.5. User-defined events are specified by logical expressions. Predefined and User-defined Events Definitions of all predefined events are found in Information Elements and Events. 290 .5). you can define events of your own. 22.TEMS Investigation 14.3. 22.

the event is generated only once when its condition becomes true. the event is generated repeatedly as long as its condition is true. NT12-7002 ver 1. Interval You build up the event expression by using the add buttons on the right. the event is triggered only when the event expression is true for this particular device.0 291 . at intervals governed by the Interval parameter. If you choose a specific external device in this combo box. The choice in this combo box governs what will be selectable when you click the Add Element button. If Periodic is checked. If Periodic is not checked. the event can be triggered by any device. If you choose “Any”.4. Periodic. Events Name System Mobile Enter a name for your user-defined event.Chapter 22. This is especially useful for cell whitelist events: see section 22. The structure of the expression is displayed in the box beneath the Name field.

Choose a threshold operator (“=”. Choose this to trigger the event whenever the value of the selected information element changes.3. • Adding a Layer 3 Message to the Event Expression Click Add Element and choose Layer 3 from the context menu.1 User’s Manual 22. Choose this to trigger the event when the selected information element assumes. and set the threshold value. If the information element has an argument. 292 . • Adding an Information Element Criterion to the Event Expression Click Add Element and choose Information Element from the context menu. “>”. or “<”).1. 22. specify it here.3. or drops below a certain value.2. Information element Argument Value: Changed Value: Threshold Choose an information element. Choose the desired message from the dialog that appears. exceeds.TEMS Investigation 14.

3. Click Edit and make the desired changes.3. 22. Available operators are AND.5. XOR.3. and NOT. Events 22. the logfile must be reloaded for the events to become visible. NT12-7002 ver 1. In the new dialog that appears. Then click OK to exit the Add User Defined Events dialog. NOT. • • Editing User-defined Events Select the event you want to edit in the Event Definition window. • In the Add User Defined Events dialog. The new event is now added to the list in the Event Definition window. or XOR).7 below for an example of a logical expression.3. 22. click Add Element and choose Event from the context menu.3.4. choose an event from the combo box.3. OR.0 293 . 22. • • Adding an Event to the Event Expression In the Add User Defined Events dialog.6.Chapter 22. See section 22. Note: If a user-defined event is added or modified after a logfile is loaded. you will need logical operators and possibly delimiters (brackets). • Deleting User-defined Events Select the event you want to delete in the Event Definition window. Adding an Operator/Delimiter to the Event Expression To build a composite logical expression. Note: Events used in the expression for a user-defined event can be combined with the OR operator only (not with AND. Keep adding items to the event expression until it is complete. click Add Operator and select an operator or delimiter from the context menu.

1 User’s Manual • Click Delete. 6. Click Add Element and choose “Information Element”. Set Value to 10. Name the event “Noise Indication” (or whatever you like).7. but the fact that the signal is overwhelmed by assorted random disturbances – i. 2. Click Add Element and choose “Information Element” from the context menu. Set Value to –99. From the Configuration folder in the Navigator. This means thermal noise generated within the circuits of the phone as well as external background noise from a plethora of sources. Click Add. The event expression should now look as follows: 294 . 11. Click OK. Choose “Threshold”. 14. From the Add Information Element combo box. In certain circumstances. open the Event Definition window. 12. Under “Information Element” choose “RxLev Sub (dBm)”. 10. including other man-made signals so faint that they merely add up to a quasirandom disturbance. 1. 9.e.TEMS Investigation 14. Two common ones are co-channel and adjacent channel interference. 13. 3. Click OK. 8. the main problem is not interference from other callers. and choose “<” from the combo box. 5. 4. Example of User-defined Event This example is taken from GSM. There are many possible causes of poor C/I values. The following event gives a rough indication that the poor C/I is probably due to a noise problem: the poor C/I coincides with a very low signal strength. Choose “Threshold” and choose “<” from the combo box. choose “C/I Worst”. however.3. what is usually called “noise”. 22. Click Add Operator and choose “AND”. 7.

In the dialog that appears. This is useful in any scenario where testing is restricted to certain cells. emergency calls would be put through normally and are therefore forbidden. enter your list of cells according to the format description given in the Technical Reference.Chapter 22. Generating Cell Whitelist Events The Event Definition window has a special function for generating userdefined events based on cell lists. Outside of these cells.0 295 . Events C/I Worst < 10 AND RxLev Sub (dBm) < –99 15. A list of allowed cells is referred to in TEMS Investigation as a “whitelist”.4. For example. To construct your whitelist. 22. The purpose of this function is to provide a convenient means of alerting the user when entering a cell that belongs to a specified set. proceed as follows: Click the Cell Whitelist button. The input might look something like this: NT12-7002 ver 1. chapter 6. Click OK to finish. testing of an emergency service might be performed in cells which have been temporarily reconfigured to divert emergency calls to a different number (so that they do not interfere with genuine emergency calls). The event is now added to the event list and can be used in the Map window and in other presentation windows.

you can view the event expression in the same format as in the Cell Whitelist Generator dialog. click OK. From the cell whitelist TEMS Investigation now constructs a set of userdefined events: one for each RAT occurring in the whitelist. When you are done. However. a RAT designation will be appended (see below). The resulting event expression is not reproduced explicitly in the Event Definition window.TEMS Investigation 14. Whenever a connected device enters one of the cells on the list. if you select the event and click the Edit button. it is represented there by the string “<Compiled Whitelist Expression>”. The name and the periodicity (Interval setting) of a previously defined whitelist event can be changed when the event is inspected. the appropriate event will be triggered.1 User’s Manual • • You can change the event name if you wish. To the Event Name string. 296 . Please note that the whitelist event expression cannot be modified from here.1 1.

See section 20. This information can be utilized by a script to perform a certain task if the device is in a white cell.10. the Cell Whitelist Generator dialog does retain the contents it held when last closed.5.3 for further guidance on how to compose such scripts. when opened.Chapter 22. This is useful if you are performing a drive test on your own and need to keep your eyes on the road.6. Audio Indications for Events For each event you can specify an audio signal to be played when the event occurs. its contents are converted to an event and cannot subsequently be reverted to the whitelist format.5. 22. (However.0 297 . To associate events with audio signals. but skip the task otherwise. After you click OK in the Cell Whitelist Generator dialog. Events Whitelist events are automatically made periodic (Periodic option checked). you use the Audio Indications window found in the Configuration folder in the Navigator. so that they can provide continuous updates on whether or not the user is camping on a white cell.1. Adding Audio Indications Click Add in the Audio Indications window. NT12-7002 ver 1. Please keep in mind that the Cell Whitelist Generator functions as a “oneway” editing aid.) 22.

Click Apply to add the current audio indication and keep the dialog open. 298 .TEMS Investigation 14. Click OK when you are done adding audio indications. Choose an event. or click Browse and select the file. The events that are now associated with sounds are listed in the Audio Indications window.1 User’s Manual Mobile Event Sound Use PC speaker Test • • Choose an external device. Check to use the internal speaker of your PC. Enter the path to the WAV file you want to use. Listen to the selected sound file.

22.5. • Saving and Loading Audio Indications Select the audio indication you want to save.5.5. To re-enable all audio indications: Click Undo Mute All. To activate a deactivated audio indication: • Select the audio indication. • Deactivating Audio Indications To deactivate an audio indication: Select the audio indication. 22. 22.3.5. and deactivated ones will remain deactivated. You might find this attractive when doing post-processing.4.5. no audio indications will be played until you decide to enable them again. • Editing Audio Indications Select the audio indication to be edited. From now on.2. Click Edit and make the desired changes.0 299 . Events 22. independently of their status (active or deactivated): Click Mute All. Click Deactivate Sound.5. They may however be deactivated (see section 22. Activating Audio Indications Audio indications are by default active.Chapter 22. Muting All Audio Indications To disable all audio indications.4 below).6. NT12-7002 ver 1. Click Activate Sound. 22. The status of the audio indications will remain the same as before you clicked Mute All: active audio indications will start playing again.5.

Click Open to load an *.7.svt file in the Audio Indications window. Click Delete. • Deleting Audio Indications Select the audio indication to be deleted.TEMS Investigation 14. 300 .1 User’s Manual Click Save and enter a file name (extension .5. 22.svt).

events. 23. Data is presented in fundamentally the same way in both cases. Regarding predefined events.2.1. see Information Elements and Events. 24 25 26 27 28 29 30 NT12-7002 ver 1. either in real time or during logfile analysis. see Information Elements and Events. Presented Data The presentation windows are used to present information elements. Presentation: Basics 23. 23.Chapter 23. chapter 7. For an overview of information element categories. differences are noted whenever relevant in the chapters that follow. Full details on information elements follow in chapters 3 and 4 of that volume. Presentation: Basics This chapter covers the fundamentals of data presentation.0 301 . and messages. chapter 2. Types of Presentation Window The following presentation windows are available in TEMS Investigation: Window Type Status window Event Counter window Message window Video Monitor GPS window Line chart Bar chart Chapter Ref.

The EQ designations currently do not appear in presentation windows. 31 23.1 User’s Manual Window Type Map window Chapter Ref. 302 . as opposed to the Navigator and Service Control components. and choose the same item from the context menu.TEMS Investigation 14. Event Counter windows). Alternatively. for example. • • The change will affect all presentation windows that display data from a specified device (as opposed to.3. From the Worksheet menu. Device Channels: MS/DC/PS In presentation windows.1.3. Select the equipment (EQ/MS/DC) number in the dialog. devices are represented by their channels: • • • MS for radio measurements DC for data service measurements PS for positioning equipment. choose Set Equipment Number. 23. right-click any empty part of the worksheet. “Set Equipment Number” Function There is a shortcut for changing which device to present data from in an entire worksheet: • • Bring the worksheet of interest forward by clicking it.

Presentation: Basics 23. The exactness of the synchronization is limited by the time resolutions of the various presentations. but in many window types.4. things are somewhat different: it is still possible to inspect previously recorded data. Video Monitor) “history” windows. as soon as a new message arrives from the phone. it is drawn in black in graphical presentations and left out in textual presentations. or statistics on it (maps. In drive-testing mode. For example. When you select a point in time in a history window. see section 26.0 303 .5. Event Counter windows).5. for use in that window only. which show the situation at one instant in time and are constantly refreshed in drive testing mode (status windows. however. Regarding synchronization between message windows and other windows. These colors are defined in the Navigator. or has no color defined for its current value.3 for details. message windows. line charts. In status windows. it is possible to visualize numeric information element values by means of a range of colors. custom color ranges for information elements can be defined. • Window Updating and Synchronization A fundamental distinction can be made between “snapshot” windows. Whenever an information element is invalid. other history windows highlight the same time instant. whereas the snapshot windows are updated to show the data that was current at this time. the line chart plots two points every second. bar charts. see section 5. You can always turn off the color coding and use a fixed color for drawing. Color Ranges In many types of presentation windows. the presentation automatically reverts to the present time. Note: The above applies without qualifications in analysis mode. The map plots a maximum of two new theme markers every second. GPS window. which accumulate information and display the whole history of the testing session. NT12-7002 ver 1. 23. and • All windows are synchronized.Chapter 23.

and click it.1. (Open a new window if necessary. • • • Import To import a saved presentation window. Export/Import of Presentation Windows Status windows. saved along with all their current settings in a file separate from the workspace.6.7. and message windows can be exported. You can later import the window into the application again by opening the file. Select the desired file and click Open. 23. • • • Export To export a presentation window. maps. proceed as follows: Select the window. proceed as follows: Focus a presentation window of the same type as the one you want to import. see appendix B.2.) From the File menu. 304 . Type a file name and click Save. The extension depends on the window type.7. 23. Other Window Properties The appearance of any presentation window can be changed by altering the window properties. line charts. From the File menu.7. which are accessed by right-clicking in the window and choosing Properties from the context menu.1 User’s Manual 23. that is. choose Export. 23. choose Import.TEMS Investigation 14.

Status Windows 24. you can modify the window using the Properties dialog. NT12-7002 ver 1. To set up a status window.2).1. 24.3. use the setup wizard (section 24. See section 24. a blank template is available which you can use to compose your own status windows. Later on.0 305 . Note: Setting the number of columns and rows in the status window cannot be done with the setup wizard. 24. Setting Up Status Window Contents The contents of a status window are conveniently set up using the setup wizard. you cannot enter text in the status window using this tool.Chapter 24. General The status windows present information elements in tabular form.3. Status Windows This chapter explains the workings of status windows.2. Also. chapter 8. In addition. The setup wizard is intended to be run only once. these are listed in Information Elements and Events. For these purposes you must use the Properties dialog. which is described in section 24. A number of ready-made windows are provided for presenting particular categories of information.

click Add. To add an information element. Note that changing the name later will create a new status window.TEMS Investigation 14. Name Name the new status window. and the contents of the current window will be lost. Font • • Click Next to proceed to step 2 of the setup wizard. Click Browse and select a font. This dialog opens: 306 .1 User’s Manual • Right-click in the status window and choose Setup Wizard.

Enter an argument for the information element (if it needs one). Status Windows Mobile System Information element Argument Choose which device to pick the information element from. • Select the View tab. Choose an information element category.0 307 . Choose an information element. chapter 2. NT12-7002 ver 1.Chapter 24. See Information Elements and Events.

Check to display numeric values as colored bars. Choose alignment for the displayed values. This is useful for information elements that represent states. etc.6. 308 . you can visualize the thresholds “T-Add (dB)” and “T-Drop (dB)” as vertical black lines drawn on top of the bars in the Energy column.1 User’s Manual Value Left. See screenshot in section 24. Min/Max indicator Associated information elements Information Element 1 Information Element 2 • Select the Color tab to customize colors and color ranges. Keep track of the all-time-low and all-time-high values by means of vertical lines.TEMS Investigation 14. In that window. This checkbox with accompanying combo boxes is enabled only for the CDMA window Finger Info. Center. Right Bar Constant length Check to display values alphanumerically. Draw the bar with constant length.2. and can only assume a limited number of values.

Then exit the setup wizard by clicking Finish.3 for details on how to do this). • Changing Status Window Properties Right-click in the status window and choose Properties from the context menu.Chapter 24. Status Windows Use common color ranges Check the box if you want to use the default color range of the information element. uncheck the box and specify the range (see section 5. 24. If you want to define a special color range here. • • Click Apply to add more information elements.0 309 . Click OK when you are done adding information elements.3. The Mode tab governs the layout and appearance of the window: NT12-7002 ver 1.

Set the number of rows. (The contents of the header are defined on the Cell Content tab. Click Browse and select a font. (To pick individual information elements from a different device.TEMS Investigation 14.) Set the number of columns.) Columns Rows Font Mobile • To edit the contents of the status window. use the Cell Content tab. select the Cell Content tab. 310 . If you choose a device in this box. regardless of earlier settings. Check if you want a header in the window. all the information elements currently shown in the window will be taken from that device.1 User’s Manual Name Header Enter a new name if desired. See below.

Then click Edit.2 above). except that it has an extra field for entering text: NT12-7002 ver 1. Status Windows • Double-click on a row and select an information element from the list. The dialog that appears is identical with the Add dialog in the setup wizard (see section 24.0 311 .Chapter 24.

1 User’s Manual In a status window.TEMS Investigation 14. This feature is handy when the default window layout has a large number of rows. then selecting the desired percentage of the current font size. and modify headers and insert information elements on the Cell Content tab.5. you can optionally rearrange the data by dividing the rows into several groups (up to three) and displaying these groups side by side horizontally. multiple column groups reduce or eliminate the need for vertical scrolling. All columns are then repeated once or twice in the window. Changing the Status Window Font Size You can adjust the font size in the status window by right-clicking in the window and selecting Zoom. Use the In and Out options to step the font size up and 312 . To do this.4. Repeating Columns in Multiple Groups In status windows with a small number of columns (up to four). 24. • Right-click in the status window and select Column Group from the context menu. then select the desired number of column groups. you might want to show the same information element for several devices. 24. create new columns as needed on the Mode tab.

expressed as a number of radio subframes (5 ms).6. rows represent timeslots. and columns represent the leaves of the channelization code tree for the DPCH (i. 24. Non-standard Status Windows TD-SCDMA Physical Channel Monitor This window has a unique design and presents data on TD-SCDMA Dedicated Physical Channels (DPCHs). Repetition period: This is the DPCH repetition period on the downlink and uplink respectively.e. The numbers are to be read as follows: x  y = channelization code no. • – – NT12-7002 ver 1. If a code straddles multiple columns.1. • • In the top left corner is displayed the current Work UARFCN. The arrow shows the direction of transmission: up arrow (blue) = uplink.0 313 .Chapter 24. if the code takes up m columns. Specifically. A repetition period p means that the DPCH is transmitted in every pth subframe.6. 24. the spreading factor is 16/m. this means that the spreading factor for that timeslot is reduced. x out of the total number of channelization codes y in that timeslot (the latter being conditioned by the value of the spreading factor). In the grid. respectively. – A code in use in a timeslot is indicated by an entry in the corresponding row and column(s) in the grid. the number of codes available when the maximum spreading factor is used). The size of the window itself is not affected by these operations. down arrow (yellow) = downlink. Status Windows down.

1.6. CDMA Finger Info window with T-Add and T-Drop thresholds drawn as dashed vertical lines in the Energy column.1. as shown in the screenshot below. The color gray means that no valid ISCP measurement is available (which is always the case on the uplink).1 User’s Manual – Codes are colored according to the same rules as the information element “Timeslot ISCP (dBm)”. In this case.e.2 (View tab). 24.6. T-Add = –13 dB and T-Drop = –15 dB. the interference signal code power for the timeslot.TEMS Investigation 14. For the setup. CDMA Finger Info This window indicates the T-Add and T-Drop thresholds by means of a window-specific feature.2. Window Properties You can right-click in this window to select which devices to display data from. 314 . 24. see section 24. i.

See section 25. right-click in the window and choose Remove Tab from the context menu. right-click it to open its Properties dialog. right-click in the window and choose New Tab from the context menu. This way it can be transferred to a spreadsheet application or other suitable program. • • • To add a new tab.2.0 315 .1. a number of tabs are preconfigured. 25.1. In the Event Counter window provided under Presentation  Analysis. NT12-7002 ver 1.Chapter 25. To remove an existing tab. 25. Event Counter Windows An Event Counter window keeps track of the number of times a set of events have occurred. Event Counter Windows 25. What events to show is user-configurable. Window Tabs Tabs are provided in this window to allow grouping of events into categories.4. To rename a tab. Copying Window Contents You can copy the entire contents of a tab in an Event Counter window to the Windows clipboard.

25.4. • Changing Event Counter Window Contents and Properties Right-click in the Event Counter window and choose Properties from the context menu. Counters are reset automatically. move the events you want to display to the Selected Events list box. This resets all counters in all open Event Counter windows. Paste the copied selection into the desired application. which is user-editable. 25.4. The event counting in the window is done in a separate column for each selected device. The General tab also holds the window title. A Total column is also provided which adds up the number of events from all selected devices.TEMS Investigation 14. 25. General Tab On this tab you choose which devices to show events from. 25.1 User’s Manual • • Right-click the tab and choose Copy to Clipboard from the context menu. 316 . Resetting Event Counter Windows The counters in an Event Counter window can be reset by the user at any time by right-clicking in the window and choosing Reset Event Counter Windows. Events Tab Here you choose which event types to display on the currently active tab (the tab from which you access the Properties dialog). in both drive testing mode and analysis mode: • • when a new logfile is opened when a logfile is closed.4. • Using the arrow buttons.1.2.3.

26. right-click in the window and choose Properties. The tab also holds the window title. NT12-7002 ver 1. 26. and error reports). which is user-editable. General Tab On this tab you choose which devices to show messages from. Message Windows The message windows are used to list messages and reports received or transmitted by external devices (Layer 2 and Layer 3 messages. • Changing Message Window Contents and Properties To access the message window Properties dialog.0 317 .Chapter 26. They are also used to present events generated by TEMS Investigation.1.1. chapter 8. Preconfigured message windows are listed in Information Elements and Events. MS and DC channels are distinguished. mode reports. Message Windows 26.1.

1. Event & Message Symbols: Event icon or arrow showing message direction (both types of symbol being placed in the same column).1.2.TEMS Investigation 14. The item Mode Reports  Sony Ericsson  Legacy Reports contains mode reports originating from certain older Sony Ericsson GSM phones that are no longer offered for sale with TEMS Investigation. the checkbox next to the category is shaded gray. you must select it on this tab in order for it to display in the message window. Message Name: Name of message or event. first move “Information Element” to the Selected Columns box.3). Information Element: Value of a user-selected information element. Message Info: Message or event information. move the events you want to display to the Selected Events list box.3. Messages Tab Here you choose which message categories to display in the window. 318 . Any type of event can always be shown. • Events Tab Here you choose which events to display in the message window. If at least one item in a category has been deselected.1. Using the arrow buttons.1 User’s Manual 26. 26. To select the element. 26. The ready-made windows are preconfigured in this regard. Message Symbols: Arrow showing message direction.4. Event Symbols: Event icon. • • • • • • • • Columns Tab Here you decide which columns to include in the message window: Equipment: The device that delivered the message. regardless of the nature of the messages. A new dialog now appears where you select what information element to display. Mobile System: The wireless technology from which the message originates. then select this item and click Edit. Note that if you add a user-defined event (section 22.

Plain-text Message Decoding In all message windows. The new window now becomes the active one. The old window will remain open. the second message will replace the first in the Layer 3 detail window. you can double-click a message to open a new window detailing the contents of the message. right-click the message and choose New Detail Window. The message windows are then updated according to the following rules: NT12-7002 ver 1. 26. Suppose.2. Presentation of Discarded Messages Layer 3 messages (from certain Sony Ericsson phones) that have been discarded according to the settings on the phone property page (see section 21.3. for example. Message Window Catch-up If you open a new message window when in drive testing mode. you can make the window catch up by right-clicking it and choosing Reload. Further.0 319 . However. then right-clicking in the window and choosing Copy from the context menu. but its contents will not change any further.Chapter 26. To abort the reload procedure. Protocol: The protocol to which the message belongs.5. To open a message in a new window. For example. the new window will not load any messages (for performance reasons).2.10) are highlighted in red in the Layer 3 Messages window.2. You can copy text from this window to the Windows clipboard by selecting the text. one or more rows are selected (colored) in each message window. that you just clicked somewhere in a line chart. when you have deactivated all external devices. an explanatory string is added to the plain-text decoding of such messages. Message Window Synchronization When message windows synchronize with each other and with other presentation windows. 26.4. 26. Message Windows • • Time: Timestamp of message. 26. right-click again and choose Cancel Reload. Each message window normally reuses a single detail window. if you double-click one Layer 3 message and then another.

The window will then stop updating.6. If several rows match equally well (for example. 320 . Freezing a Message Window This section applies to drive testing mode only. a message and one or several events triggered by that message). Searching. and Highlighting in Message Windows A number of functions for filtering.7. and its message flow is halted. You can unfreeze the window in any of the following ways: • • • by dragging its scroll bar by right-clicking the scroll bar and choosing Bottom by pressing the End key on the keyboard. 26. You can freeze a message window by clicking an arbitrary message. The freeze affects only the message window you clicked in. If the user-selected item and the message window selection belong to the same air interface message.) • 26. the message window selection is colored blue. not any other windows.1 User’s Manual • If one message window row matches the user-selected item better than any other.7. searching.TEMS Investigation 14. Filtering Functions These are found under Show/Hide in the context menu. that row alone will be selected. If there is no such exact correspondence. Filtering. and highlighting message window contents are available from the message window context menu. the row or rows immediately preceding the user-selected item are selected and colored gray.1. (If no such rows exist. 26. nothing is selected in the window. all these rows are selected.

NT12-7002 ver 1. Find previous message of this type: Finds the previous message of the same type as the one selected (going backward in time). • • • • Search Functions These are found under Search in the context menu.0 321 . hiding all messages with the same log code/name as the selected message.Chapter 26.2. Message Windows • • • Show only messages of this type: Reloads window contents to show only messages with the same log code/name as the selected message. Hide messages of this type: Reloads window contents. 26. Search for message: Opens a dialog Message Search which is explained below.7. Search again: Repeats the search last performed in the Message Search dialog. Undo: Undoes a “show only” or “hide” command that is currently in force and reverts to unfiltered presentation. Find next message of this type: Finds the next message of the same type as the one selected (going forward in time).

Also look for matches in (plain-text decoded) the message contents.1 User’s Manual Message Search Dialog Find what String to match in message header (and also in its contents.TEMS Investigation 14. Only match items with casing that exactly matches the search string. “UL” matches “ULDCCH” but not “Scheduling”. For example. As you type text in this field. The latter is the default. By default only the message header is searched. from which you can optionally make a selection. 26. Match case Match whole word Search up Also search message contents • Click Find Next (or press the right arrow key) to go to the next message matching the search criteria. This action is equivalent to the Search again command on the context menu.7. a dropdown is continuously updated with matching message names. if the Also search message contents option is checked). Only match items where the search string occurs as a whole word. Search backward (up) instead of forward (down) in the message flow.3. Highlighting Functions These are found under Highlight in the context menu. 322 .

NT12-7002 ver 1. 26. • 26. Multiple highlights can be applied. Message Windows • Color bars: Select a color in which to highlight all messages of the same type as the selected message.Chapter 26. with different colors representing different message types. See the example below. Window-specific Features Mode Reports Window In the General window.8.0 323 .8. you can adjust the updating frequency (in the TEMS Investigation application) for List Search reports from Qualcomm-based terminals.1. under WCDMA. None: Removes the highlighting (if any) for all messages of the selected type.

1. 324 . the first is used. How to Test Video Streaming To test the video streaming service. All phones sold with TEMS Investigation 14.TEMS Investigation 14.6. and various forms of live streaming (such as tapping into a live stream or repeating playlist delivered by a streaming server). 27. This value should indicate the bit rate of the stream (video + audio). The mechanics of setting up and conducting a streaming session are handled by the Streaming activity in scripts: see section 20.1 User’s Manual 27. Video clips suitable for testing are supplied on the installation CD in the subdirectory Video Clips. where a video clip of known length is downloaded. The application supports both on-demand streaming. the VSQI algorithm (see chapter 40) will use a bit rate value received from the server.4. The application is equipped with a built-in streaming video client which has been designed to imitate as closely as possible the corresponding client software found in phones. If you are using files of your own for testing streaming. the file names should contain a numeric value followed by “kbps”. where the duration of the streaming session is specified by the user. not counting overhead.1 possess this capability. Video Streaming and the Video Monitor TEMS Investigation supports streaming of video recordings via suitable connected devices. A readme file in this directory explains the file name syntax used and gives reference VSQI values obtained for these video clips in clean conditions. you need a phone capable of handling this service. but the VSQI score will then be less accurate. If the file name does not contain a numeric value.16. If multiple numeric values are given in the file name.

0 325 . NT12-7002 ver 1. you use the Video Monitor window: Only one instance of the Video Monitor can be open.) 27. Video Streaming and the Video Monitor 27.2. (On the other hand.Chapter 27.2. • Properties of the Video Monitor Right-click in the Video Monitor to access its Properties dialog: Device Enable audio Here you select the device that delivers the video stream.1. Check this box to play the streamed audio through the PC speakers. so only one video stream can be replayed at a time. it is perfectly possible to do streaming with several phones simultaneously and monitor information elements and events for all these sessions in other presentation windows. The Video Monitor To display the streamed video clip.

See Information Elements and Events. Streaming Intermediate VSQI: VSQI (Video Streaming Quality Index) is a quality measure developed specifically for estimating the viewerperceived video and audio quality of a video streaming session. RTSP. and RTCP protocols in the IP Protocol Reports window.4.8.TEMS Investigation 14.3. • • Troubleshooting Video Streaming UDP ports for video streaming must be free. Information element Streaming MTQI and event Streaming Quality MTQI: MTQI (Mobile TV Quality Index) is a refinement of VSQI which is discussed in chapter 41. you can monitor the message traffic over the RTP. “Video Streaming Quality Measurement with VSQI”. section 8.8. Evaluating Video Streaming Performance Throughput and other performance measures for video streaming are presented in the “Streaming” information elements belonging to the Data category. is found on the installation CD in the subdirectory Documents. It appraises video quality only. The function cannot be used if RTP or UDP traffic to and from the Internet is blocked (intentionally by the operator.2. section 7. Data on which video streaming KPIs are based is delivered in the form of KPI events. or for whatever reason).8. This paper. section 3. section 8. • 326 . VSQI is also the subject of a technical paper which includes general discussions of video streaming as well as video quality measurement.1 User’s Manual 27. since the received signal is presented in real time in TEMS Investigation. Event Streaming State: This event is provided for monitoring the activities of the streaming video client. • • • 27. Testing of video streaming with TEMS Investigation requires that RTP/ UDP traffic can be run with the phone used as modem. For close-up scrutiny and troubleshooting of the video streaming service. Some of these data items deserve special comment: • Information element Streaming Packet Loss: Packet loss is of particular interest for streaming. See the Getting Started Manual. see Information Elements and Events. See Information Elements and Events. It is described in more detail in chapter 40.4. Information element Streaming VSQI and events Streaming Quality VSQI.

Exactly what data is displayed depends on the type of GPS. The GPS Window This window shows data from the GPS unit.5).0 327 . Changing GPS Window Properties The GPS window can be configured to show only the parameters that interest you: NT12-7002 ver 1. the window shows data from the one currently selected as “Preferred” (see section 8.1.Chapter 28. below is an example: The fix source is one of the following: • • • • • • • • • 2D 2D with DGPS (Differential GPS) 2D: SPS Mode (Standard Positioning Service) 2D: PPS Mode (Precise Positioning Service) 3D 3D with DGPS 3D: SPS Mode 3D: PPS Mode DR (Dead Reckoning) 28. If several GPS units have been detected by TEMS Investigation. The GPS Window 28.

and the number of satellites seen. 328 . This option exists to allow presentation of positions incorrectly regarded by the GPS as invalid.1 Choose km/h or mph. Check to also plot samples whose position is labeled as invalid by the GPS unit.TEMS Investigation 14. Heading Show invalid positions 1. graphically and numerically. altitude and speed of the GPS unit. Check to show the direction of travel. Choose meters or feet. the fix source. longitude.1 User’s Manual Units Tab Speed Altitude View Tab Basic Check to show the latitude. in degrees clockwise from north.

Line Charts 29. Line Charts In line charts you can plot numeric information elements in order to visualize how their values evolve over time. Line charts can also present events. showing the scales for the plotted information elements NT12-7002 ver 1.Chapter 29.1. 29. Preconfigured line charts are listed in Information Elements and Events. containing the charts themselves a Y-axis pane for each chart. Organization of the Line Chart Window Chart pane Chart pane Legend pane Additional Information pane Y-axis pane The Line Chart is subdivided into the following panes: • • one or several Chart panes.0 329 . chapter 8.

4). Events are indicated by thin vertical lines accompanied by a symbol identifying the event type. The Chart pane is synchronized with the Legend and Additional Information panes (as well as with all other open presentation windows. To see the names of the events. describing the nature and origin of the information elements shown. displaying arbitrary information elements in textual format. 29. just click in the chart. The plotting can be done either as a curve or in the form of successive vertical bars. During logfile analysis. you can freeze the line chart by clicking the Hold button. clicking in the Chart pane displays details on the selected time instant in the two text panes. The symbols used for predefined events are given in Information Elements and Events. Contents of the Line Chart Panes The Chart Pane The information elements that can be plotted in a line chart are chiefly measurements of physical quantities. In the chart. To select a new point in time. chapter 7. You can also move backwards and forwards in a logfiles segment with the left and right arrow keys on your keyboard. a thick vertical line indicates the point in time currently selected in the presentation. and indicating their values at a single point in time an Additional Information pane. 330 . While recording. as explained in section 23.TEMS Investigation 14. A maximum of four charts can be accommodated. The legend can only gloss one chart at a time. so neither the text panes nor other presentation windows will be updated. open an Events window. along with their associated Y-axis panes. Clicking the button once more (now labeled Release) makes the chart catch up with the presentation in the other windows. The relative sizes of the panes can be freely adjusted by dragging the interior frame handles. Scrolling the chart by means of the scroll bar does not change the time instant selected.1 User’s Manual • • a Legend pane.2.

NT12-7002 ver 1. the color coding of the chart is explained. The Legend Pane In the legend full details are provided (for one chart at a time) on the information elements plotted for the currently selected time instant.). as described in section 29. [U]ARFCN. right-click anywhere in the Line Chart window and choose the desired Legend Chart item from the context menu. and so is not labeled with a unit of time. Line Charts The Y-axis Pane The Y-axis pane associated with a chart shows the scales of the information elements plotted there. The scales can be changed. elements which cannot be plotted). At the extreme left in the legend.3. as long as contents have only been defined for one single chart. 29. PN) associated with elements are given in columns of their own wherever possible. but the length of this gap might not be equivalent to the period of time with no service. Parameters (SC/BSIC. The Additional Information Pane This is a sort of status window where an arbitrary set of information elements can be displayed (for example. To focus the legend on a different chart. as a rule of thumb.Chapter 29. Time Scale The horizontal axis of the line chart does not have an exact time scale. two points are plotted each second both in idle and dedicated mode.3 (“Upper visible limit”. etc.4. If the phone spends some time in GSM no service mode. Each scale is drawn in the same color as the information element. You can choose different contents in this pane for different charts. there will be a gap in the chart to show this.4 under Additional Information Tab. see section 29. you can scroll between scales using the arrow buttons. However.0 331 . However. If the pane is too narrow to show all scales at once. this data will be shown in the pane regardless of which chart the legend currently refers to. except when several elements share the same scale. in which case the scale is black.

• • Editing the Contents of a Chart Select the chart you want to edit in the list box. This dialog appears: 332 . click Add Chart. 29. 29. right-click anywhere in the Line Chart window and choose Properties.3.1. Editing General Properties of a Chart On the General tab of the Line Chart Properties dialog.4. Adding Charts • To add a new chart in the Line Chart window.1 User’s Manual 29.4. you can edit the line chart window name and deselect the horizontal grid lines which by default are drawn in the background. 29. Changing Line Chart Contents and Properties To edit the contents of the line chart and their presentation.TEMS Investigation 14.2.4. Click Edit Chart.4.

frequency and channel numbers. scrambling code indices. it will be picked from the device the line chart is drawn for (see the title bar. A maximum of seven elements can be presented. • • First select information element category in the System combo box. Using the arrow buttons.g. one of two things will happen: • • if the element has an argument. and the value with the next higher argument is shown. chapter 2. NT12-7002 ver 1. move the elements you want to present from the Available IEs to the Selected IEs list box. If you move the same element to Selected IEs again. From elements with an argument the value with the lowest argument is picked. the element is taken from the next device. Flags.0 333 . otherwise. it is taken from the same device as before. and the like cannot be plotted. See Information Elements and Events. You can use the Ctrl and Shift keys to select multiple items in the boxes. The first time you move an information element to Selected IEs. Line Charts Information Elements Tab Here you edit the set of information elements to plot and how to present them. The information elements that can be plotted are chiefly those that represent or are derived from measured physical quantities (e.Chapter 29. for the Line Chart template it is MS1). timeslot indicators. signal strength).

4. You can adjust the line width. In the ensuing dialog you also customize the presentation of the information element: Mobile The device to pick the information element from.1 User’s Manual Naturally. If it is chosen. the neighbor ranking) changes. Color: Fixed 334 . the MS and argument can also be edited directly at any time.TEMS Investigation 14. and consists simply in your selecting one fixed color yourself. Choose this if you want the element to be plotted as a line. the application automatically assigns a color on the basis of what channel is shown. Choose this if you want the element to be plotted as successive. neighbors. This option is available only for elements made up of sorted channel lists (e. scanned channels). As far as possible.g.4. IE Argument Style: Bar Style: Line Color: Assigned to channel The argument (if any) of the information element. See section 29.g. one and the same color is used throughout for a given channel. The point of this is to ensure that you can easily see when the sort order of the list (e. tightly packed vertical bars. Note that it is possible to change the device for all chosen elements at once. This is done by clicking the Edit IE button. This option is available for all elements.

Lower limit of the value range shown for this information element. the limit is automatically changed for all other arguments as well. Line Charts Upper visible limit for IE Upper limit of the value range shown for this information element. The image file used to label the vertical line indicating the event. If you check this box. move the event you want to present to the Selected Events list box. Clicking the Edit Event button pops up the following dialog: Mobile Symbol The device to pick the event from. it will be picked from the device the line chart is drawn for (see the title bar).Chapter 29.) Lower visible limit for IE Draw threshold line at Change color in dedicated mode Events Tab Here you decide which events should appear in the line chart presentation. Check this if you want to compare the plotted values with a threshold line drawn at a specified value. This setting works the same way as Upper visible limit for IE. the plot color turns deeper when the phone enters dedicated mode. • Using the arrow buttons. That is. NT12-7002 ver 1.0 335 . it is taken from the next device. The first time you move an element to Selected Events. and the brighter color chosen in the Color box is reserved for idle mode. (The dedicated mode color is not usercustomizable. this setting adjusts the range in the Y-axis pane. If you move the same element to Selected Events again. For complex information elements.

4. 29.) 29. 336 . select the device to pick data from. Presenting Data from a Different Device If you want to present the same data as before in a chart but from a different device.TEMS Investigation 14.7. • Deleting a Chart In the Line Chart Properties dialog.5.1 User’s Manual Additional Information Tab Here you choose the information elements to view in the Additional Information pane. except that here any information element can be selected.4.3. 29.lch. select the chart you want to delete and click the Delete Chart button. See section 23.5. since the additional information is presented only as text and not graphically. Clicking the Edit IE button in this case only enables you to change the device and argument. A shortcut is therefore provided for this operation. Exporting the Line Chart Window The line chart window can be exported separately to a file with extension .4. (The information elements and events selected in the charts will be unchanged.4. it is impractical to edit the MS field for each information element separately as described in section 29. From the context menu. This tab works exactly like the Information Elements tab. • Right-click in the Line Chart window. choose Change MS: • For each chart.

Bar Charts 30.Chapter 30. NT12-7002 ver 1. chapter 8. but the chart itself is generic and can present any measurement data. One of these is a parallel coordinates presentation. The bar chart is especially suited to the presentation of frequency scans.0 337 . Preconfigured bar charts are listed in Information Elements and Events. Bar Charts Bar charts are used to view successive snapshots in time of a selected set of information elements. The bar chart has a number of presentation modes. which is strictly speaking a different means of visualization but is integrated into the bar chart window.

along with their associated Y-axis panes. and indicating their current values an Additional Information pane. The legend can only gloss one chart at a time.TEMS Investigation 14. displaying labels for the bars drawn a Y-axis pane for each chart. showing the scales for the displayed information elements a Legend pane. 338 . displaying arbitrary information elements in textual format.1. A maximum of four charts can be accommodated. containing the charts themselves a X-axis pane.1 User’s Manual 30. Organization of the Bar Chart Window Chart pane X-axis pane Legend pane Additional Information pane Y-axis pane The bar chart is subdivided into the following panes: • • • • • one or several Chart panes. describing the nature and origin of the information elements shown. The relative sizes of the panes can be freely adjusted by dragging the interior frame handles.

just click in that chart.4. just click once more on the bar. Each scale is drawn in the same color as the information element.2. section 30. but they can also show the value of an information element or consist of arbitrary text.2. The Chart pane is synchronized with the Legend and Additional Information panes. To reset the max and min indicators. in which case the scale is black. If the pane is too narrow to show all scales at once.g. At the extreme left in the legend. for instance. one indicating transmit power). as well as with all other open presentation windows.4. Clicking a bar displays max and min indicators. The value range visible on the y-axis can be changed. see. The Y-axis Pane Along the y-axis of a chart are shown the scales of the information elements plotted there. The (U)ARFCN and SC/BSIC are left out if they are not directly relevant to an element (e. By default the labels are simply consecutive numbers.4. To refocus the legend on a different chart.1 (Visible limit for IE). Bar Charts 30. you can scroll between scales using the arrow buttons. The Legend Pane In the legend full details are provided (for one chart at a time) on the information elements displayed in that chart.1. which will from then on keep track of the maximum and minimum values assumed by this parameter since the bar was clicked.Chapter 30.0 339 . as explained in section 23. The X-axis Pane The X-axis pane provides labels for the data distributed on the x-axis (for one chart at a time). NT12-7002 ver 1. See section 30. the color coding of the chart is explained. Contents of the Bar Chart Panes The Chart Pane The information elements that can be plotted in a bar chart are chiefly measurements of physical quantities. except when several elements share the same scale.

You can choose different contents in this pane for different charts.3.1 User’s Manual The Additional Information Pane This is a sort of status window where an arbitrary set of information elements can be displayed (for example.3. • Deleting a Chart To delete a chart: In the Bar Chart Properties dialog.2.TEMS Investigation 14. 30.1. 340 . 30. Setting Up General Bar Chart Properties To set up some general properties of the bar chart and its presentation. rightclick anywhere in the bar chart window and choose Properties.3.4. as described in section 30. elements which cannot be drawn in a bar chart). select the chart you want to delete and click the Delete button. Adding Charts To add a new chart in the bar chart window: • Click Add. 30.3.

4. you can edit the bar chart window name and specify that horizontal grid lines should be drawn in the background. You will now work through a sequence of three dialogs.3. Examples of bar chart presentations are found in section 30. • • Setting Up Bar Chart Contents In the Bar Chart Properties dialog.4.Chapter 30.0 341 .3. Bar Charts 30. what data to display in the Additional Information pane. select the chart you want to set up in the list box.3. Editing General Properties of a Chart On the General tab of the Bar Chart Properties dialog. what interval to show on the x-axis. and how to present it 2. 30.4. and how to label it 3. The procedures are gone through in detail in sections 30.1–30. Click Edit. The first dialog that appears is this: NT12-7002 ver 1. what data to plot in the chart.5. In doing so you specify 1.

4. channel numbers. quality measures).1.) The default color range is defined in the Navigator and is dependent on the information element value (see section 5.1 User’s Manual 30.3). or a set of components of complex information elements. Flags. are chosen. Presentation Mode.TEMS Investigation 14. and the like cannot be displayed. Colors: You can always keep the default color range for the information elements. • 342 . (Which choice is available depends on the presentation mode. window-specific colors. fixed. or to use predefined. The information elements that can be displayed are chiefly those that represent or are derived from measured physical quantities (e. These fundamental presentation modes are offered: – – – • Bar chart: Single IE with multiple components Bar chart: Components from multiple IEs (fixed set) Parallel coordinates presentation/Stacked bar chart Data: One or several information elements. signal strength. Colors In this step you select the following (full details on subsequent pages): • Presentation mode. Besides. timeslot indicators. Data.g. The bar chart is very flexible in that it can be configured in a variety of ways. there is one other option: either to define your own colors for use in the bar chart.

Chapter 30. Bar Charts 30. i. NT12-7002 ver 1. The element must be one with arguments. select Bar chart: Single IE with multiple components.2.0 343 .1. • • In the Edit Chart dialog. Max The visible range of the information element. Single IE Presentation Mode In this mode a single information element is displayed.e. Click Choose IE to select an information element: The item contained in each element indicates what the visible range of the element will be in the bar chart. by making it dependent on another (suitably chosen) information element: see section 30. If you want to change these settings: • Double-click the item (or click the Edit button): Visible limit for IE: Min. By default this range is equal to the native range of the element (as stated in the Range/Unit column in Information Elements and Events). one which consists of several components.4.4. and whether the scale will be flipped with the lowest value at the top.1. It is possible to dynamically adjust the number of components to show.

decide what colors should be used in the chart. check the Use common colors box. To set up this presentation. Select Bar chart: Multiple IE components (fixed set). Define one fixed color to be used throughout in this chart.5. To keep the default colors. proceed as follows: • First decide whether you want to use the default color ranges of the information elements or define a fixed color for each element. Multiple IE Components Presentation Mode This mode displays an arbitrary fixed set of information element components. Click OK in the Choose Information Element dialog. then click OK. Click Choose IEs to select your data. You will then be prompted to define colors later on. check the Use common colors box in the Edit Chart dialog. To this end. Check this if you want to flip the y-axis for this information element so that the lowest value is at the top and the highest at the bottom.1.4. • • • Make your changes.2. 30. uncheck it. • Now click Next to proceed to the next step. see section 30. uncheck Use common colors and select a color in the box next to the information element.1 User’s Manual MS Flip scale The device from which to pick the information element. To do this. You have two options: – – Keep the default color range for the information element. For an example of a Single IE presentation. Back in the Edit Chart dialog. This dialog appears: • • 344 . Otherwise.TEMS Investigation 14. disregarding the default color range.

Bar Charts Here. a varying number of information elements may already be listed. NT12-7002 ver 1. click the button in the IE column. click the Add button. For each index you select one piece of data: an information element with no arguments. If you have checked Use common colors. depending on the type of bar chart concerned (template or predefined. the Choose Information Element dialog appears: • Select an information element. etc. or one component of an element having arguments.). an index on the x-axis).e.0 345 . • To specify the data that should be represented by a bar (i. in the relevant table row. To add a new bar. A new row will then be inserted at the bottom of the table once the contents of the bar have been specified.Chapter 30. In either case. the Color column will be absent from this dialog.

You can select all rows with Ctrl + A. • • For an example of a Multiple IE Components presentation. Pick a color and click OK. pick an argument.TEMS Investigation 14. To the IE for Fixed Layout dialog is now added the data item and color defined for the selected index. The indices of the removed rows disappear from the table. 346 . but when you exit the dialog all items will be renumbered starting at 1.1. When you are done specifying the bar chart contents. The standard Windows color dialog appears. click OK to return to the Edit Chart dialog. Click OK to exit the Edit IE dialog. and click Remove.1 User’s Manual • Double-click the item (or click the Edit button): • • • • • Specify range and scale properties. see section 30. as described for the Single IE presentation mode (see section 30. select the corresponding rows in the table. If the information element is one with arguments. Click OK in the Choose Information Element dialog.1). Click Next to proceed to the next step.5. you are now prompted to define a color for this data item.4. If you have unchecked Use common colors. The table will look something like this: • To remove items from the bar chart.

3.1. and connects with a line each set of components that have the same argument: arg 0 arg 1 arg 2 IEs NT12-7002 ver 1. and arguments are displayed in the y-direction. this arrangement may be reversed (one bar for each argument.4. It has the following fundamental properties: • • A set of information elements is shown. and an arbitrary number of components of each element may be shown at the same time. Each information element may have arguments. all its components being stacked on top of each other: arg 2 arg 1 arg 0 IEs Optionally. • In the stacked bar chart. information elements stacked). it plots all components of each information element on the y-axis. Rather. Bar Charts 30. There are two graphical representations of the above (conceptually quite distinct): a stacked bar chart and a parallel coordinates presentation. The parallel coordinates presentation does not use bars and is thus not a bar chart in the literal sense. one composite bar is drawn for each information element. Parallel Coordinates/Stacked Bar Chart Presentation Mode This presentation mode is the most complex one. at a fixed x-axis coordinate. The information elements are distributed on the x-axis.0 347 .Chapter 30.

etc. proceed as follows: • Select Parallel coordinates (default) / Stacked bar chart. make these settings: Do not uncheck IEs on x-axis. check the Stacked bar chart box: • Uncheck IEs on x-axis. Selecting Data After deciding the basic properties of the presentation: • Click Choose IEs to select your data. are distributed on the x-axis. This dialog appears: Here.TEMS Investigation 14. If you want a stacked bar chart instead. such a presentation is possible but hardly has any natural interpretation within the TEMS Investigation framework. a varying number of information elements may already be listed. arguments stacked. 348 . Setting Up Basic Properties of the Presentation To set up this presentation. rather than information elements. If you want a parallel coordinates presentation. depending on the type of bar chart concerned (template or predefined.1 User’s Manual The parallel coordinates presentation is selected by default in this mode. arguments stacked if you want to reverse the roles of the axes so that arguments.).

Double-click the item (or click the Edit button): • Specify range and scale properties. as described for the Single IE presentation mode (see section 30. click the corresponding button. Click OK in the Choose Information Element dialog. Bar Charts • To specify the details of how an information element should be presented.4.1).1. • • Select an information element. Note: The y-axis scales look the same also for stacked bar charts. click Add.0 349 . • • Click OK to exit the Edit IE dialog. despite the fact that the bar segments (except the bottom one) will be displaced in relation to the scale bar. A new row will then be inserted at the bottom of the table once the details have been specified. the Choose Information Element dialog appears. To add a new information element. NT12-7002 ver 1. In either case.Chapter 30.

When you are done specifying the bar chart contents.TEMS Investigation 14. • Finally.5. The colors are chosen by the application and cannot be edited. one for each argument. To this end. dialog is now added the data item defined for the selected index. . The indices of the removed rows disappear from the table. When you are done: • For an example of a Parallel Coordinates/Stacked Bar Chart presentation.. For example: • To remove information elements from the bar chart. You have two options: • • Keep the default color ranges for the information elements. Use fixed colors. Click Next to proceed to the next step. Choose this option by unchecking Use common colors. Coord.1 User’s Manual To the IEs for Par. see section 30. You can select all rows with Ctrl + A. select the corresponding rows in the table and click Remove. but when you exit the dialog all items will be renumbered starting at 1.. you need to decide what colors should be used in the chart. check the Use common colors box. 350 . click OK to return to the Edit Chart dialog.

so that accepting the defaults will cause all data to be shown. The default values in the boxes are dependent on the data selected in the previous step. Choose Set by IE to have the interval dynamically governed by an information element.Chapter 30. • Choose Fixed to set an unchanging interval. Note that this is done independently of the data selected in the preceding step. This element must denote the current number of something in order to make sense. Interval The interval selected here governs what portion of the x-axis will be visible in the bar chart.4. e. Example: If you want to display scan data.g.2. Bar Charts 30. and only such elements are selectable.0 351 . (Optional) Specifying text labels on the x-axis instead of the default numeric indices. Interval and Labeling In this step you take care of the following: • • Indicating the interval to show on the x-axis. Scanned RxLev. it may be a good idea to have the interval governed by Scanned Channels No Of. Then the number of indices on the axis will always be • NT12-7002 ver 1.

you might want to label the x-axis with the neighbor cell names.4. but since the additional information is presented only as text and not graphically. A dialog appears where you enter a string for each index.4.. check Text labels on axis. either those given under Fixed or the arguments of the information element chosen under Set by IE. you can replace the numbering with text labels. There are two options: • 30. Note: The Set by IE option is disabled for the Multiple IE Components presentation. found in the information element Neighbor Cell Name. Select Text strings from IE to pick labels from a text-format information element.3.TEMS Investigation 14. Additional Information Here you choose the information elements to view in the Additional Information pane. Example: If you want to display data on neighbors.4.1 User’s Manual equal to the number of channels currently scanned.4. and the space available in the chart will be fully utilized at all times. • • To enable user-defined text labels. the bar width being adapted continuously. • • any information element can be selected clicking the Edit IE button only enables you to change the device and argument. Alternatively. 30. Select User-defined text labels to specify arbitrary text as labels. Presenting Data from a Different Device If you want to present the same data as before in a chart but from a different device. This dialog works like the Information Elements tab in the line chart properties (see section 29. it is impractical to edit the MS field for each information element 352 .. . Labeling By default the x-axis is labeled simply with numbers. Click the Compose button. since this by itself stipulates a fixed number of x-axis indices.3).

Chapter 30. Examples of Bar Chart Presentations Here are a couple of examples of how the presentation modes can be used.5. From the context menu. • Right-click in the bar chart window.0 353 . choose Change MS: • For each chart. Therefore.1.1. NT12-7002 ver 1.4. Bar Charts separately as described in section 30. (The information elements selected in the charts will be unchanged. Single IE Single IE presentation: Neighbor RxLev (Sorted). select the device to pick data from.) 30. there is a shortcut for this operation.

and with user-defined text labels added on the x-axis.1 User’s Manual Multiple IE Components Multiple IE Components presentation displaying an assortment of single-value IEs and selected components of multivalue IEs. 354 . Note that only half of the legend is visible in the picture.TEMS Investigation 14.

Each point on the horizontal axis represents a network parameter.Chapter 30.0 355 . See section 23. Parallel Coordinates Parallel coordinates presentation (the predefined Radio Parameters Parallel Bar Chart for WCDMA). 30.6. any unexpected line shape). NT12-7002 ver 1. Exporting the Bar Chart Window The bar chart window can be exported separately to a file with extension . This arrangement allows the user to spot instantaneously any pattern that is out of the ordinary (that is. Bar Charts Stacked Bar Chart.7.bch. represents a moment in time. and the colored line. connecting a set of parameter values.

How to do this is explained in section 31. and information elements are shown along the route in symbolic form.5.3–31. numeric values can also be easily accessed. 356 . Map files used in TEMS Investigation must be in MapInfo. use this section as a reference. Map windows are fully user-configurable. If you have loaded a cell file and want to view cell information. Like the other presentation windows. TEMS Investigation must have access to positioning data. bitmap.TEMS Investigation 14.1 User’s Manual 31. Data on cells. 31.1. or uncompressed TIF format. The concepts are explained again as they are brought up later in the chapter. and you might not have use for all of it. A map of the world is provided with the installation. You might want to skim this section the first time around to make yourself familiar with the concepts. Note also that to be able to plot measurements on a map. turn to section 31. Map Windows Map windows are used to display a map of your testing area and present your drive test route graphically on this map.5. some central concepts relating to Map windows are defined.2. A map usually consists of several map layers (see Layer) and is presented in a Map window. to be able to use a map file in TEMS Investigation.5. Highlights of This Chapter This chapter contains a great deal of information. Then you can proceed to set up what data you want to present on the map. are central: • • First. The following sections. you must work through some preliminaries which are described in sections 31. 31. however. events. Map A map is a set of geographical features which are treated as a unit.4. Map Concepts In this section.

labels. If your map is in MapInfo format. Additional layers can be defined by the user.tab. .id. etc.0 357 . A presentation layer contains one or several themes. This file can then be opened in a Map window. all of the same main type (see Theme below). Theme A theme is a component of a presentation layer.Chapter 31. for example.dat. for example.3). GeoSet A GeoSet (file extension . zoom levels. consist of all the roads or all the water areas on the map. Map Windows TEMS Investigation supports the following map formats: MapInfo. If you have a new map that you want to use in TEMS Investigation.3. A GeoSet contains settings regarding layer order.map. colors. . 31. displaying. bitmap. which make up the map itself. Each layer is stored in five different files with the extensions . These files are from now on collectively referred to as TAB files. A map layer may. and presentation layers.gst) is a special type of workspace used for map layers.ind. which contain information relating to the cellular network. it consists of a number of map layers and a workspace which ties them together. and . One presentation layer is predefined for each main type of theme. There are two types of layer: map layers. Constructing a GeoSet from Map Files A Map window in TEMS Investigation works with a GeoSet instead of an ordinary workspace. a further layer is provided for pinpoint markers (see section 11. NT12-7002 ver 1. Layer A layer is a set of data from a particular category which is displayed in a Map window. an information element or a type of event.1. and TIF (uncompressed only). Label A label is a text string that belongs to a map and can be displayed on it. . projections. you should construct a GeoSet file for it to be able to save changes to the map later on.

This is done by positioning the map as described in section 31.TEMS Investigation 14. Note: It is possible to load TAB files in a Map window directly. Once you have your TAB files. • The map should now be displayed in the Map window. • • • • • Click Add. You are ready to start presenting data: see section 31.bmp). • Select your newly created GeoSet file and click Open. This will save your new GeoSet file under the name you entered in the GeoSet Name edit box. On the Map window toolbar. click the Start GeoSet Manager button.7. Click Save. Click Open Map Files. avoid using 24-bit bitmap images as maps. Click OK.4. Note: The GeoSet Manager will ask you to open a GeoSet. • Copy the map’s TAB files to your map directory. you can construct a GeoSet. You are prompted to name the GeoSet. • Name your new GeoSet in the edit box of the toolbar. Choose File  Exit to close the GeoSet Manager.1 User’s Manual If your map is in bitmap format (extension . but then any changes made using the Layer Control will be lost. without constructing a GeoSet. you must generate TAB files for it. Click Cancel to ignore this. See section 31. 358 . Click Layer Control. Select the TAB files you copied to your map directory and click Open. If possible. All the selected layers are added to the Layer Control. Choose File  Save GeoSet.5.2. The GeoSet file must be in the same directory as the TAB files. The map is now displayed with all its layers.

you must supply this data yourself.4.1. In the Reference Point section. Map Windows 31. NT12-7002 ver 1. click the Pick button. 31. • • • Specifying the Map Position In this step you input the coordinates of a point on the map.Chapter 31.2.4. On the map. enter the coordinates (in decimal degrees) of the point you wish to use. in the Latitude and Longitude fields. Click the Pick button in the Reference Point section. Specifying the Map Scale In this step you indicate the distance between some two points on the map. • In the Distance section. click the point that has the given coordinates. so that the map scale can be calculated. Positioning Bitmap and TIF Maps If you open a map in bitmap or uncompressed TIF format that has not yet been assigned geographical coordinates and scale information. 31.0 359 . Click Position Map.4.

a positive number indicating a clockwise offset. • 31. • Your map is now positioned.5. see section 31. In short. In the Direction section. in the North Offset Angle field. 31.5. a dashed blue line appears. to get started with presenting data. A file with the same name as the image but with the extension . if the map is oriented with north pointing up. The *. you can also modify presentation layers and create new ones. These are the main types of theme. 31. In the Distance field. in order to present data. When you move the mouse. For example.4 360 . How to do this is described in section 31.3 event themes. The coordinates of the chosen points appear in the X_Y fields. Therefore. all your work is to do with themes and is covered in the present section. you use presentation layers and fill these with themes. enter 90°.tab is created. The offset lies between –180° and +180°. Click OK.1 User’s Manual • On the map. Release the mouse button at the second point. However.1.5. you do not need to worry about handling presentation layers. enter the offset between the map’s x-axis and its direction of north. A set of presentation layers is already supplied in the application.4. each presenting a different kind of data: • • information element (IE) themes.5. enter the actual distance between the two points. presenting an event. Themes and Theme Types A theme is basically a bundle of settings describing how to present a set of data. click the first point and keep the mouse button down.TEMS Investigation 14. see section 31. Presenting Data: Themes This section describes how to present cellular network data on the map.7. • Setting the Map’s North Direction What remains is to indicate the north direction of the map.tab file is the map file you will use from now on. presenting a set of information elements (at most three).3.

You can add new presentation layers if desired.7. presenting cell information. the Pinpoint theme. as is seen in this screenshot (where some layers have been expanded). 31. see section 31. Certain presentation layers are predefined.5. Map Windows • • cell themes.5. RF Quality. There are several subtypes of cell theme.5.0 361 . How to manipulate layers is the subject of section 31.5. see section 31. Click Add/Edit Themes to view the current presentation layers and the themes within them.Chapter 31. presenting pinpointing information. Presentation Layers When you create a theme. The various types of theme are put in different layers: • • • • IE themes in the Coverage.2. you always put it in a presentation layer. along with a number of themes.6. NT12-7002 ver 1. and AMR layers event themes in the Event layer cell themes in the Cell layer the pinpoint theme in the Pinpoint layer.

3.TEMS Investigation 14. and shape. the marker can code the values of up to three numeric information elements. select one of the layers (or create a new layer to put the theme in: see section 31. as set on the Info Element tab of the Navigator: see section 5. sizes. Click Add Theme: 362 . The colors. and to use a suite of symbols for such things as status parameters having a small set of possible values. These govern the appearance of a marker that is plotted on the map. dedicated mode.1 User’s Manual 31. For example. and use different symbols when the phone is in idle mode. it is appropriate to use the color and size attributes for information elements with a continuous value range.7). and symbols used in the map are always the default ones for each information element. size.3. To create a new IE theme: • • In the Theme Settings dialog.5. you can have the marker color governed by RxLev and the marker size by RxQual. Presenting Information Elements To present information elements. and so on: More generally. By varying its color. you create information element themes (hereafter called IE themes). It is not possible to define these attributes differently in the map.

This means. in the same way as for the color. chapter 2. a positive offset is to the right relative to the direction of travel. Choose the device from which to pick the information element. See above. NT12-7002 ver 1. Color • Size In this section you specify a rule for the theme marker size. of course. Choose Fixed to use a fixed color. and select an argument if applicable. See Information Elements and Events. Select an element.Chapter 31. This setting decides how far from its true position on the map the theme marker will be drawn. Map Windows System Mobile Offset (pixels) Choose an information element category. The offset direction is at right angles to the direction of travel. In this section you specify a rule for the theme marker color: • Choose Range to have the color governed by an information element. Using offsets enables you to display several routes side by side.0 363 . that the color will not carry any information.

A general rule is that new theme markers are drawn at most twice a second. If you want to plot such an IE with high frequency. and no extrapolation of the route is attempted by TEMS Investigation. are constantly interpolated (linearly) to enable plotting at half-second intervals.5. whether markers are actually plotted at this rate depends on other circumstances. and not for showing measurement data. Another basic fact to keep in mind is that the position of a theme marker does not necessarily correspond exactly to a pair of GPS or pinpointing coordinates. Note that some information elements are not updated this often. • • 364 . Loss of positioning data. see section 31. will then be plotted along the route at the shortest possible time intervals (about factors influencing this updating rate.3. if no more positioning data is obtained. Map positions. pick a font in the first combo box. Notes on Route Plotting and Updating The updating frequency for IE themes is governed by a number of factors. for instance circles. Note also that certain information elements are not updated regularly at all but only on special occasions (for example. If GPS data is lost for an extended period of time (for instance while driving through a tunnel) but GPS coverage is eventually regained.5.1 below). whether delivered by a GPS or pinpointed. Arrival of new measurement data.TEMS Investigation 14. then pick a symbol in the second. when the phone switches to a different RAB).1.3. Once the IE theme has been defined. If you choose Fixed. interpolation is of course impossible. in the same way as for the color. include another IE that is frequently updated in the same theme. it appears in the box in the Theme Settings dialog under the layer it belongs to.1 User’s Manual Symbol In this section you specify a rule for choosing the shape of the theme marker. A new theme marker is plotted only if a message with fresh data has been delivered by the measurement device. positions will still be interpolated and plotted throughout the gap. See below. However. Uniform markers. Updates will thus be less frequent in idle mode than in dedicated mode. On the other hand. The Fixed options are useful if you want to use an IE theme just for plotting the route. 31. Here is a summary of the factors that affect theme plotting and updating: • Interpolation.

NT12-7002 ver 1. The plotting density on the map is dependent on the current zoom of the Map window. 31. Note: If you create a new event theme for a user-defined event after loading a logfile.Chapter 31. Specifically. you create an event theme. a new theme object (whether a symbol or a line) is drawn next to the latest one if the centers of the two objects will be more than 5 pixels apart on the screen. when you zoom out.5.0 365 . more markers are filled in to show the route in more detail. Choose the device from which to pick this type of event. • • In the Theme Settings dialog.4. Presenting Events To present an event. markers are drawn more sparsely. you must reload the logfile to make this event theme visible. Click Add Theme: Event Mobile Choose an event type. select the layer named Event Layer. Map Windows • Map zoom. When you zoom in.

5. and set its size. Select the font. as is evident from section 31. This enables the creation of cell themes displaying arbitrary groups of cells.10).e. all white pixels in the bitmap become transparent. you do not have to load a cell file first. Bitmap Transparent Select this to use a bitmap image as event symbol. Select your image. How to load cell files is described in section 6. • Font Select this to pick an event symbol from a font. See section 31. 31. Where the presentation differs between cellular technologies. sections 4. Furthermore.7.7.3. the bitmap is drawn exactly as-is.TEMS Investigation 14.1 User’s Manual Offset (pixels) Set the offset.1 below. with a separate theme for each. with the obvious exception of GSM-specific information such as the Cell ARFCN theme. Presenting Cell Information1 To present cell information.5. 366 .2. a couple of cell themes are predefined. It has the same meaning as for information elements. This presentation also applies to WiMAX cells and Wi-Fi access points defined in an XML cell file (see the Technical Reference. • If this is checked. Wi-Fi and WiMAX both follow GSM. If this is not checked. i. It is also possible to draw cell information for multiple technologies in the same theme.5. individual cells can be tagged with a type. It is possible to have more than one cell file loaded.9 and 4. The themes can be defined at any time.3. in the XML cell file format. see section 31. you create cell themes. then pick a symbol and set its size and color.) Cell information for different technologies can be kept apart in the presentation. otherwise no transparency is achieved. 1. For events it is appropriate to use a non-zero offset (for instance 20 pixels) so that event theme symbols are not hidden by the IE theme markers plotted on the route. the underlying layer shines through.5. (In fact. Note that this requires a bitmap with a white background.5.5.

regardless of the zoom. Choose a cell theme type.5. To create a new cell theme.Chapter 31.3 (GSM:) Indication of cells using the same ARFCN as a given cell (Cell ARFCN theme): section 31. All cell sites are always plotted.5.0 367 . which by default hide the Cell theme.5.5.1.5. Note that certain cells are filled with other colors by other cell themes. select Cell Layer. Map Windows The following kinds of cell theme exist: • • • • Basic plotting of cell sites (Cell theme): section 31.5.4. The Cell Theme This theme is concerned with basic plotting of cell sites.2 Visualization of neighbor relations (Cell Color theme): section 31. see sections 31.5.4 In the Theme Settings dialog.5. text labels have been turned off in all of the remaining illustrations in section 31.5.5.3 and 31.1 Indication of serving cell and handover (Cell Line theme): section 31. However. Presentation on Map Three-sector site (three cells) Omni cell The zoom of the Map window does not affect this theme. to avoid clutter.5. Click Add Theme.5. Each cell is tagged with a text label if you turn on the Cell labels option (see below). NT12-7002 ver 1.5.5.5.5. The Select Theme Type dialog appears. proceed as follows: • • • 31.

Choose a cellular technology to plot only cells from that technology. see the Technical Reference. chapters 3 and 4. section 4.) Cell type Type of cell indicated in cell file.7. This section governs how cells are drawn. GSM and WCDMA cells are told apart by inspection of what type of channel is defined (ARFCN or UARFCN). You might want to create one Cell theme for each technology.TEMS Investigation 14. In XML cell files this is identical with the CELL_TYPE element: see the Technical Reference.13.1 User’s Manual Setup Dialog Cells to plot System This section governs which of the cells defined in the cell file will be plotted. Cell presentation 368 . (Regarding cellular technology support in the CEL and XML cell file formats. Choose ALL to plot cells from all technologies. In CEL files.

the following plotting rules apply: • If the antenna direction is not stated in the cell file. • Cell labels If you check this option. incompletely described cells will not be marked as such in any way. it is set to 360º in the plot (omni cell.5. If you uncheck this option. The color to be used for the border of the cell symbol. Map Windows Radius (pixels) Border color Fill color The radius of each cell symbol (circle/sector of circle) in pixels.5. Incomplete cells The default color to be used for cells that are incompletely described in the cell file. The color to be used for the interior of the cell symbol. When you select a cell. a text label will be printed next to each cell.3 and 31.5. this highlighting ceases to be visible if a Cell Color or Cell ARFCN theme is also displayed: see sections 31. If the beam width is not stated.5. In either case. see the illustration in section 31. provided that the cell is completely described in the cell file.6.4). (However. The displayed information.0 369 . it turns red. Uncheck to make the symbol transparent.Chapter 31. full circle). is as follows: • • • • • GSM: Cell name WCDMA: Cell name and SC LTE: Cell name TD-SCDMA: Cell name CDMA: Cell name NT12-7002 ver 1. it is set to zero degrees in the plot (sector centered on “twelve o’clock”). taken from the cell file.

GSM. The Cell Line theme has different meanings depending on the data source: phone or scanner.) Additionally. TD-SCDMA) active set members (WCDMA connected mode/CDMA traffic mode) (The user interface uses only the term “serving cell”. the Cell Line theme gives a best server indication. Of course. Use with Phone Data For a phone.5. Technology-specific information: Parameters used to measure signal strength • • • • • • • GSM: RxLev WCDMA: Aggregate Ec LTE: RSRQ TD-SCDMA: Ec/Io CDMA: Aggregate Ec WiMAX: Channel RSSI Wi-Fi: WLAN RSSI 370 .5. LTE. this theme is used to indicate • • the serving cell (WCDMA/CDMA idle mode. and the cell is identified which a user terminal at the same position would be most likely to use.1 User’s Manual 31. The Cell Line Theme This theme is used to indicate serving cells and positions where handovers have taken place. no interaction with base stations is involved during scanning.TEMS Investigation 14. Use with Scan Data With scan data.5.5.1). provided that cells from both cellular technologies are visible in the Cell theme (section 31. GPS data and the contents of a signal strength information element are correlated with the coordinates in the cell file. Inter-system handovers are visualized in the same way as intrasystem handovers. the theme indicates positions where handovers have taken place.2. rather. This points out the cell that uses the currently strongest signal as measured by the scanning device.

Chapter 31.1). all that is said of serving cells/active set also applies to best server indications. ensuring that large swaths of the map are not completely covered by such lines when the Leave trail option is checked. This density is governed among other things by the zoom of the Map window. Setup Dialog Below. NT12-7002 ver 1.0 371 .3. Map Windows Presentation on Map route line to current serving cell Like IE theme markers (section 31. cell lines are plotted with a variable density.5.

although no actual handover is involved. Before choosing the information element (and an argument if applicable). Serving cell Serving cell line Fixed color Color governed by IE Leave trail Serving cell list changed Line to added cell Line to removed cell 372 . See Color governed by IE below. These settings govern the indication of current and past serving cells/active set members. Note that they are independent of the Serving cell settings. Select this to have the serving cell line drawn in a fixed color. Check this to continually display a line connecting the current position along the route with the current serving cell/active set members. The line will remain on the map. At handover. Check this to leave all serving cell lines on the map. Select this to have the color of the connecting line(s) governed by an information element.1 User’s Manual System Mobile Offset (pixels) Governs what IEs are selectable.3). the line is shifted in the same way as an IE theme marker. These settings refer to indication of handovers. It has the same meaning as for information elements (see section 31. although no actual handover is involved. This feature is available also for best server indications. This feature is available also for best server indications. i. Set the offset for the starting point of the line. a line is drawn from the position where the old serving cell or active set member is last used.5. At handover. Pick a color in the combo box. The line width is adjustable. a line is drawn from the position where the new serving cell or active set member is first used.e. Choose the phone whose serving cells are to be displayed.TEMS Investigation 14. choose the desired category in the System combo box. The line remains after the phone has moved on.

the neighbor presentation is not affected by the phone’s neighbor reporting. active set WCDMA example: Cell Color and Cell Line themes. the theme will be displayed with that cell as serving cell instead.0 373 . Map Windows 31. therefore. The neighbor relations shown are those indicated in the loaded cell file. Presentation on Map yellow color from Cell theme GSM example: Cell Color theme (no route). if you click an arbitrary cell. However. Active set members pointed out by solid lines (black).Chapter 31. NT12-7002 ver 1.5. in the realtime presentation as well as during logfile analysis.5. the cell drawn in green will be the phone’s current serving cell. The Cell Color Theme This theme is used to visualize the neighbor relations of the current serving cell/active set members or of an arbitrary user-selected cell (only one cell at a time).3. The only phone data fed into this theme is the serving cell data. Neighbors indicated for all active set members (dashed red lines). By default. independently of the phone’s interaction with the network.

TEMS Investigation 14.1 User’s Manual

• •

The presentation for LTE and TD-SCDMA is similar to that for GSM. The presentation for CDMA is similar to that for WCDMA.

By default the Cell Color theme is drawn on top of the Cell theme (section 31.5.5.1). That is, cells drawn in yellow (or highlighted in red) in the Cell theme will be overlaid with the differently colored cells of the Cell Color theme, as in the above figures. Setup Dialog

System Mobile Colors: Serving cell

Not used; the choice does not matter. Choose the phone whose serving cell is to be displayed. The fill color to use for the serving cell. If you uncheck this box, the cell is not drawn (and, by default, the version of it displayed in the underlying Cell theme will be visible instead). The fill color to use for neighbors of the serving cell. If you uncheck this box, the neighbor cells are not drawn in this theme.

Colors: Neighbor cells

374

Chapter 31. Map Windows

Colors: Servingto-neighbor lines

If single serving cell in use: Check this to display dashed lines connecting the serving cell with each of its neighbors. If multi-cell active set in use: Check this to display, for each active set member, dashed lines connecting the active set member with each of its neighbors.

31.5.5.4.

The Cell ARFCN Theme (GSM)

This theme is used to point out other cells that use a specified BCCH or TCH of a selected cell. It is intended as an aid in GSM interferer identification, a function no longer supported in TEMS Investigation. The theme is retained since loading of old logfiles containing interferer identification data is still supported. To display the theme, do as follows: • Right-click the cell of interest. A context menu appears, listing the BCCH and the TCHs that it uses. Choose the ARFCN that you want to search for among other cells:

By default, matching cells are colored as follows: • • Cells that use the selected ARFCN as BCCH are colored cyan (light greenish blue). Cells that use the selected ARFCN as TCH are colored blue.

NT12-7002 ver 1.0

375

TEMS Investigation 14.1 User’s Manual

Presentation on Map

selected cell; BCCH selected in context menu other cell using same ARFCN as TCH
Cell ARFCN theme.

other cell using same ARFCN as BCCH

By default the Cell ARFCN theme is drawn on top of the Cell theme but beneath the Cell Color theme, so you may need to hide the latter or change the ordering of the themes. Setup Dialog

System Same BCCH ARFCN Same TCH ARFCN

Not used; the choice does not matter. The fill color to use for cells that use the selected ARFCN as BCCH. The fill color to use for cells that use the selected ARFCN as TCH.

376

Chapter 31. Map Windows

31.5.6.

Presenting Pinpointing

The Pinpoint theme presents the markers that you create when positioning data by pinpointing in the Map window (see section 11.1.3). Note: The Pinpoint theme is needed in order for the Map window pinpointing mechanism itself to work. Therefore, this theme should never be removed. The following properties can be edited for the Pinpoint theme:

Symbol Line

Type, size, and color of waypoint symbols. Color and width of lines connecting waypoints.

31.5.7.
• •

Editing Themes

To edit a theme: In the Theme Settings dialog, select the theme you want to edit. Click Edit.

31.5.8.

Visibility of Themes

In the Theme Settings dialog, the checkbox next to each layer and theme governs whether or not it is visible.

NT12-7002 ver 1.0

377

TEMS Investigation 14.1 User’s Manual

• •

To show a theme, check the box. To hide a theme, uncheck the box.

The same also applies to layers (section 31.7).

31.5.9.
• • •

Reordering Themes

To change the order in which themes are superimposed within a layer: In the Theme Settings dialog, select the theme you want to move. To move the theme upwards, click Up. To move the theme downwards, click Down.

The ordering is of particular relevance for cell-related themes (section 31.5.5).

31.5.10. Deleting Themes
To delete a theme: • • In the Theme Settings dialog, select the theme you want to delete. Click Delete.

31.6.
31.6.1.

The Right-hand Pane
Information on Single Theme Markers (Info Tab)

When you select a single theme marker on the map, the marker is highlighted in red,1 and the Info tab shows (some of) the data represented by this marker.

1. Exception: If a Cell Color theme is active, the selected cell is presented as a serving cell and is colored green.

378

Chapter 31. Map Windows

IE marker

Event marker

For cells, a selection of cell and channel parameters are shown, along with the cell’s defined neighbors (the red cell is highlighted):

Cell markers

For Wi-Fi access points, the cell parameters are replaced by a set of Wi-Fi parameters. There is further interplay between the map and the Info tab. For example, if you click a neighbor of the cell described in the Cells section of the Info tab, the neighbor will take over the role of serving cell in the Cell Color theme, so that its own neighbors are displayed instead. If a group of theme markers is selected, the Info tab instead shows statistics on the selected data: see section 31.6.2.

NT12-7002 ver 1.0

379

TEMS Investigation 14.1 User’s Manual

31.6.2.

Theme Statistics (Info and Graph Tabs)

You can view some basic statistics for a set of theme markers selected on the map. Textual information is then presented on the Info tab, and graphs are drawn on the Graph tab. There are two ways to select a set of theme markers: To select all objects within a rectangular area, use the Area Statistics Tool. Click and drag in the map pane to mark the rectangle. To select a segment of a route, use the Selection Tool. Click the marker where you want the segment to begin. Press and hold Ctrl, then click the marker that is to be the endpoint of the segment. (It is not possible to select an arbitrary set of objects.) When you release the mouse, statistics for the chosen marker set are computed and shown on the Info tab: • The Information Elements box holds the information elements contained in the selected theme markers. Next to the name of an element is shown the mean value of the element calculated over the selected markers. (Averaging of signal strength values takes place in the mW domain.) Expand the information element to view the full set of statistics: mean, minimum, maximum, and number of samples. The Events box shows the number of occurrences of every event that has a theme defined for it (not just those actually found among the selected theme markers). The Cells box shows all cells that have been used as serving cells at the positions included in the marker set. For the Area Statistics tool, cells that are within the rectangle but have never been serving cells are not shown.

On the Graph tab, a histogram is drawn for each information element contained in the selected theme markers. A green curve indicates the cumulative distribution. Statistics can be computed in both recording and analysis mode. It should be noted that the map plotting may be more or less thinned out (see section 31.5.3.1), so that more data goes into the statistics than actually appears on the map.

380

Chapter 31. Map Windows

31.6.3.

Theme Legend (Legend Tab)

The Legend tab gives an overview of all presentation themes, or selected ones, displaying full details of theme settings. Use the combo box at the top to select what to show.

31.7.

Layers

Section 31.5 introduced the concept of presentation layer. This section treats layers in more detail. Generally speaking, layers are sets of data which together make up the contents of a Map window. Besides the presentation layer, there are also map layers, which make up the map itself and cannot be edited. In both types of layers, however, it is possible to make a number of settings that do not affect the contents of the layers, for instance to set the visibility of each layer. These settings are detailed below.

31.7.1.

Adding Presentation Layers

Normally there is no need to add new presentation layers, since predefined layers are provided for the various types of theme. However, if you should want to define a set of data that you want to manage separately in a convenient way (for instance turn the visibility on and off), then you should put that data in a separate presentation layer. To create a new presentation layer, proceed as follows: Click Add/Edit Themes. • In the dialog that appears, click Add Layer:

Layer name

Name the new presentation layer.

NT12-7002 ver 1.0

381

TEMS Investigation 14.1 User’s Manual

Layer type

Choose a layer type, corresponding to the theme types listed in section 31.5.1.

31.7.2.

Layer Control

The Layer Control dialog is used to edit various properties of layers. Note: The Layer Control can be accessed either from a Map window or from the GeoSet Manager. Changes made from a Map window affect only that window and cannot be saved. If you want to make changes that can be saved, use the Layer Control of the GeoSet Manager (see section 31.10). • To open the Layer Control: Click the Layer Control button.

Up, Down

Change the order in which layers are superimposed on the screen. (The top layer is first in the list.) To move a layer upwards, select it and click Up. To move a layer downwards, select it and click Down.

382

See Labels below. (No further history of views is maintained. Disabled for presentation layers.8. a context menu appears with choices as described below. 31.1. Map Context Menu When you right-click in the map.g. Editable Display Labels Not used. Note that the visibility of labels may be conditioned by the zoom range. should be turned off for map layers.5. the layer they belong to must be visible. Previous View This command returns you to the previous map view. Set display properties for the selected layer. should be turned off for map layers. The Scale Bar This command shows and hides a scale bar showing distance in kilometers or miles. 31.2.8. Remove the selected layer. Check to make the selected layer in the list visible.8). Disabled for presentation layers. For labels to be visible.) NT12-7002 ver 1. Disabled for presentation layers. Map Windows Add Remove Visible Add a layer. Select a TAB file and click Open. Set label properties for the selected layer. Note that the visibility of presentation layers can also be set in the Theme Settings dialog (see section 31. Selectable Automatic Labels Not used.0 383 . Regional Options  NumbersMeasurement System).8. 31. Check to make the labels of the selected layer visible.Chapter 31. The unit of distance is governed from the Control Panel in Windows (e.

384 . Add/Edit Themes: Add or remove presentation layers.2. GeoSet Manager: Start the GeoSet Manager which is used for creating new GeoSet files and for changing the properties of a GeoSet. Press and hold Ctrl to select a segment of a route (see section 31.TEMS Investigation 14. choose an information element layer to view the whole of your route. View Entire Layer This commands zooms out to show the whole of the chosen layer. See section 31. To make changes to the GeoSet. The Map Window Toolbar This section gives a description of the Map window toolbar buttons. Layer Control: Manage layers or change displaying or labeling properties.10.1.3. See section 31. Changes are only temporary and cannot be saved.8. Open Map: Open a map. Position Map: Position a map which is in bitmap or uncompressed TIF format. but many others relate to map handling and have not previously been mentioned. use the layer control in the GeoSet Manager. 31.5.4. It should be the same as in the cell file.6. See sections 31.10. See section 31.7.2). edit or remove themes. 31. Doubleclick the object to inspect what information it contains.1 User’s Manual 31. Some of these activate functions described earlier in this chapter.2). Area Statistics Tool: Click and drag to view statistics for presentation layer objects within a rectangle (see section 31. see section 31.3 and 31.4. or add.9.6. Selection Tool: Click a presentation layer object to select it. Zoom In: Enlarge a portion of the map to view it in more detail. For example.8. Setting the Map Projection This command allows you to set the map projection.

Previous Item: Select the previous object of the same type. Center Map: Click a spot in the map to center it around this spot. Pan Tool: Move the map by clicking and dragging. choose Entire Layer.10. Holding down the Ctrl key swaps the zoom operations. Last Item: Select the last object of the same type. and select the Defaults tab. right-click in the map.1. Double-click at the endpoint. The following buttons are enabled only when an object belonging to a theme has been selected: First Item: Select the first object of the same type. The distance of the last segment and the total distance are shown on the status bar at the bottom of the Map window. choose View.Chapter 31. Click in the map to indicate a starting point. Ruler: Measure the distance of a route on the map consisting of straight line segments. choose Map Properties. GeoSet Manager The GeoSet Manager looks and works much like a Map window. If you have zoomed in and want to view the entire route again.3. However. To change the unit of distance. changes made using NT12-7002 ver 1. except cell site information. Pinpoint: Mark waypoints on the map. see section 11. Clear Map: Remove all the information in presentation layers from the map. then click at each turn. Regarding positioning of logfile data by pinpointing in the Map window.0 385 . while changes made in a Map window cannot be saved. 31. Next Item: Select the next object of the same type. right-click in the map. Map Windows Zoom Out: View a larger area than the current map view. and specify one of the presentation layers.

386 . 31. choose Map  Projections. Projections It is possible to set which projection to use for a GeoSet.2.7.1 User’s Manual the GeoSet Manager can be saved to the GeoSet (*. Layer Control The Layer Control works the same way as in Map windows. click the Start GeoSetManager button on the Map window toolbar.1.2.TEMS Investigation 14. To start the GeoSet Manager.10.10. make sure you choose the projection of the layer you usually work with.gst) file associated with the map. If your GeoSet contains multiple layers with different projections. See section 31. • To change the projection. 31.

The General Window 32. NT12-7002 ver 1.Chapter 32. The General Window In the General window.0 387 . These settings are covered elsewhere in this manual in the appropriate contexts. found on the Navigator’s Menu tab in the Configuration folder. are collected miscellaneous settings that affect the behavior of the TEMS Investigation application.

these are tagged “not in ETSI” in the Technical Reference. and integrity. In the present version of TEMS Investigation. that is. Listings and brief definitions of the KPIs are found in the Technical Reference.1 User’s Manual 33.1 The present chapter gives an general discussion of KPIs as well as an overview of how to obtain them with TEMS products. 33. A number of KPIs are not present in the ETSI specification. Key Performance Indicators – KPIs (UMTS) KPIs (Key Performance Indicators) are offered in TEMS products for measuring the user-perceived performance of a number of circuit-switched and packet-switched services. Note that this is different from certain previous TEMS Investigation versions.4. however. 1. where a “KPI Report” function was provided. all data needed for KPIs is recorded in TEMS Investigation logfiles.1 for performance measurements. 388 . to measure accessibility.1. KPI data can be collected for GSM and WCDMA. chapter 11. chapter 11. TEMS Discovery or TEMS Automatic are the products to use for explicitly generating KPIs and reports that present them. retainability. KPIs are not computed in TEMS Investigation or handled explicitly in the application in any way. Purpose of KPIs Most of the KPIs have been designed according to ETSI TS 102 250-2 V1. Full detail on technical matters is given in separate documents which are found on the installation CD in the subdirectory Documents.TEMS Investigation 14.

Integrity Integrity indicates the degree to which a service is maintained without major disturbances once it has been accessed. from very good to unacceptably bad. the user must be able to execute a chain of operations: • • • accessing the packet-switched network as such. in order for a service to be accessible in a packet-switched network. Retainability of a service or session also implies that the user does not have to perform any manual operations that are not necessary under stable network conditions.1. Integrity KPIs show the performance of successful service attempts.Chapter 33. Even if a service was accessed successfully. Key Performance Indicators – KPIs (UMTS) 33.2. Obtaining KPIs with TEMS Products General Procedure To obtain KPIs. such as (in the packet-switched case) manual reactivation of the PDP context. Retainability Retainability is the ability of the user to keep a service. Accessibility Accessibility is the ability of the user to obtain a service within specified tolerances and under other given conditions. i.2.e. perform the following steps: 1. 33. For example. the service testing should be enclosed by the NT12-7002 ver 1. 33.1. once it has been accessed. under given conditions for a requested period of time.1. performing an attach and a PDP context activation within an active PDP context.2. 33. Compose a TEMS Investigation script that executes one or several services.1.0 389 . 33.1. Furthermore. the user’s perception of the performance may vary greatly.3. accessing an IP service (for WAP and MMS) activating a WAP session. The script structure should be modeled on the predefined snippets that are provided for each service type in order to ensure that all aspects of the data collection are in accordance with ETSI KPI definitions.

3. “Data Events”. and generate KPI reports using one of these products.2. 33. 390 . 33. please consult the documentation accompanying the relevant product. special KPI events are displayed in the window Events Of KPI Type. See chapter 20. Run the script in TEMS Investigation.2. and particularly section 20.TEMS Investigation 14.4. These events underlie the computation of KPIs. The mathematical relationships between sample size and statistical accuracy are given in a separate document. “Events of KPI Type” When you test services in TEMS Investigation. For details.3. see Information Elements and Events volume. found on the installation CD in the subdirectory Documents.9 on snippets.2. section 7. 2.1 User’s Manual control activities Start Recording and Stop Recording. “Statistical Guidelines for Collecting KPI Data”. Open the logfile(s) produced by the script in TEMS Discovery or TEMS Automatic. Obtaining Significant KPI Statistics To obtain reliable KPI statistics you need to collect sufficient amounts of data.

Speech Quality Index – SQI TEMS products offer the quality measure SQI (Speech Quality Index) for estimating the downlink speech quality in a GSM. although its fundamental function remains similar to that of the old algorithm (the output of which is still available in TEMS Investigation). This chapter examines the workings of the SQI algorithm. but no comprehensive point-by-point comparison is made.1. SQI for CDMA can be based on data from any CDMA phone that is connectable in TEMS Investigation. the SQI algorithm was completely reworked.1. SQI for CDMA SQI for CDMA uses an SQI-MOS algorithm similar to those for GSM and WCDMA. see section 34. SQI for CDMA currently does not support wideband.0. or CDMA cellular network as perceived by a human listener. WCDMA. The focus of this chapter is to describe the new algorithm (called “SQI-MOS” in the application.Chapter 34.3). and attention is drawn to certain important differences between the algorithms. NT12-7002 ver 1. See also the document “Speech Quality Measurement with SQI” which is included on the TEMS Investigation installation CD in the subdirectory Documents. 34. Speech Quality Index – SQI 34. Computing SQI for GSM and WCDMA requires data collected with Sony Ericsson phones.0 391 . However. 34. in TEMS Investigation 9.1. 34.2. the SQI-MOS algorithm includes a model for rating wideband speech. Background SQI for UMTS SQI for GSM and WCDMA is a long-standing feature of TEMS products. Reference is made to the previously used algorithm (the “old SQI”).1. As wideband speech codecs are now being deployed in mobile phones and networks.

SQI-MOS for UMTS is implemented for the following codecs: • • GSM EFR.65 1.60.2 FR. each speech codec has its own strengths and weaknesses with regard to input properties and channel conditions. The speech codec used. The general speech quality level and the highest attainable quality vary widely between codecs. every handover causes a number of frames to be lost. 10. • Input to the SQI-MOS Algorithm UMTS SQI-MOS for UMTS takes the following parameters as input: The frame error rate (FER.e. the current algorithm also does not consider the distribution of frame/block errors over time. on the other hand. 5. usually because of bad radio conditions. 8.4 FR/HR. In GSM. Frame/Block errors also occur in connection with handover.1. 5.2. 4. for wideband. 34. GSM) or block error rate (BLER. WCDMA). and 12. no such quantity is reported by UEs in WCDMA mode.2 FR. Handovers are not modeled independently in any way by SQI-MOS. and GSM HR all GSM AMR-NB and AMR-WB modes up to 12.75 FR/HR. 6. The same basic SQI-MOS model is used for all supported speech codecs. 7.1 More generally. but the model is tuned separately for each codec to capture its unique characteristics. 392 .2.1 User’s Manual 34.TEMS Investigation 14. In contrast. Moreover. and these are treated like any other frame/block errors by the SQI-MOS algorithm.65 kbit/s: – – for narrowband.7 FR/HR.9 FR/HR. GSM FR.15 FR/HR. It should be noted that in WCDMA. i. handover block errors can usually be avoided thanks to the soft handover mechanism.95 FR/HR. • • The bit error rate (BER). 7.85. This is available in GSM only. the percentage of radio frames/blocks that are lost on their way to the receiving party. 6. and 12. the old SQI algorithm includes a special “handover penalty” mechanism lowering the SQI score whenever a handover has occurred.

1 applies equally to CDMA (with the term “handoff” substituted for “handover”). 7.65 kbit/s: – – for narrowband. 7.2.7.65. 5. 4. and 12.9. including bit rate information The general discussion of these parameters in section 34.0 393 . 5.2.95. 6.2. 34. 6. 8. NT12-7002 ver 1.75. Speech Quality Index – SQI • all WCDMA AMR-NB and AMR-WB modes up to 12. The SQI-MOS algorithm produces a new quality estimate at intervals of • • (UMTS) approximately 0.Chapter 34. 1. ACR stands for Absolute Category Rating: this is the “regular” MOS test where speech samples are rated without being compared to a reference. SQI-MOS Output The output from the SQI-MOS calculation is a score on the ACR1 MOS scale which is widely used in listening tests and familiar to cellular operators. SQI-MOS for CDMA is implemented for the following codecs: • • • • QCELP13K EVRC SMV VMR-WB (narrowband input only) 34.2. for wideband.5 s (CDMA) 2–4 s Such a high update rate is possible thanks to the low computational complexity of the algorithm.60.15. CDMA SQI-MOS for CDMA closely resembles WCDMA SQI.4.1. compare section 34. Input parameters are: • • Frame error rate Speech codec used.85. and 12. 10.3. The score is thus a value ranging from 1 to 5.2.2.

also taking the fixed side into account. Wideband SQI-MOS (UMTS) It is necessary to point out that narrowband and wideband SQI-MOS scores are not directly comparable. 394 .4. 34. Alignment of SQI-MOS and PESQ The SQI-MOS algorithm has been designed to correlate its output as closely as possible with the PESQ measure (Perceptual Evaluation of Speech Quality).3. whereas SQI reflects the radio link quality only. At the time that work was done.org. Regarding the latter. as benchmarks. This means that 1. it is necessary to consider what speech bandwidth has been encoded. Narrowband vs.1. Old SQI (UMTS) The old SQI (still available in the application) is expressed in dBQ.2.1. however. Note carefully that PESQ and SQI-MOS do not have the same scope. A further complicating circumstance is that there is no simple mapping between wideband and narrowband SQI-MOS. This is completely different from the old SQI algorithm. the SQI-MOS models have mostly been trimmed using PESQ scores. This is because wideband speech coding models a wider range of the speech frequency spectrum and is thus inherently superior to narrowband coding. It should be stressed that SQI-MOS cannot be derived from these dBQ scores.1 User’s Manual 34. see section 34. in absolute terms. and no exact mapping exists in this case either. where adjustments to the models have been made using the results of external listening tests. See  www.1. SQI-MOS vs.3. 2.2 The exception is the wideband modes. PESQ measures the quality end-to-end. 34. for reasons sketched in section 34. The same MOS scale and range are used for both (as is the custom in the field of speech quality assessment). the two algorithms are distinct (even if similar in general terms).1 In fact. a given MOS score indicates.pesq.0. a higher quality for wideband than for narrowband. no objective speech quality measure of the caliber of PESQ was yet commercially available.4. that is. which was trained using listening tests alone. rather than actual listening tests. It follows from this that when interpreting a figure such as SQI-MOS = 4. The highest attainable quality is therefore markedly better for wideband.4.TEMS Investigation 14.

PESQ scores need to be averaged over a range of speakers in order to eliminate speaker bias.e. a mapping could then be applied to align the wideband scores to narrowband. but they do it in completely different ways.4.0 395 . Also bear in mind that PESQ and SQI-MOS use fundamentally different approaches to quality measurement: • PESQ is a reference-based method which compares the received degraded speech signal with the same signal in original and undistorted form. since the speaker-contingent variation is already built into the model (it has been trained with a large number of speakers). Such averaging is not required in the case of SQI-MOS. 34. One relevant fact is that.2). The use of PESQ as a benchmark therefore complicated the development of SQI-MOS for wideband.1 This difference in output range would not in itself be problematic if wideband PESQ behaved similarly to narrowband PESQ as a function of FER/BLER. is a no-reference method that works with the received signal alone and extracts radio parameters from it (as described in section 34. wideband PESQ has been found to produce lower scores than narrowband PESQ.Chapter 34. in certain circumstances. SQI-MOS. • Both methods try to assess to what degree the distortions in the received signal will be audible to the human ear. since CDMA SQI currently does not extend to wideband.1. variation stemming from the characteristics of individual speakers. Notes on PESQ for Wideband (UMTS) (This subsection is relevant for UMTS only. 1. This is a phenomenon independent of the circumstances described in section 34.3. even for clean speech. i.) The PESQ algorithm for wideband (8 kHz) speech coding – as opposed to that for narrowband (4 kHz) – is afflicted with certain recognized shortcomings. Below is a brief discussion of this topic. on the other hand. NT12-7002 ver 1. Speech Quality Index – SQI PESQ and SQI values may differ while both being accurate in their respective domains.

e.0. but so far with no satisfactory results. (It is probable that the task of assessing wideband speech quality requires further refinement of the mathematical models used. while the rock-bottom SQIMOS (the worst possible score. at zero FER/BLER). 2. it cannot of course provide more than a rough indication of speech quality. things are not that simple. “Quality in Clean Speech and Error Conditions”. Wideband PESQ is much more sensitive to speaker bias than is narrowband PESQ (compare the introduction of section 34. wideband PESQ scores for different speakers show a spread of more than one point on the MOS scale. Samples with FER > 60% were excluded from the SQI-MOS modeling.4): at a fixed FER/BLER. 1. FER = 60% was selected as endpoint. The largest correction was applied to the cleanspeech SQI-MOS score (i.) For the reasons explained above it was necessary to resort to other reference material besides PESQ scores in order to avoid biasing the wideband SQIMOS model.4). speech quality in GSM networks was often measured by means of the RxQual parameter (which is also available in TEMS products). This tuning resulted in an adjustment of the SQI-MOS model that is linear as a function of FER/BLER. attained at very high FERs/BLERs2) was left unchanged. Since RxQual is merely a mapping of time-averaged bit error rates into a scale from 0 to 7 ( 3GPP 45. section 8.5.2. See  3GPP TR 26. The material used was the results from listening tests conducted during standardization of the AMR speech codec. 34.1 Only clean speech ratings from these tests were used. version 7.008.975. 396 . this variability is limited to a few tenths of a MOS point. For narrowband. The upshot of this is that no straightforward mapping between wideband and narrowband PESQ can be constructed.1 User’s Manual Unfortunately. Attempts have been made within ITU to develop such a mapping. GSM Comparison with Other Radio Parameters In the past. since PESQ (as is well known) sometimes judges severely disturbed speech in a misleading manner: certain very bad (almost muted) samples receive high PESQ scores.TEMS Investigation 14. and consequently outputs from the two are not directly comparable.0.

• NT12-7002 ver 1. being a reference-based method that compares the degraded speech with the undistorted original to assess quality. can be purchased as an option with TEMS Investigation. The POLQA algorithm is designed along similar lines as PESQ. Audio Quality Measurement (AQM): General 35. it has been refined to eliminate known weaknesses of PESQ. Audio Quality Measurement (AQM): General Audio quality measurement. 35. The PESQ Algorithm PESQ. is the successor of PESQ and has been specially developed for HD voice.  www. including PESQ and POLQA.862.1. It can be performed in GSM. WCDMA. and VoIP. The severity of the degradation as perceived by human listeners is assessed using highly refined models of the human ear and the brain’s processing of auditory input. One example is the effects of packet loss and of packet loss concealment. defined in the ITU P. is an algorithm which measures end-to-end speech quality by comparing one party’s undistorted input signal (serving as reference) with the degraded version of the same signal received by the other party.0 397 .2. The PESQ algorithm is defined by the ITU-T standard P. 3G and 4G/LTE.Chapter 35. particularly in these areas: • Handling of new and complex types of distortions that arise from today’s convergence and coexistence of voice. superwideband).863 standard. The POLQA Algorithm POLQA (Perceptual Objective Listening Quality Analysis). and multimedia application services.862/en 35. short for Perceptual Evaluation of Speech Quality.int/ rec/T-REC-P. data. and CDMA networks. Performance for higher-bandwidth audio signals (wideband.itu. However.

More information about POLQA is available at  www. 35.1 User’s Manual • Performance for CDMA speech codecs and hence for CDMA networks in general.TEMS Investigation 14.3.863/en. Measurement Setups in TEMS Investigation Audio quality measurement (AQM) in TEMS Investigation can be done in a number of contexts and hardware configurations.2 37 38 VoIP Mobile to mobile 398 .int/rec/T-RECP. AQM modules Mobile Receiving Unit (MRU) Audio Capturing Unit (ACU) (2 PCs used) AQM modules AQM modules PC PCs 36.1 36. A summary of the possibilities is given in the following table: PESQ Service POLQA Call Parties Auxiliary Components AQM Computed By Ref. CS voice Mobile to fixed Mobile to mobile Mobile to mobile Call Generator.itu.

AQM with Call Generator/MRU In this AQM configuration. Please note that POLQA is not available with these configurations. These modules contain DSP hardware. NT12-7002 ver 1. The product version does however still support AQM with previously purchased MRUs. taking care of the uplink.1. and one housed in the Call Generator. MRUs are not offered for sale with TEMS Investigation 14. or by a Mobile Receiving Unit (MRU) housed in a mobile phone (section 36. The computation of AQM scores is done in dedicated hardware units called AQM modules: one connected to the phone and to the PC.Chapter 36. which is included on the TEMS Investigation installation CD in the subdirectory Documents. 1. connected to the fixed telephone network (section 36. handling the downlink.7.2). It is referred to by the M2F DL + UL option in the PESQ Measurement activity of the Service Control script (see section 20. The call may be received: • • by a stationary component known as the Call Generator. AQM with Call Generator/MRU 36. A separate MRU User’s Manual is also available. measurements are made mobile-originated voice calls.0 399 . Mobile-to-fixed Audio Quality Measurement with Call Generator This section describes the AQM setup where a Call Generator acts as the receiver of AQM calls.4). The downlink AQM module can optionally be mounted along with the phone in an equipment case. 36.1). Below is an overview of the measurement configuration.1.1 Further technical information about these methods of audio quality measurement is found in the document “AQM in TEMS Products (Including PESQ)”.16.

The downlink AQM data is written to regular TEMS Investigation logfiles. and volume. yielding uplink and downlink PESQ scores. • • 400 . The phone calls the Call Generator and plays the reference sentences.1. To merge uplink AQM data into the logfiles. The uplink AQM data is stored in XML files. logfile export Call Generator with uplink AQM module The measurement procedure can be summarized as follows: • • • The speech segments to be used as references are loaded into the AQM modules and into the test phone. Service Control script Reference audio Downlink AQM module Transmitted audio Test terminal Downlink AQM Received degraded audio (from Call Generator) Voice calls Logfile containing downlink AQM data Reference audio Uplink AQM data in XML files (copying/ download) Logfile with uplink AQM data merged in and downlink AQM data timeadjusted TEMS Investigation. The received (degraded) signals at either end are forwarded to the respective AQM modules. See section 11. the logfile export function is used. See Information Elements and Events.TEMS Investigation 14. where the signals are compared with the originals. echo attenuation. section 3. The AQM modules also record a number of further audio quality measurements such as echo delay. The Call Generator responds by playing the same reference sentences.1 User’s Manual TEMS Investigation.7.

2. as recipient of the AQM calls.4).Chapter 36. MRU. This is the M2M DL option in the PESQ Measurement activity of the Service Control script (see section 20. logfile export 36.7.1 is that the fixed Call Generator is replaced by a Mobile Receiving Unit. AQM with Call Generator/MRU 36. Measurement configuration: TEMS Investigation. the MRU does not have an AQM module. Mobile-to-mobile Audio Quality Measurement with MRU The main difference between this setup and that described in section 36.0 401 . Another important difference is that only downlink AQM scores are obtained with this method. Obtaining AQM Data Here is an overview of how to record and present audio quality measurements in practice. It covers the both the Call Generator configuration and the MRU configuration.16. NT12-7002 ver 1.3. Service Control script Reference audio Downlink AQM module Transmitted audio Test terminal Downlink AQM Logfile containing downlink AQM data Received degraded audio (from MRU) Voice calls Reference audio MRU (Mobile Receiving Unit) Logfile with AQM data timeadjusted TEMS Investigation.

section 10. set Measurement Type to “M2F DL + UL”. you must not adjust the volume using the headset. The phone will then make voice calls to a Call Generator (identified by its phone number). For mobile-to-mobile AQM. section 3. It is possible to perform such measurements with several phones at once. See section 20. Add a PESQ Measurement activity after the Dial.TEMS Investigation 14. since that would distort the AQM output.3. • Practical Considerations You can plug a headset into the AQM module during measurement to listen live to the received audio.1 User’s Manual 36. set Measurement Type to “M2M DL” to designate an MRU as receiving party in the same manner.e.3.2. 36.3. For mobile-to-fixed AQM.3. Recording AQM Data The description below assumes that a single phone is used to make audio quality measurements. Conclude with a Hang Up activity. One or several downlink AQM modules (either stand-alone units or DSP cards mounted in an equipment case). see chapter 20): – – Add a Dial activity. If you wish to synchronize AQM calls from multiple phones.1. set a value for PESQ Duration. using a different AQM module with each phone. Call Generator or MRU. Phone supporting audio quality measurement: one of those listed as AQM-capable in the Getting Started Manual.3. Finally. One AQM module is required for each phone that you want to measure AQM with. However. put the calls (i.16.3. • Compose a script as follows (for details of all activities.2.7. which governs how long to maintain the call and collect audio quality measurements. • • • Prerequisites You need to possess the following: License for collecting AQM data: see the Getting Started Manual.1.4. sequences of the form Dial  PESQ Measurement  Hang Up as just described) in separate branches in a Parallel – – 402 . • 36. The AQM algorithms require a fixed preset volume.

When using the AQM module for the first time after connecting it. however.7.4. To have the above procedure automatically repeated as many times as desired. although no uplink AQM data is recorded in that case. so that they can be included in any presentation. Note that this operation is necessary also for mobile-to-mobile AQM. This is because the logfile export procedure also corrects the time alignment for downlink data (again. • • • • 36.5. NT12-7002 ver 1.1. The same information elements are used regardless of the choice of AQM setup. the logfile export can be skipped. enclose everything defined so far within a While construct. – – • Book-end all of the above activities with Start Recording and Stop Recording to have the calls recorded in a logfile. Associate the phone with the AQM module on the Navigator’s Equipment tab: see section 9.5.0 403 . Merging Uplink AQM Data into Logfiles After completing your measurements. The red LED on the AQM module should go out.7. use the logfile export function to merge the uplink AQM data (recorded by the Call Generator) into the logfile. you must wait for the AQM module to start up its DSP and finish some preprocessing. Run the script and record your logfiles. Make sure that the phone’s number is defined in TEMS Investigation and enter the number manually if necessary: see section 8. which already contains the downlink AQM scores. section 7. 2” and “Pre Processing Ready” appear in the Mode Reports window.2). Presentation of AQM Data Information Elements All AQM data is available as information elements. To also make all calls terminate at the same time.2.2. If precise time alignment for AQM data is not of interest.Chapter 36.10. See section 11. 36. see section 11.7. Connect your AQM equipment case (or alternatively your phone and stand-alone AQM module) to the PC and point to the requisite driver files as described in the Getting Started Manual. AQM with Call Generator/MRU construct.1.3. 36. Wait until the reports “Dsp Started Ver. simply use the same PESQ Duration for all calls.

5 s. When you merge the uplink AQM data into the logfile.) 36.5 s offset for downlink data is removed so that all data is correctly aligned. you must keep in mind that this data will lag behind other information elements because of the processing delay in the DSP. section 11.1 User’s Manual Status windows named Speech Quality are provided where all AQM information elements (as well as some other data) are presented.7. 404 .1.2. or one speech sentence. When viewing (downlink) AQM data in real time. see section 11. or when analyzing a logfile where the uplink AQM data has not yet been merged in.5. The offset is 5. the 5. (For full details. See the Technical Reference.TEMS Investigation 14.2. Downlink Frequent AQM is not displayed at all prior to merging. PESQ Key Performance Indicator A PESQ-based KPI is computable on the basis of TEMS Investigation data.5.

NT12-7002 ver 1. which call each other in pairs. are connected to an Audio Capturing Unit (ACU) which relays the audio to the PC.7. all measurement is conducted during mobile-tomobile voice calls.0 405 .16. Up to four mobile devices.1. AQM with Audio Capturing Unit (ACU) 37. Obtaining AQM Data Here is an overview of how to set up the Audio Capturing Unit AQM configuration and how to record audio quality measurements. AQM with Audio Capturing Unit (ACU) In this AQM configuration. Service Control script Voice calls Reference audio AQM calculation Audio Audio Capturing Unit Test terminals Relayed degraded audio Logfile with downlink and uplink AQM scores Voice calls 37.4). This configuration is referred to by the M2M DL + UL option in the AQM Measurement activity of the Service Control script (see section 20. TEMS Investigation.Chapter 37.

Nokia C7 Sony Ericsson W995 phones use the SE System Connector cable from the AQM module cable kit. use a Parallel activity with one branch for each phone.2.TEMS Investigation 14. Preparations See the Getting Started Manual.3. Audio adaptor cables for connecting audio cables to the ACU (delivered with ACU). 37. USB hub for phones (delivered with ACU).3.2. section 10. • Compose a script similar to the sample script files which are provided in [My] Documents\TEMS Product Files\TEMS Investigation 14.2. chapter 16.4. The diagrams in section 37. section 3. For each phone pair. Recording AQM Data This section assumes that all equipment has been prepared and interconnected as described in the Getting Started Manual. 37. refer to section 20.16. one dialing and the other answering.1.1\Scripts. Custom audio cables (these are phone model specific and need to be ordered separately): – – – • 2. Audio Capturing Unit (TerraTec DMX 6Fire USB). chapter 16.3.1.3.7.1 User’s Manual 37.1. Regarding the AQM Measurement activity.1. • 406 .5 mm cable for Sony Ericsson Xperia arc/arc S. • • • • • Prerequisites You need to possess the following: License for collecting AQM data: see the Getting Started Manual.5 mm cable for Huawei C8600 3. Phone supporting audio quality measurement: one of those listed as AQM-capable in the Getting Started Manual.1 below show the structure of the ready-made scripts.1. Run the script and record your logfiles.

37.1. in the TerraTec PC user interface. If the volume is not kept constant. or in Windows. Recommended Structure of AQM Scripts AQM script for one pair of phones. AQM with Audio Capturing Unit (ACU) Note: Be sure never to alter volume levels anywhere during measurement – whether in the phones. on the TerraTec box using the physical controls.3.Chapter 37. NT12-7002 ver 1. incorrect AQM scores will result.0 407 .1.

however. Not all AQM information elements are obtained: see the Information Elements and Events volume. for example.1 User’s Manual AQM script for two pairs of phones. so that they can be included in any presentation. 37.1. are relevant only when interacting with a PSTN. 37. that for AQM with ACU the following holds: • • Downlink PESQ/POLQA scores for one phone in a pair are also presented as uplink scores for the other phone in that pair.2. Presentation of AQM Data Information Elements All computed AQM data is available as information elements.2. The “Echo” elements. so they are not populated in this mobile-to-mobile setup. The same family of information elements is used as for the Call Generator and MRU AQM setups. 408 .TEMS Investigation 14. chapter 5. Please note.

a kind of filtering that is judged unfavorably by the AQM algorithms.Chapter 37. By contrast. CDMA For CDMA. AQM with Audio Capturing Unit (ACU) Status windows named Speech Quality are provided where all AQM information elements (as well as some other data) are presented. UMTS Notes on AQM Scores Obtained with Individual Phone Models For UMTS. – Please note again that the above does not apply to the Xperia arc S. namely when the Sony Ericsson Xperia arc (Note: not arc S) acts as sender. The described characteristics of the Xperia arc must be taken into account when evaluating AQM scores obtained with the device. There is one exception. the AQM score is not affected. causing a lowering of PESQ/POLQA scores.3.0 409 . The reason is believed to consist in the different filtering applied to the audio output in the Xperia arc phone. the Huawei C8600 exhibits behavior similar to that of the Sony Ericsson Xperia arc. NT12-7002 ver 1. PESQ and POLQA scores obtained with various phones using the setup described in this chapter generally correlate closely with PESQ as measured with AQM modules (chapter 36). 37. with any of the supported UMTS phones as receiver. for audio samples received by the Xperia arc. Tests consistently show markedly lower PESQ and POLQA scores with this configuration compared to other phone model pairings.

found on the TEMS Investigation installation CD in the subdirectory Documents. AQM for VoIP Audio quality measurement can also be performed during VoIP testing. each of which have a mobile phone connected. Everything about the Service Control mechanisms is covered in section 20.TEMS Investigation 14. The AQM computation is done on the PCs. but instead two PCs are used. A quick overview of the measurement setup follows below: TEMS Investigation: VoIP client controlled by Service Control script PC #1 Reference audio Received degraded audio VoIP server VoIP calls TEMS Investigation: VoIP client controlled by Service Control script Reference audio PC #2 AQM calculation #1 Test terminals #2 Received degraded audio AQM calculation Logfile containing downlink AQM for test terminal #1 Logfile containing downlink AQM for test terminal #2 410 . For a comprehensive treatment of VoIP testing.16.7. VoIP testing is controlled by special Service Control activities. and the audio quality measurement is governed by the VoIP Voice Quality activity. please turn to the document “VoIP Testing with TEMS Investigation”. In this measurement setup. including AQM.1 User’s Manual 38. no auxiliary hardware components are involved.

Chapter 38. the VoIP clients thus reside in the PCs and not in the mobile devices. which see. Audio is sent in semi-duplex fashion between the parties. section 3. AQM for VoIP The calling device is connected to one PC and the called device to the other.9.2. that is. 38.0 411 . Presentation of AQM Data This too is covered exhaustively in the document “VoIP Testing with TEMS Investigation”.1. Each instance of TEMS Investigation has a built-in VoIP client. The crucial information elements are the PESQ and POLQA IEs in the Media Quality category: see Information Elements and Events. 38. Obtaining AQM Data Full instructions are given in the document “VoIP Testing with TEMS Investigation”. NT12-7002 ver 1. in both directions but only in one direction at a time.

4. General Properties of VTQI Like SQI (chapter 34).1).2.1. conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests. The kind of subjective test which VTQI strives to imitate is one where viewers are instructed to assess both video and audio and combine their perception of each into an overall “multimedia quality” score. VTQI is a no-reference method which judges the quality of the received signal on its own merits. • What VTQI Is Based On The VTQI score is based on the following non-perceptual input: The quality of the encoded (compressed) signal prior to transmission. since the radio bearer currently used in UMTS for video 412 . How this algorithm works is the subject of the present chapter. There is no overall assessment of entire calls analogous to static VSQI computed for entire streaming clips (as described in section 40. However. without knowledge of the original. It is updated continuously during the call. This quality is straightforwardly a function of the codecs used and the bit rate. 39. The unit for VTQI is called “MOS-VTQI”.1 User’s Manual 39. See also the document “Video Telephony Quality Measurement with VTQI” which is included on the installation CD in the subdirectory Documents. The output from the VTQI algorithm is expressed as a value between 1 and 5. 39. VTQI estimates the quality of the video call as perceived by the viewer at a moment in time. Video Telephony Quality Index – VTQI The information element VTQI (Video Telephony Quality Index) estimates the viewer-perceived video and audio quality achieved during video telephony calls.TEMS Investigation 14.

263. This leaves the codecs: – For the H.Chapter 39. Update Rate VTQI is reported as the information element VTQI Realtime Score. This is the most important single cause of poor quality in video telephony.0 413 . This element is updated regularly – at intervals of length 1–2 s depending on the phone model – throughout the video call. the video codec is assumed to be H.2 kbit/s. In practice. that is. This windowing procedure prevents short block error bursts from impacting the VTQI score in a disproportionate manner. bit rate variation is in fact not an issue. Focusing on BLER means that VTQI will faithfully reflect the impact of air interface conditions on QoE.3. What VTQI Does Not Consider VTQI does not directly consider the signal presented to the human viewer. on the other hand. 39.) The audio codec is assumed always to be AMR-NB operating at 12.4.263 and MPEG-4 video codecs. even slight degradations impacting video and audio perception will still be noticed by the algorithm and affect the VTQI score. Bit error rate (BER). (In the current implementation of VTQI in TEMS Investigation. what codec is used in the video call is deduced from the signaling between server and client. but a VTQI model for MPEG-4 also exists. the “clean” quality in terms of VTQI has been computed in advance. – • BLER (block error rate). is not reported by current WCDMA user terminals and so is not available for use in the VTQI model. The transferred video is not analyzed frame by frame in any way. Video Telephony Quality Index – VTQI telephony is always a 64 kbit/s bearer. Thanks to the monitoring of BLER. NT12-7002 ver 1. however. no analysis of perceptual input is performed to detect specific visible artifacts. Each VTQI score is a time average taken over the last 8 seconds. the first score is thus obtained 8 s into the video call. 39.

414 . Compare chapter 41 on MTQI.1. The “clean” quality has been computed in advance for the codecs listed in section 40. The quality of the encoded (compressed) signal prior to transmission. conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests. General Properties of VSQI Like SQI (chapter 34). The information actually used by the VSQI algorithm is the video codec type and the total (video + audio) bit rate. This quality is straightforwardly a function of the video and audio codecs used.2. What VSQI Is Based On The VSQI score is based on the following non-perceptual input: 1. Video Streaming Quality Index – VSQI The information element VSQI (Video Streaming Quality Index) estimates the viewer-perceived video and audio quality achieved during video streaming sessions. This chapter takes a look the VSQI algorithm. without knowledge of the original. VSQI is a no-reference method which judges the quality of the received signal on its own merits. 40.1. The unit for VSQI is called “MOSVSQI”. See also the document “Video Streaming Quality Measurement with VSQI” which is included on the installation CD in the subdirectory Documents. 40. and their bit rates.1 User’s Manual 40. The output from the VSQI algorithm is expressed as a value between 1 and 5. The kind of subjective test which VSQI strives to imitate is one where viewers are instructed to assess both video and audio and combine their perception of each into an overall “multimedia quality” score.4.TEMS Investigation 14.

H.4. Static and Dynamic VSQI Two versions of the VSQI algorithm have been devised: one static and one dynamic version. Video Streaming Quality Index – VSQI 2. 40. Input parameters to the static version of VSQI are as follows: • • • • • • Video codec used (H. Thanks to the monitoring of packet loss (item no.0 415 . or MPEG4) Total bit rate (video + audio) Duration of initial buffering Number of rebuffering periods Duration of rebuffering periods Amount of packet loss With some degree of simplification. jitter. 40. 40.4. What VSQI Does Not Consider VSQI does not directly consider the signal presented to the human viewer.3. The transferred video is not analyzed frame by frame in any way. 2 in section 40. however.2 above). It does not appear as an information element. that is.e.263. in the video streaming client). Dynamic VSQI.1. 3. The amount of packet loss at the application level (i.Chapter 40. The amount of initial delay and the subsequent interruptions during playback of the video sequence: that is. on the other hand. Static VSQI The static version of VSQI takes an entire streamed video clip as input and assigns a single quality score to it. is contained in the information element Streaming VSQI. no analysis of perceptual input is performed to detect specific visible artifacts.264. Static VSQI is presented in the event Streaming Quality VSQI. we may describe the calculation of static VSQI with the following formula: NT12-7002 ver 1. and so on will still be noticed by the algorithm and affect the VSQI score. even slight problems with blockiness. the time required for initial buffering and the incidence of rebuffering.

which is in turn dependent on the choice of codecs and bit rate. This score is determined by the quality of the encoding. The design of dynamic VSQI is based on the following: • Previous research suggesting approximate times taken for the perceived quality to drop to MOS-VSQI 1 (during buffering) and to rise to the highest attainable VSQI (during normal replay) Modeling of the impact of packet loss on perceived quality • 416 . and moreover if the clip is short enough it will have been buffered in its entirety before the replay starts. simply because the late ones are remembered more vividly. Dynamic (Realtime) VSQI The dynamic or realtime version of VSQI estimates the quality of a streaming video clip as perceived by viewers at a moment in time.2. since the current VSQI algorithm does not take into account such memory effects. so that no rebuffering will ever occur. A running packet loss average over the last 4 s is computed approximately every second.TEMS Investigation 14. the time spent rebuffering. For clips considerably longer than 30 s. and the number of rebuffering events. The static VSQI algorithm has been fine-tuned for clips of around 30 s and should therefore in practical use be applied to clips of similar duration. and the values thus obtained are weighted and summed to yield an appropriate overall measure of the packet loss. Each VSQI output value is dependent on the recent history of the streaming session (i. disturbances towards the end will be more harshly penalized by viewers than those occurring early on. The size of the packet loss penalty is determined as follows. It is updated regularly – at intervals of the order of 1 s – while the video clip is playing. VSQIclean is the “clean value” obtained for the clip prior to transmission. it would probably perform slightly worse for long clips. Therefore.e. recent packet loss levels and possible recent buffering events).4. (The dynamic version of VSQI is naturally not affected by this limitation. The latter is then translated into a deduction from the VSQI score.) 40. The size of the buffering penalty depends on the time taken for initial buffering. The video sequences must not be too short because of how the buffering works: each instance of rebuffering takes several seconds to complete.1 User’s Manual Here. on the other hand.

After the replay has recommenced. 1. the perceived quality picks up again and soon approaches the highest achievable level. The best achievable quality. 2. Once the replay gets going. The user tolerates (and might even expect) a certain amount of initial delay. is dependent on the codec/bit rate combination but is also affected by the amount of packet loss. but the longer the buffering drags on. Rebuffering events are much less tolerated by viewers than initial buffering. i. the more the user loses patience. If rebuffering occurs. VSQI captures the latter by making the slope of the curve steeper for each new rebuffering event.0 417 . the “ceiling” in the graph.Chapter 40. VSQI recovers reasonably quickly. 3.e. but not infrequently from a rock bottom level. VSQI deteriorates rapidly. especially if repeated. NT12-7002 ver 1. In this example the packet loss is assumed to be constant so that the influence of buffering can be clearly discerned. Video Streaming Quality Index – VSQI • Tailoring of mathematical functions for expressing viewer annoyance/ satisfaction as a function of time (in each of the states that are possible during replay) Codec and bit rate parameters as in the static version • The graph below shows in rough outline the different ways in which dynamic VSQI can evolve during the replay of a streaming video clip. 4.

Unlike VSQI. MTQI does not include an assessment of audio quality. H. Buffering with skipping means that frames are skipped in connection with buffering. REAL. QVGA • • 418 .264. MPEG4 Supported video formats: QCIF. Supported video codecs: H. Mobile TV Quality Index – MTQI MTQI (Mobile TV Quality Index) is a refinement of the video part of the VSQI quality measure (see chapter 40). The MTQI algorithm can be concisely characterized as follows. no skipping means that every frame is replayed. • Algorithm components: – – – • Modeling of clean quality Modeling of packet loss Modeling of corruption duration (total duration of corrupted frames) Buffering with and buffering without skipping are distinguished.TEMS Investigation 14.263.1 User’s Manual 41.

42. it may produce misleading results. It should however be noted that the C/I measure is just as useful in the context of packet-switched data services. SQI (see chapter 34). In the past. speech quality is not further improved. it is difficult to pin down the frequencies that are affected by the degradation.2. one must take into account the possible use of power control and/or discontinuous transmission (DTX). The C/I measurement function built into TEMS Investigation enables the identification of frequencies that are exposed to particularly high levels of interference. The discussion provided here is centered on the voice service. Requirements on a Robust C/I Measure Downlink quality in a radio network can be monitored using the TEMS Speech Quality Index. particularly if EDGE is used. By NT12-7002 ver 1.Chapter 42. To obtain a correct C/I estimate. if frequency hopping is used in the network. something which comes in useful in the verification and optimization of frequency plans. while packet-switched transmissions very clearly do benefit from every extra dB. C/I Measurement (GSM) This chapter explains in some detail how GSM C/I measurements are made and why they are useful. towards the high end of the C/I range. C/I can be measured in dedicated mode. However. areas with inadequate quality can be identified.0 419 . In this way. To help resolve such ambiguities. TEMS Investigation offers the possibility of measuring average C/I for each of the frequencies used in a call. Why Measure C/I? The carrier-over-interference ratio is the ratio between the signal strength of the current serving cell and the signal strength of undesired (interfering) signal components. Since such a scheme fails to allow for power control and DTX on the TCHs. In fact.1. C/I Measurement (GSM) 42. rough C/I measurements have sometimes been carried out by comparing the BCCH signal power of the serving cell with that of neighboring cells using the same traffic channels (but different BCCHs). 42.

and four frequencies are used for transmission. If true C/I is within the range 0 to 15 dB. which is equal to the ordinary measurement interval. The C/I information elements preserve a wider value range –5 . 35 dB. the limitation of the measurement range is not a restriction. Hence. If frequency hopping is employed. and there are no DTX interruptions. 42. data from a test drive is depicted in the figure below. in addition.1 User’s Manual contrast. The measurement range extends from 0 dB to 35 dB. if four frequencies are used.TEMS Investigation 14. With more frequencies. the performance is not further improved (at least not with today’s modulation schemes). TEMS Investigation does consider these network functions and is thus able to indicate the actual C/I experienced by the phone. average C/I is presented approximately twice a second.1 If downlink DTX is used. there are fewer bursts for each frequency. 420 . 42. 25 bursts (on average) per frequency are received in each half-second (to be precise. EFR speech coding and cyclic 1. Accuracy The number of hopping frequencies determines the number of bursts used for the C/I measurement on each frequency. if the number of hopping frequencies is low. An Example To illustrate the use of C/I.4.. 480 ms) interval. TEMS Investigation makes measurements only on the bursts actually sent from the base station and disregards bursts not transmitted. 42. Beyond the upper limit. This implies that the accuracy of the measurements is better for small sets of hopping frequencies.5. For example.. Details on C/I Measurements In dedicated mode. which reflects the performance of older technology. the average C/I for each frequency is presented. The test drive lasts 40 seconds. A C/I below 0 dB can be regarded as highly unlikely. depending on the speech activity level on the transmitting side. the number of bursts transmitted from the base station to the phone may be lower than the maximum. C/I values below this limit would normally result in a dropped call.3. the measurement error is typically smaller than 1 dB.

This explains the poor speech quality. the quality problem is to do with interference rather than coverage. Such information can then be utilized in the process of optimizing the frequency plan for the area. one sees that two of the four frequencies (the thick lines) have a C/I worse than 10 dB during the SQI dip. while the lower part shows C/I for each of the four frequencies: 20 SQI 60 50 0 0 25 C/I [dB] 20 15 10 5 0 0 RxLev 40 10 15 20 25 time [s] 30 35 40 5 5 10 15 20 25 time [s] 30 35 40 As appears from the upper graph. SQI dips sharply towards the end of the test drive (after 35 s). identifying precisely which channels are disturbed. indicating poor speech quality.Chapter 42. and interestingly. RxLev stays about 50 dB above –110 dBm the whole time.0 RxLev [dB] SQI [dBQ] 421 . This means that the dip in quality is not due to low signal power level. In fact. that is. looking at the C/I graph. NT12-7002 ver 1. probably because the power of the interferer increases. The upper part of the graph shows SQI and RxLev. C/I Measurement (GSM) frequency hopping with four frequencies are employed throughout. On the other hand. Now. RxLev increases during the SQI dip.

To reduce the testing time. each row corresponds to a particular combination of BCCH and TCH. 422 .12) to be able to perform GSM channel verification. you can use several phones. • The GSM Channel Verification Window To perform GSM channel verification. one BCCH/TCH combination. 43. open the GSM Channel Verification window from the Control folder on the Navigator’s Menu tab. Throughout the present chapter.1. TEMS Investigation lets one or several GSM-capable Sony Ericsson phones1 make calls repeatedly on the chosen channels until all timeslots of interest have been tested. In this window.e. traffic channel verification may take a non-trivial amount of time to complete.1 User’s Manual 43. 1. i.TEMS Investigation 14. Since there is no way for TEMS Investigation to control the timeslot allocation. Sony Ericsson phones with both GSM and WCDMA capability must be locked on GSM (see section 9. the following terminology will be used: • Test case: One row in the GSM Channel Verification window. typically those used in one cell or a set of cells.1. GSM Channel Verification The GSM Channel Verification tool allows you to check the availability of a set of GSM traffic channels.

Chapter 43. Test case group: All test cases with the same BCCH. with BCCH in timeslot 0 and TCHs in timeslots 2–7. NT12-7002 ver 1. Note that a special test case must be prepared to test TCH timeslots on C0. Test: All rows in the window. corresponding to one cell. click Add. TCH = 20}. Example: If C0 has ARFCN 10. The following dialog appears: MS BCCH ARFCN TCH ARFCN The phone that should execute this test case. Adding a Test Case To add a test case. or in other words the complete contents of the *. The ARFCN of the BCCH to be tested. TCH = 10} and one with {BCCH = 10. Band Timeslot The frequency band where the channels are located.2.0 423 . and C1 has ARFCN 20. GSM Channel Verification • Group.11). Check the timeslots you wish to test. then you must prepare two test cases: one with {BCCH = 10. The ARFCN of the TCH to be tested.tch file (see section 43. • 43. Note that test case groups are not explicitly separated in the user interface.

but you do have the option to create a report on these results (section 43. the call must be set up correctly and maintained for a user-specified period of time.TEMS Investigation 14. Manual Verification There are two fundamentally different ways of performing channel verification. by clicking either of two buttons. 43. you decide yourself whether to accept or reject the result of the test. select it and click the Delete button. 43. In order for a timeslot to pass. That is.11). The result in the GSM Channel Verification window will look like this: Here. and in addition a set of user-specified quality requirements must be satisfied. Automatic vs. • Automatic verification: For each timeslot. Editing and Removing Test Cases To edit a test case. Manual verification: For each timeslot.8).4. select it in the GSM Channel Verification window and click the Edit button. Note that to edit a test case which has been partially executed.10) or save the test case in a special file format (section 43.3. TEMS Investigation decides whether the timeslot can be accepted or not. you must reset the test case (section 43.1 User’s Manual You can add multiple test cases without exiting the dialog. timeslots to be tested are indicated by full stops (“. • 424 . while timeslots not concerned by the test are marked by underscores (“_”).”). To remove a test case. you cannot keep any of the old test results in the window. by entering the settings for one test case at a time and clicking Apply after each.

. Choose Manual or Automatic (see explanation above). Manual verification is more work-intensive and probably more timeconsuming.0 425 . #. or you might want to “call a friend” in each instance to have the uplink quality checked as well. NT12-7002 ver 1. Automatic verification can be done more quickly. GSM Channel Verification How to take this decision is up to the user. click the Properties button. You choose how to perform the test in the Properties dialog.. In the GSM Channel Verification window. Verification mode Test phone number Add MAIO and HSN. Valid characters in the phone number are {*. You might be content with assessing the downlink quality by calling a service such as the speaking clock. but also yields an improvement in reliability proportional to the work invested. +. 0–9}. Enter the phone number to call when testing. but is a less reliable indicator of what a user’s experience of the radio conditions would be like.10) for any test case that fails in automatic verification mode.Chapter 43. Check this to have the Mobile Allocation Index Offset (MAIO) and the Hopping Sequence Number (HSN) indicated in the test report (section 43.

43. Delay time before evaluation Approve timeslot if these conditions are met: The time to wait before evaluating the quality parameters. Activating Phones Before running the test you must naturally activate the phones assigned to do the testing. The conditions will be evaluated at one point in time. See section 8. only one phone can be used. 426 . i.4.e. Check the conditions you want to use.TEMS Investigation 14. and specify thresholds. they are ANDed together.1 User’s Manual • Choose the QoS parameters tab to stipulate conditions for accepting a timeslot in automatic verification mode. namely as soon as the delay period has expired. The checked conditions must all be satisfied in order for the timeslot to be accepted. Note: In manual verification mode.5.

6. If all timeslots in the test case are now accepted. An accepted timeslot will be marked with a green rectangle (with an “h” for hopping channels).3. Activated the phone or phones to be used in the test. Note that there is no requirement to keep test case groups apart in the GSM Channel Verification window. although it may of course be practical to do so. this timeslot is tested for all channels in the hopping sequence at once. the status of the test case will change to Passed. While the test is running. In the frequency hopping case.1). Manual Verification If you have chosen manual verification.Chapter 43. in the order they have been entered.4.6. 43. If you have listed several test case groups (see section 43. having locked the phone on the corresponding BCCH. NT12-7002 ver 1.1.1–43. the application will now wait for you to either accept or reject this timeslot. it is marked with a question mark in a gray box. they will be executed one at a time. Then. handover is disabled. TEMS Investigation will now start attempting calls on the TCHs specified. GSM Channel Verification 43.2. When the testing of a timeslot begins. so that multiple gray boxes appear. • • • Running the Test Getting Started To be able to execute a test you must have done the following: Prepared your test cases according to sections 43. click Accept. and indicated a phone number to call: see section 43.6. To accept a timeslot. as are all other phone control functions in TEMS Investigation. 43. The test cases currently executed are tagged with a blue arrow in the leftmost column. to start running the test currently displayed in the GSM Channel Verification window: Click Start. Chosen manual or automatic verification mode.0 427 .

and a new call is begun immediately. the Accept and Reject buttons are disabled.1 User’s Manual To reject a timeslot. When a timeslot is allocated which has already been accepted or rejected. Automatic Verification If you have chosen automatic verification. click Reject. When a call is made in a previously accepted or rejected timeslot. and a new call is made within a few seconds. the application proceeds to make a new call. the application will itself accept the timeslot (if possible).13. The test case will ultimately be put in status Failed. otherwise it will try to make a new call the next time this timeslot is allocated. A rejected timeslot will be marked with a red rectangle (with an “h” for hopping channels). 43. the call is aborted (not affecting the earlier result).3. see section 43. Example Here is an example of an ongoing verification session: The cell described by the first three rows (tagged with blue arrows) is under test. so any timeslot tested will be verified for all three TCHs at once. within certain limits. When you have made a decision. though not until all timeslots have been either accepted or rejected. At this point. Automatic verification never rejects a timeslot. Manual verification has been chosen.4. 43.TEMS Investigation 14. the user has accepted the performance 428 .6. but keeps attempting calls indefinitely. marking it green .6. Frequency hopping is used in this cell (as shown by the “h” symbols).

it must be stopped first. Resetting a Test Case You can erase the results for a test case by resetting it. Execution of this test case is ongoing. GSM Channel Verification of timeslots 3 and 6 (green markers).7.9. If the test is executing. which is indicated by question marks. Timeslot 4 is currently being tested. The test will continue from the point where it was halted. This is also indicated in the leftmost column by a blue arrow . 43. just click Start again. Execution of this test case has been begun but the test is currently stopped. or: The test case has been reset. To resume the test. Stopping the Test In order to stop the test currently running: In the GSM Channel Verification window. Summary of Test Case Status Values A test case has one of the following status values: Status Value Not tested Testing Stopped Passed Timeslot(s) rejected Meaning No work done yet on this test case. 43. All timeslots in the test case have been accepted. while rejecting timeslot 7 (red markers). click Stop. 43. At least one timeslot in the test case has been rejected. All test cases that are in status Testing will change to Stopped.0 429 . the test case will be processed from scratch again. The status value of the test case reverts to Not tested. when execution is resumed. All test cases that are not finished will be put in status Testing again.Chapter 43. NT12-7002 ver 1.8.

1 User’s Manual Status Value Call lost BCCH lost Invalid TCH Timeout MS not connected Call setup failure Meaning These status values signify errors. an HTML report can be generated summarizing the results obtained so far.10. and select an output location for the HTML file. The error condition is also indicated in the leftmost column by the symbol . it must be stopped first. Test of timeslot not yet completed. click the Report button. see section 43. Timeslot rejected. Timeslot not included in test.13. Status values are as in the GSM Channel Verification window. Meaning 430 . Creating Test Reports At any stage of execution of a test.TEMS Investigation 14.) The report indicates • • • • the verification mode: manual or automatic the test phone number the QoS parameter settings the test result for each timeslot (where available) as well as the status of each test case at the time of creating the report. To generate a test report.9. See section 43. In case of call setup failure. (If the test is executing. 43. the used MAIO and HSN is indicated for that test case. Timeslots are marked with one of the following: Timeslot Data OK FAIL TESTING – Timeslot accepted.

tch. Error Conditions In certain situations the application judges it impossible to complete the verification and therefore aborts the test. Notes on Performance It is possible to speed up the verification process by letting several phones share the work. as soon as a timeslot is accepted by one phone. The test cases affected by the error executed are tagged with the symbol in the leftmost column. If several phones are set to execute identical test cases. as a rule. Saving and Opening Tests Channel verification tests can be saved to file at any stage of execution. (The test must be stopped first. or you may do both.Chapter 43. to begin with they will all work independently. ongoing call has been lost). Cause NT12-7002 ver 1. it is marked green for all other identical test cases.e. However. One idle mode report received from wrong cell while in dedicated mode (i. You may assign different test cases to different phones. The status value of the test case indicates what has gone wrong: Status Value Call lost Two possible causes: • • Two idle mode reports received while in dedicated mode (i. or assign identical test cases to several phones. 43.0 431 . and no phone will test it further. GSM Channel Verification 43.11. lock on BCCH has broken down). considerably reduce the time taken to perform the test. The test will be saved in a file with extension .12. click Open and select your file. click Save.13.) The file will include full information on the results obtained so far and on the status of each test case at the time of saving. This will. To open a previously saved *. To save the complete current contents of the GSM Channel Verification window.tch file. 43.e.

e.TEMS Investigation 14. Timeout MS not connected 432 .1 User’s Manual Status Value BCCH lost Two possible causes: • Cause No channel report received from correct BCCH for 20 seconds after previous successful locking on this BCCH (i. Three idle mode reports from wrong cell or two no service reports received while trying to lock on BCCH (i.e. Phone not activated at start of measurement. lock on BCCH has failed). • Invalid TCH Test case attempted 10 times in a row without the right TCH being allocated. Ten consecutive calls made where the call setup procedure could not be concluded successfully. lock on BCCH has broken down). and no timeslots marked green or red (typically occurs when the chosen TCH is in fact not used where assumed).

0 433 .1. Keyboard Shortcuts Appendix A.Appendix A. Keyboard Shortcuts A. Drive Testing Shortcuts Function Shortcut F2 Ctrl + F2 F5 F6 Activate all Deactivate all Insert filemark Start recording NT12-7002 ver 1.2. General Shortcuts Function Shortcut F1 Alt + F4 F11 F12 Ctrl + Tab Ctrl + M Ctrl + N Ctrl + O Ctrl + P Ctrl + R Ctrl + S Help Exit application Previous worksheet Next worksheet Focus on next window in worksheet Open TEMS Settings Manager New workspace Open workspace Print workspace Generate logfile report Save workspace A.

Bar Chart Function Show properties Show setup wizard (status window only) Message Window Function Show only messages of this type Hide messages of this type Undo (show only/hide) Find next message of this type Shortcut Shift + P Shift + W Shortcut Ctrl + Y Ctrl + H Ctrl + Z Right arrow 434 .3.TEMS Investigation 14.1 User’s Manual Function Stop recording Shortcut Ctrl + F6 A. Logfile Load Shortcuts Function Shortcut Shift + F10 Ctrl + F10 Open logfile Stop logfile load A. Shortcuts for Active Window Function Shortcut Ctrl + P Print window Status Window.4. Line Chart.

0 435 . Some route sample must already be selected.Appendix A. Keyboard Shortcuts Function Find previous message of this type Search for message Search again Map Window Function Open Layer Control dialog Open Theme Settings dialog Activate zoom in Activate zoom out Go to first route marker 1 Shortcut Left arrow Ctrl + F F3 Shortcut Alt + L Alt + T Shift + Z Alt + Shift + Z Home Left arrow Right arrow End Step to previous route marker Step to next route marker Go to last route marker1 1. Service Control Designer Window Function Select all Copy New script Open script Save script Shortcut Ctrl + A Ctrl + C Ctrl + N Ctrl + O Ctrl + S NT12-7002 ver 1.

TEMS Investigation 14.1 User’s Manual Function Paste Cut Shortcut Ctrl + V Ctrl + X 436 .

lch .mex .pex .evt .log .0 437 .config .cel . File Types in TEMS Investigation Appendix B.eth .trp File Type Setup file for ArcView format logfile export Bar chart export file Cell file Service Control configuration set Setup file for Ethereal format logfile export User-defined event Logfile exported in text format Line chart export file TEMS Investigation logfile (old format) Map window export file Setup file for MapInfo format logfile export Message window export file Setup file for Planet format logfile export Setup file for logfile report Status window export file Audio indication for event TEMS Investigation workspace Setup file for text format logfile export TEMS Investigation logfile (current format) NT12-7002 ver 1.rpt .tex .aex .bch .Appendix B.stm .fmt .mw .svt .map .tdc . File Types in TEMS Investigation These TEMS-specific file types are used by TEMS Investigation: Extension .

tsc Service Control script File Type 438 .1 User’s Manual Extension .TEMS Investigation 14.

in presentation windows.1. see the Getting Started Manual. which serve similar purposes. The Equipment Configuration window and the Connections toolbar were removed. Their functions were moved into the Navigator (Equipment tab.2 for a comparison of the old and new tools. • • Equipment Handling The Equipment Control toolbar was removed.0 versions of TEMS Investigation.0 underwent major changes compared to previous product versions. However. NT12-7002 ver 1. section 7. top pane). Status information is also provided by the Status Control Monitor window.1.0 User Interface Appendix C. Comparison with Pre-12. For devices there is no longer any need to deal directly with Windows COM port numbers or to configure dial-up connections in Windows dialogs (Dial-up Networking). All of its functions were taken over by the newly introduced Equipment tab in the Navigator. there is one exception. The “equipment channel” concept is not used in the Navigator or in the Service Control windows (where only the designation “EQ” appears).1 • • • 1. The Command Sequence window was replaced by the windows Service Control Designer and Service Control Monitor. A few pointers regarding these changes may be helpful to users with experience of pre-12. the equipment channels “MS” and “DC” still make an appearance. The instruction sequences used to control devices are now referred to as scripts.Appendix C.0 User Interface The user interface in TEMS Investigation 12. Comparison with Pre12. With regard to COM ports. C.0 439 .2. See section C.

• Logical Structure • Activities in SCtrl scripts are always assigned simply to the device as a whole (i. Command Sequences This section contrasts the Service Control (“SCtrl”) feature with its pre-12. There are no longer any “enable” or “disable” operations for devices. then manually activated and deactivated. and Synchronize operations.1 User’s Manual • The procedure of preparing a device for use was simplified. bottom pane). Terminology • In SCtrl. command sequences were built up of commands.1. the sole exception is the devices covered in the Getting Started Manual. Wait. 440 . Service Control vs. The same component is also used to initiate data service sessions without running a script (a function which was previously unavailable). the Command Sequence (“CSeq”) tool. There is no distinguishing of “MS” and “DC” channels as in CSeq.0 predecessor. to the “EQ”). User Interface • SCtrl uses a graphical user interface where scripts are assembled in the form of flowcharts. All supported devices are automatically detected1. 1. This allows straightforward and unrestricted application of branching and other control structures. and scanning commands are no longer issued from the Equipment Control toolbar but rather from the Navigator (Equipment tab. An activated device is ready to be used.2. control commands. you compose scripts consisting of activities.TEMS Investigation 14. which in CSeq were limited to the Loop. section 7.e. • C.2. Inter-device synchronization is implicit in a SCtrl workflow wherever workflow branches converge. Manual voice dials. Again. whereas in CSeq. There is therefore no element in SCtrl scripts equivalent to the CSeq practice of inserting a Synchronize command at each juncture where several devices need to finish their respective tasks before proceeding.

The easiest way to accomplish the latter is to base your scripts on the predefined snippets supplied for each service type.2. and along with it the old Data category information elements prefixed with “Session”.2.8. section 3. where the device must connect to an MMS Center. See section 20.3. In SCtrl you indicate the type of data connection (NDIS or RAS) using a parameter in the Network Connect activity. all setups for data service testing are done from within TEMS Investigation.17. network connect and disconnect (corresponding to dialup and hangup in CSeq) are always performed as separate activities. TEMS Automatic) is always collected with SCtrl scripts provided that they are suitably composed. NT12-7002 ver 1.). Old command sequences composed with CSeq cannot be run by SCtrl. not to individual steps performed as part of the activity. HTTP. “Data” Category Information Elements The generic “session” concept in pre-12. as was the case in CSeq. adequate data on which to base KPI computation in other TEMS products (TEMS Discovery. separate information elements are now provided for each data service type (FTP. that is.0 TEMS Investigation versions has been abolished. • • • • • C. they are never incorporated into activities for service testing as could optionally be done in CSeq. SCtrl does not have distinct activities for sessions run over an NDIS connection. Comparison with Pre-12. SCtrl does not have distinct activities for KPI data collection as did CSeq. An exception is MMS. as detailed in Information Elements and Events. however. In SCtrl. etc.0 441 . This is because the KPI concept is no longer explicit in TEMS Investigation (see chapter 33). See section 20.0 User Interface • With SCtrl. This property always applies to the activity as a whole. Instead.9.Appendix C. There is no need (as there was with CSeq) to go outside TEMS Investigation to configure phonebook entries and the like in Windows. the details of that operation are specified as part of the MMS activity. The timeout parameters provided with each CSeq command have their counterpart in the SCtrl general activity property Abort with the termination condition set to On Timeout.

TEMS Investigation 14.1 User’s Manual 442 .

0 443 .e. 58 ACU 405 analysis mode 29 Andrew scanners CDMA scanning with 186 LTE scanning with 167 plugging in 47 Anritsu scanners 144 importing files logged by Anritsu ML8720 (i. in Anritsu format) 95 plugging in ML8720 model 47 plugging in ML8780A model 47 WCDMA pilot scanning with 151 Answer activity in scripts for video call 264 for voice call 266 AQM 397 for VoIP obtaining AQM data in TEMS Investigation 268. 403 obtaining AQM data in TEMS Investigation 401 practical considerations regarding collection of AQM data 402 prerequisites for collecting AQM data 402 NT12-7002 ver 1. manual 66 Activate activity in scripts 236 activating external equipment in TEMS Investigation 46. 411 presentation of AQM data 411 measurement setups in TEMS Investigation 398 with Audio Capturing Unit (ACU) 405 notes on AQM scores obtained with individual phone models 409 obtaining AQM data in TEMS Investigation 405 prerequisites for collecting AQM data 406 presentation of AQM data 408 recording AQM data 406 with Call Generator/MRU 399 manually entering phone number 50 merging uplink AQM data into logfiles 110.Index Index A access class control.

105 arguments of information elements 6 AT activity in scripts 236 AT commands. 298 audio quality measurements (AQM) 397 autodetect function for equipment not covered by license 52 restarting 61 B Band Lock activity in scripts 236 band lock. applying manually 67 limitations for Sony Ericsson phones 67 bar charts 337 adding charts 340 Additional Information pane 340 Chart pane 339 deleting a chart 340 editing general properties of individual chart panes 341 examples of presentations 353 exporting 355 interval on x-axis 351 labeling of x-axis 351 Legend pane 339 Multiple IE Components presentation mode 344 444 . issuing manually 67 Audio Capturing Unit 405 audio indications for events 297 activating 299 adding 297 deactivating 299 deleting 300 editing 299 muting 299 saving and loading 299 Audio Indications window 297.1 User’s Manual presentation of AQM data 403 recording AQM data 402 setup with Call Generator 399 setup with MRU 401 AQM Measurement activity in scripts 267 AQM modules associating with phones in TEMS Investigation 73 plugging in 48 ArcView 98.TEMS Investigation 14.

0 445 . manual 67 C C/I measurements (GSM) 419 Call Generator 399 CAS Access Class (Sony Ericsson phone properties) 280 CAS Lock on PLMN (Sony Ericsson phone properties) 280 CAS Speech Codec (Sony Ericsson phone properties) 280 CDMA scanning 186 Cell Barred (manual control function) 68 cell data loading from Mentum CellPlanner 42 using in presentations 42 cell files creating in CEL format 42 creating in XML format 41 in CSV format 41 loading 42 Cell Lock (manual control function) 68 cell reselection behavior (Sony Ericsson phones) 282 cell whitelists 228.Index organization of window 338 parallel coordinates 347 Parallel Coordinates/Stacked Bar Chart presentation mode 347 presentation mode 342 presenting data from a different device 352 selecting additional information 352 selecting colors 342 selecting data to display 342 setting up contents 341 setting up general properties 340 Single IE presentation mode 343 stacked bar chart 347 X-axis pane 339 Y-axis pane 339 basics of TEMS Investigation 26 BCH scanning. presentation of (WCDMA) 158 BLER target control (WCDMA). 291. 295 channel verification (GSM) 422 color attribute (of information element) 303 editing 37 Configuration menu 34 contents of User’s Manual 3 Control menu 34 NT12-7002 ver 1.

236 video streaming 324 Deactivate activity in scripts 237 deactivating external equipment 59 definitions of TEMS Investigation concepts 5 device properties 277 Dial activity in scripts for voice call 266 drive testing mode 29 DRT scanners 197 detection of 51 LTE scanning with 167 plugging in 47 E editing settings in 230 E-mail Receive activity in scripts 259 E-mail Send activity in scripts 258 enhanced power scanning (LTE) 180 equipment cases 4 plugging in 48 equipment handling.0 versions 439 equipment properties 277 Ericsson Fixed Wireless Terminals plugging in 47 Ethereal 98. 106 Event Counter windows 315 changing contents and properties of 316 copying contents from 315 managing tabs in 315 resetting 316 Event Definition window 290 events 5. 290. comparison with pre-12.TEMS Investigation 14.1 User’s Manual control structures in scripts 214 CPICH Best UARFCN Data window (WCDMA) 153 CPICH Data window (WCDMA) 153 CPICH Scan bar charts (WCDMA) 153 CPICH Scan line charts (WCDMA) 154 D data service testing 5 conducting manually 78 presentation of 78. 301 audio indications for 297 446 .

192.0 447 .Index deleting user-defined 293 editing user-defined 293 example of user-defined event 294 predefined and user-defined 290 presentation of 290 user-defined. 184. contents of 4 GPS fix source 327 GPS units in scanners 138 plugging in 48 properties of 289 selecting preferred GPS 60 NT12-7002 ver 1. 58 connectable devices 3 deactivating in TEMS Investigation 59 overview of user interface components dealing with 44 plugging in 46 user-assisted detection of 53. 158. setting up 290 external equipment 4 activating in TEMS Investigation 46. 177. 387 GeoSet 357 constructing from map files 357 GeoSet Manager 385 layer control 386 map projections 386 Getting Started Manual. 56 F FAQ (on TEMS website) 4 File menu 34 File Transfer tool 95 file types in TEMS Investigation 437 Filemark activity in scripts 237 filemarks inserting in logfiles 85 Finger Info window (CDMA) special features of 314 fix source for GPS 327 FTP Download activity in scripts 249 FTP Upload activity in scripts 250 fundamentals of TEMS Investigation 2 G General window 42.

1 User’s Manual GPS window 327 properties of 327 GSM Barred Cells (Sony Ericsson phone properties) 282 GSM Cell Selection (Sony Ericsson phone properties) 282 GSM channel verification 422 adding test cases 423 automatic vs.TEMS Investigation 14. manual 424 creating test reports 430 editing test cases 424 error conditions 431 notes on performance 431 opening tests 431 removing test cases 424 resetting test cases 429 running the test 427 saving tests 431 status of test cases 429 stopping the test 429 test 423 test case 422 test case group 423 GSM EDGE Capability (Sony Ericsson phone properties) 283 GSM Handover (Sony Ericsson phone properties) 283 GSM scanning 139 GSM Tx Power (Sony Ericsson phone properties) 284 H handover behavior in GSM (Sony Ericsson phones) 283 Hang Up activity in scripts for video call 264 for voice call 267 Help menu 34 HTC Imagio detection of 51 HTC Touch Pro2 detection of 51 HTTP Get activity in scripts 252 I If--Else activity in scripts 238 IMSI 50 in-building positioning using Map window 86 448 .

381 licensing in TEMS Investigation 2 line charts 329 adding charts 332 Additional Information pane 331 changing contents and properties 332 Chart pane 330 deleting a chart 336 editing contents 332 editing general properties 332 exporting 336 Legend pane 331 organization of window 329 presenting data from a different device 336 selecting additional information 336 selecting events 335 selecting information elements 333 time scale 331 Y-axis pane 331 loading a logfile for analysis 89 NT12-7002 ver 1.0 449 . 433 KPIs (Key Performance Indicators) 213. 388 accessibility 389 integrity 389 obtaining with TEMS products 389 purpose of 388 retainability 389 L labels 357 Layer 3 Messages (Sony Ericsson phone properties) 284 layers in Map window 357.0 versions 441 installing TEMS Investigation 26 IPv6 233 K Key Performance Indicators 213 keyboard shortcuts 35. 301 Data category comparison with pre-12.Index using Pinpoint Window 120 indoor positioning using Map window 86 using Pinpoint Window 120 information elements 5.

TEMS Investigation 14.1 User’s Manual loading logfiles 94 loading logfiles from other sources 94 Logfile menu 34 logfile recording 83 clearing history buffer 86 default folder 86 inserting filemarks 85 other options 85 Recording Properties dialog 85 logfile reports 112 contents 118 event statistics 115 external devices to include 116 saving and loading setups 118 scanned channels 116 thresholding of information elements 113 user details 118 logfiles activities performed in 92 equipment used when recording 91 exporting 98 ArcView settings 105 Ethereal (Wireshark) settings 106 executing export orders 107 from command prompt 107 MapInfo settings 104 MDM settings 106 Planet settings 106 saving and loading setups 106 text file settings 102 general information on 90 loading 94 loading contents of 94 progress indication on status bar 94 loading for analysis 89 loading from other sources 94 metadata on 90 opening 89 recording 83 searching 95 statistics on activities in 93 transferring via FTP 95 450 .

returning to 383 right-hand pane 378 scale bar 383 setting projection for 384 statistics 380 toolbar 384 viewing entire layer 384 MapInfo 98. 104 maps 356 centering 385 constructing a GeoSet from map files 357 GeoSet 357 labels 357 notes on route plotting and updating 364 panning 385 positioning maps in bitmap or TIF format 359 themes 357. 106 MDM 106 export in MDM format 98 loading MDM files in TEMS Investigation 95 Mentum CellPlanner 42 menu bar 28. 361 Legend tab 381 previous view. 34 merging uplink AQM data into logfiles 110 NT12-7002 ver 1. 360 zooming 384 Marconi Planet 98.0 451 . 381 adding presentation layers 381 control of 382 map layer 357 presentation layers 357.Index viewing metadata of 89 viewing statistics on activities in 89 viewing summary of activities in 89 LTE scanning 167 M managing external equipment (general) 44 manual operation of external equipment 64 Manual UE Configuration utility 53 Map window 356 information on theme markers 378 layers 357.

TEMS Investigation 14. 301 MMS Receive activity in scripts 260 MMS Send activity in scripts 259 Mobile Receiving Unit 399 mode reports 6 Mode Reports window adjusting updating frequency for Qualcomm reports 323 Motorola UEs reading EFEM logfiles from 95 MRU 399 MTQI 418 MTR files 95 N narrowband interference scanning (CDMA) 194 Navigator 27 Equipment tab basics 48 device context menu 49 refreshing 61 re-pairing phones with AQM modules 61 saving equipment configuration 63 Info Element tab 37 Logfile tab 39 Menu tab 36 Worksheets tab 40 Navigator pane 36 NDIS data connection 59 Network Bandwidth activity in scripts 256 Network Connect activity (in scripts) prerequisites for various devices 245 Network Connect activity in scripts 243 Network Disconnect activity in scripts 247 452 .1 User’s Manual message windows 317 catch-up function 319 changing contents and properties of 317 filtering contents of 320 freezing 320 highlighting messages in 322 plain-text message decoding 319 presentation of discarded messages 319 searching contents of 321 synchronization of 319 messages 6.

Index network scanning (WCDMA scanning mode) 164 presentation 166 setting up 165 Network Search window (WCDMA) 166 Nokia phones.0 453 . technology-specific control functions 76 sector lock control 287 Nonvolatile Item Read/Write (Qualcomm device control function) 72 O online help 34 P package options for TEMS Investigation 2 Parallel activity in scripts 239 parallel coordinates presentation 347 PCTel scanners CDMA scanning with 186 detection of SeeGull EX 51 detection of SeeGull MX 51 GSM scanning with 139 LTE scanning with 167 plugging in 47 WCDMA pilot scanning with 148 WCDMA scanning with 144 PESQ 397 PESQ devices See AQM modules phone number of user terminal 50 phones 6 plugging in 47 properties of 279 pilot scanning (CDMA) 187 pilot scanning (TD-SCDMA) 183 pilot scanning (WCDMA) 146 Ping activity in scripts 254 Pinpoint Window 120 creating planned routes in 120 relation to other TEMS Investigation functions 132 walking planned routes in 126 NT12-7002 ver 1. properties of channel lock control 287 GSM cell barring control 287 RAT lock vs.

manual 74 plotting density in Map window 364 POLQA 397 preamble scanning (WiMAX) 198 preferred GPS unit 60 presentation attributes of information elements 37 presentation layers 361 Presentation menu 34 presentation of data 301 presentation windows export/import of 304 synchronization 303 types of 301 updating 303 PS Attach activity in scripts 247 PS Detach activity in scripts 247 Q Qualcomm chipset based devices Nonvolatile Item Read/Write control function (UMTS) 72 properties of 288 Qualcomm devices with LTE capability 56 quick guide to user interface 26 R Radio Access Technology lock (manual) 74 Radio Access Technology Lock activity in scripts 237 RAT lock 237 applying manually 74 recommended skills 26 recording logfiles 83 Release Note 4 Report Generator 112 reports on logfiles 112 454 .1 User’s Manual pinpointing in Map window 86 presentation 377 in Pinpoint Window 120 planned routes creating 120 walking 126 repeating parts of 129 skipping waypoints 130 PLMN control.TEMS Investigation 14.

properties of 289 scanners 7 plugging in 47 scanning general 134 manual 135 notes on scanner multitasking 137 performing a scan 79 performing manually 135 presenting scan data 136 recording scan data manually 136 scripted 134 setting up manually 135 technical data on scanning devices 136 scanning. 144 detection of 51 LTE scanning with 167 plugging in 47 WCDMA pilot scanning with 150 routes 6 RRC WCDMA capability control. CDMA 186 "PN Scan" bar charts 192 general settings 187 methods 186 Narrowband Interference Scan Bar Chart 194 narrowband interference scanning 194 of pilots 187 RSSI Scan Bar Chart 193 RSSI scanning 193 sorting of PNs in presentations 192 NT12-7002 ver 1.Index Rohde & Schwarz scanners 139.0 455 . manual 77 RSSI scanning CDMA 193 GSM 140 LTE 177 TD-SCDMA 185 WCDMA 161 WiMAX 201 Run Script activity in scripts 240 S Samsung Galaxy S 4G properties of 279 Samsung LTE modems.

141 C/I measurements 141 device capabilities 139. 167 RSSI scanning 140 spectrum analysis 143 System Information Decoding 142 scanning. 167 methods 139. GSM 139 BSIC decoding in RSSI Scanning mode 140.1 User’s Manual spectrum analysis 195 Strongest Scanned PN Bar Chart 192 scanning. 180. TD-SCDMA 182 general settings 182 methods 182 of pilots 183 presentation 184. 185 RSSI scanning 185 sorting of cells in presentations 184 scanning. 181 RSSI scanning 177 sorting of cells in presentations 177 spectrum scanning 178 scanning. 178. WCDMA 144 CPICH Best UARFCN Data window 153 CPICH Data status window 153 CPICH pilot pollution 155 CPICH Scan bar charts 153 CPICH Scan line charts 154 CPICH scanning 146 device capabilities 144 Finger Info status windows 158 methods 144 network scanning 164 number of active set members 155 of P-SCH and S-SCH channels 157 of synchronization channels (SCHs) 146 of timeslots on SCH 159 presenting scrambling codes from multiple UARFCNs together 159 RSSI Scan Bar Chart 162 RSSI scanning 161 456 .TEMS Investigation 14. LTE 167 enhanced power scanning 180 LTE signal scanning 168 presentation 176.

setting up 210 Deactivate activity 237 Dial activity (for voice call) 266 editing workflows 230 E-mail Receive activity 259 E-mail Send activity 258 failure handling properties 270 Filemark activity 237 FTP Download activity 249 FTP Upload activity 250 general activity properties 270 Hang Up activity (for video call) 264 NT12-7002 ver 1. WiMAX 197 general settings 197 methods 197 preamble scanning 198 presentation 201 RSSI scanning 201 spectrum analysis 201 SCH scanning 146 SCH Timeslot Scan Bar Chart (WCDMA) 160 scripts 230 Activate activity 236 activity filter 275 Answer activity (for video call) 264 Answer activity (for voice call) 266 AQM Measurement activity 267 AT activity 236 Band Lock activity 236 basics of creating 206 capabilities of devices 203 comparison with old command sequences 440 context menu in workflow pane 275 Control activities 236 Control Flow activities 238 control structures 214 copy--paste 230 data services.Index SCH Timeslot Scan Bar Chart 160 sorting of scrambling codes in presentations 158 spectrum analysis 163 Spectrum Analysis bar charts 164 Synch Channel Data status window 157 scanning.0 457 .

1 User’s Manual Hang Up activity (for voice call) 267 HTTP Get activity 252 If--Else activity 238 if--else constructs 215 importing and exporting 271 introduction to 203 IP activities 243 Messaging activities 258 MMS Receive activity 260 MMS Send activity 259 moving activities in 230 Network Bandwidth activity 256 Network Connect activity 243 network connection. setting up 209 Network Disconnect activity 247 Parallel activity 239 parallel construct 218 Ping activity 254 PS attach 212 PS Attach activity 247 PS detach 212 PS Detach activity 247 Radio Access Technology Lock activity 237 Run Script activity 229. 240 running 232 saving and loading 273 saving workflow as image 274 Scan activities 262 Sequence activity 240 sequences 214 SIP Register activity 248 SIP Unregister activity 248 SMS Receive activity 262 SMS Send activity 261 snippets 213 Start IP Sniffing activity 248 Start Logfile Recording activity 237 Stop IP Sniffing activity 249 Stop Logfile Recording activity 237 Streaming activity 264 supported services by cellular technology 204 suppressing parts of 235 458 .TEMS Investigation 14.

creating script for 206 VoIP Answer activity 268 VoIP Dial activity 268 VoIP Hang Up activity 268 VoIP Voice Quality activity 268 Wait activity 225.0 459 . properties of CAS Access Class 280 CAS Lock on PLMN 280 NT12-7002 ver 1. 240 UDP activity 254 UE control 231 validating 232 Video activities 264 Video Dial activity 264 Voice activities 266 voice. 240 Wait For activity 226 WAP Get activity 253 WAP Streaming activity 265 While activity 239 while loops 216 workflow control structures 214 zooming the workflow pane 275 searching a logfile 95 searching in message windows 321 Sequence activity in scripts 240 Service Control 203 See also scripts Service Control Designer 204 Service Control Monitor 232. 233 SIP Register activity in scripts 248 SIP Unregister activity in scripts 248 size attribute (of information element) editing 39 skills recommended for TEMS Investigation users 26 SMS Receive activity in scripts 262 SMS Send activity in scripts 261 snippets in scripts 213 Sony Ericsson phones GSM scanning with 139 properties of 279 WCDMA pilot scanning with 146 Sony Ericsson phones.Index Terminate activity 230.

1 User’s Manual CAS Speech Codec 280 EDGE Capability 283 Extended Reports 279 GSM Adjacent Scan 281 GSM Barred Cells 282 GSM Cell Selection 282 GSM Handover 283 GSM Tx Power 284 Layer 3 Messages 284 messages and mode reports 279 RAT lock vs. 48 statistics presentation in Map window 380 status bar 28.TEMS Investigation 14. 33 460 . technology-specific control functions 76 WCDMA Barred Cells 284 WCDMA BLER Target 285 WCDMA Cell Selection 285 WCDMA RRC Radio Capability 286 sounds for events 297 spectrum scanning CDMA 195 LTE 178 WCDMA 163 WiMAX 201 speech codec control. manual 77 speech codec information elements populating with Qualcomm chipset based devices 288 speech codecs (of Sony Ericsson phones) 280 Speech Quality Index (SQI) 391 SQI 391 SQI-MOS 391 alignment with PESQ 394 comparison with RxQual (GSM version) 396 input to algorithm 392 output 393 SRUs 144 GSM scanning with 139 plugging in 47 WCDMA pilot scanning with 146 stacked bar chart 347 Start IP Sniffing activity in scripts 248 Start Logfile Recording activity in scripts 237 starting TEMS Investigation 26.

32 File and View toolbar 33 Record toolbar 32 Replay toolbar 32 Report toolbar 33 NT12-7002 ver 1.Index Status Control Monitor 80 status windows 305 changing font size in 312 changing properties of 309 repeating columns in multiple groups 312 setting up contents of 305 ST-Ericsson chipset based phones.0 461 . properties of 279 Stop IP Sniffing activity in scripts 249 Stop Logfile Recording activity in scripts 237 Streaming activity in scripts 264 support contact information 5 symbol attribute (of information element) editing 39 Synch Channel Data window (WCDMA) 157 T TD-SCDMA Physical Channel Monitor design of 313 TD-SCDMA scanning 182 TEMS Bulletins 5 Terminate activity in scripts 240 themes 357. 377 reordering 378 visibility of 377 toolbars 27. 360 Cell ARFCN theme 375 Cell Color theme 373 Cell Line theme 370 Cell theme 367 cell themes 361 constructing cell themes 366 event themes 365 IE themes 362 deleting 378 editing 377 event themes 360 information element (IE) themes 360 Pinpoint theme 361.

414 VTQI 412 W Wait activity in scripts 240 WAP Get activity in scripts 253 WAP Streaming activity in scripts 265 WAP-based video streaming 265 WCDMA Barred Cells (Sony Ericsson phone properties) 284 WCDMA BLER Target (Sony Ericsson phone properties) 285 WCDMA Cell Selection (Sony Ericsson phone properties) 285 WCDMA RRC Radio Capability (Sony Ericsson phone properties) 286 462 .TEMS Investigation 14.1 User’s Manual track (walk along planned route) 126 tracks 7 Transcom scanners LTE scanning with 167 U UDP activity in scripts 254 user interface 29 comparison with user interface in pre-12. dialing manually 77 VoIP 410 VoIP Answer activity in scripts 268 VoIP Dial activity in scripts 268 VoIP Hang Up activity in scripts 268 VoIP Voice Quality activity in scripts 268 VSQI 326. 414 evaluating performance of 326 how to test 324 troubleshooting 326 WAP-based 265 video telephony 412 View menu 34 voice calls.0 versions 439 quick guide to 26 user modes 29 user-assisted detection of external devices 53 user-defined events 290 V video calls. dialing manually 77 Video Dial activity in scripts 264 Video Monitor 325 properties of 325 video streaming 324.

presenting on map 366 WiMAX scanning 197 Window menu 34 Windows 7 233 Windows Vista 233 Wireshark 98.0 21 what was new in TEMS Investigation 13. 30 opening from Command Prompt 31 predefined 31 NT12-7002 ver 1.Index WCDMA scanning 144 what was new in TEMS Investigation 13. 31 workspaces 27.0 11 what’s in this manual 3 what’s new in this TEMS Investigation version 8 While activity in scripts 239 Wi-Fi access points presentation on map 366 WiMAX cells.0 463 . 106 Worksheet menu 34 worksheets 27.1 16 what was new in TEMS Investigation 14.

 and our products are  supplied to the world’s top mobile operators. Ascom reserves the right to change specifications without notice. ANAlyzE. TEMS is a trademark of Ascom . equipment vendors.  www. 1943 Isaac Newton Square Reston. and professional service providers. These  state-of-the-art  offerings  facilitate  the  deployment. and analyzing network performance.  monitoring. All rights reserved.ascom. We are the industry leader.com/tems  The  TEMS™  Portfolio  offers  a  complete  set  of  trusted  solutions  for  drive  testing. ANd opTiMizE MobilE NETworkS. Ascom acknowledges all registered trademarks appearing herein. AScoM NETwork TESTiNg lEAdS ThE world iN providiNg bEST-iN-clASS SoluTioNS To MEASurE.2012 © Ascom 2012. Ascom Network Testing Inc. . Virginia 20190 | USA www.  benchmarking.ascom. optimization.com/tems 04. and maintenance of mobile  networks. All other trademarks are the property of their respective holders.

Sign up to vote on this title
UsefulNot useful