The Heart Beacon: Seed Sync The Cloud
Upcoming SlideShare
Loading in...5
×
 

The Heart Beacon: Seed Sync The Cloud

on

  • 1,620 views

The Heart Beacon Rainbow Force Tracking Net Effects ...

The Heart Beacon Rainbow Force Tracking Net Effects

ABSTRACT: method of spontaneous re-organization setting pre and post net management conditions enhancing Computer Aided Dispatch and enabling a single, unified event / alert trigger by instantiating the Common Alert Protocol with NIEM payloads / data islands across diverse military, emergency, financial, all hazard domains. Router multicast hop counts emulate threshold radius of conditions increasing / decreasing with audible tones and vibratory levels based on business / military mission thread logic. Rules display as threshold conditions as concentric color band expansion / collapse via router hop counts enhancing medical triage, evacuation, alternate routing within geographic zones with overlay graphics describing course of actions and unified symbols. The TCP/IP sub protocol’s synchronous data harvesting cycles gathering organizational identification and / or Universal Reference Number URN will in effect 'sync seed" the cloud computing environment enabling enhanced net effects and net forensics’ through the cloud in context with SYNCHRONIZED shared, cross domain services. Heartbeat data messages update net management configuration enables spontaneous integration of adhoc groups synchronizing overlay depictions of actions that enhance situational understanding and enhanced forensic analysis (e.g., the SWIFT protocol) of situational awareness and finance systems as fee for n1-1 Public Services. The Heart Beacon: One method fits many; not one size fits all. Sync Seed the Cloud.

Statistics

Views

Total Views
1,620
Views on SlideShare
1,612
Embed Views
8

Actions

Likes
0
Downloads
14
Comments
0

2 Embeds 8

http://www.slideshare.net 4
http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • The Heartbeat is a sub protocol of the TCP/IP (Internet) stack that is as old as the internet. It 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 to move data. They 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). Protocol gurus (geeks) refer to the heartbeat / beacon interchangeably or even together. Point being, to save lives by working together on an apples to apples, oranges to oranges level involves using what opportunities in time that are available to us to CHOOSE / CHANGE our (telecommunications) matrix to either save or not save each others lives in a common, consistent method across systems, networks, agencies, federal, state, local, international / sub-terranean, ocean floor, intergalactic... A clear and present opportunity to integrate heartbeat beacon enhanced systems and networks is DIRS: DIRS is a voluntary, web-based system that communications companies, including wireless, wireline, broadcast, @ cable providers, use to report communications infrastructure status and situational awareness information supported by the FCC’s Public Safety and Homeland Security Bureau. FEMA’s opt in portion of its IPAWS: Integrated Public Alert and Warning System is another. States can choose their own vendors for implementation. The Center for Disease Control sponsored Orion Rhapsody ebXML, Network Horizon, and EPA Environmental Information Exchange efforts should be focal points.
  • What the Heartbeat Beacon IS NOT Circa 1989, an engineer at the MITRE Corporate Eatontown New Jersey suggested the use of TCP/IP in what was then called battlefield digitization – the forerunner of network centric warfare. In the beginning, the use of the TCP/IP stack over military unique protocols was blockaded. As this blockade was breached, battlefield digitization progressed and networking techniques supporting maneuvers at the National Training Center in the Mojave Desert were vetted. The maneuver commanders and operations officers were frustrated at being told that they could not conduct operations as they planned given the network (routers and their intrinsic Management Information Bases MIBs) could not support their network operational "NetOPS" scheme. Warfighter reaction was to the effect “give me back my (analog) radios and (non digital) charts then”. The developers of the template system (Blue Force Tracking – BFT) acquiesced to the then unthinkable use of TCP/IP and the heartbeat sub-protocol mechanism as a means to harvest data on networks with bandwidth 220 kbps or usually less. As a relevant aside, there are other protocols and means to harvest data like NASA JPL’s OPenDAP (any data, anywhere, any format) which on closer inspection, depend on the heartbeat mechanism as an opportunity in time to collect data from (IP) hosts, devices. The developers of the template system acquiesced to the then unthinkable use of TCP/IP and the heartbeat sub-protocol mechanism as a means to harvest data on the networks with bandwidth of 220 kbps or usually less. As a relevant aside, there are other protocols and means to harvest data like NASA JPL’s OPenDAP (any data, anywhere, any format) which on closer inspection, depend on the heartbeat mechanism as it is simply an opportunity in time to collect data from (IP) targeted hosts, devices. Opening up a web connection or “surfing” in the National Training Center is a Uniform Code of Military Justice punishable offence. Think of the cell networks in New York during 9/11. Data channels also saturate.
  • Boston University Beacon Project: A Network Diagnosis Toolkit. The focus of the Beacon project is the development of tools capable of diagnosing network conditions with only the assistance of end-to-end measurements. In its basic form, this toolkit is designed to passively monitor network conditions at a single busy network endpoint such as a Mass server. In its full generality, the toolkit can be used to actively monitor network conditions, and can be concurrently operated by a set of collaborating endpoints. Over short time scales, Beacon will use wavelet analysis to identify local scaling events in wide-area TCP traffic which trigger bursts of packet loss. At medium time scales, Beacon will draw correlations between end-to-end measurements made by concurrent TCP connections to draw conclusions about hotspots in the network. Over the long time scales, Beacon will build up an understanding of long-term network dynamics, especially focusing on regions which persistently experience congestion from the perspective of the source. Components of the Beacon Toolkit will be made available from the MASS server project "Software" page. FLUX: A Forensic Time Machine for Wireless Networks: enables a typical monitoring infrastructure for forensic data collection, storage and analysis supports the recording and retrieval of traffic signatures and environmental observations, considered to be a source of network evidence. HARVARD HOURGLASS project is building a scalable, robust data collection system to support geographically diverse sensor network applications. In Hourglass, streams of data elements are routed to one or more applications. These data elements are generated from sensors inside of sensor networks whose internals can be entirely hidden from participants in the Hourglass system. SABER (Situational Awareness BEacon with Reply) is a sophisticated battle group situational awareness system that is capable of determining the location of beacon-equipped tanks, ships, aircraft, and other military assets worldwide. Using the Global Positioning System (GPS), SABER produces accurate position and platform identification data and sends that information to tactical users and global command and control nodes, The system relays position information via ultra-high frequency (UHF) line-of-sight and UHF satellite communications (SATCOM) channels. SEA GULL: Maintains routing and object state using minimal resources. e.g. less than 1% of bandwidth and CPU cycles. Server Heartbeat's “Keep-alive” beacon along each forward link.Increasing period (decreasing frequency) with the routing level. Data-Driven Server Heartbeat's “Keep-alive” Multicast to all ancestors with an object pointer that points to us. Multicast with increasing radius. SENTINEL BEACON COMMAND STATION: is a ruggedized PC that receives the data transmitted from the beacons and processes it to produce location and track information for the incident commander. The Sentinel Beacon system is designed to work as a mesh network so that a beacon out of range of the command station can have its data relayed by other beacons.
  • Adopted as a template system for Humanitarian operations by SHAPE / NATO / JFCOM as evidenced by the HANDS initiative, the Heartbeat Beacon approach fits the DHS Science and Technology Directorate portfolio exactly as the template system that The Heartbeat Beacon is modeled / derived from is a military system born from spiral development that has been in use since before the Balkan Conflict where the template system was adapted to satellite broadcast that was transitioned from the military to the Department of Homeland Security in the form of situational awareness to Blackberry devices several years ago – by the same military industrial vendor. This template system (there are reportedly between 7 and 64 of them) is credited for the capture of Saddam Hussein figure II. Mr. Cohen of DHS S&T Division stated that “light takes many forms” and “ light (beacons) is involved in many areas in the Department of Homeland Security”. By following the links and listening to the Honorable Jay Cohen’s interview, the Heartbeat Beacon; by whatever name or no name, yields an ROI for us all closing terrorist / criminal seams through reuse of our (tax payer) “venture capital”.
  • The Heart Beacon is based on a program core to the military’s situational awareness capabilities that has been in use since before the Balkan Conflict using terrestrial digital radios and after this conflict as satellite broadcast based with Qualcomm’s support – think OmniTraks known for tracking trucks and shipping. See above diagram’s leftmost “tactical GIG – Global Information Grid section. The middle section suggests that the military apply its network centric warfare procedures to “maneuver the network” and enable “spontaneous” integration to 80% of the network infrastructure that it leases from commercial providers on contracts like GSA’s NETWORX offering its procedures to the commercial sector – see right hand panel for a integrated, global, cohesive and temporally SYNCHRONIZED cross system solution. The benefits and “power” of network centric warfare would be increased 80% if not exponentially and to the commercial sector who do not collect the additional state meta data from networked devices that the military does and therefore do not benefit from the enhanced network management and network flexibility options practiced by the military.
  • Inspired by Paul Revere’s “one if by land, two if by sea” ride to alert the Colonists to the arrival of the British and mercenary forces during our Revolutionary war: "If the British march by land or sea from the town to-night, hang a lantern aloft in the belfry arch of the North Church tower as a signal light,-- one if by land, and two if by sea; And I on the opposite shore will be, Ready to ride and spread the alarm through every Middlesex village and farm, For the country folk to be up and to arm."
  • "The Homeland Security Advisory Council's recommendation is not workable. It has no chance of adoption by the military messaging community that has along with NASA and its five level tone based messaging system, ditto for the National Undersea Research Center.. the military structured messaging systems that in turn drive command and control system development to include funding simply cannot adopt this change as it breaks machine to machine level processing based on precedence on time established INFOCON levels. This recommendation also breaks down messaging between five main countries -- actually more than five. Changing this long standing system WILL BREAK mapping & machine to machine numeric processing… Other 5 Key Five Level Systems: NASA & NURC undersea tone based messaging (for blind) This recommendation is DOA. Precedence is a simple ordering, based on either importance or sequence: - Message precedence of military communications traffic - Order of precedence, the (ceremonial) hierarchy within a nation or state - Order of operations, in mathematics and computer programming CCEB military precedence: The Combined Communications-Electronics Board (CCEB), a five-nation joint military communications-electronics organization (consisting of Australia, Canada, New Zealand, the United Kingdom, and the United States), uses the following message precedence designators, in descending order of PRECEDENCE: INFOCON levels: NULL / NORMAL / ALPHA (increased), BRAVO (specific risk of attack), CHARLIE (limited attack), DELTA (general attack).
  • The template system is based on a program that is functionally workflow over IP Unicast / Multicast. Military Message Threads (hundreds to thousands of them drive system development – and even constitutes Program Manager’s funding are analogous to private industry’s workflows. FBCB2/Blue Force Tracker/Joint Blue Force Situational Awareness JBFSA are functionally workflows over multicast – think Verizon’s VCAST. Two of the military’s more famous workflow systems were developed programmatically a football field apart and geographically on each of America’s coasts.
  • Quadrant I in figure VI, state meta data such as IP lease, current GPS location & time stamp can be harvested in the millisecond range to up 99 minutes. This data is accessed from data distribution / publish-subscribe type mechanisms (the heartbeat mechanism is a TCP/IP subnet publish subscribe mechanism) from local queues, file folders, or data stores for onward distribution by more modern & flexible methods that in turn rely on the heartbeat beacon mechanism for device / platform data gathering. Transponder beacon sensor, mesh, telematics, & home awareness systems tech can move the data in the same millisecond range that the heartbeat protocol operates. This enables faster than current 30 second web page screen scrapes that exist because of data format differences between FAA & .mil systems. Quadrant II, the heartbeat protocol is part of the TCP/IP stack. Its role in failover sensing for disaster recovery traces back to the TCP/IP’s DARPA origins. The heartbeat protocol / beacon (the term is used interchangeably) can query target devices on subnets for information stored on the device. The heartbeat mechanism gathers information that is assembled into heartbeat messages that are standards used by both network centric warfare template systems and National Emergency Numbering Association requirements for Public Safety Answering Points -- PSAPs alike. The network meta – state data encapsulated in heartbeat messages change router/switch Management Information Bases or MIBS enabling units / platforms / devices / teams / organizations to be moved from network subnet to network subnet enabling network centric warfare style “maneuvering of the network” and “spontaneous integration” enabling “dynamic (re) planning scenarios. Quadrant III from top center is the International Telecommunications Union ITU’s beacon symbol as a single, unified event / alert trigger for cross domain, cross community of interest COI instantiation / triggering of events and alerts via the OASIS ratified Common Alert Protocol CAP. The remainder of this quadrant depicts ingredients and baseline givens to make this possible. In the middle of quadrant 3, a universal parsing agent replaces structured military messaging unique parsers. Quadrant IV: Gathering state meta data from target platforms, hosts and subnet or cells of interest (e.g., the function of the DHS TRIPWIRE shown in the lower left hand quadrant IV in figure V); will serve to notify units of action (UA) in military speak to converge on suspected terrorist financial activity. The Heartbeat Beacon describes a methodology to “maneuver the network” (change router databases to support maneuvering units) enhanced by beacon transponder technology & made interoperable by adapting the procedures to the world wide OASIS standards body & presidential ratified Common Alert Protocol – that is not linked with military Network Centric Warfare - NCW data exchanges hence Heartbeat Beacon’s notion of CAP child schemas to account for (commercial) domain specific business rules / work flow logic analogous to structured military message mission threads execution Quadrant IV, lower right above, South West Research Institute’s SABRE is a sensor suite available to link low level tactical to strategic sensor enabled platforms. Along the bottom right of this quadrant is shown the current state between military organizations that use a variety of proprietary structured military message formats including formats that are hybrid XML header / structured military format body messages incompatible with first responder / commercial systems necessitating gateway systems that reduce reaction time, increase complexity, introduce errors, and increase cost. The common denominators between military and first responder systems are the heartbeat sub-protocol and heartbeat network reconfiguration messages w/state meta data.
  • The above diagram shows the current Army Battle Command System / FBCB2 / Blue Force Tracker procedures in system. On the right, a commercialized, product/operating system/application neutral framework supporting the same functions to enable a global Situational Awareness Tone - SA Tone to smart phones & other mobile devices is shown. The heartbeat protocol as a low level data harvester gathers network configuration data (e.g., current IP lease, multicast group participation, state information such as moment greater than 50 meters, at halt, off line, or straggler…) that is gathered and forwarded by any newer, more efficient products or systems. Once multicast subscription group (s) state data is consolidated, data is consolidated by the tactical equivalent of the corporate system administrator or the S-6 in military speak. The Tactical Internet Management System or TIMS is used to configure router management information bases (MIBS) and associated multicast entries describing the grouping of organizations (units) for missions (Unit Task Order). The S-6 / tactical system administrator then broadcasts the updated network configuration data in the form of (K00.99 Variable Message Format) heartbeat messages to higher, lower and adjacent organizations refreshing router/switch unicast / multicast subscriptions. On the military side of this procedural method, situational awareness data subscriptions are updated and units tether and untether to network nodes as they maneuver. A similar process occurs on the commercial side of this methodology as cell phone / smart phone / wireless laptop users tether and untether to cell tower nodes – differently i.e., different heartbeat protocol data collection-distribution rates and different heartbeat XML message schema structures). Heartbeat e9-1-1 involves the commercialization of network centric warfare message structures / documents / schemas into Emergency E9-1-1 cell phones and smart phones E9-1-1 Public Safety Answering Points – PSAPs emulation. This concept involves commercialization of military proprietary tools such as the Tactical Internet Management System (TIMS) that produces the UTO – Unit Task Order. The UTO is a message template that military situational awareness applications FBCB2 and Blue Force Tracking) apply. The Unit Task Order is a hierarchical depiction of unit structure showing how units are organized for operations similar to corporate wiring diagrams. UTO distribution is enabled by the use of TCP/IP’s heartbeat mechanisms in terms of the heartbeat protocol’s send to, get from and timer / data harvest trigger. Gathering network (re) configuration data used to update tactical / corporate organization / first responder’s multicast subscription information based on unit / organizational mission posture change is key Heartbeat e9-1-1 methodology. The commercial equivalent of the military proprietary UTO Tool composes heartbeat protocol gathered network (re) configuration data as a XML EDXL-DE formatted schema with military DDMS data as embedded islands or child schemas. Commercial equivalent UTO tools will exchange these network reconfiguration messages with military counterpart organizations. Tool functionality includes the feature to update corresponding Multi-Cast Group (MCG) subscription data and Management Information Base (MIB). The UTO is part of the military TIMS (Tactical Internet Management System). The TIMS supports several complex tactical systems (e.g., FBCB2 / Blue Force Tracking / Land Warrior). These main situational awareness propagation systems apply workflow logic stored in APIs that are instantiated by scripts, defined by filters as implemented and broadcast by unicast / multicast IP groups supported by router/switches. Transitioning the Heartbeat Beacon methodology would involve developing commercial equivalents of the Army’s NOC-V: Network Operations Center Vehicle plan, manage, monitor and control tactical systems and networks in a battlefield environment. the NOC-V has an FBCB2 (Force XXI Battle Command Battalion/Brigade and Below) suite for battlefield situational awareness data traffic, information assurance systems, as well as a global broadcasting system, which allows soldiers to watch CNN and Armed Forces Network while they’re in the field. The NOC-V also contains a secondary tactical operations center (TOC) server, which can act as a primary server when the TOC “splits” to separate locations.
  • 1. Establish consistent timing and synchronous state meta-data collection. Use the heartbeat / beacon’s (terms used interchangeably) intrinsic millisecond - 99 minute timing function to enable consistent, synchronized collection of raw state meta data (geo location, moving, halt, IP address, unit / organization Universal ID) BEFORE transfer to queues, SANS, dbase... prior to data fusion activities to improve filtering / data intelligence fusion. Use the heartbeat / beacon function (send to / get from devices, platforms...) as a subnet publish-subscribe e.g., OSD Horizontal Fusion to temporary holding areas awaiting harvesting by more advanced data collection / replication mechanisms that in turn rely on the heartbeat beacon mechanism e.g., OPenDAP, DARPA’s Cougaar, UMTS cellular, mesh networking standards ZIGBEE, ZWAVE…. 2. “Maneuver the network” Use collected state meta data enabling network management of router Management Information Bases MIBs installing network router MIB updates for spontaneous (re) organization split, join, adds via multicast - anycast broadcasts of heartbeat harvested state meta data (geospatial location, status: moving, halt, URN, Org ID, Universal ID…) 3. Instantiate National Command Authority NCA chopchain - workflows – business logic over multicast / anycast IP using “true cots” tools in use e.g., Towersoft w/AgileDelta Efficient XML module embedded via the Common Alert Protocol CAP (XML child schemas and or data islands / embedded files ) to support the multicast, unicast, or anycast distribution of events, alerts via a unified alert / event trigger mechanism – the OASIS Common Alert Protocol with child schemas and / or data islands conforming to DHS OPEN: Open Platform for Emergency Networks to adjust to Communities of Interest (COI's) special needs. 4. Apply 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 Enable across N complex systems, Y networks ("network of networks") and Z systems ("system of systems")
  • 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.
  • The Heartbeat Beacon addresses the data / temporal / symbolic interoperability challenge where unique / proprietary federal / military situational awareness (SA) systems and Telco networks supporting First Responder systems must agree on common, settings of three building blocks: I. TCP/IP heartbeat protocol state data commonly timed, harvested & broadcast via beacon transponder tech. II. Heartbeat network (re) configuration XML schemas / messages Efficient/BREW/binary... XML formatted small data files replacing military unique Tactical Data Link / Joint Variable Message Formats. III. Common Alert Protocol CAP child schemas / data islands as a single, unified trigger for alerts by Community of Interest (COI) FOUR FOCUS AREA: I. Establish consistent timing and synchronous state meta-data collection. Use the heartbeat / beacon’s (terms used interchangeably) intrinsic millisecond - 99 minute timing function to enable consistent, synchronized collection of raw state meta data (geo location, moving, halt, IP address, unit / organization Universal ID) BEFORE transfer to queues, SANS, dbase... prior to data fusion activities to improve filtering / data intelligence fusion. Use the heartbeat / beacon function (send to / get from devices, platforms...) as a subnet publish-subscribe e.g., OSD Horizontal Fusion to temporary holding areas awaiting harvesting by more advanced data collection / replication mechanisms that in turn rely on the heartbeat beacon mechanism e.g., OPenDAP, DARPA’s Cougaar), UMTS cellular, mesh networking standards ZIGBEE, ZWAVE…. II. “Maneuver the network” Use collected state meta data enabling network management of router Management Information Bases MIBs installing network router MIB updates for spontaneous (re) organization split, join, adds via multicast - anycast broadcasts of heartbeat harvested state meta data (geospatial location, status: moving, halt, URN, Org ID, Universal ID…) III. Instantiate National Command Authority NCA chopchain - workflows – business logic over multicast / anycast IP using “true cots” tools in use e.g., Towersoft w/AgileDelta Efficient XML module embedded via the Common Alert Protocol CAP (XML child schemas and or data islands / embedded files ) to support the multicast, unicast, or anycast distribution of events, alerts via a unified alert / event trigger mechanism – the OASIS Common Alert Protocol with child schemas and / or data islands to accommodate disparate Communities of Interest (COI's) IV. Apply 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 Enable across N complex systems, Y networks ("network of networks") and Z systems ("system of systems")
  • The Heart Beacon involves pre and post configuration management of the network and is neutral to systems and middleware. What Vinton Cerf and his team described metaphorically as the heartbeat is actually a interval in time where (state meta) data is gathered and placed into temporary holding areas, queues, file structures for onward delivery by middleware software such as agents, bots, motes, scripts. The heartbeat is an opportunity in time to synchronize data harvesting protecting bandwidth on low capacity networks prior to entry into portals and fusion centers – the point of no return in context with event time stamping. After transition to the middleware or cloud layer, it is too late to try and re-establish timing of event / alert chain of custody. Many systems report the same event at different time intervals. Too fast updates tend to saturate the network. Too slow refresh rates cause the data to be too “stale” for targeting systems. Operational discipline derived from years of military testing and simulation is reused across the entire portfolio of assets. The Beacon process is initiated when agencies act on an event / alert via operational scenario selecting from beacon technologies shaping NET EFFECT. Multicast broadcasts are shaped and filtered by zones using router hop counts to emulate condition thresholds through visual geospatial views of effect expansion and contractions while filtering desired users and evacuee’s in and out of impacted zones enhancing (medical) triage.
  • The Heart Beacon is an all hazards process that addresses data temporal / exchange interoperability gaps by Common Alert Protocol CAP instantiated data exchanges for military, first responder, and commercial / financial domains. By standardizing data exchange formats, symbol sets, event refresh rates; direct collaboration among military, financial, and other dissemination & telemetry systems using commercial, open, standardized frameworks is possible. Router multicast radius are adjustable – e.g., increase / decrease with audible tones and vibratory levels based on business logic / military mission thread logic according to threshold rules visually displayed as concentric color band expansion / collapse based on DHS and other multi level color / audible advisory schemes. Medical triage, alert, evacuation, alternate routing of transportation assets, will then adjust & filter consistently by commercial world business logic / military mission threads by zones. Organizations, entities, platforms, vehicle, mobile smart phone type & sensor equipped devices via router network data heartbeat messages updates will spontaneously integrate connecting adhoc task forces among disparate entities enabling the network to be maneuvered to support unified operational, financial, disaster, humanitarian and situation awareness events / alerts / N1-1 Public services.
  • Explaining figure 1 and by extension, the Heartbeat Beacon idea is simple. To quote the Honorable Jay M. Cohen, a retired Navy Admiral now serving as the Undersecretary of Science and Technology for the Department of Homeland Security during his interview with SPIE: “it’s not rocket science” referring to fifty percent of his “venture investment capitalist / mutual fund” portfolio (budget) that is “simply product transition” that is “near term / three to five years”. “This part of my budget is applied towards “solving the problems of his customers through spiral development of items that are designed to close terrorist and criminal seams”. Marching in step; the Heartbeat Beacon is designed to close interoperability and synchronicity seams – e.g., between military & responders. The Heartbeat Beacon approach fits the DHS Science and Technology Directorate portfolio exactly as the template system that The Heartbeat Beacon is modeled / derived from is a military system born from spiral development that has been in use since before the Balkan Conflict where the template system was adapted to satellite broadcast that was transitioned from the military to the Department of Homeland Security in the form of situational awareness to Blackberry devices several years ago – by the same military industrial vendor. The template system FBCB2/Blue Force Tracker has also been transitioned to a peer to peer XML messaging system – Sun’s JXTA (the other cited system is based on Jabber). Mr. Cohen stated that “light takes many forms” and “light (beacons) is involved in many areas in the Department of Homeland Security”. By following the links and listening to the Honorable Jay Cohen’s interview, the Heartbeat Beacon; by whatever name or no name, yields an ROI for us all closing terrorist / criminal seams through reuse of our (tax payer) “venture capital”. GOAL: Enable an international Heartbeat Beacon by following a proven method / process and agreement on III building blocks / common denominators threaded through 4 iterative focus areas to standardize situational awareness (SA), event & alert data exchanges among N complex systems. The result will be a global SA engine providing SA tone & SA as a service.

The Heart Beacon: Seed Sync The Cloud The Heart Beacon: Seed Sync The Cloud Presentation Transcript

  • Situational Awareness CDRLS .0001 .05 .01 .1 5 15 30 99 .0001 .05 .01 .1 5 15 30 99 MANEUVER THE NETWORK SPONTANEOUS INTEGRATION NET EFFECTS Sentinel Payloads DHS Tripwire Publish-Subscribe Over Multicast FLUX CAP XML ORGANIZATIONAL IDENTIFICATION ORD ID UNIVERSAL RESOURCE NAME URN SYNC SEED THE CLOUD INCREASE MULTICAST ZONE +3 to +5 THE BIG RED BUTTON Harvesting additional state meta data each heartbeat TCP/IP cycle in heretofore unused time slots yields new opportunities In net management / NET EFFECTS e.g., move organizations by group ID rather Than individuals or single platforms Synchronized, predictable data refresh rates from Millisecond to 99 minute range enhances the consistency of the Common Picture in EOC’s Enhanced net forensics non-repudiation, enabling end to end system heartbeat for improved transactional integrity and enhanced net analytics COMMANDER”S INTENT Sync seeding the cloud enabling enhanced net effects / net forensics’ via time sync’d ORG tagged time travel (DOE Oak Ridge ripples through the cloud in context w/ SYNCHRONIZED shared, Inter cloud sync’d meta data as a service SYNC’D_ MDaaS. IF-MAP Infoblox Orchestration Server Open Science Data Cloud (OSDC) Working Group BOSTON U PROJECT BEACON UC BERKLEY SEA GULL TIME TRAVEL MESSAGES NISAC IF-MAP Sun Single Citizen View SOA Unit Task Order UTO UTO Alert Level Increase … CAP XML SEED SYNC _CLOUD -8 to -5 - 4 to -2 - 1 to +2 +6 to +8 +3 to +5 LIGHT JTF GNO GIG NCES NECC COSMOS
  • HEARTBEAT
    • TCP/IP stack sub protocol used in Infrastructure failover e.g., NISAC
    • 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
    • Verizon’s VCAST, RTI Multicast
    RFID PKI, social awareness systems e.g., 211, 311, 411, 511, 611, 711, 811 & e9-1-1 = Heartbeat Beacon Server failover e.g., HP Serviceguard Service Oriented Architecture SOA system wide heartbeat for app / system availability (DISA GIG) DHS UICDS middleware Network subnet type of DISA’s Horizontal Fusion Publish-Subscribe THINK SYNC SEED SYNC _CLOUD
    • HEARTBEAT: TCP/IP (Internet) sub-protocol old as the internet – See DARPA Vinton Cerf et al. Known mostly for system failover operations
    • HEARTBEAT: INTERVAL / OPPORTUNITY IN TIME TO GATHER STATE META DATA DURING HERETOFORE RESERVED TIME SLOTS -- ORGANIZATIONAL ID / URN UNIQUELY IDENTIFYING Platforms / Devices – BY GROUP / ORGANIZATION
      • Heartbeat harvests state meta data used to adjust infrastructure e.g.., router Management Information Dbases or MIBS 
      • State meta data moved 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…
    • Heartbeat: in this context: NOT about net equipment synchronization timing although central timing pulse from Cheyenne Mountain is essential to synchronize data harvesting prior to entry or “seeding the cloud” and subsequent BEACON TECH data propagation throughout the CLOUD
    HEARTBEAT TIME STAMPS DATA PRIOR TO ENTRY INTO CLOUD DATA FUSION CENTERS Data needs time stamped in a systematic, prior Agreed upon scheme to enhance data fusion & Protect network availability. SYNCHRONOUS Pre-planned data harvesting = enhanced fusion THINK SYNC IF-MAP SYNC SEED _CLOUD
  • Beacon Transponder Tech ADS-B: Automatic Dependent Surveillance – Broadcast: ADS-B message ields for avionics self-reporting integrity of 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 18 th 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 beacon-equipped platforms. SABER produces accurate position & platform ID. &quot;intent to shoot&quot; and &quot;friendly ID&quot; query and response mode data Sea Gull: Server Heartbeat strategy maintains routing & object state using < 1% net resources. Server Heartbeat: “Keep-alive” beacon along links. ^ period (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 processing beacon location / track data. 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 Guard UMTS: Universal Mobile Telecommunication System heartbeat to track user’s activities e.g., NG NYC metro ZIGBEE / ZWAVE: Consortiums supporting heartbeat driven mesh network standards NET EFFECTS
  • COSMOS RAINBOW FORCE TRACKING Exhibit 16-A: Public Safety Broadband Network Architecture THE HEART BEACON: ENHANCEMENTS TO FCC BROADBAND PLAN COMMAND & CONTROL MANAGEMENT FRAMEWORK UTO Situational Awareness CDRLS .0001 .05 .01 .1 5 15 30 99 .0001 .05 .01 .1 5 15 30 99 MANEUVER THE NETWORK SPONTANEOUS INTEGRATION NET EFFECTS COMM / ELECT THINK SYNC IF-MAP InfoBlox IF-MAP Orchestration Server / meta data SUN SINGLE CITIZEN VIEW SOA LEADER”S INTENT JTF GNO GIG NCES NECC Alert Level Increase … CAP XML E R I C SEED SYNC _CLOUD
  • C2 Management / Heart Beacon
    • COMMAND CONTROL MANAGEMENT
    • OPERATIONS SUPPORT
    • MOBILITY MANAGEMENT SERVER
    • DATA BASE
    • EDGE ROUTER / SWITCH
    • Land Mobile Radio LMR
    • Jurisdiction From Separate Nets
    • C2 SITUATIONAL AWARENESS SYSTEM BASED (FBCB2 / BFT)
    • EXECUTES COMMANDER’S INTENT VIA UNIT TASK ORDERS UTO
    • TEMPLATE SYSTEM DESIGNED TO ADDRESS NET MOBILITY TASKS
    • FILTERING TO / FROM DBASE
    • DERIVED FROM ROUTER / SWITCH RECONFIG CHALLENGES
    • SINGCGARS / EPLARS LMR
    • ORG ID / URN Distinguishes Nets
    THE HEART BEACON: PROCEDURES AS ENHANCEMENTS FOR FCC NATIONAL BROADBAND PLAN COMMAND AND CONTROL MANAGEMENT FRAMEWORK NET EFFECTS SEED SYNC _CLOUD
  • 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 concepts result 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 &quot;Network Centric Warfare&quot; in the United States of America, &quot;Network Enabled Capabilities&quot; in Great Britain or &quot;Vernetzte Operationsführung&quot; in Germany. The key determinants of these network-based concepts are information sharing and collaboration: &quot;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.&quot; 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 &quot;Operation Iraqi Freedom&quot; led by the United States and the United Kingdom against the Saddam Hussein regime early in 2003 . http://www.hands-24.de/SeitenENG/thesenpapier.htm#HANDSThesenpapierIV NETWORK-ENABLED HUMANITARIAN ASSISTANCE AND DISASTER RELIEF MANAGEMENT IN THE INFORMATION AGE Vernetzte Operationsführung CWID JBFSA
  • Portfolio Management Telco’s + Defense Contractors + Major Telco Contracts (i.e., GSA NETWORX) + Nation: 6700 PSAPs EOC DHS Blackberry Used here since 2004 Used here 1990’s NYC + 80 other cities 20 % 80 % 100 % DECISION Global Information Grid Gather more types of state meta data Each heartbeat collection cycle .0001 .05 .01 .1 5 15 30 99 Additional state meta data types = Enhanced network management options & opportunities for additional SYNCHRONIZED, cross system services GREY FORCE TRACKING / RAINBOW FORCE TRACKING
    • DHS / DOJ NIEM / GJXDM / GEO INT 
    • OASIS World Wide Web W3C
    • World Data Coalition WDC
    • HIMSS , EDEN, CDC, Geo Location
    Global Information Grid FBCB2/JBC-P JIOC-I FIOP S2IOP PROPHET Brain (Theater) DISTRIBUTED MISSIONS OPERATION CENTER DMOC 1 correlated event .0001 05 1 3 5 10 30 SIOP FIOP 2 UTO E R I C SEED SYNC _CLOUD
  • Homeland Security Advisory System LOW/NORMAL GUARDED/ALPHA ELEVATED/BRAVO HIGH/CHARLIE SEVERE/DELTA MESA Boston U Beacon Increase Multicast Zone Unified Comms Center EAC, EOC, DMOC ,TOC… Sensors Telematics Mesh Networks Home Awareness Systems ZigBee, Zwave CAP NIEM XML Payloads - child schemas - data islands - data files/Efficient XML NIMS ICS Structured Military Messages E9-1-1 .gov, .org systems .mil systems USMTF, VMF TADIL(s), OTH Adat-P3.. .mil Range Extension TDN/CONDOR Gateway Split / Joins / Adds XML Schema Repositories Heartbeat Protocol Subnet level “ publish, subscribe” get from, send to data from target hosts, platforms, & computer devices SABRE Sentinel FLUX RDBS ADS-B CASM MxRRM Alert Level Increase … LOW GUARDED ELEVATED HIGH SEVERE Heartbeat Publish-Subscribe GIG SOA System Wide Heartbeat JACAE NOC-V Mobile User Objective System OneNet IPAWS DIRS DMIS-SIG /OPEN SWIFT Mobility Enhanced Situational Awareness Data-casting NAVCASTing FusionX OPENDAP NASA GES DISC EVERY GOOD BOY DOES FINE UC Berkeley Sea Gull DHS TRIPWIRE Systems, Network, Process Management “NETOPS” SAN Dbase Cache MDL JXTA NIIX NEMESIS $$$ S.O.S INTELSAT IRIS NASA DMC WITS NORAD FAA FusionNET FusionNET INFOCON levels NORMAL (normal activity) ALPHA (increased risk of attack), BRAVO (specific risk of attack), CHARLIE (limited attack), DELTA (general attack). UNIVERSAL PARSING AGENT CLEO IRIS Publish Subscribe Over Multicast MUOS FBCB2/JBC-P DMOC DMOC COMMON SYMBOLS III THE BIG RED BUTTON II SYNCHRONIZED EVENTS / ALERTS I E R I C
  • Machines / Networked devices Process numeric Threshold data Extremely well… Semantic information e.g., “guarded” Not so much… CCEB military precedence: Combined Communications-Electronics Board (CCEB), a 5-nation joint military communications-electronics org:  Australia, Canada,  New Zealand, the United Kingdom, and the United States), uses message precedence designators, in descending order of PRECEDENCE: Multicast / Cell broadcast Radius / Zone thresholds & intensity Alert Level Increase … Increase Multicast Zone CAP Payloads Homeland Security Advisory System LOW/NORMAL GUARDED/ALPHA ELEVATED/BRAVO HIGH/CHARLIE SEVERE/DELTA EVERY GOOD BOY DOES FINE NORAD FAA Combined Communications Electronics Board CCEB EVERY GOOD BOY DOES FINE NORTHCOM Flash Override FLASH (Z) IMMEDIATE (O) PRIORITY (P) ROUTINE (R) Precedence is a simple ordering, based on importance or sequence: Message precedence of military communications traffic, Order of precedence,hierarchy within a nation or state, Order of operations, in mathematics and computer programming Instantiate Data Harvesting Cascades Enhance Net management & Net Forensics CAP XML Data Islands NIEM PAYLOADS 0,1,2,3,4 0, 1, 2 INFOCON levels: NORMAL / ALPHA (increased), BRAVO (specific risk of attack), C HARLIE ( limited attack), DELTA (general attack). Changing this WILL BREAK message Data Element mapping & machine to machine numeric processing… Other 5 Key Five Level Systems: NASA & NURC undersea tone based messaging (for blind) S.O.S Threat Level minimal Oh Dear! DHS Tripwire COGCOM Levels of Concern COGCOM 1 COGCOM 0 COGCOM 2 COGCOM 3 COGCOM 4 EVENT SEVERITY INDEX Child Schema’s Child Schema’s -8 to -5 - 4 to -2 - 1 to +2 +6 to +8 +3 to +5
  • House Medical Technology Caucus Vice Chair of the 21st Century Health Care Caucus NASA Disaster Management Constellation Single Citizen View SOA Vibration levels for Deaf SPECAT Heartbeat Messages NASA AMES GNOSC Silicon Valley Region Data Interop Project   NHIN Prototype - IBM < / > Multicast Radius < / > thresholds
    • “ Active Triage Tag”
    Intelligence Committee 14 th Congressional District A. Eshoo CLEO Cisco Router In Low Earth Orbit CPHPDR: U of Pittsburgh U of N Carolina U of A Public Health U of Illinois Chicago Universal ID, Triage tag… HEAL1 Project CPMRC Triage Rules Engine Urban Earth SAIC PSIC UCC NHIN E9-1-1 Ireland FLUX Beacon Center for Rural Health & Social Service Development Hour Glass / Code Blue FLUX Beacon JTF CapMed Military Health IT WINS - military Battlefield Medicine Red Cross Comms Co-Located IF-MAP ORCHESTRATION SERVER Common Operational Picture (COP): A single identical display of relevant information shared by more than one command. A common operational picture facilitates collaborative planning and assists all echelons to achieve situational awareness. US Joint Force Common Glossary //Wikipedia Congress: “Nothing less than net-centric homeland security akin to net-centric warfare” CAP XML COMMON SYMBOLS III Millisecond Exchanges II Synchronized Event / Alerts I Equinox JTF GNO GIG NCES NECC COSMOS Beacon IBM Synthesis project The Urban Health Initiative Vulnerable Populations LifeComm IPICS CESAC Golden Triangle WHO UNESCO Code Blue E R I C Sector BEACON COMMUNITIES
  • GSA NETWORX DHS EAGLE II Situational Awareness CDRLS .0001 .05 .01 .1 5 15 30 99 .0001 .05 .01 .1 5 15 30 99 SYNC Event Timing BIG RED BUTTON COMMON SYMBOLS TELECOMM CDRLS NET EFFECTS Boston U Beacon UC BERKELY SEAGULL Sync / Seed Cloud SABRE Alert Level Increase … DHS Tripwire MESA Qual comm / Verizon DOD H.A.A.R.P Increase Multicast Zone Payloads Spontaneous Integration Maneuver the Net RAINBOW FORCE TRACKING Commander’s Intent 1 correlated event SIOP DMOC UTO DISA SOA END TO END HEARTBEAT NASA DISASTER MANAGEMENT CONSTELLATION SUN SINGLE CITIZEN VIEW SOA Comm / ELEC SEARCH BY ORGANIZATION IDENTIFICATION ORG ID / URN CLEO IRIS Congress: “Nothing less than net-centric homeland security akin to net-centric warfare” Common Operational Picture (COP): A single identical display of relevant information shared by more than one command. A common operational picture facilitates collaborative planning and assists all echelons to achieve situational awareness. US Joint Force Common Glossary //Wikipedia JUNIPER CESAC CISCO IPICS LIGHT CODE BLUE IF-MAP Orchestration Server CAP XML E R I C SYNC SEED _CLOUD SYNC SEED _CLOUD
  • A TALE OF TWO WORKFLOW Based PM’s TCP/IP Heartbeat Heartbeat Messages Mid 90’s Battlefield Digitization PEO C3T FBCB2 begat BFT Balkan Conflict upgraded to SATCOM broadcast BFT to JBFSA Joint NORTHROP GRUMMAN code to General Dynamics General Dynamics Handhelds to NORTHROP Distributed Common Ground Station DCGS Wf-XML is a  BPM  standard developed by the  Workflow Management Coalition . Wf-XML is designed and implemented as an extension to OASIS   Asynchronous Service Access Protocol . ASAP provides a standardized way that a program can start and monitor a program  Program Manager Joint Computer Aided Logistics Support System JCALS prime Contractor CSC sponsored Wf-XML XPDL: The  XML  Process Definition Language (XPDL) is a format standardized by the  Workflow Management Coalition  (WfMC) to interchange  Business Process  definitions between different  workflow  products,   IBM ,  Hewlett-Packard ,  Fujitsu ,  ICL …, (XML) Workflow over TCP/IP Unicast / Multicast The Heart Beacon is process based, system, application and program neutral workflow based procedure set. Mission Threads Are Analogous to Workflows 7 – 64 Template Systems A Football Field Apart Yet World’s Away Structured Generalized Markup Language SGML begat XML
  • 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 grids to Share data - organize distributed data as a collection Digital 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.
  • 1 1 3 4 1 correlated event .0001 05 1 3 5 10 30 E9-1-1 PSAPs NORAD TRACK DATA GIG 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 > / < radius of disaster / event / alert represented by multicast zones corresponding to US / UK... five level advisory systems Use heartbeat / beacon function (send to / get from devices, platforms...) as a subnet publish-subscribe e.g., OSD Horizontal Fusion. Use intrinsic millisecond - 99 minute timing function consistent, synchronized collection of state meta data (geo location, moving, halt, IP address, unit / organization ID) BEFORE transfer to queues, folders 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 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 (&quot;network of networks&quot;) & Z systems (&quot;system of systems&quot;) IPICS CAP XML .mil Range Extension TDN/CONDOR Gateway Split / Joins SoS Heartbeat Messages XML Repositories Authorized Efficient XML Qualcomm BREW NIEM GJXDM FXR SoR C2IEDM “ Maneuver the network” “ Spontaneous Organization” Common Symbology Unified 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 Track Received MIBs Heartbeat Message Heartbeat Message State Meta Data Joint Mission Data Loader JACAE COASTS: Coalition Operating Area Surveillance Targeting System CONDOR OPEN Systems & Network Management MIB Tool Router Config State meta data for Network reconfiguration Split, joins, adds Heartbeat Messages Boston U Beacon NTCDESC JBMC2 BoD NC FCB JVMF, USMTF, TADILs, OTH-Gold, Adat-P3, FIRNS, FUDNs &quot;DFI, DUI's… UICDS Heartbeat Protocol low level state meta data harvester Use to conserve bandwidth before handoff to more sophisticated protocols / mechanisms that in turn use the heartbeat mechanism FAST C2AP UC BERKELEY SEA GULL Files, queues, folders, SANS, dbase, caches, flat files… Convert to XML tags Efficient XML Qualcomm BREW SoS Track Received CESAC UICDS NOC-V NCharT FIOP/ SIOP/ UDOP DIRS DHS TRIPWIRE Learning Systems AI N Systems /Networks AI Learning Systems Stored Process & Procedures Lean Six SIGMA NEMESIS NIMS WITS FusionNET ICEWS Multi-Modal Layered Analysis of Network Architectures for Threat Detection & Prediction (LANA) FLUX UCORE 2.0 Rules Engine Workflow Qualcomm BREW UCORE NEIM Payloads INFOBLOX Orchestration Server FIRST RESPONDERS .com, .org, .edu IPAWS HIMSS Alert Level Increase … Increase Multicast Zone COMMON SYMBOLS III THE BIG RED BUTTON II SYNCHRONIZED EVENTS / ALERSI E R I C
  • Mission Data Loader NOC-V NCharT End to End System Heartbeat TEMPLATE SYSTEM TO UNIVERSAL FRAMEWORK CONVERSION BIG RED BUTTON SYNCHRONOUS Event Timing COMMON SYMBOLS
  • Enable across N complex systems, Y networks (&quot;network of networks&quot;) & Z systems = Single Integrated Operational Picture 1 2 3 4 5 6 NETWORK INITIALIZATION PROCESS BEGIN NETWORK CONFIGURATION PROCESS ENGAGE Heartbeat sub-protocol set to gather state meta data from sub net users i.e., UMTS cell and smart phones or military JTRS radios Load current map sheet via Mission Data Loader / laptop Load template mission network initialization data S6 / Sys Admin aggregates heartbeat messages into Unit / Org Task using TIMS / Network Configuration Agent S6 / Sys Admin broadcasts Unit / Org Task via multicast / uni / anycast or SMS or beacon protocol of choice…. TIMS – Tactical Internet Management System / Commercial Equivalent CISCO IPICS / Juniper CESAC etc. operator populates Hasty Reorganization Tool from state meta data gathered by heartbeat from devices / platforms to generate new Unit Task Order UTO with next UTO version number, effective Date Time Group DTG sync Time (K00.99 heartbeat message option UTO notification Geospatial, scenario viewers / applications / browsers Schema Tools to edit Common Alert Protocol (CAP). Transmit CAP Unit Task Order (organizational structure NIEM payloads) via SMS, bots, JXTA motes, agents, email, Groove Simple Symmetric Transport Protocol SSTP, any commercial data distribution, CAP XML Integrated System Control: ISYSCON Wizards & UTO Tool commercial equivalent S6 / Sys Admin Sends out initial UTO message. FBCB2 processes UTO notification & sets timer to execute change at effective time Heartbeat Process: (TIMS/FBCB2 engine) generates Heartbeat message every 1 / 3 / 5 / 10 / 15 / 30 minutes with UTO version. GTCS – Ground Tactical Communications Server passes heartbeat to state manager (Variable Message Format VMF) 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 TIMS generates new Multicast Group (MCG) file, 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 Address LDAP Command Control Registry C2R Server update tool executed as multicast group file, UTO version number & the AIS will ignore if it already has one set) C2R – Lightweight Directory Access Protocol LDAP Server multicast MCG update tool updates multicast group data on the Army Information Server / EOC Server 9 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. NETWORK RECONFIG PROCESS UPDATE NETWORK STATE FINAL RECONFIG & BROADCAST Split / Joins, Adds 1 correlated event .0001 05 1 3 5 10 30 7 8 SIOP FIOP 2 UTO Ground Tactical Communications Server GTCS gets SM or C2R server alert, reads updated MCG from C2R then updates internal config file & LAN card if platform affected Tactical Internet Management TIMS Situational Awareness Application E R I C INFOBLOX Orchestration Server
  • 1 correlated event Enable across N complex systems, Y networks (&quot;network of networks&quot;) & Z systems = Single Integrated Operational Picture 1 2 3 4 5 6 7 8 NETWORK INITIALIZATION PROCESS BEGIN NETWORK CONFIGURATION PROCESS ENGAGE Heartbeat sub-protocol set to gather state meta data from sub net users i.e., UMTS cell and smart phones or military JTRS radios Load current map sheet via Mission Data Loader / laptop Load template mission network initialization data S6 / Sys Admin broadcasts Unit / Org Task via multicast / uni / anycast or SMS or beacon protocol of choice…. TIMS – Tactical Internet Management System / Commercial Equivalent CISCO IPICS / Juniper CESAC etc. operator populates Hasty Reorganization Tool from state meta data gathered by heartbeat from devices / platforms to generate new Unit Task Order UTO with next UTO version number, effective Date Time Group DTG sync Time (K00.99 heartbeat message option UTO notification SIOP DMOC 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, Unified Network Manager Agents Wizards & UTO Tool commercial equivalent S6 / Sys Admin Sends out initial Unit Task Order UTO message. FBCB2 / Situational Awareness App processes UTO notification & sets timer to execute change at effective date time group DTG 2 Heartbeat Process: (TIMS/FBCB2 engine) generates Heartbeat message every 1 / 3 / 5 / 10 / 15 / 30 minutes with UTO version. EOC / Computer Aided Dispatch CAD passes heartbeat message to state manager At effective date/time, All SA Agents in multicast group reconfigure database to ensure proper Situational Awareness SA Calculation, SA intelligent Agent prompts to reconfigure or delay 10 minutes (w/option to change at anytime). When operator OKs, database is rebuilt & network reconfigures Network Agent generates new Multicast Group (MCG) file, if required, Network Agent MIBs & CISCO / Juniper Agent etc router configurations automatically @ Effective time. Net Config Agent calls the ModifyMCGInfo API (Subnet filename, MCG filename, UNIT URN, UTO version, Local IP Address LDAP Command Control Registry C2R Server update tool executed as multicast group file, UTO version number & the AIS will ignore if it already has one set) C2R – Lightweight Directory Access Protocol LDAP Server multicast MCG update tool updates multicast group data on the Army Information Server 9 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. NETWORK RECONFIG PROCESS UPDATE NETWORK STATE FINAL RECONFIG & BROADCAST Learning Systems AI UTO S6 / Sys Admin aggregates heartbeat messages into Unit / Org Task using TIMS / Network Configuration Agent Communications Server gets State Manager or C2R server alert, reads updated MCG from Comm/Directory Server then updates internal config file & LAN card if platform affected Tactical / EOC Internet Management TIMS / CAD INFOBLOX Orchestration Server .0001 05 1 3 5 10 30 CAP XML Situational Awareness Application EOC Split / Joins, Adds E R I C
  • COMMON SYMBOLS III THE BIG RED BUTTON II Synchronized Event / Alerts I I II III 3 Building Blocks 4 Focus Areas Consistent, Synchronous Time stamping of Raw state meta data 1 2 3 4 Maneuver the Network Spontaneous Organization Heartbeat Messages Split / Joins, Adds Router MIBs Files, queues, folders, SANS, dbase, caches, flat files… CAP XML Unified Activation Authorized NOC Workflow / Mission Threads Chop-chain / Business Logic Spontaneous integration X family of systems via Y networks (&quot;network of networks&quot;) maneuvering by COI’s / COP’s workflow filters
    • Multicast / Cell broadcast
    • Radius / Zone
    • / <
    • thresholds & intensity
    .0001 .05 .01 1 5 15 30 1 correlated event SoS JPL BMOX “ Our cause is noble; it is the fate of mankind. G.W. The Heart Beacon tm : Systems, Process & Network Management “NETOPS” Computer Aided Dispatch Spontaneous Integration NCharT DIRS NIMS IPAWS - Child schemas for COIs, profiles, - data islands for special needs i.e; specific area encodings, inject points option fields, PIPS Vs PSAPs.. - data files for fast movers unique requirements & event code signaling Tripwire AI 6 Sigma Special Needs NIMS WITS OneNet NIEM Payloads INFOBLOX Orchestration Server Alert Level Increase … Increase Multicast Zone SEED SYNC _CLOUD E R I C
  • NET EFFECTS GSA NETWORX DHS EAGLE II Boston U Project Beacon SEAGULL Situational Awareness CDRLS Sentinel .0001 .05 .01 .1 5 15 30 99 .0001 .05 .01 .1 5 15 30 99 PROJECT BEACON 1994 SABRE DISA SOA End to End System Heartbeat Alert Level Increase … Increase Multicast Zone Payloads DHS Tripwire MESA 1 correlated event .0001 05 1 3 5 10 30 S2IOP DMOC UTO JPL BMOX BIG RED BUTTON SYNCHRONOUS Event Timing COMMON SYMBOLS EDEN Environment Exchange Data Network Qual comm / Verizon DOD H.A.A.R.P Data Centers Workflow NISAC SIP SOA Publish-Subscribe Over Multicast COMMANDER’S INTENT UNIT TASK ORDER FLUX Telecomm CDRLS DMOC CAP XML Comm/ Elec Time Travel Messages MIT PAUL REVERE NSF / DREN INTERNATIONAL BEACON NETWORK Tribalization of Business INFOBLOX Orchestration Server CAP XML JTF GNO GIG NCES NECC COSMOS SEED SYNC _CLOUD
  • “ Our Cause is noble; It is the fate of mankind” G.W. Spontaneous Integration Consistent, Synchronous Time stamping of raw data 1 2 N complex systems Y contracts Z organizations Get from Send to Publish-Subscribe Subnet meta data Multicast radius Increase / decrease with alert condition 4 Sea Gull UC Berkeley - child schemas - data islands - data files 1 Unified Alerts 3 Maneuver the Network SABRE DHS DECIDE “ Nothing less than net-centric homeland security akin to network centric warfare” Silicon Valley Region Data Interop Project   LAPD Operation Archangel MCNOSC Navajo Code Talkers Hall NISAC SOS SEWS Net Enabled Operations for the Greater Good DMOC INFOBLOX Orchestration Server CLEO IRIS NATIVE AMERICAN DISASTER NETWORK  CAP XML INTERNATIONAL BEACON NETWORK Common Symbols COMMON SYMBOLS III THE BIG RED BUTTON II SYNCHRONIZED EVENTS / ALERTS I E R I C SEED SYNC _CLOUD
  • Wardenclyffe Tower Long Island NY Wardenclyffe Tower 1901–1917 Tesla’s Tower, was a wireless telecommunications tower designed by Nikola Tesla and intended for commercial trans-Atlantic wireless telephony, broadcasting, and to demonstrate the transmission of POWER (hidden purpose from JP Morgan) w/o interconnecting wires. TESLA COIL: steps up Electricity to high voltages that are RADIO SIGNALS Qual comm / Verizon DOD H.A.A.R.P “ Our Cause is noble; It is the fate of mankind” G.W. IONOSPHERE IONOSPHERE THE TRUE STORY OF NIKOLA TESLA 300 feet underground 16 Iron Pipes Synchronicity among N Complex Systems Additional state meta data types = More network management options And opportunities for enhanced, SYNCHRONIZED, cross system Public Fee for Services Network Centric Warfare for the Greater Good Synchronicity, Interoperability, Common Symbols Computer Aided Dispatch Spontaneous Integration BML SEARCH BY ORG IG Universal Resource Name URN INFOBLOX Orchestration Server NISAC DOE DHS 1 correlated event .0001 05 1 3 5 10 30 SIOP FIOP 2 UTO SEED SYNC _CLOUD
  • Rainbow Force Tracking
    • ISSUE: E9-1-1 // DOD / DHS systems use building blocks (e.g., heartbeat / beacon sub-protocol, CAP, NIEM) & heartbeat network (re) config messages) DIFFERENTLY
    • Network Centric Warfare template applied to DHS Blackberry handhelds 04
    • DHS Program of Record: BAA08-01, DHS S&T Long Range
    • Distributed Environment for Critical Infrastructure Decision-making Exercises (DECIDE)
      • Command, Control, and Interoperability (CCI) Division
      • Distributed Missions Operation Center DMOC
      • Computer Aided Dispatch Spontaneous Integration Process FCC ERIC
    • DECISION :
    • Transition / translate template system’s procedures, filters & workflow logic to public information & human services e9-1-1 NexGen i.e., “Rainbow Force tracking” synchronized, authoritative SA as n-1-1 fee for Public Services:
    “ THINK SYNC” INFOBLOX Orchestration Server Congress: “Nothing less than net-centric homeland security akin to net-centric warfare” Common Operational Picture (COP): A single IDENTICAL display of relevant information shared by more than one command. A common operational picture facilitates collaborative planning and assists all echelons to achieve situational awareness. US Joint Force Common Glossary //Wikipedia SYBC SEED _CLOUD