SYSTEM FOR COLLABORATIVE THREAT EVASION TACTICS COORDINATION

Abstract

A system with a first mobile entity and second mobile entities is described. The system implements an approach where the second mobile entities are commanded to move along a predetermined trajectory to protect the first mobile entity from external threats.

Claims

1. A system comprising: a first mobile entity; and at least one second mobile entity; wherein the first mobile entity is communicatively connected to at least one sensor configured to acquire information about surroundings of the first mobile entity; wherein the first mobile entity is configured to determine that an external threat acquired by the at least one sensor poses a risk for the first mobile entity; wherein the system is configured to, when it was determined that the external threat acquired by the at least one sensor poses a risk for the first mobile entity, command at least one of the at least one second mobile entity to initiate a countermeasure against the external threat; and wherein the first mobile entity is configured to command the at least one of the at least one second mobile entity to move along a trajectory between a position of the external threat and the first mobile entity.

2. The system of claim 1, comprising a plurality of second mobile entities, wherein each second mobile entity comprises a drive which is configured to cause a movement of the second mobile entity.

3. The system of claim 2, wherein the plurality of second mobile entities is configured to be operated in a first state or in a second state; wherein, in the first state, the plurality of second mobile entities are configured to move around the first mobile entity or along a trajectory of the first mobile entity; wherein, in the second state, at least one of the plurality of second mobile entities is commanded to attack or clear the external threat.

4. The system of claim 3, wherein, in the second state, at least one of the plurality of second mobile entities is commanded to move along a trajectory to an interception point with the external threat.

5. The system of claim 1, wherein the at least one second mobile entity is an unmanned vehicle.

6. The system of claim 1, wherein the at least one second mobile entity comprises an effector that is configured to perform a countermeasure in response to the external threat.

7. The system of claim 1, wherein the first mobile entity is connected to each of the second mobile entities by a data link.

8. The system of claim 7, wherein the first mobile entity is configured to acquire a state vector of the system and to command the at least one second mobile entity based on the acquired state vector.

9. The system of claim 8, wherein the state vector of the system includes one or more of: a position of the first mobile entity, a trajectory of the first mobile entity; a respective position of each one of the at least one second mobile entity; a respective trajectory of each one of the at least one second mobile entity.

10. The system of claim 8, wherein the system is configured to predict a trajectory of the external threat and to command the at least one second mobile entity additionally based on the predicted trajectory of the external threat.

11. The system of claim 1, wherein the system is configured to, when the external threat is acquired, determine a modified trajectory for the first mobile entity and command the first mobile entity to follow the modified trajectory.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The subject matter will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and wherein:

[0049] FIG. 1 is a schematic representation of a system according to an embodiment with reference to aerial platforms.

[0050] FIG. 2 is a schematic representation of a system showing a second mobile entity taking a countermeasure against an external threat.

DETAILED DESCRIPTION

[0051] The following detailed description is merely exemplary in nature and is not intended to limit the disclosure herein and uses of the disclosure herein. Furthermore, there is no intention to be bound by any theory presented in the preceding background or the following detailed description.

[0052] The representations and illustrations in the drawings are schematic and not to scale. Like numerals denote like elements.

[0053] A greater understanding of the described subject matter may be obtained through a review of the illustrations together with a review of the detailed description that follows.

[0054] FIG. 1 shows a system 10 that comprises a first mobile entity 20 and multiple second mobile entities 30. The first mobile entity 20 is a so-called high-value aircraft which may transport persons and/or which contains valuable equipment. The second mobile entities 30 are unmanned aircraft and are configured to follow the first mobile entity. It is conceivable that the first mobile entity is configured to carry the second mobile entity when no external threat is expected or detected and that the second mobile entities are deployed in a situation where an external threat is likely to appear.

[0055] The first mobile entity 20 includes a mission computer 25 and sensors 40. Generally, it is noted that reference to a mission computer 25 when describing the examples presented herein also covers examples in which the functions assigned to the mission computer 25 are implemented and executed by a flight computer. The sensors 40 are configured to sense the surroundings of the first mobile entity for external threats. However, the first mobile entity may also receive sensor data from an external sensor platform 60 which includes multiple different sensors 40 that are configured to sense a surveillance region with sensors 40 working in different spectral regions (optical, acoustical, infrared, radar, lidar, any other electromagnetic wavelengths, radar warning receivers, missile approach warner). For example, the first mobile entity 20 receives sensor data from the sensor platform 60 via the data link 62. The external sensor platform may be a mobile or stationary platform, for example a surveillance aircraft/watercraft, etc.

[0056] The second mobile entities 30 include several components. While FIG. 1 shows that different components are assigned to different second mobile entities, it is noted that this assignment is shown in that way only for illustrative purposes. The second mobile entities may be structurally and functionally identical. A second mobile entity 30 includes one or more sensors 40, a drive 35, and one or more effectors 37. The sensor 40 is configured to acquire an external threat 50 that approaches the first or second mobile entities 20, 30. The drive 35 is a placeholder for any device that is designed to move the second mobile entity, like propeller, turbine engine, etc. The effector 37 is designed to take any active or passive countermeasure against the external threat, e.g., deploy chaffs, flares, decoys, jammers, etc., or fire a weapon against the external threat.

[0057] The first and second mobile entities include a mission computer 25. The mission computer controls the respective mobile entity and coordinates the trajectory of the first and second mobile entities 20, 30. For that reason, the first mobile entity 20 is communicatively coupled to each of the second mobile entities 30 via a data link 32. The individual mission computers 25 of the first and second mobile entities may exchange data about the external threat 50 and also exchange data about the own status so that a state vector is generated which is indicative of the status of the system 10. Based on the state vector of the system 10 and the information about the external threat 50, the mission computers 40 of the entities 20, 30 are able to determine an appropriate countermeasure and coordinate each of the first and second mobile entities to perform the required action.

[0058] The first mobile entity 20 or any of the second mobile entities 30 may be communicatively coupled to a mission control center 70 which may provide information to the entities 20, 30. For example, the mission control center 70 may provide information about approaching external threats 50 or generally about a threat situation so that the system can either prepare specific countermeasures or the first mobile entity 20 deploys the second mobile entities 30 to reduce the response time when external threats 50 occur.

[0059] The system 10 may also transmit sensor information to the mission control center 70 and receive prepared plans for countermeasures to be executed by the system 10. However, the system 10 is preferably configured to respond to external threats 50 autonomously without connection to the mission control center 70.

[0060] Preferably, the system 10 described herein collaboratively merges flight controls and countermeasures of different platforms, i.e., first and second mobile entities 20, 30 and commands the second mobile entities 30 to take countermeasures against an external threat 50 to protect the first mobile entity 20.

[0061] The mission computer 25 of the first mobile entity 20 and/or the group of mission computers 25 of the first and second mobile entities 20, 30 are configured to perform at least some of the following functions:

[0062] 1. Receive inputs from sensors 40 and defensive aid sub systems present in the first and second mobile entities 20, 30;

[0063] 2. Receive inputs from sensors 40 of an external sensor platform 60 or other means to improve situational awareness;

[0064] 3. Receive information from and about the first and second mobile entities and generate a state vector that includes the state of all team vehicles of the system 10;

[0065] 4. Distribute information (e.g., those received in the previous functions) among all mobile entities 20, 30 of the system 10;

[0066] 5. Determine external threat characteristics (e.g., incoming weapon characteristics like flight envelope, remaining flying time, expected range, warhead action radius, etc.) based on tables that are stored in the mission computer 25 and pre-loaded mission data;

[0067] 6. If no data are available about the external threat, the mission computer is configured to predict its performance based on real-time characterization and observation of its behavior;

[0068] 7. Determining a strategy, trajectory, and timeline for the first mobile entity 20, at least one of the second mobile entities 30, and the external threat 50 to break radar lock, deploy countermeasures and evade weapon(s);

[0069] 8. Commanding one or several second mobile entities 30 to interpose their trajectory between the first mobile entity 20 and the external threat 50 as long as the external threat is still approaching the first mobile entity 20; the system may command multiple second mobile entities to move between the external threat 50 and the first mobile entity 20 so that additional second mobile entities can intercept with the external threat in case one second mobile entity misses the external threat 50;

[0070] 9. Countermeasures (chaff, flares, jammers, decoys) are deployed collaboratively by the first and/or one or more second mobile entities 20, 30;

[0071] 10. One or more second mobile entities 30 adapt their trajectory in real-time to stay between the first mobile entity and the external threat.

[0072] FIG. 2 exemplarily shows how the first mobile entity 20 and one second mobile entity 30 are coordinated to protect the first mobile entity 20 from the external threat 50.

[0073] The sensors aboard the first and/or second mobile entity (or from an external sensor platform 60, see FIG. 1) detect an approaching external threat 50 and predict its trajectory 51 based on the acquired movement of the external threat 50. The system 10 determines a modified trajectory 21 for the first mobile entity 20 while the second mobile entity 30 is commanded to follow a trajectory 31 to an interception point 53 with the external threat 50.

[0074] Alternatively to moving to the interception point 53, the second mobile entity 30 may take other countermeasures, as described above, to protect the first mobile entity 20 from the external threat 50.

[0075] While at least one example embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the example embodiment or example embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the disclosure herein in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an example embodiment of the disclosure herein. It will be understood that various changes may be made in the function and arrangement of elements described in an example embodiment without departing from the scope of the claims.

[0076] The subject matter disclosed herein can be implemented in or with software in combination with hardware and/or firmware. For example, the subject matter described herein can be implemented in or with software executed by a processor or processing unit. In one example implementation, the subject matter described herein can be implemented using a computer readable medium having stored thereon computer executable instructions that when executed by a processor of a computer control the computer to perform steps. Example computer readable mediums suitable for implementing the subject matter described herein include non-transitory devices, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein can be located on a single device or computing platform or can be distributed across multiple devices or computing platforms.

[0077] While at least one example embodiment of the present invention(s) is disclosed herein, it should be understood that modifications, substitutions and alternatives may be apparent to one of ordinary skill in the art and can be made without departing from the scope of this disclosure. This disclosure is intended to cover any adaptations or variations of the example embodiment(s). In addition, in this disclosure, the terms “comprise” or “comprising” do not exclude other elements or steps, the terms “a”, “an” or “one” do not exclude a plural number, and the term “or” means either or both. Furthermore, characteristics or steps which have been described may also be used in combination with other characteristics or steps and in any order unless the disclosure or context suggests otherwise. This disclosure hereby incorporates by reference the complete disclosure of any patent or application from which it claims benefit or priority.

LIST OF REFERENCE SIGNS

[0078] 10 System [0079] 20 first mobile entity [0080] 21 trajectory [0081] 25 mission computer [0082] 30 second mobile entity [0083] 31 trajectory [0084] 32 data link [0085] 35 drive [0086] 37 effector [0087] 40 sensor [0088] 50 external threat [0089] 51 trajectory [0090] 53 interception point [0091] 60 sensor platform [0092] 62 data link [0093] 70 mission control