THURAYA. Packet Data User Terminals. Orion/Voyager. Radio Silence Test Procedures and Report

Transcription

1 PTF 9B12C THURAYA Packet Data User Terminals Orion/Voyager Radio Silence Test Procedures and Report Revision B November 2015 These commodities, technology or software were exported from the United States in accordance with the Export Administration Regulations. Diversion contrary to U.S. law is prohibited. In addition, Subject to the provisions of the THURAYA CONTRACT NO. 010/2012/HNS and the Written Assurance executed in connection therewith dated 22 May 2012 i

2 PROPRIETARY NOTICE All rights reserved. This publication and its contents are proprietary to Hughes Network Systems, LLC. No part of this publication may be reproduced in any form or by any means without the written permission of Hughes Network Systems, LLC, Exploration Lane, Germantown, Maryland Hughes, HughesNet, IPoS, SPACEWAY, AIReach, Broadband Unbound, and Connect to the future are trademarks of Hughes Network Systems, LLC. All other trademarks are the property of their respective owners. Copyright 2015 Hughes Network Systems, LLC

3 Table of Contents 1.0 INTRODUCTION PURPOSE SCOPE THURAYA MOBILITY PHYSICAL DESCRIPTION FIELD TESTS: RADIO SILENCE VERIFICATION FIELD RESULTS TEST SETUP TEST RESULTS SUMMARY APPENDIX A: UT INITIALIZATION APPENDIX B: LEDS OPERATION ORION/VOYAGER APPENDIX C: COLLECTING CONFIGURATION INFORMATION APPENDIX D: POLYGON DEFINITION RAD_SIL_MAP.CSV FILE APPENDIX E: COLLECTING SYSLOG APPENDIX F: UT SOFTWARE USING UPGRADER TOOL APPENDIX G: UT SOFTWARE USING.BIN FILE APPENDIX H: PROBLEM REPORTING CHECKLIST... 25

4 FIGURES Figure 1 Polygon Definition File (rad_sil_map.csv) & KML (Google Earth) File for 10 Polygons Defined... 6 Figure 2 Ten Polygons Defined in UAE... 7 Figure 3 Beam Boundaries (152, 163)... 7 Figure 4 Outbound Route... 8 Figure 5 Inbound Route... 8 Figure 6 Thuraya Maritime (Orion) or Land-Mobile (Voyager) User Terminal... 9 Figure 7 Thuraya IP Voyager used for testing Figure 8 Outbound Test Results Map Figure 9 Inbound Test Results Map Figure 10 Denmark Results Map using Simulated GPS Position within the Beam TABLES No table of figures entries found.

5 Revision History Revision Date Author Scope A.01 June 12, 2015 T. Joulapour Initial version A.02 June 17, 2015 G. Avis Updated based on review comments T. Joulapour A.03 June 19, 2015 T. Joulapour Updated Appendix F A.03 June 23, 2015 T. Joulapour Added outbound & inbound routes for drive testing A.05 June 25, 2015 T. Joulapour Updated Section 2 & Appendix E A.06 July 9, 2015 T. Joulapour Updated test results under Sections 2 & 3 M. Read A July 10, 2015 T. Joulapour CM Release B November 18, 2015 T. Joulapour Updated section 2.0 Open Issues Issue Issue Disposition No. 1 TBDs Will be identified and updated in the next revision.

6 1.0 INTRODUCTION 1.1 PURPOSE This document contains field test procedures & test results for verification of Radio Silence feature on Thuraya Orion/Voyager terminals. These field test procedures verified that when Radio Silence mode is active; satellite access is temporarily disabled. 1.2 SCOPE This is a stand-alone document that provides a detailed test definition for verification of Radio Silence mode. Guidelines for Tests: UTs located in UAE under THURAYA satellite (D2), to ensure the robustness of the release Polygons defined in CSV format (rad_sil_map.csv) with checksum protection "Wed Jun 17 10:29: " "P:Polygon 1" , , , , , , , "P:Polygon 2" , "P:Polygon 10" , , , , , , Cksum x 10000, rad_sil_map.csv Figure 1 Polygon Definition File (rad_sil_map.csv) & KML (Google Earth) File for 10 Polygons Defined 6

7 Figure 2 Ten Polygons Defined in UAE Beam 152 Beam 163 Figure 3 Beam Boundaries (152, 163) 7

8 Figure 4 Outbound Route Figure 5 Inbound Route 8

9 1.3 THURAYA MOBILITY PHYSICAL DESCRIPTION Thuraya Terminals Radio Silence Test Procedures & Report The Thuraya Mobility User Terminal is a User Terminal that supports land-mobile or maritime operation over the Thuraya satellite coverage area. It consists of two separate modules: External Antenna (Above Deck Unit - ADU) and Modem Unit (Below Deck Unit - BDU) connected by an RF coaxial cable. The ADU features a low profile antenna/stabilizer, GPS receiver, and front end RFU. The BDU contains a Hughes core module and interface board with integrated, isolated wide range DC/DC power supply housed in an extruded chassis (modem). Figure 1 shows the User Terminal for Land-mobile and Maritime use with the different antenna configurations. Figure 6 Thuraya Maritime (Orion) or Land-Mobile (Voyager) User Terminal 9

10 2.0 FIELD TESTS: RADIO SILENCE VERIFICATION Please follow test steps in the table below and Record all anomalies and provide SYSLOG files (streaming logs as well as periodic 2MB log dumps) as you go thru the following steps (Appendix E) Fill out Field Logging Report (Appendix H) Provide a quick summary which Hughes can review and react to during your testing in the field Provide a comprehensive report at the end test campaign Take test setup pictures No. Step Procedure Location/ Appendix /Fail 1. Upgrade a Voyager UT setup with the build supporting Radio F or G Silence mode (CM build: ). 2. Check the properties page to confirm the release version is loaded. 3. FTP Polygon definition file rad_sil_map.csv to UT D (Figures 1, 2) 4. Move UT to an area with satellite coverage and connect a laptop via Ethernet. 5. Power up, connect to the network (in Standard mode by A default). 6. Verify LEDs operation. B From wmmi, enable Radio Silence under Advanced Settings 7. page. Comments Dump the configuration file. Verify Radio Silence Map Version exists and configuration is displayed as ENABLE. Open a DOS window from TE (laptop) and start a ping session (ping t ). Drive towards Abu Dhabi and AL Marfa from Dubai using E66, E20 and E11 (Figure 4 Outbound Route) Make a note of the local time and location when any combination of these events occur (all should occur at roughly the same time, note which occur and which do not): - Pings timeout (no IP connectivity). - Network LED blinks (front panel of BDU) - wmmi Home page reports Network Status as Locationbased Silence C 10

11 No. Step Procedure Location/ Appendix /Fail Comments - Modem Status screen: Make a note of the local time and location when any combination of these events occur (note which occur and which do not): - Pings start working (IP connectivity). - Network LED on solid (front panel of BDU) - wmmi Home page reports Network Status as Connected Continue to note transitions between normal IP connectivity and loss of IP connectivity, along with the user interface status when those transitions occur. Continue the drive test until you reach Al Marfa. Close and save all log files. When ready to return to Dubai on E11 (Sheikh Zayed Rd) (Figure 5 Inbound Route), from the wmmi, set receive (forward channel) rate and transmit (return channel) connection rate to 128kbps. From step 10 above repeat the procedure to note the time of all event transitions. When back in Dubai, save all log files and finalize the report for Hughes. See Section 3 11

12 3.0 FIELD RESULTS 3.1 TEST SETUP Test was conducted by Xtra-Link in UAE on July 3 rd A Thuraya IP Voyager terminal was setup and driven at average speed of 100 km/hr going thru outbound (Figure 4) and inbound (Figure 5) routes. Figure 7 Thuraya IP Voyager used for testing Additional tests were also conducted in Denmark using simulated GPS position within the beam (Figure 10). 3.2 TEST RESULTS SUMMARY The following maps are results from Xtra-Link's full test route as defined under Section 2: Notes: Each map point with a dot had at least one downlink packet received. Click on the marker to see how many packets. Green dot represents UT is not in radio silence mode; passing traffic successfully Red dot represents UT is in radio silence mode; satellite access is temporarily disabled Yellow dot represents UT entering radio silence mode; a transition period in which point where GPS fix was received that caused the state change. Blue dot represents UT is exiting radio silence mode; a transition period in which point where GPS fix was received that caused the state change. 12

13 Figure 8 Outbound Test Results Map Figure 9 Inbound Test Results Map 13

14 Figure 10 Denmark Results Map using Simulated GPS Position within the Beam 14

15 APPENDIX A: UT INITIALIZATION Objective This test will verify: UT will initialize automatically after the user inserts the SIM and powers up. For Mobility, after powering on, the UT automatically performs a cable calibration routine to compensate for RF attenuation due to losses in the coaxial cable that connects the BDU to the ADU. UT, upon power-on with a valid SIM inserted, performs automatic antenna pointing. Setup 1. Thuraya terminal (Orion/Voyager) 2. Thuraya GPRS SIM 3. TE with web browser 4. SIM PIN is disabled 5. Power up profile set to Standard by default Procedure 1. Connect the TE to the UT via Ethernet cable. 2. Insert SIM. 3. Power up TE and UT. Computer goes through normal boot up sequence. Thuraya Home Page will be displayed. 4. Bring up the Thuraya web page. Thuraya web page is displayed. 5. Verify that the PDP context activation is successful. Network Status is Connected. Thuraya Mobility is connected to the network with a background class PDP Context (Standard). Criteria The UT starts its initialization routine, and automatically registering into the network. 15

16 APPENDIX B: LEDS OPERATION ORION/VOYAGER Objective This test verifies the LEDs used for UT operation. Procedure 1. Verify the Power LED turns green when UT Modem Unit is powered on. Off when UT Modem Unit is powered off. (This LED is integrated in the On/Off switch.) 2. After power on, observe the Connection Status LED. Verify this LED is off until the terminal attaches to the Thuraya network. After attachment, verify this LED is Green. 3. Ensure that while the terminal does not have a GPS fix, the GPS LED is off. 4. Place ADU outside or expose ADU to a roof antenna live GPS feed to get a GPS position. Observe the GPS Status LED. Verify LED is solid green when a valid GPS fix is acquired. 5. Take the SIM card out and power on the UT. Verify Fault LED turns on red. 6. Note: Red LED shall turn on if a hardware fault is detected by the UT (e.g.: communication failure to ADU, no SIM card detected). The LED shall be off otherwise. Criteria The operations of LEDs are verified. 16

17 APPENDIX C: COLLECTING CONFIGURATION INFORMATION Objective This test will verify the means to consolidate and summarize and extract critical status and configuration elements for ease of field support. Note: This functionality is currently supported only on IE browser. Procedure 1 Click on Properties screen. 2 Click on the Extract terminal Log button and verify that the Download file here link appears. 3 Verify download by right-click and save-as option. Check the content of the downloaded terminal summary text file. Criteria The terminal summary (sample text file) will include: 17

18 APPENDIX D: POLYGON DEFINITION RAD_SIL_MAP.CSV FILE Objective Verify that Polygon definition rad_sil_map.csv file can be loaded on the UT. Setup 1. PCs/Laptops running with Windows 7 or higher and loaded with rad_sil_map.csv file 2. Thuraya terminal connected to PC via Ethernet cable Procedure 1. Power on UT. 2. Open DOS window and access the directory where rad_sil_map.csv file is stored in. rad_sil_map.csv 3. FTP into and login. Type the following commands: FTP> cd /tffs0 FTP> bi FTP> ha FTP> put rad_sil_map.csv 4. Cycle power on the UT. 5. Check the properties page to confirm the release version is loaded. Criteria The Polygon definition rad_sil_map.csv file has been loaded successfully. 18

19 APPENDIX E: COLLECTING SYSLOG The following instructions can be done during the test to access debug screen in order to set the log levels on the fly and collecting SYSLOG: Notes: 1. Note that these log levels are only in place until the next UT reset or power cycle. 2. Collect 2MB SYSLOG files periodically during test frequently to avoid loss of log. 3. Stream SYSLOG to multiple log files during test to avoid large file sizes. 4. The three main browsers use slightly different text in the right-click menu for saving the content provided through a link: a. Firefox: "Save Link As " b. Chrome: "Save link as " c. IE: "Save Target As " Collect 2MB SYSLOG Step Instruction Description 1 On the wmmi properties page, click on the hidden link under Thuraya at the bottom of the web page to open up the support tools page 2 On support tools page, press on Enable Logging button to set the correct log levels 3 The 2MB system log can be extracted to a file on your connected PC by selecting the Extract System Log button, right click and select Save Target As (or equivalent for your browser) 19

20 4 OR, FTP into and login (see PTF 9b9a, section 1.5 for login access). Type the following commands: FTP> cd /ram0 FTP> get syslog.log Thuraya Terminals Radio Silence Test Procedures & Report Stream SYSLOG to File Step Instruction Description 1 A user-friendly tool called UTLog has been developed to collect logs. It does the same thing as the Telnet method in DOS window, but with an easier to use GUI front end. Install UTLog tool on a PC connected to the UT 2 Create a directory called logs under C drive to include three subdirectories, syslog, telnet and wireshark This tool will allow you to capture telnet session and syslog UTlog.zip 3 Simply run UTlog.exe from a PC connected to the UT and select a session telnet or syslog to connect 4 By selecting syslog, time and LogFile boxes, all streaming syslog sessions will be stored under: C:\logs\syslog Note: Log file name can be updated automatically by pressing Disconnect, and then the syslog button, then pressing Start again. This action will also help to analyze the logs more efficiently when log files are smaller in size. 20

21 APPENDIX F: UT SOFTWARE USING UPGRADER TOOL Objective Verify that Thuraya software upgrader is a software utility tool used to upgrade UT to the latest Thuraya software releases. The upgrader tool can be loaded on a PC with a standard Windows operating system (Win 7 & up). Setup 1. PCs/Laptops running with Windows 7 or higher and loaded with Thuraya software upgrader 2. Thuraya terminal connected to PC via Ethernet cable Procedure 1. Power on UT. 2. Bring up the upgrader on the PC. Verify Thuraya Upgrader is displayed. 3. Confirm the new software version to be installed on the UT. Select Software, then click on Upgrade and then Yes buttons to proceed with the upgrade. Note: This process will normally take 1-2 minutes. 21

22 The upgrader will show the status 4. At the end of the upgrade process, the Thuraya will automatically turn off and on. While it is off, the upgrader will show a red button. When the Thuraya has turned on, the upgrader will show the version of software both windows is the same. 22

23 5. Revert back to an earlier version of software. Click on the Restore button, select from the list, and click on the OK button. The upgrader will not display the earlier version of software while the upgrade is in progress, it will display it after it has power cycled the Thuraya terminal. 6. Check the properties page to confirm the release version is loaded. Criteria The Thuraya software upgrader tool is verified successfully. 23

24 APPENDIX G: UT SOFTWARE USING.BIN FILE Objective Verify that Thuraya software.bin file can be used to upgrade UT to the latest Thuraya software releases if the upgrader tool is not available or provided by Hughes. Setup 1. PCs/Laptops running with Windows 7 or higher and loaded with Thuraya software.bin file ( thip2.bin for IP+ or thip2m.bin for Orion/Voyager) 2. Thuraya terminal connected to PC via Ethernet cable Procedure 1. Power on UT. 2. Telnet into and login (see PTF 9b9a, section 1.5 for login access). Type in ll at the prompt. Verify if there is an image.txt file listed. 3. If there is such a file, type in at the prompt remove image.txt and then hit the return key. 4. Cycle power on the UT. 5. Open DOS window and access the directory where.bin file is stored in. 6. FTP into and login. Type the following commands (note: thip2.bin is for IP+): FTP> cd /tffs0/bin FTP> bi FTP> ha FTP> put thip2.bin 7. Cycle power on the UT. 8. Check the properties page to confirm the release version is loaded. Criteria The Thuraya software.bin file has been loaded successfully. 24

25 APPENDIX H: PROBLEM REPORTING CHECKLIST THURAYA User Terminal PROBLEM REPORTING CHECKLIST When completed to be sent to Hughes via CRM portal or ed to Reference PTF 9B9A Thuraya Packet Data User Terminals Field Logging & Problem Reporting Guide PRODUCT DESCRIPTION Product Thuraya IP+ Thuraya Orion Thuraya Voyager Antenna Type Internal External ive External Active Software Version Interface Type Ethernet USB WiFi PC/Laptop OS Other OPERATIONAL INFORMATION Satellite D2 D3 Connection Profile Beam ID Operation Type ARFCN Other PROBLEM DESCRIPTION Frequency Once Intermittent Reproducible No. of Units Tested (observing this problem) Component Report problem as detailed as possible by specifying sequence of test or events taken: Standard Streaming Transmit Rate Receive Rate FTP Ping Browsing Streaming Software Hardware Feature Specify Logs Checklists SYSLOG: Terminal Summary Log: (under Web MMI Properties Screen Extract Terminal Summary Log) Wireshark Log: Modem & PHY Stats: Terminal Tera Term Log: Reported By Date : 25