Reengineering Telemetry: integrated Network Enhanced Telemetry

Size: px

Start display at page:

Download "Reengineering Telemetry: integrated Network Enhanced Telemetry"

Paul Briggs
6 years ago
Views:

1 Reengineering Telemetry: integrated Network Enhanced Telemetry PRESENTER: Ray Faulstich CSC Range and Engineering Services Bill Cookson inet Project Director

2 Briefing Outline Traditional Telemetry Background Challenges inet Study Systems Engineering Capabilities Deployment

3 50 Years of Service Has served us well but it is starting to show it s age: PCM Downlink Dropouts are a fundamental flaw of the architecture PCM Downlink Rigid structure lacks flexibility Lack of a two way link limits options Single test article focused PCM Downlink Network Data Reduction Test Engrs Flight Simulators

4 A Great Ride In 1960 IRIG 106 Chapter 4 was published 3 pages in length Ushered in the era of PCM Telemetry 48 + years later Chapter 4 is still being used Virtually every major US weapons system in use today was tested using Chapter 4 However, in the late 1990 s it began to show it s age

5 Disturbing Trends Collected Data Versus Transmitted Data

6 Additional Factors Increased System of Systems Complexity Five Futures (EW, UAV, NCO/W, DE, Hypersonics) Integrated fleet (F-18E/F, E-18G, F-35, SM VI, UAV) Future Combat Systems Larger Footprints Geographic separation no longer effective Global standards and cooperation Demand for Shorter Acquisition Cycles Requires for more concurrent testing Requires for more real-time analysis

7 Rationale for Change Decrease time and cost associated with T&E Reduce rework associated with: Telemetry Dropouts, need to return to base to access data on onboard archive, etc. Provide flexibility to respond to future needs Lack of two way connectivity limits flexibility. More Efficient Use of Spectrum Real-time transmitter control, data set selection, etc Leverage Simulation/Stimulation capability with two-way connectivity to test article Leverage the Wireless Revolution DoD and Private Sector are investing huge amounts of intellectual and financial capital in wireless networks

8 The Seeds of Change Within the Telemetry Group of the RCC, fierce debates raged A vocal minority of rogue telemetry engineers argued for a departure from chapter 4 An equally vocal majority argued to simply continue to update chapter 4 In 2001 a consensus emerged for a new architecture Centered around network enhancement of telemetry To boldly go where everyone else has already been

9 Laying the Foundation The inet Study Needs Discernment What requirements does this new architecture need to meet? Foundation is 52 DoD T&E scenarios Narrative descriptions of a wide range of test scenarios» Near-term to long-term, simple to exotic, etc» Defined multiple operating environments, although mostly targeted at the aeronautical environment 53 rd added later commercial aviation Experimental Architecture Can network enhancement of telemetry meet the needs? Defined a Telemetry Network System (TmNS) Design Technology Shortfalls What technology gaps exist to deploying the experimental architecture? Investment Roadmap Where does the sponsor need to invest to make inet a reality? The Needs Discernment is the cornerstone upon which the Architecture is built

10 Telemetry Network System Vehicle Data Acquisition Network Dedicated Legacy Streaming TM Link Vehicle Data Acquisition Network Dedicated Legacy Streaming TM Link TmNS Encompasses: Vehicle Network (vnet) RF Network (rfnet) Interface to Ground (INT2gNET) Serial Streaming Link (Legacy TM) Ground Network Dedicated Legacy Streaming TM Link Flight Simulators

11 Extensive Network Connectivity

12 Long-term Vision: Near-term Results To Provide geographically independent access, to ever increasing amounts of information, from ever increasing number of test articles, through limited spectral resources. inet Project IOC Fielded Capability Long-term Vision Vision is achieved through Block Releases Block 1 Block 2 N greater than or equal to 3 Block N

13 How was the proposed TmNS architecture developed? What is an architecture? A set of elements and the relationships between them Systems engineering a tool to solve complex problems Three activities: requirements analysis, functional analysis, and synthesis Repeat at each level of detail Choose solution that: Performs needed functions Optimizes overall measure of effectiveness Use trade studies to resolve complex decisions

14 Systems Engineering Approach Internet Engineering Task Force (IETF) Best commercial practices for defining & maturing standards and architectures 4 Step process Experimental Proposed Draft Final Consistent with DoD and industry systems engineering practices

15 inet Systems Engineering: the Boeing work June 05 June 07 Systems Engineering contract with Boeing Phantom Works Evolve the architecture from Experimental to Proposed About 75 % compete at delivery Significant system decisions» What s in, what s out» Bounded the problem» Most of the technical effort was expended defining a candidate RF link Architecture described and documented in a tiered structure System thru components There is a CONOPS and Requirements Document associated with each architecture document Presented to the RCC in August 2006 and at ITC 2006 June 07 CTTRA 17: Examined the inet architecture functions

16 inet Products Network Connectivity Architecture A connectivity architecture that support delivery of payloads/time distribution between ground segment and peripherals The TmNS, Network Management, and Spectrum Management This architecture is application and payload agnostic It delivers payloads and delivers packets within specified QoS Standards A set of standards required to implement the network connectivity architecture Tools and Standards that make inet more usable on the ranges XML Schema, APIs or ICDs for Ground Station Interface, etc. Prototype Hardware, Validation Tools and User Applications The minimum set of prototype hardware, tools and user applications necessary to demonstrate the architecture. Data mining, instrumentation control, etc

17 Standards Process Multiple working groups established Each working group is led by neutral third party under contract No vested interest in building hardware Working groups established via FedBizOps announcements Weekly meetings via teleconference and webex Face-to-face meetings quarterly or as needed Communications Link Standards Working Group Test Article Standards Working Group Systems Management Standards Working Group MetaData Standards Working Group Ground Segment Standards Working Group

18 M E A S U R A N D S Network Components / Devices TEST GROUND ARTICLE STATION SEGMENT SEGMENT CLSWG Edge Devices TASWG GSSWG Edge Devices SMSWG MDSWG

19 Block I Project Overview Functional Description Preserve existing TM link for safety of life / flight Make Bi-directional wireless network connection to TAs: Dynamic spectrum sharing based upon priority and quality of service Improved transmission quality (error free delivery) Access to data recorded on TA storage device Ability to change configuration of TA instrumentation Illustration inet Project Fielded - IOC Flight Simulators Telemetry Network System (TmNS) Encompasses: Vehicle Network (vnet) (Test Article, TA) RF Network (rfnet) Ground Network [Interface only (gnet)] Serial Streaming Telemetry (SST) Link

20 Block 1 Capabilities Network communication link between TmNS ground and test article segments Quality of service mechanisms that will at least provide: (a) Priority and (b) service type discrimination for; minimum delay transmissions, minimum error transmissions Scalable media access strategy for effective use of spectrum provided to inet Direct compatibility/interoperability with Internet Protocol (IP) version 4 and 6 datagram transmission at TmNS boundaries NSA Type 1 security approval/certification, secret and lower Support precise time alignment and synchronization of data TmNS configuration, management, diagnostic, and reporting services TMNS Performance Measurement and Reporting Service Support multiple TA's / tests Scalability (Throughout the TmNS)

21 Block 2 capabilities Test article to test article network communications Test article relay services Improved / enhanced network performance (speed, capacity, latency,...) Increased number of participants Security / encryption support for multiple independent levels of security Dynamic spectrum / bandwidth management flexibility Time alignment / increased accuracy in synchronization Expand to other environments Track test articles and predict interference

22 Challenges in other environments Significant increase in number of players Limited LOS, more obstructions, multipath may be the only path Likely to require ad hoc mesh topology with high bandwidth trunking between clusters Higher RF path losses More constraints on size, weight, power, and cost More dependence on relay platforms Higher Doppler Longer ranges

Block 1 Capabilities T&E Infrastructure Ground Test, and Flight Test Capability to

23 Program Implementation inet WBS Focus on Delivery of a Network Based Capability Requirement CONOPS Architecture Concept Demos Tech Demos System Prototype Acquisition Block 1 Capabilities T&E Infrastructure Ground Test, and Flight Test Capability to Support Demonstration, Development, and Sustainment of an integrated Network Enhanced Telemetry Capability

24 Pilot: Air Force Flight Test Center and NAVAIR Range at Patuxent River 2011 deployment of pilot installations at AFFTC and NAVAIR Patuxent River Strong team, community and sponsor support Pilot Definition Document in work now Goal is to brief at ITC 08 Current thinking 6 to 8 instrumented test articles 6 to 8 modified ground antennas 4 modified data processing stations Necessary infrastructure upgrades Pilot deployment funded by CTEIP

25 AIRSpeed: inet Deployment Disruption Finder Guidebook Pax inet Deployment CONOPS PAX inet Deployment Council MOU Navy took lead AFFTC to use results of the Navy effort Disruption Finder Guidebook Systematic approach to identify disruptions (issues) in deployment of inet NAVAIR Patuxent River inet Deployment CONOPS Process to be followed to deploy inet at Patuxent River inet Council MOU Signed by Navy Head of Flight Test and Navy Head of Ranges MOU establishing inet Council to oversee deployment of inet at Patuxent River

dropout out inet Concept Demo Minimal Allow Broad near applicability impact real-time on existing to mining existing instrumentation

26 Concept Demo PCM TM Link Existing Aircraft Instrumentation System Onboard Recorder Network RF inet Data Control Center Ground Station RF Modem Interface inet Subsystem Recorder Possible Allow for early recovery implementation of data lost during due to Tm Drop dropout out inet Concept Demo Minimal Allow Broad near applicability impact real-time on existing to mining existing instrumentation of Test data Articles onboard systemarchive Small Minimal package interface size to (about legacy the instrumentation size of a loaf of bread)

27 Technology Demo: Concept Demo on Steroids Spring 08 Comm Links Team tested b with transverter Flight tests went well Paper at ITC Once operationally verified, they delivered it to the Test Article Segment Team Spring/Summer 08 Comm Link Hardware is being integrated with a Test Article Network Installed in US Naval Test Pilot School H-60 Fall 08 First Flight of Technology Demo Goals Test in helo environment CONOPS Validation Integrate into range infrastructure

28 Telemetry of the Future Summary We are well on our way! Needs Discernment -Complete Concept Demo - Complete Proposed Standards Proposed Architecture 2009 Technology Demo Fall 2008 Pilot Deployment 2011 This is an exciting time to work in telemetry!

Telemetry of the Future

Telemetry of the Future and the future is not too far off! Thomas Grace TAS Chief Engineer Thomas.Grace@navy.mil 301-342-1227 Traditional Telemetry 50 Years of Service Has served us well but it is starting