IXO Architecture

1
IXO Architecture
Composer
Knowledge Base
Pattern
Battlefield
JessKB
Search
Feature
Process Model
Signal
Web Service
GUI
Match
Target
Sensor
DB
SOAP WSDL
Target
Publish SML Instances
Mission
Sensor
Publish DAML-S Instances
Shooter
Acoustic Sensor
Query
Data
Tracking Application
Web Service
F5
SOAP WSDL
Intelligence Database
N7
F2
F4
N1
Other Applications
Query
N5
N2
N9
P2P Net JXTA
Fuselet Pool
Upload Fuselet
2
TRAFEN A Generic Fusion Engine
Application (GUI)
Composer KB
Message Content? Topics? DAML/XML
Agent 1
S
Event Subscribe
Hypothes. Storage
Engine
MOM Message Oriented Middleware
Agent 2
Topics?
S
TRAFEN Main Loop
MHT Algorithm
Config. Manager
Semantics?
S
Event/ Message
JMS
Prediction Model
Agent N
Event Publish
S
IXO Battlespace
Plug-in or Remote Model Server
Events
Distributed IDS, ICMP
Engine
Models?
Intelligence Analysis etc
Data-Driven
Event-Driven
Signal Processing
Feature Extraction
Pattern Identification
Sensors
Decision
3
JMS Message

• JMS Header
• JMS Body
• // DAML
• Topics
• Observation
• Target
• State
• Timestamp
• Source
• //Complex Type

Message
Header
Body
Source
Time
Topics
Observ.
Target
State
4
Message Body Schema

• ltrdfRDF
• xmlnsdaml"http//www.daml.org/2001/03/damloil
  "
• xmlnsrdfshttp//www.w3.org/2000/01/rdf-schema
  
• xmlnsob http//actcomm.dartmouth.edu/observat
  ion.daml
• gt
• ltdamlClass rdfIDMessage/gt
• ltdamlObjectProperty rdfIDStategt
• ltdamldomain rdfresourceObservationgt
• ltdamlrange rdfresourceobStategt
• lt/damlObjectPropertygt
• ..

.
ltdamlClass rdfIDState/gt ltdamlDatatypeProper
ty rdfID Longitudegt ltrdfsdomain
rdfresource State/gt ltrdfsrange
rdfresource "http//www.w3.org/2000/10/ XMLSchem
astring"/gt lt/damlDatatypePropertygt
.
State Schema
Message Schema
5
Pub/Sub

• Topics
• Hierarchical Topics for Pub/Sub
• Semantic MoM with DAML/XML Pub/Sub with DAML
  description instead of topic keywords
• JMS doesnt include topics in the message.
• Target
• Inheritance? If no exact model founded, use upper
  level prediction model? E.g. Tank -gtTank72
• Military.Weapon.GroundVehicle.Tank.Tank72
• Semantics
• Event sources and Engine have to share the
  standard ontology
• Add some flexibility

6
Dynamic Parsing and Loading

• Have experience in dynamic parsing and loading.
• XML/DAML
• Map the event data to prediction or comparison
  routines
• Assume the sequence of order, I.e. Engine
  prediction model Event Data has to share the
  same sequence order of inputs.
• Need some brilliant ideas.
• Need detailed design Main Loop

7
Team

• Wayne Main Loop, Parsing, Loading
• Yong Topics Message Schema, Paul
• Han Pub/sub, Mom
• Diego IXO application
• Jiang Coordination and work on all above.
• We can do it as long as there is free pizza!!!!!