dds enabling open architecture
DESCRIPTION
Even though the U.S. Department of Defense budget is shrinking and the country's military footprint worldwide is receding the need for the warfighter to have accurate and actionable intelligence has never been more critical. Data from Intelligence, Surveillance, and Reconnaissance (C4ISR) systems such as radar, image processing payloads on Unmanned Aerial Vehicles, and more will be used and fused together to provide commanders with real-time situational awareness. Each system will also need to embrace open architectures and the latest commercial standards to meet the DoD's performance, size, and cost requirements. This e-cast will discuss how embedded defense suppliers are meeting these challenges.TRANSCRIPT
Your systems. Working as one.
DDS: Enabling Open Architecture
David Barnett | [email protected] | @rtidavidDecember 4, 2013
© 2013 RTI 2
Challenge: Communication and IntegrationHow Do Applications and Devices Share Data?
System System of Systems
Mapping
UI
MissionPlanning
VehicleComms
WeaponController
December 4, 2013
Sensors
© 2013 RTI 3
Traditional Approach:Point-to-Point Integration
• Explicit connections
• Increasingly complex over time
• Stovepipe and brittle
• Poor reuse• Hard to
reconfigureE.g., sockets, RPC
December 4, 2013
Cost Constrains Integration andLimits Data Sharing
Time & cost of integration,
maintenance and upgrades
System Scale and Age
© 2013 RTI 4December 4, 2013
Solution: “Software Data Bus”
• Software components are plug and play
• Simple, loosely coupled architecture– No point-to-point
integration logic
• Scales to large projects and systems of systems– A modular, open
architecture
• Enables rapid reconfiguration
S/W S/W S/WS/W
Data Distribution Service
© 2013 RTI 5December 4, 2013
© 2013 RTI 6
Foundation: Publish/Subscribe
Components are loosely-coupled, require no knowledge of each other
Data Distribution Service
Sensor
Sens
or D
ata
Sens
or D
ata
Control App
Com
man
ds
Stat
us
Sensor
Sens
or D
ata
Actuator
Com
man
ds
Stat
us
Display App
Sens
or D
ata
Stat
us
December 4, 2013
© 2013 RTI 7
Data Distribution Service (DDS)
• Open standard• Object Management Group
(OMG)• At least 10 implementations• Designed for real-time,
embedded, mission critical• Middleware and subsystem
vendor independence
DDS Real-Time Publish-Subscribe
Wire Protocol (RTPS)
DDS Middleware
DDS API (Application Programming Interface)
Cross-vendor portability
Cross-vendor interoperability
December 4, 2013
© 2013 RTI 8
Integration Scenarios
• Completely decentralized• Components communicate peer-to-peer• No intermediate servers, message brokers, daemon processes
Unmodified App
DDS-RTPS Wire Interoperability Protocol
DDS Routing Service
Adapter
Unmodified App
DDS Routing Service
AdapterApp or
Component
DDS Library
App or Component
DDS Library
DDS or other protocol
DDSAPI
New and Updated Applications Existing, Unmodified Applications
December 4, 2013
© 2013 RTI 9
Broad Interoperability for Heterogeneous Systems
• Programming languages and environments– C, C++, C#/.NET, Java, Ada– REST/HTTP– LabVIEW, MATLAB, Simulink, UML
• Operating systems– Windows, Linux, Unix, Mac OS– Embedded, real time, partitioned– Mobile
• Processor families– x86, ARM, PowerPC– 32- and 64-bit
• Transport types– Shared memory– LAN (incl. multicast)– WAN– Secure– Low bandwidth
December 4, 2013
Completely application transparent
© 2013 RTI 10
Future Airborne Capability Environment (FACE)Transport Services Segment (TSS)
PCS Component
PCS Component
PSS Component
DDS Library
PSS Component
FACE General Purpose or Security Profile (w/Connext DDS Cert)
Transport Services API to DDS Mapping
Intra‑proces
s
Sharedmemor
y
ARINCPorts Sockets Other/
Custom
FACE
TSS
FACE Transport Services (TS) API
OMG DDS API
DDS-RTPS protocol
Pluggable transports
December 4, 2013
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
Asset Tracking System
Next-Gen Capability:• 50K lines of code—order
of magnitude less• 1 yr to develop—8x less• 1 laptop—20x less• Achieved: 250K+ tracked
updates/sec, no single point of failure
Legacy Capability:• 500K lines of code• 8 yrs to develop• 21 servers• Achieved: 20K tracked
updates/sec, reliability and uptime challenges
© 2013 RTI 12
“This would not have been possible with any other known technology.”—Network Ops Center Technical Lead
December 4, 2013
© 2013 RTI 13
About RTI
• Communications middleware market leader– Largest embedded middleware vendor*
– Over 70% commercial DDS market share*
• Standards leader– Active in 15 standards efforts– OMG Board of Directors– DDS authors
• Real-time pedigree– Founded by Stanford researchers– High-performance control, tools history
• Maturity leader– 600+ designs. 400+ research projects– 400,000+ licensed copies– TRL 9 *Embedded Market Forecasters
and Venture Development Corp (VDC)
December 4, 2013
RTI Connext DDS Product Family
DDS-RTPS Wire Interoperability
Micro
DDS Subset
Tools
Administration
Monitoring
Recording
Replay
LoggingSystem Viz
Small Footprint Apps
14
Cert
DDS Subset
Safety Critical Apps, up to DO-
178C Level ADDS API
DisparateApps/Systems
Routing Service
Mediation, routing
Adapter
© 2013 RTI
General Purpose
DDS Superset
General Purpose, Real-Time Apps
December 4, 2013
© 2013 RTI 15
Summary
Open Architecture DDS• Software foundation for OA• Eliminates costly point-to-
point integration• Provides seamless
Interoperability– Subsystems– New and existing applications
• Satisfies needs of mission-critical system
December 4, 2013
• Cost-effective integration of larger systems and SoS
• Reuse• Rapid reconfiguration• Improved data sharing and
situational awareness
Your systems. Working as one.
Thank You!