the global leader in dds a standards-based integration platform for reconfigurable unmanned aircraft...

The Global Leader in DDS

A Standards-Based Integration Platform for Reconfigurable Unmanned Aircraft Systems

Mark A. Hamilton

© 2010 Real-Time Innovations, Inc. 2

Agenda

Background– Multi-mission UAS in the net-centric environment

UAS communication requirements

Need for modular and adaptable systems architecture

Open integration framework solution– Standards based– Deployed inside and outside UAS


Net-Centric UAS

Next generation UAS is network of– Self-coordinating UAVs– Multiple Ground Control Stations (GCS’s)– Manned aircraft, space systems, ground troops

Multiple and changing mission objectives

Net-centric vision challenge:– Make data and capabilities of UAVs and GCS’s

accessible to every relevant participant tothe net-centric environment


Towards Open Integration Platform

Efficient use of communication infrastructure essential to net-centric environment

Contribution to goals from US DoD Unmanned Systems Roadmap 2007-2032:– Greater interoperability among sub-systems by

emphasizing commonality– Development of policies, standards, and procedures for

safe and timely operations and effective integration


More Efficient Communication Infrastructure Utilization

Vehicle LAN

Data Link

Ground StationLAN

Avionics

Net Centric GIG

TacticalBackbone

Real-Time

Ground Station

BackendWAN


Baseline Capabilities for UAS Communication Platform

Open standards based– Commonality and interoperability

True peer-to-peer architecture– No single point of failure or vulnerability

Portable to any communication media– RF, optical links, high-speed interconnects,

enterprise networks

Available for heterogeneous environments– Embedded, low-power, small foot-print, RTOS, MILS, ARINC 653– Mainstream OS’s (Windows, Linux) and CPUs (Intel x86)

Adaptable to certification (DO-178B)

Integrate with payload data (STANAG 4586)


Communications “Matrix of Pain”

Multiple traffic types:– Sensor data streams– Command and control data– Status, intelligence, mission, supervisory data

Different traffic requirements for each type:– Response time, priority, reliability, volume– Stealth operations

Challenging communications channel:– Large latency, low throughput– Lossy– Varying availability– Asymmetric bandwidth (downlink vs uplink)

Standards-Based Data-CentricIntegration Platform

OMG Data Distribution Service (DDS) Standard

Sen

sor

Dat

a

Control App

Com

man

ds

Sta

tus

Sensor

Sen

sor

Dat

a

Actuator

Com

man

ds

Sta

tus

8© 2010 Real-Time Innovations, Inc.



Sensor

Sen

sor

Dat

a

Sen

sor

Dat

a

Control App

Com

man

ds

Sta

tus

Sensor

Sen

sor

Dat

a

Actuator

Com

man

ds

Sta

tus




Sensor

Sen

sor

Dat

a

Sen

sor

Dat

a

Control App

Com

man

ds

Sta

tus

Sensor

Sen

sor

Dat

a

Actuator

Com

man

ds

Sta

tus

Display App

Sen

sor

Dat

a

Sta

tus


11

Raytheon Keynote Presentation September 2006 at DDS Information Day, Anaheim , CA

Why Distribution Middleware?

8.0 Training

5.0 Communications

2.0 Sensors

3.0 Fusion

4.0 BMC2

7.0 Visualization

6.0 Sensor Control

1.0 Common Services

Grouping the modules into functional clusters does nothing to change that reality and ease software integration

UNCLASSIFIED

Hawkeye has functionally oriented software modules

Each module talks to many other modules RIP TRK MSI

WAC TDA

ESM SAFERDR IFF

SEN DSCL4 L16L11

HMI ACIS

DIA NAV IPCCMCP

MUX

FIL TDM

Adding new functionality cascades integration re-work across many other modules

CEC

8.0 Training

5.0 Communications

2.0 Sensors

3.0 Fusion

4.0 BMC2

7.0 Visualization

6.0 Sensor Control

1.0 Common Services

RIP TRKCEC MSIWAC RAIDERTDA

DWC

CHAT

ESM SAFERDR IFF

SEN DSCD

istribu

ted D

ata Fram

ewo

rkIPv6L4 L16L11

HMI ACIS T4O

DIA NAV IPCCMCP

MUX

FIL TDM aADNS TIS

1.0 Common Services

Changing the communication between the modules can ease integration, when the new ‘Publish Subscribe’ approach is used – each module publishes its output w/o regard to who is receiving it, in contrast to the point-to-point approach of traditional inter-process communication

It’s about an architecture that can assimilate evolving functionality, rather than remaining set in time 12

Choosing the Right Integration Middleware

Final Designs within 30% of Pre-Design Expectations

Report by Embedded Market Forecasters

Groupsanalyzed:


Expected Development Cost for Average Project

RYO Commercial DDS

Software developers 8.5 10 6

Months of development 14.2 14.6 13.5

Developer months 120.7 146 81

Cost @ $10,000 per developer month

$1,207,000 $1,460,000 $810,000



Program Adoption

DISA: DISR mandated Navy: Open Architecture,

FORCEnet Air Force, Navy and DISA:

NESI Army: SoSCOE Air traffic control for southern

Europe

…plus over 300 individual projects


DDS Application Examples

Aegis Weapon System

Lockheed Martin

Radar, weapons, displays, C2

B-1B Bomber

Boeing

C2, communications, weapons

Common Link Integration Processing (CLIP)

Northrop Grumman

Standards-compliant interface to legacy and new tactical data links

Air Force, Navy, B-1B and B-52

ScanEagle UAV

Boeing

Sensors, ground station

Advanced Cockpit Ground Control Station

Predator and SkyWarrior UAS

General Atomics

Telemetry data, multiple workstations

RoboScout

Base10

Internal data bus and link to communications center

DDS Real-Time Quality of Service (QoS)

Time aware– Missed deadline notifications– Stale data automatically deleted– Nanosecond granularity timestamps

Historic data available to late or intermittent consumers

Fine-grained control over subscribed data– Filtering by time and content– Concurrently supports disparate requirements

with loose coupling

Highly tunable reliability protocol– Balance latency, throughput, reliability and

resource consumption– Optimize for a wide variety of interconnects—

shared memory to satellite and radio links



Pluggable Transport Framework

Standard IP network(Ethernet, SM, etc.)

IP

UDP

IB

Allows for simultaneous use of multiple transports

Enables non-IP transports (e.g. DMA fabrics)

Supports low-bandwidth links

Allows for secure/safe transports (e.g. 653, TLS)

TCPIPv4IPv6 DTLS IPsec

RTI Data Distribution Service

Real-timeapplications


Open Architecture

Vendor independent– API for portability– Wire protocol (RTPS) for interoperability

Multiple vendors– 7 of API– 4 support RTPS

Heterogeneous– C, C++, Java, .NET, Ada– Windows, Linux, Unix, embedded, real-

time, MILS, ARINC 653

Loosely coupled

Real-Time Publish-Subscribe

Wire Protocol (RTPS)

Middleware

DDS API

Cross-vendor portability

Cross-vendor interoperability

Safety Critical Edition of DDS

Foundation for a DO-178Bcertifiable middleware– Few lines of code– Deterministic– Designed to meet safety-

criticality requirements

Initially developed for satelliteapplication by US AFRL

Supports DDS standard

Supports systems using RTPS-compliant DDS middleware

Easily integrate net-centric systems


Software-verification experts Verocel have analyzed Safety-Critical Edition of DDS

Determinations:– Code is deterministic– Code is testable– Conforms to coding styles that make testing easier– Uses robustness checks and logging messages

Certifiability


Insitu Unmanned Air Vehicle

“…we have seen a 30% increase in productivity based on not having to handle data communication issues.” Gary Viviani, VP of Engineering

Insitu is a recognized leader in the exploding UAV space

The next generation of UAV’s including the Scan Eagle and newer platforms

Challenge is to have a successful UAV mission which requires impressive autonomy and reliable ground control

DDS enables an information flow that is much more orchestrated and flexible allowing seamless switch control between multiple ground stations while connecting reliably over unreliable links

© 2010 Real-Time Innovations, Inc. 23© 2008 Real-Time Innovations, Inc.23

Predator Ground Control Station

Defense

General Atomics Aeronautical Systems developed advanced cockpit ground control stations (GCSs) for unmanned aircraft systems

Required real-time data distribution for acquisition, analysis, and response of remote controlled aircraft

This application was delivered in under 14 months, significantly faster than with alternative infrastructure or building their own.

DDS speeds development


CLIP Mediator Bridge

Transportation

• Common Link Integration Processing (CLIP): U.S. Air Force and Navy joint project to build Tactical Data Link (TDL) aggregator

• Enables information exchange between platforms with incompatible tactical data links

• Challenge: existing system had poor integration with platform mission systems

• DDS bridges legacy systems

Tactical Data Links

LINK16 LINK11LINK22

TCP/UDP/IP

Displays& other systems

Conclusion


An open standards-based, net-centric architectural approach is key to building a true reconfigurable multi-mission UAS interoperable platform that is adaptable,

flexible and scalable.


RTI’s DDS Leadership

Over 70% worldwide market share First with…

– DDS API (2004)– RTPS interoperability protocol (2007)

• Native

Active in OMG standardization– Board of Directors member– Co-chair DDS SIG– Chair DDS standard revision committees

Most mature solution– 12+ years of commercial availability– Diverse range of industries: defense, finance, medical, industrial

control, power generation, communications– 300+ commercial customers, 100+ research projects– 100,000+ licensed copies– U.S. DoD Technology Readiness Level (TRL) 9


Thank You!

the global leader in dds a standards-based integration platform for reconfigurable unmanned aircraft...

Documents

control data status

realtime innovations

sensor data streams

netcentric environment

payload data stanag

netcentric uas

effective integration

outside uas slide