Your systems. Working as one.Your systems. Working as one.
RTI Support for FACE
Bill Antypas
June 20, 2013
RTI Transport Services Segment (TSS)
2
DDS-RTPS wire
protocol compliant:
interoperable with
non-FACE DDS apps
Publish/subscribe
paradigm*
Physical connection(s)
configurable at
integration time
*Will likely support additional
paradigms in future
Core Architecture
Built on Standard and Open Interfaces
PCS
Component
PCS
Component
PSS
Component
RTI Connext DDS
Core, Messaging, Micro or Cert
PSS
Component
FACE Security Profile
Transport Services API to DDS Mapping
3
Intra-
proces
s
Shared
memor
y
ARINC
Ports
Sockets
Other/
Custom
RTITransportServicesSegment
FACE Transport
Services (TS) API
FACE Security
Profile
RTI transport
API
OMG DDS API
DDS-RTPS
protocol
Pluggable
transports
Optimized, Location-Independent
Communication
• Physical transport(s) configurable at integration time
• Applications can use multiple transports concurrently
• Transport(s) configured per application
4
Transport Use
Intra-process Within the same address space (process)
Shared memory Between processes in the same partition
ARINC ports Within a node; within or between partitions
Sockets
(UDP unicast or multicast)
Within or between nodes, including over
Ethernet
Low-bandwidth Over satellite or radio links (no IP requirement)
Custom Over custom networks or busses (via plug-in API)
PartitionPartitionPartition
Deployment Example
5
UoP UoP
Shared memory
App
RTI TSS RTI TSS
UoP UoP UoP
RTI TSS RTI TSS RTI TSS
ARINC Ports
RTI TSS
Bus/Network
Node Node
TSS Connection Mechanism Comparison
6
RTIDDS
CORBA
Sockets
POSIX
Queues
Shared
memory
Queuing
ports
Sampling
ports
Proximity Intra-partition ● ● ● ● ● ● ●
Inter-partition ● ● ● ● ●
Inter-node ● ● ●
Multiple concurrently ●
Distribution One-to-one ● ● ● ● ● ● ●
One-to-many ● ● ● ● ●
Many-to-one ● ● ●
Many-to-many ● ●
● Unreliable
Level E
Partition
Up to Level A Partition
RTI Routing Service:
Transport and Network Routing
• Component of RTI Connext Integrator
• Deployable in uncertified systems or Level E partitions
• Also supports data transformations, protocol mediation
7
UoP UoP
ARINC Ports
RTI TSS RTI TSS
UoP
Node Non-Critical
Node or
Partition
UoP
Non-Critical
Node or
Partition
RTI TSS
Bus/Network
Routing
Service
RTI TSS
Level E
Partition
Up to Level A Partition
RTI Routing Service:
Transport and Network Bridging
8
UoP UoP
ARINC Ports
RTI TSS RTI TSS
Node
Routing
Service
Up to Level A Partition
UoP UoP
RTI TSS RTI TSS
Node
Level E
Partition
Bus/Network
ARINC Ports
Routing
Service
Airborne System
Airborne System
Flexible Integration
Including TSS and
Native DDS Apps
9
FACE
UoP
FACE
UoP
Local Communication
RTI TSS RTI TSS
Routing
Service
FACE
UoP
FACE
UoP
Local Communication
RTI TSS RTI TSS
Routing
Service
DDS
App
DDS
App
Local Communication
RTI DDS RTI DDS
Routing
Service
Ground System
DDS Natively Supports FACE Data Model
• FACE messages are strongly typed
• OMG IDL used by FACE Platform Data Model & DDS
– FACE messages must conform to IDLlanguage mapping
– Apps can use mappings generated by RTI’s IDL compiler
• DDS natively understands data
– Type safety
– Heterogeneous interoperability (languages, CPUs)
– Wire efficiency (minimizes metadata)
– Enables middleware-level filtering (including at source)
– Eases integration (explicit interfaces)
10
FACE Platform
Data Model
RTI IDL
Compiler
C
C++
Java
Ada
Include in
application
source
Supports DDS QoS
• Messaging reliability: Best Effort and Reliable
• Optional durability maintains consistent state
– Last value(s) persisted by publisher
– Available to late- and re-joining subscribers
– History depth configurable on pub and sub sides
• Automatic failover: Ownership and Strength
• Send/receive cache resource configuration
11
Certification Path
• Thin layer over DDS
– Currently <2K ELOC
• Compatible with Connext DDS Cert
– DO-178C Level A certifiable
– Evaluation in progress
– ~20K Executable Lines Of Code (ELOC)
– Small memory footprint: ~200 KB library
– Low CPU load: <10% at 30 HZ update rate
12
Planned FACE Profile Support
Security Safety Base Safety Extended General Purpose
RTI TSS ✔ ✔ ✔ ✔
RTI Connext DDS
Cert ✔ ✔ ✔ ✔
Micro ✔ ✔
Core ✔
Messaging ✔
RTI Routing Service ✔
13
Tools Support
• RTI Analyzer
• RTI Monitor*
• RTI Recording Service
• RTI Excel Add-in
• Wireshark
• National Instruments LabView
• The Mathworks Simulink and MATLAB
14
*Currently supported for Connext DDS Core and Connext DDS Messaging
With pub/sub paradigm: tools are non- or minimally-intrusive, application transparent
Summary of RTI TSS Benefits
• Proximity and physical transport independence
• Flexible communication
– 11, 1many, many1, manymany
• Routing and federation
• Interoperability with non-FACE apps
– Peer-to-peer with DDS apps
– Via Connext Integrator for non-DDS apps
• Optimized support for FACE data model
• Rich Quality of Service
• Expeditious path to DO-178C Level A certification
• Tooling
15
Available Now
• Early Access Release (EAR)
• Based on FACE Technical Standard 2.0
• Complete implementation of C lang TS API
• Portable source code
• No charge for TSS
• Requires license to Connext DDS edition
16
C AppJava App
Joint Demo
RTI Connext
DDS Micro
RTI FACE Transport Service Segment
DDS-RTPS Wire Interoperability Protocol
17
ARM CPU PowerPC CPU
VxWorks 653
RTI Connext DDS Messaging
Android OS

RTI Support for FACE TSS

  • 1.
    Your systems. Workingas one.Your systems. Working as one. RTI Support for FACE Bill Antypas June 20, 2013
  • 2.
    RTI Transport ServicesSegment (TSS) 2 DDS-RTPS wire protocol compliant: interoperable with non-FACE DDS apps Publish/subscribe paradigm* Physical connection(s) configurable at integration time *Will likely support additional paradigms in future
  • 3.
    Core Architecture Built onStandard and Open Interfaces PCS Component PCS Component PSS Component RTI Connext DDS Core, Messaging, Micro or Cert PSS Component FACE Security Profile Transport Services API to DDS Mapping 3 Intra- proces s Shared memor y ARINC Ports Sockets Other/ Custom RTITransportServicesSegment FACE Transport Services (TS) API FACE Security Profile RTI transport API OMG DDS API DDS-RTPS protocol Pluggable transports
  • 4.
    Optimized, Location-Independent Communication • Physicaltransport(s) configurable at integration time • Applications can use multiple transports concurrently • Transport(s) configured per application 4 Transport Use Intra-process Within the same address space (process) Shared memory Between processes in the same partition ARINC ports Within a node; within or between partitions Sockets (UDP unicast or multicast) Within or between nodes, including over Ethernet Low-bandwidth Over satellite or radio links (no IP requirement) Custom Over custom networks or busses (via plug-in API)
  • 5.
    PartitionPartitionPartition Deployment Example 5 UoP UoP Sharedmemory App RTI TSS RTI TSS UoP UoP UoP RTI TSS RTI TSS RTI TSS ARINC Ports RTI TSS Bus/Network Node Node
  • 6.
    TSS Connection MechanismComparison 6 RTIDDS CORBA Sockets POSIX Queues Shared memory Queuing ports Sampling ports Proximity Intra-partition ● ● ● ● ● ● ● Inter-partition ● ● ● ● ● Inter-node ● ● ● Multiple concurrently ● Distribution One-to-one ● ● ● ● ● ● ● One-to-many ● ● ● ● ● Many-to-one ● ● ● Many-to-many ● ● ● Unreliable
  • 7.
    Level E Partition Up toLevel A Partition RTI Routing Service: Transport and Network Routing • Component of RTI Connext Integrator • Deployable in uncertified systems or Level E partitions • Also supports data transformations, protocol mediation 7 UoP UoP ARINC Ports RTI TSS RTI TSS UoP Node Non-Critical Node or Partition UoP Non-Critical Node or Partition RTI TSS Bus/Network Routing Service RTI TSS
  • 8.
    Level E Partition Up toLevel A Partition RTI Routing Service: Transport and Network Bridging 8 UoP UoP ARINC Ports RTI TSS RTI TSS Node Routing Service Up to Level A Partition UoP UoP RTI TSS RTI TSS Node Level E Partition Bus/Network ARINC Ports Routing Service
  • 9.
    Airborne System Airborne System FlexibleIntegration Including TSS and Native DDS Apps 9 FACE UoP FACE UoP Local Communication RTI TSS RTI TSS Routing Service FACE UoP FACE UoP Local Communication RTI TSS RTI TSS Routing Service DDS App DDS App Local Communication RTI DDS RTI DDS Routing Service Ground System
  • 10.
    DDS Natively SupportsFACE Data Model • FACE messages are strongly typed • OMG IDL used by FACE Platform Data Model & DDS – FACE messages must conform to IDLlanguage mapping – Apps can use mappings generated by RTI’s IDL compiler • DDS natively understands data – Type safety – Heterogeneous interoperability (languages, CPUs) – Wire efficiency (minimizes metadata) – Enables middleware-level filtering (including at source) – Eases integration (explicit interfaces) 10 FACE Platform Data Model RTI IDL Compiler C C++ Java Ada Include in application source
  • 11.
    Supports DDS QoS •Messaging reliability: Best Effort and Reliable • Optional durability maintains consistent state – Last value(s) persisted by publisher – Available to late- and re-joining subscribers – History depth configurable on pub and sub sides • Automatic failover: Ownership and Strength • Send/receive cache resource configuration 11
  • 12.
    Certification Path • Thinlayer over DDS – Currently <2K ELOC • Compatible with Connext DDS Cert – DO-178C Level A certifiable – Evaluation in progress – ~20K Executable Lines Of Code (ELOC) – Small memory footprint: ~200 KB library – Low CPU load: <10% at 30 HZ update rate 12
  • 13.
    Planned FACE ProfileSupport Security Safety Base Safety Extended General Purpose RTI TSS ✔ ✔ ✔ ✔ RTI Connext DDS Cert ✔ ✔ ✔ ✔ Micro ✔ ✔ Core ✔ Messaging ✔ RTI Routing Service ✔ 13
  • 14.
    Tools Support • RTIAnalyzer • RTI Monitor* • RTI Recording Service • RTI Excel Add-in • Wireshark • National Instruments LabView • The Mathworks Simulink and MATLAB 14 *Currently supported for Connext DDS Core and Connext DDS Messaging With pub/sub paradigm: tools are non- or minimally-intrusive, application transparent
  • 15.
    Summary of RTITSS Benefits • Proximity and physical transport independence • Flexible communication – 11, 1many, many1, manymany • Routing and federation • Interoperability with non-FACE apps – Peer-to-peer with DDS apps – Via Connext Integrator for non-DDS apps • Optimized support for FACE data model • Rich Quality of Service • Expeditious path to DO-178C Level A certification • Tooling 15
  • 16.
    Available Now • EarlyAccess Release (EAR) • Based on FACE Technical Standard 2.0 • Complete implementation of C lang TS API • Portable source code • No charge for TSS • Requires license to Connext DDS edition 16
  • 17.
    C AppJava App JointDemo RTI Connext DDS Micro RTI FACE Transport Service Segment DDS-RTPS Wire Interoperability Protocol 17 ARM CPU PowerPC CPU VxWorks 653 RTI Connext DDS Messaging Android OS