U.S. patent application number 13/156335 was filed with the patent office on 2012-05-31 for tracking weapon health and maintenance.
This patent application is currently assigned to VISIBLE ASSETS, INC.. Invention is credited to M. Jason August, RodGilchrist, John K. Stevens, Florin Tarcoci, Paul Waterhouse.
Application Number | 20120131828 13/156335 |
Document ID | / |
Family ID | 46125680 |
Filed Date | 2012-05-31 |
United States Patent
Application |
20120131828 |
Kind Code |
A1 |
August; M. Jason ; et
al. |
May 31, 2012 |
Tracking Weapon Health and Maintenance
Abstract
A system for tracking weapon health includes a low frequency
networked radio tag coupled with a firearm, said radio tag
configured to receive and send data signals; a reader configured to
be in operative communication with the tag antenna; and a display
configured to display data relating to weapon health. The radio tag
includes a shot sensor, a shot count register for tracking the
number of shots fired and cadence registers for tracking the
intervals between shots.
Inventors: |
August; M. Jason; (Toronto,
CA) ; RodGilchrist;; (Oakville, CA) ; Stevens;
John K.; (Stratham, NH) ; Tarcoci; Florin;
(Cornwall, CA) ; Waterhouse; Paul; (Selkirk,
CA) |
Assignee: |
VISIBLE ASSETS, INC.
Mississauga
CA
|
Family ID: |
46125680 |
Appl. No.: |
13/156335 |
Filed: |
June 8, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61352672 |
Jun 8, 2010 |
|
|
|
Current U.S.
Class: |
42/1.02 |
Current CPC
Class: |
F41A 19/01 20130101;
F41A 31/00 20130101; F41C 27/00 20130101 |
Class at
Publication: |
42/1.02 |
International
Class: |
F41C 27/00 20060101
F41C027/00 |
Claims
1. A system for tracking weapon health, the system comprising: a
low frequency networked radio tag coupled with the firearm, said
radio tag configured to receive and send data signals, the radio
tag comprising: a modem, a tag antenna operable at a low radio
frequency not exceeding 300 kilohertz, a transceiver operatively
connected to the tag antenna, said transceiver configured to
transmit and receive data signals at the low radio frequency, a
data storage device configured to store data comprising
identification data for identifying the firearm and shot count
data, a processor configured to process data received from the
transceiver and the data storage device and to transmit data to
cause said transceiver to emit an identification signal based upon
the identification data stored in said data storage device, a shot
count register operatively coupled with the processor for tracking
a number of shots fired, wherein the shot count register is
incremented each time a shot is fired, a plurality of cadence
registers operatively coupled with the processor for tracking an
interval between shots, a shot sensor for detecting when a shot has
been fired from the firearm, a timing mechanism for recording time
used to determine shot cadence, and a connector for a power source
to power the processor and the transceiver; a reader configured to
be in operative communication with the tag antenna; and a display
configured to display data relating to weapon health.
2. A system according to claim 1, wherein data is displayed
graphically.
3. A system according to claim 1, wherein data is displayed as a
histogram.
4. A system according to claim 1, wherein data relating to weapon
health includes shot count and interval history.
5. A system according to claim 1, wherein each shot fired is
assigned a wear value based on the number of the shot.
6. A system according to claim 1, wherein each shot fired is
assigned a wear value based on the cadence of the shot.
7. A system according to claim 1, further comprising a weapon
health calculator configured to calculate weapon health based on
usage of the firearm.
8. A system according to claim 7, wherein the weapon health
calculator calculates barrel temperature.
9. A system according to claim 8, wherein the heat differential of
each shot fired is a temperature gain, and the temperature gain
decays at a rate dependent upon the different between a barrel
temperature and ambient temperature over time.
10. A system according to claim 7, wherein the weapon health
calculator is further configured to calculate Mean Kinetic Shot
(MKS).
11. A system according to claim 7, wherein the weapon health
calculator is further configured to calculate weapon health based
on characteristics of the firearm.
12. A system according to claim 7, wherein the display is further
configured to graphically display the calculated weapon health.
13. A method for determining firearm health, comprising: assigning
a wear value to each shot fired from a firearm based on;
graphically displaying the wear value of each shot over a selected
time; and analyzing the display to determine whether performance of
the firearm changed over the selected time.
14. A method according to claim 13, wherein the wear value is
assigned based on cadence.
15. A method according to claim 13, wherein the wear value is
assigned based on barrel temperature.
16. A method according to claim 15, wherein barrel temperature is
calculated based on shot count and cadence.
17. A method according to claim 13 wherein the wear value is
assigned based on shot count.
Description
TRADEMARKS
[0001] RuBee.RTM. is a registered trademark of Visible Assets, Inc.
of the United States of America. Other names used herein may be
registered trademarks, trademarks or product names of Visible
Assets, Inc. or other companies.
BRIEF DESCRIPTION OF THE DRAWINGS
[0002] To describe the foregoing and other exemplary purposes,
aspects, and advantages, we use the following detailed description
of an exemplary embodiment of the invention with reference to the
drawings, in which:
[0003] FIG. 1 shows a first order interval histogram of 1,000
events;
[0004] FIG. 2 shows another first order interval histogram;
[0005] FIG. 3 shows a histogram of 383 shots;
[0006] FIG. 4 shows a normal probability plot of the histogram of
FIG. 1;
[0007] FIG. 5 shows a simulated weapon that fires at 13 shots/sec,
but slows down to 7 or 8 shots/sec;
[0008] FIG. 6 shows the right auto mode of the graph of FIG. 3;
[0009] FIG. 7 shows a normal probability distribution for the data
of FIG. 5;
[0010] FIG. 8 shows a plot of 1,000 shots over a course of 3,000
seconds;
[0011] FIG. 9 shows a predicted barrel temperature vs. time for the
data of FIG. 8;
[0012] FIG. 10 shows the MKS wear factor vs. time for 1,000 shots
as seen in FIG. 1;
[0013] FIG. 11 shows a histogram for 1,000 shots all in manual
mode;
[0014] FIG. 12 shows the MKS wear factor in manual mode;
[0015] FIG. 13 shows a radio tag embedded in the grip of a
handgun;
[0016] FIG. 14 is a block diagram of the components of the radio
tag, according to an embodiment of the present invention;
[0017] FIG. 15 shows an example of some of the data that may be
stored in the radio tag;
[0018] FIG. 16 shows an example of use and performance data
contained in the tag;
[0019] FIG. 17 shows a handheld reader used to read and enter data
to/from the radio tag; and
[0020] FIG. 18 is a flow chart of the process for implementing
radio tags on firearms, according to an embodiment of the present
invention.
[0021] While the invention as claimed can be modified into
alternative forms, specific embodiments thereof are shown by way of
example in the drawings and will herein be described in detail. It
should be understood, however, that the drawings and detailed
description thereto are not intended to limit the invention to the
particular form disclosed, but on the contrary, the intention is to
cover all modifications, equivalents and alternatives falling
within the scope of the present invention.
DETAILED DESCRIPTION
[0022] We describe a long wave RuBee.RTM. active tag system and
method for high order interval analytics for shot counting events
data that are diagnostic of a current maintenance state and general
health of a weapon.
[0023] Visible Assets, Inc. has developed signal processing methods
resident on a low power, IEEE 1902.1 (RuBee) enabled four bit
microprocessor, known as a RuBee Shot Counter. The chip includes a
custom amplifier as well as what is called a ThinFir, which is a
real-time finite impulse filter that converts a firearm shot into a
single shot event. The telemetric data communication is based on
IEEE 1902.1 and is integrated into a full weapons visibility
network that can be used for physical inventory, entry and exit
detection, and access control with RuBee ID badges, as well as
visibility and physical inventory of other mission critical assets.
The shot counting data and metrics contained in the RuBee tag may
be read by a handheld, or process free within the visibility
network. The tags have the advantage of being very small with a
battery life of tens of years using small Li coin size
batteries.
[0024] When any firearm is shot the barrel becomes worn.
Additionally, as the weapon is shot the parts (springs, screws, and
washers) in a gun that control the magazine and movement of
bullets, as well as the hammer and other moving parts are worn. In
many cases the status of these parts is directly proportional to
the number of shots that have been fired. Therefore, shot counting
and shot management using an electronic measurement system and
wireless tag has the value to track use and maintenance of a
weapon. After 3,000 rounds the manufacturer may recommend that all
springs should be changed, or after 10,000 rounds the barrel may
need to be replaced and so on. We have disclosed such a tag in a
prior invention using long wavelength magnetic waves.
[0025] In many weapons the wear and tear may be accelerated
depending upon how close the rounds were fired together. This is
especially true in automatic and semi-automatic weapons that can
fire up to 10-13 rounds per second. At this rate, the heat
generated from bullets can have a harmful affect on the barrel and
other moving parts, especially if it is sustained. In other words,
in automatic and semi-automatic weapons, 3,000 rounds at one shot
per second is acceptable, but 3,000 rounds shot at 10 rounds per
second may make the weapon unusable and unsafe.
[0026] The 30 Round Clip Cluster Problem.
[0027] An additional more complex statistical issue comes with high
speed automatic weapons. For example, assume a 30 round clip is
shot in automatic mode, exchanged with a 2-3 second delay, with a
next clip and a next clip. Therefore, 90 total rounds are shot. The
wear on the barrel and components will be significant and the
barrel may reach a temperature of 100 C. If the same clips are shot
in automatic mode, but exchanged after ten minutes of cool down
time, wear will be reduced. We call this the Clip Cluster problem.
First order interval statistics using histograms, described below,
will be identical in the two scenarios. A higher order statistic is
required to differentiate and detect use of the weapon in automatic
mode.
[0028] General Weapon Health and Diagnostics.
[0029] A third interesting issue is the performance of the weapon
itself and may be both an indicator of the user skills, as well as
an indicator of the maintenance state. The use of third and fourth
order correlations between rounds to detect interval variability
can be a good metric for the general health of the weapon.
[0030] We have developed unique statistical methods and applied
them to round counting to address the issues outlined above. While
advanced thermodynamic heating models are possible, a second
requirement is that the analytics must be simple and capable of
implementation on board using a 4 bit processor in real-time.
[0031] Methods.
[0032] A simple firearm stochastic model was developed that assumes
a gun could be fired up to 30 rounds per second in automatic mode
at a rate of 13 to 8 rounds per second. Random Gaussian variation
or jitter was added with controlled means and standard deviation.
Time between clips was also a parameter from 2-3 seconds to many
hundreds of minutes. Statistical methods were developed to simulate
barrel temperature making specific simple assumptions. All data was
analyzed using MatLab and Datadesk 6.0.
[0033] Weapons Wear Metrics.
[0034] The simplest metric is the number of shots counted (fired);
therefore the weapon life and maintenance can be defined by the
number of rounds fired. RuBee-enabled shot counters enable us to
now count the shots automatically. However, not all shots cause the
same amount of wear. For example, the first round through a cold
weapon produces a given amount of wear. The last round of three
clips fired at full auto produces significantly more wear.
[0035] Do we need to keep the last 90 intervals to produce a
reasonable wear meric? Does wear produced by a round depend on the
last 90 shot intervals? Yes, it can because the gun heats up faster
with bursts of short interval shots. But time stamping every round
is impractical. So we developed a simple real-time model that
converts shot interval history to barrel temperature along with a
set of simple equations. We add shot interval measurements shown in
the shot interval histogram of FIG. 1. 400 single shots shown on
the left-hand side; 600 shots in auto mode shown on the right-hand
side. This gives us a better picture of the "health" of the weapon
than just the shot count. Interval statistics provide much richer
information than just shot count statistics. A Delta Q from each
shot gives a temperature gain that decays at a rate dependent on
how much the barrel temperature is above ambient over time. A
temperature-based wear rate is measurable and the temperature model
is physically verifiable.
[0036] Weapons Wear Metric.
[0037] Mean Kinetic Shots (MKS) Wear Factor.
[0038] Key parameters for each weapon design has to be calibrated
and checked.
[0039] Field data will lead to refined understanding of evidence
based weapons healthcare.
[0040] For example, receiving information that a weapon jammed at
83 rounds merely indicates that there is a problem. With objective
MKS field data and evidence based weapons healthcare, we can
diagnose and repair weapon before it jams.
[0041] FIG. 1 shows 1,000 events. The cluster on the right is shots
in auto mode, and on the left are shots fired in manual mode. FIG.
2 expands the histogram in FIG. 1, limited to just shots in auto
mode. FIG. 3 expands the shots in manual mode. Several clear first
order diagnostics appear in both histograms. The wear factor for
shots in the 611 shots in auto mode will be much greater than the
wear factor in manual mode. In simple terms, this weapon has twice
as many short interval shots over long interval shots.
[0042] Finally, a normal probability plot of FIG. 1 seen in FIG. 4
shows consistent and predictable normal intervals for automatic
mode and, as might be expected, more erratic unpredictable
intervals for manual mode. If the auto mode normal plot were
erratic it would be an indicator that weapons were not properly
functioning.
[0043] A simple first order wear metric might be to assume that
wear at 10-13 Shots/Sec is twice that at under one round per
second. This ratio can be assigned to each weapon on a case by case
basis. Again we emphasize this does not take into account the
possibility of clip clusters that might lead to much higher wear,
but the simple first order histogram may be adequate for most auto
and semi-automatic weapons.
[0044] First Order Diagnostics
[0045] The first order interval statistics have the advantage of
being simple and easy to obtain in real-time within a weapon. They
also can be a strong indicator or diagnostic of the weapons'
health. For example, the histogram seen below in FIG. 5 shows a
simulated weapon that fires at 13 Shots/Sec, but slows down because
of mechanical issues over time to 7 or 8 Shots/Sec. This is the
expected behavior for a weapon in poor health.
[0046] The left peak shows manual shots and the right peak shows
rounds shot in auto mode. It is clear this histogram has a much
lower mean and standard deviation. The right auto mode is shown in
FIG. 6. The same 611 shots now have a distribution with a mean of
8.93 much slower, and a standard deviation of 1.40 much wider
variability in shot intervals. The left expanded graph is the same
as that shown in FIG. 3. The first order statistics can provide
information about the general health of the weapon in the
field.
[0047] FIG. 7 illustrates the normal probability distribution, and
again, as can be seen, more, variability and much larger standard
deviation over normal simulation is easy to detect. MKS--Higher
Order Diagnostic Statistics.
[0048] In an attempt to address the Clip Cluster problem wherein
many clips are shot at once in short intervals, we developed a Mean
Kinetic Shot (MKS) algorithm that takes into account both heating
and cooling of the mechanisms and barrel. The MKS factor is
calculated using very simple assumptions, such as: a) barrel
temperature increases by one unit each time the weapon is shot; b)
barrel temperature decreases by a 0.1 unit every second; and c) as
the barrel temperature increases, wear based on a single round will
also increase.
[0049] Assumption a) is most accurate, that a round will increase
the temperature of the barrel as it passes though the barrel the
same amount at 13 Shots/Sec or 0.5 Shots per second.
[0050] The assumption b) that the barrel cools as a function of
time is also correct although it is more likely the cooling is
exponential and not linear. For simplicity, in this model we have
to assume that it is linear with time.
[0051] Assumption c) is again simplistic and we have assumed that
it is linear with temperature. It is more likely a higher order
function that must be determined empirically for each weapon.
However, for the sake of simplicity we have not scaled this as a
factor, but that will become an important factor and differentiator
between weapons.
[0052] FIG. 8 shows the same data seen in FIG. 1. 1,000 shots over
course of 3,000 seconds. Some in bursts of 3 to 4 clips in
automatic mode, some manual. The Y axis is shots per second and the
X axis is time.
[0053] FIG. 9 illustrates the new metric that calculates barrel
temperature. On the left it can be seen that the barrel temperature
goes up rapidly because four 30 round clips were shot within a few
seconds of each other. The important finding here is that a simple
model produces results that are consistent with what we see with an
actual weapon. The most critical statistic is the Mean Kinetic
Shots wear factor. If we assume a round in a hot barrel will
produce more wear more than a round shot through a cold barrel we
can compute a MKS factor by simply summing rounds and temperature.
Again, this will be scaled differently for different weapons. It
can be scaled to empirical data weapon by weapon.
[0054] FIG. 10 shows the MKS wear factor vs time. You can see
clearly that wear is at its maximum rate of increase during clip
cluster bursts on left. In full auto mode the MKS factor is 6,045
for these 1,000 rounds. A second simulation in manual mode (no auto
rounds at all is shown in FIG. 11). The mean is 1.29 Shots/Sec and
the standard deviation 0.72. The wear of the weapon should be
significantly reduced over the same 1,000 shots in full auto
mode.
[0055] FIG. 12 shows the MKS wear factor vs time for 1,000 shots in
manual mode seen in the histogram of FIG. 11. The MKS wear factor
is 1,847 in manual mode vs. 6,045 in full auto mode.
CONCLUSIONS
[0056] We have presented the first order and second order
statistical methods created for analysis of shot counting data. We
have made simple assumptions to develop these methods. These
assumptions may become more complex functions over time, but the
principals developed here can be scaled based on empirical testing
of individual weapons. That is by taking into account the weapon
wear and health will be related to number of shots, but how those
shots are distributed in time will also be a significant diagnostic
factor.
[0057] We believe these methods can be used to predict wear and
parts replacement in firearms, as well as serve as a real-time
diagnostic for the health and safety of a firearm. These first
order and second order analytics are simple enough to be calculated
in real-time in a RuBee shot counting tag.
[0058] RuBee Fireat Visibility Network--Background.
[0059] The Firearm Visibility Network (FVN) provides for the
identifying, monitoring and tracking of firearms within a network.
RuBee.RTM. is a radio tag technology designed to provide full asset
visibility and identification in harsh environments. The tags use
the standard, IEEE P1902.1, "RuBee Standard for Long Wavelength
Network Protocol," which allows for networks encompassing thousands
of radio tags operating below 450 KHz. RuBee.RTM. networks provide
for real-time tracking under harsh environments, e.g., near metal
and water and in the presence of electromagnetic noise. RuBee.RTM.
radio tags, which can be either active or passive, have proven
battery lives of ten years or more using inexpensive lithium
batteries. The tags are programmable, in contrast to RFID tags.
[0060] The RuBee.RTM. Firearm Visibility Network (FVN) provides
full visibility for storage, transport, and use of handguns,
rifles, revolvers, and other weapons in high security government
and law enforcement (LE) settings. The FVN may optionally include
electronic identity cards to tie specific individuals to
use/transport of weapons. See "Low Frequency Wireless
Identification Device," U.S. application Ser. No. 11/633,751 filed
Dec. 4, 2006. The Firearm Visibility Platform may also provide
independent audit trails for use in transport and storage of
firearms that meet 21CFRPart11 compliance regulations and adhere to
the Department of Defense (DoD) Directive 5015.2, "Department of
Defense Records Management Program," providing implementation and
procedural guidance on records management in the DoD.
[0061] Background on RuBee.RTM. Radio Tags.
[0062] Radio tags communicate via magnetic (inductive
communication) or electric radio communication to a base station or
reader, or to another radio tag. A RuBee.TM. radio tag works
through water and other bodily fluids, and near steel, with an
eight to fifteen foot range, a five to ten-year battery life, and
three million reads/writes. It operates at 132 KHz and is a full
on-demand peer-to-peer, radiating transceiver.
[0063] RuBee.RTM. is a bidirectional, on-demand, peer-to-peer
transceiver protocol operating at wavelengths below 450 KHz (low
frequency). A transceiver is a radiating radio tag that actively
receives digital data and actively transmits data by providing
power to an antenna. A transceiver may be active or passive. The
RuBee.RTM. standard is documented in the IEEE Standards body as
IEEE P1902.1.TM..
[0064] Low frequency (LF), active radiating transceiver tags are
especially useful for visibility and for tracking both inanimate
and animate objects with large area loop antennas over other more
expensive active radiating transponder high frequency (HF)/ultra
high frequency (UHF) tags. These LF tags function well in harsh
environments, near water and steel, and may have full two-way
digital communications protocol, digital static memory and optional
processing ability, sensors with memory, and ranges of up to 100
feet. The active radiating transceiver tags can be far less costly
than other active transceiver tags (many under one dollar), and
often less costly than passive back-scattered transponder RFID
tags, especially those that require memory and make use of EEPROM.
With an optional on-board crystal, these low frequency radiating
transceiver tags also provide a high level of security by providing
a date-time stamp, making full AES (Advanced Encryption Standard)
encryption and one-time pad ciphers possible.
[0065] One of the advantages of the RuBee.RTM. tags is that they
can transmit well through water and near steel. This is because
RuBee.RTM. operates at a low frequency. Low frequency radio tags
are immune to nulls often found near steel and liquids, as in high
frequency and ultra high-frequency tags. This makes them ideally
suited for use with firearms made of steel. Fluids have also posed
significant problems for current tags. The RuBee.RTM. tag works
well through water. In fact, tests have shown that the RuBee.RTM.
tags work well even when fully submerged in water. This is not true
for any frequency above 1 MHz. Radio signals in the 13.56 MHz range
have losses of over 50% in signal strength as a result of water,
and anything over 30 MHz have losses of 99%.
[0066] Another advantage is that RuBee.RTM. tags can be networked.
One tag is operable to send and receive radio signals from another
tag within the network or to a reader. The reader itself is
operable to receive signals from all of the tags within the
network. These networks operate at long-wavelengths and accommodate
low-cost radio tags at ranges to 100 feet. The standard, IEEE
P1902.1.TM., "RuBee Standard for Long Wavelength Network Protocol,"
will allow for networks encompassing thousands of radio tags
operating below 450 KHz.
[0067] The inductive mode of the RuBee.RTM. tag uses low
frequencies, 3-30 kHz VLF or the Myriametric frequency range,
30-300 kHz LF in the Kilometric range, with some in the 300-3000
kHz MF or Hectometric range (usually under 450 kHz). Since the
wavelength is so long at these low frequencies, over 99% of the
radiated energy is magnetic, as opposed to a radiated electric
field. Because most of the energy is magnetic, antennas are
significantly (10 to 1000 times) smaller than 1/4 wavelength or
1/10 wavelength, which would be required to efficiently radiate an
electrical field. This is the preferred mode.
[0068] As opposed to the inductive mode radiation above, the
electromagnetic mode uses frequencies above 3000 kHz in the
Hectometric range, typically 8-900 MHz, where the majority of the
radiated energy generated or detected may come from the electric
field, and a 1/4 or 1/10 wavelength antenna or design is often
possible and utilized. The majority of radiated and detected energy
is an electric field.
[0069] RuBee.RTM. tags are also programmable, unlike RFID tags. The
RuBee.RTM. tags may be programmed with additional data and
processing capabilities to allow them to respond to sensor-detected
events and to other tags within a network.
[0070] Referring now in specific detail to the drawings and
particularly FIG. 13, there is shown a RuBee.RTM. radio tag 100
embedded in the handle or grip of a handgun, according to an
embodiment of the present invention. As shown in FIG. 13, the radio
tag 100 is small enough to easily fit into a hollow formed into the
grip of the handgun. The firearm shown in this example is a SIG
SAUER.RTM. handgun, but the invention as discussed is not limited
to handguns. The radio tag 100 could be advantageously used with
any type of firearm or indeed most types of weaponry (swords,
knives, and so forth) and some ammunition.
[0071] The radio tag 100 as shown in this example is placed in the
handgun grip, but it could be placed in another part of the firearm
if a different firearm form factor is used. The placement of the
radio tag 100 depends on the form factor of the weapon and the size
of the weapon. The tag 100 in this example is embedded into a
cavity of the inside of the grip. Embedding the tag 100 in this
manner is the preferred embodiment. Alternatively, the tag 100 may
be affixed to the firearm by attaching it to the outside surface of
the weapon, but this is not recommended.
[0072] The tag 100 may be constructed with a waterproof housing
made to sustain wear and tear, yet remain lightweight.
[0073] FIG. 14 is a simplified diagram showing the functional
components of the radio tag 100 according to an embodiment of the
present invention. The basic components of the tag 100 are: a
RuBee.RTM. modem 1120, a RuBee.RTM. chipset 1125, an antenna 1180,
an energy source 1140, a microprocessor 1110, and a memory 1130. In
addition to these basic components, the tag 100 may also contain
optional components to increase its functionality. These optional
components are shown with dashed lines in FIG. 14 and they will be
discussed in detail later on in this discussion.
[0074] Continuing with the discussion of the basic components, the
tag 100 contains a custom RuBee.RTM. radiofrequency modem 1120,
preferably created on a custom integrated circuit using four micron
CMOS (complementary metal-oxide semiconductor) technology. This
custom modem 1120 is a transceiver, designed to communicate
(transmit and receive radio signals) through an omni-directional
loop antenna 1180. All communications take place at very low
frequencies (e.g. under 300 kHz). By using very low frequencies the
range of the tag 100 is somewhat limited; however power consumption
is also greatly reduced. Thus, the receiver of modem 1120 may be on
at all times and hundreds of thousands of communication
transactions can take place, while maintaining a life of many years
(up to 15 years) for battery 1140.
[0075] Operatively connected to the modem 1120 is a RuBee.RTM.
chipset 1125. The chipset 1125 is configured to detect and read
analog voltages. The chipset 1125 is operatively connected to the
modem 1120 and the microprocessor 1110.
[0076] The antenna 1180 shown in FIG. 14 is a small loop antenna
with a range of eight to fifteen feet. It is preferably a thin wire
wrapped many times around the inside edge of the tag housing. A
reader or monitor may be placed anywhere within that range in order
to read signals transmitted from the tag 100 or the tag's
sensor(s).
[0077] The energy source shown in this example is a battery 1140,
preferably a lithium (Li) CR2525 battery approximately the size of
an American quarter-dollar with a five to fifteen year life and up
to three million read/writes. Note that only one example of an
energy source is shown. The tag 100 is not limited to a particular
source of energy, the only requirement is that the energy source is
small in size, lightweight, and operable for powering the
electrical components.
[0078] The tag 100 also includes a memory 1130 and a four bit
microprocessor 1110, using durable, inexpensive 4 micron CMOS
technology and requiring very low power.
[0079] What has been shown and discussed so far is a basic
embodiment of the tag 100. With the components as discussed, the
tag 100 can perform the following functions: 1) the tag 100 can be
configured to receive (via the modem 1120) and store data about the
firearm to which it is attached and/or the network to which it
belongs (in the memory 1130); 2) the tag 100 can emit signals which
are picked up by a reader, the signals providing data about the
firearm; 3) the tag 100 can store data in the form of an internet
protocol address so that the tag's data can be read on the
internet.
[0080] Note that the electrical components of the tag 100 are
housed within the body of the' tag 100 and are completely enclosed
within the tag 100 when the device is sealed. This makes the tag
100 waterproof and tamperproof.
[0081] Referring to FIG. 15 there is shown an example of some of
the data that may be stored in the radio tag 100. In FIG. 15 there
is listed a weapon serial number, a model, manufacture date, owner,
and user of the weapon. It may be desirable to hide some or all of
this data. This can easily be done using known encryption methods
such as AES public/private key encryption. Also, the data may be
secured by requiring a password.
[0082] The tag 100 may contain additional features and components
as will be discussed here below.
OTHER EMBODIMENTS
[0083] The functionality of the tag 100 can be greatly enhanced
with the addition of optional components. One of these optional
components is a sensor 1150. The RuBee.RTM. chipset has the ability
to detect and read analog voltages from various optional detectors
1150. Sensors 1150 may be included to provide positional
information, use information, and other data to the microprocessor
1110. The number of sensors and the type of sensors depend on the
intended use of the tag 100. For example, an activity parameter
sensor may be used. The activity parameter sensor detects the
number of shots fired by detecting the number of projectiles
remaining in the cartridge. Another sensor 1150 may be able to
detect if the tag 100 has been removed from the handgun. In fact,
additional sensors may be placed on the back of the tag 100 for
just this purpose. Each instance of motion and/or acceleration is a
status event and it is detected by the sensor 1150. Sensors 1150
are ideal for providing an event history of the event statuses they
detect. Other sensors not mentioned here may be advantageously used
within the spirit and scope of the invention.
[0084] FIG. 16 shows an example of use and performance data that
may be contained in the radio tag 100, as provided by the onboard
sensors 1150. For example, the number of shots fired, the last shot
date, the number of the last shot, the maximum temperature, and the
last timestamp when maintenance was performed.
[0085] Additionally, a clock 1160 may be included inside the tag
100. The clock 1160 can provide a time history to correspond with
status events detected by the sensors 1150. The clock 1160 can be
configured to provide a time signal to correspond with a signal
emitted by a sensor 1150. The processor 1110 records the time
signal together with the sensor signal in order to provide a
temporal history that can be mapped to a status history. The
history data can be stored in the memory 1130 along with status
events. Tying events to a time stamp provides for a more meaningful
history of events. For example, mapping shots fired to a date and
time affords very useful information.
[0086] The tag 100 may be programmed to emit a warning signal when
at least one of the sensors 1150 detects a condition that meets a
predetermined value. For example, a sensor 1150 in the tag 100 may
emit a signal when the ammunition falls below a predetermined
amount. A jog sensor 1150 may emit a signal when the weapon has
been dropped. A signal could also be emitted when it is time to
perform maintenance on the weapon.
[0087] To secure the stored data in the tag 100, an onboard crystal
may be used to provide optical encoding using liquid crystal
spatial light modulators. One-time pad ciphers are another security
measure that can be advantageously used with a radio tag 100. Using
known security measures with the radio tag 100 is recommended when
needed to assure that the tag data does not fall into the wrong
hands.
[0088] FIG. 17 shows a handheld reader that may be used to read and
enter data to/from the radio tag 100. Although this method has the
disadvantage of requiring an individual to be in proximity to the
firearm, it has the advantage of being a low-cost way of quickly
gathering data while out in the field and away from a computer. The
handheld reader can be optimized with a USB port to facilitate
downloading of data to a computer. The antenna 1180 within the tag
100 is operable up to approximately fifteen feet. Without any
additional antennas, the handheld reader would need to be within a
fifteen-foot range of the tag 100 and positioned correctly to pick
up the transmitted signals from the tag 100. Of course, the
transmission field of the tag antenna 1180 can be amplified by
employing additional antennas as shown in FIG. 5. The range of the
tag 100 can be amplified exponentially using additional
antennas.
[0089] IEEE P1902.1 offers a real-time, tag-searchable protocol
using IPv4 addresses and subnet addresses linked to asset
taxonomies that run at speeds of 300 to 9,600 Baud. RuBee.RTM.
Visibility Networks are managed by a low-cost Ethernet enabled
router 1190. Individual tags and tag data may be viewed on a
stand-alone system or a web server from anywhere in the world. Each
RuBee.RTM. tag, if properly enabled, can be discovered and
monitored over the World Wide Web using popular search engines
(e.g., Google) or via the Visible Asset's .tag Tag Name Server.
Gathering information about one weapon is important. Equally
important, if not more so, is gathering information about all of
the weapons within a network. Note that in this discussion we refer
to a "network" of weapons as all of the weapons within one
networked RuBee.RTM. tag system. A network of weapons may or may
not be restricted to one affiliation (such as a police department)
or group of weapons (all revolvers). It is critical to track the
shots fired, event histories, and condition of a network to be able
to predict future events and to know what conditions will need to
be changed and/or further monitored. It is well known in the art of
database software that manipulating data in different ways produces
different views of the data. Data from RuBee.RTM. tags 100 can be
used for various purposes within the scope of this invention.
[0090] Optionally, a global positioning unit (GPS) 1195 may be
operatively connected to the router 1190 to pick up the position
signals detected by the tag's 100 optional positional sensor 1150
and record that information. The router 1190 and GPS 1195 unit can
be placed in separate locations or may be co-located in a strategic
location for optimal visibility of the firearm.
[0091] FIG. 18 is a flow chart 1200 of the process of implementing
RuBee.RTM.-enabled tags to provide automatic, remote, and wireless
identification, monitoring, and tracking of weapons, according to
the present invention. The process begins at step 1210 when a tag
100 is attached to a weapon. The tag 100 may be securely embedded
in a firearm as shown in FIG. 1, or it may be affixed to the
firearm in such a way that it is easily removable. A unique
identifier is assigned to the tag 100. This unique identifier
corresponds to the weapon to which the tag 100 is attached. The
identifier can be programmed into the tag 100 either before or
after it is attached.
[0092] Next in step 1220, other data concerning the weapon is
entered. This data may be the model number, the purchase date, the
affiliation (agency, police department), and/or the maintenance
record of the weapon, to name just a few data items that can be
stored in the tag 100. The tag 100 is enabled to constantly
transmit low frequency radio signals through its modem 1120. In
step 1230 the identification data from the transceiver 1120 of the
radio tag 100 is interrogated by the radio tag 100 with radio
frequency interrogation signals at a low radio frequency not
exceeding 450 kilohertz. The radio tag 100 may also transmit a
signal or signals upon detection of a status event, such as a
change in ammunition status of the weapon.
[0093] In step 1240 these signals are picked up by a reader
operable to receive low frequency radio signals below 450 kilohertz
within range of the tag antenna 1180. The reader may be a handheld
reader, such as a wand reader. The signals may also be picked up by
a router 1190, or another tag in the network.
[0094] In step 1250 the reader, router 1190, or handheld reader
transmits the data via a wireless connection to a computer. The
data may be encrypted with known encryption methods.
[0095] In step 1260 the transmitted data, after it is decrypted, if
necessary, is viewable through a computer. The data may be accessed
from a database configured to process the tag data and displayed
through a computer monitor, or a personal digital assistant (PDA)
screen, a cell phone display, or any other display means according
to advancing technology. The data may also be viewable via web
browser. When the data is available on the Internet, it then
becomes critical to safeguard the data, either by requiring a login
and password, or using data encryption methods known in the art. In
one embodiment, the login name may be the serial number of the
weapon.
[0096] In step 1270, the data gathered from the tag 100 or all of
the tags in the network may be compiled into a report such as that
shown. The report may be confined to one particular weapon, showing
event and time histories for that weapon, or it may report on some
or all of the weapons within an inventory shelf or a network. The
report may be produced daily, monthly, seasonally, or yearly. The
report may be automatically generated or may be generated upon user
request. Optionally, a report may be auto-generated according to
data received from the tag 100 which meets a pre-determined
condition. For example, a user might want a report on a particular
weapon generated when an ammunition sensor registers that the
weapon has been fired. The report may be viewable on the Internet
and/or distributed to appropriate personnel.
[0097] The purpose of generating reports is to provide information
which can be used for predicting future trends and/or improving a
situation, and/or for analyzing performance. Information gathered
from a report may indicate that a change is necessary. The change
may be a change in the data entered into the tag 100, or the data
collected by the tag 100, or the position and/or frequencies of the
equipment used to read the tags 100. You will recall that
RuBee.RTM. tags 100 are programmable, unlike RFID tags 100.
[0098] Therefore, in step 1280 information gathered from a report
may be used to add to or change the programming of the tags. To
implement this, a user would make any needed changes on a computer.
The data is transmitted to a RuBee.RTM. router 1190 which in turn
communicates with a radio tag 100 through an antenna (either the
tag antenna directly or a field antenna). The modem 1120 of the tag
100, using the chipset 1125 transmits the signals to the processor
1110. The processor 1110 records the data and makes the necessary
changes. Many other additions and modifications can be made to the
data to assist an end user in monitoring and tracking weapons
within a network.
* * * * *