05SSIW143 Bridging Simulation and C2 Systems Through an M

1
05S-SIW-143Bridging Simulation and C2 Systems
Through an MS SOA
Kang Looi, Choo Daryl Lee Defence Science
Technology Agency, Singaporeemail
ckangloo_at_dsta.gov.sg lchinsio_at_dsta.gov.sg
2
Outline

• Background, Motivation Objectives
• MS Services Through Sim-C2 Gateway
• Orchestrating MS Services Via Injects Engine
• Relevant SISO works

3
Introduction

• Background
• Ongoing work at Defence Science Technology
  Agency (DSTA), Singapore to explore suitable
  technologies to support an MS SOA
• Motivation
• To enable Sim and C2 integration via
  service-oriented architecture
• Objectives
• Build a reusable Simulation Web Service Gateway
• Facilitate the composition and deployment of
  orchestrated services

4
Overview
5
Sim-CCIS Message Gateway
Sim-CCIS Gateway
6
Protocol Translator
Simulation Wrapper
Sim-CCIS Gateway
JMS
CCIS
HTTP
CCIS
CCIS
Web/JMS Server
Internal Comms
HLA
Simulation Station/ System
7
Plug-in Component

• Gateway Module is built as a plug-in component to
  the Simulation Engine
• Used as a central translator between multiple
  simulations and C2 systems as shown in the
  previous slide.
• Deployed in different ways, as shown in the next
  2 slides

8
Individual Gateways
Internal Comms
JMS
Sim-CCIS Gateway
Simulation Station/ System
HTTP
CCIS
Web/JMS Server
HLA
CCIS
Simulation Station/ System
Sim-CCIS Gateway
CCIS
JMS
CCIS
HTTP
9
Shared Gateway
Full-fledged simulation/s
HLA
Engine
JMS
Sim-CCIS Gateway
Database
HTTP
CCIS
CCIS
CCIS
Models
Web/JMS Server
10
Real-time updating

• Required by many C2 systems e.g., those
  displaying situation pictures
• Therefore, a 'push' mechanism instead of the
  standard HTTP pull was chosen
• Data is published onto topics (JMS) to cater for
  variable numbers of C2 clients

11
Re-configurable Interface

• Messages exchanged via the interface change
  dramatically between deployments
• The Interface Mapper Tool formats and outputs
  simulation data based on XML Configuration Files
• Interfacing achieved without altering data
  formats on either end

12
Interface Mapper
Raw Simulation Data
Formatted Simulation Data
Interface Mapper
Simulation Player Station
C2 Clients
Model Interface specs (similar to BOMs)
XML Config Files
13
Meta-configuration file
Server And Login
Message Format Metafile
Topics to Subscribe to
Message Format To use
Topics to Publish to
Optional Message properties
14
Message configuration file
Simulation entity type to draw data from
Message format name
Attribute name in simulation world
XML tags to use in output
Data type to convert to (Complex
conversions available separately)
15
For example, this file ..
ltxslfor-each selectENTITY/Platformgt
ltPlatformReportgt ltIDgt ltxslvalue-of
select _at_EntityID/gt lt/IDgt ltCoordXgt
ltxslvalue-of select _at_Position.x/gt
lt/CoordXgt ltCoordYgt ltxslvalue-of
select _at_Position.y/gt lt/CoordYgt
lt/PlatformReportgt lt/xslfor-eachgt
16
producesthisoutput
ltPlatformReportgt ltIDgt2309lt/IDgt
ltCoordXgt35lt/CoordXgt ltCoordYgt58lt/CoordYgt lt/Platfo
rmReportgt ltPlatformReportgt ltIDgt2310lt/IDgt
ltCoordXgt5lt/CoordXgt ltCoordYgt-20lt/CoordYgt lt/Platfo
rmReportgt . . . ltPlatformReportgt ltIDgt2350lt/IDgt
ltCoordXgt100lt/CoordXgt ltCoordYgt56lt/CoordYgt lt/Plat
formReportgt
17
Messages exchanged so far

• Air, Land and Sea Tracks (both detections and
  ground truth)
• Targeting information (target lists and
  sensor-shooter locations)
• Mission Plans

18
Considerations of load

• The dual requirements of frequent updating and
  large scenarios leads to bandwidth issues. To
  mitigate these, the gateway can
• Produce data in binary format instead of XML
• Send only changes
• Trigger only on specific simulation events
• Do periodic refreshes to sync the systems

19
Service Orchestration through Injects Engine

• Injects Engine is an initial effort to look at
  how Service Orchestration concepts and
  technologies can be employed.

20
Concept of Injects Engine
Simulation
C2 System
21
An Event Flow
Inject Engine
External Interface
External Interface
LEGEND
22
Inject Structure
Attributes
Basic Inject attributes eg. Display and
description attributes
Name
Category
Where to find report, e.g., local path/url,
embedded in ltPayloadgt element
Payload
Contents of report to be sent to recipent
Report
Location
Supported modes are HTTP, FILE I/O and JMS (next
phase)
Recipients
List of recipients of the payload upon triggering
of Inject
Mode
Addressee
Time-based injects are atomic/standalone.
Absolute or Relative time. Event-based ones can
be chained. Manual or on receipt on another input
e.g., from HTTP, JMS, another inject (depends on
adaptors available).
Condition to determine how inject is triggered
Triggering Conditions
Time
Event
Manual inject-response tagging. To explore
automatic tagging In next phase e.g, using fields
in Payload.Report.
Expected Response
TimeOut
Tag Inject-Response
Timeout before another inject is triggered.
23
Modules Overview
Messaging Protocol
Workbench Visualizer
Templates
Triggers
Injects
Inject Editor
Map Display
Event-based
HTTP
Inject Flows
Alert Management
Inject Flow Editor
Time-based
JMS
Inject Groups
Inject-Response Tagging
SOAP
Injects-Response Matching
UDP
Logging
External Interfaces
Outgoing Injects
Application
Regular Expression
Data Store
Incoming Responses
Manual
Database
XML
AAR
Logger
Simulation
Automated
Database
24
Expected Mode of Operations
CCIS
Injects Engine
1.
Sim
Injects Engine
2.
CCIS
Sim
3.
Injects Engine
25
Injects Engine - Workbench
26
Sample Event Flow
ltEventFlow version"0.9" descBombing of
Shopping Centre"gt ltNodeSetgt ltNode
backColor"808080" id"AutoID 4"
shape"rect" textColor"" x"246"
y"146"gt ltDatagtNew Inject 4lt/Datagt ltTriggers
gt ltTrigger type"event" value"New Inject
5"/gt lt/Triggersgt lt/Nodegt ... lt/NodeSetgt ltE
dgeSetgt ltEdge source"AutoID 1" target"AutoID
2"/gt ... ltEdge source"AutoID 4"
target"AutoID 2"/gt lt/EdgeSetgt lt/EventFlowgt
27
Relevant SISO Works

• Battle Management Language (BML)
• As more C2 systems adopt C2IEDM, adopting BML
  shall enhance semantic interoperability between
  Sim and C2 environments
• Base Object Model (BOM)
• Captures single thread of simulation interplay,
  identifying the participating HLA objects

28
Questions