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

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

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

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

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

. . . . . . . . . . . . Wait . . . . . . . . . . .4. . . . .16. . . . . . . . .15. . . . Running Scripts from the Service Control Designer . . . . . . . . . . .9. . .1. Example 2: Concurrent Activities on Different Devices . .2. . .15.15. . . . . . . . . 20. . Running Scripts. .5. . 20. . . . . . UE Control Functionality . . Band Lock . . . . . . . Waiting For a Scheduled Point in Time. . . . . . . . . . . . . . 20. . . . Monitoring Equipment Status . . . . . 20. . . . . . . 20. . . . . . . . . . . . . . . . . . . . .1. . .16.TEMS Investigation 14. . . . . . . . . 20.10. . . . . . . . . . . . . . . . . .1. . 20. . . . . .1. . . . . . .16. . . . . . . . . . . . . 20. . .4. . . . . . . . . . . . . . .6. . . . . . . . 20. . . .3. . . Waiting For a Given Outcome of an Activity . . Validating Scripts . . .14. . . .15. . Deactivate . . . . . . . . . Wait For with Periodic Events . . . . . . 20. .1. . . . .4. . . . . . . . . . . . 20. . . . . . . . . . . Activities (Reference Section). . . . . . . . . . . . .3. Filemark . 20. . . . . . . . .3. . . . . . . . . .2. . . . . . 20. . . .16. Parallel Activities . . .6. . Editing Workflows and Script Settings . . . . . . . . . 20. . . . .15. . . . . . 20. . . . . . . . If–Else Constructs . . . . . . . . . . Run Script . . . . . . . . . . . . . 20. . . . . . . . .3. . .1. Stop Recording . . . . . . . . . . . . . .7. . . . . . . . . . Terminate. . . . . . . . . . .16. 20. . . . . . . . . 20. . . . . . . . 20. . . . .10.4. . . . . . . . . . . .15. . . . . .1 User’s Manual 20. . . . . . . . . .6. . .10.10. . . . . . . . 20. . 20. .16. . . AT . 20. 20. . . . . . . . . . . . . . Start Recording . . . . 20. . . . . . . . . . . Control Activities .2. . . . . . . . . . . . Notes on Script-controlled Logfile Recording . . . . . . . 20. . . . . .10. . . . . . . . .2.11. 20. .16.6.10. . . .12. . . . . . . . . . . . . . . Running Scripts from the Service Control Monitor . . . . . Wait For . . . . Viewing Statistics on Script Execution . 20. 20. . . . . . . . . .13. . .10.10. . . . . . .6. . . . . .10. . . . . . . . . . . . . . . . 20. . . . 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 . . . .4. . . . . . . . 20. . . .1.10.1. . . . .5. . . . . . . . . . . . . . Example 3: Concurrent Activities on the Same Device . .1. . . . .16. . . . . . . . . . . . . . . . . .10. . . . . . . . . . . .4. . . .1. . . . .15. .15. . . . . 20. . . . . . . . . . . . . . . .1. . . .3. General Aspects of Script Execution . .7. . . .1. . . . . . 20. . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20. . . . . . . . Activity Properties That Control Execution . . . . . . . . . . . . . . . . .16. .2. . . . . . . . Preparations.15. .15. . . . . . . 20.2. . . . . . . . . .1. . . . . . . . . . . . . . . . . .8. . . . Example 1: CS Voice/Video – Caller and Receiver . . . . . . 20. . . . . Presentation of Data Service Testing . . . . . . . . . . . . . . . . . . . . . .1. . . . . 20. . . . . . . . . . Activate . . . . . . While Loops . . . . . . . . . . . Windows 7/Windows Vista and IPv6. Suppressing Parts of a Script . . .3. .6. . . . . . .1. . . . . . . . .16.8. . . . . . . . . . . . 20. . .5. .10. . . .16. . . . .1. . . .2.3. . . . . . . . . . . Radio Access Technology Lock . . . . . . .

. 254 20. . . . . . . .1. 247 20. . . . . . . . . . . Network Disconnect . . . . . . . . . 264 20. . .4. . . . . . . .3. . . . Wait For. . .16. . . . . . . . . . . . . . . . . 243 20. . . . While . . . . . . . . . . . . . .3. .5. . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . .2. . . . . . 259 20. . . . . . . . . . . . . .8. . . . . . . . . . . . . . . PS Detach . . . . . . . . . . . . 264 20. . . . . . . .1. . . . . 259 20. . . . .3. . . . . . . . . . . . . . . . .5.4. . . Run Script .16. . . . . . . . . . . . . . . . . . . . . . . . .8. Hang Up . . . . . . . . 248 20. .2. . . . . . . 240 20. . . . . .4.16.11. . . WAP Get .6. . . 256 20. . . . .16. . Video Dial .3. . . . . . . . . . . . . . .16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12. . . . . . . . . .2. . .3. . . . . . . . . Streaming . . . . . . . . . . .16. . . . . . . .5. . . .4. . . . . . . . . .2. .9. . . . . . . . . . . . 262 20. . . . .16. . . . .16. . . . . . Predefined Snippets for IP . .16. . . . IP Activities. . . . 248 20. . . . . . SIP Register . . . . . . . . . . . . . . . . . . . . . . . .16. . . . . . . .2. . . . . .3. . . . . . . . . . 261 20. . . . . . . . . . . . . . . . . . SMS Receive. . . . . . . . . . . . .16. . . . . . . . . . . . . . . . Network Connect.4. . . . . . Control Flow Activities . . . . . . . . . . . .2. . . . . . . . .3.3. . . . . Network Bandwidth (Iperf Testing) . . . . .4.5. . . . . . . FTP Upload .16. . . . E-mail Receive . . . . . . . . . 240 20. .1. 258 20.16. .3. . . . . 239 20. .3. . 240 20. . . . . . .16. .3. 262 20. . . . . . . . . SIP Unregister . . .14. Wait . . . . . . . . PS Attach . . 240 20. . . .16. . . . . . . . . .4. . . . . . . . . .3. . . . . . . . . . . . . .2. . . . . . . 247 20. 248 20. . . . . . . . . . . . . . . . . . 258 20. . . . . . . . Start IP Sniffing . . . . . .1. . . . . . . . . . . . . 240 20. . . . . . . SMS Send . . . . . . . . .6. . .3. . . 249 20. . Predefined Snippets for Messaging . . 239 20. Sequence . . Predefined Snippets for Scanning. . . .4. . . . . . . .16. . . 262 20. . . . . .13. . . . . 247 20. . . . . . . . . . . 249 20. . . . . . . . . .16. . . . . . .4. . . . 253 20. . . . . Stop IP Sniffing . . . . . UDP.16. 243 20. . . . . . . . . . . . . . . . . . . . . .6.10. . . . .2. . . . . . . . . . . .16. . . . . . . . . MMS Send. . . . .16. . .2. .15.16. . . . . . .16.3. . . .16.16.7. . . . 264 20. .16. . . . . . . FTP Download. . . . . . . .16. . . . . . . . . . . . . .5. . . . . . . . .16.6.4. . Messaging Activities. . . . . .16. . . . . . . . . . . . . . . . . .16.16. . . . . .3. . . . . . . . . .4. . . . . . . . . Answer . . . . . . . . .16. . . . . .16. . . . . . . . MMS Receive .Contents 20. . . . . Ping . . . . . . . . .16. . . . .16. . . .16. . . .2. 238 20. . 252 20. . . 264 20. . . . .5. . . . . WAP Streaming. .7. . . . . . Terminate . . .2. . . . . . . . . . . . . . . . . . . . . . 250 20. . . . . . . . . . . 258 20. . . . . . . . . . . . .6. . . . . . . . . .3. . . . . . . . 238 20. . If–Else . . . . . . Scan Activities . . . . . . . 260 20. . . . . . . . . . .16. . 254 20. . .3. . . . . . .6. . . . . . . . . . . . . . . . . .16. . . . . .0 xiii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . .3.16.2. E-mail Send. .16. . . . . . . 264 20. Video Activities . .16. . . . . .16. .3. . . . 264 20. .2. . .7. . Parallel .1. . . . . . . . . .3. . . . . . 265 NT12-7002 ver 1. . . . . . . . . . . .6. . . . . . . . .4. . .16.6. . . . . . . . . . . . . . . . . HTTP Get . .16. .

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

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

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

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

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

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

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

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

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

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

Still more powerful post-processing facilities are provided by the product TEMS Discovery.1 User’s Manual 1. The application also boasts a vast array of windows for presentation of logfile data. it collects data and records it in logfiles. scanners.1 is an air interface test tool for cellular networks.1. Other phones are licensed separately for each supplier or.1 TEMS Investigation 14. logfile reports. 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. Supported cellular technologies can be freely selected and combined. 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. data cards. except that WCDMA always comes with GSM support included. and other measurement devices. It interfaces with phones. A/EV-DO Rev. Fundamentals of TEMS Investigation 14. 2 . TEMS Investigation is primarily a tool for data collection and real-time analysis. separately for chipsets with different capabilities. logfile export).TEMS Investigation 14. 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. 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. 0/EV-DO Rev.1.1. Package Options – Licensing TEMS Investigation can be purchased with or without data collection capability (“Base Software Package” and “Replay Package” respectively). in the case of Qualcomm.

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

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

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

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

Chapter 1. for example a PCTel scanner. 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.0 7 . Phones with scanning capabilities are not referred to as scanners.

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

previously introduced for VoIP.0 9 .1. 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. 2. Recently Introduced Features in TEMS Investigation 2. Extended Control Functionality and Logging for Sony Ericsson Xperia arc S Sony Ericsson Xperia arc S now supports audio quality measurement. POLQA for CS Voice The state-of-the-art POLQA algorithm for speech quality assessment. POLQA is obtained in the ACU (TerraTec) audio quality measurement configuration. including PESQ and POLQA. The following additional control functions have been implemented for the Xperia arc S phone. 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.1.3. Cell Whitelists A common constraint in cellular network testing is to restrict tests to a predefined set of cells: for example. is now available also for circuit-switched voice.1.1.4. See also section 2.Chapter 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. 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. This event can then be used in a script to trigger some action whenever the tester is in NT12-7002 ver 1. POLQA can be computed for both narrowband and super-wideband speech.2.3.

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

• • • New LTE Information Elements PDSCH BLER and ack/nack counters for Transport Blocks 0 and 1 separately. 2. PUSCH ack/nack counters. This is a Qualcomm chipset based device running under Android. giving a more fine-grained view of retransmission statistics.1. Rank Indication counters showing incidence of values RI = 1 and RI = 2.11.0 11 .0 continued and reinforced this tradition by adding the Sony Ericsson Xperia arc S smartphone as a connectable device. LTE RRC Redirection Events The LTE RRC connection redirection events have been extended to cover redirection to EV-DO (HRPD/eHRPD).2.1. useful for studies of MIMO channel properties. What Was New in TEMS Investigation 14.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. 2.2. 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.10. Supported LTE bands are: • • • TDD 1900 MHz (Band 39) TDD 2300 MHz (Band 40) TDD 2600 MHz (Band 38) 2.Chapter 2. New Connectable Scanners A TD-LTE scanner from Transcom Instruments is offered as a cost-efficient solution for scanning of TD-LTE networks.1. Recently Introduced Features in TEMS Investigation 2.12. 2. TEMS Investigation 14.1.

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

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

In this Web-based portal.).2. All of these features help you manage logfile export more smoothly and save time. 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. Two new HTTP information elements were provided (regardless of browser used): total document size and download time.0 introduced the option of using Internet Explorer 9 for HTTP download testing instead of TEMS Investigation’s built-in Web browser. multiple concurrent FTP download sessions with one device simply by putting the sessions in parallel branches in your script. Command line switches are provided for all aspects of the export setup that are configurable from within TEMS Investigation.TEMS Investigation 14. for example. 2. 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.8. Cell files can be included when exporting logfiles. Flow control in scripting was rendered more powerful with the new Wait For activity. Command-line controlled export can be scheduled with the generic scheduling functionality in Windows. Logfile Export Enhancements The logfile export tool was repackaged into a separate executable which can alternatively be run from a Windows command prompt. 2. etc.7. which can be installed under Windows 7 or Windows Server 2008/2003. the license server administrator assigns to each TEMS Investigation user the products 14 . This means that you can set up. Improved Service Testing Capabilities TEMS Investigation 14. Improved HASP Soft License Handling A license manager portal was introduced.6. facilitating management of network licenses and adding traceability.1 User’s Manual 2.2. 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.2. There is no need to pass special session concurrency parameters with the FTP testing activity.

0 15 . users detach licenses to their local machines. Recently Introduced Features in TEMS Investigation they are allowed to detach and sets a maximum detach duration.3 Qualcomm Snapdragon MSM8255 (1. Further constraints such as license expiry dates can be defined.76 Mbit/s) Huawei E353 LG P505 NT12-7002 ver 1.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. From this utility.4 GHz) HSDPA Category 10 (14. Reports on license usage can be generated and also exported in comma-separated (CSV) format.4 Mbit/s). Side by side with the license manager portal. 2. New Connectable User Terminals in TEMS Investigation 14.Chapter 2.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. a client license manager with a graphical user interface is provided. and the main benefit it brings is that it greatly reduces the risk of detaching the wrong license by mistake.9.2. HSUPA Category 6 (5.2. “Category” fields are provided for convenient grouping of users. The client works over a VPN.

A number of events – some new. The PESQ calculation is done by the PC itself.3.1 User’s Manual • • LG P509 Sharp 006SH 2. Huawei C8600 (CDMA). just as in the existing TEMS Investigation AQM setup.3. RACH Result. 2. 2. Extended Set of LTE RACH Information Elements A collection of new information elements deals with the RACH procedure in LTE: RACH Type. which call each other in pairs. so that no separate processing power is required in the Audio Capturing Unit. Preamble Step Size.2.1 it was implemented for the following phones: Sony Ericsson Xperia arc. 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. What Was New in TEMS Investigation 13. RACH 16 . Nokia C7-00 (GSM/WCDMA). Since the voice calls are made between the mobiles.3.1. The activities of the devices are completely controlled from TEMS Investigation by means of a Service Control script. some expanded in scope – report on the resulting interaction between the terminal and networks. Sony Ericsson W995. RACH Reason. 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. Two or four mobile devices. In TEMS Investigation 13. there is also no Call Generator or similar component in this AQM configuration.TEMS Investigation 14. Event categories: • • • Call setup events Inter-RAT events Attach events 2.3. The mobile-to-mobile AQM solution is in principle RAT-independent.3.

MME Group Id.0 17 . Improved Handling of Qualcomm-based LTE Devices Network connect can be performed for Qualcomm chipset-based LTE devices from within TEMS Investigation.3. 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. B of the EV-DO (TIA-856) standard introduces multicarrier data transfer in EV-DO.4. Recently Introduced Features in TEMS Investigation Preamble Responses with PUSCH Resource.1 allows connection of devices built on a range of Qualcomm CDMA/EV-DO Rev. without using an external connection manager. The implementation was verified with the Huawei EC367-2 device. • New Connectable User Terminals in TEMS Investigation 13.76 Mbit/s). CDMA/EV-DO Rev. B Measurement and Analysis Rev. Presented information elements subdivide into three categories: • • • Basic radio parameters Multicarrier serving channel information Forward link multicarrier RLP throughput 2. and MME Code. TEMS Investigation also permits connection of multiple Qualcomm-based LTE devices. that is.5.3. 2. I) GSM/EDGE 850/900/1800/1900 HSUPA Category 6 (5. B chipsets.1 Sequans TD-LTE USB modem SQN3010A-USB-M1. HSDPA Category 14 (21 Mbit/s) Advanced control functionality • NT12-7002 ver 1. 2. TEMS Investigation 13.Chapter 2.3.6.

18 . 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. WCDMA Scanning with Rohde & Schwarz WCDMA pilot (Top N) scanning can be undertaken with Rohde & Schwarz TSMW scanners.76 Mbit/s).3.7. There are no restrictions on supported frequency bands (30 MHz to 6 GHz). II. VIII.1 User’s Manual • Sierra Wireless AirCard 319U – – – – Dual-Carrier HSPA+ USB modem from Sierra Wireless WCDMA/HSPA+ 850/900/1900/2100 (Bands V.TEMS Investigation 14. I) GSM/EDGE 850/900/1800/1900 HSUPA Category 6 (5.

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

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

The data set obtained is similar to FDD and includes RSRP.4. Please note that lower-layer data (RF. LTE support in TEMS Investigation was restricted to FDD. Any LTE frequency band can be scanned. USB modems. This feature can be used to verify application layer performance for arbitrary devices. as well as video streaming. it is possible to do Top-N LTE signal scanning in both TDD and FDD mode. as will be desirable prior to launching them in the network. TEMS Investigation 13.4.1. Data Service Performance Verification with Generic Device TEMS Investigation 13.Chapter 2. known as TD-LTE. Using a Rohde & Schwarz TSMW Universal Radio Network Analyzer.0 21 . and all IP information elements will then be populated.0 expanded the concept of data service testing. Layer 3) is not obtained with this kind of testing. taking it to a whole new level of genericity. and SCH CINR. 2. iPhone or BlackBerry units. 2. Layer 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.0 version. or a wide variety of network cards. RSRQ. With the 13.4. however.0 version. NT12-7002 ver 1. etc. embedded modules.2. Any IPbased activity in the Service Control Designer.0 introduced scanning support also for the TDD mode. Up until the 13. can be run on such a device. 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. What Was New in TEMS Investigation 13.0 TD-LTE Support The LTE standard allows both frequency division duplex (FDD) and time division duplex (TDD) operation.

some other existing workspace.4.4.0 UMTS Terminals 2. See section 4.1. The utility can also be seen as a complement to the script saving function in the Service Control Designer. or a new one that is empty. such a file may contain all details of how to perform an LTE Reference Signal scan with a PCTel MX scanner. or all the parameters needed to access and interact with a particular FTP server.18. New Connectable Equipment in TEMS Investigation 13.4.1 User’s Manual 2. 2.2.3.5. New LTE Information Elements With LG devices.TEMS Investigation 14. Selection of Preferred Workspace at Startup When you start TEMS Investigation 13. For example.4. The TEMS Settings Manager boosts usability by enabling easy distribution of configuration data among users and among instances of TEMS Investigation. a range of additional LTE information elements are obtained. which creates files specifying the activities to perform during testing. PBCH BLER. including PDSCH Transmission Distribution. • – – – 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 . See section 20.6. 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. many LTE elements previously available only with LG devices are also obtainable with Qualcomm devices. 2.4.2.4.0.6. Furthermore. you are invited to select what workspace to use: one recently used.0. 2. using TEMS Investigation 13. and PUSCH BLER.

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. see section 2.3. Compare section 2. Support for 64-bit Windows 7 TEMS Investigation 13. Recently Introduced Features in TEMS Investigation – • – – – • HSDPA Category 8 (7.0 onward.4. Unlike the Telnet protocol.2 Mbit/s). See section 20.0 can be run under 64-bit Windows 7.1. SSH2 requires a separate license option and installation package. HSUPA Category 5 (2.6.0 23 . LTE Scanner: Rohde & Schwarz TSMW The R&S TSMW Universal Radio Network Analyzer enables TD-LTE measurements in TEMS Investigation 13.15.16. HSUPA Category 6 (5. Such technology expansions will then be possible to do remotely by means of a scanner software upgrade. since it is subject to export restrictions due to its use of strong encryption.3.0. Update to this text: GSM and WCDMA scanning is supported with R&S TSMW from TEMS Investigation 14.4.1 2.76 Mbit/s) WCDMA/HSPA 850/900/1700/1900/2100 MHz GSM/GPRS/EDGE 850/900/1800/1900 MHz HSDPA Category 9 (10. 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.7. NT12-7002 ver 1. and support for these is planned for inclusion in future releases of TEMS Investigation.4.7. which sends logins and passwords in plain text. SSH2 uses cryptography to authenticate the remote computer and therefore renders the Iperf server less vulnerable to hacker attacks.4.2 Mbit/s).Chapter 2. 1.8.2.0 Mbit/s) Nokia C7-00 HTC Imagio 2. 2.

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

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

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

Most of the toolbar buttons are mirrored in the menus. Navigator From the Navigator you manage your connected equipment or view information on the currently loaded logfile.Chapter 3. you can divide your workspace into several worksheets. NT12-7002 ver 1. particularly those relating to logfile recording and analysis. 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.0 27 . and manage your worksheets. To manage your windows more smoothly. Up to ten worksheets can be active simultaneously. Only one workspace can be open at a time. From here you also open presentation windows. Toolbars The toolbars provide shortcuts to certain functions in the application. change the mode of presentation of information elements.

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

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

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

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

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

Help Section Shows a help text when you point to a button or combo box on the main window toolbars. It is divided into the following sections: 4. Print: Print the selected window.4. Open Workspace: Open a saved workspace. the progress bar shows what proportion of the logfile has been loaded.Chapter 4.0 33 . Print Preview: Show a preview of the window printout.2. NT12-7002 ver 1. Save Workspace: Save a workspace.4. 4.4. During loading of a logfile.3.2.1.8. File and View Toolbar New Workspace: Create a new workspace. Toggle Full Screen: Toggle between full screen and normal mode. 4. “Play” Section This section is active in analysis mode.4. Compare section 11. 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. Report Toolbar Generate Report: Generate a report from one or several logfiles.3. See section 11.3. otherwise directs you to the online help: 4. User Interface 4.

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

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

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

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

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

Chapter 5. The Navigator • Check the Via Color box if you want to use a specific color in the middle of the range.3. • • To edit an interval. and make your changes. select it.2. To delete an interval. 5.2. a color range is created automatically with evenly sized intervals and suitable intermediate colors. Manual Setup of Color Ranges If you prefer to assemble your color range interval by interval. If you do not check the Via Color box. 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. NT12-7002 ver 1.4. 5.3. click Edit. set the endpoints of the interval.0 39 . click Add. nor can the color range as a whole be removed. If you delete parts of the color range so that no color is defined for some values.3. A single remaining interval cannot be deleted. the intermediate color is chosen automatically based on the “From” and “To” colors. 5. these values will be drawn in black. Logfile Tab See section 11. When you click OK. select it and click Delete.2 above.2. and choose a color. follow these steps: • To add an interval.3. See section 5.

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

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

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

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

One device at a time is in focus in this pane. Managing External Equipment: General This chapter summarizes how external equipment is handled in TEMS Investigation. 7. which is covered in chapter 20.TEMS Investigation 14. All of these tasks. 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.2. See chapter 9. Full details follow in chapters 8–10.1. Activities tab: From here you can manually apply various commands to and perform various actions with the selected device. – – • Bottom pane: – – 44 . 7. can be automated using the Service Control tool. and many more besides. The in-focus device can be changed with a context menu command. See chapter 21. The functionality here relates to the device that is currently selected in the top pane. Provides shortcut to device properties.1 User’s Manual 7. See chapter 8. Connectable Equipment The range of equipment that is compatible with TEMS Investigation is given in the Getting Started Manual. chapter 10.

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

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

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

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

4. You can change the EQ index assigned to the device: see section 8. external devices are represented by their channels (“MS”/“DC”/“PS”).3. Activating External Equipment Each device is represented by a numbered “EQ” item. the two devices will then swap indices. Change Equipment: Select a number to change the device’s EQ index to that number.3. 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”.5 8. It is possible to select an index that is already taken by another device. Device Context Menu If you right-click an EQ item.1. Deactivate: How to activate and deactivate devices is explained in section 8.1. See section 23.3.0 49 .5 Device is selected as preferred GPS: see section 8. see chapter 21. Please note that in presentation windows. 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. Properties: This menu item takes you to the device properties. • NT12-7002 ver 1.3.1.Chapter 8. a context menu pops up containing the following commands: • • Activate.3.1.

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

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

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

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

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

xml file (found under <TEMS Investigation install dir>\Application) may give an indication. (See the XML code excerpt below. and the DESCRIPTION tag is the name displayed in the tool. Mapping Device Ports to Interfaces If it is not clear which port should be mapped to which interface. Activating External Equipment Click the Refresh button in the Navigator.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. the entries in the existing UEDescription. This is necessary to update TEMS Investigation with the device configuration just defined.1.4.0 55 .) Below are some examples of mappings in UEDescription. (If you are running the Manual UE Configuration utility independently.3.Chapter 8.) 8. TEMS Investigation will update itself automatically with this data when launched. The TYPE tag is mapped towards the interfaces.

1 User’s Manual In the file UEDescription. select the appropriate chipset family. click OK. Launch the Manual UE Configuration utility and select your device as described in the introduction of section 8. do as follows.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.4.3. Finally.2.4.3. 56 . Under Type. pair each available port to the correct port type as shown in the screenshot below. In the Manage Device dialog. 2. Then. 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”).TEMS Investigation 14. in the Ports section. 1.

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

4. set Type to “Data Only Device” in the Manage Device dialog.TEMS Investigation 14. Map the device ports as appropriate. Click Save and then Close. 58 .1.4. 8. Activating and Deactivating External Equipment in TEMS Investigation Activating External Equipment 8. 8. • • If you want to use a device that is not officially supported.1 User’s Manual 4.4.4. and all IP-related information elements will then be populated. 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).3. The device is added to the list in the main dialog window. All IP-based services can be tested (as well as video streaming). You need to activate a device in TEMS Investigation before you can use it for data collection. provided that it comes with Windows drivers enabling an IP data connection. Below is an example.

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

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

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

No check is performed that the physical connections are in fact still the same.1 User’s Manual 8. To prevent this. If you have been working with different equipment configurations connected at various times to the same PC. 62 . if you are using an equipment case and let two phones swap places. the dialog is provided mainly for the purpose of troubleshooting in cases of conflicts during device detection.TEMS Investigation 14. only one of them will be paired with it. Device Detection Properties The Device Detection Properties dialog can be used to enable and disable detection of various device categories. 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. Each AQM module can only be paired with a single phone. To open this dialog: Click the Device Detection Properties button at the top of the Equipment tab.6. If several phones have previously (at different times) been using the same AQM module. 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.1.3.6. Note that normally there is no need to do this. the re-pairing will be incorrect for these phones and the AQM data will be garbage. 8.2. the following holds: • • Only AQM modules that are physically present when you click the button will be paired. For example.

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

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

1. See chapter 21. WCDMA Barred cells. Samsung Galaxy S 4G Xperia arc S* (Qualc. Supported for Qualcomm chipset based UMTS devices. K600i Access class control Band lock. these functions are in many instances implemented as device properties instead. Z750i K800i. Supported for devices capable of audio quality measurement using Call Generator/MRU.Chapter 9. Note that for devices other than Xperia arc S. No.0 Nokia NTM3 65 . access control BLER target control (WCDMA) Cell lock (+ prevent) PLMN control RAT lock Reserved cells. GSM Band lock.1. Regarding other control functions. Operating and Controlling External Equipment Manually 9. 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. See the Getting Started Manual. section 10.) K790i/a. access control NT12-7002 ver 1.1.3. W600i Control Function Samsung Infuse 4G TM506. see the table below. Sony Ericsson C702/C905*/W760i/W995* Sams.

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

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

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

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.Chapter 9. NT12-7002 ver 1. 1.0 69 . See below. click the Add button: • Band selection: Here you specify a GSM band from which to select ARFCNs.

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

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

1. 4. 72 . select it and click Remove. Below is an example of a WCDMA Cell Lock setup. the phone is locked on the Band I (2100 MHz) cells having UARFCN 10565 and SCs {3.1 User’s Manual You can define additional items as shown above to extend the cell/UARFCN set. • To remove an item from the list box. 5}. 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. clicking the Add button each time.9.TEMS Investigation 14. Specifics on the NV interface are vendor proprietary and must be obtained from the vendor. The dialog is limited to 4 bytes. Here. this is however sufficient to cover most basic NV items. 9.

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

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

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

Positioning Logfiles by Pinpointing in the Map Window This section describes how to use the pinpointing technique for positioning logfile data. Pinpointing is useful in environments where GPS coverage is lacking. and you cannot view or edit any settings controlling this behavior.TEMS Investigation 14. the Pinpoint Window.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. The Pinpoint Window is dealt with in chapter 12. meaning that you indicate your exact positions as you walk around measuring. 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. If you check this box. an internal history buffer (providing quick access to logfile data) is cleared every time you start recording a new logfile. 86 .3.000 messages. To prevent out-of-memory issues. TEMS Investigation also has another pinpointing tool. the history buffer in TEMS Investigation is automatically cleared on reaching a size of 410. The pinpointing described here is done in the Map window and is manual. This function is automatic.1. 11.

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

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

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

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

2.0 91 . “Equipment” Subtab This subtab holds all devices that were activated in TEMS Investigation during recording of the logfile.2.) just as is done in live mode for active devices on the Navigator’s top-level Equipment tab (Information subtab: see section 8. No data from that device will then be loaded into the presentation windows when you load the full logfile contents. 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. Logfiles 11. NT12-7002 ver 1. Selecting a device populates the fields at the bottom (Capabilities.3. etc.2. The Revision field contains miscellaneous device information such as firmware revision.Chapter 11.2).

3. “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.TEMS Investigation 14. 92 . etc.2. You can show all activities or only those of a particular type. Failed. Activity: The chronology is broken into separate tables for each type of activity performed. Filter by Equipment Filter by Activity You can show all activities or only those of a single EQ.2.1 User’s Manual 11.). You can group and/or filter the contents in various ways: Group by Not Grouped: The chronology is given in a single table. Result: The chronology is broken into separate tables for each possible outcome (Succeeded.

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

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

e.x logfiles cannot be loaded in TEMS Investigation.x. 8.5. Note especially the search functions in message windows. on the Menu tab of the Navigator. choose Configuration  File Transfer. 6. 7. click the Settings button. TEMS Pocket 9.0 95 . 2.4.1. • • Setting Up Logfile Transfers To set up FTP logfile transfers.2.x (any MTU logfiles) TEMS Automatic 4. 2. 1. Logfile Transfer via FTP TEMS Investigation has a function for uploading logfiles via FTP according to preconfigured FTP server settings.Chapter 11. 11. 11. files logged by the scanner itself) MTR files (GSM.x. section 3. described in section 26.x (any MTU and TEMS Pocket Remote logfiles) TEMS Automatic 5.0. see the Informations Elements and Events volume.x.7. NT12-7002 ver 1. Logfiles • • • • TEMS Automatic 9. Please note that logfiles from these TEMS Pocket versions must first be converted using a PC utility that is delivered with that version. 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. Viewing Logfile Contents Everything about data presentation is dealt with in chapters 23–31.10) 11.5.x (MTU logfiles recorded with GSM-only MTUs) TEMS Automatic 3.

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

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

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

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

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

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

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

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

Layer 3 messages. MapInfo Specific Settings For MapInfo export (whether to Interchange or Tab format).2. and phones’ mode reports exported as unabridged plain text to a common separate file whose name ends in _textexp.txt.TEMS Investigation 14.1 User’s Manual Message options Check the relevant boxes in order to have Layer 2 messages. 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. By default all reports are exported. 104 .6.3. 11.

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

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

3. for example. which is found under <TEMS Investigation install dir>\Application. right-click and choose Start from the context menu (or click the Start button in the window). /IF and /InputFiles can be used interchangeably.ExportTool.6. Command Line Controlled Logfile Export Logfile export can alternatively be initiated from a Command Prompt by running the file TEMS.2) are not saved in the above-mentioned files. • • To start executing the export orders.Chapter 11.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. the NAME and NODATA settings for information elements (see the introduction of section 11. To abort the execution of the export orders. The command has the following syntax.0 107 . NT12-7002 ver 1. 11. They are instead written to DBF files that are found in the Settings directory beneath the TEMS Investigation installation directory.ExportTool. A summary of the export execution appears in a popup window (“Export Result”). Mandatory Command Line Switches /IF (or: /InputFiles) Equivalent to Input files field in logfile export dialog.) to separate files. Logfiles However. right-click and choose Abort from the context menu. Executing Export Orders All the export orders you have defined are listed in the Export Logfile window.1. Use semicolons (.exe. 11.4. 11.6.6.6. where optional parts are placed within square brackets [ ]: TEMS. Wildcards can be used in the file name in regular DOS fashion.4.

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

The format string needs to be enclosed within double quotes (" "). the export is done in text format.) as delimiter. If you specify several cell files. NT12-7002 ver 1.0 109 . /E (or: /Extension) Equivalent to Extension field in logfile export dialog. /V (or: /Verbose) If you include this switch.Chapter 11. If this parameter is omitted. /EF (or: /ExportFormat) Equivalent to Format setting in logfile export dialog. 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. /S (or: /Suffix) Equivalent to Suffix field in logfile export dialog. /MO (or: /MergeOutput) Including this switch is equivalent to checking the Merge output checkbox in the logfile export dialog. Note again that for some export formats you cannot override the default extension. use semicolon (. the name of each exported logfile will be printed in the Command Prompt window. Logfiles /CF (or: /CellFiles) Equivalent to selecting cell files by clicking the Cell files button in the logfile export dialog.

4.3.exe /IF "C:\ExpTest\0825*" /OD C:\ExpTest\Export /V /CFG "C:\ExpTest\GsmN.2. No special tool is currently provided in TEMS Investigation for accessing the uplink AQM data. Merging Uplink AQM Data into Logfiles (UMTS) As described in chapter 35. 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. 110 . by default under C:\TIPESQ in a subfolder named <yyyymmdd><phone number>.1.1 User’s Manual 11.7.7. 11. you need to export the TEMS Investigation logfile with Format set to PESQ merge.ExportTool. Example Below is an example of a logfile export command: TEMS. uplink AQM data is computed by a Call Generator and output in XML files. This could be done in a number of ways. The XML files are given random four-digit numbers as names. Note: When downloading the uplink data files it is important to preserve the Call Generator directory structure. The output is stored under C:\ExpTest\Export. since the merge algorithm relies on this structure to locate the correct files. To perform the data merge. 11. See the screenshot in section 11. This uplink data needs to be inserted in each logfile (*.trp) recorded with TEMS Investigation.TEMS Investigation 14. Retrieving Uplink AQM Data The uplink AQM data is stored as XML files on the Call Generator PC. The output is a new logfile (still in *. using the setup described in the configuration file GsmN. the files must be collected manually from the Call Generator.trp format) that includes both uplink and downlink AQM data.6.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).tex.7.

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

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

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

Adding User-defined Thresholds • To add a pair of thresholds. All thresholded information elements listed will also have their distributions visualized in bar charts. Choose an argument (where applicable).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”. 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. Specify the two thresholds. 114 . In the report. Check those that you wish to use. Check a cellular technology to use all thresholds defined for that technology. 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. • • • Choose an information element. click the Add button.TEMS Investigation 14. and uncheck the others. as is seen in the above screenshot. you can also define your own thresholds. A number of thresholds are predefined in the dialog.

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

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

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

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

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.Chapter 11.0 119 .

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

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

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

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

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

Scanning: General Scanning can be done either • • manually from the Navigator’s Equipment tab. and they are gone through in chapters 14–19. Note. Scripted Scanning Scripted scanning works just like scripting of other activities and does not require special comment. or as an activity in a Service Control script. however. The configuration dialogs are the same in both cases.Scan .1 User’s Manual 13.1.TEMS Investigation 14.16. please refer to chapter 20 (the scan activities are listed in section 20.5). 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.

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

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

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

5.TEMS Investigation 14.4. 13.6. Sony Ericsson Phones and SRUs Sony Ericsson phones and SRUs do not handle concurrent execution of multiple scanning methods. 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.1 User’s Manual R&S recommends that each scan task should be allocated at least 20% of resources in the setup dialog. 13. See section 8. 138 .5.

Scanning Methods and Capabilities TEMS Investigation offers these GSM scanning methods.4. 14. see the Getting Started Manual. GSM Scanning 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. chapter 14. see Information Elements and Events.1.0 139 .Chapter 14. Please note that for a scanning method to be actually available in TEMS Investigation. 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. 1. the device must have been purchased with the relevant option (wherever applicable).1.1. section 4. supported using the various devices as indicated. 2. although this is a slight abuse of the term. A note on terminology: GSM radio frequency carriers are sometimes referred to below as channels for simplicity. NT12-7002 ver 1. section 10.1. For more information about connectable scanners with GSM scanning capability. For specifics. Built on Ericsson hardware.

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

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

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

3.2.0 143 . see chapter 30.1.Chapter 14. 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.5.5. NT12-7002 ver 1. The bottom chart by default shows all scanned channels in order of ascending ARFCN. 14. See section 15. GSM Scanning 14. Spectrum Analysis The setup for spectrum analysis is the same as for WCDMA (except that Technology = GSM). Regarding the bar chart window itself.

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. the device must have been purchased with the relevant option (wherever applicable). see the Getting Started Manual.1. chapter 14. 15. section 10. For more information about connectable devices with WCDMA scanning capability. Please note that for a scanning method to be actually available in TEMS Investigation.1 User’s Manual 15.1.TEMS Investigation 14.4. Scanning Methods and Capabilities TEMS Investigation offers these WCDMA scanning methods. 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. 144 . supported using the various devices as indicated.1.

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

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

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

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

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

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

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

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

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

See Information Elements and Events. the difference between them in dB. section 3.2. The peak code power of the scrambling code (Ec) relative to the total signal power in the channel (Io). The aggregate code power of the scrambling code in dBm. 15.e. Time in chips from the first to the last Ec/Io peak that is above the PN threshold. The peak code power of the scrambling code in dBm. 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”. the number of Ec/Io peaks (multipath components) that are above the PN threshold. Rake receiver gain.e. i.3). the difference between them in dB.2. Rake finger count. The time offset of the radio frame on the CPICH. Ranges from 0 to 38399. i.e.2. This is a measure of the signal spreading due to multipath propagation. i.9. Difference in dB between the aggregate code power (Ag Ec) and peak code power (Peak Ec).TEMS Investigation 14. i. Signal-to-interference ratio of the scrambling code in dB. The aggregate code power of the scrambling code relative to the total signal power in the channel (Io). Presentation: “CPICH Scan” Line Charts The default configuration of this window is as follows: 154 . given in chips from a 1/100th second time mark aligned with GPS time. 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. Measured on DPCCH.e.1 User’s Manual SC Peak Ec/Io Scrambling code number.

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. WCDMA Scanning Chart Panes The charts present the five strongest scrambling codes. Additional Information Pane The Additional Information pane (bottom right) shows the CPICH pilot pollution situation. Legend Pane The Legend pane (bottom left) glosses either of the two charts. 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. you need to add them manually. Here an SC is regarded as a possible active set member if it is sufficiently 1. NT12-7002 ver 1. To switch to the other chart.Chapter 15. right-click and choose the desired chart from the context menu.

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

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

section 3.13.11.2. However. 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. Another piece of data found in SIBs is an uplink interference measurement.2. Presentation: “Finger Info” Status Windows These windows present Rake finger information obtained during Pilot scanning.TEMS Investigation 14. 15. Customizing the Presentation 15.12. Sort by decreasing Aggr Ec/Io (default) Sort by increasing Aggr Ec/Io A dialog appears with these sorting options: 158 . see Information Elements and Events. decoded System Information Blocks are output in the Layer 3 Messages window at a greatly enhanced rate.11 above regarding the presentation of this data. 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. section 7. • • • • Open the General window from the Navigator.2.13.1. section 3. Double-click the item “WCDMA”. For definitions of the information elements. 15.2. See Information Elements and Events.2. The uplink interference measurements can of course be inspected in the plain-text SIB decoding.2. but they are also extracted as information elements. Presentation: BCH Scanning All scan data collected using the options Scan selected and Scan strongest are obtained for BCH scanning also (though less frequently). see sections 15.2.7–15.1 User’s Manual 15.2. This is particularly interesting for HSUPA. The sorting order is set in the General window. see Information Elements and Events.2. No special presentation windows are provided for BCH scanning. Sorting of Scrambling Codes You can sort scrambling codes in scanning information elements in a number of different ways.

and this sorting order is unchangeable. Sort by scrambling code: Scrambling codes are sorted by index. section 3.2) is fixed and is not affected by the General window settings. WCDMA frequency band to scan. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events.2).13. etc. WCDMA Scanning • Sort by fixed position: Scrambling codes are sorted by index and are always assigned the same argument indices.Chapter 15. • 15.1.3. 15.1. i. on a Primary Synchronization Channel (P-SCH). UARFCN to scan. It is useful for monitoring synchronization reference signals sent on this channel. Setup of SCH Timeslot Scan General Settings Always “WCDMA” for WCDMA scanning.3.e. the code with the lowest index appears at argument index 1.3. the code with the next higher index appears at argument index 2. 15. scrambling code n is always found at argument index n + 1. all scrambling codes found on all UMTS frequencies are collected in a single array. SCH Timeslot Scanning This method scans timeslot-length intervals.1. 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. 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. 15.2.2. intervals 2560 chips long. Technology Band Channels NT12-7002 ver 1. These elements are sorted by signal strength (Aggr Ec/Io) in descending order. that is.0 159 .

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

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

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

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

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

If you want the UARFCN range to consist of a portion of a band.6.101. UARFCN Ranges (“Interval 1. Include additional channels Context Settings Check this to include additional channels on the 1900 or 850 MHz band. Custom range. sections 5. To 15. Setup of Network Scan General Settings Choose “WCDMA” for WCDMA scanning. From. Each range can be located on any of the supported frequency bands.2.Chapter 15.1.1. 2. NT12-7002 ver 1. Additional fields “From” and “To” appear.3. WCDMA Scanning 15.) If this option is checked. 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.6.0 165 .6. set Custom range to Yes. If you want the UARFCN range to be identical to an entire WCDMA frequency band. in which you specify the endpoints of the UARFCN range. Interval <n> enabled Band Set the flag to Yes if you want to define this UARFCN range. 3”) You can set up three separate UARFCN ranges (Interval 1.4 for details on the two kinds of channel.6.1. 3) to scan in the network. Technology 15. 15.1. select that band here. 2. (See  3GPP 25.4. Additional channels have UARFCNs that are completely different from the general channels.3–5.4.

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

chapters 12–14. For more information about connectable devices with LTE scanning capability. NT12-7002 ver 1. supported using the various devices as indicated.4. the device must have been purchased with the relevant option (wherever applicable).Chapter 16. see the Getting Started Manual. LTE Scanning 16. 16. 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. Certain scanners require special configuration of the device itself as well as the PC to prepare them for use with TEMS Investigation.1. What needs doing is covered in the Getting Started Manual. Scanning Methods and Capabilities TEMS Investigation offers these LTE scanning methods.1. section 10. Please note that for a scanning method to be actually available in TEMS Investigation. It is possible to run several of these scanning methods concurrently.1.0 167 .

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

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

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

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

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

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

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

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

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

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

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

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

Max: 20000. 180 . Time offset in units of 50 μs. Setup of Enhanced Power Scan Bandwidth to scan. Must be less than or equal to Timing Period Mark. Given in units of 50 μs. See Information Elements and Events. or maximum frequency of the band to be scanned.4. The scan will start on the nearest Timing Period Mark with the Timing Period Mark Offset specified.1.5. 16. the enhanced power scan is a higherperformance scan that provides selective power measurements in the time and frequency domains. EARFCN to scan within the selected LTE band.6. 16. Enhanced Power Scanning Compared to the spectrum scan. Setup of Enhanced Power Scan: General Always “LTE”. Technology Band Channel 16.TEMS Investigation 14. LTE band to scan.5.5.2. Spectrum Scan Presentation Spectrum scans are presented in a predefined bar chart. 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. section 8.3.3. center.1 User’s Manual 16.

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

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

NT12-7002 ver 1. 17. located between the two data sections.3. The DwPTS is used for downlink synchronization. The scanner automatically finds the strongest CPIs. and synchronization.Chapter 17. • • 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. 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. which is transmitted in Timeslot 0 (TS0). During the cell search procedure.3. The midamble is used as a training sequence for channel estimation. Midamble Top N Pilot Scanning This mode measures the Primary Common Control Physical Channel (P-CCPCH). The switching points are used to manage the transition between uplink and downlink (since TD-SCDMA utilizes TDD to separate uplink and downlink). which is located just before the first switching point in the Guard Period (GP) and after Timeslot 0. different parts of the TD-SCDMA frame are measured. To this end it scans the TS0 midamble (144 chips). SyncDL Top N Pilot Scanning This mode measures the Downlink Pilot Timeslot (DwPTS).1. table 6. the UE acquires the timing of the DwPTS by correlating with the SYNC-DL code transmitted in the DwPTS. Number of Pilots To scan the N strongest CPIs. section 7. as explained further below.223-840.0 183 . The value N is determined by the Number of Pilots parameter. TD-SCDMA Scanning 17. enter the value N here (N  32). power measurements.3.

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

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

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

Min: –24.3. Min: 1.2. Setup of Pilot Scan: Andrew Minimum time for scan in ms. 18. CDMA: Scan correlation length in chips. Up to 12 RF channels can be selected. The PN increment. Max: 16. CDMA RF channels to scan within the selected band. CDMA Scanning 18.Chapter 18. 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. Pilot Scanning This method scans pilots. scrambled with cell-specific PN sequence offsets. Entering the number N means scan the N strongest pilots.3.2. Must be divisible by 128. Compare the discussion of the corresponding parameters in section 18. Max: 2048. Min: 1. Min: 512.0 187 . Ec/Io detection threshold in dB.1. EV-DO: Scan correlation length in slots.3. Scan Rate Report Threshold Number of Top N PN Increment Correlation Length NT12-7002 ver 1. Max: 32. Max: 0. Each channel is specified as a number representing the center frequency of the channel. 18.

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

Settings Specific to EV-DO (IS-856) Pilot Window Length This parameter indicates the length. Search Window Size Normal (64 chips). CDMA Scanning Remaining Measurement Points See section 13.. The maximum radius within which to detect pilots. If a pilot increment is used. NT12-7002 ver 1. The maximum pilot window length supported by the scanning receiver is 64. Start Pilot Pilot Increment Max Cell Radius The index of the first PN allocated.1. or Wider (256 chips). Wide (128 chips). . This parameter. 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. 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 PN increment. 3. in chips. only the PNs 0. TEMS Investigation will filter the list of selectable PNs: for example.5.Chapter 18. will appear in the list.0 189 . of the time window in which the pilot is searched. if Start Pilot = 0 and Pilot Increment = 3. are applicable only in “Scan selected” mode. This is also the default and recommended setting.. along with Start Pilot and Pilot Increment. 6.

Remaining Options Measurement Mode (EX only) There are two choices. it is only found in scanner reports. Each sample reported by the scanner is typically based on a measurement 20 ms in length. The sum of all peak pilot Ec/Io values above the PN threshold. High Dynamic puts the emphasis on accuracy.TEMS Investigation 14.1 The number of chips between the first and last pilot Ec/Io peak above the PN threshold. High Speed is faster and accordingly less accurate. This measurement does not appear as an information element. 190 .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. High Speed and High Dynamic. These are two algorithms with different priorities. 1. Each reported sample is typically based on a 10 ms measurement.

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

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

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

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

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

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

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

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

Measurement Mode Enable Channel Response: Time Domain Enable Channel Response: Frequency Domain Measurement of channel response in frequency domain. If set to True. 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.Chapter 19. Measurement of multipath delay spread. It should normally be enabled. One of Fast mode. Measurement of delay relative to GPS. Measurement of channel response in time domain. If set to False. that is. CINR will be measured over all segments.0 199 . cluster size N = 1 will be used for CINR measurement. or Rogue mode. NT12-7002 ver 1. Robust mode. Measurement of downlink MAP pilot CINR. Measurement of downlink MAP pilot power. Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. CINR will be measured for each segment. that is. since otherwise high level signals may saturate the receiver and cause errors. Measurement of downlink MAP data power.

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

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

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

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

The Service Control Designer The Service Control Designer window is where you compose service control workflows (scripts): 204 CDMA UMTS Service/Technology LTE . it should be noted that data service testing with Ericsson Fixed Wireless Terminals is limited to FTP.TEMS Investigation 14.3. there are no technology-related restrictions.1 User’s Manual Regarding other connectable devices. 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. and Ping. 20. What scanning devices can have their actions scripted is stated in chapter 13 (introduction). 20.4. HTTP.

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

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

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

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

1 for full details. you need to specify whether to use RAS or NDIS. Service Control If you want the script to control both caller and receiver.3.6. • 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. In particular. Setting Up a Network Connection This section shows how to set up a network connection. only it contains many more parameters. which is a necessary preparation for running data services. See section 20.16. • Expand the IP node in the Activity pane and add a Network Connect activity to the script.0 209 . turn to section 20.4 for guidance. 20. NT12-7002 ver 1.10.Chapter 20.

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

NT12-7002 ver 1. Service Control 1 2 • The FTP session itself is handled by the FTP Download activity.0 211 . 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. Insert an activity of this type between network connect and disconnect: • For the FTP Download activity.Chapter 20.

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

20. For an example of such a predefined snippet in use. see section 20.4. Example: The detach-plus-attach procedure in section 20. saving time and effort when creating new scripts.0 213 .8 could be a good candidate for a user-defined snippet. Predefined snippets for all supported services are provided in the Activity pane. (The KPI computation itself is done using TEMS Discovery or TEMS Automatic. since it will recur in any script where you want to detach and then reattach to the PS network. Service Control PS detach PS attach See also section 20. NT12-7002 ver 1. The predefined snippets are also tailored to produce all data required to compute KPIs. then enter the File menu and select Save as Snippet.) 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. You can also save an arbitrary activity sequence as a user-defined snippet: • Select all of the activities by dragging the mouse pointer. You are prompted to name and describe the snippet.9.9.10.Chapter 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. • Suppose your script includes PS detach followed by PS attach as described in section 20. to enable or disable them.1 User’s Manual 20.10. You can then encapsulate the PS Detach and PS Attach activities within a sequence. Sequences You can formally define a group of activities in a script as a sequence. then drag them both (using the PS Detach box as handle) into the sequenceActivity1 box.10.8.1. You can now enable and disable the detach–attach sequence as a whole: 214 . 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. 20. Suppose further that you want a convenient means of turning the detach/attach activities on and off. This is handy if you want to apply some operation to all of these activities – for example.TEMS Investigation 14.

Chapter 20. For full details on the Sequence activity. then after the FTP download has completed we want to continue with a video streaming session.16.12. (This is accomplished by imposing a “terminate on event” condition on the activity. 20. Here is an example. To this end we use an if–else construct in the following manner: • First add a Network Connect activity. Service Control Compare section 20.e.2. Suppose the phone is on a WCDMA network and is instructed to do an FTP download.0 215 . the activity should terminate. then we want to abandon the download. 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. see section 20.5. so that the throughput is sharply reduced. Now if the phone is handed over to GSM. i.10.2. we want to proceed with a voice call (which does not require a large bandwidth). 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. see section 20.15. If on the other hand the phone remains on WCDMA.) After a handover to GSM has occurred.5.

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

(Just as with sequences – compare section 20. 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. Service Control • Begin by dragging a While activity to the start of the workflow. then fill it with the desired contents. you first add the empty While construct to the workflow.10. You can accomplish this by appending a Wait activity at the end of the FTP snippet: NT12-7002 ver 1. set the number of times you want to iterate the while loop. we stipulate that the loop should be run five times in total.1 –.Chapter 20.) In the Properties pane. by entering the value 5. Below.0 217 . • • Now drag the predefined FTP download snippet into the while loop.

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

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

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

Set the wait time to 10 seconds. we need to change the equipment (EQ) parameter to EQ2 and EQ3 in branch 2 and branch 3 respectively. Let us begin with the voice calls: • • • Add while loops to branches 2 and 3 and set each to execute 5 times.0 221 . Add a voice call snippet (a predefined one is found in the Activity pane) to each while loop. After these steps. Service Control It is now time to define the service-related activities.Chapter 20. 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. To assign the activities to the correct devices.

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

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

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

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

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

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

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

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

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

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

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

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

TEMS Investigation 14.3. Clicking an underlined number in this table brings up a summary of each activity that has been run. Below is an example (UDP with full duplex tested): 20.3). Running Scripts from the Service Control Designer • Enter the Script menu and choose Run.15.15. 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.15. Viewing Statistics on Script Execution On the Summary tab of the Service Control Monitor. statistics are given on the outcome of each activity type (number of succeeded. 234 . and failed activities).4.1 User’s Manual 20. Click the Stop Script button to stop script execution. aborted. Click the Return to Designer button to return to the Service Control Designer window.2.

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

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

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

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

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

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

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

Result = Stopped by Event: The activity was aborted because a specific event occurred (Abort property set to On Event. For usage examples. Result = Failed: The activity failed for whatever reason (other than termination by the TEMS Investigation user). 1. see section 20. This can happen only if the activity has its Abort property set to On Timeout: see section 20.10. 242 . • 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. Result appear where you detail the required outcome: for example.2. “Stopped by User” equates to the user right-clicking the activity in the Navigator and choosing Stop. Operator.TEMS Investigation 14.2). This is not considered during validation. • • • • Result = Succeeded: The activity completed normally. see section 20.1 Result = Stopped by Duration: The activity was aborted because its maximum duration expired. Additional fields Activity.17. again. “ftpDownloadActivity1 Equals Failed”. Result = Stopped by User: The activity was stopped by the user clicking the Stop Script button.6. If the activity is executed manually from the Navigator as described in chapter 9.1 User’s Manual Activity Result: Wait for a particular outcome of another activity in the script.17.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.3 18. to Config.6 19.3 17. Descr.5 15.Chapter 20.4 18. Service Control • Configuration property: Scan configuration.2 16.2 14.3 19.2 15.4 14.6 17.5 15.4 16.3 16. Below is a full list of the scan activities. identical to that for a manually initiated scan.3 15. keyed to their configuration descriptions: Ref. These are all described in chapters 14–19.5 18.0 263 .4 19. 15.5 16.4 18.

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

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

16. This activity has no unique properties.3.6.2.12. Valid characters are: +. section 20... the device waits for the event Call Established.16.2.TEMS Investigation 14..3. If this event does not occur.16.3. *.. 9.4. 20.7. Voice Activities 20.16.7. this should be the number to the Call Generator or MRU: see section 36. 20. see section 20. RTSP Port . 266 . section 20. 20. The retry behavior is governed by the On Failure property.16. and p (for pause). URL .2. see section 20. WAP Streaming snippet: PS Detach  PS Attach  Network Connect  WAP Streaming  Network Disconnect..1. The call duration is most conveniently specified by means of a subsequent Wait activity. Predefined Snippets for Video • • Video Call snippet: Video Dial  Wait  Hang Up.6.7.7. After dialing.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. Answer Waits for an incoming CS voice call to arrive and answers it when it arrives. Streaming Mode: See the Streaming activity. User Agent: See the WAP Get activity..16. • Configuration property: Phone Number: The complete phone number (including country code) to call. ..17. Dial Dials a phone number and sets up a circuit-switched voice call. you may instruct the device to retry the call. 0. #. For AQM measurement.16.6.

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

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

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

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

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

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

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

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. Start TEMS Investigation. choose File  Save As Image in the Service Control window and select the desired image file format. Save your script with Format set to Redistributable. The script can now be not only run but also freely modified on the receiver PC.1. To this end. 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.TEMS Investigation 14. Choose this option if you are going to use the script on one PC only.19. This means that changes to a configuration set will automatically propagate to all scripts that reference it.1 User’s Manual – Standard: No configuration sets are saved with the script. click the Load button on the Service Control Designer toolbar. 274 . Saving Workflow as Image • You can also save the contents of the workflow pane as an image. (This is the default setting. To open an existing script stored on file. Choose this option if you are going to use the script on several computers.19. Open the sender’s workspace. – 20. Export your configuration sets. making the TSC file a self-contained and independent entity that can be immediately reused on a different PC. Open the sender’s script.2. 20.) Redistributable: All configuration sets referenced in a script are saved with the script.

20.20. 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. Zooming the Workflow Pane In the workflow pane. 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. except the Move Left and Move Right commands which you can use to change the ordering of activities in a workflow.2. You NT12-7002 ver 1. where mouse pointing actions have the effect of zooming the workflow pane in or out.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.0 275 . 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. 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. the mouse pointer by default has the usual point-andclick function. 20. After you click the Zoom In button on the window toolbar. 20.1. The rest is standard Windows functionality. By default all activities are shown (“All”). The context menu is especially useful for changing properties (EQ assignment. Further Functionality in the Service Control Designer Window 20.3.Chapter 20. on-failure behavior) of several activities at once. You can however switch the mouse to zoom mode.20.

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

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

Changing order of priority between codecs is supported for C905*/ W995* only. access control BLER target control (WCDMA) C/A measurements (GSM) Channel verification (GSM)1 Disable handover CL EDGE capability control L3 messages.1 User’s Manual Sony Ericsson C702/C905*/W760i/W995* Sams.) Control Function Samsung Infuse 4G TM506/Z750i Access class control Barred cells. That is. prevent handover to specified cells. 278 Nokia NTM3 K790i/a W600i K800i K600i . No. Samsung Galaxy S 4G Xperia arc S* (Qualc. 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.TEMS Investigation 14. See chapter 43. access control Speech codec control3 TxPower control (GSM) 1. 3. 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.

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

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

2. 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. By default all codecs are enabled. Then use the arrow buttons on the right to adjust the order of priority for the selected codecs.0 281 . Those that you leave in the Selected box will remain enabled. NT12-7002 ver 1. see above. 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.2. Number of adjacent channels Specify one or two channels. • For other phone models you can only select which codecs should be enabled.Chapter 21. this is done in a regular property grid. 21.4.

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

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

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

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

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

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

For speech codec information elements to be populated.TEMS Investigation 14.4.4. you must enable all logs with “Vocoder Packet” in their names. 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. 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. 21. This is true for the Sony Ericsson Xperia arc S as well. RAT lock and band lock functions are available. If the log is turned off. no RRC State is presented until the state changes. Regarding the NV (Nonvolatile) interface. see section 9. Please note that with this device. The “WCDMA SIR Target” log must be turned on for the WCDMA SIR Target element to be populated. as explained in section 9. • • 288 . However. for certain devices such as Option data cards and Sierra Wireless UMTS data cards.1.1. Properties of Qualcomm Chipset Based Devices Properties of Qualcomm chipset based devices are mostly limited to enabling and disabling of various logs.9. for this device all control functions are applied from the Navigator. not for packet-switched data.1. C/I is obtained only for circuit-switched.1 User’s Manual 21.

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

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

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

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

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

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

proceed as follows: Click the Cell Whitelist button. The input might look something like this: NT12-7002 ver 1. In the dialog that appears. 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). Outside of these cells. 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.Chapter 22. Events C/I Worst < 10 AND RxLev Sub (dBm) < –99 15. 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. A list of allowed cells is referred to in TEMS Investigation as a “whitelist”. 22. Generating Cell Whitelist Events The Event Definition window has a special function for generating userdefined events based on cell lists. The event is now added to the event list and can be used in the Map window and in other presentation windows. Click OK to finish.4. To construct your whitelist. chapter 6.0 295 . For example.

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

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

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

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

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

23. Presented Data The presentation windows are used to present information elements.2. see Information Elements and Events. events.1. Full details on information elements follow in chapters 3 and 4 of that volume. 23. see Information Elements and Events. Regarding predefined events. chapter 2. Data is presented in fundamentally the same way in both cases. and messages. 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.Chapter 23. 24 25 26 27 28 29 30 NT12-7002 ver 1. Presentation: Basics This chapter covers the fundamentals of data presentation. either in real time or during logfile analysis. For an overview of information element categories.0 301 . Presentation: Basics 23. chapter 7. differences are noted whenever relevant in the chapters that follow.

The EQ designations currently do not appear in presentation windows. as opposed to the Navigator and Service Control components.TEMS Investigation 14. 31 23. Event Counter windows). and choose the same item from the context menu. Alternatively.1. choose Set Equipment Number. right-click any empty part of the worksheet. 302 . From the Worksheet menu. devices are represented by their channels: • • • MS for radio measurements DC for data service measurements PS for positioning equipment. for example. Device Channels: MS/DC/PS In presentation windows.3. 23.3.1 User’s Manual Window Type Map window Chapter Ref. “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. • • The change will affect all presentation windows that display data from a specified device (as opposed to. Select the equipment (EQ/MS/DC) number in the dialog.

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

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

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

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

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

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. Min/Max indicator Associated information elements Information Element 1 Information Element 2 • Select the Color tab to customize colors and color ranges. Draw the bar with constant length. 308 . Check to display numeric values as colored bars.6. See screenshot in section 24. etc. Center. Right Bar Constant length Check to display values alphanumerically. Choose alignment for the displayed values. Keep track of the all-time-low and all-time-high values by means of vertical lines.2.1 User’s Manual Value Left. In that window. This is useful for information elements that represent states.TEMS Investigation 14. This checkbox with accompanying combo boxes is enabled only for the CDMA window Finger Info. and can only assume a limited number of values.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If multiple numeric values are given in the file name.16.1. not counting overhead. 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.TEMS Investigation 14. If the file name does not contain a numeric value. The mechanics of setting up and conducting a streaming session are handled by the Streaming activity in scripts: see section 20. and various forms of live streaming (such as tapping into a live stream or repeating playlist delivered by a streaming server). If you are using files of your own for testing streaming. Video clips suitable for testing are supplied on the installation CD in the subdirectory Video Clips. but the VSQI score will then be less accurate. where a video clip of known length is downloaded. you need a phone capable of handling this service.6. This value should indicate the bit rate of the stream (video + audio). 27. the first is used. How to Test Video Streaming To test the video streaming service.1 possess this capability. where the duration of the streaming session is specified by the user.1 User’s Manual 27. 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. the file names should contain a numeric value followed by “kbps”. 324 . All phones sold with TEMS Investigation 14.4. The application supports both on-demand streaming. Video Streaming and the Video Monitor TEMS Investigation supports streaming of video recordings via suitable connected devices. the VSQI algorithm (see chapter 40) will use a bit rate value received from the server.

0 325 . NT12-7002 ver 1. so only one video stream can be replayed at a time.2. (On the other hand.1. 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. • 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. Check this box to play the streamed audio through the PC speakers. The Video Monitor To display the streamed video clip. Video Streaming and the Video Monitor 27.2.Chapter 27. you use the Video Monitor window: Only one instance of the Video Monitor can be open.) 27.

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

0 327 .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. Changing GPS Window Properties The GPS window can be configured to show only the parameters that interest you: NT12-7002 ver 1. Exactly what data is displayed depends on the type of GPS. The GPS Window 28.1. The GPS Window This window shows data from the GPS unit.5). the window shows data from the one currently selected as “Preferred” (see section 8.

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

Line Charts In line charts you can plot numeric information elements in order to visualize how their values evolve over time.0 329 . Preconfigured line charts are listed in Information Elements and Events. Line charts can also present events. chapter 8.1. containing the charts themselves a Y-axis pane for each chart. showing the scales for the plotted information elements NT12-7002 ver 1. Line Charts 29. 29. 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.Chapter 29.

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

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

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

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

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

Line Charts Upper visible limit for IE Upper limit of the value range shown for this information element. For complex information elements. it will be picked from the device the line chart is drawn for (see the title bar). the plot color turns deeper when the phone enters dedicated mode. Lower limit of the value range shown for this information element. (The dedicated mode color is not usercustomizable. it is taken from the next device.Chapter 29. That is. The image file used to label the vertical line indicating the event. • Using the arrow buttons. the limit is automatically changed for all other arguments as well. move the event you want to present to the Selected Events list box.) 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. this setting adjusts the range in the Y-axis pane. The first time you move an element to Selected Events. Clicking the Edit Event button pops up the following dialog: Mobile Symbol The device to pick the event from.0 335 . and the brighter color chosen in the Color box is reserved for idle mode. If you move the same element to Selected Events again. 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. NT12-7002 ver 1. If you check this box.

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

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

TEMS Investigation 14. containing the charts themselves a X-axis pane. A maximum of four charts can be accommodated. The legend can only gloss one chart at a time. displaying labels for the bars drawn a Y-axis pane for each chart. displaying arbitrary information elements in textual format.1 User’s Manual 30. describing the nature and origin of the information elements shown. 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. 338 . The relative sizes of the panes can be freely adjusted by dragging the interior frame handles.1. showing the scales for the displayed information elements a Legend pane. along with their associated Y-axis panes. and indicating their current values an Additional Information pane.

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

30. Adding Charts To add a new chart in the bar chart window: • Click Add. elements which cannot be drawn in a bar chart).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.2.3. select the chart you want to delete and click the Delete button. • Deleting a Chart To delete a chart: In the Bar Chart Properties dialog. as described in section 30. 30.TEMS Investigation 14.4.3. 340 . rightclick anywhere in the bar chart window and choose Properties. Setting Up General Bar Chart Properties To set up some general properties of the bar chart and its presentation. You can choose different contents in this pane for different charts.1. 30.3.

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

) The default color range is defined in the Navigator and is dependent on the information element value (see section 5. or a set of components of complex information elements. (Which choice is available depends on the presentation mode. quality measures).1 User’s Manual 30.g. and the like cannot be displayed. fixed.4. The bar chart is very flexible in that it can be configured in a variety of ways. Data. 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. Colors: You can always keep the default color range for the information elements. Presentation Mode.1. channel numbers.3). Besides. are chosen. timeslot indicators. or to use predefined. Flags. • 342 .TEMS Investigation 14. Colors In this step you select the following (full details on subsequent pages): • Presentation mode. signal strength. window-specific colors. The information elements that can be displayed are chiefly those that represent or are derived from measured physical quantities (e. there is one other option: either to define your own colors for use in the bar chart.

Max The visible range of the information element. It is possible to dynamically adjust the number of components to show.4.1. one which consists of several components. 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). Single IE Presentation Mode In this mode a single information element is displayed. Bar Charts 30.0 343 .2. NT12-7002 ver 1.e.1. • • In the Edit Chart dialog. select Bar chart: Single IE with multiple components.Chapter 30. 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. 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.4. i. The element must be one with arguments. and whether the scale will be flipped with the lowest value at the top.

disregarding the default color range. Back in the Edit Chart dialog. Select Bar chart: Multiple IE components (fixed set).TEMS Investigation 14. • Now click Next to proceed to the next step. Otherwise. see section 30. You will then be prompted to define colors later on. To keep the default colors.4. To set up this presentation. For an example of a Single IE presentation. decide what colors should be used in the chart. check the Use common colors box in the Edit Chart dialog. 30. You have two options: – – Keep the default color range for the information element. To do this. check the Use common colors box.1. 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.5. Multiple IE Components Presentation Mode This mode displays an arbitrary fixed set of information element components. • • • Make your changes. This dialog appears: • • 344 . uncheck it. 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. To this end. Click Choose IEs to select your data. Define one fixed color to be used throughout in this chart.2. Click OK in the Choose Information Element dialog. 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. then click OK.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

so that the map scale can be calculated. • In the Distance section. Specifying the Map Scale In this step you indicate the distance between some two points on the map. click the Pick button. in the Latitude and Longitude fields. 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. you must supply this data yourself. click the point that has the given coordinates. 31.4.4. Map Windows 31. In the Reference Point section.1. Click Position Map.0 359 . 31. • • • Specifying the Map Position In this step you input the coordinates of a point on the map.2.Chapter 31.4. Click the Pick button in the Reference Point section. On the map. NT12-7002 ver 1. enter the coordinates (in decimal degrees) of the point you wish to use.

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

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

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

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

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

Specifically. Note: If you create a new event theme for a user-defined event after loading a logfile.5.4.Chapter 31.0 365 . you create an event theme. • • In the Theme Settings dialog. more markers are filled in to show the route in more detail. you must reload the logfile to make this event theme visible. when you zoom out. Click Add Theme: Event Mobile Choose an event type. Presenting Events To present an event. The plotting density on the map is dependent on the current zoom of the Map window. select the layer named Event Layer. Choose the device from which to pick this type of event. 31. When you zoom in. NT12-7002 ver 1. 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. markers are drawn more sparsely. Map Windows • Map zoom.

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

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

7. section 4. This section governs how cells are drawn.TEMS Investigation 14. Choose ALL to plot cells from all technologies. You might want to create one Cell theme for each technology. see the Technical Reference. GSM and WCDMA cells are told apart by inspection of what type of channel is defined (ARFCN or UARFCN). (Regarding cellular technology support in the CEL and XML cell file formats.) Cell type Type of cell indicated in cell file. Cell presentation 368 . In CEL files.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. Choose a cellular technology to plot only cells from that technology. In XML cell files this is identical with the CELL_TYPE element: see the Technical Reference. chapters 3 and 4.13.

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. Incomplete cells The default color to be used for cells that are incompletely described in the cell file.5.6. this highlighting ceases to be visible if a Cell Color or Cell ARFCN theme is also displayed: see sections 31.5. it is set to 360º in the plot (omni cell. When you select a cell. If the beam width is not stated. In either case.5.Chapter 31. If you uncheck this option. provided that the cell is completely described in the cell file. incompletely described cells will not be marked as such in any way.5. taken from the cell file. The displayed information. see the illustration in section 31.3 and 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.4). it is set to zero degrees in the plot (sector centered on “twelve o’clock”). the following plotting rules apply: • If the antenna direction is not stated in the cell file. Uncheck to make the symbol transparent. The color to be used for the interior of the cell symbol. (However. • Cell labels If you check this option. it turns red. a text label will be printed next to each cell.0 369 .

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. Of course. The Cell Line theme has different meanings depending on the data source: phone or scanner.5. the Cell Line theme gives a best server indication.TEMS Investigation 14. no interaction with base stations is involved during scanning.2.5. This points out the cell that uses the currently strongest signal as measured by the scanning device.) Additionally.5. The Cell Line Theme This theme is used to indicate serving cells and positions where handovers have taken place. 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. TD-SCDMA) active set members (WCDMA connected mode/CDMA traffic mode) (The user interface uses only the term “serving cell”. GSM. 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 .1 User’s Manual 31. provided that cells from both cellular technologies are visible in the Cell theme (section 31.5.1). LTE. rather. the theme indicates positions where handovers have taken place. Use with Phone Data For a phone. Use with Scan Data With scan data.

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

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

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

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

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

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

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

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

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

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

Obtaining KPIs with TEMS Products General Procedure To obtain KPIs. such as (in the packet-switched case) manual reactivation of the PDP context. Integrity KPIs show the performance of successful service attempts. Furthermore.1.1.e. Compose a TEMS Investigation script that executes one or several services. Key Performance Indicators – KPIs (UMTS) 33.1. For example. the user’s perception of the performance may vary greatly. the user must be able to execute a chain of operations: • • • accessing the packet-switched network as such. 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. the service testing should be enclosed by the NT12-7002 ver 1. performing an attach and a PDP context activation within an active PDP context.1.1. once it has been accessed. from very good to unacceptably bad. accessing an IP service (for WAP and MMS) activating a WAP session. Accessibility Accessibility is the ability of the user to obtain a service within specified tolerances and under other given conditions. Integrity Integrity indicates the degree to which a service is maintained without major disturbances once it has been accessed.2. i. perform the following steps: 1.Chapter 33. 33. in order for a service to be accessible in a packet-switched network. 33. under given conditions for a requested period of time.2. 33. 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.2. 33. Retainability Retainability is the ability of the user to keep a service.0 389 .3. Even if a service was accessed successfully.

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

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

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

1. 6. 10. 6. 4.9. for wideband.85.2. 7.95. The score is thus a value ranging from 1 to 5. 7. 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.2.5 s (CDMA) 2–4 s Such a high update rate is possible thanks to the low computational complexity of the algorithm.4. including bit rate information The general discussion of these parameters in section 34. SQI-MOS for CDMA is implemented for the following codecs: • • • • QCELP13K EVRC SMV VMR-WB (narrowband input only) 34.1.65 kbit/s: – – for narrowband. compare section 34.0 393 . NT12-7002 ver 1. The SQI-MOS algorithm produces a new quality estimate at intervals of • • (UMTS) approximately 0.2.2. 34.3.2.60.Chapter 34. and 12.75.65.1 applies equally to CDMA (with the term “handoff” substituted for “handover”). 8. Input parameters are: • • Frame error rate Speech codec used.2. Speech Quality Index – SQI • all WCDMA AMR-NB and AMR-WB modes up to 12. 5. ACR stands for Absolute Category Rating: this is the “regular” MOS test where speech samples are rated without being compared to a reference.7. 5. CDMA SQI-MOS for CDMA closely resembles WCDMA SQI. and 12.15.

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

Such averaging is not required in the case of SQI-MOS. since the speaker-contingent variation is already built into the model (it has been trained with a large number of speakers).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. 1.Chapter 34.) The PESQ algorithm for wideband (8 kHz) speech coding – as opposed to that for narrowband (4 kHz) – is afflicted with certain recognized shortcomings. This is a phenomenon independent of the circumstances described in section 34. NT12-7002 ver 1. • Both methods try to assess to what degree the distortions in the received signal will be audible to the human ear. i. Below is a brief discussion of this topic.1. SQI-MOS.0 395 . a mapping could then be applied to align the wideband scores to narrowband. Notes on PESQ for Wideband (UMTS) (This subsection is relevant for UMTS only. even for clean speech. wideband PESQ has been found to produce lower scores than narrowband PESQ.e. but they do it in completely different ways. 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. on the other hand. is a no-reference method that works with the received signal alone and extracts radio parameters from it (as described in section 34. Speech Quality Index – SQI PESQ and SQI values may differ while both being accurate in their respective domains. variation stemming from the characteristics of individual speakers. 34. PESQ scores need to be averaged over a range of speakers in order to eliminate speaker bias. since CDMA SQI currently does not extend to wideband.3.4. in certain circumstances. One relevant fact is that.

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

35. The POLQA Algorithm POLQA (Perceptual Objective Listening Quality Analysis). Audio Quality Measurement (AQM): General Audio quality measurement. it has been refined to eliminate known weaknesses of PESQ. and multimedia application services. short for Perceptual Evaluation of Speech Quality. Audio Quality Measurement (AQM): General 35. including PESQ and POLQA.2.itu.Chapter 35. However. 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. 3G and 4G/LTE.0 397 . particularly in these areas: • Handling of new and complex types of distortions that arise from today’s convergence and coexistence of voice. • NT12-7002 ver 1. 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. and CDMA networks. superwideband). defined in the ITU P. and VoIP. The PESQ Algorithm PESQ. The PESQ algorithm is defined by the ITU-T standard P.863 standard. data.  www. It can be performed in GSM. WCDMA.1.862. Performance for higher-bandwidth audio signals (wideband. can be purchased as an option with TEMS Investigation.int/ rec/T-REC-P. is the successor of PESQ and has been specially developed for HD voice. One example is the effects of packet loss and of packet loss concealment. The POLQA algorithm is designed along similar lines as PESQ.862/en 35. being a reference-based method that compares the degraded speech with the undistorted original to assess quality.

3. 35.1 User’s Manual • Performance for CDMA speech codecs and hence for CDMA networks in general.1 36.2 37 38 VoIP Mobile to mobile 398 .TEMS Investigation 14. CS voice Mobile to fixed Mobile to mobile Mobile to mobile Call Generator.int/rec/T-RECP.itu.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. More information about POLQA is available at  www. AQM modules Mobile Receiving Unit (MRU) Audio Capturing Unit (ACU) (2 PCs used) AQM modules AQM modules PC PCs 36. A summary of the possibilities is given in the following table: PESQ Service POLQA Call Parties Auxiliary Components AQM Computed By Ref.

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

The downlink AQM data is written to regular TEMS Investigation logfiles. See Information Elements and Events. To merge uplink AQM data into the logfiles. where the signals are compared with the originals.7. 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 phone calls the Call Generator and plays the reference sentences.1 User’s Manual TEMS Investigation.TEMS Investigation 14. and volume. The AQM modules also record a number of further audio quality measurements such as echo delay. section 3. 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. See section 11. echo attenuation. • • 400 .1. The uplink AQM data is stored in XML files. yielding uplink and downlink PESQ scores. The Call Generator responds by playing the same reference sentences. The received (degraded) signals at either end are forwarded to the respective AQM modules. the logfile export function is used.

4). Mobile-to-mobile Audio Quality Measurement with MRU The main difference between this setup and that described in section 36.7. 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.2. logfile export 36. NT12-7002 ver 1.1 is that the fixed Call Generator is replaced by a Mobile Receiving Unit. It covers the both the Call Generator configuration and the MRU configuration.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. AQM with Call Generator/MRU 36. MRU. the MRU does not have an AQM module.16. Measurement configuration: TEMS Investigation. This is the M2M DL option in the PESQ Measurement activity of the Service Control script (see section 20. as recipient of the AQM calls.Chapter 36.0 401 .

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

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

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

16. all measurement is conducted during mobile-tomobile voice calls. 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.7. AQM with Audio Capturing Unit (ACU) In this AQM configuration.1.Chapter 37. Up to four mobile devices.0 405 . TEMS Investigation. 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.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. NT12-7002 ver 1. which call each other in pairs. AQM with Audio Capturing Unit (ACU) 37. are connected to an Audio Capturing Unit (ACU) which relays the audio to the PC.

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

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

so they are not populated in this mobile-to-mobile setup. 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.2. 37. Please note. chapter 5. 37. Presentation of AQM Data Information Elements All computed AQM data is available as information elements. The same family of information elements is used as for the Call Generator and MRU AQM setups. 408 . for example. so that they can be included in any presentation.1 User’s Manual AQM script for two pairs of phones. are relevant only when interacting with a PSTN.1. The “Echo” elements. however.TEMS Investigation 14. Not all AQM information elements are obtained: see the Information Elements and Events volume.

0 409 . for audio samples received by the Xperia arc. UMTS Notes on AQM Scores Obtained with Individual Phone Models For UMTS. a kind of filtering that is judged unfavorably by the AQM algorithms. causing a lowering of PESQ/POLQA scores. There is one exception. namely when the Sony Ericsson Xperia arc (Note: not arc S) acts as sender. the AQM score is not affected. – Please note again that the above does not apply to the Xperia arc S. 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). Tests consistently show markedly lower PESQ and POLQA scores with this configuration compared to other phone model pairings. 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. 37.Chapter 37. By contrast. the Huawei C8600 exhibits behavior similar to that of the Sony Ericsson Xperia arc.3. CDMA For CDMA. The described characteristics of the Xperia arc must be taken into account when evaluating AQM scores obtained with the device. NT12-7002 ver 1. The reason is believed to consist in the different filtering applied to the audio output in the Xperia arc phone. with any of the supported UMTS phones as receiver.

1 User’s Manual 38. each of which have a mobile phone connected. no auxiliary hardware components are involved. 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 . please turn to the document “VoIP Testing with TEMS Investigation”. The AQM computation is done on the PCs. found on the TEMS Investigation installation CD in the subdirectory Documents. For a comprehensive treatment of VoIP testing. In this measurement setup. AQM for VoIP Audio quality measurement can also be performed during VoIP testing.16.7. Everything about the Service Control mechanisms is covered in section 20.TEMS Investigation 14. VoIP testing is controlled by special Service Control activities. and the audio quality measurement is governed by the VoIP Voice Quality activity. including AQM.

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

The unit for VTQI is called “MOS-VTQI”. This quality is straightforwardly a function of the codecs used and the bit rate. It is updated continuously during the call. 39.1 User’s Manual 39. How this algorithm works is the subject of the present chapter. without knowledge of the original.1). The output from the VTQI algorithm is expressed as a value between 1 and 5.2. There is no overall assessment of entire calls analogous to static VSQI computed for entire streaming clips (as described in section 40.4. VTQI estimates the quality of the video call as perceived by the viewer at a moment in time. VTQI is a no-reference method which judges the quality of the received signal on its own merits. See also the document “Video Telephony Quality Measurement with VTQI” which is included on the installation CD in the subdirectory Documents. 39.TEMS Investigation 14. However. conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests.1. since the radio bearer currently used in UMTS for video 412 . • 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. General Properties of VTQI Like SQI (chapter 34). 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. 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.

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

2. The “clean” quality has been computed in advance for the codecs listed in section 40.1. See also the document “Video Streaming Quality Measurement with VSQI” which is included on the installation CD in the subdirectory Documents.4. This chapter takes a look the VSQI algorithm. 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. 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. 40.TEMS Investigation 14. 414 . 40.1. conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests. The unit for VSQI is called “MOSVSQI”. without knowledge of the original. This quality is straightforwardly a function of the video and audio codecs used. and their bit rates.1 User’s Manual 40. The information actually used by the VSQI algorithm is the video codec type and the total (video + audio) bit rate. Compare chapter 41 on MTQI. General Properties of VSQI Like SQI (chapter 34). The quality of the encoded (compressed) signal prior to transmission. The output from the VSQI algorithm is expressed as a value between 1 and 5. VSQI is a no-reference method which judges the quality of the received signal on its own merits. What VSQI Is Based On The VSQI score is based on the following non-perceptual input: 1.

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

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

VSQI recovers reasonably quickly. the more the user loses patience. but the longer the buffering drags on.Chapter 40. After the replay has recommenced.0 417 . If rebuffering occurs. VSQI captures the latter by making the slope of the curve steeper for each new rebuffering event. NT12-7002 ver 1. i. the “ceiling” in the graph. In this example the packet loss is assumed to be constant so that the influence of buffering can be clearly discerned. The best achievable quality. especially if repeated. VSQI deteriorates rapidly. the perceived quality picks up again and soon approaches the highest achievable level. Rebuffering events are much less tolerated by viewers than initial buffering. is dependent on the codec/bit rate combination but is also affected by the amount of packet loss. but not infrequently from a rock bottom level. 4. 1.e. The user tolerates (and might even expect) a certain amount of initial delay. 2. 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. 3. Once the replay gets going.

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). Buffering with skipping means that frames are skipped in connection with buffering. MPEG4 Supported video formats: QCIF. Supported video codecs: H.TEMS Investigation 14.263. REAL. no skipping means that every frame is replayed. MTQI does not include an assessment of audio quality.1 User’s Manual 41. Unlike VSQI. H.264. The MTQI algorithm can be concisely characterized as follows. QVGA • • 418 . • 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.

towards the high end of the C/I range. Since such a scheme fails to allow for power control and DTX on the TCHs. To obtain a correct C/I estimate. By NT12-7002 ver 1. 42. It should however be noted that the C/I measure is just as useful in the context of packet-switched data services. C/I can be measured in dedicated mode. areas with inadequate quality can be identified. it may produce misleading results. if frequency hopping is used in the network. while packet-switched transmissions very clearly do benefit from every extra dB.0 419 . speech quality is not further improved. one must take into account the possible use of power control and/or discontinuous transmission (DTX). To help resolve such ambiguities. C/I Measurement (GSM) 42. particularly if EDGE is used. In the past. In fact. However. SQI (see chapter 34).1.2. C/I Measurement (GSM) This chapter explains in some detail how GSM C/I measurements are made and why they are useful.Chapter 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). it is difficult to pin down the frequencies that are affected by the degradation. TEMS Investigation offers the possibility of measuring average C/I for each of the frequencies used in a call. In this way. 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. 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. something which comes in useful in the verification and optimization of frequency plans. 42.

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

one sees that two of the four frequencies (the thick lines) have a C/I worse than 10 dB during the SQI dip. On the other hand. Such information can then be utilized in the process of optimizing the frequency plan for the area. This explains the poor speech quality. indicating poor speech quality. probably because the power of the interferer increases. identifying precisely which channels are disturbed. that is. 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). Now.0 RxLev [dB] SQI [dBQ] 421 . RxLev stays about 50 dB above –110 dBm the whole time. NT12-7002 ver 1. In fact.Chapter 42. This means that the dip in quality is not due to low signal power level. RxLev increases during the SQI dip. The upper part of the graph shows SQI and RxLev. and interestingly. looking at the C/I graph. C/I Measurement (GSM) frequency hopping with four frequencies are employed throughout. the quality problem is to do with interference rather than coverage.

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

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

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

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

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

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

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

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

click the Report button. it must be stopped first. To generate a test report.13. Meaning 430 . an HTML report can be generated summarizing the results obtained so far. Timeslot not included in test. and select an output location for the HTML file. Timeslots are marked with one of the following: Timeslot Data OK FAIL TESTING – Timeslot accepted.9. (If the test is executing. Timeslot rejected. The error condition is also indicated in the leftmost column by the symbol .10.TEMS Investigation 14. Status values are as in the GSM Channel Verification window. the used MAIO and HSN is indicated for that test case. See section 43. see section 43. Test of timeslot not yet completed. Creating Test Reports At any stage of execution of a test.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.) 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. In case of call setup failure. 43.

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

TEMS Investigation 14. lock on BCCH has failed). and no timeslots marked green or red (typically occurs when the chosen TCH is in fact not used where assumed). Ten consecutive calls made where the call setup procedure could not be concluded successfully.e. Timeout MS not connected 432 . Phone not activated at start of measurement. lock on BCCH has broken down).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.e. • Invalid TCH Test case attempted 10 times in a row without the right TCH being allocated. Three idle mode reports from wrong cell or two no service reports received while trying to lock on BCCH (i.

0 433 . Keyboard Shortcuts A.2.Appendix A. Drive Testing Shortcuts Function Shortcut F2 Ctrl + F2 F5 F6 Activate all Deactivate all Insert filemark Start recording NT12-7002 ver 1.1. 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. Keyboard Shortcuts Appendix A.

Shortcuts for Active Window Function Shortcut Ctrl + P Print window Status Window. Line Chart.TEMS Investigation 14.3. 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 .4. Logfile Load Shortcuts Function Shortcut Shift + F10 Ctrl + F10 Open logfile Stop logfile load A.1 User’s Manual Function Stop recording Shortcut Ctrl + F6 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. Some route sample must already be selected.Appendix A. 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.0 435 .

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

aex .cel .pex .Appendix B.tex .stm .eth . File Types in TEMS Investigation Appendix B. File Types in TEMS Investigation These TEMS-specific file types are used by TEMS Investigation: Extension .tdc .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.log .mex .map .svt .evt .lch .config .bch .0 437 .fmt .mw .rpt .

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

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

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

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

1 User’s Manual 442 .TEMS Investigation 14.

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.0 443 . 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.e.Index Index A access class control. 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.

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 .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. 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. 105 arguments of information elements 6 AT activity in scripts 236 AT commands.TEMS Investigation 14. 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.

291. 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.0 445 . presentation of (WCDMA) 158 BLER target control (WCDMA). 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.

301 audio indications for 297 446 .TEMS Investigation 14. 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. 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.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.0 versions 439 equipment properties 277 Ericsson Fixed Wireless Terminals plugging in 47 Ethereal 98. 290. comparison with pre-12.

setting up 290 external equipment 4 activating in TEMS Investigation 46. 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. 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. 184.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. 192. 177. 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. 387 GeoSet 357 constructing from map files 357 GeoSet Manager 385 layer control 386 map projections 386 Getting Started Manual.0 447 . 158.

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 .TEMS Investigation 14.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.

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 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. 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. 433 KPIs (Key Performance Indicators) 213.0 449 .

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 .TEMS Investigation 14.

360 zooming 384 Marconi Planet 98. 381 adding presentation layers 381 control of 382 map layer 357 presentation layers 357.0 451 . 34 merging uplink AQM data into logfiles 110 NT12-7002 ver 1. 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.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. 106 MDM 106 export in MDM format 98 loading MDM files in TEMS Investigation 95 Mentum CellPlanner 42 menu bar 28. returning to 383 right-hand pane 378 scale bar 383 setting projection for 384 statistics 380 toolbar 384 viewing entire layer 384 MapInfo 98. 361 Legend tab 381 previous view.

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. 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 .TEMS Investigation 14.

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.Index network scanning (WCDMA scanning mode) 164 presentation 166 setting up 165 Network Search window (WCDMA) 166 Nokia phones.

TEMS Investigation 14. 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.

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. 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. 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. 144 detection of 51 LTE scanning with 167 plugging in 47 WCDMA pilot scanning with 150 routes 6 RRC WCDMA capability control.Index Rohde & Schwarz scanners 139.0 455 .

GSM 139 BSIC decoding in RSSI Scanning mode 140. 178. LTE 167 enhanced power scanning 180 LTE signal scanning 168 presentation 176. 167 RSSI scanning 140 spectrum analysis 143 System Information Decoding 142 scanning. 167 methods 139. TD-SCDMA 182 general settings 182 methods 182 of pilots 183 presentation 184.TEMS Investigation 14. 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 .1 User’s Manual spectrum analysis 195 Strongest Scanned PN Bar Chart 192 scanning. 141 C/I measurements 141 device capabilities 139. 180. 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.

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 .

TEMS Investigation 14. 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 . 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.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.

properties of CAS Access Class 280 CAS Lock on PLMN 280 NT12-7002 ver 1.Index Terminate activity 230.0 459 . 240 UDP activity 254 UE control 231 validating 232 Video activities 264 Video Dial activity 264 Voice activities 266 voice. 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. 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.

TEMS Investigation 14.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. 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. 33 460 . 48 statistics presentation in Map window 380 status bar 28. 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.

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.0 461 . 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 versions 439 quick guide to 26 user modes 29 user-assisted detection of external devices 53 user-defined events 290 V video calls.TEMS Investigation 14. 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 . 414 evaluating performance of 326 how to test 324 troubleshooting 326 WAP-based 265 video telephony 412 View menu 34 voice calls.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. dialing manually 77 Video Dial activity in scripts 264 Video Monitor 325 properties of 325 video streaming 324.

0 21 what was new in TEMS Investigation 13. presenting on map 366 WiMAX scanning 197 Window menu 34 Windows 7 233 Windows Vista 233 Wireshark 98. 30 opening from Command Prompt 31 predefined 31 NT12-7002 ver 1.Index WCDMA scanning 144 what was new in TEMS Investigation 13.0 463 . 106 Worksheet menu 34 worksheets 27.1 16 what was new in TEMS Investigation 14. 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.

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