Patent Application
20230056587
This disclosure relates generally to laser-guided devices and processes. More specifically, this disclosure relates to coordination of pulse repetition frequency (PRF) codes in laser-guided applications.
The dynamics of ground-to-ground laser-guided weapons applications pose a number of specific challenges that are not present in more traditional air-to-ground laser-guided weapons applications. For example, individual soldiers may require their own individual pulse repetition frequency (PRF) codes in order to deconflict their weapon designations from other soldiers' weapon designations. However, existing U.S. Air Force laser-guided weapon policies do not provide for such arrangements and include many other restrictions that make these policies impossible to use, despite the proliferating use of laser-guided weapons.
This disclosure relates to coordination of pulse repetition frequency (PRF) codes in laser-guided applications.
In a first embodiment, a method includes removably coupling a projectile interface of a dongle to a dongle interface of a projectile. The method also includes loading a dongle code from the dongle onto the projectile. The dongle code identifies a PRF code to be recognized by the projectile.
In a second embodiment, a projectile assembly includes a projectile and a dongle. The projectile includes a dongle interface, and the dongle includes a projectile interface and a processor. The projectile interface is configured to be removably coupled to the dongle interface. The processor is configured to load a dongle code onto the projectile. The dongle code identifies a PRF code to be recognized by the projectile.
In a third embodiment, an apparatus includes a projectile interface and a processor. The projectile interface is configured to be removably coupled to a dongle interface of a projectile. The processor is configured to load a dongle code onto the projectile. The dongle code identifies a PRF code to be recognized by the projectile.
Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.
For a more complete understanding of this disclosure, reference is made to the following description, taken in conjunction with the accompanying drawings, in which:
Pulse repetition frequency (PRF) code technology provides for pinpoint accuracy and has been successfully used by the U.S. armed forces since the 1970s. Applications for PRF coding are often found in air-to-ground weapons, such as in Paveway, Hellfire, and Stormbreaker weapons systems. The tactical use of laser-guided weapons in surface-to-surface combat is relatively new, and there are no known solutions for using laser-guided weapons in ground combat at this time other than U.S. Air Force techniques, which are not designed for use by ground forces. Nevertheless, there is much interest in using laser-guided weapon systems during ground combat. However, existing PRF-code concepts of deployment, communication, and security (while suitable for Air Force deconflicted air-to-ground battlespace designation) cannot be directly applied to modern surface-to-surface warfare. More information about laser-guided weapon procedures can be found in Joint Laser Designation Procedures (JLASER), Joint Publication No. 3-09.1, June 1991 (which is hereby incorporated by reference in its entirety).
Current Air Force PRF code distribution and control procedures are not acceptable for close combat operations for many reasons. For instance, the level of distribution and control may be at much higher levels than needed for smaller ground combat units. Also, ground combat often involves multiple users engaging multiple targets simultaneously within the same engagement area, as opposed to air-to-ground combat that may not have multiple users simultaneously engaging multiple targets in an engagement area. Furthermore, updating codes for ground-based units often needs to occur at a faster rate due to faster tactical dynamics. In addition, there may be a much higher chance of weapons falling into the wrong hands in close combat environments.
As mentioned earlier, the dynamics of ground-to-ground laser-guided weapons applications pose a number of specific challenges that are not present in more traditional air-to-ground laser-guided weapons applications. For example, individual soldiers may require their own individual PRF codes in order to deconflict their weapon designations from other soldiers' weapon designations. One or more PRF codes set on a designator pointed at a specific target need to match one or more PRF codes on a specific weapon for a successful deconflicted engagement. The designation can be made by a soldier firing a laser-guided munition or by another party (in which case the PRF codes need to be agreed upon prior to being issued).
There are several reasons (related to weapon security) that make it necessary or desirable to confidentially maintain the PRF codes of specific users or specific weapons. In order to accommodate multiple weapon deconflictions while maintaining weapon security, each soldier is often issued a custom key with a soldier-specific identification (ID) and at least one PRF code. This data can be programmed into the key prior to field deployment, although it may also be changed in the field during deployment using an application on a companion electronic device. Prior to use, a projectile can be pre-programmed with a soldier-specific ID or a list of soldier-specific IDs. During initialization, for example, a soldier can insert his or her key into the projectile, and the projectile receives the soldier-specific ID and the PRF code(s) from the key and stores them in a memory. The projectile is now user-matched and PRF-coded. A laser designator used by at least one soldier can be set to the same PRF code(s), which are known to the user or “buddy” designator, and the projectile can be fired and attempt to strike whatever target or area is designated using the PRF code(s). Note that a key can be removed and re-used with multiple projectiles, and the key can be pre-programmed with multiple users (such as everyone in a squad). The key may also be reprogrammed in the field using a companion device, such as when current PRF codes are jeopardized and need to be changed. Certain protections are pre-built in the key that can prevent unauthorized use.
This disclosure provides techniques for committing specific weapons or other projectiles to specific users in real-time to deconflict a ground combat battlespace or other environment. As described in more detail below, these techniques permit more flexible PRF code assignments while providing suitable security. These techniques thereby help to overcome limitations of current laser-guided weapon systems through the use of PRF code management and weapon security.
In some embodiments, the SAL detector 54 may include four quadrants A, B, C, D (although other detector configurations may be used). Each quadrant produces a corresponding signal A, B, C, D in response to the laser power in the laser spot 52 incident upon that quadrant. The guidance signal ΔX indicates an imbalance between the laser power incident upon the left (quadrants A and B) and right (quadrants C and D) halves of the SAL detector 54, and the guidance signal ΔY indicates an imbalance between the laser power incident upon the top (quadrants A and C) and bottom (quadrants B and D) halves of the SAL detector 54. In some cases, the SAL detector 54 may include an A/D converter that converts analog signals to digital signals. Note that the terms “left”, “right”, “top”, and “bottom” here refer to the detector and do not imply any physical orientation within the projectile 40. When the laser spot 52 is centered on the SAL detector 54, the signals A, B, C, D may be essentially equal, and the guidance signals ΔX and ΔY may both be zero or nearly zero.
The position of the SAL seeker 46 may be fixed within the projectile 40, which may be referred to as “body fixed.” For example, the SAL seeker 46 may be disposed within the projectile 40 such that an optical axis of the SAL seeker 46 is aligned with a longitudinal axis of the projectile 40. In this case, the laser spot 52 may be centered on the SAL detector 54 when the longitudinal axis of the projectile 40 is pointed directly at a designated target 80. In other cases, the SAL seeker 46 may be mounted on a gimbal or other structure within the projectile 40 such that the optical axis of the SAL seeker 46 can be rotated with respect to the longitudinal axis of the projectile 40. In those cases, the laser spot 52 may be centered on the SAL detector 54 when the optical axis of the SAL seeker 46 is pointed directly at a designated target 80 without the longitudinal axis of the projectile 40 necessarily being pointed directly at the designated target 80.
In a pre-launch mode, the laser-guided projectile 40 can use a dongle code 58 loaded from the dongle 12 in order to be initialized. In some embodiments, the flight computer 48 of the laser-guided projectile 40 is programmed to not launch without the dongle code 58 or to not launch while the dongle code 58 is not stored on the laser-guided projectile 40. The projectile interface 13 of the dongle 12 can be inserted into the dongle interface 41, and the dongle 12 is a portable storage medium that interfaces with the laser-guided projectile 40. The dongle 12 is programmed to store at least one PRF code or dongle code 58 for the laser-guided projectile 40. One or more dongle codes 58 on the dongle 12 are matched to one or more designator codes 64 emitted from one or more designators 60 that mark one or more targets 80. In some embodiments, the dongle 12 can be designed for use by a gloved hand and in field environments. Also, in some embodiments, the dongle 12 can be used on all counter communications system (CCS) weapons.
The projectile interface 13 and the dongle interface 41 may represent physical and electrical interfaces that can be exclusive to the projectile interface 13 of the dongle 12 and the dongle interface 41 of the projectile 40. Also, in some embodiments, the dongle 12 can be programmed for use with a limited number of projectiles or authorized initializations. For example, a dongle 12 can be limited to initializing five laser-guided projectiles 40. The amount of initializations for a dongle 12 can be programmed prior to deployment, wirelessly updated, or programmed using the companion electronic device 14. Further, in some embodiments, the dongle 12 can be programmed for use during a limited amount of time. For instance, a dongle 12 can be limited to initializing laser-guided projectiles 40 within a twelve-hour time span. The amount of authorized time for a dongle 12 can be programmed prior to deployment, wirelessly updated, or programmed using the companion electronic device 14. In addition, in some embodiments, the dongle 12 can be encrypted using a military-level encryption.
In some embodiments, the dongle 12 may require personal authentication during setup. For example, the personal authentication may represent a pin code or other code that is entered prior to or after inserting the dongle 12 into the projectile 40. In particular embodiments, the pin code or other code can be entered from the companion electronic device 14 while the dongle 12 is operatively coupled to the companion electronic device 14. The personal authentication can also or alternatively include native authentications on the companion electronic device 14 or the dongle 12. The personal authentication can include any suitable type of authentication, such as a thumbprint, eye scan, password, passcode, face scan, or any other method of authentication. In some embodiments, the personal authentication is performed by loading a user-specific ID to the projectile 40. The flight computer 48 can store a list of authorized users and can compare the user-specific ID to the user IDs on the list of authorized users. Once authorization is confirmed, the one or more dongle codes 58 can be automatically loaded into the flight computer 48 to initialize the projectile 40.
The dongle 12 can further include pre-launch data 66, and the pre-launch data 66 can be loaded onto the flight computer 48 using the dongle code 58 so that the flight computer 48 can process or otherwise use the pre-launch data 66. The pre-launch data 66 may include various fields, such as fields for guidance mode (air-to-air, air-to-ground, ground-to-ground, etc.), fuse timing mode (airburst, point detonation, delayed detonation, etc.), fuse detonation mode (blast fragmentation, penetration, etc.), range to target, target location, lock mode (lock on before launch, lock on after launch, etc.), or atmospheric conditions (temperature, wind, humidity, etc.). The dongle 12 may include actual data or indices to data tables stored within the flight computer 48.
In a launch mode, a laser designator 60 illuminates a target 80 with a PRF-coded laser beam 62. The laser-guided projectile 40 is pointed at the target 80 to acquire the laser EMR scattered from the target 80 and lock on before launch or reorient during or after launch. Once locked, the projectile is fired or reoriented and ideally travels to or near the target 80 and detonates. The scattered EMR in the seeker's field-of-view is captured and formed into a spot on the SAL detector 54, which in turn generates one or more (such as four) guidance signals. The signal processor 56 executes a portion of the program code 59 that extracts the designator code 64 from the PRF-coded laser beam 62 and generates one or more guidance signals indicative of the position of the laser spot 52 on the SAL detector 54. The flight computer 48 verifies the designator code 64, calculates a bearing or flight path to the target 80 from the guidance signals, and issues control signals to control the aerodynamic control surfaces 44 in order to guide the projectile 40 to the target 80.
In some embodiments, the target 80 and the PRF-coded laser beam 62 are out of sight from a launch location of a projectile 40. In these instances, a proxy designator 60 is used to illuminate a target 80. For example, the proxy designator 60 may be installed on an unmanned aerial vehicle (UAV) flying within a projectile range or a separate designator 60 with a “forward operator,” such as a scout. In these cases, the projectile 40 can be launched in the general direction of the target 80. While in flight, the projectile 40 scans the ground for the reflected PRF coded laser beam 62 with a matching designator code 64 that is illuminating the target 80. Once the target 80 is identified, the projectile 40 can adjust course and proceed to the target 80.
When multiple designators 60 are deployed, the flight computer 48 can monitor different PRF encoded laser beams 62 that are projected onto different targets 80. The designator codes 64 from the different PRF encoded signals can each be compared to the dongle code(s) 58 loaded from the dongle 12. When a designator code 64 from one of the PRF laser beams 62 matches the dongle code(s) 58 loaded from the dongle 12, the flight computer 48 can identify the target 80 and adjust a flight path to the target 80. The deconfliction of the battlespace is a responsibility of the operators.
The flight computer 48 receives the designator code(s) 64 read from the PRF encoded laser beam(s) 62 and compares the designator code(s) 64 with the dongle code(s) 58 loaded from the dongle 12. When a designator code 64 matches a dongle code 58, the flight computer 48 adjusts the flight path of the laser-guided projectile 40. In some embodiments, the designator code 64 can include a four-digit code. In particular embodiments, the four-digit code is programmed into the designator 60 and the dongle 12 prior to deployment. The four-digit code can be unique for a dongle 12. However, multiple codes can be loaded onto the dongle 12 to associate the dongle 12 with different designators 60. While multiple codes may be loaded onto the dongle 12 before deployment, only a single dongle code 58 may loaded into a flight computer 48 in some embodiments. A default dongle code 58 can be set that is associated with the operator and/or specific designator 60. In order to change the dongle code 58 that is loaded to the flight computer 48, an alternate dongle code 58 can be selected, such as on an interface of the dongle 12 or the companion electronic device 14. The default dongle code 58 may be used in situations where an alternate dongle code 58 has not been selected.
In some embodiments, an operator can be issued a secured companion electronic device 14. The companion electronic device 14 can be used to change the dongle code 58 prior to or during deployment, such as by entering a new four-digit code on the companion electronic device 14. The companion electronic device 14 can also be used to select a specific dongle code 58 from a list of codes preloaded onto the dongle 12 before deployment. The companion electronic device 14 can further communicate with the dongle 12 through a compatible interface, over a wired connection, and over a wireless connection.
Note that once the laser-guided projectile 40 is initialized, the dongle 12 can be removed. In this way, the dongle code 58 on the dongle 12 can be used for different or multiple laser-guided projectiles 40.
As shown in
Functionally, the program code 59 implements first and second difference circuits that generate the guidance signal ΔX as an imbalance between the laser power incident upon the left (quadrants A and B) and right (quadrants C and D) halves of the detector and the guidance signal ΔY as an imbalance between the laser power incident upon the top (quadrants B and C) and bottom (quadrants A and D) halves of the detector. The program code 59 also implements a summing circuit that sums the signals generated by the A, B, C and D quadrants into a single PRF-coded signal and a signal demodulator that extracts the designator code 64 and any additional data. In some embodiments, the existing SAL seeker 46 may include SAL seeker program code 88 that performs the guidance functions of extracting the designator code 64 and generating the ΔX, ΔY guidance signals. Data extraction program code 90 can be loaded into the signal processor's memory to upgrade the SAL seeker 46 in order to provide a communication interface that extracts extra data from the PRF-coded beam and provides the data to the flight computer 48.
Although
Once the first target 212a is identified, the soldier 200 inserts his or her dongle 12 into a first projectile 210a. The flight computer 48 of the first projectile 210a has authorization information loaded prior to deployment. The flight computer 48 compares the pre-loaded authorization information with authorization information loaded on the dongle 12. In some embodiments, the pre-loaded authorization information in the flight computer 48 is compared to authorization information on a companion electronic device 14 issued to the soldier 200 prior to deployment. In this manner, if the dongle 12 or companion electronic device 14 was recovered by enemy combatants or one of the targets, the dongle 12 or companion electronic device 14 can remotely have the authorization removed. For example, the soldier 202 may notice that the companion electronic device 14 or the dongle 12 related to the first soldier 200 has been compromised, such as through capture, death, injury, retreat, etc. of the soldier 200. The soldier 202 can relay the information over a companion electronic device 14 back to base, and the base can wirelessly deactivate the companion electronic device 14 of the soldier 200.
Once the dongle 12 is authorized, the dongle code 58 (AAAA) is loaded into the flight computer 48, and the first projectile 210a is initialized. The first projectile 210a can be launched when suitable to the soldier 200. The designator 60 emits a first PRF-coded laser beam 208a encoded with the designator code 64 (AAAA) that matches the dongle code 58 (AAAA). As a result, the first projectile 210a travels to the first target 212a based on the first PRF-coded laser beam 208a including a matching designator code 64 (AAAA).
Once the second target 212b is identified, the soldier 202 inserts his or her dongle 12 into a second projectile 210b. The same process described above with reference to the first projectile 210a may occur in the second projectile 210b. Once the dongle 12 is authorized, the dongle code 58 (BBBB) is loaded into the flight computer 48, and the second projectile 210b is initialized. The second projectile 210b can be launched when suitable to the soldier 202. The designator 60 for the soldier 202 emits a second PRF-coded laser beam 208b encoded with a designator code 64 (BBBB) that matches the dongle code 58 (BBBB), which is coupled into the projectile's SAL seeker 46. The second projectile 210b travels to the second target 212b based on the second PRF-coded laser beam 208b.
In some cases, both the first PRF-coded laser beam 208a and the second PRF-coded laser beam 208b are simultaneously projected at one or more targets 80 in a general area within an optic field of view for a projectile 40. When this occurs, the first projectile 210a and the second projectile 210b can travel to the correct targets based on the designator code 64 (AAAA and BBBB, respectively) matching the respective dongle code 58 (AAAA and BBBB, respectively).
A soldier 204 can receive a communication 218 from a soldier 214 that a third target 212c is identified using a UAV 216 including a designator 60. For example, the soldier 214 may be an operator of the UAV 216 and may perform scouting functions for the soldiers 200-206. The soldier 214 can identify the third target 212c that is out of view from the soldiers 200-206, such as through optical sensors installed on the UAV 216. The soldier 214 can communicate 218 with the soldier 204 to initialize and launch a third projectile 210c. At this point, the soldier 214 can transmit a dongle code 58 (CCCC) to the dongle 12 or companion electronic device 14 of the soldier 204. In some embodiments, this transmission may identify which dongle code 58 (CCCC) to use in conjunction with the designator 60 on the UAV 216. In some embodiments, the soldier 214 can transmit the dongle code 58 (CCCC) corresponding to the dongle 12 of the soldier 204 to the UAV 216. The UAV 216 can emit a third PRF-coded laser beam 208c encoded with a designator code 64 (CCCC) that matches the dongle code 58 (CCCC) for the third projectile 210c.
The UAV 216 uses a laser designator to paint the third target 212c with a third PRF-coded laser beam 208c. The soldier 204 can aim the third projectile 210c in the direction of the third target 212c and launch the third projectile 210c. While in flight, the third projectile 210c monitors the ground to acquire the scatter EMR including the designator code 64 (CCCC) corresponding to the loaded dongle code 58 (CCCC). The flight computer 48 verifies the designator code 64 (CCCC) by matching it to the dongle code 58 (CCCC) and reorients the third projectile 210c towards the scatter EMR with the matching designator code 64 (CCCC). The UAV 216 holds the third PRF-coded laser beam 208c on the third target 212c until impact, and the SAL seeker 46 locks onto and tracks the position of the spot. The flight computer 48 processes the guidance signals provided by the SAL seeker 46 to control the aerodynamic surfaces and direct the third projectile 210c to impact the painted third target 212c.
A designator soldier 222 can be a scout for soldiers 200-206 at a forward elevated position, and the designator soldier 222 can identify a fourth target 212d. Because the designator soldier 222 is separated from other soldiers 200-206, the soldier 222 firing on the fourth target 212d would expose the forward elevated position and may compromise the soldier 222. In order to not expose the designator soldier 222 to enemy combatants, the designator soldier 222 can transmit a signal 224 to coordinate firing on the fourth target 212d with the soldier 206. At this point, the soldier 222 can transmit a dongle code 58 (DDDD) to the dongle 12 or companion electronic device 14 of the soldier 206 that corresponds to the designator code 64 (DDDD) of the designator 60 with the soldier 222. In some embodiments, this transmission may identify which dongle code 58 (DDDD) to use for the fourth projectile 210d in conjunction with the designator code 64 (DDDD) of the designator 60 with the soldier 222. The designator 60 of the soldier 222 emits a fourth PRF-coded laser beam 208d encoded with a designator code 64 (DDDD) that matches the dongle code 58 (DDDD) for the fourth projectile 210d.
The designator soldier 222 uses a laser designator to paint the fourth target 212d with a fourth PRF-coded laser beam 208d. The soldier 206 can aim the fourth projectile 210d in the direction of the fourth target 212d and launch the fourth projectile 210d. While in flight, the fourth projectile 210d monitors the ground to acquire the scatter EMR including the designator code 64 (DDDD) corresponding to the loaded dongle code 58 (DDDD). The flight computer 48 verifies the designator code 64 (DDDD) by matching it to the dongle code 58 (DDDD) and reorients the fourth projectile 210d toward the scatter EMR including the designator code 64 (DDDD). The soldier 222 holds the fourth PRF-coded laser beam 208d on the fourth target 212d until impact, and the SAL seeker 46 locks onto and tracks the position of the spot. The flight computer 48 processes the guidance signals provided by the SAL seeker 46 to control the aerodynamic surfaces and direct the fourth projectile 210d to impact the painted fourth target 212d.
Although
As shown in
The memory 310 and a persistent storage 312 are examples of storage devices 304, which represent any structure(s) capable of storing and facilitating retrieval of information (such as data, program code, and/or other suitable information on a temporary or permanent basis). The memory 310 may represent a random access memory or any other suitable volatile or non-volatile storage device(s). The persistent storage 312 may contain one or more components or devices supporting longer-term storage of data, such as a read only memory, hard drive, Flash memory, or optical disc.
The communications unit 306 supports communications with other systems or devices. For example, the communications unit 306 can include a network interface card or a wireless transceiver facilitating communications over a wired or wireless network. The communications unit 306 may support communications through any suitable physical or wireless communication link(s).
The I/O unit 308 allows for input and output of data. For example, the I/O unit 308 may provide a connection for user input through a keyboard, keypad, touchscreen, or other suitable input device. The I/O unit 308 may also send output to a display or other suitable output device. Note, however, that the I/O unit 308 may be omitted if the device 300 does not require local I/O, such as when the device 300 can be accessed remotely or operated autonomously.
In some embodiments, the instructions executed by the processing device 302 can include instructions that implement all or portions of the functionality of the dongle 12, the companion electronic device 14, the flight computer 48, or the designator 60 described above. For example, the instructions executed by the processing device 302 can include instructions for coordinating PRF codes in laser-guided weapon applications as described above or other applications.
Although
In some embodiments, various functions described in this patent document are implemented or supported by a computer program that is formed from computer readable program code and that is embodied in a computer readable medium. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive (HDD), a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable storage device.
It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer code (including source code, object code, or executable code). The term “communicate,” as well as derivatives thereof, encompasses both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrase “associated with,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
The description in the present disclosure should not be read as implying that any particular element, step, or function is an essential or critical element that must be included in the claim scope. The scope of patented subject matter is defined only by the allowed claims. Moreover, none of the claims invokes 35 U.S.C. § 112(f) with respect to any of the appended claims or claim elements unless the exact words “means for” or “step for” are explicitly used in the particular claim, followed by a participle phrase identifying a function. Use of terms such as (but not limited to) “mechanism,” “module,” “device,” “unit,” “component,” “element,” “member,” “apparatus,” “machine,” “system,” “processor,” or “controller” within a claim is understood and intended to refer to structures known to those skilled in the relevant art, as further modified or enhanced by the features of the claims themselves, and is not intended to invoke 35 U.S.C. § 112(f).
While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.
