The present disclosure relates to an identification friend or foe (IFF) system and an IFF method.
Identification friend or foe (IFF) systems include beacons capable of emitting near infrared (IR) signals used in conjunction with IF viewing equipment to identify operational active ground forces, from individuals to groups of soldiers. As time has progressed, enemies have acquired examples of equipment used by friendly force organizations and made copies of the beacons that are capable of emitting IR signals to be detected by the friendly force organizations. Improvements to IFF systems are therefore needed to improve security.
According to a first aspect of embodiments of the present disclosure, an interrogation device is provided. The interrogation device includes an emitter configured to emit an infrared (IR) inquiry signal to a target beacon to determine if the target beacon is associated with a friendly entity. The interrogation device also includes a viewing device, configured to view IR signals, through which an IR response beacon signal from the target beacon is viewed. The viewing device is configured to output a signal having a signal pattern of a response beacon signal expected from a beacon associated with the friendly entity, so that the target beacon is determined to be associated with the friendly entity if the response signal pattern of the target beacon matches the expected signal pattern in the viewing device.
According to a second aspect of embodiments of the present disclosure, a method for an interrogation device for determining whether a target beacon is associated with a friendly entity is provided. The method includes transmitting, by the interrogation device, an infrared (IR) inquiry signal to the target beacon. The method also includes, in response to receiving an IR response beacon signal from the target beacon, outputting, by a viewing device on the interrogation device configured to view IR signals, through which the IR response beacon signal from the target beacon is viewed, a signal having a signal pattern of a response beacon signal expected from a beacon associated with the friendly entity, so that the target beacon is determined to be associated with the friendly entity if the response signal pattern of the target beacon matches the expected signal pattern in the viewing device.
Reference will now be made in detail to the present embodiments, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
In an identification friend or foe (IFF) beacon system, an interrogation device transmits an inquiry signal to a target beacon. The inquiry signal is encoded with an identification code of the interrogation device. If the target beacon is associated with a friendly entity (e.g., a soldier in a friendly force organization), the target beacon will transmit an acknowledgement signal, which can be detected by the interrogation device. The acknowledgement beacon signal is encoded with the identification code of the interrogation device, which is extracted by the target beacon from the inquiry signal. Upon receiving the acknowledgement beacon signal, the interrogation device compares the identification code in the acknowledgement signal with its own identification code to make a decision of friend or foe. If the identification code in the acknowledgement signal matches the identification code of the interrogation device, the interrogation device determines that the target beacon is associated with a friendly entity. Otherwise, if the identification code found in the acknowledgement signal does not match the identification code of the interrogation device, the interrogation device determines that the target beacon is potentially associated with a hostile entity.
In the above-described IFF beacon system, the interrogation device needs to decode the acknowledgement signal in order to obtain the identification code carried by the acknowledgement signal, and then compare the obtained identification code with its own identification code in order to make a friend or foe decision. These processes performed by the interrogation device may undesirably prolong the entire IFF process, which may not be suitable in a battlefield environment.
Embodiments of the present disclosure provide an IFF system including one or more interrogation devices and one or more beacons. Each interrogation device includes a viewing device through which a response beacon signal transmitted from a target beacon is viewed. More particularly, an operator of the interrogation device directs, or aims, at a target entity for which friend/foe status is to be determined and triggers emission of an inquiry signal, e.g., an infrared (IR) inquiry signal, at the target entity. For example, the operator aims through the viewing device by positioning the interrogation device so that the target entity appears in a field of view of the viewing device, and then triggers the inquiry signal. A friendly entity associated with the IFF system is expected to have a beacon configured to emit a response signal, e.g., an IR response signal, identifiable as emitted from the friendly entity beacon, in response to the inquiry signal. The viewing device of the interrogation device is configured to display in the field of view a signal pattern of an expected response from the beacon associated with the friendly entity. Therefore, the operator of the interrogation device can determine if the beacon is associated with a friendly entity by observing the signal pattern of the response beacon signal displayed in the field of view with the expected signal pattern, and comparing them. If the displayed patterns match, then the target entity is a friendly entity.
The disclosed IFF system thereby eases the interrogation device operator's task of interpreting the interrogation response. The operator of the interrogation device maintains aim at the target entity to be able to send and receive communication from a specific beacon. This engages the operator's full visual attention, so to accomplish the task the operator triggers emission of the inquiry signal, and a response back is displayed in the same field of view due to the aiming of the interrogation device. In that field, the expected and returned light signals are shown, e.g., near each other, to make comparing them easy as well as intuitive. This comparison can be continued as long as the operator continues to trigger emission of the inquiry signal.
As used herein, the term “signal” refers to any kind of signal transmitted by an interrogation device or a beacon. The term “beacon signal” refers to a signal transmitted by a beacon. The beacon signal can be configured to flash on and off according to a pattern, which is referred to as a “signal pattern”. The term “signaling program” refers to a preestablished signal pattern. The term “initiator” refers to an operator of the interrogation device who initiates communication between the interrogation device and a beacon and remotely directs the beacon to respond to an inquiry signal from the interrogation device.
Emitter 110 is configured to, in response to an input from an initiator 10 during operation of interrogation device 100 (also referred to as “deployment”), emit an inquiry signal to a target entity to be interrogated for an IFF response, to determine if the target entity is associated with a friendly entity. Emitter 110 may be an optical communication emitter, which can emit signals having long-range, narrow-beam infrared (IR) characteristics. Thus, the inquiry signal may be an IR inquiry signal. The inquiry signal may have a wavelength selected from a range from 880 nm to 2900 nm. In addition, the inquiry signal may be a frequency modulated optical signal carrying an inquiry message, which may be an encrypted digital message. During the deployment of interrogation device 100, emitter 110 is aimed at the target entity.
Viewing device 120 is configured to view IR signals. An IR response signal from a beacon of the target entity may be viewed through viewing device 120 by initiator 10. Viewing device 120 includes an output device 122 configured to output a signal having a signal pattern of a response signal expected from a target beacon associated with the friendly entity, so that initiator 10 can determine the target beacon is associated with the friendly entity if the response signal pattern of the target beacon matches the expected signal pattern output from output device 122. Output device 122 may be a light source (e.g., a light emitting diode (LED)) attached to a ring of an eyepiece of viewing device 120 and driven by central computer 130 to generate visible light according to the expected signal pattern. The visible light may be displayed in a field of view of viewing device 120 by attaching the light source to an eyepiece ring on a viewfinder of viewing device 120. Alternatively, as further described below with reference to
In the embodiment illustrated in
Referring back to
Central computer 130 stores one or more signaling programs and settings used during deployment of interrogation device 100, responds to initiator 10's input from control panel 150, creates and sends inquiry signals to a target entity consistent with one of the signaling programs selected by initiator 10, and displays expected beacon responses to initiator 10. Central computer 130 includes a high stability clock 132, a processor 134, and a memory 136. Clock 132 provides a time standard of interrogation device 100. Processor 134 may include one or more processing devices, such as a central processing unit (CPU), which executes program instructions to perform various functions consistent with the embodiments of the present disclosure. Memory 136 may be one or more storage devices that maintain data (e.g., instructions, software applications, information used by and/or generated during execution of instructions or software applications, etc.) used by processor 134. For example, memory 136 may store one or more factory-installed or operator-entered signaling programs or passwords (e.g., code of the day). Memory 136 may also store one or more computer programs that, when executed by processor 134, perform one or more processes consistent with the present disclosure. Memory 136 may further store information used by and/or generated during execution by processor 134, of programs that perform one or more processes consistent with the present disclosure. Memory 136 may include any kind of storage devices that maintain data. For example, memory 136 may include one or more of read-only memory (ROM), random-access memory (RAM), flash memory, or the like.
Communication interface 140 includes communications hardware for one or more of wired, wireless, and/or optical communication with external beacon devices, radios, and computer networks used during a set-up process of interrogation device 100, also referred to as a “pre-deployment process”, described more fully below.
Control panel 150 is configured to receive initiator 10's input, and transmits initiator 10's input to central computer 130.
As illustrated in
The configuration of control panel 150 is not limited to the configuration illustrated in
Referring back to
Emitter 310 is controlled by beacon computer 320 to emit a beacon signal with a particular flashing signal pattern in response to an inquiry signal received from interrogation device 100. Emitter 310 may be a multi-directional emitter 310 that is capable of emitting the beacon signal in multiple directions. Like the inquiry signal emitted by interrogation device 100, the beacon signals are IR signals that have long-range, narrow-wavelength beam infrared (IR) characteristics. Narrow-wavelength refers to the IR frequency spread of the signal, e.g., 900 nm±10 nm. On the other hand, the angle of emission coverage of the beacon signal is as wide as possible, typically one-half a hemisphere, as the orientation between beacon 300 and interrogation device 100 is not known and so a wide angle maximizes the probability of successful communication. The IR beacon signals may have a wavelength selected from a range from 880 nm to 2900 nm.
Beacon computer 320 includes both hardware and software that functionally tie other components of beacon 300 together and drive the other components. Beacon computer 320 includes a beacon clock 322, a processor 324, and a memory 326. Beacon clock 322 is an internal high stability clock, which has been synchronized with clock 132 of interrogation device 100 prior to deployment (also referred to herein as “pre-deployment”), as described more fully below. Processor 324 may be one or more processing devices, such as a central processing unit (CPU), which executes program instructions to perform various functions, such as the processes described in this disclosure. Memory 326 may be one or more storage devices that maintain data (e.g., instructions, software applications, information used by and/or generated during execution of instructions or software applications, etc.) used by processor 324. For example, memory 326 may store one or more factory-installed or operator-entered signaling programs or passwords (e.g., code of the day), or signaling programs or passwords received from interrogation device 100. Memory 326 may also store one or more computer programs that, when executed by processor 324, perform one or more processes consistent with the present disclosure. Memory 326 may further store information used by and/or generated during execution, by processor 324, of programs that perform the one or more processes consistent with the present disclosure. Memory 326 may comprise any kind of storage devices that maintain data. For example, memory 326 may include one or more of ROM, RAM, flash memory, or the like.
Receiver 330 includes an optical detector 332 configured to detect the inquiry signal sent by interrogation device 100 and a signal processor 334 configured to process the inquiry signal. The inquiry signal may be digital. Optical detector 332 may have a limited angle of reception, and the direction of the signals from interrogation device 100 is not likely to be known beforehand. Therefore, in some embodiments, receiver 330 may include an array of optical detectors 332 to increase the field of detection coverage. The array of optical detectors 332 may be integrated into wearable electronics worn by a user or in a hemispherical dome-like device. The more individual optical detectors 332 there are, the more responsive beacon 300 is. Hence, it may be preferable to configure an array with as many optical detectors 332 as practical.
Referring back to
Vote and combine logic module 440 includes a vote logic and a combine logic respectively executed by a processor (e.g., processor 324 or another processor included in signal processor 334). The vote logic is configured to monitor all input signals concurrently in real time and combines the input signals in those cases where the same inquiry signal has been detected by the multiple optical detectors 332. For example, when two out of three signals received from three optical detectors 332 agree (i.e., are the same), the vote logic combines the two signals. The combine logic is configured to detect signal continuity among the signals detected by optical detectors 332 and, when possible, assemble pieces of the signals detected by different optical detectors 332 into a full message. For example, due to movement, a first piece of the inquiry signal may be detected by a first optical detector 332 while a second piece of the inquiry signal is detected by a second optical detector 332, and the first piece and the second piece may overlap with each other. The combine logic combines the first and second pieces together into a full message.
Once vote and combine logic module 440 obtains the full message, vote and combine logic module 440 transfers the full message to decryption, error correction, verification, and command extraction module 450. Decryption, error correction, verification, and command extraction module 450 is configured to decrypt, error correct, and verify the message for content applicability. If all steps are passed successfully, decryption, error correction, verification, and command extraction module 450 is further configured to extract a command carried in the message, and pass the extracted command to beacon computer 320 for execution.
Referring back to
In some embodiments, beacon 300 may be the beacon disclosed in U.S. Pat. No. 9,866,369 B1, which is incorporated herein by reference, modified to include an array of optical detectors 332 and signal processor 334. Interrogation device 100 may have the clock and code functionality of beacon 300, and interrogation device 100 and beacon 300 are synchronized with each other prior to deployment.
According to an embodiment of the present disclosure, an IFF system includes one or more interrogation devices 100 operable by initiator 10, and one or more beacons 300 carried by friendly entities. Interrogation devices 100 and beacons 300 are data and time synchronized by a set-up process prior to field deployment. Hereinafter, the set-up process prior to field deployment is referred to as a “pre-deployment set-up process.”
As illustrated in
Initiator 10: Sends, through interrogation device 100, a password “Oct1” and a command “reply with signaling program No. 6”.
Beacon 300: Receives signal from interrogation device, validates encrypted signal, checks password “Oct1”, retrieves signaling program No. 6 from memory 326, and transmits signaling program No. 6 via emitter 310 which is timed by the clock setting in beacon 300 which will be in synchronism with the clock setting of interrogation device 100 as both had been synchronized during the pre-deployment set-up process.
Initiator 10: Looks for a response through NVG 120 while output device 122 (e.g., a light source) is outputting signals, e.g., flashing, according to signaling program No. 6 at the same time as the expected response.
The pre-deployment set-up process is performed to ensure that the one or more beacons 300 to be used for the deployment have the same data as the data that has been entered into interrogation device 100 (i.e., the code of the day and the signaling programs). During the pre-deployment set-up process, the data may be entered into the one or more beacons 300 by interrogation device 100 (or another external device) transmitting an optical-link signal carrying the data to be entered. For example, the optical-link signal may be an IR-link signal having a predetermined frequency of, e.g., 37 kHz, and each one of the one or more beacons 300 may include an IR-link detector and an IR-link emitter used for communicating data carried by IR-link signals with external devices. Alternatively, the data may be entered into the one or more beacons 300 by using wired, wireless, or radio communication means.
Part of the pre-deployment set-up process also synchronizes one or more clocks 322 of the one or more beacons 300 with clock 132 of interrogation device 100. Once synchronized, clocks 322 and 132 provide time consistency for the duration of the deployment that is sufficiently accurate, so that the same signal patterns emitted by different beacons 300 will appear to initiator 10 to be flashing in unison (i.e., at the same timing).
In some embodiments, once a beacon 300 has been synchronized with interrogation device 100, the synchronized beacon 300 can then be used subsequently to synchronize additional beacons 300, since the synchronized beacon 300 has all the information and time settings received from interrogation device 100. The subsequent synchronization of additional beacons is achieved by using a handshake feature of all of the beacons 300. According to the handshake feature, once one beacon is programed, the programed beacon can be shown to another beacon (e.g., a brother beacon of the programed beacon), and the brother beacon handshakes with the programmed beacon, installs the same signal on the same clock timing, and confirms that the handshake process has been completed.
The synchronization between interrogation device 100 and the one or more beacons 300, and among beacons 300, improves communications reliability. Once synchronized, communication messages are sent by interrogation device 100 or by a beacon 300 at pre-set clock times that are known to a receiving beacon 300, thereby reducing uncertainty and noise factor.
In addition, the synchronized clocks between interrogation device 100 and the one or more beacons 300, simplify beacon signaling program recognition by initiator 10 to a straightforward comparison between what is seen through NVG 120 and a flashing light signal, an audible signal, or a haptic (vibration) signal output from output device 122 representing the expected response from beacon 300 being interrogated. This is achieved as follows. The beacon signal emitted by beacon 300 begins at pre-set clock times known to central computer 130 of interrogation device 100, as is the pattern of the beacon signal that is expected from beacon 300. With that information, central computer 130 re-creates the expected response beacon signal with compensated timing including compensations for signal transmission and processing time delays. This re-created beacon signal is displayed in the NVG viewfinder as a flashing light pattern (or generated as an audible or haptic signal) at a timing that will match a timing of the signal pattern of the response beacon signal received from beacon 300 that had been interrogated.
As illustrated in
When the target entity carries beacon 300 that has been previously linked to interrogation device 100, receiver 330 of beacon 300 receives the inquiry signal transmitted from interrogation device 100, and signal processor 334 validates data integrity of the message included in the inquiry signal (e.g., by checking that the message is in an expected encrypted format and is mathematically correct). Beacon computer 320 determines if the message applies to that beacon 300, then if so, executes the command contained in the message.
Commands contained in a message payload that call for a beacon response of flashing IR beacon signals include:
Initiator 10, continuing to look through NVG 120, will see, on the side or middle of the viewfinder within NVG 120, a small indicator light that will be flashing the response signal expected from beacon 300, only if synchronization is specified by the command contained in the inquiry signal. A response beacon signal from a “friendly” entity will be seen through NVG 120 as a flashing signal matching the flashing indicator light that simulates the expected response in real time.
Should more certain verification be called for (e.g., no response is received, or the response beacon signal does not match the expected signal), initiator 10 can use control panel 150, associated with interrogation device 100, to request beacon 300 to flash a different signaling program or a different response.
In addition to commands to beacons that call for a flashing response, initiator 10 can also use interrogation device 100 to control other beacon aspects such as:
Additional commands can be added as needs arise.
During the deployment process, there are two possible ways a friendly beacon 300 can respond to an inquiry signal transmitted from interrogation device 100. In the first way, beacon 300 may respond with its preset individual signaling program. In the second way, beacon 300 may respond with the same signaling program received from interrogation device 100, i.e., a reflection of interrogation device 100's signaling program. The manner of beacon 300 responding to the inquiry signal can be selected by a mission commander before deployment, i.e., during the pre-deployment set-up process, as well as after deployment as the information transfer process is the same in both cases.
As illustrated in
In step 704, beacon 300 sets up the same password as interrogation device 100, and is synchronized with interrogation device 100. For example, in the embodiment illustrated in
In step 706, interrogation device 100 transmits an inquiry signal to a target entity, here assumed to include beacon 300. The inquiry signal includes the password and the signaling program that were set up in step 702. For example, initiator 10 of interrogation device 100 may see, through NVG 120, a target entity (e.g., a soldier in the field), and initiator 10 pushes button 160 on interrogation device 100. In response to button 160 being pushed, interrogation device 100 transmits the inquiry signal.
In step 708, beacon 300 receives the inquiry signal and extracts the password and the signaling program included in the inquiry signal. For example, optical detector 332 of beacon 300 may detect the inquiry signal, and signal processor 334 may process the received inquiry signal and extract the password and the signaling program.
In step 710, beacon 300 verifies the received inquiry signal. For example, processor 324 of beacon 300 compares the extracted password with the password stored in memory 326. If the extracted password is the same as the stored password, beacon 300 determines that the inquiry signal is received from a “friendly” interrogation device. In step 712, processor 324 of beacon 300 generates a response beacon signal based on the signaling program extracted from the inquiry signal. In step 714, beacon 300 transmits the response beacon signal according to a timing provided by clock 322 of beacon 300.
While beacon 300 generates and transmits the response beacon signal, in step 716, interrogation device 100 generates an expected response beacon signal based on the signaling program which is set up in step 702 and included in the inquiry signal. Interrogation device 100 generates the expect response beacon signal according to a timing provided by clock 132, including compensations for signal transmission between interrogation device 100 and beacon 300 and processing time delays by interrogation device 100 and beacon 300.
In step 718, output device 122 of interrogation device 100 outputs (e.g., displays by an indicator light) the expected response beacon signal in a view finder of NVG 120 through which the response beacon signal transmitted from beacon 300 is observed. By observing the expected response beacon signal and the response beacon signal transmitted from beacon 300 at the same time in the same viewfinder, initiator 10 can make a friend or foe decision for beacon 300. For example, if the signal pattern of the response beacon signal matches the signal pattern of the expected response beacon signal, initiator 10 determines that beacon 300 is associated with a friendly entity. Otherwise, if the signal pattern of the response beacon signal does not match the signal pattern of the expected response beacon signal, initiator 10 may determine that beacon 300 is not associated with a friendly entity, or that further inquiry is needed. In such case, initiator 10 may trigger interrogation device 100 to transmit a second inquiry signal to check whether beacon 300 is associated with a hostile entity. Initiator 10 may also trigger interrogation device 100 to transmit the second inquiry signal when no response is received from beacon 300. The second inquiry signal may be the same as, or different from, the previously transmitted inquiry signal.
In some embodiments, beacon 300 is included in a group of beacons which have been synchronized during the pre-deployment set up process. Then, during the deployment process, after beacon 300 verifies an inquiry signal in step 710, beacon 300 may forward the inquiry signal to other beacons in the group and present within receiving range of the inquiry signal. The forwarding may be performed by using a short-range communication method. As a result, the other beacons may emit the same response beacon signal at the same time as beacon 300, so that all of the beacons of the team will be seen as friendly by initiator 10. Alternatively, in some embodiment, if beacon 300 targeted by interrogation device 100 fails to switch on and emit a response beacon signal, other beacons in the same team as beacon 300 and within the vicinity of beacon 300 may detect the inquiry signal and emit response beacon signals at the same time.
As illustrated in
As illustrated in
In some embodiments, during the pre-deployment set-up process, interrogation device 100 may be used to program a group of beacons 300. The programing may be performed in close quarters, i.e., within a room or small area, by using short-range signal. The short-range signal could be a close proximity radio signal (e.g., wifi signal or Bluetooth, or any other licensed frequency signals allocated for short range communication. The short-range signal may be tuned or coupled to a laptop by hard-wired or wireless connection. Such coupling would include use of security protocols.
In some embodiments, the IFF system may include multiple interrogation devices 100. The multiple interrogation devices 100 may communicate with each other such that if interrogation device A is programed with a password, e.g., a code of the day “1234”, then interrogation devices B, C, and D, are also programed with the same code “1234.” In addition, the multiple interrogation devices 100 may all be synchronized. This allows interrogation devices 100 in remote locations to all share the same code.
Once beacon 300 has been programed, beacon 300 can be placed in stand-by mode. In the stand-by mode, the code of the day, signaling programs, and synchronization are maintained but beacon 300 does not emit a beacon signal.
During the pre-deployment set-up process, beacon 300 that has been programed with the password and the one or more signaling programs can communicate the password and the one or more signaling programs to another beacon 300, provided that the other beacon 300 has not been programed with another code. The communication of the code between two beacons 300 is performed via a short-range signal.
In some embodiments, a beacon that has not been programed will, upon receiving a command from interrogation device 100, flash a signal pattern according to a signaling program previously stored in the beacon. This pattern, while not being synchronized with any other beacon or interrogation device 100, does however confirm that it is of the type, frequency of operation, and data protocol of interrogation device 100.
In some embodiments, during the deployment process, interrogation device 100 can be initiated to transmit a long-range inquiry signal to beacon 300 that is in stand-by mode. The long-range inquiry signal includes the programed code in interrogation device 100 (e.g., 1234). If the programed code in interrogation device 100 (e.g., 1234) matches the programed code in beacon 300, beacon 300 will switch from stand-by to active (flashing). The long-range inquiry signal is an IR signal. Over distance, wifi can be hacked more easily and security is more difficult. For this reason, in part, an IR signal is used herein as the inquiry signal. If the programed code in beacon 300 and the programed code in interrogation device 100 do not match, beacon 300 will not emit any beacon signal.
In some embodiments, during the deployment process, a beacon's battery may need to be changed. When the battery is removed from a beacon, all the previously set codes, as well as the built-in codes preset at the factory, are retained in non-volatile memory. Clock synchronization setting is lost as a result of power interruption but can be recovered by synchronizing to another beacon or an interrogation device. Synchronizing with another beacon would use a short-range signal.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
This application claims the benefit of priority to U.S. Provisional Application No. 63/113,068, filed on Nov. 12, 2020, the entire contents of which are incorporated herein by reference.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2021/058949 | 11/11/2021 | WO |
Number | Date | Country | |
---|---|---|---|
63113068 | Nov 2020 | US |