Patent Grant
8279105
Embodiments of the present invention relate to configuring a receiver to execute a dwell.
Detection systems exist for detecting signals generated by emitters which are of interest. For example, there are scanners (e.g., a police scanner) that are capable of scanning a frequency band for transmissions within that frequency band. In the case of a police scanner, channels are scanned sequentially to find a signal of interest. Scanning is achieved by tuning receiver hardware to a particular frequency to observe one or more transmissions within that particular frequency.
There are more sophisticated systems to detect transmitted signals that use other methods for determining signals of interest. For instance, there are what are referred to as Electronic Support Measures/Electronic Intelligence (ESM/ELINT) systems for conducting surveillance (e.g., radar, and other signals across a wide range of frequency spectrums). These systems detect one or more signals produced by emitters (often called “threats”) that are detected and observed.
For example, in a military aircraft or other vehicle, enemy signals (e.g., radar) may be observed that are capable of detecting the vehicle (e.g., an airplane). These threats may need to be determined prior to detection to ensure the safety of the vehicle, and are often observed and classified to identify the particular threat. For example, certain signals may have particular signatures that are indicative of certain types of emitters. Further, there may be a need to detect and identify the location of a threat (e.g., a radar installation) for targeting purposes.
One embodiment is directed to a method of executing a scan strategy in a receiver. The method comprises acts of: receiving configuration settings for a dwell in the scan strategy to be executed by the receiver; configuring the receiver, according to the configuration settings, to execute the dwell; executing the dwell in the receiver; receiving, during execution of the dwell, configuration settings for each dwell in a set of next possible dwells to be executed by the receiver; and storing the configuration settings for each dwell in the set of next possible dwells in a memory of the receiver. Another embodiment is directed to at least one computer readable medium encoded with instructions that, when executed, perform the above-described method.
A further embodiment is directed to receiver for executing a scan strategy. The receiver comprises: an interface for interfacing with a processor; a memory; and at least one controller, coupled to the memory and the interface, that: receives, via the interface, configuration settings for a dwell in the scan strategy to be executed by the receiver; configures the receiver, according to the configuration settings, to execute the dwell; executes the dwell in the receiver; receives via the interface, during execution of the dwell, configuration settings for each dwell in a set of next possible dwells to be executed by the receiver; and stores the configuration settings for each dwell in the set of next possible dwells in the memory.
Often it is desirable to use a receiver to attempt to detect multiple different emitters with different signal characteristics. That is, different emitters may transmit signals in different portions of the frequency spectrum, signals having different pulse widths and/or different pulse repetition intervals, and/or signals having other differing characteristics. As a result, if it desired to detect multiple emitters, the receiver may have to be reconfigured in between listening for particular emitters or sets of emitters. Thus, for example, the receiver may be configured to listen for one emitter or set of emitters and then may be reconfigured to listen for another emitter or set of emitters. A particular receiver configuration is referred to herein as a dwell. Each dwell may have an associated duration and revisit time. The duration of a dwell indicates how long the receiver spends in the configuration associated with the dwell and the revisit time indicates how frequently the dwell is executed. Thus, for example, a dwell with a duration of five milliseconds (ms) and a revisit time of 30 ms would be executed for 5 ms and the re-executed every 30 ms.
In some embodiments, a scan strategy may be computed that defines a set of dwells, each of which has an associated duration and revisit time, to be executed by the receiver to attempt to detect a particular set of emitters. The dwells that form the scan strategy may be selected in any suitable way, as the invention is not limited in this respect. For example, in some embodiments, the dwells that form the scan strategy and their associated durations and revisit times may be selected to attempt to detect a specified set of emitters.
In some embodiments, even after a scan strategy is computed, it may not be possible to determine with complete certainty the series of dwells that will be executed by the receiver. For example, in some situations the next dwell to be executed by the receiver after the currently executing dwell may depend on the results of the currently executing dwell. That is, in some embodiments, if a signal of interest is detected during a dwell, it may be desired to execute a dwell extension for that dwell to further sample the signal. For example, the receiver may be in a vehicle with multiple antennas mounted in various locations on the vehicle (e.g., left side, right side, front, and rear) and may have a separate RF channel for each antenna. If a signal of interest is detected during a dwell, the direction from which the signal originated may be determined and it may be desired to execute a dwell extension, in which the dwell is extended, but each antenna is pointed in the direction of the signal to obtain additional information about the signal, such as phase information and/or any other suitable information. Thus, it may not be possible to determine whether the next dwell to be executed after the currently executed dwell will be a dwell extension for the currently executing dwell or a different dwell.
In addition, in some situations, a signal of interest may be detected during a dwell, but the received signal may be too high power or too low power to be suitable for processing. Thus, it may be desirable to re-execute the dwell, but with the receiver configured to add in additional attenuation or amplification to the received signal. Such a re-executed dwell is referred to herein as a “spawn dwell.” In some embodiments, during a currently executing dwell, it may not be possible to determine whether the next dwell to be executed will be a spawn dwell of the currently executing dwell or a different dwell. Moreover, in some situations, a scan strategy may include dwells that are referred to herein as a “hard time dwells.” A hard time dwell is a dwell which is executed at a specific time (e.g., 14:28:16.250), taking priority over the execution of other dwells. Thus, for example, a hard time dwell may take precedence of a spawn dwell or dwell extension of a currently executing dwell. Further, in some situations, a human operator may have the ability to request execution of a particular dwell. Thus, human interruption of a scan strategy may present challenges in pre-determining the sequence of dwells to be executed by a receiver.
The examples above are merely a few examples of reasons why the sequence of dwells to be executed by a receiver may be non-deterministic. Applicants have appreciated that this sequence may be non-deterministic for other reasons and the invention is not limited to use with scan strategies that are non deterministic for the reasons described above. Moreover, in some embodiments, the sequence of dwells in the scan strategy may be deterministic and the invention is not limited to use with non-deterministic dwell sequences.
In the example above, vehicle 101 has four antennas. However, the invention is not limited in this respect as a vehicle in which the receiver is situated may have any suitable number of antennas. Further, vehicle 101 may be any suitable type of vehicle, such as, for example, an aircraft, a land vehicle, a marine vehicle (e.g, a vessel or submarine), and/or any combination thereof.
In
Applicants have appreciated that there may be a delay in between the end of execution of one dwell by the receiver and the beginning of the execution of the next dwell. This delay is, in part, a result of the time taken to configure the receiver for the next dwell. The period in between execution of dwells is referred to herein as “shadow time.” The shadow time between dwells may reduce the efficiency of the receiver in detecting emitters. That is, while the receiver is being configured in between execution of dwells, it is not being utilized to detect signals. Thus, larger shadow times decrease utilization of the receiver, and as the utilization of the receiver decreases the time taken to detect an emitter and report its detection (e.g., to a pilot of a vehicle in which the receiver is situated) increases.
Applicants have further appreciated that a large portion of the shadow time between dwells results from time taken to send configuration commands from processor 105 to receiver 103. These commands may be, for example, configuration commands for antenna switch settings, frequency tuning settings, time settings (e.g., dwell duration), threshold settings (e.g., minimum pulse width reject threshold), attenuation and amplification settings, and/or any other suitable receiver settings. In some situations, a large number of commands may be sent from processor 105 to receiver 103 to configure receiver 103 for a particular dwell and the shadow time may be large.
One embodiment of the invention is directed to reducing shadow time between dwells by pre-loading dwell configuration settings in the receiver during execution of the current dwell. This may be done in any suitable way, as the invention is not limited in this respect. By pre-loading the configuration settings for subsequent dwells in the receiver during execution of the current dwell, the shadow time may be reduced, as the configuration settings for the next dwell may be loaded into the receiver prior to completion of the currently executing dwell. As a result, after completing execution of a dwell, the receiver need not wait to receive configuration commands from the process before beginning execution of the next dwell.
As discussed above, in some embodiments, it may not be possible to determine which dwell is to be executed next until after the currently executing dwell completes. Thus, in some embodiments, a set of possible dwells to be executed after the currently executing dwell may be determined and the configuration settings for these dwells may be sent to the receiver, for example, during the currently executing dwell. When execution of the currently executing dwell completes, it may be determined which dwell the receiver should execute next. If the receiver configuration settings are already loaded in the receiver, the receiver may be instructed to execute the dwell. Thus, the receiver may execute the dwell without having to wait to receive configuration information for the dwell.
For example, as shown in
Controller 201 may be implemented in any suitable way, as the invention is not limited in this respect. For example, controller 201 may be implemented in hardware, software, firmware, or any combination thereof.
Table 1 below is a table representing an instruction cache 211 having six slots (i.e., slots A-F). In the example below, each slot is identified by a letter (A-F). However, the invention is not limited in this respect, as a slot may be identified or addressed in any suitable way.
Each slot stores a dwell, which may be either an initial dwell or a dwell extension. As discussed above, a dwell extension is an extension of a dwell that may be used to focus in on a specific field of view. Thus, for example, the dwell in Slot A is an initial dwell with a center frequency of 15 GHz and a field of view of 360 degrees. The method used to determine the angle of arrival of a signal is amplitude DF. The dwells in slots B-E are dwell extensions of dwell A, with each focusing in on a different field of view. Thus, for example, if a signal of interest is detected in a particular portion of the field of view during the initial dwell, the dwell extension corresponding to that portion of the field of view may be executed to obtain additional and/or more precise information about the received signal. The dwell in slot F is the next dwell scheduled for execution after dwell A, which is an initial dwell with a center frequency of 25 GHz.
In some embodiments, the pre-loading of dwells into the receiver may occur as follows. Initially, the receiver executes the dwell in Slot A. The results of this dwell indicate that the only signals of interest are in the field of 90-180 degrees and 180-270 degrees (i.e., the fields of view of slots C and D, respectively). Thus, the next dwells scheduled for execution may be the dwells in slots C, D, and F, sequentially. Because these dwells are already loaded into instruction cache 211 of the receiver, the receiver need not await configuration information for these dwells from the controller after the dwell in slot A has completed execution.
Slots A, B, and E may be released and the memory in instruction cache 211 used for these slots may be freed to store other dwells. Slots A, B, and E may be then be populated with the dwell extensions for the initial dwell in slot F. This may be done while the dwell in slot C, the dwell in slot D, and/or the dwell in slot F are being executed by the receiver. After slot C completes execution, the receiver is instructed to execute the dwell in slot D and the dwell in slot C may be released and freed to store another dwell. Slot C may then be populated with a dwell extension for the dwell in Slot F. This may be done while the dwell in slot D and/or the dwell in slot F are being executed by the receiver.
After the dwell in slot D completes execution, the receiver is instructed to execute the dwell stored in slot F. The dwell in slot D is released and the associated memory in instruction cache 211 is freed to store another dwell. Slot D may then be populated by the next initial dwell scheduled to run after slot F. This may be done while the dwell in slot F is executing.
This process for populating instruction cache 211 with the next dwell extensions and next initial dwell may be repeated for the remaining dwells in the scan strategy. In the example above, instruction cache 211 has six slots and each initial dwell has four extension dwells. However, the invention is not limited in this respect, as the receiver instruction cache may have any suitable number of slots and each initial dwell may have any suitable number of dwell extensions. For example, if the vehicle in which the receiver is situated has eight antennas distributed around the vehicle, each dwell may have eight dwell extensions, each with a field of view of 45 degrees.
Any suitable algorithm may be used to pre-load dwells into the instruction cache of the receiver, as the invention is not limited in this respect.
Next, a check is performed to see if there are any dwell extension segments for the current dwell. If so, for each dwell extension segment, a check is performed to determine if the segment is loaded in the receiver and, if not, each dwell extension segment is loaded into the receiver. Once all segments of the current dwell are loaded in the receiver, the initial segment is scheduled for execution and the receiver executes the initial segment. When execution of the initial segment is complete, the receiver issues a notification that the initial segment is complete. The initial segment is processed and, based on this processing, it is determined if any of the dwell extension segments should run. If it is determined that an extension segment should execute, the segment is scheduled and executed. While the segment is executing, it may be determined if any other extension segments should be run and, if so, these segments may be schedule for execution when the receiver becomes available. If it is determined that an extension segment is not to be run, the slot in the receiver's instruction cache used to store the dwell may be freed.
While the initial dwell segment of the current dwell is executing, prior to execution of any extension segments, a check may be performed to determine if the next dwell exists and, if so, the initial segment of this dwell may be loaded into the receiver (if it has not already been loaded). When the segment is loaded, a check may be performed to determine if there are any dwell extensions for the next dwell that are not loaded and, if so, these dwell extensions may be loaded into the receiver during execution of the current dwell.
It should be appreciated that the flow chart of
The above-described embodiments of the present invention can be implemented in any of numerous ways. For example, the embodiments may be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer or distributed among multiple computers. It should be appreciated that any component or collection of components that perform the functions described above can be generically considered as one or more controllers that control the above-discussed functions. The one or more controllers can be implemented in numerous ways, such as with dedicated hardware, or with general purpose hardware (e.g., one or more processors) that is programmed using microcode or software to perform the functions recited above. The one or more controllers may be included in one or more host computers, one or more storage systems, or any other type of computer that may include one or more storage devices coupled to the one or more controllers.
In this respect, it should be appreciated that one implementation of the embodiments of the present invention comprises at least one computer-readable medium (e.g., a computer memory, a floppy disk, a compact disk, a tape, etc.) encoded with a computer program (i.e., a plurality of instructions), which, when executed on a processor, performs the above-discussed functions of the embodiments of the present invention. The computer-readable medium can be transportable such that the program stored thereon can be loaded onto any computer system resource to implement the aspects of the present invention discussed herein. In addition, it should be appreciated that the reference to a computer program which, when executed, performs the above-discussed functions, is not limited to an application program running on a host computer. Rather, the term computer program is used herein in a generic sense to reference any type of computer code (e.g., software or microcode) that can be employed to program a processor to implement the above-discussed aspects of the present invention.
It should be appreciated that in accordance with several embodiments of the present invention wherein processes are implemented in a computer readable medium, the computer implemented processes may, during the course of their execution, receive input manually (e.g., from a user).
The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having,” “containing”, “involving”, and variations thereof herein, is meant to encompass the items listed thereafter and additional items.
Having described several embodiments of the invention in detail, various modifications and improvements will readily occur to those skilled in the art. Such modifications and improvements are intended to be within the spirit and scope of the invention. Accordingly, the foregoing description is by way of example only, and is not intended as limiting.
This application claims the benefit under 35 U.S.C. §119(e) to commonly-owned U.S. provisional patent application Ser. No. 60/879,912, entitled METHODS AND APPARATUS FOR USING A RECEIVER, filed on Jan. 10, 2007. This provisional patent application is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3277468 | Caspers | Oct 1966 | A |
| 3922676 | O'Berry et al. | Nov 1975 | A |
| 4025920 | Reitboeck et al. | May 1977 | A |
| 4040054 | Overman | Aug 1977 | A |
| 4695790 | Mathis | Sep 1987 | A |
| 4726050 | Menich et al. | Feb 1988 | A |
| 4750215 | Biggs | Jun 1988 | A |
| 4845682 | Boozer et al. | Jul 1989 | A |
| 4860318 | Shaw et al. | Aug 1989 | A |
| 4862175 | Biggs et al. | Aug 1989 | A |
| 4922256 | Brandstetter | May 1990 | A |
| 5061930 | Nathanson et al. | Oct 1991 | A |
| 5122801 | Hughes | Jun 1992 | A |
| 5285209 | Sharpin et al. | Feb 1994 | A |
| 5293114 | McCormick et al. | Mar 1994 | A |
| 5361069 | Klimek et al. | Nov 1994 | A |
| 5363103 | Inkol | Nov 1994 | A |
| 5396250 | Tsui et al. | Mar 1995 | A |
| 5563806 | Barry et al. | Oct 1996 | A |
| 5583505 | Andersen et al. | Dec 1996 | A |
| 5610609 | Rose | Mar 1997 | A |
| 5727204 | Greene, VII | Mar 1998 | A |
| 5884294 | Kadar et al. | Mar 1999 | A |
| 6163297 | Rose | Dec 2000 | A |
| 6177902 | Huntley et al. | Jan 2001 | B1 |
| 6201493 | Silverman | Mar 2001 | B1 |
| 6313781 | Lee | Nov 2001 | B1 |
| 6313794 | Rose | Nov 2001 | B1 |
| 6388604 | Lee | May 2002 | B1 |
| 6507308 | Ono et al. | Jan 2003 | B1 |
| 6842137 | Gounalis | Jan 2005 | B2 |
| 6859160 | Gounalis | Feb 2005 | B1 |
| 6859161 | Bricker et al. | Feb 2005 | B1 |
| 6873284 | Gounalis | Mar 2005 | B2 |
| 6894634 | Gounalis | May 2005 | B2 |
| 6894635 | Gounalis | May 2005 | B2 |
| 6917325 | Gounalis | Jul 2005 | B2 |
| 6989780 | Gounalis | Jan 2006 | B2 |
| 7038611 | Gounalis | May 2006 | B2 |
| 7068209 | Gounalis | Jun 2006 | B2 |
| 7109909 | Gounalis | Sep 2006 | B2 |
| 7148835 | Bricker et al. | Dec 2006 | B1 |
| 7176826 | Gounalis | Feb 2007 | B2 |
| 7193555 | Gounalis | Mar 2007 | B2 |
| 7236119 | Gounalis | Jun 2007 | B2 |
| 7248203 | Gounalis | Jul 2007 | B2 |
| 7348919 | Gounalis | Mar 2008 | B2 |
| 7358887 | Gounalis | Apr 2008 | B2 |
| 7369082 | Stagliano et al. | May 2008 | B2 |
| 7482967 | Beharrell | Jan 2009 | B2 |
| 20040113831 | Gounalis | Jun 2004 | A1 |
| 20040116090 | Gounalis | Jun 2004 | A1 |
| 20040119630 | Gounalis | Jun 2004 | A1 |
| 20040130476 | Gounalis | Jul 2004 | A1 |
| 20040130477 | Gounalis | Jul 2004 | A1 |
| 20040130478 | Gounalis | Jul 2004 | A1 |
| 20040135717 | Gounalis | Jul 2004 | A1 |
| 20050052311 | Gounalis | Mar 2005 | A1 |
| 20050052312 | Bricker et al. | Mar 2005 | A1 |
| 20060097904 | Gounalis | May 2006 | A1 |
| 20060176208 | Gounalis | Aug 2006 | A1 |
| 20060227035 | Gounalis | Oct 2006 | A1 |
| 20060290560 | Bricker et al. | Dec 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20080180309 A1 | Jul 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60879912 | Jan 2007 | US |
