User talk:Stevenjmcgee

From NECSIWiki

1 The HOMELAND HEART_BEACON
2 The International Homeland Heart_Beacon for interoperability, synergy & synchronicity
3 The Healthcare Heart_Beacon
4 QUAD CHART: THE HEARTBEAT BEACON BY NUMBER
5 "You just can't make this stuff up". Reverend Kathy Graves Circle of the Sacred Earth

[edit] The HOMELAND HEART_BEACON

The Homeland Heart_Beacon... "the only thing constant is change....

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 agree on common, settings of three common denominators:

= 7

The Heartbeat Beacon is based on three common building blocks iteratively and systemically processed through four focus areas:

IF III Building Blocks are applied then interatively and systemically processed through 4 focus areas:

III BUILDING BLOCKS:

I Consistent, synchronous timing of platform – device state meta-data collection using the heartbeat / beacon’s intrinsic millisecond - 99 minute timing function enabling consistent, synchronized collection of raw state meta data (geo location, moving, halt, straggler, duress, IP address, unit / org Universal ID) BEFORE transfer to queues, SANS, dbase... prior to distribution / dissemination then data fusion improving filtering / intelligence fusion.

II “Maneuver the network”: Collected state meta data enables network management of router Management Information Bases MIBs by 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…) . Functionally enable re-planning of missions dynamically, based on the actual, synchronized situations. Allow the planning/re-planning processes to be reengineered on the fly to interleave them with cross-domain execution monitoring with automated planning decision aids. Make integrated battlefield data accessible at all times, independent of location (e.g., OPenDAP, NEMSIS)..

III Instantiate chopchain - workflows – business logic over multicast / anycast IP using “true cots” tools i.e., Towersoft w/AgileDelta Efficient XML module embedded via the Common Alert Protocol CAP (XML child schemas and or data islands / embedded files ) to support multicast, unicast/or anycast distribution of events, alerts via a unified alert / event trigger mechanism = OASIS ratified CAP with child schemas and / or data islands to accommodate Communities of Interest (COI's) e.g.; financial, disaster, event, alert, 311/411/511/711/911 services

4 FOCUS AREAS:

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.

THEN:

Enable across N systems, Y networks ("network of networks") enabling "the grail" e.g., SIOP / FIOP

ELSE: Business as usual situational awareness "jitter" among N complex systems, fusion centers and TIC / TAC / TOCs // EOC's, EAC's // .... inconsistent symbol sets, and 30 second web page screen scrapes dependent on intrasystem gateways / connectors instead of millisecond beacon technology updates (e.g., the pre-9/11 Maneuver Control System Blue Live Feed requirement unfulfilled to this day).

[edit] The International Homeland Heart_Beacon for interoperability, synergy & synchronicity

Network Situational Awareness NetSA as n-1-1 Public Services

The International Heartbeat Beacon is fundamentally a network management procedure / methodology transitioned from the DOD to the DHS (Blackberries, Palm Pilots etc) several years ago. When Blue Force Tracking derived procedures / methods are transitioned to the e9-1-1 community through the world's Public Safety Answering Points / PSAPS, this will leverage our taxpayer investment in Network Centric Warfare ala the Clinger - Cohen Act of 1996; it will provide Situational Awareness (e.g., medical triage by multicast zone, geo fencing) as a Public Service, establish network forensic accountability & "democratic" exchange of emergency / threat / warning information Showing a tidal wave that travels 30 miles inland by radius would be helpful. Early warning of an event by intensity by zone (vulnerable buildings within a given radius) would be helpful. Showing a pandemic disease spread prediction by zone / radius would be helpful. Using consistent geo fencing services to depict / alert quaranteened areas through multi-cast radii will be helpful.

[edit] The Healthcare Heart_Beacon

Medical triage, alert, evacuation, alternate routing of transportation assets, will then adjust & filter consistently by business logic / mission threads by zones. Organizations, entities, platforms, vehicle, mobile smart phone type & sensor equipped devices via router/switch 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 / and e9-1-1 // n 1-1 Public Services.

Medical community professionals do not need explanations of products and systems by me. The Health Care Heart_Beacon is unique and original (purpose of a patent is to establish originality --criteria the DHS S&T Directorate is looking for in an unsolicited proposal) because of the synchronicities between key organizations, individuals and their missions and goals. For example, CAPWIN is a university led (University of Maryland) effort that promotes interoperability within the national capital region as does the Navy Medicine Joint Taskforce CapMED. Same goals, same area and customer base waiting for cross fertilization between best of breed approaches between IBM and General Dynamics (CAPWIN primes) who also happen to be Joint Blue Force Tracking JBFSA template system providers (General Dynamics). IBM not only the prime with CAPWIN, it is prime for a New York State THINC / Heal1 that synchronistic ally is linked to the North Carolina NCHICA effort by IBM (New York State and the Research Triangle in North Carolina being two main IBM centers of gravity). North Carolina is home to the 18th Airborne Corps that represents approximately half of the Army's combat power, is a JBFSA template system user, a DOD Horizontal Fusion project that benefits from Naval Post Graduate School STAN/TNT project that is a DOD effort that is well known to DISA -- provider of the Network Centric Services key enablers... That two of the United States / World's Health Care luminaries also happen to be co-chairs of the e9-1-1 Congressional Caucus is another key synchronistic opportunity in this area that has more cross associations that can be discussed in this forum. Another quick example is Intersystem's Cache' product that is widely if not predominately in use by military hospitals -- and you just thought I liked the letters :>]

CodeBlue: Wireless Sensors for Medical Care includes applications of wireless sensor network technology to a range of medical applications, including pre-hospital and in-hospital emergency care, disaster response, and stroke patient rehabilitation The Pluto mote, designed here at Harvard, is a scaled-down version of the Telos designed to be small, lightweight, and wearable. The Pluto incorporates a tiny, rechargeable Li-ion battery, small USB connector, and 3-axis accelerometer. It will be used initially for monitoring physical activity and motor functions.

CodeBlue MoteTrak: Harvard University / Boston Medical Part of the CodeBlue system includes MoteTrack, a system for tracking the location of individual patient devices indoors and outdoors, using radio signal information. In MoteTrack, a hospital, clinic, or other area is outfitted with a set of fixed radio beacon nodes that are used to calculate the 3D position of the wireless sensors, which may be attached to patients, carried by physicians or nurses, or attached as "location tags" to medical equipment. MoteTrack has been demonstrated in a building-wide deployment at Harvard and yields an 80th percentile error of about 2 meters, which is more than adequate for many location-tracking applications. SOA: DISA’s Service Oriented Architecture (SOA) product (Amber Point) employs an end to end heartbeat protocol, heartbeat XML message based system health monitor of the Network Centric Enterprise Service - NCES runtime environment that it is offering to all other agencies.

BACKGROUND: A congressional directive states "nothing less than network centric homeland security akin to network centric warfare".

The goal "grail" is to create a single integrated operational picture -- SIOP from cross domain data fusion of N domains / Community Of Interest COI's.

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.

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.

Carnegie Mellon University Software Engineering Institute SEI CERT Team: The CERT Network Situational Awareness group develops engineering solutions and research approaches for analyzing broad network activity. The goal is to quantitatively characterize threats and targeted intruder activity. As an example of the dozens of useful tools that CERT provides as open source, RAVE: Network Flow Visualization is a fully automated analysis is a valuable tool for network situational awareness, given that few techniques can discern subtle patterns in noisy data as well as human visual inspection. The CERT Network Situational Awareness Group has developed the Retrospective Analysis and Visualization Environment (RAVE), an operational environment for generating visualizations and making them available to presentation applications. RAVE would have served the post 9/11 analysis effort well.

The Heartbeat sub-protocol of the TCP/IP (Internet) stack 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-terrainian, ocean floor…

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.

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 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 interchangably 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.

Alerting building residents susceptible to earth quakes of a given magnitude or higher by intelligent alerts by filters and subscriptions will be helpful in cases on the recent Chinese earthquake lakes e.g., use of NOAA / USCG / NWS HADS Hydrometeorological Automated Data System HADS / GOES-R streamflow data.

‘These days, the problem isn't how to innovate; it's how to get society to adopt the good ideas that already exist.’ — Douglas Engelbart

Uses of the heartbeat beacon range from calling in help, bringing in teams, groups, logistics support, and subject matter experts to a crisis zone defined by community of interest described alert and event thresholds. The opposite, evacuating areas based on thresholds and types of events and alerts – say a Tsunami, is achieved by sensors located on buoys on the ocean’s surface and floor sampled in the millisecond to 99 minute range enabling an estimate of coastal areas impacted. The multicast zone’s emulating multi-level alert radii described by color codes and Shepard tones for the deaf / hearing impaired or situations where checking a screen for a change in color is not practical given the situation will alert subscribers to evacuate or rally to an aid station or take action as the case may be.

After the Katrina disaster, the council of Mayors agreed that military involvement was needed as soon as possible. Applying three common denominators in four focus areas is a simple solution. Apples to apples and oranges to oranges collaboration is improved by the heartbeat beacon methodology in establishing common symbol sets, synchronous data refresh rates designed to not saturate limited available bandwidth or too slow refresh rates resulting in overcome by events reporting.

Inspired by Paul Revere’s famous “one if by land, two if by sea” ride to alert the Colonists to the arrival of the British 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."

ISSUES RESOLVED:

- Common event / alert trigger instantiated by a common alert structure (Common Alert Protocol - CAP)

- Linkage of military message threads with .gov, .com, .edu workflows / business logic

- Non-interoperability of symbolic representation, formats (mil standard vs. .com)

- CAP symbols geographic shapes or blobs. .MIL symbol sets resolve to platform level by type

- Dissimilar XML tagging formats btwn .mil /.com / .gov, .edu.. = error inducing, time, intensive gateways

- Inconsistent network state info sampling rates (timing), event / alert reporting timing rates impairs data fusion across multiple complex systems given situational awareness data collection time tagged event / alert at different intervals (e.g., millisecond, seconds, 1, 3, 5, 10 minutes)

- Reduced “swivel chair” analysis caused by duplicative same event injections on same / different screens

- “De-babel-ized” semantic common meaning across disparate communities of interest COI’s by converting message / data exchanges from proprietary, closed military structured messaging standards to OPEN universal web

The heartbeat protocol is part of the TCP/IP stack. The heartbeat function is best known for polling devices asking for an acknowledgement revealing whether the device is "alive". Its role in failover sensing for disaster recovery traces back to the TCP/IP’s DARPA origins. The heartbeat protocol / beacon / heartbeat chunks (the term is used interchangeably by industry) can query target devices on subnets for information stored on the device. This information / data such as IP lease, current GPS location & time stamp can be harvested in the millisecond range to up 99 minutes. This data can be placed in local queues, file folders, or data stores as a mini "publish-subcribe" function for onward distribution by more modern & flexible protocols e.g., JPL's OPenDAP, Sun Microsystem JXTA based SPIDAR by BBN, Harvard's Hourglass, South West Research Institute’s SABRE Beacon, DARPA's Cougaar now commercialized etc...

The Heartbeat Beacon is a method to commercially adapt battlefield proven Force XXI Battle Command Brigade and Below (FBCB2) / satellite network adapted Blue Force Tracker – BFT, Battlefield Awareness Data Distribution – BADD, Special Operations Force Network SOFNET… for commercial First Responder use.

Since these war proven template systems are essentially workflow logic broadcast with filters by TCP/IP internet unicast, multicast groups –e.g., Verizon’s VCAST. In this way; 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 can be instantiated in times of crisis.

The military tends to handle network mobility more efficiently than the commercial sector having established a procedure to harvest network state information about their organizations that translate to moving units from network subnets based on operational need. Since routers work the same way whether purchased by the military or mayors, the heartbeat beacon’s methodology will enable organizations and military units to organize for a common cause by tethering and untethering to networks in an adhoc yet purposeful manner. Since response involves dispersal of funds, the Heartbeat Beacon will also serve to notify communities that funds have been transferred or released to a disaster zone. The FBI deployed a team to monitor financial transaction data stores following 9/11. Gathering state meta data from target platforms, hosts and subnet or cells of interest (i.e., the function of the DHS’s TRIPWIRE shown in the lower left hand quadrant IV in figure 2 below); will serve to notify units of action (UA) in military speak to converge on suspected terrorist financial activity. Teams monitoring financial activity (e.g, a core CIA activity) will be synchronized with local law enforcement teams responsible for detainment and arrests. The concept involves spontaneous integration of a CIA or FBI anti-terrorism squad using the XML heartbeat messages of the SWIFT based Terrorist Finance Tracking Program. The Terrorist Finance Tracking Program is a United States government program to access the SWIFT transaction database, revealed by The New York Times in June 2006. It is part of the Bush administration's "Global War on Terrorism". Based in Belgium, SWIFT (Society for Worldwide Interbank Financial Telecommunication) establishes common standards for financial transactions worldwide.

The Heartbeat Beacon includes four focus areas:

FOCUS AREAS:

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 (now commercialized), 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") 3 + 4 [0] = 7 // 407

GOAL: Simulate a mission thread / workflow exchange representing the National Command Authority “chop chain” between the MIT experimental aircraft Paul Revere with a sample of First Responder systems demonstrating that military network centric warfare procedures can be applied commercially demonstrating improved event mitigation.

Goal Detail:

(1) Establish a common data collection time stamp among Situation Awareness (SA) producing systems reducing “swivel chair” analysis across high level emergency / military command control centers

(2) Improve on faster than 30 second web server / Army Information Server derived screen scrape transactions too slow for targeting through use of beacon transponder technology.

(3) Use (Efficient XML encoded) XML tags vice military unique FFIRNS and FUDNS, DFI – DUIs incompatible with First Responder systems to establish common symbology.

(4) Resolve the issue of rich encoding (e.g., Microsoft Office Binary Large Objects – “blobs” on the “upper tactical internet” to users on the “lower tactical internet” that see mangled & disjoint sync matrixes that are Microsoft Excel spreadsheets on the commercial side of the equation. Close the “fidelity gap”

(5) Emulate the DHS Homeland Security Advisory System increasing / decreasing alert radius / event levels via (Sea Gull/Boston U Beacon Project) beacon multicast radius user defined thresholds.

[edit] QUAD CHART: THE HEARTBEAT BEACON BY NUMBER

QUAD CHART FOCUS AREAS:

Enable across N complex systems, Y networks ("network of networks") and Z systems ("system of systems")

The Heartbeat Beacon will be powered by a rules based workflow / data base engine called "iROD" that is open source, National Science Foundation Sponsored as developed by the San Diego Super Computing Center.

iRODS™ is a data grid software system being developed by the San Diego Supercomputer Center (SDSC) Storage Resource Broker (SRB) team and collaborators. The system is based upon the expertise gained through the application of the SRB technology in support of data grids, digital libraries, persistent archives, and real-time data systems. The management policies (sets of assertions that these communities make about their collections) are being characterized in terms of rules and state information. At the iRODS core, a Rule Engine interprets rules to decide how the system is to respond to various requests and conditions. iRODS is open source (under a BSD-type license). iRODS is an excellent rules based engine/workflow engine to power the Heartbeat Beacon.

Applying iRODS in system to close the "9/11 gap" between military fast movers and the Federal Aviation Administration using assets like iRODS that is from San Diego with Marine Corps tactical networking and communications interoperability products also developed in San Diego's Camp Pendleton and north of Camp Pendleton in the Fort Hunter-Liggett/Camp Roberts/Naval Post Graduate School area then northward to Silicon Valley's 14th Congressional District Home to one of the e9-1-1 Congressional Caucus Principles Anna Eschoo with NASA and commercial sector technology shown in other slides... (not forgetting JPL/NASA's Disaster Management Constellation & OPENDAP shown on other slides). Qualcomm is a San Diego based firm (Qualcomm stadium for the San Diego Chargers)....

UNITED STATES CITIZEN CORPS NET GUARD // FEMA

The need for common, consistent data harvesting at the edges prior to injection into the many fusion centers is most strikingly demonstrated by the Defense Intelligence Agencies Overwatch Virtual Operations Center VOC mashup. Drawing from thousands of intelligence professionals from dozens of intelligence sources, Overwatch integrates multiple intelligence sources into a desktop intelligence asset dashboard. Overwatch provides desktop situation awareness of military information. Overwatch consists of a personalizable, desktop-like intelligence asset dashboard or 'webtop' developed using JackBe's NQ Suite AJAX development platform, and a middle tier that discovers and displays intelligence data sources without any additional front-end or back-end development required. The entire solution is accessible through a standard Web browser, with no proprietary downloads or plug-ins required.

Displaying an identical common picture drawn from dozens if not hundreds of disparate sources requires the consistent harvesting / tagging of data at the edges prior to injection into fusion centers – the simple intent behind the Heartbeat Beacon concept. With the DIA’s 11,000 employees virtually partnered with say for example, FEMA’s NET Guard’s n citizens from across the nation / world, consistent harvesting with millisecond beacon transaction speeds contrasted with 30 second web server screen scrapes is clear. JackBe supports both the Defense Intelligence Agency’s Overwatch and Citibankthat would necessarily use the world standard SWIFT / heartbeat XML messages described elsewhere in this paper. The FBI immediately deployed teams to Omaha Nebraska looking for the terrorist money trail after 9/11. These disparate communities need consistent temporal data tagging of the Heartbeat Beacon and the millisecond data exchanges of broadcast / multicast / beacon technologies anchored by Six Sigma Processes.

Microsoft’s FusionX: an intelligence fusion center architecture, as the foundation with InfoPath / Biztalk with AgileDelta’s Efficient XML mobile information client / module embedded in InfoPath as the template / forms engine enabling users to activate / react to all hazards using every day tools – e.g., Microsoft Office with Groove Network’s Groove Framework (see diagram Figure 7: Commercial Heartbeat Beacon Framework interacting with Sharepoint e.g., DOD’s Defense Collaborative Tool Suite DCTS and / or commercial equivalent packages. DCTS and the Army's Information Dissemination Management Terrestrial IDM-T that is hubbed around Microsoft's Sharepoint as is the DHS Homeland Security Information Sharing Network or HISN (top center) with the INFOPATH forms engine may be the true grail for the masses – an all hazards activation / response using familiar every day tools.

                                        BUSINESS CASE

Simulate a mission thread / workflow exchange representing the National Command Authority “chop chain” between the MIT experimental aircraft Paul Revere with a sample of First Responder systems demonstrating that military network centric warfare procedures can be applied commercially demonstrating improved event mitigation.

Since the above cited CONDOR / NOC-V / NISAC / PSIC / PIP / UCC ...(re) planning scenario is functionally enabled in both battlefield and DHS programs (situational awareness to Blackberry devices by the same system integrator who has partnered with a global IP services provider with a footprint in 500 cities worldwide), it and other widespread frameworks (e.g., FEMA’s Disaster Management Interoperability Services – DMIS combined with OPEN Platform for Emergency Networks interoperability framework in collaboration with Oak Ridge National Laboratories Sensornet that is in use at Fort Bragg NC home of the 18th Airborne Corps -- an ideal post to integrate with heartbeat protocol / heartbeat XML messaging FBCB2/Blue Force Tracking equipped units.

Tactical Network Topology TNT (previously STAN). TNT is an integrated program field experiments that develop and demonstrate new technologies to support near term needs of the warfighter. Major emphasis is on wireless networks, autonomous vehicles, sensor networks, situational awareness and target tracking and identification. USSOCOM's Futures Directorate (J9) conducts experiments at NPS in conjunction with the USSOCOM Advanced Technology Directorate. These experiments focus on identifying key gaps and deficiencies resulting from applications of advanced technology, particularly network communications, unmanned systems, and net-centric applications – ideal to support the Heartbeat Beacon’s similar focus. TNT includes special operations force (SOF) systems engineering and integration.

Infrastructure testing focus would be the DHS funded NISAC National Infrastructure Simulation and Analysis center assisted by universities and select corporate entities using the Defense Research Engineering Network DREN and DISA’s Federated Development and Certification Environment providing network centric warfare subject matter experts and Common Alert Protocol XML child schema, data islands and (Efficient / BREW) encoded small flat files replacing traditional structured military message formats DISA’s XML laboratory in Fort Huachuca Arizona at the JITC would be a logical choice for this task. JFCOM’s Joint Center for Operations Analysis would provide the workflow to mission thread chop chain expertise across tactical and strategic systems.

Replicating war proven procedures that organize and "maneuver" both the military and commercial leased portions -- the entire homeland security and defense, private sector portfolio -- of networked devices that may be 80% leased by the military is the goal. Since the major defense contractors are paired with the major Telco giants bidding on the major (telecommunications) contracts e.g., NETWORX, the business case to leverage what the government widely employs now completely across our (inter) national portfolio. "Maneuver the network" involves changing router databases MIBS supporting hasty (re) organization, adds, splits, joins... of disparate organizations that suddenly must collaborate apples to apples, oranges to oranges. When federal system integrators as partnered with the telco network providers supporting key federal network centric contracts (e.g., GSA NETWORX, ALLIANT, SATCOM II, DISA ENCORE II, DHS EAGLE....) agree on three common denominators / building blocks, direct, synchronized, interoperable collaboration based on synchronized event timing and common symbols will be achieved.

Microsoft’s FusionX: an intelligence fusion center architecture, as the foundation with InfoPath / Biztalk with AgileDelta’s Efficient XML mobile information client / module embedded in InfoPath as the template / forms engine enabling users to activate / react to all hazards using every day tools – e.g., Microsoft Office with Groove Network’s Groove Framework (see diagram Figure 7: Commercial Heartbeat Beacon Framework interacting with Sharepoint e.g., DOD’s Defense Collaborative Tool Suite DCTS and / or commercial equivalent packages. This may be the true grail for the masses – an all hazards activation / response using familiar every day tools.

Microsoft technology centric, FusionNET developed for and by the 18th Airborne Corps to address the command and control needs and capability gaps they foresaw, the XVIII Airborne Corps developed capabilities to provide web access for key operational data across functional areas. The purpose of this effort, termed “FusionNet,” was to allow the Corps to:

Enable the art of command as well as the science of control by using cognition to achieve knowledge and judgment to achieve understanding, thereby enabling decision makers at all echelons to give accurate and timely guidance within the context of the current situation on the ground. Functionally, FusionNet is a suite of applications designed to meet the need for timely, accurate and relevant information from the company through corps echelons, across all Battlefield Operating Systems (BOS) and functional areas, in garrison and in the field. The intent of FusionNet is to complement existing Army and Joint battle command and enterprise information systems, bringing information from the enterprise to the desktop of commanders and staff in operational units and making ground-truth information from the lowest-connected echelon available to the enterprise.

One key aspect of FusionNet is the recognition of the presence of critical data across the battlespace in disconnected databases. The Corps implemented Fusion Net to the tactical level to create a common data entry and management method for critical operational data. As an example of desired functional end state, FusionNet will take combat patrol reports (SIGACTS) and provide operational fusion capability that will interoperate with the Joint Intelligence Operational Capability – Iraq (JIOC-I), which provides Intelligence fusion, to provide the commander with the ability to share real time data, horizontally and vertically.

FusionNet was not the first initiative outside of ABCS to address the Army’s failure to provide a standardized Battle Command Knowledge Management tool to meet operational requirements. What XVIII Airborne Corps did that previous commanders did not was seek formal Army approval of an Operational Need Statement (ONS). Maneuver Control System had made significant strides in web integration of the COP, but the requirements demanded in the FusionNet concept did not have basis in any ABCS Operational Requirements Document.

Materiel developers assisting MNC-I prior to ONS approval and funding were doing so at risk of reprimand and removal of funding. Regardless of requirement justification, MNC-I pursued the FusionNet initiative, seeking to tie situational reporting tightly with the JIOC-I. In a memorandum by the Multi-National Force – Iraq Information Management Officer, the integrative capability of FusionNet and JIOC-I was showing operational benefit.

The JIOC-I and FusionNet will assist in solving some of the critical Intelligence Operations information management shortfalls in Iraq. FusionNet is the operational reporting capability and JIOC-I is the Intelligence analytical capability. These combined capabilities will enable Soldiers to rapidly exchange intelligence and operational data, and visualize the data in geospatial context.

Juniper Network's [CESAC]: Command Enterprise Situational Awareness & Control by Juniper Networks: “Protect, Detect, React, Recover” will be a key enabler setting up network preconditions for other systems and networks to synergistically combine together towards a common cause and will speed recovery through cross system and network synchronicity. Providing the network backbone for the Defense Research Engineering Network or DREN, over 150 EDU's and the technology cited in these slides and papers will give new meaning to the phrase "the whole is greater than the sum of the parts".

Commercial Equivalent Open Framework

                                    TEMPLATE SYSTEMS CONVERTED TO COMMERCIAL EQUIVALENT

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.

The nearly universal heartbeat protocol as a low level data harvester, publish – subscribe & timing mechanism (2nd Claim Area) harvests & places network configuration data in files, queues, & object stores. Structured military messaging military unique field unit identifiers & field unit reference numbers (e.g., the time honored but now inflexible “FFIRNs and FUDs” & "DFI, DUI's") once converted to equivalent XML tags in Common Alert Protocol CAP) child schemas / embedded data islands format (1st Claim Area), will allow nearly any commercial forms engine with an XML parser to parse / process them for delivery by any more advanced sensor / data transport mechanism (e.g., Microsoft’s Groove or Biztalk or ZigBee or TXDP… etc) providing forward and backwards interoperability & standardization for both the military and commercial systems. Common operational tempo, symbology refresh to Emergency Action Screens will be possible across n complex systems.

                                   TEMPLATE SYSTEM PROCEDURES CONVERTED TO COMMERCIAL EQUIVALENT

                                    MILITARY TO COMMERCIAL TERM CONVERSION TABLE

Commercialize the military's Network Centric Warfare (NCW) tactics, techniques & operational procedures that hinge on the heartbeat protocol & heartbeat network management messages to be interoperable with the the world's SATCOM transponder beacon, telematics & Telco network Public Safety Answering Points (PSAPs) etc as provided thru key federal contracts (DHS EAGLE-FirstSource, NETWORX, Alliant, IWN, Encore II, GSA SATCOM II, Coast Guard Deep Water, Army World Wide Satellite Services WWSS, Navy NMCI follow on ...)

Beacon definition from Wikipedia: Beacons are fires lit on hills or high places, used either as lighthouses for navigation at sea, or for signaling over land that enemy troops are approaching, and alerting the defence. In the latter form, beacons are an ancient form of optical telegraph and always used in relay leagues. Incarnations of this system have existed over a large part of the world and in Scandinavia many hill forts were part of networks of beacons to warn about pillaging expeditions from other Scandinavians. Similarly the Brecon Beacons in Wales take their name from beacons to warn of approaching English raiders. In England, the most famous example is the beacons used in Elizabethan England to warn of the approaching Spanish Armada. This chain of beacons gave the name to many Beacon Hills. Beacons have often been abused by pirates. A fire at a wrong position was used to direct a ship against cliffs or beaches, so the cargo could be looted after the ship sank or ran aground. In modern technical parlance, a beacon can also be a transmitter used for navigation. Such as a cellphone tower. Beacons are aids to navigation devices. Intentionally conspicuous, beacons help guide navigators to their destinations. Beacon types include radar reflectors, radio beacons, sound signals, and visual beacons. Visual beacons range from small, single-pile structures to large lighthouses or light stations and are located on land or in water. Lighted beacons are called lights; unlighted beacons are called day beacons. In The Lord of the Rings, a series of seven beacons are used as a signaling device between Gondor and Rohan. [1] In the film adaptation of The Return of the King, Gandalf has Pippin light the beacon closest to Minas Tirith. The series is then lit, thereby notifying Rohan's King Théoden that Gondor needs aid in the battle against Sauron.

“May the heart of Earth flow to the heart of heaven through my heart and through all hearts together. And, may our hearts be the heart of every being in all the starry sky, And, may the heart of the heavens flow to the heart of the earth through my heart and though all of our hearts together. And, may our hearts be the heart of every earthly creature”. Chichicastenango Guatemala from “Stargate 2012: Surfing the tides of the Milky Way as drawn from ancient Mayan prophecies.

DOCUMENTS / PRESENTATIONS:

DECISION BRIEF: BRIEFING

CONCEPT PAPER PAPER

[edit] "You just can't make this stuff up". Reverend Kathy Graves Circle of the Sacred Earth

                                                                          Steven J. McGee: Scribe for the Heartbeat Beacon

Before our white brothers arrived to make us civilized men, we didn't have any kind of prison. Because of this, we had no delinquents. Without a prison, there can be no delinquents. We had no locks or keys and therefore among us there were no thieves. When someone was so poor that he couldn't afford a horse, a tent or a blanket, he would, in that case, receive it all as a gift. We were too uncivilized to give great importance to private property. We didn't know any kind of money and consequently, the value of a human being was not determined by his wealth.We had no written laws laid down, no lawyers, no politicians, therefore we were not able to cheat and swindle one another. We were really in bad shape before the white men arrived and I don't know how to explain how we were able to manage without these fundamental things that (so they tell us) are so necessary for a civilized society.

                                         John (Fire) Lame Deer
                                         Sioux Lakota 1903-1976

BEACON TECHNOLOGY LIST:

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 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.

CASM: DHS Communications Assets Survey and Mapping Tool part of SAFECOM Used to identify communications gaps & close them IAW the SAFECOM Interoperability Continuum framework. CASM inventories regional communications equipment assets, while providing a real- time tool to determine available interoperability links among systems & online equipment inventory

COCO protocol: rides on top of disparate communications systems to give them a common interface. It establishes a link between systems, negotiating an encoding method and a key exchange to enable secure communications with quality of service.

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

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. Hourglass is an Internet-based infrastructure for connecting a wide range of sensors, services, and applications in a robust fashion. 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. The Hourglass infrastructure consists of an overlay network of well-connected dedicated machines that provides service registration, discovery, and routing of data streams from sensors to client applications. In addition, Hourglass supports a set of in-network services such as filtering, aggregation, compression, and buffering stream data between source and destination. Hourglass also allows third party services to be deployed and used in the network.

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 specific user being reachable via more than one mobile network,which one should be used and why?

NCharT: Enterprise Network Solution that numbers network segments, identifies routes (in/out/across network) & ID’s hosts / platforms such as ports, services, Operating System’s)

OPenDAP: Goddard Earth Sciences (GES) Data and Information Services Center Open-source Project for a Network Data Access Protocol is a framework that simplifies all aspects of (scientific) data networking. OPeNDAP provides software that makes local data accessible to remote locations regardless of local storage format. OPeNDAP also provides tools for transforming existing applications into OPeNDAP clients (i.e., enabling them to remotely access OPeNDAP served data).

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.

SAFECOM / Project MESA exists to facilitate dependable, advanced, efficient, effective and inter-operable equipment, specifications and applications that are involved with public safety-oriented broadband communication needs.

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.

SWRI South West Research Institute Smart Beacons: Worldwide Tracking via Satellite Small, microprocessor-controlled "smart" beacons allow the location of objects such as aircraft, ships, and cargo vehicles to be easily monitored

TELCORDIA: Domain Announcement Protocol DAP: Beacon Protocol that maintains domains with network splits and merges. Algorithms dynamically decide domain membership based on node mobility,roles, etc.

GEORGE MASON XOM: Extensible Modeling and Simulation Framework Overlay Multicast (XOM). Growing demand for use of Internet/Web-based services in real-time distributed virtual simulation (RT-DVS) and other real-time applications is fueling extensive interest in overlay multicast protocols. These applications demand Quality of Service (QoS) and many-to-many multicast services that are not available in underlying Internet services today. This paper describes an early implementation of an overlay multicast protocol designed to support many-to-many multicast for RT-DVS applications called Extensible Modeling and Simulation Framework Overlay Multicast (XOM).

Projects that can be adjusted to suit the above paradigm are:

UC BERKELEY OCEAN STORE: 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.SEA GULL:

BOSTON UNIVERSITY PROJECT BEACON: [This project will add the elements of time & space // short, medium, long time scales & the distance traveled in router hop counts... with the caveat that two more levels need defined to match the five DHS levels... level 1 green / level 2 blue / level 3 yellow / level 4 orange / level 5 red. http://www.cs.bu.edu/groups/mass/beacon.htm Beacon Project].

UNIVERSITY OF COLORADO: Detecting and Responding to Widely Dispersed and Coordinated Terrorist Attacks A. Carzaniga, D. Heimbigner, and A. Wolf Many existing infrastructure systems are vulnerable to coordinated attacks by terrorists. If a terrorist group were to undertake a number of small, separate actions at approximately the same time (i.e., a coordinated attack), then the combined effect could be catastrophic even though no single action was very serious. We are developing technology to permit detection and response to coordinated physical attacks on critical infrastructure systems. The key components of the technology are sensors attached to physical infrastructure or operated by security staff, a set of analysis tools to detect attacks from sensed data, a mechanism to selectively broadcast alert information, and a wide-area communication substrate. The major design goals are high scale, flexible deployment, and easy extension. A cooperative project with the University of Virginia.

UNIVERSITY OF VIRGINIA: HYPERCAST: HyperCast is software for overlay multicasting and peer-to-peer networking for very large groups. The HyperCast project is a research effort that explores protocol mechanisms for peer-to-peer and multicast networking. The HyperCast project is supported in part by the National Science Foundation under grant number ANI-9870336 and ANI-0085955. We acknowledge the support of Tower Technology's donation of the TowerJ Java compiler.

GEORGE MASON UNIVERSITY: XOM: Extensible Modeling and Simulation Framework Overlay Multicast (XOM). Growing demand for use of Internet/Web-based services in real-time distributed virtual simulation (RT-DVS) and other real-time applications is fueling extensive interest in overlay multicast protocols. These applications demand Quality of Service (QoS) and many-to-many multicast services that are not available in underlying Internet services today. This paper describes an early implementation of an overlay multicast protocol designed to support many-to-many multicast for RT-DVS applications called Extensible Modeling and Simulation Framework Overlay Multicast (XOM).

The UNIVERSITY OF MICHIGAN (Umich) National Science Foundation grant supported “Inet” generator generates an Autonomous System AS-level representation of the Internet with qualitatively similar connectivity. It is important to note that Inet only provides the connectivity information; the generated topologies do not have any information pertaining to latency, bandwidth etc. It generates random networks with characteristics similar to those of the Internet from November 1997 to June 2000, and beyond. The generator should be used to generate network of no less than 3037 nodes, which is the number of ASs on the Internet in November 1997. The software package with source code for Unix, can be found at: http://topology.eecs.umich.edu/inet/

Scalable Group Composition with End-to-end Delivery Semantics: Our model relies on an abstraction which we call an intergroup router. Intergroup routers provide a mechanism for the exchange of messages between groups. They allow process groups to communicate in a fault-tolerant manner with minimal group or message state information and without modification of the underlying communication protocols. The simulation was performed using OpNet, and was built using the actual implementation code from RTCAST, an atomic, totally ordered real-time group multicast protocol developed at the University of Michigan. http://www.chillarege.com/fastabstracts/ftcs98/386.html

UNIVERSITY OF NORTH CAROLINA CHAPEL HILL: Practical Beacon Placement for Link Monitoring using Network Tomography: Recent interest in using tomography for network monitoring has motivated the issue of whether it is possible to use only a small number of probing nodes (beacons) for monitoring all edges of a network in the presence of dynamic routing. Past work has shown that minimizing the number of beacons is NP- hard, and has provided approximate solutions that may be fairly suboptimal. In this paper, we use a two-pronged approach to compute an efficient beacon set: (i) we formulate the need for, and design algorithms for, computing the set of edges that can be monitored by a beacon under all possible routing states; and (ii) we minimize the number of beacons used to monitor all network edges.

JAMES MADISON UNIVERSITY: Timelining Events from Disparate Sources. We propose the creation of a framework that allows a forensic investigator to synchronize timed events that are obtained from different sources to a common reference time. Once the timestamps have been synchronized, they may be ordered into a timeline of events as they occurred in relation to each other. This will enable the investigator to reconstruct events that are directly or indirectly responsible for incidents in computing. This will benefit investigations where connections to events in the physical world need to be established, as well as investigations of networked computer incidents or failures, such as the 2003 power blackout in the northeaster United States. JMU IIIA

HEARTBEAT BEACON FUNDAMENTALS IN USE:

The Heartbeat Beacon is based on one of the Army Research Laboratory's Greatest Invention: "FBCB2 / BFT is a paradigm-shattering communication and tracking system that provides global, real-time, situational awareness and command and control to/from air and ground platforms in a compact militarized package. Consisting of a Miltope Laptop Computer, satellite antenna and Global Positioning System receiver, BFT displays the air or ground platform’s location on the computer’s terrain-map display along with the respective location of other air and ground platforms. BFT can also be used to send and receive “email” text messages"

Federal Computer Week Article: DOD to set information sharing strategy Wennergren pointed to the ongoing development of communities of interest within DOD and throughout agencies on issues such as maritime domain awareness; Blue Force Tracking systems, which lets users see troop locations on monitors; and improvised explosive devices as ways data sharing is progressing".

Federal Computer Week.com News - Blue Force Tracker for cyberspace? "The net after next will require the true Blue Force Tracker capability to coordinate cyber forces fighting against a cyber enemy, Hobbs said. That is the longer-term challenge. Conference attendees were intrigued by Hobbs’ comments. Many corporations have already contacted him to pitch ideas. Non-corporate members of the community are searching for the solution. The commercial world has several network management software tools that could be adapted to address the cyber problem, said John Hudanich, an information systems engineer at MITRE Corp".

Enterprise class Service Oriented Architectures or SOAs implement a system wide heartbeat enabling failover, health status checks and reconfiguration of network assets applying network configuration data carried in Heartbeat XML messages. The heartbeat protocol and heartbeat XML messages as part of DISA's Network Centric Enterprise Services Technical Plan, Telco regulations, and bell weather IT firms, is a simple but effective means to improve interoperability.

The widely deployed (14+ states) Emergency Management Network (EMnet) "generates Nadat HEARTBEAT... maintains lost connections ... EMnet/EAS Messages can be delivered to broadcasters within seconds using the secure satellite delivery system".

Eaton's "Home Heartbeat" as the “World's First Home Awareness System" backed by the ZigBee Alliance of 100 companies employing the ZigBee mesh networking protocol that makes use of the underlying heartbeat protocol is a logical bridge to exchange situational awareness data with the terrorist information producing systems that also make use of the heartbeat protocol. Since there are 70+ competing wireless mesh networking standards, use of a common timing trigger, publish subscribe mechanism underlying many of these "standards" is obviously important to achieving interoperability horizontally and vertically among disparate infrastructures.

Raytheon / XM Satellite Radio's approach is described by this magazine clipping "NYC Firefighters plan a military approach to command and control" ... By viewing information displayed as an electronic map, fire department commanders will be able to move firefighters, equipment and emergency medical teams around in much the same way military commanders shift troops and equipment around a battlefield".

Cisco Systems IPICS Communications Interoperability and Safety Systems is "based on proven IP standards" "the Cisco IPICS server is monitored using a "heartbeat".. "IPICS software uses XML messaging schemas to identify types of communications devices managed by the system."

AT&T has developed a movement detection process that it calls the “Heartbeat Solution.” AT&T has designed its VoIP telephone adapters to enable it to detect when an adapter has been disconnected and then reconnected. Once the Heartbeat Solution detects a reconnection, “the AT&T network will temporarily suspend the customer’s service and will post a message at the customer’s web portal directing the customer to confirm the existing registered location address or register a new location address.”

Lockheed Martin / Qualcomm & SPRINT/NEXTEL's Department of Justice Integrated Wireless Network (IWN) big necessarily involves Qualcomm's role in the development of Blue Force Tracking (BFT) in the Balkans.

During the 2005 super bowl, an approach to fuse sensor data was demonstrated by the 51st Michigan National Guard involving the Transducer Data Exchange Protocol (TDXP). TDXP rides IETF 1451 that correlates to Management Information Bases (MIBS) that make use of the heartbeat protocol. Point being, more modern protocols are being devised as are more modern products / complex systems yet they still rely on the heartbeat protocol / heartbeat messages. the maker of the cited product (Distributed Instruments) states that “TXDP was designed and built for a Service Oriented Architecture (SOA)” supporting direct interoperability between layer one and two (mobile, chaotic environments) with enterprise level SOA(s).

09/13/06 NYC, New York City’s Department of Information Technology and Telecommunications has awarded a $500 million contract to deliver a broadband public-safety wireless network. The network will add high-speed data and video capabilities to New York’s existing mobile wireless communications network. It has several new and advanced wireless applications to support first responders and transportation personnel. This network solution uses standards-based mobile broadband wireless technology, called Universal Mobile Telecommunications System UMTS provided by IPWireless Inc. of San Bruno, Calif. Universal Mobile Telecommunications System (UMTS);. polls user periodically as a heartbeat mechanism (to track user's activity).

The user base of Heartbeat e9-1-1 are customers / stake holders of major federal contract vehicles with Situational Awareness & Telco CDRLs & eventually as cited in the Government Executive Magazine article titled "DHS revamps Emergency Alert System - DEAS": "every cell phone owner who has not opted out of the Heartbeat e9-1-1 subscription service currently offered to Blackberry device owners." See: http://www.govexec.com/dailyfed/0706/071206j1.htm

Geospatial/Dispatch systems like Intergraph’s Computer-Aided Dispatch System (I/CAD) also make use of Telco location data: Automatic address input via ANI/ALI (automated number/location information) & Automatic location verification. Vehicle positions from an AVL system auto displayed on I/CAD map

[DHS Geospatial Application http://www.gcn.com/print/24_7/35426-1.html] to Blackberry devices followed by all devices. “The system integrates video, collaborative capabilities, does blue-force tracking, integrates a weather information feed and provides a live aviation feed,” Baxter said. Blue-force tracking is a troop-monitoring tool created by the Defense Department that lets users follow movements of their groups and others in a specified geographic area. Users will be able to access the information via cell phones and ruggedized personal data assistants, Baxter said. The south Florida TSA system also will let users model the track of a plume—for example, of a toxic cloud—as it approaches high-risk sites such as schools, Baxter said." Author's note: Dave Baxter wrote the FBCB2/Blue Force Tracker API.

Nationwide Health Information Network Initiative NHIN foster widely available services that facilitate the accurate, appropriate, timely, and secure exchange of health information. A network of networks Connect: Providers (EHR’s) Consumers (PHR’s) Interconnect: State, regional, and non-geographic health information exchanges, Networks oriented to specific functions, Provide a secure foundation for growth and innovation. NHIN 2007 "Trial Implementations" Bring together:

ACRONYMS / TERMS:

University of Maryland’s CATTS. The CATT Lab's research and development activities provide a bridge between the intelligent transportation systems (ITS) community, the information technology community, and other disciplines essential to the successful application of ITS.

CESAC by Juniper Networks: Command Enterprise Situational Awareness Control) to manage the security infrastructure. Centrally configures, monitor and manages security devices & effects changes to the security posture IAW threat conditions.

CIMS Civil Support Team Information Management System designed to meet the needs, requirements, and mission of the Civil Support Teams (CST’s) nationwide. CIMS enables a 22-person team to coordinate the efforts of operations, science, medical, survey and logistical personnel. This gives the CST commander the ability to direct and monitor execution of the team’s objectives and to present a clear, thorough assessment of the situation to the on-scene incident commander in the most efficient way possible

CONDOR: C2 On-the-Move Network, Digital Over-the-Horizon Relay: maintain reliable communication across periods of unreliable connectivity through in-network store and forward. Supports data transfers in which the time-value of the information exceeds the duration of the network disruption(s)

DCGS: Distributed Common Ground Station: military satellite base station for military intelligence processing

DDS: Data Distribution Service for Real-Time Systems (DDS) Object Management Group (OMG) standard

DISA: Defense Information Systems Agency: provides military with worldwide infrastructure services e.g., GIG, SOA

DREN Defense Research Engineering Network:150+Universities

Efficient XML: alternative to XML schemas that is especially efficient for transmitting small data files

FBCB2: Force XXI Battle Command Brigade & Below/Blue Force Tracking

GEOSS is an effort by more than 60 countries and 40 international organizations to link Earth-observation instruments and data into an integrated system to aid decision-makers in areas such as energy and water management, public health, agriculture, transportation and emergency response.

JACEC: Joint Command and Control Architectures and Capability Assessment Enterprise JACAE maps out the available various command and control (C2) capabilities and how joint task force headquarters (JTF HQ) can bring them together to support a JTF and its networks.

JITC: Joint Interoperability Test Center (XML schemas) DISA

The John P. Murtha Institute for Homeland Security’s (the Murtha Institute) focus areas are education, outreach and training, and research and development in homeland security, which includes emergency management, public health preparedness, security and intelligence, and homeland defense. See NEDIS and CIMS. http://www.murthainstitute.org/

MUOS: Mobile User Objective System UMTS: “polls user periodically as a heartbeat mechanism to track user's activity.” "significantly improved and assured communications for U.S. warfighters”

NASA CLEO: Cisco Router in Low Earth Orbit: On 27 September 2003, a Cisco Systems mobileaccess router was launched into low Earth orbit as asecondary experimental payload onboard the UK–DMC disaster monitoring constellation satellite built by SSTL. The UK-DMC satellite’s primary missionis to provide Landsat-style, mid-resolution, remote sensing imagery. This satellite operates within the Disaster Monitoring Constellation (DMC) of small satellites built by SSTL for a number of collaborating countries

NAUTILIS HORIZON / VMOC A General Dynamics initiative, provides a framework for mission partners to define, test, and field an IP based command and control system capable of supporting secure distributed mission operations of any IP-based platform or sensor. At the heart of Nautilus Horizon is NASA's Virtual Mission Operations Center (VMOC). The VMOC provides a path for the rapid development and demonstration of new technologies. Virtual Mission Operations Center (VMOC). This Internet-based command and control software application allows users to direct and task sensors aboard space and airborne reconnaissance assets.

NENA - National Emergency Numbering Association Technical Support Organization for E9-1-1 Congressional Caucus

NISAC National Infrastructure Simulation & Analysis Center

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.

NSTAC: National Security Telecommunications Advisory Council

OnStar: GM Satellite Division which started as “Project Beacon” in 1994

The Paul Revere: MIT’s Airborne Laboratory

REpresentational State Transfer: REST is an approach for getting information content from a Web site by reading a designated Web page that contains an XML (Extensible Markup Language) file that describes and includes the desired content. For example, REST could be used by an online publisher to make syndicated content available. Periodically, the publisher would prepare and activate a Web page that included content and XML statements that described the content. Subscribers would need only to know the URL (Uniform Resource Locator) for the page where the XML file was located, read it with a Web browser, interpret the content data using the XML information, and reformat and use it appropriately (perhaps in some form of online publication). As described in a dissertation by Roy Fielding, REST is an "architectural style" that basically exploits the existing technology and protocols of the Web, including HTTP (Hypertext Transfer Protocol) and XML. REST is simpler to use than the well-known SOAP (Simple Object Access Protocol) approach, which requires writing or using a provided server program (to serve data) and a client program (to request data). SOAP, however, offers potentially more capability. For example, a syndicator that wanted to include up-to-date stock prices to subscribing Web sites might need to use SOAP, which allows a greater amount of program interaction between client and server. See: Extending the REpresentational State Transfer (REST)Architectural Style for Decentralized SystemsRohit Khare and Richard N. Taylor University of California, Irvine{rohit,taylor}@ics.uci.edu:

REST: REpresentational State Transfer: To ground our exploration of these new issues, we began by restating REST to verify that it could induce the property of consensus. Our more-rigorous correctnessargument elucidated that REST depends on synchronized global clocks to ensure leases expire simultaneously. Synchronization still presumes that every response message specifies its lease interval. Many real-world ORIGINSERVERs do not specify when the next permissible resource update is scheduled. The external environment could update resources at random (e.g. editing a file “byhand”). One solution is a heartbeat defining a defaultlease duration and delaying updates until the next cycle

RITIS: The Regional Integrated Transportation Information System (RITIS) project is about improving transportation efficiency, safety, and security through the integration of existing transit and transportation management system data in Virginia, Maryland, and the District of Columbia. RITIS (pronounced ritus) will emphasize data fusion and its relationship to data collection, regional transportation systems management, regional traveler information dissemination, and systems evaluation. University of Maryland CATTS laboratory.

TELEMATICS: integrated use of telecommunications and informatics, sending, receiving and storing information via telecommunication devices i.e., OnStar by GM

TXDP: Transducer Data Exchange Protocol: used during 2005 Superbowl by Michigan National Guard

UMTS: Universal Mobile Telecommunication System (wireless broadband) heartbeat to “track user’s activities”

VMOC: General Dynamics Software intended to task satellites and provide imagery via a simple GUI interface for military users. VMOC is simply a secure IP-based application for satellites, using an available IP-based satellite infrastructure

Workflow (JBFSA) addition of Joint Blue Force Situational Awareness (JBFSA) capabilities and ..... Planning Workflow: New capability will allow authorized users to track the ... www.dtic.mil/descriptivesum/Y2008/DISA/0303150K.pdf

ZIGBEE: Consortium supporting a heartbeat driven mesh network standard

ZWAVE: like ZIGBEE (70+ competing standards)

Retrieved from "http://knowledgetoday.org/wiki/index.php/User_talk:Stevenjmcgee"

User talk:Stevenjmcgee

From NECSIWiki

Contents

[edit] The HOMELAND HEART_BEACON

[edit] The International Homeland Heart_Beacon for interoperability, synergy & synchronicity

[edit] The Healthcare Heart_Beacon

[edit] QUAD CHART: THE HEARTBEAT BEACON BY NUMBER

[edit] "You just can't make this stuff up". Reverend Kathy Graves Circle of the Sacred Earth

Views

Personal tools

Navigation

Search

Toolbox