US 2014/0279809 A1 · Data Broker Reasoner

Abstract

A data broker-reasoner (DBR) system for automating mission planning and execution includes a context originating entity, a reasoner/decision entity, and a plurality of enforcement entities. The context originating entity extracts mission policy information from a variety of source materials, including checklists, manuals, and other documentation. The reasoner/decision entity interprets the mission policy in the context of situational awareness (SA) events to determine which policies should be enforced. Each of the enforcement entities is configured to enforce various policies within the context of a given mission lifecycle phase by providing commands, data, and requests to a plurality of user applications and/or other mission systems. The DBR can operate autonomously or semi-autonomously.

Claims20

Dependent claims

A data broker-reasoner (DBR) system comprising:

a context originating entity for receiving mission source information from one or more information sources and for outputting a mission policy;
a reasoner/decision entity, coupled to the context originating entity, for receiving a new mission policy from the context originating entity, for receiving event data, for determining an enforcement rule based upon the new mission policy and the event data, and for outputting the enforcement rule;
and
one or more enforcement entities, coupled to the reasoner/decision entity, for receiving an enforcement rule from the reasoner/decision entity and executing the received enforcement rule.

1 more element

A mission planning system, comprising:

one or more mission lifecycle databases;
one or more mission applications;
and
a data broker-reasoner (DBR) system coupled to the mission lifecycle databases and to the mission applications, the DBR system comprising:
a context originating entity for receiving mission source information from one or more information sources, including at least one of the mission lifecycle databases, and for outputting a mission policy to at least one of the mission applications;
a reasoner/decision entity, coupled to the context originating entity, for receiving a new mission policy from the context originating entity, for receiving event data, for determining an enforcement rule based upon the new mission policy and the event data, and for outputting the enforcement rule;
and
one or more enforcement entities, coupled to the reasoner/decision entity, for receiving an enforcement rule from the reasoner/decision entity and executing the received enforcement rule.

5 more elements

Dependencies are inferred from the claim text.

Data Broker Reasoner

Life of this patent

Data Broker Reasoner

Life of this patent

Abstract

Claims20