defense & space electronic systems military data link
TRANSCRIPT
2
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Military Data Link Integration Application (MDLIA)
James T. Sturdy
Honeywell InternationalDefense and Space Electronic Systems
9201 San Mateo Blvd., NEAlbuquerque, NM 87113-2227
(505) 828-5703 Office(505) 828-5500 Fax
3
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Military Data Link Integration Application (MDLIA)
A flexible, scalable, modular, low cost solution.
A unique integration approach providing a common solution to interface new tactical data link radios with
legacy military equipment and systems.
An implementation that allows military users to customize message processing on each unique platform
through user modifiable instructions.
4
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
The ProblemThe Problem• Network Centric Warfare Initiatives
– Driving standardization in C4ISR messaging– Link-16 has been designated as the primary tactical data link– Over 27,000 platforms are being upgraded
• Joint Tactical Radio System– Next generation data link terminal– Will be installed on numerous platforms– Will require integration with legacy subsystems (Displays,
Communications, Mission Systems)
• MIL-STD-6016B Message Set– Defines the complete tactical data link J-Series message set– Numerous legacy platforms either
Don’t implement any J-Series messages, or theyImplement a limited set of J-Series messages
5
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Bottom LineBottom Line• Military users are concerned about the high cost to
upgrade legacy subsystems (based on existing stove-piped approaches and dependence on traditional primes)
• A modular and common upgrade approach will save money
• A solution that gives users control over changes will reduce the cost of future upgrades as military data link message sets evolve
6
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Military Data Link Platform ImpactMilitary Data Link Platform Impact
•Platform data based on DoD C4I Joint Tactical Data Link Management Plan•An estimated 270 unique platform types•Traditional point solution integration costs are very high•A common integration solution (i.e. MDLIA) will result in an ~80% cost savings
0
5000
10000
15000
20000
25000
30000
1996
1998
2000
2002
2004
2010
Plan
ned
Upgr
ades
TOTAL PLATFORMS
NUMBER J-SERIES (J,VMF, 22)
7
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Common Solution OverviewCommon Solution OverviewUMI
DATABASE
CommunicationsSubsystems
LegacySubsystems
DATA LINK MESSAGEPROCESSING
Ground BasedSoftware Tool (GBST)
Data LoaderCartridge
MESSAGEPARAMETERDATABASE
HOST APPLICATIONS PROCESSOR
LEGACY I/OMODULES
HOST COMPUTER MODULE INTERCONNECTS
LEGACY IPM
MISSIONAPPLICATIONS
DATA LINK PLATFORMINTEGRATION
HOSTPLATFORM
CONFIGURATIONDATABASE
Legacy I/O
Link 16Messages
Legacy I/O
MDLI APPLICATION
MDLIA software hosted on an existing applications processor
User modifiable data prepared on a office computer
8
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Major FeaturesMajor Features• A flexible, scalable & modular solution• Common approach
– Versus traditional stove-piped solutions (i.e. different solution for each platform)
– Gives military control over each platform configuration and subsequent changes
• Integrates legacy subsystems– Can be integrated into legacy host computer as a module or
software partition– Provides automated I/O configuration control through API
database– Provides standard video output for flexible data link display
formats
9
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Major FeaturesMajor Features• Is based on the current civil CMF software application
– Model-based design and database-driven customization– Modified to implement the full data link message set and
tactical data link terminal interfaces– Modified to implement tactical data link legacy I/O interfaces
in a user modifiable database– Modified to to implement user customization capabilities for
the data link message set in a user modifiable database– Expanded to add special message processing functions– Scalable for use in multiple configurations
10
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Implements Full Data Link Message SetsImplements Full Data Link Message Sets• Integrates message subset implemented by legacy
applications• Provides additional message processing for
messages not implemented by legacy applications• Allows users to define specific message processing
with instructions database• Allows users to create specific display data/formats
with instructions database• Allows users to specify specific message routing with
instructions database
11
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Implementation Implementation -- LinkLink--16 Example16 Example
Joint TacticalRadio System
MultifunctionInformation
Distribution System
Joint TacticalInformation
Distribution System
Others
DATA LINK MESSAGE PROCESSINGImplements full Link-16 message set with processing rules and special message functions
EncodeMessages
DecodeMessages
Link-16 MessagesAutomatically
ConfigurePlatform
Interfaces
DATA LINK PLATFORM INTEGRATIONManages interface to legacy systems and applications and implements special platform functions
HOST PLATFORMCONFIGURATION
DATABASE
UMI DATABASE
Legacy I/OAutomatically
ConfigurePlatform
Interfaces
Rules and Instructions forUnique Host Platform Requirements
Display Subsystem
Crew InterfaceDevices
Mission Applications
Data Loader
MESSAGE PARAMETERDATABASE
Message 1 Parameters
Message 2 Parameters
Message 3 Parameters
Message n Parameters
RoutingInstructions
MessageProcessingInstructions
Data CollectionInstructions
Platform Application Instructions
Display FormatInstructions
Comm Equipment
Displays Equipment
Mission Equipment
Platform Unique
Standard Message Processing andLink-16 Network Management Rules
per MIL-STD-6016
SPECIAL MSG FUNCTIONS
Data Fusion,Track Files,
Shared SituationalAwareness (SSA),
User Defined Operations,Growth Functions
Other
DataLoader
Updates
UMI DataLoader
Updates
Controland
StatusExchange
SPECIAL PLATFORMFUNCTIONS
Display ApplicationsMission ApplicationsGrowth Applications
Message HandlingInstructions
Platform Instructions
PlatformConfigurations
PlatformConfigurations
Message Parameters
Message Parameters
MILITARY DATA LINK INTEGRATION APPLICATION
EncodeData
DecodeData
LegacySubsystems
CommunicationsSubsystems
12
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Civil CMU (ARINC 758) ImplementationCivil CMU (ARINC 758) Implementation
VHF Data Radio
INMARSATSATCOMEquipment
HF Data Radio
DATA LINK MESSAGE PROCESSINGImplements ACARS and ATN message sets with processing rules and special message functions
EncodeMessages
DecodeMessages
ACARS/ATN MessagesAutomaticallyConfigure to
PlatformInterfaces
DATA LINK PLATFORM INTEGRATIONManages interface to legacy systems and applications and implements special platform functions
HOST PLATFORMCONFIGURATION
DATABASE
AMI DATABASE
Subsystem I/OAutomaticallyConfigure to
PlatformInterfaces
Rules and Instructions forUnique Host Platform Requirements
Display Subsystem
Crew InterfaceDevices
End Systems
Data Loader
MESSAGE PARAMETERDATABASE
Message 1 Parameters
Message 2 Parameters
Message 3 Parameters
Message n Parameters
RoutingInstructions
MessageProcessingInstructions
Data CollectionInstructions
Platform Application Instructions
Display FormatInstructions
Comm Equipment
Displays Equipment
End Systems
Platform Unique
Standard Message Processing andNetwork Management Rules
for ACARS and ATN
SPECIAL MSG FUNCTIONS
ATC Functions,AOC Functions,
Data Management,FIS Functions,
Gatelink Functions,User Defined Operations,
Growth Functions
DataLoader
Updates
AMI DataLoader
Updates
Controland
StatusExchange
SPECIAL PLATFORMFUNCTIONS
Display ApplicationsEnd System Applications
Growth Applications
Message HandlingInstructions
Platform Instructions
Configurations
Configurations
Message Parameters
Message Parameters
COMMUNICATIONS MANAGEMENT UNIT / COMMUNICATIONS MANAGEMENT FUNCTION
EncodeData
DecodeData
LegacySubsystems
CommunicationsSubsystems
13
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
Multiple Implementation ConfigurationsMultiple Implementation Configurations• Can be hosted as a software partition in a legacy host
processor• Can be provided on a GPP and hosted in a legacy
host computer• Can be provided on an IPM and hosted in a legacy
host computer• Can be provided in an integrated system
14
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
MDLIA with GPP HostMDLIA with GPP HostLEGACY IPM
DISPLAY SUBSYSTEM
LINK 16 DISPLAY FORMAT(s)
COMMUNICATIONSSUBSYSTEM
(JTIDS, MIDS, JTRS)
LINK 16 MESSAGES
GBST
DATA LOADER
DATABASE UPLOADS
MISSION RECORDING DATA
DATA LOADER CARTRIDGEINTERCHANGE(i.e. PCMCIA or equilavent)
LEG
AC
Y I/O
MO
DU
LES
HOST COMPUTER MODULE INTERCONNECTS
DATALINK MESSAGEPROCESSING
LEGACY APPLICATIONSPROCESSOR
LEGACYMISSION
APPLICATIONS
GPP PROCESSING HOST
DISPLAY SUBSYSTEM I/O
UMI DATABASE
DATA LINK MESSAGEPROCESSING
MESSAGEPARAMETERDATABASE
DATA LINK PLATFORMINTEGRATION
HOSTPLATFORM
CONFIGURATIONDATABASE
MDLI APPLICATION
Hosted on a General Purpose Processor (GPP) module
15
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
MDLIA with IPM HostMDLIA with IPM Host
DISPLAY SUBSYSTEM
LINK 16 DISPLAY FORMAT(s)
COMMUNICATIONSSUBSYSTEM
(JTIDS, MIDS, JTRS)
LINK 16 MESSAGES
GBST
DATA LOADER
DATABASE UPLOADS
MISSION RECORDING DATA
DATA LOADER CARTRIDGEINTERCHANGE(i.e. PCMCIA or equilavent)
VID
EO M
EZLE
GA
CY
I/O M
OD
ULE
S
HOST COMPUTER MODULE INTERCONNECTS
LEGACY APPLICATIONSPROCESSOR
LEGACYMISSION
APPLICATIONS
IPM PROCESSING HOST
DISPLAY SUBSYSTEM I/O
UMI DATABASE
DATA LINK MESSAGEPROCESSING
MESSAGEPARAMETERDATABASE
DATA LINK PLATFORMINTEGRATION
HOSTPLATFORM
CONFIGURATIONDATABASE
MDLI APPLICATION
Hosted on a Image Processing Module (IPM) module
16
June 15-17, 20042004 CCRTS, Track 4 - C4ISR/C2 Architectures
BenefitsBenefits– Common scalable design that can be used on multiple unique
platform types to reduce integration costs by ~80%– Data link message set is user programmable without the need
to modify/recompile the operational software– API database allows I/O re-configuration to legacy
subsystems without the need to recompile the operational software
– Implements full message sets where each message can be activated or deactivated within the MDLIA, or allocated to legacy applications (if implemented previously) through the instructions database
– Provides standard display system interfaces and video outputs to support flexible and user programmable data and/or display formats
– Utilizes ground based software tool to create the message set instruction database