US20070011106A1 - Trusted decision support system and method - Google Patents

Trusted decision support system and method Download PDF

Info

Publication number
US20070011106A1
US20070011106A1 US11/418,382 US41838206A US2007011106A1 US 20070011106 A1 US20070011106 A1 US 20070011106A1 US 41838206 A US41838206 A US 41838206A US 2007011106 A1 US2007011106 A1 US 2007011106A1
Authority
US
United States
Prior art keywords
instructions
data set
data
decision support
analyses
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/418,382
Inventor
Greg Benson
Matthew Fistonich
Original Assignee
Palomar Tech LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Palomar Tech LLC filed Critical Palomar Tech LLC
Priority to US11/418,382 priority Critical patent/US20070011106A1/en
Assigned to PALOMAR TECHNOLOGY, LLC reassignment PALOMAR TECHNOLOGY, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BENSON, GREG, FISTONICH, MATTHEW ANTHONY
Publication of US20070011106A1 publication Critical patent/US20070011106A1/en
Assigned to PALOMAR TECHNOLOGY,LLC reassignment PALOMAR TECHNOLOGY,LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BENSON, GREG, FISTONICH, MATTHEW
Assigned to 1997 IRREVOCABLE TRUST FOR GREGORY P. BENSON reassignment 1997 IRREVOCABLE TRUST FOR GREGORY P. BENSON ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PALOMAR TECHNOLOGY, LLC
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B13/00Burglar, theft or intruder alarms
    • G08B13/22Electrical actuation
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B13/00Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion
    • G05B13/02Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion electric
    • G05B13/0265Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion electric the criterion being a learning criterion
    • G05B13/0275Adaptive control systems, i.e. systems automatically adjusting themselves to have a performance which is optimum according to some preassigned criterion electric the criterion being a learning criterion using fuzzy logic only
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/52Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00Machine learning
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N5/00Computing arrangements using knowledge-based models
    • G06N5/04Inference or reasoning models
    • G06N5/048Fuzzy inferencing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N7/00Computing arrangements based on specific mathematical models
    • G06N7/01Probabilistic graphical models, e.g. probabilistic networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083Shipping
    • G06Q10/0833Tracking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/26Government or public services
    • G06Q50/40
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/085Registering performance data using electronic data carriers
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/20Individual registration on entry or exit involving the use of a pass
    • G07C9/22Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder
    • G07C9/25Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition
    • G07C9/257Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition electronically
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F7/00Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/06Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by returnable containers, i.e. reverse vending systems in which a user is rewarded for returning a container that serves as a token of value, e.g. bottles
    • G07F7/0618Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by returnable containers, i.e. reverse vending systems in which a user is rewarded for returning a container that serves as a token of value, e.g. bottles by carts
    • G07F7/0636Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by returnable containers, i.e. reverse vending systems in which a user is rewarded for returning a container that serves as a token of value, e.g. bottles by carts in which the trolleys or carts are kept in a restricted zone such as a coral-like enclosure, or are passing a gate before use is possible
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07GREGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
    • G07G1/00Cash registers
    • G07G1/0036Checkout procedures
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07GREGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
    • G07G3/00Alarm indicators, e.g. bells
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B13/00Burglar, theft or intruder alarms
    • G08B13/18Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength
    • G08B13/189Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems
    • G08B13/194Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems
    • G08B13/196Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems using television cameras
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B13/00Burglar, theft or intruder alarms
    • G08B13/22Electrical actuation
    • G08B13/24Electrical actuation by interference with electromagnetic field distribution
    • G08B13/2402Electronic Article Surveillance [EAS], i.e. systems using tags for detecting removal of a tagged item from a secure area, e.g. tags for detecting shoplifting
    • G08B13/2451Specific applications combined with EAS
    • G08B13/2454Checking of authorisation of a person accessing tagged items in an EAS system
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02Alarms for ensuring the safety of persons
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02Alarms for ensuring the safety of persons
    • G08B21/12Alarms for ensuring the safety of persons responsive to undesired emission of substances, e.g. pollution alarms
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/14Central alarm receiver or annunciator arrangements
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B29/00Checking or monitoring of signalling or alarm systems; Prevention or correction of operating errors, e.g. preventing unauthorised operation
    • G08B29/16Security signalling or alarm systems, e.g. redundant systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04KSECRET COMMUNICATION; JAMMING OF COMMUNICATION
    • H04K3/00Jamming of communication; Counter-measures
    • H04K3/20Countermeasures against jamming
    • H04K3/22Countermeasures against jamming including jamming detection and monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101Access control lists [ACL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/52Network services specially adapted for the location of the user terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/535Tracking the activity of the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00Television systems
    • H04N7/18Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
    • H04N7/181Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a plurality of remote sources
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/03Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
    • G06F2221/034Test or assess a computer or a system
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/00174Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00896Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys specially adapted for particular uses
    • G07C2009/0092Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys specially adapted for particular uses for cargo, freight or shipping containers and applications therefore in general
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/0875Registering performance data using magnetic data carriers
    • G07C5/0891Video recorder in combination with video camera
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/30Individual registration on entry or exit not involving the use of a pass
    • G07C9/32Individual registration on entry or exit not involving the use of a pass in combination with an identity check
    • G07C9/37Individual registration on entry or exit not involving the use of a pass in combination with an identity check using biometric data, e.g. fingerprints, iris scans or voice recognition
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B29/00Checking or monitoring of signalling or alarm systems; Prevention or correction of operating errors, e.g. preventing unauthorised operation
    • G08B29/02Monitoring continuously signalling or alarm systems
    • G08B29/04Monitoring of the detection circuits
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80Wireless
    • H04L2209/805Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor

Definitions

  • PALO.001A3 filed on even date herewith
  • TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A4, filed on even date herewith); TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A5, filed on even date herewith)
  • TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A6, filed on even date herewith)
  • TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A1, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty.
  • the field of the invention relates to complex data modeling and data modeling. More particularly, the invention relates to massive correlative analysis and predictive modeling.
  • One embodiment is a system including an electronic device configured to select a data set for an application area, to assign weighted scores to the data in the data set, to correlate the weighted data set with one or more previously correlated weighted data sets, and to determine, based upon the correlation, a recommended action as a response to an event related to the data set.
  • Another embodiment is a system including a sensor network, a database including data from the sensor network, and an electronic device configured to select a data set from the database for an application area, to assign weighted scores to the data in the data set, to correlate the weighted data set with one or more previously correlated weighted data sets, and to determine, based upon the correlation, a recommended action as a response to an event related to the data set.
  • Another embodiment is a method of analyzing data, including identifying one or more data sets for an application area, assigning weighted scores to the data in the data set, correlating the weighted data set with one or more previously correlated weighted data sets, and determining, based upon the correlation, a recommendation a recommendation for a response to an event that is related to the identified data set.
  • Another embodiment is a system including an electronic device configured to select a data set for an application area and to analyze the data set according to fuzzy logic instructions so as to generate a recommended action and outcome information for the recommended action.
  • Another embodiment is a method of analyzing data, including identifying one or more data set for an application area, and analyzing the data set according to fuzzy logic instructions, so as to generated a recommended action and outcome information for such recommended action.
  • Another embodiment is a system including an electronic device configured to select a data set for an application area and to analyze the data set according to statistical analysis instructions so as to generate a recommended action and outcome information for the recommended action.
  • Another embodiment is a method of analyzing data, including identifying one or more data set for an application area, and analyzing the data set according to statistical analysis instructions, so as to generated a recommended action and outcome information for such recommendation action.
  • FIG. 1 shows a network for implementing a trusted decision support system.
  • FIG. 2 is a block diagram illustrating certain functional blocks of a server based system for hosting the trusted decision support system.
  • FIG. 3 is a flowchart illustrating certain steps in a process for developing an application specific decision support model.
  • FIG. 4 is a flowchart illustrating certain steps in a process for performing a decision support process using an application specific model developed with the process of FIG. 3 .
  • FIG. 5 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to an anti-terrorism application.
  • FIG. 6 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to a general data types application.
  • FIG. 7 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to a human factors application.
  • FIG. 8 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to an ecosystem application.
  • FIG. 9 is a flowchart illustrating certain steps in a process for parsing private information and storing it in segregated databases, where the databases can be accessed in an anonymous mode to retain personal privacy, or accessed in an authorized mode that reconstructs the private information including the personal identity.
  • FIG. 10 is a flowchart illustrating certain steps in a process for obtaining information for use in a decision support process.
  • FIG. 11 is an example template that can be created for an application with the process of FIG. 3 .
  • Data can be obtained from multiple disparate data sources, depending on the information deemed necessary for the situation being modeled. Some embodiments perform complex systems modeling including performing massive correlative analyses of the data obtained from the multiple disparate data sources with current situational data obtained regarding the situation for which the decision support process is being utilized.
  • the decision support system may provide a prediction or predictions and a recommendation or a choice of recommendations based on the correlative analysis and/or other analyses. In some embodiments the decision support system may provide possible consequences that could result from a recommendation. In other embodiments the decision support system may provide a list of tasks for acting upon a recommendation.
  • the decision support model development process may include identifying multiple disparate data sources for retrieval of related information, selection of classification variables to be retrieved from the data sources, assignment of weights to each classification variable, selecting and/or defining rules, and selecting and/or defining analysis functions.
  • a process is terminated when its operations are completed.
  • a process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
  • a process corresponds to a function
  • its termination corresponds to a return of the function to the calling function or the main function.
  • FIG. 1 shows a network for implementing a trusted decision support system.
  • the decision support system 100 includes a server 105 , a storage component 110 , client terminals 115 A, 115 B and 115 C, where three client terminals is only used as an example, and a network 120 connecting the other components.
  • the server 105 contains processing components and software and/or hardware components for implementing the decision support system.
  • the server 105 contains a processor for performing the related tasks of the decision support system.
  • the server 105 also contains internal memory for performing the necessary processing tasks.
  • the server 105 is connected to an external storage component 110 via the network 120 .
  • the processor is configured to execute one or more software applications to control the operation of the various modules of the server as will be discussed below in reference to FIG. 2 .
  • the processor is also configured to access the internal memory of the server 105 , or the external storage 110 to read and/or store data.
  • the processor may be any conventional general purpose single- or multi-chip microprocessor such as a Pentium® processor, Pentium II® processor, Pentium III® processor, Pentium IV® processor, Pentium® Pro processor, a 8051 processor, a MIPS® processor, a Power PC® processor, or an ALPHA® processor.
  • the microprocessor 100 may be any conventional special purpose microprocessor such as a digital signal processor.
  • the storage component 110 contains memory for storing information used for performing the decision support processes provided by the system 100 .
  • Memory refers to electronic circuitry that allows information, typically computer data, to be stored and retrieved.
  • Memory can refer to external devices or systems, for example, disk drives or tape drives.
  • Memory can also refer to fast semiconductor storage (chips), for example, Random Access Memory (RAM) or various forms of Read Only Memory (ROM), that are directly connected to the processor.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • Other types of memory include bubble memory and core memory.
  • the client devices 115 A- 115 C represent any type of device that can access a computer network. Devices such as PDA's (personal digital assistants), cell phones, personal computers, lap top computers, set top boxes are examples of devices that could be used as the client devices 115 .
  • the client devices will typically have a display device and one or more input devices.
  • the input device may be a keyboard, rollerball, pen and stylus, mouse, or voice recognition system.
  • the input device may also be a touch screen associated with an output device. The user may respond to prompts on the display by touching the screen. Textual or graphic information may be entered by the user through the input device.
  • the network 120 may include any type of electronically connected group of computers including, for instance, the following networks: Internet, Intranet, Local Area Networks (LAN) or Wide Area Networks (WAN).
  • the connectivity to the network may be, for example, remote modem, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI) or Asynchronous Transfer Mode (ATM).
  • computing devices may be desktop, server, portable, hand-held, set-top, or any other desired type of configuration.
  • the network includes network variations such as the public Internet, a private network within the Internet, a secure network within the Internet, a private network, a public network, a value-added network, an intranet, and the like.
  • FIG. 2 is a block diagram illustrating certain functional blocks of a server based system for hosting the trusted decision support system.
  • the system 200 includes the server 105 that is connected, to an administrative workstation 236 , and to external data sources 240 .
  • the server 105 is comprised of various modules 202 - 234 .
  • each of the modules 202 - 234 comprises various sub-routines, procedures, definitional statements, and macros.
  • Each of the modules 202 - 234 are typically separately compiled and linked into a single executable program. Therefore, the following description of each of the modules 202 - 210 is used for convenience to describe the functionality of the server 105 .
  • each of the modules 202 - 234 may be arbitrarily redistributed to one of the other modules, combined together in a single module, or made available in a shareable dynamic link library. Further each of the modules 202 - 234 could be implemented in hardware.
  • the controller 220 serves as the central interface linking the other modules 222 - 234 .
  • the controller 220 coordinates the use of the other modules based on the script instructions that define the task (e.g., an application specific decision support model) that is being processed.
  • the modules 232 - 234 execute the various functions used to perform the decision support processes.
  • the data modules 202 - 210 comprise memory that stores previously generated data an is also used to store new data as it is generated by the other modules.
  • the data storage interface module 224 is configured to retrieve and store data to and from the data modules 202 - 210 .
  • the real-time monitoring interface 222 is configured to monitor multiple disparate data sources in search of information that matches any of several variables that the current decision support model is designed to retrieve.
  • the real-time monitoring interface 222 retrieves from the disparate data sources that are part of a secure communications network for use with the decision support system.
  • each of the disparate data sources conforms to a security protocol and a data format.
  • the data that is retrieved by the real-time monitoring interface 222 is forwarded to the controller 220 which then forwards the data for use by other modules or to be stored.
  • Disparate data sources that are part of a secure communication network may include data sources that are under the control of an organization that controls the communications network that the data is retrieved from.
  • the decision support system is part of a U.S. government communications network
  • the following databases may be directly connected to the decision support system and may conform to the security protocol and data format:
  • the real-time monitoring interface 222 retrieves data from a set of conforming data sources.
  • an import data translation module 226 is configured to retrieve information from non-conforming data sources 240 .
  • the information may be any that matches any of the several variables that the current decision support model is designed to retrieve.
  • the non-conforming data sources can be accessed from any of several public, private, secure, and/or non-secure networks such as those discussed above in reference to the network 120 of FIG. 1 .
  • Non-conforming data sources may include web pages on the Internet.
  • the Internet contains a plurality of web pages that are searchable by the import data translation module 226 .
  • the web pages are virtual documents that each have embedded links which link portions of the virtual pages to other virtual pages and other data.
  • the import data translation module 226 can traverse the virtual pages and download data that matches any of the several variables that the current decision support model is designed to retrieve.
  • the data that is retrieved by the import data translation module is converted to conform to the same data format that the real-time monitoring interface module 222 uses.
  • the conversion to the conforming format may include classifying portions of the information into the various search variables and then parsing the classified information variables into specific fields of a multidimensional data structure (e.g., fields may include time, location, account numbers, flight numbers, etc.). After the retrieved data is converted to the conforming format, it is forwarded to the controller 220 for use in other modules or to be stored.
  • the data that is retrieved by the import data translation component 226 may be of questionable integrity.
  • Networks such as the internet typically employ a base level of protection for transporting data of all kinds.
  • TCP Transport Control Protocol
  • TCP is a transport layer protocol used to provide a reliable, connection-oriented, transport layer link among computer systems.
  • the network layer provides services to the transport layer.
  • TCP provides the mechanism for establishing, maintaining, and terminating logical connections among computer systems.
  • TCP transport layer uses IP as its network layer protocol. Additionally, TCP performs functions such as transmission of byte streams, data flow definitions, data acknowledgments, lost or corrupt data re-transmissions, and multiplexing multiple connections through a single network connection.
  • TCP is responsible for encapsulating information into a datagram structure.
  • An integrity services module 242 is configured to perform the integrity checks of TCP or other types of transport layer protocols known to those of skill in the art (e.g., hypertext transmission protocol, secure: HTTPS).
  • the integrity services module 242 may also be used to authenticate contextual information obtained from non-conforming sources by comparing the non-conformal source information to duplicate information that has been obtained from trusted sources (e.g., sources such as the conformal sources connected to the real-time monitoring interface 222 ). This type of contextual authentication may avoid the importation of accidentally incorrect information and/or purposefully false information (e.g., information that may have been planted for purposes of disinformation).
  • the import data translation component 226 may use methods to convert non-textual information into text to be stored.
  • Many sources of information, especially on the internet, are stored in various forms of multimedia including audio, image, and our video formats.
  • Various methods can be used to convert from a media format to a textual format. These methods include, for example, speech to text methods, voice recognition methods, and image recognition (recognizing faces, and/or objects and classifying them as identified people or things).
  • These types of conversions can be used to classify variables (e.g., time, location, people, and/or objects) discovered in audio files, image files and/or video files, and store them in the various databases, such as the historical data module 202 , for later analysis.
  • the disparate data sources whether they are of the conforming type or the non-conforming type, preferable come from as many different types of networks and/or systems as possible.
  • the information obtained by the real-time monitoring interface 222 is data sampled by one or more remote monitoring systems and/or remote sensors as described in the U.S. application entitled: TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A) and filed on even date. Examples of disparate data sources that may be utilized for several application specific situations are illustrated in FIGS. 5 to 8 .
  • the modules 228 , 232 and 234 are analysis components that are used in searching for patterns, correlated events, recommended actions and/or probable consequences using various mathematical methods.
  • a fuzzy inference engine component 228 is configured to analyze any of the newly retrieved and/or stored data according to fuzzy logic rules defined by the specific decision support model that is being executed. Examples of commercially available fuzzy inference engines include: mbFuzzIT, Mentalogic Systems Inc Fuzzy Inference Engine and the Fuzzy Inference Development Environment from Zaptron. Fuzzy logic can be used to represent the correctness of a chain of reasoning connecting a chain of events. The correctness can vary from true (represented by a 1, for example), to false (represented by zero, for example) and may be equal to intermediate values (almost true or almost false).
  • Fuzzy logic rules may be used to identify various inferences and/or implications correlated to various chains of events.
  • the various inferences and/or implications may be the recommended actions and/or consequences identified by the decision support model.
  • a data mining module 232 is configured to analyze data retrieved by the various other modules using tools which look for trends or anomalies without knowledge of the meaning of the data.
  • the data mining module 232 is used to discover patterns and correlations in the large preexisting data modules 202 - 210 in order to uncover new meaning in data. Examples of commercially available data mining tools include: DataCruncher by DataMind, Darwin by Thinking Machines, and Intelligent Miner from IBM.
  • a statistical analysis engine 234 is configured to perform statistical analysis for determining probabilities, for example, for use in determining the recommended actions generated by the decision support system.
  • Examples of commercially available statistical analysis tools include SAS/STAT from SAS, MatLAB from MathWorks, and MS Office-Excel from Microsoft.
  • a graphic interface generation module 230 is configured to present a graphical user interface to a user of the administrative workstation 236 in this example.
  • the graphical user interface enables an administrative user to develop models and use the models for performing the decision support analysis. Examples of commercially available graphical user interface design tools that can be used to generate the graphical user interfaces include CVSgui from WinCVS, System Management Interface Tool from IBM, and Visual Basic from Microsoft.
  • any one of the functional blocks illustrated in FIG. 2 may be rearranged and/or combined with one or more other blocks without changing the function of the server 200 .
  • FIG. 3 is a flowchart illustrating certain steps in a process for developing an application specific decision support model.
  • the process 400 is used to develop a decision support model directed to a specific application for providing guidance and decision making to a user.
  • An application is a scenario that the decision support process is directed at. Examples of applications include the following application areas each listing representative samples of related sub-application components:
  • the process 400 starts at step 402 where a template of an application model is imported to the design process 400 from a library 422 containing one or more templates of models that can be fine-tuned to fit a given application (e.g., flight safety in this example).
  • FIG. 11 is an example template that can be created for an application by the process 400 .
  • FIG. 11 is a completed template, whereas the templates that are imported at the step 402 are typically blank.
  • a model identification data structure 1105 contains information input by the user to identify the application model being designed.
  • the model is an aviation safety model.
  • the templates may contain a basic starting point that allows a user to select from multiple selections at each step, from step 404 to step 416 in this example, of the design process 400 .
  • the templates may each be aimed at a central theme or category that the application areas (see step 404 ) are centered around. For example, one template may focus around business, another around entertainment and yet another around health.
  • the design process 400 continues at step 404 with the selection of the application area of interest.
  • the example template 1100 contains an application data structure 1110 where the application area Civil Aviation is listed.
  • an application library 424 is a database containing previously identified application areas that will help narrow the design process 400 in subsequent steps.
  • the application area may be a smaller subset of the template category. For example, if the template is aimed at the business category, then the application area may be business ethics, stock market research, real estate investment, and venture capital funding.
  • the selection of the application area may be done in a tiered approach where the entire category is defined as a sort of tree structure with several branches.
  • Process 400 continues at step 406 with the identification of the database (or simply data) sources.
  • a database library 426 contains a list of disparate data sources that may be utilized. Referring back to FIG. 11 , the template 1100 lists three exemplary data sources that could be chosen for the aviation safety application of the example.
  • the data sources in data structure 1115 include an aircraft data source, an air traffic route data source, and airline maintenance data sources.
  • the database library is preferably an evolving library where new data sources are added whenever they are uncovered in searches of other databases (e.g., new links to associated web pages may be identified during the process of running other related or unrelated decision support models). As more and more data sources become available, the more powerful the resulting decision support system potentially becomes. Preferably, as many data sources as possible are identified at step 406 . However, constrains such as time, processing power, security clearance and others may limit the databases that a user selects to include in the application specific model.
  • the data sources may be categorized into pre-selected categories that are already match to the application area and/or template that the user has selected. The pre-selected data sources may be the result of past success in obtaining relevant information during the execution of other decision support models in the same or similar application areas.
  • FIGS. 5-8 illustrate examples of disparate data sources that may be used in designing a decision support system for four specific application areas
  • FIG. 5 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to an anti-terrorism application.
  • FIG. 6 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to a general data types application.
  • FIG. 7 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to a human factors application.
  • FIG. 8 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to an ecosystem application.
  • the FIGS. 5-8 are simply examples of the types of different data sources that can be selected at step 406 when using the process 400 .
  • Process 400 continues at step 408 with the selection of the variables to be searched for at each source. Some embodiments may search for the same variables on all data sources while other embodiments may specify data source specific variables to be searched.
  • the template 1100 contains a variable data structure 1120 .
  • the variables in the data structure 1120 include a vehicle registration number variable, a vehicle model variable and a vehicle payload variable. These are example variable and are not meant to be an exhaustive list.
  • variable library 428 contains information that may be used in selecting the variables at step 408 .
  • the variable library may be an evolving library which includes variables selected by other users when designing their models.
  • the variable library 428 may contain variables categorized under various headings in a tiered hierarchy. For example, a category of personal identification may include variables listed for drivers license variables, birth certificate variables, international visa variables, and or passport variables.
  • the passport variables might contain the following choices:
  • the process 400 continues at step 410 where weights are assigned to each variable.
  • the weights are used in calculated the relevance of information found at the many disparate sources that were selected at step 406 . Higher weights should be given to those variables that are most important to the decision support process.
  • the template 1100 lists the weights assigned to each variable in the variables data structure 1120 .
  • a weighting guidelines library 430 contains suggested weightings for variables. The weighting guidelines may be based on the application area, the database source, and other criteria. In some embodiments, the weighting guidelines evolve or develop over time in a training session. The training session may be in the design phase of the model. The training session may continue during actual use by multiple clients. This way the weighting guidelines change as the information and world of events changes.
  • Time frame limits and location limitations may be defined at step 412 .
  • Each application may look at the time variable differently. For example in a flight safety application, the time range may be fairly small with regard to reaching pre-defined waypoints or performing certain aircraft navigation duties. In contrast, the status of a shipping container may be of low interest for weeks at a time but once the vessel comes within a certain range of port, the relevant timeframe may change to minutes. Lastly, the relevant timeframe for a valid passport may be ten years whereas a visa may only be valid for days or weeks. Time frame limits may be added to narrow the searches for predicted outcomes and/or correlated past events to a certain range around the current time that the model is being run. This may be desired in order to save time and/or processing power. Referring back to FIG.
  • the example template 1100 contains a time frame and location limitations data structure 1125 listing some exemplary uses of time and location limitations.
  • the searches will be limited to Persons over 18 and present in the US as relevant to any analysis. However, with respect to Aircraft, the search is broadened to include any craft globally with the same model number. Finally, the search will consider any route flown from 1940 to the present in the U.S. to be of relevance.
  • a timeframe guideline library 432 contains suggested time frame limitations for each data type and application area.
  • Fuzzy rules are selected or defined at step 414 .
  • Fuzzy rules may include chains of fuzzy variable membership functions combined with fuzzy logic operations including unions, intersections, and complements or combinations thereof. Fuzzy rules may also include modifiers (e.g., raising membership functions to a power to add a degree of correctness or incorrectness) that may be used to apply the weighting factors assigned in step 410 .
  • the template 1100 contains a rules definition data structure 1130 that lists rules sets (identified by rule numbers) for each variable and lists the associated Fuzzy Rules System and/or Application that the rule set numbers relate to.
  • a Rule Library 434 presents a list of tools, each of which is linked to a series of pre-defined rule sets is used
  • Zaptron FIDE that resides on system SuperSam3
  • Rule set 87 is used to identify anomalies in the FAA registration database.
  • the rules selection process is continued for each variable or variables with as many rules as needed.
  • a fuzzy rule library may contain guidelines to designing the fuzzy rules in step 414 .
  • the fuzzy rule guidelines contained in the library 434 evolve or develop over time (e.g., during development of the system or during actual use of the system). The basics of fuzzy logic are known to those of skill in the art and will not be discussed in detail.
  • analysis functions may be designed or defined at step 416 .
  • Analysis functions can include probability theory, Boolean logic, data mining and other types of correlative types of analysis functions. Analysis functions can include any of several analysis techniques known to those of skill in the art, such as:
  • the template 1100 contains an analytical process data structure 1135 that lists analytical processes selected for each variable and lists the specific analytical techniques and Systems and/or Applications to be used.
  • a Function Library 436 presents a list of tools, each of which is linked to a series of pre-defined analytical analysis sets.
  • a MatLAB7 tool that resides on system BigBlue7 comprising Bayes Function set 45A is selected to identify anomalies in the passenger manifest.
  • the analysis function selection process is continued for each desired variable or variables with as many rules as needed.
  • a function library, 436 contains suggested analysis functions.
  • the analysis guidelines contained in the library 436 evolve or develop over time (e.g., during development of the system or during actual use of the system).
  • the application specific model (or script) is stored at step 418 .
  • the model can be stored in the model library 422 that also stored the template that was used to start the process 400 .
  • the model can be loaded from memory to be used by the designer or by other clients depending on the embodiments. It should be noted that any of the steps and/or libraries in FIG. 3 may be rearranged or combined with one or more other steps without changing the function of the process 400 .
  • FIG. 4 is a flowchart illustrating certain steps in a process for performing a decision support process using an application specific model developed with the process of FIG. 3 .
  • Process 500 begins by importing an already designed decision support model, created using the process 400 , from a model library 532 .
  • the model library 532 can be the same as the model library 422 of FIG. 3 .
  • the controller 220 of FIG. 2 can perform the importing of the application model.
  • the controller 220 can also coordinate the flow of the process 500 to the other components of the server 200 that can be conducting some or all of the process 500 steps.
  • a correlation process is conducted.
  • a current scenario 505 of the applicable variables is input to the process 500 in order to perform the correlation acts.
  • the current scenario 505 can include values for each of the selected variables designed into the decision support model being executed (e.g., the variables selected at step 408 in the process 400 ).
  • the current scenario 505 variables can be updated periodically using the real-time monitoring interface 222 and/or the external/non-conforming data sources component 240 of FIG. 2 .
  • the current scenario is correlated with previously obtained data contained in the various libraries/storage components such as, for example, a scenario library 534 and/or the historical data module 202 shown in FIG. 2 .
  • the data storage interface can retrieve the previously obtained data contained in the libraries and/or storage components.
  • the correlation process preferably uses the weights assigned to each variable, at step 410 in the model design process 400 , in calculating the correlations. This way the correlated historical scenarios will be skewed in the direction of the more important variables.
  • Some models can be conducted without weights, or with all weights set to a default value such as one.
  • “Complex Systems Modeling” may be used to identify the correlations between the current scenario data obtained from the multiple disparate data sources and the historical data stored in the scenario library 534 .
  • the data mining components 232 of FIG. 2 can be used in performing the correlation tasks of step 504 , e.g., using pattern recognition techniques.
  • the process 500 can also conduct fuzzy logic rule processing at step 506 in identifying previously obtained chains of events that may relate to the current scenario 505 .
  • the fuzzy rules may be stored in a rule library 536 .
  • the fuzzy logic rules can enable the process 500 to identify inferences and/or implications in the historical chains of events and compare these chains of events to the current chain of events as exhibited by the current scenario 505 .
  • the fuzzy rules can be designed to reflect the variable weights assigned to the variables in step 410 of the process 400 .
  • the fuzzy inference engine 228 can conduct the fuzzy rule processing of step 506 .
  • Analyses can include statistical analyses, Bayesian analyses, and/or neural network analyses.
  • a function library 538 contains stored analytical functions used at step 508 .
  • the current scenario data can be analyzed to identify parameters or events that are outside of acceptable normal ranges.
  • the current scenario variables can be compared to the accepted ranges (e.g., historical ranges, calculated ranges etc.) in order to identify outlying characteristics.
  • the normal ranges for the variables in question can be stored in the historical ranges component 204 shown in FIG. 2 .
  • an expert information database such as the expert info component 206 of FIG. 2
  • the expert information database may indicate subjective data values corresponding to states such as “optimal”, “danger”, “recommended action or other states, that are indicative of the current scenario chain of events 505 .
  • states such as “optimal”, “danger”, “recommended action or other states, that are indicative of the current scenario chain of events 505 .
  • the statistical analysis component 234 of FIG. 2 can perform the analyses at step 508 .
  • step 510 predictions are made as to what the next likely outcome or event will be.
  • the multiple predictions can be made to fit a time limit determined by the step 412 of the process 400 where the time frame to be used in the application specific model was defined.
  • the multiple analyses performed at step 508 can form the basis for predicting the most likely outcomes.
  • the most probable outcomes identified by the statistical, neural network, and/or fuzzy logic analyses of step 508 are used as the predictions at step 510 .
  • a prediction library 540 contains templates that specify one or more parameters and values, one or more formulae, and one or more predictions at specified time points along a projected vector.
  • the severity of the outcome is contained in the prediction library 540 .
  • the severity of the outcome can be a subjective type of measure indicating the extremeness of an outcome, whether positive or negative. For example, an extremely positive outcome could be that the prediction analysis indicates that the user will win the lottery. An extremely negative outcome could be that the user can expect to lose 90% of his investments in the next year.
  • the extremeness of the outcome can be considered when the recommended actions are determined at step 512 and the potential consequences determined at step 514 , as discussed below.
  • the statistical analysis component 234 , the fuzzy inference engine 228 and/or information retrieved by the controller 220 (using the data storage interface 224 ) can perform the prediction acts of step 510 .
  • recommendations are identified based, at least in part, on their effect on the predicted outcome derived at step 510 .
  • Past scenarios that have been identified by the correlation step 504 and or the fuzzy rule processing step 506 can form the basis for making the recommended actions.
  • the recommended actions may be a single action or multiple actions.
  • the recommended actions may include doing nothing.
  • the recommended actions may be made for the range of time selected at step 412 of the process 400 .
  • the recommended actions are made in parallel with determining the potential outcomes or consequences at step 514 .
  • a recommendation library 542 contains a historical record of past recommended actions and subsequent results that are used to affect the recommendations. These historical recommended actions can be identified by links that were identified in the correlation process of step 504 .
  • Historical recommendations that resulted in both positive and negative outcomes can be included, preferably with negative outcomes causing a change in the historical recommendation and a positive outcome reinforcing the historical recommendation.
  • the controller 220 can locate and retrieve the historical recommendations from the recommendation actions module 210 shown n FIG. 2 . Using these historical recommendations, the controller 220 can make the one or more recommendations at step 512 .
  • the potential consequences as well as the severity of the consequences are determined at step 514 (preferable steps 510 , 512 and 514 are executed simultaneously such that the severity of the predicted outcomes affect the recommended actins).
  • the consequences are stored in a consequence library 544 .
  • the consequences contained in the library 544 are linked to the severity measures discussed above in relation to making the predictions at step 510 .
  • the recommended action/consequence results 518 are presented to the user in order to receive user input 520 as to which recommended action to take.
  • the user can be presented the actions/consequences on the display of the client device (e.g., any of client devices 115 shown in FIG. 1 ).
  • the user is given a choice to select automatic or manual selection of the recommended actions. If the user selects the automatic selection option, a decision block 516 will detect this selection and the process 500 will proceed to step 522 where the recommended action or actions are performed.
  • the user may be presented with a list of one or more historical scenarios including the recommended actions that were given, the tasks that were performed to carry out the recommended actions and the resulting outcomes. These historical recommended actions may not correspond to the current recommended actions, but are presented to the user so as to let the user observe what outcomes may lie ahead if he were not to perform the recommended actions.
  • the automatic selection of actions may choose the action(s) that result in a highest risk reward measurement.
  • the risk reward measurement may qualitative measure (e.g., most happy, least injured, etc.) or a quantitative measure (e.g., highest rate of return on investment, lowest mortgage rate, etc.).
  • the automatic selection may, in some embodiments choose the action that results in optimizing a user specified condition, such as, for example, fastest trip to a destination, lowest grocery bill satisfying nutritional needs and others.
  • the user selects the manual selection of the recommended actions, then the user also inputs (user input 220 ) the recommended action.
  • the decision block 516 then causes the process 500 to proceed to step 524 where the manual action is performed. It should be noted that the recommended actions made at step 512 that follow from predictions made at 510 and the tasks entailed in carrying out the recommended actions, at steps 522 or 524 , are distinct from each other.
  • the chosen recommended action is stored into the database.
  • the outcomes resulting from the tasks performed at steps 522 or 524 are also stored at step 526 when the process 500 obtains them.
  • the user may enter outcomes if they are not obtainable by the prediction support system itself.
  • the server executing the process 500 may retrieve the outcome automatically using either the real-tome monitoring interface 222 or the input data translation component 226 shown in FIG. 2 .
  • an action library 546 contains the necessary script commands to perform the tasks needed to carry out the chosen recommended actions.
  • the script commands contain the necessary instructions to perform the needed task(s) whether it is performed at step 522 (automatic) or step 524 (manual).
  • selecting a recommended action to be performed may not actually cause the corresponding tasks to be performed.
  • the client device or the server running the process 500 can perform the task, the task can be performed.
  • the recommended action requires the user to physically (or mentally) perform the task, then there is no guarantee that the user will actually perform it.
  • any of the steps and/or libraries in FIG. 4 may be rearranged or combined with one or more other steps without changing the function of the process 500 .
  • Steps 510 , 512 and 514 for example can be combined in a way to determine recommended actions based on historical outcomes and the actions taken historically that led to those outcomes.
  • One method of performing these steps starts by identifying a set of past scenarios or chains of events that closely relate to the current scenario 505 (e.g., scenarios identified by the weighted correlation process performed at step 504 and/or the fuzzy rule processing performed at step 506 ).
  • the identified past scenarios can be stored as chain of event templates, where the chain of event templates each include the historical values of the variables defining the scenario, the action that was taken and the resulting outcome.
  • the recommended action can be determined by choosing the historic action that led to a desired or most favorable outcome most often.
  • fuzzy logic can be used to combine multiple actions taken with the desirability of the resulting outcome where the fuzzy logic algorithms provide weighting to the desirability and the type of actions taken.
  • the chain of event templates may also include the action that was recommended (if the scenarios were using the decision support process) in order for the process 500 to be able to identify cases where the recommended action does not correspond to the action that was taken. This may avoid false feedback where a recommended action was ignored and a negative outcome resulted.
  • New chain of event templates are created when no past chain of event scenarios match the current scenario 505 .
  • Existing chain of event templates can also evolve to be substantially different from when they were first created. This can be the result of parameters outside of the control of the user or the process 500 evolving to create a substantially different set of rules that control the chain of events scenarios that are represented by the templates.
  • the application models developed using the process 400 and executed with the process 500 can be structured to resemble a goal-seeking system that begins the process by querying the user for the desired outcome.
  • the process then obtains the values of the variables in the current scenario 505 and compares those values to the variables consistent with the values of the desired outcome.
  • the process 500 described above then seeks to find scenarios (chains of events) that will identify actions to be taken to transition the current scenario toward the desired scenario. There will typically be multiple paths to get to the desired result.
  • the application model can query the user on how he would prefer to get to the goal.
  • the goal can be achieved while optimizing certain characteristics or variables of the application specific model. For example, in an investment application, the goal may be to double the value of an investment in 5 years.
  • the decision support process can identify multiple recommended actions (e.g., investing in highly aggressive or conservative investments) that are chosen to minimize risk, maximize gain, provide less than a certain threshold chance of losing all of the initial investment.
  • the goal can be open-ended or indefinite.
  • the goal may be to optimize a subjective quality. For example, the goal may be to arrive at a destination in the fastest time, in the least dangerous fashion, in the most comfort, etc.
  • fuzzy logic may be used to identify the chain of events that best meet the chances of arriving at the desired destination while optimizing the subjective quality.
  • FIG. 9 is a flowchart illustrating certain steps in a process for parsing private information and storing it in segregated databases, where the databases can be accessed in an anonymous mode to retain personal privacy, or accessed in an authorized mode that reconstructs the private information including the personal identity.
  • the process 900 obtains private records 905 containing a personal identity and information concerning various facts about the person.
  • the information may include sensitive or private information that a person has the right to keep private unless mitigating circumstances exist. Sensitive information may include financial information, criminal records, a record of associations or acquaintances, social security number etc.
  • the information by itself is not an issue. It is only when the information is linked with an identity of an individual that privacy becomes a concern. For this reason, when private information is imported to the decision support system (e.g., retrieved by the real-time monitoring interface component 222 and or the import data translation component 226 of the server 105 shown in FIG. 2 ), a private import process 910 is performed.
  • the private import process 910 starts by parsing the incoming data.
  • the data is parsed to a level needed to keep the identity separate from sensitive or private information.
  • a unique code is assigned to link the identity to the parsed information.
  • Identities and codes may be stored in separate, secure databases with restricted access. True identities are only revealed where special conditions are met, such as securing a warrant. Warrants may be represented as electronic keys to streamline automated processing without compromising security.
  • the information is stored into any of several separated databases such as the databases 915 A, 915 B and 915 C.
  • the databases 915 A to 915 C can be stored on any kind of memory device such as hard drives, CD-ROM, magnetic tape, etc.
  • the information is stored in a data structure that links the unique code with the information.
  • the information in the individual databases can be retrieved (e.g., in order to perform correlative analysis, making predicted outcomes, making recommendation of the process 500 ) separately by proceeding to block 920 .
  • the separate databases do not contain enough information to link the person with the individual facts or events. Data from multiple databases may be combined in a restricted way such that the chains of events used in the decision support process 500 can be identified without connecting a personal identity to the chain of events. This allows the data-mining or exportation of anonymous data.
  • the reconstruction of the private records 905 may be permitted. Such a situation is similar to the issue of a warrant or a subpoena.
  • An electronic warrant key is used to authorize, authenticate and/or permit decryption of information (e.g., access codes or cryptographic keys) to allow reconstruction of the private record for which the authorization was granted 905 .
  • the authorization/authentication act is typically a recorded transaction that is kept in a secure database for purposes of providing an audit trail.
  • Step 925 is able to access multiple data bases as well as link the data in each database to the identification of the person that it is linked to. Obtaining the reconstructed records 925 that include the personal identity variable enables the use of the identity of the person as a variable in the decision support process 500 . It should be noted that any of the steps and/or libraries in FIG. 9 may be rearranged or combined with one or more other steps without changing the function of the process 900 . While the process 900 was described in relation to parsing information to keep the information separate from a person's identity, those of skill in the art will recognize that other forms of sensitive information can be protected in a similar manner. For example, the authorization warrant methodology can also be used to restrict access to other forms of private information. For example, governmental top secret information may be accessed only by authorized individuals. Similar protection may be afforded sensitive information such as company trade secrets, secret negotiations, etc.
  • FIG. 10 is a flowchart illustrating certain steps in a process for obtaining information for use in the decision support process.
  • the process 1000 can be performed by the server based system 200 shown in FIG. 2 .
  • any information that is retrieved by the system 200 performs all of the steps shown in the process 1000 . However, some steps may be omitted without changing the function of the process 1000 .
  • the information may be retrieved by the real-time monitoring interface component 222 and/or the import data transaction component 226 .
  • the process 1000 starts with an authentication process 1005 .
  • the authentication process verifies the source of the retrieved information.
  • the authentication process confirms that the received data is unchanged from what the source transmitted and it also confirms the identity of the source.
  • the sender uses a one-way hash function to generate a digital signature from the transmitted data.
  • the sender then encrypts the hash-code with a private key.
  • the receiver e.g. the server based system 200
  • the integrity services module 242 may perform the authentication at step 1005 .
  • the process 1000 checks if the authentication was successful. If the authentication was not successful, the process 1000 is aborted and the retrieved information may be discarded. The retrieved information may also be retained to be used later.
  • the decision block 1010 directs the process 1000 to proceed to a decryption process 1015 .
  • the decryption process 1015 decrypts the information.
  • the integrity of the decrypted data is typically verified through the use of checksums (e.g., cyclic redundancy checks). If portions of the decrypted data are determined to be erroneous, decision block 1020 will determine that the decryption was unsuccessful for that portion of data and abort the process (discard the erroneous portions of data) as it pertains to the erroneous data.
  • the integrity services module 222 may perform the decryption at step 1015 .
  • the decision block 1020 directs the process 1000 to a decompression process 1025 .
  • Any of the various compression/decompression algorithms can be used to compress information depending on the type of media that is being compressed. If decompression is unsuccessful, the decision block 1030 causes the process 1000 to be aborted, at least for the portion of information that was unsuccessfully decompressed.
  • the integrity services module 222 may perform the decompression at step 1025 .
  • the process 1000 proceeds to a filtering process 1035 .
  • the filtering process can perform the reformatting tasks discussed above in relation to the import data translation module 226 .
  • the data is filtered so as to conform to the format desired by the decision support system 200 . If the filtering at step 1035 is determined, at decision block 1040 , to be unsuccessful in translating the information into a conformal format, then the process 1000 is aborted, at least for the portion of information that was not successfully filtered.
  • the process 1000 proceeds to step 1045 where the privacy process 900 shown in FIG. 9 is performed.
  • the privacy process 1045 can be performed in at least two exemplary ways.
  • the privacy process 1045 is used to reconstruct the private information (see the reconstructed records 935 in FIG. 9 ) retrieved from the already parsed databases (e.g., the databases 915 A, 915 B and 915 C).
  • decision block 1050 checks to see if the proper authorization warrant 930 is available. If the authorization warrant 930 is not available, the decision block 1050 aborts the process 1000 as it relates to obtaining the reconstructed records 935 .
  • the decision block 1050 directs the process 1000 to a parsing process 1055 .
  • the privacy process 1045 is used to determine if there is private information contained in the retrieved information that needs to be parsed before the data is stored for use in the decision support system.
  • the decision block 1050 determines if the private information (e.g., personal identity information) has been identified (e.g., flagged) to be parsed into the secure personal identification/unique code database that was discussed above in relation to FIG. 9 . This way the parsing process 1055 can recognize that there is personal identity information present and the unique code can be linked to the parsed information to separate the information from the personal identity. If the personal identity information is properly identified, then the process 1000 proceeds to the parsing process 1055 .
  • the private information e.g., personal identity information
  • the parsing process 1055 performs parsing of the received information into the various variables that are used to identify related chains of events in the process 500 discussed above.
  • the parsed information is then linked to classifications of the data structure to be used for the decision support process.
  • the linking can be in the form of cross references to the various application specific model templates that the information may be relevant to.
  • the linking can be in the form of cross references to the individual chain of events templates used in determining the predicted outcomes and the recommended actions of the process 500 .
  • the linking can also be in the form of cross references to the various libraries used in the process 400 for developing the application specific models.
  • step 1065 the information is stored in to the multidimensional data structure to be used in the processes discussed above. It should be noted that any of the steps in FIG. 10 may be rearranged or combined with one or more other steps without changing the function of the process 1000 .
  • the pilot arrives at the aircraft to perform the routine preflight checks of the aircraft.
  • the Trusted Decision Support System has pre-assigned the subject being analyzed as aircraft safety of flight.
  • the decision support system references the model library and selects the script designated for the aviation safety model.
  • the model for aviation safety identifies areas specific to aviation safety that must be analyzed by the system. For example, one aspect of the model instructs the system to reference the FAA Airmen Certification Database using the pilot information for the crew assigned to flight 261.
  • the airmen certificate number, the pilot name, and the airline employee identification number are used to research the pilot flight test records, the pilot citation records, pilot citation records, pilot training records, pilot conduct records, and pilot performance records, aircraft flown records, and type rating records.
  • the decision support system then references the scenario library while conducting a correlation process between the information in the library and the information provided about the flight crew.
  • the rule library is referenced for allowable parameter values and a customized set of rules regarding the flight crew is established for the flight.
  • the value of parameters are evaluated against the fuzzy rule set to determine if any value is outside the established allowable values. For example, rules for this flight based on the historical values given from the scenario library dictate that the crew must have 10 hours of off duty rest period between block times in the aircraft. The pilot information database confirms 11.5 hours between the aircraft shut down, the crew arrival, and aircraft restart. This variable would be evaluated as a non-anomaly based on it falling within the parameters allowed by the established rule set.
  • the aviation safety model used in this scenario calls for the maintenance records of the specific MD-83 aircraft scheduled for flight 261 to be referenced.
  • the rule library for this scenario dictates that the variable may not have any instances of required maintenance work going undone.
  • the referenced maintenance records indicate that in September 1997 mechanics at the Alaska Airlines Oakland maintenance facility discovered that the gimbal nut on the horizontal stabilizer was “badly worn and in dire need of replacement.”
  • the same maintenance records showed that Alaska Airlines ordered additional tests on the assembly and deemed it airworthy with no maintenance action required.
  • the rule set for this scenario calls for no deviations from required maintenance actions. This event would be flagged as negatively effecting the safety of flight for this aircraft
  • the system references a function library to conduct multiple levels of analysis regarding the information provided in the correlation process and the variable rule processing stages.
  • the system references a prediction library to base probabilities of event occurrence based on current variable values.
  • the system references the time when the pilot activates the electrical system of the aircraft as the starting point to reference the flight timeline against. All predictions made for this flight from the prediction library are linked to a predicted time of occurrence related to this timeline.
  • Each event is linked to a list of consequences related to that recommendation via the consequence library.
  • the pilot is presented a score based on the risk factors for the flight, and given a list of events and their corresponding probability score. Each event listed is given a time of occurrence and is linked to a list of recommendations from the recommendation library.
  • the crew is presented with a list of actions, both manual and automatic for them to choose from to lessen the risk associated with this flight.
  • the crew has performed all actions listed on the actions page and permitted the automated systems to perform all available actions automatically.
  • the actions of the crew, and the results of the actions are stored in the database for the flight and the process is reset automatically updating with each change in any observed variable in the aviation safety model.
  • the system constantly updates the information provided by the prediction system, along with readings from the avionics systems aboard the aircraft.
  • Current conditions and flight system information is run through the fuzzy rule process based on information from the rule library.
  • Each variable is assessed through the fuzzy rule set to determine whether its value falls within the allowable parameter value limits.
  • the control pressure for pitch attitude has a limit of 100 pounds of force required at the control input end to manipulate the control.
  • the system was on autopilot, so no control input should have been taking place.
  • constant input from the trim system was required to maintain aircraft attitude.
  • the pitch trim force required variable observed to be within the allowable fuzzy rule parameters The analysis of the system, and the prediction process show that according to the current patterns, the pitch trim force required to maintain level flight will exceed the allowable parameter value limits in one hour and 45 minutes of flight.
  • the system determines the recommended actions according to the timeline established by the prediction process.
  • the consequence library is used to determine potential consequences for each action performed by the crew, automated systems, and failures of systems and their interdependent systems.
  • the crew is alerted about the results of the process and prompted to acknowledge the severity of the consequences of the predicted system failures. Both manual and automatic actions are performed to mitigate the risks associated with the failure.
  • the FAA, emergency crews at the nearest airports, search and rescue personnel, aircraft experts, airline emergency maintenance personnel, and airline crisis management teams are all notified of the situation.
  • Each entity is updated with complete information automatically relayed to and from the aircraft.
  • the timeline for failure is constantly updated with each action taken by the flight and ground crews.
  • the system has alerted the pilots and all appropriate parties of the impending failure and its consequences 1:56 minutes prior to the actual point of failure. Based on the actions recommended by the decision support system, the crew is able to adjust the flight controls on the aircraft to minimize the forces acting upon the horizontal stabilizer. Furthermore, the aircraft is diverted to the nearest location, landing safely in San Diego, 42 minutes prior to the point of failure.

Abstract

Methods and apparatus for providing a comprehensive decision support system to include predictions, recommendations with consequences and optimal follow-up actions in specific situations are described. Data is obtained from multiple disparate data sources, depending on the information deemed necessary for the situation being modeled. Some embodiments perform complex systems modeling including performing massive correlative analyses of the data obtained from the multiple disparate data sources with current situational data obtained regarding the situation for which the decision support process is being utilized. The decision support system provides a prediction or predictions and a recommendation or a choice of recommendations based on the correlative analysis and/or other analyses. In some embodiments the decision support system provides possible consequences that could result from a recommendation. In other embodiments the decision support system provides a list of tasks for acting upon a recommendation. Also described are methods and apparatus for developing application specific decision support models. The decision support model development process may include identifying multiple disparate data sources for retrieval of related information, selection of classification variables to be retrieved from the data sources, assignment of weights to each classification variable, selecting and/or defining rules, and selecting and/or defining analysis functions.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims priority of U.S. provisional application Ser. No. 60/677,164 filed on May 3, 2005, and of U.S. provisional application Ser. No. 60/735,539 filed on Nov. 10, 2005, both of which are incorporated by reference in their entirety. This application is one of a set of related U.S. applications, the set including: TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A, filed on even date herewith); TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A2, filed on even date herewith); TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A3, filed on even date herewith); TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A4, filed on even date herewith); TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A5, filed on even date herewith) TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A6, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A1, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A2, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A3, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A4, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A5, filed on even date herewith); TRUSTED DECISION SUPPORT SYSTEM AND METHOD (Atty. Docket No. PALO.002A6, filed on even date herewith); all of which are incorporated by reference in their entirety.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The field of the invention relates to complex data modeling and data modeling. More particularly, the invention relates to massive correlative analysis and predictive modeling.
  • 2. Description of the Related Art
  • The exponential increase of information over the last half-century is widely reported yet the impact of this on decision making has gone largely unnoticed. It's not that the decisions themselves have become more difficult—just that our expectations have become exponentially higher as a result of the volume of available data, coupled with our access to vast computer processing power.
  • As most any modern decision-maker can attest, this volume of information surrounding decisions is not always helpful. In all but very few cases, one must rely upon myriad disparate sources of information, each having been gathered and structured in its own idiosyncratic way. This causes several fundamental problems: 1) the information is often collected or input by inadequately trained individuals who don't understand the importance of consistent, quality data; 2) each database is designed to serve a particular purpose and rarely lends itself to use outside the narrow scope of its original purpose (e.g. comparing apples to oranges); and 3) most data collected is not accurately synchronized with a time/space context that all but prevents accurate cross-referencing with similar information.
  • For decades researchers have been attempting to address this growing problem. Solutions have been labeled everything from Recommender Systems to Artificial Intelligence, but met with only modest results. This disappointing outcome can be attributed partially to the fundamental data weaknesses outlined above and partially to the myopic scope of these earlier solutions. A growing body of research in complex systems theory suggests that many phenomena are significantly impacted by a large number of adjacent spheres of influence—an observations referred to as “small world networks”. In field after field, researchers are discovering a high degree of interconnectivity that reveals new correlations never before understood. This has led some to draw a parallel to a similar phenomenon in the social domain called “Six degrees of separation”. This work has recently been successfully verified in applications ranging from protein-protein interactions in a cell to the behavior of a terrorist cell. In all these cases, the common theme is the behavior of each component depends on the behavior of others. Thus there is a need for improved systems and methods for making decisions and for carrying out related tasks
  • SUMMARY OF THE INVENTION
  • The system, method, and devices of the invention each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this invention, its more prominent features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “Detailed Description of Certain Inventive Embodiments” one will understand how the features of this invention provide advantages over other error management solutions.
  • One embodiment is a system including an electronic device configured to select a data set for an application area, to assign weighted scores to the data in the data set, to correlate the weighted data set with one or more previously correlated weighted data sets, and to determine, based upon the correlation, a recommended action as a response to an event related to the data set.
  • Another embodiment is a system including a sensor network, a database including data from the sensor network, and an electronic device configured to select a data set from the database for an application area, to assign weighted scores to the data in the data set, to correlate the weighted data set with one or more previously correlated weighted data sets, and to determine, based upon the correlation, a recommended action as a response to an event related to the data set.
  • Another embodiment is a method of analyzing data, including identifying one or more data sets for an application area, assigning weighted scores to the data in the data set, correlating the weighted data set with one or more previously correlated weighted data sets, and determining, based upon the correlation, a recommendation a recommendation for a response to an event that is related to the identified data set.
  • Another embodiment is a system including an electronic device configured to select a data set for an application area and to analyze the data set according to fuzzy logic instructions so as to generate a recommended action and outcome information for the recommended action.
  • Another embodiment is a method of analyzing data, including identifying one or more data set for an application area, and analyzing the data set according to fuzzy logic instructions, so as to generated a recommended action and outcome information for such recommended action.
  • Another embodiment is a system including an electronic device configured to select a data set for an application area and to analyze the data set according to statistical analysis instructions so as to generate a recommended action and outcome information for the recommended action.
  • Another embodiment is a method of analyzing data, including identifying one or more data set for an application area, and analyzing the data set according to statistical analysis instructions, so as to generated a recommended action and outcome information for such recommendation action.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 shows a network for implementing a trusted decision support system.
  • FIG. 2 is a block diagram illustrating certain functional blocks of a server based system for hosting the trusted decision support system.
  • FIG. 3 is a flowchart illustrating certain steps in a process for developing an application specific decision support model.
  • FIG. 4 is a flowchart illustrating certain steps in a process for performing a decision support process using an application specific model developed with the process of FIG. 3.
  • FIG. 5 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to an anti-terrorism application.
  • FIG. 6 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to a general data types application.
  • FIG. 7 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to a human factors application.
  • FIG. 8 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to an ecosystem application.
  • FIG. 9 is a flowchart illustrating certain steps in a process for parsing private information and storing it in segregated databases, where the databases can be accessed in an anonymous mode to retain personal privacy, or accessed in an authorized mode that reconstructs the private information including the personal identity.
  • FIG. 10 is a flowchart illustrating certain steps in a process for obtaining information for use in a decision support process.
  • FIG. 11 is an example template that can be created for an application with the process of FIG. 3.
  • DETAILED DESCRIPTION OF CERTAIN INVENTIVE EMBODIMENTS
  • Methods and apparatus for providing a comprehensive decision support system to include predictions, recommendations with consequences and optimal follow-up actions in specific situations are described. Data can be obtained from multiple disparate data sources, depending on the information deemed necessary for the situation being modeled. Some embodiments perform complex systems modeling including performing massive correlative analyses of the data obtained from the multiple disparate data sources with current situational data obtained regarding the situation for which the decision support process is being utilized. The decision support system may provide a prediction or predictions and a recommendation or a choice of recommendations based on the correlative analysis and/or other analyses. In some embodiments the decision support system may provide possible consequences that could result from a recommendation. In other embodiments the decision support system may provide a list of tasks for acting upon a recommendation. Also described are methods and apparatus for developing application specific decision support models. The decision support model development process may include identifying multiple disparate data sources for retrieval of related information, selection of classification variables to be retrieved from the data sources, assignment of weights to each classification variable, selecting and/or defining rules, and selecting and/or defining analysis functions.
  • In the following description, specific details are given to provide a thorough understanding of the disclosed methods and apparatus. However, it will be understood by one of ordinary skill in the art that the disclosed methods and apparatus may be practiced without these specific details. For example, electrical components may be shown in block diagrams in order not to obscure certain aspects in unnecessary detail. In other instances, such components, other structures and techniques may be shown in detail to further explain certain aspects.
  • It is also noted that certain aspects may be described as a process, which is depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently and the process can be repeated. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.
  • FIG. 1 shows a network for implementing a trusted decision support system. The decision support system 100 includes a server 105, a storage component 110, client terminals 115A, 115B and 115C, where three client terminals is only used as an example, and a network 120 connecting the other components.
  • The server 105 contains processing components and software and/or hardware components for implementing the decision support system. The server 105 contains a processor for performing the related tasks of the decision support system. The server 105 also contains internal memory for performing the necessary processing tasks. In addition, the server 105 is connected to an external storage component 110 via the network 120. The processor is configured to execute one or more software applications to control the operation of the various modules of the server as will be discussed below in reference to FIG. 2. The processor is also configured to access the internal memory of the server 105, or the external storage 110 to read and/or store data. The processor may be any conventional general purpose single- or multi-chip microprocessor such as a Pentium® processor, Pentium II® processor, Pentium III® processor, Pentium IV® processor, Pentium® Pro processor, a 8051 processor, a MIPS® processor, a Power PC® processor, or an ALPHA® processor. In addition, the microprocessor 100 may be any conventional special purpose microprocessor such as a digital signal processor.
  • The storage component 110 contains memory for storing information used for performing the decision support processes provided by the system 100. Memory refers to electronic circuitry that allows information, typically computer data, to be stored and retrieved. Memory can refer to external devices or systems, for example, disk drives or tape drives. Memory can also refer to fast semiconductor storage (chips), for example, Random Access Memory (RAM) or various forms of Read Only Memory (ROM), that are directly connected to the processor. Other types of memory include bubble memory and core memory.
  • The client devices 115A-115C represent any type of device that can access a computer network. Devices such as PDA's (personal digital assistants), cell phones, personal computers, lap top computers, set top boxes are examples of devices that could be used as the client devices 115. The client devices will typically have a display device and one or more input devices. For example, the input device may be a keyboard, rollerball, pen and stylus, mouse, or voice recognition system. The input device may also be a touch screen associated with an output device. The user may respond to prompts on the display by touching the screen. Textual or graphic information may be entered by the user through the input device.
  • The network 120 may include any type of electronically connected group of computers including, for instance, the following networks: Internet, Intranet, Local Area Networks (LAN) or Wide Area Networks (WAN). In addition, the connectivity to the network may be, for example, remote modem, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI) or Asynchronous Transfer Mode (ATM). Note that computing devices may be desktop, server, portable, hand-held, set-top, or any other desired type of configuration. As used herein, the network includes network variations such as the public Internet, a private network within the Internet, a secure network within the Internet, a private network, a public network, a value-added network, an intranet, and the like.
  • FIG. 2 is a block diagram illustrating certain functional blocks of a server based system for hosting the trusted decision support system. The system 200 includes the server 105 that is connected, to an administrative workstation 236, and to external data sources 240. The server 105 is comprised of various modules 202-234. As can be appreciated by one of ordinary skill in the art, each of the modules 202-234 comprises various sub-routines, procedures, definitional statements, and macros. Each of the modules 202-234 are typically separately compiled and linked into a single executable program. Therefore, the following description of each of the modules 202-210 is used for convenience to describe the functionality of the server 105. Thus, the processes that are undergone by each of the modules 202-234 may be arbitrarily redistributed to one of the other modules, combined together in a single module, or made available in a shareable dynamic link library. Further each of the modules 202-234 could be implemented in hardware.
  • The controller 220 serves as the central interface linking the other modules 222-234. The controller 220 coordinates the use of the other modules based on the script instructions that define the task (e.g., an application specific decision support model) that is being processed. The modules 232-234 execute the various functions used to perform the decision support processes. The data modules 202-210 comprise memory that stores previously generated data an is also used to store new data as it is generated by the other modules. The data storage interface module 224 is configured to retrieve and store data to and from the data modules 202-210.
  • The real-time monitoring interface 222 is configured to monitor multiple disparate data sources in search of information that matches any of several variables that the current decision support model is designed to retrieve. In some embodiments, the real-time monitoring interface 222 retrieves from the disparate data sources that are part of a secure communications network for use with the decision support system. In these embodiments, each of the disparate data sources conforms to a security protocol and a data format. The data that is retrieved by the real-time monitoring interface 222 is forwarded to the controller 220 which then forwards the data for use by other modules or to be stored.
  • Disparate data sources that are part of a secure communication network may include data sources that are under the control of an organization that controls the communications network that the data is retrieved from. For example, if the decision support system is part of a U.S. government communications network, the following databases may be directly connected to the decision support system and may conform to the security protocol and data format:
  • FBI's INFRAGUARD database
  • National Homeland Security database
  • FAA Airmen Certification database
  • FAA Registered Aircraft database
  • SEC filings EDGAR database
  • TECS US Customs Enforcement database
  • The real-time monitoring interface 222 retrieves data from a set of conforming data sources. In contrast, an import data translation module 226 is configured to retrieve information from non-conforming data sources 240. The information may be any that matches any of the several variables that the current decision support model is designed to retrieve. The non-conforming data sources can be accessed from any of several public, private, secure, and/or non-secure networks such as those discussed above in reference to the network 120 of FIG. 1. Non-conforming data sources may include web pages on the Internet. The Internet contains a plurality of web pages that are searchable by the import data translation module 226. The web pages are virtual documents that each have embedded links which link portions of the virtual pages to other virtual pages and other data. Other examples of data sources that may be accessed using the real-time monitoring interface include private databases such as Lexis/Nexis, Dow Jones, Medline, etc, each of which have different security, quality, structure and subject matter. The import data translation module 226 can traverse the virtual pages and download data that matches any of the several variables that the current decision support model is designed to retrieve. The data that is retrieved by the import data translation module is converted to conform to the same data format that the real-time monitoring interface module 222 uses. The conversion to the conforming format may include classifying portions of the information into the various search variables and then parsing the classified information variables into specific fields of a multidimensional data structure (e.g., fields may include time, location, account numbers, flight numbers, etc.). After the retrieved data is converted to the conforming format, it is forwarded to the controller 220 for use in other modules or to be stored.
  • In some embodiments, the data that is retrieved by the import data translation component 226 may be of questionable integrity. Networks such as the internet typically employ a base level of protection for transporting data of all kinds. One example is the Transport Control Protocol (TCP). TCP is a transport layer protocol used to provide a reliable, connection-oriented, transport layer link among computer systems. The network layer provides services to the transport layer. Using a two-way handshaking scheme, TCP provides the mechanism for establishing, maintaining, and terminating logical connections among computer systems. TCP transport layer uses IP as its network layer protocol. Additionally, TCP performs functions such as transmission of byte streams, data flow definitions, data acknowledgments, lost or corrupt data re-transmissions, and multiplexing multiple connections through a single network connection. Finally, TCP is responsible for encapsulating information into a datagram structure. An integrity services module 242 is configured to perform the integrity checks of TCP or other types of transport layer protocols known to those of skill in the art (e.g., hypertext transmission protocol, secure: HTTPS). The integrity services module 242 may also be used to authenticate contextual information obtained from non-conforming sources by comparing the non-conformal source information to duplicate information that has been obtained from trusted sources (e.g., sources such as the conformal sources connected to the real-time monitoring interface 222). This type of contextual authentication may avoid the importation of accidentally incorrect information and/or purposefully false information (e.g., information that may have been planted for purposes of disinformation).
  • In some embodiments, the import data translation component 226 may use methods to convert non-textual information into text to be stored. Many sources of information, especially on the internet, are stored in various forms of multimedia including audio, image, and our video formats. Various methods can be used to convert from a media format to a textual format. These methods include, for example, speech to text methods, voice recognition methods, and image recognition (recognizing faces, and/or objects and classifying them as identified people or things). These types of conversions can be used to classify variables (e.g., time, location, people, and/or objects) discovered in audio files, image files and/or video files, and store them in the various databases, such as the historical data module 202, for later analysis.
  • The disparate data sources, whether they are of the conforming type or the non-conforming type, preferable come from as many different types of networks and/or systems as possible. The larger the number of disparate data sources, the more chance of that analysis tools such as the complex systems modeling tools and massive correlative analysis tools may uncover correlated events. In some embodiments, the information obtained by the real-time monitoring interface 222 is data sampled by one or more remote monitoring systems and/or remote sensors as described in the U.S. application entitled: TRUSTED MONITORING SYSTEM AND METHOD (Atty. Docket No. PALO.001A) and filed on even date. Examples of disparate data sources that may be utilized for several application specific situations are illustrated in FIGS. 5 to 8.
  • The modules 228, 232 and 234 are analysis components that are used in searching for patterns, correlated events, recommended actions and/or probable consequences using various mathematical methods. A fuzzy inference engine component 228 is configured to analyze any of the newly retrieved and/or stored data according to fuzzy logic rules defined by the specific decision support model that is being executed. Examples of commercially available fuzzy inference engines include: mbFuzzIT, Mentalogic Systems Inc Fuzzy Inference Engine and the Fuzzy Inference Development Environment from Zaptron. Fuzzy logic can be used to represent the correctness of a chain of reasoning connecting a chain of events. The correctness can vary from true (represented by a 1, for example), to false (represented by zero, for example) and may be equal to intermediate values (almost true or almost false). Those of skill in the art will recognize these and other uses of fuzzy logic. Fuzzy logic rules may be used to identify various inferences and/or implications correlated to various chains of events. The various inferences and/or implications may be the recommended actions and/or consequences identified by the decision support model.
  • A data mining module 232 is configured to analyze data retrieved by the various other modules using tools which look for trends or anomalies without knowledge of the meaning of the data. The data mining module 232 is used to discover patterns and correlations in the large preexisting data modules 202-210 in order to uncover new meaning in data. Examples of commercially available data mining tools include: DataCruncher by DataMind, Darwin by Thinking Machines, and Intelligent Miner from IBM.
  • A statistical analysis engine 234 is configured to perform statistical analysis for determining probabilities, for example, for use in determining the recommended actions generated by the decision support system. Examples of commercially available statistical analysis tools include SAS/STAT from SAS, MatLAB from MathWorks, and MS Office-Excel from Microsoft.
  • A graphic interface generation module 230 is configured to present a graphical user interface to a user of the administrative workstation 236 in this example. The graphical user interface enables an administrative user to develop models and use the models for performing the decision support analysis. Examples of commercially available graphical user interface design tools that can be used to generate the graphical user interfaces include CVSgui from WinCVS, System Management Interface Tool from IBM, and Visual Basic from Microsoft.
  • It should be noted that any one of the functional blocks illustrated in FIG. 2 may be rearranged and/or combined with one or more other blocks without changing the function of the server 200.
  • FIG. 3 is a flowchart illustrating certain steps in a process for developing an application specific decision support model. The process 400 is used to develop a decision support model directed to a specific application for providing guidance and decision making to a user. An application is a scenario that the decision support process is directed at. Examples of applications include the following application areas each listing representative samples of related sub-application components:
  • 1. Flight safety
      • a. Vehicle integrity
      • b. Passenger integrity
      • c. Route integrity
      • d. Schedule integrity
  • 2. Cargo logistics
      • a. Supplier/manufacturer integrity
      • b. Container integrity
      • c. Product integrity
      • d. Shipper integrity
      • e. Handling personnel integrity
      • f. Route integrity
  • 3. Crude oil futures
      • a. Untapped reserves
      • b. Refining capacity
      • c. GNP of industrialized nations
      • d. Annual vehicle sales
      • e. News stories about oil
      • f. Annual production of petroleum based products
      • g. Financial markets commodity trading volume
  • 4. Financial condition of public companies
      • a. Board integrity
      • b. Management integrity
      • c. Market integrity
      • d. Raw material integrity
      • e. Stock trading volume
      • f. Financial performance
      • g. Sector comparables
      • h. News reports
      • i. SEC filings notations
      • j. Legal actions pending
  • The process 400 starts at step 402 where a template of an application model is imported to the design process 400 from a library 422 containing one or more templates of models that can be fine-tuned to fit a given application (e.g., flight safety in this example). FIG. 11 is an example template that can be created for an application by the process 400.
  • FIG. 11 is a completed template, whereas the templates that are imported at the step 402 are typically blank. A model identification data structure 1105 contains information input by the user to identify the application model being designed. In this example, the model is an aviation safety model. Referring back to FIG. 11, the templates may contain a basic starting point that allows a user to select from multiple selections at each step, from step 404 to step 416 in this example, of the design process 400. In some embodiments, the templates may each be aimed at a central theme or category that the application areas (see step 404) are centered around. For example, one template may focus around business, another around entertainment and yet another around health.
  • After a template is imported, the design process 400 continues at step 404 with the selection of the application area of interest. The example template 1100 contains an application data structure 1110 where the application area Civil Aviation is listed. In one embodiment, an application library 424 is a database containing previously identified application areas that will help narrow the design process 400 in subsequent steps. The application area may be a smaller subset of the template category. For example, if the template is aimed at the business category, then the application area may be business ethics, stock market research, real estate investment, and venture capital funding. The selection of the application area may be done in a tiered approach where the entire category is defined as a sort of tree structure with several branches.
  • Process 400 continues at step 406 with the identification of the database (or simply data) sources. A database library 426 contains a list of disparate data sources that may be utilized. Referring back to FIG. 11, the template 1100 lists three exemplary data sources that could be chosen for the aviation safety application of the example.
  • The data sources in data structure 1115 include an aircraft data source, an air traffic route data source, and airline maintenance data sources. The database library is preferably an evolving library where new data sources are added whenever they are uncovered in searches of other databases (e.g., new links to associated web pages may be identified during the process of running other related or unrelated decision support models). As more and more data sources become available, the more powerful the resulting decision support system potentially becomes. Preferably, as many data sources as possible are identified at step 406. However, constrains such as time, processing power, security clearance and others may limit the databases that a user selects to include in the application specific model. In some embodiments, the data sources may be categorized into pre-selected categories that are already match to the application area and/or template that the user has selected. The pre-selected data sources may be the result of past success in obtaining relevant information during the execution of other decision support models in the same or similar application areas.
  • FIGS. 5-8 illustrate examples of disparate data sources that may be used in designing a decision support system for four specific application areas FIG. 5 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to an anti-terrorism application. FIG. 6 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support process related to a general data types application. FIG. 7 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to a human factors application. FIG. 8 is a block diagram illustrating certain disparate data sources accessible through a communication infrastructure for performing a decision support analysis related to an ecosystem application. The FIGS. 5-8 are simply examples of the types of different data sources that can be selected at step 406 when using the process 400.
  • Process 400 continues at step 408 with the selection of the variables to be searched for at each source. Some embodiments may search for the same variables on all data sources while other embodiments may specify data source specific variables to be searched. Referring back to FIG. 11, the template 1100 contains a variable data structure 1120. The variables in the data structure 1120 include a vehicle registration number variable, a vehicle model variable and a vehicle payload variable. These are example variable and are not meant to be an exhaustive list.
  • The variables define the information elements that will be searched for during the decision support process. For example, if the application area is airline flight safety, some of the variables may include airline names, passenger lists, airline accident records, flight numbers, weather, time of year, destination and origination points and many others. A variable library 428 contains information that may be used in selecting the variables at step 408. In some embodiments, the variable library may be an evolving library which includes variables selected by other users when designing their models. The variable library 428 may contain variables categorized under various headings in a tiered hierarchy. For example, a category of personal identification may include variables listed for drivers license variables, birth certificate variables, international visa variables, and or passport variables. The passport variables might contain the following choices:
  • Passport number
  • Photograph
  • First name
  • Last name
  • Birth date
  • Street address, state, zip
  • Issue date
  • Issue location
  • Valid until date
  • After the variables are selected, the process 400 continues at step 410 where weights are assigned to each variable. The weights are used in calculated the relevance of information found at the many disparate sources that were selected at step 406. Higher weights should be given to those variables that are most important to the decision support process. Referring back to FIG. 11, the template 1100 lists the weights assigned to each variable in the variables data structure 1120. A weighting guidelines library 430 contains suggested weightings for variables. The weighting guidelines may be based on the application area, the database source, and other criteria. In some embodiments, the weighting guidelines evolve or develop over time in a training session. The training session may be in the design phase of the model. The training session may continue during actual use by multiple clients. This way the weighting guidelines change as the information and world of events changes.
  • Time frame limits and location limitations may be defined at step 412. Each application may look at the time variable differently. For example in a flight safety application, the time range may be fairly small with regard to reaching pre-defined waypoints or performing certain aircraft navigation duties. In contrast, the status of a shipping container may be of low interest for weeks at a time but once the vessel comes within a certain range of port, the relevant timeframe may change to minutes. Lastly, the relevant timeframe for a valid passport may be ten years whereas a visa may only be valid for days or weeks. Time frame limits may be added to narrow the searches for predicted outcomes and/or correlated past events to a certain range around the current time that the model is being run. This may be desired in order to save time and/or processing power. Referring back to FIG. 11, the example template 1100 contains a time frame and location limitations data structure 1125 listing some exemplary uses of time and location limitations. In the example template 1100, the searches will be limited to Persons over 18 and present in the US as relevant to any analysis. However, with respect to Aircraft, the search is broadened to include any craft globally with the same model number. Finally, the search will consider any route flown from 1940 to the present in the U.S. to be of relevance. A timeframe guideline library 432 contains suggested time frame limitations for each data type and application area.
  • Fuzzy rules are selected or defined at step 414. Fuzzy rules may include chains of fuzzy variable membership functions combined with fuzzy logic operations including unions, intersections, and complements or combinations thereof. Fuzzy rules may also include modifiers (e.g., raising membership functions to a power to add a degree of correctness or incorrectness) that may be used to apply the weighting factors assigned in step 410. Referring back to FIG. 11, the template 1100 contains a rules definition data structure 1130 that lists rules sets (identified by rule numbers) for each variable and lists the associated Fuzzy Rules System and/or Application that the rule set numbers relate to. In this example, a Rule Library 434 presents a list of tools, each of which is linked to a series of pre-defined rule sets is used In the first instance, an application Zaptron FIDE that resides on system SuperSam3 is selected and Rule set 87 is used to identify anomalies in the FAA registration database. The rules selection process is continued for each variable or variables with as many rules as needed. A fuzzy rule library may contain guidelines to designing the fuzzy rules in step 414. In some embodiments, the fuzzy rule guidelines contained in the library 434 evolve or develop over time (e.g., during development of the system or during actual use of the system). The basics of fuzzy logic are known to those of skill in the art and will not be discussed in detail.
  • Similar to fuzzy logic base rules, analysis functions may be designed or defined at step 416. Analysis functions can include probability theory, Boolean logic, data mining and other types of correlative types of analysis functions. Analysis functions can include any of several analysis techniques known to those of skill in the art, such as:
  • Probability distribution for random variable X
  • Sampling distribution of the mean
  • Confidence interval estimation of the mean for (variable X)
  • Z test of hypothesis for the mean
  • t Test for the mean difference between (variable X and variable Y)
  • Autoregressive modeling for trend fitting and forecasting
  • Residual analysis for the multiple regression
  • The template 1100 contains an analytical process data structure 1135 that lists analytical processes selected for each variable and lists the specific analytical techniques and Systems and/or Applications to be used. In the example template 1100, a Function Library 436 presents a list of tools, each of which is linked to a series of pre-defined analytical analysis sets. In the first instance, a MatLAB7 tool that resides on system BigBlue7 comprising Bayes Function set 45A is selected to identify anomalies in the passenger manifest. The analysis function selection process is continued for each desired variable or variables with as many rules as needed. A function library, 436 contains suggested analysis functions. In some embodiments, the analysis guidelines contained in the library 436 evolve or develop over time (e.g., during development of the system or during actual use of the system).
  • At the completion of the design process 400, the application specific model (or script) is stored at step 418. The model can be stored in the model library 422 that also stored the template that was used to start the process 400. The model can be loaded from memory to be used by the designer or by other clients depending on the embodiments. It should be noted that any of the steps and/or libraries in FIG. 3 may be rearranged or combined with one or more other steps without changing the function of the process 400.
  • FIG. 4 is a flowchart illustrating certain steps in a process for performing a decision support process using an application specific model developed with the process of FIG. 3. Process 500 begins by importing an already designed decision support model, created using the process 400, from a model library 532. The model library 532 can be the same as the model library 422 of FIG. 3. The controller 220 of FIG. 2 can perform the importing of the application model. The controller 220 can also coordinate the flow of the process 500 to the other components of the server 200 that can be conducting some or all of the process 500 steps.
  • After importing the application model, the process 500 continues to step 504 where a correlation process is conducted. Typically, a current scenario 505 of the applicable variables is input to the process 500 in order to perform the correlation acts. The current scenario 505 can include values for each of the selected variables designed into the decision support model being executed (e.g., the variables selected at step 408 in the process 400). The current scenario 505 variables can be updated periodically using the real-time monitoring interface 222 and/or the external/non-conforming data sources component 240 of FIG. 2.
  • During the correlation process, the current scenario is correlated with previously obtained data contained in the various libraries/storage components such as, for example, a scenario library 534 and/or the historical data module 202 shown in FIG. 2. The data storage interface can retrieve the previously obtained data contained in the libraries and/or storage components. The correlation process preferably uses the weights assigned to each variable, at step 410 in the model design process 400, in calculating the correlations. This way the correlated historical scenarios will be skewed in the direction of the more important variables. Some models can be conducted without weights, or with all weights set to a default value such as one. “Complex Systems Modeling” (e.g., data mining) may be used to identify the correlations between the current scenario data obtained from the multiple disparate data sources and the historical data stored in the scenario library 534. The data mining components 232 of FIG. 2 can be used in performing the correlation tasks of step 504, e.g., using pattern recognition techniques.
  • In addition, or instead of, the correlative analysis performed at step 504, the process 500 can also conduct fuzzy logic rule processing at step 506 in identifying previously obtained chains of events that may relate to the current scenario 505. The fuzzy rules may be stored in a rule library 536. The fuzzy logic rules can enable the process 500 to identify inferences and/or implications in the historical chains of events and compare these chains of events to the current chain of events as exhibited by the current scenario 505. The fuzzy rules can be designed to reflect the variable weights assigned to the variables in step 410 of the process 400. The fuzzy inference engine 228 can conduct the fuzzy rule processing of step 506.
  • After identifying historical scenarios that correlate to or are indicated via fuzzy logic rules to relate to the current scenario chain of events, multiple analyses are conducted at step 508. Analyses can include statistical analyses, Bayesian analyses, and/or neural network analyses. A function library 538 contains stored analytical functions used at step 508. In some embodiments, the current scenario data can be analyzed to identify parameters or events that are outside of acceptable normal ranges. The current scenario variables can be compared to the accepted ranges (e.g., historical ranges, calculated ranges etc.) in order to identify outlying characteristics. The normal ranges for the variables in question can be stored in the historical ranges component 204 shown in FIG. 2. In addition to the accepted ranges method of identifying possible non-normal conditions, an expert information database, such as the expert info component 206 of FIG. 2, can be used to identify states that are judged to be unusual by experts of fields that are associated with the application model being executed in the current process. In some embodiments, the expert information database may indicate subjective data values corresponding to states such as “optimal”, “danger”, “recommended action or other states, that are indicative of the current scenario chain of events 505. These are some examples of the multiple analyses that can be conducted at step 508. Other forms of analyses known to those of skill in the art may also be conducted. The statistical analysis component 234 of FIG. 2 can perform the analyses at step 508.
  • Based on the multiple analyses performed at step 508, the process proceeds to step 510 where predictions are made as to what the next likely outcome or event will be. The multiple predictions can be made to fit a time limit determined by the step 412 of the process 400 where the time frame to be used in the application specific model was defined. The multiple analyses performed at step 508 can form the basis for predicting the most likely outcomes. In some embodiments, the most probable outcomes identified by the statistical, neural network, and/or fuzzy logic analyses of step 508 are used as the predictions at step 510. A prediction library 540 contains templates that specify one or more parameters and values, one or more formulae, and one or more predictions at specified time points along a projected vector. For example, in flight safety a historical template might read as follows: [PARAMETERS] SPEED: 600 mph; PITCH: 5 degrees; ALTITUDE: 5,000 FT [PREDICTION] EVENT: Imminent Crash; TIMEFRAME: 3 minutes, 20 seconds. In some embodiments, the severity of the outcome is contained in the prediction library 540. The severity of the outcome can be a subjective type of measure indicating the extremeness of an outcome, whether positive or negative. For example, an extremely positive outcome could be that the prediction analysis indicates that the user will win the lottery. An extremely negative outcome could be that the user can expect to lose 90% of his investments in the next year. The extremeness of the outcome can be considered when the recommended actions are determined at step 512 and the potential consequences determined at step 514, as discussed below. The statistical analysis component 234, the fuzzy inference engine 228 and/or information retrieved by the controller 220 (using the data storage interface 224) can perform the prediction acts of step 510.
  • At step 512, recommendations are identified based, at least in part, on their effect on the predicted outcome derived at step 510. Past scenarios that have been identified by the correlation step 504 and or the fuzzy rule processing step 506 can form the basis for making the recommended actions. The recommended actions may be a single action or multiple actions. The recommended actions may include doing nothing. The recommended actions may be made for the range of time selected at step 412 of the process 400. Preferably, the recommended actions are made in parallel with determining the potential outcomes or consequences at step 514. A recommendation library 542 contains a historical record of past recommended actions and subsequent results that are used to affect the recommendations. These historical recommended actions can be identified by links that were identified in the correlation process of step 504. Historical recommendations that resulted in both positive and negative outcomes can be included, preferably with negative outcomes causing a change in the historical recommendation and a positive outcome reinforcing the historical recommendation. The controller 220 can locate and retrieve the historical recommendations from the recommendation actions module 210 shown n FIG. 2. Using these historical recommendations, the controller 220 can make the one or more recommendations at step 512.
  • As discussed above in relation to making predictions at step 510 and making recommendations at step 512, the potential consequences as well as the severity of the consequences are determined at step 514 ( preferable steps 510, 512 and 514 are executed simultaneously such that the severity of the predicted outcomes affect the recommended actins). The consequences are stored in a consequence library 544. The consequences contained in the library 544 are linked to the severity measures discussed above in relation to making the predictions at step 510.
  • After determining the potential consequences (outcomes) at step 518, the recommended action/consequence results 518 are presented to the user in order to receive user input 520 as to which recommended action to take. The user can be presented the actions/consequences on the display of the client device (e.g., any of client devices 115 shown in FIG. 1). In some embodiments the user is given a choice to select automatic or manual selection of the recommended actions. If the user selects the automatic selection option, a decision block 516 will detect this selection and the process 500 will proceed to step 522 where the recommended action or actions are performed. In some embodiments, the user may be presented with a list of one or more historical scenarios including the recommended actions that were given, the tasks that were performed to carry out the recommended actions and the resulting outcomes. These historical recommended actions may not correspond to the current recommended actions, but are presented to the user so as to let the user observe what outcomes may lie ahead if he were not to perform the recommended actions.
  • The automatic selection of actions may choose the action(s) that result in a highest risk reward measurement. The risk reward measurement may qualitative measure (e.g., most happy, least injured, etc.) or a quantitative measure (e.g., highest rate of return on investment, lowest mortgage rate, etc.). The automatic selection may, in some embodiments choose the action that results in optimizing a user specified condition, such as, for example, fastest trip to a destination, lowest grocery bill satisfying nutritional needs and others.
  • If the user selects the manual selection of the recommended actions, then the user also inputs (user input 220) the recommended action. The decision block 516 then causes the process 500 to proceed to step 524 where the manual action is performed. It should be noted that the recommended actions made at step 512 that follow from predictions made at 510 and the tasks entailed in carrying out the recommended actions, at steps 522 or 524, are distinct from each other.
  • After the selection of the recommended action has taken place, either automatically or manually, the chosen recommended action is stored into the database. In some embodiments, the outcomes resulting from the tasks performed at steps 522 or 524 (the tasks performed to carry out the chosen recommended actions) are also stored at step 526 when the process 500 obtains them. The user may enter outcomes if they are not obtainable by the prediction support system itself. The server executing the process 500 may retrieve the outcome automatically using either the real-tome monitoring interface 222 or the input data translation component 226 shown in FIG. 2.
  • For actions that can be performed by the server executing the process 500, an action library 546 contains the necessary script commands to perform the tasks needed to carry out the chosen recommended actions. The script commands contain the necessary instructions to perform the needed task(s) whether it is performed at step 522 (automatic) or step 524 (manual).
  • It should be noted that selecting a recommended action to be performed may not actually cause the corresponding tasks to be performed. In a case where the client device or the server running the process 500 can perform the task, the task can be performed. However, if the recommended action requires the user to physically (or mentally) perform the task, then there is no guarantee that the user will actually perform it.
  • It should be noted that any of the steps and/or libraries in FIG. 4 may be rearranged or combined with one or more other steps without changing the function of the process 500. Steps 510, 512 and 514 for example can be combined in a way to determine recommended actions based on historical outcomes and the actions taken historically that led to those outcomes. One method of performing these steps starts by identifying a set of past scenarios or chains of events that closely relate to the current scenario 505 (e.g., scenarios identified by the weighted correlation process performed at step 504 and/or the fuzzy rule processing performed at step 506). The identified past scenarios can be stored as chain of event templates, where the chain of event templates each include the historical values of the variables defining the scenario, the action that was taken and the resulting outcome. In one example, the recommended action can be determined by choosing the historic action that led to a desired or most favorable outcome most often. In another example, fuzzy logic can be used to combine multiple actions taken with the desirability of the resulting outcome where the fuzzy logic algorithms provide weighting to the desirability and the type of actions taken. The chain of event templates may also include the action that was recommended (if the scenarios were using the decision support process) in order for the process 500 to be able to identify cases where the recommended action does not correspond to the action that was taken. This may avoid false feedback where a recommended action was ignored and a negative outcome resulted.
  • New chain of event templates are created when no past chain of event scenarios match the current scenario 505. Existing chain of event templates can also evolve to be substantially different from when they were first created. This can be the result of parameters outside of the control of the user or the process 500 evolving to create a substantially different set of rules that control the chain of events scenarios that are represented by the templates.
  • In some embodiments, the application models developed using the process 400 and executed with the process 500 can be structured to resemble a goal-seeking system that begins the process by querying the user for the desired outcome. The process then obtains the values of the variables in the current scenario 505 and compares those values to the variables consistent with the values of the desired outcome. The process 500 described above then seeks to find scenarios (chains of events) that will identify actions to be taken to transition the current scenario toward the desired scenario. There will typically be multiple paths to get to the desired result. The application model can query the user on how he would prefer to get to the goal. The goal can be achieved while optimizing certain characteristics or variables of the application specific model. For example, in an investment application, the goal may be to double the value of an investment in 5 years. The decision support process can identify multiple recommended actions (e.g., investing in highly aggressive or conservative investments) that are chosen to minimize risk, maximize gain, provide less than a certain threshold chance of losing all of the initial investment. In some embodiments, the goal can be open-ended or indefinite. The goal may be to optimize a subjective quality. For example, the goal may be to arrive at a destination in the fastest time, in the least dangerous fashion, in the most comfort, etc. In these situations, fuzzy logic may be used to identify the chain of events that best meet the chances of arriving at the desired destination while optimizing the subjective quality.
  • Special consideration to a person's privacy (or other private information such as top secret materials) may be a desirable feature for some applications of the decision control process 500. For example, a person's private information can be stored such that the private and/or sensitive information is made available for analysis and identification of correlated scenarios that match a current scenario, but at the same time keep the person's identity separated from the private and/or sensitive information. FIG. 9 is a flowchart illustrating certain steps in a process for parsing private information and storing it in segregated databases, where the databases can be accessed in an anonymous mode to retain personal privacy, or accessed in an authorized mode that reconstructs the private information including the personal identity.
  • The process 900 obtains private records 905 containing a personal identity and information concerning various facts about the person. The information may include sensitive or private information that a person has the right to keep private unless mitigating circumstances exist. Sensitive information may include financial information, criminal records, a record of associations or acquaintances, social security number etc. The information by itself is not an issue. It is only when the information is linked with an identity of an individual that privacy becomes a concern. For this reason, when private information is imported to the decision support system (e.g., retrieved by the real-time monitoring interface component 222 and or the import data translation component 226 of the server 105 shown in FIG. 2), a private import process 910 is performed. The private import process 910 starts by parsing the incoming data. The data is parsed to a level needed to keep the identity separate from sensitive or private information. A unique code is assigned to link the identity to the parsed information. Identities and codes may be stored in separate, secure databases with restricted access. True identities are only revealed where special conditions are met, such as securing a warrant. Warrants may be represented as electronic keys to streamline automated processing without compromising security. After parsing, the information is stored into any of several separated databases such as the databases 915A, 915B and 915C. The databases 915A to 915C can be stored on any kind of memory device such as hard drives, CD-ROM, magnetic tape, etc. The information is stored in a data structure that links the unique code with the information.
  • The information in the individual databases can be retrieved (e.g., in order to perform correlative analysis, making predicted outcomes, making recommendation of the process 500) separately by proceeding to block 920. The separate databases do not contain enough information to link the person with the individual facts or events. Data from multiple databases may be combined in a restricted way such that the chains of events used in the decision support process 500 can be identified without connecting a personal identity to the chain of events. This allows the data-mining or exportation of anonymous data.
  • In certain critical situations, such as when a person's safety is involved, or in cases where a criminal act has been committed, the reconstruction of the private records 905 may be permitted. Such a situation is similar to the issue of a warrant or a subpoena. An electronic warrant key is used to authorize, authenticate and/or permit decryption of information (e.g., access codes or cryptographic keys) to allow reconstruction of the private record for which the authorization was granted 905. The authorization/authentication act is typically a recorded transaction that is kept in a secure database for purposes of providing an audit trail. When the electronic warrant 930 is obtained, the process performs step 925 where authentication of the warrant 930 is performed and the subsequent reconstruction results in reconstructed records 935. Step 925 is able to access multiple data bases as well as link the data in each database to the identification of the person that it is linked to. Obtaining the reconstructed records 925 that include the personal identity variable enables the use of the identity of the person as a variable in the decision support process 500. It should be noted that any of the steps and/or libraries in FIG. 9 may be rearranged or combined with one or more other steps without changing the function of the process 900. While the process 900 was described in relation to parsing information to keep the information separate from a person's identity, those of skill in the art will recognize that other forms of sensitive information can be protected in a similar manner. For example, the authorization warrant methodology can also be used to restrict access to other forms of private information. For example, governmental top secret information may be accessed only by authorized individuals. Similar protection may be afforded sensitive information such as company trade secrets, secret negotiations, etc.
  • FIG. 10 is a flowchart illustrating certain steps in a process for obtaining information for use in the decision support process. The process 1000 can be performed by the server based system 200 shown in FIG. 2. Preferably, any information that is retrieved by the system 200 performs all of the steps shown in the process 1000. However, some steps may be omitted without changing the function of the process 1000. The information may be retrieved by the real-time monitoring interface component 222 and/or the import data transaction component 226. The process 1000 starts with an authentication process 1005. The authentication process verifies the source of the retrieved information. The authentication process confirms that the received data is unchanged from what the source transmitted and it also confirms the identity of the source. In some embodiments, the sender uses a one-way hash function to generate a digital signature from the transmitted data. The sender then encrypts the hash-code with a private key. The receiver (e.g. the server based system 200) then recalculates the digital signature from the data and decrypts the received digital signature with the sender's public key. If the two digital signatures are equal, the receiver can be confident that data has not been corrupted and that it came from the given sender. The integrity services module 242 may perform the authentication at step 1005.
  • By proceeding to decision block 1010, the process 1000 checks if the authentication was successful. If the authentication was not successful, the process 1000 is aborted and the retrieved information may be discarded. The retrieved information may also be retained to be used later.
  • If the authentication was successful, the decision block 1010 directs the process 1000 to proceed to a decryption process 1015. The decryption process 1015 decrypts the information. The integrity of the decrypted data is typically verified through the use of checksums (e.g., cyclic redundancy checks). If portions of the decrypted data are determined to be erroneous, decision block 1020 will determine that the decryption was unsuccessful for that portion of data and abort the process (discard the erroneous portions of data) as it pertains to the erroneous data. The integrity services module 222 may perform the decryption at step 1015.
  • After successful decryption of the information, the decision block 1020 directs the process 1000 to a decompression process 1025. Any of the various compression/decompression algorithms can be used to compress information depending on the type of media that is being compressed. If decompression is unsuccessful, the decision block 1030 causes the process 1000 to be aborted, at least for the portion of information that was unsuccessfully decompressed. The integrity services module 222 may perform the decompression at step 1025.
  • After successful decompression of the information, the process 1000 proceeds to a filtering process 1035. The filtering process can perform the reformatting tasks discussed above in relation to the import data translation module 226. The data is filtered so as to conform to the format desired by the decision support system 200. If the filtering at step 1035 is determined, at decision block 1040, to be unsuccessful in translating the information into a conformal format, then the process 1000 is aborted, at least for the portion of information that was not successfully filtered.
  • After successful filtering of the information, the process 1000 proceeds to step 1045 where the privacy process 900 shown in FIG. 9 is performed. The privacy process 1045 can be performed in at least two exemplary ways. In one example, the privacy process 1045 is used to reconstruct the private information (see the reconstructed records 935 in FIG. 9) retrieved from the already parsed databases (e.g., the databases 915A, 915B and 915C). In this case, decision block 1050 checks to see if the proper authorization warrant 930 is available. If the authorization warrant 930 is not available, the decision block 1050 aborts the process 1000 as it relates to obtaining the reconstructed records 935. If the private information is determined to be authorized to be obtained, then the decision block 1050 directs the process 1000 to a parsing process 1055. In a second example, the privacy process 1045 is used to determine if there is private information contained in the retrieved information that needs to be parsed before the data is stored for use in the decision support system. In this case, the decision block 1050 determines if the private information (e.g., personal identity information) has been identified (e.g., flagged) to be parsed into the secure personal identification/unique code database that was discussed above in relation to FIG. 9. This way the parsing process 1055 can recognize that there is personal identity information present and the unique code can be linked to the parsed information to separate the information from the personal identity. If the personal identity information is properly identified, then the process 1000 proceeds to the parsing process 1055.
  • The parsing process 1055 performs parsing of the received information into the various variables that are used to identify related chains of events in the process 500 discussed above. At step 1060, the parsed information is then linked to classifications of the data structure to be used for the decision support process. The linking can be in the form of cross references to the various application specific model templates that the information may be relevant to. The linking can be in the form of cross references to the individual chain of events templates used in determining the predicted outcomes and the recommended actions of the process 500. The linking can also be in the form of cross references to the various libraries used in the process 400 for developing the application specific models.
  • After linking the parsed information, the process 100 proceeds to step 1065, where the information is stored in to the multidimensional data structure to be used in the processes discussed above. It should be noted that any of the steps in FIG. 10 may be rearranged or combined with one or more other steps without changing the function of the process 1000.
  • An exemplary use of some of the features of the decision support system discussed above will now be described. This example describes a scenario for monitoring a shipping container. History of accident or disaster investigation has shown us that connections between seemingly unrelated or insignificant events play a major part in the failure of the entire safety system. One such example of the nature of humans to mistake very vital clues and relationships of key factors in a disaster was the crash of Alaska Airlines flight 261 Jan. 31, 2000 that killed all 88 people aboard the aircraft.
  • The initial investigation of the flight records and aircraft wreckage showed significant signs pointing to mechanical failure. Specifically, the National Transportation Safety Board concluded that a flight control system inside the horizontal stabilizer called a jackscrew and gimbal nut assembly failed during flight in the tail of the MD-83. Analysts concluded that the jackscrew had torn through the badly worn nut causing the horizontal stabilizer, the flight control that regulates the pitch of the nose, had jammed in the full nose down position causing the aircraft to dive into the ocean.
  • More than six years after the accident there has still not been advances in the sensor technology on aircraft that would have warned the pilots that the jackscrew would be under enough stress to strip the gimbal nut assembly causing a catastrophic failure.
  • Conversely, over the same six year period, data gathering, data mining, decision tree analysis, neural networks, and threat mitigation algorithms have enjoyed great increases in sophistication. This path of continued improvement has lead to the present invention. The following is an example of how the present invention would have illustrated the full extent of the risk associated with flight 261 and how the flight crew and public would have been presented with the risks involved with Alaska Airlines as a corporation, and with the entire US airline industry at the time.
  • Jan. 31st, 2000 0900-PST
  • The pilot arrives at the aircraft to perform the routine preflight checks of the aircraft. As the system powers up, the Trusted Decision Support System has pre-assigned the subject being analyzed as aircraft safety of flight. The decision support system references the model library and selects the script designated for the aviation safety model.
  • The model for aviation safety identifies areas specific to aviation safety that must be analyzed by the system. For example, one aspect of the model instructs the system to reference the FAA Airmen Certification Database using the pilot information for the crew assigned to flight 261. The airmen certificate number, the pilot name, and the airline employee identification number are used to research the pilot flight test records, the pilot citation records, pilot citation records, pilot training records, pilot conduct records, and pilot performance records, aircraft flown records, and type rating records. The decision support system then references the scenario library while conducting a correlation process between the information in the library and the information provided about the flight crew. The rule library is referenced for allowable parameter values and a customized set of rules regarding the flight crew is established for the flight. The value of parameters are evaluated against the fuzzy rule set to determine if any value is outside the established allowable values. For example, rules for this flight based on the historical values given from the scenario library dictate that the crew must have 10 hours of off duty rest period between block times in the aircraft. The pilot information database confirms 11.5 hours between the aircraft shut down, the crew arrival, and aircraft restart. This variable would be evaluated as a non-anomaly based on it falling within the parameters allowed by the established rule set.
  • The process of establishing rule sets and evaluating parameter values is performed throughout all the requirements of the aviation safety model.
  • The aviation safety model used in this scenario calls for the maintenance records of the specific MD-83 aircraft scheduled for flight 261 to be referenced. The rule library for this scenario dictates that the variable may not have any instances of required maintenance work going undone. The referenced maintenance records indicate that in September 1997 mechanics at the Alaska Airlines Oakland maintenance facility discovered that the gimbal nut on the horizontal stabilizer was “badly worn and in dire need of replacement.” The same maintenance records showed that Alaska Airlines ordered additional tests on the assembly and deemed it airworthy with no maintenance action required. The rule set for this scenario calls for no deviations from required maintenance actions. This event would be flagged as negatively effecting the safety of flight for this aircraft
  • Data collected from grand jury investigations showed that Alaska Airlines had allowed more that 840 flights by two MD-80 series jetliners “in an unairworthy condition” between October 1998 and January 1999. The rule set for the Aviation Safety model states that no unairworthy aircraft are permitted to fly at any time. The information from the investigation would be flagged by the system as negatively effecting the safety of flight.
  • According to the aviation safety model, records from the FBI would be referenced in the correlation and data gathering process. The FBI records show that in December of 1998 the Alaska Airlines Corporate headquarters in Seattle were raided based on charges filed by the President of the Local Machinists Union and senior aircraft mechanic John Liotine that “supervisors and mechanics were signing off work that they were either unqualified to do, or had not performed, so that planes could be put back into service as soon as possible.” The rules for this variable state that any investigation by the FBI as well as any accusations by current or former employees are labeled as a negative influence on the safety of flight.
  • In February 1999 the FAA database for airline citations shows that Alaska Airlines allowed aircraft to fly despite falsified maintenance checks that included work by an Alaska Airlines supervisor who was not qualified to perform such work. According to the rules for this variable, one airline citation is outside the allowable value range for the variable. This variable would be flagged as negatively effecting the safety of flight.
  • The system references a function library to conduct multiple levels of analysis regarding the information provided in the correlation process and the variable rule processing stages.
  • The system references a prediction library to base probabilities of event occurrence based on current variable values. The system references the time when the pilot activates the electrical system of the aircraft as the starting point to reference the flight timeline against. All predictions made for this flight from the prediction library are linked to a predicted time of occurrence related to this timeline.
  • Jan. 31, 2001 0901-PST
  • Each event is linked to a list of consequences related to that recommendation via the consequence library.
  • Jan. 31, 2001 0902-PST
  • The pilot is presented a score based on the risk factors for the flight, and given a list of events and their corresponding probability score. Each event listed is given a time of occurrence and is linked to a list of recommendations from the recommendation library.
  • Jan. 31, 2001 0903-PST
  • The crew is presented with a list of actions, both manual and automatic for them to choose from to lessen the risk associated with this flight.
  • Jan. 31, 2001 0915-PST
  • The crew has performed all actions listed on the actions page and permitted the automated systems to perform all available actions automatically.
  • Jan. 31, 2001 0916-PST
  • The actions of the crew, and the results of the actions are stored in the database for the flight and the process is reset automatically updating with each change in any observed variable in the aviation safety model.
  • Had the flight crew seen the risk report and list of probable failures and the likelihood of those failures occurring, they may not have chosen to make the flight. However, for the example, it is assumed that the flight has occurred.
  • Inside the flight deck the system constantly updates the information provided by the prediction system, along with readings from the avionics systems aboard the aircraft. Current conditions and flight system information is run through the fuzzy rule process based on information from the rule library. Each variable is assessed through the fuzzy rule set to determine whether its value falls within the allowable parameter value limits. For example, the control pressure for pitch attitude has a limit of 100 pounds of force required at the control input end to manipulate the control. The system was on autopilot, so no control input should have been taking place. However, due to the malfunction of the pitch attitude control mechanism, constant input from the trim system was required to maintain aircraft attitude.
  • Jan. 31, 2001 1230-PST
  • The pitch trim force required variable observed to be within the allowable fuzzy rule parameters. The analysis of the system, and the prediction process show that according to the current patterns, the pitch trim force required to maintain level flight will exceed the allowable parameter value limits in one hour and 45 minutes of flight.
  • Jan. 31, 2001 1231-PST
  • The system determines the recommended actions according to the timeline established by the prediction process. The consequence library is used to determine potential consequences for each action performed by the crew, automated systems, and failures of systems and their interdependent systems.
  • Jan. 31, 2001 1232-PST
  • The crew is alerted about the results of the process and prompted to acknowledge the severity of the consequences of the predicted system failures. Both manual and automatic actions are performed to mitigate the risks associated with the failure.
  • Jan. 31, 2001 1232-PST
  • The FAA, emergency crews at the nearest airports, search and rescue personnel, aircraft experts, airline emergency maintenance personnel, and airline crisis management teams are all notified of the situation. Each entity is updated with complete information automatically relayed to and from the aircraft. The timeline for failure is constantly updated with each action taken by the flight and ground crews.
  • The system has alerted the pilots and all appropriate parties of the impending failure and its consequences 1:56 minutes prior to the actual point of failure. Based on the actions recommended by the decision support system, the crew is able to adjust the flight controls on the aircraft to minimize the forces acting upon the horizontal stabilizer. Furthermore, the aircraft is diverted to the nearest location, landing safely in San Diego, 42 minutes prior to the point of failure.
  • While the above detailed description has shown, described, and pointed out novel features of the invention as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the spirit of the invention. As will be recognized, the present invention may be embodied within a form that does not provide all of the features and benefits set forth herein, as some features may be used or practiced separately from others.

Claims (19)

1. A system comprising:
an electronic device configured to select a data set for an application area, to assign weighted scores to the data in the data set, to correlate the weighted data set with one or more previously correlated weighted data sets, and to determine, based upon the correlation, a recommended action as a response to an event related to the data set.
2. The system of claim 1, further comprising a statistical analysis engine configured to perform statistical analysis on the data set.
3. The system of claim 1, further comprising a statistical analyses engine configured to be programmed with one or more models, wherein each model comprises mathematical instructions for processing the data set.
4. The system of claim 3, wherein the mathematical instructions comprise weights to be assigned to the data set according to at least one of a source from which the data set was received and an age of the data set.
5. The system of claim 3, wherein the mathematical instructions comprise at least one of fuzzy logic instructions, Bayesian analyses instructions, neural network analyses instructions, probability calculation instructions, mean calculation instructions, confidence interval calculation instructions, Z-test instructions, T-test instructions, autoregressive modeling instructions, and residual analysis instructions for multiple regression.
6. A system comprising:
a sensor network;
a database comprising data from the sensor network; and
a electronic device configured to select a data set from the database for an application area, to assign weighted scores to the data in the data set, to correlate the weighted data set with one or more previously correlated weighted data sets, and to determine, based upon the correlation, a recommended action as a response to an event related to the data set.
7. The system of claim 6, further comprising a statistical analysis engine configured to perform statistical analysis on the data set.
8. The system of claim 6, further comprising a statistical analyses engine configured to be programmed with one or more models, wherein each model comprises mathematical instructions for processing the data set.
9. The system of claim 8, wherein the mathematical instructions comprise weights to be assigned to the data set according to at least one of a source from which the data set was received and an age of the data set.
10. The system of claim 8, wherein the mathematical instructions comprise at least one of fuzzy logic instructions, Bayesian analyses instructions, neural network analyses instructions, probability calculation instructions, mean calculation instructions, confidence interval calculation instructions, Z-test instructions, T-test instructions, autoregressive modeling instructions, and residual analysis instructions for multiple regression.
11. A system comprising:
an electronic device configured to select a data set for an application area, the electronic device further configured to analyze the data set according to fuzzy logic instructions so as to generate a recommended action and outcome information for the recommended action.
12. The system of claim 11, further comprising a statistical analysis engine configured to perform statistical analysis on the data set.
13. The system of claim 11, further comprising a statistical analyses engine configured to be programmed with one or more models, wherein each model comprises mathematical instructions for processing the data set.
14. The system of claim 13, wherein the mathematical instructions comprise weights to be assigned to the data set according to at least one of a source from which the data set was received and an age of the data set.
15. The system of claim 13, wherein the mathematical instructions comprise at least one of fuzzy logic instructions, Bayesian analyses instructions, neural network analyses instructions, probability calculation instructions, mean calculation instructions, confidence interval calculation instructions, Z-test instructions, T-test instructions, autoregressive modeling instructions, and residual analysis instructions for multiple regression.
16. A system comprising:
an electronic device configured to select a data set for an application area, the electronic device further configured to analyze the data set according to statistical analysis instructions so as to generate a recommended action and outcome information for the recommended action.
17. The system of claim 16, further comprising a statistical analyses engine configured to be programmed with one or more models, wherein each model comprises mathematical instructions for processing the data set.
18. The system of claim 17, wherein the mathematical instructions comprise weights to be assigned to the data set according to at least one of a source from which the data set was received and an age of the data set.
19. The system of claim 17, wherein the mathematical instructions comprise at least one of fuzzy logic instructions, Bayesian analyses instructions, neural network analyses instructions, probability calculation instructions, mean calculation instructions, confidence interval calculation instructions, Z-test instructions, T-test instructions, autoregressive modeling instructions, and residual analysis instructions for multiple regression.
US11/418,382 2005-05-03 2006-05-03 Trusted decision support system and method Abandoned US20070011106A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/418,382 US20070011106A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US67716405P 2005-05-03 2005-05-03
US73553905P 2005-11-10 2005-11-10
US11/418,382 US20070011106A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method

Publications (1)

Publication Number Publication Date
US20070011106A1 true US20070011106A1 (en) 2007-01-11

Family

ID=36764587

Family Applications (24)

Application Number Title Priority Date Filing Date
US11/418,472 Abandoned US20060291657A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,448 Active - Reinstated 2026-06-30 US7526455B2 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/418,447 Abandoned US20070022079A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/417,893 Abandoned US20070011105A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/418,382 Abandoned US20070011106A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/417,910 Abandoned US20070182544A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,496 Abandoned US20070002140A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,385 Abandoned US20070008410A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,381 Active US7609159B2 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,395 Abandoned US20070011107A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/417,887 Active 2026-11-24 US7512583B2 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/418,380 Active 2028-06-29 US7656286B2 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US12/431,656 Abandoned US20090210378A1 (en) 2005-05-03 2009-04-28 Trusted decision support system and method
US12/641,139 Abandoned US20100090822A1 (en) 2005-05-03 2009-12-17 Trusted monitoring system and method
US13/399,249 Active US8515895B2 (en) 2005-05-03 2012-02-17 Trusted decision support system and method
US13/724,942 Active US8830053B2 (en) 2005-05-03 2012-12-21 Trusted monitoring system and method
US13/970,514 Abandoned US20140058990A1 (en) 2005-05-03 2013-08-19 Trusted decision support system and method
US14/480,362 Abandoned US20160019384A1 (en) 2005-05-03 2014-09-08 Trusted monitoring system and method
US15/265,551 Abandoned US20170004407A1 (en) 2005-05-03 2016-09-14 Trusted decision support system and method
US15/287,464 Active US10504349B2 (en) 2005-05-03 2016-10-06 Trusted monitoring system and method
US16/706,445 Abandoned US20200118405A1 (en) 2005-05-03 2019-12-06 Trusted monitoring system and method
US16/874,493 Abandoned US20200273304A1 (en) 2005-05-03 2020-05-14 Trusted decision support system and method
US17/447,389 Abandoned US20220237997A1 (en) 2005-05-03 2021-09-10 Trusted monitoring system and method
US18/150,495 Pending US20230401945A1 (en) 2005-05-03 2023-01-05 Trusted decision support system and method

Family Applications Before (4)

Application Number Title Priority Date Filing Date
US11/418,472 Abandoned US20060291657A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,448 Active - Reinstated 2026-06-30 US7526455B2 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/418,447 Abandoned US20070022079A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/417,893 Abandoned US20070011105A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method

Family Applications After (19)

Application Number Title Priority Date Filing Date
US11/417,910 Abandoned US20070182544A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,496 Abandoned US20070002140A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,385 Abandoned US20070008410A1 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,381 Active US7609159B2 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US11/418,395 Abandoned US20070011107A1 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/417,887 Active 2026-11-24 US7512583B2 (en) 2005-05-03 2006-05-03 Trusted decision support system and method
US11/418,380 Active 2028-06-29 US7656286B2 (en) 2005-05-03 2006-05-03 Trusted monitoring system and method
US12/431,656 Abandoned US20090210378A1 (en) 2005-05-03 2009-04-28 Trusted decision support system and method
US12/641,139 Abandoned US20100090822A1 (en) 2005-05-03 2009-12-17 Trusted monitoring system and method
US13/399,249 Active US8515895B2 (en) 2005-05-03 2012-02-17 Trusted decision support system and method
US13/724,942 Active US8830053B2 (en) 2005-05-03 2012-12-21 Trusted monitoring system and method
US13/970,514 Abandoned US20140058990A1 (en) 2005-05-03 2013-08-19 Trusted decision support system and method
US14/480,362 Abandoned US20160019384A1 (en) 2005-05-03 2014-09-08 Trusted monitoring system and method
US15/265,551 Abandoned US20170004407A1 (en) 2005-05-03 2016-09-14 Trusted decision support system and method
US15/287,464 Active US10504349B2 (en) 2005-05-03 2016-10-06 Trusted monitoring system and method
US16/706,445 Abandoned US20200118405A1 (en) 2005-05-03 2019-12-06 Trusted monitoring system and method
US16/874,493 Abandoned US20200273304A1 (en) 2005-05-03 2020-05-14 Trusted decision support system and method
US17/447,389 Abandoned US20220237997A1 (en) 2005-05-03 2021-09-10 Trusted monitoring system and method
US18/150,495 Pending US20230401945A1 (en) 2005-05-03 2023-01-05 Trusted decision support system and method

Country Status (2)

Country Link
US (24) US20060291657A1 (en)
WO (2) WO2006119323A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8781987B1 (en) * 2012-12-31 2014-07-15 Gary Stephen Shuster Decision making using algorithmic or programmatic analysis

Families Citing this family (301)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6636733B1 (en) 1997-09-19 2003-10-21 Thompson Trust Wireless messaging method
GB2387912A (en) * 2002-04-26 2003-10-29 Messier Dowty Inc Monitoring parameters in structural components
DE10328906A1 (en) * 2003-06-26 2005-01-13 Endress + Hauser Process Solutions Ag field bus
US7619512B2 (en) 2006-10-02 2009-11-17 Alarm.Com System and method for alarm signaling during alarm system destruction
US7265668B1 (en) * 2003-12-12 2007-09-04 Skybitz, Inc. System and method for asset tracking and monitoring
CN1833253B (en) * 2004-06-04 2010-09-01 三菱电机株式会社 Certificate issuance server and certification system for certifying operating environment
US20060291657A1 (en) 2005-05-03 2006-12-28 Greg Benson Trusted monitoring system and method
US20060288207A1 (en) * 2005-06-17 2006-12-21 Research In Motion Limited Encoding messages for use in a communication system based on classificaiton status
US7978067B2 (en) * 2005-06-22 2011-07-12 Custom Metalcraft, Inc. Intelligent container
US7953536B2 (en) * 2005-07-29 2011-05-31 GM Global Technology Operations LLC Inertial sensor software architecture security method
AU2006287503B2 (en) * 2005-09-06 2011-04-07 Infraegis, Inc. Threat detection and monitoring apparatus with integrated display system
WO2007115341A2 (en) * 2005-10-04 2007-10-11 Roderick Mark Dyson Transaction management system
CA2625907A1 (en) * 2005-10-12 2007-04-19 First Data Corporation System and method for authorizing electronic payment transactions
US9411969B2 (en) * 2005-11-25 2016-08-09 Continuity Software Ltd. System and method of assessing data protection status of data protection resources
IL172289A (en) * 2005-11-30 2011-07-31 Rafael Advanced Defense Sys Limited bandwidth surveillance system and method with rotation among monitors
TW200732980A (en) * 2006-02-21 2007-09-01 Guo Yuan Heng Intelligent display control device, system and operation method for the same
US20070200701A1 (en) * 2006-02-27 2007-08-30 English Kent L Network centric sensor fusion for shipping container security
US20070294360A1 (en) * 2006-06-15 2007-12-20 International Business Machines Corporation Method and apparatus for localized adaptation of client devices based on correlation or learning at remote server
EP1870806A1 (en) * 2006-06-19 2007-12-26 Wolfgang Pree GmbH System for executing distributed sofware
US7714719B2 (en) * 2006-06-27 2010-05-11 Qualcomm Incorporated Field disturbance sensor utilizing leaky or radiating coaxial cable for a conformable antenna pattern
US20080020724A1 (en) * 2006-07-19 2008-01-24 John Robert Orrell Establishing a data link between stacked cargo containers
US7940933B2 (en) * 2006-08-18 2011-05-10 Medtronic, Inc. Secure telemetric link
US7930543B2 (en) * 2006-08-18 2011-04-19 Medtronic, Inc. Secure telemetric link
US8102999B2 (en) * 2006-08-18 2012-01-24 Medtronic, Inc. Secure telemetric link
SG143084A1 (en) * 2006-11-17 2008-06-27 Nanyang Polytechnic Software copyright protection and licensing system using rfid
US7916022B2 (en) * 2006-11-21 2011-03-29 Deere & Company Agricultural information gathering system
FI20065766A0 (en) * 2006-11-30 2006-11-30 Ekahau Oy Techniques to improve the reliability of the forecasting system
JP2008140095A (en) * 2006-12-01 2008-06-19 Hitachi Ltd Decision-making support system
US8116748B2 (en) 2006-12-14 2012-02-14 At&T Intellectual Property I, Lp Management of locations of group members via mobile communications devices
US8566602B2 (en) * 2006-12-15 2013-10-22 At&T Intellectual Property I, L.P. Device, system and method for recording personal encounter history
US7646297B2 (en) 2006-12-15 2010-01-12 At&T Intellectual Property I, L.P. Context-detected auto-mode switching
US8160548B2 (en) * 2006-12-15 2012-04-17 At&T Intellectual Property I, Lp Distributed access control and authentication
US20080146250A1 (en) * 2006-12-15 2008-06-19 Jeffrey Aaron Method and System for Creating and Using a Location Safety Indicator
US8199003B2 (en) * 2007-01-30 2012-06-12 At&T Intellectual Property I, Lp Devices and methods for detecting environmental circumstances and responding with designated communication actions
US7788200B2 (en) * 2007-02-02 2010-08-31 Microsoft Corporation Goal seeking using predictive analytics
US8009050B2 (en) * 2007-02-02 2011-08-30 Semiconductor Energy Laboratory Co., Ltd. Wireless system, semiconductor device, and communication device
EP1956523B1 (en) * 2007-02-02 2013-05-29 Semiconductor Energy Laboratory Co., Ltd. Wireless identification system, semiconductor device, and communication device
US7855005B2 (en) * 2007-02-12 2010-12-21 Deeya Energy, Inc. Apparatus and methods of determination of state of charge in a redox flow battery
DE102007009023B4 (en) * 2007-02-23 2011-12-22 Siemens Ag Device and method for providing RFID identification data for an authentication server
US7696869B2 (en) * 2007-04-05 2010-04-13 Health Hero Network, Inc. Interactive programmable container security and compliance system
US20080270473A1 (en) * 2007-04-30 2008-10-30 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Determining an influence on a person by web pages
US8290973B2 (en) * 2007-04-30 2012-10-16 The Invention Science Fund I, Llc Determining influencers
US20080270551A1 (en) * 2007-04-30 2008-10-30 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Rewarding influencers
US8793155B2 (en) * 2007-04-30 2014-07-29 The Invention Science Fund I, Llc Collecting influence information
US8712837B2 (en) * 2007-04-30 2014-04-29 The Invention Science Fund I, Llc Rewarding independent influencers
US20080270620A1 (en) * 2007-04-30 2008-10-30 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Reporting influence on a person by network-available content
US20080270552A1 (en) * 2007-04-30 2008-10-30 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Determining influencers
US9135657B2 (en) * 2007-07-27 2015-09-15 The Invention Science Fund I, Llc Rewarding independent influencers
US20080270474A1 (en) * 2007-04-30 2008-10-30 Searete Llc Collecting influence information
WO2008144550A1 (en) * 2007-05-17 2008-11-27 Law Enforcement Support Agency System and method for remote surveillance
US20090077156A1 (en) * 2007-09-14 2009-03-19 Srinivas Raghav Kashyap Efficient constraint monitoring using adaptive thresholds
GB0712981D0 (en) * 2007-07-05 2007-08-15 Ibm an apparatus for establishing trust in data associated with a data processing system
US8335504B2 (en) * 2007-08-23 2012-12-18 At&T Intellectual Property I, Lp Methods, devices and computer readable media for providing quality of service indicators
US8799103B1 (en) 2007-09-20 2014-08-05 Ariba, Inc. Client-side structured data capture and remote application integration using a web browser
US20090102659A1 (en) * 2007-09-24 2009-04-23 Savi Technology, Inc. Method and Apparatus for Tracking and Monitoring Containers
DE102007050708B4 (en) * 2007-10-22 2009-08-06 Phoenix Contact Gmbh & Co. Kg System for operating at least one non-safety-critical and at least one safety-critical process
EP2065849A1 (en) * 2007-11-30 2009-06-03 Sap Ag Detection of counterfeited products based on sensor measurements
US7786858B2 (en) * 2007-12-07 2010-08-31 Honeywell International Inc. Video-enabled rapid response system and method
US8136095B2 (en) * 2007-12-19 2012-03-13 Microsoft Corporation Relations in fuzzing data
US20100287083A1 (en) * 2007-12-28 2010-11-11 Mastercard International, Inc. Detecting modifications to financial terminals
US7895131B2 (en) * 2008-01-04 2011-02-22 Tracking Innovations, Inc. Cargo tracking apparatus, system and method
WO2009105719A2 (en) * 2008-02-20 2009-08-27 Icontrol, Inc. Methods for remote device status determination
US8587150B2 (en) * 2008-02-28 2013-11-19 Deeya Energy, Inc. Method and modular system for charging a battery
US8977843B2 (en) * 2008-05-30 2015-03-10 The Boeing Company Geolocating network nodes in attenuated environments for cyber and network security applications
US8769267B2 (en) * 2008-05-30 2014-07-01 The Boeing Company Geothentication based on new network packet structure
US20100013496A1 (en) * 2008-06-23 2010-01-21 Jay R. Goetz Branch circuit black box
US7927731B2 (en) * 2008-07-01 2011-04-19 Deeya Energy, Inc. Redox flow cell
US8854205B2 (en) * 2008-07-18 2014-10-07 The F3M3 Companies, Inc. System and method for countering terrorism by monitoring containers over international seas
JP5200725B2 (en) * 2008-07-18 2013-06-05 株式会社リコー Electronic device regeneration support system
US8883297B2 (en) * 2008-10-10 2014-11-11 Imergy Power Systems, Inc. Methods for bonding porous flexible membranes using solvent
EP2351184A4 (en) * 2008-10-10 2014-07-09 Deeya Energy Technologies Inc Method and apparatus for determining state of charge of a battery
WO2010042895A1 (en) * 2008-10-10 2010-04-15 Deeya Energy Technologies, Inc. Thermal control of a flow cell battery
US8230736B2 (en) * 2008-10-10 2012-07-31 Deeya Energy, Inc. Level sensor for conductive liquids
WO2010040413A1 (en) * 2008-10-10 2010-04-15 Telefonaktiebolaget Lm Ericsson (Publ) Lawful authorities warrant management
WO2010042899A1 (en) * 2008-10-10 2010-04-15 Deeya Energy Technology, Inc. Flexible multi-walled tubing assembly
US8236463B2 (en) * 2008-10-10 2012-08-07 Deeya Energy, Inc. Magnetic current collector
US20100092843A1 (en) * 2008-10-10 2010-04-15 Deeya Energy Technologies, Inc. Venturi pumping system in a hydrogen gas circulation of a flow battery
US9691114B2 (en) * 2008-10-23 2017-06-27 Whirlpool Corporation Consumables inventory management method
US20100106515A1 (en) * 2008-10-23 2010-04-29 Whirlpool Corporation Introduction and activation of a self-reporting portable container into an inventory system
US20100101317A1 (en) * 2008-10-23 2010-04-29 Whirlpool Corporation Lid based amount sensor
US20100106624A1 (en) * 2008-10-23 2010-04-29 Whirlpool Corporation Method of inventory management
US8115688B2 (en) * 2008-10-24 2012-02-14 Intelleflex Corporation RF conduit and systems implementing same
US20100141445A1 (en) * 2008-12-08 2010-06-10 Savi Networks Inc. Multi-Mode Commissioning/Decommissioning of Tags for Managing Assets
US9423793B2 (en) * 2008-12-23 2016-08-23 Andrew Wong System, method and computer program for pattern based intelligent control, monitoring and automation
US9659257B2 (en) * 2009-01-12 2017-05-23 Alphatrac, Inc. Predictive cueing
US8423492B2 (en) * 2009-01-12 2013-04-16 Alphatrac, Inc. Predictive prompting and decision outcome
US8590021B2 (en) * 2009-01-23 2013-11-19 Microsoft Corporation Passive security enforcement
US8170997B2 (en) * 2009-01-29 2012-05-01 Microsoft Corporation Unbundled storage transaction services
US9509436B2 (en) 2009-01-29 2016-11-29 Cubic Corporation Protection of near-field communication exchanges
US20100235314A1 (en) * 2009-02-12 2010-09-16 Decisive Analytics Corporation Method and apparatus for analyzing and interrelating video data
US8458105B2 (en) * 2009-02-12 2013-06-04 Decisive Analytics Corporation Method and apparatus for analyzing and interrelating data
US10600315B2 (en) * 2009-03-23 2020-03-24 Chris Kelly Mesh network enabled building safety system and method
TWM369991U (en) * 2009-04-24 2009-12-01 Taiwan Secom Co Ltd Cash box capable of electric shocking and smoke spraying
US8587255B2 (en) * 2009-05-28 2013-11-19 Deeya Energy, Inc. Control system for a flow cell battery
WO2010138948A2 (en) * 2009-05-28 2010-12-02 Deeya Energy, Inc. Buck-boost control circuit
WO2010138949A2 (en) * 2009-05-28 2010-12-02 Deeya Energy, Inc. Optical leak detection sensor
WO2010138945A2 (en) * 2009-05-28 2010-12-02 Deeya Energy, Inc. Preparation of flow cell battery electrolytes from raw materials
WO2010138943A2 (en) * 2009-05-28 2010-12-02 Deeya Energy, Inc. Electrolyte compositions
US8551299B2 (en) * 2009-05-29 2013-10-08 Deeya Energy, Inc. Methods of producing hydrochloric acid from hydrogen gas and chlorine gas
US8289160B1 (en) 2009-05-29 2012-10-16 United Services Automobile Association (Usaa) Systems and methods for recording and using information about conditions present in a house or other location
US20100306155A1 (en) * 2009-05-29 2010-12-02 Giannetto Mark D System and method for validating signatory information and assigning confidence rating
US20100302369A1 (en) * 2009-06-01 2010-12-02 Monsive Jr Michael G Security system with satellite surveillance units
US8456302B2 (en) * 2009-07-14 2013-06-04 Savi Technology, Inc. Wireless tracking and monitoring electronic seal
WO2011008871A1 (en) * 2009-07-14 2011-01-20 Savi Networks Llc Security seal
US8065257B2 (en) * 2009-07-27 2011-11-22 Saab Sensis Corporation System and method for correlating past activities, determining hidden relationships and predicting future activities
TW201104450A (en) * 2009-07-29 2011-02-01 Inventec Corp Method of remote controlling a server device and the server device
US8432274B2 (en) 2009-07-31 2013-04-30 Deal Magic, Inc. Contextual based determination of accuracy of position fixes
US9328857B2 (en) * 2009-08-04 2016-05-03 Zia Systems, Llc System and method for real-time tracking of objects
BR112012003727A2 (en) * 2009-08-17 2017-05-23 Deal Magic Inc contextually aware asset monitoring
US20110050397A1 (en) * 2009-08-28 2011-03-03 Cova Nicholas D System for generating supply chain management statistics from asset tracking data
US8314704B2 (en) * 2009-08-28 2012-11-20 Deal Magic, Inc. Asset tracking using alternative sources of position fix data
US8334773B2 (en) 2009-08-28 2012-12-18 Deal Magic, Inc. Asset monitoring and tracking system
US20110054979A1 (en) * 2009-08-31 2011-03-03 Savi Networks Llc Physical Event Management During Asset Tracking
US9633327B2 (en) 2009-09-25 2017-04-25 Fedex Corporate Services, Inc. Sensor zone management
US20110153343A1 (en) * 2009-12-22 2011-06-23 Carefusion 303, Inc. Adaptable medical workflow system
US9978251B2 (en) 2009-12-28 2018-05-22 Honeywell International Inc. Wireless location-based system and method for detecting hazardous and non-hazardous conditions
US8442801B2 (en) * 2009-12-28 2013-05-14 Honeywell International Inc. Wireless location-based system for detecting hazardous conditions
US20120297028A1 (en) * 2010-01-21 2012-11-22 Pranamesh Das Integrated remote pollution monitoring and indexing system and method thereof
US8951665B2 (en) * 2010-03-10 2015-02-10 Imergy Power Systems, Inc. Methods for the preparation of electrolytes for chromium-iron redox flow batteries
US8473447B2 (en) * 2010-03-29 2013-06-25 Palo Alto Research Center Incorporated AI planning based quasi-montecarlo simulation method for probabilistic planning
US20110248846A1 (en) * 2010-04-13 2011-10-13 Green SHM Systems, Inc, Incorporated Wireless Sensing Module and Method of Operation
US9442178B2 (en) * 2010-04-23 2016-09-13 Qualcomm Incorporated Hybrid tracking device
US8963720B2 (en) * 2010-05-11 2015-02-24 The Boeing Company RFID tag container
DE102010029671B4 (en) * 2010-06-02 2012-03-01 Cargoguard Gmbh Backup module for position monitoring of objects
US8930321B2 (en) 2010-06-30 2015-01-06 Microsoft Corporation Logical recovery with unbundled transaction services
US8607353B2 (en) * 2010-07-29 2013-12-10 Accenture Global Services Gmbh System and method for performing threat assessments using situational awareness
FR2963448A1 (en) * 2010-07-29 2012-02-03 Sagem Defense Securite METHOD AND SYSTEM FOR ANALYSIS OF FLIGHT DATA RECORDED DURING THE FLIGHT OF AN AIRCRAFT.
US10131419B2 (en) * 2010-10-15 2018-11-20 Goodrich Corporation Systems and methods for detecting landing gear ground loads
US8779966B2 (en) * 2010-11-16 2014-07-15 Tialinx, Inc. Remote interrogation for detection of activity or living organisms inside electronically conductive containers
US9043798B2 (en) 2010-12-16 2015-05-26 International Business Machines Corporation Remediating gaps between usage allocation of hardware resource and capacity allocation of hardware resource
US8874734B1 (en) * 2011-01-09 2014-10-28 Globaltrak, Llc Enhanced ZigBee mesh network with dormant mode activation
US8860570B2 (en) 2011-02-03 2014-10-14 SenseTech, LLC Portable wireless personal head impact reporting system
EP2485201A1 (en) 2011-02-07 2012-08-08 F.I.M. Legno S.p.A. Telematic risk management system
US9253635B2 (en) * 2011-02-09 2016-02-02 Cubic Corporation Low power wireless network for transportation and logistics
US9130937B1 (en) * 2011-03-07 2015-09-08 Raytheon Company Validating network communications
DE102011016163B4 (en) * 2011-04-05 2015-01-22 Stöbich Brandschutz GmbH Documenting device with satellite navigation system data receiver and method for documenting the state of a technical device installed in or on a building
US8681674B2 (en) 2011-04-28 2014-03-25 Cubic Corporation Accelerated rejoining in low power wireless networking for logistics and transportation applications
US9129225B2 (en) * 2011-05-25 2015-09-08 Nokia Technologies Oy Method and apparatus for providing rule-based recommendations
US9058612B2 (en) * 2011-05-27 2015-06-16 AVG Netherlands B.V. Systems and methods for recommending software applications
US9070131B2 (en) 2011-06-14 2015-06-30 Ark Ideaz, Inc. Authentication systems and methods
US8656013B2 (en) * 2011-06-14 2014-02-18 Sony Computer Entertainment America Llc Real-time data monitoring based on data push
US8862313B2 (en) * 2011-08-09 2014-10-14 Continental Automotive Systems, Inc Smart trailer RFID system
US9119167B2 (en) 2011-08-30 2015-08-25 Qualcomm Incorporated Generic broadcast of location assistance data
US9710768B2 (en) * 2011-09-23 2017-07-18 Elwha Llc Acquiring and transmitting event related tasks and subtasks to interface devices
US10789526B2 (en) 2012-03-09 2020-09-29 Nara Logics, Inc. Method, system, and non-transitory computer-readable medium for constructing and applying synaptic networks
US8732101B1 (en) 2013-03-15 2014-05-20 Nara Logics, Inc. Apparatus and method for providing harmonized recommendations based on an integrated user profile
US11151617B2 (en) 2012-03-09 2021-10-19 Nara Logics, Inc. Systems and methods for providing recommendations based on collaborative and/or content-based nodal interrelationships
US8170971B1 (en) 2011-09-28 2012-05-01 Ava, Inc. Systems and methods for providing recommendations based on collaborative and/or content-based nodal interrelationships
US10467677B2 (en) 2011-09-28 2019-11-05 Nara Logics, Inc. Systems and methods for providing recommendations based on collaborative and/or content-based nodal interrelationships
US11727249B2 (en) 2011-09-28 2023-08-15 Nara Logics, Inc. Methods for constructing and applying synaptic networks
JP5874292B2 (en) * 2011-10-12 2016-03-02 ソニー株式会社 Information processing apparatus, information processing method, and program
US20130097317A1 (en) * 2011-10-18 2013-04-18 Daniel Sheleheda Method and apparatus for remote trust management for machine to machine communications in a network
US20130135080A1 (en) * 2011-11-28 2013-05-30 Upm Rfid Oy Tag forgery protection
US20130170107A1 (en) * 2012-01-04 2013-07-04 Doug Dean Enclosure for Preventing Tampering of Mobile Communication Equipment in Transportation Industry
KR20140114009A (en) 2012-01-06 2014-09-25 쓰리엠 이노베이티브 프로퍼티즈 캄파니 Released offender geospatial location information user application
CA2860411A1 (en) 2012-01-06 2013-07-11 Hoyt M. Layson Released offender geospatial location information trend analysis
AU2013207534A1 (en) 2012-01-06 2014-07-24 3M Innovative Properties Company Released offender geospatial location information clearinghouse
JP5854856B2 (en) * 2012-01-24 2016-02-09 三菱電機株式会社 Plant operation device and plant operation training simulator device
WO2013147873A1 (en) * 2012-03-30 2013-10-03 Hewlett-Packard Development Company, L.P. Protecting context-sensitive data
US10122710B2 (en) * 2012-04-19 2018-11-06 Pq Solutions Limited Binding a data transaction to a person's identity using biometrics
US8935191B2 (en) * 2012-05-02 2015-01-13 Sap Ag Reuse of on-demand enterprise system customization knowledge utilizing collective experience
US9582767B2 (en) * 2012-05-16 2017-02-28 Excalibur Ip, Llc Media recommendation using internet media stream modeling
GB2502966A (en) * 2012-06-11 2013-12-18 Everything Everywhere Ltd Container monitoring device
US9003162B2 (en) 2012-06-20 2015-04-07 Microsoft Technology Licensing, Llc Structuring storage based on latch-free B-trees
US20140018976A1 (en) * 2012-07-13 2014-01-16 Honeywell International Inc. System and method for unmanned system data collection, management, and reporting
US9294936B2 (en) 2012-08-14 2016-03-22 Honeywell International Inc. System and method for improved location system accuracy
US8892484B2 (en) * 2012-09-28 2014-11-18 Sphere Of Influence, Inc. System and method for predicting events
RU2532723C2 (en) * 2012-11-14 2014-11-10 Федеральное государственное бюджетное учреждение науки Институт проблем информатики Российской академии наук (ИПИ РАН) Method of supporting operation of organisational system
RU2533090C2 (en) * 2012-11-29 2014-11-20 Федеральное государственное бюджетное учреждение науки Институт проблем информатики Российской академии наук (ИПИ РАН) System for situation-analytical centres of organisational system
WO2014104567A1 (en) * 2012-12-27 2014-07-03 동아대학교 산학협력단 Intrusion-detecting and security system on external wall surface of container
WO2014116691A2 (en) * 2013-01-22 2014-07-31 Raytheon Company Predictive information transmission
US9131369B2 (en) * 2013-01-24 2015-09-08 Nuance Communications, Inc. Protection of private information in a client/server automatic speech recognition system
US9142114B2 (en) 2013-01-28 2015-09-22 Apple Inc. Tracking group members' proximity
US9514741B2 (en) 2013-03-13 2016-12-06 Nuance Communications, Inc. Data shredding for speech recognition acoustic model training under data retention restrictions
US9514740B2 (en) 2013-03-13 2016-12-06 Nuance Communications, Inc. Data shredding for speech recognition language model training under data retention restrictions
US8910298B2 (en) * 2013-03-15 2014-12-09 Leeo, Inc. Environmental monitoring device
US20140279574A1 (en) 2013-03-15 2014-09-18 Leeo, Inc. Environmental measurement display system and method
US8704178B1 (en) 2013-03-15 2014-04-22 Surgitrac Corporation Container for surgical object and fluid monitoring system
US8692140B1 (en) 2013-03-15 2014-04-08 Surgitrac Corporation Surgical object and fluid monitoring system having highly sensitive and reliable detection of objects being placed in a container
US8963025B2 (en) 2013-03-15 2015-02-24 Surgitrac Corporation Surgical object and fluid monitoring system having highly sensitive and reliable detection of objects being placed in a container
US9347817B2 (en) 2013-03-15 2016-05-24 Surgitrac Corporation Surgical object and comprehensive fluid monitoring system having capability of mobile monitoring and having highly sensitive and reliable detection of objects being placed in a container
US8929246B2 (en) 2013-04-19 2015-01-06 Cubic Corporation Payment reconciliation in mixed-ownership low-power mesh networks
US10304319B2 (en) * 2013-04-23 2019-05-28 Canary Connect, Inc. Monitoring and security devices comprising multiple sensors
US9519591B2 (en) 2013-06-22 2016-12-13 Microsoft Technology Licensing, Llc Latch-free, log-structured storage for multiple access methods
GB2515801A (en) * 2013-07-04 2015-01-07 Sony Corp Transmitter and receiver and methods of transmitting and receiving
US8947230B1 (en) 2013-07-16 2015-02-03 Leeo, Inc. Electronic device with environmental monitoring
US9116137B1 (en) 2014-07-15 2015-08-25 Leeo, Inc. Selective electrical coupling based on environmental conditions
US9901250B2 (en) * 2013-10-09 2018-02-27 Senseonics, Incorporated Use of a sensor with multiple external sensor transceiver devices
GB2519347A (en) * 2013-10-18 2015-04-22 Pole Star Space Applic Ltd Method and apparatus for tracking and checking compliance of vessels such as ships
KR102180226B1 (en) * 2013-10-30 2020-11-18 삼성전자주식회사 Electronic device and method for securing using complex biometrics
US10078811B2 (en) 2013-11-29 2018-09-18 Fedex Corporate Services, Inc. Determining node location based on context data in a wireless node network
RU2665882C2 (en) * 2013-12-11 2018-09-04 Ска Хайджин Продактс Аб Distributed data acquisition equipment configuration
US10282949B2 (en) * 2013-12-12 2019-05-07 Rustin B. Penland Security system for identifying disturbances in a building
US9177481B2 (en) * 2013-12-13 2015-11-03 Sikorsky Aircraft Corporation Semantics based safe landing area detection for an unmanned vehicle
WO2015094354A1 (en) * 2013-12-20 2015-06-25 Intel Corporation Electronic goal monitoring
US9869998B2 (en) * 2014-01-09 2018-01-16 Oceaneering International, Inc. Wireless data communications between a remotely operated vehicle and a remote location
US10382194B1 (en) * 2014-01-10 2019-08-13 Rockwell Collins, Inc. Homomorphic encryption based high integrity computing system
WO2015107427A2 (en) * 2014-01-17 2015-07-23 Jaber Alexander Tactical personal surveillance and monitoring system
US10528357B2 (en) * 2014-01-17 2020-01-07 L3 Technologies, Inc. Web-based recorder configuration utility
EP3164663B1 (en) * 2014-06-03 2019-11-13 The Security Oracle, Inc. Defense and denial method
US20150379419A1 (en) * 2014-06-26 2015-12-31 International Business Machines Corporation Ghost-pattern analyzer
US9170625B1 (en) 2014-07-15 2015-10-27 Leeo, Inc. Selective electrical coupling based on environmental conditions
US9213327B1 (en) 2014-07-15 2015-12-15 Leeo, Inc. Selective electrical coupling based on environmental conditions
US9372477B2 (en) 2014-07-15 2016-06-21 Leeo, Inc. Selective electrical coupling based on environmental conditions
US9514211B2 (en) 2014-07-20 2016-12-06 Microsoft Technology Licensing, Llc High throughput data modifications using blind update operations
WO2016020762A2 (en) * 2014-08-04 2016-02-11 TaKaDu Ltd. A system and method for assessing sensors' reliability
US9092060B1 (en) 2014-08-27 2015-07-28 Leeo, Inc. Intuitive thermal user interface
US10102566B2 (en) 2014-09-08 2018-10-16 Leeo, Icnc. Alert-driven dynamic sensor-data sub-contracting
US9535153B2 (en) * 2014-09-09 2017-01-03 Honeywell International Inc. System and method for improved location accuracy
US10356649B2 (en) * 2014-09-26 2019-07-16 Intel Corporation Multisensory change detection for internet of things domain
AU2015323957B2 (en) * 2014-09-30 2020-11-19 Joshua KRAGE Detecting unauthorized device access by comparing multiple independent spatial-time data sets
US9474040B2 (en) * 2014-10-07 2016-10-18 Cisco Technology, Inc. Independently verifying a transit point in a network environment
US9445451B2 (en) 2014-10-20 2016-09-13 Leeo, Inc. Communicating arbitrary attributes using a predefined characteristic
US10026304B2 (en) 2014-10-20 2018-07-17 Leeo, Inc. Calibrating an environmental monitoring device
KR101638879B1 (en) * 2014-11-06 2016-07-12 주식회사 아이디스 Mobile device capable of connection with security system under widget
US9848458B2 (en) * 2014-12-01 2017-12-19 Oceus Networks, Inc. Wireless parameter-sensing node and network thereof
US9495861B2 (en) * 2014-12-02 2016-11-15 Honeywell International Inc. System and method for take-over protection for a security system
GB2533307B (en) * 2014-12-15 2017-07-19 Ge Aviat Systems Ltd Aircraft wireless network for fixed aircraft components
US10956856B2 (en) 2015-01-23 2021-03-23 Samsung Electronics Co., Ltd. Object recognition for a storage structure
US9769182B2 (en) * 2015-02-06 2017-09-19 Honeywell International Inc. System and method of preventing hijacking of security systems and components
US11238397B2 (en) 2015-02-09 2022-02-01 Fedex Corporate Services, Inc. Methods, apparatus, and systems for generating a corrective pickup notification for a shipped item using a mobile master node
WO2016133609A1 (en) 2015-02-18 2016-08-25 Fedex Corporate Services, Inc. Managing logistics information related to a logistics container using a container interface display apparatus
US10909540B2 (en) * 2015-02-24 2021-02-02 Micro Focus Llc Using fuzzy inference to determine likelihood that financial account scenario is associated with illegal activity
EP3268247A1 (en) * 2015-03-09 2018-01-17 AutoConnect Holdings LLC Vehicle supervising of occupant applications
EP3269180B1 (en) * 2015-03-12 2020-11-25 Honeywell International Inc. Wireless mesh network gas detection real time location system and method
US9813334B2 (en) * 2015-03-31 2017-11-07 Verizon Patent And Licensing Inc. Network element federation controller and forwarding box
KR101683592B1 (en) * 2015-04-14 2016-12-07 삼성에스디에스 주식회사 Method and Apparatus for Managing Data, Data Management System Using the Same
CN104899674A (en) * 2015-04-24 2015-09-09 公安部交通管理科学研究所 Public traffic management service pre-warning method and pre-warning system
US20160335592A1 (en) * 2015-05-13 2016-11-17 Carrier Corporation Modular data logging system with combined data logs
US10156552B2 (en) 2015-05-13 2018-12-18 Honeywell International Inc. Method to auto-configure gas detectors based on real-time location
CA2930807C (en) 2015-06-05 2021-09-21 Rustin B. Penland Security system for identifying disturbances in a building
US10902374B2 (en) * 2015-06-19 2021-01-26 International Business Machines Corporation Encrypted transit information for shipments
US10378936B2 (en) * 2015-09-04 2019-08-13 International Business Machines Corporation Identification of failed sensors in a system of interconnected devices
US10003466B1 (en) * 2015-09-15 2018-06-19 Amazon Technologies, Inc. Network traffic with credential signatures
US10805775B2 (en) 2015-11-06 2020-10-13 Jon Castor Electronic-device detection and activity association
US9801013B2 (en) 2015-11-06 2017-10-24 Leeo, Inc. Electronic-device association based on location duration
US20180275988A1 (en) * 2015-12-09 2018-09-27 Entit Software Llc Software development managements
US10354653B1 (en) 2016-01-19 2019-07-16 United Services Automobile Association (Usaa) Cooperative delegation for digital assistants
JP6957496B2 (en) 2016-03-23 2021-11-02 フェデックス コーポレイト サービシズ,インコーポレイティド Radio node-based methods for auto-tuning the broadcast settings of nodes in a radio node network, non-temporary computer-readable media containing instructions to perform that method, and auto-tuning broadcast node equipment in a radio node network.
RU2630393C1 (en) * 2016-03-31 2017-09-07 Федеральное государственное учреждение "Федеральный исследовательский центр "Информатика и управление" Российской академии наук (ФИЦ ИУ РАН) Integrated control system
US10287816B2 (en) 2016-04-21 2019-05-14 Rustin B. Penland Lockable firearm cabinet
US10907399B2 (en) 2016-04-21 2021-02-02 Rustin B. Penland Lockable firearm cabinet
US20170352234A1 (en) * 2016-06-01 2017-12-07 Al Radeef Technology & Solutions L.L.C. Security and surveillance system
US10769854B2 (en) 2016-07-12 2020-09-08 Tyco Fire & Security Gmbh Holographic technology implemented security solution
EP3270321B1 (en) * 2016-07-14 2020-02-19 Kontron Modular Computers SAS Technique for securely performing an operation in an iot environment
US9905120B1 (en) 2016-08-29 2018-02-27 At&T Digital Life, Inc. Alarm initiation when sensor is intentionally jammed
US10311702B2 (en) * 2016-09-01 2019-06-04 Locus Solutions, Llc Systems and methods for monitoring vibrations during transportation of goods
US9965939B2 (en) * 2016-09-01 2018-05-08 Locus Solutions, Llc Systems and methods for monitoring vibrations during transportation of goods
US10902537B2 (en) * 2016-11-23 2021-01-26 Electronics And Telecommunications Research Institute Method of processing logistics information, logistics information processing server using the same, and logistics managing apparatus using the same
IT201600127390A1 (en) * 2016-12-16 2018-06-16 Sanco S P A FIRE-FIGHTING CENTRAL
EP3351473A1 (en) * 2017-01-20 2018-07-25 Honeywell International Inc. Apparatus and method for qualifying data automatically generated from an unqualified system
US10839401B2 (en) 2017-01-20 2020-11-17 Honeywell International Inc. Apparatus and method for qualifying data automatically generated from an unqualified system
US11514056B2 (en) * 2017-01-23 2022-11-29 Raytheon Technologies Corporation Data request workflow system
US11036883B2 (en) * 2017-01-23 2021-06-15 Raytheon Technologies Corporation Data filtering for data request workflow system
BR102017005171A8 (en) * 2017-03-15 2021-05-18 Velsis Sist E Tecnologia Viaria S/A embedded system for instantaneous measurement of weight, vibration, deformation, pressure, acceleration and temperature of vehicles and containers
US10726711B2 (en) 2017-05-01 2020-07-28 Johnson Controls Technology Company Building security system with user presentation for false alarm reduction
US20180357598A1 (en) * 2017-06-09 2018-12-13 Walmart Apollo, Llc Systems, Devices, and Methods for Monitoring Packages with Affixed Sensors
CN110771090B (en) * 2017-06-16 2023-09-15 索尼半导体解决方案公司 Signal processing device, signal processing method, and program
CN107895413A (en) * 2017-09-18 2018-04-10 同方威视技术股份有限公司 Electronic lock equipment and the method for carrying out loading space examination
US10652742B2 (en) * 2017-11-20 2020-05-12 Valeo Comfort And Driving Assistance Hybrid authentication of vehicle devices and/or mobile user devices
US11356804B2 (en) 2018-02-25 2022-06-07 Qualcomm Incorporated Systems and methods for efficiently supporting broadcast of location assistance data in a wireless network
US11669914B2 (en) 2018-05-06 2023-06-06 Strong Force TX Portfolio 2018, LLC Adaptive intelligence and shared infrastructure lending transaction enablement platform responsive to crowd sourced information
US11544782B2 (en) 2018-05-06 2023-01-03 Strong Force TX Portfolio 2018, LLC System and method of a smart contract and distributed ledger platform with blockchain custody service
US11550299B2 (en) 2020-02-03 2023-01-10 Strong Force TX Portfolio 2018, LLC Automated robotic process selection and configuration
SG11202010731VA (en) 2018-05-06 2020-11-27 Strong Force Tx Portfolio 2018 Llc Methods and systems for improving machines and systems that automate execution of distributed ledger and other transactions in spot and forward markets for energy, compute, storage and other resources
US11429922B2 (en) * 2018-06-21 2022-08-30 Raquel Holatz Cluster-based container lifecycle tracker
US20200005172A1 (en) * 2018-06-29 2020-01-02 Paypal, Inc. System and method for generating multi-factor feature extraction for modeling and reasoning
DE102018210959A1 (en) * 2018-07-04 2020-01-09 Audi Ag Method for monitoring a traffic component, in particular a motor vehicle, for an unauthorized activity, and system
US11191056B2 (en) 2018-08-08 2021-11-30 Qualcomm Incorporated Systems and methods for validity time and change notification of broadcast location assistance data
DK201870684A1 (en) 2018-08-27 2020-05-19 Aptiv Technologies Limited Partitioned wireless communication system with redundant data links and power lines
US10878681B2 (en) * 2018-09-22 2020-12-29 Fedex Corporate Services, Inc. Systems, apparatus, and methods for detecting an environmental anomaly and initiating an enhanced automatic response using elements of a wireless node network including a command node environmental sensor
US11546138B2 (en) * 2018-09-28 2023-01-03 Benjamin Allan Mord Information integrity in blockchain and related technologies
US10607476B1 (en) 2019-03-28 2020-03-31 Johnson Controls Technology Company Building security system with site risk reduction
US10607478B1 (en) * 2019-03-28 2020-03-31 Johnson Controls Technology Company Building security system with false alarm reduction using hierarchical relationships
CN109903501B (en) * 2019-04-03 2020-11-24 湖南科技学院 Security probe analysis processing system based on big data
US11153373B2 (en) 2019-05-03 2021-10-19 EMC IP Holding Company LLC Method and system for performance-driven load shifting
US11153315B2 (en) * 2019-05-30 2021-10-19 Bank Of America Corporation Controlling access to secure information resources using rotational datasets and dynamically configurable data containers
US11138328B2 (en) 2019-05-30 2021-10-05 Bank Of America Corporation Controlling access to secure information resources using rotational datasets and dynamically configurable data containers
US11165777B2 (en) 2019-05-30 2021-11-02 Bank Of America Corporation Controlling access to secure information resources using rotational datasets and dynamically configurable data containers
US11922246B2 (en) * 2019-06-04 2024-03-05 Position Imaging, Inc. Article-identification-and-location device systems and methods of using same
US20200388194A1 (en) * 2019-06-05 2020-12-10 Honeywell International Inc. Systems and methods for generating aircraft training programs adapted to user characteristics
US10999075B2 (en) 2019-06-17 2021-05-04 Advanced New Technologies Co., Ltd. Blockchain-based patrol inspection proof storage method, apparatus, and electronic device
US11750448B2 (en) 2019-08-02 2023-09-05 Hewlett Packard Enterprise Development Lp Network device-integrated asset tag-based environmental sensing with mutual authentication
US11917488B2 (en) 2019-09-13 2024-02-27 Troverlo, Inc. Passive asset tracking using observations of pseudo Wi-Fi access points
US11589187B2 (en) 2019-09-13 2023-02-21 Troverlo, Inc. Passive sensor tracking using observations of Wi-Fi access points
US11622234B2 (en) 2019-09-13 2023-04-04 Troverlo, Inc. Passive asset tracking using observations of Wi-Fi access points
CN114503105A (en) * 2019-09-25 2022-05-13 联邦科学和工业研究组织 Password service for browser applications
CN110889944A (en) * 2019-10-18 2020-03-17 合肥森弗卡电子科技有限公司 Internet-based security analysis alarm system and method
CN111063056B (en) * 2019-11-21 2021-09-07 中国电子产品可靠性与环境试验研究所((工业和信息化部电子第五研究所)(中国赛宝实验室)) Aviation accident analysis method and device, computer equipment and storage medium
US11277712B2 (en) * 2019-12-20 2022-03-15 Tatiana Guydouk Cellular global tracker for freight
US11763182B1 (en) * 2020-05-07 2023-09-19 Jared Anders Newcombe Software facilitating decision making method
US11575979B1 (en) * 2020-06-29 2023-02-07 Amazon Technologies, Inc. Real-time multi-dimensional monitoring of environmental parameters
RU2744767C1 (en) * 2020-07-09 2021-03-15 Илья Владимирович Волочков Method and automated system for solving problems
DE102020211761A1 (en) 2020-09-21 2022-05-19 Siemens Aktiengesellschaft Measurement monitor display
EP3993345A1 (en) * 2020-10-28 2022-05-04 Furuno Hellas S.A. Apparatus and method for remote monitoring
US11811520B2 (en) 2020-12-10 2023-11-07 International Business Machines Corporation Making security recommendations
CN113034841A (en) * 2021-03-19 2021-06-25 北京红山信息科技研究院有限公司 City cooperative management early warning system
US11646896B1 (en) 2021-04-15 2023-05-09 National Technology & Engineering Solutions Of Sandia, Llc Systems and methods for verification and authentication of remote sensing imagery
US20230325784A1 (en) * 2022-04-11 2023-10-12 Truist Bank System for applying an artificial intelligence engine in real-time to affect course corrections and influence outcomes
CN116540275B (en) * 2023-07-06 2023-09-01 中国科学院空天信息创新研究院 Reliable monitoring and early warning method for probability domain of accurate positioning correction information
CN117037350B (en) * 2023-10-10 2023-12-19 成都汉度科技有限公司 Dynamic ring monitoring system and data processing method

Citations (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4636634A (en) * 1984-08-28 1987-01-13 Veeco Integrated Automation, Inc. Apparatus with intelligent bins indicating the presence and identity of stored coded articles
US5078952A (en) * 1989-06-16 1992-01-07 Science Applications International Corporation Multi-sensor explosive detection system
US5219194A (en) * 1992-02-28 1993-06-15 Viking Corporation Security seal
US5345809A (en) * 1989-06-09 1994-09-13 Research Corporation Technologies, Inc. Explosive detection screening system
US5377906A (en) * 1993-10-29 1995-01-03 Mason; Randall Device for detecting and signalling the presence of objects in a closed container and a mailbox containing the same
US5416706A (en) * 1984-04-27 1995-05-16 Hagenbuch; Leroy G. Apparatus for identifying containers from which refuse is collected and compiling a historical record of the containers
US5629498A (en) * 1995-01-18 1997-05-13 Richard A. Pollock Intraoperative tracking devices and processes
US5644489A (en) * 1984-04-27 1997-07-01 Hagenbuch; Leroy G. Apparatus and method for identifying containers from which material is collected and loaded onto a haulage vehicle
US5696884A (en) * 1994-05-09 1997-12-09 Microsoft Corporation Method for assisting in rendering a decision using improved belief networks
US5774876A (en) * 1996-06-26 1998-06-30 Par Government Systems Corporation Managing assets with active electronic tags
US6204764B1 (en) * 1998-09-11 2001-03-20 Key-Trak, Inc. Object tracking system with non-contact object detection and identification
US6248063B1 (en) * 1994-10-13 2001-06-19 Horus Therapeutics, Inc. Computer assisted methods for diagnosing diseases
US6281797B1 (en) * 2000-04-04 2001-08-28 Marconi Data Systems Inc. Method and apparatus for detecting a container proximate to a transportation vessel hold
US6370222B1 (en) * 1999-02-17 2002-04-09 Ccvs, Llc Container contents verification
US20020083022A1 (en) * 2000-11-06 2002-06-27 Algazi Allan Stuart System and methods for mail security
US20020124664A1 (en) * 1998-11-13 2002-09-12 Mesosystems Technology, Inc. Robust system for screening mail for biological agents
US6483434B1 (en) * 1999-10-20 2002-11-19 Ifco System Europe Gmbh Container tracking system
US6560592B1 (en) * 1998-03-19 2003-05-06 Micro Data Base Systems, Inc. Multi-model computer database storage system with integrated rule engine
US6594578B2 (en) * 2000-07-10 2003-07-15 United Parcel Service Of America Detection and removal of self-alerts in a tracking system
US6613571B2 (en) * 2001-12-19 2003-09-02 Pitney Bowes Inc. Method and system for detecting biological and chemical hazards in mail
US20030227392A1 (en) * 2002-01-11 2003-12-11 Ebert Peter S. Context-aware and real-time item tracking system architecture and scenarios
US6669631B2 (en) * 2000-06-14 2003-12-30 Medtronic, Inc. Deep computing applications in medical device systems
US20040006398A1 (en) * 2000-06-09 2004-01-08 Bickford Randall L. Surveillance system and method having parameter estimation and operating mode partitioning
US20040026491A1 (en) * 2001-10-29 2004-02-12 Lockheed Martin Federal Systems Hazardous material detection system for use with mail and other objects
US20040041706A1 (en) * 2002-09-04 2004-03-04 Stratmoen Scott Alan Smart and secure container
US6707381B1 (en) * 2001-06-26 2004-03-16 Key-Trak, Inc. Object tracking method and system with object identification and verification
US20040066887A1 (en) * 2002-10-08 2004-04-08 Jeffrey Garfinkle Cargo security method and apparatus
US20040122703A1 (en) * 2002-12-19 2004-06-24 Walker Matthew J. Medical data operating model development system and method
US6763299B2 (en) * 1993-05-18 2004-07-13 Arrivalstar, Inc. Notification systems and methods with notifications based upon prior stop locations
US6765490B2 (en) * 2001-10-23 2004-07-20 Steven W. Lopez System and methods for detecting harmful agents within contents of mail
US6768421B1 (en) * 2003-01-31 2004-07-27 Veritainer Corporation Container crane radiation detection systems and methods
US20040174259A1 (en) * 2003-02-20 2004-09-09 Peel John W. Container tracking system
US20040196182A1 (en) * 2003-04-03 2004-10-07 Unnold Robert M. Intelligent mobile asset management system
US20040233055A1 (en) * 2003-05-19 2004-11-25 Canich David J. Sensor suite and communication system for cargo monitoring and identification
US20040257223A1 (en) * 2003-06-17 2004-12-23 Intelagents, Inc System and method for monitoring a security of an asset

Family Cites Families (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6919803B2 (en) * 2002-06-11 2005-07-19 Intelligent Technologies International Inc. Low power remote asset monitoring
US5068798A (en) * 1989-03-03 1991-11-26 Precision Systems, Inc. Process environment monitoring system
US5161110A (en) * 1990-02-27 1992-11-03 Atlantic Richfield Company Hierarchical process control system and method
US5199672A (en) * 1990-05-25 1993-04-06 Orbital Sciences Corporation Method and apparatus for deploying a satellite network
US5121467A (en) * 1990-08-03 1992-06-09 E.I. Du Pont De Nemours & Co., Inc. Neural network/expert system process control system and method
US5219195A (en) * 1992-03-30 1993-06-15 Lawrence Barry G Window closure mechanism
US5280527A (en) * 1992-04-14 1994-01-18 Kamahira Safe Co., Inc. Biometric token for authorizing access to a host system
US5311562A (en) * 1992-12-01 1994-05-10 Westinghouse Electric Corp. Plant maintenance with predictive diagnostics
US7397363B2 (en) * 1993-06-08 2008-07-08 Raymond Anthony Joao Control and/or monitoring apparatus and method
US5528228A (en) * 1994-09-08 1996-06-18 Wilk; Peter J. Protective device for storage and transport containers
US5905443A (en) * 1995-10-02 1999-05-18 Motorola, Inc. Paging system employing delivery schedule combining and method of operation thereof
US5917433A (en) * 1996-06-26 1999-06-29 Orbital Sciences Corporation Asset monitoring system and associated method
JP3989058B2 (en) * 1997-08-05 2007-10-10 株式会社ショーワ Dust cover mounting structure
US6070143A (en) * 1997-12-05 2000-05-30 Lucent Technologies Inc. System and method for analyzing work requirements and linking human resource products to jobs
US5969884A (en) * 1998-01-30 1999-10-19 Dal-Craft, Inc. Place keeper for line magnifier
US5963131A (en) * 1998-06-19 1999-10-05 Lexent Technologies, Inc. Anti-theft device with alarm screening
GB2339614B (en) * 1998-07-14 2000-06-21 Infrared Integrated Syst Ltd Detector-array sensor with mask warning
US6398727B1 (en) * 1998-12-23 2002-06-04 Baxter International Inc. Method and apparatus for providing patient care
DK1175749T3 (en) 1999-04-22 2005-10-24 Veridicom Inc Biometric authentication with high security using public key / private key encryption pairs
US6240415B1 (en) 1999-10-07 2001-05-29 J. Seth Blumberg Corporate and entertainment management interactive system using a computer network
US6448898B1 (en) * 1999-12-16 2002-09-10 Cardinal Automation, Inc. System for auditing refuse collection
WO2001063994A2 (en) 2000-02-23 2001-08-30 Iridian Technologies, Inc. Tamper proof case for electronic devices having memories with sensitive information
US6622050B2 (en) 2000-03-31 2003-09-16 Medtronic, Inc. Variable encryption scheme for data transfer between medical devices and related data management systems
US6988279B1 (en) * 2000-05-30 2006-01-17 International Business Machines Corporation Intelligent agent authentication via position locator system
US20020017977A1 (en) * 2000-08-04 2002-02-14 Wall Mark Emanuel Method and apparatus for licensing and controlling access, use, and viability of product utilizing geographic position
WO2002025528A1 (en) 2000-09-21 2002-03-28 Theradoc.Com, Inc. Systems and methods for manipulating medical data via a decision support system
US6836773B2 (en) * 2000-09-28 2004-12-28 Oracle International Corporation Enterprise web mining system and method
JP4648533B2 (en) * 2000-10-30 2011-03-09 Okiセミコンダクタ株式会社 Semiconductor device
US20020120864A1 (en) * 2000-12-13 2002-08-29 Wu Jackie Zhanhong Automatable secure submission of confidential user information over a computer network
US20020152185A1 (en) * 2001-01-03 2002-10-17 Sasken Communication Technologies Limited Method of network modeling and predictive event-correlation in a communication system by the use of contextual fuzzy cognitive maps
JP3832257B2 (en) * 2001-02-26 2006-10-11 株式会社日立製作所 Synchronous motor start control method and control device
US6934673B2 (en) * 2001-05-25 2005-08-23 Hewlett-Packard Development Company, L.P. Method and apparatus for predicting multi-part performability
US7433826B2 (en) * 2001-09-19 2008-10-07 Eleytheria, Ltd System and method for identity validation for a regulated transaction
US7032816B2 (en) 2001-12-28 2006-04-25 Kimberly-Clark Worldwide, Inc. Communication between machines and feed-forward control in event-based product manufacturing
US7334130B2 (en) * 2002-07-19 2008-02-19 Bowers Charles R Method and apparatus for managing confidential information
US7353532B2 (en) * 2002-08-30 2008-04-01 International Business Machines Corporation Secure system and method for enforcement of privacy policy and protection of confidentiality
US6801819B1 (en) * 2002-08-30 2004-10-05 Advanced Micro Devices, Inc. Method and apparatus for evaluating bids for scheduling a resource
US6782302B1 (en) * 2002-08-30 2004-08-24 Advanced Micro Devices, Inc. Method and apparatus for scheduling workpieces with compatible processing requirements
US20040122709A1 (en) * 2002-12-18 2004-06-24 Avinash Gopal B. Medical procedure prioritization system and method utilizing integrated knowledge base
EP1584077A1 (en) * 2003-01-14 2005-10-12 United Technologies Corporation Shipping container and method of using same
US6988179B2 (en) * 2003-04-07 2006-01-17 International Business Machines Corporation Method, system, and program for ordering of physical extents
US20050075899A1 (en) * 2003-10-06 2005-04-07 Corcoran Timothy M. Global cargo container information clearinghouse
US7126473B1 (en) 2004-02-18 2006-10-24 Roger Andrew Powell Intrusion detection and secure remote alarm communication system for a security system for the inactive storage of the active ingredients of weapons of mass destruction
CN2696022Y (en) * 2004-04-15 2005-04-27 鸿富锦精密工业(深圳)有限公司 Computer panel
JP2005319590A (en) * 2004-05-06 2005-11-17 Konica Minolta Medical & Graphic Inc Printing plate material, printing plate, and printing method
US7525431B2 (en) * 2004-05-06 2009-04-28 Ut-Battelle Llc Space charge dosimeters for extremely low power measurements of radiation in shipping containers
US7225031B2 (en) * 2004-06-29 2007-05-29 Hitachi Global Storage Technologies Netherlands, B.V. Hard disk drive medical monitor with security encryption
US20060071786A1 (en) * 2004-10-05 2006-04-06 Accenture Global Sevices Gmbh Cargo security sensing system
US20060080316A1 (en) * 2004-10-08 2006-04-13 Meridio Ltd Multiple indexing of an electronic document to selectively permit access to the content and metadata thereof
JP4167640B2 (en) * 2004-10-14 2008-10-15 シャープ株式会社 Method for determining program voltage of nonvolatile memory
US7250855B2 (en) * 2004-12-27 2007-07-31 Sap Aktiengesellschaft False alarm mitigation using a sensor network
US7327248B2 (en) * 2004-12-30 2008-02-05 Sap Aktiengesellschaft Generating electronic seals
US7218974B2 (en) * 2005-03-29 2007-05-15 Zarpac, Inc. Industrial process data acquisition and analysis
US20060291657A1 (en) * 2005-05-03 2006-12-28 Greg Benson Trusted monitoring system and method

Patent Citations (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5644489A (en) * 1984-04-27 1997-07-01 Hagenbuch; Leroy G. Apparatus and method for identifying containers from which material is collected and loaded onto a haulage vehicle
US5416706A (en) * 1984-04-27 1995-05-16 Hagenbuch; Leroy G. Apparatus for identifying containers from which refuse is collected and compiling a historical record of the containers
US4636634A (en) * 1984-08-28 1987-01-13 Veeco Integrated Automation, Inc. Apparatus with intelligent bins indicating the presence and identity of stored coded articles
US5345809A (en) * 1989-06-09 1994-09-13 Research Corporation Technologies, Inc. Explosive detection screening system
US5078952A (en) * 1989-06-16 1992-01-07 Science Applications International Corporation Multi-sensor explosive detection system
US5219194A (en) * 1992-02-28 1993-06-15 Viking Corporation Security seal
US6763299B2 (en) * 1993-05-18 2004-07-13 Arrivalstar, Inc. Notification systems and methods with notifications based upon prior stop locations
US5377906A (en) * 1993-10-29 1995-01-03 Mason; Randall Device for detecting and signalling the presence of objects in a closed container and a mailbox containing the same
US5696884A (en) * 1994-05-09 1997-12-09 Microsoft Corporation Method for assisting in rendering a decision using improved belief networks
US6248063B1 (en) * 1994-10-13 2001-06-19 Horus Therapeutics, Inc. Computer assisted methods for diagnosing diseases
US5629498A (en) * 1995-01-18 1997-05-13 Richard A. Pollock Intraoperative tracking devices and processes
US5774876A (en) * 1996-06-26 1998-06-30 Par Government Systems Corporation Managing assets with active electronic tags
US6560592B1 (en) * 1998-03-19 2003-05-06 Micro Data Base Systems, Inc. Multi-model computer database storage system with integrated rule engine
US6204764B1 (en) * 1998-09-11 2001-03-20 Key-Trak, Inc. Object tracking system with non-contact object detection and identification
US20020124664A1 (en) * 1998-11-13 2002-09-12 Mesosystems Technology, Inc. Robust system for screening mail for biological agents
US6370222B1 (en) * 1999-02-17 2002-04-09 Ccvs, Llc Container contents verification
US6483434B1 (en) * 1999-10-20 2002-11-19 Ifco System Europe Gmbh Container tracking system
US6281797B1 (en) * 2000-04-04 2001-08-28 Marconi Data Systems Inc. Method and apparatus for detecting a container proximate to a transportation vessel hold
US20040006398A1 (en) * 2000-06-09 2004-01-08 Bickford Randall L. Surveillance system and method having parameter estimation and operating mode partitioning
US6669631B2 (en) * 2000-06-14 2003-12-30 Medtronic, Inc. Deep computing applications in medical device systems
US6594578B2 (en) * 2000-07-10 2003-07-15 United Parcel Service Of America Detection and removal of self-alerts in a tracking system
US20020083022A1 (en) * 2000-11-06 2002-06-27 Algazi Allan Stuart System and methods for mail security
US6707381B1 (en) * 2001-06-26 2004-03-16 Key-Trak, Inc. Object tracking method and system with object identification and verification
US6765490B2 (en) * 2001-10-23 2004-07-20 Steven W. Lopez System and methods for detecting harmful agents within contents of mail
US20040026491A1 (en) * 2001-10-29 2004-02-12 Lockheed Martin Federal Systems Hazardous material detection system for use with mail and other objects
US6613571B2 (en) * 2001-12-19 2003-09-02 Pitney Bowes Inc. Method and system for detecting biological and chemical hazards in mail
US20030227392A1 (en) * 2002-01-11 2003-12-11 Ebert Peter S. Context-aware and real-time item tracking system architecture and scenarios
US20040041706A1 (en) * 2002-09-04 2004-03-04 Stratmoen Scott Alan Smart and secure container
US20040066887A1 (en) * 2002-10-08 2004-04-08 Jeffrey Garfinkle Cargo security method and apparatus
US20040122703A1 (en) * 2002-12-19 2004-06-24 Walker Matthew J. Medical data operating model development system and method
US6768421B1 (en) * 2003-01-31 2004-07-27 Veritainer Corporation Container crane radiation detection systems and methods
US20040174259A1 (en) * 2003-02-20 2004-09-09 Peel John W. Container tracking system
US20040196182A1 (en) * 2003-04-03 2004-10-07 Unnold Robert M. Intelligent mobile asset management system
US20040233055A1 (en) * 2003-05-19 2004-11-25 Canich David J. Sensor suite and communication system for cargo monitoring and identification
US20040257223A1 (en) * 2003-06-17 2004-12-23 Intelagents, Inc System and method for monitoring a security of an asset

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8781987B1 (en) * 2012-12-31 2014-07-15 Gary Stephen Shuster Decision making using algorithmic or programmatic analysis

Also Published As

Publication number Publication date
US20120150782A1 (en) 2012-06-14
US20090210378A1 (en) 2009-08-20
US7512583B2 (en) 2009-03-31
US8515895B2 (en) 2013-08-20
WO2006119323A3 (en) 2007-02-22
US20100090822A1 (en) 2010-04-15
US7526455B2 (en) 2009-04-28
US20070002139A1 (en) 2007-01-04
US7656286B2 (en) 2010-02-02
US8830053B2 (en) 2014-09-09
US20160019384A1 (en) 2016-01-21
US20070022057A1 (en) 2007-01-25
US20140058990A1 (en) 2014-02-27
US20170024988A1 (en) 2017-01-26
US20130120135A1 (en) 2013-05-16
WO2006119323A2 (en) 2006-11-09
US20220237997A1 (en) 2022-07-28
US20070182544A1 (en) 2007-08-09
US20070011108A1 (en) 2007-01-11
US20070022079A1 (en) 2007-01-25
US20170004407A1 (en) 2017-01-05
US20200118405A1 (en) 2020-04-16
US20070008410A1 (en) 2007-01-11
US20070030143A1 (en) 2007-02-08
US20060291657A1 (en) 2006-12-28
US7609159B2 (en) 2009-10-27
US20070002140A1 (en) 2007-01-04
US20070011105A1 (en) 2007-01-11
US20200273304A1 (en) 2020-08-27
US20230401945A1 (en) 2023-12-14
US10504349B2 (en) 2019-12-10
US20070011107A1 (en) 2007-01-11
WO2007027239A8 (en) 2007-04-26
WO2007027239A1 (en) 2007-03-08

Similar Documents

Publication Publication Date Title
US20230401945A1 (en) Trusted decision support system and method
Kotenko et al. Framework for mobile Internet of Things security monitoring based on big data processing and machine learning
Beaudouin et al. Flexible and context-specific AI explainability: a multidisciplinary approach
CN114586048A (en) Machine Learning (ML) infrastructure techniques
US11055420B2 (en) Controlling access to data requested from an electronic information system
US8825578B2 (en) System and method for determining an entity's identity and assessing risks related thereto
US11625647B2 (en) Methods and systems for facilitating analysis of a model
EP3920067A1 (en) Method and system for machine learning model testing and preventive measure recommendation
Rice et al. Machine coding of policy texts with the Institutional Grammar
US20220038489A1 (en) Cybersecurity threat modeling and analysis
WO2016016973A1 (en) Result evaluation device, control method for result evaluation device, and control program for result evaluation device
CN113221747B (en) Privacy data processing method, device and equipment based on privacy protection
Elsayed et al. AdaptIDS: Adaptive intrusion detection for mission-critical aerospace vehicles
Zikrullah et al. A comparison of hazard analysis methods capability for safety requirements generation
CN106650945B (en) A kind of software architecture security assessment method based on evidence combining theory
Seale et al. Approaches for using machine learning algorithms with large label sets for rotorcraft maintenance
Montasari Artificial Intelligence and the Internet of Things Forensics in a National Security Context
Giusti et al. Analyzing flight delay prediction under concept drift
US20050010541A1 (en) Method and system for computing categories and prediction of categories utilizing time-series classification data
DeFranco et al. A taxonomy of critical AI system characteristics for use in proxy system testing
Kroll et al. Understanding, Assessing, and Mitigating Safety Risks in Artificial Intelligence Systems
Carson A Hybrid Decision Tree-Neural Network (DT-NN) Model for Predictive Maintenance Applications in Aircraft
Wehbi Machine Learning Based Practical and Efficient DDoS Attacks Detection System for IoT
Rubio FRAUD DETECTION BY ANALY-ZING HUMAN BEHAVIOR APPLY MACHINE LEARNING TECHNIQUES
Corrêa Artificial Intelligence Ethics and Safety: practical tools for creating" good" models

Legal Events

Date Code Title Description
AS Assignment

Owner name: PALOMAR TECHNOLOGY, LLC, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BENSON, GREG;FISTONICH, MATTHEW ANTHONY;REEL/FRAME:018258/0877

Effective date: 20060823

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: PALOMAR TECHNOLOGY,LLC, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BENSON, GREG;FISTONICH, MATTHEW;SIGNING DATES FROM 20110802 TO 20110811;REEL/FRAME:026891/0352

AS Assignment

Owner name: 1997 IRREVOCABLE TRUST FOR GREGORY P. BENSON, CALI

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PALOMAR TECHNOLOGY, LLC;REEL/FRAME:037383/0300

Effective date: 20151229