|
Federal / military situational awareness (SA) SATCOM, Telco
/ cable networks supporting First Responder e9-1-1 systems apply 3 common denominators: the TCP/IP heartbeat protocol, heartbeat
transponder beacons & heartbeat (XML) schemas / messages conveying network configuration data e.g, router MIBs / multicast
group subscriptions -- DIFFERENTLY. The government developed the Heartbeat / Beacon -- simply an opportunity in time to gather
state meta data -- the terms are often used interchangeably by protocol geeks; about 40 years ago. DARPA fielded a heartbeat
and heartbeat message based solution a decade ago that was transitioned to the DHS in 2004. NENA: National Emergency Numbering
Association stipulated XML heartbeat messages in 2001.the Heart Beacon as I call it (not my idea by the way) is a procedure
based on what the government has been doing for 40 years...more famously as Network Centric Warfare based on the US Army Communication
Electronic Command's Greatest Invention for the past decade. The basic heartbeat function simply collects more state meta
data than normal resulting in more network management and broadcast options... its not rocket science... wait, yes it is...
NASA's OPenDAP protocol is heartbeat based as is every other data collection protocol since data collection is ultimately
simply a interval in time where state meta data is collected and used for a more flexible alert / event response paradigm.
From a training aspect, since it is taught to soldiers executing this procedure in austere and challenging environments (e.g.,
war); it can be taught in the commercial domain.
|
