MISSILE SYSTEM INCLUDING ADS-B RECEIVER

• US 20160216073A1
• Filed: 10/06/2014
• Published: 07/28/2016
• Est. Priority Date: 10/08/2013
• Status: Active Grant

• Current Assignee: Israel Aerospace Industries Limited (Government of Israel)
• Original Assignee: Israel Aerospace Industries Limited (Government of Israel)
• Inventors: BONEN, Uri
• Granted Patent: US 10,126,100 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: F41G 7/007 Preparatory measures taken before the launching of the guided missiles

Abstract

The disclosure presents at least one example of a missile system, method, and/or computer program product. The missile system may, for example, include a radar, an Automatic Dependent Surveillance Broadcast (“ADS-B”) receiver, a missile launcher, and a control station. The missile system may, for example, be configured to handle various situations such as when only ADS-B data relating to an airborne entity is available, only radar data relating to the airborne entity is available or both ADS-B data and radar data relating to the airborne entity are available. The missile system, may, for example, be a surface to air missile system.

Claims

1. A missile method comprising,

determining that Automatic Dependent Surveillance Broadcast (“

ADS-B”

) data relating to an airborne entity was obtained;

determining whether or not radar data relating to the airborne entity was obtained;

determining whether or not to command missile launch against the airborne entity; and

if determined not to command missile launch, then refraining from commanding missile launch against the airborne entity.

2. The method of claim 1, wherein if radar data relating to the airborne entity was not obtained, then said determining whether or not to command missile launch against the airborne entity includes determining that a missile should not be launched against the airborne entity.

3. The method of claim 1, wherein said determining whether or not radar data relating to the airborne entity was obtained includes:

determining whether or not radar data was obtained; and

if radar data was obtained, then determining whether or not said radar data pertains to the airborne entity at least partly based on comparing position data included in said radar data with position data included in said ADS-B data.

4. The method of claim 1, further comprising:

if determined to command missile launch, then commanding missile launch against the airborne entity.

5. The method of claim 1, wherein if determined that radar data relating to the airborne entity was obtained, then said determining whether or not to command missile launch includes:

estimating that said entity is not hostile because ADS-B data was obtained;

providing to an operator a result of said estimating; and

receiving an indication from the operator whether or not a missile should be launched against the airborne entity.

6. The method of claim 1, wherein if determined that radar data relating to the airborne entity was obtained, then said determining whether or not to command missile launch includes:

estimating a likelihood that said entity is not hostile or hostile, including evaluating a likelihood that an identification consistent with a non-hostile entity, included in said ADS-B data, is trustworthy or untrustworthy;

providing to an operator a result of said estimating; and

receiving an indication from the operator whether or not a missile should be launched against the airborne entity.

7. The method of claim 1, wherein said determining whether or not to command missile launch includes:

estimating that said entity is not hostile because ADS-B data was obtained; and

determining that a missile should not be launched.

8. The method of claim 1, wherein if determined that radar data relating to the airborne entity was obtained, then said determining whether or not to command missile launch includes:

estimating a likelihood that said entity is not hostile or hostile, including evaluating a likelihood that an identification consistent with a non-hostile entity, included in said ADS-B data, is trustworthy or untrustworthy; and

determining whether or not a missile should be launched against the airborne entity, at least partly based on a result of said estimating.

9. The method of claim 1, wherein if determined that radar data relating to the airborne entity was obtained, then said determining whether or not to command missile launch includes:

providing to an operator an indication that ADS-B data and radar data were obtained for the airborne entity; and

receiving an indication from the operator whether or not a missile should be launched against the airborne entity.

10. The method of claim 1, wherein missile launch is not commanded against the airborne entity if it is estimated that a likelihood of said entity being not hostile is above a predetermined threshold, at least partly based on an evaluation that a likelihood of an identification consistent with a non-hostile entity, included in said ADS-B data, being trustworthy is above a predefined percentage.

11. The method of claim 1, wherein missile launch is not commanded against the airborne entity because ADS-B data was obtained.

12. The method of claim 1, wherein said missile is a surface to air missile.

13. A missile system, comprising:

a launch control configured to determine that Automatic Dependent Surveillance Broadcast (“

ADS-B”

) data relating to an airborne entity was obtained, to determine whether or not radar data relating to the airborne entity was obtained, to determine whether or not to command missile launch against the airborne entity, and to refrain from commanding missile launch against the airborne entity if determined not to command missile launch.

14. The system of claim 13, further comprising:

an ADS-B receiver.

15. The system of claim 13, further comprising:

a missile launcher.

16. The system of claim 13, further comprising:

a radar.

17. The system of claim 13, being a surface to air missile system.

18. The system of claim 13, wherein said launch control is configured to refrain from commanding missile launch against the airborne entity, if it is estimated that a likelihood of said entity being not hostile is above a predetermined threshold, at least partly based on an evaluation that a likelihood of an identification consistent with a non-hostile entity, included in said ADS-B data, being trustworthy is above a predefined percentage.

19. The system of claim 13, wherein said launch control is configured to refrain from commanding missile launch against the airborne entity because ADS-B data was obtained.

20. A computer program product, comprising a computer readable medium having computer readable program code embodied therein, the computer program product comprising:

computer readable program code for causing the computer to determine that Automatic Dependent Surveillance Broadcast (“

ADS-B”

) data relating to an airborne entity was obtained;

computer readable program code for causing the computer to determine whether or not radar data relating to the airborne entity was obtained;

computer readable program code for causing the computer to determine whether or not to command missile launch against the airborne entity; and

computer readable program code for causing the computer to refrain from commanding missile launch against the airborne entity if determined not to command missile launch.