XMSF XC2I Web Service Architecture

1
XMSF XC2I Web ServiceArchitecture
General Dynamics AIS
2
XC2I Services

• Introduction
• Project update
• Communications
• Authorization / Access control
• Order of battle
• Symbols (2525B)
• 3D models
• Terrain
• Weather

3
XMSF XC2I IntroductionUpdate
General Dynamics AIS
4
Generalizing Communications

• Must be able to abstract the communications
  specific parts away.
• HLA uses a publish / subscribe paradigm
• Distinguish between objects, reacts to attribute
  changes
• HLA uses regions to split up the play field and
  reduce network traffic
• DIS blasts Protocol data units (PDU)
• Other data sources with specific protocols

5
Generalizing Communications

• What do we want to hide?
• Programming API
• Data structures
• Methods and procedures specific to the protocol

6
Generalizing Communications

• Authorization Access control
• Shared services
• Both are visible only to other services.
• The APIs are not exposed to the outside world.
• XMSF partners still experimenting!

7
Generalizing Communications

• One Conceptual model to unify the battle space
• Many simple and highly configurable information
  services
• Utilize cascading services to supply information
  reduction / filtering

8
XC2I Visual Solution

• Area of interest
• A view box metaphor
• Display command hierarchy
• Display A B company, for example.
• By type
• Kind or broad class of entity

9
XC2I Web Service Parts
Component
Broker
I/P
I/P
I/P
HLA
DIS
C4I

• Broker handles component access
• Info Provider (I/P) handles specific protocols
  (HLA, DIS, ), aggregation

10
XC2I Web Service Architecture
Broker
I/P
I/P
I/P
I/P
I/P
JCATS
JSAF(s)
Clutter
JCATS
11
XC2I Web Service Architecture
Broker
I/P
I/P
I/P
I/P
I/P
I/P
I/P
JSAF(A)
JSAF(M)
JSAF(NF)
DIS (AF)
12
XC2I Web Service Architecture
Vis Comp.
UDDI Repository
Broker
request
Broker addr
XC2I request
LC2IEDM formatted info
13
XC2I Request Language

• The XC2I request language
• Authenticate
• Alloc Broker
• Interest Expression
• Interest by spatial volume - viewbox
• Interest by echelon whole or partial tree
• Interest by entity type part of cmd / ctl

14
XC2I Web Service Architecture
Vis. Comp
Broker
I/P Factory
Info Prov.

Config a provider
! Broker I/P handshake
Recv info from provider
Reformat and send to comp.
15
XC2I Request Language

• The Component sends an interest expression.
• ltinterestexpressiongt     ltviewboxgt        
  ltposition lat30.720 lon-98.588/gt        
  ltposition lat31.720 lon-97.588/gt    
  lt/viewboxgt lt/interestexpressiongt

16
XC2I Request Language

• ! The Broker and Info Provider exchange addresses
  and agree to data formats
• Data flows from the I/P toward the Broker.
• The I/P is reconfigurable
• Or the Broker can just call the factory for a new
  setup.

17
XC2I Web Service Architecture
Broker
I/P Agg
I/P
HLA
Change of interest
Change subscription
Lots of new data
Entity level
Aggregated
18
Command Hierarchy

• Unit order of battle
• How are the forces equipped?
• How are the forces currently deployed
• Discovered from the simulation engine

19
XC2I Solution

• XC2I currently utilizes
• JSAF echelon db
• JCATS namegen
• XC2I does not maintain a dynamic data base yet.
• Maybe something will fix us (XBML?)?

20
XC2I Unit Order of Battle
Visualization Object Caching
echelonDB
Config Data
Broker Info Provider(s)
Low level Sim
21
Symbols

• Use MIL Std 2525B symbols.
• Symbols need to be scalable

22
XC2I Web Service Architecture
Visualization Object Caching
2525B Symbols
Broker Info Provider(s)
Low level Sim
23
XC2I Terrain Service

• Terrain
• SEDRIS STF
• Cultural Features
• Too much data to push thru the web right now!

24
XC2I Web Service Architecture
Visualization Object Caching
SEDRIS STF
Broker Info Provider(s)
Low level Sim
25
Open Questions

• What other info could be surfaced as a Web
  Service?
• Should the Command Hierarchy/UOB be surfaced as a
  service?
• Who cares about maintaining dynamic attrition
  totals?
• How many people care about weather effects now?