Common Object Framework

1
A Common Object Framework for Distributed
Intelligence Processing
George Green Space and Naval Warfare Systems
Center January 13, 1999
2
Common Object Framework

• Vision
• Architecture
• The Common Object Framework
• Implementation
• Credits

3
Vision

• Interoperable and Integrated

4
UNCLASSIFIED
National Systems Data
Mission Planning
Interoperability The ability to use external
data and pass it between applications while
maintaining the semantics of the data
Historical Data

• In the same computer
• Across the network
• Written in different languages and environments

Organic Sensor Data
Threat Analysis
5
Integrated Applications
Mission Planner with ELINT
SPOT Imagery with ELINT
Common Object Framework (COF)
Object Request Broker (ORB)
DCW Map with ELINT
6
Vision

• Interoperable and Integrated
• A World of Components (Plug n Play)

7
A Typical C4I System
8
Vision

• Interoperable and Integrated
• A World of Components (Plug n Play)
• Incremental Acquisition

9
Vision

• Interoperable and Integrated
• A World of Components (Plug n Play)
• Incremental Acquisition
• Ultimately, systems that are scalable and
  reconfigurable and well-integrated and
  distributed and acquirable!

10
Architecture

• CORBA Backbone
• Interface Reuse -- Common data exchange and
  control interfaces

11
Interface Reuse
Shared data and control interface
Traditional Integration
Characteristics Incremental pairwise
integration leads to O(N2) interfaces
Although built with components, complexity of
dependencies renders this a monolithic system,
thus... Large lifecycle costs Resistant to
new technology
Characteristics Faster integration Improved
encapsulation O(N) interfaces -- one adapter
per application Common data exchange and
system control interfaces. Credits to Tom
Mowbray and DISCUS
12
Architecture

• CORBA Backbone
• Interface Reuse -- Common data exchange and
  control interfaces
• Self-describing data
• Functional autonomy
• Necessary for scalability
• Example persistence

13
Common Object Framework

• COF is an architecture that specifies interfaces
  for common services and methods for integrating
  distributed applications.
• And, COF is a framework which provides services
  and libraries for systems integrators to build
  intelligence systems from new components and
  legacy applications.

14
Common Object Framework Technical Overview
System Application Layer
Provides mechanisms that allow objects
and components to be grouped into a C4ISR system
Provides mechanisms that control the flow of
information between components in a system
Control Layer
Provides mechanisms that allow components to
communicate information in a flexible fashion
Transport Layer
Provides software that allows easy integration of
applications into COF environment
Tools Objects
15
Common Object Framework Transport Layer
Provides mechanisms that allow components to
communicate information in a flexible fashion

• Opaque message handlers
• Utilize CORBA sequence of Anys
• Self-describing
• A Handler for data and commands
• Table based abstraction
• Multiple objects per transaction
• Cached table schema
• Transformation Mechanisms
• Supports building native C Objects
• Distributed environment via use of CORBA

CORBA Sequence of Anys ,Value, ...
16
Common Object Framework Control Layer
Provides mechanisms that control the flow of
information between components in a system
Registration Models
SINK
?
?
M
S
C
- Manager informs server which client to connect
to - Server send all data

• Provides mechanisms to define relationships
  between components
• Data Registration
• Selective by subobjects
• Flexible models (SINK, SOURCE, TAGGED)
• Provides control mechanisms
• Component Control (Start, Stop, Pause, Status)
• Process Monitoring
• Provide mechanisms to discover the data
• Metadata (i.e. data about data)
• Object Definitions
• Contacts (ELINT, RIT, COMINT, IR)
• Tracks (PICES, TIBS, IR)
• Routes

SOURCE
?
M
C
?
S
?
- Manager informs client which server to register
to - Cleint sends registration to server - Server
sends data
TAGGED SINK
?
M
S
?
C
?
C
- Manager informs server which clients to connect
to - Server sends data to multiple clients
17
Common Object Framework Control Layer
Naming and Trader Services

• Naming Service
• Maybe youve noticed a conflict between CORBA
  and a Common Interface approach -- all objects
  have the same signature!
• Part of removing dependency on proprietary
  Implementation Repository
• Even identical servers cannot be treated as
  equivalent -- and that distinction is best
  managed in the server rather than externally
• A necessary facility for dynamic
  reconfiguration.
• Trader Service
• The next step toward dynamic reconfigurability
• Will allow end user control of data sources
  and shared data areas.

18
Common Object Framework System Application Layer
Provides mechanisms that allow objects and
components to be grouped into a C4ISR system

• Provides models for data sharing and
  interoperability
• Problem Sets
• Publish Subscribe
• Arbitrary configurations
• Information Filtering
• Provides a set of management functions
• System Manager
• Problem Set Manager
• Style Tool
• Filter Tool
• Data Store
• Façade for underlying DBMS
• Cross platform
• Sun Solaris
• Windows NT

System Parsers Storage Correlators
Problem Set
19
Common Object Framework System Application Layer
Problem Set Model Sharing Display State
Problem Set Manager
SYSTEM
Data Store
Image
Problem Set
20
Common Object Framework System Application Layer
Publish Subscribe Model
Manages heterogeneous named objects Distributes
within and across problem sets Updates are pushed
to subscribers Subscriptions and updates
maintained across activation of author or
subscriber
Publish Subscribe Server
Mission Planner
Route Server
Register as author of object -
Create/Modify/Delete - Set Modify
(Read/Write/Notify)
Register as subscriber - Gets List of Available
Objects - Subscribe to object by name -
Receive through COF exchange interface
Aggregate (Problem Set)
Tool
Tool
Tool
21
Common Object Framework Tools and Objects
Provides software that allows easy integration of
applications into COF environment
IIOP

• Wrapper Technology
• CFApp
• Standard set of common methods used by
  applications to operate in a COF environment
• CFAccess
• Library of C representation of COF Objects
• GenXMap
• Standard set of common methods used by Map
  applications to operate in a COF environment
• Facilities
• Metadata
• Style
• Filters

Legacy Application
CFAccess
CFHandler
CFCommand
Custom Logic for Legacy
Externally Accessible API
CFApp Wrapper
In-process API Network RPC Sockets
22
COF Plumbing 101
UNCLASSIFED
TIBS Tracks
PICES Correlator
Track Manager
TREM
TDIMF Parser
TERPES Correlator
MATT - TDDS - TIBS
Tracks
Tabular Parser
TRE - TADIXS B
Data Store
Contacts
Metadata Service
Contacts SIGINT ELINT COMINT
Tracks Routes Weather
Position
File
Re-ID
GPS
Naming Service
STRS
Filters
Problem Set
Aggregate
Contacts Tracks Routes Symbology Display
Attributes
Style
Mission Planners
PFPS AFMSS MPS
Table Tool
23
Partnerships
OSO
Object Oriented Integration Requirements
Configurable
Scalable
Plug Play
Technology
IW
CORBA
SSC-SD NIMA/SR NSA
Battlespace Awareness
COF
DISCUS
Common Frame
SOCOM SWC
Targeting
Applications
Mission Planning
AFSOC/DOX
Mission Requirements
Operations
24
Contacts

• George Green, ggreen_at_spawar.navy.mil,
• [phone], DSN 553-4054
• Trudy Morgan, trudy_at_spawar.navy.mil,
• [phone], DSN 553-6554
• Address

SPAWARSYSCEN SD CODE D73C 53560 Hull Street, San
Diego, CA 92152