The present invention relates to the field of locating systems, and more particularly to a monitoring and locating system implementing secure communications between the monitoring device and the monitored unit to lessen the ability of a third party locating the object, e.g., person, automobile, attached to the monitored unit.
There are numerous methods and systems for locating moveable objects such as automobiles, pets and people. One such system for locating moveable objects, such as a person, utilizes a Global Positioning Sensor (GPS) locator device that may be attached to the object, e.g., carried by the person. The GPS locator device may receive and triangulate signals from each of three or more geostationary satellites and determine the geographical coordinates of the device's current location. The geographical coordinates may be made available to an individual via a web site by the GPS locator device transmitting the GPS coordinates to either a device monitoring the GPS locator device or to a centralized location. However, GPS locator devices may not be able to receive and triangulate signals because the signals may be blocked or scattered by a variety of objects such as dense tree canopies, heavy clouds, metal roofs, layers of rock, concrete or canyon walls. For example, GPS locator devices may not be able to receive and triangulate signals in or around buildings or homes or in the woods with lots of vegetation. Hence, GPS may be of no assistance in locating an object in certain environments as discussed above. Further, in order for the GPS locator device to include both the capabilities of determining the geographical coordinates of the device's current location and transmitting that information to another device or centralized location, the GPS locator device becomes bulky and costly to implement.
One system that does not utilize GPS to locate objects, such as children, uses a monitoring device configured to monitor the position of a child by detecting the signal strength of a radio frequency carrier from a transmitter attached to the child. If the signal of the radio frequency carrier is too weak, the child is too far away from the adult who has the monitoring device. When this happens, the adult is informed that the child has wandered too far away through the use of an audio tone or through the use of vibrations coming from the device. Once the adult is notified that the child is too far away, the device also has a locating display for indicating the relative direction of the child with respect to the adult. However, since the transmitter worn by the child simply transmits a signal with no unique identification code at a particular frequency, a third party, e.g., potential abductor, may be able to intercept the signal and with a similar monitoring device track the child. Furthermore, since the transmitter worn by the child simply transmits a signal with no unique identification code at a particular frequency, a third party, e.g., potential abductor, may be able to transmit false information to the monitoring device.
Therefore, there is a need in the art for a monitoring and locating system that does not rely upon GPS and provides secure communication making it more difficult for a third party, e.g., potential abductor, potential thief, to be able to locate the object, e.g., child, automobile, as well as transmit false information to the monitoring device and/or monitored unit.
The problems outlined above may at least in part be solved in some embodiments of the present invention by the monitoring device transmitting a seed of an algorithm and a time synchronization to the monitored unit which will be used in conjunction with an algorithm, e.g., frequency hopping table, stored in both the monitoring device and the monitored unit, to communicate at a particular time and frequency between one another. Time synchronization may refer to the time the monitoring device transmits the seed. Each subsequent transmission from the monitored unit to the monitoring device is in a specific time slot, synchronized with the monitoring device and at a frequency that changes pseudo-randomly. A response from the monitoring device resynchronizes the time slot. A seed may refer to a multiple bit number, e.g., 16-bit number, used in conjunction with these time slots to select a particular frequency stored in the algorithm, e.g., frequency hopping table. Hence, the frequency of each communication between the monitoring device and the monitored unit changes according to the algorithm stored in both the monitoring device and the monitored unit thereby making it more difficult for a third party, e.g., potential abductor, potential thief, to be able to locate the object, e.g., child, automobile, as well as transmit false information to the monitoring device and/or monitored unit.
In one embodiment of the present invention, a method for monitoring and locating an object, e.g., person, automobile, may comprise the step of activating a unit to be monitored by a monitoring unit. The method may further comprise receiving a first packet of data form the monitored unit where the first packet of data comprises an identification. The method may further comprise transmitting a seed of an algorithm to the monitored unit if the identification associated with the first packet of data is a valid identification. The method may further comprise measuring a signal strength of a second packet of data if the second packet of data was received at an expected frequency from the monitored unit. The measured signal strength of the second packet of data indicates an approximate distance the monitored unit is located from the monitoring device.
In another embodiment of the present invention, a system may comprise a monitored unit attached to an object. The monitored unit may comprise a memory unit operable for storing a computer program product operable for determining if the monitored unit has been tampered with. The monitored unit may further comprise a processor coupled to the memory unit. The monitored unit may further comprise an emitter coupled to the processor where the emitter is configured to emit infrared signals to the skin of an individual. The monitored unit may further comprise a detector coupled to the processor where the detector is configured to receive reflections of the emitted infrared signals from the skin. The processor, responsive to the computer program, may comprise circuitry operable for determining if an intensity of the reflections of the emitted infrared signals is less than a threshold. The processor may further comprise circuitry operable for transmitting an indication that the monitored unit has been tampered with if the intensity of the reflections of the emitted infrared signals is less than the threshold.
The foregoing has outlined rather broadly the features and technical advantages of one or more embodiments of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention.
A better understanding of the present invention can be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
FIG. 1—System for Monitoring and Locating an Object
Returning to
Referring to
Returning to
Digital compass 105 may be used in the “locate mode” of operation, as discussed in further detail below in conjunction with
Battery 108 may supply the necessary operating power for the circuitry and components of monitoring device 101. Battery 108 may be a standard carbon or lithium battery, or a rechargeable type battery such as nickel metal hydride (NiMH), nickel cadmium (NiCAD) or lithium-ion.
Monitoring device 101 may comprise input/output devices such as button(s)/switch(es) 109, LEDs 110, beeper 111, vibrator 112, and/or display 106. Data may be inputted to monitoring device 101 through button(s)/switch(es) 109, e.g., inputting a maximum distance the monitored unit 102 should be located from monitoring device 101 as discussed below in conjunction with
Transmitter/receiver circuit 113 may be configured to transmit information to and receive information from monitored unit 102. Upon activating unit 102 as discussed above, a “seed”, a unique identification assigned to unit 102, as well as an identification used to identify monitoring device 101, may be transmitted to monitored unit 102. Further, upon activating unit 102, a “time synchronization” may be transmitted to unit 102. “Time synchronization” may refer to the time that monitoring device 101 transmitted the above information. Each subsequent transmission from monitored unit 102 to monitoring device 101 is a specific time slot synchronized with monitoring device 101. A response from monitoring device 101 resynchronizes the time slot. A “seed” may refer to a multiple bit number, e.g., 16-bit number, used in conjunction with these time slots to select a particular frequency stored in an algorithm, e.g., frequency hopping table. The algorithm may be stored in both monitoring device 101 and monitored unit 102. As discussed below, the algorithm may be stored in a memory unit in monitored unit 102 prior to a customer purchasing monitored unit 102. In one embodiment, the frequencies selected may correspond to frequencies between 902–928 MHz in the license-free ISM band. In one embodiment, system 100 may be configured to implement frequency hopping spread spectrum in the license-free ISM band by selecting 50 hopping frequencies in the algorithm using the seed and time slots as discussed above. It is noted that frequency hopping spread spectrum is known in the art and therefore will not be described in detail for sake of brevity.
In one embodiment, monitoring device 101 may be configured to coordinate multiple monitored units 102 that use the same algorithms, e.g., frequency hop tables, without accidentally activating a different monitored unit 102 than the one intended by ensuring these units 102 are time shifted from each other. The coordination may be accomplished via software stored in memory 107.
Antenna switch 114 may be configured to activate directional antenna 115 to receive transmitted information when monitoring device 101 operates in “locate mode.” Locate mode may refer to the mode of operation in which monitored unit 102 increases its rate of transmissions to aid in monitoring device 101 tracking and determining the approximate location of monitored unit 102. For example, the locate mode of operation may be enacted when monitored unit 102 is located beyond a pre-determined maximum distance from monitoring device 101 or when monitored unit 102 has been tampered with as discussed in conjunction with
Antenna switch 110 may also be configured to activate an omni directional antenna 116 when monitoring device 101 operates in “monitoring mode.” Monitoring mode may refer to the mode of operation in which monitoring device 101 monitors the approximate distance unit 102 is located from monitoring device 101. Omni-directional antennas are well known to persons of ordinary skill in the art and will therefore not be discussed in further detail for the sake of brevity.
It is noted that other features of monitoring device 101 will be discussed further below in conjunction with
Returning to
Activation/deactivation sensor 118 may be configured to receive a signal to activate or deactivate monitored unit 102 from activation/deactivation unit 104. In one embodiment, activation/deactivation sensor 118 may include an infrared detector and emitter configured to detect and transmit signals in the infrared band from and to monitoring device 101, respectively.
Processor 117 may be configured similarly as processor 103. In one embodiment, memory 119, e.g., non-volatile memory, may store a program for transmitting packets of data at an increased rate during the “locate mode” of operation as described further below in conjunction with
Battery 120 may supply the necessary operating power for the circuitry and components of monitored unit 102. Battery 120 may be a standard carbon or lithium battery, or a rechargeable type battery such as nickel metal hydride (NiMH), nickel cadmium (NiCAD) or lithium-ion.
Monitored unit 102 may comprise input/output devices such as LEDs 121, beeper 122 and button(s)/switch(es) 123. Data may be inputted to monitored unit 102 through button(s)/switch(es) 123. Output may be received by the user of monitored unit 102 through LEDs 121 and beeper 122, e.g., outputting an indication that monitored unit 102 has been tampered with as discussed further below in conjunction with
Tamper sensor 124 may be configured to detect monitored unit 102 being tampered with such as removing monitored unit 102 from an object, e.g., wrist of a child. A more detail description of detecting the tampering of monitored unit 102 is described further below in conjunction with
Transmitter/receiver circuit 125 may be configured similarly as transmitter/receiver circuit 113. Transmitter/receiver circuit 125 may be configured to transmit information to and receive information from monitoring device 101 via omni directional antenna 126. Omni directional antenna 126 is configured similarly as omni directional antenna 116.
As stated in the Background Information section, there is a need in the art for a monitoring and locating system that makes it more difficult for a third party, e.g., potential abductor, potential thief, to be able to locate the object, e.g., child, automobile, as well as transmit false information to the monitoring device and/or monitored unit.
FIG. 2—Method for Activating and Setting Up Monitored Unit
Referring to
In step 202, monitoring device 101 receives a packet of data from the activated monitored unit 102 that includes the identification of the monitoring device 101 that activated monitored unit 102 as well as the identification of monitored unit 102.
In step 203, monitoring device 101 determines if the identification of a monitoring device 101 is valid. That is, monitoring device 101 determines if the identification of a monitoring device 101 matches its own identification.
If the identification is not valid, then, in step 204, monitoring device 101 ignores the received packet of data. The packet of data may have been intended for another monitoring device 101 that activated this particular monitored unit 102.
If, however, the identification is valid, then, in step 205, monitoring device 101 transmits a seed and a time synchronization, as discussed above, to monitored unit 102. Further, if the identification is valid, monitoring device 101 may transmit an identification assigned to monitored unit 102. Monitoring device 101 may be said to be in “monitoring mode” at this point in time as will be described below in conjunction with
It is noted that method 200 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 200 may be executed in a different order presented and that the order presented in the discussion of
FIG. 3—Method for Monitoring Monitored Unit
Referring to
If monitoring device 101 did not receive received a packet of data from monitored unit 102 at the appropriate time and at the expected frequency, then, in step 302, monitoring device 101 makes a determination if the time that monitoring device 101 has not heard from monitored unit 102 exceeds a threshold, e.g., three seconds. If the time that monitoring device 101 has not heard from monitored unit 102 does not exceed a threshold, then monitoring device 101 makes a determination if it received a packet of data from monitored unit 102 at an expected time and frequency in step 301.
If, however, the time that monitoring device 101 has not heard from monitored unit 102 exceeds a threshold, then, in step 303, monitoring device 101 outputs an indication, e.g., lights from LEDs 110, a beep from beeper 111, vibration from vibrator 112, to the user of monitoring device 101 that monitoring device 101 has not heard from monitored unit 102 for over a threshold of time.
Returning to step 301 of
If the identification is not valid, then, in step 305, monitoring device 101 ignores the received packet of data. The packet of data may have been intended for another monitoring device 101.
If, however, the identification is valid, then, in step 306, monitoring device 101 measures the signal strength of the received packet of data. In step 307, monitoring device 101 determines if the signal strength is below a threshold.
If the signal strength at or above the threshold, then, in step 308, monitoring device 101 transmits an acknowledgment to monitored unit 102 at a frequency determined by the algorithm, e.g., frequency hopping table, stored in memory 107.
If, however, the signal strength is below the threshold, then, in step 309, monitoring device 101 outputs an indication, e.g., lights from LEDs 110, a beep from beeper 111, vibration from vibrator 112, to the user of monitoring device 101 that monitored unit 102 is located beyond a “comfort zone.” The “comfort zone” may refer to a distance determined by the user of monitoring device 101 as to how far monitored unit 102 should be located from monitoring device 101.
In step 309, monitoring device 101 transmits an acknowledgment to monitored unit 102 at a frequency determined by the algorithm, e.g., frequency hopping table, stored in memory 107.
Referring to steps 303 and 310, upon outputting an indication to the user of monitoring device 101 that monitoring device 101 has not heard from monitored unit 102 for over a threshold of time and transmitting an acknowledgment, respectively, monitoring device 101, in step 311, provides the user of monitoring device 101 an option of entering the “locate mode” of operation.
In step 312, monitoring device 101 makes a determination if it received a request to enter the locate mode of operation. If monitoring device 101 does not receive a request to enter the locate mode of operation, then monitoring device 101 makes a determination if it received a packet of data from monitored unit 102 at the appropriate time and frequency in step 301.
If, however, monitoring device 101 does receive a request to enter the locate mode of operation, then, in step 313, monitoring device 101 enters the locate mode of operation. A description of different methods of enacting the locate mode of operation on monitored unit 102 is provided below in conjunction with
It is noted that method 300 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 300 may be executed in a different order presented and that the order presented in the discussion of
FIG. 4—Method for Enacting the Locate Mode of Operation on Monitored Unit
Referring to
In step 403, monitored unit 102 determines if it received a signal from monitoring device 101 to exit the locate mode of operation. If not, then monitored unit 102 continues to transmit packets of data at an increased rate at expected frequencies in step 402.
If, however, monitored unit 102 receives a signal from monitoring device 101 to exit the locate mode of operation, then monitored unit 102 exits the locate mode of operation in step 404. In step 405, monitored unit 102 transmits packets of data at a normal rate, e.g., 1 transmission per second, at expected frequencies according to an algorithm, e.g., frequency hopping table, stored in memory 119. That is, monitored unit 102 enters the monitoring mode of operation and transmits packets of data at the normal rate of transmission.
It is noted that method 400 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 400 may be executed in a different order presented and that the order presented in the discussion of
FIG. 5—Alternative Method for Enacting the Locate Mode of Operation on Monitored Unit
Referring to
If monitored unit 102 received an acknowledgment at the appropriate time from monitoring device 101 at the expected frequency, then, in step 502, monitored unit 102 transmits packets of data to monitoring device 101. In one embodiment, the packets of data may include the identification of monitoring device 101 and the identification of monitored unit 102.
If, however, monitored unit 102 did not receive an acknowledgment at the appropriate time from monitoring device 101 at the expected frequency, then, in step 503, monitored unit 102 determines if the time that monitored unit 102 has not received the acknowledgment exceeds a time threshold, e.g., three seconds.
If the time that monitored unit 102 has not received the acknowledgment does not exceed the time threshold, then, in step 501, monitored unit 102 determines if it received an acknowledgment at the next appropriate time from monitoring device 101 at the next expected frequency according to the algorithm, e.g. frequency hopping table, stored in memory 119.
If, however, the time that monitored unit 102 has not received the acknowledgment does exceed the time threshold, then, in step 504, monitored unit 102 enters the locate mode of operation from monitoring device 101. In step 505, monitored unit 102 transmits packets of data at an increased rate at expected frequencies according to an algorithm, e.g., frequency hopping table, stored in memory 119. For example, monitored unit 102 may transmit packets of data at expected frequencies every 1 second during the monitoring mode of operation. During the locate mode of operation, monitored unit 102 may transmit packets of data at expected frequencies every 200 milliseconds.
In step 506, monitored unit 102 determines if it received a signal to exit the locate mode of operation from monitoring device 101. If monitored unit 102 does not receive a signal to exit the locate mode of operation from monitoring device 101, then, in step 505, monitored unit 102 transmits packets of data at an increased rate at expected frequencies according to an algorithm, e.g., frequency hopping table, stored in memory 119. If, however, monitored unit 102 does receive a signal to exit the locate mode of operation from monitoring device 101, then, in step 507, monitored unit 102 exits the locate mode of operation.
It is noted that method 500 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 500 may be executed in a different order presented and that the order presented in the discussion of
FIG. 6—Method for Locating Monitored Unit in the Locate Mode of Operation
Referring to
In step 602, the user of monitoring device 101 may scan over a 360 degree field with monitoring device 101.
In step 603, monitoring device 101 transmits a signal to monitored unit 102 at the expected time and frequency using the algorithm stored in memory 107 to enter the locate mode of operation. In step 604, monitoring device 101 determines if it received a packet of data at the appropriate time and at the expected frequency from monitored unit 102.
If monitoring device 101 did not receive a packet of data from monitored unit 102 at the appropriate time and at the expected frequency, then, in step 603, monitoring device 101 transmits a signal to monitored unit 102 at the expected frequency using the algorithm stored in memory 107 to enter the locate mode of operation.
If, however, monitoring device 101 did receive a packet of data from monitored unit 102 at the appropriate time and at the expected frequency, then, in step 605, monitoring device 101 determines if it received a valid identification. As stated above, each time monitored unit 102 communicates with monitoring device 101, monitored unit 102 may transmit a packet of data that includes the identification of a monitoring device 101.
If the identification is not valid, then, in step 606, monitoring device 101 ignores the received packet of data. The packet of data may have been intended for another monitoring device 101.
If, however, the identification is valid, then, in step 607, monitoring device 101 transmits an acknowledgment to monitored unit 102 at the expected frequency determined by the algorithm stored in memory 107.
In step 608, monitoring device 101 measures the strength of the received packet of data. In step 609, monitoring device 101 determines the direction of the signal using digital compass 105.
In step 610, monitoring device 101 creates a polar plot, which is displayed on display 106, indicating both the signal strength and direction of the received signal.
In step 611, monitoring device 101 determines if the user of monitoring device 101 exits the locate mode of operation. In one embodiment, the user of monitoring device 101 may exit the locate mode of operation by inputting to monitoring device 101, such as by button(s)/switch(es) 109, a command to exit the locate mode of operation.
If the user does not exit the locate mode of operation, then, in step 604, monitoring device 101 determines if it received a packet of data at the anticipated time and at the expected frequency from monitored unit 102.
If, however, the user did exit the locate mode of operation, then, in step 612, monitoring device 101 transmits a signal to monitored unit 102 to exit out of the locate mode of operation. In step 613, monitoring device 101 returns to the monitoring mode of operation.
It is noted that method 600 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 600 may be executed in a different order presented and that the order presented in the discussion of
FIG. 7—Wrist Infrared Reflector
Referring to
FIG. 8—Method for Detecting Tampering of Monitored Unit
Referring to
If the intensity of the reflections is less than a threshold, then monitored unit 102 continues to determine if the intensity of the reflections is less than a threshold in step 802.
If, however, the intensity of the reflections is equal to or greater than the threshold, then, in step 802, monitored unit 102 transmits an indication to monitoring device 101 that monitored unit 102 has been tampered with. In step 803, an indication, e.g., alarm, is outputted by monitored unit 102. For example, an alarm may be outputted via beeper 122 or a speaker (not shown) on monitored unit 102.
In step 804, monitored unit 102 enters the locate mode of operation. It is noted that the locate mode of operation is discussed above and that the description will not be repeated herein for the sake of brevity.
It is noted that method 800 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 800 may be executed in a different order presented and that the order presented in the discussion of
FIG. 9—Method for Requesting the User of Monitored Unit to Return to Base
Referring to
In step 902, monitoring device 101 transmits a signal to monitored unit 102, selected by the user of monitoring device 101, indicating to return to base.
In step 903, monitored unit 102 receives the transmitted signal from monitoring device 101 indicating to return to base.
In step 904, monitored unit 102 outputs an indication to the user of monitored unit 102 to return to base. For example, an indication to return to base may be outputted via beeper 122 or a speaker (not shown) on monitored unit 102.
It is noted that method 900 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 900 may be executed in a different order presented and that the order presented in the discussion of
FIG. 10—Method for Deactivating a Selected Monitored Unit
Referring to
In step 1002, monitoring device 101 transmits a signal to monitored unit 102, selected by the user of monitoring device 101, to deactivate the selected monitored unit 102.
In step 1003, monitored unit 102 receives the transmitted signal from monitoring device 101.
In step 1004, monitored unit 102 becomes deactivated.
It is noted that method 1000 may include other and/or additional steps that, for clarity, are not depicted. It is noted that method 1000 may be executed in a different order presented and that the order presented in the discussion of
Although the system, computer program product and method are described in connection with several embodiments, it is not intended to be limited to the specific forms set forth herein; but on the contrary, it is intended to cover such alternatives, modifications and equivalents, as can be reasonably included within the spirit and scope of the invention as defined by the appended claims. It is noted that the headings are used only for organizational purposes and not meant to limit the scope of the description or claims.
The present application is a divisional application of U.S. patent application Ser. No. 10/644,152, entitled “System for Monitoring and Locating People and Objects,” filed Aug. 20, 2003, now U.S. Pat. No. 6,778,902, which is a continuation-in-part of U.S. patent application Ser. No. 10/224,643, entitled “A Directional Finding System Implementing A Rolling Code,” filed Aug. 20, 2002 now abandoned, which are incorporated by reference herein. The present application claims priority benefits to U.S. patent application Ser. Nos. 10/644,152 and 10/224,643 under 35 U.S.C. §121.
Number | Name | Date | Kind |
---|---|---|---|
4884208 | Marinell et al. | Nov 1989 | A |
5289163 | Perez et al. | Feb 1994 | A |
5471404 | Mazer | Nov 1995 | A |
5537102 | Pinnow | Jul 1996 | A |
5590133 | Billstrom et al. | Dec 1996 | A |
5594425 | Ladner et al. | Jan 1997 | A |
5603094 | Greear, Jr. | Feb 1997 | A |
5621417 | Hassan et al. | Apr 1997 | A |
5640146 | Campana, Jr. | Jun 1997 | A |
5642303 | Small et al. | Jun 1997 | A |
5650769 | Campana, Jr. | Jul 1997 | A |
5650770 | Schlager et al. | Jul 1997 | A |
5652570 | Lepkofker | Jul 1997 | A |
5694428 | Campana, Jr. | Dec 1997 | A |
5714932 | Castellon et al. | Feb 1998 | A |
5714937 | Campana, Jr. | Feb 1998 | A |
5722059 | Campana, Jr. | Feb 1998 | A |
5742644 | Campana, Jr. | Apr 1998 | A |
5748103 | Flach et al. | May 1998 | A |
5751773 | Campana, Jr. | May 1998 | A |
5857433 | Files | Jan 1999 | A |
5900818 | Lemnell | May 1999 | A |
5914671 | Tuttle | Jun 1999 | A |
5952958 | Speasl et al. | Sep 1999 | A |
5973601 | Campana, Jr. | Oct 1999 | A |
5987421 | Chuang | Nov 1999 | A |
6075458 | Ladner et al. | Jun 2000 | A |
6127917 | Tuttle | Oct 2000 | A |
6169484 | Schuchman et al. | Jan 2001 | B1 |
6169485 | Campana, Jr. | Jan 2001 | B1 |
6169494 | Lopes | Jan 2001 | B1 |
6236365 | LeBlanc et al. | May 2001 | B1 |
6246376 | Bork et al. | Jun 2001 | B1 |
6249252 | Dupray | Jun 2001 | B1 |
6297768 | Allen, Jr. | Oct 2001 | B1 |
6300903 | Richards et al. | Oct 2001 | B1 |
6337628 | Campana, Jr. | Jan 2002 | B1 |
6459888 | Clark | Oct 2002 | B1 |
6492906 | Richards et al. | Dec 2002 | B1 |
6563427 | Bero et al. | May 2003 | B1 |
6600418 | Francis et al. | Jul 2003 | B1 |
Number | Date | Country | |
---|---|---|---|
20040260463 A1 | Dec 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10644152 | Aug 2003 | US |
Child | 10865528 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10224643 | Aug 2002 | US |
Child | 10644152 | US |