TEMS Investigation 14.1 User's Manual
Comments
Description
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 . . . . . . . . . . . DRT Scanners .1 User’s Manual 13. . . . . . . Technical Data on Scanning Devices . . . . .2. . . 13. 15. .3. . . . . . Setup of Pilot Scan: Anritsu . . . . . . . . . . . . .5. . .2. . . . . . .1. . . .2. . . . Presentation: General .4. . . Presentation: Synch Channel Data Window . . . . PCTel Scanners. . . . . Setup of Pilot Scan: PCTel . . . . . .2. . . . . . . .4. . . . . . . Rohde & Schwarz TSMW . 14. . . . . . . .9. . . . . . . . . . . . . . 15. . . . . . . . .2. . . . . . . . . . . . . . . .2. . . 13. . . . . . . . . . . . . . Presenting Scan Data . . . . . . . . Setup of RSSI Scan: PCTel SeeGull . 15. . . . . . .2. . . . . . WCDMA Scanning 144 144 146 146 146 148 150 151 152 153 153 154 157 15. .5. . . . . . . . . . .2. . . . 13. .1. . . . . . . . . . . . . 15. . 13. . . Scripted Scanning. . . . . . . . 15. . . . . . . .7. . . .2. . . . . . . . . . .5. .4. . . . . . . . . . . . 13. . . . .1. . . . . . . . . . . . Presentation: “CPICH Scan” Bar Charts . . . . . . . . . Manual Scanning .2. . SRU . . . Presentation: “CPICH Scan” Line Charts. . . . .1. . . . Setup of RSSI Scan: General Settings .8. . . . . . .2. 14. 15. . . . . . . . . . . . . . . . . . . . . . . . . . . 13. . . 13. .3. . . . . . . . . . . . 13. . . . . . . . . . . . . . . . . . . . . Setup of Pilot Scan: Sony Ericsson. . . . . 15. . . . . . . . . . 14. . . . .5. . . GSM Scanning 139 139 140 140 140 141 142 143 143 14. Performing a Scan Manually . . . . . . . .2. . . Setup of Pilot Scan: Rohde & Schwarz TSMW . Sony Ericsson Phones and SRUs . . . . .6. . SRU . . . . Spectrum Analysis . . . . . . . . . . . .2. . . Setup of RSSI Scan: Sony Ericsson. 14. . .2. . 14. . . . .2. . . . . .1. . . . .5. . . .2. . . . . . . 14. . . . . . . . . 13. . Presentation: “CPICH Data” Status Windows . . viii . . . . . .2. . 13. . . . .10. . . . . . 15. . . . . . . . . . . . . . . 14. . . . . . . . . RSSI Scanning . . . . . . . . . . . . . .2. . . . . . . . . . . . . . Setup of Pilot Scan: General . . .2. . Notes on GPS Units in Scanners . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . .TEMS Investigation 14.2.5. . . . . . 13. . . . . . . .2. . . . . . . Setting Up a Scan Manually. . . . . . . . . Scanning Methods and Capabilities . . . . . . . 15. . . . . . .1. . . Notes on Scanner Multitasking . . . . . . . . . . . Presentation of RSSI Scanning . . . . . .4. . . . . . . . . . . . . . . . . . . . . 13. . . . . . . . . . 14. . Scanning Methods and Capabilities . Setup of RSSI Scan: Rohde & Schwarz TSMW . . . . . . . . . . . .2. Recording Scan Data Manually .5. . Scanning: General 134 134 135 135 135 136 136 136 137 137 137 137 138 138 13. . . . . . . . . . . .6. . . . . . . . . . . .3. . . . . . .3. . . . . 15. . . . . . . 15. . . . . . . . . . . . . . .1. . .2. . . . 15. . . . .2. . . . .3. . . . Pilot Scanning (with SCH Scanning). . . . . . . .2. . . . . 2. 161 15. . . . . . 177 NT12-7002 ver 1. . . . . . . . . . . . . . . . . 160 15. . . . . . . . . . . . . . . . . . . .2. .5. . . . . .13. . . . . . . . . .0 ix . . . . Setup of LTE Signal Scan: PCTel . . 164 15. . . . . . . . . 165 15. . . . . . . . . . .2. . . .2. . . . . . . . . .1. . . . . 169 16. . . . . . . . . . . . . .4. . 159 15. . 160 15. . . 167 16.5. . Context Settings . . . .2. . . .1. .1. . . .4. . . . . .2. . .4. . . . 161 15. . . Setup of LTE Signal Scan: Rohde & Schwarz TSMW . . . . . . . . .2. . . Spectrum Analysis. . . 169 16. . . . . . . Setup of Spectrum Analysis Scan . . . . . . .13. . . . . .1. . . . . . .2. . . . . . . . . . . . Setup of Network Scan. . .1. 165 15. 175 16. . 176 16. . . . .1. . . .2. . . . . .6. . . . .Contents 15.1. . . . Sorting of Scrambling Codes. .2. . . . . . . 158 15. . .3.1. . . . . . . . . . . Setup of SCH Timeslot Scan . . . . . . . 177 16. . . . . . . . . . . . . . . . Presentation of LTE Signal Scan . . Presentation: Network Search Window . . . . . . . . . . . . . . . 161 15. . . . .2. . . . .1. . . . . . . . . . . . . . . . . . . .1. . . Setup of LTE Signal Scan: Andrew . . . . . . . . .1. . . . . . . . . . . . . . Network Scanning . . . 162 15. LTE Scanning 167 16. . . .2. 2. . . . . . . . . . . . Presentation: “Finger Info” Status Windows. . . . . . . . . . .7. . . . . . 168 16. . . 158 15. . Context Settings . . . . . .6. . . . .5. . . . 164 15. . . . . . . Presentation: BCH Scanning . General Settings . . . . .5. . . . . . .2. 163 15. LTE Signal Scanning. . . . .1. . . . . . 3”) . .4. . . .6. . . . 166 16. . 163 15. .1. . . .2. . . . . . Customizing the Presentation . . .4. . . . . . . . . . . . . . . . . . . . Context Settings . . . . .1. . . Sorting of Cells . Presentation: SCH Timeslot Scan Bar Chart . . . Setup of LTE Signal Scan: DRT. . . . . . . . . . . . . . . . .2. . . . . .2. . . . . .2. . . . .13.1. . . . . . . . . . .1. . . . . . . . . . .2. . . . . .6. . . . . . . .6. . . . Presentation: Spectrum Analysis Bar Charts .1. . . . . . . Setup of LTE Signal Scan: General . . . . . 158 15. General Settings . . .4. 163 15. . . .2. . .3. . . . Setup of RSSI Scan . . . . 165 15. . . . . . RSSI Scanning . . Context Settings . . .2. . . . . . . . . . . . . . . . .8. . .12. . . . . . . 159 15. . . . .11. .6. General Settings . . . . .2. . .3. 172 16. . . .1. . .3. . . .2. . . . . . . . . . .1. . Scanning Methods and Capabilities . . . . . . .3. . . . . . . . . . . . . 162 15. . . . . . . . . . . . . . . . . . .5. . . . . . . . . . 168 16. . . . . . . . . . . . . . . . . . . . . SCH Timeslot Scanning . . . . . 159 15. . . . . . . . .8. . . . . . . .1. . . . . . . . . . . Presenting Scrambling Codes from Multiple UARFCNs .2. .6. .2. . Customizing the Presentation . . . . . . . . . . . . . . . . . . . . UARFCN Ranges (“Interval 1. . . . Presentation: RSSI Scan Bar Chart . . . . . 165 15. . . . . . . . .3. . . . 174 16.5. . . . . . . .3. . . . . . . . . 159 15.1. . . . . . . . . . . . . . . . . . . . . .2. . . 163 15. . Setup of LTE Signal Scan: Transcom . . . . . . . . . . . . . . . . . . . . . . . . . . General Settings . . . . . . . . . . . . . . . . 158 15. . . . . . . . . 16.5. .3. . . . . . . . . . . .4.3. 18. . . . . . 16. . .1 User’s Manual 16. .4. . . . . . . . . General Scan Settings . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . Pilot Scanning . . . .1. 16.2. 17. . . . . . . . . . General Scan Settings . . . .3. . . . . . . . . Customizing the Presentation . . . 16. . . . 177 177 178 178 178 178 178 178 179 179 179 179 180 180 180 180 181 17. Sorting of Cells . .1. . . . . . 18. . . . . . . .5. . . . . . . . . .3. . x . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . Presentation: Strongest Scanned PN Bar Chart . . . .4.2. . . . . .3. . . . . . . . . . . . . . . . . . . . . . .1. . . . Presentation of RSSI Scan . . . . . . . . . . . . . . .4. . . . . . .5. . . . . . .4. . CDMA Scanning 186 186 187 187 187 188 192 192 192 192 18. . . . . . . . . . . . 18. . . . . . . . . .2. . . . . . . . . . . . . . . Setup of Enhanced Power Scan . . . .3.3. . . . . 16. . 18. . . Scanning Methods . . . . . . . Setup of Spectrum Scan: Transcom . . . . . . Presentation of Enhanced Power Scan . . . . . . . . . . . . . . . . . . . . . . . . Setup of RSSI Scan: Transcom . . . Spectrum Scan Presentation . . . . . . . . . . . . . .3. . . . . . . .4. . . . . . . . . 17. . . . . . . . . . . . . . . . 16. 17. . . .3. . . . . . .1. . . . . . . . . . . . Setup of Spectrum Scan: DRT. . . . 16. . . . . . . . . . . . . . . . .2. .4. 16. . . . . 17. .1. . . . . . . . . . Sorting of Pilots . . . . . . . . . . 18. . . . . . . . . . . . . . . . . . .2. . . . . . . .3. . . . .3. . . Presentation: “PN Scan” Bar Charts . . . . . . . . . . Pilot Scanning . . . . . . . . . . . . . . .3. . . . 18. . . . . . . . . . Presentation of RSSI Scan . . . . . . . . . . . . . .4. . 16. 16. . . . . . .4. . . . . Setup of Pilot Scan . .4. . . . . . . . . . .2. .4. . . . . RSSI Scanning . . . . . . . . . . . . .TEMS Investigation 14. . . . . .6. . . . . . . . 17. . . . . . . . . . . . . . . . .3. . . . . . . . . . 16. . . . . . . . . . . . . . . . . . . . . Setup of RSSI Scan: General .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup of Spectrum Scan: PCTel . . . . . .4. . . . . . . . . . . . . . . . . . . . Setup of RSSI Scan . . . .1. . . . . . . Setup of Pilot Scan: Andrew . . . . . . . 16. . . . . .3. . . . . . . . . 18. . . . . . . . . . . . . . .3. . . . . . . . . 18. . . . .1. . . . . . . . . . . . . . . . . . . .5. . . . . . . . . . 18. .1. . . . . 16. . RSSI Scanning . . . . . . . .3. . . . .4.1. . . . . . Setup of Spectrum Scan: Andrew . . . . . .5. .5. . . 16.2.3. . . . .5. Setup of RSSI Scan: PCTel . . Scanning Methods . . . . . . . . . . . . . . . . . . . . . . . . . 16. . 17. . . . Presentation of Pilot Scan .3. . Setup of Pilot Scan: PCTel . . . Spectrum Scanning. . . . . .3. . . . . 16. TD-SCDMA Scanning 182 182 182 183 183 184 184 185 185 185 17. . . .3. . Setup of Enhanced Power Scan: General . . . . . . . . . . 17. . . . Setup of Spectrum Scan: General . . . Enhanced Power Scanning. . 17. . . . Setup of RSSI Scan: DRT . .1. . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . Setting Up a Network Connection . . . . . . . . . . .5.1. . . . . . . . . . . . 195 18. . . . . . Setup of Spectrum Analysis Scan . . . . . . . . . . . . 204 20. . . . . . . . . . 209 20. . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . 206 20. . . . . . . . .2. .1. . . . . . . . . Basics of Creating Scripts (with Voice) . .1. . . . . . . 210 20.2. . . . . . . . . . . . . . . Interference Offset. . . . . . . . . . Capabilities of Devices . . . .Contents 18. . . . . . . . General Settings . . . . . . . . . . . . . . . . . . WiMAX Scanning 197 19. .4. . . .6. . . . 194 18. . . . . . . . . . . . . . . . . . . . . . . .3. . . . . .1. Setup of Preamble Scan . . . . . . . 197 19. . . . . . . Presentation: RSSI Scan Bar Chart . . 201 19.5.1. . 212 20. . .6. . . . . . . . . . Setting Up a Data Service Activity. . . . . General Scan Settings . .1. . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. .6. . . . . . . . . . . 195 18. Context Settings . 194 18. .1. . . . . . . . . . . . 201 19. . .4. . . . . . . . . . . .7. . . . . . . . . . . . . . . . . . . . Narrowband Interference Scanning. . . . . . 193 18. . . 194 18. 194 18. . Context Settings . . . . 201 19. . . . General Settings . . . . . . .10. . . . . . . . . . . . . . 201 19. . . . . . . . . Preamble Scanning . . . . . . . . . 195 18. .3. . . . . . 193 18. . . . . . . . . . .2. . . . . . . . . . 193 18. . . . . . . . . . . . . . . . . The Service Control Designer . . . . . . . . . 194 18. .3. . . . . . . . . Presentation of Spectrum Analysis Scan . . . . 201 20. . . . . . . Sequences . 204 20. . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . 196 19. . . . .5. .1.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . . . . . Setup of Narrowband Interference Scan . . . . . . . .6. . . . . Stand-alone PS Attach and Detach. .2. . . . . . . . . .4. Service Control 203 20. . . . . . Supported Services by Cellular Technology . . . Presentation . . . . . . . . . . . . . .8. . . . Scanning Methods. .1. . . . . . . . 194 18. .6. . . . . . . . . . 214 NT12-7002 ver 1. . . . 213 20. . .1. . . . . . . . .5. . . . . . . . . . . . . . . . . . .3. . . .1.1. Spectrum Analysis. . . . . . . . . . . . . . . . . .5. Introduction to Service Control . . . .5. . . . . . . . . . . . . . .6. . . . 196 18. . . . . . . . . . . . . . . . .1. .1. . . . . . . Presentation: Narrowband Interference Scan Bar Chart .10. . . . . . . . . . . . . . . . Snippets . 198 19. . . . . . . . . . . . 198 19. . . . . . . . . . . . . . . . . . . . . . . 197 19. . . . .9. . . . . . . .0 xi . . . . . . . . . . . . . . RSSI Scanning . 214 20. . . . . . . . . Workflow Control Structures .1. . . . . .2. . . . . . . . . . . . 203 20. . . Setup of RSSI Scan . . . . . . . . . . . Setup of RSSI Scan . .6. . RSSI Scanning . . . . . . . 203 20. . . . . . . . . . . . . . Spectrum Analysis. . . . . . . .5. . . . .5.4. . . . . . . . . . . . . . . . . . . . . . . . . . Setup of Spectrum Analysis Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16. . . . . . . . . . . . . . . . .3.15. . Running Scripts from the Service Control Monitor . . . . . . . . . . . . . . . . . . . . . . . .16. . 20. . . . .10. 20. . . . . .14. . . . . . . .16. . .1. Activity Properties That Control Execution . .6. Wait For with Periodic Events . . . . .10. . . . . . . . . . . . . . . . . . . .16. . . . . .5. . . .10. . Presentation of Data Service Testing .10. . . Example 2: Concurrent Activities on Different Devices .10. . . .2. . Wait For . . . 20. 20. . 20. . . . . . . . . . . . . . UE Control Functionality . . . . . . . . . . . . . . . . . . 20. . . . . . 20. . . . . . . . . . . . . .16. . . . . . . . . . 20. .4. . . .1. . .15. . . . .10. . Control Activities . . . . . . Notes on Script-controlled Logfile Recording . .1. .1. Validating Scripts . . . 20. 20.4. . . . . . . . . . . . . . . . . 20. .15. . Radio Access Technology Lock . . . . .1. . . .15. . . . . If–Else Constructs .9. . . While Loops . . . . . . . . . . 20. .3. . . . . . .15. . . . . . . . . . . . . . 20. . 20. . . . . . . . . . . . . . . . Waiting For a Scheduled Point in Time. . . . . . . .10. .1. .4. . . . .15. . .3. . . . . . . . . . . Stop Recording . . . . . . . AT . . . 20. . . Monitoring Equipment Status . . . Editing Workflows and Script Settings . . . . . . . . . . . 20. . . . . . . . . . . . . . . . . . . . . . . . . . Filemark . . . . . . . . . . 20. . . . . . . . . . Activities (Reference Section). . . . . . 20. . .10. . .1. . . . . .5. . . . . .15. . . . . . . .16. . . . . . . . . .TEMS Investigation 14. . . . . . .11. . 20. . . . . . . . . .10. . . . . . Viewing Statistics on Script Execution . . . . . . . Windows 7/Windows Vista and IPv6. 20. . . Example 3: Concurrent Activities on the Same Device . . . . . . . . . . . .1. . . . . . . Deactivate .1. . . . . . . . . . . . . . . . . . . . . . . 20.4. . . . .6. . 20. . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . .1. . . .3. . . . .3. . . . . . . . . . . Waiting For a Given Outcome of an Activity . 20. . Preparations. . . . . . . . . . . . . . . . . . Running Scripts from the Service Control Designer . . . .6. . . . . . . . Running Scripts. . . . . . . . Activate . . . . . . . . . . . . .15. . . . . Example 1: CS Voice/Video – Caller and Receiver .2. . . . . . . .6. .8. . . . . . . .4. . . . . . . . . . . . . . . . . . . Wait . . . . Start Recording . . . . . . 20.15. . .4. . .16. 20. Parallel Activities . . . . . . . .12. . . . . . . .1. . . . . . . 20. . . . . . . . . . . . . . . 20.1. . . . . .2. . .3. . . . . . . . 20. . .7. . . . . .1.2.1.16. 20. 20. . . . . . .10. . . . . . . 20. . . . . . 20. . . . . . . . . . . . . . . Suppressing Parts of a Script . . . . . . . 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 . . . .2. . .16. . . . . Terminate. . . . . . . . . . . 20. . . . . . . . . . . . . . . . .10. . . . . .15. . . . . .6. . 20. . . .10. . . . . . .13. . . . . . . . . . . . . .1. . Band Lock . . . . . . . . . . . .1. . . . . . . . . . . . . . 20. . . . . . . . . . . . . . . . . . . . . . . . . . . 20. .16.2. . . . . . .16. . . . . . . . . . . . . . . . . . . 20.5. .8. . . .1 User’s Manual 20. . . Run Script . . . .7. . . . . . . . . General Aspects of Script Execution . . . . . . . .6. .10. . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . .16. . . . . . . . . . . . . . . . . . . . . . . . .16. . . . . . . . . . . . .2. . . . . . 264 20. .16. . . . . . .6. . . . . . . . .4. . . . . . .16. . . . . . .16. . Stop IP Sniffing . . . . . . . . . . . .2.5. 238 20. . . . . . . . . . . . . . . .16. . . . . . . . . . . . . . . .16. .2. . . . . . . . . .16. .16. . . . . . . WAP Get . . . SMS Receive. . . . . . . . . . . . . . . 240 20. . Answer . . . . . . .16. . . . . .3. . .16. .16. . . . 258 20. . Sequence . 243 20. . . . . . . . .16. . . . . . . . . While . . . . PS Attach . .7. .16. . . . .16. . . . . .5. . .16. . . . . . . . . . . . . . Control Flow Activities . . .3.4. .16. IP Activities. . . . . . . . .4. . . . . . . . . . . 240 20. . . 243 20. . .4. . .0 xiii .3. . . .16. . . . Network Connect.2. . . . . . . . . . . . 247 20. . . . . . .1. . .4.15.4. . . .16. . . . . . . . . . . . . . . FTP Download. . . . Ping . . . . . . . .3. . . . . . . . . . . . . . . . . . 239 20. . .13.4. . . . . Streaming . . . . . . . . . HTTP Get . . . . . . . . . . . . . . E-mail Send. . . . . . . . . . Video Activities . . .3. . . .4. . . . . .2. . . . . .7. . . . . . . . . . . .5. 254 20. . . . . . . . . . .16. .16. . 262 20.2. . . .16. . . . . MMS Send. . . . . . . . . . .6. . . . . . . . . . . . .16. . . . . . . . . . . 248 20. . . 248 20. . . . . . . .16. . . . 261 20. . .3. . . . . . PS Detach . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . 238 20. . 262 20. . . . . . . . . . .3. . .8. . . . . . . . . . . .6. . .9. . . .Contents 20. . . . . . . . . .16. . . . . . . . . . . . . . . . . .5. . . . . . . 259 20. . . . . . . . . . . . . . . . . . SIP Unregister . . . . . . . . .14. 254 20. . . .1.8. . . 248 20. . . . .3.4.5. . . . . . . . . . . . . .16. . . . . . . 240 20. . .16. . . . . . . Predefined Snippets for IP . 264 20. . . . . . . . .2. . . .2. . . .12. . . . . . . UDP. . . .2. . . . . .16. . . Predefined Snippets for Scanning. . 249 20. . . . . . . . . . . . . . .3. . . . . . .3. . . . SMS Send . Predefined Snippets for Messaging . . . . . . . . . . . MMS Receive . . E-mail Receive . . . . . . . . .3. . .6. . .2.2. . . . Run Script . . . . . . . . . . . . . . . Messaging Activities. . . . . . . . .6.11. . . . . . . . . . . . .16. . . . . . . . . . . . . . 265 NT12-7002 ver 1. . . . . . . . . . . . . . . . 256 20. . 249 20. . . . . 240 20. .2. . . . . . . . . 253 20. . . . Start IP Sniffing . . . . . . . . . . . .3. . . . . .16. . Network Bandwidth (Iperf Testing) . . . . . . . . . . . . . . . . . . . . If–Else . . . .16. . . . .6. . .3. . . 250 20. . . . . .16. . . . . . 240 20. . . 262 20. . . 264 20. . . . . . . . 252 20. . . . . . . . . . . . Wait For. . . . . . . . . . .3.1. . . . 239 20. . . . . .2. .3. . . Parallel . . . . 259 20. . 260 20. . . . . . . . . . . . . .6. . . . .4.16. . . . . . .5. . . . . . . . . . . . . . .3. . . . . . . . . . . . . Video Dial . . . . Wait . . . . .3. . . . . . . . .16. . . . . .16. . . . . . .16.16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP Upload . . . . . . . . . .3. . . . . . . .16. . . . . . . . . 247 20. . . . .7. . .16. . . . . . . . . . . . . Terminate . . . .16. . . . 258 20. . . . . . . . .4. . . . . . . . . .3. . . . . . . 247 20. . Scan Activities . .4. . . . . . . . . . . . . 264 20. . .6. . 264 20. . . . 264 20. . . . . . .1. . . . .3. . . . WAP Streaming.6. 258 20. . Network Disconnect . .16. . . . . . . . . . . . .1. . . . . . . . . . . . . . . . Hang Up . . . . . . . . . . .3. . . . . . . . . SIP Register . .16. . . . . . . .16. . . .7. . . . . . . . . . . . . . . . . . .18.2. . .2. . . . AQM Measurement . . . . . CAS Speech Codec . . . . . . . Configuration Sets . . . . . . . Predefined Snippets for Voice. . . . . . . . . GSM Cell Selection . .7. . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dial . . . 267 20. . .2. . . . . . . . . . . . . .10. . . . VoIP Answer . . .5. . . 271 20. . . . . .16. . . . . . . . . . . . . . . . Device Properties 277 277 279 279 279 280 280 280 281 282 282 283 21. . . . 268 20. CAS Access Class .1. . . . Zooming the Workflow Pane . . . . How to Set Up VoIP Testing . .1. . . .19. . . . .3.2. . .2. . . . . . . . . 21. .3. .1. . . . .2. . . .2. . . . . .6.18. 270 20. .18. . . . . . . . . . . . . . .3. . Properties of ST-Ericsson Chipset Based Phones . . . . . . . . . . . . . Tutorial on Porting Scripts between PCs . . .16. . . . . . . . VoIP Hang Up . . . . . . . . . . . . . . . . . Hang Up . . . .7. . . . 274 20. . . . VoIP Dial . . 275 21. .2. .1. . Saving Workflow as Image . . . . . 21. . . . . . . . .7. . . Predefined Snippets for Video . . . . . . . . . . . . . . . . . . Activity Section. . . . . . . . 270 20. . . 21. . . . . . . . .16. . .2. 274 20. . . . . . . . . 268 20. . . . . . . . . . .2.6. . Saving and Loading Scripts .2. . . . . . .7. . . . . . General Activity Properties . .19. . . . . .2.2. . .7.1 User’s Manual 20. . . . Answer . . . . .2. . . . . . . . . . .16. . . . . . . . . 21. . . . . . . .7. . . . . . . . 269 20. . . .18. . . . . . . Exporting Configuration Sets . . . . . . . . . . . . .17. . . . . . . Common Controls . . .TEMS Investigation 14. . . . . . 266 20. . . Voice Activities.17. . . . . 273 20.9. . . .2. . . . . . Deleting Configuration Sets .2. Failure Handling Section . . . . . . . . . Importing Configuration Sets. . . . . .2. GSM EDGE Capability .16. . . . .16. .7. . . . . . .2. . . . . . . . . . . . . 21. . . . . . .20. . . . .7. . . . . . .18. . . . . . 267 20. . . . 21. . . 270 20. . 21. . . . 275 20. . . . . . GSM Adjacent Scan .19. . . . . . . . .1. . . . . . . . . . . . . . CAS Lock on PLMN . 266 20. . . . . . . . . . . . . . . 272 20. . . . . . . . . . Activity Filter. . . . . . . . . . 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further Functionality in the Service Control Designer Window . . . . . . . 273 20. . . .6. . . 275 20. .2.16. . . . . . . . 266 20.2. . . . . . . . .2. . 275 20. . . . . . . . . . Overview of Properties by Device. . . . . 268 20. . . .3. . . . . . .7. . . xiv .7.1. . . . . . . . . . . . 21. . . . . . . . . . VoIP Voice Quality . . .5. . .20. .20. . 21. .18. . .7. GSM Barred Cells . . . .4. . . . 271 20.2. 269 20. . . . . . . . .2. . . . . Descriptions of Configuration Sets. 268 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . .20. . .16. . . . . . . . . . . . . . . . . . . . .1. . . . . . .17. . . . . . . . . . . . . . .8. . . . . . . . . . . . . . . .2. . 266 20. Context Menu in Workflow Pane . . . . . . . .2. . .2.16. . . . . . . . . . . . . . . . . . . . . . . . .16. . . Managing Configuration Sets.16. . . .6. . .2. . . . .7. . . . Extended Reports . . . . . . . .4. . . . 271 20. . . . . . . .1. . . . . . . . . . . . . . . 272 20. . . . . . . .16. . . . . . . . . . . . . . . . WCDMA BLER Target. . .5. . . . . . . . . . 288 21.Contents 21. . . . .5. . . . .3. . . 299 22. . . Example of User-defined Event . . . . . . . . .5. . Muting All Audio Indications . .2. .5. 297 22. . . .3. . . . . . . . . . .5. . . . .2. . . . . . 292 22. . . . . . . . .2.3. . .2. . . . .8. . . Setting Up a User-defined Event. . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . .2. . . . . . . . . . . . . . . . 299 22. . . . . . . . . . . . . . . WCDMA Cell Selection . . . . . . .2. .3. . . . . . . .5. . . . . . Adding an Information Element Criterion to the Event Expression. . . . . . . .7. . . . .2. . . . . .2. . Properties of Nokia Phones (NTM3) . . . . . . .3. . .2. . . . . . . 293 22. . . . . . . . . .1.4. .5. 284 21. .2. .2. Deleting Audio Indications . . . . . 289 22. . . . . . . .3. . . 285 21. Editing Audio Indications . . Properties of Qualcomm Chipset Based Devices . . . . .2. . . . . . . . 287 21. . . . . . 293 22. . . 286 21. 288 21. . . . 287 21. . . 293 22. . . Adding a Layer 3 Message to the Event Expression . .2. .0 xv . . . . . . . . . GSM Tx Power . . . . . . . . . . . . . . 299 22. . . . . . . . . . . . . . . . . Sector Lock Control (WCDMA) . . . . . . . . . . . 300 NT12-7002 ver 1. . . . . GSM Cell Barring Control. . . . . . . . . WCDMA RRC Radio Capability . . .2. . . . . . . . . . . . . . . .1. 283 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . .9. . . . . . . . . . . . . . .3. . Predefined and User-defined Events . . Presentation of Events . . . . 285 21.2. . . . 295 22. . . . . .3. . . . . . Deleting User-defined Events. . . .7. . . . . .3. . . . . . . . . . . . . . . . . . . . . Adding an Operator/Delimiter to the Event Expression . . . . . 299 22.1.2. . . . . 290 22. . . . . . . .6. . . 299 22. 284 21. . . .3. . . .4. . . 290 22. . .6. . .2. Audio Indications for Events . . . . . . . . . . . . . . . . . . . .5.11. . . 293 22. .6. . . . . . . . . . . . . Properties of GPS Units . . . Properties of Samsung LTE Modems . . . . . . Adding an Event to the Event Expression . . . . . . . . . . . . . . . GSM Handover . . . . . . Deactivating Audio Indications .4. . .3. Generating Cell Whitelist Events. . . .4. Events 290 22. . . . 287 21. 287 21. . Activating Audio Indications . . . . . . . . Adding Audio Indications . . . . . . . 289 21. . 284 21. . . . . . . . . . . . . . . . . . . .5. . .1. . . . . . . . . . . Layer 3 Messages . . . .10. . .3. . Properties Specific to Sony Ericsson Xperia arc S. . . . . 292 22. . . . . . Channel Lock Control (GSM) . . . . . . . . . Saving and Loading Audio Indications . WCDMA Barred Cells . . . . . . . . . . 297 22.5. . . . .5.4. . . . . . . . . .2. . . . . . . . . . . .13. . . . . . . . . . .14. . . . . . . . . . . . . . . . . .12. . . . . . . . . . Editing User-defined Events. . . . .3. . . 290 22. 294 22. . . . . . . . . . . . . . .1. . . . . . . . Device Channels: MS/DC/PS . . . . . . . . . . Resetting Event Counter Windows . . . . . . . . . . 25. . . 24. . . . . . . . . TD-SCDMA Physical Channel Monitor . . . .1. . . Presentation: Basics 301 301 301 302 302 303 303 304 304 304 304 23. . . . . . . . . . . . . . . . .4. . . . .1. . . . . . Window Tabs . . Changing the Status Window Font Size . . . . . . . . . . . . . . . Types of Presentation Window . . . . . . . . . . .1. . .6. . . . . . . . . . 24. . . . . . . . . . . . . . Repeating Columns in Multiple Groups .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26. . . . . . . . . General Tab . . . . . .2. . Changing Message Window Contents and Properties . . . . . . 25. Presented Data . . . . . . . . Color Ranges . . . . . . . . . . . . . . . . . . . . 23. 24. . . Copying Window Contents . . . . . Changing Status Window Properties . . . . .1. . . . . . . . .6. . . . General Tab . . Window Properties . . . . . . .2. . . . . . 23. . 23. . . . .7. . . . . . . .4. . . . . . . . . . . . . .4. . Other Window Properties . . . . . . . . . .7. . . . .TEMS Investigation 14. . . . 24. . . . . . . . . 26. . Export/Import of Presentation Windows . . . Changing Event Counter Window Contents and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . .4. . . . . .3. . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . xvi . . . . . . . . . . . . . . . .2. .5. . . . . . . . . . . . . . . .3. . . .2. . . . . Event Counter Windows 315 315 315 316 316 316 316 25. . . . . . . . . . . . . . 23. . . . 25. 23. . . . . . . . Status Windows 305 305 305 309 312 312 313 313 314 314 24. .3. . . . . . . . . . . . . . . . . . . CDMA Finger Info . . . . . . . . .6. . . . . . . . . . . . 24. . . .1. . .5. . . . . . . . . . . . . . . . . . . . . . .1. . . . 23. . . . . . . . . . . .1 User’s Manual 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25. . . General . . 25. . . . . . . . . . .6. . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . Setting Up Status Window Contents. . 24. . . . . Export. . . . 23. . .6. . . . . 24. . . . . . . Message Windows 317 317 317 318 318 26. . . . . . . . . . . . . .3. . . . . . . . . . . . . 26. . . . . . . . . . . Non-standard Status Windows . . . . . .1. . . . . . . . . . Import. . 26. . . .1. . . . . . . .4. . . . 23. . . . . . . . . . . . . . . . . . 23. . . . . . . . . . . . . . . . Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . Window Updating and Synchronization .1. . . . . . . . . . Events Tab. . . . . . . . 25. . . . . . . . . . . . “Set Equipment Number” Function . .1. . . . . . . . . . . . . . .2. 24. . . .2. . . .7. . . . . . . . . . 24. Messages Tab . . . .1. . . . . . . . . 336 NT12-7002 ver 1. . . . . . 321 26. 320 26. . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . 324 27. . . . . . . . . . . . . . . . Exporting the Line Chart Window . . . . . Time Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 29. . .1. . . . . .1. . . 319 26. 323 27. . . . . . . . . . . . . . . . . . . . 326 27. . . . . . . . . . . . . . . . . . . .3. . .4.4. . . and Highlighting in Message Windows. . . . . . . . 331 29. . . . Search Functions . . . . . .8. The GPS Window 327 28. . . . 336 29. .4. . . . .4. . . . Message Window Synchronization . . . . . . . . . . . . . . .2. 332 29. . . . . . . . Changing GPS Window Properties . . . . .1. . . . . . . . . . .4. . . . . . . . . . . .3. . Editing General Properties of a Chart . 330 29. 326 28. . . . . . . . . . . . . . . . . . . Editing the Contents of a Chart . . . . 319 26. 329 29. Searching. . . . . . . .6. . Presentation of Discarded Messages . . .7. . . . . . . . . . . . .1. . . . . . . . 332 29. . . . . . . . . .4. .3. . . . . . .7. . . . . . . . . . . . .5. . . . . . . . . . .2. . . . . . . . . . . . . .2. . . Filtering Functions . . . . . . . . . . . . . . . . . . Filtering. . . . . . . . . . . . . . . . . 327 29. . . . .0 xvii . . . . . . . . Evaluating Video Streaming Performance . .4. . . Plain-text Message Decoding . . . . 323 26. . .8. . . . . . . 319 26. . . . . . . . .4. . . . . . . . . . . . . Deleting a Chart . .4. . . . . . . . . .7. . . 320 26. . . The Video Monitor . . 325 27. . . . . . . .1. . . . . . . . . . Video Streaming and the Video Monitor 324 27. . . . . . . . . . . Window-specific Features . . . . . . . . . . . . . . 320 26. . Line Charts 329 29. . . . . . . Properties of the Video Monitor . . . .1. . . . . . . . . .Contents 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . .4. . Contents of the Line Chart Panes . . Organization of the Line Chart Window. . 325 27. . . . . .3. . . . .2. . . . . . . . . . . . . . . . . . . How to Test Video Streaming . 322 26. . . . . Message Window Catch-up . . . . Troubleshooting Video Streaming . . . . . . . . . . . . . . . . . . . . . Mode Reports Window . . . . . . . . . . . . . Freezing a Message Window . . . .1. . . . . . . . . . . . . . .5. . . . . . . . Columns Tab . . . . . . . . . .1. . . . Changing Line Chart Contents and Properties . . 332 29. . . Highlighting Functions . 318 26.7. . . . . . . . . . . . . . . . . . . . 336 29. . 319 26.2. . . . . Presenting Data from a Different Device . . . . . . . . . . . . Adding Charts.5. . . . Positioning Bitmap and TIF Maps . . . . . . . Presentation Layers . . Data. . . . . . . . . . . . . . . . . . 31. 31. . . . . . . . . 30. . . . . . . . .2. . . . . . . . . . . . . . . . . . . . Single IE Presentation Mode. . . .2. . . . 31. . . . . . 31. . . . . . . . . . . . . 30. . . . . . 30. .5. . . . . . . .5. . . . . . . . .3. .3. . .5. . . . .1. . . . . .3. . .4. . . . . . .5. . . . . . . . . . . Presenting Data from a Different Device . . . . . . . . . 31.3. . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information . . . .1. . . . . . . . . . . . Specifying the Map Scale . Presentation Mode. Interval and Labeling .6. . .4. . .3. . . . Organization of the Bar Chart Window . . .4. . . . . . . . . . . . . .4. . . . . . . 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. . 31. .4. . . . .1. . . . Setting Up General Bar Chart Properties . . . 30. . . . . . . . . . . . . . . . . . . .3. . . . . . . . . Presenting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. . . . . . . .5. . .2.5. 31. . Multiple IE Components Presentation Mode. . . . .TEMS Investigation 14. . . . . Bar Charts 337 338 339 340 340 340 341 341 342 343 344 347 351 352 352 353 355 30. . . . .3.3. . . 31. . . . Presenting Data: Themes . Map Concepts. Contents of the Bar Chart Panes . . 31. . . .6.4. . . . . . . . . . . .2. . . 31.1. . . . . . . . . . .5. . . .5. .5. . . . . . . Deleting a Chart . 31. . . . . .1. . . .4. . . . .4. . . Setting the Map’s North Direction .5. . . . The Cell Color Theme . . . . .5. . . . . . . . . Presenting Pinpointing . . . . . . . . . . . .4. . . . . . . 31. . . .1. .4. . . . . Constructing a GeoSet from Map Files. . . . .2. . . 30. .3. Presenting Information Elements .5. . . . . . . . . . . . . .1. . .1 User’s Manual 30. . . . . . . .5. . . 30. . . . The Cell Line Theme. .4. . .5. . . . . . . . . . Presenting Cell Information . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . 31. . . . . . . . . . . . . . Examples of Bar Chart Presentations. . . . . . . . . Themes and Theme Types .3. . . . . . . . . . . . . . . . . . . Highlights of This Chapter. . . . . .4. . . . . . . . . . . . Adding Charts . . . . . . . . . . . . . . . . . . . . . .1. . . 31. . 30. . . .1. . 30. xviii . . . . . . .1. .4. . . . 31. . . . . . .5. . . . . . . . . . .5. .1. . . . . . . . . . . . . . . . 30. . . . . . . . . . . . . . .3. . . . . . . . . . . . . . Notes on Route Plotting and Updating . Parallel Coordinates/Stacked Bar Chart Presentation Mode . . . 30. . . . . . . . . . . Setting Up Bar Chart Contents . The Cell ARFCN Theme (GSM) . . . . . . . . . . . . . . . The Cell Theme. . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . .5. . 31. . 31. . . . . . Exporting the Bar Chart Window. . 30. . . . . 30. . . . . . . . . Specifying the Map Position. . . . . . .2. . . . . . 30. . . . . . . .2. . . . . . . 30. . . . . . . . . . . .2. .4. 31. . . . .4. Editing General Properties of a Chart . . . . . Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrity.6. . . . . . . . . . . . .1. . . . . . .7. . . . . .7. . . The Map Window Toolbar . . . . . . . 384 31. . . The General Window 33. . . . . . . . .1. . . . . . . . . . Setting the Map Projection . . . . . . . . . . . 381 31. . . . . . . . 384 31. . 389 33. . . . . . General Procedure . . . . . . . . . . . . . . . . Accessibility . .9. . . . . . . . . . . . . . . . . . . . . . Layers . . . . . Layer Control . . . . . . . . . . .3. . . . . . . . . . . . .5. . 391 34. . . . Layer Control . Editing Themes . . . . . . . . 382 31. . . The Scale Bar. . . . . . . . . . . SQI for UMTS. . . . 383 31. . . . .5. . . . . . . . . . . . . . .5. . . . “Events of KPI Type” . . .1. .3. . . . . . . . . . . . Deleting Themes . . . . . . . .10. . . . . . . . . . . . . . . . . 386 31. . . . . . 390 34. . . . . . Information on Single Theme Markers (Info Tab). . . . . . . . . .2. . . . . . . . . . .7. . . . . . . . . . . . .1. . .1. . . . . . . . .1. . . . . . . . . . . . 377 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . .3. . . . . . . . . . . . Retainability .8. . . . . . . . . View Entire Layer . . . . . . .10. . Speech Quality Index – SQI 391 34. . . . . . . . Reordering Themes . . . . . . . . . . . . . .2. . . . . . . . . . . 389 33. . 383 31. . . Visibility of Themes . . . . . . 389 33. . . . .10. . . . 389 33. . . . . . . . . . . . . . . . . . .1. . . Theme Legend (Legend Tab). . . . . . . . . . . .1. Previous View. . . .2. . . . . .2. . . . .1. . .10. 380 31. .6. . . . . . . . . . . . . . . . . . .Contents 31. . . . . Purpose of KPIs . . 390 33. . . . . . . 384 31. . . . . . . .2.8. . . . . . . . . . . . .9. 377 31. . . . . . . . . . . . . . . . .8. . . . . . . . .2. . . . . . . . . . . . 381 31. . . . . . . . . . . .1. . .8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Performance Indicators – KPIs (UMTS) 387 388 33.5. . .2. . . The Right-hand Pane . . . . . . . . . . Map Context Menu . . . . . . . . . . .7. . . . . . . . . . 386 32. . . . . . . . . . . . . . . Theme Statistics (Info and Graph Tabs) . . . . . . . . . . . . 378 31. . . . . . . . . . . .1. . . . .0 xix . Obtaining KPIs with TEMS Products. . . .1. . . . . . . . . . . . . . .8. . . . . . . . . . 385 31. .2. .2. .6. . . . . . . . . . . . . . . .4. . . . . . . 383 31. . . . . . . . . . . . 378 31.2. 378 31. .1. . . . 389 33. . . GeoSet Manager . . . . .3. . . . . . . . . . . . . . 388 33. . . . . . . . . . . . . . . . . . . . . . . . . . 391 34. Projections . 378 31. . . . . . . . . . . . . . . . . . . SQI for CDMA . . . . . . . . . . . . . . . 381 31. . . .8. . . . . . . . . Background . . . . . . . . . . 391 NT12-7002 ver 1. . . . . . . . . . .6. . Obtaining Significant KPI Statistics . . . . . . . . . . . . . . . . . . . . . . . . Adding Presentation Layers . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 User’s Manual 34. . . . . Input to the SQI-MOS Algorithm . . 403 36. . . . . 402 36. . . . The POLQA Algorithm .3. . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . Information Elements . . . .2. . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . .1. . . . .5. . . . . . . . . . . . . . . . . . . .3. . . . . . . 397 35. .3. . . . . . . . . . . . . . 34. 406 37. . . .3. . . . . . . . . Practical Considerations . . . . . . . . . 406 37. SQI-MOS Output.1. . . . .3.5. . . . . . . . . .2. . . Recording AQM Data. . . . .2. . . . . . . . . . . . . . . . . . . . . 34. .2. 408 37. . . . . . . . .5.3. . . . . . . . . . . . . . .1. . . . . . . . . . .1. . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . 34. . . . . . . . . . . . . . . . . . Prerequisites . . 406 37. . 34. . . . . . . . . . . . . . . .5. . . . . Wideband SQI-MOS (UMTS) . . . . . . . . . . . . .3. . . . 401 36. . . . . AQM with Call Generator/MRU 399 36. . . . .1. . . . . . . . . . . . . . . . . . . . . . . 402 36. . .4. . . . . . . . . . 34. . . . . Prerequisites . 34. . . .4. . . . . . . . . . . . . . . . . . . . . . . .3. . Alignment of SQI-MOS and PESQ . . . . Audio Quality Measurement (AQM): General 397 35. . . . . . 34. . . . . . Information Elements . . . . . . .1. Old SQI (UMTS) . . . . . . . 409 xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . .1. .2. . . . . . 397 35.4.2. .1. . . . . . . 403 36. .2.1. . . . . . . .1. . . Presentation of AQM Data . . . . .2. . . . . . . . . .399 36. . . . Notes on AQM Scores Obtained with Individual Phone Models.2. . . . . . Obtaining AQM Data. Presentation of AQM Data . . . SQI-MOS vs. . . . . Preparations. . . . Notes on PESQ for Wideband (UMTS) . . . UMTS. . . . . . . . . Narrowband vs. . . Measurement Setups in TEMS Investigation . . . . Comparison with Other Radio Parameters . . . AQM with Audio Capturing Unit (ACU) 405 37. .1. . Mobile-to-fixed Audio Quality Measurement with Call Generator. . 402 36. . . . . . . . . . . . . . . . . .2. .3. . . CDMA . . . . Recommended Structure of AQM Scripts . . . . . . .TEMS Investigation 14. . . . .3. . . 401 36. . . . 398 36. .1. . . . . . .2. . . . 34. . The PESQ Algorithm. . . . . . . . . . . 407 37. . . . . . . Recording AQM Data. . . . 408 37. . . . . . . . . . 403 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PESQ Key Performance Indicator . . . . . . Merging Uplink AQM Data into Logfiles . . . . . . . . . . . Mobile-to-mobile Audio Quality Measurement with MRU . . 392 392 393 393 394 394 394 395 396 35. . . . . . . . . . . . . . . . . Obtaining AQM Data. . . . . . . . . . . . . . . .2. . . .1. . . . . . . . . 404 37. 405 37. . . . . . . . 411 39. . . . . . . . . . Adding a Test Case. . . . . . . . . Obtaining AQM Data .1. . . . Details on C/I Measurements .3. . . . . . .4. . . . . . What VTQI Is Based On .3. . . . . . . . . . . . . . . . . . . . . . General Properties of VSQI. . . . . . . 419 42. . . . 426 NT12-7002 ver 1. . . . . . . . . . What VSQI Is Based On . . . . . . . . . . . . . . . . . . .4. . . . . 412 39. . . . . Static and Dynamic VSQI . . . . . . . . . . . . . . . 424 43. . 414 40. . . . . . . . . . . . . Automatic vs. . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . . . . .2.0 xxi . 424 43. . 414 40. . . . . . . . . 420 42. . . . . . . . . . Video Streaming Quality Index – VSQI 414 40. . . . . . . What VSQI Does Not Consider . . . . Manual Verification . . . . General Properties of VTQI. . . . . .4. . . . . . . . . . . . . . . . Why Measure C/I?. . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5. 423 43. . . . . . .1. . . . . . . . . . . 420 42. . . 415 40.4. . . . 411 38. . . . . . Static VSQI. . . . . . . . . . . . . . . . .2. . . . . . . . . .1. . . . . . . The GSM Channel Verification Window . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . An Example . . 422 43. . . . C/I Measurement (GSM) 418 419 42. . . . . . . . . . . . 413 40. . . . . . . . What VTQI Does Not Consider .3. . . . . Mobile TV Quality Index – MTQI 42. . . . .4. . . . .1.Contents 38. . . . . 413 39. . . . . . . . . . . . .5. . . . 416 41. . . . . . . . . AQM for VoIP 410 38. . . . . . . . . . . . 415 40. . . . . . . . . . . . 412 39. . .2. .2. . Activating Phones . . . Dynamic (Realtime) VSQI . . . . . . . . . . . . . . . . . . . . . . . Update Rate . . . . . . . . . . . GSM Channel Verification 422 43. . . . . Requirements on a Robust C/I Measure . . .1.3. . . . . . . . . . Editing and Removing Test Cases . . . . . . . . . . . . Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 42. . 420 43. . . . . . . . . .2. . . . Presentation of AQM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Video Telephony Quality Index – VTQI 412 39. . 415 40. . . . . . . . . . . . . . . . . . . . . . 43. . . . . . . . . . . . . . . Command Sequences. . . . . . . . 43. Appendix B. .6. . . . . . . 43. . . . . . . . . General Shortcuts. . . . . . .1. Drive Testing Shortcuts . . . .2. . . . . . . 43. . . . . . . . Summary of Test Case Status Values . . . . . . 441 Index 443 xxii . . . . 43. . . . . . . . .1. . . . Manual Verification .1 User’s Manual 43. . . . . . . . . .6. . . . 43. . . . . . . .13. . . . . . . 427 427 427 428 428 429 429 429 430 431 431 431 Appendix A. . . . .6. . . . . . Resetting a Test Case . . 43. . . . . . . . Running the Test. . . . . . . . . . . . . . . . . . . . . . 439 C. . . . . A. . . . . . . . Service Control vs.12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 C. . . Notes on Performance . . . . . . . . . . . .2. . . . . . . . . . A. . . . . . . . . Automatic Verification . . . 43. . . . . . Error Conditions . .1. . . . . . . . . .0 User Interface 437 439 C. . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile Load Shortcuts . . . . . . . . . . Keyboard Shortcuts 433 433 433 434 434 A. . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Handling . . . . . . . . File Types in TEMS Investigation Appendix C.9. . . . . . . Stopping the Test . . . . . . . . . .3. . . Getting Started.2. . 43. . . . .4. . . . . Comparison with Pre-12. . . . . . . . . . . .3. A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10. . 43. . . . . Saving and Opening Tests .8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43. Example . . . . . .TEMS Investigation 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shortcuts for Active Window. . . . . . . . . . . . . . . . .11. “Data” Category Information Elements. . . . . . .7. . . . . . . . .4. .6. . . . . . . Creating Test Reports. . . . . . . . . . and maintenance of wireless networks. optimization. verification.Chapter 1. and post-processing all in one. Any restrictions that apply to your edition are indicated in the Release Note included in the delivery. TEMS Investigation is a complete solution for all of a network operator’s daily network optimization tasks.0 1 . reducing costs and saving time and effort for operations staff. real-time analysis. Introduction Thank you for choosing TEMS Investigation – the industry-leading tool for troubleshooting. 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 1. Offering data collection. please take the time to read this user manual in order to gain an in-depth understanding of the product features. To get the most out of TEMS Investigation. Note: Please note that the TEMS Investigation product exists in various editions. This complete solution eliminates the need for multiple tools. all of which are covered by the product documentation but are not differentiated there. NT12-7002 ver 1. in the case of Qualcomm. It interfaces with phones.1.1 User’s Manual 1. Still more powerful post-processing facilities are provided by the product TEMS Discovery. Other phones are licensed separately for each supplier or. Supported cellular technologies can be freely selected and combined. Fundamentals of TEMS Investigation 14. Package Options – Licensing TEMS Investigation can be purchased with or without data collection capability (“Base Software Package” and “Replay Package” respectively). 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.1.1 TEMS Investigation 14. 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. scanners. separately for chipsets with different capabilities. 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. except that WCDMA always comes with GSM support included. 2 . logfile reports. it collects data and records it in logfiles. The application also boasts a vast array of windows for presentation of logfile data.TEMS Investigation 14. 0/EV-DO Rev. TEMS Investigation is primarily a tool for data collection and real-time analysis.1 is an air interface test tool for cellular networks. 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. logfile export). and other measurement devices. A/EV-DO Rev.1. data cards. The number of external devices that can be connected simultaneously in the application is dependent on many factors.0 3 . What’s in This Manual (and What’s Not) This book describes the user interface of TEMS Investigation 14. LTE. Qualcomm. Novatel Wireless. Pantech. The manual gives a comprehensive account of all functions in the application. Rohde & Schwarz. and CDMA networks and of interaction among them (for example.1 supports a wide variety of user terminals. WCDMA. Nokia. and CDMA. DRT. LG. The Information Elements and Events volume provides full details on all IEs and events found in the application.Chapter 1. It also lists and describes all preconfigured presentation windows. Audio quality measurement (AQM). GPS units can be connected for geographical positioning. positioning by pinpointing (either manual or according to planned routes) is supported. and ZTE. HTC. Hisilicon. is likewise sold as a separate option. NT12-7002 ver 1. Together they allow comprehensive monitoring of UMTS. For indoor environments. Sierra Wireless. Sequans.1 for further details on the range of connectable equipment. and WiMAX scanning. CDMA. and Transcom. TD-SCDMA.2. Audio quality measurement is supported for GSM. Option. 1. TD-SCDMA. section 10. See the Release Note for further information. GCT.1. A separate license option is available for collecting data with multiple phones concurrently. PCTel. Samsung. A variety of devices are supported for GSM. Anritsu. Sequans. Leadcore. such as whether a data service is being run. including PESQ/POLQA. See the Getting Started Manual. including ones from Ascom. and Via.2. GERAN–UTRAN–E-UTRAN inter-RAT handover). 1. ST-Ericsson. It concentrates on how to use that application once it has been installed and all external devices are connected and ready for use. These terminals are built on chipsets from Altair. LTE. Connectable Equipment TEMS Investigation 14. This option includes all required hardware as well as the ability to connect that hardware to TEMS Investigation. WCDMA. including ones from Sony Ericsson.1. Introduction The Base Software Package permits data collection with one phone at a time. Huawei. 1 User’s Manual The Technical Reference volume contains file and report format descriptions. In the remainder of this book. please refer to the documentation accompanying the phones. The same applies to all other third-party products mentioned in the manuals. and other information of a technical nature. Besides the above reference manuals. sometimes refer to TEMS Investigation documentation. The manual does not describe the full range of functions and capabilities of the connectable phones.ascom.com/en/index/support/supporttems/technical-support/tems-investigation. designed to accommodate phones and other equipment during drive tests. FAQ Many questions regarding TEMS Investigation are answered in the FAQ sections found on the Web at www. 4 .TEMS Investigation 14. 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. For exhaustive information. chapter 10.pdf which is found in the TEMS Investigation installation folder. Equipment Cases The TEMS equipment cases. a Getting Started Manual is provided which covers all preliminaries. are not covered here but have their own manuals. however. External Equipment The basics on external devices are covered in the Getting Started Manual. operate. Release Note Some technical issues not addressed in this manual are dealt with in the file ReleaseNote.htm. and control external equipment is described in the present document. external devices are discussed further whenever certain capabilities are required in order for a function in TEMS Investigation to be supported. These. Layer 3 messages. 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.com/networktesting and. TEMS Bulletins TEMS Bulletins contain updates on new TEMS product releases.com/networktesting under the link “TEMS Support”. chapter 7. TEMS News. as opposed to voice calls.0 5 .ascom. and general information about the TEMS portfolio. click the link “Register for TEMS Bulletins”. All predefined events are found in Information Elements and Events. Data Services This term refers to services requiring a data connection (either circuitswitched or packet-switched). These expressions can contain predefined events. please contact technical support. User-defined events are specified by logical expressions which trigger the event when they evaluate to true. 1. Besides these. either in the cellular network or in connected equipment. A number of events are predefined. under the heading “TEMS Bulletins”. Information Element Information elements are pieces of numeric or text-format data that are presentable in the TEMS Investigation user interface. and conditions involving information elements. Definitions This section explains a number of central concepts in TEMS Investigation which are frequently referred to in this user manual.3. events. you can define events of your own. All information NT12-7002 ver 1.Chapter 1.ascom. go to www. To sign up for this free service. Along with this material you will also receive our customer magazine. Event An event is generated by the TEMS Investigation software in order to indicate that something worthy of note has occurred. Contact information is given on the Web at www. You can also obtain up-to-date details on patch releases. and/or a more precise term is used (“GSM phone”. or events. Complete details on the arguments of information elements are given in Information Elements and Events. etc.TEMS Investigation 14. the word is used more loosely. A “message window”. “Sony Ericsson GSM phone”. Information Element. “LG UE”. rather than phones. etc. “Samsung LTE modem”. a suitable qualifier is prefixed. Outside of that context. chapter 3. may list either air interface messages. without any difference in meaning from the point of view of TEMS Investigation. you must specify an argument in the form of a neighbor index between 1 and 32. Mode Report A mode report is a status or measurement report generated by a phone. To present the signal strength of a particular neighbor channel. chapter 3. an argument is used. most often a Layer 3 message. Phone The term “phone” covers user terminals from all supported technologies.). the GSM information element Neighbor RxLev contains the signal strengths of all neighboring channels (there may be up to 32). For instance. however (chapter 26). The word “terminal” is therefore sometimes used instead of “phone”. When a subset is meant. or messages from various protocols. or mode or error reports produced by phones. To pick one item from the array. 6 .1 User’s Manual elements handled by TEMS Investigation are found in Information Elements and Events. “Sierra Wireless CDMA data card”. Route In connection with the Pinpoint Window. Message The term “message” in this user manual generally denotes an air interface message described in the wireless technology specifications. USB modems. Some user terminals supported by TEMS Investigation are in fact data cards. the term “route” refers to a planned route created in that window. Argument of Many information elements contain an array of values rather than a single value. Introduction Scanner The term “scanner” denotes a device dedicated to scanning. Phones with scanning capabilities are not referred to as scanners. NT12-7002 ver 1.Chapter 1.0 7 . Track A track is a walk along a planned route in the Pinpoint Window. for example a PCTel scanner. Optimize heterogeneous cell deployment: for example. What’s New in TEMS Investigation 14. Estimate distance to a site and determine its position by triangulation.1 User’s Manual 2. For TD-LTE in particular with its unpaired spectrum. This information can for example be used to: • • • Verify and troubleshoot synchronization in the network.1. including interference between UEs in adjacent cells and between eNodeBs. TEMS Investigation 14.1 presents cell frame timing data in newly constructed information elements for the current LTE serving cell and neighbors.1.1. Identify co-sited cells (having identical or nearly identical timing offsets) in an unknown network. Still.1 LTE Cell Frame Timing IEs Inter-cell synchronization is a central concept in LTE networks. • • 8 .TEMS Investigation 14. Compared to FDD there is also a more complex range of interference issues to handle. scheduling traffic in an efficient way among multiple cells. the same frequency being used on both uplink and downlink. synchronization is necessary within a site owing to the overlap between its cells. adjust timing in a pico cell to a surrounding macro cell. it is also highly beneficial between sites. 2. since this enables the use of techniques such as CoMP (coordinated multipoint). even for FDD. Compare and evaluate synchronization techniques. accurate synchronization between cells is crucial. taking into account the propagation delay from the macro cell eNodeB. Recently Introduced Features in TEMS Investigation 2. 2.Chapter 2. See also section 2. Cell Whitelists A common constraint in cellular network testing is to restrict tests to a predefined set of cells: for example.1. POLQA for CS Voice The state-of-the-art POLQA algorithm for speech quality assessment. 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. including PESQ and POLQA. This event can then be used in a script to trigger some action whenever the tester is in NT12-7002 ver 1. is now available also for circuit-switched voice. previously introduced for VoIP. 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. The following additional control functions have been implemented for the Xperia arc S phone.1. POLQA can be computed for both narrowband and super-wideband speech. Recently Introduced Features in TEMS Investigation 2.4. notably: • • • UARFCN and SC indicated for each SIB C/I per TCH computed for GSM circuit-switched services SIR target presented 2.1.1.3. Extended Control Functionality and Logging for Sony Ericsson Xperia arc S Sony Ericsson Xperia arc S now supports audio quality measurement.0 9 . to verify a new or reconfigured cell cluster. 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.3. POLQA is obtained in the ACU (TerraTec) audio quality measurement configuration. 2. 1. Via CDMA/EV-DO Chipset Support TEMS Investigation 14.1. The manual mode is similar to the pinpointing function in the Map window. Scripted Scanning Scanning tasks can be scripted instead of being run manually from the Navigator pane. 2. 2.1.1 User’s Manual an allowed cell. Hisilicon LTE Chipset Support The accessibility of LTE network testing is further broadened as TEMS Investigation 14. 2.1 introduces support for devices equipped with a Via CDMA/EV-DO chipset.1. as opposed to being planned in advance and followed during the walk. 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. so that a cell whitelist event can be generated repeatedly and continuously listened for by a script. 2. Controlling scanning from a script brings the same benefits of convenience and automation as for other testing activities. Offering both modes in the Pinpoint Window tool adds further to its flexibility and usefulness. Manual Pinpointing Mode in Pinpoint Window In the Pinpoint Window.TEMS Investigation 14.7. • • New Connectable User Terminals Axesstel MV610VR (Gateway R90.1.8.1 adds support for Hisilicon chipset based LTE devices. EV-DO Rev.5. 2.9. A “periodic” flag has been added as a new property of userdefined events. Net1. B) Huawei E398S (Hisilicon chipset based) 10 .6. routes can now alternatively be traced manually while walking. 1. PUSCH ack/nack counters. useful for studies of MIMO channel properties. giving a more fine-grained view of retransmission statistics. This is a Qualcomm chipset based device running under Android. 2. 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.1. 2. Supported LTE bands are: • • • TDD 1900 MHz (Band 39) TDD 2300 MHz (Band 40) TDD 2600 MHz (Band 38) 2.2.1.12. LTE RRC Redirection Events The LTE RRC connection redirection events have been extended to cover redirection to EV-DO (HRPD/eHRPD). 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. Rank Indication counters showing incidence of values RI = 1 and RI = 2.0 11 . Recently Introduced Features in TEMS Investigation 2.11. TEMS Investigation 14. 2. • • • New LTE Information Elements PDSCH BLER and ack/nack counters for Transport Blocks 0 and 1 separately.0 continued and reinforced this tradition by adding the Sony Ericsson Xperia arc S smartphone as a connectable device.Chapter 2.2.1.10. New Connectable Scanners A TD-LTE scanner from Transcom Instruments is offered as a cost-efficient solution for scanning of TD-LTE networks. each recording being wholly independent of the others. The logfile size is significantly reduced compared to the LOG format.2. A complete chronology of the activities performed by all devices.trp.2. If you wish. and more) but also: • A list of the participating devices with accompanying key properties (capabilities. sorting. 12 . Activity statistics: Total/succeeded/failed/aborted. or filtered to show only one device or one type of activity.1 User’s Manual The Samsung Infuse 4G smartphone (ST-Ericsson chipset based). • • Full compatibility with the old logfile format (*. New Logfile Format The old logfile format (*.log) was replaced in TEMS Investigation 14. you can opt to record only a subset of the activated devices. extensive information about the file appears on a new Navigator tab called the Logfile tab.0. The chronology can be grouped by device or activity type. hardware identifiers. you can tag logfiles with metadata which can serve as an aid to locating. you can hide data from selected devices in the logfile presentation. At creation time. presented in the same way as in live mode. and their outcomes. • • • When loading a completed logfile into TEMS Investigation later on for analysis. The new format embodies a more flexible and versatile framework for recording of measurement data: • Multiple logfiles can be recorded in parallel. Here you can view not only general information (time and space coordinates. 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. The activities of one device can be recorded in any number of logfiles simultaneously. Some of this metadata is also visible in Windows Explorer. descriptive metadata added at recording time.0 by a new format with extension .TEMS Investigation 14. and more). and categorizing the files later on. In logfile recording controlled by a script.log) is of course maintained. likewise new as a connectable device in TEMS Investigation 14. the full message contents can be searched. and visual highlighting were implemented in message windows in order to accelerate analysis. which was removed in TEMS Investigation 14.863 standard. and Highlighting in Message Windows New functions for searching.2. NT12-7002 ver 1. Optionally. 3G and 4G/LTE. • • LTE: TDD and FDD pilot scans can be run in parallel on Rohde & Schwarz TSMW. Show only messages of a selected type. POLQA was introduced in TEMS Investigation 14. • Expansion of Scanning Capabilities GSM scanning capabilities of Rohde & Schwarz TSMW were made available for use with TEMS Investigation: – – – RSSI scanning.Chapter 2. Searching. being specially developed for HD voice. Filtering. Case and whole-word matching is available.2. Hide messages of a selected type. Speech Quality Measurement with POLQA POLQA.3. defined in the ITU P. static ARFCN set RSSI scanning: BSIC decoding RSSI scanning: C/I measurement. Highlight selected types of messages in unique colors. See chapter 35. is the successor of PESQ.5.2. A “find next/find previous” feature is included for easy stepping back and forth between hits (can be done with the keyboard arrow keys).2. You can: • Find arbitrary text in message headers. and VoIP. The POLQA (Perceptual Objective Listening Quality Analysis) algorithm is designed along similar lines as PESQ. Recently Introduced Features in TEMS Investigation 2. The search functions essentially correspond to the Find in Logfile feature in pre14. • • • 2.0 as a speech quality measurement algorithm for VoIP. 2.0 13 . allowing multiple devices to scan concurrently using different configuration sets. filtering.0 product versions.4. The handling of scanning configuration sets was relaxed.0. 2. All of these features help you manage logfile export more smoothly and save time. which can be installed under Windows 7 or Windows Server 2008/2003. multiple concurrent FTP download sessions with one device simply by putting the sessions in parallel branches in your script. 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.6.2. Command-line controlled export can be scheduled with the generic scheduling functionality in Windows. Cell files can be included when exporting logfiles. Command line switches are provided for all aspects of the export setup that are configurable from within TEMS Investigation.0 introduced the option of using Internet Explorer 9 for HTTP download testing instead of TEMS Investigation’s built-in Web browser.7. Logfile Export Enhancements The logfile export tool was repackaged into a separate executable which can alternatively be run from a Windows command prompt.8. for example. Flow control in scripting was rendered more powerful with the new Wait For activity. the license server administrator assigns to each TEMS Investigation user the products 14 .TEMS Investigation 14. etc.2.2. 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.1 User’s Manual 2. This means that you can set up. In this Web-based portal. Improved HASP Soft License Handling A license manager portal was introduced.). 2. There is no need to pass special session concurrency parameters with the FTP testing activity. Two new HTTP information elements were provided (regardless of browser used): total document size and download time. Improved Service Testing Capabilities TEMS Investigation 14. 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. facilitating management of network licenses and adding traceability. a client license manager with a graphical user interface is provided.4 GHz) HSDPA Category 10 (14.2. Reports on license usage can be generated and also exported in comma-separated (CSV) format. From this utility.Chapter 2.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.0 15 . HSUPA Category 6 (5. “Category” fields are provided for convenient grouping of users.76 Mbit/s) Huawei E353 LG P505 NT12-7002 ver 1.9. 2. New Connectable User Terminals in TEMS Investigation 14. users detach licenses to their local machines.4 Mbit/s). and the main benefit it brings is that it greatly reduces the risk of detaching the wrong license by mistake. Further constraints such as license expiry dates can be defined. Side by side with the license manager portal. Recently Introduced Features in TEMS Investigation they are allowed to detach and sets a maximum detach duration.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.3 Qualcomm Snapdragon MSM8255 (1. The client works over a VPN.2. TEMS Investigation 14. Two or four mobile devices. A number of events – some new. Huawei C8600 (CDMA). RACH 16 . 2.1 User’s Manual • • LG P509 Sharp 006SH 2. 2.3.3. Event categories: • • • Call setup events Inter-RAT events Attach events 2. RACH Reason. The mobile-to-mobile AQM solution is in principle RAT-independent. are connected to an Audio Capturing Unit (ACU) which relays the audio to the PC. RACH Result.2. The PESQ calculation is done by the PC itself. Preamble Step Size. Extended Set of LTE RACH Information Elements A collection of new information elements deals with the RACH procedure in LTE: RACH Type.3.3.1 Alternative Mobile-to-mobile AQM Solution This is a cost-efficient solution for mobile-to-mobile audio quality measurement. some expanded in scope – report on the resulting interaction between the terminal and networks. What Was New in TEMS Investigation 13. so that no separate processing power is required in the Audio Capturing Unit.1 it was implemented for the following phones: Sony Ericsson Xperia arc. In TEMS Investigation 13. Sony Ericsson W995.1. just as in the existing TEMS Investigation AQM setup. 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. there is also no Call Generator or similar component in this AQM configuration. Nokia C7-00 (GSM/WCDMA). which call each other in pairs. The activities of the devices are completely controlled from TEMS Investigation by means of a Service Control script. Since the voice calls are made between the mobiles.3. TEMS Investigation also permits connection of multiple Qualcomm-based LTE devices.4. • New Connectable User Terminals in TEMS Investigation 13. that is.Chapter 2.6. and MME Code. TEMS Investigation 13. The implementation was verified with the Huawei EC367-2 device. 2. CDMA/EV-DO Rev. without using an external connection manager.5. MME Group Id. I) GSM/EDGE 850/900/1800/1900 HSUPA Category 6 (5. B chipsets. 2.1 Sequans TD-LTE USB modem SQN3010A-USB-M1. 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. 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. Improved Handling of Qualcomm-based LTE Devices Network connect can be performed for Qualcomm chipset-based LTE devices from within TEMS Investigation.3. HSDPA Category 14 (21 Mbit/s) Advanced control functionality • NT12-7002 ver 1.0 17 .3.3. 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.76 Mbit/s). 1 User’s Manual • Sierra Wireless AirCard 319U – – – – Dual-Carrier HSPA+ USB modem from Sierra Wireless WCDMA/HSPA+ 850/900/1900/2100 (Bands V. There are no restrictions on supported frequency bands (30 MHz to 6 GHz).3. WCDMA Scanning with Rohde & Schwarz WCDMA pilot (Top N) scanning can be undertaken with Rohde & Schwarz TSMW scanners. I) GSM/EDGE 850/900/1800/1900 HSUPA Category 6 (5.76 Mbit/s). 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.7. II. 18 .TEMS Investigation 14. VIII. This feature is a time-saver that reduces the hours you have to spend on drive testing. HS MIMO Transport Block Size (Max). • – • • • Support added for Samsung Galaxy S II LTE. This service checks for new patch releases on a regular basis. Min/max/median versions of HS transport block size IEs introduced: – HS Transport Block Size (Min).1 Multiple concurrent PN scans can be performed with PCTel MX and EX scanners: for example. Support added for Anydata ADU-895A (CDMA/EV-DO Rev. RSSI scan) with PCTel SeeGull MX.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. Recently Introduced Features in TEMS Investigation 2. HS Transport Block Size (Median).Chapter 2.9. HS MIMO Transport Block Size (Median).0 19 . The new feature streamlines administration processes and minimizes waiting time.3. Software Update Service A TEMS Investigation software update service was introduced. Support added for Novatel Ovation MC551 4G LTE USB modem (Band 13).10.1. HS Transport Block Size (Max). all with arguments for stream 0 and stream 1.3. B. one PN scan on a cdma2000 frequency and one on an EV-DO frequency. HS MIMO Transport Block Size (Min).8. • Enhancements in TEMS Investigation 13. CDMA Scanning with PCTel SeeGull MX Support was added for CDMA scanning (PN scan. 450 MHz). all with arguments for primary carrier and secondary carrier.3.11. • • • New Connectable Scanners in TEMS Investigation 13.3. NT12-7002 ver 1. 2. 2. User actions are reduced to the clicking of three buttons: commit to a waypoint on reaching it. The point of pre-planning routes is to render route walks as simple as possible. where you create and walk pre-planned indoor test routes.1 User’s Manual • Support added for Huawei U6100 (HSPA). These relate mainly to: cell reselection parameter settings and measurements (intra-frequency.2 The existing indoor measurement solution was complemented with a new Pinpoint Window. step forward to the next waypoint.3. which incorporate building and floor plan information as well as the planned routes you create. The buttons are generously sized to permit easy and accurate tapping on a touch screen while walking around.1. DCI format usage on PDCCH. or after downloading a specified amount of data. inter-frequency.ibwc). discontinuous reception (DRX). 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. Indoor map sets. • A large number of new LTE information elements have been introduced. promoting an efficient work process and saving time and money. and step backward to the previous waypoint in case you want to repeat a part of the route.2).1.TEMS Investigation 14. To the HTTP Get script activity have been added two new options: terminate session after a specified duration. and sounding reference signals (SRS). 2. and inter-RAT). Logfiles recorded when walking planned routes are saved in regular TEMS Investigation logfiles.12. are saved in the iBwave Design container format (*. Support added for Altair DC-E3100 chipset (no devices commercially available at the time of releasing TEMS Investigation 13. Support added for GSM scanning with Rohde & Schwarz TSMW. • Enhancements in TEMS Investigation 13. Support added for the following devices: – – – – Datang/Leadcore LC8143 HTC Vivid (PH39100) LG MS695 Quanta LU220 • • • • 20 . 2. USB modems. Any IPbased activity in the Service Control Designer.0 version.Chapter 2.0 version. iPhone or BlackBerry units. Please note that lower-layer data (RF. it is possible to do Top-N LTE signal scanning in both TDD and FDD mode.4. taking it to a whole new level of genericity. RSRQ. as will be desirable prior to launching them in the network. and all IP information elements will then be populated. 2. however. as well as video streaming. etc. NT12-7002 ver 1. known as TD-LTE. and SCH CINR.1. Layer 2.0 TD-LTE Support The LTE standard allows both frequency division duplex (FDD) and time division duplex (TDD) operation. Up until the 13. What Was New in TEMS Investigation 13. TEMS Investigation 13. 2. Layer 3) is not obtained with this kind of testing. LTE support in TEMS Investigation was restricted to FDD.0 21 . or a wide variety of network cards.4. With the 13. The data set obtained is similar to FDD and includes RSRP. 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. This feature can be used to verify application layer performance for arbitrary devices. embedded modules. can be run on such a device. Data Service Performance Verification with Generic Device TEMS Investigation 13.4.0 expanded the concept of data service testing. Using a Rohde & Schwarz TSMW Universal Radio Network Analyzer.0 introduced scanning support also for the TDD mode. Any LTE frequency band can be scanned. 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. For example.4.18.1. such a file may contain all details of how to perform an LTE Reference Signal scan with a PCTel MX scanner. a range of additional LTE information elements are obtained.4. New Connectable Equipment in TEMS Investigation 13.6. New LTE Information Elements With LG devices. and PUSCH BLER. See section 20.6. PBCH BLER.3. 2.4.0 UMTS Terminals 2. 2.TEMS Investigation 14.0. The utility can also be seen as a complement to the script saving function in the Service Control Designer. many LTE elements previously available only with LG devices are also obtainable with Qualcomm devices. including PDSCH Transmission Distribution. See section 4. 2.5. Selection of Preferred Workspace at Startup When you start TEMS Investigation 13.1 User’s Manual 2. Furthermore. you are invited to select what workspace to use: one recently used.4.2.4. The TEMS Settings Manager boosts usability by enabling easy distribution of configuration data among users and among instances of TEMS Investigation. 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. using TEMS Investigation 13. some other existing workspace. • – – – 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 .4.2. or all the parameters needed to access and interact with a particular FTP server. or a new one that is empty. which creates files specifying the activities to perform during testing. 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. Unlike the Telnet protocol. 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. Support for 64-bit Windows 7 TEMS Investigation 13. SSH2 uses cryptography to authenticate the remote computer and therefore renders the Iperf server less vulnerable to hacker attacks. Update to this text: GSM and WCDMA scanning is supported with R&S TSMW from TEMS Investigation 14. HSUPA Category 5 (2. 1.0.4.4. see section 2.4. which sends logins and passwords in plain text.Chapter 2.7.2 Mbit/s).16. since it is subject to export restrictions due to its use of strong encryption. HSUPA Category 6 (5.2 Mbit/s).2.1 2.3. LTE Scanner: Rohde & Schwarz TSMW The R&S TSMW Universal Radio Network Analyzer enables TD-LTE measurements in TEMS Investigation 13.7.0 Mbit/s) Nokia C7-00 HTC Imagio 2.3.15.8.0 23 . Recently Introduced Features in TEMS Investigation – • – – – • HSDPA Category 8 (7. SSH2 requires a separate license option and installation package.0 onward. Such technology expansions will then be possible to do remotely by means of a scanner software upgrade. NT12-7002 ver 1. Compare section 2. See section 20.1.6.0 can be run under 64-bit Windows 7.4. and support for these is planned for inclusion in future releases of TEMS Investigation. Extensive set of VoIP jitter buffer metrics obtained as information elements: RFC 1889 Jitter. Average/Min/Max Playout Delay.9. MTSI Session Setup Failure Ratio (%). TEMS Investigation 13. Special Subframe Configuration. – – – • TD-LTE information elements introduced: Ack Reporting Mode. Decoding Errors. • • 24 .4. Position of Minimum k Distribution. Lost Packets. PCFICH CFI Information.4.11. UL/DL Configuration.4. UL/DL Configuration Type. 2. Size Increase (frequency of jitter buffer size increases). nCCE Average/Min/Max. HSUPA: New information element “HS UL E-DCH TTI (ms)” indicating TTI length (2 ms or 10 ms).0. Performance Improvements For any given device configuration and test setup. Underruns. Possible to select AMR-NB or AMR-WB as VoIP speech codec. MTSI Session Setup Time (s). • – – New Features in TEMS Investigation 13. Possible to select AMR speech codec rate. MTSI Registration Time (s).10.0 generates lower CPU load than previous versions. More LTE information elements obtainable with Qualcomm chipset based devices: MAC PDU Handover Interruption Time.TEMS Investigation 14. Events generated enabling computation of the following VoIP KPIs: MTSI Registration Failure Ratio (%). MTSI Session Completion Failure Ratio (%). 2. • • Additional New Features Internal GPS of PCTel MX available as data source in TEMS Investigation. Other improvements include better memory management and reduced start-up time. GT-B3740 LTE/UMTS dual-technology devices. PUSCH Phy Throughput. Np and Np+1 Distribution. PBCH BLER. UMTS network connect can be done from within TEMS Investigation with Samsung GT-B3730. Overruns. PDSCH Transmission Distribution elements.1 Improved VoIP testing: PJSIP VoIP client added as alternative to CounterPath. The KPI computation itself is done in TEMS Discovery or TEMS Automatic.1 User’s Manual 2. Chapter 2. Support added for Samsung SCH-I510. Support added for Qualcomm TD9200 TDD. Support added for ZTE MF682. Support added for LG MN270. NT12-7002 ver 1. Support added for Samsung SCH-R380. Support added for Samsung SGH-A307 (LTE part). Support added for Sierra Wireless AC320U. Support added for Vodafone K5005.0 25 . Support added for ZTE AL611. Support added for ZTE AL621. Recently Introduced Features in TEMS Investigation • • • • • • • • • • • • Timestamps given with 1 ms resolution in message windows and logfile text format export. Support added for LG FM300. This option is selected by right-clicking the Start menu item above and choosing Properties Shortcut tab Advanced. 3. The overall structure of the user interface is described in more detail in chapters 4 and 5. In Windows Vista and Windows 7 you must run the application as administrator. Quick Guide to the User Interface This section gives a quick overview of the TEMS Investigation user interface.1 User’s Manual 3. To obtain a genuine understanding of the presented information. Starting TEMS Investigation Once installed. you need a working knowledge of the wireless technologies concerned.3.2. familiarity with Windows is useful. • Choose Start Programs Ascom TEMS Products TEMS Investigation 14. Recommended Skills Since TEMS Investigation is a Windows application. chapter 5 and section 8. 3. TEMS Investigation can be launched from the Start menu. Installing TEMS Investigation See the Getting Started Manual. 3.2.1. Note: We recommend that you plug the external equipment you are going to use into the PC before starting TEMS Investigation. 26 .1. 3. Basics of TEMS Investigation This chapter guides you through some fundamentals of TEMS Investigation.TEMS Investigation 14.4. change the mode of presentation of information elements. Up to ten worksheets can be active simultaneously. Most of the toolbar buttons are mirrored in the menus. NT12-7002 ver 1.Chapter 3. 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. Toolbars The toolbars provide shortcuts to certain functions in the application. you can divide your workspace into several worksheets.0 27 . Navigator From the Navigator you manage your connected equipment or view information on the currently loaded logfile. particularly those relating to logfile recording and analysis. Only one workspace can be open at a time. From here you also open presentation windows. To manage your windows more smoothly. and manage your worksheets. Status Bar The status bar displays various messages that indicate the current status of the application.1 User’s Manual Menu Bar The menus mirror the toolbars as well as the Navigator’s Menu and Worksheets tabs.TEMS Investigation 14. 28 . This means that: • • If you have a logfile open. see section 8.4. the application is in analysis mode. At the beginning of a session. 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. you must close it before you can activate external devices.Chapter 4.4.1. you must first deactivate all currently active external devices. Note: You do not set the working mode explicitly in the user interface. Analysis mode: The presented information is read from a logfile which you have loaded in order to inspect and analyze it. As soon as you activate external equipment. User Interface 4.0 29 . and can be seen as an expanded version of section 3. however.) In drive testing mode you can record new logfiles. Deactivating all external devices returns the application to analysis mode. 4. The terminology is used in the manual to clarify how things work. it switches to drive testing mode and remains in this mode as long as some external device is activated. nor is the current mode shown there. one for testing and recording. NT12-7002 ver 1. User Modes TEMS Investigation can be run in two different modes. User Interface This chapter goes through the user interface in more detail. To be able to open a logfile. • The two modes are mutually exclusive. (Regarding the “activate” operation. where it is automatically selected.TEMS Investigation 14. later on.1 User’s Manual 4. the default workspace (identified in the dialog) is opened. If you click OK without making any selection in the dialog shown above. Only one workspace can be open at a time. Click OK and TEMS Investigation will start with the chosen workspace.tdc). Archived Material: This option takes you to the regular open workspace dialog. Workspaces and Worksheets Workspaces The environment that stores all the windows and settings used in a working session is called the workspace. where you browse the file system to select a workspace file. A timer in the lower left corner indicates the remaining time. When you start TEMS Investigation.2. The workspace selection dialog closes automatically after 10 seconds if there is no user interaction. Create a New Workspace: This option creates a new.2. The chosen workspace is added to the workspace list in the dialog above. empty workspace.1. you handle workspaces 30 . 4. 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 (*. The dialog cannot be opened again. Settings include information on connected external devices. give the following command: investigation. save the workspace under a different name. 4.Chapter 4.0 31 . whether predefined or user-created.1. Up to ten worksheets can be active simultaneously.2.3. This is already done in the default workspace.exe -newwksp • • 4. or alternatively from the File menu.1\Workspaces Windows XP: C:\Documents and Settings\<user>\My Documents\TEMS Product Files\TEMS Investigation 14. User Interface from the File and View toolbar (see section 4.2. which has a number of worksheets dedicated to different purposes. Windows Vista: C:\Users\<user>\Documents\TEMS Product Files\TEMS Investigation 14.1\Workspaces Note: You cannot save changes to the predefined workspaces.2. Opening Workspaces from a Command Prompt Alternatively. • If you know the exact name of the workspace you want to use. Worksheets To manage your windows more smoothly.2. NT12-7002 ver 1.1. as shown by their designations.2.exe -recent To start the application without loading any existing workspace. you can use the Command Prompt to launch TEMS Investigation with a specific workspace.1 cannot load workspaces from older TEMS Investigation versions.1. They all normally reside in the following directory: • • Windows 7. give the following command: investigation.4 for further details). you can launch TEMS Investigation with that workspace loaded by giving the following command: investigation. some further predefined workspaces are supplied.tdc To start the application with the most recently used workspace. you can divide your workspace into several worksheets. TEMS Investigation 14.exe <workspace name>. 4. Predefined Workspaces Besides the default workspace. All of the commands that follow need to be executed from the directory <TEMS Investigation install dir>\Application. To save your modifications. Insert Filemark: Insert a filemark in the logfile. 4. the logfile is closed. not the full contents of the file. Recording properties are set from the Logfile menu. When you copy a worksheet.TEMS Investigation 14.2. see chapters 7–9.2.2.3.1. For a full description of the recording function. “MS1” is replaced by “MS2”.3. 32 .1 User’s Manual Worksheets are handled from the Worksheet menu. The Toolbars The toolbars in the main window give speedy access to some of the most central functions of TEMS Investigation. This allows you to instantly duplicate a worksheet for a different device. Open/Close Logfile: Open a logfile/Close the logfile that is currently open. which can also be accessed by right-clicking in a worksheet. Replay Toolbar This toolbar is accessible in analysis mode. Record Toolbar Start/Stop Recording: Start/stop recording a logfile. Fast Forward/Stop: Start or resume loading of the opened logfile/Stop loading of the opened logfile.1. 4. the device channel (“MS”/“DC”) index is incremented in all windows: for example. see section 11. Equipment handling is done from the Equipment tab of the Navigator. See section 11. When you stop the recording. See section 11.5). 4.3. The toolbars are mirrored in the menus (see section 4.1. Note that this operation only presents logfile metadata. Toggle Full Screen: Toggle between full screen and normal mode.8. During loading of a logfile.1. “Play” Section This section is active in analysis mode. See section 11. File and View Toolbar New Workspace: Create a new workspace.3.3. It is divided into the following sections: 4.4. 4. 4. Help Section Shows a help text when you point to a button or combo box on the main window toolbars. Print: Print the selected window.4. the progress bar shows what proportion of the logfile has been loaded.2.3.0 33 . Save Workspace: Save a workspace. Compare section 11. NT12-7002 ver 1. otherwise directs you to the online help: 4.2. Print Preview: Show a preview of the window printout.Chapter 4. Report Toolbar Generate Report: Generate a report from one or several logfiles.4. The Status Bar The status bar at the bottom of the main window displays symbols and short messages concerning the current status of the application and of external devices.4. Open Workspace: Open a saved workspace. User Interface 4. 6. From here you can also set recording properties. Help Menu Gives access to online help. 4. 34 .1. File Menu The Menu Bar Apart from holding some standard File menu commands. Presentation. a rolling progress bar is displayed here.5.3. and Configuration Menus These menus mirror the Menu tab of the Navigator. 11. this menu mirrors part of the File and View toolbar.1. “Record” Section This section is active in drive testing mode. Compare section 11.2. Window Menu This is a standard window manager. View Menu From here you choose which toolbars and which other tools should be visible. and to the about page.TEMS Investigation 14. Logfile Menu The Logfile menu mirrors the Record and Replay toolbars. Control. and 11. When some form of logfile recording is ongoing.4.8 respectively). containing the same information as this manual. The Full Screen mode hides the Navigator.1 User’s Manual 4. export logfiles. and generate logfile reports (see sections 11. Worksheet Menu From this menu you manage your worksheets. 0 35 .Chapter 4.6. can also be performed from the keyboard. A list of keyboard shortcuts is found in appendix A. NT12-7002 ver 1. User Interface 4. as well as many standard file and edit operations. Keyboard Shortcuts A number of central operations in TEMS Investigation. They are divided into the categories Presentation. The Navigator has the following tabs: • • • • • the Equipment tab.3 the Logfile tab. showing information on the logfile currently loaded: section 5. giving an overview of your current workspace configuration: section 5.2 the Info Element tab. The Navigator The Navigator pane. All Navigator windows can also be opened from the menu bar. See Information Elements and Events. listing the types of windows provided: section 5.1 the Menu tab. Menu Tab The Menu tab lists most types of windows that are available in the application. To open a window. Control. Equipment Tab See chapters 7–9. or drag the symbol from the Navigator to the worksheet where you want it. listing information elements: section 5. chapter 8 for descriptions of the contents of individual presentation windows. 5.2. 36 . How the windows work and how they can be configured is covered in the present document: see chapters 23– 31.4 the Worksheets tab.1 User’s Manual 5.TEMS Investigation 14. located on the left in the TEMS Investigation main window. and Configuration. You can hide the Navigator by switching to full screen mode (done from the View menu or from the File and View toolbar). 5. allows you to set up and manage your workspace and your external equipment.5.1. used for equipment handling: section 5. double-click the corresponding symbol. The Navigator The control and configuration windows are also described in this volume. right-click the element in the Navigator and select Add Color. • Editing the Color Ranges of Information Elements If you want to add color ranges to an information element.0 37 . see section 5.3. The attributes are edited from the Info Element tab.1.2. Symbol: Range of plot marker shapes (symbols) encoding the IE value in Map windows. Please use the alphabetical index to locate them. Some numeric elements have such presentation attributes defined by default. 5.5). others do not. see section 23. Regarding information element categories. see Information Elements and Events. 5.Chapter 5. 5. Info Element Tab The Info Element tab lists all the information elements handled by TEMS Investigation.3. 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. The attributes are: • • • Color: Range of colors used to encode the IE value (in a variety of presentation windows).2.3. NT12-7002 ver 1. these settings are automatically used unless you have specified a different usage in that particular window (possible only with colors in certain window types. Size: Range of plot marker sizes encoding the IE value in Map windows. Presentation Attributes of Information Elements For all numeric information elements (that is. When you add an information element to a presentation window.3. 2.1 User’s Manual • If you want to edit the default color ranges of an information element. then double-click Color.1. Click Auto Setup.TEMS Investigation 14. double-click the information element to expand it and show the presentation attributes. In either case. • • Set the number of intervals.3. Under From Color and To Color. continue as follows: 5. 38 . • Automatic Setup of Color Ranges This is the easiest way to set up color ranges. choose colors for the extremes of the value range. and choose a color. click Add.3. 5. A single remaining interval cannot be deleted. select it. 5. Logfile Tab See section 11.2. If you do not check the Via Color box. 5.2. When you click OK.0 39 .4. nor can the color range as a whole be removed. set the endpoints of the interval.2. See section 5. To delete an interval.3.3. If you delete parts of the color range so that no color is defined for some values. Manual Setup of Color Ranges If you prefer to assemble your color range interval by interval. follow these steps: • To add an interval. select it and click Delete.Chapter 5. NT12-7002 ver 1. click Edit. these values will be drawn in black. Editing the Marker Sizes and Symbols of Information Elements Ranges for map plot marker sizes and symbols are edited in exactly the same way as color ranges. • • To edit an interval. and make your changes. the intermediate color is chosen automatically based on the “From” and “To” colors. The Navigator • Check the Via Color box if you want to use a specific color in the middle of the range.2 above. a color range is created automatically with evenly sized intervals and suitable intermediate colors.3. Each worksheet is represented by a folder containing the windows in this worksheet.TEMS Investigation 14.5. Double-clicking on a symbol will make that particular window (and the worksheet it is placed on) active.1 User’s Manual 5. You can rearrange windows from this tab by dragging them between the worksheet folders. Worksheets Tab The Worksheets tab lists the worksheets currently active in the workspace. 40 . 6.cel). Regarding TEMS Investigation CDMA CSV cell files in general.xml) whose format is common to several TEMS products: See section 6. This format is for UMTS only.2. Cell Data TEMS Investigation can present information on individual cells in cellular networks. In particular. which are found in the directory XMLSchema beneath the TEMS Investigation installation directory: • The schema TEMSDataTypes. relying on the data types in TEMSDataTypes. See section 6. Creating a Cell File in XML Format The XML-format cell file uses two XML schemas. section 4. A full description of the XML format is found in the Technical Reference. NT12-7002 ver 1. GSM and WCDMA cells can be mixed in one file. it is possible to draw cells on maps and to display cell names in various windows. and fill in the data from there.xsd defines XML attributes and elements that embody cell and site data. chapter 4. see the Technical Reference. in a file with a plain-text. Cell Data 6. CDMA cell files in TEMS Investigation CDMA CSV format can be converted to the XML format using TEMS Discovery.xsd. The schema TEMSCell.3. TEMS Investigation specific format (*.Chapter 6.1.0 41 .1. • The most convenient way of composing XML-format cell files is to load the above schemas into a suitable XML development tool.xsd defines TEMS-specific XML data types. Cell data is also made use of in logfile reports. Cell data can be provided in two ways: • • in a plain-text XML file (*. derived from the fundamental data types set down in the XML specification. To remove a cell file from the list. Creating a Cell File in CEL Format The CEL format is a unified version allowing both GSM and WCDMA cells in the same file.TEMS Investigation 14. If you use a spreadsheet application to edit CEL files. You can have several cell files loaded in the application at the same time. click OK. chapter 3.4. click the Add button and browse to select your file.3. The set of loaded cell files can be modified at any time.5.2. be sure to save them in tab-delimited plain text format. if you load both CEL and XML files. If multiple files of the same type (CEL or XML) are loaded. Otherwise. 6. 42 . open the General window.5.4. It is described exhaustively in the Technical Reference. 6.1 User’s Manual 6. select it and click Remove.3. it must be loaded in the General window. However.5. cell information is presented separately from each type of file. the following functions become available in the application: • Drawing of cells and indication of neighbor relations and channel usage on the map. and 31.5. click Remove all. Use of Cell Data in Presentations Once cell data has been loaded. 6. See sections 31. 31. To add a cell file. Loading Cell Files To make a cell file active. In the General window.5.1. The cell file is added in the list box. Loading Cell Data from Mentum CellPlanner Mentum CellPlanner uses the XML format for cell data. XML cell files created with Mentum CellPlanner can be loaded into TEMS Investigation. the information in all files is correlated in the presentation. rather. unwanted characters might be inserted which prevent TEMS Investigation from interpreting the file correctly. double-click the item Cellfile Load.5. When you are done selecting cell files to load. • • • • • From the Navigator’s Menu tab. no attempt is made to correlate CEL and XML cell information. To remove all cell files.5. chapter 3 (“Cell Distance” IEs).0 43 . Cell Data • • • Serving cell and handover indication on the map. Presentation of cell names in status windows.3.Chapter 6. Computation of cell ranking based on these statistics. See section 31. See the Technical Reference. Bar charts: section 30.2.5. Presentation of cell data on the Info tab of a Map window.3. line charts. chapter 7. Best server indication on the map. • • • • NT12-7002 ver 1.6. Generation of events detecting (probable) missing neighbors.5. See section 31. section 10.3. based on scan data.2. In logfile reports: Association of statistics with individual cells. and bar charts.5. See section 31. Configuration of status windows is covered in sections 24.2–24.4. See Information Elements and Events. Line charts: section 29.4. Indication of distance from current position to current serving cell.5. See Information Elements and Events. 1 User’s Manual 7.1. See chapter 21. can be automated using the Service Control tool. Managing External Equipment: General This chapter summarizes how external equipment is handled in TEMS Investigation. 7. One device at a time is in focus in this pane. Connectable Equipment The range of equipment that is compatible with TEMS Investigation is given in the Getting Started Manual. See chapter 9.TEMS Investigation 14. 7.2. which is covered in chapter 20. The functionality here relates to the device that is currently selected in the top pane. and many more besides. chapter 10. Provides shortcut to device properties. Activities tab: From here you can manually apply various commands to and perform various actions with the selected device. – – • Bottom pane: – – 44 . All of these tasks. Full details follow in chapters 8–10. See chapter 8. The in-focus device can be changed with a context menu command. 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. turn to chapter 10. of equipment connected. and of the PC. NT12-7002 ver 1. Managing External Equipment: General – Information tab: Shows some basic data on the selected device.0 45 . For further information. its purpose is to give an at-a-glance overview of vital data in one place. See section 8.3.Chapter 7. 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. 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.Scan scanner Rohde & Schwarz TSMW scanner GS Chapter 11 12 13 14 8. see the Getting Started Manual.TEMS Investigation 14. special configuration of both device and PC is required. External devices supported by TEMS Investigation are automatically detected by the application after they have been plugged into the PC.6. For some devices.1 User’s Manual 8. 46 . These steps are covered in the Getting Started Manual as follows: Device Ericsson Fixed Wireless Terminal DRT scanner Andrew i.1. see the Getting Started Manual. section 10. Special PC and Device Configuration Requirements Regarding device-specific preparations for running data services. section 7. Activating External Equipment This chapter describes how to activate external devices in TEMS Investigation for the purpose of data collection. The only exceptions to this rule are handled using the Manual UE Configuration utility.1. but the TEMS Device Manager has not started or cannot detect the SRU. Anritsu ML8720 scanners connect to a COM port.3. (All OK. Flashing red: The SRU does not have sufficient power to start up the scanning module. Workaround: Restart the TEMS Device Manager service in Windows. Activating External Equipment 8. – If the scanner is connected directly to the PC.) 8. a 100Base-T crossover cable is used for this purpose. • Plugging In Scanners SRUs connect via USB. 8.1. The device has two USB plugs. either directly on the PC or via a local area network. NT12-7002 ver 1.Scan. chapter 11. – – • • • • • PCTel SeeGull MX. Other PCTel SeeGull LX scanners connect to a COM port.1. (See the Getting Started Manual. The “Status” LED on the SRU front panel is interpreted as follows: – Steady green: The SRU has sufficient power. or connect the power connector of the SRU cable to an external 12 V power source. LX MM2. Anritsu ML8780A scanners connect via USB. A single USB cable connects the USB port on the device to a USB port on the PC. Andrew i.1. the black one must always be connected.) Flashing green: The SRU has sufficient power. Rohde & Schwarz TSMW and DRT scanners connect to an Ethernet port.2. and so no startup command is sent to the scanning module. and the Windows service “TEMS Device Manager” has detected the SRU. 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).Chapter 8. so that the SRU’s scanning module has started up. and PCTel PCT scanners connect via USB.0 47 .1. Plugging In Ericsson Fixed Wireless Terminals An Ericsson Fixed Wireless Terminal is connected to the PC by means of a LAN cable. Plugging In Phones and Data Cards Most supported phones and data cards connect to the PC via USB. EX. Plug in the red USB plug. 6. The AQM module also requires a separate 12 V power supply (the voltage provided through the USB connector is insufficient).1 User’s Manual – If the scanner and PC are to communicate over a local area network.3.1. 8. a Sony Ericsson Z750i phone has been autodetected. An audio cable is connected between the AQM module and its associated phone. Plugging In Stand-alone AQM Modules The stand-alone AQM module connects to the PC via USB. 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. both should be connected to local area network ports with normal 100Base-T cables.4. In Windows 7 and Windows Vista you must run the application as administrator.1. or to a COM port. 48 .5.1. In the example below. 8.2.TEMS Investigation 14. 8.1.3. This option is selected by right-clicking the Start menu item above and choosing Properties Shortcut tab Advanced. Plugging In GPS Units Supported GPS units connect via USB or Bluetooth.1. Plugging In Equipment Cases All supported equipment cases connect via USB. 8. 8. 8. • Starting TEMS Investigation Launch the application as follows: Choose Start Programs Ascom TEMS Products TEMS Investigation 14. 5 8. a context menu pops up containing the following commands: • • Activate. Device Context Menu If you right-click an EQ item.3.3. • NT12-7002 ver 1. Please note that in presentation windows.1. Change Equipment: Select a number to change the device’s EQ index to that number.Chapter 8.1. Activating External Equipment Each device is represented by a numbered “EQ” item.3. Deactivate: How to activate and deactivate devices is explained in section 8.1. external devices are represented by their channels (“MS”/“DC”/“PS”). You can change the EQ index assigned to the device: see section 8. See section 23.1.5 Device is selected as preferred GPS: see section 8. Properties: This menu item takes you to the device properties.3.0 49 . the two devices will then swap indices. see chapter 21.4.3. 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. 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”. It is possible to select an index that is already taken by another device. the number of the phone must be known to TEMS Investigation. A phone number retrieved by an AT command will always override a manually entered number. The number you enter will be used for this phone from now on.2. PESQ. unless the AT command succeeds at that time.3. Air Interface. Data.2. or because the phone did not respond properly to the AT command. Bottom Pane “Activities” Subtab See chapter 9. In such cases you need to enter the phone number manually in this field. If this operation succeeds. Editable field. Examples: IP Sniff.2.2. 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). When you plug in a phone. 8. If a phone is going to measure AQM in a Call Generator/MRU configuration.1 User’s Manual 8. Capabilities Identity IMSI Phone Number Shows the IMSI of a UMTS phone’s subscription. this may be because no phone number is defined on the SIM. Device identity.3. Position. It will also be used on future occasions when the phone is plugged in. “Information” Subtab Capabilities of the device. the autodetect procedure sends an AT command to it in order to find out the phone number. The phone number of a user terminal. which is usually stored on the SIM card. the phone number will display here.TEMS Investigation 14. If no phone number shows.1.3. 50 . 8. This can take up to 90 seconds (during which time the LED is pale green or orange). On all phones you need to activate tethering via USB while the phone is connected to the PC by the USB cable.3. a brief description is given of what needs to be done. 8.3.6. 8. Tethering means using a mobile device as a modem to provide Internet access to an unconnected device – in NT12-7002 ver 1. and Windows has detected the device for the first time. etc. the scanner should be rebooted.3.).3. if you plug in one of those scanners after 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.3. Below.0 51 . pull the USB cable before doing so. The details of the configuration differ depending on the phone (unbranded.4.1. Wait until the LED turns green before plugging the USB cable into the scanner.3. Always wait for the scanner to boot completely (LED turns dark green) before starting TEMS Investigation. Detection of DRT Scanners and Rohde & Schwarz TSMW For technical reasons. • • Detection of PCTel SeeGull MX Scanner After installing the driver.2. 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. 8.Chapter 8. and do not reconnect it until the scanner has started up again (green LED). AT&T branded. Verizon branded. 8. If you need to power cycle the scanner during use.3. • • Detection of Equipment: Special Cases Detection of PCTel SeeGull EX Scanner Start up the scanner without the USB cable connected. Therefore. 8. you need to click the Refresh button to have it detected.3. Activating External Equipment Ports Ports exposed by the device.3.1).3.3. For HTC Touch Pro2 phones generally. IP sniffing needs to be disabled.3. 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. This is to prevent an inordinate number of devices from appearing in TEMS Investigation when you are doing data collection with multiple devices. the text for this device will be red. On other HTC Touch Pro2 phones.1 User’s Manual this case. you also need to install TCP Router software. 52 .3. WLAN) is by default disabled. section 3. it cannot of course be activated in TEMS Investigation. Detection of Network Adapters Detection of network adapters (LAN. Detection of Equipment Not Covered by License If you plug in a type of device for which you have no license. The terminology used to refer to tethering differs between phones: • • On a Verizon branded phone. activate the “Modem link”. However. 8.16. this operation creates ports in Windows that TEMS Investigation can detect. 8. Of phones having the “Internet Sharing” function. only one phone at a time can be used with TEMS Investigation. See the Getting Started Manual. This limitation does not apply to the Verizon branded phones.3. as granted by your TEMS Investigation license. please refer to section 20. it will still appear on the Navigator’s Equipment tab.TEMS Investigation 14.5. In each case.3. activate “Internet Sharing”. the PC on which TEMS Investigation is running.3.1.1. On all HTC Touch Pro2 phones except Verizon branded ones. When a device has no license. This is provided by Ascom in the form of a CAB file.3. For instructions. That means that KPI data cannot be collected with these phones.6. The Port Configuration tab is mainly used for Datang devices.exe.Chapter 8. • On the Port Configuration tab you create an entry that is directly mapped to a COM port number on the PC.4. although it is supported. click the button Start Manual UE Config. Alternatively. section 7. see the Getting Started Manual.3.0 53 . You must restart the application for the change to take effect.1. you can launch this utility by running the file <TEMS Investigation install dir>\Application\ManualUEConfig. then you can run the Manual UE Configuration utility to help TEMS Investigation recognize the device. see section 11.1.2. The Device Configuration tab is the most commonly used.3). set the Network Card device to enabled in the Device Detection Properties dialog (see section 8. On the Equipment tab of the Navigator. section 7. You must enable network adapter detection if you want to transfer logfiles over a LAN or WLAN connection. 8.5. Activating External Equipment • To enable detection of network adapters. • NT12-7002 ver 1. 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. Normally there is no need to do this. User-assisted Detection of Devices If a device is not detected properly by TEMS Investigation. there are however certain devices for which you must use Manual UE Configuration as an aid to detection – see the Getting Started Manual.6. It creates an entry for the device that can be reused independently of the actual COM port number used for the device. ) Under Type. • • 54 . enter a name for the device.4. Then click OK. • The Manage Device dialog appears. • • • Under Name. click OK. In the Ports section.1–8. In the tree view. click the New button to create a new entry. select the device root node that contains the ports of interest. all ports of the device are listed. Finally. See also sections 8. You can change this assignment by modifying the selections in the combo boxes. choose the correct device type according to its capabilities.1 User’s Manual • On the Device Configuration tab.4. Select the type of device to use and map each available port on the device to its function. Click Save and Close.TEMS Investigation 14. (The string does not show anywhere else in TEMS Investigation. In the combo boxes on the right is indicated the functional assignment of each port in TEMS Investigation. A dialog titled Select your device appears. The device is added to the list in the main window.3.3. Ports that do not have a mapping can be left blank or undefined.4. Mapping Device Ports to Interfaces If it is not clear which port should be mapped to which interface.0 55 .4.3. This is necessary to update TEMS Investigation with the device configuration just defined.) Below are some examples of mappings in UEDescription.1.xml file (found under <TEMS Investigation install dir>\Application) may give an indication.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. (If you are running the Manual UE Configuration utility independently. (See the XML code excerpt below. and the DESCRIPTION tag is the name displayed in the tool. The TYPE tag is mapped towards the interfaces. TEMS Investigation will update itself automatically with this data when launched.) 8. Activating External Equipment Click the Refresh button in the Navigator. the entries in the existing UEDescription.Chapter 8. 1. Finally. pair each available port to the correct port type as shown in the screenshot below. Launch the Manual UE Configuration utility and select your device as described in the introduction of section 8. click OK. In the Manage Device dialog.3.TEMS Investigation 14. do as follows.2. in the Ports section.4. 2.4. 56 . select the appropriate chipset family.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. 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”).1 User’s Manual In the file UEDescription.3. Under Type. Then. ..4. 3. From now on. NT12-7002 ver 1. set Type to “LG Electronics LTE Modem”.Chapter 8.3. Under Ports. If the device has a “Samsung LTE Control Port” that answers to AT commands. Also identify and map the ports to use for air interface messages (“Air Interface”) and AT communication (“AT Interface”). Launch the Manual UE Configuration utility and select your device as described in the introduction of section 8. assign the port named “.3. Click Save and then Close. 2. Activating External Equipment 3.0 57 . LG and Samsung Devices with LTE Capability 1. For a Samsung device. assign that port to “AT Interface”.4.3. assign the port named “Samsung USB LTE Adapter” to the “Ethernet Interface” function. For an LG device. TEMS Investigation will detect the Qualcomm device as being of the type you selected in step 2. USB NDIS” (or similar) to the “Ethernet Interface” function. The device is added to the list in the main dialog window. Under Ports. 8. set Type to “Samsung LTE Modem”. 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). Activating and Deactivating External Equipment in TEMS Investigation Activating External Equipment 8. provided that it comes with Windows drivers enabling an IP data connection. Click Save and then Close. 8. and all IP-related information elements will then be populated.4.1 User’s Manual 4. Map the device ports as appropriate. All IP-based services can be tested (as well as video streaming).4. 8.TEMS Investigation 14.1.4. Below is an example. • • If you want to use a device that is not officially supported.4. The device is added to the list in the main dialog window. You need to activate a device in TEMS Investigation before you can use it for data collection. 58 .3. set Type to “Data Only Device” in the Manage Device dialog. section 10. Note: A device that is going to use an NDIS data connection must have an APN assigned to it. Of HTC Touch Pro2 phones having an “Internet Sharing” function and requiring installation of TCP Router software. Limitations for Particular Devices • If the device connection must be set up using an external connection manager application. NT12-7002 ver 1. Compare section 8. do as follows: • Right-click the device on the Equipment tab and choose Deactivate from the context menu. but deactivate it in TEMS Investigation for the time being.3. The red cross disappears from each device icon to indicate that the device is now active. To activate all detected devices. right-click it on the Navigator’s Equipment tab and choose Activate from the context menu.1. See the Getting Started Manual. Activating External Equipment Note: If you have a logfile open. the Activities tab in the bottom pane is populated with the operations that you can perform manually on this device. • To activate a detected device. a phone device starts delivering idle mode reports. and a GPS device starts reporting positions.Chapter 8.2. On being activated. you can activate it in TEMS Investigation. Furthermore. only one such device at a time can be activated in TEMS Investigation (unless the connection manager supports multiple devices).4. click the Activate All button on the Navigator toolbar. Deactivating External Equipment If you want to leave an external device plugged into the PC. • 8.6.3. only one phone at a time can be activated in TEMS Investigation. when you select an activated device in the Navigator top pane. Once the device has an APN. see chapter 9. Regarding these operations.0 59 . you must close it to be able to activate equipment.4. that GPS automatically becomes the preferred one.1 However. 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). are currently not recognized by TEMS Investigation. and they will then all be detected by TEMS Investigation. and you click the Activate All button. 8.TEMS Investigation 14. and you activate one GPS. 60 . While a logfile is being recorded. while multiple GPS units can be detected and activated. • • 1. only one at a time can update the positioning-related information elements in TEMS Investigation. Managing GPS Units It is possible to have several positioning devices plugged into the PC. the “Preferred” setting cannot be changed. If no GPS is activated. If no GPS is activated in TEMS Investigation. 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.1 User’s Manual To deactivate all active devices: Click the Deactivate All button on the Equipment tab toolbar. the “Preferred” setting cannot be changed. This includes GPS units built into scanners. It is referred to as the current Preferred GPS. GPS units in phones.5. The device responsible for this will be the one tagged with an “earth” symbol on the Navigator’s Equipment tab. As long as a GPS or some other device is activated in TEMS Investigation. on the other hand. Further Features of the Navigator’s Equipment Tab The Refresh Function 8. If a device could not be matched with an AQM module. you can inspect which AQM module is matched with a device by right-clicking the PESQ Device Pairing item under the Control node. NT12-7002 ver 1. This function operates the same way whether your AQM modules are standalone or mounted in an equipment case. you can start the detection procedure over from scratch. 8.1.0 61 .1. mappings between phone IMEIs and AQM module identities are stored by TEMS Investigation in the Windows registry.2. the pairing must not have been undone using the Reset function (see section 9. Re-pairing Phones with AQM Modules When you match phones with AQM modules manually as described in section 9.3. Click the Re-pair Phones with AQM Modules button at the top of the Equipment tab. Note that for this to work. on the Activities tab. If the devices you connected to the PC were not detected properly (for whatever reason).10) before the phone was deactivated. you can recreate the same pairings automatically in TEMS Investigation. then right-click the desired GPS in the Navigator and choose Preferred GPS from the context menu.6.Chapter 8.10. The earth symbol and “Preferred GPS” tag will then be transferred to that GPS. see section 8. 8. the text “UE not paired” will be displayed in the PESQ Device Pairing dialog.1. At any time.6. Note that you must always do a refresh after using the Manual UE Configuration utility. To do this: Click the Refresh button at the top of the Equipment tab. Activating External Equipment • To select a different GPS as the preferred one. first deactivate any devices that are activated and stop logfile recording if applicable. When plugging the same phones and AQM modules into the PC on a later occasion.6.4. Note that normally there is no need to do this. only one of them will be paired with it. No check is performed that the physical connections are in fact still the same. If several phones have previously (at different times) been using the same AQM module.1 User’s Manual 8. 8. 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. 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.3. Device Detection Properties The Device Detection Properties dialog can be used to enable and disable detection of various device categories. 62 .TEMS Investigation 14. Each AQM module can only be paired with a single phone. To prevent this. If you have been working with different equipment configurations connected at various times to the same PC.6. the re-pairing will be incorrect for these phones and the AQM data will be garbage. the following holds: • • Only AQM modules that are physically present when you click the button will be paired.1.6.2. To open this dialog: Click the Device Detection Properties button at the top of the Equipment tab. For example. 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. If you make changes in this dialog.3.Chapter 8. as well as other network adapters accessible via LAN/WLAN. 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. you must enable the “Network Card” item.0 63 . Compare section 11. This means that the mappings between devices and EQ items are stored in the Windows registry. By default. Saving of the Equipment Configuration When you exit TEMS Investigation. you need to restart TEMS Investigation for the change to take effect. which would be undesirable most of the time. if a device is represented at one time by (say) EQ3. As a result. that if you wish to upload logfiles over FTP using the PC network card. TEMS Investigation does not save any information on equipment configuration in the workspace. the configuration on the Navigator’s Equipment tab is automatically saved. would always be detected as EQs in the application. detection is enabled for all device types listed except “Network Card”. The latter is disabled because otherwise the PC’s network adapter.7. NT12-7002 ver 1. Activating External Equipment The checkbox in the Enabled column determines if detection of a device type is enabled.5. Note. Such devices include phones with their IMEIs. however.1. 8. The saving extends to all devices whose hardware permits a reliable identification. Activities “subtab”). you double-click the desired item on the Activities tab to open the setup dialog associated with it. Control Functions See also chapter 21.TEMS Investigation 14. and particularly the reference material in section 20. which covers device property dialogs that provide further means of controlling devices.16. 9. you make use of the same configuration sets that you refer to in scripts. Operating and Controlling External Equipment Manually From the Navigator’s Equipment tab (bottom pane. 64 . For all manual device operations.1 User’s Manual 9. 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). right-click and choose Stop. To stop the operation. When operating devices manually. right-click the desired item on the Activities tab and choose Start from the context menu. Compare chapter 20. These operations are the subject of the present chapter. • • To execute an operation.1. Sony Ericsson C702/C905*/W760i/W995* Sams. No.) K790i/a. See the Getting Started Manual. GSM Band lock. access control NT12-7002 ver 1. W600i Control Function Samsung Infuse 4G TM506.Chapter 9. these functions are in many instances implemented as device properties instead.0 Nokia NTM3 65 . Supported for devices capable of audio quality measurement using Call Generator/MRU.1. Supported for Qualcomm chipset based UMTS devices. access control BLER target control (WCDMA) Cell lock (+ prevent) PLMN control RAT lock Reserved cells. see the table below. section 10. K600i Access class control Band lock. Regarding other control functions. 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. Z750i K800i. Operating and Controlling External Equipment Manually 9.3.1.1. See chapter 21. Note that for devices other than Xperia arc S. WCDMA Barred cells. Samsung Galaxy S 4G Xperia arc S* (Qualc. The Set Default Access Class option causes the phone to revert to its default access class settings.2. No. 9.TEMS Investigation 14. the control function dialogs contain an Apply button.) K790i/a. Functions of Dialog Buttons Besides OK and Cancel.2. The latter transfers the current dialog settings to the device.1. They are explained in section 21. just like OK.011.1.1 User’s Manual Sony Ericsson C702/C905*/W760i/W995* Sams. 66 Nokia NTM3 . Samsung Galaxy S 4G Xperia arc S* (Qualc.3. but without exiting the dialog.2. Access Class Control Here you can manipulate access class settings ( 3GPP 22. W600i Control Function Samsung Infuse 4G TM506. K600i RRC WCDMA capability control Speech codec control 9. Z750i K800i.1. chapter 4). For details.1. AT Commands The AT item is used to issue AT commands manually. What frequency bands appear here depends on what the phone has support for.5.2. If no AT configuration set exists. you need to create one. Sony Ericsson Specific Limitations If you make selections under GSM. you need to be aware of the following limitations: • • If the 850 band is selected.0 67 . Each AT command is specified in a configuration set which is identical to that referenced by an AT activity in a Service Control script. whereas Apply keeps it open.2 for details.1.4. 9.1.6. the P-900 band cannot be selected. NT12-7002 ver 1. Operating and Controlling External Equipment Manually 9. • • 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.16. Clicking OK will close the dialog. Band Lock You can restrict the phone’s use of frequency bands.Chapter 9. Only one 900 band at a time can be selected. Click either OK or Apply. 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. see section 21. See section 20.12.2. 9.1. The phone is then restricted to using only these cells. In other words.1 User’s Manual 9.2. Prevent one or several cells.1.1. The options are the same as in sections 21.2.1. reserved. This is the Allow option in the Cell Lock dialog. it can be used to control both cell selection and handover behavior. and other cells. Cell Lock The Cell Lock function spans both GSM and WCDMA.2.TEMS Investigation 14. Cell Barred Here you can modify the phone’s behavior with respect to accessing of barred.7.11 (WCDMA). 68 . The phone is then prevented from using these cells.2. 9.8.5 (GSM) and 21.8. This is the Prevent option in the Cell Lock dialog. • • Cell Lock in GSM For GSM you can do the following: Lock the phone on one or several cells1. and it has an effect in idle as well as dedicated (connected) mode. NT12-7002 ver 1. 1.Chapter 9. Operating and Controlling External Equipment Manually • To configure the set of cells to which the lock or prevent function should apply.0 69 . The word “cell” is used somewhat loosely here to mean either an ARFCN or an ARFCN + BSIC combination. See below. click the Add button: • Band selection: Here you specify a GSM band from which to select ARFCNs. select it and click Remove. The phone is then restricted to using only these cells/UARFCNs. • • Cell Lock in WCDMA For WCDMA you can do one of the following: Lock the phone to one or several cells and/or UARFCNs. Under Range selection.2.1. clicking the Add button each time.. Here. The ARFCN and the BSIC set are joined by an implicit AND. • To remove an item from the list box. 137} on the GSM 850 MHz band. 70 . A complete list of BSICs from 00 to 77 is displayed for devices that support BSIC selection. 134. you pick a single ARFCN and one or several BSICs. the phone is locked to the ARFCN set {132 . or both..1 You can define additional items as shown above to extend the ARFCN set. 9. Under Channel selection. The phone is then prevented from using these cells/UARFCNs. Below is an example of a GSM Cell Lock setup. The BSIC box is empty in the above screenshot because BSIC selection is not supported for the phone in question.8.TEMS Investigation 14. you specify a range of ARFCNs as extending from Start Channel to Stop Channel. Prevent one or several cells and/or UARFCNs. 1.1 User’s Manual • • • Range selection and Channel selection: You can define either of these. 0 71 . Operating and Controlling External Equipment Manually • To configure the set of cells/UARFCNs to which the lock or prevent function should apply.Chapter 9. Range selection is not used for WCDMA. NT12-7002 ver 1. The UARFCN and the SC set are joined by an implicit AND. you pick one UARFCN and one or several SCs. Under Channel selection. click the Add button: • • • Band selection: Here you specify a WCDMA band from which to select UARFCNs. 1.9. Here. select it and click Remove. 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. • To remove an item from the list box. 4. 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. clicking the Add button each time. The dialog is limited to 4 bytes. 9. 72 . 5}.1 User’s Manual You can define additional items as shown above to extend the cell/UARFCN set. Specifics on the NV interface are vendor proprietary and must be obtained from the vendor.TEMS Investigation 14. this is however sufficient to cover most basic NV items. Click either OK or Apply. Before an NV write. Selecting this item opens the PESQ Device Pairing dialog: • • At the outset.Chapter 9. • NT12-7002 ver 1.1. All traffic over the NV interface is logged in internal protocol reports. AQM modules do not themselves appear as EQs on the Equipment tab. select the appropriate AQM module in the combo box. After an NV write the phone is always automatically reset.1). which holds all available AQM modules. this is how you select the AQM module with which a given EQ should interact.3.10. section 10. Operating and Controlling External Equipment Manually WARNING: It is possible to corrupt the phone’s calibration parameters or otherwise damage the phone by writing the wrong value to the wrong address. The PESQ Device Pairing item is selectable only for devices supporting audio quality measurements (these are listed in the Getting Started Manual. and consequently it is deactivated in TEMS Investigation.0 73 . 9. the string “UE not paired” is displayed. PESQ Device Pairing If you are going to do audio quality measurement with a Call Generator or MRU. identified by their serial numbers. You are always prompted to confirm an NV command before it is executed. a read is always performed at the same address. To accomplish pairing. indicating that the device has not yet been paired with an AQM module. 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. whereas Apply keeps it open. Clicking OK will close the dialog. Radio Access Technology Lock (Lock on RAT) Certain devices can be locked to a particular radio access technology. the two-digit MNC “01” is entered like this: On the other hand. you can use the re-pairing function (see section 8. 74 .1.2. On later occasions.2) to recreate the same pairing automatically.2.12. 9. click the Reset button. • If you want to undo the pairing so that the device is no longer associated with any AQM module.2.1 User’s Manual You need to pair off your EQs and AQM modules manually like this the first time around.TEMS Investigation 14. you can no longer use the re-pairing function. PLMN Control This function locks the device on a PLMN. The RAT lock function works only in idle mode. There is however one difference compared to the device property setting: The control function allows you to distinguish two-digit and three-digit MNCs. Two-digit MNC are entered in the first two combo boxes. the three-digit MNC “001” (formally distinct from the preceding!) is entered as follows: 9.6. provided that the physical connections between phones and AQM modules are unchanged. For example.11. with the third box set to “-”. specified by an MCC and MNC combination just as in section 21. Note that if you unpair the devices in this way.1. 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 and you cannot view or edit any settings controlling this behavior.1. Positioning Logfiles by Pinpointing in the Map Window This section describes how to use the pinpointing technique for positioning logfile data.3. where you can either pinpoint manually or plan and create your route in advance and then walk it in a simplified fashion. If you check this box. This reduces the consumption of disk space as well as the CPU load during recording. The Pinpoint Window is dealt with in chapter 12. TEMS Investigation also has another pinpointing tool. To prevent out-of-memory issues. Pinpointing is useful in environments where GPS coverage is lacking. an internal history buffer (providing quick access to logfile data) is cleared every time you start recording a new logfile. 86 . the Pinpoint Window. meaning that you indicate your exact positions as you walk around measuring.000 messages. 11.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 pinpointing described here is done in the Map window and is manual. This function is automatic.TEMS Investigation 14. the history buffer in TEMS Investigation is automatically cleared on reaching a size of 410. The waypoint is marked with a black diamond. To record positions for measurements. and a new route segment in the form of a straight line is drawn to it from the preceding waypoint. load your floor plan or other image to be used for pinpointing into a Map window. 11. As long as a phone is activated.1. A GPS can be physically plugged in without disabling the pinpointing function. clicks on the map will be interpreted as pinpointing actions. you indicate your position by clicking on the map at regular intervals. the corresponding position is registered in the logfile as a waypoint along your route. Each time you pinpoint. You must do this before starting the logfile recording. If the image file is unpositioned. you need to position it. Now click the Start Recording button on the main window toolbar. while pinpointing is in progress.4.0 87 . Conversely. Then. pinpointing in the Map window is disabled. On the Map window toolbar.3. but it cannot be activated in the TEMS Investigation application. • Basic Pinpointing Procedures First. 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). See sections 31. you cannot activate a GPS in TEMS Investigation. Logfiles Note: If you activate a GPS in TEMS Investigation. click the Pinpoint button.1.3–31.Chapter 11. This is indicated by the cursor changing into an upward arrow whenever it enters the Map window. 2 1 3 4 5 Route Waypoints (pinpoint markers) Measurement data points NT12-7002 ver 1. ) If you pinpoint close to the edge of the Map window. When logfile recording is started (by any of the available methods). the failure will likely be registered in both logfiles. Click Stop Recording to end the recording and close the logfile. If the Start Recording and Stop Recording activities are put first and last in the loop. the signaling leading up to the establishment of the call or data session. you should try to maintain approximately the same speed throughout your route. is dropped). • Pinpoint one last time to ensure that all data is accurately positioned.1. where the tester has increased his speed considerably between waypoints 3 and 4. (Note that this is in fact not the case in the figure in section 11. Advice on Pinpointing and Recording From section 11. Now if a call fails (e. Please note that this mechanism may cause unexpected and possibly unwanted data to appear at the beginning of a logfile.000 messages.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.1 it is clear that in order for the recorded route to agree well with the actual one.4.3.g.3.1. you should pinpoint every time you change direction.2. Therefore the waypoints and connecting lines appear also when the logfile is loaded for analysis later on.3.1. and this duplication of data will skew any statistics that are computed based on it. To 88 . Consider a script where voice calls are repeated in a while loop and a new logfile is recorded in each turn. whichever is less. To optimize the performance of the Map window.1. Furthermore. the map will scroll automatically. then any two consecutive logfiles will overlap. It is wise not to replace the map during recording.5) and avoid having other presentation windows open at the same time unless you really need them. the contents of this buffer are inserted at the start of the logfile. 11. to obtain equal data densities in different locations.TEMS Investigation 14.1. you should remove all unused themes (see section 31. finish as follows: Deactivate the phone. Buffering in Connection with Logfile Recording For each connected device. for example. This is potentially useful in order to capture as much as possible of the context surrounding a device activity. 11. TEMS Investigation continuously maintains an internal buffer with the latest signaling: up to 15 seconds’ worth of it or up to 1. 2.16. insert Wait activities in your script. the measurement data). for instance by clicking the Selection Tool button on the Map window toolbar (see section 31. Alternatively.1. not the full contents of the file (that is. The metadata is displayed on the Navigator’s Logfile tab. see section 20.3.9. The remaining space on the Logfile tab is divided into subtabs whose contents are detailed in the subsections that follow. Furthermore.9).1. you can open a logfile by drag-and-drop from Windows Explorer. TEMS Discovery is used. This tab shows the logfile name at the top. Loading Logfiles for Analysis Note: To be able to load a logfile. Logfile loading is controlled from the Replay toolbar or from the Logfile menu. NT12-7002 ver 1.Chapter 11. turn to section 11. 11. Logfiles prevent logfiles from overlapping. The file must then be dropped onto the Logfile tab of the Navigator. The quickest method is to use the toolbar buttons. you must also exit Pinpoint mode there.2. Regarding the latter.2. Opening a Logfile Click the Open Logfile button to open a logfile.0 89 . One logfile at a time can be loaded in TEMS Investigation. Opening a logfile only loads logfile metadata into the application. if you have been pinpointing in the Map window. For multi-logfile analysis. you must deactivate your external equipment. 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. 11. Date and time when the recording concluded. Logfile Metadata and Statistics “General” Subtab Subject. Tags. Normal: The logfile was recorded normally.1. but it might just as well be. and an attempt was made to recover the file.2. TEMS product or component used to record the logfile.2. This can be a version of TEMS Investigation. Description Start Time Stop Time Probe Shows the contents of these fields as defined at logfile creation time. a TEMS Automatic RTU or a TEMS Pocket release. Recovered: A failure occurred during recording of this logfile. Date and time when the recording started.2.1.0) logfiles. Status Bounding Box The smallest area (defined by min/max latitude and longitude) that encompasses the route traveled in the logfile. 90 . Unknown: Value displayed for old (pre-14.TEMS Investigation 14.2.1 User’s Manual 11. for example. 11. Please note that the file may be corrupt. see section 11. The Revision field contains miscellaneous device information such as firmware revision. etc.2. Selecting a device populates the fields at the bottom (Capabilities.0 91 . 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.3.2. NT12-7002 ver 1.2.2.) just as is done in live mode for active devices on the Navigator’s top-level Equipment tab (Information subtab: see section 8.Chapter 11. No data from that device will then be loaded into the presentation windows when you load the full logfile contents. Logfiles 11.2). “Equipment” Subtab This subtab holds all devices that were activated in TEMS Investigation during recording of the logfile. Filter by Equipment Filter by Activity You can show all activities or only those of a single EQ. etc. “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. You can group and/or filter the contents in various ways: Group by Not Grouped: The chronology is given in a single table.1 User’s Manual 11.). Result: The chronology is broken into separate tables for each possible outcome (Succeeded. Failed. Activity: The chronology is broken into separate tables for each type of activity performed.2.2. 92 .3. You can show all activities or only those of a particular type. which shows equipment status and the outcome of the last activity performed during the execution of a script.4.2. and outcome of the activity. execution.2. • Click the Back link to return to the activity listing. Compare the Service Control Monitor (section 20.3. “Statistics” Subtab NT12-7002 ver 1.0 93 . Below are shown a couple of extracts from the description of an FTP Download activity.1). Logfiles Clicking an activity link opens a detailed description of the configuration.15.Chapter 11. 11. • • • • • • TEMS Investigation 6. When you are done analyzing a logfile. 7. 3. Click Fast forward once more to resume logfile loading.x1. 6. 8. 10.x1.3. Filter by Equipment You can show statistics for all devices taken together or for one selected device.1.x1.2.3.x1. See section 4.x TEMS DriveTester GSM–TDMA 1. 11.TEMS Investigation 14. Loading Logfiles from Other Sources TEMS Investigation can load and analyze logfiles from the TEMS products listed below.3. 11. 5. which computes similar statistics in testing mode while a script is executing.4.x.2).x.x. click the Close Logfile button to close it. You can click the same button again. now labeled Stop. Compare the Service Control Monitor (section 20. the Play section of the status bar shows the name of the file and indicates the percentage of the file that has been loaded.x.2. Loading Logfile Contents Click the Fast forward button to load the logfile measurement data into the presentation windows.x TEMS Investigation WCDMA 3.3.15.1 User’s Manual This tab provides statistics on the outcomes of activities performed by the devices during recording. Play Section of Status Bar While a logfile is being loaded.x TEMS Investigation EDGE 1.x and later TEMS Investigation GSM 5.x 2 94 . 11.x (GSM logfiles) TEMS Pocket 12. The data loaded thus far is then displayed in the presentation windows. 4. 2.x. to halt the loading of the logfile. 11. x (MTU logfiles recorded with GSM-only MTUs) TEMS Automatic 3.7. 11. choose Configuration File Transfer.x.5. described in section 26.4. 6. 7. Logfile Transfer via FTP TEMS Investigation has a function for uploading logfiles via FTP according to preconfigured FTP server settings.0 95 . Please note that logfiles from these TEMS Pocket versions must first be converted using a PC utility that is delivered with that version.x (any MTU and TEMS Pocket Remote logfiles) TEMS Automatic 5.5. 2. files logged by the scanner itself) MTR files (GSM. on the Menu tab of the Navigator.2.0. TEMS Pocket 9.10) 11. Note especially the search functions in message windows.x. Viewing Logfile Contents Everything about data presentation is dealt with in chapters 23–31. NT12-7002 ver 1. 11.x.1.e.Chapter 11. 1. see the Informations Elements and Events volume. section 3. Logfiles • • • • TEMS Automatic 9. click the Settings button. 2.5 TEMS Investigation can also read • • • • EFEM logfiles from Motorola phones MDM logfiles from Qualcomm chipset based devices logfiles from Anritsu ML8720 scanners (i. • • Setting Up Logfile Transfers To set up FTP logfile transfers.x logfiles cannot be loaded in TEMS Investigation. 8.x (any MTU logfiles) TEMS Automatic 4. In the window that appears. The local directory on the PC from which logfiles will be uploaded. if required. The logfile names are augmented with a timestamp indicating the time of upload: _tfu__hh_mm_ss (“tfu” means “TEMS file upload”). User.TEMS Investigation 14. Password Server Address Port Server Logfile Directory Local Logfile Directory 96 . IP address or host name of FTP server. The FTP server port to use. Path to the directory on the FTP server where the uploaded logfiles will be stored (in a subdirectory named according to the current date).1.1 User’s Manual 11. FTP Server Settings User name and password on the FTP server.1.5. Equipment Here you select the device to use for logfile transfer. For a cellular network device. logfiles that have been uploaded are moved to a subdirectory Complete that is created automatically for the purpose.2. they are deleted from the local directory..1.5. If the option is not checked.Chapter 11. or over an Ethernet or WLAN connection.3. 11. If Start transfer when logfile is closed is checked.3.0 97 . Logfiles 11. Logfile Options If this is checked.16.3.1. NT12-7002 ver 1.1. Click the Connection parameters button to open the dialog for creating a Network Connect configuration set. Note that you do not need to have the device activated in TEMS Investigation to be able to transfer files. you initiate transfers manually as described in section 11. Note: Transfer over Ethernet or WLAN requires that detection of network adapters be enabled (it is disabled by default). 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. Start transfer when logfile is closed [. Using some suitable third-party software. you need to supply parameters for connecting to the network. this behavior is preselected and cannot be changed.2. Move: Within the local directory. you can then compute the checksum for the uploaded file and confirm that it agrees with that of the original.5.6. The parameters of this configuration are gone through in section 20.5.3. • • Delete: After logfiles have been uploaded. The transfer can be done over a cellular network. every logfile will be transferred immediately after the recording has ended..] files after transfer Generate MD5 checksum If checked. See section 8. select it in the list box and click Load. TEMS Automatic logfiles.1. Starting Logfile Transfers This section is applicable only when the option Start transfer when logfile is closed described in section 11. • • • To save a setup. see the Technical Reference. for example. The text export format is described in detail in the Technical Reference. can be exported in this format.1 User’s Manual 11. (If the file transfer is automatic. type a name for it in the Name box and click Save.0 (Interchange or Tab format) ArcView Shapefile: about version.5. In the File Transfer window.2 is not set. click the Start button. there is no explicit handling of setup files. • • In the File Transfer Settings dialog.TEMS Investigation 14. too.2. then click OK.4. • Exporting Logfiles in Other Formats Logfiles can be exported in the following formats: Text file with tab delimited data (suitable for processing in. 98 .5.2 Marconi Planet DMS 3. a spreadsheet application). Setup You can save all settings made in this dialog as a file transfer setup. In this case you start the logfile transfer manually on each occasion. MapInfo 3. this button is named Auto and grayed out. section 9. 11.1. chapter 8.) The progress bar will indicate the progress of the transfer. define or select the setup you want to use. To load a previously saved setup. See the Technical Reference. To delete a setup.1 Ethereal (Wireshark) MDM • • • • • Some of these formats contain multiple files for each logfile. The setup is added in the list box.6. chapter 9 for details.5. 11. The setups are maintained in the dialog. select it in the list box and click Delete. click Add.6. choose Export Logfile. ArcView.1. From the Logfile menu. A separate window named TEMS Export is launched. see section 11. This is necessary in order for the export to work properly. The Add Export Order dialog appears: Format Select the output format for your logfiles. deactivate any external devices that are currently activated. (This is not a logfile export format in the strict sense. the export file will contain only a header and no route data. If there is no positioning information in the logfile.7. Logfile export can be done either from the TEMS Investigation user interface or from a Command Prompt. Logfiles Note: Export in MapInfo. Regarding the choice PESQ merge.0 99 .6. or Planet format requires that the data be positioned.) Input files Type or select the logfile or logfiles you want to export. • • Preparing an Export Order First.4. see section 11. In the TEMS Export window. For the latter possibility. NT12-7002 ver 1. 11.Chapter 11. Merge output Directory Prefix Suffix Extension The directory where the export files are written.1 User’s Manual Cell files Click this button to include one or several cell files in the export. a dialog appears whose contents partly depend on the format chosen. each logfile is exported separately. see section 11. etc. File extension for export file. (Logfiles are simply concatenated. Here you select which information elements to include in the export: 100 .2. as described in the Technical Reference.).2 below. 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. including the plain-text format. chapter 9. 11. Selecting Information Elements to Export The Information Elements tab is common to many of the formats.1. Editable only for certain formats. Export to other formats produces files with fixed extensions.6. there is no sorting of messages by timestamps. If the Merge output option is unchecked. If you are exporting several logfiles and this option is checked. and the export file set simply retains the name of the logfile. • Now click the Setup button to specify details of the export.6. Specifying the Contents of Export Files On clicking the Setup button. To the export file name you can optionally add a descriptive prefix.6. To the export file name you can optionally add a descriptive suffix. all logfiles will be merged into a single set of export files.2.) The name given to the export files depends on the ordering of logfiles in the Input files box. 11.TEMS Investigation 14. select it in the Available IEs list and click the “>” button to move it to the Selected IEs list. but only the component with the lowest argument. you can restrict the export of a selected IE to a single device. select the desired item and click the Edit button above the box. click “>” again. • To export an element. By default the items selected are picked from all phones. choose that category in the combo box in the Available IEs section. you must edit the item. Repeat for all components you want to export. you do not get the whole element at once. To remove an item from the Selected IEs box.g. To select the component with the next higher argument. the Data category). you can also edit the following settings: NT12-7002 ver 1. see Editing the Selected Items below. If the element has arguments. For all export formats except tab-delimited text. click “<<”. To export an information element from a different category (e. For all export formats. To export the item only from specified phones.0 101 . The Edit IE dialog appears. or change the IE argument (where one exists). To clear the entire Selected IEs box. Elements from different categories can be freely mixed in export files. From information elements with arguments you pick one component at a time. • • • Editing the Selected Items To edit an information element: • In the Selected IEs box. Logfiles You choose each individual element separately. By default a chosen item is exported from all devices that report it.Chapter 11. select the item and click “<”. TEMS Investigation 14. whereas for the remaining formats the string must be numeric (e. By default the text export file also contains message information. Optionally. but in different files. You can rearrange the items by selecting them and moving them using the Up and Dn buttons. Text File Specific Settings Besides your chosen information elements. any string is accepted.1 User’s Manual • NAME field: This is the IE column heading in the export file.2. 11. (You might want to make this string shorter.8. it will be written in the export file whenever the IE does not have a valid value. “-1”). including user-inserted filemarks. The choice is made on the Options tab: 102 . By default. the text export file always contains data on events. Note also that the NAME and NODATA settings are not saved along with other logfile export settings. There are no user settings relating to the event data. • As long as these settings have not been edited.g. the IE name is preceded by an asterisk (*) in the Selected IEs box.2.6. “999”. See section 11.) NODATA field: If you enter a string here. For Planet.6. the export can be reduced in order to decrease the duplication of data and the number of lines in the export file. the column heading string consists of the IE name.2. Arranging Items in the Export Files The order of the items in the Selected IEs list will also be the order in which they come in the export files. and Hexadecimal String are excluded from the export file. chapter 8.. (The Event column is kept. The export file is reduced in two ways: • The columns Frame Number. All other standard columns are always included. Check a column to include it.0 103 .. In addition there will be one column for each selected IE or IE component. IE values are written out only if they have changed since the previous message. Logfiles Full message information. • Event information Governs whether the Event Info column is included in the export. NT12-7002 ver 1. If you check Show changed IE values only.. All messages are kept. This makes for a considerable reduction of the export file size. The following columns are optional: Message Type.Chapter 11. as is the Event Info column provided that the Event information checkbox below is checked. If the box is not checked. and Hexadecimal String. Message ID. Message ID.) Messages not triggering an event and containing no changed IE values are wholly excluded.. Events and filemarks only. all IE values are written for every message. see the Technical Reference. 1 User’s Manual Message options Check the relevant boxes in order to have Layer 2 messages. Layer 3 messages. By default all reports are exported.3.6.txt. 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. MapInfo Specific Settings For MapInfo export (whether to Interchange or Tab format). and phones’ mode reports exported as unabridged plain text to a common separate file whose name ends in _textexp.TEMS Investigation 14. 11.2. 104 . • • • Include file name in file Check this to include the file name in the export files.. section 9. uplink. section 9. Note. Events This setting governs the export of events. and that the symbol used is not one of the default TEMS Investigation event symbols.Chapter 11. that there is no differentiation of event types.1. Check this to include information on Layer 3 and Layer 2 messages in the export files. uplink. downlink) Message name Hexadecimal string Extension (containing cause values) Do not export events: No event information is exported.2.4.. NT12-7002 ver 1. see the Technical Reference. Export events and plot. ArcView Specific Settings Export message information. 11. The following data is added (one column for each item): • • • • Message direction (internal. For details on MapInfo output. downlink) Message name Hexadecimal string For details on ArcView output....: Events are exported.2.. see the Technical Reference.. The following data is added (one column for each item): • • • Message direction (internal.: Events are exported. however.6. Logfiles Export message information.0 105 . Check this to include information on Layer 3 and Layer 2 messages in the export files. but no event-specific symbol is used in MapInfo when plotting on a map. Export events but do not plot.. and a unique symbol is used when plotting in MapInfo to distinguish events from other data. 11. .2. section 9. MDM Specific Settings MDM export is intended for logfiles recorded with Qualcomm chipset based devices. Ethereal (Wireshark) Specific Settings The export encompasses all of the logfile content.3. section 9. • 106 . section 9. For details on MDM output. Marconi Planet Specific Settings Export message information.. you may want to save the setup for future use. click Load and locate the setup file. 11. Check this to include information on Layer 3 and Layer 2 messages in the export file.1 User’s Manual 11.6. To load a previously saved setup in the Setup dialog. The Export message information checkbox must be checked.5. The export encompasses all Qualcomm-specific air interface messages in the logfile.6. Saving and Loading Export Setups When you are done specifying the export. see the Technical Reference. The following data is added (one column for each item): • • Message direction (internal. 11.6.2. • In the Setup dialog.6. downlink) Message name For details on Marconi Planet output. For details on Ethereal output. The file extension will depend on the format (for example.TEMS Investigation 14.. The Export message information checkbox must be checked.2.8. otherwise the output file will be empty. see the Technical Reference. otherwise the output files will be empty.5.2. click Save and store the file where appropriate.7. uplink.4.tex for a text-format export setup).6. see the Technical Reference. 6. the NAME and NODATA settings for information elements (see the introduction of section 11. A summary of the export execution appears in a popup window (“Export Result”). which is found under <TEMS Investigation install dir>\Application.0 107 .4. 11. /IF and /InputFiles can be used interchangeably. for example. To abort the execution of the export orders. Logfiles However.6.6. 11. right-click and choose Abort from the context menu. The command has the following syntax. • • To start executing the export orders. Use semicolons (.Chapter 11. Executing Export Orders All the export orders you have defined are listed in the Export Logfile window.ExportTool.6. They are instead written to DBF files that are found in the Settings directory beneath the TEMS Investigation installation directory. Wildcards can be used in the file name in regular DOS fashion.) to separate files.exe.ExportTool.2) are not saved in the above-mentioned files. 11.1. Command Line Controlled Logfile Export Logfile export can alternatively be initiated from a Command Prompt by running the file TEMS.4.3. Mandatory Command Line Switches /IF (or: /InputFiles) Equivalent to Input files field in logfile export dialog. NT12-7002 ver 1. where optional parts are placed within square brackets [ ]: TEMS.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. right-click and choose Start from the context menu (or click the Start button in the window). mex" /EF "MapInfo Tab-file" /CFG "C:\Path\filename." Exports all TEMS Investigation logfiles found in the specified directory. under Windows 7: C:\Users\<user name>\AppData\Local\Temp).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.trp" Exports the logfiles listed.6. Here is how configuration file types match up with export formats (/EF): • • • • • /EF "Text file" /CFG "C:\Path\filename. 108 .4. Equivalent to Directory field in logfile export dialog. 11. created by saving a setup in the logfile export dialog as described in section 11. • /IF "C:\ExpTest1\*.1 User’s Manual Examples: • /IF "C:\ExpTest\0825_01.avx" /EF "Marconi Planet-file" /CFG "C:\Path\filename.TEMS Investigation 14.trp. • /IF "C:\ExpTest\*. compare section 11.2. Most importantly.6. a configuration file is required to have any information element values exported.mex" /EF "ArcView shape-file" /CFG "C:\Path\filename. This parameter is optional but strongly recommended for all export formats that have a configuration.tex" /EF "MapInfo Interchange (mif)" /CFG "C:\Path\filename. /CFG (or: /ConfigurationFile) Logfile export configuration file.6. the location where the export files are written is indicated in a file batch_result.pex" No configuration file exists for export to MDM or Ethereal. nor for PESQ uplink data merge. Optional Command Line Switches /OD (or: /OutputDirectory) Full path of output directory.1.2.8.C:\ExpTest2\*. If you do not specify an output directory.C:\ExpTest\0825_02.2.C:\ExpTest3\0825_*1.txt which is found in the Temp directory of your Windows user (for example. If this parameter is omitted. Logfiles /CF (or: /CellFiles) Equivalent to selecting cell files by clicking the Cell files button in the logfile export dialog. the name of each exported logfile will be printed in the Command Prompt window. use semicolon (. /MO (or: /MergeOutput) Including this switch is equivalent to checking the Merge output checkbox in the logfile export dialog. If you specify several cell files. 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.) as delimiter. /V (or: /Verbose) If you include this switch.Chapter 11. /S (or: /Suffix) Equivalent to Suffix field in logfile export dialog. NT12-7002 ver 1. /EF (or: /ExportFormat) Equivalent to Format setting in logfile export dialog. The format string needs to be enclosed within double quotes (" "). the export is done in text format.0 109 . Note again that for some export formats you cannot override the default extension. /E (or: /Extension) Equivalent to Extension field in logfile export dialog. The XML files are given random four-digit numbers as names. uplink AQM data is computed by a Call Generator and output in XML files. for example: • • • by setting up access to the Call Generator output directory as a network drive by downloading the uplink data files via FTP by copying the files onto a USB stick or a CD/DVD. No special tool is currently provided in TEMS Investigation for accessing the uplink AQM data. Example Below is an example of a logfile export command: TEMS.1 User’s Manual 11. you need to export the TEMS Investigation logfile with Format set to PESQ merge. 11.trp format) that includes both uplink and downlink AQM data. This could be done in a number of ways. See the screenshot in section 11.TEMS Investigation 14.7. 11.tex. The output is stored under C:\ExpTest\Export. Note: When downloading the uplink data files it is important to preserve the Call Generator directory structure. since the merge algorithm relies on this structure to locate the correct files. 110 .2. by default under C:\TIPESQ in a subfolder named <yyyymmdd><phone number>. using the setup described in the configuration file GsmN. The output is a new logfile (still in *.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).4. the files must be collected manually from the Call Generator.6.exe /IF "C:\ExpTest\0825*" /OD C:\ExpTest\Export /V /CFG "C:\ExpTest\GsmN. To perform the data merge. Merging Uplink AQM Data into Logfiles (UMTS) As described in chapter 35.7.1. This uplink data needs to be inserted in each logfile (*.ExportTool.trp) recorded with TEMS Investigation.3. Retrieving Uplink AQM Data The uplink AQM data is stored as XML files on the Call Generator PC.7. trp. Click the Setup button next to the Format combo box.7.6. To this end. click the Browse dir button next to the Directory box and navigate to the desired directory. Click OK to exit the Add Export Order dialog. Back in the Add Export Order dialog. choose Export Logfile.Chapter 11. select the TEMS Investigation logfiles (*. An example is shown below: UL AQM root directory • • • Click OK. • Preparing and Performing a Merge From the Logfile menu..1.” button and locate the root directory holding all XML files (the level above the directories named by date). Logfiles 11.. You are now ready to perform the merge. The name of each output logfile will consist of the original name plus the suffix “-AQM”. • • • The output files will remain TEMS Investigation logfiles with extension .1.0 111 . Be sure not to check the Merge output option. Click Add. • • Under Format.2. Click the “.6. select PESQ merge.5 s backwards in time so that each score aligns with the speech sentence for which it was computed. Compare section 11. (Exception: The first score in each pair of Frequent AQM scores needs to be moved a further 2. under Input files. To compensate for the delay in computing the AQM data. then OK once more. The Add Export Order dialog appears.3. See section 11. What happens during the merge is that the uplink AQM data is integrated into the logfile.75 s NT12-7002 ver 1. You also need to specify where the merged output files should be written.trp) containing the downlink AQM data. all entries being sorted by their timestamps.7. the logfile export function also moves the downlink data 5. Execute the AQM export order from the Export Logfile window as described in section 11. A dialog appears in which you point out where the uplink AQM data files are located (one XML file for each AQM call). It is possible to perform a merge with an incomplete set of uplink data files. For full details of logfile report contents and format. or 8. From one or several logfiles you can generate a report in HTML format which summarizes the data in the logfiles. and to repeat the merge procedure later on with further uplink data supplemented. see the Technical Reference. If any external devices are activated.8.) The uplink data is simply inserted into the logfiles at the correct points in time. chapter 10.25 s in total. Generating Logfile Reports Note: Reporting functions are also available in TEMS Discovery. For in-depth coverage of the computation of AQM data. To prepare a logfile report. see the document “AQM in TEMS Products (Including PESQ and POLQA)” which is found on the installation CD in the subdirectory Documents. If one of these files is currently open. including timing issues. • • The logfiles to be included in the report cannot be open while the report is generated. This is necessary in order for the report generation to work properly. This dialog appears: 112 . 11. 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. close it.TEMS Investigation 14. deactivate them.1 User’s Manual backwards. Logfiles • • • First.0 113 .” to browse your file system. IE Tab NT12-7002 ver 1. Those that you choose are listed in the Files box.Chapter 11. or click the button labeled “. Enter a path. Now click Properties to assemble the contents of the report. choose the logfile or logfiles on which to base the report. 11..1. Specify an output directory for the report. Click Add and browse for the files. A multi-tab dialog appears..8. All thresholded information elements listed will also have their distributions visualized in bar charts. A number of thresholds are predefined in the dialog. Specify the two thresholds. Check a cellular technology to use all thresholds defined for that technology. as is seen in the above screenshot. you can also define your own thresholds. and uncheck the others. Check those that you wish to use. 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. In the report. 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. 114 . It will contain statistics of the type “Percentage of measurement points with Active Set CPICH Ec/No below –15 dB”. click the Add button.1 User’s Manual The report can compare information element values with thresholds. • • • Choose an information element. Adding User-defined Thresholds • To add a pair of thresholds.TEMS Investigation 14. Choose an argument (where applicable). Editing Thresholds • To edit a threshold.Chapter 11. Customizing Value Ranges The Ranges column is used to customize the drawing of distribution charts (see the Technical Reference. Editing Arguments • To edit the argument of the information element (where one exists). double-click it and enter the desired new value. and the distribution charts are drawn in a preconfigured manner. NT12-7002 ver 1.2. 11. double-click it and enter the desired new value.0 115 .4). Modify the value ranges in the dialog that appears. Deleting Thresholds • To delete a threshold pair. Events Tab The report has a section with event statistics.8. section 10. the distribution chart will be drawn with one bar for each range: • • • Select the desired information element. By default no ranges are set. select it and click the Delete button. Logfiles • • Click Add to add this threshold pair to the list and keep the Add Threshold dialog open. On this tab you choose what event types to include in these statistics. If you set up your own value ranges for an IE. Click OK to add this threshold pair to the list and close the Add Threshold dialog. Click the Edit Range button. 8. In this step you choose what scan data to present in the report. The algorithm counts all events. By default all device channels (“MS1”.TEMS Investigation 14. • Mobiles Tab Check the external devices whose data you want to include in the report. This dialog appears: 116 .4. Therefore. GPS data. etc. • First. and leave the rest unchecked. This is also the default setting. click the Define channels button in order to populate the “Available” box. if available. 11.) used to record the logfile will be checked. Note: The ranking of cells in the report (“Worst Cell Indication”) is partially based on the number of events occurring in the cell.3. “MS2”. not only those signifying failures. only failure events should be checked in this step. Press Ctrl + A to select all events.8. “DC1”. press Ctrl + A again to deselect all events. Scanned Channels Tab Note: The settings on this tab are applicable only if your logfiles contain scan data. in order for the cell ranking to make sense. 11.1 User’s Manual • Check the events you want to include. is included implicitly. – – – • Click OK to return to the Report Properties dialog. For LTE. NT12-7002 ver 1. then check the desired Cell Identities in the list box.Chapter 11. The PN selection applies to all RF channels within the chosen range. For CDMA. For WCDMA. – – For GSM. then check the desired CPIs in the list box. Logfiles • In the combo box at the top. specify a UARFCN range under “Lower limit” and “Upper limit”. The scrambling code selection applies to all UARFCNs within the chosen range. then check the desired scrambling codes in the list box. specify an RF channel range under “Lower limit” and “Upper limit”. The cell selection applies to all EARFCNs within the chosen range. select the band of interest. then check the desired PNs in the list box.0 117 . specify a UARFCN range under “Lower limit” and “Upper limit”. specify an EARFCN range under “Lower limit” and “Upper limit”. WCDMA: m[f] means scrambling code m on UARFCN f. 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. just check the desired ARFCNs in the list box. The CPI selection applies to all UARFCNs within the chosen range. For TD-SCDMA. the report will contain signal strength statistics (mean.1\GeneratedReports. Prepared by Logfile information: Logfile names and used equipment 118 . • Generating the Report In the Report wizard. • • In the Report Properties dialog.TEMS Investigation 14. CDMA: m[f] means PN m on RF channel f. min. TD-SCDMA: m[f] means CPI m on UARFCN f. The file extension is . User Details Tab Here you can type a user name and a report number which will be printed in the report header.1 User’s Manual • • • • LTE: m[f] means Cell Identity m on EARFCN f. click Finish.8. Report Contents The logfile report has the following main sections (see the Technical Reference. Saving and Loading Report Setups When you are done specifying the report contents. The averaging takes place in the mW domain. click Load and locate the setup file.6.8.8. 11. The report will be stored under [My] Documents\TEMS Product Files\TEMS Investigation 14. median. you may want to save the setup for future use. chapter 10 for a complete description): • • Header: Date. For each selected item.8. 11.7. Time. 11. Move the items that you wish to present from the Available box to the Selected box.rpt.5. max) and a bar chart. click Save and store the file where appropriate.8. To load a previously saved setup into the Report Properties dialog. 11. 0 119 . Logfiles • • • • • • Worst cell indication: Ranking of cells based on thresholds crossed and events triggered Thresholds: Detailed statistics on how often and in what cells each threshold has been crossed Events: Statistics on events Scan data: Statistics on the signal strength of scanned channels (if any) Distribution charts for thresholded parameters Distribution charts for scan data (if any) The output involving cell data naturally requires a cell file in order to be generated.Chapter 11. NT12-7002 ver 1. 12. but please note that image files larger than 75 MB (pixel width × pixel height × 4 > 7. the iBwave format is always used.TEMS Investigation 14.1.5 × 107) will be displayed at reduced resolution in the Pinpoint Window. The Pinpoint Window supports loading of map sets in the iBwave container format (as does TEMS Pocket) and in a number of other formats. Such logfiles incorporate the map set used.1.3).1. Logfiles that you record in the Pinpoint Window are created in regular TEMS Investigation format (*. Map images of arbitrary size can be loaded. Introduction The Pinpoint Window is designed to further facilitate pinpointing of indoor routes by enabling the construction and use of pre-planned routes.trp).2. Please note that the Pinpoint Window is not a subtype of the Map window (see chapter 31) but distinct from it. The Pinpoint Window 12. • Creating Planned Routes Opening a Map Set Click the Open button and browse to select a map set file. similar to those in TEMS Pocket 11. 12.x and later. Alternatively. Supported File Formats Holding Map Sets Some of these file types are pure map set formats.1 User’s Manual 12.2. while others may include a map set in addition to their regular contents.1. 12. When you save a map set that you have modified in the Pinpoint Window (by defining planned routes in it). The operations in the Pinpoint Window are also wholly distinct from the pinpointing performed in a Map window.2.1. which is always manual (see section 11. you can also pinpoint manually in this window. 120 . 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 which also accommodates the auxiliary pinpoint data.3). however. using the Back and Forward buttons. This “freehand” pinpointing is similar to the procedure used in a Map window (described in section 11. 12. Pinpointing Without a Planned Route In the Pinpoint Window you can alternatively place waypoints manually to indicate your trajectory as you go. Here is how to do manual pinpointing: • • Load the map set you want to use by clicking the Open button.TEMS Investigation 14. The following controls appear in the pop-out pane: 130 . click the “No Route” item. Please bear in mind. The logfile is created in the regular TEMS Investigation logfile format (*. Skipping Waypoints of a Route You can skip waypoints without committing to them.3. for instance because it is behind a locked door. Instead of selecting a route. This initiates recording of a logfile.1 User’s Manual 12.1.4. A “shortcut” might thus be created that goes through walls or other obstacles – compare the advice given in section 12. This is useful if you cannot get to a waypoint. the measurements will be positioned along a straight line between the adjacent retained waypoints. • Click the Start button.2. that this effectively removes the waypoint from the track when it comes to the positioning of the recorded data.trp).3 on the preparation of planned routes. without following a planned route. except that it always involves logfile recording.3. and you are prompted for a location in which to save it. pinpointing at regular intervals and whenever you change direction. (When you perform a commit. Mouse: In this mode. as explained above. As soon as you have started recording. Stop button: Stop pinpointing and close the logfile. you simply click a spot on the map to place a waypoint in that spot. These modes are just two different methods of placing waypoints.Chapter 12. Continue along your intended trajectory. Pan the map so that the pin marks your current position.) • Each time you place a new waypoint it is highlighted. This button is used only in Crosshair mode. a large redheaded pin with a crosshair appears at a fixed position in the map view. they do not affect the positioning itself or how it is represented in the logfile. Crosshair: In this mode. NT12-7002 ver 1. The Pinpoint Window Control Function The Mouse and Crosshair buttons are used to select pinpointing mode. all measurements collected since your previous commit are positioned in a straight line between the two waypoints. Commit button: Place a waypoint at the current position. The button is then always labeled with the sequence number of the next waypoint to be added. click the Crosshair button. A pin with a green head is drawn in the map view to mark the spot. You may of course need to pan the map first to bring the relevant part of it into view. The waypoint is automatically committed. and the map is recentered around it.0 131 . • • The default pinpointing mode is Mouse. All measurements collected so far are positioned at that waypoint. pinpoint once to indicate your starting position. You can toggle between the two modes at any time. then click the Commit button to place a waypoint there. If you prefer Crosshair mode instead. Also keep a steady pace between waypoints. 2.1 User’s Manual Each time you place a new waypoint. Note also that you can have your walked track plotted in a Map window.TEMS Investigation 14. click Stop.5. Relation to Other TEMS Investigation Functions Data Presentation 12. you can of course have any presentation windows open side by side with the Pinpoint Window and inspect measurement data there. a Pinpoint Added event is triggered. its sequence number and time of creation (“hh:mm:ss”) are displayed. If you do. 12.1. This closes the logfile.5. Naturally you can change that name if desired. Coexistence Issues While you are recording a logfile in the Pinpoint Window (whether pinpointing manually or walking along a pre-planned route). 12.5. the new route will appear in the popout pane listing as “Unnamed Route <n>”. Below the Commit button in the pop-out pane is a stack of boxed items representing your latest waypoints. For each waypoint. Currently there is no presentation of information elements or other measurement data in the Pinpoint Window. You are also asked whether you want to save the waypoints you have placed as a route in the map set. However. in live mode as well as during analysis. the following applies: 132 . • When you are done with your test. Chapter 12. it will keep the positioning source that was preferred in TEMS Investigation when the recording began.0 133 . A Start Recording activity in a script will start a new logfile. However. and not by any other source. but note again that the positioning will be governed by your actions in the Pinpoint Window. all methods of logfile recording can be used independently without restrictions. but the positioning source is not unique to each recording. Having a GPS activated in TEMS Investigation does not affect the Pinpoint Window in any way. NT12-7002 ver 1. The Pinpoint Window • You can start recording of other logfiles by other means (using the manual controls or running a script). • • • Conversely. these recordings will automatically be positioned according to the Pinpoint Window waypoints. so that any subsequent recordings initiated while the pinpointing is still active will be positioned according to the pinpointing data. Clicking Stop Recording on the main window toolbar has no effect on the Pinpoint Window. Scripts can run independently of what is done in the Pinpoint Window. In summary. while logfile recording initiated by other means is in progress. The ongoing recording will not be affected. starting to record in the Pinpoint Window automatically redefines the preferred positioning source as pinpointing. However. it is possible to start another recording in the Pinpoint Window. 1 User’s Manual 13. and they are gone through in chapters 14–19.Scan . The configuration dialogs are the same in both cases. Scripted Scanning Scripted scanning works just like scripting of other activities and does not require special comment. that scripted scanning is currently available for a subset of supported scanning devices: R&S TSMW Manual Scripted 13.16. Scanning: General Scanning can be done either • • manually from the Navigator’s Equipment tab.1. 134 Transcom Anritsu PCTel SRU DRT Scanning Type/ Scanning Device Sony Ericsson Andrew i. however.5).TEMS Investigation 14. or as an activity in a Service Control script. Note. please refer to chapter 20 (the scan activities are listed in section 20. See chapter 8. the Activities subtab is populated.0 135 . and from the context menu select the desired configuration set among those in existence. and select Configuration Sets from the context menu. you need to activate the device you want to scan with (if it is not already activated). expand the Scan node. • • Right-click the scanning method you want to use. Expand this node to view a list of the scanning methods that this device supports. Performing a Scan Manually With suitable configuration sets already defined. This opens a dialog where you define a setup for the selected scanning method. Scanning: General 13.1. and from the context menu select Start. select the device to scan with. All details are covered in subsequent chapters (14–19). specifically. For a scanning-capable device. Right-click the scanning method you want to use.2. from the Activities subtab in the bottom pane. Once the device has been activated. The dialog contents depend on the technology and scanning method chosen as well as on the make and model of the scanning device. NT12-7002 ver 1. On the Activities subtab. Right-click the scanning method item again. to be able to access the scanning configuration dialogs. 13. 13.2. Manual Scanning Setting Up a Scan Manually Scanning tasks can be set up manually on the Navigator’s Equipment tab.2. the available activities will include ones collected under a Scan node. • First. you can initiate a scan manually as follows: • • • • On the Navigator’s Equipment tab.Chapter 13.2. • 136 . Presenting Scan Data The output of scans is primarily intended to be displayed in a suite of readymade bar charts and other windows. However.4. it will be indicated in the top pane of the Equipment tab for the device that is busy scanning. 13. • • Technical Data on Scanning Devices A Sony Ericsson phone cannot act as a regular phone while it is scanning. create a new logfile as described in section 11. and the output from all of these can be displayed in parallel. The information elements of interest are all found in the Information Elements and Events volume.1. right-click the scanning method being executed. 13.4.1 User’s Manual While the scan is ongoing. included on the installation CD in the subdirectory Documents. go to the Activities subtab again. Frequency band support is determined by the scanning device and by the antennas.2. For example. • To stop scanning. and select Stop. see the Getting Started Manual. It cannot engage in voice/video calls or data services during this time. section 10.1. Recording Scan Data Manually To record data from a manually initiated scan.3. 13. It is possible to scan with several devices simultaneously.TEMS Investigation 14. since all scan data is available in information elements. you are free to present it in any presentation window. scan data can be displayed in status windows of your own design. 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. For band support in connectable scanning devices.3. The scanning presentation windows are fully synchronized with the rest of the application. Under the Scan node. Only the scanner measurement capacity places a limit on the possibilities of handling several scanning tasks in parallel.2. (The DRT scanner can produce more data than this. a WCDMA SCH timeslot scan at maximum resolution may require the full resources of the PCTel scanner. Notes on Scanner Multitasking PCTel Scanners Within a cellular technology.7. For further information on third-party scanning devices. 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.Chapter 13.) Again the limit is expressed in terms of measurement points.5. TEMS Investigation sets a limit on the amount of scan data it will accept. DRT Scanners For a DRT scanner.5. For example. 13. Scanning: General • Some technical data on PCTel scanners and antennas used with them is provided in the Getting Started Manual. 13.3. A PCTel scanner’s measurement capacity is indicated as a number of measurement points. The resource percentage selected is the minimum that the scan task is guaranteed to get when executed. but the data volume would then become unmanageably large. (There is no inverse mechanism treating the selected resource percentages as “opening bids” that can be pared down at execution time. you are continuously notified in the setup dialog of how many measurement points that remain. and the setup dialog keeps track of the number of measurement points that remain to be allocated. 13. scanning methods are conceptually independent.5. and they can be run concurrently by PCTel scanners.) NT12-7002 ver 1. please consult documentation from the respective suppliers.5. As you set up the scanning tasks. then the actual resource use will be raised automatically if the scan tasks require it. so that it cannot perform any other tasks at the same time.1.2.0 137 .5. If the scan tasks that are running have a combined resource allocation of less than 100% in their setups. section 10. It is therefore not possible when setting up scan tasks to allocate more than 100% of resources in total. 13. See section 8.5.6. 13.TEMS Investigation 14. 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.5.4. Sony Ericsson Phones and SRUs Sony Ericsson phones and SRUs do not handle concurrent execution of multiple scanning methods. 138 .1 User’s Manual R&S recommends that each scan task should be allocated at least 20% of resources in the setup dialog. 13. 1. section 10.1.4. supported using the various devices as indicated. 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.1.1.1. Built on Ericsson hardware. GSM Scanning 14. the device must have been purchased with the relevant option (wherever applicable). 2. see Information Elements and Events. chapter 14. see the Getting Started Manual.Chapter 14. NT12-7002 ver 1. although this is a slight abuse of the term. section 4. Scanning Methods and Capabilities TEMS Investigation offers these GSM scanning methods. For specifics. 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.0 139 . A note on terminology: GSM radio frequency carriers are sometimes referred to below as channels for simplicity. For more information about connectable scanners with GSM scanning capability. 14. 2.2 14. 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. Select all channels to scan the entire band.2. SRU .1 User’s Manual Sony Ericsson PCTel SeeGull GSM Scanning Capability/ Scanning Device RSSI scanning.2 14. BSIC Setup of RSSI Scan: Sony Ericsson. GSM frequency band or bands to scan.3 14.2.TEMS Investigation 14. 140 Section Ref.2. ARFCNs to scan on the selected band. It should be noted that BSIC decoding is computationally costly and considerably reduces the sample rate of the scan.3 14.1. 14. SRU Setting this to Yes causes the phone to decode the Base Station Identity Code whenever possible. static ARFCN set RSSI scanning: BSIC decoding RSSI scanning: C/I measurement RSSI scanning: Sys Info decoding Spectrum analysis R&S TSMW 14. Technology Band Channels 14.3 14.2.2. Check the Device Inquiry mode report from the scanner to find out whether it is capable of decoding BSIC. section 3.1. the function can be turned on and off in the dialog. etc. Regardless of the choice made here. PCTel scanners can be purchased with or without the C/I scanning function enabled. Bandwidth Remaining Measurement Points BSIC See section 13. GSM Scanning 14.Chapter 14. 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 has this capability (“GSM BCCH C/I”). as described in Information Elements and Events.2. C/I Measurements Setting this to Yes causes a subset of the “C/I” information elements to be updated. This setting applies to all channels you select for scanning.3. If available. It is not possible to specify the type of scan for each channel separately. PCTel scanners supplied with older versions of TEMS Investigation may lack BSIC decoding capability.0 141 . It should be noted that BSIC decoding is computationally costly and considerably reduces the sample rate of the scan.5.1. Setup of RSSI Scan: PCTel SeeGull Select whether to perform a regular GSM signal scan (“Normal”) or a Continuous Wave scan (“CW”). in the “GSM” category). Setting this to Yes causes the phone to decode the Base Station Identity Code whenever possible. NT12-7002 ver 1. Resource Allocation (%) 142 . SCH Power (DL): Enables SCH-related measurements such as SCH power. Measurement Rate (mHz) Measurement Details • • • RF Front-end Front-end on which to schedule measurements. the information element Neighbor (SI) ARFCN is updated. Dummy Burst Removal (DL): Enables detection of dummy bursts and removal of dummy bursts from the GSM signal before further analysis. This can produce many more power results for C0 carriers than the SCH measurement. Resources allocated on the specified front-end. 14.2.4. BSIC. and this is therefore done only once each time the strongest cell changes. Whenever System Information is read. Setup of RSSI Scan: Rohde & Schwarz TSMW Average measurement rate (in millihertz) shared between all selected channels.TEMS Investigation 14.5. C/I (DL): Enables carrier-to-interference measurement. ETS power. The measurement tasks are manually distributed on the built-in front-ends.1 User’s Manual SI on Strongest Setting this to Yes causes the scanner to decode System Information messages for the strongest cell. Dummy Burst Power (DL): Enables power measurement for dummy bursts. See also section 13. and GSM frame number. This is only valid for SCH-related measurements. The scanner must suspend the regular scan in order to read System Information.3. • • Channels: Channels to scan. 0 143 . Regarding the bar chart window itself. The bottom chart by default shows all scanned channels in order of ascending ARFCN.5. Spectrum Analysis The setup for spectrum analysis is the same as for WCDMA (except that Technology = GSM).1. see chapter 30.3.2.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. NT12-7002 ver 1.5. 14. See section 15. GSM Scanning 14. 1. 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. chapter 14.TEMS Investigation 14. For more information about connectable devices with WCDMA scanning capability. the device must have been purchased with the relevant option (wherever applicable).1. Please note that for a scanning method to be actually available in TEMS Investigation. 144 . see the Getting Started Manual. Scanning Methods and Capabilities TEMS Investigation offers these WCDMA scanning methods. supported using the various devices as indicated. section 10.1.4. 15.1 User’s Manual 15. 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. 4 15.3 15.2 15.3 15.2 15. of UARFCNs SCH timeslot scanning RSSI scanning Spectrum analysis Network scanning 1. Anritsu ML8720: 1 or 2 depending on physical configuration. R&S TSMW PCTel PCT WCDMA Scanning Capability/ Scanning Device PCTel SeeGull MX PCTel SeeGull EX PCTel SeeGull LX Anritsu ML8780A Anritsu ML8720 .5 15. 12 1 15.2 15.2.Chapter 15. SRU Pilot scanning. no. Top N Pilot: SIB decoding (continuous) Pilot: SIB decoding (snapshot) Pilot: High Speed/High Dynamic Pilot: P-SCH + S-SCH Pilot: Max.6 NT12-7002 ver 1. static SC set Pilot scanning.2 15.2.2 8 4 12 12 12 12 15.2 15.0 145 Section Ref. WCDMA Scanning Sony Ericsson. The choice is made under Type of Scanning in the setup dialog. Scan strongest: Strongest scrambling codes scanned (“Top N”). The allowed range is dependent on the frequency band. Where supported. scrambled with cell-specific scrambling codes.TEMS Investigation 14. static set of scrambling codes (common to all UARFCNs) scanned. • • • Setup of Pilot Scan: Sony Ericsson. Optional snapshot SIB decoding. the same method also scans primary and secondary synchronization channels (P-SCH. S-SCH). Several UARFCNs can be scanned at a time.2. Technology Band Channels 15.1. static set of scrambling codes (common to all UARFCNs) is scanned.2. SRU Setup options are as follows: Scan selected: A user-defined.2. BCH scanning: User-defined. WCDMA frequency band to scan. 15. Unconditional and continuous SIB decoding. 146 . UARFCNs and scrambling codes are selected independently of one another. Pilot Scanning (with SCH Scanning) This method scans CPICH control channels.2.1 User’s Manual 15. Here you set the UARFCNs of the frequencies on which to scan the CPICH. Setup of Pilot Scan: General Always “WCDMA” for WCDMA scanning. Optional snapshot SIB decoding. 0 147 . However. the updating frequency will be considerably lower. you select scrambling codes in the same way as for Scan selected. Scrambling Codes NT12-7002 ver 1. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under Channels. unlike that governed by the System Information option (which see). enter the value N here (N 40). The threshold should be adjusted to ensure detection of cells actually present while keeping the false detection rate down. The scanner automatically finds the strongest scrambling codes. BCH scanning: If you choose this option. • Cell Noise Floor Ec/Io threshold for accepting a signal on the CPICH as a detected cell. This decoding is furthermore continuous. and the same scan data will be collected. The processing time freed up in this way is instead used to continuously decode System Information Blocks (SIBs). WCDMA Scanning Type of Scanning See also the introduction of this section. • Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs. Enter the scrambling codes you want to scan. The default is –26 dB.Chapter 15. and the sensitivity of the scrambling code detection may be lower as well. This field is enabled if you have chosen “Scan selected” or “BCH scanning” under Type of Scanning. Scan Strongest This field is enabled if you have chosen “Scan strongest” under Type of Scanning. To scan the N strongest scrambling codes. this option is always set to Yes. Only settings supported by the connected scanner are displayed in the dialog. static set of scrambling codes. Up to 128 scrambling codes can be selected. enter the value N here (N 32). SIBs will be decoded again for that cell. It then refers not to snapshot SIB decoding but to the continuous SIB decoding performed by that method. • Number of Pilots This field appears if Type of Scanning is set to “Scan strongest”. For BCH scanning.3. 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). Setup of Pilot Scan: PCTel The set of scrambling codes to scan on each UARFCN is composed in one of two ways: • • user-defined. the phone reverts to regular pilot scanning. Type of Scanning See also the introduction of this section.1 User’s Manual System Information If this option is set to Yes for Scan selected or Scan strongest. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under Channels. 15. The scanner automatically finds the strongest scrambling codes. 148 . The same scrambling codes will be scanned on the CPICH and on the P-SCH and S-SCH. To scan the N strongest scrambling codes.1. 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. If the strongest cell does not change within two minutes.2. On completing the SIB decoding. Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs.TEMS Investigation 14. .2. The precise meaning of “Sub” depends on the scope of the scan: • For “Scan selected”.8 and 15. SIR”.) For “Scan strongest”. Enter the scrambling codes you want to scan. WCDMA Scanning Selected Numbers PN Threshold This field appears if Type of Scanning is set to “Scan selected”. P-SCH Ec/Io. Remaining Measurement Points Data Mode See section 13.2. and Rake Finger Count are excluded.. Time Offset. and you will thus be able to discern multipath and fading effects more accurately.10).1. only P-SCH Ec/Io and S-SCH Ec/Io are excluded. • SIR Setting this to Yes causes the scanner to deliver the information elements “Sc .7). the Aggregate Ec/Io and Delay Spread values will be affected by random noise more than may be desired. Sub means that some data is not presented or recorded (compare sections 15. This is a signal code power threshold (in dB) used for the Aggregate Ec/Io and Delay Spread measurements (see section 15.Chapter 15. By raising the threshold you reduce the influence of random noise correlations. as is SIR. It is possible to reduce the amount of data that is presented and recorded: • • Full means no reduction. It should be noted that choosing “Sub” results in a much faster updating of scan presentations. If the PN threshold is set too low. NT12-7002 ver 1.5. The setting –20 dB is recommended.0 149 . (The “SIR” field is disabled in this case. S-SCH Ec/Io.2. a maximum of 16 scrambling codes can be scanned. Measurement Mode There are two choices. • 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. Each sample reported by the scanner is typically based on a measurement 20 ms in length. Front-end (processor) on which to schedule measurement. 15. before moving on to the next cell. Given as a multiple of 40 ms. 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.2. Resources allocated on the specified front-end. Measurement Mode Measurement Rate (mHz) RF Front-end Resource Allocation (%) 150 . The default is 50 = 2000 ms. High Dynamic puts the emphasis on accuracy. The measurement tasks are manually distributed on the two built-in front-ends.1 User’s Manual System Information Set this to Yes to decode System Information blocks (continuously). 3rd.5.TEMS Investigation 14. 4th) Intra-freq Cells”. With this option selected. These are two algorithms with different priorities. From the SIB decoding are extracted the information elements “Sc 1st (2nd. Setup of Pilot Scan: Rohde & Schwarz TSMW High Speed or High Dynamic. whereas High Speed is faster and accordingly less accurate.3. Average measurement rate (in millihertz) shared between all selected channels. High Speed and High Dynamic. See also section 13. The scanner automatically finds the strongest scrambling codes.Chapter 15. Up to 32 scrambling codes can be selected. The same scrambling codes will be scanned on the CPICH and on the P-SCH and S-SCH. or strongest scrambling codes (“Top N”) Type of Scanning See also the introduction of this section. The maximum number of pilots that can be scanned is equal to floor(40/Nch). enter the value N here. where Nch is the number of UARFCNs entered under Channels.2. For example. Selective Level NT12-7002 ver 1. WCDMA Scanning Resource Available (%) Read-only field indicating the remaining available resources on the processor selected under RF Frontend. common to all UARFCNs. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under “UARFCN” below. if 3 UARFCNs are selected. This threshold (value in dB) determines how high above the noise floor a scrambling code must reach in order to be accepted as valid by the scanner. up to 13 SCs can be scanned on each. 15. static set of scrambling codes.0 151 .5. Setup of Pilot Scan: Anritsu The set of scrambling codes to scan on a UARFCN is composed in one of two ways: • • user-defined. The default is 4 dB. To scan the N strongest scrambling codes. • Number of Pilots This field appears if Type of scanning is set to “Scan strongest”. (ML8720 only) Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs (“Top N”). (For all scrambling codes detected in this way. If you are scanning two UARFCNs it is the only option. The default is 20 dB.2.1 User’s Manual Rake Threshold This threshold (value in dB) determines. This setting governs the choice of cell search method in Top N scan mode (“Scan strongest” option).9) 152 . • If SCH is selected. This is more suitable for drive testing and is the default setting in TEMS Investigation. If you select two UARFCNs. this threshold governs how many Rake fingers will contribute to the signal. • If P-CPICH is selected. Search Method (ML8720) BCH Scan (ML8780A) If selected. for a given scrambling code.2. the scanner will search for scrambling codes that use P-SCH and S-SCH. • • • Presentation: General Pilot scan data is presented in the CPICH Scan bar charts (section 15. 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. only CPICH channels will be scanned to find scrambling codes. however. In other words.2.6. Setting the threshold at n dB means that a signal path must not be more than n dB weaker than the strongest one.7) the CPICH Scan Data status window (section 15.8) the CPICH Scan line charts (section 15. The P-CPICH mode cannot be used if two UARFCNs are to be scanned.TEMS Investigation 14. as explained above. This can only be done on one UARFCN at a time (only one is selectable under Channels when the BCH Scan option is set). 15.) This mode is useful especially for troubleshooting of transmitters. the scanner will perform continuous SIB decoding.2. the scanner will measure and report on the P-SCH and S-SCH as well. the P-CPICH radio button is grayed. whereas CPICH Best UARFCN Data is sorted by Aggr Ec/Io regardless of UARFCN. Each bar chart by default presents peak Ec/Io (see section 15. 15.2.Chapter 15.1.2. Regarding data sorting.8) for each scrambling code found. 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.10). 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.8. They differ only with respect to sorting: CPICH Data is sorted first by UARFCN. the updating rate is also greatly affected by the size of this set. For a manually selected set of scrambling codes.0 153 . The columns have the following meanings: NT12-7002 ver 1. The updating rate is chiefly dependent on the number of live signals encountered in the network.7. One predefined bar chart is provided for each UMTS frequency scanned.2.13. 15. WCDMA Scanning Synchronization channels are presented in the Synch Channels window (section 15. see section 15. Presentation: “CPICH Scan” Bar Charts The CPICH Scan bar charts present CPICH scan data.2. e. 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 time offset of the radio frame on the CPICH.e.9. Ranges from 0 to 38399. The peak code power of the scrambling code (Ec) relative to the total signal power in the channel (Io).e. Signal-to-interference ratio of the scrambling code in dB. i. i.e. This is a measure of the signal spreading due to multipath propagation. the difference between them in dB. the difference between them in dB. Presentation: “CPICH Scan” Line Charts The default configuration of this window is as follows: 154 . The peak code power of the scrambling code in dBm. 15.2.3). Measured on DPCCH. Time in chips from the first to the last Ec/Io peak that is above the PN threshold. Rake receiver gain. Rake finger count. 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. i. the number of Ec/Io peaks (multipath components) that are above the PN threshold. i.1 User’s Manual SC Peak Ec/Io Scrambling code number. The aggregate code power of the scrambling code relative to the total signal power in the channel (Io). given in chips from a 1/100th second time mark aligned with GPS time.2.2. section 3.TEMS Investigation 14. Difference in dB between the aggregate code power (Ag Ec) and peak code power (Peak Ec). The aggregate code power of the scrambling code in dBm. See Information Elements and Events. The top chart shows Aggr Ec (in dBm) and the bottom chart shows Aggr Ec/Io (in dB). NT12-7002 ver 1.Chapter 15. Additional Information Pane The Additional Information pane (bottom right) shows the CPICH pilot pollution situation. Please note that the IEs described here are no longer present by default in this window. To switch to the other chart.0 155 .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. Here an SC is regarded as a possible active set member if it is sufficiently 1. right-click and choose the desired chart from the context menu. you need to add them manually. WCDMA Scanning Chart Panes The charts present the five strongest scrambling codes. Legend Pane The Legend pane (bottom left) glosses either of the two charts. For “Max N SCs”. max 2 SCs SC Other power. all SCs with a code power not more than 3 dB below that of the strongest SC will be counted. indicated by argument Threshold for possible AS members (which are included in “Own”) Own power. 2. : These are estimated ratios between polluting signal power and desired signal power.e. In the example below. 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. otherwise it is simply the sum of the code powers of all possible active set members. The four “Other/Own” elements represent the assumptions that there is desired signal power on 1. there are three other SCs reaching above the threshold which is set relative to the strongest SC. “Own” is the sum of the code powers of the N strongest possible active set members. 156 . However.1 User’s Manual strong compared to the strongest SC. there are three such SCs. 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. if the number of possible members is at least N. for “Max 2 SCs”. and 4 SCs respectively. Example: If the argument is 3 (default value). In the above figure.. SC code power Strongest SC Distance to threshold. • Other/Own . The relative code power threshold is determined by the argument within square brackets [].TEMS Investigation 14. “Other” is the sum of the code powers of all remaining SCs. so the active set is judged to have a total of four possible members.. only the strongest of the three is included in “Own”. 3. max 2 SCs The “Other/Own” ratios are of course calculated from absolute code power values (i. Ec values in mW). S-SCH Ec S-SCH Ec/Io By default the scrambling codes are sorted by signal power with the strongest on top. the difference between them in dB. Presentation: Synch Channel Data Window This window presents scan data on the synchronization channels P-SCH and S-SCH. i. NT12-7002 ver 1. the difference between them in dB. but with different arguments for different elements you cannot really draw any useful conclusions.0 157 .e. SC P-SCH Ec P-SCH Ec/Io Scrambling code number. i. The peak power of the Primary Synchronization Channel. P-SCH (in dBm). WCDMA Scanning Note: The arguments should be kept the same for all five information elements. The presented data can be freely rearranged. S-SCH (in dBm).10. The peak power of the S-SCH (Ec) relative to the total signal power in the channel (Io). The peak power of the P-SCH (Ec) relative to the total signal power in the channel (Io).e. It is of course possible to set each argument to any of the permissible values.2. 15. The peak power of the Secondary Synchronization Channel. as described in section 24.Chapter 15. “Changing Status Window Properties”. obtained with the Pilot scanning method.3. see sections 15.2.13. For definitions of the information elements. However. 15.1.2. section 3.11 above regarding the presentation of this data.13. but they are also extracted as information elements. Double-click the item “WCDMA”. Another piece of data found in SIBs is an uplink interference measurement. see Information Elements and Events.1 User’s Manual 15. 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.2. The uplink interference measurements can of course be inspected in the plain-text SIB decoding. 15. • • • • Open the General window from the Navigator.2.2. No special presentation windows are provided for BCH scanning. Presentation: “Finger Info” Status Windows These windows present Rake finger information obtained during Pilot scanning. section 3.7–15. Sort by decreasing Aggr Ec/Io (default) Sort by increasing Aggr Ec/Io A dialog appears with these sorting options: 158 .2. 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. Sorting of Scrambling Codes You can sort scrambling codes in scanning information elements in a number of different ways. see Information Elements and Events. The sorting order is set in the General window.11.12. decoded System Information Blocks are output in the Layer 3 Messages window at a greatly enhanced rate. This is particularly interesting for HSUPA.2. See Information Elements and Events.TEMS Investigation 14. Customizing the Presentation 15. Presentation: BCH Scanning All scan data collected using the options Scan selected and Scan strongest are obtained for BCH scanning also (though less frequently).2.2. section 7. etc.3. It is useful for monitoring synchronization reference signals sent on this channel. 15. Presenting Scrambling Codes from Multiple UARFCNs In the “Sc Best” information elements. Sort by scrambling code: Scrambling codes are sorted by index.1.3.2) is fixed and is not affected by the General window settings. SCH Timeslot Scanning This method scans timeslot-length intervals. 15.2).1. WCDMA Scanning • Sort by fixed position: Scrambling codes are sorted by index and are always assigned the same argument indices. UARFCN to scan. on a Primary Synchronization Channel (P-SCH). intervals 2560 chips long. the code with the lowest index appears at argument index 1. • 15. Use these elements in order to view scan data from several UARFCNs in one window.2.2. and this sorting order is unchangeable. scrambling code n is always found at argument index n + 1. Setup of SCH Timeslot Scan General Settings Always “WCDMA” for WCDMA scanning.13. Technology Band Channels NT12-7002 ver 1. the code with the next higher index appears at argument index 2.0 159 .e. 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. section 3. WCDMA frequency band to scan. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events. i. all scrambling codes found on all UMTS frequencies are collected in a single array.3.Chapter 15. These elements are sorted by signal strength (Aggr Ec/Io) in descending order. that is.1. 15. 15.TEMS Investigation 14.1. 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.3. Compression Rate Remaining Measurement Points See section 13. The legend pane gives 160 . etc. Context Settings The time resolution of the scan: • • Every means that a power value is reported for every chip in the timeslot.3.1 User’s Manual Center Frequency The center frequency of the UARFCN chosen.2. or 8 chips in length. Presentation: SCH Timeslot Scan Bar Chart The bar chart displays an Es/Io trace for the latest timeslot scanned (2560 chips).5. 4. 15. the height of the spike reflecting the strength of the signal in terms of Es/Io. Every 2.2. 256. WCDMA Scanning Es/Io for each chip. depending on the setup. no conclusions can be drawn about the value of T_Cell. Provided that the base station clock is synchronized with GPS time. From this the time separation between the sectors can be determined. the offset being due to delay in the scanner. If the base station is not synchronized with GPS time. 4. or 8 chips. Technology Band NT12-7002 ver 1. In a WCDMA cell with multiple sectors. the spikes will normally remain in the same positions as the trace is updated. see Information Elements and Events. The position of a spike shows at what point a new timeslot begins in the current transmission.0 161 . 15. The SCH timeslot scan will then display multiple spikes within a timeslot. 15. and 512 chips). 15. 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.1.4. In the lower right pane.g. 0. or peak Es/Io for every 2. if the compression rate is set to “Every 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. These parameters are identical with the information elements SCH TS Sc Time Diff 1-2 and SCH TS Sc Time Diff 2-3.3.4.2.1. However. WCDMA frequency band to scan.Chapter 15.4. however. Determining the time separation naturally does not require synchronization of the base station with GPS time.1. see section 15. “Time diff 2-3” indicates the time separation in chips between the second strongest peak and the third strongest. the updating interval will be on the order of 1 s. section 3. RSSI Scanning Setup of RSSI Scan General Settings Always “WCDMA” for WCDMA scanning.1. each sector will transmit/receive at a different time offset (e. Since the SCH signals are repeated every timeslot. one for each sector. 15.1.1 User’s Manual Channels UARFCNs to scan (up to 255). The allowed UARFCN range is dependent on the band. 162 .4. Bandwidth Context Settings Select whether to perform a regular WCDMA signal scan (“Normal”) or a Continuous Wave scan (“CW”).5.2. the measurements are extracted to the same information elements (CW Sc RSSI. Remaining Measurement Points See section 13. in the “WCDMA” category). This setting applies to all channels you select for scanning. Regardless of the choice made here.1. etc. 15.2.TEMS Investigation 14. Presentation: RSSI Scan Bar Chart This bar chart displays RSSI for each UARFCN scanned.4. can of course only distinguish the samples as far as the screen resolution permits. Technology Band Start Frequency Stop Frequency Resolution Bandwidth 15.2. the legend pane will list all samples.1.1. High end of the frequency range to be swept by the scan.5.0 163 . See section 13. and the maximum is 16.5.1. WCDMA Scanning 15.5.5. Note that the spectrum analysis is prone to consume a large number of measurement points. Given in MHz.5. The minimum number is 1. Interval between successive scan samples in kHz. Number of Sweeps Context Settings The number of sweeps on which to base the presented average RSSI. Given in MHz. WCDMA frequency band to scan. Remaining Measurement Points NT12-7002 ver 1. on the other hand. 15.Chapter 15.1.1. the highest selectable resolution being 5 kHz. the chart. In the presentation window. Low end of the frequency range to be swept by the scan. Spectrum Analysis This scanning method shows downlink signal strength as a function of frequency. Setup of Spectrum Analysis Scan General Settings Choose “WCDMA” for WCDMA scanning. 15. Adapt the resolution to the width of the frequency range. Uplink spectrum analysis is currently not supported by any currently connectable devices. 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. 850 MHz. 1.1 They both display RSSI as a function of frequency. once it has found a WCDMA carrier. 164 . one cell (scrambling code) is detected and presented.5. On each carrier. overlapping or not. one for the downlink (Spectrum Analysis Bar Chart) and one for the uplink (Spectrum Analysis Uplink Bar Chart). thus allowing faulty frequency allocations to be easily found and rectified. 1900 MHz. In contrast. a Sony Ericsson phone in scan mode is usually able to identify all carriers. A mobile phone in regular phone mode.TEMS Investigation 14.2. Presentation: Spectrum Analysis Bar Charts Two charts are provided. but the chart is retained to allow displaying of such data from old logfiles.1 User’s Manual 15. 15. It will detect WCDMA carriers (UARFCNs) that are in use on each of the WCDMA bands 2100 MHz. Network Scanning This function is highly useful for obtaining a bird’s-eye view of an unfamiliar WCDMA radio environment.6. 3”) You can set up three separate UARFCN ranges (Interval 1.6.4. UARFCN Ranges (“Interval 1. set Custom range to Yes. To 15.6. Each range can be located on any of the supported frequency bands.1. 2. 3) to scan in the network. (See 3GPP 25.6. Additional fields “From” and “To” appear. From.3–5. If you want the UARFCN range to consist of a portion of a band.1. If you want the UARFCN range to be identical to an entire WCDMA frequency band.1. in which you specify the endpoints of the UARFCN range.6. Additional channels have UARFCNs that are completely different from the general channels. 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. 15.1. sections 5. WCDMA Scanning 15.) If this option is checked.Chapter 15. Interval <n> enabled Band Set the flag to Yes if you want to define this UARFCN range.3. select that band here.0 165 .2.1.4. 2.101.4 for details on the two kinds of channel. Technology 15. Custom range. Include additional channels Context Settings Check this to include additional channels on the 1900 or 850 MHz band. NT12-7002 ver 1. Setup of Network Scan General Settings Choose “WCDMA” for WCDMA scanning. several minutes at –100 dBm). 166 . where all cells will be significantly disturbed. RSSI threshold RSSI threshold for detecting carriers. This threshold should be high enough to minimize the false detection rate. reflecting a trade-off between the desire to detect all networks in operation and the wish to avoid spurious “hits”.2. that is. One scrambling code (cell) is displayed for each UARFCN. which should be suitable in most situations. 15. It lists all UARFCNs found.6. the center frequency of each detected WCDMA carrier.g. The default setting is –26 dB. yet not so high that cells actually present may go undetected. The risk of the latter is particularly pronounced in the case of overlapping carriers. Presentation: Network Search Window The result of the network scan is output in the Network Search window. The default setting is –94 dBm. Setting the threshold too low results in a very long search time (e. UARFCNs from all WCDMA frequency bands are listed in the same column.1 User’s Manual Cell Ec/No threshold Ec/No threshold for cell detection within a detected carrier.TEMS Investigation 14. 1.1. section 10. Please note that for a scanning method to be actually available in TEMS Investigation. Certain scanners require special configuration of the device itself as well as the PC to prepare them for use with TEMS Investigation. the device must have been purchased with the relevant option (wherever applicable). For more information about connectable devices with LTE scanning capability.0 167 . LTE Scanning TEMS Investigation supports scanning of LTE carriers with the following kinds of device: • • • • • Andrew scanner DRT scanner PCTel scanner Rohde & Schwarz TSMW scanner Transcom scanner. see the Getting Started Manual. What needs doing is covered in the Getting Started Manual.1.Chapter 16. LTE Scanning 16. NT12-7002 ver 1. chapters 12–14. Scanning Methods and Capabilities TEMS Investigation offers these LTE scanning methods. 16. It is possible to run several of these scanning methods concurrently.4. supported using the various devices as indicated. LTE Signal Scanning The LTE air interface uses OFDM as modulation method on the downlink.2 16.2.1. Setup of LTE Signal Scan: General Always “LTE”. PCIG.2 16. RSRQ) CINR (SCH CINR.Scan PCTel SeeGull MX PCTel SeeGull EX .5 16.3 16. The LTE signal scan provides the following metrics: • • • • • SCH (PCI.TEMS Investigation 14.1 User’s Manual R&S TSMW Signal scanning Enhanced signal scanning RSSI scanning Spectrum scanning Enhanced power scanning Transcom DRT 16. S-SCH RSSI. Synchronization Channels are used for service detection and synchronization. RS CINR) CFO Time Offset 16. LTE band to scan. P-SCH RSSI. LTE Scanning Capability/ Scanning Device Andrew i. and Reference Signals (RS’s) are used for channel estimation purposes.2.4 16. SCHRQ) RS (RSRP. Technology Band 168 Section Ref. Top N: Select this if you wish to scan the strongest cells. None: Do not log to MMC. (This logging has got nothing to do with TEMS Investigation. Setup of LTE Signal Scan: Andrew Minimum time for scan in ms. For example. Scan Rate Report Threshold 16.2. If you are using a DRT scanner with the optional multimedia card (MMC). the scan data is always recorded in regular TEMS Investigation logfiles (*. you can optionally record a logfile with scan data on the MMC as well. Min: –240 = –24 dB. –6. • • MMC: Log to MMC. Epss/Io detection threshold (i.) The MMC must have been formatted and inserted into the scanner before the scanner is powered on.2.e. Max: 0 = 0 dB.5 dB is indicated as –65.Chapter 16. Each EARFCN is specified as a number representing the center frequency of the channel. 16. NT12-7002 ver 1.trp). given in 0. Scan Type • Logging Mode When using a DRT scanner purchased with TEMS Investigation. Setup of LTE Signal Scan: DRT • Targeted Scan: Select this if you wish to scan a fixed set of cells. LTE Scanning Channels EARFCNs to scan within the selected LTE band.2.1 dB increments. for Primary Synchronization Channel). Up to 12 EARFCNs can be selected.0 169 . Set the number of cells the scanner should report under Top N. Specify the cells under Cell Index List.3. regardless of how this parameter is set. setting the field to N causes the scanner to return the N strongest cells (N 16). Min: –30 dB.TEMS Investigation 14. Measurement of Center Frequency Offset. Carrier to Interference-plusNoise Ratio for SCH and RS. This field is editable if you have set Scan Type to “Targeted”. CINR threshold for attempting to decode the MIB/ SIB. Max: 0 dB. Max: 0 dB. Not supported by currently connectable scanners. Here you specify how many cells the scanner should report. Calculation of CINR. RSRQ). Min: –30 dB. Min: –30 dB. Measurement of Reference Signal (RSRP. 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 .e. i. Measurement of Synchronization Channels: P-SCH RSSI. Max: 50 dB. Threshold (in negative dB) for detection of Primary Synchronization Channel. up to 16 × 12 = 192 cells in total). Measurement of BCH received power. and SCHRQ. Not supported by currently connectable scanners. Here you specify the indices of the cells to scan (up to 16 cells for each EARFCN. and the interference can be either noise or co-channel interference or both. Threshold (in negative dB) for detection of Secondary Synchronization Channel.1 User’s Manual Top N This field is editable if you have set Scan Type to “Top N”. S-SCH RSSI. The carrier is the desired signal. 15. simply select it. Automatic: Duplexing method used by detected cells is automatically detected. LTE Scanning Bandwidth The bandwidth to scan. 3GPP 36.4. the scanner will itself detect the bandwidth in use. • • Fast mode: This mode offers reasonable sensitivity with a fast scan rate. since otherwise high-level signals may saturate the receiver and cause errors.0 171 . • Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. 10. that bandwidth will always be scanned. Robust mode: This mode uses lower detection thresholds and increased averaging to detect lower-level signals.211.2. or 20 MHz). Cyclic Prefix Detection Mode Duplexing Detection Mode • • • Enable ECP This should be turned on if the network uses Extended Cyclic Prefixes. 5. It should normally be enabled. a valid LTE signal with strength greater than the detection thresholds is required.3-1 Number of LTE frames over which to average scan measurements. • • • Automatic: Cyclic prefix used by detected cells is automatically detected. Extended: Extended prefix assumed. For this to work. table 6. Normal: Normal prefix assumed. If you choose a fixed bandwidth (1. • If you choose Auto-select. 3. Observations Average Detection Mode NT12-7002 ver 1.Chapter 16. If you know what the implemented bandwidth is. FDD: Frequency Division Duplexing assumed. TDD: Time Division Duplexing assumed. It is a slower scan mode. Number of Antenna Ports Cyclic Prefix Sync Signal Measurement Threshold Reference Signal Measurement Threshold 172 . not scanning of a fixed cell list. setting the field to N causes the scanner to return the N strongest cells. with separate RS symbols per Tx port.4. Bandwidth Carrier RSSI Threshold Top N The bandwidth to scan. The RS and SS measurements will be performed only if measured Carrier RSSI is above this threshold. e. The type of cyclic prefix used in OFDM. The bandwidth must be selected manually. The number of antenna ports to measure on (multiple ports for MIMO). “Normal 15 kHz”.2. If the eNodeB is using MIMO transmission. Only Synchronization Signal (SS) measurements above this threshold will be reported.g. Setup of LTE Signal Scan: PCTel With PCTel only Top-N scanning is supported. Here you specify how many cells the scanner should report.1 User’s Manual Number of Tx The number of Tx signals to be detected by the scanner.TEMS Investigation 14. The scanner is capable of detecting this automatically (“Auto Detect”). 16. the scanner can detect each of the different RS’s and is then able to measure each Tx signal separately. Only Reference Signal (RS) measurements above this threshold will be reported. The scanner is capable of detecting this automatically (“Auto Detect”). . It populates the MIMO scanning information elements with “Tx1” . Subband start index within the measurement bandwidth. If this option is included. the subband settings that follow become visible in the property grid. “Tx4” in their names..1. Equal to Bandwidth/Subband Size. multiple concurrent LTE signal scans can be performed. Subband Size Subband Start Size of subband. However. which does not populate any special information elements. One of: • • • • Wideband Wideband + Subband Wideband + RF Path Wideband + Subband + RF Path The RF Path option means multipath (MIMO) scanning.Chapter 16. Must be in the range 0 .0 173 . LTE Scanning Measurement Mode Signal scan measurement mode. stated as a number of resource blocks. If a total of more than 12 EARFCNs are scanned.. Number of subbands to divide the measurement bandwidth into. for example on different bands. NT12-7002 ver 1.. Subband Count – 1. only the first 12 selected for scanning are presented. The output to information elements remains exactly the same with this setup: All scanned EARFCNs are presented within the information element range “1st” … “12th”. The RF Path and Subband options are referred to collectively as “Enhanced signal scanning” in section 16. The Subband option refers to subband scanning. Subband Count With PCTel SeeGull MX scanners. all subband measurements appear in the plain-text decoded scan reports. RS-CINR being measured for each such section separately. Specifies the type of LTE signal to assume for RS-CINR measurements. 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. uplink and downlink transmitters use separate frequency bands. Channel frame structure. It is possible to run FDD and TDD signal scan tasks concurrently. A signal matching filter reducing scanner-internal interference will be applied if this parameter is set. The final output is a single RS-CINR value.5. The output to information elements remains exactly the same with this setup: All scanned EARFCNs are presented within the information element range “1st” … “12th”. a single frequency band is shared between uplink and downlink. only the first 12 selected for scanning are presented. Setup of LTE Signal Scan: Rohde & Schwarz TSMW The type of cyclic prefix used in OFDM.1 User’s Manual 16. which is what is presented in TEMS Investigation. You can select several values.2. The scanner is capable of detecting this automatically (“Auto Detect”). Enables RS-CINR measurement within the innermost 1080 kHz around the center frequency of the LTE channel. Each selected value corresponds to a measurement where the 1080 kHz segment is divided into the specified number of equal-sized sections. Cyclic Prefix Frame Structure Measurement Rate (Hz) RS-CINR Carrier Sections Average number of 100 ms blocks to measure per second.TEMS Investigation 14. If FDD. RS-CINR Noise Reduction 174 . each dividing the 1080 kHz into a different number of sections. and if TDD. If a total of more than 12 EARFCNs are scanned. which will then give rise to multiple instances of the RS-CINR measurement. See also section 13. Cell Coverage Scan: Scan only the EARFCNs selected under Channels. S-SCH to P-SCH Ratio Settings Ratio Type Specifies either a list of ratios or a range in which the power ratio between the primary and secondary synchronization channel must reside. Front-end (processor) on which to schedule measurement. The measurement tasks are manually distributed on the two built-in front-ends.6. Lower limit for ratio between primary and secondary synchronization channel. Resources allocated on the specified front-end.3. List of power ratios between the primary and secondary synchronization channels. Setup of LTE Signal Scan: Transcom Please note that the Transcom scanner is not capable of scanning more than one band at a time.2. Read-only field indicating the remaining available resources on the processor selected under RF Frontend. LTE Signal Scan Type • • Top Number Full Band Scan: Scan the full band selected under Band. What cells will appear depends on the selected sorting order (Sort Cells By parameter).Chapter 16.5. NT12-7002 ver 1. LTE Scanning TDD Frame Configurations Specifies uplink–downlink configurations to try when performing reference signal measurements on TDD channels.0 175 . Upper limit for ratio between primary and secondary synchronization channel. Number of cells to include in the presentation (up to 32). Lower Ratio Limit (dB) Upper Ratio Limit (dB) Fixed Ratios (dB) RF Front-end Resource Allocation (%) Resource Available (%) 16. 7. table 4. Presentation of LTE Signal Scan LTE signal scans are presented in a suite of predefined charts and status windows. a single frequency band is shared between uplink and downlink.3. section 8. If FDD. RP. Use of BCH measurement. 16. 176 . Use of Primary Synchronization Signal measurement. or RS. See Information Elements and Events. Use of Secondary Synchronization Signal measurement. or CINR for one of the signals PSS. TDD special subframe configuration: 3GPP 36.1 User’s Manual Sort Cells By Parameter by which to sort cells in presentation windows.3. If TDD. RQ. One of RSSI. uplink and downlink transmitters use separate frequency bands. Use of co-channel detection.2-1.TEMS Investigation 14. Use of timeslot measurement. Does not exist for FDD. Use of Reference Signal measurement with Rx1 antenna. Timing. SSS. Channel frame structure.2.211. “Unsorted” means that the cells will be listed in the order they are scanned. 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 Reference Signal measurement with Rx2 antenna. a cell with Cell Identity n is always found at argument index n. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events.8. etc. Up to 255 EARFCNs can be scanned. Sort by Cell Identity: Cells are sorted by Cell Identity. 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. the cell with the next higher Cell Identity appears at argument index 2.2.3. section 3. RSSI Scanning Setup of RSSI Scan: General Always “LTE”. the cell with the lowest Cell Identity appears at argument index 1. 16. • • • • • Open the General window from the Navigator.1.3. Double-click the item “LTE”. Technology Band Channels NT12-7002 ver 1.2. Each EARFCN is specified as a number representing the center frequency of the channel.0 177 . that is. Customizing the Presentation Sorting of Cells You can sort LTE cells in scanning information elements in a number of different ways. EARFCNs to scan within the selected LTE band.1. LTE band to scan. LTE Scanning 16.Chapter 16. 16. The sorting order is set in the General window.3) is fixed and is not affected by the General window settings. A dialog appears with these sorting options: • 16.8. 3. Setup of RSSI Scan: DRT See section 16. RSSI Scan Type Measured Bandwidth Bandwidth to scan.3.3. Bandwidth Remaining Measurement Points 16.3.1.2. Setup of Spectrum Scan: General Always “LTE”. Bandwidth to scan. See section 13.4. 16. fixed at 100 kHz.3. Presentation of RSSI Scan RSSI scans are presented in a suite of predefined charts. Logging Mode Bandwidth 16.1 User’s Manual 16. section 8.4.1. Technology 178 .3. Spectrum Scanning A spectrum scan shows downlink signal strength as a function of frequency.3.TEMS Investigation 14. select a bandwidth from the list.5. 16. 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 Information Elements and Events. Setup of RSSI Scan: PCTel Bandwidth to scan.3. 16.5. select a bandwidth from the list.4.2. see section 19. Setup of Spectrum Scan: PCTel The PCTel-specific settings are the same as for WCDMA. Given in MHz.4. it will come into play only if you are using the LTE scanner to search for WiMAX presence.Chapter 16. LTE Scanning Band Start Frequency Stop Frequency Resolution Bandwidth Select the LTE frequency band to scan. Note. the only value supported is 1. 16. however. Currently. 16. 16. the legend pane will list all samples. can of course only distinguish the samples as far as the screen resolution permits.4.5. that the Triggered Scan option is still associated with WiMAX frames.4.0 179 .5. Number of Sweeps NT12-7002 ver 1. Interval between successive scan samples in kHz.2.3. Given in MHz.4.4. on the other hand. Low end of the frequency range to be swept by the scan. Setup of Spectrum Scan: Andrew Minimum time for scan in ms. High end of the frequency range to be swept by the scan.1. Setup of Spectrum Scan: Transcom The number of sweeps on which to base the presented average RSSI.5. that is. See section 15. Scan Rate 16. Setup of Spectrum Scan: DRT The DRT-specific settings are the same as for WiMAX. the chart. In the presentation window. Setup of Enhanced Power Scan: General Always “LTE”. Given in units of 50 μs. 16.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.5.1. Setup of Enhanced Power Scan Bandwidth to scan. See Information Elements and Events. One of: CW: 100 kHz Normal: 1. 180 . Enhanced Power Scanning Compared to the spectrum scan. Time offset in units of 50 μs. 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. The scan will start on the nearest Timing Period Mark with the Timing Period Mark Offset specified.3.5. Max: 20000. or maximum frequency of the band to be scanned.TEMS Investigation 14.3.4. LTE band to scan. section 8.5. Must be less than or equal to Timing Period Mark.2. Spectrum Scan Presentation Spectrum scans are presented in a predefined bar chart. Technology Band Channel 16.1 User’s Manual 16. center. 16. section 8. 16.5 kHz.5 kHz. See Information Elements and Events.1.3.0 181 . 8000. or else set to zero which means that the choice of window size is made by the scanner for optimal measurement performance.. Presentation of Enhanced Power Scan Enhanced power scans are presented in a predefined bar chart. See section 13. Valid range: 2 .3.5. Must be larger than 100. LTE Scanning Measurement Window Measurement window size in units of 50 μs.5.Chapter 16. then the number of bins must be odd. The number of measurements to make within the specified band.3. NT12-7002 ver 1. Frequency step size in units of 2.. Number of Bins Resolution Bandwidth Frequency Step Size Remaining Measurement Points Resolution bandwidth in units of 2. If Time Period Reference is set to Center. Up to 12 UARFCNs can be selected for pilot scanning. 17. For more information. Each UARFCN is specified as a number representing the center frequency of the channel. TD-SCDMA Scanning TEMS Investigation supports scanning of TD-SCDMA UARFCNs with PCTel scanners. General Scan Settings Regardless of scanning method. As for other cellular technologies.1. TD-SCDMA band or bands to scan.3): Top N RSSI scanning (section 17. you need to set the following: Technology Band Channels Always “TD-SCDMA” for TD-SCDMA scanning. Note: You must have GPS coverage to obtain TD-SCDMA scan data. TEMS Investigation can make use of GPS data from the scanner’s internal GPS. TD-SCDMA UARFCNs to scan within the selected band. and up to 255 UARFCNs for RSSI scanning.2. • • Scanning Methods Pilot scanning (section 17. which is indispensable for the TD (Time Division) component of the TD-SCDMA technology. 182 .1 User’s Manual 17. section 10. This is because a GPS signal is needed for time synchronization.4.2.4) 17. see the Getting Started Manual.1.TEMS Investigation 14. 3. Midamble Top N Pilot Scanning This mode measures the Primary Common Control Physical Channel (P-CCPCH). • • 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.1.Chapter 17. Type of Scanning Setup of Pilot Scan • Scan strongest: The N strongest CPIs will be reported from the chosen UARFCNs. The value N is determined by the Number of Pilots parameter.3. To this end it scans the TS0 midamble (144 chips). During the cell search procedure. section 7. enter the value N here (N 32). and synchronization. which is located just before the first switching point in the Guard Period (GP) and after Timeslot 0. The mapping between Cell Parameter Identity (CPI) and the Basic Midamble Code used is given in 3GPP 25. Number of Pilots To scan the N strongest CPIs. The midamble is used as a training sequence for channel estimation. power measurements. as explained further below. which is transmitted in Timeslot 0 (TS0). different parts of the TD-SCDMA frame are measured. table 6.0 183 . The switching points are used to manage the transition between uplink and downlink (since TD-SCDMA utilizes TDD to separate uplink and downlink). NT12-7002 ver 1.223-840. located between the two data sections. SyncDL Top N Pilot Scanning This mode measures the Downlink Pilot Timeslot (DwPTS).3. 17. the UE acquires the timing of the DwPTS by correlating with the SYNC-DL code transmitted in the DwPTS. TD-SCDMA Scanning 17. The DwPTS is used for downlink synchronization. The scanner automatically finds the strongest CPIs. etc. Ec/Io will not be reported. Sorting of Cells You can sort TD-SCDMA cells in scanning information elements in a number of different ways. Select “Midamble Top N” or “SyncDL Top N”.3. Double-click the item “TD-SCDMA”.3. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events. See Information Elements and Events. the cell with the next higher CPI appears at argument index 2.2. See section 13. section 8. The sorting order is set in the General window. 17.1. The modes are described in the introduction of section 17.1. so that a cell with CPI n is always found at argument index n + 1.3.1 User’s Manual PN Threshold Remaining Measurement Points Measurement Mode If the Ec/Io value is below the PN threshold.TEMS Investigation 14. A dialog appears with these sorting options: • 184 . 17.4) is fixed and is not affected by the General window settings. section 3. Sort by Cell Parameter Id: Cells are sorted in order of ascending CPI. Presentation of Pilot Scan Pilot scans are presented in a suite of predefined charts and status windows.5.2. 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. so that the cell with the lowest CPI appears at argument index 1.4.3. • • • • • Open the General window from the Navigator. 4.2.4.1. Presentation of RSSI Scan RSSI scans are presented in a suite of predefined charts. You make the selection under General settings Technology. 17.4. Scanners with both TD-SCDMA and GSM capability can do an RSSI scan on either of these technologies. NT12-7002 ver 1. See section 13. See Information Elements and Events. TD-SCDMA Scanning 17.Chapter 17. see section 17. Setup of RSSI Scan What UARFCNs to scan is set in the General settings.2. The GSM RSSI scan is configured in the usual manner as described in section 14.4.0 185 .3.1. section 8.5. RSSI Scanning The RSSI scan returns narrowband or wideband channel aggregate power.2. 17. Bandwidth Remaining Measurement Points Bandwidth to scan: either “Normal” (wideband) or “CW” (narrowband). Andrew i. chapter 13.TEMS Investigation 14.4 18.Scan scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual. supported using the various devices as indicated.3. Scanning Methods TEMS Investigation offers these CDMA scanning methods. IS-95) RF channels with Andrew and PCTel scanners.3 18.1.1 User’s Manual 18. the device must have been purchased with the relevant option (wherever applicable).4. 18.6 186 Section Ref. PCTel MX CDMA Scanning Capability/ Scanning Device 1 18. section 10. CDMA Scanning TEMS Investigation supports scanning of CDMA (IS-2000. . Follow UE option not supported.Scan PCTel LX/EX Pilot scanning RSSI scanning Narrowband interference scanning Spectrum analysis 1. IS-856. See also the Getting Started Manual. Please note that for a scanning method to be actually available in TEMS Investigation. How to configure the Andrew i.1.5 18. Ec/Io detection threshold in dB. Min: –24. Setup of Pilot Scan: Andrew Minimum time for scan in ms. Max: 16. Max: 0. Max: 32.1. The PN increment.2.3. 18.0 187 . CDMA RF channels to scan within the selected band. Compare the discussion of the corresponding parameters in section 18. Must be divisible by 128. EV-DO: Scan correlation length in slots. Min: 512. 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. CDMA: Scan correlation length in chips. Entering the number N means scan the N strongest pilots. scrambled with cell-specific PN sequence offsets. Up to 12 RF channels can be selected. Scan Rate Report Threshold Number of Top N PN Increment Correlation Length NT12-7002 ver 1. Min: 1. 18.Chapter 18.3. Pilot Scanning This method scans pilots.3. Each channel is specified as a number representing the center frequency of the channel. CDMA Scanning 18. Max: 2048. Min: 1.2. common to all selected RF channels. General Settings (Not Technology-dependent) Type of Scanning The set of pilots (PNs) to scan on each RF channel is composed in one of the following ways: • Scan selected: User-defined. the scanner automatically finds the strongest pilots. The setting –20 dB is recommended. one PN scan on a CDMA2000 frequency and one on an EV-DO frequency. or the 32 strongest pilots on the RF channel currently used by a CDMA phone that is also activated in the application. If the PN threshold is set too low. The latter option is activated by setting “Follow UE” to Yes. static set of pilots (up to 512. regardless of technology. are presented within the information element range “1st” … “12th”. the Delay Spread values will be affected by random noise more than may be desired.2.e. In either case.TEMS Investigation 14. The output to information elements remains exactly the same with this setup: All scanned frequencies. only the first 12 selected for scanning are presented. no restriction on number of pilots). i. Entering the number N means scan the N strongest pilots. If a total of more than 12 frequencies are scanned. Max: 32. Min: 1. Setup of Pilot Scan: PCTel With PCTel SeeGull MX and EX scanners. PN Threshold 188 . This is a signal code power threshold (in dB) used for the Delay Spread measurements.1 User’s Manual 18. Here you pick the pilots you want to scan. up to N = 32) on each RF channel.3. multiple concurrent PN scans can be performed: for example. Scan strongest: The strongest pilots (“Top N”. By raising the threshold you reduce the influence of random noise correlations. This field is visible if Type of Scanning is set to “Scan strongest”. • Selected Numbers Number of Pilots This field is visible if Type of Scanning is set to “Scan selected”. and you will thus be able to discern multipath and fading effects more accurately. 0 189 .Chapter 18. of the time window in which the pilot is searched. are applicable only in “Scan selected” mode. The maximum pilot window length supported by the scanning receiver is 64. TEMS Investigation will filter the list of selectable PNs: for example. CDMA Scanning Remaining Measurement Points See section 13.1. Wide (128 chips). 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.. Settings Specific to EV-DO (IS-856) Pilot Window Length This parameter indicates the length. 6. The maximum radius within which to detect pilots. 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. only the PNs 0. . This parameter. will appear in the list. If a pilot increment is used. Start Pilot Pilot Increment Max Cell Radius The index of the first PN allocated. if Start Pilot = 0 and Pilot Increment = 3. NT12-7002 ver 1. 3. Search Window Size Normal (64 chips). The PN increment. in chips..5. This is also the default and recommended setting. along with Start Pilot and Pilot Increment. or Wider (256 chips). 190 .1 The number of chips between the first and last pilot Ec/Io peak above the PN threshold. Each reported sample is typically based on a 10 ms measurement. These are two algorithms with different priorities. 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.TEMS Investigation 14. High Speed is faster and accordingly less accurate. This measurement does not appear as an information element. High Dynamic puts the emphasis on accuracy. it is only found in scanner reports. High Speed and High Dynamic. Remaining Options Measurement Mode (EX only) There are two choices. 1.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. and 3072 for IS-856. and RF channel information is taken from the phone. Follow UE. Pilot Sync Only: The scanner will rely exclusively on the Pilot and Sync channels for timing. • • • GPS Only: The scanner will rely exclusively on its internal GPS for timing. The scan will then cover the 32 strongest pilots on the RF channel that the selected phone is currently using. Selected UE If this is set to On. This setting is enabled only if the scanner has been purchased with the Sync Channel Timing option. Without the Sync Channel Timing option. not for IS-856. The default and recommended value is 2048 for IS-2000 and IS-95. protocol. a further field “Selected UE” appears where you select which CDMA phone the scanner should follow. GPS Preferred: The scanner will use its internal GPS for timing whenever possible and resort to the Pilot and Sync channels in other cases. the scanner follows along automatically. The band.Chapter 18. the scanner can only use its GPS for timing.0 191 . If you choose this option. When the phone switches to a different RF channel. all other controls in the dialog are disabled. The Timing mode setting is applicable for IS-95 and IS-2000 only. Pilot synchronization allows the scanner to operate in indoor environments where GPS coverage is lacking. Setting this parameter high improves the accuracy and reliability of the output but also slows the scan down. Integration (Chips) This is the number of chips over which each signal energy value is integrated. CDMA Scanning Timing Mode Here you select by what method the scanner should synchronize to the base station’s transmissions. NT12-7002 ver 1. 1 User’s Manual 18. The updating rate is chiefly dependent on the number of live signals encountered in the network. Sort by increasing Ec/Io.3. the pilot with the lowest index appears at argument index 1.3. whereas for the “Top N” scan the number N is only marginally important (since all pilots have to be searched regardless of N). Pilots are sorted by ascending PN offset. Each bar chart by default presents peak Ec/Io for each pilot found. regardless of RF channel.4. A dialog appears with these sorting options: • 192 .2) is fixed and is not affected by the General window settings. section 3. For a manually selected set of pilots.TEMS Investigation 14.3. 18. etc. Customizing the Presentation Sorting of Pilots You can sort pilots in scanning information elements in a number of different ways. Sort by Pilot PN: Pilot PNs are sorted by index. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events. Double-click the item “CDMA”. The sorting order is set in the General window. pilot PN n is always found at argument index n + 1. 18. • • • • • Open the General window from the Navigator. 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.3.1.5. that is. the pilot with the next higher index appears at argument index 2. Presentation: “PN Scan” Bar Charts The PN Scan bar charts present pilot scan data. One predefined bar chart is provided for each RF channel scanned.5. Sort by fixed position: Pilot PNs are sorted by index and are always assigned the same argument indices. 18.3. Sort by decreasing Ec/Io (default). protocol and RF channel information are taken from the phone.1 When the phone switches to a different RF channel. This setting applies to all channels you select for scanning. all other controls in the dialog are disabled.. the bandwidth is 30 kHz.2. etc..2288 MHz. CW: “Condensed” or CW band.Chapter 18. n + 26] if 79 n 275. in the “CDMA” category). n + 13].1. NT12-7002 ver 1. • • Normal: CDMA band.. on the 450 MHz band. For the PCS (1900) band. Specifically (n = phone’s RF channel number): on the 800 MHz band. Remaining Measurement Points Follow UE See section 13. RSSI Scanning Setup of RSSI Scan Select Normal or Continuous Wave (“CW”). otherwise [n – 33 . For the cellular (800) band. If you choose this option.. Bandwidth Regardless of the choice made here. This option is not available for EV-DO.. bandwidth 1... 18. n + 33].4. the measurements are extracted to the same information elements (Scanned RSSI.4. RF channels [n – 13 .5. 1. 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). 18.1..4. RF channels [n – 21 . on the 1900 MHz band. CDMA Scanning 18. Presentation: RSSI Scan Bar Chart This bar chart displays RSSI for each RF channel scanned. the bandwidth is 50 kHz. n + 21]. RF channels [n – 26 . The band. the scanner follows along automatically.0 193 . 1.1.TEMS Investigation 14. thereby obtaining an even clearer view of the problematic signals. As regards the rest.5. • • Interference Offset Open the General window and double-click the CDMA item. 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.2. see section 18. Remaining Measurement Points 18.1. In the dialog that appears. Once you have done a narrowband interference scan to identify interferers.1.6) but is considerably faster.2.1.5.5.5. 18. Specifically. For the cellular (800) band the scanned bandwidth is 30 kHz. The narrowband interference scan has lower resolution than the spectrum analysis scan (see section 18.1 User’s Manual 18. Narrowband Interference Scanning In this mode the scanner scans a narrow band centered around a specific RF channel. Presentation: Narrowband Interference Scan Bar Chart The results from this scanning method are presented in the CDMA Narrowband Interference Scan Bar Chart: 194 .1. 18. 18.5.5. you can proceed to perform a spectrum analysis in the relevant frequency range. 18. enter the Interference Offset in dB. and for the PCS (1900) band it is 50 kHz.2. This is a threshold governing how strong an RF channel must be in order to be regarded as an interferer. Setup of Narrowband Interference Scan General Settings Under Channels.5.3. Context Settings See section 13. you select a single RF channel around which to scan. identifying other sufficiently strong RF channels as interferers. 1.0 195 . This chart uses a special. CDMA frequency band to scan. 18.6. Spectrum Analysis This scanning method shows downlink signal strength as a function of frequency. CDMA Scanning Each bar in this chart represents an RF channel.1.6. section 7.1). See Information Elements and Events. Green: The RF channel is not an interferer according to the Interference Offset criterion. 18.6.3. 18. An event “Narrowband Interference” is reported when an in-band interferer is detected.1. Technology Band NT12-7002 ver 1. predefined color coding: • • Yellow: The RF channel is an interferer according to the Interference Offset threshold criterion entered (see section 18. Setup of Spectrum Analysis Scan General Settings Choose the relevant CDMA technology.5.Chapter 18. 4.2. on the other hand. the legend pane will list all samples. See section 15. Given in MHz. 196 . the highest selectable resolution being 5 kHz.6. High end of the frequency range to be swept by the scan.5. 18.1. Presentation of Spectrum Analysis Scan Spectrum scans are presented in a predefined bar chart. • • Context Settings The Andrew-specific settings are the same as for LTE. See section 16. 18.2.1.3.6.TEMS Investigation 14. Given in MHz. In the presentation window. can of course only distinguish the samples as far as the screen resolution permits. section 8. the chart.2.1 User’s Manual Start Frequency Stop Frequency Resolution Bandwidth Low end of the frequency range to be swept by the scan. The PCTel-specific settings are the same as for WCDMA. Interval between successive scan samples in kHz.5. See Information Elements and Events. 1. Channels Technology NT12-7002 ver 1.4.Chapter 19. and the associated OFDMA bandwidth. 19.1. How to configure the DRT scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual. WiMAX Scanning 19. WiMAX Scanning TEMS Investigation has the ability to scan WiMAX carriers with a DRT scanner. Each channel is specified as a number representing the center frequency of the channel. Always “WiMAX” at present.4.1. chapter 12. General Scan Settings Regardless of scanning method. For more information.2. • • • Scanning Methods WiMAX scanning methods are as follows: WiMAX preamble scan RSSI scan Spectrum analysis 19. section 10. see section 19. Regarding band support. see the Getting Started Manual. WiMAX channels to scan within the selected band. you need to set the following: Band WiMAX band to scan: one of the bands (WiMAX RF Profiles) supported by the scanner. Up to 1500 channels can be selected.0 197 . currently either 5 or 10 MHz). If you are using a DRT scanner with the optional multimedia card (MMC). (This logging has got nothing to do with TEMS Investigation. WiMAX RF Profile. you can optionally record a logfile with scan data on the MMC as well.3. The bandwidth scanned during preamble scanning is that of the selected band (i. each subframe is preceded by a preamble. Scan Type • Logging Mode When using a DRT scanner purchased with TEMS Investigation. Set the number of preambles to report under Top N. • • MMC: Log to MMC. None: Do not log to MMC. 198 . Specify the preambles under Preamble Index List. Enable Preamble Power Enable Preamble CINR Calculation of preamble power.trp).e.TEMS Investigation 14. Up to 100 preambles can be tracked simultaneously.3. Preamble Scanning The WiMAX air interface uses OFDM as modulation method. The carrier is the desired signal. Setup of Preamble Scan • Targeted: Select this if you wish to scan a fixed set of preambles. The preamble is used for synchronization and channel estimation purposes. Within an OFDM frame.1 User’s Manual 19. Top N: Select this if you wish to scan the strongest preambles. and the interference can be either noise or co-channel interference or both. Calculation of CINR. the scan data is always recorded in regular TEMS Investigation logfiles (*. Carrier to Interference-plusNoise Ratio.) The MMC must have been formatted and inserted into the scanner before the scanner is powered on. regardless of how this parameter is set. 19.1. that is. 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. cluster size N = 1 will be used for CINR measurement.Chapter 19. CINR will be measured over all segments. If set to True. It should normally be enabled. Measurement of downlink MAP pilot power. Measurement of delay relative to GPS. Robust mode.0 199 . or Rogue mode. Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. cluster size N = 3 will be used for CINR measurement. Measurement of channel response in time domain. Measurement Mode Enable Channel Response: Time Domain Enable Channel Response: Frequency Domain Measurement of channel response in frequency domain. since otherwise high level signals may saturate the receiver and cause errors. NT12-7002 ver 1. that is. Measurement of downlink MAP pilot CINR. Measurement of multipath delay spread. Measurement of downlink MAP data power. CINR will be measured for each segment. One of Fast mode. If set to False. Threshold (in negative dB) below which no preamble detection is reported. Here you specify how many preambles the scanner should report. Here you specify the indices of the preambles to scan. These include the burst profile for each user. the actual number of samples used may be smaller. CINR) to be computed. which defines the modulation and coding scheme used on the downlink.TEMS Investigation 14. Decoding of Downlink Channel Descriptor (a message containing information about downlink characteristics). 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 . The number of samples on which to base each computation of measurement statistics. setting the field to N causes the scanner to return the N strongest preambles. Compare Enable Downlink Map Decoding. Decoding of downlink MAP messages. However.6). This must be set on for measurement statistics (mean and standard deviation for RSSI. section 3. This field is editable if you have set Scan Type to “Targeted”. as reported in the “Samples Taken” information elements (see Information Elements and Events. Decoding of uplink MAP messages. Decoding of downlink Frame Prefix (DLFP). Threshold (in dB) below which data is not decoded.1 User’s Manual Top N This field is editable if you have set Scan Type to “Top N”. The Frame Prefix specifies the modulation type and number of symbols associated with one or several downlink bursts that follow the FCH. 3. NT12-7002 ver 1.6. 19. 19. select a bandwidth from the list. Setting this to Yes means that the scanning will be triggered at the start of a new WiMAX frame.4. The number of measurement points left to allocate.5. Logging Mode Bandwidth 19. Spectrum Analysis A spectrum scan shows downlink signal strength as a function of frequency. Bandwidth to scan.5. See Information Elements and Events.1. section 8. Length of time for block averaging in μs. Length of time for total averaging in μs. Valid for triggered scan only.Chapter 19. Setup of Spectrum Analysis Scan See section 19.6. Logging Mode Average Time Triggered Scan Offset Time (µs) Block Time (µs) Measurement Points 19. 19.1. Offset from start of frame in μs.3. WiMAX Scanning Enable UCD Decoding Decoding of Uplink Channel Descriptor (a message containing information about uplink characteristics). Presentation WiMAX scans are presented in a suite of predefined charts and status windows.0 201 . Valid for triggered scan only.1. RSSI Scanning Setup of RSSI Scan See section 19.4. is to provide information that is helpful in determining coverage. without any grouping by segment. is to provide information about all the sectors of a site. and handover targets for neighbor lists.TEMS Investigation 14. This can help identify improperly aimed antennas. or find crossed feeders. best server.1 User’s Manual The purpose of having views that are grouped by preamble index. rather than by RSSI or CINR. 202 . The purpose of having views sorted by RSSI or CINR. and WAP.2. section 10. multiple data connections can be maintained concurrently. HTTP. Service Control 20. Ping. phone devices sold with TEMS Investigation 14.1. Which of these are testable for particular cellular technologies is tabulated in section 20.1) normally support all types of script activities.Chapter 20. chapter 11 regarding preconfiguration of Fixed Wireless Terminals. it is not possible to do data service testing with any other devices at the same time. NT12-7002 ver 1. Introduction to Service Control The Service Control tool is used to control the actions of devices that you activate in the application.2.1. With multiple devices activated. SMS. FTP.1 Scanning can be scripted for all devices indicated in the introduction of chapter 13. Data service testing encompasses the following services and protocols: e-mail.3. UDP.trp). 1. TCP. for applying various control functions to devices. See the Getting Started Manual. video streaming. The recordings will be regular logfiles (extension . Service Control 20.0 203 . Capabilities of Devices Apart from technology-related restrictions as noted in section 20.1 (listed in the Getting Started Manual. However. MMS. • Special activities are available • • • 20. • • Circuit-switched voice and video calls are supported. for recording data collected while executing the scripts. such as RAT lock and band lock for AT commands. if an Ericsson Fixed Wireless Terminal is activated. VoIP. HTTP. Supported Services by Cellular Technology TD-SCDMA CS voice calls CS video calls E-mail FTP HTTP MMS Ping SMS UDP Video streaming VoIP WAP For scanning.1 User’s Manual Regarding other connectable devices. there are no technology-related restrictions.TEMS Investigation 14.4. The Service Control Designer The Service Control Designer window is where you compose service control workflows (scripts): 204 CDMA UMTS Service/Technology LTE . 20. it should be noted that data service testing with Ericsson Fixed Wireless Terminals is limited to FTP. What scanning devices can have their actions scripted is stated in chapter 13 (introduction). and Ping.3. 20. with numerous screenshots and examples (sections 20.16–20. In the Properties and Configuration Sets panes. 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). 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.Chapter 20.0 205 .15). for example all the details of accessing a particular FTP server. use the buttons at the top to toggle between the two display modes. and for execution flow control. In the Configuration Sets pane you define various entities that can be reused in any script. Finally some additional features of the Service NT12-7002 ver 1. First comes a hands-on tutorial on how to build and run scripts. for controlling devices.18). The Workflow pane is the area where you assemble your script graphically in the form of a flowchart.5–20. The rest of this chapter is organized as follows. Then follows a reference part cataloging all script activity types with their properties and associated configuration sets (sections 20. items can either be grouped into categories or be listed in alphabetical order. ) 1 2 • The Dial box is tagged by an exclamation mark. expand the Voice node in the Activity pane and drag the Dial item to the empty workflow. This means that the activity is not yet properly configured. Basics of Creating Scripts (with Voice) This section covers the fundamentals of creating a complete and valid script that is ready to be run.1 User’s Manual Control tool are covered.5. (The cross-reference here. 20.TEMS Investigation 14. and some reference material is given (sections 20. A similar exclamation mark in the Properties pane indicates the property that is undefined: “Configuration”. points to the reference section 20.16. just like others that follow. For purposes of illustration we will build a very simple script that dials single voice calls. Video calls are handled in similar fashion.20). 206 .19–20. • Add a voice dial activity to the script. To this end. Finish by clicking the Apply button. the configuration consists simply of the phone number to call. The example below uses a neutral designation “Voice Call Recipient 1”.Chapter 20.0 207 .) Give the configuration a suitable name. This is done in the Configuration Sets pane. • • • The Properties and Workflow panes are now updated with the configuration data. Service Control • What we need to do is to define a configuration set for the Dial activity. The call will be established and then immediately hung up (since the script has run to NT12-7002 ver 1. as will be seen later. such as one identifying the subscription having this number. For a voice dial. (In other cases it can be more complex. for which you will probably want to substitute something more specific. When just dialing a call like this. it will not have a duration. 208 .1 User’s Manual completion).10. 1 2 • Set the duration of the wait in the Properties pane: • Finally. use the Wait activity: compare section 20. The graphical user interface helps you position the Wait box correctly by means of guiding symbols and text. • Drag the Wait activity to a position just below the voice dial box.5.TEMS Investigation 14. add a Hang Up activity after the wait. To give duration to a call. Service Control If you want the script to control both caller and receiver.4 for guidance.1 for full details.3.16.0 209 . 20. only it contains many more parameters. Setting Up a Network Connection This section shows how to set up a network connection. which is a necessary preparation for running data services.10. turn to section 20. In particular. NT12-7002 ver 1.Chapter 20. • 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. • Expand the IP node in the Activity pane and add a Network Connect activity to the script. you need to specify whether to use RAS or NDIS.6. See section 20. if you have multiple network connect configurations defined.7. we will set up an FTP download as an example of a data service activity. Later on. point to it from the Configuration field in the activity properties. so you do not need to associate it with a configuration set. Then add a Network Disconnect activity at the bottom of the workflow. Setting Up a Data Service Activity In this section.6. Associate it with the “W995_Dialup_1” configuration set created in section 20.TEMS Investigation 14. you can pick and choose among them. The disconnect operation will take down the network connection. This activity needs no particular configuration.1 User’s Manual • Once you have the configuration down. We will use the data connection configuration created in section 20. • • First add a Network Connect activity. 210 . 20.6. 0 211 .Chapter 20. NT12-7002 ver 1. you need to create a configuration set representing the FTP server and how to access it. Insert an activity of this type between network connect and disconnect: • For the FTP Download activity. Again this is done in similar fashion as for previously created configurations. Service Control 1 2 • The FTP session itself is handled by the FTP Download activity. 8.dat from the FTP server with address 123.TEMS Investigation 14. We will reuse the configuration sets and activities from sections 20.7.6 and 20. 212 . reference it from the FTP Download activity in the same manner as before. One reason for doing this could be to measure the time taken by these operations.89.7. • After completing the definition of the FTP server configuration.67. in that order (they are found in the IP category).1 User’s Manual We will download the file My_10_MB_File. • • We begin with the FTP download workflow from section 20. This will detach the device from the PS network and then reattach the device. particularly for the purpose of computing KPIs. Stand-alone PS Attach and Detach In this section we will perform explicit PS attach and detach operations in isolation.45. At the start of this workflow. 20. logging in as user “TEMS_User”. add a PS Detach and a PS Attach activity. (The KPI computation itself is done using TEMS Discovery or TEMS Automatic. You are prompted to name and describe the snippet.10.9. Snippets A snippet is a fixed sequence of activities that is defined as a building block and can be reused as such.4. You can also save an arbitrary activity sequence as a user-defined snippet: • Select all of the activities by dragging the mouse pointer. The predefined snippets are also tailored to produce all data required to compute KPIs. Service Control PS detach PS attach See also section 20.) Compare chapter 33.9. then enter the File menu and select Save as Snippet. Example: The detach-plus-attach procedure in section 20. saving time and effort when creating new scripts.Chapter 20. For an example of such a predefined snippet in use.0 213 . see section 20. since it will recur in any script where you want to detach and then reattach to the PS network. 20.8 could be a good candidate for a user-defined snippet. NT12-7002 ver 1. Predefined snippets for all supported services are provided in the Activity pane. This is handy if you want to apply some operation to all of these activities – for example. • Suppose your script includes PS detach followed by PS attach as described in section 20.10. You can then encapsulate the PS Detach and PS Attach activities within a sequence. then drag them both (using the PS Detach box as handle) into the sequenceActivity1 box. 20.1.10.8.1 User’s Manual 20. to enable or disable them.TEMS Investigation 14. 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. 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. Sequences You can formally define a group of activities in a script as a sequence. Suppose further that you want a convenient means of turning the detach/attach activities on and off. 10.12. see section 20. 20. Here is an example. then after the FTP download has completed we want to continue with a video streaming session.) After a handover to GSM has occurred. (This is accomplished by imposing a “terminate on event” condition on the activity. then we want to abandon the download. To this end we use an if–else construct in the following manner: • First add a Network Connect activity.e.2.5. the activity should terminate. Service Control Compare section 20.2.0 215 . 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. i. Now if the phone is handed over to GSM.16. For full details on the Sequence activity. see section 20.15.5. 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.Chapter 20. Suppose the phone is on a WCDMA network and is instructed to do an FTP download. so that the throughput is sharply reduced. If on the other hand the phone remains on WCDMA. 216 .5 and 20.3. Result = Stopped by Event. by default “ftpDownloadActivity1”. so that the right-hand branch will be executed whenever the condition in the left-hand branch is false. While Loops While loops are used to repeat a sequence of activities a predetermined number of times. set Condition Type to Activity Result.TEMS Investigation 14. (Not shown in the screenshot below. This always evaluates to true. • Suppose we want to execute an FTP download five times over.2. and set the associated attributes as follows: Activity = the name of the FTP download activity. Operator = Equals. This is done just as in sections 20. See section 20. as described in the introduction of this subsection. 20. For the right-hand branch (“ifElseBranchActivity2”).16.1 User’s Manual – For the left-hand branch (“ifElseBranchActivity1”). set Condition Type to Any.7 and is not detailed here.10. See next screenshot.1 for full details on the If–Else activity.) – • Add a voice dial activity on the left (to the node “sequenceActivity1”) and a streaming activity on the right (to the node “sequenceActivity2”). then fill it with the desired contents. you first add the empty While construct to the workflow.Chapter 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. You can accomplish this by appending a Wait activity at the end of the FTP snippet: NT12-7002 ver 1. • • Now drag the predefined FTP download snippet into the while loop. Below. (Just as with sequences – compare section 20. we stipulate that the loop should be run five times in total. set the number of times you want to iterate the while loop.) In the Properties pane. Service Control • Begin by dragging a While activity to the start of the workflow.10. by entering the value 5.0 217 .1 –. if one phone is to place a voice or video call to another.2 for full details on the While activity. one dialing and the other answering.4.1 User’s Manual • Set the duration of the wait in the Properties pane: For example. See the screenshot below.4.10. Parallel Activities All scripts so far have been written for a single device engaged in one activity at a time. To create a branching structure for these concurrent tasks. caller and receiver must be put in parallel. However. the script will perform five FTP downloads in succession with a 10 s idle interval between downloads. we use the Parallel activity from the Control Flow category. where EQ1 calls EQ2: 218 .TEMS Investigation 14. 20. Example 1: CS Voice/Video – Caller and Receiver For example. or assign multiple parallel activities to the same device. if you set Duration to 10 s. a script can also control the activities of multiple devices. 20.2. See section 20.1.16.10. one performing downloads over FTP and the other two looping short voice calls.4.0 219 .Chapter 20. This will become an outer loop repeating the various activities that will be included in it.2. NT12-7002 ver 1. For this purpose we need to build a somewhat more complicated workflow. Suppose that we want to control three UEs in parallel. 20. Example 2: Concurrent Activities on Different Devices Next is a slightly more complicated example. • First add a While activity and set it to run 10 times. as detailed in this section. Service Control A parallel structure is also recommended for MMS send/receive.10. right-click the “parallelActivity1” box and choose Add Branch from the context menu. To this end.) Drop a Parallel activity inside the while loop.TEMS Investigation 14. (The Sequence activity is created automatically. • • Since the Parallel construct by default provides only two branches. The structure is now expanded with a third branch: 220 . but in this case we do not need it at the topmost level – compare the steps that follow. we need to add one more.1 User’s Manual • Remove “sequenceActivity1” by selecting it and pressing Delete. 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. This is done in the Properties pane or from the context menu for each activity. Service Control It is now time to define the service-related activities. To assign the activities to the correct devices.0 221 . branches 2 and 3 of the workflow should have the following structure: NT12-7002 ver 1. After these steps.Chapter 20. Add a voice call snippet (a predefined one is found in the Activity pane) to each while loop. TEMS Investigation 14.1 User’s Manual • Next. define the FTP task for device no. the voice sequences have been collapsed to clarify the overall structure of the workflow. 1. All you need to do here is to add an FTP download snippet to branch 1 and associate it with a functional configuration. 222 . In the screenshot that follows. ) NT12-7002 ver 1.16. Note: When composing a script for multiple concurrent data service sessions using multiple devices. it is wise to make sure that these sessions are not all initiated simultaneously.3 for full details on the Parallel activity. allowing at least a few seconds between successive initiations.Chapter 20. It is better to let the sessions start one at a time. Insert Wait activities as appropriate to achieve this. See section 20. which contains only one data service session. Service Control This script will conduct a total of 10 FTP downloads and 2 × 5 × 10 = 100 voice calls.2. (No such Waits are present in the above example.0 223 . branch 2: Wait with duration 2 s. Insert short waits as appropriate to stagger the start times.2. each activity adds a unique prefix to the target file name (refer to section 20. When assigning multiple scanning activities to the same device.16. and Ping.9 for details). 224 . provided that the device supports it.3. it is best not to start all of the scans at the exact same time. HTTP.4.4. e-mail.1 User’s Manual 20. however. as exemplified in the following screenshot (branch 1: no Wait.10. to prevent file write conflicts. branch 3: Wait with duration 4 s).TEMS Investigation 14. Compare the similar advice in section 20. The activities concerned are those for FTP download/ upload. even multiple activities of the same type. The script shown below lets one device perform two concurrent FTP downloads.10.3. All instances of the FTP Download activity use the same configuration set. Example 3: Concurrent Activities on the Same Device The Parallel structure can also be used to run multiple activities concurrently on the same device. 5.0 225 . Scan activity.1. the execution proceeds to the next activity.5. 20. the Wait has the apparent effect of giving duration to that activity. see sections 20. Service Control 20.10..10.Chapter 20.. and it temporarily halts the execution of the workflow branch it is located in.10. After the wait time has expired. 20. or Start .16. NT12-7002 ver 1.4.9. See section 20. When following a (voice) Dial.2. and 20.7 for full details on this activity. The Wait activity also comes in useful whenever some tasks need to be cleanly separated in time for one reason or other.16. For some usage examples. Video Dial.3. Wait The Wait activity basically does nothing. and this construction is the most convenient method of controlling the duration.2. 20.10. This pattern will repeat until the while loop terminates. 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”). This is straightforward.6. To make the loop execute with the desired frequency.1 below.1 User’s Manual 20.10. see the reference section 20.10. The schedule can be set up in a number of ways. Wait For The Wait For activity can be used to: • • • Wait for a scheduled point in time.10. At the top of the loop. Add activities for the voice call (Dial. • • Create a While loop and set its termination condition to whatever you like.10. set Start to Immediately.3.1.2. Alternatively. – – • If you just want to start the dialing as soon as the script starts. Wait.6. the call duration has been set to 2 minutes.2.6. Wait for a particular kind of event to occur. See section 20. put a Wait For with Trigger = Schedule. Waiting For a Scheduled Point in Time Suppose we want a device to dial a short voice call once every 10 minutes. A special case is Wait For with periodic events: see section 20. See section 20.6.TEMS Investigation 14.8 for the fine points. • 226 . continue by setting Repeat to Yes and Repeat Interval to 10 minutes. Wait for another activity to finish with a predetermined outcome. providing a timing mechanism.16.5. In the screenshots below. This can be accomplished by putting the voice call inside a while loop which also contains a Wait For activity. Hang Up) just as in section 20.6. The loop will then pause at the Wait For activity each time until 10 minutes have passed since the previous turn. 10.Chapter 20. insert a While loop repeating voice calls. suppose that the voice service is tested by dialing one call after another. Set the Trigger property to Activity Result and stipulate that it should equal “Stopped by Event”.2. Then add activities for logfile recording beneath the Wait For: Start Recording followed by a Wait with Duration = 1 min and finally Stop Recording.0 227 . Again taking CS voice as a simple use case. put a Wait For activity at the top monitoring the voice calls. If a call proceeds normally. 20. In the left-hand branch. an alternative (“event-driven”) approach to data collection is to wait until something interesting happens and trigger recording only then.6. Configure the Dial activity to abort if the call is blocked (Abort property set to On Event with “Blocked Call” selected as trigger). we want to start a logfile recording to capture what happens over the following one-minute period. Service Control Left: Loop controlled by Wait For with Start = Immediately. we do not log any data. but if a call is blocked. • • Create a Parallel structure with two branches. In the right-hand branch. Waiting For a Given Outcome of an Activity Instead of collecting data continuously. Right: Loop controlled by Wait For with Start = Time of Day. • NT12-7002 ver 1. The rest of the loop contains the task to be performed. In this case. the script proceeds through the rest of the while loop. If such an event is generated. See section 22.1 User’s Manual If any call failures are of interest.4. Recording will then be triggered by any voice call that does not complete normally. Then a new whitelist check is done. so that the device performs its task once. Next. One natural application of this construction is to cell whitelists. and not only blocks. We can then construct a user-defined event for the condition and make that event periodic. 20. at the start of which a Wait For activity listens for the periodic event.3).6. signifying that the user is currently camping on an allowed cell. a script is written containing a while loop. etc. which means that it is generated repeatedly at fixed intervals as long as the condition is true (see section 22. the Wait For activity waits for a whitelist event. Wait For with Periodic Events Suppose we want to perform some kind of task whenever a given condition is satisfied. then set Activity Result to the catch-all value “Failed” instead.10. 228 .3.TEMS Investigation 14. If you add the Wait For first and create the userdefined events only later. the events will not show in the drop-down list for that particular Wait For instance. Service Control Note that user-defined events are prefixed with the string “User Defined:” in the Events drop-down box. simply drag a new Wait For activity into the script flowchart and use that one instead.1 20. Right: Selection of whitelist events (one for each RAT) as Wait For triggers. Using Run Script can be regarded as an alternative to saving and reusing snippets (see section 20.0 229 . they must exist when you add the Wait For activity to the script. and it may be preferable if you want to organize your scripts in modular fashion.Chapter 20. NT12-7002 ver 1.7. 1. Left: While loop with Wait For having event as trigger. 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. To resolve. See the image below.10. keeping down the complexity of each individual script. Please note in this connection that for the user-defined events to appear in the Events drop-down list.9). or copy by holding Ctrl and clicking.8. If you are selecting a number of consecutive activities and wish to preserve their ordering after they are moved or pasted.TEMS Investigation 14. (Whatever activity you use as handle will end up on top. the sequence depicted below might then be inserted in the while loop to stop execution at 3 p. 20.10. The activities do not have to be adjacent in the workflow but can be picked arbitrarily.1 User’s Manual 20. The editing commands work in standard Windows fashion. cut. Terminate The Terminate activity simply kills the whole script immediately and unconditionally. When dragging a selection to a new position in the sequence. suppose the script contains a while loop. Ctrl-click the activities from top to bottom in the same order as they come in the workflow.) The destination of a pasted item depends on what. The Wait For should then have Trigger = Schedule and Start = “Time of Day”. and Paste commands found in the Edit menu of the Service Control Designer window. You can also edit workflows using the Cut. Editing Workflows and Script Settings You can move activities around in the workflow by clicking and dragging. if anything.11. is currently selected in the workflow: • • • 230 . A few points merit special comment: • You can select multiple activities to move. The same operations can be performed from the window toolbar or from the context menu that appears when right-clicking a workflow item. For example.m. Copy. use the topmost activity as handle to preserve the ordering of activities. One possible application of this activity is to combine it with Wait For to stop a script at a fixed time of day. 17. or if a specific event occurs (Abort property). 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. Any except the ones mentioned in subsequent table rows. 20. You can have an activity aborted after a fixed length of time. since when composing a script it is not known what devices the activities will apply to.12.. retry the activity. For the RAT lock and band lock functions.0 231 . you can choose to skip that activity. The keyboard shortcuts Ctrl + C. For full details. see section 20. 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. Therefore. the Band Lock activity has bands from every supported technology selectable.Chapter 20. cannot be used for this purpose.2. note the following: • To copy. UE Control Functionality A number of control functions accessible from the Navigator (Equipment tab. • • Activity Properties That Control Execution All activities have some general properties governing their execution: If an activity fails. Service Control Item(s) Selected in Workflow None One or more arrows. and paste material in text fields. cut. While.13. 20. or terminate the entire script (On Failure property). bottom part. or Parallel activity 1.1) can also be applied in a script in the form of activities. etc. Activities tab: see section 9. it must be noted that the script activities are inevitably more generic in nature than the manual control functions. Regarding editing of text input fields in the Properties and Configuration Sets panes. use the context menu in the text field. it needs to be validated to ensure that it is syntactically correct and does not assign tasks that your devices do not support.15. You will be presented with the results.14 on validation).15. a UE control activity in a script can be executed only if the target device is capable of the operation in question.1 for full details on the UE control activities. when building more complex scripts involving multiple devices and control logic. all branches are synchronized before the execution proceeds past the point of convergence. Validation is also crucial for UE control functionality (see section 20. How to run only parts of a script is described in section 20. However.14. For uncomplicated scripts like our first example in section 20. • 232 .1.13). 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. 20. General Aspects of Script Execution • The devices involved in a script will execute their assigned activities independently of one another. 20. Validating Scripts Before a script is run. except when the devices engage in a service where they interact. In the latter case.15.1 User’s Manual and model) can only lock on the bands supported by the device. You can also explicitly have a script validated in advance: • • Enter the Script menu and choose Validate. In conclusion.15.TEMS Investigation 14. 20. If the script passes validation. the validation becomes a non-trivial issue. and when devices are involved in different workflow branches that converge. See section 20.5.16.5. you will receive a notification “Script validation succeeded”. A script is automatically validated when you start it. You will be notified if this is not the case (see section 20. this may seem trivial. See section 20. Monitoring Equipment Status On the Status tab of the Service Control Monitor. 20. Running Scripts from the Service Control Monitor Click the Open Script button and select your script (file extension .1. Click the Run Script button to start the script. See the Getting Started Manual.1 for further details and instructions. however. it is recommended that you disable IPv6 for all device modems. 20. unpredictable behavior may result. If it is.2. this is not recommended. Otherwise.15. you should wait until the receiving device has received the message before restarting the script.15.3.2. If you stop a script while an SMS or MMS message is being transferred.3.15.15. Click the Stop Script button to stop script execution. NT12-7002 ver 1. section 8.tsc). (The script validation does not extend to such usage.Chapter 20.2. the script will not work properly.15. Preparations 20. Windows 7/Windows Vista and IPv6 In Windows 7 and Windows Vista. one line is printed for each session. the keylock function must not be activated in any of the phones.0 233 . If a device is engaged in multiple concurrent service sessions. Service Control • It is possible in the application to run several scripts at the same time. • • 20.1.) When executing a script. the current status for each device is displayed. Viewing Statistics on Script Execution On the Summary tab of the Service Control Monitor. aborted. Running Scripts from the Service Control Designer • Enter the Script menu and choose Run. 234 . Below is an example (UDP with full duplex tested): 20. statistics are given on the outcome of each activity type (number of succeeded.15.2. 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. Click the Stop Script button to stop script execution.15.3.15.1 User’s Manual 20.3).TEMS Investigation 14.4. Clicking an underlined number in this table brings up a summary of each activity that has been run. Click the Return to Designer button to return to the Service Control Designer window. and failed activities). 0 235 .15. Service Control 20. For example. After disabling the sequence comprising the first two activities. You can easily disable any individual activity by right-clicking it or by changing the Enabled flag in the Properties pane. Suppressing Parts of a Script It may happen that you want to run only certain parts of a script and exclude others.5. An activity that is currently disabled appears dimmed in the workflow pane. as shown below. suppose we want to skip the initial detach/attach procedure.Chapter 20. the flowchart looks like this: NT12-7002 ver 1. 5.6.16. just set the Enable property to True again.1. 20.2. For example.1.16. Band Lock Locks the device to a subset of frequency bands. The details are analogous to the manual band lock function on the Navigator’s Equipment tab.3.1. Activate Activates the device so that it can be used in TEMS Investigation. To re-enable a disabled activity. Presentation of Data Service Testing See section 9. 20.10.3.1 User’s Manual Note: Be sure not to disable an activity that another activity is dependent on. Activities (Reference Section) This section also explains all activity-specific properties found in the Properties pane: that is.16.) 20. (Define a configuration for each AT command you want to send.16.16.15.1.1.TEMS Investigation 14. AT Sends an AT command. Control Activities 20. 20.17. This activity has no unique properties. • AT Command property: AT command string.1. Not all activities have unique properties. see section 9. those not covered in section 20. • Bands property: Specify band or bands to lock on. 236 . do not suppress an activity whose outcome is used to evaluate a subsequent If–Else condition (see section 20. 20.2).1. 1.1. Prefix property: You can add a descriptive prefix to the default logfile name. • Filemark property: Filemark text string. Description.1).4. The choice “No Technology” releases a lock that has been previously applied. Stop Recording Concludes the recording of a logfile initiated by a Start Recording activity (see section 20. A Start Recording activity must be paired with a Stop Recording activity (see section 20.7) and closes the logfile. • Equipment property: Here you select which devices to include in the recording.1.4. The selection is made at the EQ level.16.16.1. 20.1.16. 20.1. This activity has no unique properties.7. and Tags properties: These correspond to the identically named metadata fields that you can define when recording a logfile manually. Service Control 20.1.Chapter 20. See section 11. Filemark Enables automatic filemarks.1.16. Subject. or else manually from the Navigator – see section 8.1.16. NT12-7002 ver 1.0 237 . • • • 20.8. Deactivate Deactivates the device so that it can no longer be used in TEMS Investigation until you activate it again (using Activate.8) that concludes the recording and closes the logfile. The following characters are ignored if entered in this field: \ / : * ? ' < > | Directory property: The directory where logfiles produced by the script will be stored. Radio Access Technology Lock Locks the device to a particular radio access technology (RAT).16.6. Start Recording Starts recording of a logfile. By default all EQs are selected. recording MS but not DC for a particular device).1. 20.16. device channels cannot be distinguished (for example.5. • Technology property: Specify the RAT to lock on. see section 11. 1. For example. not only the devices that participate in the script (i. Evaluation of conditions proceeds from left to right. please turn to section 20.e.16. set Condition Type to Activity Result. 20.2. The following attributes are then visible: 238 .TEMS Investigation 14. If–Else This activity splits the workflow into two or more branches. Notes on Script-controlled Logfile Recording Note that logfiles always record data from all activated devices.10. 20. those that have some device-specific activity assigned to them). Control Flow Activities For a hands-on tutorial on how to use these activities. 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.9. insert a Wait at the end.16.g. in a loop that begins with Start Recording and ends with Stop Recording.4.1. “startRecordingActivity1”). If you want to avoid this. The automatic data buffering in TEMS Investigation may result in overlap between logfiles. Each branch of the construct. is constituted by an “if–else branch” activity which has the following property: • Condition Type property: To define a non-trivial condition. however.2.1. with a boolean condition attached to each branch. 20. identified by its name (e.16. as explained in section 11. Other methods of recording are independent of scripted recording and do not affect a script that is executing.1. See section 11. 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.1 User’s Manual • Recording Activity property: Here you select which Start Recording activity to stop. Operator: Boolean operator: “Equals” or “NotEquals”.3. A device can participate in more than one branch. One of: Succeeded. Time: Fixed execution time.2. Setting Condition Type to “Any” creates a condition that always evaluates to true.10. This value should always be used as a catch-all condition for the rightmost if–else branch. NT12-7002 ver 1.5). 20.2.2.16. There is no hard limit on the number of branches. (The running time is compared to the limit before a new turn begins.Chapter 20.) For an example of usage.2. see section 20.16. Stopped by Event.) Event: The while loop is terminated when any of the selected events is reported by the selected equipment. While This activity constitutes a while loop. Parallel This activity splits the workflow unconditionally into two or more branches. 20. For an example of usage.3. the while loop does not terminate immediately.2. (The If–Else construct is set up in that way by default. Result: The activity result that you want to match. rather. the current turn is completed first. Stopped by Timeout. Failed.0 239 . This activity has no unique properties. see section 20. Stopped by User. Each of the parallel branches is encapsulated within a Sequence activity (see section 20. provided that the device supports concurrent execution of the services involved (or several sessions using the same service). While loops can be nested arbitrarily.16. • Condition Type property: Count: Fixed number of iterations.10. Service Control Activity: The activity (identified by its name in the workflow) whose outcome will determine the value of the boolean expression. When this duration expires. It has no unique properties. and this construction is the most convenient method of controlling the call length. When following a (voice) Dial or Video Dial activity. See also section 20.10.10.2. For usage examples.2.4.4.) This activity has no unique properties. see section 20. allowing it to be treated as such.2.4.6. and 20.3. the entire sequence can be enabled or disabled in a single action. The situation with Start .16. For an example of usage. (For example.16.5. the Wait has the apparent effect of giving duration to the call. Scan activities is similar. 20. see sections 20.10. Furthermore.1.1 User’s Manual For usage examples. 240 .2.tsc) that you want to call.16.1.. as exemplified in section 20. • Script to Run property: Browse for the script file (*.16.7. Run Script This activity calls another script and is equivalent to inserting the whole of that script in its place. see section 20. Terminate This activity terminates the entire script immediately. 20. the execution proceeds to the next activity. It should be stored in the same directory as the calling script. After the wait time has expired.8. 20. The Duration property governs how long to wait. Wait For This is a conditional wait which lasts until a given condition is satisfied. 20.9. 20. 20. and in effect it temporarily halts the execution of the workflow branch where it is located.TEMS Investigation 14.16.8. Wait The Wait activity basically does nothing at all. Sequence This control structure formally defines a sequence of activities as a unit.2.2. 20..5. the Wait activity comes in useful whenever some other tasks need to be separated in time.10.10.10.16.7. there will be no repetitions.2. 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. see below. see section 20.6. Schedule: Wait for a point in time determined by a schedule (which is unrelated to any device activity). Additional fields Start. See the example in section 20. the wait will end as soon as any of the devices reports any of the events. Event: Wait for an event to occur. and Repeat Interval appear where you set up the schedule.6. Repeat: This option is intended to be used in loops and has an effect only within such a structure. Start = On The Hour: Wait for a new hour to begin. stated in the format hh:mm:ss. An example is given in section 20.10. Its use is best illustrated by an example. Repeat. if you specify multiple devices and/or multiple events.1. What it does is to reiterate the “wait for” procedure at regular intervals whose length is defined by Repeat Interval. An implicit OR relationship holds among devices as well as among events. If Repeat is set to No. That is. Equivalent to Time of Day with Time = hh:00:00.6. Start = Time of Day: Wait for a specified time of day (Time).10. Additional fields Equipment and Events appear where you specify the desired event(s) and the device(s) that should report it. • • • NT12-7002 ver 1.Chapter 20.0 241 . • Start = Immediately: No wait.1. Time.10. Result = Stopped by Event: The activity was aborted because a specific event occurred (Abort property set to On Event.6. Additional fields Activity. “Stopped by User” equates to the user right-clicking the activity in the Navigator and choosing Stop.17. Operator. • You must yourself ensure that the monitored activity has a position in the work flow where it will in fact complete to terminate the Wait For activity. see section 20. Result = Stopped by User: The activity was stopped by the user clicking the Stop Script button. “ftpDownloadActivity1 Equals Failed”.TEMS Investigation 14. • • • • Result = Succeeded: The activity completed normally.10.1 User’s Manual Activity Result: Wait for a particular outcome of another activity in the script.1 Result = Stopped by Duration: The activity was aborted because its maximum duration expired. 242 . Result appear where you detail the required outcome: for example.17. 1. For usage examples. If the activity is executed manually from the Navigator as described in chapter 9. again. see section 20.2.2). Result = Failed: The activity failed for whatever reason (other than termination by the TEMS Investigation user). This is not considered during validation. This can happen only if the activity has its Abort property set to On Timeout: see section 20. 16.Chapter 20. in the circuit-switched case.0 243 .3. (NDIS only. Note: For certain devices. Network Connect Establishes a data service connection. Ericsson Fixed Wireless Terminals must use an NDIS data connection. Whether NDIS or RAS is used is governed by the Mode parameter.) If your data collecting device is unable to perform the IP sniffing.) NT12-7002 ver 1. or you can ignore failure to start IP sniffing and go ahead with the execution anyway: ignoreIPSniffError="true". See section 20. (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. Please note that in either case. which by default reads: <dataServicesConfiguration ipSniffEnabled="true" ignoreIPSniffError="false" /> You can either disable IP sniffing by setting ipSniffEnabled="false". Be aware that in these cases.16.exe. Service Control 20. a PDP context is activated (UMTS) or a PPP session established (CDMA).3.1.1. using their connection manager applications. the phone works like an ordinary modem and performs a dial-up. whereas RAS can be used with both PS and CS. rather than automatically in the Service Control script.1 below for specifics in this regard on various devices and device categories. no KPI data can be collected. a Network Connection Lost event is generated. 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. If an Network Connect has previously succeeded but the connection goes down later on. the connection manager must be started to enable the Network Connect activity in scripts.config. NDIS can be chosen for packetswitched only. as detailed under Configuration below. – For other LTE devices. you can work around that problem by editing a line in the file <TEMS Investigation install dir>\Application\Investigation. In the packet-switched case. – Some LTE devices must be connected to the network manually.3.16. setting up an NDIS connection requires prior configuration using a software application delivered with the device. IP Activities 20. you must still include a Network Connect activity in your script. see the Getting Started Manual. Leave this field empty if an APN is specified in the device (always needed for NDIS) or for the modem in Windows. For CDMA/EV-DO. and on the Summary tab of the Service Control Monitor it will be noted that a connection was already available. as follows: *99***n#. enter *98*1#. the Network Connect activity will count as a failure.1 User’s Manual • Configuration property: Mode: Technology to use for connecting to the network: NDIS or RAS. RAS Phone Number: Phone number to use when performing a RAS dial. NDIS is first and RAS is second priority. If “Best available” is chosen. 244 . and you wish to avoid triggering a failure just because the device was already connected. For an NDIS connection to be establishable.1. For UMTS this is usually *99#. enter #777. Regarding devices for which the APN must be configured differently. The parameter is not applicable to other cellular technologies. For TD-SCDMA. if a CID other than 1 is to be used you need to specify that value. for example using an external connection manager. the Network Connect activity will count as successful anyway. NDIS CID: The CID (Connection Identifier) to connect with when NDIS is used.TEMS Investigation 14. however. • If set to True. UMTS/LTE APN: The Access Point Name to use for UMTS and LTE networks. If set to False. the device must of course support NDIS. 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. you cannot run the Network Connect activity twice without an intervening Network Disconnect. section 10. the second Network Connect will fail. If you do. • No matter how this parameter is set.6. This setting is useful if you want to be able to run Network Connect without full knowledge of the device’s previous activities. Service Control User Name. 20. and preconnected Network Connect will be used. Examples of models: AD600.Chapter 20.) Not applicable to circuit-switched. Doing so will cause a port conflict. 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”. Use Header Compression: Use of header compression for packetswitched. 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. 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. P936. the shorthand “CM” is used below for convenience.0 245 . • NT12-7002 ver 1.1. VL600. LG LTE Devices • • For LG LTE USB modems. MS910. MS840.1.) Not applicable to circuit-switched. Leave blank if this is provided automatically by the operator. LD611. G7. LG Generic: If the device is detected as “LG Generic”. Leave blank if this is provided automatically by the operator.16. (Property of PS bearer. IP Address: Local IP address. Primary DNS: IP address of the primary domain name server. (Property of PS bearer. For “connection manager”. enter user and password here. Network Connect performed from within TEMS Investigation is referred to as “scripted Network Connect”. If this is the case for you. Password: Certain operators require authentication in order to establish a data service connection. Use Data Compression: Use of data compression for packetswitched. Examples of models: LS840. FM300. do not use a CM.3. the connection must be set up either from a CM or from the device menu system. Leave blank if the IP address is provided automatically by the operator. G13. Qualcomm Android LTE smartphones generally require preconnected Network Connect. Novatel MC996D. or tethering must be enabled in the device menu system (preconnected Network Connect performed in either case). ZTE N910. no CM should be used with any such devices. R920. If no AT port is present in the operating system. GT-B3730. then start the CM or enable tethering from the device menu system. R820. provided they are detected as Sierra Wireless devices in TEMS Investigation. and TEMS Investigation will use preconnected Network Connect instead. These NDIS devices should likewise not require use of a CM: Huawei E1820. R940. or if the port is blocked. Huawei E353. If scripted Network Connect fails. No CM should then be used. Huawei M920. Examples of models: I510. Samsung Android LTE smartphones do not have a CM accompanying them. 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. R900. TEMS Investigation then communicates with the CM to control the connection. • • • Qualcomm HSPA+ Devices and Other Devices • • Sierra Wireless devices should not need to have a CM running. Samsung LTE Devices • General procedure: If an AT port exists for the device.TEMS Investigation 14. With newer firmware. R910. 246 . GT-B3710: Some older firmware of this device without an AT port requires that the CM should be running. the device behaves like GT-B3730/3740: see next paragraph. TEMS Investigation will use that port to perform a scripted Network Connect. then the device must be configured using a CM. If no AT port is available.1 User’s Manual Qualcomm LTE Devices (MDM9x00 Chipsets) • • • Normally. TEMS Investigation will try to open that port and use it to control the network connection. a tethered connection must be set up. and a preconnected Network Connect will be performed. 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. You cannot have the CM running when executing the Network Connect and Network Disconnect activities. ZTE Z006Z. PS Attach Performs a packet service attach. This activity may be useful to make sure that the phone is not attached to the packet service when starting a measurement (for example.16.) This activity has no unique properties.3.3. Devices not mentioned in the foregoing generally require preconnected Network Connect. Note that in such cases. this activity has no effect.16. This activity has no unique properties. 20. 20.1). section 20. If the device is already disconnected. no CM should ever be needed. if it has attached automatically at power-on).3. but it still counts as successful on the Summary tab of the Service Control Monitor. you can start the CM or enable tethering from the device menu system. Service Control If scripted Network Connect fails. In the packet-switched case a PDP context is deactivated (UMTS) or a PPP session ended (CDMA). PS Detach Performs a packet service detach. in the circuit-switched case the phone performs a hang-up. and TEMS Investigation will use preconnected Network Connect instead. For certain NDIS-capable devices.2.4.3. This activity has no unique properties. Note that this activity may not be needed since the device may have automatically attached to a PS network when powered on.16. 20. an NDIS connection must be terminated using the PC application accompanying the device (compare the Network Connect activity. NT12-7002 ver 1. and scripted Network Connect should work fine. it is still necessary to include a Network Disconnect activity in the script.3.16. • • For Qualcomm devices using a RAS connection.0 247 .Chapter 20. (Same behavior as for Network Connect with Succeed If Already Connected set to True. Network Disconnect Terminates a data service connection. a valid server name must be entered here. User Name: User name of account on the server.6. • Configuration property: Proxy: The proxy server to use.16. SIP Register Causes the device to register with a SIP or IMS server. Note that you do not have to use this command to obtain the data required for KPIs.16. This activity has no unique properties. A user account must exist on the server.3.16. May be omitted. This is a necessary preparation for a VoIP call.3. see sections 20.7. SIP Unregister Causes the device to unregister from a SIP or IMS server used for VoIP.16. Domain: The domain to register with. 20.1 User’s Manual 20. 248 .TEMS Investigation 14. Start IP Sniffing Starts capture of IP packets.7. such data is collected automatically. 20.7.3. If Proxy is not used.6. Password: Password for the server account.5. 20.5. Compare chapter 33.16. This activity has no unique properties. Note also that you can conduct TCP load tests with the Network Bandwidth activity (see section 20. If you choose Full packet size. (Packets are filtered with respect to IP address.3. 20. and port. Note: This means that all packets belonging to any service used by the PC will be captured. any further bytes in the message will be truncated. Service Control • Configuration property: Packet Size: Determines how many bytes of each message will be presented. (Packets are filtered with respect to IP address only. This is frequently the preferable setting.15). 20.16.9.16. • Optimized Performance: Capture of IP packets is reduced to the minimum needed to compute KPIs. None: No filtering of IP packets.16. Please be aware that paths and file names must have correct case throughout.Chapter 20.0 249 .3. NT12-7002 ver 1.) Headers Only: The first 54 bytes of every IP packet are captured.8. all messages are presented in full and the entire header is always decoded.3. Filter: Type of filtering to apply to IP packets. Stop IP Sniffing Stops capture of IP packets initiated by the Start IP Sniffing activity.) • • The information element TCP Packet Loss and the event IP Interruption Time require that the Filter parameter not be set to “Optimized Performance”. FTP Download Downloads a file from an FTP server. protocol [TCP/UDP]. If you choose a fixed packet size. 250 . e. if applicable. and file name describing where to store the file on your computer. 20.16. Local Data Port: The data port the client will use for FTP download.dat. Note that it is essential to set this correctly.10. The address may not contain a path to a subdirectory. path. if the file is in the root directory.3. this is the default setting.dat. User: User name on the FTP server. if required. C:\targdir\targfile. Server Address: The IP address or host name of the FTP server. The drive letter must be included. Target File: Drive letter. enabling or disabling passive FTP as defined in IETF RFC 959. Valid only when Firewall Mode = PORT.dat. srcdir/srcfile. Account: Account name on the FTP server.1 User’s Manual • Configuration property: Source File: The path and name of the file residing on the FTP server. If multiple FTP Download activities execute in parallel. multiple files are created. If the Target File field is left blank.g.g.g. 1targfile. if required. Firewall Mode: PASV or PORT. type the file name only. e. Server Port: The port on which the FTP server listens for requests. FTP Upload Uploads a file to an FTP server.TEMS Investigation 14. e. each with a unique session ID prefixed to prevent conflicts. No explicit root symbol is used (no leading slash). Note that the correct orientation of the slashes is dependent on the FTP server operating system. No ftp:// prefix is to be used. The default port number is 21. no files are stored.dat. A session ID (integer) is prefixed to the file name.: 0targfile. Please be aware that paths and file names must have correct case throughout. Password: User password on the FTP server. Note. Server Address: The IP address or host name of the FTP server. if applicable. e. The drive letter must be included. a temporary file is created holding the data to upload. Local Data Port: The data port the client will use for FTP upload. G = gigabyte. if you type a file name only. Alternatively. Firewall Mode: PASV or PORT.dat.dat. Note that the correct orientation of the slashes is dependent on the FTP server operating system. A session ID (integer) is prefixed to the file name. however. Size to Upload: Size of the file to upload (only valid if Use Temporary File = True).g.0 251 . User: User name on the FTP server. C:\srcdir\srcfile. Use Temporary File: If set to True. No ftp:// prefix is to be used. 1targfile. enabling or disabling passive FTP as defined in IETF RFC 959. NT12-7002 ver 1. Service Control • Configuration property: Target File: Path and file name describing where and how to store the file on the FTP server. if required. K = kilobyte. No explicit root symbol is used. The address may not contain a path to a subdirectory. Source File: Drive letter. e. Server Port: The port on which the FTP server listens for requests.g. Account: Account name on the FTP server. If set to False. each with a unique session ID prefixed to prevent conflicts. each instance must use a unique target file name. The default port number is 21. M = megabyte. that if multiple instances of TEMS Investigation installed on different PCs are uploading to the same server. path. multiple files are created. It is possible to specify the unit as follows: B = byte. the number you enter is interpreted as a byte count. e.dat. lowercase letters can be used with no difference in meaning. If multiple FTP Upload activities execute in parallel.: 0targfile. and file name identifying the file to be uploaded. no file is created. if required. Note that it is essential to set this correctly.dat. the file will be written to the root directory.Chapter 20. T = terabyte.g. targdir/targfile. If you do not specify a unit. Valid only when Firewall Mode = PORT. Password: User password on the FTP server. An additional field Time appears for entering the desired session duration.3. see below.1 User’s Manual 20. • • TEMS Browser: The internal Web browser in TEMS Investigation is used.16. but not under Windows XP. Limitations on HTTP Session Concurrency At any given time. End Session After Payload Size: The HTTP session is ended automatically after a user-specified amount of data has been downloaded.11. Note that the main URL (specified under URL) is downloaded only once. Internet Explorer: Internet Explorer 9 is used. in a Service Control script. This is supported under Windows 7 and Vista.TEMS Investigation 14. Internet Explorer use is limited to one device at a time running one HTTP Get activity. Enter the number of bytes to download in the Payload Size field that appears. • Configuration property: Browser Client: Web browser used to conduct HTTP sessions. The time is counted from the moment the first HTTP packet is received from the server. 252 . Proxy Server Address: Proxy server address. not even with the TEMS browser. that device cannot execute any other HTTP Get activities at all. Client Threads: Number of concurrent threads to be used by the client in handling the HTTP session. Regarding concurrency limitations. While using Internet Explorer. Other devices can however employ the TEMS browser to run HTTP Get while Internet Explorer is in use. Therefore. End Session After Time: The HTTP session is ended automatically after a user-specified length of time. regardless of the number of threads. that is. Use Proxy Server: Select whether to use a proxy server for this connection. URL: Main URL to download. HTTP Get Downloads a URL from an HTTP server. Proxy Server Port: Proxy server port. TEMS Investigation can only make use of a single Internet Explorer session running on the PC. • CO and CL are used by WAP 1. • Gateway Address: (Appears when Connection Mode = CO or CL) The IP address of the operator’s WAP gateway. WP-HTTP is used by WAP 2. Gateway Port: (Appears when Connection Mode = CO or CL) The WSP port on the server.16.0. Connection Mode: One of CO (Connection-oriented).Chapter 20.0 253 . whereas with CL this is not done. the http:// prefix is optional. there are no restrictions on HTTP session concurrency. or WP-HTTP (Wireless Profiled HTTP). 9200 (CL). The default port numbers are 9201 (CO). Proxy Port: (Appears when Connection Mode = WP-HTTP.3. • Configuration property: URL: URL of WAP page to download. CL (Connectionless). optional) The WAP proxy port number. The default is 8080. NT12-7002 ver 1. but this is optional. Note that WAP pages that redirect the user to a different page cannot be downloaded.x and require a WAP gateway. The WAP server can be specified as an IP address or host name. WAP Get Downloads a page from a WAP server. The difference between the modes is essentially this: With CO. the phone first contacts and performs a handshake with the WAP gateway before starting to request WAP pages. 20. neither for a single device nor for multiple devices. This WAP version may use a WAP proxy. Service Control When the TEMS browser alone is used. optional) The IP address of the WAP proxy. Proxy Address: (Appears when Connection Mode = WP-HTTP.12. . There is no upper limit. The application will then start out at a low throughput rate and gradually increase the throughput until the packet loss becomes excessive. 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.3.16.1 User’s Manual User Agent: This is a string indicating. How to install and configure this software is described in the document “TEMS UDP Server User’s Manual”. The maximum size is 2000 bytes. Ping Initiates a sequence of pings.ddd. found on the installation CD in 254 . Given in the format hh:mm:ss. 20.3. Number of Pings: The number of pings to send. even if the service does not require these safeguards. • Configuration property: Remote Address: The IP address or host name of the server to be pinged.4. (Some WAP portals adapt their contents to the devices accessing them. UDP is more suitable than TCP for this purpose.TEMS Investigation 14.16. UDP testing is done against a PC that is running the application TEMS UDP Server. the make and model of the device and what WAP software it has installed. .1 20. among other things. You can let TEMS Investigation run the UDP test in an automated fashion.4 Profile/ MIDP-2.13.1 JavaPlatform/JP-8.14. Max Response Time: Maximum time to wait for each ping response. Given in the format hh:mm:ss.... since the rigorous acknowledgement and retransmission mechanisms of TCP (designed to guarantee full data integrity) will always slow down data throughput..) Example of User Agent string (for Sony Ericsson W995): User-Agent: SonyEricssonW995/R1DB Browser/NetFront/3. Packet Size: Size in bytes of the packet sent with the Ping activity.ddd.1 Configuration/CLDC-1. Interval Time: Time between consecutive pings. since the parameters are constrained by the relation (packets per second) (packet size) = throughput. However. If you select automatic mode. • Direction: • • • Send: The client sends UDP data to the server. If you select manual mode. For Full Duplex mode. using the parameters below. UDP Mode: • Automatic: The TEMS Investigation UDP client will automatically determine the optimum data rate. Please note that you cannot test Full Duplex in automatic mode. see the introductory text above. Specify the TCP control port to use here.0 255 . • Configuration property: Remote Address: The IP address or host name of the UDP server. all parameters are set by the application and cannot be edited. Service Control the subdirectory Documents. Throughput (kbit/s): The UDP throughput rate that will be used. The packet and throughput parameters work as follows. NT12-7002 ver 1. you specify the parameter values yourself. Duration (sec): The duration of the UDP session. Full Duplex: Data is sent in both directions concurrently. The TEMS Investigation application has a UDP client built into it which interacts with this server. this is the packet rate in each direction. the parameters from Packets Per Second onward (see below) are set automatically and are not editable. when you change one parameter the others will be adjusted so that the above equation still holds true. 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. Packets per Second: Number of UDP packets to send or receive per second. Manual: You specify the data rate and packet rate yourself. In this case. Packet Size: The UDP packet size (in bytes) that will be used.Chapter 20. Receive: The server sends UDP data to the client. is comparable to assigning multiple concurrent FTP activities to a device. They do not indicate the amount successfully transferred to the server.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. See the Getting Started Manual. Therefore.3.14. The client uses TCP to obtain this information from the server after the UDP session has concluded.3.10. section 3.6 for details. In contrast. the UDP Upload Throughput information element is no longer reliable. just as for other service sessions. See section 20. you need to check the summary statistics in the Service Control Monitor. Network Bandwidth (Iperf Testing) This activity measures maximum TCP and UDP bandwidth performance by interacting with an Iperf server.4.16. To find out what percentage of packets was actually received by the UDP server.15. • Configuration property: 256 . see the example in section 20. It must be kept in mind that the uplink UDP information elements in the category Data. see section 20. you must download the Iperf software and install it on the desired machine. section 5. Before you can use this activity. which are updated continuously in the course of the UDP session (see Information Elements and Events. UDP testing with the Network Bandwidth activity is similar to the UDP activity. Measuring over TCP.16.15. on the other hand.TEMS Investigation 14.8) only indicate the amount of data sent. 20.2.3. the UDP Download Throughput is always accurate.3. when the packet loss rate becomes nonnegligible. If you want to specify a port on which TEMS Investigation should listen for data (not required). see the Getting Started Manual. Duration: The duration of the Iperf testing session (hh:mm:ss). Password: Password on the remote server.6. UDP section (used for UDP only) Bandwidth: UDP bandwidth (throughput) in Mbit/s. Listen Port: See above. User: User name on the remote server. Protocol: The protocol to use for Iperf testing: TCP or UDP.2. Packet Size: UDP packet size in bytes. Receive: The server sends data to the client. Port: The port on which the Iperf server listens for requests. Please note that SSH2 requires a special TEMS Investigation license option. set this parameter to True and enter the port under Listen Port. no such port is specified. Buffer Size: UDP buffer size in kilobytes.Chapter 20.0 257 . Port: Port on the remote server. Direction: • • • Send: The client sends data to the server. Telnet/SSH2 section Connection Client: Either Telnet or SSH2 can be used as protocol. Path: Path to Iperf on the remote server. Use Listen Port: True or False. NT12-7002 ver 1. Full Duplex: Data is sent in both directions concurrently. Service Control General section Remote Address: The IP address or host name of the remote server. If you set the parameter to False. section 5. User: User name of e-mail account. Server Port: The port on which the SMTP server listens for requests.1. When composing an e-mail script controlling both sender and receiver. To: E-mail address of recipient.16.16. it is best to use a sequence structure with a waiting period: E-mail Send Wait E-mail Receive.TEMS Investigation 14. 258 . but a STARTTLS command is issued later on to set up a secure session.4. Security: • • • None: No security is applied.1 User’s Manual 20. Messaging Activities 20. Body Text File: Name of file containing e-mail body text. all with the following structure: PS Detach PS Attach Network Connect <data service activity> Network Disconnect.4. STARTTLS: The initial communication is not encrypted. • Configuration property: From: E-mail address of sender.16. Password: Password for e-mail account. SSL/TLS: SSL or TLS is used during the whole e-mail session. Server Address: The IP address or host name of the SMTP server.3. E-mail Send Sends an e-mail to an SMTP server. Predefined Snippets for IP One snippet is provided for each data service related activity.16. 20. Attachment: (Optional) Name of file to enclose with the e-mail as attachment. Subject: Content of e-mail Subject field. and attachments (if any). All e-mail contents are written to a single file: header fields.10. Password: Password for e-mail account.4 and 20. it is best to use a Parallel structure.2. User: User name of e-mail account. see section 20. Service Control 20. Security: • • • None: No security is applied.3. When composing an MMS script controlling both sender and receiver. it is best to use a sequence structure with a waiting period: E-mail Send Wait E-mail Receive. SSL/TLS: SSL or TLS is used during the whole e-mail session.16.4. the same as for the WAP Get activity. body text.Chapter 20. • Configuration property: Server Address: The IP address or host name of the POP3 server. Store Location: Full path to directory in which to store e-mails. Server Port: The port on which the POP3 server listens for requests.12.0 259 . When composing an e-mail script controlling both sender and receiver. E-mail Receive Receives an e-mail from a POP3 server. • Configuration property: Gateway section These are WAP settings. 20.16.16.3. NT12-7002 ver 1.4.2. See sections 20.16. but a STARTTLS command is issued later on to set up a secure session. MMS Send Sends an MMS. STARTTLS: The initial communication is not encrypted.3. MMS Receive Receives an MMS. Multiple recipients can be specified.16. is supported. A wide variety of file types. MMS Message Center section URL: The URL of the MMS Center (usually beginning with http://). • Configuration property: Connection Parameters section: Same as for Network Connect. separated by semicolons.16. A file with an extension unknown to TEMS Investigation will be sent as an attachment to the MMS (content type “application/octet-stream”).1. see section 20.3.TEMS Investigation 14. Gateway section: These are WAP settings. User.3. 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). Attachment: The file to send.16. Please note that operators generally impose a limit on the MMS file size. The MMS Receive activity needs its own connection parameters since logging in to the MMS Center frequently requires connecting to a different APN. including plain-text files and frequently used image file formats. the same as for the WAP Get activity. The receiving device can be identical with the sender. If you encounter problems sending MMS messages. 260 . 20.12.4. Password: Login credentials for MMS Center.1 User’s Manual MMS Content section To: The phone number(s) or e-mail address(es) to send the MMS to. try sending very small files to find out whether the size limit is causing the problem. see section 20. Message: Free text field containing the text message of the MMS (if any). if required.4. AT+CMGW. NT12-7002 ver 1. The SMS service is implemented with AT commands. SMS Message: SMS message string. Service Control 20. Delivery Report Timeout: Time to wait for the delivery report. To stick with the SMS Center indicated on the SIM. and AT+CMSS.5. the phone must therefore support the following AT commands: • • • UMTS: AT+CMGF with format 0 or 1 and AT-CMGS. SMS Send Sends an SMS. Configuration property: Receiving Device: The phone number or e-mail address to send the SMS to.0 261 . set this parameter to False.Chapter 20. Request Delivery Report: Set this to True if you want the device to request a delivery report from the SMS Center.4. Use Custom SMS Center: Set this to True if you want to make use of an SMS Center other than the one specified on the SIM. SMS Center: Phone number to SMS Center. The receiving device may be identical with the sender.16. For SMS Send activities to work. CDMA: AT+MODE. and no configurations have yet been defined for that activity type.1 User’s Manual 20. the activity waits for a matching message to arrive. 262 . any message will match. Scan Activities A scan activity starts or stops a scan task of a specified type. 20. The point of doing this is to catch a message already received by the device before it performs the SMS Receive activity. all with the following structure: PS Detach PS Attach Network Connect <data service activity> Network Disconnect. 20. If the field is left empty.TEMS Investigation 14. The choice made here determines the contents of the Configuration property. • Scanner property: Here you select the type of scanner to use.90). • • Message Match Pattern: The pattern to use for matching incoming or stored messages.5. If no match is found.7. Please note that if you add a scan activity to the workflow.microsoft. SMS Receive Receives an SMS.16.6. Search Text Messages in Device: If set to True.com/en-us/library/hs600312(v=VS.4.4. Predefined Snippets for Messaging One snippet is provided for each messaging activity. Use a Wait activity between Start and Stop to specify the duration of the scan. SMS messages stored in the device will be searched for matching messages.16. The syntax is that of . Ends with: Enter string under Message Match Pattern to match end of message text.NET Framework regular expressions. Reference: msdn. then you need to make a selection in the Scanner drop-down box to enable the Configuration Sets pane.16. • Configuration property: Match Type: • Regular expression: Enter regular expression under Message Match Pattern to match whole message text.aspx Starts with: Enter string under Message Match Pattern to match beginning of message text. 4 18. Below is a full list of the scan activities. keyed to their configuration descriptions: Ref.5 18.4 16.2 14.5 15. identical to that for a manually initiated scan.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.6 17.2 16. These are all described in chapters 14–19.4 14. 15.Chapter 20.3 18.3 15.0 263 .4 18.4 19.2 15.3 17.3 19.3 16.6 19. Descr.5 15. Service Control • Configuration property: Scan configuration. to Config.5 16. 17.. This activity has no unique properties. Video Activities 20. and p (for pause).16.. Predefined Snippets for Scanning One snippet is provided for each scan type.1.6.2.16.6. For a general discussion of video streaming testing.6.16. Hang Up Hangs up a video call. see chapter 27. 20.TEMS Investigation 14. After dialing. Answer Waits for an incoming video call to arrive and answers it when it arrives... Valid characters are: +. the device may retry the call. 9. • 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. 0. If this event does not occur. 20.2. The retry behavior is governed by the On Failure property. All of these have the following structure: Start . the device waits for the event Call Established.16.5.16. Scan Wait Stop . see section 20. 264 .. Video Dial Dials a phone number and sets up a video call.6.16.1 User’s Manual 20. This activity has no unique properties..4. see section 20.2. Streaming Download streaming video from a streaming server and play it in TEMS Investigation. *. Scan. . 20.7.6.1. #.. 20.16.3. Target File: Name and storage location for received streaming file. NT12-7002 ver 1. Streaming Server: The IP address or host name of the streaming server. Max: 20 s. Min: 1 s. The port entered and the three following ports will be allocated to RTP data. Rebuffer Length: Length (in seconds) of segment to buffer during rebuffering.6. File To Stream: The file name of the video clip or streaming session description to be downloaded from the streaming server. “Live” means tapping into a live stream or repeating playlist delivered by a streaming server. Use Proxy Server: Specify whether to access the streaming server through an RTSP proxy server. WAP Streaming This activity is used to do streaming via a WAP page. Proxy Address: The IP address or host name of the RTSP proxy. By default ports 5004–5007 are used. Prebuffer Length: Length (in seconds) of segment to buffer during initial buffering. specify the duration of the streaming session here. The default port number is 554. Service Control • Configuration property: RTSP Port: The RTSP port on the streaming server. 20. Streaming Mode: “Normal” means downloading a video clip of known length (on-demand streaming).Chapter 20.3gp. The format is . the activity terminates. RTP Port: Here you specify ports to use for RTP on your PC. When this time has expired.16. Streaming Duration: For Streaming Mode = “Live”. Min: 1 s.5.0 265 . Max: 20 s. #.16. Dial Dials a phone number and sets up a circuit-switched voice call.6. the device waits for the event Call Established.16.12. 20. RTSP Port . This activity has no unique properties.TEMS Investigation 14..7.7.16. section 20.7. After dialing. 266 . and p (for pause). this should be the number to the Call Generator or MRU: see section 36. Voice Activities 20. The retry behavior is governed by the On Failure property. WAP Streaming snippet: PS Detach PS Attach Network Connect WAP Streaming Network Disconnect.17.16.16.1. you may instruct the device to retry the call.. Valid characters are: +.2. For AQM measurement.. Streaming Mode: See the Streaming activity. see section 20. section 20. User Agent: See the WAP Get activity. 20. URL . 0.16. Predefined Snippets for Video • • Video Call snippet: Video Dial Wait Hang Up.4.6. 20. 9. If this event does not occur.3.16. see section 20. The call duration is most conveniently specified by means of a subsequent Wait activity. • Configuration property: Phone Number: The complete phone number (including country code) to call.7.3..2.2. *.3.. Answer Waits for an incoming CS voice call to arrive and answers it when it arrives.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.6.. .. including PESQ/POLQA. M2M DL + UL: Mobile-to-mobile audio quality measurement using Audio Capturing Unit (ACU). Channel4: Channel for phone connected to LINE IN 4/ LINE OUT 4. AQM Duration: The length of time for which to collect audio quality measurements (hh:mm:ss). Service Control 20.7. • Configuration property: Algorithm: One of PESQ.7.3. See chapters 35–37. M2M DL: Mobile-to-mobile audio quality measurement using Mobile Receiving Unit (MRU). POLQA NB. Channel3: Channel for phone connected to LINE IN 3/ LINE OUT 3. Channel2: Channel for phone connected to LINE IN 2/ LINE OUT 2. Audio Channel (only used for M2M DL + UL. and POLQA SWB. during a CS voice call.16. Hang Up Hangs up a CS voice call. NT12-7002 ver 1. Please note that POLQA can only be measured in the ACU configuration (Measurement Type = “M2M DL + UL”). This activity has no unique properties. AQM Measurement Performs audio quality measurement (AQM).4. 20. otherwise has the value “None”): • • • • Channel1: Choose this channel for the phone connected to LINE IN 1/LINE OUT 1 on the ACU. Measurement Type: • • • M2F DL + UL: Mobile-to-fixed audio quality measurement using Call Generator.0 267 .Chapter 20.16. AMR-WB.5.8.7.16. or AMR-NB.pcm) with an AQM value worse than this threshold value will be stored under My Documents\TEMS Product Files\TEMS Investigation 14.16.7. Codec Rate: Voice codec rate. VoIP Answer Waits for an incoming voice-over-IP call to arrive and answers it when it arrives. Codec: Voice codec. The point of this mechanism is to have poor quality files automatically saved for further study. Note that the measurements are found in the Media Quality information element category: see Information Elements and Events. one of: G.6. • Configuration property: Phone Number: The phone number to call. 20.1\PESQ\Recordings. • Configuration property: Codec: Voice codec. See also section 20. or AMR-NB.7. 20.711 A-law.7. VoIP Hang Up Hangs up a voice-over-IP call. VoIP Voice Quality Performs audio quality measurement (AQM) including PESQ/POLQA. 20. This activity has no unique properties.7.TEMS Investigation 14. See chapter 38.16.9.7. 268 .16. section 3. VoIP Dial Dials a voice-over-IP call.9. one of: G.7. 20.9. AMR-WB.711 A-law. Codec Rate: Voice codec rate.16.16.1 User’s Manual Recording Threshold (only used for M2M DL + UL): All audio files (*. See also section 20. Chapter 20. see the technical paper “VoIP Testing with TEMS Investigation”.16. Store AQM files: Yes or No. • The calling device and called device must be connected to different PCs. For a full tutorial on testing VoIP.7. one for the caller and one for the callee. nor any other internet connections in parallel.9. both fixed and wireless. MOS limit: If the MOS value for an audio file is lower than or equal to this threshold. Predefined Snippets for Voice • Voice Call snippet (CS): Dial Wait Hang Up. You cannot have an Ethernet cable connected either. 20. the audio file will be saved under [My] Documents\TEMS Product Files\TEMS Investigation 14. Furthermore. This setup is necessary to enable audio quality measurement for VoIP. You must not have any other measurement devices plugged into either PC when doing VoIP testing.16. The Duration parameter should be set differently for caller and callee. Caller and callee must use the same speech codec. Both caller and callee must register with the SIP or IMS server to be used for VoIP. see section 20. The callee script must therefore complete its SIP Register activity before the caller script reaches VoIP Dial.1\PESQ. NT12-7002 ver 1. the callee must be registered before the caller places the call.7. found on the installation CD in the subdirectory Documents. Service Control • Configuration property: Duration: The length of time for which to collect voice quality measurements. each running an instance of TEMS Investigation.16.10. Two scripts must be prepared. Predefined VoIP snippets are provided. Below is a summary of the salient points. All network interfaces except the testing device must be disabled. so that it can be controlled which side hangs up the call.7. How to Set Up VoIP Testing A number of things must be observed when setting up and running VoIP scripts. • • • • • 20.10.0 269 . Activity-specific properties are covered in section 20.2.17. you need to create one in the Configuration Sets pane.16 in connection with their respective activities. Enabled: True or False. Failure Handling Section • On Failure: This property determines what will happen if an activity fails (when first attempted). and the whole script is terminated. the activity is disabled and will not be performed when the script is run. the activity is abandoned. Activity Section • • Name: Name given to the activity.1.TEMS Investigation 14.1 User’s Manual • VoIP Dial snippet: Network Connect SIP Register VoIP Dial VoIP Voice Quality VoIP Hang Up SIP Unregister Network Disconnect. if no such configuration set exists. This is indicated by the activity being dimmed by a semi-transparent greenish box in the flowchart. for FTP Download. the activity is abandoned. If set to False. and the execution proceeds to the next activity in the workflow branch in question. (Only appears for certain non-editable activities such as the “root” activity at the top and bottom of the workflow. • 20. Stop Script Execution: If an activity fails. For example.17. Equipment: The EQ to which the activity is assigned. – Continue Script Execution: If an activity fails.) Configuration: Reference to a configuration set of the type associated with this activity.17. The combo box is populated with all existing configuration sets that fit the activity. – 270 . VoIP Answer snippet: Network Connect SIP Register VoIP Answer VoIP Voice Quality SIP Unregister Network Disconnect. General Activity Properties These properties are common to all or many activity types. 20. an FTP server configuration set needs to be selected here. • • 20. unless it has already completed before that time. On Failure – what action to take if all retries fail (continue or stop script). When you choose this option. 20. 20. it will be retried. For that reason each configuration set is described in section 20. which aborts the whole script with immediate effect. Descriptions of Configuration Sets All types of configuration set are associated with a particular service. Configuration Sets 20. On Event: The activity will be aborted if and when one of the specified events occurs. – – Never: The activity will execute as long as it takes to complete. Managing Configuration Sets You can manage configuration sets using the Settings Manager utility. What you indicate here is thus a maximum duration for the activity. see section 20. • To launch the Settings Manager utility.18. a set of further parameters appear: Retries – the number of retries. Compare the Terminate activity.1.16 in conjunction with the activity or activities that use it. On Timeout: The activity will be aborted after a fixed period of time.18. For a tutorial on how to use these functions in conjunction with script saving/loading in order to port scripts between PCs.2. Service Control – Retry: If an activity fails.19. – Note that this property is also possessed by the root activity.18.1.0 271 . NT12-7002 ver 1. choose File Manage Settings. • Abort: This property determines under what conditions the activity will be aborted. otherwise it will run to completion. Delay – the time to wait before each retry. in which case it applies to the entire script.Chapter 20. right-click in the list and choose Select All/Unselect All.1.. • Click the Source button and browse to the directory you want to import from. This window appears: 20. Now select where to export the configuration sets.2. All configuration sets currently known to the application are listed in the window.2. Each configuration set is now exported as a file named according to the format TEMS.1 User’s Manual Alternatively. • Select the configuration sets you want to export by clicking them in the list. in standard Windows fashion. To perform the export.TEMS Investigation 14.Services. • 272 .>.<. Click the Target button and point to the desired directory. choose Start [All] Programs Ascom TEMS Products Utilities TEMS Investigation 14. in standard Windows fashion. Exporting Configuration Sets To export configuration sets you use the Export tab. To select/unselect all sets. • • 20.config. Importing Configuration Sets To import previously exported configuration sets. Select the configuration sets you want to import by clicking them in the list..Settings.1 Service Settings. To select/deselect all sets. right-click in the list and choose Select All/Unselect All. Shift + click and Ctrl + click can also be used.18. Shift + click and Ctrl + click can also be used. you use the Import tab.2. The window is populated with all configuration sets found in that directory. click the Export button. in Windows.18.<service name>Settings. The Save Script dialog contains the following options: • • Description: Free-text field where you can optionally enter a description of the script. From the Tools menu you can delete all configuration sets by choosing Clear Settings.3. select it and click Clear. • To restore configuration sets from a backup. • 20. Note that configuration sets can also be saved separately: see section 20. click the Import button.2. click the Save button on the Service Control Designer toolbar. NT12-7002 ver 1.19.2.18. and click the Restore button.0 273 .Chapter 20. Deleting Configuration Sets You can delete a configuration set from TEMS Investigation by selecting it on the Export tab and clicking the Delete button.tsc (for “TEMS Service Control”). Saving and Loading Scripts To save a script to file. a backup of the configuration sets will be created whenever you use the Clear Settings command. If the Enable Backup option is selected. Service Control • To perform the import. select the backup of interest from the list. To delete a backup. The file will receive the extension . choose Tools Manage Backups. Format: You can save the script either with or without the configuration sets it uses.18. 20. 20. (This is the default setting. Choose this option if you are going to use the script on several computers. 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. making the TSC file a self-contained and independent entity that can be immediately reused on a different PC. Open the sender’s workspace. Open the sender’s script. The script can now be not only run but also freely modified on the receiver PC. 274 .) Redistributable: All configuration sets referenced in a script are saved with the script. To open an existing script stored on file.2.19. choose File Save As Image in the Service Control window and select the desired image file format.TEMS Investigation 14.19. Choose this option if you are going to use the script on one PC only. 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.1 User’s Manual – Standard: No configuration sets are saved with the script. click the Load button on the Service Control Designer toolbar. Start TEMS Investigation. This means that changes to a configuration set will automatically propagate to all scripts that reference it.1. Save your script with Format set to Redistributable. Export your configuration sets. Saving Workflow as Image • You can also save the contents of the workflow pane as an image. To this end. – 20. By default all activities are shown (“All”).1.3. After you click the Zoom In button on the window toolbar. 20. Further Functionality in the Service Control Designer Window 20. Service Control 20.0 275 . The rest is standard Windows functionality. Context Menu in Workflow Pane The context menu that appears when you right-click in the workflow pane has functionality that is mostly mirrored in other places: in the regular window menu and in the Properties pane. except the Move Left and Move Right commands which you can use to change the ordering of activities in a workflow. The context menu is especially useful for changing properties (EQ assignment. You NT12-7002 ver 1.20. 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.20.Chapter 20. 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.20. the mouse pointer by default has the usual point-andclick function.2. on-failure behavior) of several activities at once. You can however switch the mouse to zoom mode. then right-click the selection and choose the desired command from the context menu. 20. where mouse pointing actions have the effect of zooming the workflow pane in or out. Activity Filter The Activity Filter combo box at the top of the Activity pane can be used to filter the list of activities so that it shows only the activity types supported by a particular device.20. mouse clicks in the workflow pane will magnify its contents in predefined steps. To return the mouse to pointing mode. To reverse the mouse-click zoom function. 276 . click the Pointer button.TEMS Investigation 14. click the Zoom Out button on the window toolbar.1 User’s Manual can also click and drag to select a portion of the workflow pane that you want to enlarge. Chapter 21. Some devices have Navigator control functions that correspond to device properties for other devices. To access the property dialog of a device. Device Properties 21. see section 9.1. NT12-7002 ver 1.8) are labeled “CL” in the table. do as follows: • • Right-click on the device on the Navigator’s Equipment tab.1.0 277 . 21. these instances are marked with an “N” (for “Navigator”) in the table below. Overview of Properties by Device This overview covers certain Sony Ericsson. Regarding control functions applied from the Navigator. Device properties that correspond to aspects of the Cell Lock control function in the Navigator (described in section 9. Choose Properties from the context menu. Device Properties From TEMS Investigation you can view and modify certain properties of devices. For clarity. and Samsung phones. Other supported devices share little or none of the control functionality listed here. Nokia.1. ) Control Function Samsung Infuse 4G TM506/Z750i Access class control Barred cells. 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.1 User’s Manual Sony Ericsson C702/C905*/W760i/W995* Sams. Changing order of priority between codecs is supported for C905*/ W995* only. No. 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. access control BLER target control (WCDMA) C/A measurements (GSM) Channel verification (GSM)1 Disable handover CL EDGE capability control L3 messages. access control Speech codec control3 TxPower control (GSM) 1. 278 Nokia NTM3 K790i/a W600i K800i K600i . That is. prevent handover to specified cells. 3. Samsung Galaxy S 4G Xperia arc S* (Qualc.TEMS Investigation 14. See chapter 43. the Properties dialog contains the buttons Restore Defaults and Apply. It is also applicable to the subset of those properties exhibited by the Samsung Galaxy S 4G. Regarding “TPC Info Per Cell”.2.2. like OK. but without exiting the dialog. Device Properties 21. You can turn the reporting on and off for each item listed. Common Controls Each of the nodes in the property grid contains a field Default/Modified. Restore Defaults resets all settings to their defaults. which means no alteration of regular phone behavior.Chapter 21.1. 21. Any changes to the properties will apply as long as the phone remains activated in TEMS Investigation.1. the phone retrieves all settings you have specified for it. To activate a control function.2. Functions of Dialog Buttons Besides OK and Cancel. and the Samsung Galaxy S 4G and Infuse 4G models. without exiting the dialog. These buttons have the following functions: • • Apply saves all changes made to settings. Note the following: • • “Path Searcher Report (A2)” must be checked for the Finger Info information elements (WCDMA) to be valid. At the outset this field has the value Default everywhere. section 6. listing messages and mode reports delivered by the phone. then proceed to set the other parameters as desired according to the subsections below. 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. When you activate the phone in the application. 21.2. NT12-7002 ver 1. see Information Elements and Events. you must switch the corresponding “Default/Modified” field to Modified (can be done by double-clicking the value).0 279 . Extended Reports This item appears for certain Sony Ericsson phones. 2. Classes 10 .2. 15 21. Classes 0 ...011.2. 21. Note that this function can be meaningfully applied only if the SIM supports multiple PLMNs. CAS Speech Codec For certain phone models (indicated in section 21.1) you can both define a subset of codecs that should be enabled and change the default order of priority between the selected codecs.2. the user interface shown below appears.. Membership of these classes entitles a phone to make access attempts in various special situations. chapter 4). Speech codecs When you click the “. specified by an MCC and MNC combination.TEMS Investigation 14. the phone will go into limited service mode.2.1. 9 Every phone is by default allocated randomly to one of these classes. CAS Access Class Here you can manipulate access class settings ( 3GPP 22. CAS Lock on PLMN You can lock the phone on a PLMN.1 User’s Manual 21.3. 280 . If you lock on a PLMN that is not available.2..” button in the right-hand field listing codecs. Check the classes that you want the phone to be a member of... MCC.2. MNC Define the target PLMN here. You can change the default allocation here. Those that you leave in the Selected box will remain enabled. 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. 21. • For other phone models you can only select which codecs should be enabled.Chapter 21. Then use the arrow buttons on the right to adjust the order of priority for the selected codecs.4. NT12-7002 ver 1.2. By default all codecs are enabled. 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. this is done in a regular property grid. Number of adjacent channels Specify one or two channels. see above.0 281 .2. 6. it can be locked to one channel or to a set of channels. Only barred cells allowed: The phone will camp only on barred cells. Normal: No effect on default behavior. If the “barred” flag is set for a cell.2. Prevent: The phone will be prevented from camping on the channels checked under ARFCNs. regardless of the signal strength and quality of neighboring cells. you must first lock the phone to the GSM RAT (see section 9. ARFCNs Control mode Check the channels you want to lock on or exclude. Lock: The phone will be locked to the set of channels checked under ARFCNs. 21. The inverted operation is also possible. GSM Cell Selection When the phone is in idle mode. 282 . namely to prevent reselection to a specified channel set. Note: To apply this kind of lock.2.1 User’s Manual 21.1. All cells allowed: The phone will camp on any cell.TEMS Investigation 14. Mode Normal: The phone will not camp on barred cells.2. GSM Barred Cells Here you can alter the phone’s behavior in GSM idle mode with respect to barred cells.1. this normally prevents the phone from accessing it. ignoring cell barring.2.12) and to a GSM band (see section 9.5.5). This inhibits all reselections to other channels. Selecting a single channel forces handover to that channel. Disable handover: The phone will be prevented from performing any handovers at all. The phone will then report no RxLev for these channels.2. EDGE allowed Yes: EDGE enabled. Normal: No effect on default behavior. No: EDGE disabled.8. Force handover to a specified channel.2. The phone will then report a very high RxLev for any such cell. Specifically. 21. Device Properties 21.2.0 283 . or restrict handovers to a chosen channel set. Disable handover altogether. a very low RxLev for the serving cell.7.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. GSM Handover When the phone is in dedicated mode. • NT12-7002 ver 1. ARFCNs Control mode Check the channels you want to prevent handover to or restrict handover to. and no RxLev for other neighboring cells.2. you can manipulate its handover behavior. Lock: The phone will be able perform handover only to the set of channels checked under ARFCNs. you can do one of the following: • • Prevent handover to specified channels. GSM EDGE Capability For EDGE-capable phones you can choose to disable the EDGE capability. and other cells: Normal No change from normal cell barring behavior.11.2. Number of Layer 3 message types selected under Message types. Tx Power GSM 850 (dBm) (etc.) Enter the desired new Tx Power in dBm for the GSM 850 MHz band. 21... Discarded messages are colored red in the Layer 3 Messages window and tagged with a special note in the plain-text decoding.1 User’s Manual 21.2.9. The phone can store up to 10 message types in its memory. check the types of Layer 3 message that you want to discard.TEMS Investigation 14. Note: The UE must have been activated at least once for the full tree of Layer 3 message types to appear here. 21. see section 26. WCDMA Barred Cells Here you can modify the phone’s behavior with respect to accessing of barred.2.2. GSM Tx Power For each GSM frequency band you can specify a Tx Power value which will override the network allocated Tx Power. section 4.”). select Discard here. Layer 3 Messages For certain Sony Ericsson UEs you can discard Layer 3 messages of specified types.2.2. Click the browse button (marked “. Regarding the latter. In the dialog that appears.1.10.005. reserved. 284 . Default/Discard Loaded Message types To enable the function.3. see 3GPP 45. Regarding the format of this value. see 3GPP 25.0 285 . BLER Target value The BLER target for the UE will change to the value you set here. 21. in idle mode as well as connected mode. Only reserved for operator use: The phone will only access cells that are reserved for operator use. 21.2. Only reserved: The phone will only access reserved cells. Only barred or reserved: The phone will only access cells that are barred or reserved. Lock: The phone will be locked to the set of UARFCNs/scrambling codes that you select in the UARFCNs and Scrambling codes fields. Only reserved for future use: The phone will only access cells that are reserved for future use.Chapter 21. WCDMA Cell Selection Here you can lock the UE to selected UARFCNs or scrambling codes in WCDMA. Device Properties Mode All cells allowed: The phone will access any cell.2.331.2. Only barred: The phone will only access barred cells.13.2. WCDMA BLER Target For certain Sony Ericsson UEs you can override the BLER target set for the UE by the network. NT12-7002 ver 1.12. Control mode Normal: No effect on default behavior. also barred and reserved ones. you must first have selected a single target UARFCN.12) and to a WCDMA band (see section 9. If HSUPA is enabled. These categories are defined in 3GPP 25.14. table 5.2.5).1. you can set here what HSDPA (HS-DSCH) category the phone should report. WCDMA RRC Radio Capability For phones supporting HSDPA. Up to 32 target UARFCNs can be specified. HSUPA category 286 . To be able to specify target SCs.1a. HSDPA + HSUPA: Both HSDPA and HSUPA are enabled.2. These categories are defined in 3GPP 25. However. 21. you can enable or disable these capabilities.1 User’s Manual Scrambling codes Lists the scrambling codes to lock on.1. or all of HSPA. note that if you list more than one UARFCN. UARFCNs Check the UARFCN you want to lock to. If you have specified multiple target UARFCNs. Allowed technologies R99 only: Only WCDMA R99 is enabled.306.TEMS Investigation 14. you cannot also select scrambling codes as targets.306. HSDPA: HSDPA is enabled (but not HSUPA. you must first lock the phone to the WCDMA RAT (see section 9.1g. Note: To apply this kind of lock. even if the phone supports it). you can set here what HSUPA (E-DCH) category the phone should report. HSDPA category If HSDPA is enabled. Up to 32 SCs can then be listed as targets. table 5. you cannot add any target SCs (the Scrambling codes field is grayed). Chapter 21.0 287 . Specify the UARFCN to lock on. Cell barring Normal: The phone will not camp on barred cells. Specify the scrambling code to lock on.3. Properties of Nokia Phones (NTM3) Channel Lock Control (GSM) In GSM mode. you can lock the phone to a single ARFCN.1.3. The channel lock function works in idle mode only.2. Specify the band containing the channel you want to lock on. Enable channel lock Band ARFCN Set this to Yes to enable the channel lock function. Reversed: The phone will camp only on barred cells. GSM Cell Barring Control This setting governs how the phone behaves with respect to barred cells in GSM. Device Properties 21. NT12-7002 ver 1.3. The phone will be locked to the chosen UARFCN and scrambling code.3. 21. Sector Lock Control (WCDMA) These settings apply in WCDMA mode. 21. Specify the ARFCN of the channel to lock on. 21. Ignored: The phone will camp on any cell. ignoring cell barring.3. Enable sector lock UARFCN Scrambling code Set this to Yes to enable the sector lock function. 21.1.4.1. you must enable all logs with “Vocoder Packet” in their names. However.TEMS Investigation 14. see section 9. For speech codec information elements to be populated.4. • • 288 . for this device all control functions are applied from the Navigator. no RRC State is presented until the state changes. Regarding the NV (Nonvolatile) interface. C/I is obtained only for circuit-switched. 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. Please note that with this device. as explained in section 9.1.1 User’s Manual 21. RAT lock and band lock functions are available.9. not for packet-switched data. Properties of Qualcomm Chipset Based Devices Properties of Qualcomm chipset based devices are mostly limited to enabling and disabling of various logs. The “WCDMA SIR Target” log must be turned on for the WCDMA SIR Target element to be populated. for certain devices such as Option data cards and Sierra Wireless UMTS data cards. 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. If the log is turned off. This is true for the Sony Ericsson Xperia arc S as well. (The settings you make here do not affect the scope of All enabled. further fields appear which allow you to enable or disable various subcategories of messages. 21. Properties of GPS Units You can inspect and change some properties of a GPS unit. NT12-7002 ver 1. LTE For each of these top-level message categories.0 289 . no reports from the MS device channel will be displayed in TEMS Investigation. various message categories can be enabled and disabled. All disabled: All messages are disabled. Select messages: When this option is chosen. which always means all messages without restriction. the following options exist: All enabled: All messages are enabled.6.Chapter 21. What properties are editable depends on what product you are using.5. Device Properties 21.) Please note that if you disable everything here. Properties of Samsung LTE Modems For Samsung LTE modems. Common. 1 User’s Manual 22. User-defined events are specified by logical expressions.5).5. Click Add. you can define events of your own. Regarding this window. Predefined and User-defined Events Definitions of all predefined events are found in Information Elements and Events. see Information Elements and Events.4) as symbols and vertical lines in line charts (see section 29.3. 22. • Setting Up a User-defined Event Open the Event Definition window. Events TEMS Investigation generates events to indicate noteworthy occurrences in the cellular network. in addition to these.TEMS Investigation 14. 290 . Presentation of Events Events that occur are listed in the Events window.8. chapter 7. 22. section 8. 22. which trigger the event when they evaluate to true.4) as audio signals (see section 22.2. A number of events are predefined. Events can also be presented: • • • as symbols on the map (see section 31. These expressions can contain: • • • Layer 3 messages other events conditions involving information elements.1. Periodic. the event can be triggered by any device.4. This is especially useful for cell whitelist events: see section 22. Interval You build up the event expression by using the add buttons on the right. the event is triggered only when the event expression is true for this particular device. If Periodic is checked. the event is generated only once when its condition becomes true. NT12-7002 ver 1.0 291 . The choice in this combo box governs what will be selectable when you click the Add Element button. Events Name System Mobile Enter a name for your user-defined event. If Periodic is not checked. The structure of the expression is displayed in the box beneath the Name field. If you choose a specific external device in this combo box. at intervals governed by the Interval parameter. If you choose “Any”.Chapter 22. the event is generated repeatedly as long as its condition is true. 3. • Adding a Layer 3 Message to the Event Expression Click Add Element and choose Layer 3 from the context menu. or “<”). Choose a threshold operator (“=”. 292 . Information element Argument Value: Changed Value: Threshold Choose an information element. 22. or drops below a certain value. “>”.1. Choose this to trigger the event when the selected information element assumes.TEMS Investigation 14.3. exceeds. specify it here. 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.2. Choose this to trigger the event whenever the value of the selected information element changes. If the information element has an argument.1 User’s Manual 22. and set the threshold value. Click Edit and make the desired changes. Available operators are AND. 22.3.3. click Add Operator and select an operator or delimiter from the context menu. and NOT. Note: If a user-defined event is added or modified after a logfile is loaded. NOT. Events 22. NT12-7002 ver 1.6.4. • Deleting User-defined Events Select the event you want to delete in the Event Definition window. Adding an Operator/Delimiter to the Event Expression To build a composite logical expression.3.7 below for an example of a logical expression.3. • In the Add User Defined Events dialog.Chapter 22.0 293 . In the new dialog that appears. XOR. OR. 22.5. • • Adding an Event to the Event Expression In the Add User Defined Events dialog. See section 22. 22. • • Editing User-defined Events Select the event you want to edit in the Event Definition window. or XOR). you will need logical operators and possibly delimiters (brackets). choose an event from the combo box. Then click OK to exit the Add User Defined Events dialog.3.3. The new event is now added to the list in the Event Definition window. Keep adding items to the event expression until it is complete. click Add Element and choose Event from the context menu. the logfile must be reloaded for the events to become visible. Note: Events used in the expression for a user-defined event can be combined with the OR operator only (not with AND. In certain circumstances. 7. Two common ones are co-channel and adjacent channel interference. 3. 13. 9. 10. 1. Choose “Threshold” and choose “<” from the combo box. Click Add Operator and choose “AND”. Click Add. Example of User-defined Event This example is taken from GSM. 8. 4. Under “Information Element” choose “RxLev Sub (dBm)”. 2. 6.1 User’s Manual • Click Delete. This means thermal noise generated within the circuits of the phone as well as external background noise from a plethora of sources.TEMS Investigation 14. There are many possible causes of poor C/I values. From the Configuration folder in the Navigator. 12. Choose “Threshold”.e. Click Add Element and choose “Information Element”. 5. Click OK.3. choose “C/I Worst”. The event expression should now look as follows: 294 . however.7. From the Add Information Element combo box. Set Value to –99. 14. Click Add Element and choose “Information Element” from the context menu. 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. the main problem is not interference from other callers. but the fact that the signal is overwhelmed by assorted random disturbances – i. 22. what is usually called “noise”. Name the event “Noise Indication” (or whatever you like). open the Event Definition window. and choose “<” from the combo box. including other man-made signals so faint that they merely add up to a quasirandom disturbance. 11. Set Value to 10. Click OK. 0 295 . proceed as follows: Click the Cell Whitelist button. For example. Events C/I Worst < 10 AND RxLev Sub (dBm) < –99 15. 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”. 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. emergency calls would be put through normally and are therefore forbidden. Outside of these cells. In the dialog that appears. The input might look something like this: NT12-7002 ver 1. This is useful in any scenario where testing is restricted to certain cells. 22.4. chapter 6. Click OK to finish. testing of an emergency service might be performed in cells which have been temporarily reconfigured to divert emergency calls to a different number (so that they do not interfere with genuine emergency calls). Generating Cell Whitelist Events The Event Definition window has a special function for generating userdefined events based on cell lists. To construct your whitelist. The event is now added to the event list and can be used in the Map window and in other presentation windows.Chapter 22. 1 User’s Manual • • You can change the event name if you wish. When you are done. The name and the periodicity (Interval setting) of a previously defined whitelist event can be changed when the event is inspected. Whenever a connected device enters one of the cells on the list. the appropriate event will be triggered.TEMS Investigation 14. you can view the event expression in the same format as in the Cell Whitelist Generator dialog. a RAT designation will be appended (see below). it is represented there by the string “<Compiled Whitelist Expression>”.1 1. click OK. To the Event Name string. 296 . Please note that the whitelist event expression cannot be modified from here. The resulting event expression is not reproduced explicitly in the Event Definition window. From the cell whitelist TEMS Investigation now constructs a set of userdefined events: one for each RAT occurring in the whitelist. However. if you select the event and click the Edit button. NT12-7002 ver 1. To associate events with audio signals.Chapter 22.0 297 . but skip the task otherwise.5.10. the Cell Whitelist Generator dialog does retain the contents it held when last closed.6. when opened. its contents are converted to an event and cannot subsequently be reverted to the whitelist format. you use the Audio Indications window found in the Configuration folder in the Navigator.) 22.1. After you click OK in the Cell Whitelist Generator dialog. See section 20. Events Whitelist events are automatically made periodic (Periodic option checked). Please keep in mind that the Cell Whitelist Generator functions as a “oneway” editing aid.5. Audio Indications for Events For each event you can specify an audio signal to be played when the event occurs. 22. (However. This is useful if you are performing a drive test on your own and need to keep your eyes on the road. Adding Audio Indications Click Add in the Audio Indications window.3 for further guidance on how to compose such scripts. This information can be utilized by a script to perform a certain task if the device is in a white cell. so that they can provide continuous updates on whether or not the user is camping on a white cell. Enter the path to the WAV file you want to use. Choose an event. Listen to the selected sound file. Check to use the internal speaker of your PC. or click Browse and select the file. The events that are now associated with sounds are listed in the Audio Indications window. Click OK when you are done adding audio indications. 298 . Click Apply to add the current audio indication and keep the dialog open.TEMS Investigation 14.1 User’s Manual Mobile Event Sound Use PC speaker Test • • Choose an external device. • Saving and Loading Audio Indications Select the audio indication you want to save. Activating Audio Indications Audio indications are by default active. 22. 22. • Editing Audio Indications Select the audio indication to be edited. Click Activate Sound.5. NT12-7002 ver 1. Muting All Audio Indications To disable all audio indications. To activate a deactivated audio indication: • Select the audio indication. no audio indications will be played until you decide to enable them again.6. To re-enable all audio indications: Click Undo Mute All.5. Click Edit and make the desired changes.5. 22. Events 22.0 299 . You might find this attractive when doing post-processing. independently of their status (active or deactivated): Click Mute All. From now on.5.4 below).4. and deactivated ones will remain deactivated. The status of the audio indications will remain the same as before you clicked Mute All: active audio indications will start playing again.3.Chapter 22.5. Click Deactivate Sound.5.2. They may however be deactivated (see section 22. 22. • Deactivating Audio Indications To deactivate an audio indication: Select the audio indication.5. 22.TEMS Investigation 14. • Deleting Audio Indications Select the audio indication to be deleted.1 User’s Manual Click Save and enter a file name (extension . Click Open to load an *. Click Delete.svt).5.svt file in the Audio Indications window.7. 300 . Data is presented in fundamentally the same way in both cases. For an overview of information element categories. events. chapter 2. Types of Presentation Window The following presentation windows are available in TEMS Investigation: Window Type Status window Event Counter window Message window Video Monitor GPS window Line chart Bar chart Chapter Ref.0 301 . see Information Elements and Events. chapter 7.1. Regarding predefined events. see Information Elements and Events. 24 25 26 27 28 29 30 NT12-7002 ver 1. 23. Presented Data The presentation windows are used to present information elements. Presentation: Basics 23. and messages. differences are noted whenever relevant in the chapters that follow.Chapter 23. 23. Presentation: Basics This chapter covers the fundamentals of data presentation. either in real time or during logfile analysis.2. Full details on information elements follow in chapters 3 and 4 of that volume. right-click any empty part of the worksheet. 302 . Select the equipment (EQ/MS/DC) number in the dialog. choose Set Equipment Number. From the Worksheet menu.TEMS Investigation 14. and choose the same item from the context menu. “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. Alternatively. • • The change will affect all presentation windows that display data from a specified device (as opposed to. 31 23. The EQ designations currently do not appear in presentation windows.1. Device Channels: MS/DC/PS In presentation windows.3. 23. as opposed to the Navigator and Service Control components. for example. devices are represented by their channels: • • • MS for radio measurements DC for data service measurements PS for positioning equipment.1 User’s Manual Window Type Map window Chapter Ref. Event Counter windows).3. Event Counter windows).Chapter 23. which show the situation at one instant in time and are constantly refreshed in drive testing mode (status windows. • 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. and • All windows are synchronized. whereas the snapshot windows are updated to show the data that was current at this time. as soon as a new message arrives from the phone. Video Monitor) “history” windows. custom color ranges for information elements can be defined.3 for details. but in many window types. bar charts. Color Ranges In many types of presentation windows. GPS window. The exactness of the synchronization is limited by the time resolutions of the various presentations. see section 26. Whenever an information element is invalid. When you select a point in time in a history window. line charts. the presentation automatically reverts to the present time. NT12-7002 ver 1. message windows. other history windows highlight the same time instant. or has no color defined for its current value. for use in that window only. Note: The above applies without qualifications in analysis mode. In status windows. which accumulate information and display the whole history of the testing session. You can always turn off the color coding and use a fixed color for drawing. however. For example.0 303 .4. things are somewhat different: it is still possible to inspect previously recorded data. In drive-testing mode.5. it is drawn in black in graphical presentations and left out in textual presentations. Presentation: Basics 23. These colors are defined in the Navigator. see section 5. 23. the line chart plots two points every second. or statistics on it (maps. it is possible to visualize numeric information element values by means of a range of colors. Regarding synchronization between message windows and other windows.5. that is. 304 . see appendix B. choose Import. • • • Import To import a saved presentation window. You can later import the window into the application again by opening the file. Export/Import of Presentation Windows Status windows. and message windows can be exported. • • • Export To export a presentation window.) From the File menu. maps.7. 23. From the File menu. Type a file name and click Save. Other Window Properties The appearance of any presentation window can be changed by altering the window properties. 23. and click it. proceed as follows: Focus a presentation window of the same type as the one you want to import. choose Export.1. line charts.1 User’s Manual 23.TEMS Investigation 14.7. Select the desired file and click Open.2.7.6. which are accessed by right-clicking in the window and choosing Properties from the context menu. The extension depends on the window type. saved along with all their current settings in a file separate from the workspace. (Open a new window if necessary. proceed as follows: Select the window. 23. 1. you can modify the window using the Properties dialog. In addition.0 305 . a blank template is available which you can use to compose your own status windows.2). A number of ready-made windows are provided for presenting particular categories of information. Later on. Also. use the setup wizard (section 24. For these purposes you must use the Properties dialog. which is described in section 24.3. Status Windows 24. Note: Setting the number of columns and rows in the status window cannot be done with the setup wizard. these are listed in Information Elements and Events. See section 24. 24. The setup wizard is intended to be run only once.3. 24.2. General The status windows present information elements in tabular form.Chapter 24. Status Windows This chapter explains the workings of status windows. Setting Up Status Window Contents The contents of a status window are conveniently set up using the setup wizard. NT12-7002 ver 1. To set up a status window. you cannot enter text in the status window using this tool. chapter 8. This dialog opens: 306 . To add an information element. Note that changing the name later will create a new status window. Name Name the new status window.1 User’s Manual • Right-click in the status window and choose Setup Wizard. click Add.TEMS Investigation 14. and the contents of the current window will be lost. Click Browse and select a font. Font • • Click Next to proceed to step 2 of the setup wizard. Choose an information element category. NT12-7002 ver 1.Chapter 24. Status Windows Mobile System Information element Argument Choose which device to pick the information element from. Choose an information element. Enter an argument for the information element (if it needs one). See Information Elements and Events. • Select the View tab. chapter 2.0 307 . 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.TEMS Investigation 14. In that window. Draw the bar with constant length. This is useful for information elements that represent states. See screenshot in section 24. Keep track of the all-time-low and all-time-high values by means of vertical lines. Min/Max indicator Associated information elements Information Element 1 Information Element 2 • Select the Color tab to customize colors and color ranges. etc.6.1 User’s Manual Value Left. and can only assume a limited number of values. This checkbox with accompanying combo boxes is enabled only for the CDMA window Finger Info. Center. 308 . Right Bar Constant length Check to display values alphanumerically.2. Check to display numeric values as colored bars. Choose alignment for the displayed values. The Mode tab governs the layout and appearance of the window: NT12-7002 ver 1. Click OK when you are done adding information elements. If you want to define a special color range here. Then exit the setup wizard by clicking Finish.0 309 . 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). uncheck the box and specify the range (see section 5.3. 24.Chapter 24. • Changing Status Window Properties Right-click in the status window and choose Properties from the context menu. • • Click Apply to add more information elements. If you choose a device in this box. Click Browse and select a font.) Columns Rows Font Mobile • To edit the contents of the status window.TEMS Investigation 14.) Set the number of columns. (The contents of the header are defined on the Cell Content tab. (To pick individual information elements from a different device. regardless of earlier settings. use the Cell Content tab. Set the number of rows. See below. select the Cell Content tab. Check if you want a header in the window. all the information elements currently shown in the window will be taken from that device.1 User’s Manual Name Header Enter a new name if desired. 310 . 2 above). Then click Edit. Status Windows • Double-click on a row and select an information element from the list. The dialog that appears is identical with the Add dialog in the setup wizard (see section 24.0 311 . except that it has an extra field for entering text: NT12-7002 ver 1.Chapter 24. All columns are then repeated once or twice in the window. 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. • Right-click in the status window and select Column Group from the context menu. create new columns as needed on the Mode tab. then select the desired number of column groups. This feature is handy when the default window layout has a large number of rows. Repeating Columns in Multiple Groups In status windows with a small number of columns (up to four). 24.1 User’s Manual In a status window.TEMS Investigation 14. To do this. 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. and modify headers and insert information elements on the Cell Content tab. Use the In and Out options to step the font size up and 312 . then selecting the desired percentage of the current font size. 24.5. multiple column groups reduce or eliminate the need for vertical scrolling.4. A repetition period p means that the DPCH is transmitted in every pth subframe. • – – NT12-7002 ver 1.0 313 . If a code straddles multiple columns. and columns represent the leaves of the channelization code tree for the DPCH (i. rows represent timeslots. 24. Non-standard Status Windows TD-SCDMA Physical Channel Monitor This window has a unique design and presents data on TD-SCDMA Dedicated Physical Channels (DPCHs). this means that the spreading factor for that timeslot is reduced. if the code takes up m 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). • • In the top left corner is displayed the current Work UARFCN. respectively. the number of codes available when the maximum spreading factor is used).Chapter 24. the spreading factor is 16/m.e.6. Repetition period: This is the DPCH repetition period on the downlink and uplink respectively. The size of the window itself is not affected by these operations. expressed as a number of radio subframes (5 ms). In the grid.1. 24. – A code in use in a timeslot is indicated by an entry in the corresponding row and column(s) in the grid.6. down arrow (yellow) = downlink. The arrow shows the direction of transmission: up arrow (blue) = uplink. The numbers are to be read as follows: x y = channelization code no. Specifically. Status Windows down. 24. the interference signal code power for the timeslot.6.1. In this case. 314 .6. as shown in the screenshot below. For the setup. The color gray means that no valid ISCP measurement is available (which is always the case on the uplink).TEMS Investigation 14. 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. 24.2 (View tab). see section 24. i.e.1. Window Properties You can right-click in this window to select which devices to display data from.1 User’s Manual – Codes are colored according to the same rules as the information element “Timeslot ISCP (dBm)”. CDMA Finger Info This window indicates the T-Add and T-Drop thresholds by means of a window-specific feature.2. 0 315 . Window Tabs Tabs are provided in this window to allow grouping of events into categories. Event Counter Windows 25.Chapter 25.4. In the Event Counter window provided under Presentation Analysis. 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.2. To rename a tab. a number of tabs are preconfigured. See section 25. What events to show is user-configurable. right-click in the window and choose Remove Tab from the context menu. • • • To add a new tab. 25. Copying Window Contents You can copy the entire contents of a tab in an Event Counter window to the Windows clipboard. 25. NT12-7002 ver 1.1. right-click in the window and choose New Tab from the context menu.1. This way it can be transferred to a spreadsheet application or other suitable program. To remove an existing tab. TEMS Investigation 14. 25. Events Tab Here you choose which event types to display on the currently active tab (the tab from which you access the Properties dialog). The General tab also holds the window title. 25.4. Counters are reset automatically. in both drive testing mode and analysis mode: • • when a new logfile is opened when a logfile is closed. move the events you want to display to the Selected Events list box.4. A Total column is also provided which adds up the number of events from all selected devices.1. This resets all counters in all open Event Counter windows.2. The event counting in the window is done in a separate column for each selected device. which is user-editable. 25. 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. 316 . • Changing Event Counter Window Contents and Properties Right-click in the Event Counter window and choose Properties from the context menu. Paste the copied selection into the desired application.4. 25. • Using the arrow buttons. General Tab On this tab you choose which devices to show events from.3.1 User’s Manual • • Right-click the tab and choose Copy to Clipboard from the context menu. right-click in the window and choose Properties. NT12-7002 ver 1. Message Windows 26.0 317 . mode reports. Preconfigured message windows are listed in Information Elements and Events.1. chapter 8.Chapter 26. They are also used to present events generated by TEMS Investigation.1. and error reports). 26. • Changing Message Window Contents and Properties To access the message window Properties dialog. 26. 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. which is user-editable. MS and DC channels are distinguished. The tab also holds the window title. General Tab On this tab you choose which devices to show messages from. 26. Message Name: Name of message or event. the checkbox next to the category is shaded gray. Event Symbols: Event icon. The ready-made windows are preconfigured in this regard. Using the arrow buttons.1. Information Element: Value of a user-selected information element. 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. Event & Message Symbols: Event icon or arrow showing message direction (both types of symbol being placed in the same column). • • • • • • • • Columns Tab Here you decide which columns to include in the message window: Equipment: The device that delivered the message. 318 .1. Message Symbols: Arrow showing message direction.1 User’s Manual 26. Mobile System: The wireless technology from which the message originates. Note that if you add a user-defined event (section 22. regardless of the nature of the messages.2.1. Messages Tab Here you choose which message categories to display in the window. A new dialog now appears where you select what information element to display. • Events Tab Here you choose which events to display in the message window. you must select it on this tab in order for it to display in the message window.3). Message Info: Message or event information.3. To select the element.4. 26. first move “Information Element” to the Selected Columns box. If at least one item in a category has been deselected. move the events you want to display to the Selected Events list box.TEMS Investigation 14. then select this item and click Edit. Any type of event can always be shown. Each message window normally reuses a single detail window. Further. The new window now becomes the active one. that you just clicked somewhere in a line chart. the new window will not load any messages (for performance reasons). Message Window Synchronization When message windows synchronize with each other and with other presentation windows. To open a message in a new window. you can make the window catch up by right-clicking it and choosing Reload. one or more rows are selected (colored) in each message window. 26. right-click again and choose Cancel Reload. Protocol: The protocol to which the message belongs. Message Window Catch-up If you open a new message window when in drive testing mode.2.2.10) are highlighted in red in the Layer 3 Messages window. for example. right-click the message and choose New Detail Window.4. you can double-click a message to open a new window detailing the contents of the message. However. Message Windows • • Time: Timestamp of message. 26. You can copy text from this window to the Windows clipboard by selecting the text. To abort the reload procedure. 26. when you have deactivated all external devices. The message windows are then updated according to the following rules: NT12-7002 ver 1.2. Plain-text Message Decoding In all message windows. 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. 26.3. The old window will remain open. an explanatory string is added to the plain-text decoding of such messages. but its contents will not change any further.5.Chapter 26. For example.0 319 . then right-clicking in the window and choosing Copy from the context menu. the second message will replace the first in the Layer 3 detail window. Suppose. Freezing a Message Window This section applies to drive testing mode only. nothing is selected in the window. (If no such rows exist. and its message flow is halted. and Highlighting in Message Windows A number of functions for filtering. 320 . Filtering Functions These are found under Show/Hide in the context menu. that row alone will be selected. the row or rows immediately preceding the user-selected item are selected and colored gray. The freeze affects only the message window you clicked in. You can freeze a message window by clicking an arbitrary message. not any other windows.7. the message window selection is colored blue. 26.TEMS Investigation 14.1. 26. Filtering. If the user-selected item and the message window selection belong to the same air interface message. The window will then stop updating. Searching. a message and one or several events triggered by that message).6. searching. If several rows match equally well (for example. 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 there is no such exact correspondence. and highlighting message window contents are available from the message window context menu.) • 26.7.1 User’s Manual • If one message window row matches the user-selected item better than any other. all these rows are selected. • • • • Search Functions These are found under Search in the context menu. Search for message: Opens a dialog Message Search which is explained below.Chapter 26.2. Hide messages of this type: Reloads window contents. Undo: Undoes a “show only” or “hide” command that is currently in force and reverts to unfiltered presentation. Find previous message of this type: Finds the previous message of the same type as the one selected (going backward in time). 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. NT12-7002 ver 1.7.0 321 . hiding all messages with the same log code/name as the selected message. Search again: Repeats the search last performed in the Message Search dialog. 26. Find next message of this type: Finds the next message of the same type as the one selected (going forward in time). Search backward (up) instead of forward (down) in the message flow. The latter is the default. if the Also search message contents option is checked). For example. As you type text in this field. 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. Only match items with casing that exactly matches the search string.7. Also look for matches in (plain-text decoded) the message contents.1 User’s Manual Message Search Dialog Find what String to match in message header (and also in its contents. 322 .TEMS Investigation 14. “UL” matches “ULDCCH” but not “Scheduling”. a dropdown is continuously updated with matching message names. This action is equivalent to the Search again command on the context menu.3. 26. from which you can optionally make a selection. Highlighting Functions These are found under Highlight in the context menu. By default only the message header is searched. Only match items where the search string occurs as a whole word. 1.Chapter 26. with different colors representing different message types. • 26.8. 26. Window-specific Features Mode Reports Window In the General window. Message Windows • Color bars: Select a color in which to highlight all messages of the same type as the selected message. NT12-7002 ver 1.8. None: Removes the highlighting (if any) for all messages of the selected type. you can adjust the updating frequency (in the TEMS Investigation application) for List Search reports from Qualcomm-based terminals.0 323 . See the example below. under WCDMA. Multiple highlights can be applied. The application supports both on-demand streaming. 27. If the file name does not contain a numeric value.1 User’s Manual 27.4.TEMS Investigation 14. The mechanics of setting up and conducting a streaming session are handled by the Streaming activity in scripts: see section 20. Video clips suitable for testing are supplied on the installation CD in the subdirectory Video Clips. you need a phone capable of handling this service. If multiple numeric values are given in the file name. Video Streaming and the Video Monitor TEMS Investigation supports streaming of video recordings via suitable connected devices.1. the VSQI algorithm (see chapter 40) will use a bit rate value received from the server. but the VSQI score will then be less accurate. All phones sold with TEMS Investigation 14. If you are using files of your own for testing streaming. where a video clip of known length is downloaded. the file names should contain a numeric value followed by “kbps”. the first is used.16.1 possess this capability. How to Test Video Streaming To test the video streaming service. 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.6. and various forms of live streaming (such as tapping into a live stream or repeating playlist delivered by a streaming server). 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. where the duration of the streaming session is specified by the user. This value should indicate the bit rate of the stream (video + audio). not counting overhead. 324 . Video Streaming and the Video Monitor 27.2.1. Check this box to play the streamed audio through the PC speakers. (On the other hand. so only one video stream can be replayed at a time. you use the Video Monitor window: Only one instance of the Video Monitor can be open. 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.Chapter 27. The Video Monitor To display the streamed video clip.0 325 . NT12-7002 ver 1. • 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.2.) 27. See the Getting Started Manual.4. is found on the installation CD in the subdirectory Documents.4. and RTCP protocols in the IP Protocol Reports window. Evaluating Video Streaming Performance Throughput and other performance measures for video streaming are presented in the “Streaming” information elements belonging to the Data category. • • • 27. This paper.1 User’s Manual 27.8. The function cannot be used if RTP or UDP traffic to and from the Internet is blocked (intentionally by the operator. “Video Streaming Quality Measurement with VSQI”. • 326 . Event Streaming State: This event is provided for monitoring the activities of the streaming video client.3.TEMS Investigation 14. 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. since the received signal is presented in real time in TEMS Investigation. See Information Elements and Events.8.8. 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. It is described in more detail in chapter 40. VSQI is also the subject of a technical paper which includes general discussions of video streaming as well as video quality measurement. section 7. section 3. For close-up scrutiny and troubleshooting of the video streaming service. Some of these data items deserve special comment: • Information element Streaming Packet Loss: Packet loss is of particular interest for streaming. It appraises video quality only. section 8. or for whatever reason). • • Troubleshooting Video Streaming UDP ports for video streaming must be free. Testing of video streaming with TEMS Investigation requires that RTP/ UDP traffic can be run with the phone used as modem. section 8. RTSP. see Information Elements and Events. Data on which video streaming KPIs are based is delivered in the form of KPI events. See Information Elements and Events.2. you can monitor the message traffic over the RTP. Information element Streaming VSQI and events Streaming Quality VSQI. the window shows data from the one currently selected as “Preferred” (see section 8. If several GPS units have been detected by TEMS Investigation.1. The GPS Window 28. Exactly what data is displayed depends on the type of GPS.Chapter 28. The GPS Window This window shows data from the GPS unit.5). 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.0 327 . Changing GPS Window Properties The GPS window can be configured to show only the parameters that interest you: NT12-7002 ver 1. TEMS Investigation 14. Heading Show invalid positions 1. and the number of satellites seen. Check to also plot samples whose position is labeled as invalid by the GPS unit. Check to show the direction of travel. 328 . altitude and speed of the GPS unit. the fix source.1 User’s Manual Units Tab Speed Altitude View Tab Basic Check to show the latitude. graphically and numerically. longitude. in degrees clockwise from north. Choose meters or feet.1 Choose km/h or mph. This option exists to allow presentation of positions incorrectly regarded by the GPS as invalid. 1. showing the scales for the plotted information elements NT12-7002 ver 1. Line Charts In line charts you can plot numeric information elements in order to visualize how their values evolve over time. Line charts can also present events. Preconfigured line charts are listed in Information Elements and Events.Chapter 29.0 329 . Line Charts 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 8. containing the charts themselves a Y-axis pane for each chart. 29. so neither the text panes nor other presentation windows will be updated. You can also move backwards and forwards in a logfiles segment with the left and right arrow keys on your keyboard.2. open an Events window. The plotting can be done either as a curve or in the form of successive vertical bars.4). chapter 7. 330 . A maximum of four charts can be accommodated. 29. along with their associated Y-axis panes. The symbols used for predefined events are given in Information Elements and Events. While recording. In the chart. 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. just click in the chart. Events are indicated by thin vertical lines accompanied by a symbol identifying the event type.1 User’s Manual • • a Legend pane.TEMS Investigation 14. a thick vertical line indicates the point in time currently selected in the presentation. displaying arbitrary information elements in textual format. as explained in section 23. To see the names of the events. The relative sizes of the panes can be freely adjusted by dragging the interior frame handles. Clicking the button once more (now labeled Release) makes the chart catch up with the presentation in the other windows. During logfile analysis. The legend can only gloss one chart at a time. clicking in the Chart pane displays details on the selected time instant in the two text panes. describing the nature and origin of the information elements shown. Scrolling the chart by means of the scroll bar does not change the time instant selected. you can freeze the line chart by clicking the Hold button. To select a new point in time. The Chart pane is synchronized with the Legend and Additional Information panes (as well as with all other open presentation windows. and indicating their values at a single point in time an Additional Information pane. 4. At the extreme left in the legend. Line Charts The Y-axis Pane The Y-axis pane associated with a chart shows the scales of the information elements plotted there. except when several elements share the same scale. as a rule of thumb. elements which cannot be plotted). You can choose different contents in this pane for different charts. Time Scale The horizontal axis of the line chart does not have an exact time scale. If the phone spends some time in GSM no service mode.3 (“Upper visible limit”. However. The Additional Information Pane This is a sort of status window where an arbitrary set of information elements can be displayed (for example. etc. and so is not labeled with a unit of time. 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. The scales can be changed. Each scale is drawn in the same color as the information element. you can scroll between scales using the arrow buttons. but the length of this gap might not be equivalent to the period of time with no service. If the pane is too narrow to show all scales at once. two points are plotted each second both in idle and dedicated mode. the color coding of the chart is explained. as long as contents have only been defined for one single chart. as described in section 29. NT12-7002 ver 1. 29.0 331 . see section 29. Parameters (SC/BSIC. in which case the scale is black. PN) associated with elements are given in columns of their own wherever possible. there will be a gap in the chart to show this.). right-click anywhere in the Line Chart window and choose the desired Legend Chart item from the context menu. However.Chapter 29. [U]ARFCN. this data will be shown in the pane regardless of which chart the legend currently refers to. To focus the legend on a different chart.3.4 under Additional Information Tab. you can edit the line chart window name and deselect the horizontal grid lines which by default are drawn in the background.3.4. 29.4.2. This dialog appears: 332 . 29.4. • • Editing the Contents of a Chart Select the chart you want to edit in the list box. Editing General Properties of a Chart On the General tab of the Line Chart Properties dialog.TEMS Investigation 14. Click Edit Chart.1 User’s Manual 29. Adding Charts • To add a new chart in the Line Chart window.4. 29.1. right-click anywhere in the Line Chart window and choose Properties. Changing Line Chart Contents and Properties To edit the contents of the line chart and their presentation. click Add Chart. for the Line Chart template it is MS1). timeslot indicators. The information elements that can be plotted are chiefly those that represent or are derived from measured physical quantities (e. chapter 2. otherwise. A maximum of seven elements can be presented. Line Charts Information Elements Tab Here you edit the set of information elements to plot and how to present them. See Information Elements and Events. move the elements you want to present from the Available IEs to the Selected IEs list box. it is taken from the same device as before. scrambling code indices. Flags.0 333 . You can use the Ctrl and Shift keys to select multiple items in the boxes. the element is taken from the next device. The first time you move an information element to Selected IEs. and the value with the next higher argument is shown. and the like cannot be plotted. signal strength). it will be picked from the device the line chart is drawn for (see the title bar. From elements with an argument the value with the lowest argument is picked.g. Using the arrow buttons. one of two things will happen: • • if the element has an argument. If you move the same element to Selected IEs again. NT12-7002 ver 1. • • First select information element category in the System combo box.Chapter 29. frequency and channel numbers. TEMS Investigation 14. Choose this if you want the element to be plotted as successive. and consists simply in your selecting one fixed color yourself. Note that it is possible to change the device for all chosen elements at once. neighbors. This is done by clicking the Edit IE button. See section 29. As far as possible.1 User’s Manual Naturally. This option is available for all elements. scanned channels).g. Choose this if you want the element to be plotted as a line. the neighbor ranking) changes. the MS and argument can also be edited directly at any time.g. one and the same color is used throughout for a given channel.4. Color: Fixed 334 . The point of this is to ensure that you can easily see when the sort order of the list (e. IE Argument Style: Bar Style: Line Color: Assigned to channel The argument (if any) of the information element.4. tightly packed vertical bars. In the ensuing dialog you also customize the presentation of the information element: Mobile The device to pick the information element from. This option is available only for elements made up of sorted channel lists (e. the application automatically assigns a color on the basis of what channel is shown. If it is chosen. You can adjust the line width. it will be picked from the device the line chart is drawn for (see the title bar). This setting works the same way as Upper visible limit for IE. Check this if you want to compare the plotted values with a threshold line drawn at a specified value.Chapter 29. move the event you want to present to the Selected Events list box. Line Charts Upper visible limit for IE Upper limit of the value range shown for this information element. (The dedicated mode color is not usercustomizable. the plot color turns deeper when the phone enters dedicated mode. That is. Lower limit of the value range shown for this information element. it is taken from the next device. 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. NT12-7002 ver 1. If you check this box. The image file used to label the vertical line indicating the event. For complex information elements. • Using the arrow buttons. this setting adjusts the range in the Y-axis pane. and the brighter color chosen in the Color box is reserved for idle mode.) 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. If you move the same element to Selected Events again.0 335 . the limit is automatically changed for all other arguments as well. A shortcut is therefore provided for this operation. since the additional information is presented only as text and not graphically. Exporting the Line Chart Window The line chart window can be exported separately to a file with extension . • Deleting a Chart In the Line Chart Properties dialog. select the chart you want to delete and click the Delete Chart button. choose Change MS: • For each chart.4.4. This tab works exactly like the Information Elements tab. From the context menu. select the device to pick data from. 29. • Right-click in the Line Chart window.4. Clicking the Edit IE button in this case only enables you to change the device and argument. (The information elements and events selected in the charts will be unchanged.lch. except that here any information element can be selected.1 User’s Manual Additional Information Tab Here you choose the information elements to view in the Additional Information pane.7. 336 .3. Presenting Data from a Different Device If you want to present the same data as before in a chart but from a different device.4.5.) 29. See section 23. it is impractical to edit the MS field for each information element separately as described in section 29.5. 29.TEMS Investigation 14. One of these is a parallel coordinates presentation.0 337 . chapter 8.Chapter 30. Preconfigured bar charts are listed in Information Elements and Events. Bar Charts 30. The bar chart has a number of presentation modes. NT12-7002 ver 1. The bar chart is especially suited to the presentation of frequency scans. Bar Charts Bar charts are used to view successive snapshots in time of a selected set of information elements. but the chart itself is generic and can present any measurement data. which is strictly speaking a different means of visualization but is integrated into the bar chart window. 1. displaying arbitrary information elements in textual format. and indicating their current values an Additional Information pane. The relative sizes of the panes can be freely adjusted by dragging the interior frame handles.TEMS Investigation 14. containing the charts themselves a X-axis pane. The legend can only gloss one chart at a time. displaying labels for the bars drawn a Y-axis pane for each chart.1 User’s Manual 30. Organization of the Bar Chart Window Chart pane X-axis pane Legend pane Additional Information pane Y-axis pane The bar chart is subdivided into the following panes: • • • • • one or several Chart panes. A maximum of four charts can be accommodated. describing the nature and origin of the information elements shown. along with their associated Y-axis panes. showing the scales for the displayed information elements a Legend pane. 338 . To refocus the legend on a different chart.1 (Visible limit for IE). Each scale is drawn in the same color as the information element. The Legend Pane In the legend full details are provided (for one chart at a time) on the information elements displayed in that chart.Chapter 30. as explained in section 23. just click once more on the bar.4. See section 30.4.4. The Chart pane is synchronized with the Legend and Additional Information panes.1. The value range visible on the y-axis can be changed. At the extreme left in the legend. which will from then on keep track of the maximum and minimum values assumed by this parameter since the bar was clicked. in which case the scale is black. The X-axis Pane The X-axis pane provides labels for the data distributed on the x-axis (for one chart at a time). section 30. By default the labels are simply consecutive numbers.2. To reset the max and min indicators. as well as with all other open presentation windows. The (U)ARFCN and SC/BSIC are left out if they are not directly relevant to an element (e. except when several elements share the same scale.2. NT12-7002 ver 1. you can scroll between scales using the arrow buttons. see. but they can also show the value of an information element or consist of arbitrary text. If the pane is too narrow to show all scales at once. Clicking a bar displays max and min indicators. one indicating transmit power).0 339 . The Y-axis Pane Along the y-axis of a chart are shown the scales of the information elements plotted there. for instance. just click in that chart. Bar Charts 30. 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. the color coding of the chart is explained.g. 3.2.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. Setting Up General Bar Chart Properties To set up some general properties of the bar chart and its presentation. 30. You can choose different contents in this pane for different charts. Adding Charts To add a new chart in the bar chart window: • Click Add.TEMS Investigation 14. as described in section 30. • Deleting a Chart To delete a chart: In the Bar Chart Properties dialog. 340 . select the chart you want to delete and click the Delete button. elements which cannot be drawn in a bar chart).4.3. rightclick anywhere in the bar chart window and choose Properties.3. 30.1. 30.3. The first dialog that appears is this: NT12-7002 ver 1.3. what interval to show on the x-axis. Click Edit. Bar Charts 30. you can edit the bar chart window name and specify that horizontal grid lines should be drawn in the background. • • Setting Up Bar Chart Contents In the Bar Chart Properties dialog.3. 30.4.0 341 . select the chart you want to set up in the list box. what data to plot in the chart. Editing General Properties of a Chart On the General tab of the Bar Chart Properties dialog. In doing so you specify 1. what data to display in the Additional Information pane. The procedures are gone through in detail in sections 30. and how to label it 3. and how to present it 2. Examples of bar chart presentations are found in section 30.3.4.5. You will now work through a sequence of three dialogs.1–30.4.Chapter 30. window-specific colors. 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. Data. • 342 . (Which choice is available depends on the presentation mode.TEMS Investigation 14.3). Colors In this step you select the following (full details on subsequent pages): • Presentation mode. Besides.) The default color range is defined in the Navigator and is dependent on the information element value (see section 5. Presentation Mode. channel numbers. timeslot indicators. fixed. Flags. or to use predefined. The information elements that can be displayed are chiefly those that represent or are derived from measured physical quantities (e. signal strength. and the like cannot be displayed. or a set of components of complex information elements. there is one other option: either to define your own colors for use in the bar chart. are chosen. Colors: You can always keep the default color range for the information elements.1 User’s Manual 30. quality measures). The bar chart is very flexible in that it can be configured in a variety of ways.g.4.1. 4. 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).2. select Bar chart: Single IE with multiple components.4. one which consists of several components.e. It is possible to dynamically adjust the number of components to show. Bar Charts 30. 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. Max The visible range of the information element. If you want to change these settings: • Double-click the item (or click the Edit button): Visible limit for IE: Min. The element must be one with arguments.0 343 . i. NT12-7002 ver 1. • • In the Edit Chart dialog. by making it dependent on another (suitably chosen) information element: see section 30.1. Single IE Presentation Mode In this mode a single information element is displayed.1.Chapter 30. and whether the scale will be flipped with the lowest value at the top. then click OK. check the Use common colors box in the Edit Chart dialog. To set up this presentation. You will then be prompted to define colors later on. uncheck Use common colors and select a color in the box next to the information element. This dialog appears: • • 344 . see section 30. Multiple IE Components Presentation Mode This mode displays an arbitrary fixed set of information element components.4. 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. Select Bar chart: Multiple IE components (fixed set).TEMS Investigation 14. To keep the default colors. To do this. Define one fixed color to be used throughout in this chart. Back in the Edit Chart dialog. 30. Click OK in the Choose Information Element dialog. Otherwise. decide what colors should be used in the chart. 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. • Now click Next to proceed to the next step.2. For an example of a Single IE presentation. • • • Make your changes. You have two options: – – Keep the default color range for the information element.5. check the Use common colors box.1 User’s Manual MS Flip scale The device from which to pick the information element.1. uncheck it. disregarding the default color range. To this end. Click Choose IEs to select your data. the Color column will be absent from this dialog.e. To add a new bar.). NT12-7002 ver 1. click the button in the IE column. depending on the type of bar chart concerned (template or predefined. For each index you select one piece of data: an information element with no arguments. or one component of an element having arguments. • To specify the data that should be represented by a bar (i. If you have checked Use common colors. etc. in the relevant table row. Bar Charts Here. click the Add button. a varying number of information elements may already be listed. In either case. A new row will then be inserted at the bottom of the table once the contents of the bar have been specified. an index on the x-axis).Chapter 30.0 345 . the Choose Information Element dialog appears: • Select an information element. The standard Windows color dialog appears. as described for the Single IE presentation mode (see section 30. If the information element is one with arguments. The table will look something like this: • To remove items from the bar chart. • • For an example of a Multiple IE Components presentation. you are now prompted to define a color for this data item. When you are done specifying the bar chart contents. 346 . Click Next to proceed to the next step.1. The indices of the removed rows disappear from the table.1). and click Remove.4. If you have unchecked Use common colors. Pick a color and click OK. Click OK to exit the Edit IE dialog.TEMS Investigation 14. pick an argument. Click OK in the Choose Information Element dialog. select the corresponding rows in the table. see section 30.5.1 User’s Manual • Double-click the item (or click the Edit button): • • • • • Specify range and scale properties. click OK to return to the Edit Chart dialog. You can select all rows with Ctrl + A. To the IE for Fixed Layout dialog is now added the data item and color defined for the selected index. but when you exit the dialog all items will be renumbered starting at 1. Rather. Parallel Coordinates/Stacked Bar Chart Presentation Mode This presentation mode is the most complex one. There are two graphical representations of the above (conceptually quite distinct): a stacked bar chart and a parallel coordinates presentation.0 347 . and arguments are displayed in the y-direction. • In the stacked bar chart. Bar Charts 30.3.1. The parallel coordinates presentation does not use bars and is thus not a bar chart in the literal sense. and an arbitrary number of components of each element may be shown at the same time. Each information element may have arguments. one composite bar is drawn for each information element. 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. all its components being stacked on top of each other: arg 2 arg 1 arg 0 IEs Optionally. this arrangement may be reversed (one bar for each argument. information elements stacked). It has the following fundamental properties: • • A set of information elements is shown. The information elements are distributed on the x-axis.4. it plots all components of each information element on the y-axis. at a fixed x-axis coordinate.Chapter 30. 1 User’s Manual The parallel coordinates presentation is selected by default in this mode. are distributed on the x-axis. etc.TEMS Investigation 14. make these settings: Do not uncheck IEs on x-axis. If you want a stacked bar chart instead. Selecting Data After deciding the basic properties of the presentation: • Click Choose IEs to select your data.). If you want a parallel coordinates presentation. depending on the type of bar chart concerned (template or predefined. This dialog appears: Here. such a presentation is possible but hardly has any natural interpretation within the TEMS Investigation framework. arguments stacked. Setting Up Basic Properties of the Presentation To set up this presentation. proceed as follows: • Select Parallel coordinates (default) / Stacked bar chart. 348 . check the Stacked bar chart box: • Uncheck IEs on x-axis. a varying number of information elements may already be listed. rather than information elements. arguments stacked if you want to reverse the roles of the axes so that arguments. click Add. Click OK in the Choose Information Element dialog.Chapter 30. A new row will then be inserted at the bottom of the table once the details have been specified. despite the fact that the bar segments (except the bottom one) will be displaced in relation to the scale bar. Note: The y-axis scales look the same also for stacked bar charts. as described for the Single IE presentation mode (see section 30. Double-click the item (or click the Edit button): • Specify range and scale properties. the Choose Information Element dialog appears.1.4.1). • • Click OK to exit the Edit IE dialog. In either case. Bar Charts • To specify the details of how an information element should be presented. • • Select an information element.0 349 . click the corresponding button. NT12-7002 ver 1. To add a new information element. . Choose this option by unchecking Use common colors. one for each argument.5. 350 . Coord. The indices of the removed rows disappear from the table. . Use fixed colors. You can select all rows with Ctrl + A. You have two options: • • Keep the default color ranges for the information elements. you need to decide what colors should be used in the chart. dialog is now added the data item defined for the selected index. check the Use common colors box. but when you exit the dialog all items will be renumbered starting at 1. see section 30. The colors are chosen by the application and cannot be edited. select the corresponding rows in the table and click Remove.TEMS Investigation 14. Click Next to proceed to the next step. When you are done specifying the bar chart contents. • Finally. To this end.1 User’s Manual To the IEs for Par.. click OK to return to the Edit Chart dialog. When you are done: • For an example of a Parallel Coordinates/Stacked Bar Chart presentation. For example: • To remove information elements from the bar chart. (Optional) Specifying text labels on the x-axis instead of the default numeric indices. e. Interval The interval selected here governs what portion of the x-axis will be visible in the bar chart. • Choose Fixed to set an unchanging interval.Chapter 30. Then the number of indices on the axis will always be • NT12-7002 ver 1.2. and only such elements are selectable. Example: If you want to display scan data.4.g. so that accepting the defaults will cause all data to be shown. Choose Set by IE to have the interval dynamically governed by an information element. Scanned RxLev. Note that this is done independently of the data selected in the preceding step. This element must denote the current number of something in order to make sense. Bar Charts 30. it may be a good idea to have the interval governed by Scanned Channels No Of. Interval and Labeling In this step you take care of the following: • • Indicating the interval to show on the x-axis. The default values in the boxes are dependent on the data selected in the previous step.0 351 . 3..3). you can replace the numbering with text labels. Alternatively. either those given under Fixed or the arguments of the information element chosen under Set by IE. Select User-defined text labels to specify arbitrary text as labels.4. and the space available in the chart will be fully utilized at all times.4. Click the Compose button. Example: If you want to display data on neighbors. Presenting Data from a Different Device If you want to present the same data as before in a chart but from a different device.4. There are two options: • 30. the bar width being adapted continuously.1 User’s Manual equal to the number of channels currently scanned. Note: The Set by IE option is disabled for the Multiple IE Components presentation. it is impractical to edit the MS field for each information element 352 .TEMS Investigation 14. . you might want to label the x-axis with the neighbor cell names. This dialog works like the Information Elements tab in the line chart properties (see section 29. Select Text strings from IE to pick labels from a text-format information element. check Text labels on axis.. 30. A dialog appears where you enter a string for each index. Labeling By default the x-axis is labeled simply with numbers. found in the information element Neighbor Cell Name. since this by itself stipulates a fixed number of x-axis indices. but since the additional information is presented only as text and not graphically. • • To enable user-defined text labels.4. Additional Information Here you choose the information elements to view in the Additional Information pane. • • any information element can be selected clicking the Edit IE button only enables you to change the device and argument. there is a shortcut for this operation. Therefore.0 353 .5. NT12-7002 ver 1. Single IE Single IE presentation: Neighbor RxLev (Sorted). From the context menu.) 30.1. choose Change MS: • For each chart.4. • Right-click in the bar chart window.Chapter 30. Examples of Bar Chart Presentations Here are a couple of examples of how the presentation modes can be used. (The information elements selected in the charts will be unchanged.1. Bar Charts separately as described in section 30. select the device to pick data from. 354 . Note that only half of the legend is visible in the picture.1 User’s Manual Multiple IE Components Multiple IE Components presentation displaying an assortment of single-value IEs and selected components of multivalue IEs.TEMS Investigation 14. and with user-defined text labels added on the x-axis. Exporting the Bar Chart Window The bar chart window can be exported separately to a file with extension . See section 23. 30. Bar Charts Stacked Bar Chart.7.0 355 . any unexpected line shape). This arrangement allows the user to spot instantaneously any pattern that is out of the ordinary (that is.bch.Chapter 30. and the colored line. NT12-7002 ver 1. Each point on the horizontal axis represents a network parameter.6. connecting a set of parameter values. Parallel Coordinates Parallel coordinates presentation (the predefined Radio Parameters Parallel Bar Chart for WCDMA). represents a moment in time. 5. The concepts are explained again as they are brought up later in the chapter. Map Concepts In this section. and you might not have use for all of it. are central: • • First. numeric values can also be easily accessed. some central concepts relating to Map windows are defined.5. 356 . If you have loaded a cell file and want to view cell information. Highlights of This Chapter This chapter contains a great deal of information.2.5. 31. A map of the world is provided with the installation. Data on cells. A map usually consists of several map layers (see Layer) and is presented in a Map window. turn to section 31.1 User’s Manual 31. Then you can proceed to set up what data you want to present on the map. use this section as a reference.3–31. TEMS Investigation must have access to positioning data. you must work through some preliminaries which are described in sections 31. Note also that to be able to plot measurements on a map. Map windows are fully user-configurable.1. and information elements are shown along the route in symbolic form. You might want to skim this section the first time around to make yourself familiar with the concepts. Map Windows Map windows are used to display a map of your testing area and present your drive test route graphically on this map. or uncompressed TIF format. bitmap. events. however.TEMS Investigation 14. Map A map is a set of geographical features which are treated as a unit.4. Map files used in TEMS Investigation must be in MapInfo. 31. The following sections. Like the other presentation windows. How to do this is explained in section 31. to be able to use a map file in TEMS Investigation. dat. etc. A map layer may. and . These files are from now on collectively referred to as TAB files. 31. and TIF (uncompressed only). colors.map. Constructing a GeoSet from Map Files A Map window in TEMS Investigation works with a GeoSet instead of an ordinary workspace.3. NT12-7002 ver 1. Theme A theme is a component of a presentation layer. If you have a new map that you want to use in TEMS Investigation. A GeoSet contains settings regarding layer order. for example. Map Windows TEMS Investigation supports the following map formats: MapInfo. an information element or a type of event. Each layer is stored in five different files with the extensions .Chapter 31.id.ind. Label A label is a text string that belongs to a map and can be displayed on it. labels. which make up the map itself. which contain information relating to the cellular network. bitmap. all of the same main type (see Theme below). There are two types of layer: map layers.3). .tab. Layer A layer is a set of data from a particular category which is displayed in a Map window. projections. This file can then be opened in a Map window. for example. If your map is in MapInfo format.1. consist of all the roads or all the water areas on the map. Additional layers can be defined by the user.gst) is a special type of workspace used for map layers. GeoSet A GeoSet (file extension . A presentation layer contains one or several themes. you should construct a GeoSet file for it to be able to save changes to the map later on. One presentation layer is predefined for each main type of theme. .0 357 . displaying. a further layer is provided for pinpoint markers (see section 11. it consists of a number of map layers and a workspace which ties them together. and presentation layers. zoom levels. . avoid using 24-bit bitmap images as maps. Click Save. Note: The GeoSet Manager will ask you to open a GeoSet. You are prompted to name the GeoSet. Click Open Map Files.2. but then any changes made using the Layer Control will be lost. This is done by positioning the map as described in section 31.5. you can construct a GeoSet.bmp). If possible. On the Map window toolbar. • • • • • Click Add.TEMS Investigation 14. • Name your new GeoSet in the edit box of the toolbar. 358 . you must generate TAB files for it. You are ready to start presenting data: see section 31. The map is now displayed with all its layers. Click OK. Choose File Save GeoSet. See section 31. click the Start GeoSet Manager button.7. • The map should now be displayed in the Map window. Choose File Exit to close the GeoSet Manager. • Copy the map’s TAB files to your map directory. • Select your newly created GeoSet file and click Open. Click Cancel to ignore this. Note: It is possible to load TAB files in a Map window directly.1 User’s Manual If your map is in bitmap format (extension . All the selected layers are added to the Layer Control.4. Click Layer Control. This will save your new GeoSet file under the name you entered in the GeoSet Name edit box. without constructing a GeoSet. The GeoSet file must be in the same directory as the TAB files. Select the TAB files you copied to your map directory and click Open. Once you have your TAB files. click the point that has the given coordinates. Map Windows 31. in the Latitude and Longitude fields. 31. • In the Distance section.Chapter 31. Click the Pick button in the Reference Point section.0 359 . 31.2. • • • Specifying the Map Position In this step you input the coordinates of a point on the map. Specifying the Map Scale In this step you indicate the distance between some two points on the map. you must supply this data yourself. so that the map scale can be calculated. click the Pick button. Click Position Map. On the map. NT12-7002 ver 1. In the Reference Point section.4. 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. enter the coordinates (in decimal degrees) of the point you wish to use.4.4.1. A set of presentation layers is already supplied in the application. How to do this is described in section 31.TEMS Investigation 14. you do not need to worry about handling presentation layers.3.5. enter the offset between the map’s x-axis and its direction of north. each presenting a different kind of data: • • information element (IE) themes. a positive number indicating a clockwise offset. When you move the mouse.5. presenting a set of information elements (at most three).tab file is the map file you will use from now on. Release the mouse button at the second point. • Setting the Map’s North Direction What remains is to indicate the north direction of the map. 31. However. Therefore. Presenting Data: Themes This section describes how to present cellular network data on the map. The coordinates of the chosen points appear in the X_Y fields. all your work is to do with themes and is covered in the present section.5. see section 31. enter 90°. Click OK. 31. A file with the same name as the image but with the extension . a dashed blue line appears.3 event themes. The offset lies between –180° and +180°.1. in the North Offset Angle field.5.1 User’s Manual • On the map. see section 31. if the map is oriented with north pointing up.7. in order to present data. For example.4 360 . In the Distance field. to get started with presenting data.4. presenting an event. enter the actual distance between the two points. • 31. click the first point and keep the mouse button down. These are the main types of theme. In the Direction section.tab is created. In short. you can also modify presentation layers and create new ones. • Your map is now positioned. Themes and Theme Types A theme is basically a bundle of settings describing how to present a set of data. The *. you use presentation layers and fill these with themes. Chapter 31. Certain presentation layers are predefined. and AMR layers event themes in the Event layer cell themes in the Cell layer the pinpoint theme in the Pinpoint layer. you always put it in a presentation layer. as is seen in this screenshot (where some layers have been expanded). presenting pinpointing information. How to manipulate layers is the subject of section 31.0 361 . There are several subtypes of cell theme. Click Add/Edit Themes to view the current presentation layers and the themes within them. The various types of theme are put in different layers: • • • • IE themes in the Coverage.5. the Pinpoint theme.5. see section 31. Presentation Layers When you create a theme. NT12-7002 ver 1. see section 31. RF Quality. You can add new presentation layers if desired.5. Map Windows • • cell themes.2. 31.5.6.7. presenting cell information. along with a number of themes. and to use a suite of symbols for such things as status parameters having a small set of possible values. For example. These govern the appearance of a marker that is plotted on the map. It is not possible to define these attributes differently in the map. as set on the Info Element tab of the Navigator: see section 5. By varying its color. it is appropriate to use the color and size attributes for information elements with a continuous value range.3. and use different symbols when the phone is in idle mode. and symbols used in the map are always the default ones for each information element. To create a new IE theme: • • In the Theme Settings dialog. dedicated mode. and shape.5. you create information element themes (hereafter called IE themes). the marker can code the values of up to three numeric information elements.1 User’s Manual 31. select one of the layers (or create a new layer to put the theme in: see section 31. you can have the marker color governed by RxLev and the marker size by RxQual. Presenting Information Elements To present information elements. The colors. Click Add Theme: 362 .3. sizes.TEMS Investigation 14. and so on: More generally.7). size. a positive offset is to the right relative to the direction of travel. Color • Size In this section you specify a rule for the theme marker size. Map Windows System Mobile Offset (pixels) Choose an information element category. This setting decides how far from its true position on the map the theme marker will be drawn.0 363 . in the same way as for the color. This means. Using offsets enables you to display several routes side by side. and select an argument if applicable. of course. See above. Select an element. chapter 2.Chapter 31. The offset direction is at right angles to the direction of travel. Choose the device from which to pick the information element. In this section you specify a rule for the theme marker color: • Choose Range to have the color governed by an information element. that the color will not carry any information. NT12-7002 ver 1. Choose Fixed to use a fixed color. See Information Elements and Events. and no extrapolation of the route is attempted by TEMS Investigation. Once the IE theme has been defined. and not for showing measurement data.5. A general rule is that new theme markers are drawn at most twice a second. whether delivered by a GPS or pinpointed. However.1 below).3.1. A new theme marker is plotted only if a message with fresh data has been delivered by the measurement device. • • 364 . See below. On the other hand. whether markers are actually plotted at this rate depends on other circumstances. 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. Updates will thus be less frequent in idle mode than in dedicated mode. for instance circles. it appears in the box in the Theme Settings dialog under the layer it belongs to. in the same way as for the color.TEMS Investigation 14. pick a font in the first combo box. Map positions. are constantly interpolated (linearly) to enable plotting at half-second intervals. when the phone switches to a different RAB).1 User’s Manual Symbol In this section you specify a rule for choosing the shape of the theme marker.5. If you want to plot such an IE with high frequency. 31. see section 31. interpolation is of course impossible. Arrival of new measurement data. Loss of positioning data. Note that some information elements are not updated this often.3. If GPS data is lost for an extended period of time (for instance while driving through a tunnel) but GPS coverage is eventually regained. if no more positioning data is obtained. If you choose Fixed. will then be plotted along the route at the shortest possible time intervals (about factors influencing this updating rate. include another IE that is frequently updated in the same theme. positions will still be interpolated and plotted throughout the gap. Notes on Route Plotting and Updating The updating frequency for IE themes is governed by a number of factors. Uniform markers. Note also that certain information elements are not updated regularly at all but only on special occasions (for example. then pick a symbol in the second. The Fixed options are useful if you want to use an IE theme just for plotting the route. Here is a summary of the factors that affect theme plotting and updating: • Interpolation. Note: If you create a new event theme for a user-defined event after loading a logfile.0 365 . 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.Chapter 31. 31. Choose the device from which to pick this type of event.4. When you zoom in. Click Add Theme: Event Mobile Choose an event type. you must reload the logfile to make this event theme visible. The plotting density on the map is dependent on the current zoom of the Map window. NT12-7002 ver 1. select the layer named Event Layer. more markers are filled in to show the route in more detail. when you zoom out.5. markers are drawn more sparsely. Specifically. Map Windows • Map zoom. • • In the Theme Settings dialog. you create an event theme. Presenting Events To present an event. It is possible to have more than one cell file loaded. See section 31. sections 4. with a separate theme for each. This presentation also applies to WiMAX cells and Wi-Fi access points defined in an XML cell file (see the Technical Reference. a couple of cell themes are predefined. the underlying layer shines through.7. 31. as is evident from section 31.5. It has the same meaning as for information elements. you do not have to load a cell file first. Where the presentation differs between cellular technologies. Select the font. • If this is checked. Select your image.9 and 4.7.2.TEMS Investigation 14.1 User’s Manual Offset (pixels) Set the offset. • Font Select this to pick an event symbol from a font.e. Wi-Fi and WiMAX both follow GSM. see section 31.1 below. then pick a symbol and set its size and color. individual cells can be tagged with a type. in the XML cell file format. How to load cell files is described in section 6. It is also possible to draw cell information for multiple technologies in the same theme. Bitmap Transparent Select this to use a bitmap image as event symbol. the bitmap is drawn exactly as-is. otherwise no transparency is achieved.5. The themes can be defined at any time. all white pixels in the bitmap become transparent. Presenting Cell Information1 To present cell information. Note that this requires a bitmap with a white background.5. This enables the creation of cell themes displaying arbitrary groups of cells.10).5. you create cell themes. 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.3.3. with the obvious exception of GSM-specific information such as the Cell ARFCN theme. (In fact. Furthermore. and set its size. 366 .5. If this is not checked.5. 1.) Cell information for different technologies can be kept apart in the presentation. i. 5.0 367 .5.Chapter 31.5. regardless of the zoom.5. text labels have been turned off in all of the remaining illustrations in section 31. All cell sites are always plotted. Map Windows The following kinds of cell theme exist: • • • • Basic plotting of cell sites (Cell theme): section 31. The Cell Theme This theme is concerned with basic plotting of cell sites. to avoid clutter.5. select Cell Layer.1 Indication of serving cell and handover (Cell Line theme): section 31.5.5.2 Visualization of neighbor relations (Cell Color theme): section 31.5. Note that certain cells are filled with other colors by other cell themes.5. NT12-7002 ver 1.5.5. Each cell is tagged with a text label if you turn on the Cell labels option (see below). see sections 31.3 and 31. proceed as follows: • • • 31.5.5. which by default hide the Cell theme. However. Presentation on Map Three-sector site (three cells) Omni cell The zoom of the Map window does not affect this theme.5.3 (GSM:) Indication of cells using the same ARFCN as a given cell (Cell ARFCN theme): section 31.1.4 In the Theme Settings dialog.5.4. To create a new cell theme. The Select Theme Type dialog appears. Choose a cell theme type.5. Click Add Theme. see the Technical Reference. Cell presentation 368 . chapters 3 and 4.TEMS Investigation 14. GSM and WCDMA cells are told apart by inspection of what type of channel is defined (ARFCN or UARFCN). This section governs how cells are drawn.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.7.) Cell type Type of cell indicated in cell file. In XML cell files this is identical with the CELL_TYPE element: see the Technical Reference. Choose a cellular technology to plot only cells from that technology. Choose ALL to plot cells from all technologies. (Regarding cellular technology support in the CEL and XML cell file formats.13. In CEL files. section 4. You might want to create one Cell theme for each technology. If you uncheck this option. If the beam width is not stated. The displayed information. provided that the cell is completely described in the cell file. it turns red.0 369 . The color to be used for the border of the cell symbol. it is set to 360º in the plot (omni cell. full circle). (However.5.5.3 and 31. incompletely described cells will not be marked as such in any way. The color to be used for the interior of the cell symbol.6.Chapter 31. a text label will be printed next to each cell. When you select a cell. taken from the cell file.5. In either case. • Cell labels If you check this option. this highlighting ceases to be visible if a Cell Color or Cell ARFCN theme is also displayed: see sections 31. Incomplete cells The default color to be used for cells that are incompletely described in the cell file. Map Windows Radius (pixels) Border color Fill color The radius of each cell symbol (circle/sector of circle) in pixels.4). the following plotting rules apply: • If the antenna direction is not stated in the cell file. Uncheck to make the symbol transparent.5. is as follows: • • • • • GSM: Cell name WCDMA: Cell name and SC LTE: Cell name TD-SCDMA: Cell name CDMA: Cell name NT12-7002 ver 1. it is set to zero degrees in the plot (sector centered on “twelve o’clock”). see the illustration in section 31. Use with Phone Data For a phone. rather.TEMS Investigation 14. this theme is used to indicate • • the serving cell (WCDMA/CDMA idle mode. no interaction with base stations is involved during scanning. TD-SCDMA) active set members (WCDMA connected mode/CDMA traffic mode) (The user interface uses only the term “serving cell”.1). and the cell is identified which a user terminal at the same position would be most likely to use. The Cell Line theme has different meanings depending on the data source: phone or scanner. LTE. GSM.5.5. Inter-system handovers are visualized in the same way as intrasystem handovers.5.) Additionally. Use with Scan Data With scan data.1 User’s Manual 31. provided that cells from both cellular technologies are visible in the Cell theme (section 31. the theme indicates positions where handovers have taken place. This points out the cell that uses the currently strongest signal as measured by the scanning device.5.2. 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 . Of course. the Cell Line theme gives a best server indication. 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. Map Windows Presentation on Map route line to current serving cell Like IE theme markers (section 31. NT12-7002 ver 1. cell lines are plotted with a variable density.3. ensuring that large swaths of the map are not completely covered by such lines when the Leave trail option is checked. This density is governed among other things by the zoom of the Map window. all that is said of serving cells/active set also applies to best server indications.1). Setup Dialog Below.Chapter 31.0 371 .5. The line width is adjustable. Set the offset for the starting point of the line. At handover. Check this to leave all serving cell lines on the map.5. a line is drawn from the position where the old serving cell or active set member is last used.1 User’s Manual System Mobile Offset (pixels) Governs what IEs are selectable. Check this to continually display a line connecting the current position along the route with the current serving cell/active set members. 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 . The line will remain on the map.TEMS Investigation 14. choose the desired category in the System combo box. the line is shifted in the same way as an IE theme marker. 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). This feature is available also for best server indications. i.3). although no actual handover is involved. These settings refer to indication of handovers. These settings govern the indication of current and past serving cells/active set members. Pick a color in the combo box. Select this to have the serving cell line drawn in a fixed color. Note that they are independent of the Serving cell settings. The line remains after the phone has moved on.e. At handover. It has the same meaning as for information elements (see section 31. Choose the phone whose serving cells are to be displayed. This feature is available also for best server indications. although no actual handover is involved. Select this to have the color of the connecting line(s) governed by an information element. Map Windows 31. in the realtime presentation as well as during logfile analysis.5. The only phone data fed into this theme is the serving cell data. active set WCDMA example: Cell Color and Cell Line themes.5. 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). independently of the phone’s interaction with the network. if you click an arbitrary cell. Active set members pointed out by solid lines (black). the theme will be displayed with that cell as serving cell instead. the cell drawn in green will be the phone’s current serving cell.Chapter 31.0 373 . By default. Neighbors indicated for all active set members (dashed red lines). NT12-7002 ver 1. However.3. The neighbor relations shown are those indicated in the loaded cell file. Presentation on Map yellow color from Cell theme GSM example: Cell Color theme (no route). therefore. the neighbor presentation is not affected by the phone’s neighbor reporting. 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 g. Disabled for presentation layers. a context menu appears with choices as described below. Note that the visibility of presentation layers can also be set in the Theme Settings dialog (see section 31.8. Set label properties for the selected layer. Check to make the labels of the selected layer visible. the layer they belong to must be visible.8). (No further history of views is maintained. Regional Options NumbersMeasurement System).8. Check to make the selected layer in the list visible. For labels to be visible. 31. Previous View This command returns you to the previous map view. The Scale Bar This command shows and hides a scale bar showing distance in kilometers or miles.Chapter 31.8.0 383 . Map Context Menu When you right-click in the map. Note that the visibility of labels may be conditioned by the zoom range. 31. See Labels below. should be turned off for map layers.2. Selectable Automatic Labels Not used. Disabled for presentation layers. Disabled for presentation layers. Set display properties for the selected layer. should be turned off for map layers. Editable Display Labels Not used.1.5. Select a TAB file and click Open. Remove the selected layer. 31. The unit of distance is governed from the Control Panel in Windows (e.) NT12-7002 ver 1. Map Windows Add Remove Visible Add a layer. Press and hold Ctrl to select a segment of a route (see section 31.3. Area Statistics Tool: Click and drag to view statistics for presentation layer objects within a rectangle (see section 31. See section 31.2).2.10.7. Changes are only temporary and cannot be saved.TEMS Investigation 14.6. or add.8. choose an information element layer to view the whole of your route. 31.8. 384 .4. use the layer control in the GeoSet Manager. 31. To make changes to the GeoSet. GeoSet Manager: Start the GeoSet Manager which is used for creating new GeoSet files and for changing the properties of a GeoSet.4. but many others relate to map handling and have not previously been mentioned. Zoom In: Enlarge a portion of the map to view it in more detail.1. See sections 31.3 and 31. See section 31. See section 31. Add/Edit Themes: Add or remove presentation layers.10. Setting the Map Projection This command allows you to set the map projection. edit or remove themes. For example. Open Map: Open a map. Some of these activate functions described earlier in this chapter. It should be the same as in the cell file. see section 31.2).6.1 User’s Manual 31. The Map Window Toolbar This section gives a description of the Map window toolbar buttons.9. Layer Control: Manage layers or change displaying or labeling properties. View Entire Layer This commands zooms out to show the whole of the chosen layer.5. Position Map: Position a map which is in bitmap or uncompressed TIF format. Selection Tool: Click a presentation layer object to select it. Doubleclick the object to inspect what information it contains. 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.1. Regarding positioning of logfile data by pinpointing in the Map window.10. Ruler: Measure the distance of a route on the map consisting of straight line segments. Double-click at the endpoint. Pinpoint: Mark waypoints on the map. Clear Map: Remove all the information in presentation layers from the map. Last Item: Select the last object of the same type. GeoSet Manager The GeoSet Manager looks and works much like a Map window. If you have zoomed in and want to view the entire route again. right-click in the map. Previous Item: Select the previous object of the same type. However. except cell site information.3. and select the Defaults tab. choose Entire Layer. choose View. while changes made in a Map window cannot be saved.0 385 . and specify one of the presentation layers. The distance of the last segment and the total distance are shown on the status bar at the bottom of the Map window. Click in the map to indicate a starting point. 31. Map Windows Zoom Out: View a larger area than the current map view. Next Item: Select the next object of the same type. To change the unit of distance. Center Map: Click a spot in the map to center it around this spot. right-click in the map. see section 11. Pan Tool: Move the map by clicking and dragging. choose Map Properties. Holding down the Ctrl key swaps the zoom operations. then click at each turn. changes made using NT12-7002 ver 1.Chapter 31. 10. choose Map Projections. If your GeoSet contains multiple layers with different projections.1.TEMS Investigation 14.2. click the Start GeoSetManager button on the Map window toolbar.2. To start the GeoSet Manager.10. Layer Control The Layer Control works the same way as in Map windows. See section 31. Projections It is possible to set which projection to use for a GeoSet. • To change the projection. make sure you choose the projection of the layer you usually work with.1 User’s Manual the GeoSet Manager can be saved to the GeoSet (*. 31. 386 . 31.7.gst) file associated with the map. 0 387 .Chapter 32. found on the Navigator’s Menu tab in the Configuration folder. These settings are covered elsewhere in this manual in the appropriate contexts. are collected miscellaneous settings that affect the behavior of the TEMS Investigation application. The General Window In the General window. NT12-7002 ver 1. The General Window 32. KPI data can be collected for GSM and WCDMA. Note that this is different from certain previous TEMS Investigation versions. these are tagged “not in ETSI” in the Technical Reference.1 for performance measurements. 1. that is.4. 33.1 User’s Manual 33. 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. KPIs are not computed in TEMS Investigation or handled explicitly in the application in any way. A number of KPIs are not present in the ETSI specification. to measure accessibility.TEMS Investigation 14.1. retainability. Purpose of KPIs Most of the KPIs have been designed according to ETSI TS 102 250-2 V1. all data needed for KPIs is recorded in TEMS Investigation logfiles.1 The present chapter gives an general discussion of KPIs as well as an overview of how to obtain them with TEMS products. 388 . chapter 11. however. where a “KPI Report” function was provided. and integrity. In the present version of TEMS Investigation. chapter 11. TEMS Discovery or TEMS Automatic are the products to use for explicitly generating KPIs and reports that present them. Listings and brief definitions of the KPIs are found in the Technical Reference. Full detail on technical matters is given in separate documents which are found on the installation CD in the subdirectory Documents. 2.Chapter 33. the service testing should be enclosed by the NT12-7002 ver 1. For example. 33. Integrity KPIs show the performance of successful service attempts.1. Integrity Integrity indicates the degree to which a service is maintained without major disturbances once it has been accessed. 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. 33. perform the following steps: 1. Accessibility Accessibility is the ability of the user to obtain a service within specified tolerances and under other given conditions.1.0 389 . 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. accessing an IP service (for WAP and MMS) activating a WAP session. the user must be able to execute a chain of operations: • • • accessing the packet-switched network as such. the user’s perception of the performance may vary greatly.e. from very good to unacceptably bad. Compose a TEMS Investigation script that executes one or several services. such as (in the packet-switched case) manual reactivation of the PDP context.3. once it has been accessed. Obtaining KPIs with TEMS Products General Procedure To obtain KPIs. Retainability Retainability is the ability of the user to keep a service. 33. Furthermore.2. Even if a service was accessed successfully.1. performing an attach and a PDP context activation within an active PDP context. under given conditions for a requested period of time.2. i. Key Performance Indicators – KPIs (UMTS) 33.1. in order for a service to be accessible in a packet-switched network.1. 33. Run the script in TEMS Investigation. “Events of KPI Type” When you test services in TEMS Investigation.2.1 User’s Manual control activities Start Recording and Stop Recording. and generate KPI reports using one of these products. Open the logfile(s) produced by the script in TEMS Discovery or TEMS Automatic. 33.3. The mathematical relationships between sample size and statistical accuracy are given in a separate document. section 7.2.9 on snippets. These events underlie the computation of KPIs.TEMS Investigation 14. see Information Elements and Events volume. 33. See chapter 20. “Statistical Guidelines for Collecting KPI Data”. please consult the documentation accompanying the relevant product. Obtaining Significant KPI Statistics To obtain reliable KPI statistics you need to collect sufficient amounts of data. 2.4. special KPI events are displayed in the window Events Of KPI Type. 3. For details. “Data Events”. found on the installation CD in the subdirectory Documents. 390 . and particularly section 20.2. 1. 34. 34.3). As wideband speech codecs are now being deployed in mobile phones and networks. Speech Quality Index – SQI TEMS products offer the quality measure SQI (Speech Quality Index) for estimating the downlink speech quality in a GSM. but no comprehensive point-by-point comparison is made. WCDMA. SQI for CDMA can be based on data from any CDMA phone that is connectable in TEMS Investigation. Reference is made to the previously used algorithm (the “old SQI”). Background SQI for UMTS SQI for GSM and WCDMA is a long-standing feature of TEMS products. in TEMS Investigation 9. Speech Quality Index – SQI 34.Chapter 34. see section 34.1.1. 34. the SQI-MOS algorithm includes a model for rating wideband speech. Computing SQI for GSM and WCDMA requires data collected with Sony Ericsson phones.0 391 . or CDMA cellular network as perceived by a human listener.0. This chapter examines the workings of the SQI algorithm. although its fundamental function remains similar to that of the old algorithm (the output of which is still available in TEMS Investigation). and attention is drawn to certain important differences between the algorithms. However. SQI for CDMA currently does not support wideband. the SQI algorithm was completely reworked. See also the document “Speech Quality Measurement with SQI” which is included on the TEMS Investigation installation CD in the subdirectory Documents.1. NT12-7002 ver 1. The focus of this chapter is to describe the new algorithm (called “SQI-MOS” in the application. SQI for CDMA SQI for CDMA uses an SQI-MOS algorithm similar to those for GSM and WCDMA.2. the current algorithm also does not consider the distribution of frame/block errors over time. the percentage of radio frames/blocks that are lost on their way to the receiving party. • Input to the SQI-MOS Algorithm UMTS SQI-MOS for UMTS takes the following parameters as input: The frame error rate (FER. Moreover.65 kbit/s: – – for narrowband. each speech codec has its own strengths and weaknesses with regard to input properties and channel conditions. GSM) or block error rate (BLER. 5. 7. for wideband. The speech codec used. the old SQI algorithm includes a special “handover penalty” mechanism lowering the SQI score whenever a handover has occurred. 7. i. 5. 6.95 FR/HR. handover block errors can usually be avoided thanks to the soft handover mechanism.1 User’s Manual 34. and these are treated like any other frame/block errors by the SQI-MOS algorithm. This is available in GSM only.2 FR. on the other hand. and 12. every handover causes a number of frames to be lost. It should be noted that in WCDMA. Handovers are not modeled independently in any way by SQI-MOS.60.e. 4.2.1. 8.2.1 More generally. but the model is tuned separately for each codec to capture its unique characteristics. GSM FR. usually because of bad radio conditions.75 FR/HR. In contrast.2 FR.85. 34. In GSM.TEMS Investigation 14. 392 . • • The bit error rate (BER). Frame/Block errors also occur in connection with handover.65 1. 10.4 FR/HR. The same basic SQI-MOS model is used for all supported speech codecs. and 12. no such quantity is reported by UEs in WCDMA mode. and GSM HR all GSM AMR-NB and AMR-WB modes up to 12.9 FR/HR.15 FR/HR. The general speech quality level and the highest attainable quality vary widely between codecs. 6. WCDMA). SQI-MOS for UMTS is implemented for the following codecs: • • GSM EFR.7 FR/HR. 1.0 393 .2. SQI-MOS for CDMA is implemented for the following codecs: • • • • QCELP13K EVRC SMV VMR-WB (narrowband input only) 34.75.4.5 s (CDMA) 2–4 s Such a high update rate is possible thanks to the low computational complexity of the algorithm. 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. 1.9.7. The SQI-MOS algorithm produces a new quality estimate at intervals of • • (UMTS) approximately 0. 6. for wideband. 34.2.60.2.15. 10. 6. The score is thus a value ranging from 1 to 5. including bit rate information The general discussion of these parameters in section 34. and 12. ACR stands for Absolute Category Rating: this is the “regular” MOS test where speech samples are rated without being compared to a reference. 8.95. 7.1 applies equally to CDMA (with the term “handoff” substituted for “handover”).3. Input parameters are: • • Frame error rate Speech codec used.Chapter 34.2. Speech Quality Index – SQI • all WCDMA AMR-NB and AMR-WB modes up to 12.65 kbit/s: – – for narrowband. 4.85. NT12-7002 ver 1.2.65. compare section 34. 5. and 12. 5.2. CDMA SQI-MOS for CDMA closely resembles WCDMA SQI. whereas SQI reflects the radio link quality only. 2.3. PESQ measures the quality end-to-end. 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).4. however. for reasons sketched in section 34.2 The exception is the wideband modes. also taking the fixed side into account. The same MOS scale and range are used for both (as is the custom in the field of speech quality assessment). which was trained using listening tests alone. Wideband SQI-MOS (UMTS) It is necessary to point out that narrowband and wideband SQI-MOS scores are not directly comparable.1. This is completely different from the old SQI algorithm. A further complicating circumstance is that there is no simple mapping between wideband and narrowband SQI-MOS.4.1 User’s Manual 34. Regarding the latter.0.2. It should be stressed that SQI-MOS cannot be derived from these dBQ scores.TEMS Investigation 14. This means that 1. It follows from this that when interpreting a figure such as SQI-MOS = 4.pesq. the two algorithms are distinct (even if similar in general terms). as benchmarks. Old SQI (UMTS) The old SQI (still available in the application) is expressed in dBQ. see section 34. and no exact mapping exists in this case either. SQI-MOS vs. 34. 34.1.3.4. in absolute terms. This is because wideband speech coding models a wider range of the speech frequency spectrum and is thus inherently superior to narrowband coding. a given MOS score indicates. Note carefully that PESQ and SQI-MOS do not have the same scope. rather than actual listening tests. a higher quality for wideband than for narrowband. The highest attainable quality is therefore markedly better for wideband. that is.1. 394 . At the time that work was done.org. where adjustments to the models have been made using the results of external listening tests. See www. no objective speech quality measure of the caliber of PESQ was yet commercially available. Narrowband vs. the SQI-MOS models have mostly been trimmed using PESQ scores.1 In fact. it is necessary to consider what speech bandwidth has been encoded. but they do it in completely different ways.2). NT12-7002 ver 1. The use of PESQ as a benchmark therefore complicated the development of SQI-MOS for wideband.1.3. on the other hand. since the speaker-contingent variation is already built into the model (it has been trained with a large number of speakers). SQI-MOS. since CDMA SQI currently does not extend to wideband.e. a mapping could then be applied to align the wideband scores to narrowband. 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. PESQ scores need to be averaged over a range of speakers in order to eliminate speaker bias.) The PESQ algorithm for wideband (8 kHz) speech coding – as opposed to that for narrowband (4 kHz) – is afflicted with certain recognized shortcomings. wideband PESQ has been found to produce lower scores than narrowband PESQ. Below is a brief discussion of this topic. Such averaging is not required in the case of SQI-MOS. One relevant fact is that. Notes on PESQ for Wideband (UMTS) (This subsection is relevant for UMTS only.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. i. Speech Quality Index – SQI PESQ and SQI values may differ while both being accurate in their respective domains. 34. 1. • Both methods try to assess to what degree the distortions in the received signal will be audible to the human ear.Chapter 34.0 395 . is a no-reference method that works with the received signal alone and extracts radio parameters from it (as described in section 34. variation stemming from the characteristics of individual speakers. even for clean speech.4. This is a phenomenon independent of the circumstances described in section 34. in certain circumstances. 5.1 User’s Manual Unfortunately. (It is probable that the task of assessing wideband speech quality requires further refinement of the mathematical models used. “Quality in Clean Speech and Error Conditions”.4). 1. 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. speech quality in GSM networks was often measured by means of the RxQual parameter (which is also available in TEMS products).e. at zero FER/BLER). 34. Since RxQual is merely a mapping of time-averaged bit error rates into a scale from 0 to 7 ( 3GPP 45. FER = 60% was selected as endpoint. things are not that simple. Wideband PESQ is much more sensitive to speaker bias than is narrowband PESQ (compare the introduction of section 34. and consequently outputs from the two are not directly comparable. This tuning resulted in an adjustment of the SQI-MOS model that is linear as a function of FER/BLER. attained at very high FERs/BLERs2) was left unchanged.TEMS Investigation 14. version 7.975.2.0.4): at a fixed FER/BLER. See 3GPP TR 26.1 Only clean speech ratings from these tests were used. The upshot of this is that no straightforward mapping between wideband and narrowband PESQ can be constructed. 2.) 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. while the rock-bottom SQIMOS (the worst possible score. For narrowband.008. Samples with FER > 60% were excluded from the SQI-MOS modeling. it cannot of course provide more than a rough indication of speech quality. The largest correction was applied to the cleanspeech SQI-MOS score (i. GSM Comparison with Other Radio Parameters In the past. wideband PESQ scores for different speakers show a spread of more than one point on the MOS scale. but so far with no satisfactory results. Attempts have been made within ITU to develop such a mapping. section 8. 396 . this variability is limited to a few tenths of a MOS point. The material used was the results from listening tests conducted during standardization of the AMR speech codec.0. Performance for higher-bandwidth audio signals (wideband.862/en 35. including PESQ and POLQA. and CDMA networks. Audio Quality Measurement (AQM): General Audio quality measurement. data. short for Perceptual Evaluation of Speech Quality. WCDMA. www. The PESQ algorithm is defined by the ITU-T standard P. Audio Quality Measurement (AQM): General 35.863 standard. The POLQA algorithm is designed along similar lines as PESQ. superwideband). One example is the effects of packet loss and of packet loss concealment.1.int/ rec/T-REC-P. is an algorithm which measures end-to-end speech quality by comparing one party’s undistorted input signal (serving as reference) with the degraded version of the same signal received by the other party. it has been refined to eliminate known weaknesses of PESQ. 35.862. particularly in these areas: • Handling of new and complex types of distortions that arise from today’s convergence and coexistence of voice.Chapter 35. 3G and 4G/LTE.itu. defined in the ITU P. However. being a reference-based method that compares the degraded speech with the undistorted original to assess quality. and multimedia application services. • NT12-7002 ver 1. The POLQA Algorithm POLQA (Perceptual Objective Listening Quality Analysis). The PESQ Algorithm PESQ. 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. can be purchased as an option with TEMS Investigation. and VoIP.2. is the successor of PESQ and has been specially developed for HD voice. It can be performed in GSM.0 397 . Measurement Setups in TEMS Investigation Audio quality measurement (AQM) in TEMS Investigation can be done in a number of contexts and hardware configurations.1 User’s Manual • Performance for CDMA speech codecs and hence for CDMA networks in general. CS voice Mobile to fixed Mobile to mobile Mobile to mobile Call Generator. More information about POLQA is available at www.3.itu.1 36.863/en. 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.int/rec/T-RECP.2 37 38 VoIP Mobile to mobile 398 . 35.TEMS Investigation 14. 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. measurements are made mobile-originated voice calls. The call may be received: • • by a stationary component known as the Call Generator. handling the downlink.1. MRUs are not offered for sale with TEMS Investigation 14.1. The computation of AQM scores is done in dedicated hardware units called AQM modules: one connected to the phone and to the PC. Below is an overview of the measurement configuration. The product version does however still support AQM with previously purchased MRUs.Chapter 36. taking care of the uplink.0 399 . The downlink AQM module can optionally be mounted along with the phone in an equipment case. which is included on the TEMS Investigation installation CD in the subdirectory Documents.7. 1. and one housed in the Call Generator.1 Further technical information about these methods of audio quality measurement is found in the document “AQM in TEMS Products (Including PESQ)”.1).4). AQM with Call Generator/MRU 36. or by a Mobile Receiving Unit (MRU) housed in a mobile phone (section 36. It is referred to by the M2F DL + UL option in the PESQ Measurement activity of the Service Control script (see section 20. AQM with Call Generator/MRU In this AQM configuration. A separate MRU User’s Manual is also available. 36. connected to the fixed telephone network (section 36. These modules contain DSP hardware.16.2). Please note that POLQA is not available with these configurations. NT12-7002 ver 1. The AQM modules also record a number of further audio quality measurements such as echo delay. See section 11. The phone calls the Call Generator and plays the reference sentences.1 User’s Manual TEMS Investigation. 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 Call Generator responds by playing the same reference sentences. See Information Elements and Events. echo attenuation.7. yielding uplink and downlink PESQ scores. The downlink AQM data is written to regular TEMS Investigation logfiles. The received (degraded) signals at either end are forwarded to the respective AQM modules. the logfile export function is used. and volume.1. 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. To merge uplink AQM data into the logfiles. • • 400 . The uplink AQM data is stored in XML files.TEMS Investigation 14. where the signals are compared with the originals. section 3. It covers the both the Call Generator configuration and the MRU configuration. This is the M2M DL option in the PESQ Measurement activity of the Service Control script (see section 20. AQM with Call Generator/MRU 36. Measurement configuration: TEMS Investigation. Mobile-to-mobile Audio Quality Measurement with MRU The main difference between this setup and that described in section 36.1 is that the fixed Call Generator is replaced by a Mobile Receiving Unit. 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.4).Chapter 36. the MRU does not have an AQM module.0 401 . Another important difference is that only downlink AQM scores are obtained with this method. MRU.16. logfile export 36.2. as recipient of the AQM calls.3. Obtaining AQM Data Here is an overview of how to record and present audio quality measurements in practice. NT12-7002 ver 1.7. • Practical Considerations You can plug a headset into the AQM module during measurement to listen live to the received audio. • Compose a script as follows (for details of all activities.3. See section 20.3.1. One or several downlink AQM modules (either stand-alone units or DSP cards mounted in an equipment case). For mobile-to-mobile AQM. 36. set Measurement Type to “M2F DL + UL”. Recording AQM Data The description below assumes that a single phone is used to make audio quality measurements. • • • Prerequisites You need to possess the following: License for collecting AQM data: see the Getting Started Manual.3. • 36. One AQM module is required for each phone that you want to measure AQM with. see chapter 20): – – Add a Dial activity.3.4.e.3.16. section 10. Phone supporting audio quality measurement: one of those listed as AQM-capable in the Getting Started Manual.3.2.1. It is possible to perform such measurements with several phones at once. you must not adjust the volume using the headset. set a value for PESQ Duration.7. For mobile-to-fixed AQM. The AQM algorithms require a fixed preset volume. using a different AQM module with each phone.1 User’s Manual 36. However.TEMS Investigation 14. set Measurement Type to “M2M DL” to designate an MRU as receiving party in the same manner. Finally. The phone will then make voice calls to a Call Generator (identified by its phone number). which governs how long to maintain the call and collect audio quality measurements. put the calls (i. Conclude with a Hang Up activity.2. Call Generator or MRU. Add a PESQ Measurement activity after the Dial. section 3. since that would distort the AQM output. sequences of the form Dial PESQ Measurement Hang Up as just described) in separate branches in a Parallel – – 402 . If you wish to synchronize AQM calls from multiple phones. – – • Book-end all of the above activities with Start Recording and Stop Recording to have the calls recorded in a logfile. 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. Wait until the reports “Dsp Started Ver.0 403 . When using the AQM module for the first time after connecting it. The red LED on the AQM module should go out. use the logfile export function to merge the uplink AQM data (recorded by the Call Generator) into the logfile.1. section 7. AQM with Call Generator/MRU construct. 36. Merging Uplink AQM Data into Logfiles After completing your measurements. simply use the same PESQ Duration for all calls.10. see section 11. however. the logfile export can be skipped. Note that this operation is necessary also for mobile-to-mobile AQM. 2” and “Pre Processing Ready” appear in the Mode Reports window.Chapter 36. although no uplink AQM data is recorded in that case.3.5.7. To have the above procedure automatically repeated as many times as desired. Presentation of AQM Data Information Elements All AQM data is available as information elements. enclose everything defined so far within a While construct.7. NT12-7002 ver 1.2).7.1. so that they can be included in any presentation. Make sure that the phone’s number is defined in TEMS Investigation and enter the number manually if necessary: see section 8. If precise time alignment for AQM data is not of interest. you must wait for the AQM module to start up its DSP and finish some preprocessing. which already contains the downlink AQM scores.2. To also make all calls terminate at the same time. • • • • 36. The same information elements are used regardless of the choice of AQM setup.4. See section 11. Run the script and record your logfiles.5. 36. This is because the logfile export procedure also corrects the time alignment for downlink data (again. Associate the phone with the AQM module on the Navigator’s Equipment tab: see section 9.2. section 11.7. When viewing (downlink) AQM data in real time.TEMS Investigation 14. (For full details. When you merge the uplink AQM data into the logfile.2. or when analyzing a logfile where the uplink AQM data has not yet been merged in. See the Technical Reference.1 User’s Manual Status windows named Speech Quality are provided where all AQM information elements (as well as some other data) are presented. Downlink Frequent AQM is not displayed at all prior to merging. the 5. 404 .5 s offset for downlink data is removed so that all data is correctly aligned. see section 11. you must keep in mind that this data will lag behind other information elements because of the processing delay in the DSP.5.5 s. PESQ Key Performance Indicator A PESQ-based KPI is computable on the basis of TEMS Investigation data.1.) 36.5. or one speech sentence. The offset is 5.2. This configuration is referred to by the M2M DL + UL option in the AQM Measurement activity of the Service Control script (see section 20.7. AQM with Audio Capturing Unit (ACU) 37. all measurement is conducted during mobile-tomobile voice calls.4). AQM with Audio Capturing Unit (ACU) In this AQM configuration.0 405 . 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. TEMS Investigation. 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.1. NT12-7002 ver 1.Chapter 37. Up to four mobile devices. which call each other in pairs. are connected to an Audio Capturing Unit (ACU) which relays the audio to the PC.16. 7. For each phone pair. use a Parallel activity with one branch for each phone.1. Regarding the AQM Measurement activity. Recording AQM Data This section assumes that all equipment has been prepared and interconnected as described in the Getting Started Manual. Run the script and record your logfiles.TEMS Investigation 14.4.2. chapter 16.1. USB hub for phones (delivered with ACU).5 mm cable for Sony Ericsson Xperia arc/arc S.3.1. section 10.16. 37.3.1\Scripts. Preparations See the Getting Started Manual. Custom audio cables (these are phone model specific and need to be ordered separately): – – – • 2. section 3. Phone supporting audio quality measurement: one of those listed as AQM-capable in the Getting Started Manual. Audio Capturing Unit (TerraTec DMX 6Fire USB).1 below show the structure of the ready-made scripts.1. • Compose a script similar to the sample script files which are provided in [My] Documents\TEMS Product Files\TEMS Investigation 14. refer to section 20.2.3. 37.3.1 User’s Manual 37. Audio adaptor cables for connecting audio cables to the ACU (delivered with ACU). Nokia C7 Sony Ericsson W995 phones use the SE System Connector cable from the AQM module cable kit.2. • 406 . The diagrams in section 37. • • • • • Prerequisites You need to possess the following: License for collecting AQM data: see the Getting Started Manual. one dialing and the other answering. chapter 16.5 mm cable for Huawei C8600 3.1. 1. Recommended Structure of AQM Scripts AQM script for one pair of phones.1. If the volume is not kept constant.0 407 . NT12-7002 ver 1.Chapter 37. 37.3. on the TerraTec box using the physical controls. AQM with Audio Capturing Unit (ACU) Note: Be sure never to alter volume levels anywhere during measurement – whether in the phones. or in Windows. in the TerraTec PC user interface. incorrect AQM scores will result. The “Echo” elements.TEMS Investigation 14. 37. chapter 5. Presentation of AQM Data Information Elements All computed AQM data is available as information elements.2. 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. Not all AQM information elements are obtained: see the Information Elements and Events volume. are relevant only when interacting with a PSTN. so they are not populated in this mobile-to-mobile setup. for example. however. so that they can be included in any presentation. 37. Please note.1 User’s Manual AQM script for two pairs of phones. 408 .2. The same family of information elements is used as for the Call Generator and MRU AQM setups.1. The described characteristics of the Xperia arc must be taken into account when evaluating AQM scores obtained with the device. 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). NT12-7002 ver 1. There is one exception. 37. the AQM score is not affected.Chapter 37. CDMA For CDMA. the Huawei C8600 exhibits behavior similar to that of the Sony Ericsson Xperia arc. UMTS Notes on AQM Scores Obtained with Individual Phone Models For UMTS. By contrast.0 409 . 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. for audio samples received by the Xperia arc. with any of the supported UMTS phones as receiver. namely when the Sony Ericsson Xperia arc (Note: not arc S) acts as sender. – Please note again that the above does not apply to the Xperia arc S.3. The reason is believed to consist in the different filtering applied to the audio output in the Xperia arc phone. causing a lowering of PESQ/POLQA scores. a kind of filtering that is judged unfavorably by the AQM algorithms. including AQM.16.1 User’s Manual 38. but instead two PCs are used. For a comprehensive treatment of VoIP testing. found on the TEMS Investigation installation CD in the subdirectory Documents. each of which have a mobile phone connected. no auxiliary hardware components are involved. In this measurement setup. AQM for VoIP Audio quality measurement can also be performed during VoIP testing. The AQM computation is done on the PCs. please turn to the document “VoIP Testing with TEMS Investigation”. 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 .7.TEMS Investigation 14. VoIP testing is controlled by special Service Control activities. Everything about the Service Control mechanisms is covered in section 20. and the audio quality measurement is governed by the VoIP Voice Quality activity. the VoIP clients thus reside in the PCs and not in the mobile devices.2. in both directions but only in one direction at a time.9. which see. Presentation of AQM Data This too is covered exhaustively in the document “VoIP Testing with TEMS Investigation”. The crucial information elements are the PESQ and POLQA IEs in the Media Quality category: see Information Elements and Events. Each instance of TEMS Investigation has a built-in VoIP client.Chapter 38. AQM for VoIP The calling device is connected to one PC and the called device to the other. section 3.0 411 . NT12-7002 ver 1. 38.1. Audio is sent in semi-duplex fashion between the parties. 38. Obtaining AQM Data Full instructions are given in the document “VoIP Testing with TEMS Investigation”. that is. This quality is straightforwardly a function of the codecs used and the bit rate. The unit for VTQI is called “MOS-VTQI”. See also the document “Video Telephony Quality Measurement with VTQI” which is included on the installation CD in the subdirectory Documents. The kind of subjective test which VTQI strives to imitate is one where viewers are instructed to assess both video and audio and combine their perception of each into an overall “multimedia quality” score. VTQI is a no-reference method which judges the quality of the received signal on its own merits. There is no overall assessment of entire calls analogous to static VSQI computed for entire streaming clips (as described in section 40. 39.4. How this algorithm works is the subject of the present chapter.1.2. • 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. without knowledge of the original. since the radio bearer currently used in UMTS for video 412 . It is updated continuously during the call.1 User’s Manual 39. 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. 39. The output from the VTQI algorithm is expressed as a value between 1 and 5. VTQI estimates the quality of the video call as perceived by the viewer at a moment in time.1). General Properties of VTQI Like SQI (chapter 34). conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests.TEMS Investigation 14. However. Each VTQI score is a time average taken over the last 8 seconds. Update Rate VTQI is reported as the information element VTQI Realtime Score. Thanks to the monitoring of BLER. What VTQI Does Not Consider VTQI does not directly consider the signal presented to the human viewer. Bit error rate (BER). bit rate variation is in fact not an issue. This is the most important single cause of poor quality in video telephony.2 kbit/s. is not reported by current WCDMA user terminals and so is not available for use in the VTQI model.Chapter 39. NT12-7002 ver 1. (In the current implementation of VTQI in TEMS Investigation. 39. This element is updated regularly – at intervals of length 1–2 s depending on the phone model – throughout the video call. however. Focusing on BLER means that VTQI will faithfully reflect the impact of air interface conditions on QoE. 39.3.) The audio codec is assumed always to be AMR-NB operating at 12. even slight degradations impacting video and audio perception will still be noticed by the algorithm and affect the VTQI score. but a VTQI model for MPEG-4 also exists. the “clean” quality in terms of VTQI has been computed in advance. This leaves the codecs: – For the H. on the other hand. that is. In practice. – • BLER (block error rate). no analysis of perceptual input is performed to detect specific visible artifacts.263 and MPEG-4 video codecs. The transferred video is not analyzed frame by frame in any way.0 413 .4. This windowing procedure prevents short block error bursts from impacting the VTQI score in a disproportionate manner. what codec is used in the video call is deduced from the signaling between server and client. the first score is thus obtained 8 s into the video call. the video codec is assumed to be H.263. Video Telephony Quality Index – VTQI telephony is always a 64 kbit/s bearer. 4. See also the document “Video Streaming Quality Measurement with VSQI” which is included on the installation CD in the subdirectory Documents. conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests. This chapter takes a look the VSQI algorithm. What VSQI Is Based On The VSQI score is based on the following non-perceptual input: 1.1. The information actually used by the VSQI algorithm is the video codec type and the total (video + audio) bit rate. 414 . 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.2. 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. and their bit rates. Compare chapter 41 on MTQI. without knowledge of the original. This quality is straightforwardly a function of the video and audio codecs used. 40.1 User’s Manual 40. General Properties of VSQI Like SQI (chapter 34). The unit for VSQI is called “MOSVSQI”. The quality of the encoded (compressed) signal prior to transmission.TEMS Investigation 14. The “clean” quality has been computed in advance for the codecs listed in section 40. 40. 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.1. e. Static and Dynamic VSQI Two versions of the VSQI algorithm have been devised: one static and one dynamic version.263. in the video streaming client). 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. however. Video Streaming Quality Index – VSQI 2. Thanks to the monitoring of packet loss (item no. is contained in the information element Streaming VSQI. on the other hand. 3. and so on will still be noticed by the algorithm and affect the VSQI score.2 above). no analysis of perceptual input is performed to detect specific visible artifacts.1. Input parameters to the static version of VSQI are as follows: • • • • • • Video codec used (H. Dynamic VSQI.4.3. H. Static VSQI is presented in the event Streaming Quality VSQI. we may describe the calculation of static VSQI with the following formula: NT12-7002 ver 1. What VSQI Does Not Consider VSQI does not directly consider the signal presented to the human viewer.4. 40. 2 in section 40. Static VSQI The static version of VSQI takes an entire streamed video clip as input and assigns a single quality score to it. 40. The transferred video is not analyzed frame by frame in any way. the time required for initial buffering and the incidence of rebuffering. The amount of initial delay and the subsequent interruptions during playback of the video sequence: that is.Chapter 40. 40. It does not appear as an information element.0 415 . jitter.264. The amount of packet loss at the application level (i. that is. even slight problems with blockiness. e. disturbances towards the end will be more harshly penalized by viewers than those occurring early on. For clips considerably longer than 30 s. The latter is then translated into a deduction from the VSQI score. Each VSQI output value is dependent on the recent history of the streaming session (i. it would probably perform slightly worse for long clips.2. It is updated regularly – at intervals of the order of 1 s – while the video clip is playing. and moreover if the clip is short enough it will have been buffered in its entirety before the replay starts. the time spent rebuffering. recent packet loss levels and possible recent buffering events).4.) 40. 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 . A running packet loss average over the last 4 s is computed approximately every second. (The dynamic version of VSQI is naturally not affected by this limitation. on the other hand. and the number of rebuffering events. so that no rebuffering will ever occur. The size of the buffering penalty depends on the time taken for initial buffering.TEMS Investigation 14. Therefore. and the values thus obtained are weighted and summed to yield an appropriate overall measure of the packet loss. The video sequences must not be too short because of how the buffering works: each instance of rebuffering takes several seconds to complete. VSQIclean is the “clean value” obtained for the clip prior to transmission. This score is determined by the quality of the encoding.1 User’s Manual Here. simply because the late ones are remembered more vividly. which is in turn dependent on the choice of codecs and bit rate. The size of the packet loss penalty is determined as follows. since the current VSQI algorithm does not take into account such memory effects. 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 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. 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. VSQI captures the latter by making the slope of the curve steeper for each new rebuffering event. The best achievable quality. Once the replay gets going. 4.0 417 . After the replay has recommenced. Rebuffering events are much less tolerated by viewers than initial buffering. the perceived quality picks up again and soon approaches the highest achievable level. the “ceiling” in the graph. NT12-7002 ver 1. 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. The user tolerates (and might even expect) a certain amount of initial delay.Chapter 40. In this example the packet loss is assumed to be constant so that the influence of buffering can be clearly discerned. 3. VSQI recovers reasonably quickly.e. 1. 2. but the longer the buffering drags on. i. If rebuffering occurs. VSQI deteriorates rapidly. especially if repeated. the more the user loses patience. H. Buffering with skipping means that frames are skipped in connection with buffering.TEMS Investigation 14. 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). MTQI does not include an assessment of audio quality.264. Supported video codecs: H.263. no skipping means that every frame is replayed. MPEG4 Supported video formats: QCIF.1 User’s Manual 41. • 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. The MTQI algorithm can be concisely characterized as follows. REAL. Unlike VSQI. QVGA • • 418 . something which comes in useful in the verification and optimization of frequency plans. Requirements on a Robust C/I Measure Downlink quality in a radio network can be monitored using the TEMS Speech Quality Index.1. areas with inadequate quality can be identified.2.Chapter 42. C/I Measurement (GSM) 42. rough C/I measurements have sometimes been carried out by comparing the BCCH signal power of the serving cell with that of neighboring cells using the same traffic channels (but different BCCHs). if frequency hopping is used in the network. particularly if EDGE is used. In fact. To obtain a correct C/I estimate. By NT12-7002 ver 1. it may produce misleading results. speech quality is not further improved. However. C/I Measurement (GSM) This chapter explains in some detail how GSM C/I measurements are made and why they are useful. one must take into account the possible use of power control and/or discontinuous transmission (DTX). 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. SQI (see chapter 34). Since such a scheme fails to allow for power control and DTX on the TCHs. In this way. In the past. It should however be noted that the C/I measure is just as useful in the context of packet-switched data services. it is difficult to pin down the frequencies that are affected by the degradation. towards the high end of the C/I range. while packet-switched transmissions very clearly do benefit from every extra dB. 42. 42. C/I can be measured in dedicated mode. The C/I measurement function built into TEMS Investigation enables the identification of frequencies that are exposed to particularly high levels of interference. TEMS Investigation offers the possibility of measuring average C/I for each of the frequencies used in a call. The discussion provided here is centered on the voice service. To help resolve such ambiguities.0 419 . in addition. 480 ms) interval. C/I values below this limit would normally result in a dropped call. 420 . An Example To illustrate the use of C/I. and four frequencies are used for transmission. the number of bursts transmitted from the base station to the phone may be lower than the maximum. the limitation of the measurement range is not a restriction. TEMS Investigation makes measurements only on the bursts actually sent from the base station and disregards bursts not transmitted. the measurement error is typically smaller than 1 dB.. Beyond the upper limit. If frequency hopping is employed. and there are no DTX interruptions. average C/I is presented approximately twice a second. 42. 35 dB. data from a test drive is depicted in the figure below. 25 bursts (on average) per frequency are received in each half-second (to be precise. The test drive lasts 40 seconds.1 User’s Manual contrast. TEMS Investigation does consider these network functions and is thus able to indicate the actual C/I experienced by the phone. which reflects the performance of older technology. the average C/I for each frequency is presented. Hence. the performance is not further improved (at least not with today’s modulation schemes). if the number of hopping frequencies is low.4. A C/I below 0 dB can be regarded as highly unlikely. Accuracy The number of hopping frequencies determines the number of bursts used for the C/I measurement on each frequency. 42.3. The measurement range extends from 0 dB to 35 dB.1 If downlink DTX is used.5. depending on the speech activity level on the transmitting side. The C/I information elements preserve a wider value range –5 . 42. EFR speech coding and cyclic 1. there are fewer bursts for each frequency. For example. With more frequencies. Details on C/I Measurements In dedicated mode. if four frequencies are used.. which is equal to the ordinary measurement interval.TEMS Investigation 14. This implies that the accuracy of the measurements is better for small sets of hopping frequencies. If true C/I is within the range 0 to 15 dB. probably because the power of the interferer increases. that is. indicating poor speech quality. RxLev stays about 50 dB above –110 dBm the whole time. and interestingly. one sees that two of the four frequencies (the thick lines) have a C/I worse than 10 dB during the SQI dip. Now. looking at the C/I graph. On the other hand. RxLev increases during the SQI dip. SQI dips sharply towards the end of the test drive (after 35 s). 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. C/I Measurement (GSM) frequency hopping with four frequencies are employed throughout. In fact. Such information can then be utilized in the process of optimizing the frequency plan for the area. NT12-7002 ver 1.0 RxLev [dB] SQI [dBQ] 421 . This means that the dip in quality is not due to low signal power level. This explains the poor speech quality.Chapter 42. the quality problem is to do with interference rather than coverage. The upper part of the graph shows SQI and RxLev. identifying precisely which channels are disturbed. 1. open the GSM Channel Verification window from the Control folder on the Navigator’s Menu tab.1. you can use several phones. 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. typically those used in one cell or a set of cells. one BCCH/TCH combination.12) to be able to perform GSM channel verification. GSM Channel Verification The GSM Channel Verification tool allows you to check the availability of a set of GSM traffic channels. To reduce the testing time. the following terminology will be used: • Test case: One row in the GSM Channel Verification window.1 User’s Manual 43. Throughout the present chapter. 43.TEMS Investigation 14. each row corresponds to a particular combination of BCCH and TCH.e.1. Since there is no way for TEMS Investigation to control the timeslot allocation. traffic channel verification may take a non-trivial amount of time to complete. Sony Ericsson phones with both GSM and WCDMA capability must be locked on GSM (see section 9. i. • The GSM Channel Verification Window To perform GSM channel verification. 422 . In this window. Example: If C0 has ARFCN 10.11). Note that test case groups are not explicitly separated in the user interface. • 43. The following dialog appears: MS BCCH ARFCN TCH ARFCN The phone that should execute this test case.0 423 . click Add. Test: All rows in the window.Chapter 43. or in other words the complete contents of the *. TCH = 20}. with BCCH in timeslot 0 and TCHs in timeslots 2–7. then you must prepare two test cases: one with {BCCH = 10. and C1 has ARFCN 20. Test case group: All test cases with the same BCCH.tch file (see section 43. GSM Channel Verification • Group. Adding a Test Case To add a test case. Note that a special test case must be prepared to test TCH timeslots on C0. TCH = 10} and one with {BCCH = 10. Check the timeslots you wish to test. The ARFCN of the TCH to be tested. Band Timeslot The frequency band where the channels are located. NT12-7002 ver 1. The ARFCN of the BCCH to be tested. corresponding to one cell.2. TEMS Investigation 14. 43. In order for a timeslot to pass. That is. you decide yourself whether to accept or reject the result of the test.”). Manual Verification There are two fundamentally different ways of performing channel verification. you cannot keep any of the old test results in the window. The result in the GSM Channel Verification window will look like this: Here.1 User’s Manual You can add multiple test cases without exiting the dialog. • Automatic verification: For each timeslot. Note that to edit a test case which has been partially executed. but you do have the option to create a report on these results (section 43. and in addition a set of user-specified quality requirements must be satisfied. 43. Automatic vs.10) or save the test case in a special file format (section 43. • 424 . Manual verification: For each timeslot. you must reset the test case (section 43. while timeslots not concerned by the test are marked by underscores (“_”).8). To remove a test case. TEMS Investigation decides whether the timeslot can be accepted or not. the call must be set up correctly and maintained for a user-specified period of time.3. by clicking either of two buttons. by entering the settings for one test case at a time and clicking Apply after each.11). Editing and Removing Test Cases To edit a test case. select it and click the Delete button. timeslots to be tested are indicated by full stops (“.4. select it in the GSM Channel Verification window and click the Edit button. NT12-7002 ver 1. You choose how to perform the test in the Properties dialog. #. or you might want to “call a friend” in each instance to have the uplink quality checked as well. You might be content with assessing the downlink quality by calling a service such as the speaking clock. but is a less reliable indicator of what a user’s experience of the radio conditions would be like.. Automatic verification can be done more quickly. Check this to have the Mobile Allocation Index Offset (MAIO) and the Hopping Sequence Number (HSN) indicated in the test report (section 43. Choose Manual or Automatic (see explanation above). In the GSM Channel Verification window. 0–9}.Chapter 43. Manual verification is more work-intensive and probably more timeconsuming. but also yields an improvement in reliability proportional to the work invested. Enter the phone number to call when testing. GSM Channel Verification How to take this decision is up to the user. Valid characters in the phone number are {*.0 425 . +..10) for any test case that fails in automatic verification mode. Verification mode Test phone number Add MAIO and HSN. click the Properties button. TEMS Investigation 14. namely as soon as the delay period has expired. and specify thresholds. 43. Delay time before evaluation Approve timeslot if these conditions are met: The time to wait before evaluating the quality parameters. i.e.5.1 User’s Manual • Choose the QoS parameters tab to stipulate conditions for accepting a timeslot in automatic verification mode. The checked conditions must all be satisfied in order for the timeslot to be accepted. 426 .4. See section 8. Check the conditions you want to use. they are ANDed together. Note: In manual verification mode. The conditions will be evaluated at one point in time. Activating Phones Before running the test you must naturally activate the phones assigned to do the testing. only one phone can be used. Then. the status of the test case will change to Passed. 43. Manual Verification If you have chosen manual verification. While the test is running. NT12-7002 ver 1.Chapter 43. An accepted timeslot will be marked with a green rectangle (with an “h” for hopping channels). If you have listed several test case groups (see section 43. to start running the test currently displayed in the GSM Channel Verification window: Click Start. the application will now wait for you to either accept or reject this timeslot. Activated the phone or phones to be used in the test. GSM Channel Verification 43. To accept a timeslot. and indicated a phone number to call: see section 43. When the testing of a timeslot begins. The test cases currently executed are tagged with a blue arrow in the leftmost column. TEMS Investigation will now start attempting calls on the TCHs specified. In the frequency hopping case. click Accept.4.2. so that multiple gray boxes appear. in the order they have been entered.1.6. although it may of course be practical to do so. this timeslot is tested for all channels in the hopping sequence at once.3.1–43. handover is disabled. it is marked with a question mark in a gray box. they will be executed one at a time. having locked the phone on the corresponding BCCH. If all timeslots in the test case are now accepted. as are all other phone control functions in TEMS Investigation. 43.6.6. Chosen manual or automatic verification mode. Note that there is no requirement to keep test case groups apart in the GSM Channel Verification window.0 427 .1). • • • 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. The test case will ultimately be put in status Failed. the application proceeds to make a new call.TEMS Investigation 14. so any timeslot tested will be verified for all three TCHs at once. At this point. and a new call is begun immediately. 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.1 User’s Manual To reject a timeslot. see section 43.3. the call is aborted (not affecting the earlier result). A rejected timeslot will be marked with a red rectangle (with an “h” for hopping channels).6. When a timeslot is allocated which has already been accepted or rejected. the application will itself accept the timeslot (if possible). otherwise it will try to make a new call the next time this timeslot is allocated. the user has accepted the performance 428 . 43. within certain limits. When you have made a decision. Manual verification has been chosen. marking it green . 43. though not until all timeslots have been either accepted or rejected. but keeps attempting calls indefinitely. the Accept and Reject buttons are disabled. click Reject. Automatic verification never rejects a timeslot. Automatic Verification If you have chosen automatic verification. and a new call is made within a few seconds.6.4. Frequency hopping is used in this cell (as shown by the “h” symbols). When a call is made in a previously accepted or rejected timeslot.13. The status value of the test case reverts to Not tested. when execution is resumed. 43. Timeslot 4 is currently being tested. while rejecting timeslot 7 (red markers). click Stop. Execution of this test case has been begun but the test is currently stopped.0 429 . All timeslots in the test case have been accepted. 43. Stopping the Test In order to stop the test currently running: In the GSM Channel Verification window. it must be stopped first. All test cases that are in status Testing will change to Stopped. The test will continue from the point where it was halted. Resetting a Test Case You can erase the results for a test case by resetting it. To resume the test. the test case will be processed from scratch again. All test cases that are not finished will be put in status Testing again. which is indicated by question marks.9. Execution of this test case is ongoing. 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. At least one timeslot in the test case has been rejected. If the test is executing.7. NT12-7002 ver 1.8. GSM Channel Verification of timeslots 3 and 6 (green markers). just click Start again.Chapter 43. 43. This is also indicated in the leftmost column by a blue arrow . the used MAIO and HSN is indicated for that test case. Status values are as in the GSM Channel Verification window. (If the test is executing. Timeslots are marked with one of the following: Timeslot Data OK FAIL TESTING – Timeslot accepted. and select an output location for the HTML file. Meaning 430 .TEMS Investigation 14. To generate a test report. The error condition is also indicated in the leftmost column by the symbol . an HTML report can be generated summarizing the results obtained so far.9. click the Report button. See section 43.10. Test of timeslot not yet completed.) 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. it must be stopped first. Timeslot not included in test. Timeslot rejected. 43. Creating Test Reports At any stage of execution of a test.13. In case of call setup failure. see section 43.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. considerably reduce the time taken to perform the test. 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.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. GSM Channel Verification 43. To open a previously saved *. The test will be saved in a file with extension . To save the complete current contents of the GSM Channel Verification window. Saving and Opening Tests Channel verification tests can be saved to file at any stage of execution.e.11. click Open and select your file.e. This will. as soon as a timeslot is accepted by one phone.tch. lock on BCCH has broken down). Cause NT12-7002 ver 1.Chapter 43. You may assign different test cases to different phones. If several phones are set to execute identical test cases. to begin with they will all work independently. Notes on Performance It is possible to speed up the verification process by letting several phones share the work. The test cases affected by the error executed are tagged with the symbol in the leftmost column. click Save. or you may do both. 43. it is marked green for all other identical test cases.0 431 .12. 43.13. as a rule. and no phone will test it further. ongoing call has been lost). Error Conditions In certain situations the application judges it impossible to complete the verification and therefore aborts the test. or assign identical test cases to several phones. (The test must be stopped first. However. One idle mode report received from wrong cell while in dedicated mode (i. Timeout MS not connected 432 . • Invalid TCH Test case attempted 10 times in a row without the right TCH being allocated. Ten consecutive calls made where the call setup procedure could not be concluded successfully. Phone not activated at start of measurement. lock on BCCH has failed).TEMS Investigation 14.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. and no timeslots marked green or red (typically occurs when the chosen TCH is in fact not used where assumed). lock on BCCH has broken down).e. Three idle mode reports from wrong cell or two no service reports received while trying to lock on BCCH (i.e. 2. Keyboard Shortcuts A.1. Keyboard Shortcuts Appendix A.Appendix A. 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. Drive Testing Shortcuts Function Shortcut F2 Ctrl + F2 F5 F6 Activate all Deactivate all Insert filemark Start recording NT12-7002 ver 1.0 433 . Logfile Load Shortcuts Function Shortcut Shift + F10 Ctrl + F10 Open logfile Stop logfile load A.TEMS Investigation 14.4.1 User’s Manual Function Stop recording Shortcut Ctrl + F6 A. Bar Chart Function Show properties Show setup wizard (status window only) Message Window Function Show only messages of this type Hide messages of this type Undo (show only/hide) Find next message of this type Shortcut Shift + P Shift + W Shortcut Ctrl + Y Ctrl + H Ctrl + Z Right arrow 434 . Line Chart.3. Shortcuts for Active Window Function Shortcut Ctrl + P Print window Status Window. 0 435 . Some route sample must already be selected. 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. 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.Appendix A. 1 User’s Manual Function Paste Cut Shortcut Ctrl + V Ctrl + X 436 .TEMS Investigation 14. trp File Type Setup file for ArcView format logfile export Bar chart export file Cell file Service Control configuration set Setup file for Ethereal format logfile export User-defined event Logfile exported in text format Line chart export file TEMS Investigation logfile (old format) Map window export file Setup file for MapInfo format logfile export Message window export file Setup file for Planet format logfile export Setup file for logfile report Status window export file Audio indication for event TEMS Investigation workspace Setup file for text format logfile export TEMS Investigation logfile (current format) NT12-7002 ver 1.rpt .lch .0 437 .eth .bch . File Types in TEMS Investigation Appendix B.cel .evt .aex .config .mex .tdc .log .tex .stm .svt .fmt .pex . File Types in TEMS Investigation These TEMS-specific file types are used by TEMS Investigation: Extension .Appendix B.map .mw . TEMS Investigation 14.1 User’s Manual Extension .tsc Service Control script File Type 438 . The instruction sequences used to control devices are now referred to as scripts. The Command Sequence window was replaced by the windows Service Control Designer and Service Control Monitor. The “equipment channel” concept is not used in the Navigator or in the Service Control windows (where only the designation “EQ” appears). NT12-7002 ver 1. Status information is also provided by the Status Control Monitor window.Appendix C. section 7. Comparison with Pre-12. which serve similar purposes. A few pointers regarding these changes may be helpful to users with experience of pre-12.0 User Interface The user interface in TEMS Investigation 12.0 underwent major changes compared to previous product versions. Comparison with Pre12.1.1 • • • 1.1. 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). there is one exception. All of its functions were taken over by the newly introduced Equipment tab in the Navigator. in presentation windows. see the Getting Started Manual.2. See section C. With regard to COM ports.0 versions of TEMS Investigation. the equipment channels “MS” and “DC” still make an appearance. However. Their functions were moved into the Navigator (Equipment tab.0 User Interface Appendix C.0 439 . The Equipment Configuration window and the Connections toolbar were removed. • • Equipment Handling The Equipment Control toolbar was removed.2 for a comparison of the old and new tools. top pane). C. command sequences were built up of commands. User Interface • SCtrl uses a graphical user interface where scripts are assembled in the form of flowcharts. whereas in CSeq. which in CSeq were limited to the Loop. Terminology • In SCtrl.2. There is no distinguishing of “MS” and “DC” channels as in CSeq. Manual voice dials. you compose scripts consisting of activities. 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. • C. Inter-device synchronization is implicit in a SCtrl workflow wherever workflow branches converge. the Command Sequence (“CSeq”) tool.0 predecessor. This allows straightforward and unrestricted application of branching and other control structures. and scanning commands are no longer issued from the Equipment Control toolbar but rather from the Navigator (Equipment tab. 440 .1 User’s Manual • The procedure of preparing a device for use was simplified. then manually activated and deactivated. bottom pane). Service Control vs. Command Sequences This section contrasts the Service Control (“SCtrl”) feature with its pre-12. and Synchronize operations. The same component is also used to initiate data service sessions without running a script (a function which was previously unavailable).TEMS Investigation 14. 1. section 7.2. All supported devices are automatically detected1. Wait.1. There are no longer any “enable” or “disable” operations for devices.e. • Logical Structure • Activities in SCtrl scripts are always assigned simply to the device as a whole (i. the sole exception is the devices covered in the Getting Started Manual. to the “EQ”). control commands. Again. all setups for data service testing are done from within TEMS Investigation. as detailed in Information Elements and Events. See section 20. SCtrl does not have distinct activities for sessions run over an NDIS connection.3. • • • • • C. This is because the KPI concept is no longer explicit in TEMS Investigation (see chapter 33). etc. as was the case in CSeq. they are never incorporated into activities for service testing as could optionally be done in CSeq. Comparison with Pre-12.0 441 . the details of that operation are specified as part of the MMS activity. There is no need (as there was with CSeq) to go outside TEMS Investigation to configure phonebook entries and the like in Windows.0 User Interface • With SCtrl.9. adequate data on which to base KPI computation in other TEMS products (TEMS Discovery. and along with it the old Data category information elements prefixed with “Session”. NT12-7002 ver 1. In SCtrl you indicate the type of data connection (NDIS or RAS) using a parameter in the Network Connect activity. This property always applies to the activity as a whole. 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. TEMS Automatic) is always collected with SCtrl scripts provided that they are suitably composed.17. See section 20.8. SCtrl does not have distinct activities for KPI data collection as did CSeq.). HTTP. Old command sequences composed with CSeq cannot be run by SCtrl. network connect and disconnect (corresponding to dialup and hangup in CSeq) are always performed as separate activities. where the device must connect to an MMS Center. separate information elements are now provided for each data service type (FTP.0 TEMS Investigation versions has been abolished. that is. section 3. Instead. however. not to individual steps performed as part of the activity.Appendix C.2.2. An exception is MMS. “Data” Category Information Elements The generic “session” concept in pre-12. In SCtrl. TEMS Investigation 14.1 User’s Manual 442 . manual 66 Activate activity in scripts 236 activating external equipment in TEMS Investigation 46. 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. 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. 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.0 443 . 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.e.Index Index A access class control. 105 arguments of information elements 6 AT activity in scripts 236 AT commands. 298 audio quality measurements (AQM) 397 autodetect function for equipment not covered by license 52 restarting 61 B Band Lock activity in scripts 236 band lock. 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.TEMS Investigation 14. 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. 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. 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.0 445 . 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. presentation of (WCDMA) 158 BLER target control (WCDMA). 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. comparison with pre-12. 290. 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.TEMS Investigation 14. 301 audio indications for 297 446 . setting up 290 external equipment 4 activating in TEMS Investigation 46.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. 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. 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. 184. 192. 177.0 447 . 58 connectable devices 3 deactivating in TEMS Investigation 59 overview of user interface components dealing with 44 plugging in 46 user-assisted detection of 53. 158. 387 GeoSet 357 constructing from map files 357 GeoSet Manager 385 layer control 386 map projections 386 Getting Started Manual. 1 User’s Manual GPS window 327 properties of 327 GSM Barred Cells (Sony Ericsson phone properties) 282 GSM Cell Selection (Sony Ericsson phone properties) 282 GSM channel verification 422 adding test cases 423 automatic vs.TEMS Investigation 14. manual 424 creating test reports 430 editing test cases 424 error conditions 431 notes on performance 431 opening tests 431 removing test cases 424 resetting test cases 429 running the test 427 saving tests 431 status of test cases 429 stopping the test 429 test 423 test case 422 test case group 423 GSM EDGE Capability (Sony Ericsson phone properties) 283 GSM Handover (Sony Ericsson phone properties) 283 GSM scanning 139 GSM Tx Power (Sony Ericsson phone properties) 284 H handover behavior in GSM (Sony Ericsson phones) 283 Hang Up activity in scripts for video call 264 for voice call 267 Help menu 34 HTC Imagio detection of 51 HTC Touch Pro2 detection of 51 HTTP Get activity in scripts 252 I If--Else activity in scripts 238 IMSI 50 in-building positioning using Map window 86 448 . Index using Pinpoint Window 120 indoor positioning using Map window 86 using Pinpoint Window 120 information elements 5. 433 KPIs (Key Performance Indicators) 213. 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. 388 accessibility 389 integrity 389 obtaining with TEMS products 389 purpose of 388 retainability 389 L labels 357 Layer 3 Messages (Sony Ericsson phone properties) 284 layers in Map window 357.0 449 . 301 Data category comparison with pre-12. 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. returning to 383 right-hand pane 378 scale bar 383 setting projection for 384 statistics 380 toolbar 384 viewing entire layer 384 MapInfo 98. 104 maps 356 centering 385 constructing a GeoSet from map files 357 GeoSet 357 labels 357 notes on route plotting and updating 364 panning 385 positioning maps in bitmap or TIF format 359 themes 357.0 451 . 34 merging uplink AQM data into logfiles 110 NT12-7002 ver 1. 106 MDM 106 export in MDM format 98 loading MDM files in TEMS Investigation 95 Mentum CellPlanner 42 menu bar 28.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. 360 zooming 384 Marconi Planet 98. 381 adding presentation layers 381 control of 382 map layer 357 presentation layers 357. 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. 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.Index network scanning (WCDMA scanning mode) 164 presentation 166 setting up 165 Network Search window (WCDMA) 166 Nokia phones. properties of channel lock control 287 GSM cell barring control 287 RAT lock vs.0 453 . 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 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 .TEMS Investigation 14. 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. 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.0 455 .Index Rohde & Schwarz scanners 139. 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. 1 User’s Manual spectrum analysis 195 Strongest Scanned PN Bar Chart 192 scanning. 181 RSSI scanning 177 sorting of cells in presentations 177 spectrum scanning 178 scanning. 167 RSSI scanning 140 spectrum analysis 143 System Information Decoding 142 scanning.TEMS Investigation 14. GSM 139 BSIC decoding in RSSI Scanning mode 140. 180. 185 RSSI scanning 185 sorting of cells in presentations 184 scanning. TD-SCDMA 182 general settings 182 methods 182 of pilots 183 presentation 184. 167 methods 139. LTE 167 enhanced power scanning 180 LTE signal scanning 168 presentation 176. 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 . 141 C/I measurements 141 device capabilities 139. 178. 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 . 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. 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.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 .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. 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. 240 UDP activity 254 UE control 231 validating 232 Video activities 264 Video Dial activity 264 Voice activities 266 voice.Index Terminate activity 230. creating script for 206 VoIP Answer activity 268 VoIP Dial activity 268 VoIP Hang Up activity 268 VoIP Voice Quality activity 268 Wait activity 225.0 459 . properties of CAS Access Class 280 CAS Lock on PLMN 280 NT12-7002 ver 1. 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. 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 .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. 377 reordering 378 visibility of 377 toolbars 27. 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.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. 32 File and View toolbar 33 Record toolbar 32 Replay toolbar 32 Report toolbar 33 NT12-7002 ver 1.0 461 . 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. dialing manually 77 Video Dial activity in scripts 264 Video Monitor 325 properties of 325 video streaming 324. dialing manually 77 VoIP 410 VoIP Answer activity in scripts 268 VoIP Dial activity in scripts 268 VoIP Hang Up activity in scripts 268 VoIP Voice Quality activity in scripts 268 VSQI 326. 414 evaluating performance of 326 how to test 324 troubleshooting 326 WAP-based 265 video telephony 412 View menu 34 voice calls.0 versions 439 quick guide to 26 user modes 29 user-assisted detection of external devices 53 user-defined events 290 V video calls.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.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 . 1 16 what was new in TEMS Investigation 14. presenting on map 366 WiMAX scanning 197 Window menu 34 Windows 7 233 Windows Vista 233 Wireshark 98.0 11 what’s in this manual 3 what’s new in this TEMS Investigation version 8 While activity in scripts 239 Wi-Fi access points presentation on map 366 WiMAX cells.0 463 . 106 Worksheet menu 34 worksheets 27.Index WCDMA scanning 144 what was new in TEMS Investigation 13. 30 opening from Command Prompt 31 predefined 31 NT12-7002 ver 1.0 21 what was new in TEMS Investigation 13. 31 workspaces 27. Virginia 20190 | USA www. These state-of-the-art offerings facilitate the deployment. and analyzing network performance. ANAlyzE.com/tems The TEMS™ Portfolio offers a complete set of trusted solutions for drive testing. and our products are supplied to the world’s top mobile operators. . All rights reserved. optimization.2012 © Ascom 2012. Ascom reserves the right to change specifications without notice. Ascom Network Testing Inc. and professional service providers. www. ANd opTiMizE MobilE NETworkS. Ascom acknowledges all registered trademarks appearing herein.ascom. equipment vendors. All other trademarks are the property of their respective holders. monitoring. AScoM NETwork TESTiNg lEAdS ThE world iN providiNg bEST-iN-clASS SoluTioNS To MEASurE. benchmarking. TEMS is a trademark of Ascom . 1943 Isaac Newton Square Reston.ascom. We are the industry leader.com/tems 04. and maintenance of mobile networks.
Copyright © 2024 DOKUMEN.SITE Inc.