Homeland Heart_Beacon Interoperability, Synergy & Synchronicity SOS Consistent, Synchronous Time stamping of raw data 1 2 Unified Alert Scheme CAP XML Enable over N complex systems Y major contracts e.g., NETWORX & Z organizations Get from Send to Publish-Subscribe Subnet meta data Multicast radius Increase / decrease with alert condition 3 4 5 Sea Gull UC Berkeley Common Symbology - child schemas - data islands - data files INTERNATIONAL BEACON NETWORK SWAN Island RAINS 1 Unified Alert Scheme IPSAN NATIVE AMERICAN DISASTER NETWORK
16
Embed
Homeland Heart_Beacon Interoperability, Synergy & Synchronicity View mnesterpics' mapTaken near Dare, North Carolina (See more photos here)more photos.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• TCP/IP stack sub protocol used in Infrastructure failover
• Publish/Subscribe: get from/send to platforms on subnet
• FBCB2/BFT, Land Warrior, FCS, MUOS– Subnet filename, MCG filename, UNIT
URN, UTO version, Local IP – Gathers subnet & state data for “heartbeat”
message updating router MIBS adds & joins
• E9-1-1 Telco regulations NENA/APCO
• AT&T’s Heartbeat Solution• Sony Ericsson Heartbeat Suite• Mesh network protocols e.g., Zigbee,
Zwave, sensor networks• NASA/JPL OpenDAP data availability
anywhere, any format• Eaton “Home Awareness System”
RFID PKI, social awareness systemse.g., 211, 311, 411, 511, 611, 711, 811 & e9-1-1 = Heartbeat Beacon
Server failover e.g., HP Serviceguard
Service Oriented ArchitectureSOA system wide heartbeat for app /system availability (DISA GIG)
Network subnet type of DISA’sHorizontal Fusion Publish-Subscribe
3
Heartbeat• The Heartbeat is a sub-protocol of the TCP/IP (Internet) stack that is as old as the internet. It is
usually referred to for system failover operations.
• The Heartbeat function in this context is NOT about network timing using Loran-C or newer cesium / quartz crystal timing mechanisms although a central timing pulse from Cheyenne Mountain is essential to synchronize data harvesting and data propagation over grid
• The Heartbeat function IS simply an opportunity in time to gather (state meta) data from internet devices that is then used to adjust the internet infrastructure.
• The military (having developed the internet stack in the first place (DARPA / Mr. Al Gore...); knew that there were unused opportunities in time (unused data frames) to move data via heartbeat mechanism to folders, queues, caches, folders… then to system administrators via the structured military K00.99 “Heartbeat Message” – . - .. -- .. beep beep…. beep beep…
– The developers of FBCB2/Blue Force Tracking exploited this (to this day) arcane knowledge in developing
what is call the "template system" (actually there are 7 - 64 of them as briefed to congress) by several different 4 star generals.
– Protocol gurus (geeks) refer to the heartbeat / beacon interchangeably or even together i.e., heartbeat / beacon / heartbeat beacon…. Decision makers avoid these geeky discussions by any means necessary.
• Point being, working together on an apples to apples, oranges to oranges level involves using opportunities in time to CHOOSE / CHANGE our (telecommunications) matrix to help each other in a consistent, synchronous, synergistic method across systems, networks, agencies, federal, state, local, Tribal, international / sub-terrainian, ocean floor, intergalactic...
4
Bea
con
Tra
nspo
nder
Tec
h
ADS-B: Automatic Dependent Surveillance – Broadcast: ADS-B messages include fields for avionics self-reporting of the integrity of ADS-B position information & proximity alerts
Boston University Project Beacon : A Network Diagnosis Toolkit used to actively monitor network conditions concurrently operated by a set of collaborating endpoints. Features radius of three areas / zones
Cell Broadcast: one-to-many geographically focused messaging service contrasted with Short Message Service - Point to Point (SMS-PP) as a one-to-one and one-to-few service,. Cell Broadcast messaging is supported by UMTS defined by 3GPP.
FLUX Beacon: A Forensic Time Machine for Wireless Networks: monitoring infrastructure for forensic data collection, storage and analysis. Records & retrieves traffic signatures and environmental observations as a source of network evidence.
FusionNET: Unique Data Replication & Data Synchronization Technology to Support Military Operations in Extreme Networking Environments developed by and for the 18th Airborne Corps that allows commanders to collect, access &disseminate mission-critical data to and from the field via PeerDirect data replication & synchronization solution by Progress Software Corporation
MESA: “The FEDEX of military communications systems” relay and receives data under the DHS SAFECOM umbrella. Facilitates dependable, advanced, efficient, effective and inter-operable equipment, specifications and applications
MxRRM Radio Resource Management in multi standard environments: Beacon on one system for all, assuming this one has nearly ubiquitous coverage like GSM. Using a priority scheme to define an order how to scan. If there is an incoming call for a user being reachable by more than one network, which one should be used and why?
GM ONSTAR: Originally Project Beacon circa 1994. Telematics, emergency and first responder services for GM’s fleet
RDS: Radio Data System: Displays PSN (Program Service Name) as warning/cost effective means of sending data to large areas
SABRE: Situational Awareness Beacon Response: battle group situational awareness system for beacon-equipped platforms. SABER produces accurate position & platform ID. "intent to shoot" and "friendly ID" query and response mode data
Sea Gull: Server Heartbeat strategy maintains routing & object state using < 1% minimal network resources. Server Heartbeat: “Keep-alive” beacon along each forward link. Increasing period (decreasing frequency) with routing level. Data-Driven Server Heartbeat's “Keep-alive” Multicast increasing / decreasing radius based on intensity, thresholds
Sentinel Beacon System : Command Station & mesh network of rugged PCs processing beacon location / track information. A beacon out of range of the command station data is relay by other beacons.
TXDP: Transducer Data Exchange Protocol: used during 2005 Superbowl by Michigan National GuardUMTS: Universal Mobile Telecommunication System (wireless broadband) heartbeat to track user’s activities e.g., NG NYC metroZIGBEE / ZWAVE: Consortiums supporting heartbeat driven mesh network standards
The continuous adaptation of capabilities relevant to security - in short transformation - in order to meet the security challenges of the information age is well under way regarding the demands of the military. Based on the support of highly developed information technology to speed up the processes of influencing an adversary, new conceptsresult in the adaptation of military doctrine, organization, training, material, infrastructure, interagency interaction, leadership, personnel and facilities.
Efforts to achieve the adaptation are comprehensively described on numerous Internet websites such as those of the United States Joint Forces Command, the Allied Command Transformation and the German Bundeswehr. Core elements of the improvement of capabilities are the concepts of "Network Centric Warfare" in the United States of America, "Network Enabled Capabilities" in Great Britain or "Vernetzte Operationsführung" in Germany.
The key determinants of these network-based concepts are information sharing and collaboration: "Information-sharing and collaboration enhance the quality of information and shared situational awareness. Shared situational awareness enables collaboration and self-synchronization, and enhances sustainability and speed of command."
The widespread use of new Information Communication Technology is intended to enable better exploitation and faster dissemination of intelligence in support of military operations so that political and military decision-making is more authoritative and practical outcomes are more effective. The idea began moving forward from the experimental stage into practical application with "Operation Iraqi Freedom" led by the United States and the United Kingdom against the Saddam Hussein regime early in 2003.
How? Convert battlefield military tactics, tools, & procedures…
O: Maneuver Control Systems (S3) generates & xmits consolidated Unit Task Order (UTO) to TIMS / FBCB2 operator (S6)1. TIMS – Tactical Internet Management System operator populates “Hasty” Reorg Tool” that generates a new UTO with next UTOVersion number, effective Date Time Group and synchronization Time (K00.99 heartbeat message option UTO notification) 2. S6 Sends out initial UTO message. FBCB2 processes UTO notification & sets timer to execute change at effective time3. Heartbeat Process: (TIMS/FBCB2 engine) generates “Heartbeat” message every 15 minutes with the current UTO version. 4A: GTCS – Ground Tactical Communications Server passes heartbeat to state manager (Variable Message Format or VMF)4/5: At effective date/time, All FBCB2’s in multicast group reconfigures database to ensure proper Situational Awareness SA Calculation, new INC (Internet Controller – a router adapted for combat radio interface ) MIBS Management Information Base (common to all routers – military & commercial) & distribution lists / subscription lists in commercial parlance. Operator is promptedTo reconfigure or delay 10 minutes (w/option to change at anytime). When operator OKs, database is rebuilt & network reconfigures6. TIMS generates new Multicast Group (MCG) file, and if required, TOC INC MIBs & TOC router configurations automatically @Effective time. TIMS calls the ModifyMCGInfo API (Subnet filename, MCG filename, UNIT URN, UTO version, Local IP AddressLDAP C2R Server update tool executed as multicast group file, UTO version number & the AIS – Army Information Server e.g.,Server running n supporting processes/apps to connect (will ignore if it already has one set)7. C2R – LDAP Server MCG update tool updates multicast group data on the AIS8. C2R Server recognizes that a UTO has occurred & notifies state manager (SM) if it is there. Else it sends out the SM alert that the State Manager would have sent. C2R server replicates multicast group data to all configured UTO replication destinations.9. GTCS gets SM or C2R server alert, reads updated MCG from C2R then updates internal config file & LAN card if platform affected
C2RServer
MCSManeuver
ControlSystem
Application
0
All FBCB2’sOn current heartbeat
TIMS C2RMCG
Force XXI Battle Command Brigade & Below
Tactical InternetManagement SystemFBCB2 software based
2
ArmyInformation
Server
Multicast GroupUpdate tool
14 5
3 6
LDAPServer
StateManager
GTCS
Ground Tactical Communications Server GOTS Messaging
GTCS
C2RServer
AIS 7
4a
8
9
AISWeb Application Serverw/ business logic /Mission threads
USMTF MIL STD 6040/ADatP-3 / STANAG 5500OTH-T GOLD / OS-OTGVMF / TADIL A, B, J, KADFORMS, XML-MTF, NATO ACP123/STANAGJANAP128 , NICS-TARE
Structured Military Message Formats:
Viewers / Applications /Browsers Schema Tools: Common Alert Protocol (CAP)
Import
XML Tags DDMS & EDXL-DE Message Set Data Autopost/Auto fill
To equivalent.com, .gov, org, edu Communities of Interest // Primary Injection Point PIP profiles, subscriptions using product / system neutral methods / procedures
FormsEngine
TransponderBeacons /
Sensor nets
Convert to XML Schemas
1st application claim area
3rd claim area10/709358
Apply TCP/IP’s universal “heartbeat” mechanism to time the data exchanges from/to platforms of interest by way of IP multicast groups - routers. Configure multi-cast groups / MIBS via commercial vice military tools in commercial development / integration frameworks. Use intrinsic TCP/IP heartbeat beacon frames send to / gather from functions to place harvested data into queue/object store for processing & onward distribution via intelligent agents, bots, protocols i.e., SSTP, mesh network, ZigBee, Zwave, TDXP, Telematics, OnStar OpenDAP, Sea Gull data & nav casting..
O: Using map sheets and network (re) configuration state meta data stored on the Mission Data Loader (MDL) harvested by the heartbeat sub network protocol subsequently couriered or sent to and aggregated by the S-6, the Maneuver Control Systems (S3 Operations Officer) generates & transmits consolidated Unit Task Order (UTO) to TIMS / FBCB2 operator (S6) for network broadcast. Note: this process is iterative based on completion of one mission and start of the next.
0: Laptop / handheld with network initialization data processes (e.g., Juniper CESAC) geospatial, scenario viewers / applications / browsers Schema Tools to edit Common Alert Protocol (CAP). Transmit CAP Unit Task Order (organizational structure) via SMS, bots, JXTA motes, agents, email, Groove Simple Symmetric Transport Protocol SSTP, any commercial data distribution, file distribution product, system, component / commercial equivalent of the Mission Data Loader
1: TIMS – Tactical Internet Management System operator / Network Characterization Tool NCharT) populates “Hasty” Reorganization Tool” from heartbeat mechanism state meta data gathered from devices / platforms to generate a new Unit Task Order UTO with next UTO version number, effective Date Time Group DTG synchronization Time (K00.99 heartbeat message option UTO notification)
1: Wizards & UTO Tool commercial equivalent e.g., CISCO IPCS, Juniper CESAC used to (re) configure network management parameters using state meta data harvested by heartbeat beacon mechanism that is Telco PSAP standard from computer devices on TCP/IP networks described by heartbeat message counterpart to K00.99 heartbeat message
2: S6 Sends out initial UTO message. FBCB2 processes UTO notification & sets timer to execute change at effective time
2: System administrator / network monitoring software enabled with wizards, intelligent software agents sends out unit / entity / organization task organization message and sets time for effective time (when order will be executed) distribution via workflow tool over Unicast / Multicast groups by subscription filtered by user permissions / need to know / security classification settings
3: Heartbeat Process: (TIMS/FBCB2 engine) generates “Heartbeat” message every 15 minutes with UTO version.
3: Wizards & UTO Tool commercial equivalent e.g., CISCO IPCS, Juniper CESAC used to (re) configure network management parameters using state meta data harvested by heartbeat beacon mechanism from computer devices on TCP/IP networks described by heartbeat XML message
4A: GTCS – Ground Tactical Communications Server passes heartbeat to state manager (Variable Message Format VMF)
4a:, Short Message Service SMS “texting”, Bots, JXTA motes, agents, email, Groove Simple Symmetric Transport Protocol SSTP, any data distribution, file distribution product, system, component e.g., Mission Data Loader to distribute (binary) XML schema Common Alert Protocol schema, child schemas, efficient XML, Binary Runtime Environment BREW type structures
4/5: At effective date/time, All FBCB2’s in multicast group reconfigure database to ensure proper Situational Awareness SA Calculation, new INC Operator is prompted to reconfigure or delay 10 minutes (w/option to change at anytime). When operator OKs, database is rebuilt & network reconfigures
4/5: At pre coordinated data and time, devices in multicast groups reconfigure router Management Information Base MIB Configuration descriptions MIBS (common to all routers – military & commercial) & distribution lists / subscription lists in commercial parlance. (INC: Internet Controller – a router adapted for combat radio interface )
6: TIMS makes new Multicast Group (MCG) file, and if required, TOC INC MIBs & TOC auto router configs @ Effective time. TIMS calls the ModifyMCGInfo API (Subnet filename, MCG filename, UNIT URN, UTO version, Local IP Address LDAP Command and Control Registry C2R Server update tool executed as multicast group file, UTO version number & the AIS – Army Information Server e.g., Server running n supporting processes/apps to connect (will ignore if it already has one set)
6: CISCO IPICS, Juniper CESAC.. makes new multicast group file used to update router MIBs automatically at agreed on time. Agent, scripts, product / system Application Program Interface API. Lightweight Directory Access Protocol LDAP server (e.g., Netscape LDAP software). AIS = application server. XML Libraries / Directory Services: Heartbeat XML Child Schemas/Data Islands,
7. Command and Control Registry C2R – Lightweight Directory Access Protocol LDAP Server multicast MCG update tool updates multicast group data on AIS
7: Command and Control Registry C2R = Lightweight Directory Access Protocol LDAP Server multicast MCG update tool updates multicast group data on the AIS (application server)
8. C2R Server recognizes that a UTO has occurred & notifies state manager (SM) if it is there else it sends out the SM alert that the State Manager would have sent. C2R server replicates multicast group data to all configured UTO replication destinations.
8: State Management process on AIS / LDAP server recognizes change has occurred (intrinsic to Groove Networks Groove product) and sends out change alert (binary differential in Groove’s example). Simple Symmetric Transport Protocol vice multicast protocol in Groove’s case
9. Ground Tactical Communications Server GTCS gets SM or C2R server alert, reads updated MCG from C2R then updates internal configuration file & LAN card if platform is affected
9: XML SOAP relay intrinsic to Groove product receives state change via its intrinsic state manager & replicates updated multicast group from LDAP software on server & updates Network Interface Card NIC configuration JACAENCharT TABLE !: .mil to .com conversion
Efficient XML QUALCOMM BREW… - child schemas for COIs, profiles specific area encodings, inject points - data islands for special needs - data files for fast movers
Apply broadcast beacon technology to enable millisecond data exchanges vice 30 second screen scrapes while increasing / decreasing radius of disaster / event / alert radius represented by multicast zones corresponding to US / UK... five level advisory systems
Use the heartbeat / beacon function (send to / get from devices, platforms...) as a subnet publish-subscribe e.g., OSD Horizonal Fusion. Use the intrinsic millisecond - 99 minute timing function of the heartbeat to enable consistent, synchronized collection of raw state meta data (geo location, moving, halt, IP address, unit / organization ID) BEFORE transfer to queues, SANS, dbase... prior to data fusion improving filtering / data intel fusion
Instantiate National Command Authority NCA chopchain - workflows over multicast / anycast IP using “true cots” tools in use e.g., Towersoft w/AgileDelta Efficient XML module embedded synchronized across N complex systems achieving synchronized, interoperable collaboration based on synchronized event timing and common symbols via the Common Alert Protocol as a universal event / alert trigger
5
Use state meta data collected during step 1 to enable systems & network management of router Management Information Bases MIBs supporting Router/switch MIB dbase files for spontaneous (re) organization split, join, adds via broadcasts, P2P, multicast… of heartbeat harvested state meta data i.e., location, status: moving, halt…)
2
Enable across N complex systems, Y networks ("network of networks") & Z systems ("system of systems")
IPICS
CAPXML
.mil Range ExtensionTDN/CONDOR Gateway
Split / Joins
SoS
Heartbeat Messages
XML Repositories
Authorized
Efficient XMLQualcomm BREW
NIEM GJXDM FXR SoR C2IEDM
“Maneuver the network” “Spontaneous Organization”
Common SymbologyUnified Alerts / Event Trigger
Consistent, Synchronous Timing of State Meta Data Collection
The Heartbeat / Beacon as subnet publish subscribe mechanism
Millisecond Transactions via Beacon Tech
SABRE
EOC
Weapons Free
TrackReceived
MIBs
Heartbeat Message
Heartbeat Message
State Meta Data
Alert Level Increase…
Increase Multicast Zone
Joint MissionData Loader
JACAE
COASTS: Coalition Operating
Area Surveillance Targeting System
CONDOR
OPEN Systems& Network ManagementMIB ToolRouter ConfigState meta data for
Heartbeat Protocol low level state meta data harvester Use to conserve bandwidth before handoff to more sophisticated protocols / mechanismsthat often use the heartbeat mechanism
integrated Rule-Oriented Data System iRODS: a: flexible data archive management system supporting many different site configurations.
Four main components :
1. iRODS server that manages stored data 2. iCAT catalog metadata manager
3. Database used by the catalog. 4. 'i-commands' command-line data access
Data Management Applications: Data Management Applications: Data grids to Share data - organize distributed data as a collectionDigital libraries to Publish data @ support browsing and discovery Persistent archives to Preserve data - manage technology evolution Real-time sensor systems Federate sensor data - integrate across sensor streams Workflow systems Analyze data - integrate client- & server-side workflows
The integrated Rule Oriented Data management System (iRODS), is an open source software data management system developed by the Data Intensive Computing Environments (DICE) group at the University of California San Diego with funding from the National Archives and Records Administration & National Science Foundation.
iRODS functionality includes: maintaining global name spaces for identifying files, users, and storage resources, authentication and authorization controls, high performance WAN data transport, system and user-defined metadata, query-based data discovery and browsing, management of data distribution and replication, and checksum and synchronization mechanisms.
iRODS provides a flexible, adaptive, and customizable data management architecture through the use of a custom-designed Rule Engine at its core which invokes 'micro-services' that are integrated into workflows to process requests and handle information. iRODS automates the execution of management policies by enforcing rules directly at each storage resource.
Metadata, both system-maintained and optional user-defined, are ingested & accessed in an RDBMS system. Accesses go through the iRODS clients to iRODS servers via the iRODS protocol, and then to the catalog library which interfaces to the RDBMS via either ODBC or OCI.
Performance and scalability are critical, as the digital holdings can be massive in size, measured in hundreds of millions of files and petabytes of storage, and may be maintained for decades.
iRODS is proposed as an excellent rules based engine/workflow engine to power the Heartbeat Beacon.
Workflow / Mission Threads Chop-chain / Business Logic
Spontaneous integration of X“Family Of Interoperable Systems - FIOP” to “maneuver”the network” by distributing Y disparate organization’s workflow logic / filters via N “network of networks" creating a Single Integrated Operational Picture SIOP a.k.a “The Grail”
Multicast / Cell broadcastRadius / Zone
> / <thresholds & intensity
Alert Level Increase…
Increase Multicast Zone
.0001 .05 .01 1 5 15 301 correlated event
SoSHomeland Heart_Beacon:
Systems, Process & Network Management
“NETOPS”
NET FORENSICS
NCharT
- Child schemas for COIs, profiles, - data islands for special needs i.e; specific area encodings, inject pointsoption fields, PIPS Vs PSAPs.. - data files for fast movers unique requirements & event code signaling
Tripwire
AI
6 Sigma
Special Needs
ACE
WITSFusionNET
Urgency Algorithm
UCORE 2.0
docBlock
NCTC SharePoint
Every day tools
SingleCitizen View SOA
ITACGNAO IBIP HIST TIPS
In common language: provide situational awareness of events / alerts as n 1- 1 Public Services
-Wireless broadband via Tesla inspired Ionosphere modulation -FBCB2 to BFT conversion to SATCOM in BALKANS (Tesla birth place)-OmniTraks Transportation / GNOC // TSA is lead on e9-1-1 NexGen
FEMA United States Citizens Corps NET GUARD Template
DHS CHLOE:High Altitude above civil airspace
SCOPEScalable Common Operating Picture Experiment
Alert Level > / <…
> / < Multicast Radius
MIT PAUL REVERE
MCI
NORAD / SPACECOM / NORTHCOM
SEWS
DHS REG: Resilient Electrical Grid
Boston UBeaconProject
National Science Foundation
Sea Gull
JBFSA
TESLA
Time Travel Messages
FAA
Heartbeat Messages
CAPXML
Wireless Broadband
First NET: First Responder reliable relay link.
DCGS: Distributed (Data)Common Ground Station
PSAPS
Universal Parsing Agent
DHS Tripwire
HEARTBEAT
NORAD TRACK DATA NOT SENT
THRU PSAPS TO FAA IN TADL/SADL FORMATS !
S.O.S
CONDOR
DisasterManagement Constellation
C2 On-the-Move Digital Over-the-Horizon Relay
.mil to .gov to .comDISCONNECT!
DISADREN
NASANREN
Messages
TDN
CommunicationsAND
Electricity to Deployed units
Trickle Chart BatteriesTrickle charge hybridVehicles & power supplies
HAARP
DACT
JWARN
C2PC
BCOTM
XMPP
MAGTF C2 Intra-net
IRIDIUM
AIR TRACKS
JTF GNOGIG
NCES
NECC
COSMOS
STAN
TNT
Fort Hunter-LiggetCamp Roberts
IOW:IntelligenceOperationsWorkstation
Digital Tech Control (DTC)
UCC
PSIC
DACT
EPLRS
BREW
EfficientXML
INTELSAT IRIS
TESLA:WirelessElectricity
INTEL
Universal Communications Interface Module (UCIM) SystemIP ADAPTER universal modules comprising architecture fornet centric integration of voice, data and video functions across the battlespace.
NISAC
CONDORGateway
JTRS POP
TADLS / SADLSBinary but not
Binary XML
UCIM
NRL
DWITS
Track Received
NCharT
JACAE
UniversalAlert
Trigger
CONDOR as GATEWAY extends network to maneuvering forces. CONDOR JTRS Point of Presence and Jump C2 Vehicle Integrate Tactical Data Network capabilities into ANY PLATFORM thru Universal Communications Interface Module (UCIM) System.
DOE Fort Bragg/Pope AFBSwitch Modernization 18 + military switches upgraded
Time Travel Messages
Intergraph Business Intelligence forPublic Safety Suite Computer-Aided Dispatch CAD
18th ABC FusionNET
RTC
Tripwire
DHS
DOE Sensornet
Situational Awareness As a service / subscription
H.A.A.R.PAdvanced PowerTechnologies Inc..
COSMOS. Coalition Secure Management and Operations Systems