SORD Gateway Updates

1. SORD Gateway Updates Stephanie Graffuis

2. Overview • Introduction • Capabilities • Enhancements and Fixes • SORD Gateway Efforts • Client Capabilities • New Applications of the SGW

3. Introduction • The SORD Gateway is a component in OneSAF that provides HTTP access to OneSAF’s distributed runtime simulation data. • Uses standard mechanisms for data distribution • HTTP for database queries • XML used to encode objects • REST principles with HTTP request verbs • Provides a non-simulation specific API that improves scalability • Objects and interactions in the SORD are resources for clients to act on via the SORD Gateway

4. Simulation Needs • Simulation community needs addressed by the SORD Gateway: • Reusable components • Enhanced methods of interoperability • Solutions for complex, larger training problems • Rapid prototype results • Support multiple communication protocols, fidelities, and configurations

5. Capabilities • The core capabilities of the SORD Gateway are • Getting, deleting, creating, and updating objects • Subscribing to object and interaction events • Creating and firing interactions • Defining new object and interaction types

6. Enhancements - Dynamic Requests • Requests provided by SGW are its resources • SORD has different resources (objects, interactions) • Requests extension framework • uses OneSAF composability concepts • Allows now we can add specific capabilities without cluttering core functionality • Advantages • Keep SGW generic and simulation independent • Minimize OneSAF dependencies and changes

7. Enhancements - Online Help • Help is provided online while SORD Gateway is running • Web browser accessible • Content is accumulated from all available SGW request resources • Manually exported for offline viewing in our documentation folders

8. Enhancements - Other • JUnit tests • Multi-client notification/subscription support • Performance • Tests written • HTTP Compression

9. SORD Gateway Efforts Each project demonstrates a new requirement for interoperability to satisfy a complex training requirement. Several projects within the RDECOM-STTC use the SORD Gateway for their research efforts.

10. SORD Gateway Efforts • Game Based C2 • SGW used to inject externally calculated physics effects into OneSAF • ARA SGW Client and RPEL • Rubble • SGW used to create rubble piles based on external calculations for flyout debris • Anyar, Inc. physics motion solver • ARA SGW Client and RPEL

11. SORD Gateway Efforts • HI2NT • SGW used to assist in transferring combat intelligence information into OneSAF • ARA SGW Client • MATREX ProtoCore API

12. Client Capabilities • These are documented efforts on how the SORD Gateway was used to accomplish certain goals. They may or may not require code changes. • How-to information written up • Minimal to no code changes needed • Proof-of-concept tests

13. Client Capabilities • Ownship • Client goal: override entity location (mobility) and damage state (vulnerability) • Documented how to use existing framework within OneSAF • Mood/Gesture • Communicate mood/gesture from JNEM to OneSAF • OneSAF RDM modified to store values per entity

14. Client Capabilities • Creating Rubble • Inject rubble piles into OneSAF during scenario run based on external physics calculations • Proof-of-concept test uses existing OneSAF dynamic terrain with minor workarounds • Scenario Management • Change simulation state via the SORD Gateway • JUnit test and SORD Gateway dynamic request created

15. New Applications of the SORD Gateway • In what interesting ways can we enhance the SGW or use existing enhancements to further promote interoperability to solve complex use cases? • Graphical User Interfaces • Object Wrappers

16. Graphical User Interfaces • The SORD Gateway publishes available client requests via URL. • Content is available as HTML or XML • Publication is dynamic based on runtime settings • Originally started as a means of capability testing

17. Graphical User Interfaces • When available requests are retrieved as HTML content ... • A web form is provided for user interaction • viewable within an internet browser • requests can be made via ‘point and click’ • Allows for independent user interfaces via web enabled desktop applications

18. Graphical User Interfaces • When available requests are retrieved as XML content ... • Same scalability, more powerful • Not limited to Gateway’s HTML rendering • Clients can render content into HTML or other GUIs to create custom applications

19. Object Wrappers • The SORD Gateway allows you define new data types at runtime for information storage and distribution. • Data changes only remain while running after being defined • minimal effort to setup and/or change • no hard coded changes required

20. Object Wrappers WRAPPER myVehicle vin make model GROUND_VEHICLE name location velocity entityType ... • Extend OneSAF data for data tracking and linking in federate/client • Wrap existing OneSAF objects to add metadata about that object that is not represented

21. Object Wrappers WRAPPER-ENTITY trueSelf objectType size appearance LIFEFORM name location velocity entityType ... • Disguise OneSAF data for different visual representation within federate/client • Wrap existing OneSAF objects to represent them differently than they really are

22. Questions? Email info@stackframe.com