Patent Application
20070163430
The present invention is generally related to countermeasures for protecting aircraft from missile threats. More particularly the present invention relates to a cooperative network for protecting aircrafts from missile threats.
Recently, there has been an increased interest in improving protection of commercial aircraft. One specific area of increased interest with regard to protection of commercial aircraft is protection of commercial aircraft from ground to air missiles. Examples of ground to air missile systems of specific concern are Man Portable Air Defense Systems (MANPADS), which are man-portable surface to air missiles. MANPADS pose a serious threat to aircraft in general due to their portability, compared to more stationary missile systems that are larger and require transportation via a vehicle, thereby making them easier to detect, and therefore, easier to protect against.
MANPADS defense systems have been mounted on commercial aircraft for the purpose of defending against MANPADS. Unfortunately, MANPADS defense systems have certain limitations. As an example, MANPADS defense systems have limitations as to how many missiles they are capable of defending an associated aircraft from at one time. Therefore, if multiple missiles are launched at the same time or near the same time, the MANPADS defense system may fail to protect the associated aircraft.
Another limitation of MANPADS defense systems becomes apparent in areas with multiple aircrafts flying in a confined area, such as in airports. Since there may be many aircrafts having MANPADS defense systems departing or arriving at an airport at the same time, an attack on one aircraft among the many may cause multiple MANPADS defense systems to attempt to defend against a single missile at the same time. Unfortunately, multiple MANPADS defense systems detecting a missile and acting at the same time in close vicinity of each other may cause interference between the MANPADS defense systems, thereby limiting their defensive capabilities and placing the target of the missile in great danger.
Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.
Embodiments of the present invention provide a system and method for providing a cooperative countermeasure network to counter missile threats. Briefly described, in architecture, one embodiment of the network, among others, can be implemented as follows. The system contains at least one aircraft having an airborne countermeasures system (ACS) capable of controlling deployment of countermeasures located on the aircraft. The system also contains a central countermeasures management system (CCMS) capable of communicating with the ACS to control the ACS in deployment of the countermeasures located on the aircraft.
The present invention can also be viewed as providing methods for providing countering an airborne threat to an aircraft. A first method for providing countering an airborne threat to an aircraft, comprises the steps of: receiving threat information about the airborne threat from a remote source; receiving source information about the remote source; determining a type of airborne threat from the received threat information and the received source information; selecting a countermeasure that is presently available by the remote source, wherein the countermeasure is capable of deterring the airborne threat from inflicting damage to the aircraft; and instructing the remote source to deploy the selected countermeasure that is presently available.
A second method for providing countering an airborne threat to an aircraft, comprises the steps of: determining threat information about the airborne threat; transmitting the threat information to a remote device; transmitting source information to the remote device; receiving instructions to deploy a countermeasure selected by the remote device, as a result of the steps of determining threat information, transmitting the threat information, and transmitting the source information, wherein the selected countermeasure is presently available; and deploying the selected countermeasure, wherein the threat information and the source information is collectively referred to as a track file.
Other systems, methods, features, and advantages of the present invention will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
Many aspects of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
The present system and method provides a cooperative countermeasure network to counter missile threats. To provide the present network information detected by multiple aircrafts is transmitted to a base station for analysis, countermeasure determination, and assignment of countermeasure deployment. A general view of communication within the present cooperative countermeasure network is provided by
Although
Generally, in terms of hardware architecture, as shown in
The CCMS 102 also contains a storage device 160 for storing data therein. As an example, in accordance with the first exemplary embodiment of the invention, the data may include threat characteristics, countermeasures and effectiveness against such threats, local ACSs 12, 22, 32, 42 and their available countermeasures, and local countermeasures made available by sources other than the ACSs 12, 22, 32, 42. Further discussion of this data, in addition to the process of using such data, is provided herein.
The processor 120 is a hardware device for executing software 132, particularly that stored in the memory 130. The processor 120 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computer, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions. Examples of suitable commercially available microprocessors are as follows: a PA-RISC series microprocessor from Hewlett-Packard Company, an 80x86 or Pentium series microprocessor from Intel Corporation, a PowerPC microprocessor from IBM, a Sparc microprocessor from Sun Microsystems, Inc, or a 68xxx series microprocessor from Motorola Corporation.
The memory 130 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory 130 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 130 can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the processor 120.
The software 132 in the memory 130 may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing logical functions. In the example of
The I/O devices 140 may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, or other input devices. Furthermore, the I/O devices 140 may also include output devices, for example but not limited to, a printer, display, or other output devices. Finally, the I/O devices 140 may further include devices that communicate both inputs and outputs, for example but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, or other communication devices.
The CCMS 102 also contains a transceiver 170 that is capable of transmitting and receiving signals from an ACS 12, 22, 32, 42. In accordance with the first exemplary embodiment of the invention, the transceiver 170 is capable of high speed, high bandwidth data communication.
When the CCMS 102 is in operation, the processor 120 is configured to execute the software 132 stored within the memory 130, to communicate data to and from the memory 130, and to generally control operations of the CCMS 102 pursuant to the software 132, as defined herein. The software 132 and the O/S 134, in whole or in part, but typically the latter, are read by the processor 120, perhaps buffered within the processor 120, and then executed.
When the CCMS 102 is implemented in software, it should be noted that the CCMS 102 can be stored on any computer readable medium for use by or in connection with any computer related system or method. In the context of this document, a computer readable medium is an electronic, magnetic, optical, or other physical device or means that can contain or store a computer program for use by or in connection with a computer related system or method. The CCMS 102 can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM, or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
In an alternative embodiment, where the CCMS 102 is implemented in hardware, the CCMS 102 can be implemented with any or a combination of the following technologies, which are each well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals; an application specific integrated circuit (ASIC) having appropriate combinational logic gates; a programmable gate array(s) (PGA); and a field programmable gate array (FPGA), among others.
The storage device 160 also contains a countermeasure effectiveness database 164. The countermeasure effectiveness database 164 has stored therein different known countermeasures that are capable of defending a targeted aircraft against different known types of missile threats. Preferably, countermeasures known to defend against the known types of missile threats defined within the threat characteristics database 162 are stored within the countermeasure effectiveness database 164. In addition, it is beneficial to have specific data cells located within the threat characteristics database 162, having characteristics of a specific type of missile threat, directly associated with specific data cells located within the countermeasure effectiveness database 164, that have stored therein countermeasures capable of defending an aircraft from the specific type of missile.
An ACS available countermeasures database 166 is located within the storage device 160. The ACS available countermeasure database 166 has stored therein identifications of specific aircrafts 10, 20, 30, 40 that have communicated with the CCMS 102 through their respective ACS 12, 22, 32, 42, and countermeasures presently available on the aircrafts 10, 20, 30, 40.
Data stored within the ACS available countermeasures database 166 changes in real time with communication between an ACS 12, 22, 32, 42 and a CCMS 102, as is further explained in detail herein. It should be noted, however, that standard countermeasures known to be available on aircrafts 10, 20, 30, 40 that will communicate with the CCMS 102 may be stored within the ACS available countermeasure database 166, however, present availability of such standard countermeasures on an aircraft 10, 20, 30, 40 in communication with the CCMS 102 is confirmed prior to the CCMS 102 assigning a countermeasure deployment task to the ACS 12, 22, 32, 42 or any other device. It should also be noted that the ACS available countermeasure database 166 may have stored therein the identifications of numerous aircrafts 10, 20, 30, 40 that have communicated with the CCMS 102, and each of their present individual countermeasure availabilities. By having the identification of each aircraft that has communicated with the CCMS 102 and their individual countermeasure availabilities, the CCMS 102 is capable of determining which aircraft 10, 20, 30, 40 is capable of assisting in deterring a current missile threat, as is explained in detail herein.
Optionally, the storage device 160 may contain a CCMS available countermeasures database 168. The CCMS available countermeasures database 168 has stored therein identifications of local systems having countermeasures that can deter a missile from striking an aircraft 10, 20, 30, 40, where the local systems are not located on the aircrafts 10, 20, 30, 40. As an example, a countermeasure launch pad may be located in the vicinity of the CCMS 102 and capable of communicating with the CCMS 102, thereby making its countermeasures available to the CCMS 102 for deterring a missile from striking an aircraft 10, 20, 30, 40. It should be noted that the CCMS available countermeasures database 168 may not be provided if the only countermeasures available to deter a missile threat are located on aircrafts 10, 20, 30, 40.
Each ACS 12, 22, 32, 42 has a structure that is similar to the structure of the CCMS 102 of
The ACS 12 also contains a missile detection system 272 that is capable of detecting a missile threat prior to infliction of damage by the missile. The missile detection system 272 may be one of many different missile detection systems known to those having ordinary skill in the art, for example, but not limited to, the AN/ALQ-212(V) ATIRCMWS, the BAE Counter MANPADS system or others). Preferably, the missile detection system 272 is capable of determining certain characteristics of the missile threat. Examples of such characteristics of the missile threat may include, but are not limited to, missile plume intensity and location of the missile threat in comparison to the aircraft 10 (e.g., vector to threat including azimuth, elevation, range, and time). Of course, other characteristics of the missile threat may be determined by the missile detection system 272.
The storage device 232 located within the ACS 12 has stored therein identification of countermeasures presently available on the aircraft 10 that are capable of being deployed by the aircraft 10 having the ACS 12 therein. This identification is used by the CCMS 102 in deterring a detected missile threat prior to missile detonation, as is explained in detail herein. An identification of the aircraft 10 is also stored within the storage device 232, where the identification of the aircraft 10 is capable of being used by the CCMS 102 to determine a source of a transmission received by the CCMS 102.
Depending on the type of missile detection system 272 provided within the ACS 12, when the missile detection system 272 detects a missile threat, certain characteristics of the missile threat, the identification and characteristics of the aircraft 10 (e.g., roll, horizontal elevation, azimuth northing, and time), and countermeasure availability on the aircraft 10 are immediately transmitted from the ACS 12 to the CCMS 102 via the transceiver 252. The transmission from the ACS 12 to the CCMS 102 and use of information within the transmission is described in further detail herein.
As is shown by block 302, an ACS 12, 22, 32, 42 detects a missile threat and creates a track file. The missile is detected by the missile detection system 272. Preferably, the missile detection system 272 determines information about the missile threat such as, but not limited to, missile plume intensity and location of the missile threat in comparison to the aircraft 10, 20, 30, 40 (e.g., vector to threat including azimuth, elevation, range, and time). Of course, other characteristics of the missile threat may be determined during detection of the missile threat.
The created track file contains the determined missile threat information, identification of the aircraft 10, 20, 30, 40 that detected the missile threat, characteristics of the aircraft 10, 20, 30, 40 such as, but not limited to, aircraft; roll, pitch, and yaw, target; horizontal elevation, azimuth northing and time, and present countermeasure availability on the aircraft 10, 20, 30, 40. Of course other characteristics of the aircraft 10, 20, 30, 40 may also be incorporated into the track file.
The track file is then transmitted from the ACS 12, 22, 32, 42 to the CCMS 102 (block 304). When the track file is received by the CCMS 102 the identification of the aircraft 10, 20, 30, 40 that detected the missile threat and its present countermeasure availability is stored within the ACS available countermeasures database 166. In addition, the determined missile threat information is also stored within the threat characteristics database 162.
As is shown by block 306, a determination is made as to whether more than one track file has been received by the CCMS 102, where each track file is received from a different ACS 12, 22, 32, 42. If more than one track file has been received the tracks are fused (block 308), resulting in comparison of characteristics of the missile threat. During fusion of the track files, information from the track files is combined to provide a detailed description of the missile threat. Specifically, the plume intensities and locations of the missile threat are combined and compared to determine if there is a single missile of concern or multiple missiles. As an example, information describing location of the missile threat may be received from three different ACSs 12, 22, 32, each of which has detected a missile threat. However, after fusing the track files it may be discovered that there are two missiles of concern due to two different detected plume intensities, and comparison of vector to threats, elevations, ranges, and times of the missile threat.
As is shown by block 310, threat typing is then performed to determine the type of missile threat and confidence in the determined threat type from the fused tracks. A known algorithmic theory may be used to determine the type of missile threat and confidence that the missile threat is authentic. As an example, a Bayesian theory, such as the Dempster-Shafer decision theory, may be used to analyze the fused threat track characteristics with false alarm characteristics and known false alarm locations, thereby deriving a type of missile threat and a confidence that the derived type of missile threat is correct. Since one having ordinary skill in the art would know how to use the Dempster-Shafer decision theory, a detailed description of the theory and its use is not provided herein. Of course, other known algorithmic theories may be used to derive a type of missile threat and a confidence that the derived type of missile threat is correct. It should be noted that if there is not more than one tract file being received, threat typing as described above is performed.
As is shown by block 312, when results of threat typing show that a derived threat is authentic, the derived missile threats are prioritized so that the missile most dangerous to a target aircraft is deterred from hitting its target first. Prioritization of the missile threats is performed by searching for each derived missile threat within the threat characteristics database 162. As is mentioned above, the threat characteristics database 162 has stored therein a prioritization rating associated with each missile threat. Therefore, when a derived missile threat is found within the threat characteristics database 162, the associated prioritization rating is determined.
Optionally, when results of threat typing show that the derived threat is authentic, the CCMS 102 may also alert the department of homeland security and/or air traffic control to give notice of the missile threat. Of course other authorities may also be notified of the missile threat so as to ensure that proper actions are taken immediately. In addition, with authenticity of the missile threat assured, reviewing the vector to threat, elevation, range, and time of the missile threat from each ACS 12, 22, 32, 42 may provide a location of the source of the missile threat.
Response management is then performed to address the derived missile threat (block 314). During response management, a countermeasure capable of deterring the derived missile threat is sought within the countermeasure effectiveness database 164. Specifically, the derived missile threat is searched for within the countermeasure effectiveness database 164 to determine what countermeasures are capable of deterring the determined missile threat. During response management, the determined countermeasures are then sought within the ACS available countermeasures database 166 to determine which aircrafts 10, 20, 30, 40 have the determined countermeasures readily available for deployment.
In accordance with an alternative embodiment of the invention, the CCMS available countermeasures database 168 may be searched during response management to determine if any local systems have the determined countermeasures readily available for deployment. As has been mentioned above, such local systems may include a launch pad located local to the CCMS 102 that is capable of launching countermeasures.
As is shown by block 316, the CCMS 102 then transmits a request to a single ACS 12, 22, 32, 42 that is best equipped to deploy the determined countermeasures for purposes of deterring the missile. In addition, if there are multiple missiles launched, the CCMS 102 may transmit different requests to different ACSs 12, 22, 32, 42 that are best equipped to deploy the determined countermeasures. It should be noted, however, that when multiple ACSs are instructed to deploy countermeasures, the decision to use the multiple ACSs takes into consideration that ACSs having a small distance between them may cause interference. Therefore, the CCMS 102 causes selected ACSs that are close together to coordinate deployment of countermeasures to ensure lack of interference.
It should be emphasized that the above-described embodiments of the present invention are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiments of the invention without departing substantially from the spirit and principles of the invention. All such modifications and variations are intended to be included herein within the scope of this disclosure and the present invention and protected by the following claims.
This application claims priority to copending U.S. Provisional Application entitled, “Cooperative Network Centric Counter Manpads Airborne Countermeasures System,” having Ser. No. 60/578,747, filed Jun. 10, 2004, which is entirely incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/US04/43733 | 12/23/2004 | WO | 8/28/2006 |
| Number | Date | Country | |
|---|---|---|---|
| 60578747 | Jun 2004 | US |
