TEMS

TEMS™ INVESTIGATION 1 3 .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 2011. All rights reserved. Document number: NT11-20502 Contents Contents 1. Introduction 1 1.1. Fundamentals of TEMS Investigation 13.1 . . . . . . . . . . . . . . . . . . . . 2 1.1.1. Package Options – Licensing. . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.2. Connectable Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. What’s New in TEMS Investigation 13.1 . . . . . . . . . . . . . . . . . . . . . . 3 1.2.1. Alternative Mobile-to-mobile AQM Solution . . . . . . . . . . . . . . 3 1.2.2. CS Fallback Events and Information . . . . . . . . . . . . . . . . . . . 4 1.2.3. Extended Set of LTE RACH Information Elements . . . . . . . . 4 1.2.4. Improved Handling of Qualcomm-based LTE Devices . . . . . 4 1.2.5. CDMA/EV-DO Rev. B Measurement and Analysis . . . . . . . . 5 1.2.6. New Connectable User Terminals . . . . . . . . . . . . . . . . . . . . . 5 1.2.7. WCDMA Scanning with Rohde & Schwarz . . . . . . . . . . . . . . 6 1.2.8. CDMA Scanning with PCTel SeeGull MX . . . . . . . . . . . . . . . 6 1.2.9. New Connectable Scanners. . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3. What Was New in TEMS Investigation 13.0 . . . . . . . . . . . . . . . . . . . 6 1.3.1. TD-LTE Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3.2. Data Service Performance Verification with Generic Device . 7 1.3.3. Selection of Preferred Workspace at Startup . . . . . . . . . . . . . 7 1.3.4. New Utility for Sharing Script Configuration Settings . . . . . . . 7 1.3.5. New LTE Information Elements . . . . . . . . . . . . . . . . . . . . . . . 8 1.3.6. New Connectable Equipment. . . . . . . . . . . . . . . . . . . . . . . . . 8 1.3.6.1. UMTS Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.3.6.2. LTE Scanner: Rohde & Schwarz TSMW. . . . . . . . . . . 8 1.3.7. Support for SSH2 Protocol in Iperf Testing . . . . . . . . . . . . . . 9 1.3.8. Support for 64-bit Windows 7 . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3.9. Performance Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3.10. Additional New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3.11. New Features in TEMS Investigation 13.0.1 . . . . . . . . . . . . 9 1.4. What’s in This Manual (and What’s Not) . . . . . . . . . . . . . . . . . . . . . 11 1.5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 NT11-20502 i TEMS Investigation 13.1 User’s Manual 2. Basics of TEMS Investigation 15 2.1. Recommended Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. Installing TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. Starting TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. Quick Guide to the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . 3. User Interface 18 3.1. User Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2. Workspaces and Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1. Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.1. Opening Workspaces from a Command Prompt . . . 3.2.1.2. Predefined Workspaces . . . . . . . . . . . . . . . . . . . . . . 3.2.2. Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3. The Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1. Record Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2. Replay Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3. Report Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4. File and View Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4. The Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1. Help Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2. Replay Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.3. Recording Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5. The Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6. Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. The Navigator 18 19 19 20 20 20 21 21 21 22 22 22 23 23 23 23 24 25 4.1. Equipment Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2. Menu Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3. Info Element Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1. Presentation Attributes of Information Elements . . . . . . . . . 4.3.2. Editing the Color Ranges of Information Elements . . . . . . . 4.3.2.1. Automatic Setup of Color Ranges. . . . . . . . . . . . . . . 4.3.2.2. Manual Setup of Color Ranges . . . . . . . . . . . . . . . . . 4.3.3. Editing the Marker Sizes and Symbols of Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4. Worksheets Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii 15 15 15 15 25 25 26 26 26 27 28 28 28 Contents 5. Cell Data 29 5.1. Creating a Cell File in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.2. Creating a Cell File in CEL Format . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.3. Loading Cell Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.4. Loading Cell Data from Mentum CellPlanner . . . . . . . . . . . . . . . . . 30 5.5. Use of Cell Data in Presentations . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6. Managing External Equipment: General 32 6.1. Connectable Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.2. Overview of User Interface Components Dealing with External Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.3. Notes on Reworked User Interface . . . . . . . . . . . . . . . . . . . . . . . . . 33 7. Activating External Equipment 35 7.1. Plugging In External Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.1.1. Plugging In Phones and Data Cards . . . . . . . . . . . . . . . . . . 36 7.1.2. Plugging In Ericsson Fixed Wireless Terminals . . . . . . . . . . 36 7.1.3. Plugging In Scanners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 7.1.4. Plugging In GPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.1.5. Plugging In Equipment Cases . . . . . . . . . . . . . . . . . . . . . . . 37 7.1.6. Plugging In Standalone AQM Modules . . . . . . . . . . . . . . . . 37 7.2. Starting TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.3. The Navigator Equipment Tab: Basics . . . . . . . . . . . . . . . . . . . . . . 37 7.3.1. Top Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.3.1.1. Device Context Menu . . . . . . . . . . . . . . . . . . . . . . . . 38 7.3.2. Bottom Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 7.3.2.1. Activities Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 7.3.2.2. Information Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 7.3.3. Detection of Equipment: Special Cases . . . . . . . . . . . . . . . . 40 7.3.3.1. Detection of PCTel SeeGull EX Scanner . . . . . . . . . 40 7.3.3.2. Detection of PCTel SeeGull MX Scanner . . . . . . . . . 40 7.3.3.3. Detection of DRT Scanners and Rohde & Schwarz TSMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.3.3.4. Detection of HTC Touch Pro2 Phones . . . . . . . . . . . 40 7.3.3.5. Detection of Equipment Not Covered by License . . . 41 7.3.3.6. Detection of Network Adapters . . . . . . . . . . . . . . . . . 41 7.3.4. User-assisted Detection of Devices . . . . . . . . . . . . . . . . . . . 42 7.3.4.1. Mapping Device Ports to Interfaces . . . . . . . . . . . . . 44 NT11-20502 iii TEMS Investigation 13.1 User’s Manual 7.3.4.2. Qualcomm Devices with LTE/TD-LTE Capability . . . 7.3.4.3. LG and Samsung Devices with LTE Capability. . . . . 7.3.4.4. Data Service Testing with Arbitrary Devices . . . . . . . 7.4. Activating and Deactivating External Equipment in TEMS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.1. Activating External Equipment . . . . . . . . . . . . . . . . . . . . . . . 7.4.2. Deactivating External Equipment . . . . . . . . . . . . . . . . . . . . . 7.5. Managing GPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6. Further Features of the Navigator’s Equipment Tab. . . . . . . . . . . . 7.6.1. The Refresh Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2. Re-pairing Phones with AQM Modules . . . . . . . . . . . . . . . . 7.6.2.1. Details and Limitations of the Re-pairing Function . . 7.6.3. Device Detection Properties . . . . . . . . . . . . . . . . . . . . . . . . 7.7. Saving of the Equipment Configuration . . . . . . . . . . . . . . . . . . . . . 8. Operating and Controlling External Equipment Manually 53 53 54 54 55 56 57 58 59 59 59 60 60 61 9.1. Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2. Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3. Service Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4. Computer Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv 47 47 48 49 50 50 50 51 51 52 53 8.1. Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1. Control Function Support by Device . . . . . . . . . . . . . . . . . . 8.1.2. AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.3. Band Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.4. Nonvolatile Item Read/Write . . . . . . . . . . . . . . . . . . . . . . . . 8.1.5. PESQ Device Pairing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.6. Radio Access Technology Lock (Lock on RAT). . . . . . . . . . 8.1.6.1. RAT Lock vs. Technology-specific Control Functions: Sony Ericsson . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.6.2. RAT Lock vs. Technology-specific Control Functions: Nokia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2. Voice/Video Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3. Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.1. Presentation of Data Service Testing . . . . . . . . . . . . . . . . . 8.4. Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. The Status Control Monitor 45 46 47 61 62 62 63 Contents 9.5. Logfile Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 9.6. Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 10. Logfiles 64 10.1. Recording Logfiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 10.1.1. Inserting Filemarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 10.1.2. Swapping Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 10.1.3. Further Recording Options . . . . . . . . . . . . . . . . . . . . . . . . . 66 10.1.4. Positioning Logfiles by Pinpointing. . . . . . . . . . . . . . . . . . . 68 10.1.4.1. Basic Pinpointing Procedures . . . . . . . . . . . . . . . . . 68 10.1.4.2. Advice on Pinpointing and Recording . . . . . . . . . . . 69 10.2. Replaying Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 10.2.1. Replay Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 10.2.2. Searching a Logfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 10.2.3. Replay Section of Status Bar . . . . . . . . . . . . . . . . . . . . . . . 72 10.2.4. Logfile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 10.3. Loading Logfiles from Other Sources . . . . . . . . . . . . . . . . . . . . . . 72 10.4. Logfile Transfer via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 10.4.1. Setting Up Logfile Transfers. . . . . . . . . . . . . . . . . . . . . . . . 73 10.4.1.1. FTP Server Settings . . . . . . . . . . . . . . . . . . . . . . . . 74 10.4.1.2. Logfile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 10.4.1.3. Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 10.4.1.4. Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 10.4.2. Starting Logfile Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . 75 10.5. Exporting Logfiles in Other Formats . . . . . . . . . . . . . . . . . . . . . . . 76 10.5.1. Preparing an Export Order . . . . . . . . . . . . . . . . . . . . . . . . . 76 10.5.2. Specifying the Contents of Export Files . . . . . . . . . . . . . . . 78 10.5.2.1. Text File Specific Settings . . . . . . . . . . . . . . . . . . . . 79 10.5.2.2. MapInfo Specific Settings . . . . . . . . . . . . . . . . . . . . 81 10.5.2.3. ArcView Specific Settings . . . . . . . . . . . . . . . . . . . . 83 10.5.2.4. Marconi Planet Specific Settings. . . . . . . . . . . . . . . 83 10.5.2.5. Ethereal Specific Settings . . . . . . . . . . . . . . . . . . . . 83 10.5.2.6. MDM Specific Settings . . . . . . . . . . . . . . . . . . . . . . 83 10.5.2.7. “Logfile with Uplink Data” . . . . . . . . . . . . . . . . . . . . 84 10.5.2.8. Saving and Loading Export Setups . . . . . . . . . . . . . 84 10.5.3. Executing Export Orders . . . . . . . . . . . . . . . . . . . . . . . . . . 84 10.6. Merging Uplink AQM Data into Logfiles (UMTS). . . . . . . . . . . . . . 85 10.6.1. Retrieving Uplink AQM Data . . . . . . . . . . . . . . . . . . . . . . . 85 10.6.2. Preparing and Performing a Merge . . . . . . . . . . . . . . . . . . 85 NT11-20502 v TEMS Investigation 13.1 User’s Manual 10.7. Merging Logfiles with Uplink (MTR) Data . . . . . . . . . . . . . . . . . . . 87 10.7.1. The Merging Algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 10.7.2. Limitations of the Merging Algorithm . . . . . . . . . . . . . . . . . 88 10.7.3. Performing the Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 10.7.4. Accuracy of the Alignment . . . . . . . . . . . . . . . . . . . . . . . . . 91 10.7.5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 10.8. Generating Logfile Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 10.8.1. IE Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 10.8.2. Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 10.8.3. Mobiles Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 10.8.4. Scanned Channels Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 10.8.5. User Details Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 10.8.6. Saving and Loading Report Setups . . . . . . . . . . . . . . . . . 101 10.8.7. Generating the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 10.8.8. Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 11. Scanning: General 102 11.1. Setting Up a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2. Performing a Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3. Recording Scan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4. Replaying Scan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5. Presenting Scan Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6. Technical Data on Scanning Devices . . . . . . . . . . . . . . . . . . . . . 11.7. Notes on Scanning Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.8. Notes on GPS Units in Scanners . . . . . . . . . . . . . . . . . . . . . . . . 12. GSM Scanning 106 12.1. Scanning Methods and Capabilities . . . . . . . . . . . . . . . . . . . . . . 12.2. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1. Setup of RSSI Scan: General Settings . . . . . . . . . . . . . . 12.2.2. Setup of RSSI Scan: Sony Ericsson, SRU . . . . . . . . . . . 12.2.3. Setup of RSSI Scan: PCTel SeeGull . . . . . . . . . . . . . . . . 12.2.4. Presentation of RSSI Scanning . . . . . . . . . . . . . . . . . . . . 12.3. Spectrum Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13. WCDMA Scanning 102 102 103 103 103 104 104 105 106 107 107 107 108 109 110 111 13.1. Scanning Methods and Capabilities . . . . . . . . . . . . . . . . . . . . . . 111 vi Contents 13.2. Pilot Scanning (with SCH Scanning) . . . . . . . . . . . . . . . . . . . . . . 113 13.2.1. Setup of Pilot Scan: General . . . . . . . . . . . . . . . . . . . . . . 113 13.2.2. Setup of Pilot Scan: Sony Ericsson, SRU . . . . . . . . . . . . 113 13.2.3. Setup of Pilot Scan: PCTel. . . . . . . . . . . . . . . . . . . . . . . . 115 13.2.4. Setup of Pilot Scan: Rohde & Schwarz . . . . . . . . . . . . . . 117 13.2.5. Setup of Pilot Scan: Anritsu . . . . . . . . . . . . . . . . . . . . . . . 118 13.2.6. Presentation: General . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 13.2.7. Presentation: “CPICH Scan” Bar Charts . . . . . . . . . . . . . 120 13.2.8. Presentation: “CPICH Data” Status Windows . . . . . . . . . 120 13.2.9. Presentation: “CPICH Scan” Line Charts . . . . . . . . . . . . . 121 13.2.10. Presentation: Synch Channel Data Window . . . . . . . . . 124 13.2.11. Presentation: “Finger Info” Status Windows. . . . . . . . . . 125 13.2.12. Presentation: BCH Scanning . . . . . . . . . . . . . . . . . . . . . 125 13.2.13. Customizing the Presentation . . . . . . . . . . . . . . . . . . . . 125 13.2.13.1. Sorting of Scrambling Codes. . . . . . . . . . . . . . . . 125 13.2.13.2. Presenting Scrambling Codes from Multiple UARFCNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 13.3. SCH Timeslot Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 13.3.1. Setup of SCH Timeslot Scan . . . . . . . . . . . . . . . . . . . . . . 126 13.3.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 126 13.3.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 127 13.3.2. Presentation: SCH Timeslot Scan Bar Chart . . . . . . . . . . 127 13.4. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 13.4.1. Setup of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 13.4.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 128 13.4.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 129 13.4.2. Presentation: RSSI Scan Bar Chart . . . . . . . . . . . . . . . . . 129 13.5. Spectrum Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 13.5.1. Setup of Spectrum Analysis Scan . . . . . . . . . . . . . . . . . . 130 13.5.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 130 13.5.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 130 13.5.2. Presentation: Spectrum Analysis Bar Charts . . . . . . . . . . 131 13.6. Network Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 13.6.1. Setup of Network Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . 132 13.6.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 132 13.6.1.2. UARFCN Ranges (“Interval 1, 2, 3”) . . . . . . . . . . . 132 13.6.1.3. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 132 13.6.2. Presentation: Network Search Window . . . . . . . . . . . . . . 133 14. LTE Scanning 134 14.1. Scanning Methods and Capabilities . . . . . . . . . . . . . . . . . . . . . . 134 NT11-20502 vii TEMS Investigation 13.1 User’s Manual 14.2. LTE Signal Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2.1. Setup of LTE Signal Scan: General . . . . . . . . . . . . . . . . . 14.2.2. Setup of LTE Signal Scan: Andrew . . . . . . . . . . . . . . . . . 14.2.3. Setup of LTE Signal Scan: DRT . . . . . . . . . . . . . . . . . . . 14.2.4. Setup of LTE Signal Scan: PCTel . . . . . . . . . . . . . . . . . . 14.2.5. Setup of LTE Signal Scan: R&S TSMW . . . . . . . . . . . . . 14.2.6. Presentation of LTE Signal Scan . . . . . . . . . . . . . . . . . . . 14.2.7. Customizing the Presentation . . . . . . . . . . . . . . . . . . . . . 14.2.7.1. Sorting of Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.1. Setup of RSSI Scan: General . . . . . . . . . . . . . . . . . . . . . 14.3.2. Setup of RSSI Scan: DRT . . . . . . . . . . . . . . . . . . . . . . . . 14.3.3. Setup of RSSI Scan: PCTel . . . . . . . . . . . . . . . . . . . . . . . 14.3.4. Presentation of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . 14.4. Spectrum Scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4.1. Setup of Spectrum Scan: General . . . . . . . . . . . . . . . . . . 14.4.2. Setup of Spectrum Scan: Andrew . . . . . . . . . . . . . . . . . . 14.4.3. Setup of Spectrum Scan: DRT. . . . . . . . . . . . . . . . . . . . . 14.4.4. Setup of Spectrum Scan: PCTel . . . . . . . . . . . . . . . . . . . 14.4.5. Spectrum Scan Presentation . . . . . . . . . . . . . . . . . . . . . . 14.5. Enhanced Power Scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.1. Setup of Enhanced Power Scan: General . . . . . . . . . . . . 14.5.2. Setup of Enhanced Power Scan . . . . . . . . . . . . . . . . . . . 14.5.3. Presentation of Enhanced Power Scan . . . . . . . . . . . . . . 15. TD-SCDMA Scanning 146 15.1. Scanning Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2. General Scan Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3. Pilot Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.1. Setup of Pilot Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2. Presentation of Pilot Scan . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2.1. Sorting of Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.1. Setup of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.2. Presentation of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . 16. CDMA Scanning 135 135 136 136 139 139 141 141 141 141 141 142 142 142 142 142 143 143 143 143 143 144 144 145 146 146 147 147 148 148 149 149 149 150 16.1. Scanning Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 16.2. General Scan Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 viii Contents 16.3. Pilot Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 16.3.1. Setup of Pilot Scan: Andrew. . . . . . . . . . . . . . . . . . . . . . . 151 16.3.2. Setup of Pilot Scan: PCTel. . . . . . . . . . . . . . . . . . . . . . . . 152 16.3.3. Presentation: “PN Scan” Bar Charts . . . . . . . . . . . . . . . . 155 16.3.4. Presentation: Strongest Scanned PN Bar Chart . . . . . . . 155 16.3.5. Customizing the Presentation . . . . . . . . . . . . . . . . . . . . . 156 16.3.5.1. Sorting of Pilots . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 16.4. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 16.4.1. Setup of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 16.4.2. Presentation: RSSI Scan Bar Chart . . . . . . . . . . . . . . . . . 157 16.5. Narrowband Interference Scanning. . . . . . . . . . . . . . . . . . . . . . . 158 16.5.1. Setup of Narrowband Interference Scan . . . . . . . . . . . . . 158 16.5.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 158 16.5.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 158 16.5.1.3. Interference Offset. . . . . . . . . . . . . . . . . . . . . . . . . 158 16.5.2. Presentation: Narrowband Interference Scan Bar Chart . 158 16.6. Spectrum Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 16.6.1. Setup of Spectrum Analysis Scan . . . . . . . . . . . . . . . . . . 159 16.6.1.1. General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 159 16.6.1.2. Context Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 160 16.6.2. Presentation of Spectrum Analysis Scan . . . . . . . . . . . . . 160 17. WiMAX Scanning 161 17.1. Scanning Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 17.2. General Scan Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 17.3. Preamble Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 17.3.1. Setup of Preamble Scan . . . . . . . . . . . . . . . . . . . . . . . . . 162 17.4. RSSI Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 17.4.1. Setup of RSSI Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 17.5. Spectrum Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 17.5.1. Setup of Spectrum Analysis Scan . . . . . . . . . . . . . . . . . . 165 17.6. Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 18. Service Control 167 18.1. Introduction to Service Control . . . . . . . . . . . . . . . . . . . . . . . . . . 167 18.2. Service Control vs. Command Sequences . . . . . . . . . . . . . . . . . 168 18.3. Capabilities of Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 18.4. Supported Services by Cellular Technology . . . . . . . . . . . . . . . . 170 NT11-20502 ix TEMS Investigation 13.1 User’s Manual 18.5. The Service Control Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . 18.6. Basics of Creating Scripts (with Voice) . . . . . . . . . . . . . . . . . . . . 18.7. Setting Up a Network Connection. . . . . . . . . . . . . . . . . . . . . . . . 18.8. Setting Up a Data Service Activity . . . . . . . . . . . . . . . . . . . . . . . 18.9. Standalone PS Attach and Detach . . . . . . . . . . . . . . . . . . . . . . . 18.10. Snippets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.11. Workflow Control Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.11.1. Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.11.2. If–Else Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.11.3. While Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.11.4. Parallel Activities: Controlling Multiple Devices . . . . . . . 18.11.5. Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12. Tips and Tricks for Creating Script Workflows . . . . . . . . . . . . . 18.13. Activity Properties That Control Execution . . . . . . . . . . . . . . . . 18.14. UE Control Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.15. Validating Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.16. Running Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.16.1. General Aspects of Script Execution . . . . . . . . . . . . . . . 18.16.2. Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.16.2.1. Windows 7/Windows Vista and IPv6. . . . . . . . . . 18.16.3. Running Scripts from the Service Control Monitor . . . . . 18.16.4. Running Scripts from the Service Control Designer . . . 18.16.5. Suppressing Parts of a Script . . . . . . . . . . . . . . . . . . . . 18.16.6. Presentation of Data Service Testing . . . . . . . . . . . . . . 18.17. Activities (Reference Section). . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1. Control Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.1. Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.2. AT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.3. Band Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.4. Deactivate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.5. Filemark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.6. Radio Access Technology Lock . . . . . . . . . . . . . 18.17.1.7. Start Recording . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.8. Stop Recording . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.1.9. Notes on Script-controlled Logfile Recording . . . 18.17.2. Control Flow Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.2.1. If–Else . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.2.2. While . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.2.3. Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.2.4. Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.17.2.5. Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x 170 172 175 176 178 179 180 180 181 182 184 188 189 189 189 190 190 190 191 191 191 192 192 194 194 194 194 194 194 194 194 195 195 195 195 195 195 196 197 197 197 Contents 18.17.3. IP Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 18.17.3.1. Network Connect. . . . . . . . . . . . . . . . . . . . . . . . . 198 18.17.3.2. Network Disconnect . . . . . . . . . . . . . . . . . . . . . . 201 18.17.3.3. PS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 18.17.3.4. PS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 18.17.3.5. SIP Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 18.17.3.6. SIP Unregister . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 18.17.3.7. Start IP Sniffing . . . . . . . . . . . . . . . . . . . . . . . . . . 202 18.17.3.8. Stop IP Sniffing . . . . . . . . . . . . . . . . . . . . . . . . . . 203 18.17.3.9. FTP Download. . . . . . . . . . . . . . . . . . . . . . . . . . . 203 18.17.3.10. FTP Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 18.17.3.11. HTTP Get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 18.17.3.12. WAP Get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 18.17.3.13. Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 18.17.3.14. UDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 18.17.3.15. Network Bandwidth (Iperf Testing) . . . . . . . . . . 210 18.17.3.16. Predefined Snippets for IP . . . . . . . . . . . . . . . . 212 18.17.4. Messaging Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 18.17.4.1. E-mail Send. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 18.17.4.2. E-mail Receive . . . . . . . . . . . . . . . . . . . . . . . . . . 213 18.17.4.3. MMS Send. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 18.17.4.4. MMS Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 18.17.4.5. SMS Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 18.17.4.6. SMS Receive. . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 18.17.4.7. Predefined Snippets for Messaging . . . . . . . . . . 216 18.17.5. Video Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 18.17.5.1. Video Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 18.17.5.2. Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 18.17.5.3. Hang Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 18.17.5.4. Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 18.17.5.5. WAP Streaming. . . . . . . . . . . . . . . . . . . . . . . . . . 218 18.17.5.6. Predefined Snippets for Video. . . . . . . . . . . . . . . 219 18.17.6. Voice Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 18.17.6.1. Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 18.17.6.2. Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 18.17.6.3. Hang Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 18.17.6.4. PESQ Measurement . . . . . . . . . . . . . . . . . . . . . . 219 18.17.6.5. VoIP Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 18.17.6.6. VoIP Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 18.17.6.7. VoIP Hang Up . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 18.17.6.8. VoIP Voice Quality . . . . . . . . . . . . . . . . . . . . . . . 221 18.17.6.9. How to Set Up VoIP Testing . . . . . . . . . . . . . . . . 221 NT11-20502 xi TEMS Investigation 13.1 User’s Manual 18.17.6.10. Predefined Snippets for Voice. . . . . . . . . . . . . . 18.18. General Activity Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.18.1. Activity Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.18.2. Failure Handling Section . . . . . . . . . . . . . . . . . . . . . . . . 18.18.3. Termination Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.19. Configuration Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.19.1. Descriptions of Configuration Sets. . . . . . . . . . . . . . . . . 18.19.2. Managing Configuration Sets. . . . . . . . . . . . . . . . . . . . . 18.19.2.1. Exporting Configuration Sets . . . . . . . . . . . . . . . 18.19.2.2. Importing Configuration Sets. . . . . . . . . . . . . . . . 18.19.2.3. Deleting Configuration Sets . . . . . . . . . . . . . . . . 18.20. Saving and Loading Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.20.1. Tutorial on Porting Scripts between PCs . . . . . . . . . . . . 18.20.2. Saving Workflow as Image . . . . . . . . . . . . . . . . . . . . . . 18.21. Further Functionality in the Service Control Designer Window. 18.21.1. Activity Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.21.2. Context Menu in Workflow Pane . . . . . . . . . . . . . . . . . . 18.21.3. Zooming the Workflow Pane . . . . . . . . . . . . . . . . . . . . . 19. Device Properties 229 19.1. Overview of Properties by Device. . . . . . . . . . . . . . . . . . . . . . . . 19.2. Properties of Sony Ericsson Phones and Samsung Galaxy S 4G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.1. Extended Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2. Common Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.1. CAS Access Class . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.2. CAS Lock on PLMN . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.3. CAS Speech Codec . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.4. GSM Adjacent Scan . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.5. GSM Barred Cells . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.6. GSM Cell Selection . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.7. GSM EDGE Capability . . . . . . . . . . . . . . . . . . . . . 19.2.2.8. GSM Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.9. GSM Tx Power . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.10. Layer 3 Messages. . . . . . . . . . . . . . . . . . . . . . . . 19.2.2.11. WCDMA Barred Cells . . . . . . . . . . . . . . . . . . . . . 19.2.2.12. WCDMA BLER Target . . . . . . . . . . . . . . . . . . . . 19.2.2.13. WCDMA Cell Selection . . . . . . . . . . . . . . . . . . . . 19.2.2.14. WCDMA RRC Radio Capability . . . . . . . . . . . . . xii 222 222 222 223 223 224 224 224 224 225 225 226 226 227 227 227 228 228 229 231 231 231 232 232 232 233 234 234 235 235 236 236 236 237 237 238 Contents 19.3. Properties of Nokia Phones (NTM3) . . . . . . . . . . . . . . . . . . . . . . 239 19.3.1. Channel Lock Control (GSM) . . . . . . . . . . . . . . . . . . . . . . 239 19.3.2. GSM Cell Barring Control. . . . . . . . . . . . . . . . . . . . . . . . . 239 19.3.3. Sector Lock Control (WCDMA) . . . . . . . . . . . . . . . . . . . . 239 19.4. Properties of Qualcomm Chipset Based Devices . . . . . . . . . . . . 240 19.5. Properties of Samsung LTE Modems . . . . . . . . . . . . . . . . . . . . . 240 19.6. Properties of GPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 20. Events 241 20.1. Presentation of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 20.2. Predefined and User-defined Events . . . . . . . . . . . . . . . . . . . . . 241 20.3. Setting Up a User-defined Event. . . . . . . . . . . . . . . . . . . . . . . . . 241 20.3.1. Adding a Layer 3 Message to the Event Expression . . . . 242 20.3.2. Adding an Information Element Criterion to the Event Expression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 20.3.3. Adding an Event to the Event Expression . . . . . . . . . . . . 243 20.3.4. Adding an Operator/Delimiter to the Event Expression . . 243 20.4. Editing User-defined Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 20.5. Deleting User-defined Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 20.6. Example of Event Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 20.7. Audio Indications for Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 20.7.1. Adding Audio Indications . . . . . . . . . . . . . . . . . . . . . . . . . 246 20.7.2. Editing Audio Indications . . . . . . . . . . . . . . . . . . . . . . . . . 247 20.7.3. Activating Audio Indications . . . . . . . . . . . . . . . . . . . . . . . 247 20.7.4. Deactivating Audio Indications . . . . . . . . . . . . . . . . . . . . . 247 20.7.5. Muting All Audio Indications . . . . . . . . . . . . . . . . . . . . . . . 247 20.7.6. Saving and Loading Audio Indications . . . . . . . . . . . . . . . 248 20.7.7. Deleting Audio Indications . . . . . . . . . . . . . . . . . . . . . . . . 248 21. Presentation: Basics 249 21.1. Presented Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 21.2. Types of Presentation Window . . . . . . . . . . . . . . . . . . . . . . . . . . 249 21.3. Device Channels: MS/DC/PS . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 21.4. Window Updating and Synchronization. . . . . . . . . . . . . . . . . . . . 250 21.5. Color Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 21.6. Other Window Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 NT11-20502 xiii TEMS Investigation 13.1 User’s Manual 21.7. Export/Import of Presentation Windows . . . . . . . . . . . . . . . . . . . 251 21.7.1. Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 21.7.2. Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 22. Status Windows 253 22.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2. Setting Up Status Window Contents. . . . . . . . . . . . . . . . . . . . . . 22.3. Changing Status Window Properties . . . . . . . . . . . . . . . . . . . . . 22.4. Repeating Columns in Multiple Groups . . . . . . . . . . . . . . . . . . . 22.5. Changing the Status Window Font Size . . . . . . . . . . . . . . . . . . . 22.6. Non-standard Status Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6.1. TD-SCDMA Physical Channel Monitor . . . . . . . . . . . . . . 22.6.1.1. Window Properties . . . . . . . . . . . . . . . . . . . . . . . . 22.6.2. CDMA Finger Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23. Event Counter Windows 262 23.1. Window Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2. Copying Window Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3. Resetting Event Counter Windows . . . . . . . . . . . . . . . . . . . . . . 23.4. Changing Event Counter Window Contents and Properties . . . . 23.4.1. General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4.2. Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24. Message Windows 262 262 262 263 263 263 264 24.1. Changing Message Window Contents and Properties . . . . . . . . 24.1.1. General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1.2. Messages Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1.3. Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1.4. Columns Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.2. Plain-text Message Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.3. Presentation of Discarded Messages . . . . . . . . . . . . . . . . . . . . . 24.4. Message Window Catch-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.5. Message Window Synchronization . . . . . . . . . . . . . . . . . . . . . . . 24.6. Freezing a Message Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.7. Window-specific Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.7.1. Mode Reports Window. . . . . . . . . . . . . . . . . . . . . . . . . . . xiv 253 253 257 259 259 260 260 261 261 264 264 264 265 265 265 266 266 266 267 267 267 Contents 25. Video Streaming and the Video Monitor 268 25.1. How to Test Video Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 25.2. The Video Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 25.2.1. Properties of the Video Monitor . . . . . . . . . . . . . . . . . . . . 269 25.3. Evaluating Video Streaming Performance . . . . . . . . . . . . . . . . . 270 25.4. Troubleshooting Video Streaming . . . . . . . . . . . . . . . . . . . . . . . . 270 26. The GPS Window 271 26.1. Changing GPS Window Properties . . . . . . . . . . . . . . . . . . . . . . . 271 27. Line Charts 273 27.1. Organization of the Line Chart Window. . . . . . . . . . . . . . . . . . . . 273 27.2. Contents of the Line Chart Panes . . . . . . . . . . . . . . . . . . . . . . . . 274 27.3. Time Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 27.4. Changing Line Chart Contents and Properties . . . . . . . . . . . . . . 276 27.4.1. Adding Charts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 27.4.2. Editing General Properties of a Chart . . . . . . . . . . . . . . . 276 27.4.3. Editing the Contents of a Chart . . . . . . . . . . . . . . . . . . . . 276 27.4.4. Presenting Data from a Different Device . . . . . . . . . . . . . 280 27.4.5. Deleting a Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 27.5. Exporting the Line Chart Window . . . . . . . . . . . . . . . . . . . . . . . . 280 28. Bar Charts 281 28.1. Organization of the Bar Chart Window . . . . . . . . . . . . . . . . . . . . 282 28.2. Contents of the Bar Chart Panes . . . . . . . . . . . . . . . . . . . . . . . . 283 28.3. Setting Up General Bar Chart Properties . . . . . . . . . . . . . . . . . . 284 28.3.1. Adding Charts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 28.3.2. Deleting a Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 28.3.3. Editing General Properties of a Chart . . . . . . . . . . . . . . . 285 28.4. Setting Up Bar Chart Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 285 28.4.1. Presentation Mode, Data, Colors . . . . . . . . . . . . . . . . . . . 286 28.4.1.1. Single IE Presentation Mode. . . . . . . . . . . . . . . . . 287 28.4.1.2. Multiple IE Components Presentation Mode . . . . . 288 28.4.1.3. Parallel Coordinates/Stacked Bar Chart Presentation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 28.4.2. Interval and Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 NT11-20502 xv TEMS Investigation 13.1 User’s Manual 28.4.3. Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.4.4. Presenting Data from a Different Device . . . . . . . . . . . . . 28.5. Examples of Bar Chart Presentations. . . . . . . . . . . . . . . . . . . . . 28.6. Exporting the Bar Chart Window. . . . . . . . . . . . . . . . . . . . . . . . . 29. Map Windows 300 29.1. Highlights of This Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.2. Map Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.3. Constructing a GeoSet from Map Files. . . . . . . . . . . . . . . . . . . . 29.4. Positioning Bitmap and TIF Maps . . . . . . . . . . . . . . . . . . . . . . . . 29.4.1. Specifying the Map Position. . . . . . . . . . . . . . . . . . . . . . . 29.4.2. Specifying the Map Scale . . . . . . . . . . . . . . . . . . . . . . . . 29.4.3. Setting the Map’s North Direction . . . . . . . . . . . . . . . . . . 29.5. Presenting Data: Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.1. Themes and Theme Types . . . . . . . . . . . . . . . . . . . . . . . 29.5.2. Presentation Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.3. Presenting Information Elements . . . . . . . . . . . . . . . . . . . 29.5.3.1. Notes on Route Plotting and Updating . . . . . . . . . 29.5.4. Presenting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.5. Presenting Cell Information . . . . . . . . . . . . . . . . . . . . . . . 29.5.5.1. The Cell Theme. . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.5.2. The Cell Line Theme. . . . . . . . . . . . . . . . . . . . . . . 29.5.5.3. The Cell Color Theme . . . . . . . . . . . . . . . . . . . . . . 29.5.5.4. The Cell ARFCN Theme (GSM) . . . . . . . . . . . . . . 29.5.6. Presenting Pinpointing . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.7. Editing Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.8. Visibility of Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.9. Reordering Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.5.10. Deleting Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.6. The Right-hand Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.6.1. Information on Single Theme Markers (Info Tab) . . . . . . 29.6.2. Theme Statistics (Info and Graph Tabs) . . . . . . . . . . . . . 29.6.3. Theme Legend (Legend Tab) . . . . . . . . . . . . . . . . . . . . . 29.7. Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.7.1. Adding Presentation Layers. . . . . . . . . . . . . . . . . . . . . . . 29.7.2. Layer Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.8. Map Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.8.1. The Scale Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.8.2. Previous View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.8.3. View Entire Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi 296 296 297 299 300 300 301 303 303 303 304 304 304 305 306 308 309 310 311 314 317 319 321 321 321 322 322 322 322 324 325 325 325 326 327 327 327 328 Contents 29.8.4. Setting the Map Projection . . . . . . . . . . . . . . . . . . . . . . . . 328 29.9. The Map Window Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 29.10. GeoSet Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 29.10.1. Layer Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 29.10.2. Projections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 30. The General Window 331 31. Key Performance Indicators – KPIs (UMTS) 332 31.1. Purpose of KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 31.1.1. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 31.1.2. Retainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 31.1.3. Integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 31.2. Obtaining KPIs with TEMS Products. . . . . . . . . . . . . . . . . . . . . . 333 31.2.1. General Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 31.2.2. Points to Bear in Mind . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 31.2.3. “Events of KPI Type” . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 32. Speech Quality Index – SQI 335 32.1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 32.1.1. SQI for UMTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 32.1.2. SQI for CDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 32.2. Input to the SQI-MOS Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . 336 32.2.1. UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 32.2.2. CDMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 32.3. SQI-MOS Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 32.3.1. Narrowband vs. Wideband SQI-MOS (UMTS). . . . . . . . . 338 32.3.2. SQI-MOS vs. Old SQI (UMTS). . . . . . . . . . . . . . . . . . . . . 338 32.4. Alignment of SQI-MOS and PESQ . . . . . . . . . . . . . . . . . . . . . . . 338 32.4.1. Notes on PESQ for Wideband (UMTS) . . . . . . . . . . . . . . 339 32.5. Comparison with Other Radio Parameters . . . . . . . . . . . . . . . . . 340 33. Audio Quality Measurement (AQM): General 341 33.1. Measurement Setups in TEMS Investigation . . . . . . . . . . . . . . . 341 NT11-20502 xvii TEMS Investigation 13.1 User’s Manual 34. AQM with Call Generator/MRU 342 34.1. Mobile-to-fixed Audio Quality Measurement with Call Generator. . 342 34.2. Mobile-to-mobile Audio Quality Measurement with MRU . . . . . . 344 34.3. Obtaining AQM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 34.3.1. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 34.3.2. Practical Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 345 34.3.3. Recording AQM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 34.4. Merging Uplink AQM Data into Logfiles . . . . . . . . . . . . . . . . . . . 346 34.5. Presentation of AQM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 34.5.1. Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 34.5.2. PESQ Key Performance Indicator . . . . . . . . . . . . . . . . . . 347 35. AQM with Audio Capturing Unit (ACU) 348 35.1. Obtaining AQM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 35.1.1. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 35.1.2. Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 35.1.3. Recording AQM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 35.1.3.1. Recommended Structure of AQM Scripts . . . . . . . 350 35.2. Presentation of AQM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 35.2.1. Information Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 35.2.2. PESQ Key Performance Indicator . . . . . . . . . . . . . . . . . . 352 35.3. Notes on PESQ Scores Obtained with Individual Phone Models. . 352 36. AQM for VoIP 353 36.1. Obtaining AQM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 36.2. Presentation of AQM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 37. Video Telephony Quality Index – VTQI 355 37.1. General Properties of VTQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37.2. What VTQI Is Based On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37.3. What VTQI Does Not Consider. . . . . . . . . . . . . . . . . . . . . . . . . . 37.4. Update Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38. Video Streaming Quality Index – VSQI 355 355 356 356 357 38.1. General Properties of VSQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 xviii Contents 38.2. What VSQI Is Based On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 38.3. What VSQI Does Not Consider . . . . . . . . . . . . . . . . . . . . . . . . . . 358 38.4. Static and Dynamic VSQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 38.4.1. Static VSQI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 38.4.2. Dynamic (Realtime) VSQI . . . . . . . . . . . . . . . . . . . . . . . . 359 39. Mobile TV Quality Index – MTQI 361 40. C/I Measurement (GSM) 362 40.1. Why Measure C/I?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 40.2. Requirements on a Robust C/I Measure . . . . . . . . . . . . . . . . . . . 362 40.3. Details on C/I Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 40.4. Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 40.5. An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 41. Uplink (MTR) Data (GSM) 365 41.1. Uplink Data: MTR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 41.1.1. Supported MTR File Versions . . . . . . . . . . . . . . . . . . . . . 365 41.2. Utilizing Data from Uplink Files . . . . . . . . . . . . . . . . . . . . . . . . . . 366 41.2.1. Uplink Data on Handovers . . . . . . . . . . . . . . . . . . . . . . . . 366 41.3. Merging Uplink Files with TEMS Logfiles . . . . . . . . . . . . . . . . . . 366 41.4. Presentation of Uplink Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 42. GSM Channel Verification 368 42.1. The GSM Channel Verification Window . . . . . . . . . . . . . . . . . . . 368 42.2. Adding a Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 42.3. Editing and Removing Test Cases . . . . . . . . . . . . . . . . . . . . . . . 370 42.4. Automatic vs. Manual Verification . . . . . . . . . . . . . . . . . . . . . . . . 370 42.5. Activating Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 42.6. Running the Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 42.6.1. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 42.6.2. Manual Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 42.6.3. Automatic Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 42.6.4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 42.7. Stopping the Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 NT11-20502 xix TEMS Investigation 13.1 User’s Manual 42.8. Resetting a Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.9. Summary of Test Case Status Values . . . . . . . . . . . . . . . . . . . . 42.10. Creating Test Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.11. Saving and Opening Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.12. Notes on Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.13. Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A. Keyboard Shortcuts 375 375 376 377 377 377 379 A.1. General Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2. Drive Testing Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3. Replay Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4. Shortcuts for Active Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 379 380 380 Appendix B. File Types in TEMS Investigation 382 Index 383 xx Chapter 1. Introduction 1. Introduction Thank you for choosing TEMS Investigation – the industry-leading tool for troubleshooting, verification, optimization, and maintenance of wireless networks. Offering data collection, real-time analysis, and post-processing all in one, TEMS Investigation is a complete solution for all of a network operator’s daily network optimization tasks. This complete solution eliminates the need for multiple tools, reducing costs and saving time and effort for operations staff. To get the most out of TEMS Investigation, please take the time to read this user manual in order to gain an in-depth understanding of the product features. Note: Please note that the TEMS Investigation product exists in various editions, all of which are covered by the product documentation but are not differentiated there. This means that descriptions of functionality and external device compatibility are not necessarily applicable in every single respect to the TEMS Investigation edition you have purchased. Any restrictions that apply to your edition are indicated in the Release Note included in the delivery. NT11-20502 1 TEMS Investigation 13.1 User’s Manual 1.1. Fundamentals of TEMS Investigation 13.1 TEMS Investigation 13.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. 0/EV-DO Rev. A/EV-DO Rev. B, plus basic iDEN support • 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. TEMS Investigation is primarily a tool for data collection and real-time analysis. It interfaces with phones, data cards, scanners, and other measurement devices; it collects data and records it in logfiles. The application also boasts a vast array of windows for presentation of logfile data. Still more powerful post-processing facilities are provided by the product TEMS Discovery. 1.1.1. Package Options – Licensing TEMS Investigation can be purchased with or without data collection capability (“Base Software Package” and “Replay Package” respectively). Customers who dispense with TEMS Investigation data collection are still able to use the non-realtime functions of the application (single-logfile replay, logfile reports, logfile export). Supported cellular technologies can be freely selected and combined, except that WCDMA always comes with GSM support included. The Base Software Package provides the ability to collect data with Sony Ericsson phones in UMTS networks and with Qualcomm chipset based terminals in CDMA networks. Other phones are licensed separately for each supplier or, in the case of Qualcomm, separately for chipsets with different capabilities. 2 Chapter 1. Introduction The Base Software Package permits data collection with one phone at a time. A separate license option is available for collecting data with multiple phones concurrently. Audio quality measurement (AQM), including PESQ, is likewise sold as a separate option. This option includes all required hardware as well as the ability to connect that hardware to TEMS Investigation. Audio quality measurement is supported for GSM, WCDMA, and CDMA. TEMS Discovery Standard can optionally be bundled with TEMS Investigation whenever the latter is purchased with data collection capability. TEMS Discovery is thus available to all customers using TEMS Investigation for data collection. 1.1.2. Connectable Equipment TEMS Investigation 13.1 supports a wide variety of user terminals, including ones from Sony Ericsson, Datang, Huawei, LG, Nokia, Novatel, Option, Pantech, Qualcomm, Samsung, Sequans, Sierra Wireless, and ZTE. They allow comprehensive monitoring of UMTS, LTE, TD-SCDMA, and CDMA networks and of GSM–UTRAN and GSM–TD-SCDMA as well as cdmaOne– cdma2000–EV-DO interaction. A variety of devices are supported for GSM, WCDMA, LTE, TD-SCDMA, CDMA, and WiMAX scanning. GPS units can be connected for geographical positioning. Manual positioning (“pinpointing”) is supported, with indoor measurements in mind. See the Getting Started Manual, section 10.1 for further details on the range of connectable equipment. The number of external devices that can be connected simultaneously in the application is dependent on many factors, such as whether a data service is being run. See the Release Note for further information. 1.2. What’s New in TEMS Investigation 13.1 1.2.1. Alternative Mobile-to-mobile AQM Solution This is a cost-efficient solution for mobile-to-mobile audio quality measurement. Two or four mobile devices, which call each other in pairs, are connected to an Audio Capturing Unit (ACU) which relays the audio to the PC. The PESQ calculation is done by the PC itself, so that no separate NT11-20502 3 TEMS Investigation 13.1 User’s Manual processing power is required in the Audio Capturing Unit. Since the voice calls are made between the mobiles, there is also no Call Generator or similar component in this AQM configuration. The activities of the devices are completely controlled from TEMS Investigation by means of a Service Control script, just as in the existing TEMS Investigation AQM setup. The mobile-to-mobile AQM solution is in principle RAT-independent. In TEMS Investigation 13.1 it has been implemented for the following phones: Sony Ericsson Xperia arc, Sony Ericsson W995, Nokia C7-00 (GSM/WCDMA); Huawei C8600 (CDMA). 1.2.2. 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. A number of events – some new, some expanded in scope – report on the resulting interaction between the terminal and networks. Event categories: • Call setup events • Inter-RAT events • Attach events 1.2.3. Extended Set of LTE RACH Information Elements A collection of new information elements deals with the RACH procedure in LTE: RACH Type, RACH Reason, RACH Result, Preamble Step Size, RACH Preamble Responses with PUSCH Resource, MME Group Id, and MME Code. 1.2.4. Improved Handling of Qualcomm-based LTE Devices Network connect can now be performed for Qualcomm chipset-based LTE devices from within TEMS Investigation, that is, without using an external connection manager. TEMS Investigation now also permits connection of multiple Qualcommbased LTE devices. 4 Chapter 1. Introduction 1.2.5. CDMA/EV-DO Rev. B Measurement and Analysis Rev. B of the EV-DO (TIA-856) standard introduces multicarrier data transfer in EV-DO. TEMS Investigation 13.1 allows connection of devices built on a range of Qualcomm CDMA/EV-DO Rev. B chipsets. Presented information elements subdivide into three categories: • Basic radio parameters • Multicarrier serving channel information • Forward link multicarrier RLP throughput 1.2.6. New Connectable User Terminals • 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, I) – GSM/EDGE 850/900/1800/1900 – HSUPA Category 6 (5.76 Mbit/s), HSDPA Category 14 (21 Mbit/s) – Advanced control functionality Sierra Wireless AirCard 319U – Dual-Carrier HSPA+ USB modem from Sierra Wireless – WCDMA/HSPA+ 850/900/1900/2100 (Bands V, VIII, II, I) – GSM/EDGE 850/900/1800/1900 – HSUPA Category 6 (5.76 Mbit/s), HSDPA Category 24 (42 Mbit/s) Other new LTE devices: – Huawei E392 – Sierra Wireless AirCard 313U Other new UMTS devices: – Huawei E367 – Huawei E372 NT11-20502 5 TEMS Investigation 13.1 User’s Manual • New CDMA devices: – Huawei C8600 – Huawei M860 – LG KV600 – LG KV755 – ZTE AC8710 1.2.7. WCDMA Scanning with Rohde & Schwarz WCDMA pilot (Top N) scanning can be undertaken with Rohde & Schwarz TSMW scanners. There are no restrictions on supported frequency bands (30 MHz to 6 GHz). 1.2.8. CDMA Scanning with PCTel SeeGull MX Support has been added for CDMA scanning (PN scan, RSSI scan) with PCTel SeeGull MX. 1.2.9. New Connectable Scanners • PCTel SeeGull MX WCDMA 850/1900/2100 AWS + GSM 850/1900 + CDMA/EV-DO 850/1900/2100 AWS • Anritsu ML8780A WCDMA 2100/1500 1.3. What Was New in TEMS Investigation 13.0 1.3.1. TD-LTE Support The LTE standard allows both frequency division duplex (FDD) and time division duplex (TDD) operation. Up until the 13.0 version, LTE support in TEMS Investigation was restricted to FDD; however, TEMS Investigation 13.0 introduced scanning support also for the TDD mode, known as TD-LTE. Using a Rohde & Schwarz TSMW Universal Radio Network Analyzer, it is possible to do Top-N LTE signal scanning in both TDD and FDD mode. Any LTE frequency band can be scanned. The data set obtained is similar to FDD and includes RSRP, RSRQ, and SCH CINR. 6 Chapter 1. Introduction 1.3.2. Data Service Performance Verification with Generic Device TEMS Investigation 13.0 expanded the concept of data service testing, taking it to a whole new level of genericity. With the 13.0 version, 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, iPhone or BlackBerry units, or a wide variety of network cards, USB modems, embedded modules, etc. This feature can be used to verify application layer performance for arbitrary devices, as will be desirable prior to launching them in the network. Any IPbased activity in the Service Control Designer, as well as video streaming, can be run on such a device, and all IP information elements will then be populated. Please note that lower-layer data (RF, Layer 2, Layer 3) is not obtained with this kind of testing. 1.3.3. Selection of Preferred Workspace at Startup When you start TEMS Investigation 13.0, you are invited to select what workspace to use: one recently used, some other existing workspace, or a new one that is empty. See section 3.2. 1.3.4. 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. For example, such a file may contain all details of how to perform an LTE Reference Signal scan with a PCTel MX scanner, or all the parameters needed to access and interact with a particular FTP server. The TEMS Settings Manager boosts usability by enabling easy distribution of configuration data among users and among instances of TEMS Investigation. The utility can also be seen as a complement to the script saving function in the Service Control Designer, which creates files specifying the activities to perform during testing. See section 18.19.2. NT11-20502 7 TEMS Investigation 13.1 User’s Manual 1.3.5. New LTE Information Elements With LG devices, a range of additional LTE information elements are obtained, including PDSCH Transmission Distribution, PBCH BLER, and PUSCH BLER. Furthermore, using TEMS Investigation 13.0, many LTE elements previously available only with LG devices are also obtainable with Qualcomm devices. 1.3.6. New Connectable Equipment 1.3.6.1. • • • UMTS Terminals 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) – HSDPA Category 8 (7.2 Mbit/s), HSUPA Category 5 (2.0 Mbit/s) Nokia C7-00 – WCDMA/HSPA 850/900/1700/1900/2100 MHz – GSM/GPRS/EDGE 850/900/1800/1900 MHz – HSDPA Category 9 (10.2 Mbit/s), HSUPA Category 5 (2.0 Mbit/s) HTC Imagio 1.3.6.2. LTE Scanner: Rohde & Schwarz TSMW The R&S TSMW Universal Radio Network Analyzer enables TD-LTE measurements in TEMS Investigation 13.0. Compare section 1.3.1. 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, and support for these is planned for inclusion in future releases of TEMS Investigation. Such technology expansions will then be possible to do remotely by means of a scanner software upgrade.1 8 Chapter 1. Introduction 1.3.7. 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. Unlike the Telnet protocol, which sends logins and passwords in plain text, SSH2 uses cryptography to authenticate the remote computer and therefore renders the Iperf server less vulnerable to hacker attacks. SSH2 requires a separate license option and installation package, since it is subject to export restrictions due to its use of strong encryption. See section 18.17.3.15. 1.3.8. Support for 64-bit Windows 7 TEMS Investigation 13.0 can be run under 64-bit Windows 7. 1.3.9. Performance Improvements For any given device configuration and test setup, TEMS Investigation 13.0 generates lower CPU load than previous versions. Other improvements include better memory management and reduced start-up time. 1.3.10. Additional New Features • Internal GPS of PCTel MX available as data source in TEMS Investigation. • UMTS network connect can be done from within TEMS Investigation with Samsung GT-B3730, GT-B3740 LTE/UMTS dual-technology devices. 1.3.11. • New Features in TEMS Investigation 13.0.1 Improved VoIP testing: – PJSIP VoIP client added as alternative to CounterPath. – Extensive set of VoIP jitter buffer metrics obtained as information elements: RFC 1889 Jitter, Decoding Errors, Average/Min/Max 1. Update to this text: WCDMA scanning is supported with R&S TSMW in TEMS Investigation 13.1; see section 1.2.7. NT11-20502 9 TEMS Investigation 13.1 User’s Manual Playout Delay, Lost Packets, Overruns, Underruns, Size Increase (frequency of jitter buffer size increases). – Possible to select AMR-NB or AMR-WB as VoIP speech codec. – Possible to select AMR speech codec rate. – Events generated enabling computation of the following VoIP KPIs: MTSI Registration Failure Ratio (%), MTSI Registration Time (s), MTSI Session Setup Failure Ratio (%), MTSI Session Setup Time (s), MTSI Session Completion Failure Ratio (%). The KPI computation itself is done in TEMS Discovery or TEMS Automatic. • TD-LTE information elements introduced: Ack Reporting Mode, UL/DL Configuration, UL/DL Configuration Type, nCCE Average/Min/Max, Np and Np+1 Distribution, Position of Minimum k Distribution, Special Subframe Configuration. • More LTE information elements obtainable with Qualcomm chipset based devices: MAC PDU Handover Interruption Time, PBCH BLER, PCFICH CFI Information, PDSCH Transmission Distribution elements, PUSCH Phy Throughput. • HSUPA: New information element “HS UL E-DCH TTI (ms)” indicating TTI length (2 ms or 10 ms). • Timestamps given with 1 ms resolution in message windows and logfile text format export. • Support added for LG FM300. • Support added for LG MN270. • Support added for Qualcomm TD9200 TDD. • Support added for Samsung SCH-I510. • 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. • Support added for ZTE AL611. • Support added for ZTE AL621. • Support added for ZTE MF682. 10 Chapter 1. Introduction 1.4. What’s in This Manual (and What’s Not) This book describes the user interface of TEMS Investigation 13.1. It concentrates on how to use that application once it has been installed and all external devices are connected and ready for use. The manual gives a comprehensive account of all functions in the application. The Information Elements and Events volume provides full details on all IEs and events found in the application. It also lists and describes all preconfigured presentation windows. The Technical Reference volume contains file and report format descriptions, and other information of a technical nature. Besides the above reference manuals, a Getting Started Manual is provided which covers all preliminaries; 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, operate, and control external equipment is described in the present document. External Equipment The basics on external devices are covered in the Getting Started Manual, chapter 10. In the remainder of this book, external devices are discussed further whenever certain capabilities are required in order for a function in TEMS Investigation to be supported. The manual does not describe the full range of functions and capabilities of the connectable phones. For exhaustive information, please refer to the documentation accompanying the phones. The same applies to all other third-party products mentioned in the manuals. Data Service Testing Configuration of the PC and external devices is covered in the Getting Started Manual. The present document describes how to conduct data sessions from within TEMS Investigation using Service Control scripts (see chapter 18). NT11-20502 11 TEMS Investigation 13.1 User’s Manual Equipment Cases The TEMS equipment cases, designed to accommodate phones and other equipment during drive tests, are not covered here but have their own manuals. These, however, sometimes refer to TEMS Investigation documentation. Release Note Some technical issues not addressed in this manual are dealt with in the file ReleaseNote.pdf which is found in the TEMS Investigation installation folder. FAQ Many questions regarding TEMS Investigation are answered in the FAQ sections found on the Web at www.ascom.com/en/index/support/supporttems/technical-support/tems-investigation.htm. 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, please contact technical support. Contact information is given on the Web at www.ascom.com/networktesting under the link “TEMS Support”. TEMS Bulletins TEMS Bulletins contain updates on new TEMS product releases, events, and general information about the TEMS portfolio. You can also obtain up-to-date details on patch releases. To sign up for this free service, go to www.ascom.com/networktesting and, under the heading “TEMS Bulletins”, click the link “Register for TEMS Bulletins”. Along with this material you will also receive our customer magazine, TEMS News. 1.5. Definitions This section explains a number of central concepts in TEMS Investigation which are frequently referred to in this user manual. Data Services This term refers to services requiring a data connection (either circuitswitched or packet-switched), as opposed to voice calls. 12 Chapter 1. Introduction Event An event is generated by the TEMS Investigation software in order to indicate that something worthy of note has occurred, either in the cellular network or in connected equipment. A number of events are predefined. Besides these, you can define events of your own. All predefined events are found in Information Elements and Events, chapter 7. User-defined events are specified by logical expressions which trigger the event when they evaluate to true. These expressions can contain predefined events, Layer 3 messages, and conditions involving information elements. Information Element Information elements are pieces of numeric or text-format data that are presentable in the TEMS Investigation user interface. All information elements handled by TEMS Investigation are found in Information Elements and Events, chapter 3. Information Element, Argument of Many information elements contain an array of values rather than a single value. To pick one item from the array, an argument is used. For instance, the GSM information element Neighbor RxLev contains the signal strengths of all neighboring channels (there may be up to 32). To present the signal strength of a particular neighbor channel, you must specify an argument in the form of a neighbor index between 1 and 32. Complete details on the arguments of information elements are given in Information Elements and Events, chapter 3. Message The term “message” in this user manual generally denotes an air interface message described in the wireless technology specifications, most often a Layer 3 message. A “message window”, however (chapter 24), may list either air interface messages, or mode or error reports produced by phones, or messages from various protocols, or events. Similarly, in the Find in Logfile dialog (section 10.2.2), a “message” may be an air interface message or a phone mode report. Mode Report A mode report is a status or measurement report generated by a phone. NT11-20502 13 TEMS Investigation 13.1 User’s Manual Phone The term “phone” covers user terminals from all supported technologies. When a subset is meant, a suitable qualifier is prefixed, and/or a more precise term is used (“GSM phone”, “Sony Ericsson GSM phone”, “LG UE”, “Samsung LTE modem”, “Sierra Wireless CDMA data card”, etc.). Some user terminals supported by TEMS Investigation are in fact data cards, USB modems, etc. rather than phones. The word “terminal” is therefore sometimes used instead of “phone”, without any difference in meaning from the point of view of TEMS Investigation. Scanner The term “scanner” denotes a device dedicated to scanning, for example a PCTel scanner. Phones with scanning capabilities are not referred to as scanners. 14 Chapter 2. Basics of TEMS Investigation 2. Basics of TEMS Investigation This chapter guides you through some fundamentals of TEMS Investigation. 2.1. Recommended Skills Since TEMS Investigation is a Windows application, familiarity with Windows is useful. To obtain a genuine understanding of the presented information, you need a working knowledge of the wireless technologies concerned. 2.2. Installing TEMS Investigation See the Getting Started Manual, chapter 5 and section 8.2. 2.3. Starting TEMS Investigation Once installed, TEMS Investigation can be launched from the Start menu. Note: We recommend that you plug the external equipment you are going to use into the PC before starting TEMS Investigation. • Choose Start → Programs → Ascom → TEMS Products → TEMS Investigation 13.1. In Windows Vista and Windows 7 you must run the application as administrator. This option is selected by right-clicking the Start menu item above and choosing Properties → Shortcut tab → Advanced. 2.4. Quick Guide to the User Interface This section gives a quick overview of the TEMS Investigation user interface. The overall structure of the user interface is described in more detail in chapters 3 and 4. NT11-20502 15 TEMS Investigation 13.1 User’s Manual Menu bar Toolbars 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. Only one workspace can be open at a time. To manage your windows more smoothly, you can divide your workspace into several worksheets. Up to ten worksheets can be active simultaneously. Navigator From the Navigator you manage and operate your connected equipment, open presentation windows, change the mode of presentation of information elements, and manage your worksheets. Toolbars The toolbars provide shortcuts to certain functions in the application, particularly those relating to logfile recording and replay. Most of the toolbar buttons are mirrored in the menus. 16 Chapter 2. Basics of TEMS Investigation Menu Bar The menus mirror the toolbars as well as the Navigator’s Menu and Worksheets tabs. Status Bar The status bar displays various messages that indicate the current status of the application. NT11-20502 17 TEMS Investigation 13.1 User’s Manual 3. User Interface This chapter goes through the user interface in more detail, and can be seen as an expanded version of section 2.4. 3.1. User Modes TEMS Investigation can be run in two different modes, one for testing and recording, and one for replay and 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. (Regarding the “activate” operation, see section 7.4.) In drive testing mode you can record new logfiles. • Replay mode: The presented information is read from a logfile. In this mode you replay logfiles for inspection and analysis. The two modes are mutually exclusive. At the beginning of a session, the application is in replay mode. As soon as you activate external equipment, however, it switches to drive testing mode and remains in this mode as long as some external device is activated. Deactivating all external devices returns the application to replay mode. This means that: • If you have a logfile open, you must close it before you can activate external devices. • To be able to open a logfile, you must first deactivate all currently active external devices. Note: You do not set the working mode explicitly in the user interface, nor is the current mode shown there. The terminology is used in the manual to clarify how things work. 18 Chapter 3. User Interface 3.2. Workspaces and Worksheets 3.2.1. Workspaces The environment that stores all the windows and settings used in a working session is called the workspace. Settings include information on connected external devices. Only one workspace can be open at a time. When you start TEMS Investigation, 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 (*.tdc). • Create a New Workspace: This option creates a new, empty workspace. • Archived Material: This option takes you to the regular open workspace dialog, where you browse the file system to select a workspace file. The chosen workspace is added to the workspace list in the dialog above, where it is automatically selected. Click OK and TEMS Investigation will start with the chosen workspace. If you click OK without making any selection in the dialog depicted above, the default workspace (identified in the dialog) is opened. The workspace selection dialog closes automatically after 90 seconds (a timer in the lower left corner indicates the remaining time). It cannot be opened again; later on, you handle workspaces from the File and View NT11-20502 19 TEMS Investigation 13.1 User’s Manual toolbar (see section 3.3.4 for further details), or alternatively from the File menu. 3.2.1.1. Opening Workspaces from a Command Prompt Alternatively, you can use the Command Prompt to launch TEMS Investigation with a specific workspace. All of the commands that follow need to be executed from the directory <TEMS Investigation install dir>\Application. • If you know the exact name of the workspace you want to use, you can launch TEMS Investigation with that workspace loaded by giving the following command: investigation.exe <workspace name>.tdc • To start the application with the most recently used workspace, give the following command: investigation.exe -recent • To start the application without loading any existing workspace, give the following command: investigation.exe -newwksp 3.2.1.2. Predefined Workspaces Besides the default workspace, some further predefined workspaces are supplied. They all normally reside in the following directory: • Windows 7, Windows Vista: C:\Users\<user>\Documents\TEMS Product Files\TEMS Investigation 13.1\Workspaces • Windows XP: C:\Documents and Settings\<user>\My Documents\TEMS Product Files\TEMS Investigation 13.1\Workspaces Note: You cannot save changes to the predefined workspaces. To save your modifications, save the workspace under a different name. TEMS Investigation 13.1 cannot load workspaces from older TEMS Investigation versions, whether predefined or user-created. 3.2.2. Worksheets To manage your windows more smoothly, you can divide your workspace into several worksheets. This is already done in the default workspace, which has a number of worksheets dedicated to different purposes, as shown by their designations. Up to ten worksheets can be active simultaneously. 20 Chapter 3. User Interface Worksheets are handled from the Worksheet menu, which can also be accessed by right-clicking in a worksheet. When you copy a worksheet, the device channel (“MS”/“DC”) index is incremented in all windows: for example, “MS1” is replaced by “MS2”. This allows you to instantly duplicate a worksheet for a different device. 3.3. The Toolbars The toolbars in the main window give speedy access to some of the most central functions of TEMS Investigation. The toolbars are mirrored in the menus (see section 3.5). Equipment handling is done from the Equipment tab of the Navigator; see chapters 6–8. 3.3.1. Record Toolbar Start/Stop Recording: Start/stop recording a logfile. When you stop the recording, the logfile is closed. Insert Filemark: Insert a filemark in the logfile. Pause/Resume Recording: Pause the recording and end the current route in the logfile/Resume recording, starting a new route. Swap Logfiles: Close the current logfile and continue the recording to a new file. For a full description of the recording function, see section 10.1. Recording properties are set from the Logfile menu. See section 10.1.3. 3.3.2. Replay Toolbar This toolbar is accessible in replay mode. Open/Close Logfile: Open a logfile/Close the logfile that is currently open. Rewind Logfile: Rewind the logfile to the beginning. NT11-20502 21 TEMS Investigation 13.1 User’s Manual Play/Stop Logfile: Replay the logfile/Stop logfile replay. The speed of the replay is variable and is set from the Logfile menu; see section 10.2.1. Step Logfile: Advance one step in the logfile. Fast-forward Logfile: Play the logfile at high speed. Find in Logfile: Search the logfile. Information: Show information about the logfile. See section 10.2. 3.3.3. Report Toolbar Generate Report: Generate a report from one or several logfiles. See section 10.8. 3.3.4. File and View Toolbar New Workspace: Create a new workspace. Open Workspace: Open a saved workspace. Save Workspace: Save a workspace. Print: Print the selected window. Print Preview: Show a preview of the window printout. Toggle Full Screen: Toggle between full screen and normal mode. 3.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. It is divided into the following sections: 22 Chapter 3. User Interface 3.4.1. Help Section Shows a help text when you point to a button or combo box on the main window toolbars, otherwise directs you to the online help: 3.4.2. Replay Section This section is active in replay mode. It shows the name of the logfile being replayed and the percentage of the replay that has been completed. 3.4.3. Recording Section This section is active in drive testing mode. It shows the name of the file being recorded, its current size (the number of phone reports logged), and the number of filemarks inserted (see section 10.1.1). 3.5. The Menu Bar File Menu Apart from holding some standard File menu commands, this menu mirrors part of the File and View toolbar. View Menu From here you choose which toolbars and which other tools should be visible. The Full Screen mode hides the Navigator. Logfile Menu The Logfile menu mirrors the Record and Replay toolbars. From here you can also set recording and replay properties, and export logfiles (see sections 10.1.3, 10.2.4, and 10.5). NT11-20502 23 TEMS Investigation 13.1 User’s Manual Presentation, Control, and Configuration Menus These menus mirror the Menu tab of the Navigator. Worksheet Menu From this menu you manage your worksheets. Window Menu This is a standard window manager. Help Menu Gives access to online help, containing the same information as this manual, and to the about page. 3.6. Keyboard Shortcuts A number of central operations in TEMS Investigation, as well as many standard file and edit operations, can also be performed from the keyboard. A list of keyboard shortcuts is found in appendix A. 24 Chapter 4. The Navigator 4. The Navigator The Navigator pane, located on the left in the TEMS Investigation main window, allows you to set up and manage your workspace and your external equipment. The Navigator has the following tabs: • the Equipment tab, used for equipment handling: section 4.1 • the Menu tab, listing the types of windows provided: section 4.2 • the Info Element tab, listing information elements: section 4.3 • the Worksheets tab, giving an overview of your current workspace configuration: section 4.4. You can hide the Navigator by switching to full screen mode (done from the View menu or from the File and View toolbar). 4.1. Equipment Tab See chapters 6–8. 4.2. Menu Tab The Menu tab lists most types of windows that are available in the application. They are divided into the categories Presentation, Control, and Configuration. To open a window, double-click the corresponding symbol, or drag the symbol from the Navigator to the worksheet where you want it. All Navigator windows can also be opened from the menu bar. See Information Elements and Events, chapter 8 for descriptions of the contents of individual presentation windows. How the windows work and how they can be configured is covered in the present document: see chapters 21– 29. The control and configuration windows are also described in this volume. Please use the alphabetical index to locate them. NT11-20502 25 TEMS Investigation 13.1 User’s Manual 4.3. Info Element Tab The Info Element tab lists all the information elements handled by TEMS Investigation. Regarding information element categories, see Information Elements and Events. 4.3.1. Presentation Attributes of Information Elements For all numeric information elements (that is, 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). • Size: Range of plot marker sizes encoding the IE value in Map windows. • Symbol: Range of plot marker shapes (symbols) encoding the IE value in Map windows. Some numeric elements have such presentation attributes defined by default; others do not. The attributes are edited from the Info Element tab; see section 4.3.2. When you add an information element to a presentation window, these settings are automatically used unless you have specified a different usage in that particular window (possible only with colors in certain window types; see section 21.5). 4.3.2. Editing the Color Ranges of Information Elements • If you want to add color ranges to an information element, right-click the element in the Navigator and select Add → Color. • If you want to edit the default color ranges of an information element, double-click the information element to expand it and show the presentation attributes, then double-click Color. In either case, continue as follows: 26 Chapter 4. The Navigator 4.3.2.1. Automatic Setup of Color Ranges This is the easiest way to set up color ranges. • Click Auto Setup. • Set the number of intervals. • Under From Color and To Color, choose colors for the extremes of the value range. • Check the Via Color box if you want to use a specific color in the middle of the range. If you do not check the Via Color box, the intermediate color is chosen automatically based on the “From” and “To” colors. When you click OK, a color range is created automatically with evenly sized intervals and suitable intermediate colors. NT11-20502 27 TEMS Investigation 13.1 User’s Manual 4.3.2.2. Manual Setup of Color Ranges If you prefer to assemble your color range interval by interval, follow these steps: • To add an interval, click Add, set the endpoints of the interval, and choose a color. • To edit an interval, select it, click Edit, and make your changes. • To delete an interval, select it and click Delete. A single remaining interval cannot be deleted, nor can the color range as a whole be removed. If you delete parts of the color range so that no color is defined for some values, these values will be drawn in black. 4.3.3. 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. See section 4.3.2 above. 4.4. Worksheets Tab The Worksheets tab lists the worksheets currently active in the workspace. Each worksheet is represented by a folder containing the windows in this worksheet. Double-clicking on a symbol will make that particular window (and the worksheet it is placed on) active. You can rearrange windows from this tab by dragging them between the worksheet folders. 28 Chapter 5. Cell Data 5. Cell Data TEMS Investigation can present information on individual cells in cellular networks. In particular, it is possible to draw cells on maps and to display cell names in various windows. Cell data is also made use of in logfile reports. Cell data can be provided in two ways: • in a plain-text XML file (*.xml) whose format is common to several TEMS products: See section 5.1. • in a file with a plain-text, TEMS Investigation specific format (*.cel). This format is for UMTS only. GSM and WCDMA cells can be mixed in one file. See section 5.2. CDMA cell files in TEMS Investigation CDMA CSV format can be converted to the XML format using TEMS Discovery. Regarding TEMS Investigation CDMA CSV cell files in general, see the Technical Reference, section 3.3. 5.1. Creating a Cell File in XML Format The XML-format cell file uses two XML schemas, which are found in the directory XMLSchema beneath the TEMS Investigation installation directory: • The schema TEMSDataTypes.xsd defines TEMS-specific XML data types, derived from the fundamental data types set down in the XML specification. • The schema TEMSCell.xsd defines XML attributes and elements that embody cell and site data, relying on the data types in TEMSDataTypes.xsd. The most convenient way of composing XML-format cell files is to load the above schemas into a suitable XML development tool, and fill in the data from there. A full description of the XML format is found in the Technical Reference, chapter 3. NT11-20502 29 TEMS Investigation 13.1 User’s Manual 5.2. Creating a Cell File in CEL Format The CEL format is a unified version allowing both GSM and WCDMA cells in the same file. It is described exhaustively in the Technical Reference, chapter 2. If you use a spreadsheet application to edit CEL files, be sure to save them in tab-delimited plain text format. Otherwise, unwanted characters might be inserted which prevent TEMS Investigation from interpreting the file correctly. 5.3. Loading Cell Files To make a cell file active, it must be loaded in the General window. You can have several cell files loaded in the application at the same time. • From the Navigator’s Menu tab, open the General window. • In the General window, double-click the item Cellfile Load. • To add a cell file, click the Add button and browse to select your file. The cell file is added in the list box. • To remove a cell file from the list, select it and click Remove. To remove all cell files, click Remove all. • When you are done selecting cell files to load, click OK. The set of loaded cell files can be modified at any time. If multiple files of the same type (CEL or XML) are loaded, the information in all files is correlated in the presentation. However, if you load both CEL and XML files, no attempt is made to correlate CEL and XML cell information; rather, cell information is presented separately from each type of file. 5.4. 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. 5.5. Use of Cell Data in Presentations Once cell data has been loaded, the following functions become available in the application: • 30 Drawing of cells and indication of neighbor relations and channel usage on the map. See sections 29.5.5.1, 29.5.5.3, and 29.5.5.4. Chapter 5. Cell Data • Serving cell and handover indication on the map. See section 29.5.5.2. • Presentation of cell data on the Info tab of a Map window. See section 29.6. • In logfile reports: Association of statistics with individual cells. Computation of cell ranking based on these statistics. See the Technical Reference, section 8.3. • Presentation of cell names in status windows, line charts, and bar charts. Configuration of status windows is covered in sections 22.2–22.3. Line charts: section 27.4.3. Bar charts: section 28.4. • Best server indication on the map, based on scan data. See section 29.5.5.2. • Indication of distance from current position to current serving cell. See Information Elements and Events, chapter 3 (“Cell Distance” IEs). • Generation of events detecting (probable) missing neighbors. See Information Elements and Events, chapter 7. NT11-20502 31 TEMS Investigation 13.1 User’s Manual 6. Managing External Equipment: General This chapter summarizes how external equipment is handled in TEMS Investigation 13.1. Full details follow in chapters 7–9. 6.1. Connectable Equipment The range of equipment that is compatible with TEMS Investigation is given in the Getting Started Manual, chapter 10. 6.2. Overview of User Interface Components Dealing with External Equipment Equipment tab of Navigator: • • 32 Top pane: – Shows the devices currently plugged into the PC and has controls for activating and deactivating the devices in TEMS Investigation. See chapter 7. – Provides shortcut to device properties. See chapter 19. – One device at a time is in focus in this pane. The in-focus device can be changed with a context menu command. Bottom pane: – The functionality here relates to the device that is currently selected in the top pane. – Activities tab: From here you can manually apply various commands to and perform various actions with the selected device. See chapter 8. All of these tasks, and many more besides, can be automated using the Service Control tool, which is covered in chapter 18. Chapter 6. Managing External Equipment: General – Information tab: Shows some basic data on the selected device. See section 7.3. Status Control Monitor: This window gives a quick overview of the status of current tasks, of equipment connected, and of the PC. The information shown in this window can be found in other places in the application or can be retrieved with the Computer Diagnostics tool; its purpose is to give an at-a-glance overview of vital data in one place. For further information, turn to chapter 9. 6.3. Notes on Reworked User Interface The user interface in TEMS Investigation 12.0 underwent major changes compared to previous product versions. A few pointers regarding these changes may be helpful to users with experience of older versions of TEMS Investigation. • The Equipment Control toolbar was removed. All of its functions were taken over by the newly introduced Equipment tab in the Navigator. • The Equipment Configuration window and the Connections toolbar were removed. Their functions were moved into the Navigator (Equipment tab, top pane). Status information is also provided by the Status Control Monitor window. • The Command Sequence window was replaced by the windows Service Control Designer and Service Control Monitor, which serve similar purposes. The instruction sequences used to control devices are now referred to as scripts. See section 18.2 for a comparison of the old and new tools. • The “equipment channel” concept is not used in the Navigator or in the Service Control windows (where only the designation “EQ” appears). However, in presentation windows, the equipment channels “MS” and “DC” still make an appearance. • 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).1 1. With regard to COM ports, there is one exception; see the Getting Started Manual, section 7.1.2. NT11-20502 33 TEMS Investigation 13.1 User’s Manual • The procedure of preparing a device for use was simplified. All supported devices are automatically detected1, then manually activated and deactivated. An activated device is ready to be used. There are no longer any “enable” or “disable” operations for devices. • Manual voice dials, control commands, and scanning commands are no longer issued from the Equipment Control toolbar but rather from the Navigator (Equipment tab, bottom pane). The same component is also used to initiate data service sessions without running a script (a function which was previously unavailable). 1. Again, the sole exception is the devices covered in the Getting Started Manual, section 7.1.2. 34 Chapter 7. Activating External Equipment 7. Activating External Equipment This chapter describes how to activate external devices in TEMS Investigation for the purpose of data collection. External devices supported by TEMS Investigation are automatically detected by the application after they have been plugged into the PC. The only exceptions to this rule are handled using the Manual UE Configuration utility; see the Getting Started Manual, section 7.1. Special PC and Device Configuration Requirements Regarding device-specific preparations for running data services, see the Getting Started Manual, section 10.6. For some devices, special configuration of both device and PC is required. These steps are covered in the Getting Started Manual as follows: Device GS Chapter Ericsson Fixed Wireless Terminal 11 DRT scanner 12 Andrew i.Scan scanner 13 Rohde & Schwarz TSMW scanner 14 7.1. 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. NT11-20502 35 TEMS Investigation 13.1 User’s Manual 7.1.1. Plugging In Phones and Data Cards Most supported phones and data cards connect to the PC via USB. A single USB cable connects the USB port on the device to a USB port on the PC. 7.1.2. Plugging In Ericsson Fixed Wireless Terminals An Ericsson Fixed Wireless Terminal is connected to the PC by means of a LAN cable. (See the Getting Started Manual, chapter 11.) 7.1.3. • Plugging In Scanners SRUs connect via USB. The device has two USB plugs; the black one must always be connected, 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). The “Status” LED on the SRU front panel is interpreted as follows: – Steady green: The SRU has sufficient power, and the Windows service “TEMS Device Manager” has detected the SRU, so that the SRU’s scanning module has started up. (All OK.) – Flashing green: The SRU has sufficient power, but the TEMS Device Manager has not started or cannot detect the SRU, and so no startup command is sent to the scanning module. Workaround: Restart the TEMS Device Manager service in Windows. – Flashing red: The SRU does not have sufficient power to start up the scanning module. Plug in the red USB plug, or connect the power connector of the SRU cable to an external 12 V power source. • PCTel SeeGull MX, EX, LX MM2, and PCTel PCT scanners connect via USB. • Other PCTel SeeGull LX scanners connect to a COM port. • Anritsu ML8780A scanners connect via USB. • Anritsu ML8720 scanners connect to a COM port. • Andrew i.Scan, Rohde & Schwarz TSMW and DRT scanners connect to an Ethernet port, either directly on the PC or via a local area network. – 36 If the scanner is connected directly to the PC, a 100Base-T crossover cable is used for this purpose. Chapter 7. Activating External Equipment – If the scanner and PC are to communicate over a local area network, both should be connected to local area network ports with normal 100Base-T cables. 7.1.4. Plugging In GPS Units Supported GPS units connect via USB or Bluetooth, or to a COM port. 7.1.5. Plugging In Equipment Cases All supported equipment cases connect via USB. 7.1.6. Plugging In Standalone AQM Modules The standalone AQM module connects to the PC via USB. An audio cable is connected between the AQM module and its associated phone. The AQM module also requires a separate 12 V power supply (the voltage provided through the USB connector is insufficient). 7.2. Starting TEMS Investigation Launch the application as follows: • Choose Start → Programs → Ascom → TEMS Products → TEMS Investigation 13.1. In Windows 7 and Windows Vista you must run the application as administrator. This option is selected by right-clicking the Start menu item above and choosing Properties → Shortcut tab → Advanced. 7.3. The Navigator Equipment Tab: Basics 7.3.1. Top Pane All devices detected by TEMS Investigation are listed in the top pane of the Navigator’s Equipment tab. In the example below, a Sony Ericsson Z750i phone has been autodetected. NT11-20502 37 TEMS Investigation 13.1 User’s Manual Each device is represented by a numbered “EQ” item. You can change the EQ index assigned to the device: see section 7.3.1.1. Please note that in presentation windows, external devices are represented by their channels (“MS”/“DC”/“PS”). See section 21.3. The icon to the left of each device shows the status of the device in TEMS Investigation: 7.3.1.1. No symbol added Device is activated Red cross Device is deactivated Hourglass Device activation or deactivation is in progress Prohibited sign and label “NL”; device string is red Device has no license: see section 7.3.3.5 Earth symbol Device is selected as preferred GPS: see section 7.5 Device Context Menu If you right-click an EQ item, a context menu pops up containing the following commands: • Activate, Deactivate: How to activate and deactivate devices is explained in section 7.4. • Change Equipment: Select a number to change the device’s EQ index to that number. It is possible to select an index that is already taken by another device; the two devices will then swap indices. • Properties: This menu item takes you to the device properties; see chapter 19. 38 Chapter 7. Activating External Equipment 7.3.2. 7.3.2.1. Bottom Pane Activities Tab See chapter 8. 7.3.2.2. Information Tab Capabilities Capabilities of the device. Examples: IP Sniff, Data, PESQ, Air Interface, Position. Identity Device identity. 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). IMSI Shows the IMSI of a UMTS phone’s subscription. Phone Number The phone number of a user terminal. Editable field. If a phone is going to measure AQM in a Call Generator/MRU configuration, the number of the phone must be known to TEMS Investigation. When you plug in a phone, the autodetect procedure sends an AT command to it in order to find out the phone number, which is usually stored on the SIM card. If this operation succeeds, the phone number will display here. If no phone number shows, this may be because no phone number is defined on the SIM, or because the phone did not respond properly to the AT command. In such cases you need to enter the phone number manually in this field. The number you enter will be used for this phone from now on. It will also be used on future occasions when the phone is plugged in, unless the AT command succeeds at that time. A phone number retrieved by an AT command will always override a manually entered number. NT11-20502 39 TEMS Investigation 13.1 User’s Manual 7.3.3. Detection of Equipment: Special Cases 7.3.3.1. Detection of PCTel SeeGull EX Scanner • Start up the scanner without the USB cable connected. Wait until the LED turns green before plugging the USB cable into the scanner. • If you need to power cycle the scanner during use, pull the USB cable before doing so, and do not reconnect it until the scanner has started up again (green LED). 7.3.3.2. Detection of PCTel SeeGull MX Scanner • After installing the driver, and Windows has detected the device for the first time, the scanner should be rebooted. • Always wait for the scanner to boot completely (LED turns dark green) before starting TEMS Investigation. This can take up to 90 seconds (during which time the LED is pale green or orange). 7.3.3.3. Detection of DRT Scanners and Rohde & Schwarz TSMW For technical reasons, 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 7.6.1). Therefore, if you plug in one of those scanners after starting TEMS Investigation, you need to click the Refresh button to have it detected. 7.3.3.4. Detection of HTC Touch Pro2 Phones HTC Touch Pro2 phones (including HTC Imagio) need some configuring before TEMS Investigation can detect them. The details of the configuration differ depending on the phone (unbranded, AT&T branded, Verizon branded, etc.). Below, a brief description is given of what needs to be done. On all phones you need to activate tethering via USB while the phone is connected to the PC by the USB cable. Tethering means using a mobile device as a modem to provide Internet access to an unconnected device – in this case, the PC on which TEMS Investigation is running. The terminology used to refer to tethering differs between phones: • On a Verizon branded phone, activate the “Modem link”. • On other HTC Touch Pro2 phones, activate “Internet Sharing”. 40 Chapter 7. Activating External Equipment In each case, this operation creates ports in Windows that TEMS Investigation can detect. Of phones having the “Internet Sharing” function, only one phone at a time can be used with TEMS Investigation. This limitation does not apply to the Verizon branded phones. On all HTC Touch Pro2 phones except Verizon branded ones, you also need to install TCP Router software. This is provided by Ascom in the form of a CAB file. For HTC Touch Pro2 phones generally, IP sniffing needs to be disabled. That means that KPI data cannot be collected with these phones. For instructions, please refer to section 18.17.3.1. 7.3.3.5. Detection of Equipment Not Covered by License If you plug in a type of device for which you have no license, it will still appear on the Navigator’s Equipment tab. However, the text for this device will be red, 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, as granted by your TEMS Investigation license. See the Getting Started Manual, section 3.3.1. When a device has no license, it cannot of course be activated in TEMS Investigation. 7.3.3.6. Detection of Network Adapters Detection of network adapters (LAN, WLAN) is by default disabled. This is to prevent an inordinate number of devices from appearing in TEMS Investigation when you are doing data collection with multiple devices. • To enable detection of network adapters, set the Network Card device to enabled in the Device Detection Properties dialog (see section 7.6.3). You must restart the application for the change to take effect. You must enable network adapter detection if you want to transfer logfiles over a LAN or WLAN connection; see section 10.4. NT11-20502 41 TEMS Investigation 13.1 User’s Manual 7.3.4. User-assisted Detection of Devices If a device is not detected properly by TEMS Investigation, although it is supported, then you can run the Manual UE Configuration utility to help TEMS Investigation recognize the device. Normally there is no need to do this; there are however certain devices for which you must use Manual UE Configuration as an aid to detection – see the Getting Started Manual, section 7.1. On the Equipment tab of the Navigator, click the button Start Manual UE Config. Alternatively, you can launch this utility by running the file <TEMS Investigation install dir>\Application\ManualUEConfig.exe. The tool Manual UE Configuration has two tabs where you create different kinds of entries used in the detection phase: Device Configuration and Port Configuration. • On the Port Configuration tab you create an entry that is directly mapped to a COM port number on the PC. The Port Configuration tab is mainly used for Datang devices; see the Getting Started Manual, section 7.1.2. • The Device Configuration tab is the most commonly used. It creates an entry for the device that can be reused independently of the actual COM port number used for the device. • On the Device Configuration tab, click the New button to create a new entry. A dialog titled Select your device appears. In the tree view, select the device root node that contains the ports of interest. Then click OK. 42 Chapter 7. Activating External Equipment • The Manage Device dialog appears. Select the type of device to use and map each available port on the device to its function. Ports that do not have a mapping can be left blank or undefined. • Under Name, enter a name for the device. (The string does not show anywhere else in TEMS Investigation.) • Under Type, choose the correct device type according to its capabilities. • In the Ports section, all ports of the device are listed. In the combo boxes on the right is indicated the functional assignment of each port in TEMS Investigation. You can change this assignment by modifying the selections in the combo boxes. See also sections 7.3.4.1–7.3.4.4. • Finally, click OK. • The device is added to the list in the main window. Click Save and Close. Click the Refresh button in the Navigator. This is necessary to update TEMS Investigation with the device configuration just defined. (If you are running the Manual UE Configuration utility independently, TEMS NT11-20502 43 TEMS Investigation 13.1 User’s Manual Investigation will update itself automatically with this data when launched.) 7.3.4.1. Mapping Device Ports to Interfaces If it is not clear which port should be mapped to which interface, the entries in the existing UEDescription.xml file (found under <TEMS Investigation install dir>\Application) may give an indication. The TYPE tag is mapped towards the interfaces, and the DESCRIPTION tag is the name displayed in the tool. (See the XML code excerpt below.) Below are some examples of mappings in UEDescription.xml: Function LG LTE Qualcomm Samsung LTE ST Ericsson Air Interface Diag:xxx LTE DM – Modem Data Interface Data Modem – – Data Modem AT Interface AT AT AT Device Management Ethernet Interface Ndis Ndis Ndis Ndis For a Samsung LTE modem (third column above) this corresponds to the following selections in the Manage Device dialog: 44 Chapter 7. Activating External Equipment In the file UEDescription.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> 7.3.4.2. 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. Launch the Manual UE Configuration utility and select your device as described in the introduction of section 7.3.4. 2. In the Manage Device dialog, do as follows. Under Type, select the appropriate chipset family. Then, in the Ports section, pair each available port to the correct port type as shown in the screenshot below. Finally, click OK. NT11-20502 45 TEMS Investigation 13.1 User’s Manual 3. The device is added to the list in the main dialog window. Click Save and then Close. From now on, TEMS Investigation will detect the Qualcomm device as being of the type you selected in step 2. 7.3.4.3. LG and Samsung Devices with LTE Capability 1. Launch the Manual UE Configuration utility and select your device as described in the introduction of section 7.3.4. 2. For an LG device, set Type to “LG Electronics LTE Modem”. Under Ports, assign the port named “... USB NDIS” (or similar) to the “Ethernet Interface” function. Also identify and map the ports to use for air interface messages (“Air Interface”) and AT communication (“AT Interface”). 3. For a Samsung device, set Type to “Samsung LTE Modem”. Under Ports, assign the port named “Samsung USB LTE Adapter” to the “Ethernet Interface” function. If the device has a “Samsung LTE Control Port” that answers to AT commands, assign that port to “AT Interface”. 46 Chapter 7. Activating External Equipment 4. The device is added to the list in the main dialog window. Click Save and then Close. 7.3.4.4. 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), provided that it comes with Windows drivers enabling an IP data connection. All IP-based services can be tested (as well as video streaming), and all IP-related information elements will then be populated. • If you want to use a device that is not officially supported, set Type to “Data Only Device” in the Manage Device dialog. • Map the device ports as appropriate. Below is an example. 7.4. Activating and Deactivating External Equipment in TEMS Investigation 7.4.1. Activating External Equipment You need to activate a device in TEMS Investigation before you can use it for data collection. NT11-20502 47 TEMS Investigation 13.1 User’s Manual Note: If you have a logfile open, you must close it to be able to activate equipment. Note: A device that is going to use an NDIS data connection must have an APN assigned to it. See the Getting Started Manual, section 10.6.1. Once the device has an APN, you can activate it in TEMS Investigation. • To activate a detected device, right-click it on the Navigator’s Equipment tab and choose Activate from the context menu. To activate all detected devices, click the Activate All button on the Navigator toolbar. The red cross disappears from each device icon to indicate that the device is now active. Furthermore, when you select an activated device in the Navigator top pane, the Activities tab in the bottom pane is populated with the operations that you can perform manually on this device. Regarding these operations, see chapter 8. On being activated, a phone device starts delivering idle mode reports, and a GPS device starts reporting positions. Limitations for Particular Devices • If the device connection must be set up using an external connection manager application, only one such device at a time can be activated in TEMS Investigation (unless the connection manager supports multiple devices). • Of HTC Touch Pro2 phones having an “Internet Sharing” function and requiring installation of TCP Router software, only one phone at a time can be activated in TEMS Investigation. Compare section 7.3.3.4. 7.4.2. Deactivating External Equipment If you want to leave an external device plugged into the PC, but deactivate it in TEMS Investigation for the time being, do as follows: • 48 Right-click the device on the Equipment tab and choose Deactivate from the context menu. Chapter 7. Activating External Equipment To deactivate all active devices: Click the Deactivate All button on the Equipment tab toolbar. 7.5. Managing GPS Units It is possible to have several positioning devices plugged into the PC, and they will then all be detected by TEMS Investigation. This includes GPS units built into scanners.1 However, while multiple GPS units can be detected and activated, only one at a time can update the positioning-related information elements in TEMS Investigation. The device responsible for this will be the one tagged with an “earth” symbol on the Navigator’s Equipment tab. It is referred to as the current Preferred GPS, 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. • If no GPS is activated, and you activate one GPS, that GPS automatically becomes the preferred one. • If no GPS is activated in TEMS Investigation, and you click the Activate All button, 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). • As long as a GPS or some other device is activated in TEMS Investigation, the “Preferred” setting cannot be changed. • While a logfile is being recorded, the “Preferred” setting cannot be changed. 1. GPS units in phones, on the other hand, are currently not recognized by TEMS Investigation. NT11-20502 49 TEMS Investigation 13.1 User’s Manual • To select a different GPS as the preferred one, first deactivate any devices that are activated and stop logfile recording if applicable, then right-click the desired GPS in the Navigator and choose Preferred GPS from the context menu. The earth symbol and “Preferred GPS” tag will then be transferred to that GPS. 7.6. Further Features of the Navigator’s Equipment Tab 7.6.1. The Refresh Function If the devices you connected to the PC were not detected properly (for whatever reason), you can start the detection procedure over from scratch. To do this: Click the Refresh button at the top of the Equipment tab. Note that you must always do a refresh after using the Manual UE Configuration utility; see section 7.3.4. 7.6.2. Re-pairing Phones with AQM Modules When you match phones with AQM modules manually as described in section 8.1.5, mappings between phone IMEIs and AQM module identities are stored by TEMS Investigation in the Windows registry. When plugging the same phones and AQM modules into the PC on a later occasion, you can recreate the same pairings automatically in TEMS Investigation. Note that for this to work, the pairing must not have been undone using the Reset function (see section 8.1.5) before the phone was deactivated. Click the Re-pair Phones with AQM Modules button at the top of the Equipment tab. This function operates the same way whether your AQM modules are standalone or mounted in an equipment case. At any time, on the Activities tab, you can inspect which AQM module is matched with a device by right-clicking the PESQ Device Pairing item under the Control node. If a device could not be matched with an AQM module, the text “UE not paired” will be displayed in the PESQ Device Pairing dialog. 50 Chapter 7. Activating External Equipment 7.6.2.1. 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. No check is performed that the physical connections are in fact still the same. For example, if you are using an equipment case and let two phones swap places, the re-pairing will be incorrect for these phones and the AQM data will be garbage. To prevent this, 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 have been working with different equipment configurations connected at various times to the same PC, the following holds: • Only AQM modules that are physically present when you click the button will be paired. • Each AQM module can only be paired with a single phone. If several phones have previously (at different times) been using the same AQM module, only one of them will be paired with it. 7.6.3. Device Detection Properties The Device Detection Properties dialog can be used to enable and disable detection of various device categories. Note that normally there is no need to do this; the dialog is provided mainly for the purpose of troubleshooting in cases of conflicts during device detection. To open this dialog: Click the Device Detection Properties button at the top of the Equipment tab. NT11-20502 51 TEMS Investigation 13.1 User’s Manual The checkbox in the Enabled column determines if detection of a device type is enabled. By default, detection is enabled for all device types listed except “Network Card”. The latter is disabled because otherwise the PC’s network adapter, as well as other network adapters accessible via LAN/WLAN, would always be detected as EQ’s in the application, which would be undesirable most of the time. Note, however, that if you wish to upload logfiles over FTP using the PC network card, you must enable the “Network Card” item. Compare section 10.4.1.3. If you make changes in this dialog, you need to restart TEMS Investigation for the change to take effect. 7.7. Saving of the Equipment Configuration When you exit TEMS Investigation, the configuration on the Navigator’s Equipment tab is automatically saved. This means that the mappings between devices and EQ items are stored in the Windows registry. As a result, if a device is represented at one time by (say) EQ3, that device will again be mapped to EQ3 the next time it is plugged into the same PC with the same Windows user logged in. The saving extends to all devices whose hardware permits a reliable identification. Such devices include phones with their IMEIs. TEMS Investigation does not save any information on equipment configuration in the workspace. 52 Chapter 8. Operating and Controlling External Equipment Manually 8. Operating and Controlling External Equipment Manually From the Navigator’s Equipment tab (bottom pane, Activities “subtab”), 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). These operations are the subject of the present chapter. For all manual device operations, you double-click the desired item on the Activities tab to open the setup dialog associated with it. When operating devices manually, you make use of the same configuration sets that you refer to in scripts. Compare chapter 18, and particularly the reference material in section 18.17. 8.1. Control Functions See also chapter 19, which covers device property dialogs that provide further means of controlling devices. 8.1.1. Control Function Support by Device • AT commands: Supported for all connectable devices. • Nonvolatile item read/write: Supported for Qualcomm chipset based UMTS devices. NT11-20502 53 TEMS Investigation 13.1 User’s Manual • PESQ device pairing: Supported for devices capable of audio quality measurement using Call Generator/MRU. See the Getting Started Manual, section 10.3.1. • Band lock, RAT lock: See the table below. Nokia NTM3 Sa No Samsung Galaxy S 4G K790i/a, W600i K800i, K600i TM506, Z750i C702/C905*/W760i/W995* Control Function Xperia X10, arc Sony Ericsson Lock on GSM band Lock on RAT Lock on WCDMA band 8.1.2. AT Commands The AT item is used to issue AT commands manually. Each AT command is specified in a configuration set which is identical to that referenced by an AT activity in a Service Control script. If no AT configuration set exists, you need to create one. See section 18.17.1.2 for details. 8.1.3. Band Lock You can restrict the phone’s use of frequency bands. What frequency bands appear here depends on what the phone has support for. 54 Chapter 8. Operating and Controlling External Equipment Manually • Check the bands that the phone should be allowed to use. • Click either OK or Apply. Clicking OK will close the dialog, whereas Apply keeps it open. 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, the P-900 band cannot be selected. • Only one 900 band at a time can be selected. 8.1.4. 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. The dialog is limited to 4 bytes; this is however sufficient to cover most basic NV items. NT11-20502 55 TEMS Investigation 13.1 User’s Manual Specifics on the NV interface are vendor proprietary and must be obtained from the vendor. 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. You are always prompted to confirm an NV command before it is executed. Before an NV write, a read is always performed at the same address. All traffic over the NV interface is logged in internal protocol reports, 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. After an NV write the phone is always automatically reset, and consequently it is deactivated in TEMS Investigation. 8.1.5. PESQ Device Pairing If you are going to do audio quality measurement with a Call Generator or MRU, this is how you select the AQM module with which a given EQ should interact. The PESQ Device Pairing item is selectable only for devices supporting audio quality measurements (these are listed in the Getting Started Manual, section 10.3.1). AQM modules do not themselves appear as EQs on the Equipment tab. Selecting this item opens the PESQ Device Pairing dialog: • At the outset, the string “UE not paired” is displayed, indicating that the device has not yet been paired with an AQM module. • To accomplish pairing, select the appropriate AQM module in the combo box, which holds all available AQM modules, identified by their serial numbers. 56 Chapter 8. Operating and Controlling External Equipment Manually • Click either OK or Apply. Clicking OK will close the dialog, whereas Apply keeps it open. You need to pair off your EQs and AQM modules manually like this the first time around. On later occasions, you can use the re-pairing function (see section 7.6.2) to recreate the same pairing automatically, provided that the physical connections between phones and AQM modules are unchanged. • If you want to undo the pairing so that the device is no longer associated with any AQM module, click the Reset button. Note that if you unpair the devices in this way, you can no longer use the re-pairing function. 8.1.6. Radio Access Technology Lock (Lock on RAT) Certain devices can be locked to a particular radio access technology. The RAT lock function works only in idle mode. 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. NT11-20502 57 TEMS Investigation 13.1 User’s Manual • • GSM – 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. WCDMA – 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. 8.1.6.1. RAT Lock vs. Technology-specific Control Functions: Sony Ericsson The RAT lock setting takes priority over all technology-specific locking functions (channel, cell, and band lock) covered in sections 8.1.3, 19.2.2.6, and 19.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. 1. Except if you put the phone in scanning mode, in which case it ceases to behave like a phone at all. 58 Chapter 8. Operating and Controlling External Equipment Manually 8.1.6.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 release the GSM RAT lock, the phone will immediately switch to WCDMA and lock on the WCDMA cell you selected. 8.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 18.17.5 and 18.17.6. 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. 8.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 18.17.3–18.17.5. 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. NT11-20502 59 TEMS Investigation 13.1 User’s Manual Progress indicators are shown for data service sessions in the same way as for CS voice/video; compare section 8.2. 8.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.9. 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.9. • Messages in the Data Reports message window: see Information Elements and Events, section 8.9. 8.4. Scanning The Scan node is where you set up and execute scanning sessions. These activities, too, are configured using configuration sets (but can be run only manually, as the Service Control tool does not provide scanning support). See chapter 11. For complete details on scanning setups for each cellular technology, see chapters 12–17. 60 Chapter 9. The Status Control Monitor 9. 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. 9.1. Equipment Connection This indicator relates to the status of data collecting devices other than positioning equipment. Symbol Meaning green A new device (EQ) has been activated in TEMS Investigation. yellow A device which is activated has stopped delivering data. red A device has been deactivated in TEMS Investigation. no color No devices detected. Compare the Navigator’s Equipment tab: see section 7.3. NT11-20502 61 TEMS Investigation 13.1 User’s Manual 9.2. Positioning This indicator reflects the status of the currently preferred positioning device. (Regarding the definition of “preferred”, see section 7.5.) Symbol Meaning green The preferred positioning device is delivering valid data. red The preferred positioning device has stopped delivering valid data. no color No positioning device detected. Compare the Navigator’s Equipment tab: see section 7.3. 9.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 8.2, 8.3) and service sessions controlled by a script (see chapter 18). However, if you initiate a service directly on the device, using the device keypad, such an action does not affect this indicator. Symbol 62 Meaning green Last service execution OK, everything in order. yellow Service execution failed once or twice. red Service execution failed repeatedly (at least three times in a row). no color No service executing. Chapter 9. The Status Control Monitor 9.4. Computer Performance This information is taken from Windows. Memory usage for all tasks, not only TEMS Investigation, is indicated. Symbol Meaning green CPU and memory usage both below 75%. yellow CPU and/or memory usage above 75%, but both below 95%. red CPU and/or memory usage above 95%. 9.5. Logfile Progress This indicator is concerned with logfile recording only, not logfile replay. Symbol Meaning green Recording active. red One of the following: no color • Recording paused. • Size of logfile not increasing due to an error. • Device deactivated. No recording in progress. Compare the status bar, Recording section: see section 3.4.3. 9.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. NT11-20502 63 TEMS Investigation 13.1 User’s Manual 10. Logfiles This chapter explains: • how to log information received from external devices to file (section 10.1) • how to replay a logfile (section 10.2). The chapter also describes: • loading of logfiles from sources outside TEMS Investigation (section 10.3) • transferring of logfiles via FTP (section 10.4) • logfile export (section 10.5) • merging of uplink AQM data into logfiles (section 10.6) • merging of logfiles with uplink data files (section 10.7) • generation of logfile reports (section 10.8). 10.1. Recording Logfiles Logfiles can be recorded in the following ways in TEMS Investigation: • from the Record toolbar or Logfile menu • from within scripts. All these procedures produce the same type of output file, with extension .log. The functions available for controlling the recording and modifying the logfile are however somewhat different in each case. For instructions on how to perform recording in scripts, consult sections 18.17.1.7–18.17.1.9. The present section deals with direct 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. You are asked specify a name and storage location for the logfile. The default naming format is MMDD_nn.log, where MM is the current month, DD is the current day of the month, and nn is an incrementing counter starting at 01. 64 Chapter 10. Logfiles 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.) • Perform the desired tasks with your external equipment. To pause the recording without closing the logfile, click Pause Recording. Click the same button once more to resume the recording. Events indicating pausing and resumption are written to the logfile. See Information Elements and Events, section 7.1. 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. 10.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. Filemarks can be searched for during logfile replay (see section 10.2 below). They are treated as events and appear as such in presentation windows. In Service Control scripts, you can use the Filemark activity to have filemarks inserted automatically. See section 18.17.1.5. To add a filemark manually: Click the Insert Filemark button and enter the filemark text. You can also insert so-called quick filemarks; see section 10.1.3 below. A Filemark event is written to the logfile for each filemark. NT11-20502 65 TEMS Investigation 13.1 User’s Manual 10.1.2. Swapping Logfiles At any time while recording, you can close the current logfile immediately and continue recording to a new file. Click the Swap Logfiles button. If the original logfile was named according to the default format, the new logfile is named according to the format MMDD_02.log. For subsequent files the counter is incremented further. If the original logfile was named differently (say, my_logfile.log), the second file receives the name my_logfile_02.log, and so on. Note that if you have the Quick logging option turned on (see section 10.1.3), you can specify that logfiles should be swapped after a given number of messages have been logged. The manual swapping function is independent of this option and works also when it is active. Note: The Swap Logfiles function must not be used when recording KPIs. All input to a KPI computation must be recorded in one file. Note also that average throughput IEs, byte counts, and the like require a Network Connect activity at the start of the logfile (see Information Elements and Events, section 3.9.1.1). In general, it is best to swap logfiles only in idle mode if at all possible. 10.1.3. Further Recording Options Some additional options are available when recording logfiles. • 66 From the Logfile menu, choose Recording Properties. Chapter 10. Logfiles Default Recording Folder Here you can change the default recording directory. Quick Logging If you check this box, TEMS Investigation will not ask for a logfile name before starting the recording, but create a default logfile name automatically (with the format MMDD_nn.log as described at the start of section 10.1). To ensure that you will not end up with impractically large logfiles, you can check Swap files after reaching message and specify a limit on the number of air interface messages in a logfile. Then, once the given number of messages have been logged, the logfile is closed and the recording automatically continues to a new file. Quick Filemark If you check this box, the filemarks you insert will simply be integers. You will not be asked to enter a text string. Quick filemarks are useful for just marking one position or a few positions in the logfile without having to bother with writing comments. Add User Info If you check this box, you will get the opportunity to write a comment in the logfile after concluding the recording (a text box will pop up). If you use the swap logfiles function (see section 10.1.2), the text you enter in the box will be written to the last logfile only. NT11-20502 67 TEMS Investigation 13.1 User’s Manual Clear History Buffer at Start of New Logfile If you check this box, an internal history buffer (providing quick access to logfile data) is cleared every time you start recording a new logfile. This reduces the consumption of disk space as well as the CPU load during recording. To avoid out-of-memory issues, the history buffer in TEMS Investigation is automatically cleared on reaching a size of 410,000 messages. The function is automatic and the user cannot view or edit any settings controlling this behavior. 10.1.4. Positioning Logfiles by Pinpointing This section describes how to use the pinpointing technique for positioning logfile data. Pinpointing is useful in environments where GPS coverage is lacking. Note: If you activate a GPS in TEMS Investigation, pinpointing is disabled. A GPS can be physically plugged in without disabling the pinpointing function, but it cannot be activated in the TEMS Investigation application. Conversely, while pinpointing is in progress, you cannot activate a GPS in TEMS Investigation. 10.1.4.1. Basic Pinpointing Procedures Begin by clicking the Pinpoint button. You must do this before starting the logfile recording. Now click the Start Recording button. To record positions for measurements, you indicate your position by clicking on the map at regular intervals. As long as a phone is activated, clicks on the map will be interpreted as pinpointing actions. This is indicated by the cursor changing into an upward arrow whenever it enters the Map window. Each time you pinpoint, the corresponding position is registered in the logfile as a waypoint along your route. The waypoint is marked with a black diamond, and a new route segment in the form of a straight line is drawn to it from the preceding waypoint. Then, 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). 68 Chapter 10. Logfiles 2 1 4 3 5 Route Waypoints (pinpoint markers) Measurement data points The waypoints themselves are stored in the logfile as “Pinpoint” messages which appear by default in the Events window. Therefore the waypoints and connecting lines appear also when the logfile is replayed. If you want to pause the recording temporarily, without closing the logfile: • Pinpoint once just before pausing to ensure that all measurement data is plotted correctly. Click Pause Recording. To resume the recording, click the same button again, and pinpoint immediately so that all data can be accurately positioned. When you are done with your entire measurement session, finish as follows: Deactivate the phone. • Pinpoint one last time to ensure that all data is accurately positioned. Click Stop Recording to end the recording and close the logfile. 10.1.4.2. Advice on Pinpointing and Recording From section 10.1.4.1 it is clear that in order for the recorded route to agree well with the actual one, you should pinpoint every time you change direction. Furthermore, to obtain equal data densities in different locations, you should try to maintain approximately the same speed throughout your route. (Note that this is in fact not the case in the figure in section 10.1.4.1, where the tester has increased his speed considerably between waypoints 3 and 4.) If you pinpoint close to the edge of the Map window, the map will scroll automatically. It is wise not to replace the map during recording. NT11-20502 69 TEMS Investigation 13.1 User’s Manual To optimize the performance of the Map window, you should remove all unused themes (see section 29.5) and avoid having other presentation windows open at the same time unless you really need them. 10.2. Replaying Logfiles Note: To be able to replay a logfile, you must deactivate your external equipment. Furthermore, if you have been using pinpointing, you must also exit Pinpoint mode in the Map window, for instance by clicking the Selection Tool button on the Map window toolbar (see section 29.9). Logfile replay is controlled from the Replay toolbar or from the Logfile menu. The quickest method is to use the toolbar buttons: Open/Close Logfile: Open a logfile/Close the logfile that is currently open. Only one logfile can be open at a time. Rewind Logfile: Rewind the logfile to the beginning. Play/Stop Logfile: Replay the logfile/Stop logfile replay. The speed of the replay is variable and is set from the Logfile menu; see section 10.2.1 below. When the stop button is clicked to halt fastforwarding, all presentation windows are updated. Step Logfile: Advance one step in the logfile, i.e. read one more message from the phone. Note that a presentation window is not always updated when advancing a single step or just a few steps. Fast-forward Logfile: Play the logfile at high speed. No updating of presentation windows takes place until the replay is stopped. Find in Logfile: Search forward in the logfile for a time instant, a type of event, or a type of message. See section 10.2.2 below. Information: See section 10.2.4. 70 Chapter 10. Logfiles 10.2.1. Replay Properties From the Logfile menu, you can adjust the speed of the logfile replay. • Choose Play Properties from the Logfile menu. Normal This is the default replay speed (and the fastest). Intermediate Somewhat slower than Normal. Interpretable (Slow) Very slow. At this speed, the screen is updated for each new message, which is not the case for the higher speeds. 10.2.2. Searching a Logfile During replay you can search a logfile for one of the following: • a time instant (e.g. “16:32:47”) • a type of event (e.g. “Call Setup”) • a type of Layer 3 message, Layer 2 message, or mode report • filemarks with specified text. To perform a search, click the Find in Logfile button on the Replay toolbar. The dialog that appears has separate tabs for each of the above categories. • Choose what you want to search for, then click either Find or Find Next. – If you click Find, the logfile is rewound to the beginning and then the first occurrence of the requested item is searched for. The dialog is closed immediately on clicking the Find button. – If you click Find Next, the search starts from the point to which the replay has progressed. The dialog remains open. NT11-20502 71 TEMS Investigation 13.1 User’s Manual When an item of the specified type has been found, the replay halts at this point. 10.2.3. Replay Section of Status Bar While a logfile is being replayed, the Replay section of the status bar shows the name of the file and indicates the percentage of the file that has been replayed. See section 3.4. 10.2.4. Logfile Information It is possible to view some information about logfiles. Click the Information button on the Replay toolbar. • The Header tab shows data on the logfile currently in use. • If the user who recorded the logfile made use of the Add User Info option (see section 10.1.3), the User Info tab shows the information input by this user. 10.3. Loading Logfiles from Other Sources TEMS Investigation can load and replay logfiles from the TEMS products listed below. • TEMS Investigation 13.x, 12.x, 11.x, 10.x, 9.x, 8.x, 7.x, 6.x • TEMS Investigation GSM 5.x, 4.x, 3.x • TEMS Investigation EDGE 1.x • TEMS Investigation WCDMA 3.x, 2.x • TEMS DriveTester GSM–TDMA 1.x (GSM logfiles) • TEMS Pocket 11.x1, 10.x1, 8.x1, 7.x, 6.x, 5.x 2 • TEMS Automatic 8.x, 7.x, 6.x (any MTU and TEMS Pocket Remote [HTU] logfiles) • TEMS Automatic 5.x (any MTU logfiles) 1. Please note that logfiles from these TEMS Pocket versions must first be converted using a PC utility that is delivered with that version. 2. TEMS Pocket 9.x logfiles cannot be loaded in TEMS Investigation. 72 Chapter 10. Logfiles • TEMS Automatic 4.x (MTU logfiles recorded with GSM-only MTUs) • TEMS Automatic 3.x, 2.5 TEMS Investigation can also read • EFEM logfiles from Motorola phones • MDM logfiles • logfiles from Anritsu ML8720 scanners (i.e. files logged by the scanner itself) • MTR files (GSM; see section 41.1) 10.4. Logfile Transfer via FTP TEMS Investigation has a function for uploading logfiles via FTP according to preconfigured FTP server settings. 10.4.1. Setting Up Logfile Transfers • To set up FTP logfile transfers, on the Menu tab of the Navigator, choose Configuration → File Transfer. • In the window that appears, click the Settings button. NT11-20502 73 TEMS Investigation 13.1 User’s Manual 10.4.1.1. FTP Server Settings User, Password User name and password on the FTP server, if required. Server Address IP address or host name of FTP server. Port The FTP server port to use. Server Logfile Directory Path to the directory on the FTP server where the uploaded logfiles will be stored (in a subdirectory named according to the current date). The logfile names are augmented with a timestamp indicating the time of upload: _tfu__hh_mm_ss (“tfu” means “TEMS file upload”). Local Logfile Directory The local directory on the PC from which logfiles will be uploaded. 10.4.1.2. Logfile Options Start transfer when logfile is closed If this is checked, every logfile will be transferred immediately after the recording has ended. If the option is not checked, you initiate transfers manually as described in section 10.4.2. [...] files after transfer • Delete: After logfiles have been uploaded, they are deleted from the local directory. • Move: Within the local directory, logfiles that have been uploaded are moved to a subdirectory Complete that is created automatically for the purpose. If Start transfer when logfile is closed is checked, this behavior is preselected and cannot be changed. Generate MD5 checksum 74 If checked, 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. Using some suitable third-party software, you can then compute the checksum for the uploaded file and confirm that it agrees with that of the original. Chapter 10. Logfiles 10.4.1.3. Equipment Here you select the device to use for logfile transfer. The transfer can be done over a cellular network, or over an Ethernet or WLAN connection. Note: Transfer over Ethernet or WLAN requires that detection of network adapters be enabled (it is disabled by default). See section 7.3.3.6. Note that you do not need to have the device activated in TEMS Investigation to be able to transfer files. For a cellular network device, you need to supply parameters for connecting to the network. Click the Connection parameters button to open the dialog for creating a Network Connect configuration set. The parameters of this configuration are gone through in section 18.17.3.1. 10.4.1.4. Setup You can save all settings made in this dialog as a file transfer setup. The setups are maintained in the dialog; there is no explicit handling of setup files. • To save a setup, type a name for it in the Name box and click Save. The setup is added in the list box. • To load a previously saved setup, select it in the list box and click Load. • To delete a setup, select it in the list box and click Delete. 10.4.2. Starting Logfile Transfers This section is applicable only when the option Start transfer when logfile is closed described in section 10.4.1.2 is not set. In this case you start the logfile transfer manually on each occasion. • In the File Transfer Settings dialog, define or select the setup you want to use, then click OK. • In the File Transfer window, click the Start button. (If the file transfer is automatic, this button is named Auto and grayed out.) The progress bar will indicate the progress of the transfer. NT11-20502 75 TEMS Investigation 13.1 User’s Manual 10.5. Exporting Logfiles in Other Formats Logfiles can be exported in the following formats: • Text file with tab delimited data (suitable for processing in, for example, a spreadsheet application). TEMS Automatic logfiles, too, can be exported in this format. The text export format is described in detail in the Technical Reference, chapter 6. • MapInfo 3.0 (Interchange or Tab format) • ArcView Shapefile: about version, see the Technical Reference, section 7.2 • Marconi Planet DMS 3.1 • Ethereal • MDM (CDMA) Some of these formats contain multiple files for each logfile. See the Technical Reference, chapter 7 for details. Note: Export in MapInfo, ArcView, or Planet format requires that the data be positioned. If there is no positioning information in the logfile, the export file will contain only a header and no route data. 10.5.1. Preparing an Export Order • First, deactivate any external devices that are currently activated. This is necessary in order for the export to work properly. • From the Logfile menu, choose Export Logfile. Click Add. The Add Export Order dialog appears: 76 Chapter 10. Logfiles Format Select the output format for your logfiles. Regarding the choice PESQ merge, see section 10.6. Regarding the choice Logfile with uplink data, see section 10.7. (These are not logfile export formats in the strict sense.) Input files Type or select the logfile or logfiles you want to export. Merge output If you are exporting several logfiles and this option is checked, all logfiles will be merged into a single set of export files. (Logfiles are simply concatenated; there is no sorting of messages by timestamps.) The name given to the export files depends on the ordering of logfiles in the Input files box. If the Merge output option is unchecked, each logfile is exported separately, and the export file set simply retains the name of the logfile. Directory The directory where the export files are written. Prefix, Suffix To the export file name you can add a descriptive prefix and suffix if desired – e.g. downtown as prefix and am or pm as suffix. NT11-20502 77 TEMS Investigation 13.1 User’s Manual Extension • File extension for export file. Editable only for certain formats, including the plain-text format. Export to other formats produces files with fixed extensions, as described in the Technical Reference, chapter 7. Now click the Setup button to specify details of the export; see section 10.5.2 below. 10.5.2. Specifying the Contents of Export Files On clicking the Setup button, a dialog appears whose contents partly depend on the format chosen. The Information Elements tab, however, is common to many of the formats: Here you select which information elements to include in the export. You choose each individual element separately. From information elements with arguments you pick one component at a time. By default the chosen item is exported from all devices that report it. • To export an element, select it in the Available IEs list and click the “>” button to move it to the Selected IEs list. If the element has arguments, you do not get the whole element at once, but only the component with the lowest argument. To select the component with the next higher argument, click “>” again. Repeat for all components you want to export. • By default the items selected are picked from all phones. To export the item only from specified phones, you must edit the item; see Editing the Selected Items below. 78 Chapter 10. Logfiles • To export an information element from a different category (e.g. the Data category), choose that category in the combo box in the Available IEs section. Elements from different categories can be freely mixed in export files. • To remove an item from the Selected IEs box, select the item and click “<”. To clear the entire Selected IEs box, click “<<”. Editing the Selected Items To edit an information element: • In the Selected IEs box, select the desired item and click the Edit button above the box. The Edit IE dialog appears. For all export formats, you can restrict the export of a selected IE to a single device, or change the IE argument (where one exists). For all export formats except tab-delimited text, you can also edit the following settings: • NAME field: This is the IE column heading in the export file. By default, the column heading string consists of the IE name. (You might want to make this string shorter.) • NODATA field: If you enter a string here, it will be written in the export file whenever the IE does not have a valid value. For Planet, any string is accepted, whereas for the remaining formats the string must be numeric (e.g. “999”, “-1”). As long as these settings have not been edited, the IE name is preceded by an asterisk (*) in the Selected IEs box. Note also that the NAME and NODATA settings are not saved along with other logfile export settings, but in different files. See section 10.5.2.8. 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. You can rearrange the items by selecting them and moving them using the Up and Dn buttons. 10.5.2.1. Text File Specific Settings Besides your chosen information elements, the text export file always contains data on events, including user-inserted filemarks. There are no user settings relating to the event data. By default the text export file also contains message information. NT11-20502 79 TEMS Investigation 13.1 User’s Manual Optionally, the export can be reduced in order to decrease the duplication of data and the number of lines in the export file. The choice is made on the Options tab: Full message information... All messages are kept. The following columns are optional: Message Type, Message ID, and Hexadecimal String. Check a column to include it. All other standard columns are always included; see the Technical Reference, chapter 6. In addition there will be one column for each selected IE or IE component. If you check Show changed IE values only, IE values are written out only if they have changed since the previous message. This makes for a considerable reduction of the export file size. If the box is not checked, all IE values are written for every message. 80 Chapter 10. Logfiles Events and filemarks only... The export file is reduced in two ways: • The columns Frame Number, Message ID, and Hexadecimal String are excluded from the export file. (The Event column is kept, as is the Event Info column provided that the Event information checkbox below is checked.) • Messages not triggering an event and containing no changed IE values are wholly excluded. Event information Governs whether the Event Info column is included in the export. Message options Check the relevant boxes in order to have Layer 2 messages, Layer 3 messages, and phones’ mode reports exported as unabridged plain text to a common separate file whose name ends in _textexp.txt. 10.5.2.2. MapInfo Specific Settings For MapInfo export (whether to Interchange or Tab format), the Options tab looks like this: NT11-20502 81 TEMS Investigation 13.1 User’s Manual Reports to export data from This setting governs what types of report from the phone are included in the export files: • all reports • only Layer 3 reports • only mode reports. By default all reports are exported. Export message information... Events Include file name in file Check this to include information on Layer 3 and Layer 2 messages in the export files. The following data is added (one column for each item): • Message direction (internal, uplink, downlink) • Message name • Hexadecimal string • Extension (containing cause values) This setting governs the export of events. • Do not export events: No event information is exported. • Export events but do not plot...: Events are exported, but no event-specific symbol is used in MapInfo when plotting on a map. • Export events and plot...: Events are exported, and a unique symbol is used when plotting in MapInfo to distinguish events from other data. Note, however, that there is no differentiation of event types, and that the symbol used is not one of the default TEMS Investigation event symbols. Check this to include the file name in the export files. For details on MapInfo output, see the Technical Reference, section 7.1. 82 Chapter 10. Logfiles 10.5.2.3. ArcView Specific Settings Export message information... Check this to include information on Layer 3 and Layer 2 messages in the export files. The following data is added (one column for each item): • Message direction (internal, uplink, downlink) • Message name • Hexadecimal string For details on ArcView output, see the Technical Reference, section 7.2. 10.5.2.4. Marconi Planet Specific Settings Export message information... Check this to include information on Layer 3 and Layer 2 messages in the export file. The following data is added (one column for each item): • Message direction (internal, uplink, downlink) • Message name For details on Marconi Planet output, see the Technical Reference, section 7.3. 10.5.2.5. Ethereal Specific Settings The export encompasses all of the logfile content. The Export message information checkbox must be checked, otherwise the output file will be empty. For details on Ethereal output, see the Technical Reference, section 7.4. 10.5.2.6. MDM Specific Settings MDM export is intended for logfiles recorded with Qualcomm chipset based devices. NT11-20502 83 TEMS Investigation 13.1 User’s Manual The export encompasses all Qualcomm-specific CDMA/WCDMA messages in the logfile. The Export message information checkbox must be checked, otherwise the output files will be empty. For details on MDM output, see the Technical Reference, section 7.5. 10.5.2.7. “Logfile with Uplink Data” This is not an ordinary logfile export format, but it has been grouped with these for convenience; see section 10.7. 10.5.2.8. Saving and Loading Export Setups When you are done specifying the export, you may want to save the setup for future use. • In the Setup dialog, click Save and store the file where appropriate. The file extension will depend on the format (for example, .tex for a text-format export setup). • To load a previously saved setup in the Setup dialog, click Load and locate the setup file. However, the NAME and NODATA settings for information elements (see the introduction of section 10.5.2) are not saved in the above-mentioned files. They are instead written to DBF files that are found in the Settings directory beneath the TEMS Investigation installation directory. 10.5.3. Executing Export Orders All the export orders you have defined are listed in the Export Logfile window. • To start executing the export orders, right-click and choose Start from the context menu (or click the Start button in the window). • To abort the execution of the export orders, right-click and choose Abort from the context menu. A summary of the export execution appears in a popup window (“Export Result”). 84 Chapter 10. Logfiles 10.6. Merging Uplink AQM Data into Logfiles (UMTS) As described in chapter 33, uplink AQM data is computed by a Call Generator and output in XML files. This uplink data needs to be inserted in each logfile (*.log) recorded with TEMS Investigation. To perform the data merge, you need to export the TEMS Investigation logfile with Format set to PESQ merge. The output is a new logfile (still in *.log format) that includes both uplink and downlink AQM data. 10.6.1. Retrieving Uplink AQM Data The uplink AQM data is stored as XML files on the Call Generator PC, by default under C:\TIPESQ in a subfolder named <yyyymmdd><phone number>. The XML files are given random four-digit numbers as names. No special tool is currently provided in TEMS Investigation for accessing the uplink AQM data; the files must be collected manually from the Call Generator. This could be done in a number of ways, 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. 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. See the screenshot in section 10.6.2. 10.6.2. • Preparing and Performing a Merge From the Logfile menu, choose Export Logfile. Click Add. The Add Export Order dialog appears. Compare section 10.5.1. • Under Format, select PESQ merge. • Click the Setup button next to the Format combo box. A dialog appears in which you point out where the uplink AQM data files are located (one XML NT11-20502 85 TEMS Investigation 13.1 User’s Manual file for each AQM call). See section 10.6.1. Click the “...” button and locate the root directory holding all XML files (the level above the directories named by date). An example is shown below: UL AQM root directory • Click OK, then OK once more. • Back in the Add Export Order dialog, under Input files, select the TEMS Investigation logfiles (*.log) containing the downlink AQM data. • You also need to specify where the merged output files should be written. To this end, click the Browse dir button next to the Directory box and navigate to the desired directory. • Be sure not to check the Merge output option. • Click OK to exit the Add Export Order dialog. • You are now ready to perform the merge. Execute the AQM export order from the Export Logfile window as described in section 10.5.3. The output files will remain TEMS Investigation logfiles with extension .log. The name of each output logfile will consist of the original name plus the suffix “-AQM”. What happens during the merge is that the uplink AQM data is integrated into the logfile, all entries being sorted by their timestamps. To compensate for the delay in computing the AQM data, the logfile export function also moves the downlink data 5.5 s backwards in time so that each score aligns with the speech sentence for which it was computed. (Exception: The first score in each pair of Frequent AQM scores needs to be moved a further 2.75 s backwards, or 8.25 s in total.) The uplink data is simply inserted into the logfiles at the correct points in time. For in-depth coverage of the computation of AQM data, including timing issues, see the document “AQM in TEMS Products (Including PESQ)” which is found on the installation CD in the subdirectory Documents. It is possible to perform a merge with an incomplete set of uplink data files, and to repeat the merge procedure later on with further uplink data supplemented. No duplication of data in the output logfile will result from this: the logfile export function processes each AQM call only once. 86 Chapter 10. Logfiles 10.7. Merging Logfiles with Uplink (MTR) Data It is possible to incorporate into logfiles data originating from Ericsson uplink data files (MTR files). See chapter 41. The term “MTR file” will be used in this section when referring to characteristics of this specific file type. Before going through the mechanics of merging the files, it is appropriate to outline how the merging algorithm works. 10.7.1. The Merging Algorithm The task of the merging algorithm is to time-align – synchronize – the information in the uplink files with that in the logfiles. A time offset can be expected between the clock that governs uplink file time-stamping (for MTR files, the BSC clock) and the clock in the PC on which the logfiles were recorded. While an uplink file contains (usually) one complete call involving a specific phone (actually a specific IMSI, i.e. subscriber identity), a logfile can comprise an arbitrary number of calls made by one or several phones. The typical situation, therefore, is that a logfile corresponds to multiple uplink files, each covering a logfile segment that concerns a single call: 1 Uplink files idle call idle call idle call idle Logfile For each call in the logfile, the merging algorithm extracts a number of key characteristics: start time, stop time, and information about handovers (time of occurrence and serving cells involved). Then, each uplink file is compared to each call in the logfile with respect to these characteristics. The uplink files for which a reliable match has been found are finally incorporated into the 1. Note, however, that both types of file may contain call fragments. Multiple MTR files will be generated by a call if switching between BSCs occurs during the call (provided of course that all BSCs are recording). TEMS logfiles will contain fragments of calls whenever recording is not active throughout a call, and also when the “Swap logfiles” function is used so that the recording continues to a new file (section 10.1.3). NT11-20502 87 TEMS Investigation 13.1 User’s Manual logfile, aligned as indicated by the calculated time offset. The output is a new logfile (extension .log), augmented with the uplink information, which is represented as being reported by a fictitious phone “MS5”. The merging algorithm may sometimes fail for certain uplink files; typical reasons for failure are discussed in section 10.7.2 below. When this happens, you can put the algorithm on the right track by providing additional information. There is also the possibility of aligning uplink files manually. Regarding this, see section 10.7.3 under Handling Problematic Uplink Files. 10.7.2. Limitations of the Merging Algorithm If the merging algorithm has enough to go on, that is, if all calls in the files can be readily distinguished from each other by means of the characteristics considered, the procedure is straightforward. However, if this is not the case for some uplink file, so that there is difficulty in finding an obvious best match for it, the procedure will fail for this file. Problems will thus arise with sets of similar calls, especially if they are short and lack distinctive features (namely, handover events). Multiple calls with uniform characteristics can indeed be expected when running a script repeatedly (regarding scripts, see chapter 18). Fragments of calls, whether in uplink files or logfiles, are also more likely to be problematic, because either the start time or stop time and thus the call duration is unknown. Furthermore, the algorithm does not handle day transitions. Therefore, it cannot correctly process calls beginning before and ending after midnight, or deal with time offsets that are so large as to place part of the calls on a different day. In other respects the size of the time offset does not affect the performance of the algorithm. 10.7.3. Performing the Merge The procedure is carried out from the Export Logfile window: • From the Logfile menu, choose Export logfile. In the Export Logfile window, click Add. • Under Input files, enter the logfile names, or click “Browse file” and select your files. (If you choose several logfiles, the merge will be done separately for each logfile.) • Under Directory, specify a directory for the output. 88 Chapter 10. Logfiles • In the Format combo box, choose Logfile with uplink data. • Click the Setup button. In the dialog that follows, you decide how to perform the merge (Method tab) and what uplink files to include in it (Uplink files tab). Method Tab Unless you somehow know the exact time offset beforehand, you should begin by running the algorithm described in the previous sections. (If you do know the offset, you may want to carry out the alignment yourself. See section 10.7.3 under Manual Alignment.) • Mobile to match in logfile determines what logfile data is considered when comparing it with the uplink files. If you have data from several phones in the logfile, but uplink files for a single phone, it is appropriate to disregard the data from the other phones: this eliminates a source of uncertainty in the matching process and also speeds it up. • If you have some idea about the size of the offset, you can check Place bounds on uplink file offset and enter lower and upper bounds. This, too, increases the reliability and speed of the algorithm. Uplink Files Tab On this tab you choose your uplink files. You do not have to list them in any particular order. NT11-20502 89 TEMS Investigation 13.1 User’s Manual Running the Merging Algorithm When you have completed the Add Export Order dialog, the specified merge appears in the list in the Export Logfile window. Click Start to carry out the merge. The procedure will take some time. When it has completed, you will receive a message (“Export Result”) stating success or failure for each uplink file. See the example in section 10.7.5. • If all uplink files have been successfully matched, you are done. • If the algorithm has failed for some files, see Handling Problematic Uplink Files below. Do not close the Export Result window – you will need to inspect the information given there. To terminate an ongoing merge, click Abort. Handling Problematic Uplink Files If no sufficiently reliable match is found for an uplink file, it is not included in the output logfile. There are two possibilities: Either there is no match – the data in the uplink file simply does not exist in the logfile –, or there is indeed a match to be found, but the algorithm has problems identifying it, typically for one of the reasons stated in section 10.7.2. In the latter case, you can try to remedy the problem as follows. What the algorithm needs in order to align the troublesome file, or files, is more precise information about the offset. Often several calls in the logfile are good matches and there is a problem figuring out which is the correct one. Now, the offsets calculated for the successfully aligned uplink files (which should be nearly identical) should be similar to that of the remaining files as well. Therefore, you can assist the algorithm by feeding back the information on the offset:1 In the Export Logfile window, click the Edit Order button. • Click Setup. • On the Method tab, check Place bounds on uplink file offset and enter upper and lower bounds based on the values observed in the Export 1. The reasons for requiring that this be done manually are given in the section Why the Manual Steps? below. 90 Chapter 10. Logfiles Result window. The bounds should be tight enough to ensure that a call in the logfile cannot be mistaken for an adjacent call. Exit the dialogs, and click Start to run the algorithm again. With this new constraint applied, it should be possible to align all the uplink files that have a genuine match. Manual Alignment If the procedure still fails for some files, they probably do not correspond to anything in the logfile. It might be the case, however, that some files are corrupt (for instance, they might be truncated). Even so, you might want of course want to use them. There may also be a day transition problem (see section 10.7.2). As a last resort, therefore, you can carry out the alignment by brute force, simply assuming an offset: • On the Method tab, choose Assume static offset time and enter a value in the box. (The offsets obtained for the successfully aligned files should still be a good clue.) Click Start. The remaining files will then be aligned unconditionally with the logfile according to the chosen offset. You might also prefer to use this method if you have already determined the offset outside TEMS Investigation. Why the Manual Steps? You may ask why the offset that has been reliably determined for some uplink files is not automatically assumed for the other files (for which the algorithm has initially failed). After all, this would eliminate the need for intervention by the user. The answer is that it has been thought safest to give a warning as soon as something goes wrong, and leave it to the user to decide what to do next with the concerned files. As already noted, they might not belong with the logfile at all, or they may be damaged and possibly uninterpretable. 10.7.4. Accuracy of the Alignment Note: This section is to a great extent MTR file specific. NT11-20502 91 TEMS Investigation 13.1 User’s Manual There are limits to the accuracy that can be achieved in time-aligning the uplink files. The accuracy is affected by the following factors: • The time offset for an uplink file is computed as the average of the offsets for all characteristic events detected in the call (call start, call end, handovers, etc.). Therefore, the longer the call, the more reliable the offset, and vice versa. • Measurement reports in MTR files are not tagged with time-of-day information, but merely with a counter that is reset after each handover. This may have the effect that the MTR measurement reports are imperfectly synchronized with the measurement reports from the phone. 10.7.5. Example Suppose that we want to merge the following files: 00.axe 19.axe 02.axe 20.axe 18.axe 21.axe Uplink files logfile.log TEMS logfile We do not know anything about the offset, and therefore we first run the automatic algorithm without specifying any bounds: 92 Chapter 10. Logfiles The following result is obtained: The outcome is indicated for each uplink file: • A time indication after the file name means that the file was successfully matched and merged with the logfile. The time is the offset determined for this file. Here we see that files 02, 18, and 20 were successfully matched. • “ambiguous” means that several good matches were found, and it was impossible to determine which of them is correct (here, files 19 and 21). • “no match” means that the uplink file matched nothing in the logfile (here, 00). In the last two cases the merge has failed. File 00 most probably does not belong with the logfile at all, and in any case it cannot be aligned using the algorithm. For files 19 and 21, on the other hand, it should be possible to find NT11-20502 93 TEMS Investigation 13.1 User’s Manual a single match by specifying bounds on the offset. The offsets computed for the files 02, 18, 20 suggest a value close to –1570 seconds, so we fill in the dialog as follows: Running the algorithm once more gives Files 19 and 21 could now be aligned unambiguously, and the procedure is finished (file 00 must be discarded in the context). 94 Chapter 10. Logfiles 10.8. Generating Logfile Reports Note: Reporting functions are also available in TEMS Discovery. From one or several logfiles you can generate a report in HTML format which summarizes the data in the logfiles. For full details of logfile report contents and format, see the Technical Reference, chapter 8. • The logfiles to be included in the report cannot be open while the report is generated. If one of these files is currently open, close it. • If any external devices are activated, deactivate them. This is necessary in order for the report generation to work properly. To prepare a logfile report, click the Generate Report button on the Report toolbar. This dialog appears: • First, choose the logfile or logfiles on which to base the report. Click Add and browse for the files. Those that you choose are listed in the Files box. • Specify an output directory for the report. Enter a path, or click the button labeled “...” to browse your file system. • Now click Properties to assemble the contents of the report. A multi-tab dialog appears. NT11-20502 95 TEMS Investigation 13.1 User’s Manual 10.8.1. IE Tab The report can compare information element values with thresholds. It will contain statistics of the type “Percentage of measurement points with RxLev Full below –100 dBm”. All thresholded information elements listed will also have their distributions visualized in bar charts. A number of thresholds are predefined in the dialog, as is seen in the above screenshot; you can also define your own thresholds. Check those that you wish to use, and uncheck the others. Check a cellular technology to use all thresholds defined for that technology. Each item in the list represents a set of two thresholds for an information element value: or Whether peaks or dips are counted depends on the information element and cannot be changed. In the report, it is indicated for each threshold • 96 how many times the value of the information element has crossed the threshold (changed from a more normal value to a more extreme one) Chapter 10. Logfiles • how long these peaks/dips have lasted on average. Adding User-defined Thresholds • To add a pair of thresholds, click the Add button. • Choose an information element. • Choose an argument (where applicable). • Specify the two thresholds. • Click Add to add this threshold pair to the list and keep the Add Threshold dialog open. • Click OK to add this threshold pair to the list and close the Add Threshold dialog. Editing Thresholds • To edit a threshold, double-click it and enter the desired new value. Editing Arguments • To edit the argument of the information element (where one exists), double-click it and enter the desired new value. Deleting Thresholds • To delete a threshold pair, select it and click the Delete button. Customizing Value Ranges The Ranges column is used to customize the drawing of distribution charts (see the Technical Reference, section 8.4). By default no ranges are set, and the distribution charts are drawn in a preconfigured manner. If you set up your own value ranges for an IE, the distribution chart will be drawn with one bar for each range: NT11-20502 97 TEMS Investigation 13.1 User’s Manual • Select the desired information element. • Click the Edit Range button. • Modify the value ranges in the dialog that appears. 10.8.2. Events Tab The report has a section with event statistics. On this tab you choose what event types to include in these statistics. • Check the events you want to include, and leave the rest unchecked. Press Ctrl + A to select all events; press Ctrl + A again to deselect all events. Note: The ranking of cells in the report (“Worst Cell Indication”) is partially based on the number of events occurring in the cell. The algorithm counts all events, not only those signifying failures. Therefore, in order for the cell ranking to make sense, only failure events should be checked in this step. This is also the default setting. 10.8.3. • Mobiles Tab Check the external devices whose data you want to include in the report. By default all device channels (“MS1”, “DC1”, “MS2”, etc.) used to record the logfile will be checked. GPS data, if available, is included implicitly. 10.8.4. Scanned Channels Tab Note: The settings on this tab are applicable only if your logfiles contain scan data. 98 Chapter 10. Logfiles In this step you choose what scan data to present in the report. • First, click the Define channels button in order to populate the “Available” box. This dialog appears: • In the combo box at the top, select the band of interest. • – For WCDMA, specify a UARFCN range under “Lower limit” and “Upper limit”, then check the desired scrambling codes in the list box. The scrambling code selection applies to all UARFCNs within the chosen range. – For GSM, just check the desired ARFCNs in the list box. – For CDMA, specify an RF channel range under “Lower limit” and “Upper limit”, then check the desired PNs in the list box. The PN selection applies to all RF channels within the chosen range. – For TD-SCDMA, specify a UARFCN range under “Lower limit” and “Upper limit”, then check the desired CPIs in the list box. The CPI selection applies to all UARFCNs within the chosen range. – For LTE, specify an EARFCN range under “Lower limit” and “Upper limit”, then check the desired Cell Identities in the list box. The cell selection applies to all EARFCNs within the chosen range. Click OK to return to the Report Properties dialog. It might look like this: NT11-20502 99 TEMS Investigation 13.1 User’s Manual The “Available” list box now lists the selected channels in the following format: • GSM: m[p] means ARFCN m on the p MHz band. • WCDMA: m[f] means scrambling code m on UARFCN f. • CDMA: m[f] means PN m on RF channel f. • TD-SCDMA: m[f] means CPI m on UARFCN f. • LTE: m[f] means Cell Identity m on EARFCN f. • Move the items that you wish to present from the Available box to the Selected box. For each selected item, the report will contain RxLev/code power statistics (mean, median, min, max) and a bar chart. The averaging takes place in the mW domain. 10.8.5. User Details Tab Here you can type a user name and a report number which will be printed in the report header. 100 Chapter 10. Logfiles 10.8.6. Saving and Loading Report Setups When you are done specifying the report contents, you may want to save the setup for future use. • In the Report Properties dialog, click Save and store the file where appropriate. The file extension is .rpt. • To load a previously saved setup into the Report Properties dialog, click Load and locate the setup file. 10.8.7. • Generating the Report In the Report wizard, click Finish. The report will be stored under [My] Documents\TEMS Product Files\TEMS Investigation 13.1\GeneratedReports. 10.8.8. Report Contents The logfile report has the following main sections (see the Technical Reference, chapter 8 for a complete description): • Header: Date, Time, Prepared by • Logfile information: Logfile names and used equipment • 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. NT11-20502 101 TEMS Investigation 13.1 User’s Manual 11. Scanning: General 11.1. Setting Up a Scan Scanning tasks are set up from the Navigator’s Equipment tab; specifically, from the Activities subtab in the bottom pane. • First, to be able to access the scanning configuration dialogs, you need to activate the device you want to scan with (if it is not already activated). See chapter 7. • Once the device has been activated, the Activities tab is populated. For a scanning-capable device, the available activities will include a Scan item. Expand this node to expose a list of the scanning methods that this device supports. • Right-click the scanning method you want to use, and select Configuration Sets. This opens a dialog where you define a setup for the selected scanning method. The dialog contents depend on the technology and scanning method chosen as well as on the make and model of the scanning device. All details are covered in subsequent chapters (12–17). 11.2. Performing a Scan With suitable configuration sets already defined, here is how to initiate a scan: • On the Navigator’s Equipment tab, select the device to scan with. • On the Activities subtab, expand the Scan node. • Right-click the scanning method you want to use, and from the context menu select the desired configuration set among those in existence. 102 Chapter 11. Scanning: General • Right-click the scanning method item again, and from the context menu select Start. While the scan is ongoing, it will be indicated in the top pane of the Equipment tab for the device that is busy scanning. It is possible to scan with several devices simultaneously. • To stop scanning, go to the Activities subtab again. Under the Scan node, right-click the scanning method being executed, and select Stop. 11.3. Recording Scan Data To record scan data, create a new logfile as described in section 10.1. 11.4. Replaying Scan Data If you are replaying a logfile with scan data, you may want to replay the file slowly in order to see clearly what is happening. The replay speed is set from the Logfile menu (see section 10.2.1). 11.5. Presenting Scan Data The output of scans is primarily intended to be displayed in a suite of readymade bar charts and other windows. The scanning presentation windows are fully synchronized with the rest of the application, and the output from all of these can be displayed in parallel. However, since all scan data is available in information elements, you are free to present it in any presentation window. For example, scan data can be displayed in status windows of your own design. How to build a status window is covered in chapter 22. The information elements of interest are all found in the Information Elements and Events volume. 11.6. • Technical Data on Scanning Devices A Sony Ericsson phone cannot act as a regular phone while it is scanning. It cannot engage in voice/video calls or data services during this time. NT11-20502 103 TEMS Investigation 13.1 User’s Manual • Frequency band support is determined by the scanning device and by the antennas. For band support in connectable scanning devices, see the Getting Started Manual, section 10.1.4. • Detailed data on the scanning capabilities and performance of Sony Ericsson phones is provided in the technical paper “Scanning with Sony Ericsson TEMS Devices”, included on the installation CD in the subdirectory Documents. • Some technical data on PCTel scanners and antennas used with them is provided in the Getting Started Manual, section 10.7.2.5. For further information on third-party scanning devices, please consult documentation from the respective suppliers. 11.7. Notes on Scanning Methods Within a cellular technology, scanning methods are conceptually independent, and they can be run concurrently by PCTel scanners. Only the scanner measurement capacity places a limit on the possibilities of handling several scanning tasks in parallel. For example, a WCDMA SCH timeslot scan at maximum resolution may require the full resources of the PCTel scanner, so that it cannot perform any other tasks at the same time. A PCTel scanner’s measurement capacity is indicated as a number of measurement points. As you set up the scanning tasks, you are continuously notified in the setup dialog of how many measurement points that remain. For a DRT scanner, TEMS Investigation sets a limit on the amount of scan data it will accept. (The DRT scanner can produce more data than this, but the data volume would then become unmanageably large.) Again the limit is expressed in terms of measurement points, and the setup dialog keeps track of the number of measurement points that remain to be allocated. Sony Ericsson phones and SRUs do not handle concurrent execution of multiple scanning methods. 11.8. Notes on GPS Units in Scanners The internal GPS in a scanner equipped with such a device will deliver data only if it is selected as Preferred GPS and activated in TEMS Investigation. See section 7.5. 104 Chapter 12. GSM Scanning 12. 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. For a full listing of connectable scanners with GSM scanning capability, see the Getting Started Manual, section 10.1.4.1. A note on terminology: GSM radio frequency carriers are sometimes referred to below as channels for simplicity, although this is a slight abuse of the term. 12.1. Scanning Methods and Capabilities TEMS Investigation offers these GSM scanning methods, supported using the various devices as indicated. Please note that for a scanning method to be actually available in TEMS Investigation, the device must have been purchased with the relevant option (wherever applicable). 1. For specifics, see Information Elements and Events, section 4.1. 2. Built on Ericsson hardware. See the Getting Started Manual, section 10.1.4.1. NT11-20502 105 Section Ref. PCTel SeeGull SRU GSM Scanning Capability/ Scanning Device Sony Ericsson TEMS Investigation 13.1 User’s Manual RSSI scanning, static ARFCN set 12.2 RSSI scanning: BSIC decoding 12.2 RSSI scanning: C/I measurement 12.2.3 RSSI scanning: Sys Info decoding 12.2.3 Spectrum analysis 12.3 12.2. RSSI Scanning 12.2.1. Setup of RSSI Scan: General Settings Technology Set this to “GSM” for GSM scanning. Band GSM frequency band or bands to scan. Channels ARFCNs to scan on the selected band. Select all channels to scan the entire band. There is no limit to the selectable number of channels. 12.2.2. BSIC 106 Setup of RSSI Scan: Sony Ericsson, SRU Setting this to Yes causes the phone to decode the Base Station Identity Code whenever possible. It should be noted that BSIC decoding is computationally costly and considerably reduces the sample rate of the scan. Chapter 12. GSM Scanning 12.2.3. Setup of RSSI Scan: PCTel SeeGull Bandwidth Select whether to perform a regular GSM signal scan (“Normal”) or a Continuous Wave scan (“CW”). This setting applies to all channels you select for scanning. It is not possible to specify the type of scan for each channel separately. Regardless of the choice made here, the measurements are extracted to the same information elements (Scanned RxLev, etc. in the “GSM” category). Remaining Measurement Points See section 11.7. BSIC Setting this to Yes causes the phone to decode the Base Station Identity Code whenever possible. It should be noted that BSIC decoding is computationally costly and considerably reduces the sample rate of the scan. PCTel scanners supplied with older versions of TEMS Investigation may lack BSIC decoding capability. Check the Device Inquiry mode report from the scanner to find out whether it is capable of decoding BSIC. C/I Measurements NT11-20502 Setting this to Yes causes a subset of the “C/I” information elements to be updated, as described in Information Elements and Events, section 3.1. PCTel scanners can be purchased with or without the C/I scanning function enabled; check the Device Inquiry mode report from the scanner to find out whether it has this capability (“GSM BCCH C/I”). If available, the function can be turned on and off in the dialog. 107 TEMS Investigation 13.1 User’s Manual SI on Strongest 12.2.4. Setting this to Yes causes the scanner to decode System Information messages for the strongest cell. The scanner must suspend the regular scan in order to read System Information, and this is therefore done only once each time the strongest cell changes. Whenever System Information is read, the information element Neighbor (SI) ARFCN is updated. 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. The bottom chart by default shows all scanned channels in order of ascending ARFCN. Regarding the bar chart window itself, see chapter 28. Scan data can also be presented in status windows. There is no predefined status window for this purpose, but you can design one yourself: see chapter 22. The information elements of interest are those in Information Elements and Events, section 3.1 that are associated with scanning. 108 Chapter 12. GSM Scanning 12.3. Spectrum Analysis The setup for spectrum analysis is the same as for WCDMA (except that Technology = GSM). See section 13.5.1. NT11-20502 109 TEMS Investigation 13.1 User’s Manual 13. 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. For a full listing of connectable devices with WCDMA scanning capability, see the Getting Started Manual, section 10.1.4.1. 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, chapter 14. 13.1. Scanning Methods and Capabilities TEMS Investigation offers these WCDMA scanning methods, supported using the various devices as indicated. Please note that for a scanning method to be actually available in TEMS Investigation, the device must have been purchased with the relevant option (wherever applicable). 110 Section Ref. R&S TSMW PCTel SeeGull MX PCTel SeeGull EX PCTel SeeGull LX PCTel PCT Anritsu ML8780A Anritsu ML8720 WCDMA Scanning Capability/ Scanning Device Sony Ericsson, SRU Chapter 13. WCDMA Scanning Pilot scanning, static SC set 13.2 Pilot scanning, Top N 13.2 Pilot: SIB decoding (continuous) 13.2 Pilot: SIB decoding (snapshot) 13.2.2 Pilot: High Speed/High Dynamic 13.2.3 Pilot: P-SCH + S-SCH Pilot: Max. no. of UARFCNs 13.2 12 1 8 4 12 12 12 12 13.2 SCH timeslot scanning 13.3 RSSI scanning 13.4 Spectrum analysis 13.5 Network scanning 13.6 1. Anritsu ML8720: 1 or 2 depending on physical configuration. NT11-20502 111 TEMS Investigation 13.1 User’s Manual 13.2. Pilot Scanning (with SCH Scanning) This method scans CPICH control channels, scrambled with cell-specific scrambling codes. Several UARFCNs can be scanned at a time. UARFCNs and scrambling codes are selected independently of one another. Where supported, the same method also scans primary and secondary synchronization channels (P-SCH, S-SCH). 13.2.1. Setup of Pilot Scan: General Technology Always “WCDMA” for WCDMA scanning. Band WCDMA frequency band to scan. Channels Here you set the UARFCNs of the frequencies on which to scan the CPICH. The allowed range is dependent on the frequency band. 13.2.2. Setup of Pilot Scan: Sony Ericsson, SRU Setup options are as follows: • Scan selected: A user-defined, static set of scrambling codes (common to all UARFCNs) is scanned. Optional snapshot SIB decoding. • BCH scanning: User-defined, static set of scrambling codes (common to all UARFCNs) scanned. Unconditional and continuous SIB decoding. • Scan strongest: Strongest scrambling codes scanned (“Top N”). Optional snapshot SIB decoding. The choice is made under Type of Scanning in the setup dialog. 112 Chapter 13. WCDMA Scanning Type of Scanning See also the introduction of this section. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under Channels. • BCH scanning: If you choose this option, you select scrambling codes in the same way as for Scan selected, and the same scan data will be collected. However, the updating frequency will be considerably lower, and the sensitivity of the scrambling code detection may be lower as well. The processing time freed up in this way is instead used to continuously decode System Information Blocks (SIBs). This decoding is furthermore continuous, unlike that governed by the System Information option (which see). • Cell Noise Floor Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs. The scanner automatically finds the strongest scrambling codes. Ec/Io threshold for accepting a signal on the CPICH as a detected cell. The threshold should be adjusted to ensure detection of cells actually present while keeping the false detection rate down. The default is –26 dB. Scan Strongest This field is enabled if you have chosen “Scan strongest” under Type of Scanning. To scan the N strongest scrambling codes, enter the value N here (N ≤ 40). Scrambling Codes This field is enabled if you have chosen “Scan selected” or “BCH scanning” under Type of Scanning. Enter the scrambling codes you want to scan. NT11-20502 113 TEMS Investigation 13.1 User’s Manual System Information If this option is set to Yes for Scan selected or Scan strongest, 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). On completing the SIB decoding, the phone reverts to regular pilot scanning. If the strongest cell does not change within two minutes, SIBs will be decoded again for that cell. For BCH scanning, this option is always set to Yes. It then refers not to snapshot SIB decoding but to the continuous SIB decoding performed by that method. 13.2.3. Setup of Pilot Scan: PCTel The set of scrambling codes to scan on each UARFCN is composed in one of two ways: • user-defined, static set of scrambling codes, common to all UARFCNs • strongest scrambling codes (“Top N”) What settings are supported by the various PCTel SeeGull models appears from the table in section 13.1. Only settings supported by the connected scanner are displayed in the dialog. Type of Scanning Number of Pilots 114 See also the introduction of this section. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under Channels. The same scrambling codes will be scanned on the CPICH and on the P-SCH and S-SCH. Up to 128 scrambling codes can be selected. • Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs. The scanner automatically finds the strongest scrambling codes. This field appears if Type of Scanning is set to “Scan strongest”. To scan the N strongest scrambling codes, enter the value N here (N ≤ 32). Chapter 13. WCDMA Scanning Selected Numbers This field appears if Type of Scanning is set to “Scan selected”. Enter the scrambling codes you want to scan. PN Threshold This is a signal code power threshold (in dB) used for the Aggregate Ec/Io and Delay Spread measurements (see section 13.2.7). If the PN threshold is set too low, the Aggregate Ec/Io and Delay Spread values will be affected by random noise more than may be desired. By raising the threshold you reduce the influence of random noise correlations, and you will thus be able to discern multipath and fading effects more accurately. The setting –20 dB is recommended. Remaining Measurement Points See section 11.7. Data Mode It is possible to reduce the amount of data that is presented and recorded: • Full means no reduction. • Sub means that some data is not presented or recorded (compare sections 13.2.8 and 13.2.10). It should be noted that choosing “Sub” results in a much faster updating of scan presentations. The precise meaning of “Sub” depends on the scope of the scan: SIR NT11-20502 • For “Scan selected”, Time Offset, P-SCH Ec/Io, S-SCH Ec/Io, and Rake Finger Count are excluded, as is SIR. (The “SIR” field is disabled in this case.) • For “Scan strongest”, only P-SCH Ec/Io and S-SCH Ec/Io are excluded. Setting this to Yes causes the scanner to deliver the information elements “Sc ... SIR”. 115 TEMS Investigation 13.1 User’s Manual System Information Set this to Yes to decode System Information blocks (continuously). With this option selected, a maximum of 16 scrambling codes can be scanned. From the SIB decoding are extracted the information elements “Sc 1st (2nd, 3rd, 4th) Intra-freq Cells”. Measurement Mode Dwelling Time 13.2.4. There are two choices, High Speed and High Dynamic. These are two algorithms with different priorities: • High Dynamic puts the emphasis on accuracy. Each sample reported by the scanner is typically based on a measurement 20 ms in length. • High Speed is faster and accordingly less accurate. Each reported sample is typically based on a 10 ms measurement. The length of time the scanner dwells on each scrambling code (cell) trying to decode System Information blocks, before moving on to the next cell. Given as a multiple of 40 ms. The default is 50 = 2000 ms. Setup of Pilot Scan: Rohde & Schwarz Measurement Mode High Speed or High Dynamic. Measurement Rate (MHz) Average measurement rate shared between all selected channels. RF Front-end Front-end (processor) on which to schedule measurement. The measurement tasks are manually distributed on the two built-in front-ends. Resource Allocation (%) Resources allocated on the specified front-end. 116 These are two algorithms with different priorities. High Dynamic puts the emphasis on accuracy, whereas High Speed is faster and accordingly less accurate. Chapter 13. WCDMA Scanning Resource Available (%) 13.2.5. Read-only field indicating the remaining available resources on the processor selected under RF Frontend. Setup of Pilot Scan: Anritsu The set of scrambling codes to scan on a UARFCN is composed in one of two ways: • user-defined, static set of scrambling codes, common to all UARFCNs, or • strongest scrambling codes (“Top N”) Type of Scanning See also the introduction of this section. • Scan selected: Choose this to scan a static set of scrambling codes on all frequencies defined under “UARFCN” below. The same scrambling codes will be scanned on the CPICH and on the P-SCH and S-SCH. Up to 32 scrambling codes can be selected. (ML8720 only) • Scan strongest: Choose this to have the N strongest scrambling codes reported from the chosen UARFCNs (“Top N”). The scanner automatically finds the strongest scrambling codes. Number of Pilots This field appears if Type of scanning is set to “Scan strongest”. To scan the N strongest scrambling codes, enter the value N here. The maximum number of pilots that can be scanned is equal to floor(40/Nch), where Nch is the number of UARFCNs entered under Channels. For example, if 3 UARFCNs are selected, up to 13 SCs can be scanned on each. Selective Level 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. The default is 4 dB. NT11-20502 117 TEMS Investigation 13.1 User’s Manual Rake Threshold This threshold (value in dB) determines, for a given scrambling code, 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. Setting the threshold at n dB means that a signal path must not be more than n dB weaker than the strongest one. In other words, this threshold governs how many Rake fingers will contribute to the signal. The default is 20 dB. Search Method (ML8720) This setting governs the choice of cell search method in Top N scan mode (“Scan strongest” option). • If P-CPICH is selected, only CPICH channels will be scanned to find scrambling codes. (For all scrambling codes detected in this way, however, the scanner will measure and report on the P-SCH and S-SCH as well.) This mode is useful especially for troubleshooting of transmitters. The P-CPICH mode cannot be used if two UARFCNs are to be scanned. If you select two UARFCNs, the P-CPICH radio button is grayed. • BCH Scan (ML8780A) 13.2.6. If SCH is selected, the scanner will search for scrambling codes that use P-SCH and S-SCH. This is more suitable for drive testing and is the default setting in TEMS Investigation. If you are scanning two UARFCNs it is the only option, as explained above. If selected, the scanner will perform continuous SIB decoding. This can only be done on one UARFCN at a time (only one is selectable under Channels when the BCH Scan option is set). Presentation: General Pilot scan data is presented in • the CPICH Scan bar charts (section 13.2.7) • the CPICH Scan Data status window (section 13.2.8) • the CPICH Scan line charts (section 13.2.9) 118 Chapter 13. WCDMA Scanning Synchronization channels are presented in the Synch Channels window (section 13.2.10). 13.2.7. Presentation: “CPICH Scan” Bar Charts The CPICH Scan bar charts present CPICH scan data. One predefined bar chart is provided for each UMTS frequency scanned. Each bar chart by default presents peak Ec/Io (see section 13.2.8) for each scrambling code found. Regarding data sorting, see section 13.2.13.1. The updating rate is chiefly dependent on the number of live signals encountered in the network. For a manually selected set of scrambling codes, the updating rate is also greatly affected by the size of this set, whereas for the “Top N” scan the number N is only marginally important (since all scrambling codes have to be searched regardless of N). 13.2.8. 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. They differ only with respect to sorting: CPICH Data is sorted first by UARFCN, whereas CPICH Best UARFCN Data is sorted by Aggr Ec/Io regardless of UARFCN. The columns have the following meanings: NT11-20502 119 TEMS Investigation 13.1 User’s Manual SC Scrambling code number. Peak Ec/Io The peak code power of the scrambling code (Ec) relative to the total signal power in the channel (Io), i.e. the difference between them in dB. Peak Ec The peak code power of the scrambling code in dBm. Ag Ec/Io The aggregate code power of the scrambling code relative to the total signal power in the channel (Io), i.e. the difference between them in dB. Ag Ec The aggregate code power of the scrambling code in dBm. 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 13.2.3). Aggr–Peak Ec Difference in dB between the aggregate code power (Ag Ec) and peak code power (Peak Ec), i.e. Rake receiver gain. Delay Spread Time in chips from the first to the last Ec/Io peak that is above the PN threshold. This is a measure of the signal spreading due to multipath propagation. RFC Rake finger count, i.e. the number of Ec/Io peaks (multipath components) that are above the PN threshold. Time Offset The time offset of the radio frame on the CPICH, given in chips from a 1/100th second time mark aligned with GPS time. Ranges from 0 to 38399. SIR Signal-to-interference ratio of the scrambling code in dB. Measured on DPCCH. All of these are identical with information elements having similar names but beginning with “Sc”. See Information Elements and Events, section 3.2. 13.2.9. Presentation: “CPICH Scan” Line Charts The default configuration of this window is as follows: 120 Chapter 13. WCDMA Scanning Chart Panes The charts present the five strongest scrambling codes. The top chart shows Aggr Ec (in dBm) and the bottom chart shows Aggr Ec/Io (in dB). Legend Pane The Legend pane (bottom left) glosses either of the two charts. To switch to the other chart, right-click and choose the desired chart from the context menu. Additional Information Pane The Additional Information pane (bottom right) shows the CPICH pilot pollution situation.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. Please note that the IEs described here are no longer present by default in this window; you need to add them manually. NT11-20502 121 TEMS Investigation 13.1 User’s Manual strong compared to the strongest SC. The relative code power threshold is determined by the argument within square brackets []. 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. Example: If the argument is 3 (default value), all SCs with a code power not more than 3 dB below that of the strongest SC will be counted. In the above figure, there are three such SCs, so the active set is judged to have a total of four possible members. • Other/Own ... : These are estimated ratios between polluting signal power and desired signal power, 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. The four “Other/Own” elements represent the assumptions that there is desired signal power on 1, 2, 3, and 4 SCs respectively. For “Max N SCs”, “Own” is the sum of the code powers of the N strongest possible active set members, if the number of possible members is at least N; otherwise it is simply the sum of the code powers of all possible active set members. “Other” is the sum of the code powers of all remaining SCs. In the example below, there are three other SCs reaching above the threshold which is set relative to the strongest SC. However, for “Max 2 SCs”, only the strongest of the three is included in “Own”. SC code power Strongest SC Distance to threshold, indicated by argument Threshold for possible AS members (which are included in “Own”) Own power, max 2 SCs SC Other power, max 2 SCs The “Other/Own” ratios are of course calculated from absolute code power values (i.e. Ec values in mW). 122 Chapter 13. WCDMA Scanning Note: The arguments should be kept the same for all five information elements. It is of course possible to set each argument to any of the permissible values, but with different arguments for different elements you cannot really draw any useful conclusions. 13.2.10. Presentation: Synch Channel Data Window This window presents scan data on the synchronization channels P-SCH and S-SCH, obtained with the Pilot scanning method. SC Scrambling code number. P-SCH Ec The peak power of the Primary Synchronization Channel, P-SCH (in dBm). P-SCH Ec/Io The peak power of the P-SCH (Ec) relative to the total signal power in the channel (Io), i.e. the difference between them in dB. S-SCH Ec The peak power of the Secondary Synchronization Channel, S-SCH (in dBm). S-SCH Ec/Io The peak power of the S-SCH (Ec) relative to the total signal power in the channel (Io), i.e. the difference between them in dB. By default the scrambling codes are sorted by signal power with the strongest on top. The presented data can be freely rearranged, as described in section 22.3, “Changing Status Window Properties”. NT11-20502 123 TEMS Investigation 13.1 User’s Manual 13.2.11. Presentation: “Finger Info” Status Windows These windows present Rake finger information obtained during Pilot scanning. For definitions of the information elements, see Information Elements and Events, section 3.2. 13.2.12. Presentation: BCH Scanning All scan data collected using the options Scan selected and Scan strongest are obtained for BCH scanning also (though less frequently); see sections 13.2.7–13.2.11 above regarding the presentation of this data. No special presentation windows are provided for BCH scanning. However, decoded System Information Blocks are output in the Layer 3 Messages window at a greatly enhanced rate. 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. See Information Elements and Events, section 7.2. Another piece of data found in SIBs is an uplink interference measurement. This is particularly interesting for HSUPA, where the guiding principle of scheduling is to provide (as far as possible) all UEs with all the resources they need while also making sure that the total uplink interference does not exceed the accepted maximum. The uplink interference measurements can of course be inspected in the plain-text SIB decoding, but they are also extracted as information elements; see Information Elements and Events, section 3.2. 13.2.13. Customizing the Presentation 13.2.13.1. Sorting of Scrambling Codes You can sort scrambling codes in scanning information elements in a number of different ways. The sorting order is set in the General window. • Open the General window from the Navigator. • Double-click the item “WCDMA”. A dialog appears with these sorting options: • Sort by decreasing Aggr Ec/Io (default) • Sort by increasing Aggr Ec/Io 124 Chapter 13. WCDMA Scanning • Sort by fixed position: Scrambling codes are sorted by index and are always assigned the same argument indices, that is, scrambling code n is always found at argument index n + 1. • Sort by scrambling code: Scrambling codes are sorted by index; the code with the lowest index appears at argument index 1, the code with the next higher index appears at argument index 2, etc. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events, section 3.2) is fixed and is not affected by the General window settings. 13.2.13.2. Presenting Scrambling Codes from Multiple UARFCNs In the “Sc Best” information elements, all scrambling codes found on all UMTS frequencies are collected in a single array. These elements are sorted by signal strength (Aggr Ec/Io) in descending order, and this sorting order is unchangeable. Use these elements in order to view scan data from several UARFCNs in one window. 13.3. SCH Timeslot Scanning This method scans timeslot-length intervals, i.e. intervals 2560 chips long, on a Primary Synchronization Channel (P-SCH). It is useful for monitoring synchronization reference signals sent on this channel. 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 13.2). 13.3.1. 13.3.1.1. Setup of SCH Timeslot Scan General Settings Technology Always “WCDMA” for WCDMA scanning. Band WCDMA frequency band to scan. Channels UARFCN to scan. NT11-20502 125 TEMS Investigation 13.1 User’s Manual Center Frequency 13.3.1.2. The center frequency of the UARFCN chosen. Context Settings Compression Rate Remaining Measurement Points 13.3.2. The time resolution of the scan: • Every means that a power value is reported for every chip in the timeslot. • Every 2, etc. means that the peak (not average) power is reported for successive segments 2, 4, or 8 chips in length. See section 11.7. Presentation: SCH Timeslot Scan Bar Chart The bar chart displays an Es/Io trace for the latest timeslot scanned (2560 chips). Each SCH signal will show up as a spike on the trace, the height of the spike reflecting the strength of the signal in terms of Es/Io. The legend pane gives 126 Chapter 13. WCDMA Scanning Es/Io for each chip, or peak Es/Io for every 2, 4, or 8 chips, depending on the setup; see section 13.3.1. Since the SCH signals are repeated every timeslot, the spikes will normally remain in the same positions as the trace is updated. The updating rate is dependent on the compression rate and on network conditions. However, if the compression rate is set to “Every 4”, the updating interval will be on the order of 1 s. The position of a spike shows at what point a new timeslot begins in the current transmission. Provided that the base station clock is synchronized with GPS time, the T_Cell parameter can be determined: the spike will be positioned approximately at T_Cell + 140 chips, the offset being due to delay in the scanner. If the base station is not synchronized with GPS time, however, no conclusions can be drawn about the value of T_Cell. In a WCDMA cell with multiple sectors, each sector will transmit/receive at a different time offset (e.g. 0, 256, and 512 chips). The SCH timeslot scan will then display multiple spikes within a timeslot, one for each sector. From this the time separation between the sectors can be determined. In the lower right pane, 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. • “Time diff 2-3” indicates the time separation in chips between the second strongest peak and the third strongest. These parameters are identical with the information elements SCH TS Sc Time Diff 1-2 and SCH TS Sc Time Diff 2-3; see Information Elements and Events, section 3.2. Determining the time separation naturally does not require synchronization of the base station with GPS time. 13.4. RSSI Scanning 13.4.1. Setup of RSSI Scan 13.4.1.1. General Settings Technology Always “WCDMA” for WCDMA scanning. Band WCDMA frequency band to scan. NT11-20502 127 TEMS Investigation 13.1 User’s Manual Channels UARFCNs to scan (up to 255). The allowed UARFCN range is dependent on the band. 13.4.1.2. Context Settings Bandwidth Select whether to perform a regular WCDMA signal scan (“Normal”) or a Continuous Wave scan (“CW”). This setting applies to all channels you select for scanning. Regardless of the choice made here, the measurements are extracted to the same information elements (CW Sc RSSI, etc. in the “WCDMA” category). Remaining Measurement Points 13.4.2. See section 11.7. Presentation: RSSI Scan Bar Chart This bar chart displays RSSI for each UARFCN scanned. 128 Chapter 13. WCDMA Scanning 13.5. Spectrum Analysis This scanning method shows downlink signal strength as a function of frequency. 13.5.1. Setup of Spectrum Analysis Scan 13.5.1.1. General Settings Technology Choose “WCDMA” for WCDMA scanning. Band WCDMA frequency band to scan. Start Frequency Low end of the frequency range to be swept by the scan. Given in MHz. Stop Frequency High end of the frequency range to be swept by the scan. Given in MHz. Resolution Bandwidth Interval between successive scan samples in kHz, the highest selectable resolution being 5 kHz. In the presentation window, the legend pane will list all samples; the chart, on the other hand, can of course only distinguish the samples as far as the screen resolution permits. 13.5.1.2. Context Settings Number of Sweeps The number of sweeps on which to base the presented average RSSI. The minimum number is 1, and the maximum is 16. Remaining Measurement Points See section 11.7. NT11-20502 Note that the spectrum analysis is prone to consume a large number of measurement points. Adapt the resolution to the width of the frequency range. 129 TEMS Investigation 13.1 User’s Manual 13.5.2. Presentation: Spectrum Analysis Bar Charts Two charts are provided, one for the downlink (Spectrum Analysis Bar Chart) and one for the uplink (Spectrum Analysis Uplink Bar Chart).1 They both display RSSI as a function of frequency. 13.6. Network Scanning This function is highly useful for obtaining a bird’s-eye view of an unfamiliar WCDMA radio environment. It will detect WCDMA carriers (UARFCNs) that are in use on each of the WCDMA bands 2100 MHz, 1900 MHz, 850 MHz. On each carrier, one cell (scrambling code) is detected and presented. In network scanning mode it is also possible to detect inappropriate allocation of UARFCNs resulting in carrier overlap. A mobile phone in regular phone mode, once it has found a WCDMA carrier, automatically assumes that there are no further UARFCNs within ±3 MHz of the detected carrier and is therefore unable to spot overlapping carriers. In contrast, a Sony Ericsson phone in scan mode is usually able to identify all carriers, overlapping or not, thus allowing faulty frequency allocations to be easily found and rectified. 1. Uplink spectrum analysis is currently not supported by any currently connectable devices, but the chart is retained to allow displaying of such data from old logfiles. 130 Chapter 13. WCDMA Scanning 13.6.1. Setup of Network Scan 13.6.1.1. General Settings Technology 13.6.1.2. Choose “WCDMA” for WCDMA scanning. UARFCN Ranges (“Interval 1, 2, 3”) You can set up three separate UARFCN ranges (Interval 1, 2, 3) to scan in the network. Each range can be located on any of the supported frequency bands. Interval <n> enabled Set the flag to Yes if you want to define this UARFCN range. Band If you want the UARFCN range to be identical to an entire WCDMA frequency band, select that band here. Custom range; From, To If you want the UARFCN range to consist of a portion of a band, set Custom range to Yes. Additional fields “From” and “To” appear, in which you specify the endpoints of the UARFCN range. 13.6.1.3. Include additional channels Context Settings Check this to include additional channels on the 1900 or 850 MHz band. Additional channels have UARFCNs that are completely different from the general channels. (See  3GPP 25.101, sections 5.4.3–5.4.4 for details on the two kinds of channel.) If this option is checked, all additional channels that lie within the frequency range you have specified in the dialog (whole band or UARFCN range) will be included in the scan. NT11-20502 131 TEMS Investigation 13.1 User’s Manual Cell Ec/No threshold Ec/No threshold for cell detection within a detected carrier. This threshold should be high enough to minimize the false detection rate, 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, where all cells will be significantly disturbed. The default setting is –26 dB, which should be suitable in most situations. RSSI threshold RSSI threshold for detecting carriers. The default setting is –94 dB, reflecting a trade-off between the desire to detect all networks in operation and the wish to avoid spurious “hits”. Setting the threshold too low results in a very long search time (e.g. several minutes at –100 dB). 13.6.2. Presentation: Network Search Window The result of the network scan is output in the Network Search window. It lists all UARFCNs found, that is, the center frequency of each detected WCDMA carrier. UARFCNs from all WCDMA frequency bands are listed in the same column. One scrambling code (cell) is displayed for each UARFCN. 132 Chapter 14. LTE Scanning 14. 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. For the full range of supported LTE-capable scanners, see the Getting Started Manual, section 10.1.4.2. How to configure the PC and the above scanners for use with TEMS Investigation is covered in the Getting Started Manual, chapters 12–14. (For PCTel, no special preparations are required.) 14.1. Scanning Methods and Capabilities TEMS Investigation offers these LTE scanning methods, supported using the various devices as indicated. Please note that for a scanning method to be actually available in TEMS Investigation, the device must have been purchased with the relevant option (wherever applicable). It is possible to run several of these scanning methods concurrently. NT11-20502 133 Section Ref. R&S TSMW PCTel SeeGull MX PCTel SeeGull EX DRT LTE Scanning Capability/ Scanning Device Andrew i.Scan TEMS Investigation 13.1 User’s Manual LTE signal scan 14.2 RSSI scan 14.3 Spectrum scan 14.4 Enhanced power scan 14.5 14.2. LTE Signal Scanning The LTE air interface uses OFDM as modulation method on the downlink. Synchronization Channels are used for service detection and synchronization, and Reference Signals (RS’s) are used for channel estimation purposes. The LTE signal scan provides the following metrics: • SCH (PCI, PCIG, P-SCH RSSI, S-SCH RSSI, SCHRQ) • RS (RSRP, RSRQ) • CINR (SCH CINR, RS CINR) • CFO • Time Offset 14.2.1. Setup of LTE Signal Scan: General Technology Always “LTE”. Band LTE band to scan. Regarding band support in scanners, see the Getting Started Manual, section 10.1.4.2. 134 Chapter 14. LTE Scanning Channels 14.2.2. EARFCNs to scan within the selected LTE band. Each EARFCN is specified as a number representing the center frequency of the channel. Up to 12 EARFCNs can be selected. Setup of LTE Signal Scan: Andrew Scan Rate Minimum time for scan in ms. Report Threshold Epss/Io detection threshold (i.e. for Primary Synchronization Channel), given in 0.1 dB increments. For example, –6.5 dB is indicated as –65. Min: –240 = –24 dB. Max: 0 = 0 dB. 14.2.3. Setup of LTE Signal Scan: DRT Scan Type Logging Mode • Targeted Scan: Select this if you wish to scan a fixed set of cells. Specify the cells under Cell Index List. • Top N: Select this if you wish to scan the strongest cells. Set the number of cells the scanner should report under Top N. When using a DRT scanner purchased with TEMS Investigation, the scan data is always recorded in regular TEMS Investigation logfiles (*.log), regardless of how this parameter is set. If you are using a DRT scanner with the optional multimedia card (MMC), you can optionally record a logfile with scan data on the MMC as well. (This logging has got nothing to do with TEMS Investigation.) The MMC must have been formatted and inserted into the scanner before the scanner is powered on. NT11-20502 • MMC: Log to MMC. • None: Do not log to MMC. 135 TEMS Investigation 13.1 User’s Manual Top N This field is editable if you have set Scan Type to “Top N”. Here you specify how many cells the scanner should report; setting the field to N causes the scanner to return the N strongest cells (N ≤ 16). Cell Index List This field is editable if you have set Scan Type to “Targeted”. Here you specify the indices of the cells to scan (up to 16 cells for each EARFCN, i.e. up to 16 × 12 = 192 cells in total). Primary Detection Threshold (dB) Threshold (in negative dB) for detection of Primary Synchronization Channel. Min: –30 dB. Max: 0 dB. Secondary Detection Threshold (dB) Threshold (in negative dB) for detection of Secondary Synchronization Channel. Min: –30 dB. Max: 0 dB. Decoding Threshold (dB) CINR threshold for attempting to decode the MIB/ SIB. Min: –30 dB. Max: 50 dB. Enable SCH Measurement of Synchronization Channels: P-SCH RSSI, S-SCH RSSI, and SCHRQ. Enable BCH RP Measurement of BCH received power. Not supported by currently connectable scanners. Enable RS Measurement of Reference Signal (RSRP, RSRQ). Enable CINR Calculation of CINR, Carrier to Interference-plusNoise Ratio for SCH and RS. The carrier is the desired signal, and the interference can be either noise or co-channel interference or both. Enable CFO Measurement of Center Frequency Offset. Not supported by currently connectable scanners. 136 Chapter 14. LTE Scanning Bandwidth The bandwidth to scan. • If you choose Auto-select, the scanner will itself detect the bandwidth in use. For this to work, a valid LTE signal with strength greater than the detection thresholds is required. • If you choose a fixed bandwidth (1.4, 3, 5, 10, 15, or 20 MHz), that bandwidth will always be scanned. If you know what the implemented bandwidth is, simply select it. Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. It should normally be enabled, since otherwise high level signals may saturate the receiver and cause errors. Cyclic Prefix Detection Mode • Automatic: Cyclic prefix used by detected cells is automatically detected. • Normal: Normal prefix assumed. • Extended: Extended prefix assumed. • Automatic: Duplexing method used by detected cells is automatically detected. • FDD: Frequency Division Duplexing assumed. • TDD: Time Division Duplexing assumed. Duplexing Detection Mode Enable ECP This should be turned on if the network uses Extended Cyclic Prefixes.  3GPP 36.211, table 6.2.3-1 Observations Average Number of LTE frames over which to average scan measurements. Detection Mode • Fast mode: This mode offers reasonable sensitivity with a fast scan rate. • Robust mode: This mode uses lower detection thresholds and increased averaging to detect lower-level signals. It is a slower scan mode. NT11-20502 137 TEMS Investigation 13.1 User’s Manual Number of Tx 14.2.4. The number of Tx signals to be detected by the scanner. If the eNode-B is using MIMO transmission, with separate RS symbols per Tx port, the scanner can detect each of the different RS’s and is then able to measure each Tx signal separately. Setup of LTE Signal Scan: PCTel With PCTel only Top-N scanning is supported, not scanning of a fixed cell list. Bandwidth The bandwidth to scan. The bandwidth must be selected manually. Top N Here you specify how many cells the scanner should report; setting the field to N causes the scanner to return the N strongest cells. Number of Antenna Ports The number of antenna ports to measure on. The scanner is capable of detecting this automatically (“Auto Detect”). Cyclic Prefix The type of cyclic prefix used in OFDM, e.g. “Normal 15 kHz”. The scanner is capable of detecting this automatically (“Auto Detect”). Reference Signal Data Mode Select the measurements you want to collect. 14.2.5. Setup of LTE Signal Scan: R&S TSMW Cyclic Prefix 138 Please note that Delay Spread measurement requires PCTel LTE scanners with software version 1.3 or higher. The type of cyclic prefix used in OFDM. Seven (7) OFDM symbols (15 kHz) can be transmitted per slot if normal prefix length is used and 6 OFDM symbols per slot if extended prefix length is used. The scanner is capable of detecting this automatically (“Auto Detect”). Chapter 14. LTE Scanning Frame Structure Channel frame structure. If FDD, uplink and downlink transmitters use separate frequency bands, and if TDD, a single frequency band is shared between uplink and downlink. Measurement Rate (Hz) Average number of 100 ms blocks to measure per second. Reference Signal Enables reference signal measurement. This is used to enable or disable RSRP/RSRQ measurements. TDD Frame Configurations Specifies uplink–downlink configurations to try when performing reference signal measurements on TDD channels. S-SCH to P-SCH Ratio Settings Ratio Type Specifies either a list of ratios or a range in which the power ratio between the primary and secondary synchronization channel must reside. Lower Ratio Limit (dB) Lower limit for ratio between primary and secondary synchronization channel. Upper Ratio Limit (dB) Upper limit for ratio between primary and secondary synchronization channel. Fixed Ratios (dB) List of power ratios between the primary and secondary synchronization channels. RF Front-end Front-end (processor) on which to schedule measurement. The measurement tasks are manually distributed on the two built-in front-ends. Resource Allocation (%) Resources allocated on the specified front-end. Resource Available (%) Read-only field indicating the remaining available resources on the processor selected under RF Frontend. NT11-20502 139 TEMS Investigation 13.1 User’s Manual 14.2.6. Presentation of LTE Signal Scan LTE signal scans are presented in a suite of predefined charts and status windows. See Information Elements and Events, section 8.3.2. 14.2.7. 14.2.7.1. Customizing the Presentation Sorting of Cells You can sort LTE cells in scanning information elements in a number of different ways. The sorting order is set in the General window. • Open the General window from the Navigator. • Double-click the item “LTE”. A dialog appears with these sorting options: • 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, that is, a cell with Cell Identity n is always found at argument index n. • Sort by Cell Identity: Cells are sorted by Cell Identity; the cell with the lowest Cell Identity appears at argument index 1, the cell with the next higher Cell Identity appears at argument index 2, etc. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events, section 3.3) is fixed and is not affected by the General window settings. 14.3. RSSI Scanning 14.3.1. Setup of RSSI Scan: General Technology 140 Always “LTE”. Chapter 14. LTE Scanning Band LTE band to scan. Regarding band support in scanners, see the Getting Started Manual, section 10.1.4.2. Channels EARFCNs to scan within the selected LTE band. Each EARFCN is specified as a number representing the center frequency of the channel. Up to 255 EARFCNs can be scanned. 14.3.2. Setup of RSSI Scan: DRT Logging Mode See section 14.2.3. Bandwidth Bandwidth to scan; fixed at 100 kHz. 14.3.3. Setup of RSSI Scan: PCTel Bandwidth Bandwidth to scan; select a bandwidth from the list. Remaining Measurement Points See section 11.7. 14.3.4. Presentation of RSSI Scan RSSI scans are presented in a suite of predefined charts. See Information Elements and Events, section 8.3.2. 14.4. Spectrum Scanning A spectrum scan shows downlink signal strength as a function of frequency. 14.4.1. Setup of Spectrum Scan: General Technology Always “LTE”. Band Select the LTE frequency band to scan. NT11-20502 141 TEMS Investigation 13.1 User’s Manual Start Frequency Low end of the frequency range to be swept by the scan. Given in MHz. Stop Frequency High end of the frequency range to be swept by the scan. Given in MHz. Resolution Bandwidth Interval between successive scan samples in kHz, the highest selectable resolution being 5 kHz. In the presentation window, the legend pane will list all samples; the chart, on the other hand, can of course only distinguish the samples as far as the screen resolution permits. 14.4.2. Setup of Spectrum Scan: Andrew Scan Rate 14.4.3. Minimum time for scan in ms. Setup of Spectrum Scan: DRT The DRT-specific settings are the same as for WiMAX; see section 17.5. Note, however, that the Triggered Scan option is still associated with WiMAX frames; that is, it will come into play only if you are using the LTE scanner to search for WiMAX presence. 14.4.4. Setup of Spectrum Scan: PCTel The PCTel-specific settings are the same as for WCDMA. See section 13.5.1. 14.4.5. Spectrum Scan Presentation Spectrum scans are presented in a predefined bar chart. See Information Elements and Events, section 8.3.2. 14.5. Enhanced Power Scanning Compared to the spectrum scan, the enhanced power scan is a higherperformance scan that provides selective power measurements in the time and frequency domains. 142 Chapter 14. LTE Scanning 14.5.1. Setup of Enhanced Power Scan: General Technology Always “LTE”. Band LTE band to scan. Regarding band support in scanners, see the Getting Started Manual, section 10.1.4.2. Channel EARFCN to scan within the selected LTE band. 14.5.2. Setup of Enhanced Power Scan Bandwidth Bandwidth to scan. One of: CW: 100 kHz Normal: 1.4 MHz Wide Type 2: 3 MHz Wide Type 3: 5 MHz Wide Type 4: 10 MHz Wide Type 5: 15 MHz Wide Type 6: 20 MHz Time Period Reference Specifies whether the EARFCN given under Channel is the minimum, center, or maximum frequency of the band to be scanned. Timing Period Mark The scan will start on the nearest Timing Period Mark with the Timing Period Mark Offset specified. Given in units of 50 μs. Max: 20000. Timing Period Mark Offset Time offset in units of 50 μs. Must be less than or equal to Timing Period Mark. Measurement Window Measurement window size in units of 50 μs. Must be larger than 100, or else set to zero which means that the choice of window size is made by the scanner for optimal measurement performance. Number of Bins The number of measurements to make within the specified band. If Time Period Reference is set to Center, then the number of bins must be odd. NT11-20502 143 TEMS Investigation 13.1 User’s Manual Resolution Bandwidth Resolution bandwidth in units of 2.5 kHz. Frequency Step Size Frequency step size in units of 2.5 kHz. Remaining Measurement Points See section 11.7. 14.5.3. Valid range: 2 ... 8000. Presentation of Enhanced Power Scan Enhanced power scans are presented in a predefined bar chart. See Information Elements and Events, section 8.3.2. 144 Chapter 15. TD-SCDMA Scanning 15. TD-SCDMA Scanning TEMS Investigation supports scanning of TD-SCDMA UARFCNs with the PCTel scanners listed in the Getting Started Manual, section 10.1.4.3. As for other cellular technologies, TEMS Investigation can make use of GPS data from the scanner’s internal GPS. Note: You must have GPS coverage to obtain TD-SCDMA scan data. This is because a GPS signal is needed for time synchronization, which is indispensable for the TD (Time Division) component of the TD-SCDMA technology. 15.1. Scanning Methods • Pilot scanning (section 15.3): Top N • RSSI scanning (section 15.4) 15.2. General Scan Settings Regardless of scanning method, you need to set the following: Technology Always “TD-SCDMA” for TD-SCDMA scanning. Band TD-SCDMA band or bands to scan. Regarding band support in connectable scanners, see the Getting Started Manual, section 10.1.4.3. Channels TD-SCDMA UARFCNs to scan within the selected band. Each UARFCN is specified as a number representing the center frequency of the channel. Up to 12 UARFCNs can be selected for pilot scanning, and up to 255 UARFCNs for RSSI scanning. NT11-20502 145 TEMS Investigation 13.1 User’s Manual 15.3. Pilot Scanning TD-SCDMA pilot scanning can be done in two different modes: • Midamble Top N mode • Sync DL Top N mode Depending on the mode, different parts of the TD-SCDMA frame are measured, as explained further below. Midamble Top N Pilot Scanning This mode measures the Primary Common Control Physical Channel (P-CCPCH), which is transmitted in Timeslot 0 (TS0). To this end it scans the TS0 midamble (144 chips), located between the two data sections. The midamble is used as a training sequence for channel estimation, power measurements, and synchronization. The mapping between Cell Parameter Identity (CPI) and the Basic Midamble Code used is given in  3GPP 25.223-840, table 6, section 7.3. SyncDL Top N Pilot Scanning This mode measures the Downlink Pilot Timeslot (DwPTS), which is located just before the first switching point in the Guard Period (GP) and after Timeslot 0. The switching points are used to manage the transition between uplink and downlink (since TD-SCDMA utilizes TDD to separate uplink and downlink). The DwPTS is used for downlink synchronization. During the cell search procedure, the UE acquires the timing of the DwPTS by correlating with the SYNC-DL code transmitted in the DwPTS. 15.3.1. Setup of Pilot Scan Type of Scanning • Number of Pilots To scan the N strongest CPIs, enter the value N here (N ≤ 32). 146 Scan strongest: The N strongest CPIs will be reported from the chosen UARFCNs. The value N is determined by the Number of Pilots parameter. The scanner automatically finds the strongest CPIs. Chapter 15. TD-SCDMA Scanning PN Threshold If the Ec/Io value is below the PN threshold, Ec/Io will not be reported. Remaining Measurement Points See section 11.7. Measurement Mode Select “Midamble Top N” or “SyncDL Top N”. The modes are described in the introduction of section 15.3. 15.3.2. Presentation of Pilot Scan Pilot scans are presented in a suite of predefined charts and status windows. See Information Elements and Events, section 8.4.3. 15.3.2.1. Sorting of Cells You can sort TD-SCDMA cells in scanning information elements in a number of different ways. The sorting order is set in the General window. • Open the General window from the Navigator. • Double-click the item “TD-SCDMA”. A dialog appears with these sorting options: • 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 a cell with CPI n is always found at argument index n + 1. • Sort by Cell Parameter Id: Cells are sorted in order of ascending CPI, so that the cell with the lowest CPI appears at argument index 1, the cell with the next higher CPI appears at argument index 2, etc. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events, section 3.4) is fixed and is not affected by the General window settings. NT11-20502 147 TEMS Investigation 13.1 User’s Manual 15.4. RSSI Scanning The RSSI scan returns narrowband or wideband channel aggregate power. Scanners with both TD-SCDMA and GSM capability can do an RSSI scan on either of these technologies. You make the selection under General settings → Technology. The GSM RSSI scan is configured in the usual manner as described in section 12.2. 15.4.1. Setup of RSSI Scan What UARFCNs to scan is set in the General settings; see section 15.2. Bandwidth Bandwidth to scan: either “Normal” (wideband) or “CW” (narrowband). Remaining Measurement Points See section 11.7. 15.4.2. Presentation of RSSI Scan RSSI scans are presented in a suite of predefined charts. See Information Elements and Events, section 8.4.3. 148 Chapter 16. CDMA Scanning 16. CDMA Scanning TEMS Investigation supports scanning of CDMA (IS-2000, IS-856, IS-95) RF channels with the Andrew and PCTel scanners listed in the Getting Started Manual, section 10.1.4.4. 16.1. Scanning Methods Pilot scanning 1 Section Ref. PCTel MX PCTel LX/EX CDMA Scanning Capability/ Scanning Device Andrew i.Scan TEMS Investigation offers these CDMA scanning methods, supported using the various devices as indicated. Please note that for a scanning method to be actually available in TEMS Investigation, the device must have been purchased with the relevant option (wherever applicable). 16.3 RSSI scanning 16.4 Narrowband interference scanning 16.5 Spectrum analysis 16.6 1. Follow UE option not supported. NT11-20502 149 TEMS Investigation 13.1 User’s Manual 16.2. General Scan Settings The following settings are common to all or most of the scanning methods: Technology One of: • CDMA One (IS-95) • CDMA2000 • EV-DO Band CDMA band or bands to scan. Regarding band support in connectable scanners, see the Getting Started Manual, section 10.1.4.4. Channels CDMA RF channels to scan within the selected band. Each channel is specified as a number representing the center frequency of the channel. Up to 12 RF channels can be selected. 16.3. Pilot Scanning This method scans pilots, scrambled with cell-specific PN sequence offsets. 16.3.1. Setup of Pilot Scan: Andrew Scan Rate Minimum time for scan in ms. Report Threshold Ec/Io detection threshold in dB. Min: –24. Max: 0. Number of Top N Entering the number N means scan the N strongest pilots. Min: 1. Max: 32. PN Increment The PN increment. Compare the discussion of the corresponding parameters in section 16.3.2. Correlation Length CDMA: Scan correlation length in chips. Must be divisible by 128. Min: 512. Max: 2048. EV-DO: Scan correlation length in slots. Min: 1. Max: 16. 150 Chapter 16. CDMA Scanning 16.3.2. Setup of Pilot Scan: PCTel 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, static set of pilots (up to 512, i.e. no restriction on number of pilots), common to all selected RF channels. • Scan strongest: The strongest pilots (“Top N”; up to N = 32) on each RF channel, or the 32 strongest pilots on the RF channel currently used by a CDMA phone that is also activated in the application. The latter option is activated by setting “Follow UE” to Yes. In either case, the scanner automatically finds the strongest pilots. Selected Numbers This field is visible if Type of Scanning is set to “Scan selected”. Here you pick the pilots you want to scan. Number of Pilots This field is visible if Type of Scanning is set to “Scan strongest”. Entering the number N means scan the N strongest pilots. Min: 1. Max: 32. PN Threshold This is a signal code power threshold (in dB) used for the Delay Spread measurements. If the PN threshold is set too low, the Delay Spread values will be affected by random noise more than may be desired. By raising the threshold you reduce the influence of random noise correlations, and you will thus be able to discern multipath and fading effects more accurately. The setting –20 dB is recommended. Remaining Measurement Points NT11-20502 See section 11.7. 151 TEMS Investigation 13.1 User’s Manual 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. This parameter, along with Start Pilot and Pilot Increment, are applicable only in “Scan selected” mode. If a pilot increment is used, TEMS Investigation will filter the list of selectable PNs: for example, if Start Pilot = 0 and Pilot Increment = 3, only the PNs 0, 3, 6, ... will appear in the list. Start Pilot The index of the first PN allocated. Pilot Increment The PN increment. Max Cell Radius The maximum radius within which to detect pilots. Settings Specific to EV-DO (IS-856) Pilot Window Length This parameter indicates the length, in chips, of the time window in which the pilot is searched. The maximum pilot window length supported by the scanning receiver is 64. This is also the default and recommended setting. Search Window Size Normal (64 chips), Wide (128 chips), or Wider (256 chips). 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. Pilot Delay The number of chips between the expected arrival time and the actual arrival time of the signal. Aggregate Ec/Io The sum of all peak pilot Ec/Io values above the PN threshold.1 152 Chapter 16. CDMA Scanning Delay Spread The number of chips between the first and last pilot Ec/Io peak above the PN threshold. 1. This measurement does not appear as an information element; it is only found in scanner reports. Remaining Options Measurement Mode (EX only) There are two choices, High Speed and High Dynamic. These are two algorithms with different priorities. High Dynamic puts the emphasis on accuracy. Each sample reported by the scanner is typically based on a measurement 20 ms in length. High Speed is faster and accordingly less accurate. Each reported sample is typically based on a 10 ms measurement. Timing Mode Here you select by what method the scanner should synchronize to the base station’s transmissions. • GPS Only: The scanner will rely exclusively on its internal GPS for timing. • Pilot Sync Only: The scanner will rely exclusively on the Pilot and Sync channels for timing. • GPS Preferred: The scanner will use its internal GPS for timing whenever possible and resort to the Pilot and Sync channels in other cases. This setting is enabled only if the scanner has been purchased with the Sync Channel Timing option. Pilot synchronization allows the scanner to operate in indoor environments where GPS coverage is lacking. Without the Sync Channel Timing option, the scanner can only use its GPS for timing. The Timing mode setting is applicable for IS-95 and IS-2000 only, not for IS-856. NT11-20502 153 TEMS Investigation 13.1 User’s Manual Integration (Chips) This is the number of chips over which each signal energy value is integrated. Setting this parameter high improves the accuracy and reliability of the output but also slows the scan down. The default and recommended value is 2048 for IS-2000 and IS-95, and 3072 for IS-856. Follow UE, Selected UE If this is set to On, a further field “Selected UE” appears where you select which CDMA phone the scanner should follow. The scan will then cover the 32 strongest pilots on the RF channel that the selected phone is currently using. When the phone switches to a different RF channel, the scanner follows along automatically. If you choose this option, all other controls in the dialog are disabled. The band, protocol, and RF channel information is taken from the phone. 16.3.3. 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. Each bar chart by default presents peak Ec/Io for each pilot found. Pilots are sorted by ascending PN offset. The updating rate is chiefly dependent on the number of live signals encountered in the network. For a manually selected set of pilots, the updating rate is also greatly affected by the size of this set, whereas for the “Top N” scan the number N is only marginally important (since all pilots have to be searched regardless of N). 16.3.4. Presentation: Strongest Scanned PN Bar Chart This bar chart shows the strongest pilots scanned, regardless of RF channel. 154 Chapter 16. CDMA Scanning 16.3.5. 16.3.5.1. Customizing the Presentation Sorting of Pilots You can sort pilots in scanning information elements in a number of different ways. The sorting order is set in the General window. • Open the General window from the Navigator. • Double-click the item “CDMA”. A dialog appears with these sorting options: • Sort by decreasing Ec/Io (default). • Sort by increasing Ec/Io. • Sort by fixed position: Pilot PNs are sorted by index and are always assigned the same argument indices, that is, pilot PN n is always found at argument index n + 1. • Sort by Pilot PN: Pilot PNs are sorted by index; the pilot with the lowest index appears at argument index 1, the pilot with the next higher index appears at argument index 2, etc. Note: The sorting order of the “Sc Best” elements (see Information Elements and Events, section 3.2) is fixed and is not affected by the General window settings. NT11-20502 155 TEMS Investigation 13.1 User’s Manual 16.4. RSSI Scanning 16.4.1. Setup of RSSI Scan Bandwidth Select Normal or Continuous Wave (“CW”). This setting applies to all channels you select for scanning. • Normal: CDMA band, bandwidth 1.2288 MHz. • CW: “Condensed” or CW band. For the cellular (800) band, the bandwidth is 30 kHz. For the PCS (1900) band, the bandwidth is 50 kHz. Regardless of the choice made here, the measurements are extracted to the same information elements (Scanned RSSI, etc. in the “CDMA” category). Remaining Measurement Points See section 11.7. Follow UE 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).1 When the phone switches to a different RF channel, the scanner follows along automatically. If you choose this option, all other controls in the dialog are disabled. The band, protocol and RF channel information are taken from the phone. This option is not available for EV-DO. 1. Specifically (n = phone’s RF channel number): on the 800 MHz band, RF channels [n – 21 ... n + 21]; on the 1900 MHz band, RF channels [n – 13 ... n + 13]; on the 450 MHz band, RF channels [n – 26 ... n + 26] if 79 ≤ n ≤ 275, otherwise [n – 33 ... n + 33]. 16.4.2. Presentation: RSSI Scan Bar Chart This bar chart displays RSSI for each RF channel scanned. 156 Chapter 16. CDMA Scanning 16.5. Narrowband Interference Scanning In this mode the scanner scans a narrow band centered around a specific RF channel, identifying other sufficiently strong RF channels as interferers. For the cellular (800) band the scanned bandwidth is 30 kHz, and for the PCS (1900) band it is 50 kHz. The narrowband interference scan has lower resolution than the spectrum analysis scan (see section 16.6) but is considerably faster. Once you have done a narrowband interference scan to identify interferers, you can proceed to perform a spectrum analysis in the relevant frequency range, thereby obtaining an even clearer view of the problematic signals. 16.5.1. 16.5.1.1. Setup of Narrowband Interference Scan General Settings Under Channels, you select a single RF channel around which to scan. As regards the rest, see section 16.2. 16.5.1.2. Context Settings Remaining Measurement Points 16.5.1.3. See section 11.7. Interference Offset • Open the General window and double-click the CDMA item. • In the dialog that appears, enter the Interference Offset in dB. This is a threshold governing how strong an RF channel must be in order to be regarded as an interferer. Specifically, 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. 16.5.2. Presentation: Narrowband Interference Scan Bar Chart The results from this scanning method are presented in the CDMA Narrowband Interference Scan Bar Chart: NT11-20502 157 TEMS Investigation 13.1 User’s Manual Each bar in this chart represents an RF channel. This chart uses a special, predefined color coding: • Yellow: The RF channel is an interferer according to the Interference Offset threshold criterion entered (see section 16.5.1). • Green: The RF channel is not an interferer according to the Interference Offset criterion. An event “Narrowband Interference” is reported when an in-band interferer is detected. See Information Elements and Events, section 7.3. 16.6. Spectrum Analysis This scanning method shows downlink signal strength as a function of frequency. 16.6.1. 16.6.1.1. Setup of Spectrum Analysis Scan General Settings Technology Choose the relevant CDMA technology. Band CDMA frequency band to scan. 158 Chapter 16. CDMA Scanning Start Frequency Low end of the frequency range to be swept by the scan. Given in MHz. Stop Frequency High end of the frequency range to be swept by the scan. Given in MHz. Resolution Bandwidth Interval between successive scan samples in kHz, the highest selectable resolution being 5 kHz. In the presentation window, the legend pane will list all samples; the chart, on the other hand, can of course only distinguish the samples as far as the screen resolution permits. 16.6.1.2. Context Settings • The Andrew-specific settings are the same as for LTE. See section 14.4.2. • The PCTel-specific settings are the same as for WCDMA. See section 13.5.1. 16.6.2. Presentation of Spectrum Analysis Scan Spectrum scans are presented in a predefined bar chart. See Information Elements and Events, section 8.5.3. NT11-20502 159 TEMS Investigation 13.1 User’s Manual 17. WiMAX Scanning TEMS Investigation has the ability to scan WiMAX carriers with a DRT scanner. For the range of supported WiMAX-capable DRT models, see the Getting Started Manual, section 10.1.4.6. How to configure the DRT scanner (and the PC along with it) for use with TEMS Investigation is covered in the Getting Started Manual, chapter 12. 17.1. Scanning Methods WiMAX scanning methods are as follows: • WiMAX preamble scan • RSSI scan • Spectrum analysis 17.2. General Scan Settings Regardless of scanning method, you need to set the following: Band WiMAX band to scan: one of the bands (WiMAX RF Profiles) supported by the scanner, and the associated OFDMA bandwidth. Regarding band support, see section 17.1. Channels WiMAX channels to scan within the selected band. Each channel is specified as a number representing the center frequency of the channel. Up to 1500 channels can be selected. Technology Always “WiMAX” at present. 160 Chapter 17. WiMAX Scanning 17.3. Preamble Scanning The WiMAX air interface uses OFDM as modulation method. Within an OFDM frame, each subframe is preceded by a preamble. The preamble is used for synchronization and channel estimation purposes. The bandwidth scanned during preamble scanning is that of the selected band (i.e. WiMAX RF Profile; currently either 5 or 10 MHz). Up to 100 preambles can be tracked simultaneously. 17.3.1. Setup of Preamble Scan Scan Type Logging Mode • Targeted: Select this if you wish to scan a fixed set of preambles. Specify the preambles under Preamble Index List. • Top N: Select this if you wish to scan the strongest preambles. Set the number of preambles to report under Top N. When using a DRT scanner purchased with TEMS Investigation, the scan data is always recorded in regular TEMS Investigation logfiles (*.log), regardless of how this parameter is set. If you are using a DRT scanner with the optional multimedia card (MMC), you can optionally record a logfile with scan data on the MMC as well. (This logging has got nothing to do with TEMS Investigation.) The MMC must have been formatted and inserted into the scanner before the scanner is powered on. • MMC: Log to MMC. • None: Do not log to MMC. Enable Preamble Power Calculation of preamble power. Enable Preamble CINR Calculation of CINR, Carrier to Interference-plusNoise Ratio. The carrier is the desired signal, and the interference can be either noise or co-channel interference or both. NT11-20502 161 TEMS Investigation 13.1 User’s Manual Enable CFO Measurement of Carrier Frequency Offset. Enable Delay Spread Measurement of multipath delay spread. Enable Absolute Delay Measurement of delay relative to GPS. Enable DL-MAP Pilot CINR Measurement of downlink MAP pilot CINR. Enable DL-MAP Pilot Power Measurement of downlink MAP pilot power. Enable DL-MAP Data Power Measurement of downlink MAP data power. Use N=3 for CINR Measurements If set to True, cluster size N = 3 will be used for CINR measurement, that is, CINR will be measured for each segment. If set to False, cluster size N = 1 will be used for CINR measurement, that is, CINR will be measured over all segments. Enable AGC Use of AGC (Automatic Gain Control) scanning parameter. It should normally be enabled, since otherwise high level signals may saturate the receiver and cause errors. Measurement Mode One of Fast mode, Robust mode, or Rogue mode. Enable Channel Response: Time Domain Measurement of channel response in time domain. Enable Channel Response: Frequency Domain Measurement of channel response in frequency domain. 162 Chapter 17. WiMAX Scanning Top N This field is editable if you have set Scan Type to “Top N”. Here you specify how many preambles the scanner should report; setting the field to N causes the scanner to return the N strongest preambles. Preamble Index List This field is editable if you have set Scan Type to “Targeted”. Here you specify the indices of the preambles to scan. Detect Threshold Threshold (in negative dB) below which no preamble detection is reported. Decode Threshold Threshold (in dB) below which data is not decoded. Enable Statistical Information This must be set on for measurement statistics (mean and standard deviation for RSSI, CINR) to be computed. Number of Samples for Stats The number of samples on which to base each computation of measurement statistics. However, the actual number of samples used may be smaller, as reported in the “Samples Taken” information elements (see Information Elements and Events, section 3.7). Enable Frame Prefix Decoding Decoding of downlink Frame Prefix (DLFP). The Frame Prefix specifies the modulation type and number of symbols associated with one or several downlink bursts that follow the FCH. Enable Downlink Map Decoding Decoding of downlink MAP messages. These include the burst profile for each user, which defines the modulation and coding scheme used on the downlink. Enable Uplink Map Decoding Decoding of uplink MAP messages. Compare Enable Downlink Map Decoding. Enable DCD Decoding Decoding of Downlink Channel Descriptor (a message containing information about downlink characteristics). NT11-20502 163 TEMS Investigation 13.1 User’s Manual Enable UCD Decoding Decoding of Uplink Channel Descriptor (a message containing information about uplink characteristics). 17.4. RSSI Scanning 17.4.1. Setup of RSSI Scan Logging Mode See section 17.3. Bandwidth Bandwidth to scan; select a bandwidth from the list. 17.5. Spectrum Analysis A spectrum scan shows downlink signal strength as a function of frequency. 17.5.1. Setup of Spectrum Analysis Scan Logging Mode See section 17.3. Average Time Length of time for total averaging in μs. Triggered Scan Setting this to Yes means that the scanning will be triggered at the start of a new WiMAX frame. Offset Time (µs) Offset from start of frame in μs. Valid for triggered scan only. Block Time (µs) Length of time for block averaging in μs. Valid for triggered scan only. Measurement Points The number of measurement points left to allocate. 17.6. Presentation WiMAX scans are presented in a suite of predefined charts and status windows. See Information Elements and Events, section 8.7.1. 164 Chapter 17. WiMAX Scanning The purpose of having views that are grouped by preamble index, rather than by RSSI or CINR, is to provide information about all the sectors of a site. This can help identify improperly aimed antennas, or find crossed feeders. The purpose of having views sorted by RSSI or CINR, without any grouping by segment, is to provide information that is helpful in determining coverage, best server, and handover targets for neighbor lists. NT11-20502 165 TEMS Investigation 13.1 User’s Manual 18. Service Control 18.1. Introduction to Service Control The Service Control tool is used to control the actions of devices that you activate in the application. • Circuit-switched voice and video calls are supported. • Data service testing encompasses the following services and protocols: e-mail, FTP, HTTP, MMS, Ping, SMS, TCP, UDP, video streaming, VoIP, and WAP. Which of these are testable for particular cellular technologies is tabulated in section 18.3. With multiple devices activated, multiple data connections can be maintained concurrently.1 Special activities are available • for recording all data collected while executing the scripts. The recordings will be regular logfiles (extension .log). • for applying various control functions to devices, such as RAT lock and band lock • for AT commands. 1. However, if an Ericsson Fixed Wireless Terminal is activated, it is not possible to do data service testing with any other devices at the same time. See the Getting Started Manual, chapter 11 regarding preconfiguration of Fixed Wireless Terminals. 166 Chapter 18. Service Control 18.2. Service Control vs. Command Sequences For the benefit of users of pre-12.0 TEMS Investigation versions, this section contrasts the Service Control (“SCtrl”) feature with its predecessor, the Command Sequence (“CSeq”) tool. Compare section 6.3. Terminology • In SCtrl, you compose scripts consisting of activities, whereas in CSeq, command sequences were built up of commands. User Interface • SCtrl uses a graphical user interface where scripts are assembled in the form of flowcharts. This allows straightforward and unrestricted application of branching and other control structures, which in CSeq were limited to the Loop, Wait, and Synchronize operations. • Inter-device synchronization is implicit in a SCtrl workflow wherever workflow branches converge. 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. Logical Structure • Activities in SCtrl scripts are always assigned simply to the device as a whole (i.e. to the “EQ”). There is no distinguishing of “MS” and “DC” channels as in CSeq. • With SCtrl, all setups for data service testing are done from within TEMS Investigation. There is no need (as there was with CSeq) to go outside TEMS Investigation to configure phonebook entries and the like in Windows. • In SCtrl, network connect and disconnect (corresponding to dialup and hangup in CSeq) are always performed as separate activities; that is, they are never incorporated into activities for service testing as could optionally be done in CSeq. An exception is MMS, where the device must connect to an MMS Center; the details of that operation are specified as part of the MMS activity. • SCtrl does not have distinct activities for sessions run over an NDIS connection, as was the case in CSeq. In SCtrl you indicate the type of data connection (NDIS or RAS) using a parameter in the Network Connect activity. NT11-20502 167 TEMS Investigation 13.1 User’s Manual • SCtrl does not have distinct activities for KPI data collection as did CSeq. This is because the KPI concept is no longer explicit in TEMS Investigation (see chapter 31); however, adequate data on which to base KPI computation in other TEMS products (TEMS Discovery, TEMS Automatic) is always collected with SCtrl scripts provided that they are suitably composed. The easiest way to accomplish the latter is to base your scripts on the predefined snippets supplied for each service type. See section 18.10. • 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. See section 18.18.3. This property always applies to the activity as a whole, not to individual steps performed as part of the activity. • Old command sequences composed with CSeq cannot be run by SCtrl. 18.3. Capabilities of Devices Apart from technology-related restrictions as noted in section 18.4, phone devices sold with TEMS Investigation 13.1 (listed in the Getting Started Manual, section 10.1.1) normally support all types of script activities. Regarding other connectable devices, it should be noted that data service testing with Ericsson Fixed Wireless Terminals is limited to FTP, HTTP, and Ping. 168 Chapter 18. Service Control CDMA TD-SCDMA Service/Technology LTE Supported Services by Cellular Technology UMTS 18.4. Voice calls Video calls E-mail FTP HTTP MMS Ping SMS UDP Video streaming VoIP WAP Please note that the iDEN technology is not supported by the Service Control tool. 18.5. The Service Control Designer The Service Control Designer window is where you compose service control workflows (scripts): NT11-20502 169 TEMS Investigation 13.1 User’s Manual Properties pane Workflow pane Activity pane Configuration Sets pane • The Activity pane is a palette holding all script building blocks: for running services, for controlling devices, and for execution flow control. • The Workflow pane is the area where you assemble your script graphically in the form of a flowchart. • The Properties pane contains properties of the activity that you are currently working with (the one currently selected in the Workflow pane). • In the Configuration Sets pane you define various entities that can be reused in any script, for example all the details of accessing a particular FTP server. In the Properties and Configuration Sets panes, items can either be grouped into categories or be listed in alphabetical order; use the buttons at the top to toggle between the two display modes. At the bottom of each pane is a box showing an explanation for the item currently selected. The rest of this chapter is organized as follows. First comes a hands-on tutorial on how to build and run scripts, with numerous screenshots and examples (sections 18.6–18.16). Then follows a reference part cataloging all script activity types with their properties and associated configuration sets (sections 18.17–18.19). Finally some additional features of the Service 170 Chapter 18. Service Control Control tool are covered, and some reference material is given (sections 18.20–18.21). 18.6. Basics of Creating Scripts (with Voice) This section covers the fundamentals of creating a complete and valid script that is ready to be run. For purposes of illustration we will build a very simple script that dials single voice calls. Video calls are handled in similar fashion. Add a voice dial activity to the script. To this end, expand the Voice node in the Activity pane and drag the Dial item to the empty workflow. • 2 1 • The Dial box is tagged by an exclamation mark. This means that the activity is not yet properly configured. A similar exclamation mark in the Properties pane indicates the property that is undefined: “Configuration”. • What we need to do is to define a configuration set for the Dial activity. This is done in the Configuration Sets pane. For a voice dial, the NT11-20502 171 TEMS Investigation 13.1 User’s Manual configuration consists simply of the phone number to call. (In other cases it can be more complex, as will be seen later.) • Give the configuration a suitable name, such as one identifying the subscription having this number. The example below uses a neutral designation “Voice Call Recipient 1”, for which you will probably want to substitute something more specific. • Finish by clicking the Apply button. • The Properties and Workflow panes are now updated with the configuration data. When just dialing a call like this, it will not have a duration. The call will be established and then immediately hung up. To give duration to a call, use the Wait activity: compare section 18.11.5. 172 Chapter 18. Service Control • Drag the Wait activity to a position just below the voice dial box. The graphical user interface helps you position the Wait box correctly by means of guiding symbols and text. 1 2 • Set the duration of the wait in the Properties pane: • Finally, add a Hang Up activity after the wait. If you want the script to control both caller and receiver, turn to section 18.11.4 for guidance. NT11-20502 173 TEMS Investigation 13.1 User’s Manual 18.7. Setting Up a Network Connection This section shows how to set up a network connection, which is a necessary preparation for running data services. • Expand the IP node in the Activity pane and add a Network Connect activity to the script. • 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, only it contains many more parameters. In particular, you need to specify whether to use RAS or NDIS. See section 18.17.3.1 for full details. 174 Chapter 18. Service Control • Once you have the configuration down, point to it from the Configuration field in the activity properties. Later on, if you have multiple network connect configurations defined, you can pick and choose among them. 18.8. Setting Up a Data Service Activity In this section, we will set up an FTP download as an example of a data service activity. We will use the data connection configuration created in section 18.7. • First add a Network Connect activity. Associate it with the “W995_Dialup_1” configuration set created in section 18.7. • Then add a Network Disconnect activity at the bottom of the workflow. The disconnect operation will take down the network connection. This activity needs no particular configuration, so you do not need to associate it with a configuration set. NT11-20502 175 TEMS Investigation 13.1 User’s Manual 1 2 • The FTP session itself is handled by the FTP Download activity. Insert an activity of this type between network connect and disconnect: • For the FTP Download activity, you need to create a configuration set representing the FTP server and how to access it. Again this is done in similar fashion as for previously created configurations. 176 Chapter 18. Service Control We will download the file My_10_MB_File.dat from the FTP server with address 123.45.67.89, logging in as user “TEMS_User”. • After completing the definition of the FTP server configuration, reference it from the FTP download activity in the same manner as before. 18.9. Standalone PS Attach and Detach In this section we will perform explicit PS attach and detach operations in isolation. One reason for doing this could be to measure the time taken by these operations, particularly for the purpose of computing KPIs. We will reuse the configuration sets and activities from sections 18.7 and 18.8. • We begin with the FTP download workflow from section 18.8. • At the start of this workflow, add a PS Detach and a PS Attach activity, in that order (they are found in the IP category). This will detach the device from the PS network and then reattach the device. NT11-20502 177 TEMS Investigation 13.1 User’s Manual PS detach PS attach See also section 18.10. 18.10. Snippets A snippet is a fixed sequence of activities that is defined as a building block and can be reused as such, saving time and effort when creating new scripts. Predefined snippets for all supported services are provided in the Activity pane. For an example of such a predefined snippet in use, see section 18.11.4. The predefined snippets are also tailored to produce all data required to compute KPIs. (The KPI computation itself is done using TEMS Discovery or TEMS Automatic.) Compare chapter 31. You can also save an arbitrary activity sequence as a user-defined snippet: • Select all of the activities by dragging the mouse pointer, then enter the File menu and select Save as Snippet. You are prompted to name and describe the snippet. Example: The detach-plus-attach procedure in section 18.9 could be a good candidate for a user-defined snippet, since it will recur in any script where you want to detach and then reattach to the PS network. 178 Chapter 18. Service Control 18.11. 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. 18.11.1. Sequences You can formally define a group of activities in a script as a sequence. This is handy if you want to apply some operation to all of these activities – for example, to enable or disable them. • Suppose your script includes PS detach followed by PS attach as described in section 18.9. Suppose further that you want a convenient means of turning the detach/attach activities on and off. You can then encapsulate the PS Detach and PS Attach activities within a sequence. • 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, then drag them both (using the PS Detach box as handle) into the sequenceActivity1 box. You can now enable and disable the detach–attach sequence as a whole: NT11-20502 179 TEMS Investigation 13.1 User’s Manual Compare section 18.16.5. For full details on the Sequence activity, see section 18.17.2.4. 18.11.2. 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. Here is an example. Suppose the phone is on a WCDMA network and is instructed to do an FTP download. Now if the phone is handed over to GSM, so that the throughput is sharply reduced, then we want to abandon the download, i.e. the activity should terminate. (This is accomplished by imposing a “terminate on event” condition on the activity; see section 18.13.) After a handover to GSM has occurred, we want to proceed with a voice call (which does not require a large bandwidth). If on the other hand the phone remains on WCDMA, then after the FTP download has completed we want to continue with a video streaming session. To this end we use an if–else construct in the following manner: • First add a Network Connect activity, 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: 180 Chapter 18. Service Control • – For the left-hand branch (“ifElseBranchActivity1”), set Condition Type to Activity Result, and set the associated attributes as follows: Activity = the name of the FTP download activity, by default “ftpDownloadActivity1”, Operator = Equals, Result = Stopped by Event. See next screenshot. – For the right-hand branch (“ifElseBranchActivity2”), set Condition Type to Any. This always evaluates to true, so that the right-hand branch will be executed whenever the condition in the left-hand branch is false. (Not shown in the screenshot below.) Add a voice dial activity on the left (to the node “sequenceActivity1”) and a streaming activity on the right (to the node “sequenceActivity2”), as described in the introduction of this subsection. This is done just as in sections 18.6 and 18.8 and is not detailed here. See section 18.17.2.1 for full details on the If–Else activity. 18.11.3. While Loops While loops are used to repeat a sequence of activities a predetermined number of times. • Suppose we want to execute an FTP download five times over. NT11-20502 181 TEMS Investigation 13.1 User’s Manual • Begin by dragging a While activity to the start of the workflow. (Just as with sequences – compare section 18.11.1 –, you first add the empty While construct to the workflow, then fill it with the desired contents.) • In the Properties pane, set the number of times you want to iterate the while loop. Below, by entering the value 5, we stipulate that the loop should be run five times in total. • Now drag the predefined FTP download snippet into the while loop, 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: 182 Chapter 18. Service Control • Set the duration of the wait in the Properties pane: For example, if you set Duration to 10 s, the script will perform five FTP downloads in succession with a 10 s idle interval between downloads. See section 18.17.2.2 for full details on the While activity. 18.11.4. Parallel Activities: Controlling Multiple Devices All scripts so far have been written for a single device only. However, a script can also control the activities of multiple devices. For example, if one phone is to place a voice or video call to another, caller and receiver must be put in parallel, one dialing and the other answering. To create a branching structure for these concurrent tasks, we use the Parallel activity from the Control Flow category. See the screenshot below, where EQ1 calls EQ2: NT11-20502 183 TEMS Investigation 13.1 User’s Manual A parallel structure is also recommended for MMS send/receive. Next is a slightly more complicated example. Suppose that we want to control three UEs in parallel, one performing downloads over FTP and the other two looping short voice calls. For this purpose we need to build a somewhat more complicated workflow, as detailed in this section. • 184 First add a While activity and set it to run 10 times. This will become an outer loop repeating the various activities that will be included in it. Chapter 18. Service Control • Remove “sequenceActivity1” by selecting it and pressing Delete. (The Sequence activity is created automatically, but in this case we do not need it at the topmost level – compare the steps that follow.) • Drop a Parallel activity inside the while loop. • Since the Parallel construct by default provides only two branches, we need to add one more. To this end, right-click the “parallelActivity1” box and choose Add Branch from the context menu. The structure is now expanded with a third branch: It is now time to define the service-related activities. Let us begin with the voice calls: NT11-20502 185 TEMS Investigation 13.1 User’s Manual • Add while loops to branches 2 and 3 and set each to execute 5 times. • Add a voice call snippet (a predefined one is found in the Activity pane) to each while loop. Set the wait time to 10 seconds. • To assign the activities to the correct devices, we need to change the equipment (EQ) parameter to EQ2 and EQ3 in branch 2 and branch 3 respectively. This is done in the Properties pane or from the context menu for each activity. After these steps, branches 2 and 3 of the workflow should have the following structure: • Next, define the FTP task for device no. 1. All you need to do here is to add an FTP download snippet to branch 1 and associate it with a functional configuration. In the screenshot that follows, the voice sequences have been collapsed to clarify the overall structure of the workflow. 186 Chapter 18. Service Control This script will conduct a total of 10 FTP downloads and 2 × 5 × 10 = 100 voice calls. See section 18.17.2.3 for full details on the Parallel activity. 18.11.5. Wait The Wait activity has two chief functions: • When following a (voice) Dial or Video Dial activity, the Wait gives duration to the call after it has been established. • When appearing elsewhere, the Wait activity does nothing, so it effectively halts the workflow branch it is in. After the wait time has expired, the execution proceeds to the next activity. For usage examples, see sections 18.6, 18.11.3, and 18.11.4. See section 18.17.2.5 for full details on this activity. NT11-20502 187 TEMS Investigation 13.1 User’s Manual 18.12. Tips and Tricks for Creating Script Workflows • To copy, cut, and paste material in text fields, use the context menu in the text field. The keyboard accelerators Ctrl + C, etc. cannot be used for this purpose. • When using the mouse to select and drag a sequence of activities, do as follows: – Ctrl-click the activities from top to bottom in the same order as they come in the workflow. – Then use the topmost activity as handle when dragging. This procedure is necessary to preserve the ordering of activities within the sequence. (Whatever activity you use as handle will end up on top, and the remaining activities will follow in the order you have Ctrl-clicked them.) 18.13. Activity Properties That Control Execution All activities have some general properties governing their execution: • If an activity fails, you can choose to skip that activity, retry the activity, or terminate the entire script (On Failure property). • You can have an activity aborted after a fixed length of time, or if a specific event occurs (Abort property). For full details, see sections 18.18.2–18.18.3. 18.14. UE Control Functionality A number of control functions accessible from the Navigator (Equipment tab, bottom part, Activities tab: see section 8.1) can also be applied in a script in the form of activities. For the RAT lock and band lock functions, it must be noted that the script activities are inevitably more generic in nature than the manual control functions, since when composing a script it is not known what devices the activities will apply to. Therefore, the Band Lock activity has bands from every supported technology selectable, whereas the manual band lock function in the Navigator (acting as it does on a specific device of a well-defined make and model) can only lock on the bands supported by the device. In conclusion, a UE control activity in a script can be executed only if the target 188 Chapter 18. Service Control device is capable of the operation in question. You will be notified if this is not the case (see section 18.15 on validation). See section 18.17.1 for full details on the UE control activities. 18.15. Validating Scripts Before a script is run, it needs to be validated to ensure that it is syntactically correct and does not assign tasks that your devices do not support. For uncomplicated scripts like our first example in section 18.6, this may seem trivial. However, when building more complex scripts involving multiple devices and control logic, the validation becomes a non-trivial issue. Validation is also crucial for UE control functionality (see section 18.14). A script is automatically validated when you start it. You can also explicitly have a script validated in advance: • Enter the Script menu and choose Validate. You will be presented with the results. • If the script passes validation, you will receive a notification “Script validation succeeded”. The script is then ready to be run. See section 18.16. 18.16. Running Scripts You can run a script either from the Service Control Monitor or from the Service Control Designer. 18.16.1. General Aspects of Script Execution • The devices involved in a script will execute their assigned activities independently of one another, except when the devices engage in a service where they interact, and when devices are involved in different workflow branches that converge. In the latter case, all branches are synchronized before the execution proceeds past the point of convergence. • When executing a script, the keylock function must not be activated in any of the phones. If it is, the script will not work properly. • If you stop a script while an SMS or MMS message is being transferred, you should wait until the receiving device has received the message before restarting the script. Otherwise, unpredictable behavior may result. NT11-20502 189 TEMS Investigation 13.1 User’s Manual • How to run only parts of a script is described in section 18.16.5. • It is possible in the application to run several scripts at the same time; however, this is not recommended. (The script validation does not extend to such usage.) 18.16.2. Preparations 18.16.2.1. Windows 7/Windows Vista and IPv6 In Windows 7 and Windows Vista, it is recommended that you disable IPv6 for all device modems. See the Getting Started Manual, section 8.2.15.1 for further details and instructions. 18.16.3. Running Scripts from the Service Control Monitor Click the Open Script button and select your script (file extension .tsc). Click the Run Script button to start the script. Click the Stop Script button to stop script execution. Status Tab On this tab, the current status for each device is displayed. If a device is engaged in multiple concurrent service sessions, one line is printed for each session. Summary Tab On this tab, statistics are given on the outcome of each activity type (number of succeeded, aborted, and failed activities). Clicking an underlined number in this table brings up a summary of each activity that has been run. Below is an example (UDP, full duplex): 190 Chapter 18. Service Control 18.16.4. Running Scripts from the Service Control Designer • Enter the Script menu and choose Run. 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 18.16.3). Click the Stop Script button to stop script execution. Click the Return to Designer button to return to the Service Control Designer window. 18.16.5. Suppressing Parts of a Script It may happen that you want to run only certain parts of a script and exclude others. You can easily disable any individual activity by right-clicking it or by changing the Enabled flag in the Properties pane, as shown below. NT11-20502 191 TEMS Investigation 13.1 User’s Manual An activity that is currently disabled appears dimmed in the workflow pane. For example, suppose we want to skip the initial detach/attach procedure. After disabling the sequence comprising the first two activities, the flowchart looks like this: Note: Be sure not to disable an activity that another activity is dependent on. For example, do not suppress an activity whose outcome is used to evaluate a subsequent If–Else condition (see section 18.11.2). To re-enable a disabled activity, just set the Enable property to True again. 192 Chapter 18. Service Control 18.16.6. Presentation of Data Service Testing See section 8.3.1. 18.17. Activities (Reference Section) This section also explains all activity-specific properties found in the Properties pane: that is, those not covered in section 18.18. Not all activities have unique properties. 18.17.1. Control Activities 18.17.1.1. Activate Activates the device so that it can be used in TEMS Investigation. This activity has no unique properties. 18.17.1.2. AT Sends an AT command. • AT Command property: AT command string. (Define a configuration for each AT command you want to send.) 18.17.1.3. Band Lock Locks the device to a subset of frequency bands. • Bands property: Specify band or bands to lock on. The details are analogous to the manual band lock function on the Navigator’s Equipment tab; see section 8.1.3. 18.17.1.4. Deactivate Deactivates the device so that it can no longer be used in TEMS Investigation until you activate it again (using Activate, or else manually from the Navigator – see section 7.4.1). This activity has no unique properties. 18.17.1.5. Filemark Enables automatic filemarks. See section 10.1.1. • Filemark property: Filemark text string. NT11-20502 193 TEMS Investigation 13.1 User’s Manual 18.17.1.6. Radio Access Technology Lock Locks the device to a particular radio access technology (RAT). • Technology property: Specify the RAT to lock on. The choice “No Technology” releases a lock that has been previously applied. 18.17.1.7. Start Recording Starts recording of a logfile. (“Quick logging” will be used; see section 10.1.3.) • Prefix property: You can add a descriptive prefix to the default logfile name. The following characters are ignored if entered in this field: \ / : * ? ' < > | • Directory property: The directory where logfiles produced by the script will be stored. 18.17.1.8. Stop Recording Concludes the recording of the logfile that is being recorded. The logfile is closed. 18.17.1.9. Notes on Script-controlled Logfile Recording Note that logfiles always record data from all activated devices, not only the devices that participate in the script (i.e. those that have some device-specific activity assigned to them). While recording governed by a script is ongoing, the ordinary recording mechanism (for example, the Recording toolbar in the main window) is still enabled and will operate on that recording. You can thus stop the recording at any time by clicking the Stop Recording toolbar button. The execution of the script is not affected by this action, except that the anticipated Stop Logfile Recording activity becomes meaningless and will obviously fail. 18.17.2. Control Flow Activities For a hands-on tutorial on how to use these activities, please turn to section 18.11. 18.17.2.1. If–Else Causes the workflow to split into two or more branches, with a boolean condition attached to each branch. Each condition (except the catch-all “Any”: 194 Chapter 18. Service Control see below) is based on the outcome of a previous activity. Evaluation of conditions proceeds from left to right. At the top level the If–Else activity does not have any unique properties. Each branch of the construct, however, is constituted by an “if–else branch” activity which has the following property: • Condition Type property: To define a non-trivial condition, set Condition Type to Activity Result. The following attributes are then visible: Activity: The activity (identified by its name in the workflow) whose outcome will determine the value of the boolean expression. Operator: Boolean operator: “Equals” or “NotEquals”. Result: The activity result that you want to match. One of: Succeeded, Failed, Stopped by User, Stopped by Timeout, Stopped by Event. Setting Condition Type to “Any” creates a condition that always evaluates to true. This value should always be used as a catch-all condition for the rightmost if–else branch. (The If–Else construct is set up in that way by default.) For an example of usage, see section 18.11.2. 18.17.2.2. While • Condition Type property: Count: Fixed number of iterations. Time: Fixed execution time. When this duration expires, the while loop does not terminate immediately; rather, the current turn is completed first. (The running time is compared to the limit before a new turn begins.) Event: The while loop is terminated when any of the selected events is reported by the selected equipment. While loops can be nested arbitrarily. For an example of usage, see section 18.11.3. NT11-20502 195 TEMS Investigation 13.1 User’s Manual 18.17.2.3. Parallel This control structure causes the workflow to split unconditionally into two or more branches, each of which must involve different devices. There is no hard limit on the number of branches. A device can participate in more than one branch, provided that the device supports concurrent execution of the services involved (or several sessions using the same service). Each of the parallel branches is encapsulated within a Sequence activity (see section 18.17.2.4). This activity has no unique properties. For usage examples, see section 18.11.4. 18.17.2.4. Sequence This control structure formally defines a sequence of activities as a unit, allowing it to be treated as such. (For example, the entire sequence can be enabled or disabled in a single action, as exemplified in section 18.11.1.) This activity has no unique properties. 18.17.2.5. Wait The function of the Wait activity depends on its position in the workflow: • When following a (voice) Dial or Video Dial activity, the Wait gives duration to the call, extending it beyond the “call established” point for as long as specified by the wait time. If there is no Wait, the call is established and then terminated immediately. • When appearing elsewhere, the Wait activity does nothing, so in effect it temporarily suspends the execution of the workflow branch where it is located. After the wait time has expired, the execution proceeds to the next activity. The Duration property governs how long to wait. For usage examples, see sections 18.6, 18.11.3, and 18.11.4. 196 Chapter 18. Service Control 18.17.3. IP Activities 18.17.3.1. Network Connect Establishes a data service connection. In the packet-switched case, a PDP context is activated (UMTS) or a PPP session established (CDMA); in the circuit-switched case, the phone works like an ordinary modem and performs a dial-up. Whether NDIS or RAS is used is governed by the Mode parameter, as detailed under Configuration below. NDIS can be chosen for packetswitched only, whereas RAS can be used with both PS and CS. Ericsson Fixed Wireless Terminals must use an NDIS data connection. Note: For certain devices, setting up an NDIS connection requires prior configuration using a software application delivered with the device. – Some LTE devices must be connected to the network manually, using their connection manager applications, rather than automatically in the Service Control script. Be aware that in these cases, you must still include a Network Connect activity in your script. – For other LTE devices, the connection manager must be started to enable the Network Connect activity in scripts. See section 18.17.3.1.1 below for specifics in this regard on various devices and device categories. 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. (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.) If your data collecting device is unable to perform the IP sniffing, you can work around that problem by editing a line in the file <TEMS Investigation install dir>\Application\Investigation.exe.config, which by default reads: <dataServicesConfiguration ipSniffEnabled="true" ignoreIPSniffError="false" /> You can either disable IP sniffing by setting ipSniffEnabled="false", or you can ignore failure to start IP sniffing and go ahead with the execution anyway: ignoreIPSniffError="true". Please note that in either case, no KPI data can be collected. NT11-20502 197 TEMS Investigation 13.1 User’s Manual • Configuration property: Mode: Technology to use for connecting to the network: NDIS or RAS. If “Best available” is chosen, NDIS is first and RAS is second priority. For an NDIS connection to be establishable, the device must of course support NDIS. UMTS/LTE APN: The Access Point Name to use for UMTS and LTE networks. The parameter is not applicable to other cellular technologies. Leave this field empty if an APN is specified in the device (always needed for NDIS) or for the modem in Windows. Regarding devices for which the APN must be configured differently, see the Getting Started Manual, section 10.6.1. RAS Phone Number: Phone number to use when performing a RAS dial. For UMTS this is usually *99#; however, if a CID other than 1 is to be used you need to specify that value, as follows: *99***n#. For TD-SCDMA, enter *98*1#. For CDMA/EV-DO, enter #777. NDIS CID: The CID (Connection Identifier) to connect with when NDIS is used. User Name, Password: Certain operators require authentication in order to establish a data service connection. If this is the case for you, enter user and password here. IP Address: Local IP address. Leave blank if the IP address is provided automatically by the operator. Primary DNS: IP address of the primary domain name server. Leave blank if this is provided automatically by the operator. Secondary DNS: IP address of the secondary domain name server. Leave blank if this is provided automatically by the operator. Use Header Compression: Use of header compression for packetswitched. (Property of PS bearer.) Not applicable to circuit-switched. Use Data Compression: Use of data compression for packetswitched. (Property of PS bearer.) Not applicable to circuit-switched. 18.17.3.1.1. 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. Network Connect performed from within TEMS Investigation is referred to as “scripted Network Connect”. 198 Chapter 18. Service Control 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”. For “connection manager”, the shorthand “CM” is used below for convenience. LG LTE Devices • LG Generic: If the device is detected as “LG Generic”, the connection must be set up either from a CM or from the device menu system, and preconnected Network Connect will be used. • MS910: This device requires tethered network connection setup from the device menu system and preconnected Network Connect. • AD600, FM300, G7, G13, VL600: Do not use the CM for these devices. Doing so will cause a port conflict. Qualcomm LTE Devices (MDM9x00 Chipsets) • Normally, no CM should be used with any such devices. • If scripted Network Connect fails, then start the CM or enable tethering from the device menu system, and TEMS Investigation will use preconnected Network Connect instead. Samsung LTE Devices • General procedure: If an AT port exists for the device, TEMS Investigation will try to open that port and use it to control the network connection. No CM should then be used. If no AT port is available, or if the port is blocked, then the device must be configured using a CM, or tethering must be enabled in the device menu system (preconnected Network Connect performed in either case). • GT-B3710: Some older firmware of this device without an AT port requires that the CM should be running. TEMS Investigation then communicates with the CM to control the connection. With newer firmware, the device behaves like GT-B3730/3740: see next paragraph. • GT-B3730, 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, since a port conflict will then occur (both TEMS Investigation and the CM communicate with AT commands over the LTE Control Port). NT11-20502 199 TEMS Investigation 13.1 User’s Manual • R900, R910, R920, i510: These Android-based devices do not have a CM accompanying them. If the device firmware exposes an AT port, TEMS Investigation will use that port to perform a scripted Network Connect. If no AT port is present in the operating system, a tethered connection must be set up, and a preconnected Network Connect will be performed. Qualcomm HSPA+ Devices and Other Devices • Sierra Wireless devices should not need to have a CM running, provided they are detected as Sierra Wireless devices in TEMS Investigation. • These NDIS devices should likewise not require use of a CM: – Huawei E1820 – Novatel MC996D – ZTE Z006Z If scripted Network Connect fails, you can start the CM or enable tethering from the device menu system, and TEMS Investigation will use preconnected Network Connect instead. • For Qualcomm devices using a RAS connection, no CM should ever be needed, and scripted Network Connect should work fine. • Devices not mentioned in the foregoing generally require preconnected Network Connect. 18.17.3.2. Network Disconnect Terminates a data service connection. In the packet-switched case a PDP context is deactivated (UMTS) or a PPP session ended (CDMA); in the circuit-switched case the phone performs a hang-up. For certain NDIS-capable devices, an NDIS connection must be terminated using the PC application accompanying the device (compare the Network Connect activity, section 18.17.3.1). Note that in such cases, it is still necessary to include a Network Disconnect activity in the script. This activity has no unique properties. 18.17.3.3. PS Attach Performs a packet service attach. Note that this activity may not be needed since the device may have automatically attached to a PS network when powered on. 200 Chapter 18. Service Control This activity has no unique properties. 18.17.3.4. PS Detach Performs a packet service detach. This activity may be useful to make sure that the phone is not attached to the packet service when starting a measurement (for example, if it has attached automatically at power-on). This activity has no unique properties. 18.17.3.5. SIP Register Causes the device to register with a SIP or IMS server. This is a necessary preparation for a VoIP call; see sections 18.17.6.5, 18.17.6.6. A user account must exist on the server. • Configuration property: Proxy: The proxy server to use. May be omitted. Domain: The domain to register with. If Proxy is not used, a valid server name must be entered here. User Name: User name of account on the server. Password: Password for the server account. 18.17.3.6. SIP Unregister Causes the device to unregister from a SIP or IMS server used for VoIP. This activity has no unique properties. 18.17.3.7. Start IP Sniffing Starts capture of IP packets. Note that you do not have to use this command to obtain the data required for KPIs; such data is collected automatically. Compare chapter 31. NT11-20502 201 TEMS Investigation 13.1 User’s Manual • Configuration property: Packet Size: Determines how many bytes of each message will be presented. If you choose a fixed packet size, any further bytes in the message will be truncated. If you choose Full packet size, all messages are presented in full and the entire header is always decoded. Filter: Type of filtering to apply to IP packets. • Optimized Performance: Capture of IP packets is reduced to the minimum needed to compute KPIs. (Packets are filtered with respect to IP address, protocol [TCP/UDP], and port.) • Headers Only: The first 54 bytes of every IP packet are captured. This is frequently the preferable setting. • None: No filtering of IP packets. Note: This means that all packets belonging to any service used by the PC will be captured. (Packets are filtered with respect to IP address only.) The information element TCP Packet Loss and the event IP Interruption Time require that the Filter parameter not be set to “Optimized Performance”. 18.17.3.8. Stop IP Sniffing Stops capture of IP packets initiated by the Start IP Sniffing activity. This activity has no unique properties. 18.17.3.9. FTP Download Downloads a file from an FTP server. 202 Chapter 18. Service Control • Configuration property: Source File: The path and name of the file residing on the FTP server, e.g. srcdir/srcfile.dat. No explicit root symbol is used (no leading slash); if the file is in the root directory, type the file name only. Note that the correct orientation of the slashes is dependent on the FTP server operating system. Target File: Drive letter, path, and file name describing where to store the file on your computer, e.g. C:\targdir\targfile.dat. The drive letter must be included. If Concurrent file transfers is set larger than 1, multiple files are created, each with a different digit prefixed to the file name, e.g.: 0targfile.dat, 1targfile.dat. If this field is left blank, no files are stored; this is the default setting. Server Address: The IP address or host name of the FTP server. No ftp:// prefix is to be used. The address may not contain a path to a subdirectory. Server Port: The port on which the FTP server listens for requests. The default port number is 21. Firewall Mode: PASV or PORT, enabling or disabling passive FTP as defined in IETF RFC 959. Note that it is essential to set this correctly. Local Data Port: The data port the client will use for FTP download. Valid only when Firewall Mode = PORT. User: User name on the FTP server, if required. Password: User password on the FTP server, if required. Account: Account name on the FTP server, if applicable. Concurrent file transfers: If this parameter is set larger than 1 (the maximum is 5), then the specified number of FTP transfers will be executed in parallel, the same file being downloaded in each case. This provides an easy way to increase the load on the FTP server. Note also that you can conduct TCP load tests with the Network Bandwidth activity (see section 18.17.3.15). 18.17.3.10. FTP Upload Uploads a file to an FTP server. Please note the following: • For FTP upload with multiple phones, use different target files for each phone. NT11-20502 203 TEMS Investigation 13.1 User’s Manual • Paths and file names must have correct case. • Configuration property: Target File: Path and file name describing where and how to store the file on the FTP server, e.g. targdir/targfile.dat. No explicit root symbol is used; if you type a file name only, the file will be written to the root directory. Note that the correct orientation of the slashes is dependent on the FTP server operating system. Source File: Drive letter, path, and file name identifying the file to be uploaded, e.g. C:\srcdir\srcfile.dat. The drive letter must be included. Size to Upload: Size of the file to upload (only valid if Use Temporary File = True). It is possible to specify the unit as follows: B = byte, K = kilobyte, M = megabyte, G = gigabyte, T = terabyte. Alternatively, lowercase letters can be used with no difference in meaning. If you do not specify a unit, the number you enter is interpreted as a byte count. Use Temporary File: If set to True, a temporary file is created holding the data to upload. If set to False, no file is created. Server Address: The IP address or host name of the FTP server. No ftp:// prefix is to be used. The address may not contain a path to a subdirectory. Server Port: The port on which the FTP server listens for requests. The default port number is 21. Firewall Mode: PASV or PORT, enabling or disabling passive FTP as defined in IETF RFC 959. Note that it is essential to set this correctly. Local Data Port: The data port the client will use for FTP upload. Valid only when Firewall Mode = PORT. User: User name on the FTP server, if required. Password: User password on the FTP server, if required. Account: Account name on the FTP server, if applicable. Concurrent file transfers: Same function as for the FTP Download activity (section 18.17.3.10), except that files are uploaded. 204 Chapter 18. Service Control 18.17.3.11. HTTP Get Downloads a file from an HTTP server. • Configuration property: URL: URL of the file to download. Use Proxy Server: Select whether to use a proxy server for this connection. Proxy Server Address: Proxy server address. Proxy Server Port: Proxy server port. 18.17.3.12. WAP Get Downloads a page from a WAP server. Note that WAP pages that redirect the user to a different page cannot be downloaded. NT11-20502 205 TEMS Investigation 13.1 User’s Manual • Configuration property: URL: URL of WAP page to download. The WAP server can be specified as an IP address or host name; the http:// prefix is optional. Connection Mode: One of CO (Connection-oriented), CL (Connectionless), or WP-HTTP (Wireless Profiled HTTP). • CO and CL are used by WAP 1.x and require a WAP gateway. 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, whereas with CL this is not done. • WP-HTTP is used by WAP 2.0. This WAP version may use a WAP proxy, but this is optional. Gateway Address: (Appears when Connection Mode = CO or CL) The IP address of the operator’s WAP gateway. Gateway Port: (Appears when Connection Mode = CO or CL) The WSP port on the server. The default port numbers are 9201 (CO), 9200 (CL). Proxy Address: (Appears when Connection Mode = WP-HTTP; optional) The IP address of the WAP proxy. Proxy Port: (Appears when Connection Mode = WP-HTTP; optional) The WAP proxy port number. The default is 8080. User Agent: This is a string indicating, among other things, the make and model of the device and what WAP software it has installed. (Some WAP portals adapt their contents to the devices accessing them.) Example of User Agent string (for Sony Ericsson W995): User-Agent: SonyEricssonW995/R1DB Browser/NetFront/3.4 Profile/ MIDP-2.1 Configuration/CLDC-1.1 JavaPlatform/JP-8.4.1 206 Chapter 18. Service Control 18.17.3.13. Ping Initiates a sequence of pings. • Configuration property: Remote Address: The IP address or host name of the server to be pinged. Packet Size: Size in bytes of the packet sent with the Ping activity. The maximum size is 2000 bytes. Interval Time: Time between pings. Given in the format hh:mm:ss.ddd... . Number of Pings: The number of pings to send. There is no upper limit. Max Response Time: Maximum time to wait for each ping response. Given in the format hh:mm:ss.ddd... . 18.17.3.14. 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. UDP is more suitable than TCP for this purpose, since the rigorous acknowledgement and retransmission mechanisms of TCP (designed to guarantee full data integrity) will always slow down data throughput, even if the service does not require these safeguards. You can let TEMS Investigation run the UDP test in an automated fashion. The application will then start out at a low throughput rate and gradually increase the throughput until the packet loss becomes excessive. UDP testing is done against a PC that is running the application TEMS UDP Server. How to install and configure this software is described in the document “TEMS UDP Server User’s Manual”, found on the installation CD in the subdirectory Documents. The TEMS Investigation application has a UDP client built into it which interacts with this server. NT11-20502 207 TEMS Investigation 13.1 User’s Manual • Configuration property: Remote Address: The IP address or host name of the UDP server. 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. Specify the TCP control port to use here. UDP Mode: • Automatic: The TEMS Investigation UDP client will automatically determine the optimum data rate; see the introductory text above. In this case, the parameters from Packets Per Second onward (see below) are set automatically and are not editable. Please note that you cannot test Full Duplex in automatic mode. • Manual: You specify the data rate and packet rate yourself, using the parameters below. Direction: • Send: The client sends UDP data to the server. • Receive: The server sends UDP data to the client. • Full Duplex: Data is sent in both directions concurrently. Packet Size: The UDP packet size (in bytes) that will be used. Packets per Second: Number of UDP packets to send or receive per second. For Full Duplex mode, this is the packet rate in each direction. Throughput (kbit/s): The UDP throughput rate that will be used. The packet and throughput parameters work as follows. If you select automatic mode, all parameters are set by the application and cannot be edited. If you select manual mode, you specify the parameter values yourself. However, since the parameters are constrained by the relation (packets per second) × (packet size) = throughput, when you change one parameter the others will be adjusted so that the above equation still holds true. Duration (sec): The duration of the UDP session. Further Notes on UDP Testing Statistics on completed UDP sessions are output on the Summary tab of the Service Control Monitor, just as for other service sessions. See section 18.16.3. 208 Chapter 18. Service Control It must be kept in mind that the uplink UDP information elements in the category Data, which are updated continuously in the course of the UDP session (see Information Elements and Events, section 3.9) only indicate the amount of data sent. They do not indicate the amount successfully transferred to the server. Therefore, when the packet loss rate becomes nonnegligible, the UDP Upload Throughput information element is no longer reliable. To find out what percentage of packets was actually received by the UDP server, you need to check the summary statistics in the Service Control Monitor. The client uses TCP to obtain this information from the server after the UDP session has concluded. In contrast, the UDP Download Throughput is always accurate. 18.17.3.15. Network Bandwidth (Iperf Testing) This activity measures maximum TCP and UDP bandwidth performance by interacting with an Iperf server. Before you can use this activity, you must download the Iperf software and install it on the desired machine. See the Getting Started Manual, section 5.2.6 for details. UDP testing with the Network Bandwidth activity is similar to the UDP activity; see section 18.17.3.14. Measuring over TCP, on the other hand, is comparable to FTP with multiple concurrent file transfers; see section 18.17.3.9. NT11-20502 209 TEMS Investigation 13.1 User’s Manual • Configuration property: General section Remote Address: The IP address or host name of the remote server. Port: The port on which the Iperf server listens for requests. Protocol: The protocol to use for Iperf testing: TCP or UDP. Direction: • Send: The client sends data to the server. • Receive: The server sends data to the client. • Full Duplex: Data is sent in both directions concurrently. Use Listen Port: True or False. If you want to specify a port on which TEMS Investigation should listen for data (not required), set this parameter to True and enter the port under Listen Port. If you set the parameter to False, no such port is specified. Listen Port: See above. Duration: The duration of the Iperf testing session (hh:mm:ss). Telnet/SSH2 section Connection Client: Either Telnet or SSH2 can be used as protocol. Please note that SSH2 requires a special TEMS Investigation license option; see the Getting Started Manual, section 5.2.6. Port: Port on the remote server. User: User name on the remote server. Password: Password on the remote server. Path: Path to Iperf on the remote server. UDP section (used for UDP only) Bandwidth: UDP bandwidth (throughput) in Mbit/s. Buffer Size: UDP buffer size in kilobytes. Packet Size: UDP packet size in bytes. 210 Chapter 18. Service Control 18.17.3.16. Predefined Snippets for IP One snippet is provided for each data service related activity; all with the following structure: PS Detach → PS Attach → Network Connect → <data service activity> → Network Disconnect. 18.17.4. Messaging Activities 18.17.4.1. E-mail Send Sends an e-mail to an SMTP server. When composing an e-mail 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. • Configuration property: From: E-mail address of sender. To: E-mail address of recipient. Subject: Content of e-mail Subject field. Body Text File: Name of file containing e-mail body text. Attachment: (Optional) Name of file to enclose with the e-mail as attachment. Server Address: The IP address or host name of the SMTP server. Server Port: The port on which the SMTP server listens for requests. User: User name of e-mail account. Password: Password for e-mail account. Security: • None: No security is applied. • SSL/TLS: SSL or TLS is used during the whole e-mail session. • STARTTLS: The initial communication is not encrypted, but a STARTTLS command is issued later on to set up a secure session. NT11-20502 211 TEMS Investigation 13.1 User’s Manual 18.17.4.2. E-mail Receive Receives an e-mail from a POP3 server. When composing an e-mail 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. • Configuration property: Server Address: The IP address or host name of the POP3 server. Server Port: The port on which the POP3 server listens for requests. User: User name of e-mail account. Password: Password for e-mail account. Store Location: Full path to directory in which to store e-mails. All e-mail contents are written to a single file: header fields, body text, and attachments (if any). Security: • None: No security is applied. • SSL/TLS: SSL or TLS is used during the whole e-mail session. • STARTTLS: The initial communication is not encrypted, but a STARTTLS command is issued later on to set up a secure session. 18.17.4.3. MMS Send Sends an MMS. When composing an MMS script controlling both sender and receiver, it is best to use a Parallel structure. See sections 18.11.4 and 18.17.2.3. • Configuration property: Gateway section These are WAP settings, the same as for the WAP Get activity; see section 18.17.3.12. 212 Chapter 18. Service Control MMS Content section To: The phone number(s) or e-mail address(es) to send the MMS to. Multiple recipients can be specified, separated by semicolons. The receiving device can be identical with the sender. Message: Free text field containing the text message of the MMS (if any). Attachment: The file to send. A wide variety of file types, including plain-text files and frequently used image file formats, is supported. A file with an extension unknown to TEMS Investigation will be sent as an attachment to the MMS (content type “application/octet-stream”). Please note that operators generally impose a limit on the MMS file size. If you encounter problems sending MMS messages, try sending very small files to find out whether the size limit is causing the problem. MMS Message Center section URL: The URL of the MMS Center (usually beginning with http://). User, Password: Login credentials for MMS Center, if required. 18.17.4.4. MMS Receive Receives an MMS. 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). • Configuration property: Connection Parameters section: Same as for Network Connect; see section 18.17.3.1. The MMS Receive activity needs its own connection parameters since logging in to the MMS Center frequently requires connecting to a different APN. Gateway section: These are WAP settings, the same as for the WAP Get activity; see section 18.17.3.12. NT11-20502 213 TEMS Investigation 13.1 User’s Manual 18.17.4.5. SMS Send Sends an SMS. The SMS service is implemented with AT commands. For SMS Send activities to work, the phone must therefore support the following AT commands: • UMTS: AT+CMGF with format 0 or 1 and AT-CMGS. • CDMA: AT+MODE, AT+CMGW, and AT+CMSS. • Configuration property: Receiving Device: The phone number or e-mail address to send the SMS to. The receiving device may be identical with the sender. SMS Message: SMS message string. Request Delivery Report: Set this to True if you want the device to request a delivery report from the SMS Center. Delivery Report Timeout: Time to wait for the delivery report. 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. To stick with the SMS Center indicated on the SIM, set this parameter to False. SMS Center: Phone number to SMS Center. 18.17.4.6. SMS Receive Receives an SMS. 214 Chapter 18. Service Control • Configuration property: Match Type: • Regular expression: Enter regular expression under Message Match Pattern to match whole message text. The syntax is that of .NET Framework regular expressions. Reference:  msdn.microsoft.com/en-us/library/hs600312(v=VS.90).aspx • Starts with: Enter string under Message Match Pattern to match beginning of message text. • Ends with: Enter string under Message Match Pattern to match end of message text. Message Match Pattern: The pattern to use for matching incoming or stored messages. Search Text Messages in Device: If set to True, SMS messages stored in the device will be searched for matching messages. The point of doing this is to catch a message already received by the device before it performs the SMS Receive activity. 18.17.4.7. Predefined Snippets for Messaging One snippet is provided for each messaging activity; all with the following structure: PS Detach → PS Attach → Network Connect → <data service activity> → Network Disconnect. 18.17.5. Video Activities 18.17.5.1. Video Dial Dials a phone number and conducts a video call. After dialing, the device waits for the event Call Established. If this event does not occur, the device may retry the call. The retry behavior is governed by the On Failure property; see section 18.18.2. The call duration is specified by means of a subsequent Wait activity; see section 18.17.2.5. • Configuration property: Phone Number: The complete phone number (including country code) to call. Valid characters are: +, #, *, 0, ..., 9, and p (for pause). NT11-20502 215 TEMS Investigation 13.1 User’s Manual 18.17.5.2. Answer Waits for an incoming video call to arrive and answers it when it arrives. This activity has no unique properties. 18.17.5.3. Hang Up Hangs up a video call. This activity has no unique properties. 18.17.5.4. Streaming Download streaming video from a streaming server and play it in TEMS Investigation. For a general discussion of video streaming testing, see chapter 25. 216 Chapter 18. Service Control • Configuration property: RTSP Port: The RTSP port on the streaming server. The default port number is 554. RTP Port: Here you specify ports to use for RTP on your PC. The port entered and the three following ports will be allocated to RTP data. By default ports 5004–5007 are used. Use Proxy Server: Specify whether to access the streaming server through an RTSP proxy server. Proxy Address: The IP address or host name of the RTSP proxy. Prebuffer Length: Length (in seconds) of segment to buffer during initial buffering. Min: 1 s. Max: 20 s. Rebuffer Length: Length (in seconds) of segment to buffer during rebuffering. Min: 1 s. Max: 20 s. Streaming Duration: For Streaming Mode = “Live”, specify the duration of the streaming session here. When this time has expired, the activity terminates. Target File: Name and storage location for received streaming file. The format is .3gp. Streaming Mode: “Normal” means downloading a video clip of known length (on-demand streaming). “Live” means tapping into a live stream or repeating playlist delivered by a streaming server. Streaming Server: The IP address or host name of the streaming server. File To Stream: The file name of the video clip or streaming session description to be downloaded from the streaming server. 18.17.5.5. WAP Streaming This activity is used to do streaming via a WAP page. • Configuration property: Streaming Link: The text string of the WAP page RTSP link to the stream that is to be downloaded. URL ... User Agent: See the WAP Get activity, section 18.17.3.12. RTSP Port ... Streaming Mode: See the Streaming activity, section 18.17.5.4. NT11-20502 217 TEMS Investigation 13.1 User’s Manual 18.17.5.6. Predefined Snippets for Video • Video Call snippet: Video Dial → Wait → Hang Up. • WAP Streaming snippet: PS Detach → PS Attach → Network Connect → WAP Streaming → Network Disconnect. 18.17.6. Voice Activities 18.17.6.1. Dial Dials a phone number and conducts a circuit-switched voice call. After dialing, the device waits for the event Call Established. If this event does not occur, you may instruct the device to retry the call. The retry behavior is governed by the On Failure property; see section 18.18.2. The call duration is specified by means of a subsequent Wait activity; see section 18.17.2.5. • Configuration property: Phone Number: The complete phone number (including country code) to call. For AQM measurement, this should be the number to the Call Generator or MRU: see section 34.3.3. Valid characters are: +, #, *, 0, ..., 9, and p (for pause). 18.17.6.2. Answer Waits for an incoming CS voice call to arrive and answers it when it arrives. This activity has no unique properties. 18.17.6.3. Hang Up Hangs up a CS voice call. This activity has no unique properties. 18.17.6.4. PESQ Measurement Performs audio quality measurement (AQM), including PESQ, during a CS voice call. See chapters 33–35. 218 Chapter 18. Service Control • Configuration property: Measurement Type: • M2F DL + UL: Mobile-to-fixed audio quality measurement using Call Generator. • M2M DL: Mobile-to-mobile audio quality measurement using Mobile Receiving Unit (MRU). • M2M DL + UL: Mobile-to-mobile audio quality measurement using Audio Capturing Unit (ACU). PESQ Duration: The length of time for which to collect audio quality measurements. Audio Channel (only used for M2M DL + UL): • CH1: Choose this channel for the phone connected to LINE IN 1/ LINE OUT 1 on the ACU. • CH2: Channel for phone connected to LINE IN 2/LINE OUT 2. • CH3: Channel for phone connected to LINE IN 3/LINE OUT 3. • CH4: Channel for phone connected to LINE IN 4/LINE OUT 4. Recording Threshold (only used for M2M DL + UL): All audio files (*.pcm) with a PESQ value worse than this threshold value will be stored under My Documents\TEMS Product Files\TEMS Investigation 13.1\PESQ. The point of this mechanism is to have poor quality files automatically saved for further study. 18.17.6.5. VoIP Dial Dials a voice-over-IP call. See also section 18.17.6.9. • Configuration property: Phone Number: The phone number to call. Codec: Voice codec, one of: G.711 A-law, AMR-WB, or AMR-NB. Codec Rate: Voice codec rate. NT11-20502 219 TEMS Investigation 13.1 User’s Manual 18.17.6.6. VoIP Answer Waits for an incoming voice-over-IP call to arrive and answers it when it arrives. See also section 18.17.6.9. • Configuration property: Codec: Voice codec, one of: G.711 A-law, AMR-WB, or AMR-NB. Codec Rate: Voice codec rate. 18.17.6.7. VoIP Hang Up Hangs up a voice-over-IP call. This activity has no unique properties. 18.17.6.8. VoIP Voice Quality Performs audio quality measurement (AQM) including PESQ. See chapter 36. Note that the measurements are contained in special AQM information elements distinct from those for CS voice: see Information Elements and Events, section 3.9 (“VoIP PESQ Score”). • Configuration property: Duration: The length of time for which to collect voice quality measurements. Store AQM files: Yes or No. MOS limit: If the MOS value for an audio file is lower than or equal to this threshold, the audio file will be saved under [My] Documents\TEMS Product Files\TEMS Investigation 13.1\PESQ. 18.17.6.9. How to Set Up VoIP Testing A number of things must be observed when setting up and running VoIP scripts. For a full tutorial on testing VoIP, see the technical paper “VoIP Testing with TEMS Investigation”, found on the installation CD in the subdirectory Documents. Below is a summary of the salient points. • 220 The calling device and called device must be connected to different PCs, each running an instance of TEMS Investigation. This setup is necessary to enable PESQ measurement for VoIP. Chapter 18. Service Control • You must not have any other measurement devices plugged into either PC when doing VoIP testing. You cannot have an Ethernet cable connected either, nor any other internet connections in parallel. All network interfaces except the testing device must be disabled, both fixed and wireless. • Two scripts must be prepared, one for the caller and one for the callee. Predefined VoIP snippets are provided; see section 18.17.6.10. • 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. Furthermore, the callee must be registered before the caller places the call. The callee script must therefore complete its SIP Register activity before the caller script reaches VoIP Dial. • The Duration parameter should be set differently for caller and callee, so that it can be controlled which side hangs up the call. 18.17.6.10. Predefined Snippets for Voice • Voice Call snippet (CS): Dial → Wait → Hang Up. • VoIP Dial snippet: Network Connect → SIP Register → VoIP Dial → VoIP Voice Quality → VoIP Hang Up → SIP Unregister → Network Disconnect. • VoIP Answer snippet: Network Connect → SIP Register → VoIP Answer → VoIP Voice Quality → SIP Unregister → Network Disconnect. 18.18. General Activity Properties These properties are common to all or many activity types. Activity-specific properties are covered in section 18.17 in connection with their respective activities. 18.18.1. Activity Section • Name: Name given to the activity. (Only appears for certain non-editable activities such as the “root” activity at the top and bottom of the workflow.) • Enabled: True or False. If set to False, the activity is disabled and will not be performed when the script is run. This is indicated by the activity being dimmed by a semi-transparent greenish box in the flowchart. NT11-20502 221 TEMS Investigation 13.1 User’s Manual • Configuration: Reference to a configuration set of the type associated with this activity. For example, for FTP Download, an FTP server configuration set needs to be selected here. The combo box is populated with all existing configuration sets that fit the activity; if no such configuration set exists, you need to create one in the Configuration Sets pane. • Equipment: The EQ to which the activity is assigned. • Description: Free-text field where you can optionally enter a description of the activity. 18.18.2. Failure Handling Section • On Failure: This property determines what will happen if an activity fails (when first attempted). – Continue Script Execution: If an activity fails, the activity is abandoned, and the execution proceeds to the next activity in the workflow branch in question. – Stop Script Execution: If an activity fails, the activity is abandoned, and the whole script is terminated. – Retry: If an activity fails, it will be retried. When you choose this option, a set of further parameters appear: Retries – the number of retries; Delay – the time to wait before each retry; On Failure – what action to take if all retries fail (continue or stop script). 18.18.3. Termination Section • 222 Abort: – Never: The activity will execute as long as it takes to complete. – On Timeout: The activity will be aborted after a fixed period of time, unless it has already completed before that time. What you indicate here is thus a maximum duration for the activity. Chapter 18. Service Control – On Event: The activity will be aborted if and when one of the specified events occurs; otherwise it will run to completion. Note that this property is also possessed by the root activity, in which case it applies to the entire script. 18.19. Configuration Sets 18.19.1. Descriptions of Configuration Sets All types of configuration set are associated with a particular service. For that reason each configuration set is described in section 18.17 in conjunction with the activity or activities that use it. 18.19.2. Managing Configuration Sets You can manage configuration sets using the Service Settings utility. For a tutorial on how to use these functions in conjunction with script saving/loading in order to port scripts between PCs, see section 18.20.1. • To launch the Service Settings utility, choose File → Manage Settings. Alternatively, in Windows, choose Start → [All] Programs → Ascom → TEMS Products → Utilities → TEMS Investigation 13.1 Service Settings. This window appears: 18.19.2.1. Exporting Configuration Sets To export configuration sets you use the Export tab. All configuration sets currently known to the application are listed in the window. NT11-20502 223 TEMS Investigation 13.1 User’s Manual • Select the configuration sets you want to export by clicking them in the list. Shift + click and Ctrl + click can also be used, in standard Windows fashion. To select/deselect all sets, right-click in the list and choose Select All/Unselect All. • Now select where to export the configuration sets. Click the Target button and point to the desired directory. • To perform the export, click the Export button. Each configuration set is now exported as a file named according to the format TEMS.Services.Settings.<service name>Settings.<...>.config. 18.19.2.2. Importing Configuration Sets To import previously exported configuration sets, you use the Import tab. • Click the Source button and browse to the directory you want to import from. The window is populated with all configuration sets found in that directory. • Select the configuration sets you want to import by clicking them in the list. Shift + click and Ctrl + click can also be used, in standard Windows fashion. To select/unselect all sets, right-click in the list and choose Select All/Unselect All. • To perform the import, click the Import button. 18.19.2.3. Deleting Configuration Sets You can delete a configuration set from TEMS Investigation by selecting it on the Export tab and clicking the Delete button. From the Tools menu you can delete all configuration sets by choosing Clear Settings. If the Enable Backup option is selected, a backup of the configuration sets will be created whenever you use the Clear Settings command. • To restore configuration sets from a backup, choose Tools → Manage Backups, select the backup of interest from the list, and click the Restore button. • To delete a backup, select it and click Clear. 224 Chapter 18. Service Control 18.20. Saving and Loading Scripts To save a script to file, click the Save button on the Service Control Designer toolbar. The file will receive the extension .tsc (for “TEMS Service Control”). The Save Script dialog contains the following options: • Description: Free-text field where you can optionally enter a description of the script. • Format: You can save the script either with or without the configuration sets it uses. Note that configuration sets can also be saved separately: see section 18.19.2. – Standard: No configuration sets are saved with the script. This means that changes to a configuration set will automatically propagate to all scripts that reference it. Choose this option if you are going to use the script on one PC only. (This is the default setting.) – Redistributable: All configuration sets referenced in a script are saved with the script, making the TSC file a self-contained and independent entity that can be immediately reused on a different PC. Choose this option if you are going to use the script on several computers. To open an existing script stored on file, click the Load button on the Service Control Designer toolbar. 18.20.1. Tutorial on Porting Scripts between PCs Follow these steps to share a script and its related configuration sets between two computers: NT11-20502 225 TEMS Investigation 13.1 User’s Manual • • On the “sender” PC: – Save your workspace. – Save your script with Format set to Redistributable. – Export your configuration sets. 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. – Start TEMS Investigation. – 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. 18.20.2. Saving Workflow as Image • You can also save the contents of the workflow pane as an image. To this end, choose File → Save As Image in the Service Control window and select the desired image file format. 18.21. Further Functionality in the Service Control Designer Window 18.21.1. 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. By default all activities are shown (“All”). 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. 226 Chapter 18. Service Control 18.21.2. Context Menu in Workflow Pane The context menu that appears when you right-click in the workflow pane has functionality that is mostly mirrored in other places: in the regular window menu and in the Properties pane. The rest is standard Windows functionality, 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, on-failure behavior) of several activities at once. 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, then right-click the selection and choose the desired command from the context menu. 18.21.3. Zooming the Workflow Pane In the workflow pane, the mouse pointer by default has the usual point-andclick function. You can however switch the mouse to zoom mode, where mouse pointing actions have the effect of zooming the workflow pane in or out. After you click the Zoom In button on the window toolbar, mouse clicks in the workflow pane will magnify its contents in predefined steps. You can also click and drag to select a portion of the workflow pane that you want to enlarge. To reverse the mouse-click zoom function, click the Zoom Out button on the window toolbar. To return the mouse to pointing mode, click the Pointer button. NT11-20502 227 TEMS Investigation 13.1 User’s Manual 19. Device Properties From TEMS Investigation you can view and modify certain properties of devices. To access the property dialog of a device, do as follows: • Right-click on the device on the Navigator’s Equipment tab. • Choose Properties from the context menu. 19.1. Overview of Properties by Device This overview covers Sony Ericsson phones, Nokia phones, and the Samsung Galaxy S 4G phone. Other supported devices share little or none of the control functionality listed here. Regarding control functions applied from the Navigator, see section 8.1. 228 Chapter 19. Device Properties Nokia NTM3 Samsung Galaxy S 4G Sa No W600i K600i K790i/a K800i TM506/Z750i C702/C905*/W760i/W995* Control Function Xperia X10/arc Sony Ericsson Access class control Barred cells, access control BLER target control (WCDMA) C/A measurements (GSM) Channel verification (GSM)1 Disable handover (GSM) EDGE capability control HSPA capability control L3 messages, discard/ignore Lock on ARFCN Lock on BSIC Lock on PLMN Lock on SC Lock on UARFCN Prevent handover2 (GSM) Redial on block Reserved cells, access control Speech codec control (GSM)3 TxPower control (GSM) 1. See chapter 42. 2. That is, prevent handover to specified ARFCNs. 3. Changing order of priority between codecs is supported for C905*/W995* only. NT11-20502 229 TEMS Investigation 13.1 User’s Manual 19.2. Properties of Sony Ericsson Phones and Samsung Galaxy S 4G This section deals with viewable and editable properties of Sony Ericsson phones. It is also applicable to the subset of those properties exhibited by the Samsung Galaxy S 4G. When you activate the phone in the application, the phone retrieves all settings you have specified for it. Any changes to the properties will apply as long as the phone remains activated in TEMS Investigation. Functions of Dialog Buttons Besides OK and Cancel, the Properties dialog contains the buttons Restore Defaults and Apply. These buttons have the following functions: • Apply saves all changes made to settings, like OK, but without exiting the dialog. • Restore Defaults resets all settings to their defaults, without exiting the dialog. 19.2.1. Extended Reports This item appears for certain Sony Ericsson phones, listing messages and mode reports delivered by the phone. You can turn the reporting on and off for each item listed. Note the following: • “Path Searcher Report (A2)” must be checked for the Finger Info information elements (WCDMA) to be valid. • Regarding “TPC Info Per Cell”, see Information Elements and Events, section 6.1. 19.2.2. Common Controls Each of the nodes in the property grid contains a field Default/Modified. At the outset this field has the value Default everywhere, which means no alteration of regular phone behavior. To activate a control function, you must switch the corresponding “Default/Modified” field to Modified (can be done by double-clicking the value), then proceed to set the other parameters as desired according to the subsections below. 230 Chapter 19. Device Properties 19.2.2.1. CAS Access Class Here you can manipulate access class settings ( 3GPP 22.011, chapter 4). Classes 0 ... 9 Every phone is by default allocated randomly to one of these classes. You can change the default allocation here. Classes 10 ... 15 Membership of these classes entitles a phone to make access attempts in various special situations. Check the classes that you want the phone to be a member of. 19.2.2.2. CAS Lock on PLMN You can lock the phone on a PLMN, specified by an MCC and MNC combination. Note that this function can be meaningfully applied only if the SIM supports multiple PLMNs. If you lock on a PLMN that is not available, the phone will go into limited service mode. MCC, MNC 19.2.2.3. Define the target PLMN here. CAS Speech Codec For certain phone models (indicated in section 19.1) you can both define a subset of codecs that should be enabled and change the default order of priority between the selected codecs. Speech codecs NT11-20502 When you click the “...” button in the right-hand field listing codecs, the user interface shown below appears. 231 TEMS Investigation 13.1 User’s Manual • Use the arrow buttons in the middle to move any codecs you want to disable from the Selected box to the Available box. Those that you leave in the Selected box will remain enabled. • Then use the arrow buttons on the right to adjust the order of priority for the selected codecs. For other phone models you can only select which codecs should be enabled; this is done in a regular property grid. By default all codecs are enabled. 19.2.2.4. 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. Number of adjacent channels 232 Specify one or two channels; see above. Chapter 19. Device Properties 19.2.2.5. GSM Barred Cells Here you can alter the phone’s behavior in GSM idle mode with respect to barred cells. If the “barred” flag is set for a cell, this normally prevents the phone from accessing it. Mode Normal: The phone will not camp on barred cells. All cells allowed: The phone will camp on any cell, ignoring cell barring. Only barred cells allowed: The phone will camp only on barred cells. 19.2.2.6. GSM Cell Selection When the phone is in idle mode, it can be locked to one channel or to a set of channels. This inhibits all reselections to other channels, regardless of the signal strength and quality of neighboring cells. The inverted operation is also possible, namely to prevent reselection to a specified channel set. ARFCNs Check the channels you want to lock on or exclude. Control mode Normal: No effect on default behavior. Lock: The phone will be locked to the set of channels checked under ARFCNs. Prevent: The phone will be prevented from camping on the channels checked under ARFCNs. Note: To apply this kind of lock, you must first lock the phone to the GSM RAT (see section 8.1.6) and to a GSM band (see section 8.1.3). NT11-20502 233 TEMS Investigation 13.1 User’s Manual 19.2.2.7. GSM EDGE Capability For EDGE-capable phones you can choose to disable the EDGE capability. This function can be used to force data transfer over GPRS rather than EDGE. EDGE allowed Yes: EDGE enabled. No: EDGE disabled. 19.2.2.8. GSM Handover When the phone is in dedicated mode, you can manipulate its handover behavior. Specifically, you can do one of the following: • Prevent handover to specified channels. The phone will then report no RxLev for these channels. • Force handover to a specified channel, or restrict handovers to a chosen channel set. The phone will then report a very high RxLev for any such cell, a very low RxLev for the serving cell, and no RxLev for other neighboring cells. • Disable handover altogether. ARFCNs Check the channels you want to prevent handover to or restrict handover to. Control mode Normal: No effect on default behavior. Lock: The phone will be able perform handover only to the set of channels checked under ARFCNs. Selecting a single channel forces handover to that channel. Prevent: The phone will be prevented from performing handover to the channels checked under ARFCNs. Disable handover: The phone will be prevented from performing any handovers at all. 234 Chapter 19. Device Properties 19.2.2.9. GSM Tx Power For each GSM frequency band you can specify a Tx Power value which will override the network allocated Tx Power. Regarding the latter, see  3GPP 45.005, section 4.1. Tx Power GSM 850 (dBm) Enter the desired new Tx Power in dBm for the GSM 850 MHz band. (etc.) 19.2.2.10. Layer 3 Messages For certain Sony Ericsson UEs you can discard Layer 3 messages of specified types. Default/Discard To enable the function, select Discard here. Loaded Number of Layer 3 message types selected under Message types. Message types Click the browse button (marked “...”). In the dialog that appears, check the types of Layer 3 message that you want to discard. The phone can store up to 10 message types in its memory. Discarded messages are colored red in the Layer 3 Messages window and tagged with a special note in the plain-text decoding; see section 24.3. 19.2.2.11. WCDMA Barred Cells Here you can modify the phone’s behavior with respect to accessing of barred, reserved, and other cells: Normal NT11-20502 No change from normal cell barring behavior. 235 TEMS Investigation 13.1 User’s Manual Mode All cells allowed: The phone will access any cell, also barred and reserved ones. Only barred: The phone will only access barred cells. Only reserved: The phone will only access reserved cells. Only reserved for operator use: The phone will only access cells that are reserved for operator use. Only reserved for future use: The phone will only access cells that are reserved for future use. Only barred or reserved: The phone will only access cells that are barred or reserved. 19.2.2.12. WCDMA BLER Target For certain Sony Ericsson UEs you can override the BLER target set for the UE by the network. BLER Target value The BLER target for the UE will change to the value you set here. Regarding the format of this value, see  3GPP 25.331. 19.2.2.13. WCDMA Cell Selection Here you can lock the UE to selected UARFCNs or scrambling codes in WCDMA, in idle mode as well as connected mode. Control mode Normal: No effect on default behavior. Lock: The phone will be locked to the set of UARFCNs/scrambling codes that you select in the UARFCNs and Scrambling codes fields. 236 Chapter 19. Device Properties Scrambling codes Lists the scrambling codes to lock on. To be able to specify target SCs, you must first have selected a single target UARFCN. Up to 32 SCs can then be listed as targets. If you have specified multiple target UARFCNs, you cannot add any target SCs (the Scrambling codes field is grayed). UARFCNs Check the UARFCN you want to lock to. Up to 32 target UARFCNs can be specified. However, note that if you list more than one UARFCN, you cannot also select scrambling codes as targets. Note: To apply this kind of lock, you must first lock the phone to the WCDMA RAT (see section 8.1.6) and to a WCDMA band (see section 8.1.3). 19.2.2.14. WCDMA RRC Radio Capability For phones supporting HSDPA, or all of HSPA, you can enable or disable these capabilities. Allowed technologies R99 only: Only WCDMA R99 is enabled. HSDPA: HSDPA is enabled (but not HSUPA, even if the phone supports it). HSDPA + HSUPA: Both HSDPA and HSUPA are enabled. HSDPA category If HSDPA is enabled, you can set here what HSDPA (HS-DSCH) category the phone should report. These categories are defined in  3GPP 25.306, table 5.1a. HSUPA category If HSUPA is enabled, you can set here what HSUPA (E-DCH) category the phone should report. These categories are defined in  3GPP 25.306, table 5.1g. NT11-20502 237 TEMS Investigation 13.1 User’s Manual 19.3. Properties of Nokia Phones (NTM3) 19.3.1. Channel Lock Control (GSM) In GSM mode, you can lock the phone to a single ARFCN. The channel lock function works in idle mode only. Enable channel lock Set this to Yes to enable the channel lock function. Band Specify the band containing the channel you want to lock on. ARFCN Specify the ARFCN of the channel to lock on. 19.3.2. GSM Cell Barring Control This setting governs how the phone behaves with respect to barred cells in GSM. Cell barring Normal: The phone will not camp on barred cells. Reversed: The phone will camp only on barred cells. Ignored: The phone will camp on any cell, ignoring cell barring. 19.3.3. Sector Lock Control (WCDMA) These settings apply in WCDMA mode. The phone will be locked to the chosen UARFCN and scrambling code. Enable sector lock Set this to Yes to enable the sector lock function. UARFCN Specify the UARFCN to lock on. Scrambling code Specify the scrambling code to lock on. 238 Chapter 19. Device Properties 19.4. Properties of Qualcomm Chipset Based Devices Properties of Qualcomm chipset based devices are limited to enabling and disabling of various logs. Regarding the NV (Nonvolatile) interface, see section 8.1.4. 19.5. Properties of Samsung LTE Modems For Samsung LTE modems, various message categories can be enabled and disabled. Common; LTE For each of these top-level message categories, the following options exist: All enabled: All messages are enabled. All disabled: All messages are disabled. Select messages: When this option is chosen, further fields appear which allow you to enable or disable various subcategories of messages. (The settings you make here do not affect the scope of All enabled, which always means all messages without restriction.) Please note that if you disable everything here, no reports from the MS device channel will be displayed in TEMS Investigation. 19.6. Properties of GPS Units You can inspect and change some properties of a GPS unit. What properties are editable depends on what product you are using. NT11-20502 239 TEMS Investigation 13.1 User’s Manual 20. Events TEMS Investigation generates events to indicate noteworthy occurrences in the cellular network. A number of events are predefined; in addition to these, you can define events of your own. 20.1. Presentation of Events Events that occur are listed in the Events window. Regarding this window, see Information Elements and Events, section 8.9. Events can also be presented: • as symbols on the map (see section 29.5.4) • as symbols and vertical lines in line charts (see section 27.4) • as audio signals (see section 20.7). 20.2. Predefined and User-defined Events Definitions of all predefined events are found in Information Elements and Events, chapter 7. User-defined events are specified by logical expressions, which trigger the event when they evaluate to true. These expressions can contain: • Layer 3 messages • other events • conditions involving information elements. 20.3. • Setting Up a User-defined Event Open the Event Definition window. Click Add. 240 Chapter 20. Events Name Enter a name for your user-defined event. System The choice in this combo box governs what will be selectable when you click the Add Element button. Mobile If you choose a specific external device in this combo box, the event is triggered only when the event expression is true for this particular device. If you choose “Any”, the event can be triggered by any device. You build up the event expression by using the add buttons on the right. The structure of the expression is displayed in the box beneath the Name field. 20.3.1. • Click Add Element and choose Layer 3 from the context menu. Choose the desired message from the dialog that appears. 20.3.2. • Adding a Layer 3 Message to the Event Expression Adding an Information Element Criterion to the Event Expression Click Add Element and choose Information Element from the context menu. NT11-20502 241 TEMS Investigation 13.1 User’s Manual Information element Choose an information element. Argument If the information element has an argument, specify it here. Value: Changed Choose this to trigger the event whenever the value of the selected information element changes. Value: Threshold Choose this to trigger the event when the selected information element assumes, exceeds, or drops below a certain value. Choose a threshold operator (“=”, “>”, or “<”), and set the threshold value. 20.3.3. Adding an Event to the Event Expression • In the Add User Defined Events dialog, click Add Element and choose Event from the context menu. • In the new dialog that appears, choose an event from the combo box. 20.3.4. Adding an Operator/Delimiter to the Event Expression To build a composite logical expression, you will need logical operators and possibly delimiters (brackets). Available operators are AND, OR, XOR, and NOT. 242 Chapter 20. Events • In the Add User Defined Events dialog, click Add Operator and select an operator or delimiter from the context menu. Note: Events used in the expression for a user-defined event can be combined with the OR operator only (not with AND, NOT, or XOR). Keep adding items to the event expression until it is complete. Then click OK to exit the Add User Defined Events dialog. The new event is now added to the list in the Event Definition window. See section 20.6 below for an example of a logical expression. Note: If a user-defined event is added or modified after a logfile is loaded, the logfile must be reloaded for the events to become visible. 20.4. Editing User-defined Events • Select the event you want to edit in the Event Definition window. • Click Edit and make the desired changes. 20.5. Deleting User-defined Events • Select the event you want to delete in the Event Definition window. • Click Delete. 20.6. Example of Event Definition This example is taken from GSM. There are many possible causes of poor C/I values. Two common ones are co-channel and adjacent channel interference. In certain circumstances, however, the main problem is not interference from other callers, but the fact that the signal is overwhelmed by assorted random disturbances – i.e. what is usually called “noise”. This means thermal noise generated within the circuits of the phone as well as external background noise from a plethora of sources, NT11-20502 243 TEMS Investigation 13.1 User’s Manual including other man-made signals so faint that they merely add up to a quasirandom disturbance. 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. 1. From the Configuration folder in the Navigator, open the Event Definition window. 2. Click Add. 3. Name the event “Noise Indication” (or whatever you like). 4. Click Add Element and choose “Information Element” from the context menu. 5. From the Add Information Element combo box, choose “C/I Worst”. 6. Choose “Threshold”, and choose “<” from the combo box. 7. Set Value to 10. 8. Click OK. 9. Click Add Operator and choose “AND”. 10. Click Add Element and choose “Information Element”. 11. Under “Information Element” choose “RxLev Sub (dBm)”. 12. Choose “Threshold” and choose “<” from the combo box. 13. Set Value to –99. 14. Click OK. The event expression should now look as follows: C/I Worst < 10 AND RxLev Sub (dBm) < –99 15. Click OK to finish. The event is now added to the event list and can be used in the Map window and in other presentation windows. 244 Chapter 20. Events 20.7. Audio Indications for Events For each event you can specify an audio signal to be played when the event occurs. This is useful if you are performing a drive test on your own and need to keep your eyes on the road. To associate events with audio signals, you use the Audio Indications window found in the Configuration folder in the Navigator. 20.7.1. Adding Audio Indications Click Add in the Audio Indications window. Mobile Choose an external device. Event Choose an event. Sound Enter the path to the WAV file you want to use, or click Browse and select the file. Use PC speaker Check to use the internal speaker of your PC. Test Listen to the selected sound file. • Click Apply to add the current audio indication and keep the dialog open. • Click OK when you are done adding audio indications. NT11-20502 245 TEMS Investigation 13.1 User’s Manual The events that are now associated with sounds are listed in the Audio Indications window. 20.7.2. • Editing Audio Indications Select the audio indication to be edited. Click Edit and make the desired changes. 20.7.3. Activating Audio Indications Audio indications are by default active. They may however be deactivated (see section 20.7.4 below). To activate a deactivated audio indication: • Select the audio indication. Click Activate Sound. 20.7.4. Deactivating Audio Indications To deactivate an audio indication: • Select the audio indication. Click Deactivate Sound. 20.7.5. Muting All Audio Indications To disable all audio indications, independently of their status (active or deactivated): Click Mute All. From now on, no audio indications will be played until you decide to enable them again. You might find this attractive when doing post-processing. 246 Chapter 20. Events To re-enable all audio indications: Click Undo Mute All. The status of the audio indications will remain the same as before you clicked Mute All: active audio indications will start playing again, and deactivated ones will remain deactivated. 20.7.6. • Saving and Loading Audio Indications Select the audio indication you want to save. Click Save and enter a file name (extension .svt). Click Open to load an *.svt file in the Audio Indications window. 20.7.7. • Deleting Audio Indications Select the audio indication to be deleted. Click Delete. NT11-20502 247 TEMS Investigation 13.1 User’s Manual 21. Presentation: Basics This chapter covers the fundamentals of data presentation. 21.1. Presented Data The presentation windows are used to present information elements, events, and messages, either in real time or during logfile replay. Real-time and logfile data are presented in fundamentally the same way; differences are noted whenever relevant in the chapters that follow. For an overview of information element categories, see Information Elements and Events, chapter 2. Full details on information elements follow in chapters 3 and 4 of that volume. Regarding predefined events, see Information Elements and Events, chapter 7. 21.2. Types of Presentation Window The following presentation windows are available in TEMS Investigation: • Status windows: chapter 22 • Event Counter windows: chapter 23 • Message windows: chapter 24 • The Video Monitor window: chapter 25 • The GPS window: chapter 26 • Line charts: chapter 27 • Bar charts: chapter 28 • Map windows: chapter 29. 248 Chapter 21. Presentation: Basics 21.3. Device Channels: MS/DC/PS In presentation windows, as opposed to the Navigator and Service Control components, devices are represented by their channels: • MS for radio measurements • DC for data service measurements • PS for positioning equipment. The EQ designations currently do not appear in presentation windows. 21.4. Window Updating and Synchronization A fundamental distinction can be made between • “snapshot” windows, which show the situation at one instant in time and are constantly refreshed in drive testing mode (status windows, bar charts, GPS window, Video Monitor) and • “history” windows, which accumulate information and display the whole history of the testing session, or statistics on it (maps, line charts, message windows, Event Counter windows). All windows are synchronized. When you select a point in time in a history window, other history windows highlight the same time instant, whereas the snapshot windows are updated to show the data that was current at this time. Note: The above applies without qualifications in replay mode. In drivetesting mode, however, things are somewhat different: it is still possible to inspect previously recorded data, but in many window types, as soon as a new message arrives from the phone, the presentation automatically reverts to the present time. The exactness of the synchronization is limited by the time resolutions of the various presentations. For example, the line chart plots two points every second. The map plots a maximum of two new theme markers every second. Regarding synchronization between message windows and other windows, see section 24.5. NT11-20502 249 TEMS Investigation 13.1 User’s Manual 21.5. Color Ranges In many types of presentation windows, it is possible to visualize numeric information element values by means of a range of colors. These colors are defined in the Navigator; see section 4.3 for details. You can always turn off the color coding and use a fixed color for drawing. In status windows, custom color ranges for information elements can be defined, for use in that window only. Whenever an information element is invalid, or has no color defined for its current value, it is drawn in black in graphical presentations and left out in textual presentations. 21.6. Other Window Properties The appearance of any presentation window can be changed by altering the window properties, which are accessed by right-clicking in the window and choosing Properties from the context menu. 21.7. Export/Import of Presentation Windows Status windows, line charts, maps, and message windows can be exported, that is, saved along with all their current settings in a file separate from the workspace. You can later import the window into the application again by opening the file. 21.7.1. Export To export a presentation window, proceed as follows: • Select the window. • From the File menu, choose Export. • Type a file name and click Save. The extension depends on the window type; see appendix B. 21.7.2. Import To import a saved presentation window, proceed as follows: • 250 Focus a presentation window of the same type as the one you want to import. (Open a new window if necessary, and click it.) Chapter 21. Presentation: Basics • From the File menu, choose Import. • Select the desired file and click Open. NT11-20502 251 TEMS Investigation 13.1 User’s Manual 22. Status Windows This chapter explains the workings of status windows. 22.1. General The status windows present information elements in tabular form. A number of ready-made windows are provided for presenting particular categories of information; these are listed in Information Elements and Events, chapter 8. In addition, a blank template is available which you can use to compose your own status windows. To set up a status window, use the setup wizard (section 22.2). The setup wizard is intended to be run only once. Later on, you can modify the window using the Properties dialog, which is described in section 22.3. 22.2. Setting Up Status Window Contents The contents of a status window are conveniently set up using the setup wizard. Note: Setting the number of columns and rows in the status window cannot be done with the setup wizard. Also, you cannot enter text in the status window using this tool. For these purposes you must use the Properties dialog. See section 22.3. • 252 Right-click in the status window and choose Setup Wizard. Chapter 22. Status Windows Name Name the new status window. Note that changing the name later will create a new status window, and the contents of the current window will be lost. Font Click Browse and select a font. • Click Next to proceed to step 2 of the setup wizard. • To add an information element, click Add. This dialog opens: Mobile NT11-20502 Choose which device to pick the information element from. 253 TEMS Investigation 13.1 User’s Manual System Choose an information element category. See Information Elements and Events, chapter 2. Information element Choose an information element. Argument Enter an argument for the information element (if it needs one). • Select the View tab. Value Check to display values alphanumerically. Left, Center, Right Choose alignment for the displayed values. Bar Check to display numeric values as colored bars. Constant length Draw the bar with constant length. This is useful for information elements that represent states, etc. and can only assume a limited number of values. Min/Max indicator Keep track of the all-time-low and all-time-high values by means of vertical lines. 254 Chapter 22. Status Windows Associated information elements Information Element 1 Information Element 2 • This checkbox with accompanying combo boxes appears only for the CDMA window Finger Info. In that window, 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. See screenshot in section 22.6.2. Select the Color tab to customize colors and color ranges. Use common color ranges Check the box if you want to use the default color range of the information element. If you want to define a special color range here, uncheck the box and specify the range (see section 4.3 for details on how to do this). • Click Apply to add more information elements. • Click OK when you are done adding information elements. Then exit the setup wizard by clicking Finish. NT11-20502 255 TEMS Investigation 13.1 User’s Manual 22.3. • Changing Status Window Properties Right-click in the status window and choose Properties from the context menu. The Mode tab governs the layout and appearance of the window: Name Enter a new name if desired. Header Check if you want a header in the window. (The contents of the header are defined on the Cell Content tab.) Columns Set the number of columns. Rows Set the number of rows. Font Click Browse and select a font. Mobile If you choose a device in this box, all the information elements currently shown in the window will be taken from that device, regardless of earlier settings. (To pick individual information elements from a different device, use the Cell Content tab. See below.) 256 Chapter 22. Status Windows • To edit the contents of the status window, select the Cell Content tab. • Double-click on a row and select an information element from the list. Then click Edit. The dialog that appears is identical with the Add dialog in the setup wizard (see section 22.2 above), except that it has an extra field for entering text: NT11-20502 257 TEMS Investigation 13.1 User’s Manual In a status window, you might want to show the same information element for several devices. To do this, create new columns as needed on the Mode tab, and modify headers and insert information elements on the Cell Content tab. 22.4. Repeating Columns in Multiple Groups In status windows with a small number of columns (up to four), you can optionally rearrange the data by dividing the rows into several groups (up to three) and displaying these groups side by side horizontally. All columns are then repeated once or twice in the window. This feature is handy when the default window layout has a large number of rows; multiple column groups reduce or eliminate the need for vertical scrolling. • Right-click in the status window and select Column Group from the context menu, then select the desired number of column groups. 22.5. 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, then selecting the desired percentage of the current font size. Use the In and Out options to step the font size up and 258 Chapter 22. Status Windows down, respectively. The size of the window itself is not affected by these operations. 22.6. Non-standard Status Windows 22.6.1. TD-SCDMA Physical Channel Monitor This window has a unique design and presents data on TD-SCDMA Dedicated Physical Channels (DPCHs). • In the top left corner is displayed the current Work UARFCN. • Repetition period: This is the DPCH repetition period on the downlink and uplink respectively, expressed as a number of radio subframes (5 ms). A repetition period p means that the DPCH is transmitted in every pth subframe. • In the grid, rows represent timeslots, and columns represent the leaves of the channelization code tree for the DPCH (i.e. the number of codes available when the maximum spreading factor is used). – A code in use in a timeslot is indicated by an entry in the corresponding row and column(s) in the grid. If a code straddles multiple columns, this means that the spreading factor for that timeslot is reduced. Specifically, if the code takes up m columns, the spreading factor is 16/m. – The arrow shows the direction of transmission: up arrow (blue) = uplink, down arrow (yellow) = downlink. – The numbers are to be read as follows: x  y = channelization code no. x out of the total number of channelization codes y in that timeslot (the latter being conditioned by the value of the spreading factor). NT11-20502 259 TEMS Investigation 13.1 User’s Manual – Codes are colored according to the same rules as the information element “Timeslot ISCP (dBm)”, i.e. the interference signal code power for the timeslot. The color gray means that no valid ISCP measurement is available (which is always the case on the uplink). 22.6.1.1. Window Properties You can right-click in this window to select which devices to display data from. 22.6.2. CDMA Finger Info This window indicates the T-Add and T-Drop thresholds by means of a window-specific feature, as shown in the screenshot below. For the setup, see section 22.2 (View tab). CDMA Finger Info window with T-Add and T-Drop thresholds drawn as dashed vertical lines in the Energy column. In this case, T-Add = –13 dB and T-Drop = –15 dB. 260 Chapter 23. Event Counter Windows 23. Event Counter Windows The Event Counter window keeps track of the number of times a set of events have occurred. What events to show is user-configurable. 23.1. Window Tabs Tabs are provided in this window to allow grouping of events into categories. In the Event Counter window provided under Presentation → Analysis, a number of tabs are preconfigured. • To add a new tab, right-click in the window and choose New Tab from the context menu. • To rename a tab, right-click it to open its Properties dialog. See section 23.4.1. • To remove an existing tab, right-click in the window and choose Remove Tab from the context menu. 23.2. Copying Window Contents You can copy the entire contents of a tab in an Event Counter window to the Windows clipboard. This way it can be transferred to a spreadsheet application or other suitable program. • Right-click the tab and choose Copy to Clipboard from the context menu. • Paste the copied selection into the desired application. 23.3. 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. This resets all counters in all open Event Counter windows. Counters are reset automatically, in both drive testing and replay mode: NT11-20502 261 TEMS Investigation 13.1 User’s Manual • when a new logfile is opened • when a logfile is closed. In replay mode, a reset is also performed when the logfile is rewound. 23.4. • Changing Event Counter Window Contents and Properties Right-click in the Event Counter window and choose Properties from the context menu. 23.4.1. General Tab On this tab you choose which devices to show events from. The event counting in the window is done in a separate column for each selected device. A Total column is also provided which adds up the number of events from all selected devices. The General tab also holds the window title, which is user-editable. 23.4.2. Events Tab Here you choose which event types to display on the currently active tab (the tab from which you access the Properties dialog). • 262 Using the arrow buttons, move the events you want to display to the Selected Events list box. Chapter 24. Message Windows 24. Message Windows The message windows are used to list messages and reports received or transmitted by external devices (Layer 2 and Layer 3 messages, mode reports, and error reports). They are also used to present events generated by TEMS Investigation. Preconfigured message windows are listed in Information Elements and Events, chapter 8. 24.1. • Changing Message Window Contents and Properties To access the message window Properties dialog, right-click in the window and choose Properties. 24.1.1. General Tab On this tab you choose which devices to show messages from. MS and DC channels are distinguished. The tab also holds the window title, which is user-editable. 24.1.2. Messages Tab Here you choose which message categories to display in the window. The ready-made windows are preconfigured in this regard. If at least one item in a category has been deselected, the checkbox next to the category is shaded gray. 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. NT11-20502 263 TEMS Investigation 13.1 User’s Manual 24.1.3. Events Tab Here you choose which events to display in the message window. • Using the arrow buttons, move the events you want to display to the Selected Events list box. Any type of event can always be shown, regardless of the nature of the messages. Note that if you add a user-defined event (section 20.3), you must select it on this tab in order for it to display in the message window. 24.1.4. Columns Tab Here you decide which columns to include in the message window: • Equipment: The device that delivered the message. • Mobile System: The wireless technology from which the message originates. • Event & Message Symbols: Event icon or arrow showing message direction (both types of symbol being placed in the same column). • Event Symbols: Event icon. • Message Symbols: Arrow showing message direction. • Message Name: Name of message or event. • Message Info: Message or event information. • Information Element: Value of a user-selected information element. To select the element, first move “Information Element” to the Selected Columns box, then select this item and click Edit. A new dialog now appears where you select what information element to display. • Time: Timestamp of message. • Protocol: The protocol to which the message belongs. 24.2. Plain-text Message Decoding In all message windows, you can double-click a message to open a new window detailing the contents of the message. You can copy text from this window to the Windows clipboard by selecting the text, then right-clicking in the window and choosing Copy from the context menu. 264 Chapter 24. Message Windows Each message window normally reuses a single detail window. For example, if you double-click one Layer 3 message and then another, the second message will replace the first in the Layer 3 detail window. To open a message in a new window, right-click the message and choose New Detail Window. The new window now becomes the active one. The old window will remain open, but its contents will not change any further. 24.3. 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 19.2.2.10) are highlighted in red in the Layer 3 Messages window. Further, an explanatory string is added to the plain-text decoding of such messages. 24.4. Message Window Catch-up If you open a new message window when in replay mode, the new window will catch up and load all data from the beginning of the logfile. If you open a new message window when in drive testing mode, the new window will not load any messages (for performance reasons). However, when you have deactivated all external devices, you can make the window catch up by right-clicking it and choosing Reload. To abort the reload procedure, right-click again and choose Cancel Reload. 24.5. Message Window Synchronization When message windows synchronize with each other and with other presentation windows, one or more rows are selected (colored) in each message window. Suppose, for example, that you just clicked somewhere in a line chart. The message windows are then updated according to the following rules: • If one message window row matches the user-selected item better than any other, that row alone will be selected. If several rows match equally well (for example, a message and one or several events triggered by that message), all these rows are selected. • If the user-selected item and the message window selection belong to the same air interface message, the message window selection is colored blue. If there is no such exact correspondence, the row or rows NT11-20502 265 TEMS Investigation 13.1 User’s Manual immediately preceding the user-selected item in time are selected and colored gray. (If no such rows exist, nothing is selected in the window.) 24.6. Freezing a Message Window You can freeze a message window by clicking an arbitrary message. The window will then stop updating, and its message flow is halted. The freeze affects only the message window you clicked in, not any other windows. This works in both drive testing mode and replay mode. 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. In replay mode, if you have frozen a message window, stopped the replay, and then resume replaying of the logfile, the message window “wakes up” automatically. 24.7. Window-specific Features 24.7.1. Mode Reports Window In the General window, under WCDMA, you can adjust the updating frequency (in the TEMS Investigation application) for List Search reports from Qualcomm-based terminals. 266 Chapter 25. Video Streaming and the Video Monitor 25. Video Streaming and the Video Monitor TEMS Investigation supports streaming of video recordings through UMTS and CDMA phones. The application is equipped with a built-in streaming video client which has been designed to imitate as closely as possible the corresponding client software found in phones. The application supports both on-demand streaming, where a video clip of known length is downloaded, and various forms of live streaming (such as tapping into a live stream or repeating playlist delivered by a streaming server), where the duration of the streaming session is specified by the user. 25.1. How to Test Video Streaming To test the video streaming service, you need a phone capable of handling this service. All UMTS phones sold with TEMS Investigation 13.1 possess this capability. The mechanics of setting up and conducting a streaming session are handled by the Streaming activity in scripts: see section 18.17.5.4. Video clips suitable for testing are supplied on the installation CD in the subdirectory Video Clips. 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. If you are using files of your own for testing streaming, the file names should contain a numeric value followed by “kbps”. This value should indicate the bit rate of the stream (video + audio), not counting overhead. If multiple numeric values are given in the file name, the first is used. If the file name does not contain a numeric value, the VSQI algorithm (see chapter 38) will use a bit rate value received from the server, but the VSQI score will then be less accurate. NT11-20502 267 TEMS Investigation 13.1 User’s Manual 25.2. The Video Monitor To display the streamed video clip, you use the Video Monitor window: Only one instance of the Video Monitor can be open, so only one video stream can be replayed at a time. (On the other hand, 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.) 25.2.1. • Properties of the Video Monitor Right-click in the Video Monitor to access its Properties dialog: Device Here you select the device that delivers the video stream. Enable audio Check this box to play the streamed audio through the PC speakers. 268 Chapter 25. Video Streaming and the Video Monitor 25.3. Evaluating Video Streaming Performance Throughput and other performance measures for video streaming are presented in the “Streaming” information elements belonging to the Data category. See Information Elements and Events, section 3.9. Data on which video streaming KPIs are based is delivered in the form of KPI events; see Information Elements and Events, section 7.4. Some of these data items deserve special comment: • Information element Streaming Packet Loss: Packet loss is of particular interest for streaming, since the received signal is presented in real time in TEMS Investigation. • Information element Streaming VSQI and events Streaming Quality VSQI, 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. It is described in more detail in chapter 38. VSQI is also the subject of a technical paper which includes general discussions of video streaming as well as video quality measurement. This paper, “Video Streaming Quality Measurement with VSQI”, is found on the installation CD in the subdirectory Documents. • Information element Streaming MTQI and event Streaming Quality MTQI: MTQI (Mobile TV Quality Index) is a refinement of VSQI which is discussed in chapter 39. It appraises video quality only. • Event Streaming State: This event is provided for monitoring the activities of the streaming video client. 25.4. Troubleshooting Video Streaming • UDP ports for video streaming must be free. See the Getting Started Manual, section 8.2.8. • Testing of video streaming with TEMS Investigation requires that RTP/ UDP traffic can be run with the phone used as modem. The function cannot be used if RTP or UDP traffic to and from the Internet is blocked (intentionally by the operator, or for whatever reason). • For close-up scrutiny and troubleshooting of the video streaming service, you can monitor the message traffic over the RTP, RTSP, and RTCP protocols in the IP Protocol Reports window. See Information Elements and Events, section 8.9. NT11-20502 269 TEMS Investigation 13.1 User’s Manual 26. The GPS Window This window shows data from the GPS unit. If several GPS units have been detected by TEMS Investigation, the window shows data from the one currently selected as “Preferred” (see section 7.5). Exactly what data is displayed depends on the type of GPS; 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) 26.1. Changing GPS Window Properties The GPS window can be configured to show only the parameters that interest you: 270 Chapter 26. The GPS Window Units Tab Speed Choose km/h or mph. Altitude Choose meters or feet. View Tab Basic Check to show the latitude, longitude, altitude and speed of the GPS unit, the fix source, and the number of satellites seen. Heading Check to show the direction of travel, graphically and numerically, in degrees clockwise from north. Show invalid positions Check to also plot samples whose position is labeled as invalid by the GPS unit. 1 1. This option exists to allow presentation of positions incorrectly regarded by the GPS as invalid. NT11-20502 271 TEMS Investigation 13.1 User’s Manual 27. 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 8. 27.1. 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, containing the charts themselves • a Y-axis pane for each chart, showing the scales for the plotted information elements 272 Chapter 27. Line Charts • a Legend pane, describing the nature and origin of the information elements shown, and indicating their values at a single point in time • an Additional Information pane, displaying arbitrary information elements in textual format. A maximum of four charts can be accommodated, along with their associated Y-axis panes. The legend can only gloss one chart at a time. The relative sizes of the panes can be freely adjusted by dragging the interior frame handles. 27.2. 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. The plotting can be done either as a curve or in the form of successive vertical bars. Events are indicated by thin vertical lines accompanied by a symbol identifying the event type. The symbols used for predefined events are given in Information Elements and Events, chapter 7. To see the names of the events, open an Events window. The Chart pane is synchronized with the Legend and Additional Information panes (as well as with all other open presentation windows, as explained in section 21.4). Clicking somewhere in a replayed logfile segment in the chart (after stopping the replay) displays details about the chosen instant in the two text panes. You can also move backwards and forwards in a replayed segment with the left and right arrow keys on your keyboard. In the chart, a thick vertical line indicates the point in time currently selected in the presentation. You can freeze the line chart during recording or replay by clicking the Hold button. Clicking the button again (now labeled Release) makes the chart catch up with the presentation in the other windows. Scrolling the chart by means of the scroll bar does not change the time instant selected, so neither the text panes nor other presentation windows will be updated. To select a new point in time, just click in the chart. NT11-20502 273 TEMS Investigation 13.1 User’s Manual The Y-axis Pane The Y-axis pane associated with a chart shows the scales of the information elements plotted there. Each scale is drawn in the same color as the information element, except when several elements share the same scale, in which case the scale is black. If the pane is too narrow to show all scales at once, you can scroll between scales using the arrow buttons. The scales can be changed; see section 27.4.3 (“Upper visible limit”, etc.). 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. At the extreme left in the legend, the color coding of the chart is explained. Parameters (SC/BSIC, [U]ARFCN, PN) associated with elements are given in columns of their own wherever possible. To focus the legend on a different chart, right-click anywhere in the Line Chart window and choose the desired Legend Chart item from the context menu. The Additional Information Pane This is a sort of status window where an arbitrary set of information elements can be displayed (for example, elements which cannot be plotted). You can choose different contents in this pane for different charts, as described in section 27.4 under Additional Information Tab. However, as long as contents have only been defined for one single chart, this data will be shown in the pane regardless of which chart the legend currently refers to. 27.3. Time Scale The horizontal axis of the line chart does not have an exact time scale, and so is not labeled with a unit of time. However, as a rule of thumb, two points are plotted each second both in idle and dedicated mode. If the phone spends some time in GSM no service mode, there will be a gap in the chart to show this, but the length of this gap might not be equivalent to the period of time with no service. 274 Chapter 27. Line Charts 27.4. Changing Line Chart Contents and Properties To edit the contents of the line chart and their presentation, right-click anywhere in the Line Chart window and choose Properties. 27.4.1. • Adding Charts To add a new chart in the Line Chart window, click Add Chart. 27.4.2. Editing General Properties of a Chart On the General tab of the Line Chart Properties dialog, you can edit the line chart window name and deselect the horizontal grid lines which by default are drawn in the background. 27.4.3. Editing the Contents of a Chart • Select the chart you want to edit in the list box. • Click Edit Chart. This dialog appears: NT11-20502 275 TEMS Investigation 13.1 User’s Manual Information Elements Tab Here you edit the set of information elements to plot and how to present them. The information elements that can be plotted are chiefly those that represent or are derived from measured physical quantities (e.g. signal strength). Flags, frequency and channel numbers, scrambling code indices, timeslot indicators, and the like cannot be plotted. • First select information element category in the System combo box. See Information Elements and Events, chapter 2. • Using the arrow buttons, move the elements you want to present from the Available IEs to the Selected IEs list box. A maximum of seven elements can be presented. You can use the Ctrl and Shift keys to select multiple items in the boxes. The first time you move an information element to Selected IEs, it will be picked from the device the line chart is drawn for (see the title bar; for the Line Chart template it is MS1). From elements with an argument the value with the lowest argument is picked. If you move the same element to Selected IEs again, one of two things will happen: • if the element has an argument, it is taken from the same device as before, and the value with the next higher argument is shown; • otherwise, the element is taken from the next device. 276 Chapter 27. Line Charts Naturally, the MS and argument can also be edited directly at any time. This is done by clicking the Edit IE button. In the ensuing dialog you also customize the presentation of the information element: Mobile The device to pick the information element from. Note that it is possible to change the device for all chosen elements at once. See section 27.4.4. IE Argument The argument (if any) of the information element. Style: Bar Choose this if you want the element to be plotted as successive, tightly packed vertical bars. Style: Line Choose this if you want the element to be plotted as a line. You can adjust the line width. Color: Assigned to channel This option is available only for elements made up of sorted channel lists (e.g. neighbors, scanned channels). If it is chosen, the application automatically assigns a color on the basis of what channel is shown. The point of this is to ensure that you can easily see when the sort order of the list (e.g. the neighbor ranking) changes. As far as possible, one and the same color is used throughout for a given channel. Color: Fixed This option is available for all elements, and consists simply in your selecting one fixed color yourself. NT11-20502 277 TEMS Investigation 13.1 User’s Manual Upper visible limit for IE Upper limit of the value range shown for this information element. That is, this setting adjusts the range in the Y-axis pane. For complex information elements, the limit is automatically changed for all other arguments as well. Lower visible limit for IE Lower limit of the value range shown for this information element. This setting works the same way as Upper visible limit for IE. Draw threshold line at Check this if you want to compare the plotted values with a threshold line drawn at a specified value. Change color in dedicated mode If you check this box, the plot color turns deeper when the phone enters dedicated mode, and the brighter color chosen in the Color box is reserved for idle mode. (The dedicated mode color is not usercustomizable.) Events Tab Here you decide which events should appear in the line chart presentation. • Using the arrow buttons, move the event you want to present to the Selected Events list box. The first time you move an element to Selected Events, it will be picked from the device the line chart is drawn for (see the title bar). If you move the same element to Selected Events again, it is taken from the next device. Clicking the Edit Event button pops up the following dialog: Mobile The device to pick the event from. Symbol The image file used to label the vertical line indicating the event. 278 Chapter 27. Line Charts Additional Information Tab Here you choose the information elements to view in the Additional Information pane. This tab works exactly like the Information Elements tab, except that here any information element can be selected. Clicking the Edit IE button in this case only enables you to change the device and argument, since the additional information is presented only as text and not graphically. 27.4.4. Presenting Data from a Different Device If you want to present the same data as before in a chart but from a different device, it is impractical to edit the MS field for each information element separately as described in section 27.4.3. A shortcut is therefore provided for this operation. • Right-click in the Line Chart window. From the context menu, choose Change MS: • For each chart, select the device to pick data from. (The information elements and events selected in the charts will be unchanged.) 27.4.5. • Deleting a Chart In the Line Chart Properties dialog, select the chart you want to delete and click the Delete Chart button. 27.5. Exporting the Line Chart Window The line chart window can be exported separately to a file with extension .lch. See section 21.7. NT11-20502 279 TEMS Investigation 13.1 User’s Manual 28. Bar Charts Bar charts are used to view successive snapshots in time of a selected set of information elements. The bar chart is especially suited to the presentation of frequency scans, but the chart itself is generic and can present any measurement data. The bar chart has a number of presentation modes. One of these is a parallel coordinates presentation, which is strictly speaking a different means of visualization but is integrated into the bar chart window. Preconfigured bar charts are listed in Information Elements and Events, chapter 8. 280 Chapter 28. Bar Charts 28.1. 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, containing the charts themselves • a X-axis pane, displaying labels for the bars drawn • a Y-axis pane for each chart, showing the scales for the displayed information elements • a Legend pane, describing the nature and origin of the information elements shown, and indicating their current values • an Additional Information pane, displaying arbitrary information elements in textual format. A maximum of four charts can be accommodated, along with their associated Y-axis panes. The legend can only gloss one chart at a time. The relative sizes of the panes can be freely adjusted by dragging the interior frame handles. NT11-20502 281 TEMS Investigation 13.1 User’s Manual 28.2. 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 Chart pane is synchronized with the Legend and Additional Information panes, as well as with all other open presentation windows, as explained in section 21.4. Clicking a bar displays max and min indicators, which will from then on keep track of the maximum and minimum values assumed by this parameter since the bar was clicked. To reset the max and min indicators, just click once more on the bar. The X-axis Pane The X-axis pane provides labels for the data distributed on the x-axis (for one chart at a time). By default the labels are simply consecutive numbers, but they can also show the value of an information element or consist of arbitrary text. See section 28.4.2. The Y-axis Pane Along the y-axis of a chart are shown the scales of the information elements plotted there. Each scale is drawn in the same color as the information element, except when several elements share the same scale, in which case the scale is black. If the pane is too narrow to show all scales at once, you can scroll between scales using the arrow buttons. The value range visible on the y-axis can be changed; see, for instance, section 28.4.1.1 (Visible limit for IE). The Legend Pane In the legend full details are provided (for one chart at a time) on the information elements displayed in that chart. At the extreme left in the legend, the color coding of the chart is explained. The (U)ARFCN and SC/BSIC are left out if they are not directly relevant to an element (e.g. one indicating transmit power). To refocus the legend on a different chart, just click in that chart. 282 Chapter 28. Bar Charts The Additional Information Pane This is a sort of status window where an arbitrary set of information elements can be displayed (for example, elements which cannot be drawn in a bar chart). You can choose different contents in this pane for different charts, as described in section 28.4.3. 28.3. Setting Up General Bar Chart Properties To set up some general properties of the bar chart and its presentation, rightclick anywhere in the bar chart window and choose Properties. 28.3.1. Adding Charts To add a new chart in the bar chart window: • Click Add. 28.3.2. Deleting a Chart To delete a chart: • In the Bar Chart Properties dialog, select the chart you want to delete and click the Delete button. NT11-20502 283 TEMS Investigation 13.1 User’s Manual 28.3.3. Editing General Properties of a Chart On the General tab of the Bar Chart Properties dialog, you can edit the bar chart window name and specify that horizontal grid lines should be drawn in the background. 28.4. Setting Up Bar Chart Contents • In the Bar Chart Properties dialog, select the chart you want to set up in the list box. • Click Edit. You will now work through a sequence of three dialogs. In doing so you specify 1. what data to plot in the chart, and how to present it 2. what interval to show on the x-axis, and how to label it 3. what data to display in the Additional Information pane. The procedures are gone through in detail in sections 28.4.1–28.4.3. Examples of bar chart presentations are found in section 28.5. The first dialog that appears is this: 284 Chapter 28. Bar Charts 28.4.1. Presentation Mode, Data, Colors In this step you select the following (full details on subsequent pages): • Presentation mode. The bar chart is very flexible in that it can be configured in a variety of ways. 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, or a set of components of complex information elements, are chosen. The information elements that can be displayed are chiefly those that represent or are derived from measured physical quantities (e.g. signal strength, quality measures). Flags, channel numbers, timeslot indicators, and the like cannot be displayed. • Colors: You can always keep the default color range for the information elements. Besides, there is one other option: either to define your own colors for use in the bar chart, or to use predefined, fixed, window-specific colors. (Which choice is available depends on the presentation mode.) The default color range is defined in the Navigator and is dependent on the information element value (see section 4.3). NT11-20502 285 TEMS Investigation 13.1 User’s Manual 28.4.1.1. Single IE Presentation Mode In this mode a single information element is displayed. The element must be one with arguments, i.e. one which consists of several components. It is possible to dynamically adjust the number of components to show, by making it dependent on another (suitably chosen) information element: see section 28.4.2. • In the Edit Chart dialog, select Bar chart: Single IE with multiple components. • 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, and whether the scale will be flipped with the lowest value at the top. If you want to change these settings: • Double-click the Visible limit for IE: Min, Max 286 item (or click the Edit button): The visible range of the information element. 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). Chapter 28. Bar Charts MS The device from which to pick the information element. Flip scale 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. • Make your changes, then click OK. • Click OK in the Choose Information Element dialog. • Back in the Edit Chart dialog, decide what colors should be used in the chart. You have two options: • – Keep the default color range for the information element. To this end, check the Use common colors box. – Define one fixed color to be used throughout in this chart, disregarding the default color range. To do this, uncheck Use common colors and select a color in the box next to the information element. Now click Next to proceed to the next step. For an example of a Single IE presentation, see section 28.5. 28.4.1.2. Multiple IE Components Presentation Mode This mode displays an arbitrary fixed set of information element components. To set up this presentation, proceed as follows: • First decide whether you want to use the default color ranges of the information elements or define a fixed color for each element. To keep the default colors, check the Use common colors box in the Edit Chart dialog. Otherwise, uncheck it. You will then be prompted to define colors later on. • Select Bar chart: Multiple IE components (fixed set). • Click Choose IEs to select your data. This dialog appears: NT11-20502 287 TEMS Investigation 13.1 User’s Manual Here, a varying number of information elements may already be listed, depending on the type of bar chart concerned (template or predefined, etc.). For each index you select one piece of data: an information element with no arguments, or one component of an element having arguments. If you have checked Use common colors, the Color column will be absent from this dialog. • To specify the data that should be represented by a bar (i.e. an index on the x-axis), click the button in the IE column, in the relevant table row. To add a new bar, click the Add button. A new row will then be inserted at the bottom of the table once the contents of the bar have been specified. In either case, the Choose Information Element dialog appears: • 288 Select an information element. Chapter 28. Bar Charts • Double-click the item (or click the Edit button): • Specify range and scale properties, as described for the Single IE presentation mode (see section 28.4.1.1). • If the information element is one with arguments, pick an argument. • Click OK to exit the Edit IE dialog. • Click OK in the Choose Information Element dialog. • If you have unchecked Use common colors, you are now prompted to define a color for this data item. The standard Windows color dialog appears. Pick a color and click OK. To the IE for Fixed Layout dialog is now added the data item and color defined for the selected index. The table will look something like this: • To remove items from the bar chart, select the corresponding rows in the table, and click Remove. You can select all rows with Ctrl + A. The indices of the removed rows disappear from the table, but when you exit the dialog all items will be renumbered starting at 1. • When you are done specifying the bar chart contents, click OK to return to the Edit Chart dialog. • Click Next to proceed to the next step. For an example of a Multiple IE Components presentation, see section 28.5. NT11-20502 289 TEMS Investigation 13.1 User’s Manual 28.4.1.3. Parallel Coordinates/Stacked Bar Chart Presentation Mode This presentation mode is the most complex one. It has the following fundamental properties: • A set of information elements is shown. • Each information element may have arguments, and an arbitrary number of components of each element may be shown at the same time. The information elements are distributed on the x-axis, and arguments are displayed in the y-direction. • There are two graphical representations of the above (conceptually quite distinct): a stacked bar chart and a parallel coordinates presentation. In the stacked bar chart, one composite bar is drawn for each information element, 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). The parallel coordinates presentation does not use bars and is thus not a bar chart in the literal sense. Rather, it plots all components of each information element on the y-axis, at a fixed x-axis coordinate, and connects with a line each set of components that have the same argument: arg 0 arg 1 arg 2 IEs 290 Chapter 28. Bar Charts The parallel coordinates presentation is selected by default in this mode. Setting Up Basic Properties of the Presentation To set up this presentation, proceed as follows: • Select Parallel coordinates (default) / Stacked bar chart. If you want a parallel coordinates presentation, make these settings: Do not uncheck IEs on x-axis, arguments stacked; such a presentation is possible but hardly has any natural interpretation within the TEMS Investigation framework. If you want a stacked bar chart instead, check the Stacked bar chart box: • Uncheck IEs on x-axis, arguments stacked if you want to reverse the roles of the axes so that arguments, rather than information elements, are distributed on the x-axis. Selecting Data After deciding the basic properties of the presentation: • Click Choose IEs to select your data. This dialog appears: Here, a varying number of information elements may already be listed, depending on the type of bar chart concerned (template or predefined, etc.). NT11-20502 291 TEMS Investigation 13.1 User’s Manual • To specify the details of how an information element should be presented, click the corresponding button. To add a new information element, click Add. A new row will then be inserted at the bottom of the table once the details have been specified. In either case, the Choose Information Element dialog appears. • Select an information element. • Double-click the • Specify range and scale properties, as described for the Single IE presentation mode (see section 28.4.1.1). item (or click the Edit button): Note: The y-axis scales look the same also for stacked bar charts, despite the fact that the bar segments (except the bottom one) will be displaced in relation to the scale bar. • Click OK to exit the Edit IE dialog. • Click OK in the Choose Information Element dialog. 292 Chapter 28. Bar Charts To the IEs for Par. Coord. ... dialog is now added the data item defined for the selected index. For example: • To remove information elements from the bar chart, select the corresponding rows in the table and click Remove. You can select all rows with Ctrl + A. The indices of the removed rows disappear from the table, but when you exit the dialog all items will be renumbered starting at 1. • When you are done specifying the bar chart contents, click OK to return to the Edit Chart dialog. Finally, you need to decide what colors should be used in the chart. You have two options: • Keep the default color ranges for the information elements. To this end, check the Use common colors box. • Use fixed colors, one for each argument. The colors are chosen by the application and cannot be edited. Choose this option by unchecking Use common colors. When you are done: • Click Next to proceed to the next step. For an example of a Parallel Coordinates/Stacked Bar Chart presentation, see section 28.5. NT11-20502 293 TEMS Investigation 13.1 User’s Manual 28.4.2. Interval and Labeling In this step you take care of the following: • Indicating the interval to show on the x-axis. Note that this is done independently of the data selected in the preceding step. • (Optional) Specifying text labels on the x-axis instead of the default numeric indices. 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. The default values in the boxes are dependent on the data selected in the previous step, 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. This element must denote the current number of something in order to make sense, and only such elements are selectable. Example: If you want to display scan data, e.g. Scanned RxLev, it may be a good idea to have the interval governed by Scanned Channels No Of. Then the number of indices on the axis will always be 294 Chapter 28. Bar Charts equal to the number of channels currently scanned, and the space available in the chart will be fully utilized at all times, the bar width being adapted continuously. Note: The Set by IE option is disabled for the Multiple IE Components presentation, since this by itself stipulates a fixed number of x-axis indices. Labeling By default the x-axis is labeled simply with numbers, either those given under Fixed or the arguments of the information element chosen under Set by IE. Alternatively, you can replace the numbering with text labels. • To enable user-defined text labels, check Text labels on axis... . There are two options: • Select Text strings from IE to pick labels from a text-format information element. Example: If you want to display data on neighbors, you might want to label the x-axis with the neighbor cell names, found in the information element Neighbor Cell Name. • Select User-defined text labels to specify arbitrary text as labels. Click the Compose button. A dialog appears where you enter a string for each index. 28.4.3. Additional Information Here you choose the information elements to view in the Additional Information pane. This dialog works like the Information Elements tab in the line chart properties (see section 27.4.3), but since the additional information is presented only as text and not graphically, • any information element can be selected • clicking the Edit IE button only enables you to change the device and argument. 28.4.4. Presenting Data from a Different Device If you want to present the same data as before in a chart but from a different device, it is impractical to edit the MS field for each information element NT11-20502 295 TEMS Investigation 13.1 User’s Manual separately as described in section 28.4.1.1. Therefore, there is a shortcut for this operation. • Right-click in the bar chart window. From the context menu, choose Change MS: • For each chart, select the device to pick data from. (The information elements selected in the charts will be unchanged.) 28.5. Examples of Bar Chart Presentations Here are a couple of examples of how the presentation modes can be used. Single IE Single IE presentation: Neighbor RxLev (Sorted). 296 Chapter 28. Bar Charts Multiple IE Components Multiple IE Components presentation displaying an assortment of single-value IEs and selected components of multivalue IEs, and with user-defined text labels added on the x-axis. Note that only half of the legend is visible in the picture. NT11-20502 297 TEMS Investigation 13.1 User’s Manual Stacked Bar Chart, Parallel Coordinates Parallel coordinates presentation (the predefined Radio Parameters Parallel Bar Chart for WCDMA). Each point on the horizontal axis represents a network parameter, and the colored line, connecting a set of parameter values, represents a moment in time. This arrangement allows the user to spot instantaneously any pattern that is out of the ordinary (that is, any unexpected line shape). 28.6. Exporting the Bar Chart Window The bar chart window can be exported separately to a file with extension .bch. See section 21.7. 298 Chapter 29. Map Windows 29. Map Windows Map windows are used to display a map of your testing area and present your drive test route graphically on this map. Data on cells, events, and information elements are shown along the route in symbolic form; numeric values can also be easily accessed. Like the other presentation windows, Map windows are fully user-configurable. Map files used in TEMS Investigation must be in MapInfo, bitmap, or uncompressed TIF format. Note also that to be able to plot measurements on a map, TEMS Investigation must have access to positioning data. A map of the world is provided with the installation. 29.1. Highlights of This Chapter This chapter contains a great deal of information, and you might not have use for all of it. The following sections, however, are central: • First, to be able to use a map file in TEMS Investigation, you must work through some preliminaries which are described in sections 29.3–29.4. • Then you can proceed to set up what data you want to present on the map. How to do this is explained in section 29.5. If you have loaded a cell file and want to view cell information, turn to section 29.5.5. 29.2. Map Concepts In this section, some central concepts relating to Map windows are defined. You might want to skim this section the first time around to make yourself familiar with the concepts. The concepts are explained again as they are brought up later in the chapter; use this section as a reference. Map A map is a set of geographical features which are treated as a unit. A map usually consists of several map layers (see Layer) and is presented in a Map window. NT11-20502 299 TEMS Investigation 13.1 User’s Manual TEMS Investigation supports the following map formats: MapInfo, bitmap, and TIF (uncompressed only). Layer A layer is a set of data from a particular category which is displayed in a Map window. There are two types of layer: map layers, which make up the map itself, and presentation layers, which contain information relating to the cellular network. A map layer may, for example, consist of all the roads or all the water areas on the map. A presentation layer contains one or several themes, all of the same main type (see Theme below). One presentation layer is predefined for each main type of theme; a further layer is provided for pinpoint markers. Additional layers can be defined by the user. Theme A theme is a component of a presentation layer, displaying, for example, an information element or a type of event. Label A label is a text string that belongs to a map and can be displayed on it. GeoSet A GeoSet (file extension .gst) is a special type of workspace used for map layers. A GeoSet contains settings regarding layer order, projections, zoom levels, labels, colors, etc. 29.3. Constructing a GeoSet from Map Files A Map window in TEMS Investigation works with a GeoSet instead of an ordinary workspace. If you have a new map that you want to use in TEMS Investigation, you should construct a GeoSet file for it to be able to save changes to the map later on. This file can then be opened in a Map window. If your map is in MapInfo format, it consists of a number of map layers and a workspace which ties them together. Each layer is stored in five different files with the extensions .dat, .id, .ind, .map, and .tab. These files are from now on collectively referred to as TAB files. 300 Chapter 29. Map Windows If your map is in bitmap format (extension .bmp), you must generate TAB files for it. This is done by positioning the map as described in section 29.4. If possible, avoid using 24-bit bitmap images as maps. Once you have your TAB files, you can construct a GeoSet. • Copy the map’s TAB files to your map directory. On the Map window toolbar, click the Start GeoSet Manager button. Note: The GeoSet Manager will ask you to open a GeoSet. Click Cancel to ignore this. • Name your new GeoSet in the edit box of the toolbar. Click Layer Control. • Click Add. • Select the TAB files you copied to your map directory and click Open. All the selected layers are added to the Layer Control. • Click OK. The map is now displayed with all its layers. • Choose File → Save GeoSet. You are prompted to name the GeoSet. • Click Save. This will save your new GeoSet file under the name you entered in the GeoSet Name edit box. The GeoSet file must be in the same directory as the TAB files. • Choose File → Exit to close the GeoSet Manager. Click Open Map Files. • Select your newly created GeoSet file and click Open. The map should now be displayed in the Map window. You are ready to start presenting data: see section 29.5. Note: It is possible to load TAB files in a Map window directly, without constructing a GeoSet, but then any changes made using the Layer Control will be lost. See section 29.7.2. NT11-20502 301 TEMS Investigation 13.1 User’s Manual 29.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, you must supply this data yourself. Click Position Map. 29.4.1. Specifying the Map Position In this step you input the coordinates of a point on the map. • In the Reference Point section, in the Latitude and Longitude fields, enter the coordinates (in decimal degrees) of the point you wish to use. • Click the Pick button in the Reference Point section. • On the map, click the point that has the given coordinates. 29.4.2. Specifying the Map Scale In this step you indicate the distance between some two points on the map, so that the map scale can be calculated. • 302 In the Distance section, click the Pick button. Chapter 29. Map Windows • On the map, click the first point and keep the mouse button down. When you move the mouse, a dashed blue line appears. Release the mouse button at the second point. The coordinates of the chosen points appear in the X_Y fields. • In the Distance field, enter the actual distance between the two points. 29.4.3. Setting the Map’s North Direction What remains is to indicate the north direction of the map. • In the Direction section, in the North Offset Angle field, enter the offset between the map’s x-axis and its direction of north. For example, if the map is oriented with north pointing up, enter 90°. The offset lies between –180° and +180°, a positive number indicating a clockwise offset. • Click OK. Your map is now positioned. A file with the same name as the image but with the extension .tab is created. The *.tab file is the map file you will use from now on. 29.5. Presenting Data: Themes This section describes how to present cellular network data on the map. In short, in order to present data, you use presentation layers and fill these with themes. A set of presentation layers is already supplied in the application. Therefore, to get started with presenting data, you do not need to worry about handling presentation layers; all your work is to do with themes and is covered in the present section. However, you can also modify presentation layers and create new ones. How to do this is described in section 29.7. 29.5.1. Themes and Theme Types A theme is basically a bundle of settings describing how to present a set of data. These are the main types of theme, each presenting a different kind of data: • information element (IE) themes, presenting a set of information elements (at most three); see section 29.5.3 • event themes, presenting an event; see section 29.5.4 NT11-20502 303 TEMS Investigation 13.1 User’s Manual • cell themes, presenting cell information; see section 29.5.5. There are several subtypes of cell theme. • the Pinpoint theme, presenting pinpointing information; see section 29.5.6. 29.5.2. Presentation Layers When you create a theme, you always put it in a presentation layer. Click Add/Edit Themes to view the current presentation layers and the themes within them. Certain presentation layers are predefined, along with a number of themes, as is seen in this screenshot (where some layers have been expanded). The various types of theme are put in different layers: • IE themes in the Coverage, RF Quality, and AMR layers • event themes in the Event layer • cell themes in the Cell layer • the pinpoint theme in the Pinpoint layer. You can add new presentation layers if desired. How to manipulate layers is the subject of section 29.7. 304 Chapter 29. Map Windows 29.5.3. Presenting Information Elements To present information elements, you create information element themes (hereafter called IE themes). These govern the appearance of a marker that is plotted on the map. By varying its color, size, and shape, the marker can code the values of up to three numeric information elements. For example, you can have the marker color governed by RxLev and the marker size by RxQual, and use different symbols when the phone is in idle mode, dedicated mode, and so on: More generally, it is appropriate to use the color and size attributes for information elements with a continuous value range, and to use a suite of symbols for such things as status parameters having a small set of possible values. The colors, sizes, and symbols used in the map are always the default ones for each information element, as set on the Info Element tab of the Navigator: see section 4.3. It is not possible to define these attributes differently in the map. To create a new IE theme: • In the Theme Settings dialog, select one of the layers (or create a new layer to put the theme in: see section 29.7). • Click Add Theme: NT11-20502 305 TEMS Investigation 13.1 User’s Manual System Choose an information element category. See Information Elements and Events, chapter 2. Mobile Choose the device from which to pick the information element. Offset (pixels) This setting decides how far from its true position on the map the theme marker will be drawn. The offset direction is at right angles to the direction of travel; a positive offset is to the right relative to the direction of travel. Using offsets enables you to display several routes side by side. Color In this section you specify a rule for the theme marker color: Size 306 • Choose Range to have the color governed by an information element. Select an element, and select an argument if applicable. • Choose Fixed to use a fixed color. This means, of course, that the color will not carry any information. In this section you specify a rule for the theme marker size, in the same way as for the color. See above. Chapter 29. Map Windows Symbol In this section you specify a rule for choosing the shape of the theme marker, in the same way as for the color. If you choose Fixed, pick a font in the first combo box, 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, and not for showing measurement data. Uniform markers, for instance circles, will then be plotted along the route at the shortest possible time intervals (about factors influencing this updating rate, see section 29.5.3.1 below). Note that some information elements are not updated this often. Once the IE theme has been defined, it appears in the box in the Theme Settings dialog under the layer it belongs to. 29.5.3.1. Notes on Route Plotting and Updating The updating frequency for IE themes is governed by a number of factors. A general rule is that new theme markers are drawn at most twice a second. 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. Here is a summary of the factors that affect theme plotting and updating: • Interpolation. Map positions, whether delivered by a GPS or pinpointed, are constantly interpolated (linearly) to enable plotting at half-second intervals. However, whether markers are actually plotted at this rate depends on other circumstances. See below. • Arrival of new measurement data. A new theme marker is plotted only if a message with fresh data has been delivered by the measurement device. Updates will thus be less frequent in idle mode than in dedicated mode. Note also that certain information elements are not updated regularly at all but only on special occasions (for example, when the phone switches to a different RAB). If you want to plot such an IE with high frequency, include another IE that is frequently updated in the same theme. • Loss of positioning data. If GPS data is lost for an extended period of time (for instance while driving through a tunnel) but GPS coverage is eventually regained, positions will still be interpolated and plotted throughout the gap. On the other hand, if no more positioning data is obtained, interpolation is of course impossible, and no extrapolation of the route is attempted by TEMS Investigation. NT11-20502 307 TEMS Investigation 13.1 User’s Manual • Map zoom. The plotting density on the map is dependent on the current zoom of the Map window. When you zoom in, more markers are filled in to show the route in more detail; when you zoom out, markers are drawn more sparsely. Specifically, 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. 29.5.4. Presenting Events To present an event, you create an event theme. Note: If you create a new event theme for a user-defined event after loading a logfile, you must reload the logfile to make this event theme visible. • In the Theme Settings dialog, select the layer named Event Layer. • Click Add Theme: Event Choose an event type. Mobile Choose the device from which to pick this type of event. 308 Chapter 29. Map Windows Offset (pixels) Set the offset. It has the same meaning as for information elements; see section 29.5.3. 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. Bitmap Select this to use a bitmap image as event symbol. Select your image, and set its size. Transparent • If this is checked, all white pixels in the bitmap become transparent, i.e. the underlying layer shines through. Note that this requires a bitmap with a white background; otherwise no transparency is achieved. • If this is not checked, the bitmap is drawn exactly as-is. Font 29.5.5. Select this to pick an event symbol from a font. Select the font, then pick a symbol and set its size and color. Presenting Cell Information1 To present cell information, you create cell themes. The themes can be defined at any time; you do not have to load a cell file first. (In fact, a couple of cell themes are predefined, as is evident from section 29.5.2.) Cell information for different technologies can be kept apart in the presentation, with a separate theme for each. It is also possible to draw cell information for multiple technologies in the same theme. Furthermore, in the XML cell file format, individual cells can be tagged with a type. This enables the creation of cell themes displaying arbitrary groups of cells. See section 29.5.5.1 below. How to load cell files is described in section 5.3. It is possible to have more than one cell file loaded. 1. This presentation also applies to WiMAX cells and Wi-Fi access points defined in an XML cell file (see the Technical Reference, sections 3.7.9 and 3.7.10). Where the presentation differs between cellular technologies, Wi-Fi and WiMAX both follow GSM, with the obvious exception of GSM-specific information such as the Cell ARFCN theme. NT11-20502 309 TEMS Investigation 13.1 User’s Manual The following kinds of cell theme exist: • Basic plotting of cell sites (Cell theme): section 29.5.5.1 • Indication of serving cell and handover (Cell Line theme): section 29.5.5.2 • Visualization of neighbor relations (Cell Color theme): section 29.5.5.3 • (GSM:) Indication of cells using the same ARFCN as a given cell (Cell ARFCN theme): section 29.5.5.4 To create a new cell theme, proceed as follows: • In the Theme Settings dialog, select Cell Layer. • Click Add Theme. The Select Theme Type dialog appears. • Choose a cell theme type. 29.5.5.1. The Cell Theme This theme is concerned with basic plotting of cell sites. Presentation on Map Three-sector site (three cells) Omni cell The zoom of the Map window does not affect this theme. All cell sites are always plotted, regardless of the zoom. Each cell is tagged with a text label if you turn on the Cell labels option (see below). However, to avoid clutter, text labels have been turned off in all of the remaining illustrations in section 29.5.5. Note that certain cells are filled with other colors by other cell themes, which by default hide the Cell theme; see sections 29.5.5.3 and 29.5.5.4. 310 Chapter 29. Map Windows Setup Dialog Cells to plot This section governs which of the cells defined in the cell file will be plotted. System Choose ALL to plot cells from all technologies. Choose a cellular technology to plot only cells from that technology. You might want to create one Cell theme for each technology. (Regarding cellular technology support in the CEL and XML cell file formats, see the Technical Reference, chapters 2 and 3.) 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, section 3.7.13. In CEL files, GSM and WCDMA cells are told apart by inspection of what type of channel is defined (ARFCN or UARFCN). Cell presentation This section governs how cells are drawn. NT11-20502 311 TEMS Investigation 13.1 User’s Manual Radius (pixels) The radius of each cell symbol (circle/sector of circle) in pixels. Border color The color to be used for the border of the cell symbol. Fill color The color to be used for the interior of the cell symbol, provided that the cell is completely described in the cell file. Uncheck to make the symbol transparent. When you select a cell, it turns red; see the illustration in section 29.6. (However, this highlighting ceases to be visible if a Cell Color or Cell ARFCN theme is also displayed: see sections 29.5.5.3 and 29.5.5.4). Incomplete cells Cell labels 312 The default color to be used for cells that are incompletely described in the cell file. If you uncheck this option, incompletely described cells will not be marked as such in any way. In either case, the following plotting rules apply: • If the antenna direction is not stated in the cell file, it is set to zero degrees in the plot (sector centered on “twelve o’clock”). • If the beam width is not stated, it is set to 360º in the plot (omni cell, full circle). If you check this option, a text label will be printed next to each cell. The displayed information, taken from the cell file, is as follows: • GSM: Cell name • WCDMA: Cell name and SC • LTE: Cell name • TD-SCDMA: Cell name • CDMA: Cell name Chapter 29. Map Windows 29.5.5.2. The Cell Line Theme This theme is used to indicate serving cells and positions where handovers have taken place. The Cell Line theme has different meanings depending on the data source: phone or scanner. Use with Phone Data For a phone, this theme is used to indicate • the serving cell (WCDMA/CDMA idle mode; GSM; LTE; TD-SCDMA) • active set members (WCDMA connected mode/CDMA traffic mode) (The user interface uses only the term “serving cell”.) Additionally, the theme indicates positions where handovers have taken place. Inter-system handovers are visualized in the same way as intrasystem handovers, provided that cells from both cellular technologies are visible in the Cell theme (section 29.5.5.1). Use with Scan Data With scan data, the Cell Line theme gives a best server indication. This points out the cell that uses the currently strongest signal as measured by the scanning device. Of course, no interaction with base stations is involved during scanning; rather, GPS data and the contents of a signal strength information element are correlated with the coordinates in the cell file, and the cell is identified which a user terminal at the same position would be most likely to use. 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 NT11-20502 313 TEMS Investigation 13.1 User’s Manual Presentation on Map route line to current serving cell Like IE theme markers (section 29.5.3.1), cell lines are plotted with a variable density. This density is governed among other things by the zoom of the Map window, ensuring that large swaths of the map are not completely covered by such lines when the Leave trail option is checked. Setup Dialog Below, all that is said of serving cells/active set also applies to best server indications. 314 Chapter 29. Map Windows System Governs what IEs are selectable. See Color governed by IE below. Mobile Choose the phone whose serving cells are to be displayed. Offset (pixels) Set the offset for the starting point of the line. It has the same meaning as for information elements (see section 29.5.3), i.e. the line is shifted in the same way as an IE theme marker. Serving cell These settings govern the indication of current and past serving cells/active set members. Serving cell line Check this to continually display a line connecting the current position along the route with the current serving cell/active set members. The line width is adjustable. Fixed color Select this to have the serving cell line drawn in a fixed color. Pick a color in the combo box. Color governed by IE Select this to have the color of the connecting line(s) governed by an information element. Before choosing the information element (and an argument if applicable), choose the desired category in the System combo box. Leave trail Check this to leave all serving cell lines on the map. Serving cell list changed These settings refer to indication of handovers. Note that they are independent of the Serving cell settings. Line to added cell At handover, a line is drawn from the position where the new serving cell or active set member is first used. The line remains after the phone has moved on. This feature is available also for best server indications, although no actual handover is involved. Line to removed cell At handover, a line is drawn from the position where the old serving cell or active set member is last used. The line will remain on the map. This feature is available also for best server indications, although no actual handover is involved. NT11-20502 315 TEMS Investigation 13.1 User’s Manual 29.5.5.3. The Cell Color Theme This theme is used to visualize the neighbor relations of the current serving cell/active set members or of an arbitrary user-selected cell (only one cell at a time). The neighbor relations shown are those indicated in the loaded cell file; the neighbor presentation is not affected by the phone’s neighbor reporting. The only phone data fed into this theme is the serving cell data. By default, therefore, in the realtime presentation as well as during logfile replay, the cell drawn in green will be the phone’s current serving cell. However, if you stop the replay and click an arbitrary cell, the theme will be displayed with that cell as serving cell instead, independently of the phone’s interaction with the network. Presentation on Map yellow color from Cell theme GSM example: Cell Color theme (no route). active set WCDMA example: Cell Color and Cell Line themes. Active set members pointed out by solid lines (black). Neighbors indicated for all active set members (dashed red lines). 316 Chapter 29. Map Windows • 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 29.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 Not used; the choice does not matter. Mobile Choose the phone whose serving cell is to be displayed. Colors: Serving cell 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). Colors: Neighbor cells 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. NT11-20502 317 TEMS Investigation 13.1 User’s Manual Colors: Servingto-neighbor lines 29.5.5.4. • 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. 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 replay 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. 318 Chapter 29. Map Windows Presentation on Map selected cell; BCCH selected in context menu other cell using same ARFCN as BCCH other cell using same ARFCN as TCH Cell ARFCN theme. 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 Not used; the choice does not matter. Same BCCH ARFCN The fill color to use for cells that use the selected ARFCN as BCCH. Same TCH ARFCN The fill color to use for cells that use the selected ARFCN as TCH. NT11-20502 319 TEMS Investigation 13.1 User’s Manual 29.5.6. Presenting Pinpointing The Pinpoint theme presents the markers that you create when using pinpointing rather than a GPS to position data (section 10.1.4). Note: The Pinpoint theme is needed in order for the pinpointing mechanism itself to work. Therefore, this theme should never be removed. The following properties can be edited for the Pinpoint theme: Symbol Type, size, and color of waypoint symbols. Line Color and width of lines connecting waypoints. 29.5.7. Editing Themes To edit a theme: • In the Theme Settings dialog, select the theme you want to edit. • Click Edit. 29.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. 320 Chapter 29. Map Windows • To show a theme, check the box. • To hide a theme, uncheck the box. The same also applies to layers (section 29.7). 29.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 29.5.5). 29.5.10. Deleting Themes To delete a theme: • In the Theme Settings dialog, select the theme you want to delete. • Click Delete. 29.6. The Right-hand Pane 29.6.1. 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. NT11-20502 321 TEMS Investigation 13.1 User’s Manual 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 29.6.2. 322 Chapter 29. Map Windows 29.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 both during recording and during replay. During replay, the statistics cover only the part of the logfile that has been replayed and plotted so far, not the entire logfile. On the other hand, it should be noted that the plotting may be more or less thinned out (see section 29.5.3.1), so that more data goes into the statistics than actually appears on the map. NT11-20502 323 TEMS Investigation 13.1 User’s Manual 29.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. 29.7. Layers Section 29.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. 29.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 324 Name the new presentation layer. Chapter 29. Map Windows Layer type 29.7.2. Choose a layer type, corresponding to the theme types listed in section 29.5.1. 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 29.10). • To open the Layer Control: Click the Layer Control button. Up, Down NT11-20502 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. 325 TEMS Investigation 13.1 User’s Manual Add Add a layer. Select a TAB file and click Open. Remove Remove the selected layer. Visible Check to make the selected layer in the list visible. Note that the visibility of presentation layers can also be set in the Theme Settings dialog (see section 29.5.8). Selectable Not used. Disabled for presentation layers; should be turned off for map layers. Automatic Labels Check to make the labels of the selected layer visible. For labels to be visible, the layer they belong to must be visible. Disabled for presentation layers. Note that the visibility of labels may be conditioned by the zoom range. See Labels below. Editable Not used. Disabled for presentation layers; should be turned off for map layers. Display Set display properties for the selected layer. Labels Set label properties for the selected layer. 29.8. Map Context Menu When you right-click in the map, a context menu appears with choices as described below. 29.8.1. The Scale Bar This command shows and hides a scale bar showing distance in kilometers or miles. The unit of distance is governed from the Control Panel in Windows (e.g. Regional Options → Numbers → Measurement System). 29.8.2. Previous View This command returns you to the previous map view. (No further history of views is maintained.) 326 Chapter 29. Map Windows 29.8.3. View Entire Layer This commands zooms out to show the whole of the chosen layer. For example, choose an information element layer to view the whole of your route. 29.8.4. Setting the Map Projection This command allows you to set the map projection. It should be the same as in the cell file. 29.9. The Map Window Toolbar This section gives a description of the Map window toolbar buttons. Some of these activate functions described earlier in this chapter, but many others relate to map handling and have not previously been mentioned. GeoSet Manager: Start the GeoSet Manager which is used for creating new GeoSet files and for changing the properties of a GeoSet. See sections 29.3 and 29.10. Open Map: Open a map. Position Map: Position a map which is in bitmap or uncompressed TIF format. See section 29.4. Layer Control: Manage layers or change displaying or labeling properties. Changes are only temporary and cannot be saved. See section 29.7.2. To make changes to the GeoSet, use the layer control in the GeoSet Manager; see section 29.10.1. Add/Edit Themes: Add or remove presentation layers, or add, edit or remove themes. See section 29.5. Selection Tool: Click a presentation layer object to select it. Doubleclick the object to inspect what information it contains. Press and hold Ctrl to select a segment of a route (see section 29.6.2). Area Statistics Tool: Click and drag to view statistics for presentation layer objects within a rectangle (see section 29.6.2). Zoom In: Enlarge a portion of the map to view it in more detail. NT11-20502 327 TEMS Investigation 13.1 User’s Manual Zoom Out: View a larger area than the current map view. Holding down the Ctrl key swaps the zoom operations. If you have zoomed in and want to view the entire route again, right-click in the map, choose View, choose Entire Layer, and specify one of the presentation layers. Center Map: Click a spot in the map to center it around this spot. Pan Tool: Move the map by clicking and dragging. Ruler: Measure the distance of a route on the map consisting of straight line segments. Click in the map to indicate a starting point, then click at each turn. The distance of the last segment and the total distance are shown on the status bar at the bottom of the Map window. Double-click at the endpoint. To change the unit of distance, right-click in the map, choose Map Properties, and select the Defaults tab. Pinpoint: Mark waypoints on the map. Regarding positioning of logfile data by pinpointing, see section 10.1.4. Clear Map: Remove all the information in presentation layers from the map, except cell site information. 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. Previous Item: Select the previous object of the same type. Next Item: Select the next object of the same type. Last Item: Select the last object of the same type. 29.10. GeoSet Manager The GeoSet Manager looks and works much like a Map window. However, while changes made in a Map window cannot be saved, changes made using 328 Chapter 29. Map Windows the GeoSet Manager can be saved to the GeoSet (*.gst) file associated with the map. To start the GeoSet Manager, click the Start GeoSetManager button on the Map window toolbar. 29.10.1. Layer Control The Layer Control works the same way as in Map windows. See section 29.7.2. 29.10.2. Projections It is possible to set which projection to use for a GeoSet. If your GeoSet contains multiple layers with different projections, make sure you choose the projection of the layer you usually work with. • To change the projection, choose Map → Projections. NT11-20502 329 TEMS Investigation 13.1 User’s Manual 30. The General Window In the General window, found on the Navigator’s Menu tab in the Configuration folder, are collected miscellaneous settings that affect the behavior of the TEMS Investigation application. These settings are covered elsewhere in this manual in the appropriate contexts. 330 Chapter 31. Key Performance Indicators – KPIs (UMTS) 31. 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; however, all data needed for KPIs is recorded in TEMS Investigation logfiles. TEMS Discovery or TEMS Automatic are the products to use for explicitly generating KPIs and reports that present them.1 The present chapter gives an general discussion of KPIs as well as an overview of how to obtain them with TEMS products. Listings and brief definitions of the KPIs are found in the Technical Reference, chapter 9. Full detail on technical matters is given in separate documents which are found on the installation CD in the subdirectory Documents. In the present version of TEMS Investigation, KPI data can be collected for GSM and WCDMA. 31.1. Purpose of KPIs Most of the KPIs have been designed according to ETSI TS 102 250-2 V1.4.1 for performance measurements, that is, to measure accessibility, retainability, and integrity. A number of KPIs are not present in the ETSI specification; these are tagged “not in ETSI” in the Technical Reference, chapter 9. 1. Note that this is different from previous TEMS Investigation versions, where a “KPI Report” function was provided. NT11-20502 331 TEMS Investigation 13.1 User’s Manual 31.1.1. Accessibility Accessibility is the ability of the user to obtain a service within specified tolerances and under other given conditions. For example, in order for a service to be accessible in a packet-switched network, the user must be able to execute a chain of operations: • accessing the packet-switched network as such, i.e. performing an attach and a PDP context activation • within an active PDP context, accessing an IP service • (for WAP and MMS) activating a WAP session. 31.1.2. Retainability Retainability is the ability of the user to keep a service, once it has been accessed, under given conditions for a requested period of time. 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, such as (in the packet-switched case) manual reactivation of the PDP context. 31.1.3. Integrity Integrity indicates the degree to which a service is maintained without major disturbances once it has been accessed. Integrity KPIs show the performance of successful service attempts. Even if a service was accessed successfully, the user’s perception of the performance may vary greatly, from very good to unacceptably bad. 31.2. Obtaining KPIs with TEMS Products 31.2.1. General Procedure To obtain KPIs, perform the following steps: 1. Compose a TEMS Investigation script that executes one or several services. 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. Furthermore, the service testing should be enclosed by the 332 Chapter 31. Key Performance Indicators – KPIs (UMTS) control activities Start Recording and Stop Recording. See chapter 18, and particularly section 18.10 on snippets. 2. Run the script in TEMS Investigation. 3. Open the logfile(s) produced by the script in TEMS Discovery or TEMS Automatic, and generate KPI reports using one of these products. For details, please consult the documentation accompanying the relevant product. 31.2.2. Points to Bear in Mind A couple of things must be observed when recording KPI data: • The Swap Logfiles function (section 10.1.2) must not be used when recording KPIs. This is because all input to a KPI computation must be obtainable in a single logfile. • To obtain reliable KPI statistics you need to collect sufficient amounts of data. The mathematical relationships between sample size and statistical accuracy are given in a separate document, “Statistical Guidelines for Collecting KPI Data”, found on the installation CD in the subdirectory Documents. 31.2.3. “Events of KPI Type” When you test services in TEMS Investigation, special KPI events are displayed in the window Events Of KPI Type; see Information Elements and Events volume, section 7.4, “Data Events”. These events underlie the computation of KPIs. NT11-20502 333 TEMS Investigation 13.1 User’s Manual 32. Speech Quality Index – SQI TEMS products offer the quality measure SQI (Speech Quality Index) for estimating the downlink speech quality in a GSM, WCDMA, or CDMA cellular network as perceived by a human listener. Computing SQI for GSM and WCDMA requires data collected with Sony Ericsson phones. SQI for CDMA can be based on data from any CDMA phone that is connectable in TEMS Investigation. This chapter examines the workings of the SQI algorithm. See also the document “Speech Quality Measurement with SQI” which is included on the TEMS Investigation installation CD in the subdirectory Documents. 32.1. Background 32.1.1. SQI for UMTS SQI for GSM and WCDMA is a long-standing feature of TEMS products. However, in TEMS Investigation 9.0, the SQI algorithm was completely reworked, although its fundamental function remains similar to that of the old algorithm (the output of which is still available in TEMS Investigation). The focus of this chapter is to describe the new algorithm (called “SQI-MOS” in the application; see section 32.3). Reference is made to the previously used algorithm (the “old SQI”), and attention is drawn to certain important differences between the algorithms, but no comprehensive point-by-point comparison is made. As wideband speech codecs are now being deployed in mobile phones and networks, the SQI-MOS algorithm includes a model for rating wideband speech. 32.1.2. SQI for CDMA SQI for CDMA uses an SQI-MOS algorithm similar to those for GSM and WCDMA. SQI for CDMA currently does not support wideband. 334 Chapter 32. Speech Quality Index – SQI 32.2. Input to the SQI-MOS Algorithm 32.2.1. UMTS SQI-MOS for UMTS takes the following parameters as input: • The frame error rate (FER; GSM) or block error rate (BLER; WCDMA), i.e. the percentage of radio frames/blocks that are lost on their way to the receiving party, usually because of bad radio conditions. Frame/Block errors also occur in connection with handover, and these are treated like any other frame/block errors by the SQI-MOS algorithm. It should be noted that in WCDMA, handover block errors can usually be avoided thanks to the soft handover mechanism. In GSM, on the other hand, every handover causes a number of frames to be lost. Handovers are not modeled independently in any way by SQI-MOS.1 More generally, the current algorithm also does not consider the distribution of frame/block errors over time. • The bit error rate (BER). This is available in GSM only; no such quantity is reported by UEs in WCDMA mode. • The speech codec used. The general speech quality level and the highest attainable quality vary widely between codecs. Moreover, each speech codec has its own strengths and weaknesses with regard to input properties and channel conditions. The same basic SQI-MOS model is used for all supported speech codecs, but the model is tuned separately for each codec to capture its unique characteristics. SQI-MOS for UMTS is implemented for the following codecs: • GSM EFR, GSM FR, and GSM HR • all GSM AMR-NB and AMR-WB modes up to 12.65 kbit/s: – for narrowband, 4.75 FR/HR, 5.15 FR/HR, 5.9 FR/HR, 6.7 FR/HR, 7.4 FR/HR, 7.95 FR/HR, 10.2 FR, and 12.2 FR; – for wideband, 6.60, 8.85, and 12.65 1. In contrast, the old SQI algorithm includes a special “handover penalty” mechanism lowering the SQI score whenever a handover has occurred. NT11-20502 335 TEMS Investigation 13.1 User’s Manual • all WCDMA AMR-NB and AMR-WB modes up to 12.65 kbit/s: – for narrowband, 4.75, 5.15, 5.9, 6.7, 7.4, 7.95, 10.2, and 12.2; – for wideband, 6.60, 8.85, and 12.65. 32.2.2. CDMA SQI-MOS for CDMA closely resembles WCDMA SQI; compare section 32.2.1. Input parameters are: • Frame error rate • Speech codec used, including bit rate information The general discussion of these parameters in section 32.2.1 applies equally to CDMA (with the term “handoff” substituted for “handover”). SQI-MOS for CDMA is implemented for the following codecs: • QCELP13K • EVRC • SMV • VMR-WB (narrowband input only) 32.3. 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. The score is thus a value ranging from 1 to 5. The SQI-MOS algorithm produces a new quality estimate at intervals of • (UMTS) approximately 0.5 s • (CDMA) 2–4 s Such a high update rate is possible thanks to the low computational complexity of the algorithm. 1. ACR stands for Absolute Category Rating: this is the “regular” MOS test where speech samples are rated without being compared to a reference. 336 Chapter 32. Speech Quality Index – SQI 32.3.1. Narrowband vs. Wideband SQI-MOS (UMTS) It is necessary to point out that narrowband and wideband SQI-MOS scores are not directly comparable. The same MOS scale and range are used for both (as is the custom in the field of speech quality assessment); however, a given MOS score indicates, in absolute terms, a higher quality for wideband than for narrowband. This is because wideband speech coding models a wider range of the speech frequency spectrum and is thus inherently superior to narrowband coding. The highest attainable quality is therefore markedly better for wideband. It follows from this that when interpreting a figure such as SQI-MOS = 4.0, it is necessary to consider what speech bandwidth has been encoded. A further complicating circumstance is that there is no simple mapping between wideband and narrowband SQI-MOS, for reasons sketched in section 32.4.1. 32.3.2. SQI-MOS vs. Old SQI (UMTS) The old SQI (still available in the application) is expressed in dBQ. It should be stressed that SQI-MOS cannot be derived from these dBQ scores; the two algorithms are distinct (even if similar in general terms), and no exact mapping exists in this case either. 32.4. 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).1 In fact, the SQI-MOS models have mostly been trimmed using PESQ scores, rather than actual listening tests, as benchmarks.2 The exception is the wideband modes, where adjustments to the models have been made using the results of external listening tests. Regarding the latter, see section 32.4.1. Note carefully that PESQ and SQI-MOS do not have the same scope. PESQ measures the quality end-to-end, that is, also taking the fixed side into account, whereas SQI reflects the radio link quality only. This means that 1. See  www.pesq.org. 2. This is completely different from the old SQI algorithm, which was trained using listening tests alone. At the time that work was done, no objective speech quality measure of the caliber of PESQ was yet commercially available. NT11-20502 337 TEMS Investigation 13.1 User’s Manual PESQ and SQI values may differ while both being accurate in their respective domains. 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. • SQI-MOS, on the other hand, is a no-reference method that works with the received signal alone and extracts radio parameters from it (as described in section 32.2). Both methods try to assess to what degree the distortions in the received signal will be audible to the human ear; but they do it in completely different ways. PESQ scores need to be averaged over a range of speakers in order to eliminate speaker bias, i.e. variation stemming from the characteristics of individual speakers. Such averaging is not required in the case of SQI-MOS, since the speaker-contingent variation is already built into the model (it has been trained with a large number of speakers). 32.4.1. Notes on PESQ for Wideband (UMTS) (This subsection is relevant for UMTS only, since CDMA SQI currently does not extend to wideband.) The PESQ algorithm for wideband (8 kHz) speech coding – as opposed to that for narrowband (4 kHz) – is afflicted with certain recognized shortcomings. The use of PESQ as a benchmark therefore complicated the development of SQI-MOS for wideband. Below is a brief discussion of this topic. One relevant fact is that, in certain circumstances, wideband PESQ has been found to produce lower scores than narrowband PESQ, even for clean speech.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; a mapping could then be applied to align the wideband scores to narrowband. 1. This is a phenomenon independent of the circumstances described in section 32.3. 338 Chapter 32. Speech Quality Index – SQI Unfortunately, things are not that simple. Wideband PESQ is much more sensitive to speaker bias than is narrowband PESQ (compare the introduction of section 32.4): at a fixed FER/BLER, wideband PESQ scores for different speakers show a spread of more than one point on the MOS scale. For narrowband, this variability is limited to a few tenths of a MOS point. The upshot of this is that no straightforward mapping between wideband and narrowband PESQ can be constructed, and consequently outputs from the two are not directly comparable. Attempts have been made within ITU to develop such a mapping, but so far with no satisfactory results. (It is probable that the task of assessing wideband speech quality requires further refinement of the mathematical models used.) 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. The material used was the results from listening tests conducted during standardization of the AMR speech codec.1 Only clean speech ratings from these tests were used. This tuning resulted in an adjustment of the SQI-MOS model that is linear as a function of FER/BLER. The largest correction was applied to the cleanspeech SQI-MOS score (i.e. at zero FER/BLER), while the rock-bottom SQIMOS (the worst possible score, attained at very high FERs/BLERs2) was left unchanged. 32.5. Comparison with Other Radio Parameters GSM In the past, speech quality in GSM networks was often measured by means of the RxQual parameter (which is also available in TEMS products). Since RxQual is merely a mapping of time-averaged bit error rates into a scale from 0 to 7 ( 3GPP 45.008, section 8.2.4), it cannot of course provide more than a rough indication of speech quality. 1. See  3GPP TR 26.975, “Quality in Clean Speech and Error Conditions”, version 7.0.0. 2. FER = 60% was selected as endpoint. Samples with FER > 60% were excluded from the SQI-MOS modeling, 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. NT11-20502 339 TEMS Investigation 13.1 User’s Manual 33. Audio Quality Measurement (AQM): General Audio quality measurement, including PESQ, can be purchased as an option with TEMS Investigation. It can be performed in GSM, WCDMA, and CDMA networks. PESQ, short for Perceptual Evaluation of Speech Quality, is the industry standard for voice quality measurement. The PESQ algorithm measures endto-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. 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. The PESQ algorithm is defined by the ITU-T standard P.862. For in-depth information about PESQ, see also  www.pesq.org. 33.1. Measurement Setups in TEMS Investigation Audio quality measurement (AQM) in TEMS Investigation can be done in a number of contexts and hardware configurations. A summary of the possibilities is given in the following table: Service CS voice VoIP 340 Call Parties Auxiliary Components AQM Computed By Ref. Mobile to fixed Call Generator; AQM modules AQM modules 34.1 Mobile to mobile Mobile Receiving Unit (MRU) AQM modules 34.2 Mobile to mobile Audio Capturing Unit (ACU) PC 35 Mobile to mobile (2 PCs used) PCs 36 Chapter 34. AQM with Call Generator/MRU 34. AQM with Call Generator/MRU In this AQM configuration, measurements are made mobile-originated voice calls. The call may be received: • by a stationary component known as the Call Generator, connected to the fixed telephone network (section 34.1), or • by a Mobile Receiving Unit (MRU) housed in a mobile phone (section 34.2). Further technical information about these methods of audio quality measurement is found in the document “AQM in TEMS Products (Including PESQ)”, which is included on the TEMS Investigation installation CD in the subdirectory Documents. A separate MRU User’s Manual is also available. 34.1. Mobile-to-fixed Audio Quality Measurement with Call Generator This section describes the AQM setup where a Call Generator acts as the receiver of AQM calls. It is referred to by the M2F DL + UL option in the PESQ Measurement activity of the Service Control script (see section 18.17.6.4). The computation of AQM scores is done in dedicated hardware units called AQM modules: one connected to the phone and to the PC, handling the downlink; and one housed in the Call Generator, taking care of the uplink. These modules contain DSP hardware. The downlink AQM module can optionally be mounted along with the phone in an equipment case. Below is an overview of the measurement configuration. NT11-20502 341 TEMS Investigation 13.1 User’s Manual TEMS Investigation, Service Control script Downlink AQM module Reference audio Test terminal Transmitted audio Received degraded audio (from Call Generator) Downlink AQM Logfile containing downlink AQM data Reference audio Voice calls Uplink AQM data in XML files (copying/ download) Logfile with uplink AQM data merged in and downlink AQM data timeadjusted TEMS Investigation, 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. • The phone calls the Call Generator and plays the reference sentences. The Call Generator responds by playing the same reference sentences. • The received (degraded) signals at either end are forwarded to the respective AQM modules, where the signals are compared with the originals, yielding uplink and downlink PESQ scores. The AQM modules also record a number of further audio quality measurements such as echo delay, echo attenuation, and volume. See Information Elements and Events, section 3.1. • The downlink AQM data is written to regular TEMS Investigation logfiles. The uplink AQM data is stored in XML files. • To merge uplink AQM data into the logfiles, the logfile export function is used. See section 10.6. 342 Chapter 34. AQM with Call Generator/MRU 34.2. Mobile-to-mobile Audio Quality Measurement with MRU The main difference between this setup and that described in section 34.1 is that the fixed Call Generator is replaced by a Mobile Receiving Unit, MRU, as recipient of the AQM calls. This is the M2M DL option in the PESQ Measurement activity of the Service Control script (see section 18.17.6.4). Another important difference is that only downlink AQM scores are obtained with this method; the MRU does not have an AQM module. Measurement configuration: TEMS Investigation, Service Control script Downlink AQM module Reference audio Downlink AQM Test terminal Transmitted audio Received degraded audio (from MRU) Logfile containing downlink AQM data Voice calls Reference audio MRU (Mobile Receiving Unit) Logfile with AQM data timeadjusted 34.3. TEMS Investigation, logfile export Obtaining AQM Data Here is an overview of how to record and present audio quality measurements in practice. It covers the both the Call Generator configuration and the MRU configuration. NT11-20502 343 TEMS Investigation 13.1 User’s Manual 34.3.1. Prerequisites You need to possess the following: • License for collecting AQM data: see the Getting Started Manual, section 3.3.2. • Phone supporting audio quality measurement: one of those listed as AQM-capable in the Getting Started Manual, section 10.3.1. • One or several downlink AQM modules (either standalone units or DSP cards mounted in an equipment case). One AQM module is required for each phone that you want to measure AQM with. • Call Generator or MRU. 34.3.2. • Practical Considerations You can plug a headset into the AQM module during measurement to listen live to the received audio. However, you must not adjust the volume using the headset, since that would distort the AQM output. The AQM algorithms require a fixed preset volume. 34.3.3. Recording AQM Data The description below assumes that a single phone is used to make audio quality measurements. It is possible to perform such measurements with several phones at once, using a different AQM module with each phone. • 344 Compose a script as follows (for details of all activities, see chapter 18): – Add a Dial activity. – Add a PESQ Measurement activity after the Dial. See section 18.17.6.4. For mobile-to-fixed AQM, set Measurement Type to “M2F DL + UL”. The phone will then make voice calls to a Call Generator (identified by its phone number). For mobile-to-mobile AQM, set Measurement Type to “M2M DL” to designate an MRU as receiving party in the same manner. Finally, set a value for PESQ Duration, which governs how long to maintain the call and collect audio quality measurements. – Conclude with a Hang Up activity. – If you wish to synchronize AQM calls from multiple phones, put the calls (i.e. sequences of the form Dial → PESQ Measurement → Hang Up as just described) in separate branches in a Parallel Chapter 34. AQM with Call Generator/MRU construct. To also make all calls terminate at the same time, simply use the same PESQ Duration for all calls. – Book-end all of the above activities with Start Recording and Stop Recording to have the calls recorded in a logfile. – To have the above procedure automatically repeated as many times as desired, enclose everything defined so far within a While construct. • Connect your AQM equipment case (or alternatively your phone and standalone AQM module) to the PC and point to the requisite driver files as described in the Getting Started Manual, section 7.7. • Associate the phone with the AQM module on the Navigator’s Equipment tab: see section 8.1.5. The red LED on the AQM module should go out. • Make sure that the phone’s number is defined in TEMS Investigation and enter the number manually if necessary: see section 7.3.2.2. • When using the AQM module for the first time after connecting it, you must wait for the AQM module to start up its DSP and finish some preprocessing. Wait until the reports “Dsp Started Ver. 2” and “Pre Processing Ready” appear in the Mode Reports window. • Run the script and record your logfiles. 34.4. Merging Uplink AQM Data into Logfiles After completing your measurements, use the logfile export function to merge the uplink AQM data (recorded by the Call Generator) into the logfile, which already contains the downlink AQM scores. See section 10.6. Note that this operation is necessary also for mobile-to-mobile AQM, although no uplink AQM data is recorded in that case. This is because the logfile export procedure also corrects the time alignment for downlink data (again, see section 10.6.2). If precise time alignment for AQM data is not of interest, however, the logfile export can be skipped. 34.5. Presentation of AQM Data 34.5.1. Information Elements All AQM data is available as information elements, so that they can be included in any presentation. The same information elements are used regardless of the choice of AQM setup. NT11-20502 345 TEMS Investigation 13.1 User’s Manual Status windows named Speech Quality are provided where all AQM information elements (as well as some other data) are presented. When viewing (downlink) AQM data in real time, or when replaying a logfile where the uplink AQM data has not yet been merged in, you must keep in mind that this data will lag behind other information elements because of the processing delay in the DSP. The offset is 5.5 s, or one speech sentence. Downlink Frequent AQM is not displayed at all prior to merging. When you merge the uplink AQM data into the logfile, the 5.5 s offset for downlink data is removed so that all data is correctly aligned. (For full details, see section 10.6.2.) 34.5.2. PESQ Key Performance Indicator A PESQ-based KPI is computable on the basis of TEMS Investigation data. See the Technical Reference, section 9.1.5. 346 Chapter 35. AQM with Audio Capturing Unit (ACU) 35. AQM with Audio Capturing Unit (ACU) In this AQM configuration, all measurement is conducted during mobile-tomobile voice calls. 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. This configuration is referred to by the M2M DL + UL option in the PESQ Measurement activity of the Service Control script (see section 18.17.6.4). TEMS Investigation, Service Control script Voice calls Reference audio PESQ calculation Relayed degraded audio Test terminals Audio Audio Capturing Unit Logfile with downlink and uplink PESQ 35.1. Voice calls 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. NT11-20502 347 TEMS Investigation 13.1 User’s Manual 35.1.1. Prerequisites You need to possess the following: • License for collecting AQM data: see the Getting Started Manual, section 3.3.2. • Phone supporting audio quality measurement: one of those listed as AQM-capable in the Getting Started Manual, section 10.3.2. • Audio Capturing Unit (TerraTec DMX 6Fire USB). • USB hub for phones (delivered with ACU). • Custom audio cables (delivered with ACU): • – 2.5 mm cable for Huawei C8600 – 3.5 mm cable for Sony Ericsson Xperia arc, Nokia C7 – Sony Ericsson W995 phones use the SE System Connector cable from the AQM module cable kit. Audio adaptor cables for connecting audio cables to the ACU (delivered with ACU). 35.1.2. Preparations See the Getting Started Manual, chapter 16. 35.1.3. Recording AQM Data This section assumes that all equipment has been prepared and interconnected as described in the Getting Started Manual, chapter 16. • Compose a script similar to the sample script files which are provided in [My] Documents\TEMS Product Files\TEMS Investigation 13.1\Scripts. For each phone pair, use a Parallel activity with one branch for each phone, one dialing and the other answering. Regarding the PESQ Measurement activity, refer to section 18.17.6.4. The diagrams in section 35.1.3.1 below show the structure of the ready-made scripts. • Run the script and record your logfiles. 348 Chapter 35. AQM with Audio Capturing Unit (ACU) Note: Be sure never to alter volume levels anywhere during measurement – whether in the phones, on the TerraTec box using the physical controls, in the TerraTec PC user interface, or in Windows. If the volume is not kept constant, incorrect PESQ scores will result. 35.1.3.1. Recommended Structure of AQM Scripts AQM script for one pair of phones. NT11-20502 349 TEMS Investigation 13.1 User’s Manual AQM script for two pairs of phones. 35.2. Presentation of AQM Data 35.2.1. Information Elements All computed AQM data is available as information elements, so that they can be included in any presentation. The same family of information elements is used as for the Call Generator and MRU AQM setups. Please note, however, that for AQM with ACU the following holds: • PESQ DL for one phone in a pair is also presented as PESQ UL for the other phone in that pair. • Not all AQM information elements are obtained: see the Information Elements and Events volume, chapter 5. The suite of “Echo” elements as well as Speech Path Delay are only relevant when interacting with a PSTN, so they are not populated in this mobile-to-mobile setup. 350 Chapter 35. 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. 35.2.2. PESQ Key Performance Indicator A PESQ-based KPI is computable on the basis of TEMS Investigation data. See the Technical Reference, section 9.1.5. 35.3. Notes on PESQ Scores Obtained with Individual Phone Models For UMTS, PESQ scores obtained with various phones using the setup described in this chapter generally correlate closely with PESQ as measured with AQM modules (chapter 34). There is one exception, namely when the Sony Ericsson Xperia arc acts as sender (with any of the supported UMTS phones as receiver). Tests consistently show markedly lower PESQ scores with this configuration compared to other phone model pairings. The reason is believed to consist in the different filtering applied to the audio output in the Xperia arc phone, a kind of filtering that is judged unfavorably by the PESQ algorithm. By contrast, for audio samples received by the Xperia arc, the PESQ score is not affected. The described characteristics of the Xperia arc must be taken into account when evaluating PESQ scores obtained with the device. For CDMA, the Huawei C8600 exhibits behavior similar to that of the Sony Ericsson Xperia arc, causing a lowering of PESQ scores. NT11-20502 351 TEMS Investigation 13.1 User’s Manual 36. AQM for VoIP Audio quality measurement can also be performed during VoIP testing. In this measurement setup, no auxiliary hardware components are involved, but instead two PCs are used, each of which have a mobile phone connected. The AQM computation is done on the PCs. VoIP testing is controlled by special Service Control activities, and the audio quality measurement is governed by the VoIP Voice Quality activity. Everything about the Service Control mechanisms is covered in section 18.17.6. For a comprehensive treatment of VoIP testing, including AQM, please turn to the document “VoIP Testing with TEMS Investigation”, found on the TEMS Investigation installation CD in the subdirectory Documents. A quick overview of the measurement setup follows below: TEMS Investigation: VoIP client controlled by Service Control script PC #1 AQM calculation VoIP calls Reference audio Received degraded audio Reference audio Test terminals #1 Logfile containing downlink AQM for test terminal #1 352 TEMS Investigation: VoIP client controlled by Service Control script VoIP server #2 Received degraded audio Logfile containing downlink AQM for test terminal #2 PC #2 AQM calculation Chapter 36. AQM for VoIP The calling device is connected to one PC and the called device to the other. Audio is sent in semi-duplex fashion between the parties, that is, in both directions but only in one direction at a time. Each instance of TEMS Investigation has a built-in VoIP client; the VoIP clients thus reside in the PCs and not in the mobile devices. 36.1. Obtaining AQM Data Full instructions are given in the document “VoIP Testing with TEMS Investigation”, which see. 36.2. Presentation of AQM Data This too is covered exhaustively in the document “VoIP Testing with TEMS Investigation”. The crucial information element is VoIP PESQ Score. NT11-20502 353 TEMS Investigation 13.1 User’s Manual 37. 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. How this algorithm works is the subject of the present chapter. See also the document “Video Telephony Quality Measurement with VTQI” which is included on the installation CD in the subdirectory Documents. 37.1. General Properties of VTQI Like SQI (chapter 32), VTQI is a no-reference method which judges the quality of the received signal on its own merits, without knowledge of the original. 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. The output from the VTQI algorithm is expressed as a value between 1 and 5, conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests. The unit for VTQI is called “MOS-VTQI”. VTQI estimates the quality of the video call as perceived by the viewer at a moment in time. It is updated continuously during the call. There is no overall assessment of entire calls analogous to static VSQI computed for entire streaming clips (as described in section 38.4.1). 37.2. What VTQI Is Based On The VTQI score is based on the following non-perceptual input: • 354 The quality of the encoded (compressed) signal prior to transmission. This quality is straightforwardly a function of the codecs used and the bit rate. However, since the radio bearer currently used in UMTS for video Chapter 37. Video Telephony Quality Index – VTQI telephony is always a 64 kbit/s bearer, bit rate variation is in fact not an issue. This leaves the codecs: • – For the H.263 and MPEG-4 video codecs, the “clean” quality in terms of VTQI has been computed in advance. In practice, what codec is used in the video call is deduced from the signaling between server and client. (In the current implementation of VTQI in TEMS Investigation, the video codec is assumed to be H.263, but a VTQI model for MPEG-4 also exists.) – The audio codec is assumed always to be AMR-NB operating at 12.2 kbit/s. BLER (block error rate). This is the most important single cause of poor quality in video telephony. Focusing on BLER means that VTQI will faithfully reflect the impact of air interface conditions on QoE. Bit error rate (BER), on the other hand, is not reported by current WCDMA user terminals and so is not available for use in the VTQI model. 37.3. What VTQI Does Not Consider VTQI does not directly consider the signal presented to the human viewer; that is, no analysis of perceptual input is performed to detect specific visible artifacts. The transferred video is not analyzed frame by frame in any way. Thanks to the monitoring of BLER, however, even slight degradations impacting video and audio perception will still be noticed by the algorithm and affect the VTQI score. 37.4. Update Rate VTQI is reported as the information element VTQI Realtime Score. This element is updated regularly – at intervals of length 1–2 s depending on the phone model – throughout the video call. Each VTQI score is a time average taken over the last 8 seconds; the first score is thus obtained 8 s into the video call. This windowing procedure prevents short block error bursts from impacting the VTQI score in a disproportionate manner. NT11-20502 355 TEMS Investigation 13.1 User’s Manual 38. Video Streaming Quality Index – VSQI The information element VSQI (Video Streaming Quality Index) estimates the viewer-perceived video and audio quality achieved during video streaming sessions. This chapter takes a look the VSQI algorithm. See also the document “Video Streaming Quality Measurement with VSQI” which is included on the installation CD in the subdirectory Documents. Compare chapter 39 on MTQI. 38.1. General Properties of VSQI Like SQI (chapter 32), VSQI is a no-reference method which judges the quality of the received signal on its own merits, without knowledge of the original. 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. The output from the VSQI algorithm is expressed as a value between 1 and 5, conforming to the MOS (Mean Opinion Score) scale which is frequently used in subjective quality tests. The unit for VSQI is called “MOSVSQI”. 38.2. What VSQI Is Based On The VSQI score is based on the following non-perceptual input: 1. The quality of the encoded (compressed) signal prior to transmission. This quality is straightforwardly a function of the video and audio codecs used, and their bit rates. The information actually used by the VSQI algorithm is the video codec type and the total (video + audio) bit rate. The “clean” quality has been computed in advance for the codecs listed in section 38.4.1. 356 Chapter 38. Video Streaming Quality Index – VSQI 2. The amount of initial delay and the subsequent interruptions during playback of the video sequence: that is, the time required for initial buffering and the incidence of rebuffering. 3. The amount of packet loss at the application level (i.e. in the video streaming client). 38.3. What VSQI Does Not Consider VSQI does not directly consider the signal presented to the human viewer; that is, no analysis of perceptual input is performed to detect specific visible artifacts. The transferred video is not analyzed frame by frame in any way. Thanks to the monitoring of packet loss (item no. 2 in section 38.2 above), however, even slight problems with blockiness, jitter, and so on will still be noticed by the algorithm and affect the VSQI score. 38.4. Static and Dynamic VSQI Two versions of the VSQI algorithm have been devised: one static and one dynamic version. Static VSQI is presented in the event Streaming Quality VSQI. It does not appear as an information element. Dynamic VSQI, on the other hand, is contained in the information element Streaming VSQI. 38.4.1. Static VSQI The static version of VSQI takes an entire streamed video clip as input and assigns a single quality score to it. Input parameters to the static version of VSQI are as follows: • Video codec used (H.263, H.264, 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, we may describe the calculation of static VSQI with the following formula: NT11-20502 357 TEMS Investigation 13.1 User’s Manual Here, VSQIclean is the “clean value” obtained for the clip prior to transmission. This score is determined by the quality of the encoding, which is in turn dependent on the choice of codecs and bit rate. The size of the buffering penalty depends on the time taken for initial buffering, the time spent rebuffering, and the number of rebuffering events. The size of the packet loss penalty is determined as follows. A running packet loss average over the last 4 s is computed approximately every second, and the values thus obtained are weighted and summed to yield an appropriate overall measure of the packet loss. The latter is then translated into a deduction from the VSQI score. 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. The video sequences must not be too short because of how the buffering works: each instance of rebuffering takes several seconds to complete, and moreover if the clip is short enough it will have been buffered in its entirety before the replay starts, so that no rebuffering will ever occur. For clips considerably longer than 30 s, on the other hand, disturbances towards the end will be more harshly penalized by viewers than those occurring early on, simply because the late ones are remembered more vividly. Therefore, since the current VSQI algorithm does not take into account such memory effects, it would probably perform slightly worse for long clips. (The dynamic version of VSQI is naturally not affected by this limitation.) 38.4.2. 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. It is updated regularly – at intervals of the order of 1 s – while the video clip is playing. Each VSQI output value is dependent on the recent history of the streaming session (i.e. recent packet loss levels and possible recent buffering events). 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 358 Chapter 38. 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 best achievable quality, i.e. the “ceiling” in the graph, is dependent on the codec/bit rate combination but is also affected by the amount of packet loss. In this example the packet loss is assumed to be constant so that the influence of buffering can be clearly discerned. 1. The user tolerates (and might even expect) a certain amount of initial delay; but the longer the buffering drags on, the more the user loses patience. 2. Once the replay gets going, the perceived quality picks up again and soon approaches the highest achievable level. 3. If rebuffering occurs, VSQI deteriorates rapidly. Rebuffering events are much less tolerated by viewers than initial buffering, especially if repeated; VSQI captures the latter by making the slope of the curve steeper for each new rebuffering event. 4. After the replay has recommenced, VSQI recovers reasonably quickly, but not infrequently from a rock bottom level. NT11-20502 359 TEMS Investigation 13.1 User’s Manual 39. Mobile TV Quality Index – MTQI MTQI (Mobile TV Quality Index) is a refinement of the video part of the VSQI quality measure (see chapter 38). Unlike VSQI, MTQI does not include an assessment of audio quality. The MTQI algorithm can be concisely characterized as follows. • 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. Buffering with skipping means that frames are skipped in connection with buffering; no skipping means that every frame is replayed. • Supported video codecs: H.263, H.264, REAL, MPEG4 • Supported video formats: QCIF, QVGA 360 Chapter 40. C/I Measurement (GSM) 40. C/I Measurement (GSM) This chapter explains in some detail how GSM C/I measurements are made and why they are useful. The discussion provided here is centered on the voice service. It should however be noted that the C/I measure is just as useful in the context of packet-switched data services. In fact, towards the high end of the C/I range, speech quality is not further improved, while packet-switched transmissions very clearly do benefit from every extra dB, particularly if EDGE is used. 40.1. 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. The C/I measurement function built into TEMS Investigation enables the identification of frequencies that are exposed to particularly high levels of interference, something which comes in useful in the verification and optimization of frequency plans. C/I can be measured in dedicated mode. 40.2. Requirements on a Robust C/I Measure Downlink quality in a radio network can be monitored using the TEMS Speech Quality Index, SQI (see chapter 32). In this way, areas with inadequate quality can be identified. However, if frequency hopping is used in the network, it is difficult to pinpoint the frequencies that are affected by the degradation. To help resolve such ambiguities, TEMS Investigation offers the possibility of measuring average C/I for each of the frequencies used in a call. To obtain a correct C/I estimate, one must take into account the possible use of power control and/or discontinuous transmission (DTX). In the past, 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). Since such a scheme fails to allow for power control and DTX on the TCHs, it may produce misleading results. By NT11-20502 361 TEMS Investigation 13.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. 40.3. Details on C/I Measurements In dedicated mode, average C/I is presented approximately twice a second, which is equal to the ordinary measurement interval. If frequency hopping is employed, the average C/I for each frequency is presented. The measurement range extends from 0 dB to 35 dB. A C/I below 0 dB can be regarded as highly unlikely; in addition, if the number of hopping frequencies is low, C/I values below this limit would normally result in a dropped call. Beyond the upper limit, the performance is not further improved (at least not with today’s modulation schemes). Hence, the limitation of the measurement range is not a restriction.1 If downlink DTX is used, the number of bursts transmitted from the base station to the phone may be lower than the maximum, depending on the speech activity level on the transmitting side. TEMS Investigation makes measurements only on the bursts actually sent from the base station and disregards bursts not transmitted. 40.4. Accuracy The number of hopping frequencies determines the number of bursts used for the C/I measurement on each frequency. For example, if four frequencies are used, 25 bursts (on average) per frequency are received in each half-second (to be precise, 480 ms) interval. With more frequencies, there are fewer bursts for each frequency. 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, and four frequencies are used for transmission, and there are no DTX interruptions, the measurement error is typically smaller than 1 dB. 40.5. An Example To illustrate the use of C/I, data from a test drive is depicted in the figure below. The test drive lasts 40 seconds. EFR speech coding and cyclic 1. The C/I information elements preserve a wider value range –5 ... 35 dB, which reflects the performance of older technology. 362 Chapter 40. C/I Measurement (GSM) 20 60 SQI 50 0 0 RxLev 40 5 10 15 20 25 time [s] 30 35 40 5 10 15 20 25 time [s] 30 35 40 RxLev [dB] SQI [dBQ] frequency hopping with four frequencies are employed throughout. The upper part of the graph shows SQI and RxLev, while the lower part shows C/I for each of the four frequencies: C/I [dB] 25 20 15 10 5 0 0 As appears from the upper graph, SQI dips sharply towards the end of the test drive (after 35 s), indicating poor speech quality. On the other hand, RxLev stays about 50 dB above –110 dBm the whole time. This means that the dip in quality is not due to low signal power level, that is, the quality problem is to do with interference rather than coverage. In fact, and interestingly, RxLev increases during the SQI dip, probably because the power of the interferer increases. Now, looking at the C/I graph, one sees that two of the four frequencies (the thick lines) have a C/I worse than 10 dB during the SQI dip. This explains the poor speech quality, identifying precisely which channels are disturbed. Such information can then be utilized in the process of optimizing the frequency plan for the area. NT11-20502 363 TEMS Investigation 13.1 User’s Manual 41. Uplink (MTR) Data (GSM) This chapter explains the concept of uplink data and points out the benefits of utilizing such data in the network analysis. 41.1. Uplink Data: MTR Files In cellular networks using infrastructure from Ericsson, it is possible to record so-called MTR files. The MTR (Mobile Traffic Recording) function traces the behavior of an individual phone by recording event data produced in the Base Station Controller (BSC), as well as measurement data from the BTS and from the phone itself. The phone-originated data is also a subset of what is found in the TEMS logfile, although in the MTR file it is not tagged with any positioning information. The remainder of the MTR file data is referred to as “uplink data” within the TEMS Investigation framework, and MTR files are called “uplink files” in this manual outside the present section, unless characteristics specific to MTR files are dealt with. It should be noted that MTR files contain no idle mode data, but only data from calls. In general, one MTR file is generated for each call. MTR files can be recorded for voice calls only, not when running a data service. This manual does not go into the details of obtaining and transferring MTR files. In the instructions given here it is assumed that you already have the requisite MTR files stored on your computer. At present, TEMS Investigation is not capable of reading uplink data from other manufacturers’ equipment. 41.1.1. Supported MTR File Versions • R6.x, R7, R7.1, R8, R10 • MTR 2005 in binary format • G10B. 364 Chapter 41. Uplink (MTR) Data (GSM) 41.2. Utilizing Data from Uplink Files Uplink files can be replayed as-is in TEMS Investigation. They can however also be merged with the corresponding TEMS logfiles, producing output in the form of an augmented logfile which can be replayed in the usual manner. (See section 41.3 below.) The contents of the uplink file can thus be viewed concurrently with the downlink data recorded in the TEMS logfile. A further advantage of merging the files is that geographic positioning can be obtained for the uplink data. The uplink data is presented as a separate class of information elements; see section 41.4. The benefit of studying uplink data is that it yields a clearer picture of what is going on in the network and thus permits the network analyst to draw more informed conclusions. Handovers are a case in point, as is discussed in the following section. 41.2.1. Uplink Data on Handovers Decisions about handovers are made for the phone by the network (normally in the BSC), and not by the phone itself. The phone contributes in the decision-making process by reporting the signal strength of neighboring cells, but the network bases the final handover decision on other information as well (independent measurements of signal strength, and also estimates of radio quality and timing advance). Now, the TEMS logfile only contains the phone’s own “advisory” measurements, whereas the uplink file includes the final decision arrived at by the BSC (expressed as ranking of neighbors). Therefore, the uplink data shows more clearly how the phone interacts with the network. 41.3. Merging Uplink Files with TEMS Logfiles Merging and synchronization of the two file types are carried out from the Export Logfile window. Refer to section 10.7 for a complete description of this procedure. 41.4. Presentation of Uplink Data The uplink data is available as a separate class of information elements – the GSM Uplink category on the Navigator’s Info Element tab. There are status NT11-20502 365 TEMS Investigation 13.1 User’s Manual windows, a message window, and a line chart dedicated to presenting this data. See Information Elements and Events, section 8.1.5. A full listing of information elements culled from the MTR file is found in Information Elements and Events, section 3.10. Note: For MTR files, the “GSM Uplink” category in fact also includes the downlink data found in the file, data which duplicates some of the information in the TEMS logfile (although the values may not be exactly identical). 366 Chapter 42. GSM Channel Verification 42. GSM Channel Verification The GSM Channel Verification tool allows you to check the availability of a set of GSM traffic channels, typically those used in one cell or a set of cells. 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. 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. To reduce the testing time, you can use several phones. 42.1. • The GSM Channel Verification Window To perform GSM channel verification, open the GSM Channel Verification window from the Control folder on the Navigator’s Menu tab. In this window, each row corresponds to a particular combination of BCCH and TCH. Throughout the present chapter, the following terminology will be used: • Test case: One row in the GSM Channel Verification window, i.e. one BCCH/TCH combination. 1. Sony Ericsson phones with both GSM and WCDMA capability must be locked on GSM (see section 8.1.6) to be able to perform GSM channel verification. NT11-20502 367 TEMS Investigation 13.1 User’s Manual • Group, Test case group: All test cases with the same BCCH, corresponding to one cell. Note that test case groups are not explicitly separated in the user interface. • Test: All rows in the window, or in other words the complete contents of the *.tch file (see section 42.11). 42.2. Adding a Test Case To add a test case, click Add. The following dialog appears: MS The phone that should execute this test case. BCCH ARFCN The ARFCN of the BCCH to be tested. TCH ARFCN The ARFCN of the TCH to be tested. Note that a special test case must be prepared to test TCH timeslots on C0. Example: If C0 has ARFCN 10, with BCCH in timeslot 0 and TCHs in timeslots 2–7, and C1 has ARFCN 20, then you must prepare two test cases: one with {BCCH = 10, TCH = 10} and one with {BCCH = 10, TCH = 20}. Band The frequency band where the channels are located. Timeslot Check the timeslots you wish to test. 368 Chapter 42. GSM Channel Verification You can add multiple test cases without exiting the dialog, by entering the settings for one test case at a time and clicking Apply after each. The result in the GSM Channel Verification window will look like this: Here, timeslots to be tested are indicated by full stops (“.”), while timeslots not concerned by the test are marked by underscores (“_”). 42.3. Editing and Removing Test Cases To edit a test case, select it in the GSM Channel Verification window and click the Edit button. Note that to edit a test case which has been partially executed, you must reset the test case (section 42.8). That is, you cannot keep any of the old test results in the window; but you do have the option to create a report on these results (section 42.10) or save the test case in a special file format (section 42.11). To remove a test case, select it and click the Delete button. 42.4. Automatic vs. Manual Verification There are two fundamentally different ways of performing channel verification. • Automatic verification: For each timeslot, TEMS Investigation decides whether the timeslot can be accepted or not. In order for a timeslot to pass, the call must be set up correctly and maintained for a user-specified period of time, and in addition a set of user-specified quality requirements must be satisfied. • Manual verification: For each timeslot, you decide yourself whether to accept or reject the result of the test, by clicking either of two buttons. NT11-20502 369 TEMS Investigation 13.1 User’s Manual How to take this decision is up to the user. You might be content with assessing the downlink quality by calling a service such as the speaking clock, or you might want to “call a friend” in each instance to have the uplink quality checked as well. Automatic verification can be done more quickly, but is a less reliable indicator of what a user’s experience of the radio conditions would be like. Manual verification is more work-intensive and probably more timeconsuming, but also yields an improvement in reliability proportional to the work invested. You choose how to perform the test in the Properties dialog. In the GSM Channel Verification window, click the Properties button. Verification mode Choose Manual or Automatic (see explanation above). Test phone number Enter the phone number to call when testing. Valid characters in the phone number are {*, +, #, 0–9}. Add MAIO and HSN... Check this to have the Mobile Allocation Index Offset (MAIO) and the Hopping Sequence Number (HSN) indicated in the test report (section 42.10) for any test case that fails in automatic verification mode. 370 Chapter 42. GSM Channel Verification • Choose the QoS parameters tab to stipulate conditions for accepting a timeslot in automatic verification mode. Delay time before evaluation The time to wait before evaluating the quality parameters. Approve timeslot if these conditions are met: Check the conditions you want to use, and specify thresholds. The conditions will be evaluated at one point in time, namely as soon as the delay period has expired. The checked conditions must all be satisfied in order for the timeslot to be accepted, i.e. they are ANDed together. 42.5. Activating Phones Before running the test you must naturally activate the phones assigned to do the testing. See section 7.4. Note: In manual verification mode, only one phone can be used. NT11-20502 371 TEMS Investigation 13.1 User’s Manual 42.6. Running the Test 42.6.1. Getting Started To be able to execute a test you must have done the following: • Prepared your test cases according to sections 42.1–42.3. • Chosen manual or automatic verification mode, and indicated a phone number to call: see section 42.4. • Activated the phone or phones to be used in the test. Then, to start running the test currently displayed in the GSM Channel Verification window: Click Start. TEMS Investigation will now start attempting calls on the TCHs specified, having locked the phone on the corresponding BCCH. The test cases currently executed are tagged with a blue arrow in the leftmost column. While the test is running, handover is disabled, as are all other phone control functions in TEMS Investigation. If you have listed several test case groups (see section 42.1), they will be executed one at a time, in the order they have been entered. Note that there is no requirement to keep test case groups apart in the GSM Channel Verification window, although it may of course be practical to do so. When the testing of a timeslot begins, it is marked with a question mark in a gray box. In the frequency hopping case, this timeslot is tested for all channels in the hopping sequence at once, so that multiple gray boxes appear. 42.6.2. Manual Verification If you have chosen manual verification, the application will now wait for you to either accept or reject this timeslot. To accept a timeslot, click Accept. An accepted timeslot will be marked with a green rectangle (with an “h” for hopping channels). If all timeslots in the test case are now accepted, the status of the test case will change to Passed. 372 Chapter 42. GSM Channel Verification To reject a timeslot, click Reject. A rejected timeslot will be marked with a red rectangle (with an “h” for hopping channels). The test case will ultimately be put in status Failed, though not until all timeslots have been either accepted or rejected. When you have made a decision, the application proceeds to make a new call. When a call is made in a previously accepted or rejected timeslot, the Accept and Reject buttons are disabled, and a new call is made within a few seconds. 42.6.3. Automatic Verification If you have chosen automatic verification, the application will itself accept the timeslot (if possible), marking it green ; otherwise it will try to make a new call the next time this timeslot is allocated. Automatic verification never rejects a timeslot, but keeps attempting calls indefinitely, within certain limits; see section 42.13. When a timeslot is allocated which has already been accepted or rejected, the call is aborted (not affecting the earlier result), and a new call is begun immediately. 42.6.4. 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. Manual verification has been chosen. Frequency hopping is used in this cell (as shown by the “h” symbols), so any timeslot tested will be verified for all three TCHs at once. At this point, the user has accepted the performance NT11-20502 373 TEMS Investigation 13.1 User’s Manual of timeslots 3 and 6 (green markers), while rejecting timeslot 7 (red markers). Timeslot 4 is currently being tested, which is indicated by question marks. 42.7. Stopping the Test In order to stop the test currently running: In the GSM Channel Verification window, click Stop. All test cases that are in status Testing will change to Stopped. To resume the test, just click Start again. The test will continue from the point where it was halted. All test cases that are not finished will be put in status Testing again. 42.8. Resetting a Test Case You can erase the results for a test case by resetting it. If the test is executing, it must be stopped first. The status value of the test case reverts to Not tested; when execution is resumed, the test case will be processed from scratch again. 42.9. Summary of Test Case Status Values A test case has one of the following status values: Status Value Meaning Not tested No work done yet on this test case, or: The test case has been reset. Testing Execution of this test case is ongoing. This is also indicated in the leftmost column by a blue arrow . Stopped Execution of this test case has been begun but the test is currently stopped. Passed All timeslots in the test case have been accepted. Timeslot(s) rejected At least one timeslot in the test case has been rejected. 374 Chapter 42. GSM Channel Verification Status Value Meaning Call lost BCCH lost Invalid TCH Timeout MS not connected Call setup failure These status values signify errors. See section 42.13. The error condition is also indicated in the leftmost column by the symbol . 42.10. Creating Test Reports At any stage of execution of a test, an HTML report can be generated summarizing the results obtained so far. (If the test is executing, it must be stopped first.) The report indicates • the verification mode: manual or automatic • the test phone number • the QoS parameter settings • the test result for each timeslot (where available) as well as the status of each test case at the time of creating the report. In case of call setup failure, the used MAIO and HSN is indicated for that test case. To generate a test report, click the Report button, and select an output location for the HTML file. Status values are as in the GSM Channel Verification window; see section 42.9. Timeslots are marked with one of the following: Timeslot Data Meaning OK Timeslot accepted. FAIL Timeslot rejected. TESTING Test of timeslot not yet completed. – Timeslot not included in test. NT11-20502 375 TEMS Investigation 13.1 User’s Manual 42.11. Saving and Opening Tests Channel verification tests can be saved to file at any stage of execution. (The test must be stopped first.) 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. To save the complete current contents of the GSM Channel Verification window, click Save. The test will be saved in a file with extension .tch. To open a previously saved *.tch file, click Open and select your file. 42.12. Notes on Performance It is possible to speed up the verification process by letting several phones share the work. This will, as a rule, considerably reduce the time taken to perform the test. You may assign different test cases to different phones, or assign identical test cases to several phones, or you may do both. If several phones are set to execute identical test cases, to begin with they will all work independently. However, as soon as a timeslot is accepted by one phone, it is marked green for all other identical test cases, and no phone will test it further. 42.13. Error Conditions In certain situations the application judges it impossible to complete the verification and therefore aborts the test. The test cases affected by the error executed are tagged with the symbol in the leftmost column. The status value of the test case indicates what has gone wrong: Status Value Call lost 376 Cause Two possible causes: • Two idle mode reports received while in dedicated mode (i.e. ongoing call has been lost). • One idle mode report received from wrong cell while in dedicated mode (i.e. lock on BCCH has broken down). Chapter 42. GSM Channel Verification Status Value BCCH lost Cause Two possible causes: • No channel report received from correct BCCH for 20 seconds after previous successful locking on this BCCH (i.e. lock on BCCH has broken down). • Three idle mode reports from wrong cell or two no service reports received while trying to lock on BCCH (i.e. lock on BCCH has failed). Invalid TCH Test case attempted 10 times in a row without the right TCH being allocated, and no timeslots marked green or red (typically occurs when the chosen TCH is in fact not used where assumed). Timeout Ten consecutive calls made where the call setup procedure could not be concluded successfully. MS not connected Phone not activated at start of measurement. NT11-20502 377 TEMS Investigation 13.1 User’s Manual Appendix A. Keyboard Shortcuts A.1. General Shortcuts Function Help Shortcut F1 Exit application Alt + F4 Previous worksheet F11 Next worksheet F12 Focus on next window in worksheet Ctrl + Tab Open TEMS Settings Manager Ctrl + M New workspace Ctrl + N Open workspace Ctrl + O Print workspace Ctrl + P Generate logfile report Ctrl + R Save workspace Ctrl + S A.2. Drive Testing Shortcuts Function Activate all Shortcut F2 Deactivate all Ctrl + F2 Swap logfiles F4 Insert filemark F5 378 Appendix A. Keyboard Shortcuts Function Start recording Shortcut F6 Pause recording Shift + F6 Resume recording Alt + F6 Stop recording Ctrl + F6 A.3. Replay Shortcuts Function Shortcut Open logfile Shift + F10 Play logfile F10 Step logfile Alt + F10 Stop logfile Ctrl + F10 Find in logfile A.4. Ctrl + F Shortcuts for Active Window Function Print window Shortcut Ctrl + P Status Window, Line Chart, Bar Chart Function Shortcut Show properties Shift + P Show setup wizard (status window only) Shift + W NT11-20502 379 TEMS Investigation 13.1 User’s Manual Map Window Function Shortcut Open Layer Control dialog Alt + L Open Theme Settings dialog Alt + T Activate zoom in Shift + Z Activate zoom out Alt + Shift + Z Go to first route marker1 Step to previous route marker Step to next route marker Go to last route marker 1 Home Left arrow Right arrow End 1. Some route sample must already be selected. Service Control Designer Window Function Shortcut Select all Ctrl + A Copy Ctrl + C New script Ctrl + N Open script Ctrl + O Save script Ctrl + S Paste Ctrl + V Cut Ctrl + X 380 Appendix B. File Types in TEMS Investigation Appendix B. File Types in TEMS Investigation These TEMS-specific file types are used by TEMS Investigation: Extension File Type .aex Setup file for ArcView format logfile export .bch Bar chart export file .cel Cell file .config Service Control configuration set .eth Setup file for Ethereal format logfile export .evt User-defined event .fmt Logfile exported in text format .lch Line chart export file .log Logfile .map Map window export file .mex Setup file for MapInfo format logfile export .mw Message window export file .pex Setup file for Planet format logfile export .rpt Setup file for logfile report .stm Status window export file .svt Audio indication for event .tdc TEMS Investigation workspace .tex Setup file for text format logfile export .tsc Service Control script NT11-20502 381 TEMS Investigation 13.1 User’s Manual 382 Index Index A Activate activity in scripts 193 activating external equipment in TEMS Investigation 35, 47 ACU 347 Andrew scanners CDMA scanning with 149 LTE scanning with 133 plugging in 36 Anritsu scanners 110 importing files logged by Anritsu ML8720 (i.e. in Anritsu format) 73 plugging in ML8720 model 36 plugging in ML8780A model 36 WCDMA pilot scanning with 117 Answer activity in scripts for video call 216 for voice call 218 AQM 340 for VoIP obtaining AQM data in TEMS Investigation 220, 353 presentation of AQM data 353 measurement setups in TEMS Investigation 340 with Audio Capturing Unit (ACU) 347 notes on PESQ scores obtained with individual phone models 351 obtaining AQM data in TEMS Investigation 347 prerequisites for collecting AQM data 348 presentation of AQM data 350 recording AQM data 348 with Call Generator/MRU 341 manually entering phone number 39 merging uplink AQM data into logfiles 85, 345 obtaining AQM data in TEMS Investigation 343 practical considerations regarding collection of AQM data 344 prerequisites for collecting AQM data 344 presentation of AQM data 345 recording AQM data 344 NT11-20502 383 TEMS Investigation 13.1 User’s Manual setup with Call Generator 341 setup with MRU 343 AQM modules associating with phones in TEMS Investigation 56 plugging in 37 ArcView 76, 83 arguments of information elements 13 AT activity in scripts 193 AT commands, issuing manually 54 Audio Capturing Unit 347 audio indications for events 245 activating 246 adding 245 deactivating 246 deleting 247 editing 246 muting 246 saving and loading 247 Audio Indications window 245, 246 audio quality measurements (AQM) 340 autodetect function for equipment not covered by license 41 restarting 50 B Band Lock activity in scripts 193 band lock, applying manually 54 limitations for Sony Ericsson phones 55 bar charts 280 adding charts 283 Additional Information pane 283 Chart pane 282 deleting a chart 283 editing general properties of individual chart panes 284 examples of presentations 296 exporting 298 interval on x-axis 294 labeling of x-axis 294 Legend pane 282 Multiple IE Components presentation mode 287 organization of window 281 parallel coordinates 290 Parallel Coordinates/Stacked Bar Chart presentation mode 290 384 Index presentation mode 285 presenting data from a different device 295 selecting additional information 295 selecting colors 285 selecting data to display 285 setting up contents 284 setting up general properties 283 Single IE presentation mode 286 stacked bar chart 290 X-axis pane 282 Y-axis pane 282 basics of TEMS Investigation 15 BCH scanning, presentation of (WCDMA) 124 C C/I measurements (GSM) 361 CAS Access Class (Sony Ericsson phone properties) 231 CAS Lock on PLMN (Sony Ericsson phone properties) 231 CAS Speech Codec (Sony Ericsson phone properties) 231 CDMA scanning 149 cell data loading from Mentum CellPlanner 30 using in presentations 30 cell files creating in CEL format 30 creating in XML format 29 in CSV format 29 loading 30 cell reselection behavior (Sony Ericsson phones) 233 channel verification (GSM) 367 color attribute (of information element) 250 editing 26 Configuration menu 24 contents of User’s Manual 11 Control menu 24 control structures in scripts 179 CPICH Best UARFCN Data window (WCDMA) 119 CPICH Data window (WCDMA) 119 CPICH Scan bar charts (WCDMA) 119 CPICH Scan line charts (WCDMA) 120 NT11-20502 385 TEMS Investigation 13.1 User’s Manual D data service testing 11, 12 conducting manually 59 presentation of 60, 193 video streaming 267 Deactivate activity in scripts 193 deactivating external equipment 48 definitions of TEMS Investigation concepts 12 device properties 228 Dial activity in scripts for voice call 218 drive testing mode 18 DRT scanners 160 detection of 40 LTE scanning with 133 plugging in 36 E E-mail Receive activity in scripts 212 E-mail Send activity in scripts 211 enhanced power scanning (LTE) 142 equipment cases 12 plugging in 37 equipment properties 228 Ericsson Fixed Wireless Terminals plugging in 36 Ethereal 76, 83 Event Counter windows 261 changing contents and properties of 262 copying contents from 261 managing tabs in 261 resetting 261 Event Definition window 240 events 13, 240, 248 audio indications for 245 deleting user-defined 243 editing user-defined 243 example of user-defined event 243 predefined and user-defined 240 presentation of 240 user-defined, setting up 240 external equipment 11 activating in TEMS Investigation 35, 47 386 Index connectable devices 3 deactivating in TEMS Investigation 48 overview of user interface components dealing with 32 plugging in 35 user-assisted detection of 42, 45 F FAQ (on TEMS website) 12 fast-forwarding logfiles 70 File menu 23 File Transfer tool 73 file types in TEMS Investigation 381 Filemark activity in scripts 193 filemarks inserting in logfiles 65 quick filemarks 67 finding items in logfiles 71 fix source for GPS 270 FTP Download activity in scripts 202 FTP Upload activity in scripts 203 fundamentals of TEMS Investigation 2 G General window 30, 124, 140, 147, 155, 330 GeoSet 300 constructing from map files 300 GeoSet Manager 328 layer control 329 map projections 329 Getting Started Manual, contents of 11 GPS fix source 270 GPS units in scanners 104 plugging in 37 properties of 239 selecting preferred GPS 49 GPS window 270 properties of 270 GSM Barred Cells (Sony Ericsson phone properties) 233 GSM Cell Selection (Sony Ericsson phone properties) 233 GSM channel verification 367 adding test cases 368 automatic vs. manual 369 NT11-20502 387 TEMS Investigation 13.1 User’s Manual creating test reports 375 editing test cases 369 error conditions 376 notes on performance 376 opening tests 376 removing test cases 369 resetting test cases 374 running the test 372 saving tests 376 status of test cases 374 stopping the test 374 test 368 test case 367 test case group 368 GSM EDGE Capability (Sony Ericsson phone properties) 234 GSM Handover (Sony Ericsson phone properties) 234 GSM scanning 105 GSM Tx Power (Sony Ericsson phone properties) 235 H handover behavior in GSM (Sony Ericsson phones) 234 Hang Up activity in scripts for video call 216 for voice call 218 Help menu 24 HTC Imagio detection of 40 HTC Touch Pro2 detection of 40 HTTP Get activity in scripts 205 I If--Else activity in scripts 194 IMSI 39 in-building positioning 68 indoor positioning 68 information elements 13, 248 installing TEMS Investigation 15 IPv6 190 K Key Performance Indicators 178 keyboard shortcuts 24, 378 388 Index KPIs (Key Performance Indicators) 178, 331 accessibility 332 integrity 332 obtaining with TEMS products 332 purpose of 331 retainability 332 L labels 300 Layer 3 Messages (Sony Ericsson phone properties) 235 layers in Map window 300, 324 licensing in TEMS Investigation 2 line charts 272 adding charts 275 Additional Information pane 274 changing contents and properties 275 Chart pane 273 deleting a chart 279 editing contents 275 editing general properties 275 exporting 279 Legend pane 274 organization of window 272 presenting data from a different device 279 selecting additional information 279 selecting events 278 selecting information elements 276 time scale 274 Y-axis pane 274 loading logfiles from other sources 72 Logfile menu 23 logfile recording 64 adding user information 67 clearing history buffer 68 default folder 67 inserting filemarks 65 other options 66 Properties dialog 66 quick logging 67 swapping logfiles 66 logfile reports 95 contents 101 event statistics 98 NT11-20502 389 TEMS Investigation 13.1 User’s Manual external devices to include 98 saving and loading setups 101 scanned channels 98 thresholding of information elements 96 user details 100 logfiles exporting 76 ArcView settings 83 Ethereal settings 83 executing export orders 84 MapInfo settings 81 MDM settings 83 Planet settings 83 saving and loading setups 84 text file settings 79 fast-forwarding 70 loading from other sources 72 recording 64 replaying 70 rewinding 70 searching 71 stepping 70 stopping 70 transferring via FTP 73 LTE scanning 133 M managing external equipment (general) 32 manual operation of external equipment 53 Manual UE Configuration utility 42 Map window 299 information on theme markers 321 layers 300, 324 adding presentation layers 324 control of 325 map layer 300 presentation layers 300, 304 Legend tab 324 previous view, returning to 326 right-hand pane 321 scale bar 326 setting projection for 327 statistics 323 390 Index toolbar 327 viewing entire layer 327 MapInfo 76, 81 maps 299 centering 328 constructing a GeoSet from map files 300 GeoSet 300 labels 300 notes on route plotting and updating 307 panning 328 positioning maps in bitmap or TIF format 302 themes 300, 303 zooming 327 Marconi Planet 76, 83 MDM 83 export in MDM format 76 loading MDM files in TEMS Investigation 73 Mentum CellPlanner 30 menu bar 17, 23 merging logfiles with uplink data 87 merging uplink AQM data into logfiles 85 message windows 263 catch-up function 265 changing contents and properties of 263 freezing 266 plain-text message decoding 264 presentation of discarded messages 265 synchronization of 265 messages 13, 248 MMS Receive activity in scripts 213 MMS Send activity in scripts 212 mode reports 13 Mode Reports window adjusting updating frequency for Qualcomm reports 266 Motorola UEs reading EFEM logfiles from 73 MTQI 360 MTR data 364 MTR files 73, 364 N narrowband interference scanning (CDMA) 157 NT11-20502 391 TEMS Investigation 13.1 User’s Manual Navigator 16 Equipment tab basics 37 device context menu 38 refreshing 50 re-pairing phones with AQM modules 50 saving equipment configuration 52 Info Element tab 26 Menu tab 25 Worksheets tab 28 Navigator pane 25 NDIS data connection 48 Network Bandwidth activity in scripts 209 Network Connect activity (in scripts) prerequisites for various devices 198 Network Connect activity in scripts 197 Network Disconnect activity in scripts 200 network scanning (WCDMA scanning mode) 130 presentation 132 setting up 131 Network Search window (WCDMA) 132 Nokia phones, properties of channel lock control 238 GSM cell barring control 238 RAT lock vs. technology-specific control functions 59 sector lock control 238 Nonvolatile Item Read/Write (Qualcomm device control function) 55 O online help 24 P package options for TEMS Investigation 2 Parallel activity in scripts 196 parallel coordinates presentation 290 PCTel scanners CDMA scanning with 149 detection of SeeGull EX 40 detection of SeeGull MX 40 GSM scanning with 105 LTE scanning with 133 plugging in 36 WCDMA pilot scanning with 114 392 Index WCDMA scanning with 110 PESQ 340 PESQ devices See AQM modules PESQ Measurement activity in scripts 218 phone number of user terminal 39 phones 14 plugging in 36 properties of 230 pilot scanning (CDMA) 150 pilot scanning (TD-SCDMA) 146 pilot scanning (WCDMA) 112 Ping activity in scripts 207 pinpointing 68 presentation on map 320 tips 69 plotting density in Map window 307 preamble scanning (WiMAX) 161 preferred GPS unit 49 presentation attributes of information elements 26 presentation layers 304 Presentation menu 24 presentation of data 248 presentation windows export/import of 250 synchronization 249 types of 248 updating 249 PS Attach activity in scripts 200 PS Detach activity in scripts 201 Q Qualcomm chipset based devices Nonvolatile Item Read/Write control function (UMTS) 55 properties of 239 Qualcomm devices with LTE capability 45 quick filemarks 67 quick guide to user interface 15 quick logging 67 R Radio Access Technology lock (manual) 57 Radio Access Technology Lock activity in scripts 194 NT11-20502 393 TEMS Investigation 13.1 User’s Manual RAT lock 194 applying manually 57 recommended skills 15 recording logfiles 64 Release Note 12 replay mode 18 replaying a logfile 70 progress indication on status bar 72 speed 71 viewing logfile information 72 Report Generator 95 reports on logfiles 95 rewinding logfiles 70 reworked user interface, notes on 33 Rohde & Schwarz scanners 110 detection of 40 LTE scanning with 133 plugging in 36 WCDMA pilot scanning with 116 RSSI scanning CDMA 156 GSM 106 LTE 140 TD-SCDMA 148 WCDMA 127 WiMAX 164 S Samsung Galaxy S 4G properties of 230 Samsung LTE modems, properties of 239 scanners 14 plugging in 36 scanning general 102 notes on scanning methods 104 performing a scan 60, 102 presenting scan data 103 recording scan data 103 replaying scan data 103 setting up a scan 102 technical data on scanning devices 103 394 Index scanning, CDMA 149 "PN Scan" bar charts 154 general settings 150 methods 149 Narrowband Interference Scan Bar Chart 157 narrowband interference scanning 157 of pilots 150 RSSI Scan Bar Chart 156 RSSI scanning 156 sorting of PNs in presentations 155 spectrum analysis 158 Strongest Scanned PN Bar Chart 154 scanning, GSM 105 BSIC decoding in RSSI Scanning mode 106, 107 C/I measurements 107 device capabilities 105, 133 methods 105, 133 RSSI scanning 106 spectrum analysis 109 System Information Decoding 108 scanning, LTE 133 enhanced power scanning 142 LTE signal scanning 134 presentation 140, 141, 142, 144 RSSI scanning 140 sorting of cells in presentations 140 spectrum scanning 141 scanning, TD-SCDMA 145 general settings 145 methods 145 of pilots 146 presentation 147, 148 RSSI scanning 148 sorting of cells in presentations 147 scanning, WCDMA 110 CPICH Best UARFCN Data window 119 CPICH Data status window 119 CPICH pilot pollution 121 CPICH Scan bar charts 119 CPICH Scan line charts 120 CPICH scanning 112 device capabilities 110 NT11-20502 395 TEMS Investigation 13.1 User’s Manual Finger Info status windows 124 methods 110 network scanning 130 number of active set members 121 of P-SCH and S-SCH channels 123 of synchronization channels (SCHs) 112 of timeslots on SCH 125 presenting scrambling codes from multiple UARFCNs together 125 RSSI Scan Bar Chart 128 RSSI scanning 127 SCH Timeslot Scan Bar Chart 126 sorting of scrambling codes in presentations 124 spectrum analysis 129 Spectrum Analysis bar charts 130 Synch Channel Data status window 123 scanning, WiMAX 160 general settings 160 methods 160 preamble scanning 161 presentation 164 RSSI scanning 164 spectrum analysis 164 SCH scanning 112 SCH Timeslot Scan Bar Chart (WCDMA) 126 scripts Activate activity 193 activity filter 226 Answer activity (for video call) 216 Answer activity (for voice call) 218 AT activity 193 Band Lock activity 193 basics of creating 171 capabilities of devices 168 comparison with old command sequences 167 context menu in workflow pane 227 Control activities 193 Control Flow activities 194 control structures 179 data services, setting up 175 Deactivate activity 193 Dial activity (for voice call) 218 E-mail Receive activity 212 396 Index E-mail Send activity 211 failure handling properties 222 Filemark activity 193 FTP Download activity 202 FTP Upload activity 203 general activity properties 221 Hang Up activity (for video call) 216 Hang Up activity (for voice call) 218 HTTP Get activity 205 If--Else activity 194 if--else constructs 180 importing and exporting 223 introduction to 166 IP activities 197 Messaging activities 211 MMS Receive activity 213 MMS Send activity 212 multiple devices, controlling 183 Network Bandwidth activity 209 Network Connect activity 197 network connection, setting up 174 Network Disconnect activity 200 Parallel activity 196 parallel construct 183 PESQ Measurement activity 218 Ping activity 207 PS attach 177 PS Attach activity 200 PS detach 177 PS Detach activity 201 Radio Access Technology Lock activity 194 running 189 saving and loading 225 saving workflow as image 226 Sequence activity 196 sequences 179 SIP Register activity 201 SIP Unregister activity 201 SMS Receive activity 214 SMS Send activity 214 snippets 178 Start IP Sniffing activity 201 NT11-20502 397 TEMS Investigation 13.1 User’s Manual Start Logfile Recording activity 194 Stop IP Sniffing activity 202 Stop Logfile Recording activity 194 Streaming activity 216 supported services by cellular technology 169 suppressing parts of 191 termination properties 222 tips and tricks for creating 188 UDP activity 207 UE control 188 validating 189 Video activities 215 Video Dial activity 215 Voice activities 218 voice, creating script for 171 VoIP Answer activity 220 VoIP Dial activity 219 VoIP Hang Up activity 220 VoIP Voice Quality activity 220 Wait activity 187, 196 WAP Get activity 205 WAP Streaming activity 217 While activity 195 while loops 181 workflow control structures 179 zooming the workflow pane 227 searching a logfile 71 Sequence activity in scripts 196 Service Control 166 See also scripts Service Control Designer 169 Service Control Monitor 189, 190 SIP Register activity in scripts 201 SIP Unregister activity in scripts 201 size attribute (of information element) editing 28 skills recommended for TEMS Investigation users 15 SMS Receive activity in scripts 214 SMS Send activity in scripts 214 snippets in scripts 178 Sony Ericsson phones GSM scanning with 105 398 Index WCDMA pilot scanning with 112 Sony Ericsson phones, properties of 230 CAS Access Class 231 CAS Lock on PLMN 231 CAS Speech Codec 231 EDGE Capability 234 Extended Reports 230 GSM Adjacent Scan 232 GSM Barred Cells 233 GSM Cell Selection 233 GSM Handover 234 GSM Tx Power 235 Layer 3 Messages 235 messages and mode reports 230 RAT lock vs. technology-specific control functions 58 WCDMA Barred Cells 235 WCDMA BLER Target 236 WCDMA Cell Selection 236 WCDMA RRC Radio Capability 237 sounds for events 245 spectrum scanning CDMA 158 LTE 141 WCDMA 129 WiMAX 164 speech codecs (of Sony Ericsson phones) 231 Speech Quality Index (SQI) 334 SQI 334 SQI-MOS 334 alignment with PESQ 337 comparison with RxQual (GSM version) 339 input to algorithm 335 output 336 SRUs 110 GSM scanning with 105 plugging in 36 WCDMA pilot scanning with 112 stacked bar chart 290 Start IP Sniffing activity in scripts 201 Start Logfile Recording activity in scripts 194 starting TEMS Investigation 15, 37 statistics presentation in Map window 323 NT11-20502 399 TEMS Investigation 13.1 User’s Manual status bar 17, 22 Status Control Monitor 61 status windows 252 changing font size in 258 changing properties of 256 repeating columns in multiple groups 258 setting up contents of 252 stepping logfiles (during replay) 70 Stop IP Sniffing activity in scripts 202 Stop Logfile Recording activity in scripts 194 stopping logfile replay 70 Streaming activity in scripts 216 support contact information 12 swapping logfiles 66 symbol attribute (of information element) editing 28 Synch Channel Data window (WCDMA) 123 T TD-SCDMA scanning 145 TEMS Bulletins 12 themes 300, 303 Cell ARFCN theme 318 Cell Color theme 316 Cell Line theme 313 Cell theme 310 cell themes 304 constructing cell themes 309 event themes 308 IE themes 305 deleting 321 editing 320 event themes 303 information element (IE) themes 303 Pinpoint theme 304, 320 reordering 321 visibility of 320 toolbars 16, 21 File and View toolbar 22 Record toolbar 21 Replay toolbar 21 Report toolbar 22 400 Index U UDP activity in scripts 207 uplink data 364 accuracy of alignment with logfile 91 limitations of merging algorithm 88 merging algorithm 87 merging with logfiles 87, 88 presentation of 365 usefulness of 365 user interface 18 quick guide to 15 user modes 18 user-assisted detection of external devices 42 user-defined events 240 V video calls, dialing manually 59 Video Dial activity in scripts 215 Video Monitor 268 properties of 268 video streaming 267, 356 evaluating performance of 269 how to test 267 troubleshooting 269 WAP-based 217 video telephony 354 View menu 23 voice calls, dialing manually 59 VoIP 352 VoIP Answer activity in scripts 220 VoIP Dial activity in scripts 219 VoIP Hang Up activity in scripts 220 VoIP Voice Quality activity in scripts 220 VSQI 269, 356 VTQI 354 W Wait activity in scripts 196 WAP Get activity in scripts 205 WAP Streaming activity in scripts 217 WAP-based video streaming 217 WCDMA Barred Cells (Sony Ericsson phone properties) 235 WCDMA BLER Target (Sony Ericsson phone properties) 236 NT11-20502 401 TEMS Investigation 13.1 User’s Manual WCDMA Cell Selection (Sony Ericsson phone properties) 236 WCDMA RRC Radio Capability (Sony Ericsson phone properties) 237 WCDMA scanning 110 what’s in this manual 11 what’s new in this TEMS Investigation version 3 While activity in scripts 195 Wi-Fi access points presentation on map 309 WiMAX cells, presenting on map 309 WiMAX scanning 160 Window menu 24 Windows 7 190 Windows Vista 190 Worksheet menu 24 worksheets 16, 20 workspaces 16, 19 opening from Command Prompt 20 predefined 20 402 AScOM NETWORK TESTING LEADS THE WORLD IN PROVIDING BEST-IN-cLASS SOLUTIONS TO MEASURE, ANALYZE, AND OPTIMIZE MOBILE NETWORKS. The TEMS™ Portfolio offers a complete set of trusted solutions for drive testing, benchmarking, monitoring, and analyzing network performance. These state-of-the-art offerings facilitate the deployment, optimization, and maintenance of mobile networks. We are the industry leader, and our products are supplied to the world’s top mobile operators, equipment vendors, and professional service providers. Ascom reserves the right to change speciications without notice. Ascom acknowledges all registered trademarks appearing herein. Ascom Network Testing Inc. 1943 Isaac Newton Square Reston, Virginia 20190 | USA www.ascom.com/tems 06.2010 © Ascom 2010. All rights reserved. TEMS is a trademark of Ascom . All other trademarks are the property of their respective holders. www.ascom.com/tems