Method / process / procedure to enable: The Heart Beacon Rainbow Force Tracking

• US 20110047230A1
• Filed: 08/16/2010
• Published: 02/24/2011
• Est. Priority Date: 11/17/2006
• Status: Abandoned Application

• Current Assignee: Steven J. Mcgee
• Original Assignee: Steven J. Mcgee
• Inventors: McGee, Steven J.
• Application Number:
  US12/856,715
• Publication Number:
  US 20110047230A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 41/0609 based on severity or priority
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y04S 40/00 Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
• CPC Class Codes: Y04S 40/18 Network protocols supporting networked applications, e.g. including control of end-device applications over a network

Abstract

The Heart Beacon is a method/process/procedure standardizing spontaneous reorganization converting military adhoc organizational mobility techniques. Net effects are enabled by periodic net management router updates via heartbeat messages followed by router and beacon protocol broadcast of node hop count changes emulating geospatial threshold radius and precedent conditions changes represented by audible tones/vibratory levels in the grid/cloud. A single, synchronized, unified event/alert trigger is achieved by instantiating a single XML schema described by child schema'"'"'s, data islands/NIEM payloads linking disparate communities. Leader intent is emulated via mission thread/business logic representing medical triage, alert/event evacuation and alternate routing within adjustable geospatial zones. Temporally synchronous, statistically predictable data harvesting cycles sync seed clouds enhancing network forensics as shared fee for services.

Claims

1. A method of claim standardizing procedures/methods/processes, and practices intrinsic to military Network Centric Warfare (NCW) situational awareness systems extending these best methods and practices to the private grid/cloud computing sector re-using NCW templates as functional, operational guides/references enabling enhancing, unified alert, event, All Hazards processes (e.g., Single Integrated Operational Picture SIOP from a Family of Integrated Common Pictures FIOP) by commercial (NIST, ITU, OASIS) adoption of a standardized nine step iterative process/method.

a) Use TCP/IP heartbeat sub-protocol frames/intervals in time to gather/harvest/collect then place state meta data in temporary holding areas i.e., file, queue, folder, cache from a plurality of TCP/IP cloud/grid/networked computing devices, sensors and Radio Frequency Tags RFID;

b) Use TCP/IP heartbeat sub-protocol uses as a timer (i.e., 0001, 001, 05, 01, 1, 5, 10, 15 . . . 99 minute) synchronizing timing/temporal rate of state meta data collection across a plurality of inter networked cloud/grid computing devices;

c) Use TCP/IP'"'"'s time stamping function (i.e., 10;

15 AM) enhancing network forensic analysis by gathering additional state meta data types (ORG ID, URN) using heretofore reserved time slots at disciplined, and therefore statistically predicable intervals (e.g., 5, 10, 15 . . . minutes);

d) Use TCP/IP'"'"'s multicast/unicast/anycast function of routers emulating geographic area alerts via router hop counts in context with DEFCON, ALCON, COGCON, INFOCON, and (DHS) five color level advisory schemes;

e) Use TCP/IP multicast-unicast process to distribute/broadcast mission thread/business logic contained in workflows as synchronized, filtered subscription services to users supported by a cloud/grid distributed, adhoc, mobile, network sensor computing environment;

f) Use TCP/IP millisecond response range function to improve on the current too slow for fast moving objects 30 second web server screen scrapes of data refresh rates to Command and Control and Emergency Operation Centers/nodes/systems;

g) Use TCP/IP timing function to synchronize/standardize date time stamping by uniquely identifying by creating disciplined, predictable data transaction windows (start, stops, duration) for alerts and events including financial transactions (i.e., SWIFT), enhancing net forensic analysis by providing notifications of events, alerts, and change conditions on a fee for service basis;

h) Standardize heartbeat sub-protocol gathered and synchronized thus standard and predictable state meta-data refresh rates to enhance the consistency of cross system, cross cloud/data grid derived Single Integrated Operational Picture (SIOP).

2. A method of claim where proprietary military network management functionality is replicated to standardize as best practice enhancements/improvements to equivalent commercial network management system imparting to commercial domains the military'"'"'s superior network mobility practice emulating leader/commander'"'"'s intent (maneuver the network, spontaneous integration of mobile, adhoc units).

a) Use commercial wizards &

UTO Tool commercial equivalent e.g., CISCO IPCS, Juniper CESAC instead of proprietary military tools (i.e., TIMS) reconfiguring net management parameters using state meta data harvested by the heartbeat mechanism from a plurality of TCP/IP networked devices to achieve standardized command and control situational awareness;

b) Use commercial equivalent wizards corresponding to military Unit Task Order UTO tools to (re) configure net management parameters described by a military K00.99 heartbeat message and standardize on a commercial equivalent counterpart heartbeat XML message used by SWIFT, e9-1-1 and military telecommunication standards that are currently non-standard;

c) Use commercial counterparts to military command and control system administrator/network monitoring software wizards, intelligent software agents to configure then send out unit/entity/organization task organization message to set effective time (when order will be executed) via workflow tools via Unicast/Multicast group subscriptions;

d) Apply user selected beacon broadcast technology to distribute (binary) Common Alert protocol XML schemas, child schemas, data islands and/or NIEM payloads within CAP Schemas;

e) Standardize on a common paradigm of establishing pre coordinated date and time when devices in multicast groups reconfigure router Management Information Base MIB configuration descriptions MIBS (common to all routers—

military &

commercial) then;

f) Use directory (LDAP) subscription lists referral reassigning INC;

Internet Controller commercial counterpart net addresses defined by Universal Reference Number URN and or Organizational ID that is not the current practice of commercial, private of Non Governmental Agency NGO'"'"'s;

g) Use commercial equivalents to military net management applications e.g., ISYSCON, CISCO IPICS/Juniper CESAC to make new multicast group file used to update router MIBs automatically at agreed, standardized, synchronized time intervals;

h) Update Command and Control Registry C2R commercial equivalent i.e., Lightweight Directory Access Protocol LDAP Server multicast MCG update tool updates multicast group data on commercial equivalents to Army Information Management AIS servers);

i) Use a commercial equivalent to the military State Management process on Army Information Server AIS/LDAP directory server to recognize in a standardized manner that a change has occurred sending out change alert throughout the cloud computing/grid networking environment;

j) Use beacon technology (user selected) to broadcast state changes in a universally standard practice endorsed by NIST/ITU (i.e., Microsoft Groove'"'"'s intrinsic state manager) to replicate updated multicast groups with routing information obtained from LDAP server then configure the Network Interface Card NIC with new IP lease.

3. A method of claim standardizing on the web OASIS Common Alert Protocol XML schema version of the military heartbeat message (K00.99) USMTF/JVMF/TADL proprietary formatted UTO heartbeat message converted to (binary) XML message/document/form/data element XML structures;

a) enable faster than thirty second web portal screen refreshes where eXtensible markup language (XML) wrapper exposes the military discovery metadata to a web portal for screen refresh/updating faster (e.g., milliseconds, seconds) due to direct schema/message/form exchanges and use of beacon protocol and cache technologies;

b) derive and standardize from the military'"'"'s (K00.99) heartbeat message data entity values/attributes such as;

current/active data;

IP lease, location, Synchronization Delta Time Block, current Unit Task Organization UTO, UTR (U=Unit, T=Task, R=reorganization) command, Effective Date/Time/Group (DTG) Block, command relationship (OPCON, attach), Unit of Action, Unit of Employment affiliations, Universal Resource Number URN (unique numeric identification number) describing a plurality of devices, systems, and networks;

c) convert and standardize structured military messaging three and four digit code data element FFIRN/FFUDNs into equivalent CAP XML schema tags that commercial product/component/system'"'"'s intrinsic forms engine parsers, and state management engines can process;

d) As a universal standard, use OASIS Common Alert Protocol CAP equivalent to military'"'"'s Unit Task Order—

UTO heartbeat message describing key meta data state management elements intrinsic to the military template system FBCB2-BFT situational awareness data types;

who, what, where, when, how often, out of radio range, turned off, inoperative for maintenance or in a duress condition at the time of the initial or follow on heartbeat timed data collection interval (e.g., stale, straggler, duress, need medical attention, SOS.) for geospatial/gyroscopic equipped networked devices;

e) As a universal standard, reuse structured military messaging data element strategy e.g., organizational ID in counterpart commercial systems enabling more descriptive entity resolution and cohesive organization action in place of individual platform/computing devices to adjust to organizational schemes of maneuver, operation orders;

f) As a universal standard best practice, best procedure, link from subordinate organizations and import to a single, authoritative CAP schema to/from DOD, Service and Agency XML repositories data element tags correlating from civilian systems to military FFIRNs and FFUDN(s) supporting a plurality of international, federal, state, tribal, local user XML tag requirements;

g) As a universal standard, best practice, procedure and method/structure, use the Common Alert Protocol child schema/messages in accordance with National Information Exchange Model NIEM payloads compliant with the Emergency Data Exchange Language Distribution Element EDXL-DE standard that includes the DoD Discovery Metadata Standard DDMS elements as data islands in child schema and/or NIEM payloads to trigger data exchange cascades across disparate stakeholder domains (e.g., .mil, .gov, .edu, .com, .biz, .net, .org.) and Communities of Interest COI described by graphic overlays and synchronization matrixes.

4. A method of claim using beacon broadcast technologies to distribute/replicate state meta-data describing network management unit/organizational structure—

affiliations by Organizational ID ORG ID and Universal Resource Number URN, synchronously and timed in a standard, repetitive, predictable manner as a best practice, best procedure, and best method;

a) use the beacon'"'"'s millisecond—

99 minute timing function to establish standard, consistent timing and synchronous state meta-data collection 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 enhance filtering/data intelligence fusion and network forensic analysis functions;

b) To establish a universal standard best practice, assemble heartbeat network reconfiguration messages with embedded data islands, and/or separate small files (situation and scenario dependent) formatted as non military unique binary formats for example, Efficient XML by AgileDelta, Binary Runtime Environment for Wireless BREW by Qualcomm, Fast-Infoset by Sun Microsystems, and other commercial binary XML type formats (WAP, xs;

base64Binary and xs;

hexBinary,);

c) To establish a universal standard best method, use network state meta data gathered from a plurality of TCP/IP networked devices using heretofore unused opportunities in time/TCP/IP frames are temporarily stored then collected and aggregated by network administrator/S6 operators before redistribution as heartbeat network reconfiguration messages via a plurality of broadcast mechanisms e.g., TDXP, 802.11s ESS, ZigBee IEEE 802.15.4, Z-Wave type wireless mesh networks, Groove bots, JXTA motes, intelligent agents, Cougaar, and beacon protocols such as FLUX, ADS-B Sea Gull, SABRE, Sentinel, SAFECON, Telcordia DAP or Boeing Future Combat System Common Operating Environment COE middleware or Department of Homeland Security Unified Incident Command and Decision Support_UCIDS middleware) across x complex systems, y federal, state and local contracts, and z products, operating system, network and system types;

d) To standardize, enhance and improve current international response mechanisms, apply user selected beacon technology (e.g., Sea Gull, Boston University Beacon Project) to increase/increase geographic radius of disaster/event/alert emulated by multicast zones corresponding to five level advisory systems showing on geospatial displayed symbolically as intensity and threshold conditions;

e) Emulate increasing/decreasing alert/event, levels by router hop-count multicast radius supporting disabled blind and deaf users and for light degraded conditions via audible step tones i.e., NASA'"'"'s and National Undersea Research Center NURC'"'"'s tonal based messaging systems reused from space/deep sea operations to establish international standards via National Institute for Standards and Technology NIST and the International Telecommunications Union ITU;

f) To establish international standard best practice, use (military) chop chain/commercial business logic workflows over multicast IP seeded to router MIBs to set up a conditions where National Command Authority alerts and events are instantiated and cascaded from one, single focal instantiation point (i.e., the big red button metaphor) establishing a single umbrella of command, control, and communications;

g) To standardize across systems of similar use and purpose, use e9-1-1 Public Safety Answering Points (PSAP) (inter) national e9-1-1 next generation systems across a plurality of (federal, private, public and Non Governmental Organization) contracts containing telecommunication and situational awareness CDRLs.