US20150345884A1 - Remotely authorizing and disabling weapons - Google Patents

Remotely authorizing and disabling weapons Download PDF

Info

Publication number
US20150345884A1
US20150345884A1 US14/291,088 US201414291088A US2015345884A1 US 20150345884 A1 US20150345884 A1 US 20150345884A1 US 201414291088 A US201414291088 A US 201414291088A US 2015345884 A1 US2015345884 A1 US 2015345884A1
Authority
US
United States
Prior art keywords
weapon
substring
authorization
authorization message
encrypted
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US14/291,088
Other versions
US10197350B2 (en
Inventor
Morgan Draper Kauffman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US14/291,088 priority Critical patent/US10197350B2/en
Publication of US20150345884A1 publication Critical patent/US20150345884A1/en
Application granted granted Critical
Publication of US10197350B2 publication Critical patent/US10197350B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • FMECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F41WEAPONS
    • F41AFUNCTIONAL FEATURES OR DETAILS COMMON TO BOTH SMALLARMS AND ORDNANCE, e.g. CANNONS; MOUNTINGS FOR SMALLARMS OR ORDNANCE
    • F41A17/00Safety arrangements, e.g. safeties
    • F41A17/06Electric or electromechanical safeties
    • FMECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F41WEAPONS
    • F41AFUNCTIONAL FEATURES OR DETAILS COMMON TO BOTH SMALLARMS AND ORDNANCE, e.g. CANNONS; MOUNTINGS FOR SMALLARMS OR ORDNANCE
    • F41A17/00Safety arrangements, e.g. safeties
    • F41A17/06Electric or electromechanical safeties
    • F41A17/063Electric or electromechanical safeties comprising a transponder

Definitions

  • FIG. 3 shows a flowchart illustrating a method of initializing the weapon
  • FIG. 7 shows a flowchart 700 illustrating an exemplary process performed at the weapon 100 for authorizing the weapon in an embodiment of the present disclosure. Once issued, the weapon periodically performs this process to either maintain or alter its authorization state.
  • FIG. 8 shows a schematic illustration of the processes illustrated in the flowchart of FIG. 7 .
  • the processor 112 operates the monitoring program 116 to receive a transmitted authorization message 502 from the authorization center 200 .
  • the processor 112 compares the weapon ID 510 included in the authorization message 512 with the weapon ID 125 stored at the weapon 100 .
  • Box 706 if the weapon ID 510 matches the stored weapon ID 125 , the process proceeds to Box 708 . Otherwise, the process proceeds to Box 710 , in which the weapon is disabled or de-authorized.
  • the weapon 100 may additionally be de-authorized by stopping or interrupting the timed authorization messages. This therefore results in a “dead man's switch” in which the destruction or interruption of the authorization center 200 or of its transmitter 202 causes the weapon 100 to be de-authorized by default.
  • the dead man's switch prevents, for example, an opposing army or force from capturing the weapon and then blocking or otherwise interfering with a de-authorization message.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Storage Device Security (AREA)

Abstract

A weapon, a method of authorizing the weapon and weapon security system are disclosed. An authorization string is stored at the weapon. An authorization message may be received at the weapon from an authorization center. A processor at the weapon may obtain a first substring from the authorization message, the first substring being obtained from a copy of the authorization string. The processor compares the first substring to a second substring and authorizes the weapon when the first substring matches the second substring.

Description

    BACKGROUND
  • The present invention relates to weapons security, and more specifically, to a system and method for authorizing or de-authorizing a weapon remotely.
  • In times of war, with two warring parties attempting to cause destruction and death to the each other, it is possible for weapons from a first party to be captured or otherwise obtained by a second party. These captured weapons may then be used against the first party, the very party that brought them into the field of battle, or against other parties. The impact of losing these weapons to the second party can therefore result in lost lives to the first party or its allies and can sway an outcome of a battle or skirmish or provide the means for terror attacks elsewhere. Considering another situation, a first party may supply weapons to a second party, which sells the weapons to a third party, which then uses the weapons against a fourth party. Thus, the present method of proliferating arms may have unintended consequences. Therefore weapons security, or the ability to prevent such weapons from being used counter to their intended purposes, is an important aspect of warfare.
  • SUMMARY
  • In one aspect, the present disclosure provides a method of authorizing a weapon, including: storing an authorization string at the weapon; receiving an authorization message at the weapon that includes a first substring obtained from a copy of the authorization string; comparing the first substring to a second substring obtained from the authorization string stored at the weapon; and authorizing the weapon when the first substring matches the second substring.
  • In another aspect, the present disclosure provides a weapon, the weapon including: a memory configured to store an authorization string; a receiver configured to receive a first substring obtained from a copy of the authorization string; and a processor configured to: obtain a second substring from the authorization string stored in memory, compare the first substring to the second substring, and authorize the weapon when the first substring matches the second substring.
  • In another aspect, the present disclosure provides a weapon security system, the system including: an authorization center that transmits an authorization message that includes a first substring obtained from a copy of an authorization string; and a weapon that includes: a memory configured to store the authorization string; a receiver configured to receive the authorization message; and a processor configured to: obtain the first substring from the received authorization message; obtain a second substring from the authorization string stored in memory, compare the first substring to the second substring, and authorize the weapon when the first substring matches the second substring.
  • Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with the advantages and the features, refer to the description and to the drawings.
  • BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
  • The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The forgoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
  • FIG. 1 illustrates an exemplary weapon 100 in one embodiment of the present invention;
  • FIG. 2 shows an exemplary authorization center that communicates with the exemplary weapon of FIG. 1 in order to place the weapon into a selected authorization state;
  • FIG. 3 shows a flowchart illustrating a method of initializing the weapon;
  • FIG. 4 shows a flowchart illustrating a process for sending an authorization message from the authorization center to a weapon in the field, in one embodiment;
  • FIG. 5 schematically illustrates the method described in the flowchart of FIG. 4;
  • FIG. 6 shows an example of a transformation method which determines a starting location from the transmission time;
  • FIG. 7 shows a flowchart illustrating an exemplary process performed at the weapon for authorizing the weapon in an embodiment of the present disclosure; and
  • FIG. 8 shows a schematic illustration of the processes illustrated in the flowchart of FIG. 7.
  • DETAILED DESCRIPTION
  • FIG. 1 illustrates an exemplary weapon 100 in one embodiment of the present invention. The weapon in various embodiments may include a gun, a missile, an explosive, etc. The weapon 100 may include a payload 102 and a payload delivery system 104. The weapon 100 may further include an activation system 106 that activates the delivery system 104 to delivery the payload 102. In one example, the weapon 100 may be a missile such that the payload 102 is an explosive material, generally at a forward location of the weapon 100, and the delivery system 104 is a propellant generally ejected from an aft location of the weapon 100. The activation system 106 may be a trigger mechanism, switch or an electronic signal that activates the delivery system 104. The activation system 106 may be coupled mechanically or electronically to an authorization unit 108. The authorization unit 108 may be used to enable (authorize) or disable (de-authorize) the activation system 106 and thus enable or disable the weapon 100 by determining an authorization state of the weapon 100 using the methods disclosed herein. In other words, the authorization unit 108 places the weapon 100 into either an authorized state or an unauthorized state. In the authorized state, the weapon 100 is armed and can be fired, detonated, or otherwise used. In the unauthorized state, the weapon 100 is essentially harmless and may be prevented from being fired, detonated, or otherwise used. In one example, the authorization unit 108 may prevent the activation system 106 from activating the delivery system 104. In another example, the authorization unit 108 may perform an action, such as sending a “disarm” signal to a disarming unit 126 that disarms the payload.
  • The authorization unit 108 may include a control unit 110 for performing various methods disclosed herein for placing the weapon 100 into either the authorized state or the unauthorized state. The control unit 110 may include a processor 112 that performs the various methods and processes described herein. The processor 112 may have access to a memory device 114 that may include various programs 116, 118, 120, 122 stored therein which, when accessed by the processor 112, enable the processor 112 to perform the various methods for selecting or determining the authorization state of the weapon 100. The memory device 114 may be any non-transitory computer-readable medium such as a solid-state memory device. In various embodiments, the memory device 114 may include a read-only memory (ROM), a programmable read-only memory (PROM), or other suitable memory type.
  • The memory device 114 may further contain an encoded string of bits, also referred to as a stored authorization string or first authorization string 124 that is used when determining the authorization state of the weapon 100. The memory device 114 also stores a weapon identification 125 (also referred to herein as a weapon ID or WID) that identifies the weapon 100. The weapon ID 125 may be unique to the weapon 100 or may be an identification number or code that is uniquely assigned to a group of weapons, so that the entire group of weapons may be responsive to the same weapon ID 125. The memory device 114 also stores a maximum authorization interval 123 that determines the maximum period of time that may elapse since the last authorization without causing the weapon to be disabled.
  • The authorization unit 108 also includes various additional components that ensure the operation of the authorization unit 108. These components include a power supply 130, a receiver 132 and its associated antenna 134, and a clock 136. Power supply 130 provides power to the control unit 110, processor 112, receiver 132, clock 136 and any other electrical components used in the authorization and/or deployment of the weapon 100. Receiver 132 and antenna 134 may be suitable for communication over any selected radio frequency or other selected frequency of the electromagnetic spectrum. Clock 136 may be an internal digital clock or any suitable type of clock for maintaining time to a suitable degree of accuracy. For the purposes of authorizing/de-authorizing the weapon 100, clock 136 keeps a count of elapsed time since the weapon has been issued and/or since the most recent completed authorization. Whenever the weapon 100 is re-issued or re-authorized, the elapsed time stored in the clock 136 may be reset to t=0, or the time of authorization may be stored in such a way as to allow calculation of elapsed time from the time at which the weapon is re-issued or most recently re-authorized. When the time between receiving authorization messages exceed the maximum authorization interval, the weapon may be automatically disabled. Issuance of the weapon is discussed below with respect to FIG. 3. Upon issue of the weapon 100, the activation time of the clock 136 is stored at an authorization center, as discussed below with respect to FIG. 2.
  • Referring further to FIG. 1, the memory device 114 of the weapon 100 may contain, among other programs, a monitoring program 116, an encryption/decryption program 118, a matching program 120 and an authorization program 122. The processor 112 may run these programs 116, 118, 120 and 122 to determine an authorization state of the weapon 100. The monitoring program 116 includes a set of instructions that cause the receiver 132 to listen continuously or periodically at a designated interval for radio frequency messages transmitted on a specified frequency or set of frequencies and to identify and record a transmitted authorization message (see FIG. 5, 512) when a weapon ID in the authorization message matches a stored weapon ID 125 that is stored in the memory device 114 of the particular weapon 100.
  • Once the weapon 100 receives an authorization message and is authorized, if the clock 136 counts to a selected value K before the monitoring program 116 receives a next authorization signal, the weapon 100 will shut down or de-authorize. Whenever a weapon 100 is issued, its weapon ID 125 is stored in its memory 114 and its internal clock 136 starts to count from an assigned or selected start time. In one embodiment, the assigned start time may be selected to be represented by t=0. However, the assigned start time may be any recorded time, such as an issue time, a re-issue time, an authorization time, a re-authorization time or other time suitable for the purposes described herein. Every time the weapon re-authorizes, the clock is reset to a new assigned start time and begins its count from the new assigned start time.
  • In another embodiment, the monitoring program 116 may have access to the clock 136 and activate the receiver 132 periodically to listen for the transmitted authorization message at an end of a selected time interval as indicated by the clock 136. The selected time interval may be, for example, 12 hours, 24 hours, 30 minutes, etc. Listening periodically may be used in order to preserve battery life.
  • The encryption/decryption program 118 includes a set of instructions that obtains the authorization message and obtains a first substring or first encrypted substring from the authorization message. The encryption/decryption program 118 may then obtain a second substring from the stored authorization string 124. The encryption/decryption program 118 may use a conversion formula or encryption formula that provides a “one-way” conversion or encryption to obtain a second encrypted substring from the second substring. A “one-way” conversion formula may be a formula that can be performed easily and/or in a relatively short amount of time, but for which the inverse of the conversion formula is difficult or time-intensive to perform.
  • The matching program 120 includes a set of instructions that compares the first substring to the second substring. The authorization program 122 includes a set of instructions that select an authorization state of the weapon 100 based on the results of the matching program 120. In one embodiment, the authorization program 122 prevents the arming and/or firing of the weapon 100 when the matching program 122 does not register a match between the received message and stored data. In another embodiment, the authorization program 122 prevents the arming and/or firing of the weapon 100 when the interval since last authorization (stored in the clock 136) exceeds the maximum authorization interval 123. Methods for authorizing the weapon are discussed below with respect to FIGS. 5 and 6.
  • Referring now to FIG. 2, FIG. 2 shows an exemplary authorization center 200 that communicates with the exemplary weapon 100 of FIG. 1 in order to place the weapon 100 into a selected authorization state. The authorization center 200 includes one or more transmitters 202 and associated antenna(s) 204 for transmitting an authorization message to the weapon 100. The authorization center 200 further includes a processor 206 having access to a memory device 208 and various programs 210 stored therein that when accessed by the processor 206, enable the processor 206 to transmit a selected authorization message to one or more weapons. The memory device 208 may have a database or various memory locations 212, 214, 216 containing data that may be transmitted to a selected weapon for authorization purposes. An exemplary memory location 212 may include a weapon ID, as well as an authorization string and an activation time of the weapon 100. The memory device 208 may be any non-transitory computer-readable medium such as a solid-state memory device, read-only memory (ROM), programmable read-only memory (PROM), etc.
  • FIG. 3 shows a flowchart 300 illustrating a method of initializing weapon 100. The method shown in flowchart 300 prepares the authorization center (200, FIG. 2) and the weapon (100, FIG. 1) so that the authorization method disclosed herein may be executed. Prior to issuing the weapon 100, a computer or other device generates a random string of bits, referred to herein as an authorization string (Box 302). In various embodiments, this authorization string is generally a large string, such as greater than 1 gigabyte. In box 304, the authorization string 124 and the weapon ID 125 of the weapon 100 is stored at the memory device 114 of the weapon 100. In box 306, when the weapon 100 is issued, the authorization string, weapon ID and activation time is stored at the memory device 208 of the authorization center 200, such as at memory location 212. The clock 136 of the weapon 100 records the activation time using an initiation signal at the authorization center 200. Any interlocks and/or anti-tampering devices and/or programs that prevent the weapon 100 from being altered, analyzed, interrogated, reprogrammed, or disassembled by unauthorized personnel may then be applied.
  • FIG. 4 shows a flowchart 400 illustrating a process for sending an authorization message from the authorization center 200 to a weapon 100 in the field, in one embodiment. FIG. 5 schematically illustrates the method described in the flowchart 400 of FIG. 4. Referring to FIGS. 4 and 5, in Box 402, an authorization string 502 is obtained or accessed. The authorization string 502 is generally the authorization string that is stored at the authorization center 200 of FIG. 2. In Box 404, a first substring (SS) 504 is selected from the authorization string 502 based on a selected transmission time of an authorization message. Each authorization message 502 has one or more associated time slots (also referred to herein as transmission time (TT)) for transmitting the authorization message 502.
  • The first substring 504 may be obtained using a hashing algorithm or other suitable transformation algorithm. In one embodiment, the hashing algorithm is used to transform the transmission time into a starting location (SL) in the authorization string. FIG. 6 shows an example of a transformation method which determines a starting location from the transmission time. For illustrative purposes, time is shown in time array 602 and increases in a downward direction on the page. The authorization string 604 is shown having a plurality of bit locations, where the numbering of the bit locations increase in a downward direction on the page. Arrows 606 indicate the effects of applying transformation algorithm to select the SL for a selected TT. The transformation may be a non-sequential transformation. For example, a scheduled first TT may be transformed to obtain an SL of 9797, while a second TT that is scheduled for five seconds after the first TT may be transformed to obtain an SL of 183, which is less than 9797.
  • Referring back to FIGS. 4 and 5, in Box 406 the first substring 504 is encrypted to obtain a first encrypted substring (ESS) 506. In box 408, the first ESS 506, TT 508, and the weapon ID 510 are concatenated to each other or otherwise combined to obtain an authorization message 512. In another embodiment, the transmission time (TT) may be encrypted to obtain encrypted transmission time (ETT). The authorization message 512 may then include the first ESS 506, the ETT 508 and the weapon ID 510. In box 410, the authorization message 512 is transmitted to the weapon 100.
  • FIG. 7 shows a flowchart 700 illustrating an exemplary process performed at the weapon 100 for authorizing the weapon in an embodiment of the present disclosure. Once issued, the weapon periodically performs this process to either maintain or alter its authorization state. FIG. 8 shows a schematic illustration of the processes illustrated in the flowchart of FIG. 7. In Box 702, the processor 112 operates the monitoring program 116 to receive a transmitted authorization message 502 from the authorization center 200. In Box 704, the processor 112 compares the weapon ID 510 included in the authorization message 512 with the weapon ID 125 stored at the weapon 100. In Box 706, if the weapon ID 510 matches the stored weapon ID 125, the process proceeds to Box 708. Otherwise, the process proceeds to Box 710, in which the weapon is disabled or de-authorized.
  • In Box 708, TT 508 is obtained from the authorization message 512. If an encrypted transmission time (ETT) has been sent in the authorization message, encryption/decryption program 118 may be performed on the ETT to obtain its corresponding TT 508. The obtained TT 508 is then compared to a reception time (RT) of the message. The reception time may be determined from the clock 136 of the weapon 100. If the difference between TT and RT is less than a selected time threshold Δ (e.g., Δ=3 seconds) then the method proceeds to Box 716. Otherwise, the method proceeds to Box 718 at which point the attempt to re-authorize the weapon is discontinued.
  • In Box 716, the TT 508 received via transmission of the authorization message 512 is used to obtain a second substring 702 from the authorization string 124. The same hashing algorithm that is used to select a starting location for the first substring at the authorization center 200 may be used to select the starting location of the second substring at the weapon 100. Proceeding to Box 718, the processor 112 runs an encryption algorithm on the second substring 802 to obtain a second encrypted substring 804. The second encrypted substring 804 is then compared to the received (first) ESS 506. In Box 720, if the encrypted substrings 804 and 506 are equal, the process proceeds to Box 722. If the encrypted substrings 804 and 506 are not equal, the process proceeds to Box 724 at which point the attempt to re-authorize the weapon is discontinued. The substrings are compared bitwise so that a successful match is indicated when first substring and second substring (or first ESS 506 and second ESS 804) match exactly bit-for-bit. In Box 722, the processor 112 maintains or places the weapon 100 into an authorized state. From Box 722, the processor 112 may start the monitoring program 116 again at Box 702 so as to be able to run the authorization process again at the end of the next time interval.
  • The weapon 100 is therefore in an authorized state only temporarily, i.e., until a time at which a next authorization signal is expected to be received. At some point at or prior to the end of this time interval, the authorization state must be renewed by the methods disclosed herein or the weapon will be disabled or de-authorized. Therefore, a default state of the weapon 100 is an unauthorized or disabled state.
  • The amount of time between receiving a valid authorization message and disabling the weapon may be selected to be greater than the product of the number of weapon IDs and the time required to transmit one authorization message, so that weapons may be maintained in an authorized state in a given theater of operation. As an example, let K=the number of seconds since receiving a valid authorization message before a weapon becomes disabled, N=the maximum number of weapon IDs being issued using a same frequency or transmission system in a selected theater of operation, and L=the length of time needed or allotted to transmit a single authorization message, including any buffering time that may be required between messages. Therefore, K>N*L in order for all weapons in the theater to maintain their authorization state given normal authorization operations. For example, if it takes 1 second to transmit an authorization message and there are 10,000 unique weapon IDs in the theater of operation assigned to the same frequency or group of frequencies, K will need to be greater than 10,000 seconds (about 2.8 hours). Otherwise, a weapon may de-authorize before its next authorization message is even transmitted. Having the weapon listen continuously for the authorization message may allow authorization messages to be sent more frequently than necessary, providing redundancy and increased reliability
  • If weapon IDs are assigned to groups of weapons in a theater of operation, the number of unique weapon IDs may be less than the number of weapons in the theater. For example, by assigning weapon IDs to groups, 1200 unique IDs may be used rather than 10,000 unique IDs. This may allow authorization messages to be transmitted more frequently than necessary, thereby reducing the probability that a weapon misses an authorization message and disables or de-authorizes the weapon inadvertently. Therefore, in the above scenario, one may transmit each of the weapons' authorization messages in a non-stop loop that is 20 minutes in duration, rather than using a non-stop loop that is 10,000 seconds (about 2.8 hours) in duration.
  • The time interval between authorization messages may be set at a duration that is appropriate to the circumstances in which the weapon 100 is being issued. For example, a 12-hour authorization interval or a daily authorization interval may allow a weapon 100 to be used in a local theater of operations, but still prevent the weapon 100 from being shipped any considerable distance. Alternatively, a short authorization time interval may be chosen, with the option that several re-authorizations may be missed in sequence before the weapon is disabled or de-authorized. This allows the weapon 100 to remain authorized in the face of issues that may arise that may cause authorization messages to occasionally be missed, such as jamming, static, accidental shielding, etc.
  • The weapon 100 may additionally be de-authorized by stopping or interrupting the timed authorization messages. This therefore results in a “dead man's switch” in which the destruction or interruption of the authorization center 200 or of its transmitter 202 causes the weapon 100 to be de-authorized by default. The dead man's switch prevents, for example, an opposing army or force from capturing the weapon and then blocking or otherwise interfering with a de-authorization message.
  • While the invention is described with respect to artillery, weapons and weaponry, the method of authorizing and de-authorizing may also be used in other devices and/or systems not specifically disclosed herein.
  • The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one more other features, integers, steps, operations, element components, and/or groups thereof.
  • The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated
  • The flow diagrams depicted herein are just one example. There may be many variations to this diagram or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order or steps may be added, deleted, or modified. All of these variations are considered a part of the claimed invention.
  • While the preferred embodiment to the invention had been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described.

Claims (22)

What is claimed is:
1. A method of authorizing a weapon, comprising:
storing an authorization string at the weapon;
receiving an authorization message at the weapon that includes a first substring obtained from a copy of the authorization string;
comparing the first substring to a second substring obtained from the authorization string stored at the weapon; and
authorizing the weapon when the first substring matches the second substring.
2. The method of claim 1, further comprising de-authorizing and thereby disabling the weapon when the weapon is not re-authorized within a selected time interval.
3. The method of claim 1, wherein comparing the first substring to the second substring further comprises encrypting the first substring to obtain a first encrypted substring, encrypting the second substring to obtain a second encrypted substring, and comparing the first encrypted substring to the second encrypted substring.
4. The method of claim 1, wherein the received authorization message includes receiving a transmission time of the authorization message, the method further comprising using the received transmission time to obtain the second substring of from the authorization string stored at the weapon.
5. The method of claim 3, further comprising using the transmission time to determine a starting location for selecting the first substring from the copy and to determine a starting location for selecting the second substring the stored authorization string.
6. The method of claim 1, further comprising authorizing the weapon when:
(i) the weapon obtains the authorization message before the end of a selected time interval;
(ii) the weapon identification associated with the authorization message matches a weapon identification stored at the weapon;
(iii) a difference between a reception time of the authorization message and a transmission time of the authorization message is less than a selected time threshold; and
(iv) the first encrypted substring matches the second encrypted substring.
7. The method of claim 1, wherein the authorization message includes an encrypted transmission time, the method further comprising decrypting the transmission time at the weapon.
8. The method of claim 1 wherein the weapon shares a weapon identification with one or more additional weapons and the weapon and the one or more additional weapons are authorized using a same authorization message.
9. A weapon, comprising:
a memory configured to store an authorization string;
a receiver configured to receive a first substring obtained from a copy of the authorization string; and
a processor configured to:
obtain a second substring from the authorization string stored in memory,
compare the first substring to the second substring, and
authorize the weapon when the first substring matches the second substring.
10. The weapon of claim 9, wherein the processor is further configured to receive first encrypted substring corresponding to the first substring, select and encrypt the second substring to obtain a second encrypted substring, and compare the first encrypted substring to the second encrypted substring.
11. The weapon of claim 9, wherein the authorization message includes a transmission time of the authorization message and the processor is further configured to obtain the second substring of from the authorization string stored at the weapon using the received transmission time.
12. The weapon of claim 11, wherein the transmission time is further configured to obtain a starting location for selecting the first substring from the copy of the authorization string.
13. The weapon of claim 9, wherein the processor is further configured to authorize the weapon when:
(i) the weapon obtains the authorization message before the end of a selected time interval;
(ii) the weapon identification associated with the authorization message matches a weapon identification stored at the weapon;
(iii) a difference between a reception time of the authorization message and a transmission time of the authorization message is less than a selected time threshold; and
(iv) the first encrypted substring matches the second encrypted substring.
14. The weapon of claim 9, wherein the processor is further configured to decrypt an encrypted transmission time included in the received authorization message.
15. The weapon of claim 9, wherein a weapon identification of the weapon is the same as a weapon identification of one or more additional weapons and the processor authorizes the weapon use the same authorization message used to authorized the one or more additional weapons.
16. A weapon security system, comprising:
an authorization center that transmits an authorization message that includes a first substring obtained from a copy of an authorization string; and
a weapon that includes:
a memory configured to store the authorization string;
a receiver configured to receive the authorization message; and
a processor configured to:
obtain the first substring from the received authorization message;
obtain a second substring from the authorization string stored in memory,
compare the first substring to the second substring, and
authorize the weapon when the first substring matches the second substring.
17. The weapon security system of claim 16, wherein the processor is further configured to receive first encrypted substring corresponding to the first substring, encrypt the second substring to obtain a second encrypted substring, and compare the first encrypted substring to the second encrypted substring.
18. The weapon security system of claim 16, wherein a transmission time is used to obtain the first substring form the copy of the authorization message and to obtain the second substring from the authorization string stored at the weapon.
19. The weapon security system of claim 16, wherein the processor is further configured to disarm the weapon when the weapon does not receive a valid authorization message by the end of the selected time interval.
20. The weapon security system of claim 16, wherein the processor is configured to decrypt an encrypted transmission time included in the received authorization message to obtain the transmission time of the authorization message at the weapon.
21. The weapon security system of claim 16, wherein the processor is configured to authorize the weapon when:
(i) the weapon obtains the authorization message before the end of a selected time interval;
(ii) the weapon identification associated with the authorization message matches a weapon identification stored at the weapon;
(iii) a difference between a reception time of the authorization message and a transmission time of the authorization message is less than a selected time threshold; and
(iv) the first encrypted substring matches the second encrypted substring.
22. The weapon security system of claim 16, further comprising a plurality of weapons having a same weapon identification, wherein the authorization center transmits the authorization message to the plurality of weapons to authorize the plurality of weapons as a group.
US14/291,088 2014-05-30 2014-05-30 Remotely authorizing and disabling weapons Active 2035-08-03 US10197350B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/291,088 US10197350B2 (en) 2014-05-30 2014-05-30 Remotely authorizing and disabling weapons

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/291,088 US10197350B2 (en) 2014-05-30 2014-05-30 Remotely authorizing and disabling weapons

Publications (2)

Publication Number Publication Date
US20150345884A1 true US20150345884A1 (en) 2015-12-03
US10197350B2 US10197350B2 (en) 2019-02-05

Family

ID=54701323

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/291,088 Active 2035-08-03 US10197350B2 (en) 2014-05-30 2014-05-30 Remotely authorizing and disabling weapons

Country Status (1)

Country Link
US (1) US10197350B2 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021194584A2 (en) * 2019-12-17 2021-09-30 Authgrip Inc. Firearm authentication and tracking system
US11885604B1 (en) 2022-08-19 2024-01-30 Scott Belanger Firearm cartridge

Family Cites Families (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3888181A (en) 1959-09-10 1975-06-10 Us Army Munition control system
US4003152A (en) * 1974-03-18 1977-01-18 Precision Thin Film Corporation Safety system
US5062232A (en) * 1990-02-23 1991-11-05 Eppler Larry D Safety device for firearms
US5796362A (en) 1994-06-13 1998-08-18 Hittite Microwave Corporation Post launch on-board identification friend or foe system
US5461812A (en) * 1994-11-16 1995-10-31 Bennett; Emeric S. Method and apparatus for a weapon firing safety system
US5812252A (en) * 1995-01-31 1998-09-22 Arete Associates Fingerprint--Acquisition apparatus for access control; personal weapon and other systems controlled thereby
US6237271B1 (en) * 1996-07-23 2001-05-29 Colt's Manufacturing Company, Inc. Firearm with safety system having a communication package
US6014932A (en) 1997-11-18 2000-01-18 Technology Patents, Llc Land mine arming/disarming system
US5915936A (en) * 1997-12-01 1999-06-29 Brentzel; John Charles Firearm with identification safety system
IL124362A0 (en) * 1998-05-07 1999-11-30 H G Tek Ltd Weapon tag
US6223461B1 (en) * 1998-11-12 2001-05-01 Technology Patents, Llc Firearm with remotely activated safety system
US5953844A (en) * 1998-12-01 1999-09-21 Quantum Leap Research Inc. Automatic firearm user identification and safety module
US6283034B1 (en) * 1999-07-30 2001-09-04 D. Wayne Miles, Jr. Remotely armed ammunition
DE10018369A1 (en) * 2000-04-13 2001-10-25 Joergen Brosow Firearm locking system has transponder check can include munition lock could make all existing firearms useless
CA2364058A1 (en) * 2000-11-30 2002-05-30 Quantum Leap Research Inc. Automatic weapon user identification and safety module
US7848905B2 (en) 2000-12-26 2010-12-07 Troxler Electronic Laboratories, Inc. Methods, systems, and computer program products for locating and tracking objects
US6563940B2 (en) * 2001-05-16 2003-05-13 New Jersey Institute Of Technology Unauthorized user prevention device and method
US6487804B1 (en) * 2001-08-23 2002-12-03 Imet Corporation Firearm with personal safety interlock mechanism
US8375838B2 (en) 2001-12-14 2013-02-19 Irobot Corporation Remote digital firing system
US6860206B1 (en) 2001-12-14 2005-03-01 Irobot Corporation Remote digital firing system
US20030110972A1 (en) 2001-12-19 2003-06-19 Porter Frank B. Time limited weapon system
US6817130B2 (en) * 2002-06-17 2004-11-16 New Jersey Institute Of Technology Sensor array for unauthorized user prevention device
US6823621B2 (en) * 2002-11-26 2004-11-30 Bradley L. Gotfried Intelligent weapon
ES2274486T3 (en) * 2003-06-04 2007-05-16 Fn Herstal, Societe Anonyme WEAPON AUTHORIZATION SYSTEM WITH PIEZOELECTRIC DEACTIVATOR.
EP1761741A2 (en) 2004-02-06 2007-03-14 Icosystem Corporation Methods and systems for area search using a plurality of unmanned vehicles
US7441362B1 (en) * 2004-03-29 2008-10-28 Metadigm Llc Firearm with force sensitive trigger and activation sequence
US7423535B2 (en) 2004-08-26 2008-09-09 Avante International Technology, Inc. Object monitoring, locating, and tracking method employing RFID devices
US7319397B2 (en) 2004-08-26 2008-01-15 Avante International Technology, Inc. RFID device for object monitoring, locating, and tracking
US7669054B2 (en) 2005-08-17 2010-02-23 Common Credential Systems, L.L.C. Legacy access control security system modernization apparatus
ITRM20060119A1 (en) * 2006-03-08 2007-09-09 Famiglia Anzeloni S R L SAFETY DEVICE FOR FIRE WEAPON
DE102006062731B4 (en) * 2006-03-10 2009-07-09 Armatix Gmbh Device for storing a firearm
US7506468B2 (en) * 2006-08-02 2009-03-24 Michael Anthony Farrell Method and apparatus for monitoring handling of a firearm
ATE523752T1 (en) * 2006-10-20 2011-09-15 Armatix Gmbh CONVERTIBLE HAND GUN SAFETY DEVICE AND METHOD OF SECURING A HAND GUN.
DE102007007309A1 (en) 2007-02-07 2008-08-14 Atmel Germany Gmbh Method for at least temporarily unlocking a bidirectional communication and transponder
US7921588B2 (en) * 2007-02-23 2011-04-12 Raytheon Company Safeguard system for ensuring device operation in conformance with governing laws
WO2008124805A2 (en) 2007-04-10 2008-10-16 Hti Ip, Llc Methods, systems, and apparatuses for determining driver behavior
US8215048B2 (en) * 2008-04-11 2012-07-10 James Summers Weapon control device
US8312660B1 (en) * 2008-05-09 2012-11-20 Iwao Fujisaki Firearm
US8812172B2 (en) 2008-09-15 2014-08-19 Hti Ip, Llc Method for generating a vehicle identifier
US8653956B2 (en) 2009-09-11 2014-02-18 Hti Ip, L.L.C. Method and system for implementing a geofence boundary for a tracked asset
US9395132B2 (en) * 2013-04-01 2016-07-19 Yardarm Technologies, Inc. Methods and systems for enhancing firearm safety through wireless network monitoring
US9400150B2 (en) * 2013-04-01 2016-07-26 Yardarm Technologies, Inc. Methods and systems for enhancing firearm safety through wireless network monitoring
US9404698B2 (en) * 2013-04-01 2016-08-02 Yardarm Technologies, Inc. Methods and systems for enhancing firearm safety through wireless network monitoring

Also Published As

Publication number Publication date
US10197350B2 (en) 2019-02-05

Similar Documents

Publication Publication Date Title
EP2525184B1 (en) Radio controlled ammunition
US10981306B1 (en) Cryptographic system for secure command and control of remotely controlled devices
US7143696B2 (en) Remote digital firing system
US11725911B2 (en) Methods and apparatus for a conducted electrical weapon
US6283034B1 (en) Remotely armed ammunition
US20120011992A1 (en) Remote digital firing system
US20160327356A1 (en) Remote control weapon lock
US5046006A (en) Mutual missile control system
US20150241153A1 (en) Firearm safety systems and methods
US10782112B2 (en) Ammunition firing authorization system
US20150068093A1 (en) Remote control weapon lock
US20110174181A1 (en) Remote Explosion Detonation System
US10197350B2 (en) Remotely authorizing and disabling weapons
JP2005520115A (en) Detonator system and method for detonator system
CN113892011A (en) Integrated safe and dynamic protection zone system
US9979871B2 (en) Radio-frequency trigger signal system apparatus and method
US9967095B2 (en) Selective control of groups of detonators
Rudakevych et al. PackBot EOD firing system
US7055420B1 (en) Friendly fire avoidance/self-defense system
US20170116432A1 (en) System and methods for cyber-and-physically-secure high grade weaponry
CN111466247B (en) Catalytic bomb control system and launching method
US11892253B1 (en) Safety device to disable a firearm
Berman As Russo-American Tensions Rise, Nuclear Policy Must Stay Grounded
RO129740B1 (en) Security method and system for civil airports against terrorist attacks with portable surface-to-air missiles

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: SURCHARGE FOR LATE PAYMENT, MICRO ENTITY (ORIGINAL EVENT CODE: M3554); ENTITY STATUS OF PATENT OWNER: MICROENTITY

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, MICRO ENTITY (ORIGINAL EVENT CODE: M3551); ENTITY STATUS OF PATENT OWNER: MICROENTITY

Year of fee payment: 4