Patent Grant
10080971
The invention relates to sensing systems monitoring applications in sports, shipping, training, medicine, fitness, wellness and industrial production. The invention specifically relates to sensing and reporting events associated with movement, environmental factors such as temperature, health functions, fitness effects, and changing conditions.
The movement of objects and persons occurs continuously but is hardly quantified. Rather, typically only the result of the movement is known (i.e., object X moved from point A to point B; or, person Y ran to the store). Advances in technology have provided some quantification of movement. For example, GPS products now assist in determining the location of golf carts, vehicles and persons.
However, the detail of movement, minute to minute, second to second, is still not generally determinable in the prior art. For example, the movement of tangible objects typically involves (a) the shipment or carrying of goods and (b) electro-mechanical or motorized apparatus (e.g., planes, trains, automobiles, robots). The exact movements of such objects, and the conditions that they are subjected to, from point to point, are only qualitatively known. By way of example, a package is moved from location to location through delivery services like FEDERAL EXPRESS or UPS; however what occurred during transportation, and what transpired to the package, is anyone's guess. Occasionally, an object within the package is broken, indicating that the package experienced excessive abuse; but whose fault it is, or how or when it happened, are not known. What environments the package experienced is also not readily known.
The movement of persons, on the other hand, typically involves-human-powered transportation, e.g., facilitated by biking, a wheelchair, or a motorized vehicle, e.g., a car. Body movement involved in transportation is subjected to many forces, some of which are dangerous. But the prior art does not provide for this knowledge; there is no effective way, currently, to efficiently quantify human movement. In sports, physical fitness, and training, precise information about movement would assist in many ways. By way of example, how effective a hand strike is in karate or boxing is, today, only qualitatively known. Quantitative feedback would be beneficial.
It is, accordingly, one feature of the invention to provide systems and methods addressing the afore-mentioned difficulties. A further feature of the invention is to provide methods and devices to quantify movement in a number of applications. Another feature of the invention is to monitor and report meaningful environment information such as temperature and humidity. These and other features will be apparent in the description that follows.
Movement Monitoring Devices
In one aspect, the invention provides a movement monitor device (“MMD”) including an adhesive strip, a processor, a detector, and a communications port. In another aspect, two or more of the processor, port and detector are combined in a single application specific integrated circuit (“ASIC”). In one aspect the detector is an accelerometer, and preferably an accelerometer embedded into silicon within the ASIC. In other aspects, the detector is one of a strain gauge, force-sensing resistor, and piezoelectric strip. In still another aspect, the MMD includes a battery. In the preferred aspect of the invention, the MMD and battery are packaged in a protective wrapper. Preferably, the battery is packaged with the MMD in such a way that it does not “power” the MMD until the wrapper is removed. Preferably, the MMD includes a real time clock so that the MMD tags “events” (as hereinafter defined) with time and/or date information.
In yet another aspect, the MMD with adhesive strip collectively take a form similar to an adhesive bandage. More particularly, the adhesive strip of the invention is preferably like or similar to the adhesive of the adhesive bandage; and the processor (or protective wrapper) is embedded with the strip much the way the cotton is with the adhesive bandage. Preferably, a soft material (e.g., cotton or cloth) is included to surround the processor so as to (a) soften contact of rigid MMD components with a person and/or (b) protect the processor (and/or other components of the MMD). In still another aspect, the battery is also coupled with the soft material. In still another aspect, the processor and other elements of the MMD are combined into a single system-on-chip integrated circuit. A protective cover may surround the chip to protect the MMD from breakage.
In one aspect, one MMD of the invention takes a form similar to a smart label, with an adhesive substantially disposed with the label, e.g., on one side of the label. The adhesive strip of this MMD includes all or part of the back of the label with adhesive or glue permitting attachment of the label to other objects (or to a person).
In still another aspect, the MMD of the invention takes the form of a rigid monolithic that attaches to objects through one of known techniques. In this aspect, the device has a processor, communications port, and detector. A battery is typically included with the MMD. The MMD is attached to objects or persons by one of several techniques, including by glue or mechanical attachment (e.g., a pin or clip). An MMD of this aspect can for example exist in the form of a credit card, wherein the communications port is either a contact transponder or a contactless transponder. The MMD of one aspect includes a magnetic element that facilitates easily attaching the MMD to metal objects.
In operation, the MMD of the invention is typically interrogated by an interrogation device (“ID”). The MMD is responsive to the ID to communicate information within the MMD and, preferably, over secure communications protocols. By way of example, one MMD of the invention releases internal data only to an ID with the correct passwords and/or data protocols. The ID can take many forms, including a cell phone or other electronic device (e.g., a MP3 player, pager, watch, or PDA) providing communications with the MMD transmitter
However, in another aspect, the MMD communicates externally to a remote receiver (“RR”). The RR listens for data from the MMD and collects that data for subsequent relay or use. In one aspect, the MMD's communications port is a one-way transmitter. Preferably, the MMD communicates data from the MMD to the RR either (a) upon the occurrence of an “event” or (b) in repeated time intervals, e.g., once every ten minutes. Alternatively, the MMD's communication port is a transceiver that handshakes with the RR to communicate data from the MMD to the RR. Accordingly, the MMD responds to data requests from the RR, in this aspect. In still another aspect, the RR radiates the MMD with transponder frequencies; and the MMD “reflects” movement data to the RR.
Accordingly, the communications port of one aspect is a transponder responsive to one or more frequencies to relay data back to an ID. By way of example, these frequencies can be one of 125 kHz and 13.56 MHz, the frequencies common with “contactless” RFID tags known in the art. In other aspects, communications frequencies are used with emission power and frequencies that fall within the permissible “unlicensed” emission spectrum of part 15 of FCC regulations, Title 47 of the Code of Federal Regulations. In particular, one desirable feature of the invention is to emit low power, to conserve battery power and to facilitate use of the MMD in various environments; and therefore an ID is placed close to the MMD to read the data. In other words, in one aspect, wireless communications from the MMD to the ID occurs over a short distance of a fraction of an inch to no more than a few feet. By way of example, as described herein, one ID of the invention takes the form of a cell phone, which communicates with the MMD via one or more secure communications techniques. Data acquired from the MMD is then communicated through cellular networks, if desired, to relay MMD data to end-users.
Or, in another aspect, the ID has a larger antenna to pick up weak transmission signals from a MMD at further distances separation.
In another aspect, the communications port is an infrared communications port. Such a port, in one aspect, communicates with the cell phone in secure communication protocols. In other aspects, an ID communicates with the infrared port to obtain the data within the MMD.
In yet another aspect, the communications port includes a transceiver. The MMD listens for interrogating signals from the RR and, in turn, relays movement “event” data from the MMD to the RR. Alternatively, the MMD relays movement “event” data at set time intervals or when the MMD accumulates data close to an internal storage limit. In one aspect, thereby, the MMD include internal memory; and the MMD stores one or more “event” data, preferably with time-tag information, in the memory. When the memory is nearly full, the MMD transmits the stored data wirelessly to a RR. Alternatively, stored data is transmitted to an IR when interrogated. In a third alternative, the MMD transmits stored data at set intervals, e.g., once per ½ hour or once per hour, to relay stored data to a RR. Other transmission protocols can be used without departing from the scope of the invention.
In still another aspect, data from the MMD is relayed to an ID through “contact” communication between the ID and the communications port. In one aspect, the MMD includes a small conductive plate (e.g., a gold plate) that contacts with the ID to facilitate data transfer. Smart cards from the manufacturer GEMPLUS may be used in such aspects of the invention.
In one aspect, the MMD includes a printed circuit board “PCB”). A battery—e.g., a 2032 or 1025 Lithium coin cell—is also included, in another aspect of the invention. To make the device small, the PCB preferably has multilayers—and two of the internal layers have a substantial area of conducting material forming two terminals for the battery. Specifically, the PCB is pried apart at one edge, between the terminals, and the battery is inserted within the PCB making contact and providing voltage to the device. This advantageously removes then need for a separate and weighty battery holder.
In another aspect, the PCB has first and second terminals on either side of the PCB, and a first side of the battery couples to the first terminal, while a clip connects the second side of the battery to the second terminal, making the powered connection. This aspect advantageously removes the need for a separate and weighty battery holder.
In still another aspect, a terminal is imprinted on one side of the PCB, and a first side of the battery couples to that terminal. A conductive force terminal connects to the PCB and the second side of the battery, forming a circuit between the battery and the PCB.
By way of background for transponder technology, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 6,091,342 and U.S. Pat. No. 5,541,604.
By way of background for smart card and smart tag technology, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 6,151,647; U.S. Pat. No. 5,901,303. U.S. Pat. No. 5,767,503; U.S. Pat. No. 5,690,773; U.S. Pat. No. 5,671,525; U.S. Pat. No. 6,043,747; U.S. Pat. No. 5,977,877; and U.S. Pat. No. 5,745,037.
By way of background for adhesive bandages, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 5,045,035; U.S. Pat. No. 5,947,917; U.S. Pat. No. 5,633,070; U.S. Pat. No. 4,812,541; and U.S. Pat. No. 3,612,265.
By way of background for pressure and altitude sensing, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 5,178,016; U.S. Pat. No. 4,317,126; U.S. Pat. No. 4,813,272; U.S. Pat. No. 4,911,016; U.S. Pat. No. 4,694,694; U.S. Pat. No. 4,911,016; U.S. Pat. No. 3,958,459.
By way of background for rotation sensors, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 5,442,221; U.S. Pat. No. 6,089,098; and U.S. Pat. No. 5,339,699. Magnetorestrictive elements are further discussed in the following patents, also incorporated herein by reference: U.S. Pat. No. 5,983,724 and U.S. Pat. No. 5,621,316.
In accord with one aspect of the invention, the communications port is one of a transponder (including a smart tag or RFID tag), transceiver, or one-way transmitter. In other aspects, data from the MMD is communicated off-board (i.e., away from the MMD) by one of several techniques, including: streaming the data continuously off-board to get a real-time signature of data experienced by the MMD; transmission triggered by the occurrence of an “event” as defined herein; transmission triggered by interrogation, such as interrogation by an ID with a transponder; transmission staggered in “bursts” or “batches,” such as when internal storage memory is full; and transmission at predetermined intervals of time, such as every minute or hour.
In one preferred aspect of the invention, the above-described MMDs are packaged like an adhesive bandage. Specifically, in one aspect, one or more protective strips rest over the adhesive portion of the device so as to protect the adhesive until the protective strips are removed. The strips are substantially stick-free so that they are easily removed from the adhesive prior to use. In another aspect, a “wrapper” is used to surround the MMD; the wrapper for example similar to wrappers of adhesive bandages. In accord with one preferred aspect, the battery electrically couples with the electronics of the MMD when the wrapper is opened and/or when the protective strips are removed. In this way, the MMD can be “single use” with the battery energizing the electronics only when the MMD is opened and applied to an object or person; the battery power being conserved prior to use by a decoupling element associated with the wrapper or protective strips. Those skilled in the art should appreciate that other techniques can be used without departing from the scope of the invention.
The MMDs of the invention are preferably used to detect movement “metrics,” including one or more of airtime, speed, power, impact, drop distance, jarring and spin. WO9854581A2 is incorporated herein by reference as background to measuring speed, drop distance, jarring, impact and airtime. U.S. Pat. Nos. 6,157,898, 6,151,563, 6,148,271 and 6,073,086, relating to spin and speed measurement, are incorporated herein by reference. In one aspect, the detector and processor of the MMD collectively detect and determine “airtime,” such as set forth in U.S. Pat. No. 5,960,380, incorporated herein by reference. By way of example, one detector is an accelerometer, and the processor analyzes acceleration data from the accelerometer as a spectrum of information and then detects the absence of acceleration data (typically in one or more frequency bands of the spectrum of information) to determine airtime. In another aspect, the detector and processor of the MMD collectively detect and determine drop distance. By way of example, one drop distance detector is a pressure sensor, and the processor analyzes data from the pressure sensor to determine changes in pressure indicating altitude variations (a) over a preselected time interval, (b) between a maximum and minimum altitude to assess overall vertical travel, and/or (c) between local minimums and maximums to determine jump distance. By way of a further example, a drop distance detector is an accelerometer, and the processor analyzes data from the accelerometer to determine distance, or changes in distance, in a direction perpendicular to ground, or perpendicular to forward movement, to determine drop distance.
In one preferred aspect, the accelerometer has “free fall” capability (e.g., with near zero hertz detection) to determine drop distance (or other metrics described herein) based, at least on part, on free fall physics. This aspect is for example useful in detecting dropping events of packages in shipment.
In another aspect, the detector and processor of the MMD collectively detect and determine spin. By way of example, one detector is a magnetorestrictive element (“MRE”), and the processor analyzes data from the MRE to determine spin (rotation per second, number of degrees, and/or degrees per second) based upon the MME's rotation through the earth's magnetic fields. By way of a further example, another detector is a rotational accelerometer, and the processor analyzes data from the rotational accelerometer to determine spin. In another aspect, the detector and processor of the MMD collectively detect and determine jarring, power and/or impact. By way of example, one detector is an accelerometer, and the processor analyzes data from the accelerometer to determine the jarring, impact and/or power. As used herein, jarring is a function a higher power of velocity in a direction approximately perpendicular to forward movement (typically in a direction perpendicular to ground, a road, or a floor). As used herein, power is an integral of filtered (and preferably rectified) acceleration over some preselected time interval, typically greater than about ½ second. As used herein, impact is an integral of filtered (and preferably rectified) acceleration over a time interval less than about ½ second. Impact is often defined as immediately following an “airtime” event (i.e., the “thump” of a landing).
In one aspect, the MMD continuously relays a movement metric by continuous transmission of data from the detector to a RR. In this way, a MMD attached to a person may beneficially track movement, in real time, of that person by recombination of the movement metrics at a remote computer. In one aspect, multiple MMDs attached to a person quantify movement of a plurality of body parts or movements, for example to assist in athletic training (e.g., for boxing or karate). In another aspect, multiple MMDs attached to an object quantify movement of a plurality of object parts or movements, for example to monitor or assess different components or sensitive parts of an object. For example, multiple MMDs can be attached to an expensive medical device to monitor various critical components during shipment; when the device arrives at the customer, these MMDs are interrogated to determine whether any of the critical components experienced undesirable conditions—e.g., a high impact or temperature or humidity.
By way of background for moisture sensing, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 5,486,815; U.S. Pat. No. 5,546,974; and U.S. Pat. No. 6,078,056.
By way of background for humidity sensing, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 5,608,374; U.S. Pat. No. 5,546,974; and U.S. Pat. No. 6,078,056.
By way of background for temperature sensing, the following U.S. patents are incorporated herein by reference: U.S. Pat. No. 6,074,089; U.S. Pat. No. 4,210,024; U.S. Pat. No. 4,516,865; U.S. Pat. No. 5,088,836; and U.S. Pat. No. 4,955,980.
In accord with further aspects of the invention, the MMD measures one or more of the following environmental metrics: temperature, humidity, moisture, altitude and pressure. These environmental metrics are combined into the MMD with a detector that facilitates the monitoring of movement metrics such as described above. For temperature, the detector of one aspect is a temperature sensor such as a thermocouple or thermister. For altitude, the detector of one aspect is an altimeter. For pressure, the detector of one aspect is a pressure sensor such as a surface mount semiconductor element made by SENSYM.
In accord with one aspect, a MMD monitors one or more movement metrics for “events,” where data is acquired that exceeds some predetermined threshold or value. By way of example, in one aspect the detector is a triaxial accelerometer and the processor coupled to the accelerometer seeks to determine impact events that exceed a threshold, in any or all of three axes. In another aspect, a single axis accelerometer is used as the detector and a single axis is monitored for an impact event. In another example, the detector and processor collectively monitor and detect spin events, where for example it is determined that the device rotated more than 360 degrees in ½ second or less (an exemplary “event” threshold). In still another aspect, the detector is a force detector and the processor and detector collectively determine a change of weight of an object resting on the MMD over some preselected time period. In one specific object, the invention provides for a MMD to monitor human weight to report that weight, on demand, to individuals. Preferably, such a MMD is in a shoe.
In one aspect, the movement metric of rotation is measured by a MMD with a Hall effect detector. Specifically, one aspect of the Hall effect detector with a MMD of the invention monitors when the MMD is inverted. In one other aspect, the Hall effect detector is used with the processor to determine when an object is inverted or rotated through about 180 degrees. An “event” detected by this aspect can for example be one or more inversions of the MMD of about 180 degrees.
In still another aspect, the MMD has a MRE as the detector, and the MMD measures spin or rotation experienced by the MRE.
In one aspect, a plurality of MMDs are collated and packaged in a single container, preferably similar to the cans or boxes containing adhesive bandages. Preferably, in another aspect, MMDs of the invention are similarly programmed within the container. By way of example, one container carries 100 MMDs that each respond to an event of “10 g's.” In another example, another container carries 200 MMDs that respond to an event of “100 g's.” Packages of MMDs can be in any suitable number N greater than or equal to two; typically however MMDs are packaged together in groups of 50, 100, 150, 200, 250, 500 or 1000. A variety pack of MMDs are also provided, in another aspect, for example containing ten 5 g MMDs, ten 10 g MMDs, ten 15 g MMDs, ten 20 g MMDs, ten 25 g MMDs, ten 30 g MMDs, ten 35 g MMDs, ten 40 g MMDs, ten 45 g MMDs, and ten 50 g MMDs. Another variety package can for example include groups of MMDs spaced at 1 g or 10 g intervals.
In one preferred aspect, the MMD of the invention includes internal memory. Preferably the memory is within the processor or ASIC. Event data is stored in the memory, in accord with one aspect, until transmitted off-board. In this way, the MMD monitors and stores event data (e.g., an “event” occurrence where the MMD experiences 10′gs). Preferably, the event data is time tagged with data from a real-time clock; and thus a real time clock is included with the MMD (or made integral with the processor or ASIC). A crystal or other clocking mechanism may also be used.
In one aspect, the MMD is programmed with a time at the initial time of use (i.e., when the device is powered). In one other aspect, the MMD is packaged with power so that real time clock data is available when the product is used. In this aspect, therefore, a container of MMDs will typically have a “stale” date when the MMD's battery power is no longer usable. In one aspect, the MMD has a replaceable battery port so that a user can replace the battery.
The invention has certain advantages. A MMD of the invention can practically attach to almost anything to obtain movement information. By way of example, a MMD of the invention can attach to furniture to monitor shipping of furniture. If the furniture were dropped, an impact event occurs and is recorded within the MMD, or transmitted wirelessly, with an associated time tag. When the furniture is damaged prior to delivery, a reader (e.g., an ID) reads the MMD to determine when the damage occurred—leading to the responsible party who may then have to pay for the damage. In a further example, if furniture is rated to “10 g's”, a MMD (programmed and enabled to detect 10 g events) is attached to the furniture when leaving the factory, so that any 10 g event before delivery is recorded and time-stamped, again leading to a responsible party. Similarly, in other aspects, devices of the invention are attached to packages (e.g., FED EX or UPS shipments) to monitor handling. By way of example, fragile objects may be rated to 5 g; and an appropriately programmed MMD of the invention is attached to the shipment to record and time-tag 5 g events. In another aspect, fragile objects that should be maintained at a particular orientation (i.e., packages shipped within “This Side Up” instructions) are monitored by a MMD detecting inversions of about 180 degrees, such as through a Hall Effect detector.
In one aspect, the MMD includes a tamper proof detector that ensures the MMD is not removed or tampered with once applied to an object or person, until an authorized person removes the MMD. In one aspect, the tamper proof detector is a piezoelectric strip coupled into or with the adhesive strip. Once the MMD is powered and applied to an object or person, a quiescent period ensues and the MMD continually monitors the tamper proof detector (in addition to the event detector) to record tampering activity. In the case of the piezoelectric strip, removal of the MMD from a person or object after the quiescent period provides a relatively large voltage spike, indicating removal. That spike is recorded and time stamped. If there are more than one such records (i.e., one record represents the final removal), then tampering may have occurred. Since date and time are tagged with the event data, the tamper time is determined, leading to identify the tampering person (i.e., the person responsible for the object when the tamper time was tagged).
In one aspect, the invention provides an ID in the form of a cell phone. Nearly one in three Americans use a cell phone. According to the teachings of the invention, data movement “metrics” are read from a MMD through the cell phone. Preferably, data communicated from the MMD to the cell phone is made only through secure communications protocols so that only authorized cell phones can access the MMD. In one specific aspect, MMD events are communicated to a cell phone or cellular network, and from that point are relayed to persons or additional computer networks for use at a remote location.
Miniature tension or compression load cells are used in certain aspects of the invention. By way of example, a MMD incorporating such cells are used in measuring and monitoring tension and/or compression between about fifty grams and 1000 lbs, depending upon the application. In one aspect, the MMD generates a warning signal when the load cell exceeds a preselected threshold.
In accord with the invention, several advantages are apparent. The following lists some of the non-limiting movement events monitored and captured by select MMDs of the invention, in accord to varied aspects of the invention:
The above movement events may be combined for a variety of metrics useful to users of the invention. For example, in one aspect, altitude variations are used to accurately gauge caloric burn through the variations. Such information is particularly useful for mountain bikers and in mountain sports.
The invention of one aspect provides a quantizing accelerometer that detects one or more specific g-levels in a manner particularly useful as a detector in a MMD of the invention.
There are thus several applications of the invention, including the monitoring of movement for people, patients, packages, athletes, competitors, shipments, furniture, athletes in training (e.g., karate), and industrial robotics. The benefits derived by such monitoring can be used by insurance companies and manufacturers, which, for example, insure shipments and packages for safe delivery to purchasers. Media broadcasters, including Internet content providers, can also benefit by augmenting information associated with a sporting event (e.g., airtime of a snowboarder communicated in real time to the Internet, impact of a football or soccer ball during a game, boxing glove strike force during a fight, tennis racquet strike force during a match). The MMD of the invention is small, and may be attached to practically any object—so ease of use is clearly another advantage. By way of example, an MMD can be mounted to the helmet or body armor of each football player or motocross competitor to monitor movement and jerk of the athlete. In such applications, data from the MMD preferably transmits event data in real time to a RR in the form of a network, so that MMD data associated with each competitor is available for broadcast to a scoreboard, TV or the Internet. Other advantages should be apparent in the description within. Event Monitoring Devices
The invention also provides certain sensors and devices used to monitor and report temperature, humidity, chemicals, heart rate, pulse, pressure, stress, weight, environmental factors and hazardous conditions.
In one aspect, the invention provides a event monitor device (“EMD”) including an adhesive strip, a processor, a detector, and a communications port. In another aspect, two or more of the processor, port and detector are combined in a single application specific integrated circuit (“ASIC”). In one aspect the detector is an humidity or temperature sensor, and preferably that detector is embedded into silicon within the ASIC. In other aspects, the detector is one of an EKG sensing device, weight-sensing detector, and chemical detector. In still another aspect, the EMD includes a battery. In the preferred aspect of the invention, the EMD and battery are packaged in a protective wrapper. Preferably, the battery is packaged with the EMD in such a way that it does not “power” the EMD until the wrapper is removed. Preferably, the EMD includes a real time clock so that the EMD tags “events” with time and/or date information.
In yet another aspect, the EMD with adhesive strip collectively take a form similar to an adhesive bandage. More particularly, the adhesive strip of the invention is preferably like or similar to the adhesive of the adhesive bandage; and the processor is embedded with the strip much the way the cotton is with the adhesive bandage. Preferably, a soft material (e.g., cotton or cloth) is included to surround the processor so as to (a) soften contact of rigid EMD components with a person and/or (b) protect the processor (and/or other components of the EMD). In still another aspect, the battery is also coupled with the soft material. In still another aspect, the processor and other elements of the EMD are combined into a single system-on-chip integrated circuit. A protective cover may surround the chip to protect the EMD from breakage.
In one aspect, one EMD of the invention takes a form similar to a smart label, with an adhesive substantially disposed with the label, e.g., on one side of the label. The adhesive strip of this EMD includes all or part of the back of the label with adhesive or glue permitting attachment of the label to other objects (or to a person).
In still another aspect, the EMD of the invention takes the form of a rigid monolithic that attaches to objects through one of known techniques. In this aspect, the device has a processor, communications port, and detector. A battery is typically included with the EMD. The EMD is attached to objects or persons by one of several techniques, including by glue or mechanical attachment (e.g., a pin or clip). An EMD of this aspect can for example exist in the form of a credit card, wherein the communications port is either a contact transponder or a contactless transponder. The EMD of one aspect includes a magnetic element that facilitates easily attaching the EMD to metal objects.
In operation, the EMD of the invention is typically interrogated by an ID. The EMD is responsive to the ID to communicate information within the EMD and, preferably, over secure communications protocols. By way of example, one EMD of the invention releases internal data only to an ID with the correct passwords and/or data protocols. The ID can take many forms, including a cell phone or other electronic device (e.g., a MP3 player, pager, watch, or PDA) providing communications with the EMD transmitter
However, in another aspect, the EMD communicates externally to a RR. The RR listens for data from the EMD and collects that data for subsequent relay or use. In one aspect, the EMD's communications port is a one-way transmitter. Preferably, the EMD communicates data from the EMD to the RR either (a) upon the occurrence of an “event” or (b) in repeated time intervals, e.g., once every minute or more. Alternatively, the EMD's communication port is a transceiver that handshakes with the RR to communicate data from the EMD to the RR. Accordingly, the EMD responds to data requests from the RR, in this aspect. In still another aspect, the RR radiates the EMD with transponder frequencies; and the EMD “reflects” the data to the RR.
Accordingly, the communications port of one EMD is a transponder responsive to one or more frequencies to relay data back to an ID. By way of example, these frequencies can be one of 125 kHz and 13.56 MHz, the frequencies common with “contactless” RFID tags known in the art. In other aspects, communications frequencies are used with emission power and frequencies that fall within the permissible “unlicensed” emission spectrum of part 15 of FCC regulations, Title 47 of the Code of Federal Regulations. In particular, one desirable feature of the invention is to emit low power, to conserve battery power and to facilitate use of the EMD in various environments; and therefore an ID is placed close to the EMD to read the data. In other words, in one aspect, wireless communications from the EMD to the ID occurs over a short distance of a fraction of an inch to no more than a few feet. By way of example, as described herein, one ID of the invention takes the form of a cell phone, which communicates with the EMD via one or more secure communications techniques. Data acquired from the EMD is then communicated through cellular networks, if desired, to relay EMD data to end-users. Or, in another aspect, or sensitive or directional antenna is used to increase the distance to detect data of the EMD.
In another aspect, the communications port is an infrared communications port. Such a port, in one aspect, communicates with the cell phone in secure communication protocols. In other aspects, an ID communicates with the infrared port to obtain the data within the EMD.
In yet another aspect, the communications port includes a transceiver. The EMD listens for interrogating signals from the RR and, in turn, relays “event” data from the EMD to the RR. Alternatively, the EMD relays “event” data at set time intervals or when the EMD accumulates data close to an internal storage limit. In one aspect, thereby, the EMD include internal memory; and the EMD stores one or more “event” data, preferably with time-tag information, in the memory. When the memory is nearly full, the EMD transmits the stored data wirelessly to a RR. Alternatively, stored data is transmitted to an IR when interrogated. In a third alternative, the EMD transmits stored data at set intervals, e.g., once per ½ hour or once per hour, to relay stored data to a RR. Other transmission protocols can be used without departing from the scope of the invention.
In still another aspect, data from the EMD is relayed to an ID through “contact” communication between the ID and the communications port. In one aspect, the EMD includes a small conductive plate (e.g., a gold plate) that contacts with the ID to facilitate data transfer. Smart cards from the manufacturer GEMPLUS may be used in such aspects of the invention.
In one aspect, the EMD includes a printed circuit board “PCB”). A battery—e.g., a 2032 or 1025 Lithium coin cell—is also included, in another aspect of the invention. To make the device small, the PCB preferably has multilayers—and two of the internal layers have a substantial area of conducting material forming two terminals for the battery. Specifically, the PCB is pried apart at one edge, between the terminals, and the battery is inserted within the PCB making contact and providing voltage to the device. This advantageously removes then need for a separate and weighty battery holder. Flex circuit boards may also be used.
In another aspect, the PCB has first and second terminals on either side of the PCB, and a first side of the battery couples to the first terminal, while a clip connects the second side of the battery to the second terminal, making the powered connection. This aspect advantageously removes then need for a separate and weighty battery holder.
In still another aspect, a terminal is imprinted on one side of the PCB, and a first side of the battery couples to that terminal. A conductive force terminal connects to the PCB and the second side of the batter, forming a circuit between the battery and the PCB.
In accord with one aspect of the invention, the communications port is one of a transponder (including a smart tag or RFID tag), transceiver, or one-way transmitter. In other aspects, data from the EMD is communicated off-board (i.e., away from the EMD) by one of several techniques, including: streaming the data continuously off-board to get a real-time signature of data experienced by the EMD; transmission triggered by the occurrence of an “event” as defined herein; transmission triggered by interrogation, such as interrogation by an ID with a transponder; transmission staggered in “bursts” or “batches,” such as when internal storage memory is full; and transmission at predetermined intervals of time, such as every minute or hour.
In one preferred aspect of the invention, the above-described EMDs are packaged like an adhesive bandage. Specifically, in one aspect, one or more protective strips rest over the adhesive portion of the device so as to protect the adhesive until the protective strips are removed. The strips are substantially stick-free so that they are easily removed from the adhesive prior to use. In another aspect, a “wrapper” is used to surround the EMD; the wrapper being similar to existing wrappers of adhesive bandages. In accord with one preferred aspect, the battery electrically couples with the electronics of the EMD when the wrapper is opened and/or when the protective strips are removed. In this way, the EMD can be “single use” with the battery energizing the electronics only when the EMD is opened and applied to an object or person; the battery power being conserved prior to use by a decoupling element associated with the wrapper or protective strips. Those skilled in the art should appreciate that other techniques can be used without departing from the scope of the invention.
In one aspect, the EMD continuously relays an environmental metric (e.g., temperature, humidity, or chemical content) by continuous transmission of data from the detector to a RR. In this way, a EMD attached to a person or object may beneficially track conditions, in real time, of that person or object by recombination of the environmental metrics at a remote computer. In one aspect, multiple EMDs attached to a person or object quantify data for a plurality of locations, for example to monitor sub-parts of an object or person.
In accord with further aspects of the invention, the EMD measures one or more of the following environmental metrics: temperature, humidity, moisture, altitude and pressure. For temperature, the detector of one aspect is a temperature sensor such as a thermocouple or thermister. For altitude, the detector of one aspect is an altimeter. For pressure, the detector of one aspect is a pressure sensor such as a surface mount semiconductor element made by SENSYM.
In accord with one aspect, an EMD monitors one or more metrics for “events,” where data is acquired that exceeds some predetermined threshold or value. By way of example, in one aspect the detector is a temperature sensor and the processor coupled to the temperature sensor seeks to determine temperature events that exceed a threshold. In another aspect, a humidity sensor is used as the detector and this sensor is monitored for a humidity event (e.g., did the EMD experience 98% humidity conditions). In another example, the detector and processor collectively monitor stress events, where for example it is determined that the EMD attached to a human senses increased heart rate of over 180 beats per minute (an exemplary “event” threshold). In still another aspect, the detector is a chemical (or pH) detector and the processor and detector collectively determine a change of chemical composition of an object connected with the EMD over some preselected time period.
In one aspect, a plurality of EMDs are collated and packaged in a single container, preferably similar to the cans or boxes containing adhesive bandages. Preferably, in another aspect, EMDs of the invention are similarly programmed within the container. By way of example, one container carries 100 EMDs that each respond to an event of “5 degrees” variation from some reference temperature. In another example, another container carries 200 EMDs that respond to an event of “90 degrees” change absolute. Temperature sensors may be programmed to determine actual temperatures, e.g., 65 degrees, or changes in temperature from some reference point, e.g., 10 degrees from reference.
Packages of EMDs can be in any suitable number N greater than or equal to two; typically however EMDs are packaged together in groups of 50, 100, 150, 200, 250, 500 or 1000.
In one preferred aspect, the EMD of the invention includes internal memory. Preferably the memory is within the processor or ASIC. Event data is stored in the memory, in accord with one aspect, until transmitted off-board. In this way, the EMD monitors and stores event data (e.g., an “event” occurrence where the EMD experiences 100 degree temperatures). Preferably, the event data is time tagged with data from a real-time clock; and thus a real time clock is included with the EMD (or made integral with the processor or ASIC). In one aspect, the EMD is programmed with a time at the initial time of use (i.e., when the device is powered). In one other aspect, the EMD is packaged with power so that real time clock data is available when the product is used. In this aspect, therefore, a container of EMDs will typically have a “stale” date when the EMD's battery power is no longer usable. In one aspect, the EMD has a replaceable battery port so that a user can replace the battery.
The invention has certain advantages. An EMD of the invention can practically attach to almost anything to obtain event information. By way of example, an EMD of the invention can attach to patients to track health and conditions in real time and with remote monitoring capability.
In one aspect, the EMD includes a tamper proof detector that ensures the EMD is not removed or tampered with once applied to an object or person, until an authorized person removes the EMD. In one aspect, the tamper proof detector is a piezoelectric strip coupled into or with the adhesive strip. Once the EMD is powered and applied to an object or person, a quiescent period ensues and the EMD continually monitors the tamper proof detector (in addition to the event detector) to record tampering activity. In the case of the piezoelectric strip, removal of the EMD from a person or object after the quiescent period provides a relatively large voltage spike, indicating removal. That spike is recorded and time stamped. If there are more than one such records (i.e., one record represents the final removal), then tampering may have occurred. Since date and time are tagged with the event data, the tamper time is determined, leading to identify the tampering person (i.e., the person responsible for the object when the tamper time was tagged).
In one aspect, the invention provides an ID in the form of a cell phone. Nearly one in three Americans use a cell phone. According to the teachings of the invention, data event “metrics” are read from an EMD through the cell phone. Preferably, data communicated from the EMD to the cell phone is made only through secure communications protocols so that only authorized cell phones can access the EMD. In one specific aspect, EMD events are communicated to a cell phone or cellular network, and from that point are relayed to persons or additional computer networks for use at a remote location.
In accord with the invention, several advantages are apparent. The following lists some of the non-limiting events monitored and captured by select EMDs of the invention, in accord to varied aspects of the invention:
fitness or patient health characteristics
The invention will next be described in connection with preferred embodiments. In addition to those described above, certain advantages should be apparent in the description which follows.
As an EMD, for example, detector 12 senses temperature experienced by device 10 and generates signals indicative of temperature (either absolute, or relative). Processor 12 then processes the signals to extract desired data. Preferably, data such as temperature are time tagged with date and/or time information so that a limited recording is made of environmental conditions.
Communications port 16 communicates event data from device 10 to a receiver 24 as wireless data 30a. Port 16 typically performs such communications in response to commands from processor 14. Communications port 26 receives wireless data 30a for use within receiver 24. If desired, communications port 26 can also communicate with port 16 to transmit wireless data 30b to device 10. In such an embodiment, ports 16, 26 are preferably radio-frequency, infrared or magnetically-inductive transceivers. Alternatively, port 26 is a transmitter that interrogates device 10; and port 16 is a transponder that reflects event data to receiver 24. In one preferred embodiment, receiver 24 is part of the circuitry and packaging of a cell phone, which relays events (e.g., a movement event) to a remote storage facility. In other embodiments, receiver 24 is part of the circuitry and packaging of a MP3 player, pager, watch, or electronic PDA. Receiver 24 may connect with headphones (not shown) to provide information to a user and corresponding to “event” data.
Data communication between device 10 and receiver 24 is preferably “secure” so that only a receiver with the correct identification codes can interrogate and access data from device 10. In such a mode, receiver 24 is an interrogation device (“ID”); and wireless communications 30a, 30b between ports 16, 26 can be through one of several electromagnetic communications spectrums, including radio-frequencies, microwave frequencies, ultrasound or infrared. However, communications between device 10 and receiver 24 can also be one way, e.g., wireless data 30a from device 10 to receiver 24; and in such an embodiment receiver 24 preferably understands the communications protocols of data 30a to correctly interpret the data from device 10. Receiver 24 in this embodiment “listens” for data transmitted from device 10. Receiver 24 thus may function as a remote receiver (“RR”) stationed some distance (e.g., tens or hundreds of feet or more) from device 10.
A monitor device 10, 10′ of the invention preferably includes an adhesive strip that provides for convenient attachment of the device to an object or person. As shown in
Those skilled in the art should appreciate that two or more of elements 14, 16, 18, 22 (
A device 10 can also integrate directly with the adhesive strip, as shown in
As an alternative heart rate monitor, device 10 of
The invention also provides for efficiently integrating battery 18 with a monitor device.
Battery attachment to PCB 40″ can also be made as in
The battery integrations with PCBs of
The MMDs of the invention operates to detect movement “metrics.” These metrics include, for example, airtime, speed, power, impact, drop distance, jarring and spin; typically one MMD detects one movement metric, though more than one metric can be simultaneously detected by a given MMD, if desired (potentially employing multiple detectors). The MMD detector is chosen to provide signals from which the processor can interpret and determine the desired metric. For example, to detect airtime, the detector is typically one of an accelerometer or piezoelectric strip that detects vibration of an object to which the MMD is attached. Furthermore, the MMD of the invention preferably monitors the desired metric until the metric passes some threshold, at which time that metric is tagged with time and date information, and stored or transmitted off-board. If the MMD operates within a single day, only time information is typically tagged to the metric.
By way of example, if the detector is an accelerometer and the MMD is designed to monitor “impact” (e.g., acceleration events that are less than about ½ second)—and yet impact data is not considered interesting unless the MMD experiences an impact exceeding 50 g's—the preferred MMD used to accomplish this task would continuously monitor impact and tag only those impact events that exceed 50 g's. The “event” in this example is thus a “50 g event.” Such a MMD is for example useful when attached to furniture, or a package, in monitoring shipments for rough treatment. The MMD might for example record a 50 g event associated with furniture shipped on Oct. 1, 2000, from a manufacturer in California, and delivered on Oct. 10, 2000 to a store in Massachusetts. If an event stored in MMD memory indicates that on Oct. 5, 2000, at 2:30 pm, the furniture was clearly dropped, responsibility for any damages can be assessed to the party responsible for the furniture at that time. Accuracy of the time tag information can be days, hours, minutes and even seconds, depending on desired resolution and other practicalities.
Accordingly, data from such a MMD is preferably stored in internal memory (e.g., memory 20,
In another application, one or more monitor devices are attached to patients in a hospital, and one or more receivers are integrated with existing electronics at the hospital (e.g., with closed circuit television, phone systems, etc.). In operation, these device are for example used to detect “events” that indicate useful information about the patients—information that should be known. If for example the monitor device has a Hall Effect detector that detects when the device is inverted, then a device attached to the collar bone (or clothing) of a patient would generate an “event” when the patient falls or lays down. An impact detector may also be used advantageously, to detect for example a 10 g event associated with a patient who may have fallen. Accordingly, monitor devices applied to patients in hospitals typically transmit event data at occurrence, so that in real time a receiver relays important medical information to appropriate personnel.
Movement devices of the invention can also transmit movement or other metrics at select intervals. If for example “impact” data is monitored by a MMD, then the MMD can transmit the maximum impact data for a selected interval—e.g., once per minute or once per five minutes, or other time interval. In this way, a MMD applied to a patient monitors movement; and any change in movement patterns are detected in the appropriate time interval and relayed to the receiver. A MMD may thus be used to inform a hospital when a patient is awake or asleep: when asleep, the MMD transmits very low impact events; when awake, the MMD transmits relatively high impact events (e.g., indicating that the patient is walking around).
Device 120 may alternatively detect patient movement to provide real time detection of movement of a person or of part of that person. For example, such a device 120 may be used to monitor movement of an infant (instead of arm 150) or other patient.
Note that the application of a monitor device 120 as described in
Devices such as device 120 or 120′ have additional application such as for infant monitoring. Attaching such a device to the chest (instead of arm 150) of an infant to monitor respiration, pulse and/or movement provides a remote monitoring tool and may prevent death by warning the infant's parents. A monitor device 10w,
Data transmissions from a monitor device of the invention, to a receiver, typically occur in one of three forms: continuous transmissions, “event” transmissions, timed sequence transmissions, and interrogated transmissions. In continuous transmissions, a monitor device transmits detector signals (or possibly processed detector signals) in substantially real time from the monitor device to the receiver. Data reconstruction at the receiver, or at a computer arranged in network with, or in communication with, the receiver, then proceeds to analyze the data for desired characteristics. By way of example, by attaching multiple monitor devices to a person, all transmitting real-time data signals to the receiver, a reconstruction of that person's activity is determined.
Consider for example
Data plots 154, 156 have obvious advantages realized by use of the MMDs of the invention. For example, plot 154 illustrates several first “strikes” 166 generated by person A on person B, and data plot 156 illustrates corresponding blows 168 to the head of person B. Data 154, 156 may for example be used in training, where person B learns to anticipate person A more effectively to soften or eliminate blows 168.
Data plots 154, 156 have further advantages for broadcast media; specifically, data 154, 156 may be simultaneously relayed to the Internet or television 170 to display impact speed and intensity for blows given or received by persons A, B, and in real time, to enhance the pleasure and understanding of the viewing audience (i.e., viewers of television, and users of the Internet). Moreover, MMDs of the invention remove some or all of the subjectivity of impact events: a blow to an opponent is no longer qualitative but quantitative. By way of example, the magnitude of strikes 166 and blows 168 are preferably provided in the data streamed from MMDs 150, indicating magnitude or force of the blow or strike. Data 154, 156 thus represents real time movement metric data, such as acceleration associated with body parts of persons A, B. Data 154, 156 may thereafter be analyzed, at receiver 152, to determine “events”, such as when data 154, 156 indicates an impact exceeding 50 g's (or other appropriate or desired measure).
Those skilled in the art should appreciate that any number of MMDs 150 may be used for applications such as shown in
Data acquired from MMDs in sports like boxing and karate are also preferably collated and analyzed for statistical purposes. Data 154, 156 can be analyzed for statistical detail such as: impacts per minute; average strike force per boxer; average punch power received to the head; average body blow power; and peak striking impact. Rotational information may also be derived with the appropriate detector, including typical wrist rotation at impact, a movement metric that may be determined with a spin sensor.
Other than continuous transmissions, such as illustrated in
Note that timed sequence transmission of event data approaches “continuous” transmission of movement metric data for smaller and smaller timed sequence transmissions. For example, if data from the monitor device is communicated off-board each second (or less, such as each one tenth of a second), then that data becomes more and more similar to continuously transmitted data from the detector. Indeed, if sampling of the detector occurs at X Hz, and timed transmissions also occur at X Hz, then “continuous” or “timed sequence” data may be substantially identical. Timed sequence or event data, therefore, provides for the opportunity to process the detector signals, between transmissions, to derive useful events or to weed out noise or useless information.
In one preferred embodiment of the invention, a canister 200′ (e.g., similar to canister 200 but with internal electronics) has its own battery 210, micro-controller 212, sensor time tag interface 214a, and real time clock 216 (collectively the “canister electronics”), as shown in
One advantage of sensor canister 200′ is that once used, it may be reused by installing additional sensors within the cavity. In addition, one canister can carry multiple monitor devices, such as 100 MMDs that each respond to an event of “10 g's.” In another example, another canister carries 200 MMDs that respond to an event of “100 g's.” A canister of MMDs can be in any suitable number that meets a given application; typically however sensors within the canister of the invention are packaged together in groups of 50, 100, 150, 200, 250, 500 or 1000. A variety pack of MMDs can also be packaged within a canister, such as a canister containing ten 5 g MMDs, ten 10 g MMDs, ten 15 g MMDs, ten 20 g MMDs, ten 25 g MMDs, ten 30 g MMDs, ten 35 g MMDs, ten 40 g MMDs, ten 45 g MMDs, and ten 50 g MMDs. Another variety package can for example include groups of MMDs spaced at 10 g intervals. EMDs can also be packaged in variety configurations within canisters 200, 200′.
Canisters 200, 200′ can also function to dispense one or a plurality of receivers. Specifically, each of elements 202 of
Preferably, canisters 200′ imparts a unique ID to the dispensed electronics—e.g., to each sensor or receiver taken from canister 200′—for security reasons. More particularly, in addition to communicating a current date and time to the dispensed electronics, canister 200′ also preferably imparts a unique ID code which is used in subsequent interrogations of the dispensed electronics to obtain data therein. Therefore, data within a monitor device, for example, cannot be tampered with without the appropriate access code; and that code is only known by the party controlling canister 200′ and dispensing the electronics.
Batteries used in the above MMDs and devices like the lift ticket can benefit by using paper-like batteries such as set forth in U.S. Pat. No. 5,897,522, incorporated herein by reference. Such batteries provide flexibility in several of the monitor devices described herein. Powering such batteries when dispensing a sensor or receiver still provides advantages to conserve battery power until the sensor or receiver is used. A device battery 18 of
Sensor 231′ also has a battery 233′ that is preferably powered when sensor 231′ is dispensed to a user (e.g., to a snowboarder at a resort). Optionally, position locator 243 is included with sensor 231′ to track earth location of sensor 23′; processor 235′ thereafter determines speed based upon movement between locations over a time period (e.g., distance between a first location and a second location, divided by the time differential defined by arriving at the second location after leaving the first location, provides speed). Clock 237′ provides timing to sensor 231′. Optionally, memory 236′ serves one of several functions as a matter of design choice. Data gathered by sensor 231′ may be stored in memory 236′; such data may be communicated off-board during subsequent interrogations. As discussed above, data may also be communicated off-board at the occurrence of a speeding “event.” As an alternative, indicator 234′ may be a transponder RFID tag to be read by a ticket card reader. In one embodiment, on slope transmitters irradiate sensor 231′ with a signal that reflects to determine Doppler speed; that speed is imparted to sensor memory 236′ and reported to the resort.
Preferably, sensor 231′ operates in “low power” mode. Position locator 243 in one preferred embodiment is a GPS receiver. GPS receiver and processor 243, 235′ for example collectively operate to make timed measurements of earth location so as to coarsely measure speed. For example, by measuring earth location each five seconds, and by dividing the distance traveled in those five seconds by five seconds, a coarse measure of speed is determined. Other timed measurements could be made as a matter of design choice, e.g., ½, 1, 15, 20, 25, 30 or 60 seconds. By taking fewer measurements, and by reducing processing, battery power is conserved over the course of a day, as it is preferable that the ticket determines speeding violations for at least a full day, in Winter. Finely determining speed at about one-second intervals is useful in the preferred embodiment of the invention.
Memory 236′ may further define location information relative to one or more “zones” at a resort, such that speed may be assigned to each zone. In this manner, for example, a resort can specify that ski run “X” (of zone “A”) has a speed limit of 35 mph, while ski run “Y” (of zone “B”) has a speed limit of 30 mph. Speeding violations within any of zones A or B are then communicated to the resort. The advantage of this feature of the invention is that certain slopes or mountain areas permit higher speeds, and yet other slopes (e.g., a tree skiing area) do not support higher speeds. The resort may for example specify speed limits according to terrain. GPS receiver 243 determines earth position—which processor 235′ determines is within a particular zone—and speed violations are then determined relative to the speed limit within the particular zone, providing a more flexible system for the ski resort.
Position locator 243 of another embodiment is an altimeter, preferably including a solid-state pressure sensor. Altimeter 243 of one embodiment provides gross position information such as the maximum and minimum altitude on a ski mountain. For a particular resort, maximum and minimum altitude approximately correspond to a distance of “Z” meters, the distance needed to traverse between the minimum and maximum altitude. Processor 235′ then determines speed based upon dividing Z by the time between determining the minimum and maximum altitudes. Fractional speeds may also be determined. If for example a particular skier traverses between a maximum altitude and half-way between the minimum and maximum altitudes, then processor 235′ determines speed based upon dividing Z/2 by the time between determining (a) the maximum altitude and (b) the midpoint between the minimum and maximum altitudes.
As discussed above, one MMD of the invention includes an airtime sensor.
More particularly,
More particularly, data from step 260 is bifurcated along fast-signal path 262 and slow-signal path 264, as shown. In path 262, a low pass filter operation (here shown as a one pole, 20 Hz low pass filter) first occurs at step 266 to produce power signal 266a. Two comparators compare power signal 266a to thresholds, at step 268, to generate two signals 270 used to identify possible takeoffs and landings for an airtime event. In path 264, a low pass filter operation (here shown as a one pole 2 Hz low pass filter) first occurs at step 272 to produce power signal 272a. Three comparators compare power signal 272a to thresholds, at step 274, to generate three “confidence” signals 276 used to assess confidence of takeoffs and landings for an airtime event. Finally, a state machine 280, described in more detail in
Those skilled in the art should appreciate that the airtime detection scheme of
In summary, the relative fast signal from fast-signal path 262,
An accelerometer signal described in
Data transmission from a sensor (e.g., a MMD) to a display unit (e.g., a receiver) is generally at least 99.9% reliable. In the case of one-way communication, a redundant transmission protocol is preferably used to cover for lost data transmissions. Communications are also preferably optimized so as to reduce battery consumption. One way to reduce battery consumption is to synchronize transmission with reception. The “transmission period” (the period between one transmission and the next), the size of the storage buffer in sensor memory, and the number of times data is repeated (defining a maximum age of an event) are adjustable to achieve battery consumption goals.
A state diagram for transmission protocols between one sensor and display unit, utilizing one-way transmission, is shown in
By way of example, one sensor unit is monitor device 10 of
Preferably, the display unit determines the sync pattern for sensor transmissions by active listening until receipt of a synchronization or data transmission with the matching sensor ID. Once a valid transmission from the matching sensor is received, the display unit calculates the time of the next possible transmission and controls the display unit accordingly. When the sensor is a MMD used to determine airtime, and the sensor does not necessarily have a real time clock; data sent to the display unit includes airtime values with time information as to when the airtime occurred. As this sensor does not necessarily maintain a real time clock, the time information sent from the sensor is relative to the packet transmission time. Preferably, the display unit, which has a real time clock, will convert the relative time into an absolute time such that airtime as an event is tagged with appropriate time and/or date information.
The amount of data communicated between the sensor and display unit varies. By way of example, for typical skier and snowboarder operation, an airtime event covering the 0-5 second range with a resolution of 1/100th second is generally adequate. The coding of such airtime events can use nine data bits. Ten bits allow for measurement of up to approximately ten seconds, if desired. For an age, where the resolution of age is one second (i.e., a time stamp resolution) and the maximum age of a repeat transmission is fifteen seconds, four bits are used. Data transmission also typically has overhead, such as startup time, synchronization byte, sensor ID used to verify correct sensor reception, a product identifier to allow backwards compatibility in future receivers, a count of the number of data items in the packet, and, following the actual data, a checksum to gain confidence in the received data. This overhead is approximately six bytes in length. To reduce the effect of overhead, stored data in the sensor is preferably sent in one message. An airtime event for example can be stored in the sensor until transmitted with the desired redundancy, after which it is typically discarded. Thus, the number of airtime events included in a transmission depends upon the number of items still in the sensor's buffer (e.g., in memory 20,
A typical data transmission can for example include: <P/up> <Sync> <Sensor ID> <Product ID> <Count> [<Age> <Airtime>]<Checksum>. <P/up> is the power-up time for the transmitter. A character may be transmitted during power up to aid the transmitter startup, and help the receiver start to synchronize on the signal. The <Sync> character is sent so that the receiver can recognize the start of a new message. <Sensor ID> defines each sensor with a unique ID number such that the display unit can selectively use data from a matching sensor. <Product ID> defines each sensor with a product ID to allow for backward compatibility in future receivers. <Count> defines how many age/airtime values are included in a message. The <Age> field provides the age of an associated airtime value, which may be used by the display unit to identify when an airtime is retransmitted. <Airtime> is the actual airtime value. <Checksum> provides verification that the data was received correctly.
A sensor's buffer length should accommodate the maximum number of airtime jumps for the duration of retransmissions. By way of example, transmissions can be restricted so that no more than one jump every three seconds is recognized; and retransmissions should generally finish within a selected time interval (e.g., six seconds). Therefore, this exemplary sensor need only store two airtime events at any one time. The buffer length is preferably configurable, and can for example be set to hold four or more airtime events.
Transmission electronics within the sensor and display units may use a UART, meaning that data is defined in byte-sized quantities. As those skilled in the art understand, alternative transmission protocols can utilize bit level resolution to further reduce transmission length.
By way of example, consider an airtime event of 1.72 seconds, occurring 2.1 seconds before start of transmission. In accord with
<P/up><Sync><Sensor ID><Product ID><Count>[<Age><Airtime>] <Checksum><0xAA><0xAD><0x12><0x01><0x01><0x02><0x158><0x21>
Assuming that the age and airtime data are combined into two bytes, and that <P/up> is one byte in length, the entire packet is eight bytes in length. At a transmission speed of 1200 baud, a typical transmission speed between a sensor and receiver, the eight bytes takes 67 ms to transmit. Assuming sequential transmission periods of 500 ms, the transmission duty cycle is 13.4% for a single jump.
Those skilled in the art should appreciate that alternatives from the above-described protocols may be made without departing from the scope of the invention. In one alternative, pseudo random transmissions are used between a sensor and receiver. If for example two sensors are together, and transmitting, the transmissions may interfere with one another if both transmissions synchronously overlap. Therefore, in situations like this, a pseudo random transmission interval may be used, and preferably randomized by the unique sensor identification number <Sensor ID>. If both the display unit and the sensor follow the same sequence, they can remain in complete sync. Accordingly, a collision of one transmission (by two adjacent sensors) will likely not occur on the next transmission. In another alternative, it may also be beneficial for the receiver to define a bit pattern for the <Sync> byte that does not occur anywhere else in the transmitted data, such as used, for example, with the HDLC bit stuffing protocol. In another alternative, it may be beneficial to use an error correction protocol, instead of retransmissions, to reduce overall data throughput. In still another alternative, a more elaborate checksum is used to reduce the risk of processing invalid data.
In still another alternative, a “Hamming Code” may be used in the transmission protocol. Hamming codes are typically used with continuous streams of data, such as for a CD player, or for the system described in connection with
The display unit receiver is typically in the physical form of a watch, pager, cell phone or PDA; and, further, receivers also typically have corresponding functionality. By way of example, one receiver is a cell phone that additionally functions as a receiver to read and interpret data from a MMD. Furthermore, a display unit is preferably operative to receive and display more than one movement metric. As such, data packets described above preferably include the additional metric data, e.g., containing both impact and airtime event data. Display units of the invention preferably have versatile attachment options, such as to facilitate attachment to a wrist (e.g., via a watch or Velcro strap for over clothing), a neck (e.g., via a necklace), or body (e.g., by a strap or belt).
Sensors such as the monitor devices described above, and corresponding display unit receivers, preferably have certain characteristics, and such as to accommodate extreme temperature, vibration and shock environments. One representative sensor and receiver used to determine airtime in action sports can for example have the following non-limiting characteristics: sensor attaches to a flat surface (e.g., to snowboard, ski, wakeboard); sensor stays attached during normal aggressive use; display unit attachable to outside of clothing or gear; waterproof; display unit battery life three months or more; sensor battery life one week or more of continuous use; on/off functionality by switch or automatic operation; characters displayed at data unit visible from a minimum of eighteen inches; minimum data comprehension time for data minimum of 0.5 second; last airtime data accessible with no physical interaction; one second maximum time delay for display of airtime data after jump; displayed data readable in sunlight; displayed data includes time and/or date information of airtime; user selection of accumulated airtime; display unit provides real time information; display unit operable with a maximum of two buttons; physical survivability for five foot drop onto concrete; scratch and stomp resistant; no sharp edges; minimum data precision 1/30th second; minimum data accuracy 1/15th second; minimum data resolution 1/100th second; minimum data reliability 999/1000 messages received; algorithm performance less than one percent false positive and less then two percent false negative indications per day; and temperature range minimum of −10 C-60 C.
Those skilled in the art should appreciate that the above description of communication protocols of “airtime” between sensor and receiver can be applied to monitor devices sensing other metrics, e.g., temperature, without departing from the scope of the invention.
By way of example,
With regard to
Bracket 390 of
Brackets 380, 390, 400 illustrate how sensors of the invention may beneficially attach to sporting vehicles of practically any shape, and with low profile once attached thereto. The brackets of the invention preferably conform to the desired vehicle and provide desired orientations for the sensor within its housing. By way of example, L-shaped bracket 400 may be used to effectively orient a sensor to bike 398. If for example the sensor includes a two-axis accelerometer as the detector, with sensitive axes 410, 412 arranged as shown, then vehicle vibration substantially perpendicular to ground (i.e., ground being the plane of movement for the vehicle, illustrated by vector A) may be detected in sensor orientations illustrated by attachment of housing 372 to attachments 390, 400 of
Vehicle attachment brackets (and sensor brackets) are preferably made with sturdy material, e.g., Aluminum, such that, once attached to a vehicle (e.g., vehicle 390 or 398), the vibration characteristics of the underlying vehicle transmit through to the housing attached thereto; the sensor within the housing may then monitor movement signals (e.g., vibration of the vehicle, generally generated perpendicular to “A” in
Battery 426 serves to power sensor 420. PCB 422 and processor 424 serve to collect data from accelerometer(s) 428a-e when one or more contact with contacts 432a-e. Communications module 430 serves to transmit data from sensor 420 to a receiver, such as in communications ports 16, 26. Operation of accelerometer sensor 420 is described with discussion of
In illustrative example of operation of sensor 420, moment arm 428d moves in direction 434a when force moves arm 428d in the other direction 434b. Once arm 428d moves far enough (corresponding to space 436), then arm 428d contacts contact 432d. At that point, a circuit is completed between arm 428d, processor 424 and battery 426, such as through track lines 438a, 438b connecting, respectively, contact 432d and arm 428d to other components with PCB 422. A certain amount of force is required to move arm 428d to contact 432d; arm 428d is preferably constructed in such a way that that force is known. For example, arm 428d can be made to touch contact 432d in response to 10 g of force in direction 434a. Other arms 428a-c, 428e have different lengths (or at least different masses) so that they respond to different forces 434 to make contact with respective contacts 432. In this way, the array of moment arms 428 quantize several g's for accelerometer 100.
In the preferred embodiment, processor 424 includes A/D functionality and has a “sleep” mode, such as the “pic” 16F873 by MICROCHIP. Accordingly, accelerometer sensor 420 draws very little current during sleep mode and only wakes up to record contacts between arms 428 and contacts 432. The corresponding battery life of accelerometer sensor 420 is then very long since the only “active” component is processor 424—which is only active for very short period outside of sleep mode. Communications module is also active for just a period required to transmit data from sensor 420.
Processor 424 thus stores data events for the plurality of moment arms 428. By way of example, moment arms 428a-e can be made to complete the circuit with contacts 432 at 25 g (arm 428e), 20 g (arm 428d), 15 g (arm 428c), 10 g (arm 428b) and 5 g (arm 428a), and processor 424 stores results from the highest g measured by any one arm 428. For example, if the accelerometer sensor experiences a force 434b of 20 g, then each of arms 428e, 428d, 428c and 428b touch respective contacts 432; however only the largest result (20 g for arm 428b) needs to be recorded since the other arms (428e-c) cannot measure above their respective g ratings. Longer length arms 428 generally measure less force due to their increased responsiveness to force. Those skilled in the art should appreciate that arms 428 can be made with different masses, and even with the same length, to provide the same function as shown in
Data events from arms 428 may be recorded in memory 424a or 430a. If for example communications-module 430 is a transponder or RFID tag, with internal FLASH memory 430a, then data is preferably stored in memory 430a when accelerometer sensor 420 wakes up; data is then off-loaded to a receiver interrogating transponder from memory 430a. Alternatively, processor 424 has memory 424a and event data is stored there. Module 430 might also be an RF transmitter that wirelessly transmits data off-board at predetermined intervals.
In the preferred embodiment, sensors 452 internally process proximity data to calculate velocity and/or distance as “event” data, and then wirelessly communicate the event data to receiver 462. Alternatively, proximity data is relayed to receiver 462 without further calculation at sensors 452. Calculations to determine distance or velocity performed by a runner using shoes 454 can be accomplished in sensor(s) 452 or in receiver 462, or in combination between the two. Distance is determined by a maximum separation between sensors 452 for a stride; preferably, that maximum distance is scaled by a preselected value determined by empirical methods, since the maximum distance between sensors 452A, 452B determined while running is not generally equal to the actual separation 461 between successive foot landings (i.e., while running, only one of shoes 454 is on the ground at any one time typically, and so the maximum running separation is less than actual footprint separation 461—the scaling value accounts for this difference and calibrates system 450).
Velocity is then determined by the maximum stride distance (and preferably scaled to the preselected value) divided by the time associated with shoe 454 impacting ground 456. An accelerometer may be included with sensor 452 to assist in determining impacts corresponding to striking ground 456, and hence the time between adjacent impacts for shoe positions A and B. Events may be queued and transmitted in bursts to receiver 462; however events are typically communicated at each occurrence. Events are preferably time tagged, as described above, to provide additional timing detail at receiver 462.
In one embodiment, sensor 482 transmits continuous acceleration data to receiver 492; and receiver 492 calculates velocity and/or distance based upon the data, as described in more detail below. Sensor 492 thus operates much like a MMD 150 described in
Generally, sensor 482 calculates a velocity and/or distance event after sensing two “impacts.” Impacts 500 are shown in
Alternatively, sensor 482 calculates velocity and/or distance between successive low motion regions 502. Regions 502 correspond to when shoe is relatively stationary (at least along direction 491) after landing on ground 486 and prior to launching into the air.
Once impact 500 or low motion region 502 is determined within sensor 482, sensor 482 integrates acceleration data generated by its internal accelerometer until the next impact or low motion region to determine velocity; a double integration of the acceleration data may also be processed to determine distance. Preferably, data from the sensor accelerometer is processed through a low pass filter. Preferably, that filter is an analog filter with a pole of about 50 Hz (those skilled in the art should appreciate that other filters can be used). However, generally only velocity is calculated within sensor 482; and distance is calculated in receiver 492 based on the velocity information and time T between impacts 500 (or low motion regions 502) of sensor 482. Preferably, velocity is only calculated over the time interval Ti between each impact 500. Velocity may alternatively be calculated over an interval that is shorter than T, such that runner velocity is scaled to velocity over the lesser interval. The shorter interval is useful in that acceleration data is sometimes more consistent over the shorter interval, and thus much more appropriate as a scalable gauge for velocity. Given the short time of T, very little drift of accelerometer data occurs, and velocity may be determined sufficiently. Ti is typically less than about one second, and is typically about ½ second or less.
Briefly, the processor within sensor 482 samples accelerometer data within each “T” period, or portion of the T period, and integrates that data to determine velocity. The initial velocity starting from each impact 500 (or low motion region 502) is approximately zero. If Ai represents one sample of accelerometer data, and the sampling rate of the processor is 200 Hz (i.e., preferably a rate higher than the low pass filter), then Ai/200 represents the velocity for one sample period ( 1/200 second) of the processor. Data 504 illustrates data A, over time t. Since T (in seconds)*200 samples=x samples are taken for each period T, then the sum of all of the Ai/200 for each of the x samples, divided by the number x, determines average velocity over period T. For integrations over a period that is less than T, fewer samples (less than x) are used to calculate velocity.
Sensor 482 calculates and transmits its velocity data to receiver 492. Velocity data V1 corresponds to period T1, velocity data V2 corresponds to period T2, and so on. Generally, because of processing time, sensor 482 in this example transmits V1 in period T2, transmits V2 during period T3, and so on. Receiver 492 averages Vi, over time, and communicates the average to the runner in useful units, e.g., 10 mph or 15 kmph.
Note that if only one accelerometer is provided with each shoe 484, then calibration of velocity Vi may be made for sensor 452 by calibration against a known reference, e.g., by running after a car or running on a treadmill. More particularly, since the accelerometer is oriented in various ways during a period T, other than along direction 491, then errors are induced due to the acceleration of gravity and other forces. However, since Vi is reported sequentially to receiver 492, a correction factor may be applied to these velocities prior to display on display 498. By way of example, if one runner substantially maintains his shoes 484 level, such that accelerometers in sensors 492 maintain a constant orientation along direction 491 during period T, then the reported Vi reasonably approximates actual velocity over that period. However if the runner points his shoes with toe towards ground 486, during period T, then only a component of the detected acceleration vector is oriented along direction 491. However, by calibrating system 480 against a known reference, a substantially true velocity for each period T may be obtained. Moreover, shoe sensor 482 can have a different adjustment factor applied for different gaits (e.g., jogging or running, as shoe orientations during period T may vary for different gaits).
Generally, a calibration for velocity is made at least once for each shoe using the invention, to account for variations in electronic components and other effects. Calibration also adjusts for the gait of the runner in orienting the accelerometer relative to ground 486. Preferably, like several of the MMDs described herein, a battery powers sensor 482; and that battery can be replaced once depleted. Implanting the MMD within shoe 484 is beneficial in that a fixed orientation, relative to direction 491, is made at each landing.
To alleviate the problems associated with acceleration errors, one preferred sensor 482′ for a shoe 484′ is shown in
Once processor 512 determines Vi for period Ti, then communications port 514 transmits Vi to the user's watch receiver (e.g., receiver 492,
Note that the systems of
There are several advantages of the invention of
System 520 thus preferably has at least one MMD 524 attached to, or within, runner shoe 532; MMD 524 of the preferred embodiment includes at least one accelerometer arranged to detect forward acceleration of runner 525. A processor within MMD 524 processes the forward acceleration to determine runner speed. Additional accelerometers in MMD 524 may be used, as described herein, to assist in determining speed with improved accuracy. In the preferred embodiment, MMD 524 wirelessly transmits speed as wireless data 527 to wrist instrument 526, where speed is displayed for runner 525. System 520 providing speed from a single MMD 524 can provide speed accuracy of about 97%. To improve accuracy, a second MMD 524 (not shown) is attached to, or placed within, a second shoe 532; the second MMD 524 also determining runner speed. Speed information from a second shoe 532b is thus combined with speed information from shoe 532a to provide improved speed accuracy to runner 525; for example, the two speeds from shoes 532a, 532b are averaged. System 520 providing speed from a pair of MMDs 524 can provide speed accuracy of better than 97%.
System 520 works as a runner speedometer with MMD 524 (or multiple MMDs 524, one in each shoe 532). However, to improve accuracy of speed delivered to runner 525, a GPS chip device 522 is attached to clothing 530 of runner 525. Device 522 may for example be placed within a pocket of clothing 530, the pocket being in the shoulder region so that device 522 has a good view of the sky. Device 522 processes successive GPS signals to determine a speed based upon successive positions. System 520 utilizing device 522 thus provides enhanced speed to runner 525 when using device 522. Speed from device 522 is communicated to wrist instrument 526 where it is displayed for runner 525. Preferably, instrument 526 uses speed from device 522 when speed data is consistent and approximately similar to speed data from MMD 524. Instrument 526 alternatively combines speed data from device 522 and device 524 to provide a composite speed. If device 522 is obscured, so GPS signals are not available, then system 520 provides speed to runner 525 solely from MMD 524 (or multiple MMDs 524, one in each shoe). As an alternative, device 522 can be integrated within a pocket in a hat worn by runner 525, such that device 522 again has an un-obscured view of the sky.
System 540 can additionally include crank torque measurement sensor 548. Sensor 548 preferably includes a strain gauge connected with bicycle crank 550 to measure force applied to pedals 552 and wheels 554. Preferably, a sensor 548 is applied to each pedal so that system 540 determines the full effort applied by the cyclist on any terrain. Sensor(s) 548 accumulate, process and transmit tension data to receiver and display 546. System 540 can additionally include tension measurement sensor 556 used to measure tension of chain 558. Sensor 556 similarly accumulates, processes and transmits tension data to receiver and display 546. Device 546 preferably includes processing and memory elements (e.g., similar to receiver 231,
As alternatives to system 540, without departing from the scope of the invention, those skilled in the art should appreciate that (1) sensor 542 may be combined with either of sensor 544 or receiver 546; (2) sensors 542 and 544 may communicate through electrical wiring instead of through wireless communications; (3) a GPS sensor providing earth location and altitude may instead provide the data of sensors 542, 544 for system 540; and (4) receiver and display 546 may instead be a watch mounted to a user's wrist. Preferably, system 540 includes memory, e.g., within receiver and display 546, that stores gradient information associated with a certain ride on terrain, and then provides a “trail difficulty” assessment for the stored data. Maximum and minimum gradients are also preferably stored and annotated in memory for later review by a user of system 540.
Wireless data 606 can for example be at 2.4 GHz since data capture device 602 may be sufficiently powered from racecars 604. Wireless data 610 can for example be unlicensed frequencies such as 433 MHz or 900-928 MHz, so that each crowd data device 608b may be powered by small batteries such as described herein in connection with receivers for monitor devices. Wireless data 610 can further derive from cellular networks, if desired, to communicate directly with a crowd data device. Wireless link 606 and 610 can encompass two way communications, if desired, such as through wireless transceivers.
Computer relay 608a may further provide data directly to a display scoreboard 614 so that spectators 612 may view scoreboard 614 for information derived by system 600. Scoreboard 614 may for example be near to spectator stand 616.
Data relayed to spectators 612 can be of varied format. Device 602′ can for example be a MMD with a detector providing acceleration information. Acceleration data in the form of “g's” and impact is one preferred data communicated to spectators 612 through wireless data 606′. Car 604′ may in addition have accelerometers as part of car electronics; and device 602′ preferably communicates on-board acceleration data as wireless data 606′. Device 602′ and car electronics 618 can for example include a speedometer, accelerometer, tachometer, gas gauge, spin sensor, temperature gauge, and driver heart rate sensor. An on-board computer can further provide position information about car 604′ position within the current race (e.g., 4th out of fifteen racecars). Accordingly, device 602′ collects data from these sensors and electronic sources and communicates one or more of the following information as wireless data 606′: racecar speed, engine revolutions per minute, engine temperature, driver heart rate, gas level, impact, g's, race track position, and spin information. As described in connection with the monitor devices above, data 606′ may be continually transmitted or transmitted at timed sequence intervals, e.g., every minute. Data 606′ may also be transmitted when an event occurs, e.g., when a major impact is reported by a device 602′ (e.g., in the form of a MMD) such as when car 604′ experiences a crash. A spin sensor also preferably quantifies rollover rate, acceleration and total rotations (e.g., four flips of the car is 1440 degrees).
Data captured by device 608b′ may be from one car or from multiple cars 604. Car selection button 630 can be pressed to capture all data 606′ from all cars, or only certain data from one car, or variants thereof. In one embodiment, the update rate transferred as wireless data 606′ from any car 604′ to any crowd data device is about one second; and so each device generally acquires data from one car at any one time and “immediately” (i.e., within about one second) acquires data from another car if selected by button 630. Alternatively, all data 606′ from all cars 604 are communicated and captured to each device 608b′. This alternative mode however uses more data bandwidth to devices 608b′.
Accordingly, users of crowd data device 608b′ may view performance and data metrics from any car of choice during a race. Currently, spectators only have a vague feel for what is actually happening to a car at a race between multiple cars 604. With the invention, a spectator can monitor her car of choice and review data personally desired. One spectator might for example be interested in the driver heart rate of one car; one other spectator might for example be interested in the speed of the lead car; yet another spectator might for example be interested in the temperature of the top four cars; most spectators are concerned about which car is the lead car. In accord with the invention, each spectator may acquire personal desired data in near real time and display it on individual crowd data devices in accord with the invention. Data captured from system 600 can further be relayed to the Internet or to broadcast media through computer relay 608a, if desired, so that performance metrics may be obtained at remote locations and, again, in near real time.
The invention also provides for displaying certain data at display scoreboard 614. Computer relay 608a may in addition connect to race officials with computers that quantify or collate car order and other details like car speed. Such data can be relayed to individuals through crowd data devices 608b or through scoreboard 614, or both.
System 600 may be applied to many competitive sports. For example, when the data capture device is like a MMD, system 600 can be applied to sports like hockey, basketball, football, soccer, volleyball and rodeos. A MMD in the form of an adhesive bandage, described above, is particularly useful. Such a MMD can for example be applied with football body armor or padding, as illustrated in
Likewise, a MMD of the invention is effectively used in rodeo, as shown in
Those skilled in the art should also appreciate that MMDs 674 can include different detectors providing data desired by sports media. For example, if the MMD contains a linear accelerometer, linear motion forces are reported; if the MMD contains a rotational accelerometer, rotational forces are reported. These MMDs may be placed on various parts of bull 670 or rider 672, such as on the body and head. Data from MMDs may be relayed to television, scoreboards and/or the Internet. Data collated on the Internet preferably includes bull and rider performance summaries.
The invention of one preferred embodiment employs data taken from monitor devices such as described above and applies that data to video games, arcade games, computer games and the like (collectively a “game”) to “personalize” the game to real ability and persons. For example, when a monitor device is used to capture airtime (and e.g., heart rate) of a snowboarder, that data is downloaded to a database for a game and used to “limit” how a game competitor plays the game. In this way, a snowboard game player can compete against world-class athletes, and others, with some level of realism provided by the real data used in the game.
More particularly, one missing link in the prior art between video games and reality is that one a person can be great at a video game and relatively poor at a corresponding real sport (e.g., if the game is a snowboard game, the player may not be a good snowboarder; if the game is a car race, the person may not be a good race car driver; and so on). With performance metrics captured as described herein, the data is applied such that an entirely new option is provided with games. As known in the art, games take the form of PLAYSTATION, SEGA, GAMEBOY, etc.
In operation the invention of the preferred embodiment works as follows. Individuals use a monitor device to measure one or more performance metrics in real life. Data from the monitor devices are then downloaded into a game (or computer running the game) for direct use by the game. Data used in the game may be averaged or it may be the best score for a particular player. By way of example, when the performance metric is “airtime”, the option applied to the game allows the game player (typically a teenager) to measure a certain number of airtimes, in real life, and download them into the game so that the air the game player ‘catches’ during the game corresponds to his real airtime (e.g., best airtime, average airtime, etc.). Data used in games can be collated and interpreted in many ways, such as an individual's best seven airtimes of a day or a personal all time record for an airtime jump.
The effect of the invention applied to games is that game users are somewhat restricted in what they can do. In a ski game, for example, a kid that does not have the natural athletic ability to do flips will not, if the option is selected, be permitted to perform flips in a game. Competitions within games then become far more real. If a kid catches only one second of airtime, on average, then it is unlikely that he can catch three seconds of airtime like Olympic athletes; accordingly, when the gaming option is selected, those kids will not be permitted within the game to throw airtime (and corresponding tricks that require like airtimes) of three seconds or higher, for example. The game restricts them to doing tricks that could actually be completed in their normal airtime.
There would of course still be elements making the game unrealistic, and fun. The invention applied to games does however add a measure of realism to the games. For example, limiting a game to airtime may restrict movements to certain types, e.g., one flip instead of two. This is one example of how the invention applied to games makes the game much more real. Another gaming option is to permit the gaming user to expand their current real performance by some percentage. For example, a gaming user can instruct the game to permit 100% performance boost to his real data in competitions in the game. In this way, the gaming user knows how far off his real performance is from gaming performance. If for example it takes a 120% performance boost to beat a well-known Olympic athlete, then she knows (at least in some quasi-quantitative measure) how much harder she will need to work (i.e., 20%) to compete with the Olympic athlete.
Similar limitations to the games may be done with other metrics discussed herein, including drop distance, speed and impact, heart rate and other metrics. For example, by acquiring “impact” data through a MMD of the invention, it is known how much impact a particular athlete achieves during a jump or during a particular activity. By way of example, by collecting impact data from a boxer or karate athlete, it is roughly known the magnitude of impacts that that person endures. Such limitations are applied to games, in accord with other embodiments of the invention. Accordingly, a video game competitor may be limited to actions that he or she can actually withstand in real life. Spin rates too can limit the game in similar ways.
In the preferred embodiment of the invention, data from monitor devices applied to persons are downloaded as performance metrics into games. These metrics become parameters that are adhered to by the player if the gaming option is selected within the game. The ability to play the game, and the moving of the correct buttons, joystick or whatever, is thus linked to the real sport. By way of example, PLAYSTATION has a ‘world championship’ for the games. In accord with the invention, game players may now compete with their ability tied to competitions within the game, making it much more realistic on the slopes, vert ramp or other game obstacle.
In accord with one embodiment, systems like system 600 are also effectively applied to “venues” like skateparks. The data capture devices (preferably in the form of MMDs) are applied to individual users of the venue, e.g., skateboarders. Data acquired from the users are transmitted to a computer relay that in turn connects directly to game providers or Internet gaming sources. The venues are thus linked to games. Resorts with venues such as terrain parks are thus incentivized to make their venue part of the gaming world, where kids play in their park in synthesized video, and then actually use the venue to acquire data for use with the game. By tying competitors together from real venues to gaming, a real venue and a game venue become much more alike. Stigmas associated with playing games may also be reduced because gaming is then tied to reality and kids can participate in meaningful ways, both at the venue and within the game. Kids can then compete based upon real ability at both the game and in real life.
As an alternative, users of devices 702 may directly download game parameters to computer game 705, as through a local data link 710. Users may also type game parameters directly into module 708. In either case, computer game 705 has real limiting functions to gaming actions via the invention. Preferably server 704 controls the download of data to computer game 705 so that data is controlled and collated in a master database for other uses and competitions.
System 700 can further network with an arcade game 720 in a similar manner, such as through Internet connection 718. Real performance data is again stored in real personal data module 722 in game 720 (or at the computer controlling game 720) so that users have restrictions upon play. User ID codes facilitate storing and accessing data to a particular person. In this way, users of arcade games can access and limit their games to real data associated with their skill. Competitions between players at arcade games, each with their own real personal data in play, increase the competitiveness and fairness of game playing.
Approximate distances B-A, B-C, D-A, D-C are stored in remote computer 806. Specifically, computer 806 has memory 808 to store distances B-A, B-C, D-A, D-C. Computer 806 and readers 804 preferably communicate by wireless data 810-1, 810-2; thus computer 806 preferably has antenna 812, and associated receiver and transmitter 814, to facilitate communications 810. Computer 806 further has a processor 816 to process data and to facilitate control of computer 806.
A representative reader 802′ is shown in
In operation, a ticket 826 is read each time for persons riding lifts 804. A time is associated with when the ticket is read and logged into computer 806. When that ticket 826 again is read, e.g., either at lift 804-1 or 804-2, a second reading time is logged into computer 806. Processor 816 of computer 806 then determines speed based upon (a) the two reading times, (b) the approximate lift time for the appropriate lift 804, and (c) the distance traveled (i.e., one of distances B-A, B-C, D-A, D-C). For example, suppose a person enters lift 804-1 at 9 am exactly and enters lift 804-2 at 9:14 am. Suppose lift 804-1 takes ten minutes, on average, to move a rider from A to B. Accordingly, this person traveled distance B-C in four minutes. If distance B-C is two miles, then that person traversed distance B-C with a speed of 30 mph. If the resort where system 800 is installed sets a maximum speed of 25 mph for the mountain 801, then that person exceeded the speed and may be expelled from the resort. Note further that the resort may specify speed zones, corresponding to each of the paths B-A, B-C, D-A, D-C. If for example path B-A has a wide path, then a speed may be set at 30 mph. A person successively repeating lift 804-1 may thus be checked for speeds exceeding 30 mph. If on the other hand path D-A has a lot of trees, then a speed of 20 mph may be set; and a rider who rides lift 804-2 and arrives at lift 804-1 can be checked for violations along route D-A.
When a ski lift 804 stops, then additional time is added to that person's journey. A feedback data mechanism tracking lift movement can augment data in computer 806 to adjust skier speed calculations on dynamic basis.
Note that system 800 serves to replace or augment sensor 231′ of
As shown in
The invention of
The monitor devices of the invention have further application in medicine and patient health. One monitor device 870 of the invention is shown in
Like other monitor devices herein, device 870 has a detector 870a to detect the desired metric. For purposes of illustration, other elements such as the device's communications port and processor are not shown, though reference may be made to
Preferably, device 870 is integrated with an adhesive strip 880; and device 870 and strip 880 form an adhesive bandage monitor device such as described above in connection with
Those skilled in the art should appreciate that device 870 may also attach to the infant in a variety of places depending on the parent's desire. Device 870 may for example attach to the back or bottom of the infant, and generate an event for every time the infant rolls over.
As an alternative, the detector of the monitor device (
The MMDs and EMDs of the invention thus have several other advantages. They may be used discretely and safely as medical diagnostic and monitoring detectors. With appropriate detectors, EMDs of the invention can for example provide for portable, wireless pulse oxymeters or blood glucose monitors. With the appropriate detectors in MMDs, rehabilitation clinicians would be able to quantitatively monitor metrics such as limb movement and balance. EMDs equipped with certain detectors may find use as real time, remote and inexpensive pH monitors and blood gas monitors.
One MMD 900 of the invention and useful in medical applications is shown in
MMD 900 is preferably in the form of a MMD 10z of
A weight sensing MMD may also take the form of MMD 920,
In this way, a person may track his or her weight at any time. MMD 920 and receiver 940 may also communicate two-way, so that watch 940 queries MMD 920 for weight data, thereby conserving battery power. Those skilled in the art should appreciate that MMD and receiver 920, 940 may be configured differently and still be within the scope of the invention. In one embodiment, MMD 920 is integrated with a shoe pad insert to fit into any shoe. Alternatively, MMD 920 is integrated directly into a shoe, as shown in
Preferably, resistor 960 includes flexible polymers as active spring agents as the sensing element for loading conditions. Such polymers provide load-sensing resistors with enhanced performance and with preferable mechanical characteristics.
As an alternative to a single cavity 974, cavity 974 can also be made up of separate fluid cells, as exemplified by sections 974A, 974B, 974C, and 974D, and multiple sensors 976A, 976B. In this embodiment, cavity membrane walls 978 separate sections 974A, 974B, 974C, 974D; optionally two or more of sections 974A, 974B, 974C, 974D have an individual pressure sensor monitoring pressure of the particular section, such as sensor 976A for section 974D and sensor 976B for section 974C. This embodiment is particularly useful in providing highly accurate weight sensing for a user of shoe 972. Each fluid cell 974A-D may for example have differing pressurization characteristics to manage the overall weight application of a human foot. For example, cells 974B, 974C may be formed with higher pressure cavities as they are, respectively, under the ball or heel of the foot and likely have to accommodate higher pressures (i.e., higher applied weight to those sections). In either event, a processor connected to the several pressure sensors 976A, 976B beneficially determines weight as a combination of different pressures of the different fluid cells. Alternatively, a single pressure sensor 976A may be used to sequentially measure pressure from various fluid cells 974A-D; and the processor (not shown) then determines weight based upon the several measurements.
Those skilled in the art should appreciate that the number of cells 974A-D, and the number of sensors 976A, 976B, are a matter of design choice and do not depart from the scope of the invention; more or fewer cells 974 or sensors 976 may be used without departing from the scope of the invention. Those skilled in the art should also appreciate that a shoe insert can alternatively house cavity 974 (and/or sections 974A, 974B); for example, shoe 972 can for example be a shoe insert instead of a shoe—constructed and arranged such that a user applies weight on cavity 974 in use.
A weight-sensing device of the invention, for example as set forth in
The invention thus has several advantages in regard to weight loss, monitoring and human fitness. In accord with the above invention, a user of a weight monitoring system or device disclosed herein can review his or her weight at nearly any time. Runners using such a system and device to know their hydration loss; chiropodists may wish to monitor weight distribution over a patient's feet; and athletic trainers may wish to analyze weight distribution and forces. The invention of these figures assists in these areas. In making these measurements, force-sensing resistors may be used; but strain gauge pressure sensors in the shoe may also be used. Preferably, in such embodiments, the bottom surface of the foot is covered by sensors, as weight is not often evenly distributed. Accordingly, a single sensor may not encompass a preferred arrangement, and therefore multiple sensors are preferred in the sole of the shoe (or in a shoe insert), with the results of all sensors summed or combined to a single “weight” answer. In one embodiment, only a portion of the foot need to be covered, covering a certain percentage of the overall weight; and that percentage is scaled to a user's full weight. Weight and compression forces monitored in a shoe or shoe insert, in accord with the invention, can further assist in gauging caloric and/or physical effort.
Data from sensors 1108 typically include information such as impact, as described above. Events associated with “impact” are communicated wirelessly to a receiving computer 1120 as wireless data 1122. Data 1122 for example includes digital data representing impact data received at any of sensors 1108 when wrestlers hit canvas 1110, move ropes 1114, or hit post 1112. Receiving computer 1120 preferably has an antenna 1124 and communications port 1126 to receive data 1122. Computer 1120 typically re-processes and then retransmits data 1122 to a media site 1129, such as television, scoreboard or the Internet, so that viewers may see data 1122 associated with wrestling at rink 1102. Since wrestling in and about rink 1102 is often based on choreographed action, computer 1120 preferably includes a data manipulation section 1130 which post processes data 1122 in predetermined ways. For example, section 1130 may apply an exponential or quadratic function to data 1122 so that, in effect, and by way of example, a 25 g impact on canvas 1110 is reported as a 25 g impact, but a 50 g impact on canvas 1110 is reported as a 1000 g impact.
Section 1130 may also manipulate data for a particular player. For example,
Data from computer 1120 is thus reported to a media destination 129 such as television so that it may be displayed to audience members.
Thus,
In the preferred embodiment, at least one sensor 1108 attached to ropes 1114 preferably takes the form of a long thin sensor (e.g., 0.5″×3″) with a short piece wire (e.g., 3″) protruding from one end to function as the antenna. This sensor's electronics utilizes a small low power accelerometer as the sensing detector, and incorporates a simple gain block, a small micro controller such as Microchips' PIC 12LC672, and a small low power transmitter such as RFMs′RX6000 or RF Solutions' TX1. These electronics mount on flex circuit (e.g., as shown in
In the preferred embodiment, at least one sensor 1108 attached to posts 1112 incorporates a gas pressure sensor as the detector; such a sensor is incorporated into the cushions protecting the corner posts 1112 and thus registers an increase reading as the wrestlers collide with the posts Alternatively, such a sensor may be incorporated directly into a cushion attached to post 1112; preferably such a cushion is airtight.
In one embodiment, at least one of the sensors attached to ropes 1114 include extension detectors (or LVDT devices) at the points where the ropes are mounted. Sensors 1108 with strain gauges may also be used. Sensors attached to ropes 1114 preferably detect “rope deflection” as a reported metric.
In one embodiment, sensors 1108 in the floor incorporate piezoelectric cables mounted as an interlocking grid attached to the underside of the floor. For example, such cables connect the “x” locations of
One MMD 1140 may also gauge the power of a wave landing on top of the surfer 1142. Such a MMD 1140 preferably includes a pressure detector to determine pressure within water 1144 when a wave lands on surfboard 1146 and on surfer 1142. A “maximum pressure” event is then reported by MMD 1140.
Another MMD 1140 includes an inclinometer or other angle determination detector to determine and report angle of the surfboard 1146; for example a maximum angle is reported for a given run or day.
Data from any particular metric (e.g., g's in a turn, angle of surfboard, pressure under water) provided by MMD 1140 is preferably reported wirelessly to a watch worn by surfer 1142; however such data may also be displayed on a display integrated with surfboard 1146 or directly with sensor 1140, such as shown with an airtime sensor in U.S. Pat. No. 5,960,380, incorporated herein by reference. In the form of a wristwatch, one MMD of the invention includes a pressure sensor housed in the watch; the MMD watch then reports the maximum pressure events without need of a separate MMD 1140 mounted to surfboard 1146 (or integrated therein).
In one preferred embodiment, MMD 1140 includes a speed detector (such as a Doppler module or accelerometers as discussed herein or in U.S. Pat. No. 5,960,380) so that surfer speed is reported to surfer 1142. Preferably, in this embodiment, distance traveled is also reported; by way of example the receiver of data from MMD 1140 (e.g., a digital watch) converts speed to distance by multiplying speed by a time duration traveled over that speed.
In one preferred embodiment, each transceiver 1302a, 1304a, 1306a, 1308a, 1309a, 1310a includes a Bluetooth microchip and transceiver known in the art. Bluetooth transceivers only maintain a communication link (at a frequency of about 2.4 GHz in the ISM band) over a short range, e.g., 50 feet, and are not generally suitable for longer communication distances.
Optionally, one or more of transceivers 1302a, 1304a, 1306a, 1308a, 1309a, 1310a are instead transponders; and at least one of items 1302a, 1304a, 1306a, 1308a, 1309a, 1310a provide excitation energy to the transponders to “reflect” data along link 1320 to provide the functionality described herein. Those skilled in the art should appreciate that items 1302a, 1304a, 1306a, 1308a, 1309a, 1310a may incorporate other technology, such as transmitters, to facilitate like functionality. That is, not every item 1302, 1304, 1306, 1308, 1309, 1310 needs to transmit and receive data on link 1320. For example, wallet 1306 can include a transmitter instead of a transceiver to provide data about itself on link 1320; and other items 1302, 1304, 1308, 1309, 1310 can use wallet data to know whether it is in the network or not (even though wallet 1306 does not know whether other items 1302, 1304, 1308, 1309, 1310 are in the network). Transponders can provide like functionality for certain items 1302, 1304, 1306, 1308, 1309, 1310 as a matter of design choice.
Wireless link 1320 includes information about time and items in the network; preferably the information also includes location information. For example, data 1320 informs each item 1302-1310 that every other item is still within the network, and, thus, that one or more items have not moved to beyond the Network Distance. If one item—e.g., keys 1304—leaves the network so that item 1304 no longer communicates on link 1320, every other item 1302, 1306, 1308, 1310 knows that item 1304 is no longer linked and data is stored on every other item 1302, 1306, 1308, 1310 indicating a time when item 1304 left the network. Preferably, the stored data in every other item also includes where the network was when keys 1304 disappeared.
In the simplest embodiment, each of items 1302-1310 includes a corresponding indicator 1302b-1310b; each of indicators 1302b-1310b can for example be a LED, LCD, buzzer or vibrator. When any of items 1301-1310 are “lost” from the network—e.g., one item moves beyond the Network Distance—then the indicator in one or more of the other items tells the user of system 1300 that an item has “left”. That person can then expend effort to location the lost item. By way of example, each of indicators 1302b-1310b may provide a beep, sound or vibration to provide the user with knowledge of a lost item 1302-1310.
In a more complex embodiment, data stored on any item 1302-1310 indicating the loss of any item within network 1300 is a “cookie” of information detailing when and where an item left the network. In this way, a user of system 1300 can locate and find the lost item by reviewing cookies in any other item. By way of example, consider a network 1300 made from keys 1304, wallet 1306, digital watch 1309 and cell phone 1302—items commonly carried by a male business person. In the preferred embodiment, this person would designate items 1302, 1304, 1306, 1309 as being “in network” (such as described below in connection with
Users of system 1300 “program” which items are in the network preferably through a personal computer interface, shown in
Note that a “wallet” or “purse” do not generally have electronics associated therewith, to provide the functionality described above. Therefore, in the preferred embodiment, a transceiver 1306a is “attached” to a wallet or purse to provide the underlying electronics. By way of example, such a transceiver takes the form of a credit card inserted into the wallet or purse.
In the preferred embodiment, a dispenser 1514 may contain several labels similar to label 1504; dispenser preferably issues label 1504 in a manner similar to canister 200,
This application is a continuation of U.S. patent application Ser. No. 14/222,855, filed Mar. 24, 2014, which is a continuation of U.S. patent application Ser. No. 13/761,829 (now U.S. Pat. No. 8,688,406), filed Feb. 7, 2013, which is a divisional of U.S. patent application Ser. No. 12/428,186, filed Apr. 22, 2009, (now U.S. Pat. No. 8,374,825) which is a divisional of U.S. patent application Ser. No. 11/647,042, filed Dec. 28, 2006, (now U.S. Pat. No. 7,552,031) which is a divisional of U.S. patent application Ser. No. 10/601,208 filed Jun. 20, 2003, (now U.S. Pat. No. 7,174,277) which is a continuation of U.S. patent application Ser. No. 10/297,270 filed Dec. 4, 2002 (now U.S. Pat. No. 8,280,682), which claims priority to PCT Application No. PCT/US01/51620, filed Dec. 17, 2001, which claims priority to U.S. Provisional Patent Application No. 60/256,069, filed Dec. 15, 2000; U.S. Provisional Patent Application No. 60/257,386, filed Dec. 22, 2000; U.S. Provisional Patent Application No. 60/259,271, filed Dec. 29, 2000; U.S. Provisional Patent Application No. 60/261,359, filed Jan. 13, 2001; U.S. Provisional Patent Application No. 60/285,032, filed Apr. 19, 2001; and U.S. Provisional Patent Application No. 60/323,601, filed Sep. 20, 2001. The foregoing applications are expressly incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3612265 | Dickerson | Oct 1971 | A |
| 3717857 | Evans | Feb 1973 | A |
| 3807388 | Orr et al. | Apr 1974 | A |
| 3918058 | Noyori et al. | Nov 1975 | A |
| 3958459 | Shimomura | May 1976 | A |
| 3972320 | Kalman | Aug 1976 | A |
| 3978725 | Hadtke | Sep 1976 | A |
| 4031312 | Coleman et al. | Jun 1977 | A |
| 4089057 | Eriksson | May 1978 | A |
| 4101873 | Anderson et al. | Jul 1978 | A |
| 4114450 | Shulman et al. | Sep 1978 | A |
| 4195642 | Price et al. | Apr 1980 | A |
| 4210024 | Ishiwatari et al. | Jul 1980 | A |
| 4223211 | Allsen et al. | Sep 1980 | A |
| 4248244 | Charnitski et al. | Feb 1981 | A |
| 4317126 | Gragg | Feb 1982 | A |
| 4371188 | Hull | Feb 1983 | A |
| 4371945 | Karr et al. | Feb 1983 | A |
| 4375674 | Thornton | Mar 1983 | A |
| 4409983 | Albert | Oct 1983 | A |
| 4423630 | Morrison | Jan 1984 | A |
| 4434801 | Jiminez et al. | Mar 1984 | A |
| 4463433 | Hull et al. | Jul 1984 | A |
| 4516110 | Overmyer | May 1985 | A |
| 4516865 | Hideo | May 1985 | A |
| 4566461 | Lubell et al. | Jan 1986 | A |
| 4576179 | Manus et al. | Mar 1986 | A |
| 4578769 | Frederick | Mar 1986 | A |
| 4625733 | Saynajakangas | Dec 1986 | A |
| 4630021 | Brown | Dec 1986 | A |
| 4676500 | Fricano | Jun 1987 | A |
| 4694694 | Vlakancic et al. | Sep 1987 | A |
| 4699379 | Chateau et al. | Oct 1987 | A |
| 4703445 | Dassler | Oct 1987 | A |
| 4720093 | Del Mar | Jan 1988 | A |
| 4722222 | Purdy et al. | Feb 1988 | A |
| 4736312 | Dassler et al. | Apr 1988 | A |
| 4745564 | Tennes et al. | May 1988 | A |
| 4757453 | Nasiff | Jul 1988 | A |
| 4757714 | Purdy et al. | Jul 1988 | A |
| 4759219 | Cobb et al. | Jul 1988 | A |
| 4763275 | Carlin | Aug 1988 | A |
| 4763284 | Carlin | Aug 1988 | A |
| 4763287 | Gerhaeuser et al. | Aug 1988 | A |
| 4771394 | Cavanagh | Sep 1988 | A |
| 4774679 | Carlin | Sep 1988 | A |
| 4775948 | Dial et al. | Oct 1988 | A |
| 4780837 | Namekawa | Oct 1988 | A |
| 4812541 | Mallya et al. | Mar 1989 | A |
| 4813272 | Miyazaki et al. | Mar 1989 | A |
| 4821218 | Potsch | Apr 1989 | A |
| 4822042 | Landsman | Apr 1989 | A |
| 4824107 | French | Apr 1989 | A |
| 4829812 | Parks et al. | May 1989 | A |
| 4862394 | Thompson et al. | Aug 1989 | A |
| 4862395 | Fey et al. | Aug 1989 | A |
| 4873867 | McPherson et al. | Oct 1989 | A |
| 4883271 | French | Nov 1989 | A |
| 4903212 | Yokouchi et al. | Feb 1990 | A |
| 4911016 | Miyazaki et al. | Mar 1990 | A |
| 4935887 | Abdalah et al. | Jun 1990 | A |
| 4955980 | Masuo | Sep 1990 | A |
| 5027303 | Witte | Jun 1991 | A |
| 5033013 | Kato et al. | Jul 1991 | A |
| 5036467 | Blackburn et al. | Jul 1991 | A |
| 5045035 | Ganoung | Sep 1991 | A |
| 5056783 | Matcovich et al. | Oct 1991 | A |
| 5067081 | Person | Nov 1991 | A |
| 5088836 | Yamada et al. | Feb 1992 | A |
| 5144226 | Rapp | Sep 1992 | A |
| 5148002 | Kuo et al. | Sep 1992 | A |
| 5150310 | Greenspun et al. | Sep 1992 | A |
| 5162828 | Furness et al. | Nov 1992 | A |
| 5178016 | Dauenhauer et al. | Jan 1993 | A |
| 5181181 | Glynn | Jan 1993 | A |
| 5200827 | Hanson et al. | Apr 1993 | A |
| 5221088 | McTeigue et al. | Jun 1993 | A |
| 5243993 | Alexander et al. | Sep 1993 | A |
| 5258927 | Havriluk et al. | Nov 1993 | A |
| 5295085 | Hoffacker | Mar 1994 | A |
| 5316249 | Anderson | May 1994 | A |
| 5324038 | Sasser | Jun 1994 | A |
| 5335664 | Nagashima | Aug 1994 | A |
| 5339699 | Carignan | Aug 1994 | A |
| 5343445 | Cherdak | Aug 1994 | A |
| RE34728 | Hall-Tipping | Sep 1994 | E |
| 5348519 | Prince et al. | Sep 1994 | A |
| 5365930 | Takashima et al. | Nov 1994 | A |
| 5382972 | Kannes | Jan 1995 | A |
| 5396429 | Hanchett | Mar 1995 | A |
| 5420828 | Geiger | May 1995 | A |
| 5426595 | Picard | Jun 1995 | A |
| 5436838 | Miyamori | Jul 1995 | A |
| 5442221 | Mosser et al. | Aug 1995 | A |
| 5446775 | Wright et al. | Aug 1995 | A |
| 5450329 | Tanner | Sep 1995 | A |
| 5452269 | Cherdak | Sep 1995 | A |
| 5471405 | Marsh | Sep 1995 | A |
| 5467773 | Bergelson et al. | Nov 1995 | A |
| 5475725 | Nakamura | Dec 1995 | A |
| 5478006 | Taguchi | Dec 1995 | A |
| 5485163 | Singer et al. | Jan 1996 | A |
| 5485402 | Smith | Jan 1996 | A |
| 5486815 | Wagner | Jan 1996 | A |
| 5509082 | Toyama | Apr 1996 | A |
| 5513854 | Daver | May 1996 | A |
| 5524637 | Erickson | Jun 1996 | A |
| 5526326 | Fekete | Jun 1996 | A |
| 5528228 | Wilk | Jun 1996 | A |
| 5539336 | Nguyen | Jul 1996 | A |
| 5541604 | Meier | Jul 1996 | A |
| 5546307 | Mazur | Aug 1996 | A |
| 5546974 | Bireley | Aug 1996 | A |
| 5564698 | Honey | Oct 1996 | A |
| 5574669 | Marshall | Nov 1996 | A |
| 5583776 | Levi | Dec 1996 | A |
| 5590908 | Carr | Jan 1997 | A |
| 5592401 | Kramer | Jan 1997 | A |
| 5605336 | Gaoiran | Feb 1997 | A |
| 5608374 | Ikejiri | Mar 1997 | A |
| 5615132 | Horton | Mar 1997 | A |
| 5617084 | Sears | Apr 1997 | A |
| 5618995 | Otto | Apr 1997 | A |
| 5621316 | Dames et al. | Apr 1997 | A |
| 5627548 | Woo | May 1997 | A |
| 5629131 | De Keyzer | May 1997 | A |
| 5633070 | Murayama et al. | May 1997 | A |
| 5636146 | Flentov | Jun 1997 | A |
| 5646857 | McBurney | Jul 1997 | A |
| 5650770 | Schlager et al. | Jul 1997 | A |
| 5671010 | Shimbo | Sep 1997 | A |
| 5671162 | Werbin | Sep 1997 | A |
| 5671525 | Fidalgo | Sep 1997 | A |
| 5673691 | Abrams | Oct 1997 | A |
| 5688183 | Sabatino | Nov 1997 | A |
| 5690119 | Rytky et al. | Nov 1997 | A |
| 5690591 | Kenmochi | Nov 1997 | A |
| 5690773 | Fidalgo et al. | Nov 1997 | A |
| 5694340 | Kim | Dec 1997 | A |
| 5701257 | Miura | Dec 1997 | A |
| 5720200 | Anderson | Feb 1998 | A |
| 5721539 | Goetzi | Feb 1998 | A |
| 5723786 | Klapman | Mar 1998 | A |
| 5724265 | Hutchings | Mar 1998 | A |
| 5734337 | Kupersmit | Mar 1998 | A |
| 5738104 | Lo et al. | Apr 1998 | A |
| 5742509 | Goldberg et al. | Apr 1998 | A |
| 5743269 | Okigami | Apr 1998 | A |
| 5745037 | Guthrie et al. | Apr 1998 | A |
| 5749615 | Iston | May 1998 | A |
| 5761096 | Zakutin | Jun 1998 | A |
| 5767503 | Gloton | Jun 1998 | A |
| 5771485 | Echigo | Jun 1998 | A |
| 5779576 | Smith, III | Jul 1998 | A |
| 5781155 | Woo | Jul 1998 | A |
| 5790477 | Hauke | Aug 1998 | A |
| 5796338 | Mardirossian | Aug 1998 | A |
| 5807284 | Foxlin | Sep 1998 | A |
| 5812056 | Law | Sep 1998 | A |
| 5837944 | Herot | Nov 1998 | A |
| 5862803 | Besson et al. | Jan 1999 | A |
| 5886739 | Winningstad | Mar 1999 | A |
| 5891042 | Sham et al. | Apr 1999 | A |
| 5897457 | Mackovjak | Apr 1999 | A |
| 5899963 | Hutchings | May 1999 | A |
| 5901303 | Chew | May 1999 | A |
| 5905460 | Odagiri et al. | May 1999 | A |
| 5917434 | Murphy | Jun 1999 | A |
| 5918281 | Nabulsi | Jun 1999 | A |
| 5919239 | Fraker et al. | Jul 1999 | A |
| 5925001 | Hoyt et al. | Jul 1999 | A |
| 5929335 | Carter | Jul 1999 | A |
| 5930741 | Kramer | Jul 1999 | A |
| 5936523 | West | Aug 1999 | A |
| 5946643 | Zakutin | Aug 1999 | A |
| 5947917 | Carte et al. | Sep 1999 | A |
| 5955667 | Fyfe | Sep 1999 | A |
| 5959568 | Woolley | Sep 1999 | A |
| 5960380 | Flentov et al. | Sep 1999 | A |
| 5963523 | Kayama et al. | Oct 1999 | A |
| 5963891 | Walker et al. | Oct 1999 | A |
| 5976083 | Richardson et al. | Nov 1999 | A |
| 5977877 | McCulloch et al. | Nov 1999 | A |
| 5978972 | Stewart et al. | Nov 1999 | A |
| 5983724 | Yoshida | Nov 1999 | A |
| 5984842 | Chu | Nov 1999 | A |
| 6002982 | Fry | Dec 1999 | A |
| 6009629 | Gnepf et al. | Jan 2000 | A |
| 6011491 | Goetzi | Jan 2000 | A |
| 6013007 | Root et al. | Jan 2000 | A |
| 6018677 | Vidrine et al. | Jan 2000 | A |
| 6018705 | Gaudet et al. | Jan 2000 | A |
| 6020851 | Busack | Feb 2000 | A |
| 6024643 | Begis | Feb 2000 | A |
| 6028617 | Helmsderfer | Feb 2000 | A |
| 6028625 | Cannon | Feb 2000 | A |
| 6028627 | Helmsderfer | Feb 2000 | A |
| 6032084 | Anderson et al. | Feb 2000 | A |
| 6032108 | Seiple et al. | Feb 2000 | A |
| 6032530 | Hock | Mar 2000 | A |
| 6043747 | Altenhofen | Mar 2000 | A |
| 6045364 | Dugan et al. | Apr 2000 | A |
| 6052654 | Gaudet et al. | Apr 2000 | A |
| 6057756 | Engellener | May 2000 | A |
| 6059576 | Brann | May 2000 | A |
| 6073086 | Marinelli | Jun 2000 | A |
| 6074089 | Hollander et al. | Jun 2000 | A |
| 6074271 | Derrah | Jun 2000 | A |
| 6075443 | Schepps et al. | Jun 2000 | A |
| 6078056 | Teder | Jun 2000 | A |
| 6081169 | Romerein et al. | Jun 2000 | A |
| 6089098 | Tylisz et al. | Jul 2000 | A |
| 6091342 | Janesch et al. | Jul 2000 | A |
| 6104916 | Steinhoff et al. | Aug 2000 | A |
| 6111541 | Kannel | Aug 2000 | A |
| 6111571 | Summers | Aug 2000 | A |
| 6122340 | Darley et al. | Sep 2000 | A |
| 6122846 | Gray et al. | Sep 2000 | A |
| 6122959 | Hoshal et al. | Sep 2000 | A |
| 6122960 | Hutchings | Sep 2000 | A |
| 6125686 | Haan et al. | Oct 2000 | A |
| 6127931 | Mohr | Oct 2000 | A |
| 6135951 | Richardson et al. | Oct 2000 | A |
| 6148271 | Marinelli | Nov 2000 | A |
| 6151563 | Marinelli | Nov 2000 | A |
| 6151647 | Sarat | Nov 2000 | A |
| 6155927 | Levasseur et al. | Dec 2000 | A |
| 6157898 | Marinelli | Dec 2000 | A |
| 6160254 | Zimmerman et al. | Dec 2000 | A |
| 6160551 | Naughton et al. | Dec 2000 | A |
| 6163021 | Mickelson | Dec 2000 | A |
| 6167356 | Squadron et al. | Dec 2000 | A |
| 6183425 | Whalen et al. | Feb 2001 | B1 |
| 6185491 | Gray et al. | Feb 2001 | B1 |
| 6196932 | Marsh et al. | Mar 2001 | B1 |
| 6204813 | Wadell | Mar 2001 | B1 |
| 6212585 | Chrabaszcz | Apr 2001 | B1 |
| 6218941 | Cromer et al. | Apr 2001 | B1 |
| 6226622 | Dabbiere | May 2001 | B1 |
| 6238338 | Deluca et al. | May 2001 | B1 |
| 6245002 | Belikov | Jun 2001 | B1 |
| 6249487 | Yano et al. | Jun 2001 | B1 |
| 6254513 | Takenaka et al. | Jul 2001 | B1 |
| 6255961 | Van Ryzin et al. | Jul 2001 | B1 |
| 6259892 | Helferich | Jul 2001 | B1 |
| 6263279 | Bianco et al. | Jul 2001 | B1 |
| 6266623 | Vock et al. | Jul 2001 | B1 |
| 6305221 | Hutchings | Oct 2001 | B1 |
| 6314094 | Boys | Nov 2001 | B1 |
| 6314326 | Fuchu | Nov 2001 | B1 |
| 6321091 | Holland | Nov 2001 | B1 |
| 6339706 | Tillgren et al. | Jan 2002 | B1 |
| 6353637 | Mansour et al. | Mar 2002 | B1 |
| 6356856 | Damen et al. | Mar 2002 | B1 |
| 6360597 | Hubbard, Jr. | Mar 2002 | B1 |
| 6380597 | Gudesen et al. | Apr 2002 | B1 |
| 6385473 | Haines et al. | May 2002 | B1 |
| 6393478 | Bahlmann | May 2002 | B1 |
| 6401085 | Gershman et al. | Jun 2002 | B1 |
| 6407750 | Gioscia et al. | Jun 2002 | B1 |
| 6409675 | Turcott | Jun 2002 | B1 |
| 6418330 | Lee | Jul 2002 | B1 |
| 6429810 | De Roche | Aug 2002 | B1 |
| 6436052 | Nikolic et al. | Aug 2002 | B1 |
| 6441747 | Khair et al. | Aug 2002 | B1 |
| 6456261 | Zhang | Sep 2002 | B1 |
| 6459881 | Hader et al. | Oct 2002 | B1 |
| 6469664 | Michaelson et al. | Oct 2002 | B1 |
| 6487663 | Jaisimha et al. | Nov 2002 | B1 |
| 6493652 | Ohlenbusch et al. | Dec 2002 | B1 |
| 6498994 | Vock et al. | Dec 2002 | B2 |
| 6501390 | Chainer et al. | Dec 2002 | B1 |
| 6501393 | Richards et al. | Dec 2002 | B1 |
| 6504483 | Richards et al. | Jan 2003 | B1 |
| 6504580 | Thompson et al. | Jan 2003 | B1 |
| 6510210 | Baughan | Jan 2003 | B1 |
| 6512478 | Chien | Jan 2003 | B1 |
| 6516284 | Flentov et al. | Feb 2003 | B2 |
| 6516466 | Jackson | Feb 2003 | B1 |
| 6526335 | Treyz et al. | Feb 2003 | B1 |
| 6527711 | Stivoric | Mar 2003 | B1 |
| 6529131 | Wentworth | Mar 2003 | B2 |
| 6531982 | White et al. | Mar 2003 | B1 |
| 6539336 | Vock et al. | Mar 2003 | B1 |
| 6559773 | Berry | May 2003 | B1 |
| 6563417 | Shaw | May 2003 | B1 |
| 6570526 | Noller et al. | May 2003 | B1 |
| 6571193 | Unuma et al. | May 2003 | B1 |
| 6595929 | Stivoric | Jul 2003 | B2 |
| 6600418 | Francis et al. | Jul 2003 | B2 |
| 6605038 | Teller | Aug 2003 | B1 |
| 6606556 | Curatolo et al. | Aug 2003 | B2 |
| 6611782 | Wooster | Aug 2003 | B1 |
| 6611789 | Darley | Aug 2003 | B1 |
| 6614349 | Proctor et al. | Sep 2003 | B1 |
| 6617962 | Horwitz et al. | Sep 2003 | B1 |
| 6619835 | Kita | Sep 2003 | B2 |
| 6633743 | Berlinsky | Oct 2003 | B1 |
| 6643608 | Hershey et al. | Nov 2003 | B1 |
| 6658247 | Saito | Dec 2003 | B1 |
| 6714121 | Moore | Mar 2004 | B1 |
| 6728531 | Lee et al. | Apr 2004 | B1 |
| 6735630 | Gelvin et al. | May 2004 | B1 |
| 6748902 | Boesch et al. | Jun 2004 | B1 |
| 6793607 | Neil | Sep 2004 | B2 |
| 6813586 | Vock et al. | Nov 2004 | B1 |
| 6823225 | Sass | Nov 2004 | B1 |
| 6825777 | Vock et al. | Nov 2004 | B2 |
| 6845398 | Galensky et al. | Jan 2005 | B1 |
| 6856934 | Vock et al. | Feb 2005 | B2 |
| 6883694 | Abelow | Apr 2005 | B2 |
| 6885971 | Vock et al. | Apr 2005 | B2 |
| 6898492 | de Leon et al. | May 2005 | B2 |
| 6900732 | Richards | May 2005 | B2 |
| 6901067 | Kalavade | May 2005 | B1 |
| 6959259 | Vock et al. | Oct 2005 | B2 |
| 6968179 | De Vries | Nov 2005 | B1 |
| 6973437 | Olewicz et al. | Dec 2005 | B1 |
| 7009517 | Wood | Mar 2006 | B2 |
| 7016687 | Holland | Mar 2006 | B1 |
| 7020508 | Stivoric et al. | Mar 2006 | B2 |
| 7030735 | Chen | Apr 2006 | B2 |
| 7035856 | Morimoto | Apr 2006 | B1 |
| 7042360 | Light et al. | May 2006 | B2 |
| 7054784 | Flentov et al. | May 2006 | B2 |
| 7064669 | Light et al. | Jun 2006 | B2 |
| 7065342 | Rolf | Jun 2006 | B1 |
| 7072789 | Vock et al. | Jul 2006 | B2 |
| 7092846 | Vock et al. | Aug 2006 | B2 |
| 7174277 | Vock et al. | Feb 2007 | B2 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7200517 | Darley et al. | Apr 2007 | B2 |
| 7219067 | McMullen | May 2007 | B1 |
| 7285090 | Stivoric et al. | Oct 2007 | B2 |
| 7307245 | Faries, Jr. et al. | Dec 2007 | B2 |
| 7440772 | White et al. | Oct 2008 | B2 |
| 7444353 | Chen et al. | Oct 2008 | B1 |
| 7486926 | White et al. | Feb 2009 | B2 |
| 7618345 | Corbalis et al. | Nov 2009 | B2 |
| 7627451 | Vock et al. | Dec 2009 | B2 |
| 7634228 | White et al. | Dec 2009 | B2 |
| 7670263 | Ellis et al. | Mar 2010 | B2 |
| 8480471 | Lutnick | Jul 2013 | B2 |
| 8758109 | Lutnick | Jun 2014 | B2 |
| 9675889 | Lai | Jun 2017 | B2 |
| 9737815 | Dhawan | Aug 2017 | B2 |
| 20010049470 | Mault et al. | Dec 2001 | A1 |
| 20010049890 | Hirsch et al. | Dec 2001 | A1 |
| 20020010759 | Hitson et al. | Jan 2002 | A1 |
| 20020046084 | Steele et al. | Apr 2002 | A1 |
| 20020057340 | Fernandez et al. | May 2002 | A1 |
| 20020070862 | Francis et al. | Jun 2002 | A1 |
| 20020077784 | Vock et al. | Jun 2002 | A1 |
| 20020107033 | Kim | Aug 2002 | A1 |
| 20020121975 | Struble et al. | Sep 2002 | A1 |
| 20020124017 | Mault | Sep 2002 | A1 |
| 20020164973 | Janik et al. | Nov 2002 | A1 |
| 20030008659 | Waters et al. | Jan 2003 | A1 |
| 20030014210 | Vock et al. | Jan 2003 | A1 |
| 20030060211 | Chem et al. | Mar 2003 | A1 |
| 20030065805 | Barnes | Apr 2003 | A1 |
| 20030093248 | Vock et al. | May 2003 | A1 |
| 20030163287 | Volk et al. | Aug 2003 | A1 |
| 20030208113 | Mault et al. | Nov 2003 | A1 |
| 20040104845 | McCarthy | Jun 2004 | A1 |
| 20040203600 | McCorkle et al. | Oct 2004 | A1 |
| 20050177929 | Greenwald et al. | Aug 2005 | A1 |
| 20060030335 | Zellner | Feb 2006 | A1 |
| 20060152377 | Beebe et al. | Jul 2006 | A1 |
| 20060293103 | Mendelsohn | Dec 2006 | A1 |
| 20120179278 | Riley | Jul 2012 | A1 |
| 20160067615 | Lai | Mar 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 10325805 | Jan 2005 | DE |
| 0336782 | Oct 1989 | EP |
| 0744839 | Nov 1996 | EP |
| 0898378 | Feb 1999 | EP |
| 0917893 | May 1999 | EP |
| 0918408 | May 1999 | EP |
| 1292217 | Nov 2005 | EP |
| 1292218 | Apr 2006 | EP |
| 1567238 | May 1980 | GB |
| 2137363 | Oct 1984 | GB |
| 03-152469 | Jun 1991 | JP |
| 2000-122044 | Apr 2000 | JP |
| 2001-321202 | Nov 2001 | JP |
| 2002-101908 | Apr 2002 | JP |
| 9514430 | Jun 1995 | WO |
| 9806466 | Dec 1998 | WO |
| 9854581 | Dec 1998 | WO |
| 0051259 | Aug 2000 | WO |
| 00054462 | Sep 2000 | WO |
| 00078170 | Dec 2000 | WO |
| 0101706 | Apr 2001 | WO |
| Entry |
|---|
| U.S. Appl. No. 10/842,947, Office Action dated Jun. 30, 2005. |
| U.S. Appl. No. 10/842,947, Response to Office Action dated Jun. 30, 2005. |
| U.S. Appl. No. 10/842,947, Notice of Allowance dated Feb. 9, 2006. |
| U.S. Appl. No. 10/921,743; Office Action dated Mar. 4, 2005. |
| U.S. Appl. No. 10/921,743; Response to Office Action dated Mar. 4, 2005. |
| U.S. Appl. No. 10/921,743; Office Action dated May 26, 2005. |
| U.S. Appl. No. 10/921,743; Response to Office Action dated May 26, 2005. |
| U.S. Appl. No. 10/921,743; Office Action dated Sep. 13, 2005. |
| U.S. Appl. No. 10/921,743; Advisory dated Nov. 25, 2005. |
| U.S. Appl. No. 10/921,743; Response to Office Action dated Sep. 13, 2005 and Advisory dated Nov. 25, 2005. |
| U.S. Appl. No. 10/921,743; Notice of Allowance; dated Feb. 16, 2006. |
| U.S. Appl. No. 10/950,897, Notice of Allowance dated Feb. 13, 2005. |
| U.S. Appl. No. 10/950,897, Office Action dated Mar. 7, 2005. |
| U.S. Appl. No. 10/950,897, Response to Office Action dated Mar. 7, 2005. |
| U.S. Appl. No. 10/950,897, Office Action dated Jun. 23, 2005. |
| U.S. Appl. No. 10/950,897, Response to Office Action dated Jun. 23, 2005. |
| U.S. Appl. No. 10/950,897, Office Action dated Sep. 9, 2005. |
| U.S. Appl. No. 10/950,897, Response to Office Action dated Sep. 9, 2005. |
| U.S. Appl. No. 10/950,897, Office Action dated Nov. 25, 2005. |
| U.S. Appl. No. 10/950,897, Response to Office Action dated Nov. 25, 2005. |
| U.S. Appl. No. 10/950,897, Amendment to Notice of Allowance dated Dec. 13, 2005. |
| U.S. Appl. No. 11/221,029; Preliminary Amendment dated Aug. 22, 2006. |
| U.S. Appl. No. 11/221,029; Office Action dated Sep. 8, 2006. |
| U.S. Appl. No. 11/221,029; Response to Office Action dated Sep. 8, 2006. |
| U.S. Appl. No. 11/221,029; Notice of Allowance; dated Oct. 3, 2006. |
| U.S. Appl. No. 11/252,576; Notice of Allowance; dated Dec. 11, 2007. |
| U.S. Appl. No. 09/089,232, Notice of Appeal mailed Nov. 7, 2001. |
| U.S. Appl. No. 09/089,232, Appeal Brief mailed Jan. 2, 2002. |
| U.S. Appl. No. 09/089,232, Office Action dated Apr. 26, 2002. |
| U.S. Appl. No. 09/089,232, Appeal Brief mailed Jul. 26, 2002. |
| U.S. Appl. No. 09/089,232, Notice of Allowance dated Oct. 2, 2002. |
| U.S. Appl. No. 09/089,232, Comments on Allowance dated Oct. 16, 2002. |
| U.S. Appl. No. 09/089,232, Office Action dated Jan. 27, 2003. |
| U.S. Appl. No. 09/698,659, Office Action dated Mar. 19, 2002. |
| U.S. Appl. No. 09/698,659, Response to Office Action dated Mar. 19, 2002. |
| U.S. Appl. No. 09/698,659, Office Action dated Nov. 21, 2002. |
| U.S. Appl. No. 09/698,659, Response to Office Action dated Nov. 21, 2002. |
| U.S. Appl. No. 09/698,659, Notice of Allowance dated Apr. 9, 2003. |
| U.S. Appl. No. 09/848,445, Preliminary Amendment dated Dec. 5, 2001. |
| U.S. Appl. No. 09/848,445, Office Action dated Dec. 5, 2003. |
| U.S. Appl. No. 09/848,445, Response to Office Action dated Dec. 5, 2003. |
| U.S. Appl. No. 09/848,445, Office Action dated May 6, 2004. |
| U.S. Appl. No. 09/848,445, Response to Office Action (Rule 116) dated May 6, 2004. |
| U.S. Appl. No. 09/886,578, Preliminary Amendment dated Jun. 21, 2001. |
| U.S. Appl. No. 09/886,578, Office Action dated Nov. 8, 2001. |
| U.S. Appl. No. 09/886,578, Response to Office Action dated Nov. 8, 2001. |
| U.S. Appl. No. 09/886,578, Office Action dated Jun. 5, 2002. |
| U.S. Appl. No. 09/886,578, Response to Office Action dated Jun. 5, 2002. |
| U.S. Appl. No. 09/886,578, Notice of Allowance dated Sep. 9, 2002. |
| U.S. Appl. No. 09/992,966, Office Action dated Feb. 3, 2003. |
| U.S. Appl. No. 09/992,966, Response to Office Action dated Feb. 3, 2003. |
| U.S. Appl. No. 09/992,966, Office Action dated Mar. 28, 2002. |
| U.S. Appl. No. 09/992,966, Response to Office Action dated Mar. 28, 2002. |
| U.S. Appl. No. 09/992,966, Office Action dated Jul. 18, 2003. |
| U.S. Appl. No. 09/992,966, Response to Office Action dated Jul. 18, 2003. |
| U.S. Appl. No. 09/992,966, Examiner Summary dated Oct. 27, 2003. |
| U.S. Appl. No. 09/992,966, Notice of Allowance dated Apr. 15, 2004. |
| U.S. Appl. No. 09/992,966, Office Action dated Jan. 6, 2004. |
| U.S. Appl. No. 09/992,966, Response to Office Action dated Jan. 6, 2004. |
| U.S. Appl. No. 09/992,966, Notice of Allowance dated Sep. 3, 2004. |
| U.S. Appl. No. 10/234,660, Office Action dated Mar. 31, 2003. |
| U.S. Appl. No. 10/234,660, Response to Office Action dated Mar. 31, 2003. |
| U.S. Appl. No. 10/234,660, Final Office Action dated Oct. 31, 2003. |
| U.S. Appl. No. 10/234,660, filed Dec. 23, 2003 Response to Office Action dated Oct. 31, 2003. |
| U.S. Appl. No. 10/234,660; Advisory Action dated Jan. 27, 2004. |
| U.S. Appl. No. 10/234,660; Appeal Brief filed Jun. 14, 2004. |
| U.S. Appl. No. 10/234,660; Amendment filed Jul. 20, 2004. |
| U.S. Appl. No. 10/234,660; Marked up Claims by USPTO dated Jul. 28, 2004. |
| U.S. Appl. No. 10/234,660; Notice of Allowance; dated Aug. 2, 2004. |
| U.S. Appl. No. 10/297,270 Office Action dated Jul. 29, 2004. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Jul. 29, 2004. |
| U.S. Appl. No. 10/297,270 Office Action dated Dec. 13, 2004. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Dec. 13, 2004. |
| U.S. Appl. No. 10/297,270 Request Deletion of Named Inventors Pursuant to 37 CFR § 1.63 (d)(2) received by the Patent Office on Oct. 4, 2002. |
| U.S. Appl. No. 10/297,270 Office Action dated Jul. 13, 2005. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Jul. 13, 2005. |
| Wysocki, Jr., Staff Reporter, “Do Devices Measuring Body Signs Appeal to the Sick or Healthy”, Pittsburgh, US., dated before Mar. 18, 2003. |
| EP989288543 Supplementary European Search Report; dated Feb. 18, 2002. |
| PCT/US98/11268 International Search Report dated Jan. 11, 1999. |
| PCT/US00/18237 International Search Report; dated Oct. 17, 2000. |
| PCT/US01/51620 International Search Report dated Sep. 25, 2002. |
| PCT/US00/18237 International Preliminary Examination Report; dated Oct. 9, 2003. |
| Civil Action No. 05-CV-02323; Complaint, Nov. 16, 2005. |
| Civil Action No. 06-CV-01100-WDM-PAC, Complaint, Jun. 8, 2006. |
| Civil Action No. 06-CV-01100-WDM-PAC, Defendants Polar Electro Inc.'s and Polar Electra Oy's Answer and Affirmative Defenses: Polar Electra Inc.'s Counterclaim and Demand for Jury Trial, Jun. 29, 2006. |
| Civil Action No. 06-CV-01447-MSK-BNB, Complaint, Jul. 26, 2006. |
| Civil Action No. 06-CV-01447 MSK-BNB, First Amended Complaint; Aug. 16, 2006. |
| Civil Action No. 06-CV-01447-MSK-BNB, Answer, Affirmative Defenses, Counterclaim, and Demand for Jury Trial, Garmin; Sep. 26, 2006. |
| Civil Action No. 06-CV-01447-MSK-BNB; Garmin Disclosure Statement; Sep. 26, 2006. |
| Civil Action No. 06-CV-01447 MSK-BNB, Answer, Affirmative Defenses, Counterclaims and Demand for Jury Trial, Timex; Sep. 26, 2006. |
| Civil Action No. 06-CV-01447-MSK-BNB; Timex Disclosure Statement; Sep. 26, 2006. |
| Civil Action No. 06-CV-01447-MSK-BNB: PhatRat Technology, Inc.'s Supplemental Answers and Objections to Defendant, Timex Corporation's Interrogatories Nos. 1, 2, 5, 7-11, 13 and 15; Feb. 12, 2007. |
| Civil Action No. 06-CV-02122-REB-MJW, Complaint, Oct. 24, 2006. |
| Civil Action No. 06-CV-02122-REB-MJW, Apple Computer, Inc.'s Answer to Complaint and Counterclaims, Jan. 22, 2007. |
| Civil Action No. 07-CV-00078-MSK-BNB, Complaint, Jan. 12, 2007. |
| Civil Action No. 07-CV-00078-MSK-BNB, Answer, Feb. 9, 2007. |
| Civil Action No. 07-GV-00238-REB-PAC, Complaint, Feb. 1, 2007. |
| Civil Action No. 07-CV-00238-REB, Apple Inc.'s Answer to Complaint, Counterclaims and Jury Demand, Mar. 19, 2007. |
| *Civil Action No. 07-CV-00238; Nike Inc.'s Answer, Affirmative Defenses to First Complaint, Mar. 19, 2007. |
| U.S. Appl. No. 08/764,758, Office Action dated Aug. 21, 1997. |
| U.S. Appl. No. 08/764,758, Response to Office Action dated Aug. 21, 1997. |
| U.S. Appl. No. 08/764,758, Office Action dated Dec. 15, 1998. |
| U.S. Appl. No. 08/764,758, Response to Office Action dated Dec. 15, 1998. |
| U.S. Appl. No. 08/764,758, Office Action dated May 8, 1998. |
| U.S. Appl. No. 08/764,758, Response to Office Action dated May 8, 1998, filed Oct. 8, 1998. |
| U.S. Appl. No. 08/764,758, Notice of Allowance dated Jun. 1, 1999. |
| U.S. Appl. No. 08/764,758, Advisory Action dated Apr. 29, 1999. |
| U.S. Appl. No. 08/867,083, Office Action dated Apr. 8, 1999. |
| U.S. Appl. No. 08/764,758, Rule 116 Amendment filed Apr. 8, 1999. |
| U.S. Appl. No. 08/764,758, Rule 116 Amendment filed May 13, 1999. |
| U.S. Appl. No. 08/867,083, Response to Office Action dated Apr. 8, 1999. |
| U.S. Appl. No. 08/867,083, Supp. Response to Office Action dated Apr. 8, 1999. |
| U.S. Appl. No. 08/867,083, Final Office Action dated Jan. 3, 2000. |
| U.S. Appl. No. 08/867,083, Notice of Appeal dated Jan. 3, 2000. |
| U.S. Appl. No. 08/867,083, Notice of Appeal Response to Office Action dated Jan. 3, 2000. |
| U.S. Appl. No. 08/867,083, Advisory Action dated Mar. 14, 2000. |
| U.S. Appl. No. 08/867,083 Office Action dated Jun. 26, 2000. |
| U.S. Appl. No. 08/867,083 Amendment response to Office Action dated Jun. 26, 2000. |
| U.S. Appl. No. 08/867,083 Notice of Allowance, dated Feb. 6, 2001. |
| U.S. Appl. No. 09/089,232, Information Disclosure Statement dated Oct. 23, 1998. |
| U.S. Appl. No. 09/089,232, Office Action dated Nov. 27, 1998. |
| U.S. Appl. No. 09/089,232, Office Action dated May 30, 2000. |
| U.S. Appl. No. 09/089,232, Preliminary Amendment response to Office Action dated May 30, 2000. |
| U.S. Appl. No. 09/089,232, Office Action dated Dec. 19, 2000. |
| U.S. Appl. No. 09/089,232, Response to Office Action dated Dec. 19, 2000. |
| U.S. Appl. No. 09/089,232, Office Action dated Aug. 8, 2001. |
| U.S. Appl. No. 09/089,232, Notice of Appeal mailed Nov. 5, 2001. |
| U.S. Appl. No. 11/358,508, Preliminary Amendment dated Mar. 30, 2006. |
| U.S. Appl. No. 11/358,508, Preliminary Amendment dated May 30, 2006. |
| U.S. Appl. No. 11/358,508, Preliminary Amendment dated Jul. 26, 2006. |
| U.S. Appl. No. 11/358,508, Office Action dated Aug. 14, 2006. |
| U.S. Appl. No. 11/358,508, Response to Office Action dated Aug. 14, 2006. |
| U.S. Appl. No. 11/358,508. Notice of Non Compliance Amendment dated Sep. 12, 2006. |
| U.S. Appl. No. 11/358,508, Response to Notice dated Sep. 12, 2006. |
| U.S. Appl. No. 11/358,508, Notice of Allowability & Interview Summary dated Oct. 18, 2006. |
| U.S. Appl. No. 11/358,508, Rule 312 Amendment dated Oct. 24, 2006. |
| U.S. Appl. No. 11,434,588: Office Action dated Jan. 31, 2007. |
| U.S. Appl. No. 11/434,588; Response to Office Action dated Jan. 31, 2007. |
| U.S. Appl. No. 11/434,588; Notice of Allowance; dated Jul. 11, 2007. |
| U.S. Appl. No. 11/434,588; Notice of Allowance; dated Nov. 6, 2007. |
| U.S. Appl. No. 11/484,199 Preliminary Amendment; dated Sep. 7, 2006. |
| U.S. Appl. No. 11/484,199 Notice of Allowance and Examiner Interview Summary; dated Oct. 6, 2006. |
| U.S. Appl. No. 11/598,410, Office Action dated Jun. 13, 2007. |
| U.S. Appl. No. 11/598,410 Response to Office Action dated Jun. 13, 2007. |
| U.S. Appl. No. 11/598,410, Notice of Allowability dated Sep. 26, 2007. |
| U.S. Appl. No. 11/646,768, Office Action dated May 7, 2007. |
| U.S. Appl. No. 11/646,768, Response to Office Action dated May 7, 2007. |
| U.S. Appl. No. 11/646,768, Office Action dated Oct. 29, 2007. |
| U.S. Appl. No. 11/646,768, Response to Office Action dated Oct. 29, 2007. |
| U.S. Appl. No. 11/646,768; Notice of Allowance; dated Jan. 18, 2008. |
| U.S. Appl. No. 11/747,081; Office Action dated Jan. 24, 2008. |
| Office Action dated Mar. 26, 2009, issued in U.S. Appl. No. 11/746,863, filed May 10, 2007. |
| U.S. Appl. No. 10/297,270 Office Action dated Feb. 9, 2006. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Feb. 9, 2006. |
| U.S. Appl. No. 10/297,270 Office Action dated Sep. 25, 2006. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Sep. 25, 2006. |
| U.S. Appl. No. 10/297,270 Office Action dated Jan. 11, 2007. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Jan. 11, 2007. |
| U.S. Appl. No. 10/297,270 Office Action dated Jul. 26, 2007. |
| U.S. Appl. No. 10/297,270 Response to Office Action dated Jul. 26, 2007. |
| U.S. Appl. No. 10/601,208 Preliminary Amendment, dated Jun. 20, 2003. |
| U.S. Appl. No. 10/601,208 Office Action dated Jun. 15, 2004. |
| U.S. Appl. No. 10/601,208 Response to Office Action dated Jun. 15, 2004. |
| U.S. Appl. No. 10/601,208 Office Action dated Aug. 26, 2004. |
| U.S. Appl. No. 10/601,208 Response to Office Action dated Aug. 26, 2004. |
| U.S. Appl. No. 10/601,208 Second Response to Office Action dated Aug. 26, 2004. |
| U.S. Appl. No. 10/601,208 Office Action dated May 11, 2005. |
| U.S. Appl. No. 10/601,208 Response to Office Action dated May 11, 2005. |
| U.S. Appl. No. 10/601,208 Office Action dated Feb. 15, 2006. |
| U.S. Appl. No. 10/601,208 Response to Office Action dated Feb. 15, 2006. |
| U.S. Appl. No. 10/601,208 Office Action dated Sep. 26, 2006. |
| U.S. Appl. No. 10/601,208 Response to Office Action dated Sep. 26, 2006. |
| U.S. Appl. No. 10/601,208 Notice of Allowance dated Dec. 8, 2006. |
| U.S. Appl. No. 10/842,947, Preliminary Amendment dated May 11, 2004. |
| U.S. Appl. No. 10/842,947, Office Action dated Nov. 30, 2004. |
| U.S. Appl. No. 10/842,947, Response to Office Action dated Nov. 30, 2004. |
| “Briefs: Sierra Wireless . . . ” NetworkWorld vol. 16, No. 34, p. 27, Aug. 23, 1999. |
| “Cellular for Notebook PCs.” CIO vol. 13, No. 1, Section 1, p. 90, Oct. 1, 1999. |
| “Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.0.1 Release 1997)” pp. 1-56, Aug. 1998. |
| “Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.1.0 Release 1997)” pp. 1-42, Oct. 1998. |
| “Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.2.0 Release 1997)” pp. 1-42, May 1999. |
| “Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.3.0 Release 1997)” pp. 1-42, Jul. 1999. |
| “Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 7.0.0 Release 1997)” pp. 1-41, Jul. 1999. |
| GPS Locator for Children, Klass Kids Foundation Jul. 15, 2004. |
| Mark of Fitness Flyer, “High Quality, Self-Taking Blood Pressure Monitors”, four pages, Shrewsbury, NJ, US., dated before Mar. 18, 2003. |
| Nokia Quick Guide, Accessories Guide, pp. 1-31, 1999. |
| Nokia 9110i User's Manual, pp. 1-190, 1999. |
| “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.” IEEE Std 802.11-1997, pp. 1-445. |
| Qualcomm QCP—1960TM, Sprint PCS User Guide, pp. 1-76, Apr. 1999. |
| “Sierra Wireless Announces First Cellular Network Interface Card for Notebook PCs; The AirCard 300 for Windows Changes the Way Notebook PC Users Make Wireless Connections.” Business Wire, Jun. 21, 1999 (http://findarticles.com/p/articles/mi_m0EIN/is_1999_June_21/ai_54937451/), retrieved Aug. 5, 2009. |
| “Specification of the Bluetooth System, vol. 1.” pp. 1-1080, Nov. 29, 1999. |
| “Specification of the Bluetooth System, vol. 2.” pp. 1-438, Nov. 29, 1999. |
| Samsung Model SCH-3500, Sprint PCS User Guide, pp. 1-108, 1999. |
| StarTAC, Sprint PCS User Guide, pp. 1-118, Mar. 1999. |
| Visteon: for Your Listening Pleasure—Any Music, Any Time, Anywhere (http://www2.prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/01-05-2000/0001107812&DATE), originally retrieved Jan. 5, 2000. |
| Webster's II New Riverside University Dictionary, 1988, The Riverside Publishing Company, p. 1138. |
| No author listed, “Ever Forget to Bring Your Cell Phone or Keys?”, Catalog Page, PI Manufacturing Corp, 20732, 4 Currier Rd., Walnut, CA 91789, Home Office Accessory, Catalog Nos. TA-100N; TA-100M; TA-100F, US. |
| No author listed, The GPS Connection, Popular Mechanics, Feb. 2001. p. 65. |
| No author listed, WarmMark Time Temperature Indicators, www.coldice.com/wannmark.sub.-temperature.sub.-indicators.html, Cold Ice., Inc., Nov. 20, 2000. |
| No author listed, Wireless Temperature Monitor [online], Nov. 20, 2000, [retrieved on Aug. 9, 2004], retrieved from the Internet: URL: http://www.echo-on.net/mob. |
| No author listed, “Your Next . . . ”, Newsweek, Jun. 25, 2001, p. 52 US. |
| Unattributed, 3M MonitorMark Indicator Data Sheet [online), [retrieved on Aug. 9, 2004], retrieved from the Internet: URL: http://www.3m.com/us/healthcare/medicalspecialties/monitor/products.html; 4 pages. |
| Cai et al. “General Packet Radio Service in GSM.” IEEE Communications Magazine, Oct. 1997, pp. 122-131. |
| Cole, George, “The Little Label with an Explosion of Applications”, Financial Times, Ltd., 2002, pp. 1-3. |
| Deem, “Fast Forward Go for a Ride on the World's Fastest Sailboat”, Popular Mechanics, www.populannechanics.com, Feb. 2001, pp. 1-2. |
| Desmarais et al., “How to select and use the right temperature,” www.sensorsmag.com, Jan. 2001, pp. 30-36. |
| Desmarais, “Solutions in Hand”, BEI Technologies, Inc., www.sensormag.com, Jan. 2001, pp. 1-2. |
| Jackson et al. “Weighing Scales Based on Low-Power Strain-Gauge Circuits”, NASA Tech Briefs, Jun. 2001, p. 49 US. |
| Janssens et al., “Columbus: A Novel Sensor System for Domestic Washing Machines”, Sensors Magazine Online, Jun. 2002, pp. 1-9. |
| Gerhauser et al., The ‘Electronic Shoe’ for Jogging, Sports and Reconvalescene, 1989 IEEE. |
| Henkel, Research & Developments, Sensors, Nov. 2000, p. 18. |
| Licking, Special Report: E-Health, “This is the Future of Medicine”, Business Week E.Biz, Dec. 11, 2000, p. 77 and 78 US. |
| Lind et al. “The Network Vehicle—A Glimpse into the Future of Mobile Multi-Media.” IEEE, pp. 121-1-121-8, 1998. |
| Li-Ron, Tomorrow's Cures, Health & Fitness Special Section Online, Newsweek, Dec. 10, 2001, pp. 3-10. |
| Martella, Product News, “Temperature Monitoring System”, Nov. 2000, p. 77. |
| Nobbe, “Olympic Athletes Get a Boost from Technology”, Machine Design, vol. 60, No. 19, Aug. 25, 1988. |
| Orubeondo, “Trim AirCard 300 Eases Power Demands.” InfoWorld vol. 21, Issue 48, pp. 46 & 50, Nov. 29, 1999. |
| Paradiso et al., Design and Implementation of Expressive Footwear, May 12, 2000, IBM Systems Journal, vol. 39, Nos. 3&4, pp. 511-529. |
| Paradiso, et al. “Instrumented Footwear for Interactive Dance” Version 1.1, Presented at the XII Colloquium on Musical Informatics, Gorizia, Italy, Sep. 24-26, 1998, pp. 1-4. |
| Ray, J., Pedobarographic Gait Analysis on Male Subjects, IEEE 1996, pp. 25-27. |
| Sagawa et al., Classification of Human Moving Patterns Using Air Pressure and Acceleration, 1998, IEEE, pp. 1214-1219. |
| Sagawa et al., Non-Restricted Measurement of Walking Distance, Oct. 8-11, 2000, IEEE International Conference on Systems, Man, and Cybernetics, vol. 3, pp. 1847-1852. |
| Sellers. Gear to Go, Mitch Mandel Photography, Mar. 2001, pp. 61-62. |
| Sharp, A Sense of the Real World, www.idsystems.com/reader/2000_09/sens0900.htm, Sep. 2000, 4 pages. |
| Skaloud et al., DGPS-Calibrated Accelerometric System for Dynamic Sports Events, Sep. 19-22, 2000, ION GPS 2000. |
| Smith et al., “Flexible and Survivable Non-Volatile Memory Data Recorder”, AFRL Technology Horizons, Dec. 2000, p. 26. |
| Number | Date | Country | |
|---|---|---|---|
| 20150306505 A1 | Oct 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60323601 | Sep 2001 | US | |
| 60285032 | Apr 2001 | US | |
| 60261359 | Jan 2001 | US | |
| 60259271 | Dec 2000 | US | |
| 60257386 | Dec 2000 | US | |
| 60256069 | Dec 2000 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12428186 | Apr 2009 | US |
| Child | 13761829 | US | |
| Parent | 11647042 | Dec 2006 | US |
| Child | 12428186 | US | |
| Parent | 10601208 | Jun 2003 | US |
| Child | 11647042 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14222855 | Mar 2014 | US |
| Child | 14736218 | US | |
| Parent | 13761829 | Feb 2013 | US |
| Child | 14222855 | US | |
| Parent | 10297270 | US | |
| Child | 10601208 | US |
