Title: Goals for the IO Tiger Team
1Goals for the IO Tiger Team
- Inform technical community of uses of DIS in
information operations at 505EXS - Describe current customizations of DIS to
support IO at Hurlburt Field - Propose updates to the DIS standard to better
represent IO - Define the responsibilities of models and their
databases designed to represent IO - Open discussions on better representations of IO
in DIS or HLA exercises
2ACRES/IWEG/DCE Concept of Operations
3
3WHAT IS BEING DONE Support to Information
Operations (IO)
- ACRES/IWEG/DCE supports IO
- By building the transmitters which represent the
physical links nodes necessary for OPFOR
entities to communicate - OPFOR units can be represented within DCE
- DCE characterizes communications nodes not
represented by other sims - DCE owns and operates unit entities
- OPFOR comms can be ghosted onto other units on
the DIS LAN - Transmitter locations determined by entity states
from other sims - OPFOR civilian military telecomm infrastructure
consists of many physical transmitters to connect
two units - Similar representation as individual transmitters
- Transmitter/Signal PDU sent for each physical
hop required to transport conversations or
other data exchanges - By injecting OPFOR conversations into the
exercise which are propagated across comms model
defined routes - Modeled transmitters produce Transmitter/Signal
PDU pairs for each conversation inject they must
pass on a physical comms path
4Support to IO ltcontgt
- ACRES/IWEG/DCE supports IO
- By monitoring battle damage assessment reports
and updating comms enviroment status as battle
progresses - Comms routes are changed as nodes are destroyed
- By providing real-world data to allow SIGINT
analysts to use their real-world GALE or JDISS
systems to derive OPFOR command structures,
locations via external reports - ACRES IBS Tab 37 formatted external parameter
reports - By providing completed SIGINT analysis products
to provide OPFOR intent - ACRES USSID KLEIGLIGHT END PRODUCT Reports
5SUMMARYDIS Changes to Support IO
- Transmitter PDU Updates
- To better represent modern communications devices
- New Signal PDU User Defined Protocols
- To better represent types of communications
needed between simulated entities - New PDU Needed to Change Comms Links Status
- To inform models of the status of communication
routes in the comms model
6Transmitter PDU
- Transmitter PDU Updates
- Extend Radio Entity Type Enumeration List
- Need more enumerations to represent OPFOR comms
devices - Enumerations should be arranged hierarchically by
some internationally recognized standard - Extend Modulation Enumeration List
- Need more to represent modern comms devices
- Define New Attribute and Enumerations for
Multiplexing - Also needed to represent modern comms devices
- Could be added to 16 bit Padding between input
source and antenna location - Bandwidth specified in MHz Not specified in IEEE
1278 - Extend Crypto System Enumeration List
- Transmitters can impart additional encryption on
signals as they traverse a physical route
7Excerpt from Proposed Radio Entity TypesAdditions
8Proposed Radio Entity Types
- Radio Entity Type consists of 6 fields
- Kind, Domain, Country, Category, Nomenclature
Version, Nomenclature - For IO Kind, Domain, Country are fixed to
71222 by 505EXS tradition - Domain or Country could be changed for future
needs - Category field used to denote Line or RF
Transmission - Land Line 1 (cable or fiber)
- RF 2
- Use the Nomenclature Version and Nomenclature
fields to specify comms devices
9Proposed Radio Entity Types
- 3 Land Line Nomenclature Versions
- 26 RF Nomenclature Versions ranging from VLF
(3KHz) EHF (3000GHz) - Based on Manual of Regulations and Procedures for
Federal Radio Frequency Management - Published by the National Telecommunications and
Information Administration (NTIA) of the U.S.
Department of Commerce (Dated January 2004) - Use Nomenclature field to determine whether or
not Transmitter PDU data has been enhanced by
IWEG/DCE - 0 means the comms device is a generic version
from the general version specified by the
Nomenclature Version - Non-zero specifies a specific comms device model
10Transmitter PDU ltcontgt
- Need plan to represent complex Multiplexing
schemes - Could be added to 16 bit Padding between input
source and antenna location - Could be derived from the type of transmitter
device and a given Modulation enumeration - Multiplexing is currently represented within the
Modulation Attributes System Field
11Signal PDU
- New Signal PDU User Defined Protocols
- Used by 505EXS models since JEFX 2000
- Type 30 Signal PDU for simulating Integrated Air
Defense Systems (IADS) perceived truth - Type 31 Signal PDU for IADS Command and Control
- Type 35 Signal PDU for simulated voice or text
comms - Used by 505EXS for ACRES Reporting
- Type 7200 Enhanced Signal PDU for COMINT
reporting
12Communications Link Status Change PDU
- New PDU Needed to Change Comms Links Status
- Propose Communications Link Status Change PDU
- Announces a change to the functional status of a
route (logical links) to either down or available - Final format is TBD
- Detonate PDU currently used with custom field
interpretations - Firing Entity Id IWEGs Site App ID
- Target Entity Id Transmitter Nodes Entity Id
- Munition Id Receiver Nodes Entity Id
- Burst Descriptor
- Munition Type Fixed "2122552222"
- Warhead Transmitter nodes Radio Id
- Fuse Receiver nodess Radio Id
- Quantity 1
- Rate Link down 0 link up 1
- Detonation Result 3 (ground impact)
13BACK UP SLIDES
- Additional Info if needed
14ACRES/IWEG/DCE Data Flow at 505CCW/EXS (Hurlburt
Field)
505CCW/EXS, Hurlburt Field
DIS SCI LAN
Offut AFB
JWICS Output Data Flow
RJMT
E-mail KL/ENP COMINT
Socket Tab 37 COMINT, ELINT HTTP Client
Requests to web servers
ACRES
Switch
JWICS Input Data Flow
DIS PDU
Analysts access web pages needed for SIGINT
reporting.
KG
DB
CAOC-N
- IWEG DCE Entity State/ Transmitter/ Signal
PDUs (7200)
Switch
Ft Meade
DB
DIS Secret Collateral LAN
DCE
IWEG
DIS PDU
JWICS Output/Input Data Flow
Comm Model status is available to controllers and
analysts.
- DICE Entity State/ Transmitter/ Signal
PDUs (30, 31, 35) - AWSIM other Entity State PDUs
Radiant Mercury
DIS Only
15ACRES/IWEG/DCE on the DIS LAN
DIS LAN
IWEG
Entity State PDU Owns transmitter Can be owned
by other simulation.
Transmitter PDU Entity Id Radio Id Radio Entity
Type Transmit State Antenna Location Frequency Pow
er Bandwidth MHz Modulation Type Crypto System
Signal PDU Entity Id Radio Id Encoding
Class Encoding Type TDL Type Data Length Data
User specified type Info content
Language Call Sign
ACRES
OPFOR UNIT A
TX/Signal
TX/Signal
TX/Signal
From
Conversation Injects
TX/Signal
TX/Signal
OPFOR UNIT B
To
DCE Network Model
16ACRES/IWEG/DCE Feedback
- ACRES has introduced an entirely new dimension
into the constructive environment significant
volumes of high fidelity, timely SIGINT are being
introduced into the CAOC decision cycle. The flow
of SIGINT information was very comparable in
quality and quantity to that which he had
witnessed in live contingency operations. - - Col (ret.) Chris Christon, CAOC-Nellis JEFX 04
Senior Mentor - We could not have done our job had it not been
for the robust KL reporting from ACRES. The most
impressive thing was the way the KLs matched up
with the external data - - TSgt Kyle Ross, JEFX 04 CAOC-Nellis
Cryptologic Support Group Lead
9