US20040036597A1 - Directional finding system implementing a rolling code - Google Patents

Directional finding system implementing a rolling code Download PDF

Info

Publication number
US20040036597A1
US20040036597A1 US10/224,643 US22464302A US2004036597A1 US 20040036597 A1 US20040036597 A1 US 20040036597A1 US 22464302 A US22464302 A US 22464302A US 2004036597 A1 US2004036597 A1 US 2004036597A1
Authority
US
United States
Prior art keywords
monitoring device
monitored unit
unit
recited
monitored
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/224,643
Inventor
Robert Mays
Raymond Atilano
Roger Case
Bruce Cummings
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bluespan Inc
Original Assignee
Bluespan LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bluespan LLC filed Critical Bluespan LLC
Priority to US10/224,643 priority Critical patent/US20040036597A1/en
Assigned to BLUESPAN, L.L.C. reassignment BLUESPAN, L.L.C. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ATILANO, RAYMOND B., CASE, ROGER P., CUMMINGS, BRUCE, MAYS, ROBERT JR.
Priority to CA002496255A priority patent/CA2496255A1/en
Priority to US10/644,152 priority patent/US6778902B2/en
Priority to NZ535214A priority patent/NZ535214A/en
Priority to EP03754404A priority patent/EP1540443A4/en
Priority to PCT/US2003/026201 priority patent/WO2004019168A2/en
Priority to AU2003272231A priority patent/AU2003272231B2/en
Publication of US20040036597A1 publication Critical patent/US20040036597A1/en
Priority to US10/865,528 priority patent/US7050906B2/en
Assigned to BLUESPAN, INC. reassignment BLUESPAN, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: BLUESPAN, L.L.C.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02Alarms for ensuring the safety of persons
    • G08B21/0202Child monitoring systems using a transmitter-receiver system carried by the parent and the child

Definitions

  • the present invention relates to the field of directionally finding systems, and more particularly to a directional finding system implementing a rolling identification code between the monitoring device and the monitored unit to lessen the ability of a third party finding the object, e.g., person, automobile, attached to the monitored unit.
  • One such system for finding moveable objects such as a person utilizes a tracking/locating unit that transmits a unique identification signal based on at least one biological parameter of the person to be monitored, e.g., body temperature, pulse rate, scanned image of a fingerprint.
  • the person to be monitored may wear a tracked unit that monitors such biological parameter(s), e.g., body temperature. If the biological parameter(s), e.g., body temperature, of the person is outside of a pre-selected range, then an alarm condition may be indicated to the tracking/locating unit indicating that the tracked device worn by the person may have been removed.
  • basing an alarm condition on biological parameters may provide many false positives as biological parameters, e.g., body temperature, may register a value beyond a pre-selected range for reasons other than removal, such as exercising.
  • this system necessarily requires using at least one biological parameter of the person to be tracked in order to determine the location and possible abduction of the person.
  • this system is necessarily limited to locating people and not other types of objects, e.g., automobiles, that do not possess biological parameters.
  • the unique identification signal based on at least one biological parameter of the person to be tracked does not change during every communication between the tracking/locating unit and the tracked unit.
  • a third party e.g., potential abductor
  • a third party may be able to intercept the signal and with a similar tracking/locating unit track that person as well.
  • a third party e.g., potential abductor
  • Another system for finding objects includes 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.
  • a third party e.g., potential abductor
  • a third party may be able to intercept the signal and with a similar monitoring device track the child.
  • a third party e.g., potential abductor
  • the problems outlined above may at least in part be solved in some embodiments of the present invention by transmitting a rolling identification code between the monitoring device and the monitored unit attached to the object, e.g., person, automobile, being monitored.
  • a rolling identification code By transmitting a rolling identification code, a third party would be less likely to associate the identification code with the monitored object.
  • a method for finding an object may comprise the step of a monitoring device receiving input as to which unit (“monitored unit”) is to be monitored by the monitoring device.
  • the monitored unit may be pre-assigned with a unique identification code.
  • the monitoring device may further receive input establishing a maximum distance the monitored unit should be located from the monitoring device.
  • the monitoring device may then poll the monitored unit with an updated identification code.
  • the monitoring device may receive an acknowledgment from the monitored unit that includes a further updated identification code. If the received updated identification code is expected, then the monitoring device may determine an approximate distance the monitored unit is located from the monitoring device.
  • a system may comprise a unit that is monitored (“monitored unit”) attached to an object, e.g., child.
  • the monitored unit may be configured to detect tampering of the monitored unit.
  • the monitored unit may transmit an indication to a monitoring device that the monitored unit has been tampered with.
  • the monitored unit may further transmit signals in a substantially continuous manner to the monitoring device upon detecting tampering of the monitored unit.
  • the monitoring device may be configured to receive both the indication that the monitored unit has been tampered with as well as the transmitted signals from the monitored unit.
  • the monitoring device may further be configured to determine a direction of the monitored unit from the signal strength and direction of the transmitted signals.
  • a method for finding one or more objects may comprise the step of a monitoring device receiving input to monitor one or more units where each of the units may be assigned a unique identification code.
  • the monitoring device may poll each of the monitored units with a rolling identification code.
  • a system may comprise a monitoring device where the monitoring device may include a System On a Chip (SoC) configured to monitor a unit attached to an object, e.g., person, automobile.
  • SoC System On a Chip
  • the monitoring device may further include an activation unit coupled to the SoC where the activation unit may activate the SoC for a limited duration.
  • FIG. 1 illustrates an embodiment of the present invention of a system for directionally finding an object
  • FIG. 2 is a flowchart of a method for finding an object in accordance with one embodiment of the present invention
  • FIG. 3 is a flowchart of the sub-steps of the step of receiving input as to which one or more units are to be monitored by the monitoring device in accordance with one embodiment of the present invention
  • FIG. 4 is a flowchart of a method for adding a unit to be monitored by the monitoring device in accordance with one embodiment of the present invention
  • FIG. 5 is a flowchart of a method for deactivating a unit from being monitored by the monitoring device in accordance with one embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for finding a monitored unit that has been tampered with in accordance with one embodiment of the present invention.
  • FIG. 1 System for Directionally Finding an Object
  • FIG. 1 illustrates one embodiment of a system 100 for locating an object, e.g., person, automobile, baby carriage.
  • system 100 may comprise a monitoring device 101 configured to monitor one or more units 102 , e.g., wristband type of device worn by a child, attached to one or more objects. It is noted that monitoring device 101 may be configured to monitor unit 102 attached to any type of object.
  • monitoring device 101 may comprise a System On a Chip (SoC) 103 coupled to an activation unit 104 , a battery 105 , button(s) and/or switch(es) 106 , Light Emitting Diode(s) (LED's) 107 , a buzzer 108 and a transmitter/receiver circuit 109 .
  • Transmitter/receiver circuit 109 may be coupled to an antenna switch 110 which may be coupled to a Yagi antenna 111 and an omni directional antenna 112 . It is noted that monitoring device 101 may comprise different circuitry providing the same functionality as discussed herein and that FIG. 1 is illustrative.
  • SoC 103 may be configured in one embodiment to comprise a memory (not shown), e.g., non-volatile memory, to store a program to perform the steps of the method for locating an object as described further below in conjunction with FIGS. 2 - 3 .
  • the program stored in memory (not shown) may include the functionality to add a unit to be monitored by monitoring device 101 as described further below in conjunction with FIG. 4.
  • the program stored in memory (not shown) may include the functionality to deactivate a monitored unit as described further below in conjunction with FIG. 5.
  • the program stored in memory (not shown) may include the functionality to directionally find the monitored unit upon the monitored unit being tampered with as described further below in conjunction with FIG. 6.
  • SoC 103 may further comprise a processor (not shown) coupled to the memory (not shown).
  • the processor (not shown) may be configured to execute the instructions of the program listed above. It is noted that the steps of the methods performed by the program mentioned above may in an alternative embodiment be implemented in hardware such as in an Application Specific Integrated Circuit (ASIC).
  • ASIC Application Specific Integrated Circuit
  • SoC 103 may be coupled to an activation unit 104 .
  • Activation unit 104 may be configured to activate SoC 103 for a limited pre-selected duration, e.g., 90 days, upon activation unit 104 making either a physical, mechanical or electrical contact with SoC 103 .
  • a counter in SoC 103 implemented in either software or hardware in SoC 103 , may count the duration of time SoC 103 has been activated.
  • SoC 103 deactivates activation unit 104 thereby deactivating SoC 103 and deactivating monitoring unit 103 . It may be desirable for deactivating monitoring device 101 periodically for ongoing security to ensure integrity of monitoring device 101 .
  • SoC 103 may only be continuously active by using a particular activation unit 104 during different stages of operation.
  • one particular activation unit 104 may only be configured to activate SoC 103 from day 0 to day 90 of operation.
  • Another activation unit 104 may only be configured to activate SoC 103 from day 91 to day 180 of operation.
  • a counter in SoC 103 implemented in either software or hardware in SoC 103 , may continuously track the time of operation of SoC 103 thereby indicating to SoC 103 which particular activation unit 104 will activate SoC 103 .
  • SoC 103 may store a table in its memory (not shown) comprising a list of activation codes to activate SoC 103 during different stages of operation.
  • SoC 103 may be configured to read an activation code stored in the memory (not shown) in activation unit 104 to determine if this is the appropriate activation unit 104 to activate SoC 103 . If the activation code is the appropriate activation code for the particular stage of operation, then SoC 103 becomes activated. Otherwise, SoC 103 remains deactivated.
  • Battery 105 may supply the necessary operating power for the circuitry and components of monitoring device 101 .
  • Battery 105 may be a standard carbon or lithium battery, or a rechargeable type battery such as nickel metal hydride (NiMH) or nickel cadmium (NiCAD).
  • NiMH nickel metal hydride
  • NiCAD nickel cadmium
  • Monitoring device 101 may comprise input/output devices such as button(s)/switch(es) 106 , LED's 107 , and/or buzzer 108 .
  • Data may be inputted to monitoring device 101 through button(s)/switch(es) 106 , e.g., inputting a maximum distance the monitored unit 102 should be located from monitoring device 101 as discussed in conjunction with FIG. 2, inputting as to which units 102 are to be monitored by monitoring device 101 as discussed in conjunction with FIG. 2, inputting a new unit 102 to be monitored by monitoring device 101 as discussed in conjunction with FIG. 4, resetting the maximum distance monitored unit 102 may be located from monitoring device 101 as discussed in conjunction with FIG.
  • Output may be received by the user of monitoring device 101 through LED's 107 and/or buzzer 108 , e.g., outputting an indication that monitored unit 102 is located beyond a pre-selected percentage, e.g., 90%, of a pre-selected maximum distance, e.g., 1,400 feet, as discussed in conjunction with FIG. 2, outputting an indication that the monitored unit 102 is located beyond the pre-selected maximum distance as discussed in conjunction with FIG. 2.
  • a pre-selected percentage e.g. 90%
  • a pre-selected maximum distance e.g., 1,400 feet
  • monitoring device 101 may comprise other types of input/output devices, e.g., display, alphanumeric characters, not illustrated and that such input/output devices would be known to a person of ordinary skill in the art. It is further noted that embodiments incorporating such input/output devices would fall within the scope of the present invention.
  • Transmitter/receiver circuit 109 may be configured to transmit information to and receive information from monitored unit 102 .
  • a unique identification code e.g., a unique 8-bit identification number
  • This unique identification code may be continually changed during every communication with monitored unit 102 using an algorithm stored in memory (not shown) of SoC 103 . This is commonly referred to as “rolling code.”
  • the same algorithm may be used by monitored unit 102 to thereby expect the next identification code to be transmitted by monitoring device 101 . If the expected identification code is not received, then monitored unit 102 will not respond to the received transmission. Similarly, monitoring device 101 expects to receive a particular identification code from monitored unit 102 using the same algorithm. If the expected identification code is not received, then SoC 103 will not respond to the received transmission.
  • Antenna switch 110 may be configured to activate Yagi antenna 111 to receive transmitted information, e.g., when monitoring device 101 operates in “locate mode” to track the location of monitored unit 102 such as when the 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 FIGS. 2 and 6, respectively.
  • Yagi antennas are well known to persons of ordinary skill in the art and will therefore not be discussed in detail for the sake of brevity. Consequently, Yagi antenna 111 may be activated to determine the direction of monitored unit 102 .
  • Antenna switch 110 may also be configured to activate an omni directional antenna 112 when monitoring device 101 transmits information to one or more monitored units 102 .
  • monitoring device 101 It is noted that other features of monitoring device 101 will be discussed further below in conjunction with FIGS. 2 - 6 .
  • monitored unit 102 may comprise a System On a Chip (SoC) 113 coupled to a battery 114 , button(s) and/or switch(es) 115 , tamper sensor 116 , and a transmitter/receiver circuit 117 .
  • Transmitter/receiver circuit 117 may be coupled to an omni directional antenna 118 . It is noted that monitored unit 102 may comprise different circuitry providing the same functionality as discussed herein and that FIG. 1 is illustrative.
  • SoC 113 may be configured similarly as SoC 103 .
  • SoC 113 may be configured to comprise a memory (not shown), e.g., non-volatile memory, to store a program for transmitting an indication that monitored unit 102 has been tampered with as well as transmitting signals in a “panic state” as described further below in conjunction with FIG. 6.
  • the program stored in memory (not shown) may include the functionality to deactivate monitored unit 102 as described further below in conjunction with FIG. 5.
  • the program stored in memory (not shown) may store the same algorithm as stored in monitoring device 101 in order to produce the same “rolling code” as monitoring/tracing device 101 as discussed above.
  • SoC 113 may further comprise a processor (not shown) coupled to the memory (not shown).
  • the processor (not shown) may be configured to execute the instructions of the programs listed above. It is noted that the steps of the methods performed by the program mentioned above may in an alternative embodiment be implemented in hardware such as in an Application Specific Integrated Circuit (ASIC).
  • ASIC Application Specific Integrated Circuit
  • Battery 114 may supply the necessary operating power for the circuitry and components of monitored unit 102 .
  • Battery 114 may be a standard carbon or lithium battery, or a rechargeable type battery such as nickel metal hydride (NiMH) or nickel cadmium (NiCAD).
  • Monitored unit 102 may comprise input devices such as button(s)/switch(es) 116 . These devices may be used by the user of monitored unit 102 to input data to monitored unit 102 . It is noted that monitored unit 102 may comprise other types of input devices as well as output devices, e.g., display, alphanumeric characters, not illustrated and that such input/output devices would be known to a person of ordinary skill in the art. It is further noted that embodiments incorporating such input/output devices would fall within the scope of the present invention.
  • Tamper sensor 116 may be configured to detect monitored unit 102 being tampered with such as removing monitored unit 102 from an object. Upon detecting monitored unit 102 being tampered with, tamper sensor 116 may be configured to transmit a signal to SoC 113 indicating that monitored unit 102 has been tampered with. SoC 113 may then transmit a signal indicating monitored unit 102 has been tampered with to monitoring device 101 as discussed in conjunction with FIG. 6.
  • Transmitter/receiver circuit 117 may be configured similarly as transmitter/receiver circuit 109 .
  • Transmitter/receiver circuit 117 may be configured to transmit information to and receive information from monitoring device 101 via omni directional antenna 118 .
  • Omni directional antenna 118 is configured similarly as omni directional antenna 112 .
  • a unique identification code e.g., a unique 8-bit identification number
  • this unique identification code may be continually changed during every communication with a monitored unit using an algorithm stored in memory (not shown) in SoC 113 . This is the same algorithm used by monitoring device 101 to thereby expect the next identification code to be transmitted by monitoring device 101 . If the expected identification code is not received, then SoC 113 will not respond to the received transmission.
  • FIG. 2 Method for Finding an Object
  • FIG. 2 is a flowchart of one embodiment of the present invention of a method 200 for finding unit 102 (FIG. 1) attached to an object.
  • prior art locating systems did not transmit an identification code that changes upon every communication between a monitoring device and a monitored unit. Consequently, a third party, e.g., potential abductor, may be able to intercept the signal and with a similar monitoring device locate the object, e.g., child, attached to the monitored unit.
  • Method 200 is a method for finding an object, e.g., person, automobile, where the communication between the monitoring device and the monitored unit attached to the object implements a rolling code.
  • monitoring device 101 may be activated upon insertion of the appropriate activation unit 104 as discussed above.
  • monitoring device 101 may be activated for a limited duration or stage of operation, e.g., day 0 to day 90 in operation, only by inserting the appropriate activation unit 104 in monitoring device 101 containing the appropriate activation code.
  • stage of operation e.g., day 0 to day 90 in operation
  • monitoring device 101 may be activated for the next stage of operation, e.g., day 91 to day 180 in operation, upon insertion of the appropriate activation unit 104 containing the appropriate activation code.
  • monitoring device 101 may receive input as to which one or more units 102 (“monitored units”) are to be monitored by monitoring device 101 .
  • Step 202 may comprise sub-steps as illustrated in FIG. 3.
  • monitoring device 101 may read a unique identification code, e.g., 8 -bit identification number, in unit 102 to be monitored by monitoring device 101 .
  • the identification code may be stored in memory of SoC 113 .
  • each monitored unit 102 may be assigned a unique identification code.
  • the identification code read may be stored in memory (not shown) of SoC 103 . This may be valuable in case the object has been abducted or stolen and the authorities, e.g., police, want to locate the monitored unit 102 attached to the object with their own monitoring device 101 .
  • the authorities may able to use their own monitoring device 101 to locate unit 102 by appending a bit, referred to herein as an emergency bit, to the unique identification code stored in memory of SoC 103 in step 302 .
  • Unit 102 may be configured to respond to a signal containing its unique identification code with an appropriate appended value.
  • the algorithm that generates a rolling code may be implemented by monitoring device 101 .
  • the algorithm may be stored in memory of SoC 103 .
  • monitoring device 101 may transmit a command to monitored unit 102 to implement the same algorithm to generate a rolling code.
  • the algorithm may be stored in memory of SoC 113 .
  • monitored unit 102 whose identification code was read by monitoring device 101 may be assigned a particular LED 107 on monitoring device 101 .
  • one or more monitored units 102 may be associated with a particular LED 107 on monitoring device 101 .
  • the user of monitoring device 101 may be informed of a particular monitored unit 102 being located beyond a pre-selected maximum distance from monitoring device 101 by having LED 107 associated with that particular monitored unit 102 light up.
  • the user of monitoring device 101 may be informed of a particular monitored unit 102 being tampered with by having LED 107 associated with that particular monitored unit 102 light up.
  • monitoring device 101 may receive input from the user of monitoring device 101 establishing a maximum distance each unit 102 to be monitored by monitoring device 101 should be located from monitoring device 101 .
  • a user of monitoring device 101 e.g., parent
  • the object, e.g., child, attached to unit 102 may be located from the user of monitoring device 101 .
  • monitoring device 101 may be configured to monitor and find unit 102 located beyond this maximum distance established by the user of monitoring device 101 . This maximum distance may be a distance within the range monitoring device 101 may monitor unit 102 .
  • monitoring device 101 may be configured to monitor unit 102 located within two miles from monitoring device 101 .
  • the user may input the maximum distance through an input device, e.g., button/switch 106 , alphanumeric keypad, on monitoring device 101 . It is noted for clarity that the user of monitoring device 101 may input to monitoring device 101 a separate maximum distance for each monitored unit 102 to be monitored by monitoring device 101 .
  • monitoring device 101 may poll each unit 102 to be monitored periodically using a rolling code. That is, monitoring device 101 may transmit a query to each monitored unit 102 . Monitoring device 101 may transmit along with the query an updated identification code, e.g., update the identification code stored in memory of SoC 103 in step 302 (FIG. 3), generated by an algorithm stored in memory (not shown) of SoC 103 . As stated above, monitored unit 102 will only respond to the query if the updated identification code is expected. The expected updated identification code is determined by the same algorithm stored in memory (not shown) of SoC 113 .
  • an updated identification code e.g., update the identification code stored in memory of SoC 103 in step 302 (FIG. 3
  • the expected updated identification code is determined by the same algorithm stored in memory (not shown) of SoC 113 .
  • monitoring device 101 may receive an acknowledgment from the appropriate monitored unit 102 that includes an updated identification code.
  • the acknowledgment may further include the status, e.g., no tampering of monitored unit 102 , of monitored unit 102 .
  • SoC 113 of monitored unit 102 may generate an updated identification code with respect to the identification code received from monitoring device 101 .
  • monitoring device 101 may determine if the received identification code is recognized, i.e., expected. As stated above, the expected updated identification code is determined by the algorithm stored in memory (not shown) of SoC 103 .
  • monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204 .
  • monitoring device 101 may determine an approximate distance the recognized monitored unit 102 is located monitoring device 101 .
  • monitoring device 101 may determine the approximate distance the recognized monitored unit 102 is located from monitoring device 101 based on the strength of the received signal, i.e., based on the strength of the acknowledgment received in step 205 .
  • monitoring device 101 may determine if there are any monitored units 102 located beyond a pre-selected percentage, e.g., ninety percent (90%), of the maximum distance, e.g., 2,000 feet, monitored unit 102 is to be located from monitoring device 101 .
  • a pre-selected percentage e.g., ninety percent (90%)
  • the maximum distance monitored unit 102 may be located from monitoring device 101 may be established in step 203 .
  • the user of monitoring device 101 may also input to monitoring device 101 a separate pre-selected percentage, e.g., eighty percent (80%), for each monitored unit 102 such as in step 203 .
  • monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204 .
  • monitoring device 101 may determine if there are any monitored units 102 located beyond the maximum distance monitored unit 102 is to be located from monitoring device 101 .
  • monitoring device 101 may output an indication indicating that one or more monitored units 102 are located beyond the pre-selected percentage of the maximum distance but are not located beyond the maximum distance. For example, monitoring device 101 may light a particular LED 107 associated with each monitored unit 102 located beyond the pre-selected percentage, e.g., 90%, of the maximum distance, e.g., 2,000 feet, monitored unit 102 is to be located from monitoring device 101 but not located beyond the maximum distance.
  • monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204 .
  • monitoring device 101 may output an indication indicating one or more monitored units 102 located beyond the maximum distance established in step 203 .
  • monitoring device 101 may light a particular LED 107 associated with each monitored unit 102 located beyond the maximum distance monitored unit 102 is to be located from monitoring device 101 .
  • monitoring device 101 may trigger buzzer 108 . It is noted that there other means for indicating each monitored unit 102 that is located beyond the maximum distance and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments implementing such means would fall within the scope of the present invention.
  • monitoring device 101 may determine if the maximum distance monitored unit 102 (referring to monitored unit 102 that was indicated as being located beyond the maximum distance established in step 203 ) is to be located from monitoring device 101 is to be reset.
  • monitoring device may receive input from the user of monitoring device 101 to reset the maximum distance.
  • the user may reset the maximum distance through an input device, e.g., button/switch 106 , alphanumeric keypad, on monitoring device 101 .
  • monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204 .
  • monitoring device 101 may enter a mode, commonly referred to as a “locate mode”, where monitoring device 101 may transmit queries to monitored unit 102 located beyond the maximum distance in a substantially continuous manner. It is noted that queries may include a rolling identification code as discussed above.
  • monitoring device 101 may receive acknowledgments from that monitored unit 102 located beyond the pre-selected maximum distance monitored unit 102 is to be located from monitoring device 101 . It is noted that the acknowledgments may include a rolling identification code as discussed above. In step 216 , monitoring device 101 may determine the direction of that monitored unit 102 via signal strength and direction of the received acknowledgments.
  • Monitoring device 101 may be configured to perform various background processes, e.g., adding a new unit 102 to be monitored by monitoring device 101 , deactivating a monitored unit 102 currently being monitored, while monitoring device 101 locates one or more monitored units 102 as discussed above in method 102 . Some of these background processes are discussed in greater detail in FIGS. 4 - 5 .
  • method 102 may be executed in a different order presented and that the order presented in the discussion of FIG. 2 is illustrative. It is further noted that certain steps in FIG. 2 may be executed almost concurrently.
  • FIG. 4 Method for Adding a Unit to be Monitored by Monitoring Device
  • FIG. 4 is a flowchart of one embodiment of the present invention of a method 400 of a background process for adding unit 102 (FIG. 1) to be monitored by monitoring device 101 (FIG. 1).
  • monitoring device 101 may receive input to add unit 102 to be monitored by monitoring device 101 .
  • the user of monitoring device 101 may input the request to monitor an additional unit 102 via button(s)/switch(es) 106 . It is noted that there other means for the user of monitoring device 101 to input the request to monitor an additional unit 102 and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments incorporating such means would fall within the scope of the present invention.
  • monitoring device 101 may read a unique identification code, e.g., 8-bit identification number, from unit 102 to be monitored by monitoring device 101 .
  • the identification code may be stored in memory of SoC 113 .
  • each monitored unit 102 may be assigned a unique identification code.
  • the identification code read may be stored in memory (not shown) of SoC 103 . This may be valuable in case the object has been abducted or stolen and the authorities, e.g., police, want to locate the monitored unit 102 attached to the object with their own monitoring device 101 .
  • the authorities may able to use their own monitoring device 101 to locate unit 102 by appending a bit, referred to herein as an emergency bit, to the unique identification code stored in memory of SoC 103 in step 403 .
  • Unit 102 may be configured to respond to a signal containing its unique identification code with an appropriate appended value.
  • step 404 the algorithm that generates a rolling code, as discussed above, may be implemented by monitoring device 101 .
  • the algorithm may be stored in memory of SoC 103 .
  • step 405 monitoring device 101 may transmit a command to monitored unit 102 to implement the same algorithm to generate a rolling code.
  • the algorithm may be stored in memory of SoC 113 .
  • monitored unit 102 whose identification code was read by monitoring device 101 may be assigned a particular LED 107 on monitoring device 101 .
  • the additional unit 102 to be monitored may be associated with a particular LED 107 on monitoring device 101 .
  • method 400 may be executed in a different order presented and that the order presented in the discussion of FIG. 4 is illustrative. It is further noted that certain steps in FIG. 4 may be executed almost concurrently.
  • FIG. 5 Method for Deactivating a Monitored Unit from being Monitored by Monitoring Device
  • FIG. 5 is a flowchart of one embodiment of the present invention of a method 500 of a background process for deactivating monitored unit 102 (FIG. 1) from being monitored by monitoring device 101 (FIG. 1).
  • monitoring device 101 may receive input to deactivate unit 102 from being monitored by monitoring device 101 .
  • the user of monitoring device 101 may input the request to stop monitoring unit 102 via button(s)/switch(es) 106 . It is noted that there other means for the user of monitoring device 101 to input the request to stop monitoring unit 102 and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments incorporating such means would fall within the scope of the present invention.
  • monitoring device 101 may transmit a deactivation request to unit 102 to be deactivated.
  • monitored unit 102 may receive a response from monitored unit 102 indicating that unit 102 will be deactivated.
  • monitored unit 102 receiving the deactivation request may be deactivated.
  • monitored unit 102 may erase the rolling code stored in its memory of SoC 113 in step 505 .
  • monitoring device 101 may erase the identification code associated with the deactivated unit 102 stored in memory of 103 SoC in step 302 (FIG. 3) or in step 403 (FIG. 4). Monitoring device 101 may further erase the rolling code associated with the deactivated unit 102 in step 506 .
  • monitoring device 101 may cause LED 107 assigned to the deactivated monitored unit 102 to become available to be assigned to another unit 102 .
  • steps 501 - 503 and 506 - 507 may be performed by monitoring device 101 . It is further noted that steps 504 - 505 may be performed by monitored unit 102 . It is further noted that method 500 may be executed in a different order presented and that the order presented in the discussion of FIG. 5 is illustrative, e.g., steps 503 - 505 may be executed in a different order. It is further noted that certain steps in FIG. 5, e.g., steps 504 - 507 , may be executed almost concurrently.
  • FIG. 6 Method for Finding a Monitored Unit That has Been Tampered
  • FIG. 6 is a flowchart of one embodiment of the present invention of a method 600 for finding monitored unit 102 (FIG. 1) that has been tampered with.
  • monitored unit 102 may detect it being tampered with.
  • monitored unit 102 may detect any tampering via tamper sensor 106 .
  • the tampered monitored unit 102 may transmit an indication to monitoring device 101 that it has been tampered with.
  • monitoring device 101 may receive the indication that monitored unit 102 has been tampered with.
  • the tampered monitored unit 102 may enter a mode, commonly referred to as “panic mode”, where the tampered monitored unit 102 transmits signals in a substantially continuous manner. It is noted that transmissions may include a rolling identification code as discussed above.
  • monitoring device 101 may receive the transmitted signals from the tampered monitored unit 102 .
  • monitoring device 101 may determine the direction of the tampered monitored unit 102 via signal strength and direction of the received signals.
  • steps 601 - 602 and 604 may be performed by monitored unit 102 . It is further noted that steps 603 and 605 - 606 may be performed by monitoring device 101 . It is further noted that method 600 may be executed in a different order presented and that the order presented in the discussion of FIG. 6 is illustrative, e.g., steps 603 - 605 may be executed in a different order. It is further noted that certain steps in FIG. 6 may be executed almost concurrently, e.g., steps 602 and 604 .

Abstract

A method and system for finding an object, e.g., person, automobile. A monitoring device may be configured to monitor one or more units “monitored units” which are attached to various objects, e.g., person, automobile. The monitoring device may poll each monitored unit. Based on the signal strength of the responses, the monitoring device may determine the approximate distance each monitored unit is located from the monitoring device. Both the monitoring device and each monitored unit may be configured to store an algorithm to allow for a rolling identification code to be transmitted between the two devices. By transmitting a rolling identification code between the two devices, a third party would be less likely to associate the identification code with the object, e.g., person, attached to the monitored unit.

Description

    TECHNICAL FIELD
  • The present invention relates to the field of directionally finding systems, and more particularly to a directional finding system implementing a rolling identification code between the monitoring device and the monitored unit to lessen the ability of a third party finding the object, e.g., person, automobile, attached to the monitored unit. [0001]
  • BACKGROUND INFORMATION
  • There are numerous methods and systems for finding moveable objects such as automobiles, pets and people. One such system for finding moveable objects such as a person utilizes a tracking/locating unit that transmits a unique identification signal based on at least one biological parameter of the person to be monitored, e.g., body temperature, pulse rate, scanned image of a fingerprint. The person to be monitored may wear a tracked unit that monitors such biological parameter(s), e.g., body temperature. If the biological parameter(s), e.g., body temperature, of the person is outside of a pre-selected range, then an alarm condition may be indicated to the tracking/locating unit indicating that the tracked device worn by the person may have been removed. However, basing an alarm condition on biological parameters may provide many false positives as biological parameters, e.g., body temperature, may register a value beyond a pre-selected range for reasons other than removal, such as exercising. Furthermore, this system necessarily requires using at least one biological parameter of the person to be tracked in order to determine the location and possible abduction of the person. Furthermore, this system is necessarily limited to locating people and not other types of objects, e.g., automobiles, that do not possess biological parameters. Furthermore, the unique identification signal based on at least one biological parameter of the person to be tracked does not change during every communication between the tracking/locating unit and the tracked unit. Consequently, a third party, e.g., potential abductor, may be able to intercept the signal and with a similar tracking/locating unit track that person as well. Furthermore, since the identification signal does not change during every communication between the tracking/locating unit and the tracked unit, a third party, e.g., potential abductor, may be able to transmit false information to the tracking/locating device and/or tracked unit. [0002]
  • Another system for finding objects includes 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. [0003]
  • It would therefore be desirable to develop a directional finding system that made it more difficult for a third party, e.g., potential abductor, potential thief, to be able to find the object, e.g., child, automobile as well as transmit false information to the monitoring device and/or monitored unit. [0004]
  • SUMMARY
  • The problems outlined above may at least in part be solved in some embodiments of the present invention by transmitting a rolling identification code between the monitoring device and the monitored unit attached to the object, e.g., person, automobile, being monitored. By transmitting a rolling identification code, a third party would be less likely to associate the identification code with the monitored object. [0005]
  • In one embodiment of the present invention, a method for finding an object, e.g., person, automobile, may comprise the step of a monitoring device receiving input as to which unit (“monitored unit”) is to be monitored by the monitoring device. The monitored unit may be pre-assigned with a unique identification code. The monitoring device may further receive input establishing a maximum distance the monitored unit should be located from the monitoring device. [0006]
  • The monitoring device may then poll the monitored unit with an updated identification code. The monitoring device may receive an acknowledgment from the monitored unit that includes a further updated identification code. If the received updated identification code is expected, then the monitoring device may determine an approximate distance the monitored unit is located from the monitoring device. [0007]
  • In another embodiment of the present invention, a system may comprise a unit that is monitored (“monitored unit”) attached to an object, e.g., child. The monitored unit may be configured to detect tampering of the monitored unit. Upon detecting tampering of the monitored unit, the monitored unit may transmit an indication to a monitoring device that the monitored unit has been tampered with. The monitored unit may further transmit signals in a substantially continuous manner to the monitoring device upon detecting tampering of the monitored unit. [0008]
  • The monitoring device may be configured to receive both the indication that the monitored unit has been tampered with as well as the transmitted signals from the monitored unit. The monitoring device may further be configured to determine a direction of the monitored unit from the signal strength and direction of the transmitted signals. [0009]
  • In another embodiment of the present invention, a method for finding one or more objects may comprise the step of a monitoring device receiving input to monitor one or more units where each of the units may be assigned a unique identification code. The monitoring device may poll each of the monitored units with a rolling identification code. [0010]
  • In another embodiment of the present invention, a system may comprise a monitoring device where the monitoring device may include a System On a Chip (SoC) configured to monitor a unit attached to an object, e.g., person, automobile. The monitoring device may further include an activation unit coupled to the SoC where the activation unit may activate the SoC for a limited duration. [0011]
  • 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. [0012]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • 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: [0013]
  • FIG. 1 illustrates an embodiment of the present invention of a system for directionally finding an object; [0014]
  • FIG. 2 is a flowchart of a method for finding an object in accordance with one embodiment of the present invention; [0015]
  • FIG. 3 is a flowchart of the sub-steps of the step of receiving input as to which one or more units are to be monitored by the monitoring device in accordance with one embodiment of the present invention; [0016]
  • FIG. 4 is a flowchart of a method for adding a unit to be monitored by the monitoring device in accordance with one embodiment of the present invention; [0017]
  • FIG. 5 is a flowchart of a method for deactivating a unit from being monitored by the monitoring device in accordance with one embodiment of the present invention; and [0018]
  • FIG. 6 is a flowchart of a method for finding a monitored unit that has been tampered with in accordance with one embodiment of the present invention. [0019]
  • DETAILED DESCRIPTION
  • FIG. 1—System for Directionally Finding an Object [0020]
  • FIG. 1 illustrates one embodiment of a [0021] system 100 for locating an object, e.g., person, automobile, baby carriage. Referring to FIG. 1, system 100 may comprise a monitoring device 101 configured to monitor one or more units 102, e.g., wristband type of device worn by a child, attached to one or more objects. It is noted that monitoring device 101 may be configured to monitor unit 102 attached to any type of object.
  • Returning to FIG. 1, [0022] monitoring device 101 may comprise a System On a Chip (SoC) 103 coupled to an activation unit 104, a battery 105, button(s) and/or switch(es) 106, Light Emitting Diode(s) (LED's) 107, a buzzer 108 and a transmitter/receiver circuit 109. Transmitter/receiver circuit 109 may be coupled to an antenna switch 110 which may be coupled to a Yagi antenna 111 and an omni directional antenna 112. It is noted that monitoring device 101 may comprise different circuitry providing the same functionality as discussed herein and that FIG. 1 is illustrative.
  • [0023] SoC 103 may be configured in one embodiment to comprise a memory (not shown), e.g., non-volatile memory, to store a program to perform the steps of the method for locating an object as described further below in conjunction with FIGS. 2-3. Furthermore, the program stored in memory (not shown) may include the functionality to add a unit to be monitored by monitoring device 101 as described further below in conjunction with FIG. 4. Further, the program stored in memory (not shown) may include the functionality to deactivate a monitored unit as described further below in conjunction with FIG. 5. Further, the program stored in memory (not shown) may include the functionality to directionally find the monitored unit upon the monitored unit being tampered with as described further below in conjunction with FIG. 6. SoC 103 may further comprise a processor (not shown) coupled to the memory (not shown). The processor (not shown) may be configured to execute the instructions of the program listed above. It is noted that the steps of the methods performed by the program mentioned above may in an alternative embodiment be implemented in hardware such as in an Application Specific Integrated Circuit (ASIC).
  • Returning to FIG. 1, [0024] SoC 103 may be coupled to an activation unit 104. Activation unit 104 may be configured to activate SoC 103 for a limited pre-selected duration, e.g., 90 days, upon activation unit 104 making either a physical, mechanical or electrical contact with SoC 103. A counter in SoC 103, implemented in either software or hardware in SoC 103, may count the duration of time SoC 103 has been activated. Upon expiration of the pre-selected duration, e.g., 90 days, SoC 103 deactivates activation unit 104 thereby deactivating SoC 103 and deactivating monitoring unit 103. It may be desirable for deactivating monitoring device 101 periodically for ongoing security to ensure integrity of monitoring device 101.
  • In one embodiment of the present invention, [0025] SoC 103 may only be continuously active by using a particular activation unit 104 during different stages of operation. For example, one particular activation unit 104 may only be configured to activate SoC 103 from day 0 to day 90 of operation. Another activation unit 104 may only be configured to activate SoC 103 from day 91 to day 180 of operation. A counter in SoC 103, implemented in either software or hardware in SoC 103, may continuously track the time of operation of SoC 103 thereby indicating to SoC 103 which particular activation unit 104 will activate SoC 103. In one embodiment, SoC 103 may store a table in its memory (not shown) comprising a list of activation codes to activate SoC 103 during different stages of operation. Upon insertion of activation unit 104, SoC 103 may be configured to read an activation code stored in the memory (not shown) in activation unit 104 to determine if this is the appropriate activation unit 104 to activate SoC 103. If the activation code is the appropriate activation code for the particular stage of operation, then SoC 103 becomes activated. Otherwise, SoC 103 remains deactivated.
  • [0026] Battery 105 may supply the necessary operating power for the circuitry and components of monitoring device 101. Battery 105 may be a standard carbon or lithium battery, or a rechargeable type battery such as nickel metal hydride (NiMH) or nickel cadmium (NiCAD).
  • [0027] Monitoring device 101 may comprise input/output devices such as button(s)/switch(es) 106, LED's 107, and/or buzzer 108. Data may be inputted to monitoring device 101 through button(s)/switch(es) 106, e.g., inputting a maximum distance the monitored unit 102 should be located from monitoring device 101 as discussed in conjunction with FIG. 2, inputting as to which units 102 are to be monitored by monitoring device 101 as discussed in conjunction with FIG. 2, inputting a new unit 102 to be monitored by monitoring device 101 as discussed in conjunction with FIG. 4, resetting the maximum distance monitored unit 102 may be located from monitoring device 101 as discussed in conjunction with FIG. 2, inputting a unit 102 to be deactivated as discussed in conjunction with FIG. 5. Output may be received by the user of monitoring device 101 through LED's 107 and/or buzzer 108, e.g., outputting an indication that monitored unit 102 is located beyond a pre-selected percentage, e.g., 90%, of a pre-selected maximum distance, e.g., 1,400 feet, as discussed in conjunction with FIG. 2, outputting an indication that the monitored unit 102 is located beyond the pre-selected maximum distance as discussed in conjunction with FIG. 2. It is noted that monitoring device 101 may comprise other types of input/output devices, e.g., display, alphanumeric characters, not illustrated and that such input/output devices would be known to a person of ordinary skill in the art. It is further noted that embodiments incorporating such input/output devices would fall within the scope of the present invention.
  • Transmitter/[0028] receiver circuit 109 may be configured to transmit information to and receive information from monitored unit 102. When information is transmitted to monitored unit 102, a unique identification code, e.g., a unique 8-bit identification number, may be transmitted along as part of the transmitted information. This unique identification code may be continually changed during every communication with monitored unit 102 using an algorithm stored in memory (not shown) of SoC 103. This is commonly referred to as “rolling code.” The same algorithm may be used by monitored unit 102 to thereby expect the next identification code to be transmitted by monitoring device 101. If the expected identification code is not received, then monitored unit 102 will not respond to the received transmission. Similarly, monitoring device 101 expects to receive a particular identification code from monitored unit 102 using the same algorithm. If the expected identification code is not received, then SoC 103 will not respond to the received transmission.
  • [0029] Antenna switch 110 may be configured to activate Yagi antenna 111 to receive transmitted information, e.g., when monitoring device 101 operates in “locate mode” to track the location of monitored unit 102 such as when the 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 FIGS. 2 and 6, respectively. Yagi antennas are well known to persons of ordinary skill in the art and will therefore not be discussed in detail for the sake of brevity. Consequently, Yagi antenna 111 may be activated to determine the direction of monitored unit 102.
  • [0030] Antenna switch 110 may also be configured to activate an omni directional antenna 112 when monitoring device 101 transmits information to one or more monitored units 102.
  • It is noted that other features of [0031] monitoring device 101 will be discussed further below in conjunction with FIGS. 2-6.
  • Returning to FIG. 1, monitored [0032] unit 102 may comprise a System On a Chip (SoC) 113 coupled to a battery 114, button(s) and/or switch(es) 115, tamper sensor 116, and a transmitter/receiver circuit 117. Transmitter/receiver circuit 117 may be coupled to an omni directional antenna 118. It is noted that monitored unit 102 may comprise different circuitry providing the same functionality as discussed herein and that FIG. 1 is illustrative.
  • [0033] SoC 113 may be configured similarly as SoC 103. In one embodiment, SoC 113 may be configured to comprise a memory (not shown), e.g., non-volatile memory, to store a program for transmitting an indication that monitored unit 102 has been tampered with as well as transmitting signals in a “panic state” as described further below in conjunction with FIG. 6. Further, the program stored in memory (not shown) may include the functionality to deactivate monitored unit 102 as described further below in conjunction with FIG. 5. Further, the program stored in memory (not shown) may store the same algorithm as stored in monitoring device 101 in order to produce the same “rolling code” as monitoring/tracing device 101 as discussed above. SoC 113 may further comprise a processor (not shown) coupled to the memory (not shown). The processor (not shown) may be configured to execute the instructions of the programs listed above. It is noted that the steps of the methods performed by the program mentioned above may in an alternative embodiment be implemented in hardware such as in an Application Specific Integrated Circuit (ASIC).
  • [0034] Battery 114 may supply the necessary operating power for the circuitry and components of monitored unit 102. Battery 114 may be a standard carbon or lithium battery, or a rechargeable type battery such as nickel metal hydride (NiMH) or nickel cadmium (NiCAD).
  • Monitored [0035] unit 102 may comprise input devices such as button(s)/switch(es) 116. These devices may be used by the user of monitored unit 102 to input data to monitored unit 102. It is noted that monitored unit 102 may comprise other types of input devices as well as output devices, e.g., display, alphanumeric characters, not illustrated and that such input/output devices would be known to a person of ordinary skill in the art. It is further noted that embodiments incorporating such input/output devices would fall within the scope of the present invention.
  • [0036] Tamper sensor 116 may be configured to detect monitored unit 102 being tampered with such as removing monitored unit 102 from an object. Upon detecting monitored unit 102 being tampered with, tamper sensor 116 may be configured to transmit a signal to SoC 113 indicating that monitored unit 102 has been tampered with. SoC 113 may then transmit a signal indicating monitored unit 102 has been tampered with to monitoring device 101 as discussed in conjunction with FIG. 6.
  • Transmitter/[0037] receiver circuit 117 may be configured similarly as transmitter/receiver circuit 109. Transmitter/receiver circuit 117 may be configured to transmit information to and receive information from monitoring device 101 via omni directional antenna 118. Omni directional antenna 118 is configured similarly as omni directional antenna 112.
  • When information is transmitted to [0038] monitoring device 102, a unique identification code, e.g., a unique 8-bit identification number, may be transmitted along as part of the transmitted information. As stated above, this unique identification code may be continually changed during every communication with a monitored unit using an algorithm stored in memory (not shown) in SoC 113. This is the same algorithm used by monitoring device 101 to thereby expect the next identification code to be transmitted by monitoring device 101. If the expected identification code is not received, then SoC 113 will not respond to the received transmission.
  • FIG. 2—Method for Finding an Object [0039]
  • FIG. 2 is a flowchart of one embodiment of the present invention of a [0040] method 200 for finding unit 102 (FIG. 1) attached to an object. As stated in the Background Information section, prior art locating systems did not transmit an identification code that changes upon every communication between a monitoring device and a monitored unit. Consequently, a third party, e.g., potential abductor, may be able to intercept the signal and with a similar monitoring device locate the object, e.g., child, attached to the monitored unit. If, however, the object, e.g., child, automobile, was identified by an identification code that changed during every communication between a monitoring device and the monitored unit attached to the object (commonly referred to as “rolling code”), then a third party would be less likely to associate the identification code with the monitored object. It would therefore be desirable to develop a directional finding system that implements a rolling code between the monitoring device and the monitored unit to lessen the ability of a third party to locate the object, e.g., person, automobile, attached to the monitored unit. Method 200 is a method for finding an object, e.g., person, automobile, where the communication between the monitoring device and the monitored unit attached to the object implements a rolling code.
  • Referring to FIG. 2, in conjunction with FIG. 1, in [0041] step 201, monitoring device 101 may be activated upon insertion of the appropriate activation unit 104 as discussed above. In one embodiment, monitoring device 101 may be activated for a limited duration or stage of operation, e.g., day 0 to day 90 in operation, only by inserting the appropriate activation unit 104 in monitoring device 101 containing the appropriate activation code. Upon expiration of that stage of operation, e.g., day 0 to day 90 in operation, monitoring device 101 may be activated for the next stage of operation, e.g., day 91 to day 180 in operation, upon insertion of the appropriate activation unit 104 containing the appropriate activation code.
  • In [0042] step 202, monitoring device 101 may receive input as to which one or more units 102 (“monitored units”) are to be monitored by monitoring device 101. Step 202 may comprise sub-steps as illustrated in FIG. 3.
  • Referring to FIG. 3, in [0043] step 301, monitoring device 101 may read a unique identification code, e.g., 8-bit identification number, in unit 102 to be monitored by monitoring device 101. In one embodiment, the identification code may be stored in memory of SoC 113. In one embodiment, each monitored unit 102 may be assigned a unique identification code. In step 302, the identification code read may be stored in memory (not shown) of SoC 103. This may be valuable in case the object has been abducted or stolen and the authorities, e.g., police, want to locate the monitored unit 102 attached to the object with their own monitoring device 101. In one embodiment, the authorities may able to use their own monitoring device 101 to locate unit 102 by appending a bit, referred to herein as an emergency bit, to the unique identification code stored in memory of SoC 103 in step 302. Unit 102 may be configured to respond to a signal containing its unique identification code with an appropriate appended value.
  • In [0044] step 303, the algorithm that generates a rolling code, as discussed above, may be implemented by monitoring device 101. In one embodiment, the algorithm may be stored in memory of SoC 103. In step 304, monitoring device 101 may transmit a command to monitored unit 102 to implement the same algorithm to generate a rolling code. In one embodiment, the algorithm may be stored in memory of SoC 113.
  • In [0045] step 305, monitored unit 102 whose identification code was read by monitoring device 101 may be assigned a particular LED 107 on monitoring device 101. In this manner, one or more monitored units 102 may be associated with a particular LED 107 on monitoring device 101. As will later be discussed, the user of monitoring device 101 may be informed of a particular monitored unit 102 being located beyond a pre-selected maximum distance from monitoring device 101 by having LED 107 associated with that particular monitored unit 102 light up. Similarly, as will later be discussed, the user of monitoring device 101 may be informed of a particular monitored unit 102 being tampered with by having LED 107 associated with that particular monitored unit 102 light up.
  • Returning to FIG. 2, in [0046] step 203, monitoring device 101 may receive input from the user of monitoring device 101 establishing a maximum distance each unit 102 to be monitored by monitoring device 101 should be located from monitoring device 101. For example, a user of monitoring device 101, e.g., parent, may establish a limit, e.g., 250 feet, the object, e.g., child, attached to unit 102 may be located from the user of monitoring device 101. It is noted for clarity that monitoring device 101 may be configured to monitor and find unit 102 located beyond this maximum distance established by the user of monitoring device 101. This maximum distance may be a distance within the range monitoring device 101 may monitor unit 102. For example, monitoring device 101 may be configured to monitor unit 102 located within two miles from monitoring device 101. In one embodiment, the user may input the maximum distance through an input device, e.g., button/switch 106, alphanumeric keypad, on monitoring device 101. It is noted for clarity that the user of monitoring device 101 may input to monitoring device 101 a separate maximum distance for each monitored unit 102 to be monitored by monitoring device 101.
  • In [0047] step 204, monitoring device 101 may poll each unit 102 to be monitored periodically using a rolling code. That is, monitoring device 101 may transmit a query to each monitored unit 102. Monitoring device 101 may transmit along with the query an updated identification code, e.g., update the identification code stored in memory of SoC 103 in step 302 (FIG. 3), generated by an algorithm stored in memory (not shown) of SoC 103. As stated above, monitored unit 102 will only respond to the query if the updated identification code is expected. The expected updated identification code is determined by the same algorithm stored in memory (not shown) of SoC 113.
  • In [0048] step 205, monitoring device 101 may receive an acknowledgment from the appropriate monitored unit 102 that includes an updated identification code. The acknowledgment may further include the status, e.g., no tampering of monitored unit 102, of monitored unit 102. As stated above, SoC 113 of monitored unit 102 may generate an updated identification code with respect to the identification code received from monitoring device 101. In step 206, monitoring device 101 may determine if the received identification code is recognized, i.e., expected. As stated above, the expected updated identification code is determined by the algorithm stored in memory (not shown) of SoC 103.
  • If the updated identification code is not expected, then monitoring [0049] device 101 may poll each monitored unit 102 using a rolling code in step 204.
  • If the updated identification code is expected, then monitoring [0050] device 101, in step 207, may determine an approximate distance the recognized monitored unit 102 is located monitoring device 101. In one embodiment, monitoring device 101 may determine the approximate distance the recognized monitored unit 102 is located from monitoring device 101 based on the strength of the received signal, i.e., based on the strength of the acknowledgment received in step 205.
  • In [0051] step 208, monitoring device 101 may determine if there are any monitored units 102 located beyond a pre-selected percentage, e.g., ninety percent (90%), of the maximum distance, e.g., 2,000 feet, monitored unit 102 is to be located from monitoring device 101. As stated above, the maximum distance monitored unit 102 may be located from monitoring device 101 may be established in step 203. It is noted that the user of monitoring device 101 may also input to monitoring device 101 a separate pre-selected percentage, e.g., eighty percent (80%), for each monitored unit 102 such as in step 203.
  • If there are no monitored [0052] units 102 located beyond a pre-selected percentage, e.g., ninety percent (90%), of the maximum distance monitored unit 102 is to be located from monitoring device 101, then monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204.
  • It there are any monitored [0053] units 102 located beyond a pre-selected percentage, e.g., ninety percent (90%), of the maximum distance monitored unit 102 is to be located from monitoring device 101, then monitoring device 101, in step 209, may determine if there are any monitored units 102 located beyond the maximum distance monitored unit 102 is to be located from monitoring device 101.
  • If there are any monitored [0054] units 102 located beyond the pre-selected percentage of the maximum distance monitored unit 102 is to be located from monitoring device 101 but not located beyond such maximum distance, then monitoring device 101, in step 210, may output an indication indicating that one or more monitored units 102 are located beyond the pre-selected percentage of the maximum distance but are not located beyond the maximum distance. For example, monitoring device 101 may light a particular LED 107 associated with each monitored unit 102 located beyond the pre-selected percentage, e.g., 90%, of the maximum distance, e.g., 2,000 feet, monitored unit 102 is to be located from monitoring device 101 but not located beyond the maximum distance. It is noted that there other means for indicating each monitored unit 102 that is located beyond the pre-selected percentage of the maximum distance but not located beyond the maximum distance and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments implementing such means would fall within the scope of the present invention.
  • Upon outputting an indication indicating one or more [0055] monitored units 102 are located beyond the pre-selected percentage of the maximum distance but not located beyond the maximum distance, monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204.
  • If, however, there are any monitored [0056] units 102 located beyond the maximum distance monitored unit 102 is to be located from monitoring device 101, then monitoring device 101, in step 211, may output an indication indicating one or more monitored units 102 located beyond the maximum distance established in step 203. For example, monitoring device 101 may light a particular LED 107 associated with each monitored unit 102 located beyond the maximum distance monitored unit 102 is to be located from monitoring device 101. In another example, monitoring device 101 may trigger buzzer 108. It is noted that there other means for indicating each monitored unit 102 that is located beyond the maximum distance and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments implementing such means would fall within the scope of the present invention.
  • In [0057] step 212, monitoring device 101 may determine if the maximum distance monitored unit 102 (referring to monitored unit 102 that was indicated as being located beyond the maximum distance established in step 203) is to be located from monitoring device 101 is to be reset.
  • If the maximum distance is to be reset, then monitoring device, in [0058] step 213, may receive input from the user of monitoring device 101 to reset the maximum distance. In one embodiment, the user may reset the maximum distance through an input device, e.g., button/switch 106, alphanumeric keypad, on monitoring device 101.
  • Upon resetting the maximum distance, [0059] monitoring device 101 may poll each monitored unit 102 using a rolling code in step 204.
  • If, however, the maximum distance monitored [0060] unit 102 is to be located from monitoring device 101 is not to be reset by the user of monitoring device 101, then monitoring device 101 may enter a mode, commonly referred to as a “locate mode”, where monitoring device 101 may transmit queries to monitored unit 102 located beyond the maximum distance in a substantially continuous manner. It is noted that queries may include a rolling identification code as discussed above.
  • In [0061] step 215, monitoring device 101 may receive acknowledgments from that monitored unit 102 located beyond the pre-selected maximum distance monitored unit 102 is to be located from monitoring device 101. It is noted that the acknowledgments may include a rolling identification code as discussed above. In step 216, monitoring device 101 may determine the direction of that monitored unit 102 via signal strength and direction of the received acknowledgments.
  • [0062] Monitoring device 101 may be configured to perform various background processes, e.g., adding a new unit 102 to be monitored by monitoring device 101, deactivating a monitored unit 102 currently being monitored, while monitoring device 101 locates one or more monitored units 102 as discussed above in method 102. Some of these background processes are discussed in greater detail in FIGS. 4-5.
  • It is noted that [0063] method 102 may be executed in a different order presented and that the order presented in the discussion of FIG. 2 is illustrative. It is further noted that certain steps in FIG. 2 may be executed almost concurrently.
  • FIG. 4—Method for Adding a Unit to be Monitored by Monitoring Device [0064]
  • FIG. 4 is a flowchart of one embodiment of the present invention of a [0065] method 400 of a background process for adding unit 102 (FIG. 1) to be monitored by monitoring device 101 (FIG. 1).
  • Referring to FIG. 4, in conjunction with FIG. 1, in [0066] step 401, monitoring device 101 may receive input to add unit 102 to be monitored by monitoring device 101. In one embodiment, the user of monitoring device 101 may input the request to monitor an additional unit 102 via button(s)/switch(es) 106. It is noted that there other means for the user of monitoring device 101 to input the request to monitor an additional unit 102 and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments incorporating such means would fall within the scope of the present invention.
  • In [0067] step 402, monitoring device 101 may read a unique identification code, e.g., 8-bit identification number, from unit 102 to be monitored by monitoring device 101. In one embodiment, the identification code may be stored in memory of SoC 113. In one embodiment, each monitored unit 102 may be assigned a unique identification code. In step 403, the identification code read may be stored in memory (not shown) of SoC 103. This may be valuable in case the object has been abducted or stolen and the authorities, e.g., police, want to locate the monitored unit 102 attached to the object with their own monitoring device 101. In one embodiment, the authorities may able to use their own monitoring device 101 to locate unit 102 by appending a bit, referred to herein as an emergency bit, to the unique identification code stored in memory of SoC 103 in step 403. Unit 102 may be configured to respond to a signal containing its unique identification code with an appropriate appended value.
  • In [0068] step 404, the algorithm that generates a rolling code, as discussed above, may be implemented by monitoring device 101. In one embodiment, the algorithm may be stored in memory of SoC 103. In step 405, monitoring device 101 may transmit a command to monitored unit 102 to implement the same algorithm to generate a rolling code. In one embodiment, the algorithm may be stored in memory of SoC 113.
  • In [0069] step 406, monitored unit 102 whose identification code was read by monitoring device 101 may be assigned a particular LED 107 on monitoring device 101. In this manner, the additional unit 102 to be monitored may be associated with a particular LED 107 on monitoring device 101.
  • It is noted that [0070] method 400 may be executed in a different order presented and that the order presented in the discussion of FIG. 4 is illustrative. It is further noted that certain steps in FIG. 4 may be executed almost concurrently.
  • FIG. 5—Method for Deactivating a Monitored Unit from being Monitored by Monitoring Device [0071]
  • FIG. 5 is a flowchart of one embodiment of the present invention of a [0072] method 500 of a background process for deactivating monitored unit 102 (FIG. 1) from being monitored by monitoring device 101 (FIG. 1).
  • Referring to FIG. 5, in conjunction with FIG. 1, in [0073] step 501, monitoring device 101 may receive input to deactivate unit 102 from being monitored by monitoring device 101. In one embodiment, the user of monitoring device 101 may input the request to stop monitoring unit 102 via button(s)/switch(es) 106. It is noted that there other means for the user of monitoring device 101 to input the request to stop monitoring unit 102 and that such means would be recognized by an artisan of ordinary skill in the art. It is further noted that embodiments incorporating such means would fall within the scope of the present invention.
  • In [0074] step 502, monitoring device 101 may transmit a deactivation request to unit 102 to be deactivated. In step 503, monitored unit 102 may receive a response from monitored unit 102 indicating that unit 102 will be deactivated. In step 504, monitored unit 102 receiving the deactivation request may be deactivated. Upon deactivation, monitored unit 102 may erase the rolling code stored in its memory of SoC 113 in step 505. In step 506, monitoring device 101 may erase the identification code associated with the deactivated unit 102 stored in memory of 103 SoC in step 302 (FIG. 3) or in step 403 (FIG. 4). Monitoring device 101 may further erase the rolling code associated with the deactivated unit 102 in step 506. In step 507, monitoring device 101 may cause LED 107 assigned to the deactivated monitored unit 102 to become available to be assigned to another unit 102.
  • It is noted that steps [0075] 501-503 and 506-507 may be performed by monitoring device 101. It is further noted that steps 504-505 may be performed by monitored unit 102. It is further noted that method 500 may be executed in a different order presented and that the order presented in the discussion of FIG. 5 is illustrative, e.g., steps 503-505 may be executed in a different order. It is further noted that certain steps in FIG. 5, e.g., steps 504-507, may be executed almost concurrently.
  • FIG. 6—Method for Finding a Monitored Unit That has Been Tampered [0076]
  • FIG. 6 is a flowchart of one embodiment of the present invention of a [0077] method 600 for finding monitored unit 102 (FIG. 1) that has been tampered with.
  • Referring to FIG. 6, in conjunction with FIG. 1, in [0078] step 601, monitored unit 102 may detect it being tampered with. In one embodiment, monitored unit 102 may detect any tampering via tamper sensor 106.
  • In [0079] step 602, the tampered monitored unit 102 may transmit an indication to monitoring device 101 that it has been tampered with. In step 603, monitoring device 101 may receive the indication that monitored unit 102 has been tampered with.
  • In [0080] step 604, the tampered monitored unit 102 may enter a mode, commonly referred to as “panic mode”, where the tampered monitored unit 102 transmits signals in a substantially continuous manner. It is noted that transmissions may include a rolling identification code as discussed above.
  • In [0081] step 605, monitoring device 101 may receive the transmitted signals from the tampered monitored unit 102. In step 606, monitoring device 101 may determine the direction of the tampered monitored unit 102 via signal strength and direction of the received signals.
  • It is noted that steps [0082] 601-602 and 604 may be performed by monitored unit 102. It is further noted that steps 603 and 605-606 may be performed by monitoring device 101. It is further noted that method 600 may be executed in a different order presented and that the order presented in the discussion of FIG. 6 is illustrative, e.g., steps 603-605 may be executed in a different order. It is further noted that certain steps in FIG. 6 may be executed almost concurrently, e.g., steps 602 and 604.
  • Although the system 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. [0083]

Claims (45)

1. A method for finding an object comprising the steps of:
receiving input to monitor a unit by a monitoring device, wherein said monitored unit is assigned a first code;
receiving input to establish a maximum distance said monitored unit can be located from said monitoring device;
polling said monitored unit with a second code;
receiving an acknowledgement from said monitored unit with a third code; and
determining an approximate distance said monitored unit is located from said monitoring device.
2. The method as recited in claim 1 further comprising the step of:
activating said monitoring device.
3. The method as recited in claim 2, wherein the step of activating said monitoring device comprises plugging an activation unit in said monitoring device.
4. The method as recited in claim 3, wherein said activation unit activates said monitoring device for a limited duration.
5. The method as recited in claim 1 further comprising the step of:
determining if said approximate distance said monitored unit is located from said monitoring device is beyond a pre-selected percentage of said maximum distance said monitored unit can be located from said monitoring device.
6. The method as recited in claim 5, wherein if said monitored unit is located beyond said pre-selected percentage of said maximum distance said monitored unit can be located from said monitoring device then the method further comprises the step of:
determining if said monitored unit is located beyond said maximum distance said monitored unit can be located from said monitoring device.
7. The method as recited in claim 6, wherein if said monitored unit is not located beyond said maximum distance said monitored unit can be located from said monitoring device, then the method further comprises the step of:
outputting an indication that said monitored unit is located beyond said pre-selected percentage of said maximum distance said monitored unit can be located from said monitoring device.
8. The method as recited in claim 6, wherein if said monitored unit is located beyond said maximum distance said monitored unit can be located from said monitoring device, then the method further comprises the step of:
outputting an indication that said monitored unit is located beyond said maximum distance said monitored unit can be located from said monitoring device.
9. The method as recited in claim 8 further comprising the step of:
transmitting queries to said monitored unit in a substantially continuous manner.
10. The method as recited in claim 9 further comprising the step of:
receiving acknowledgments from said monitored unit.
11. The method as recited in claim 10 further comprising the step of:
determining a direction of said monitored unit from a signal strength and a direction of said acknowledgments.
12. The method as recited in claim 8 further comprising the step of:
resetting a maximum distance said monitored unit can be located from said monitoring device.
13. The method as recited in claim 1, wherein said step of receiving input to monitor said monitored unit comprises the step of:
reading said first code from said monitored unit.
14. The method as recited in claim 13, wherein said step of receiving input to monitor said monitored unit comprises the step of:
storing said received first code.
15. The method as recited in claim 13, wherein said step of receiving input to monitor said monitored unit comprises the step of:
assigning said monitored unit to a light emitting diode on said monitoring device.
16. The method as recited in claim 1 further comprising the step of:
receiving an indication that said monitored unit has been tampered with.
17. The method as recited in claim 16 further comprising the step of:
transmitting queries to said monitored unit in a substantially continuous manner.
18. The method as recited in claim 17 further comprising the step of:
receiving acknowledgments from said monitored unit.
19. The method as recited in claim 18 further comprising the step of:
determining a direction of said monitored unit from a signal strength and a direction of said acknowledgments.
20. The method as recited in claim 1 further comprising the step of:
determining if said third code is recognized.
21. The method as recited in claim 20, wherein if said third code is recognized, then the method further comprises the step of:
transmitting a fourth code to said monitored unit.
22. A system, comprising:
a monitoring device configured to monitor a position of a monitored unit attached to an object, wherein said monitoring device comprises:
circuitry operable for receiving input to monitor said monitored unit, wherein said monitored unit is assigned a first code;
circuitry operable for receiving input to establish a maximum distance said monitored unit can be located from said monitoring device;
circuitry operable for polling said monitored unit with a second code;
circuitry operable for receiving an acknowledgement from said monitored unit with a third code; and
circuitry operable for determining an approximate distance said monitored unit is located from said monitoring device.
23. The system as recited in claim 22, wherein said monitoring device is activated upon plugging in an activation unit.
24. The system as recited in claim 23, wherein said activation unit activates said monitoring device for a limited duration.
25. The system as recited in claim 22, wherein said monitoring device further comprises:
circuitry operable for determining if said approximate distance said monitored unit is located from said monitoring device is beyond a pre-selected percentage of said maximum distance said monitored unit can be located from said monitoring device.
26. The system as recited in claim 25, wherein if said monitored unit is located beyond said pre-selected percentage of said maximum distance said monitored unit can be located from said monitoring device then said monitoring device further comprises:
circuitry operable for determining if said monitored unit is located beyond said maximum distance said monitored unit can be located from said monitoring device.
27. The system as recited in claim 26, wherein if said monitored unit is not located beyond said maximum distance said monitored unit can be located from said monitoring device, then said monitoring device further comprises:
circuitry operable for outputting an indication that said monitored unit is located beyond said pre-selected percentage of said maximum distance said monitored unit can be located from said monitoring device.
28. The system as recited in claim 26, wherein if said monitored unit is located beyond said maximum distance said monitored unit can be located from said monitoring device, then said monitoring device further comprises:
circuitry operable for outputting an indication that said monitored unit is located beyond said maximum distance said monitored unit can be located from said monitoring device.
29. The system as recited in claim 28, wherein said monitoring device further comprises:
circuitry operable for transmitting queries to said monitored unit in a substantially continuous manner.
30. The system as recited in claim 29, wherein said monitoring device further comprises:
circuitry operable for receiving acknowledgments from said monitored unit.
31. The system as recited in claim 30, wherein said monitoring device further comprises:
circuitry operable for determining a direction of said monitored unit from a signal strength and a direction of said acknowledgments.
32. The system as recited in claim 28, wherein said monitoring device further comprises:
circuitry operable for resetting a maximum distance said monitored unit can be located from said monitoring device.
33. The system as recited in claim 22, wherein said circuitry operable for receiving input to monitor said monitored unit comprises:
circuitry operable for reading said first code from said monitored unit.
34. The system as recited in claim 33, wherein said circuitry operable for receiving input to monitor said monitored unit comprises:
circuitry operable for storing said received first code.
35. The system as recited in claim 33, wherein said circuitry operable for receiving input to monitor said monitored unit comprises:
circuitry operable for assigning said monitored unit to a light emitting diode on said monitoring device.
36. The system as recited in claim 22, wherein said monitoring device further comprises:
circuitry operable for receiving an indication that said monitored unit has been tampered with.
37. The system as recited in claim 36, wherein said monitoring device further comprises:
circuitry operable for transmitting queries to said monitored unit in a substantially continuous manner.
38. The system as recited in claim 37, wherein said monitoring device further comprises:
circuitry operable for receiving acknowledgments from said monitored unit.
39. The system as recited in claim 38, wherein said monitoring device further comprises:
circuitry operable for determining a direction of said monitored unit from a signal strength and a direction of said acknowledgments.
40. The system as recited in claim 22, wherein said monitoring device further comprises:
circuitry operable for determining if said third code is recognized.
41. The method as recited in claim 40, wherein if said third code is recognized, then said monitoring device further comprises:
circuitry operable for transmitting a fourth code to said monitored unit.
42. A system, comprising:
a monitored unit attached to an object; and
a monitoring device configured to monitor a position of said monitored unit, wherein said monitoring device comprises:
circuitry operable for receiving input to monitor said monitored unit, wherein said monitored unit is assigned a first code;
circuitry operable for receiving input to establish a maximum distance said monitored unit can be located from said monitoring device;
circuitry operable for polling said monitored unit with a second code;
circuitry operable for receiving an acknowledgement from said monitored unit with a third code; and
circuitry operable for determining an approximate distance said monitored unit is located from said monitoring device.
43. A system, comprising:
a monitored unit attached to an object, wherein said monitored unit comprises:
circuitry operable for detecting tampering of said monitored unit;
circuitry operable for transmitting an indication that said monitored unit has been tampered with; and
circuitry operable for transmitting signals in a substantially continuous manner; and
a monitoring device configured to monitor a position of said monitored unit, wherein said monitoring device comprises:
circuitry operable for receiving said indication that said monitored unit has been tampered with;
circuitry operable for receiving said transmitted signals; and
circuitry operable for determining a direction of said monitored unit via a signal strength and a direction of said transmitted signals.
44. A method for finding one or more objects comprising the steps of:
receiving input to monitor one or more units by a monitoring device, wherein each of said one or more units is assigned a unique identification code, wherein each of said one or more units is attached to an object; and
polling each of said one or more units with a rolling identification code.
45. A system, comprising:
a monitoring device, wherein said monitoring device comprises:
a system on a chip (SoC) configured to monitor a unit attached to an object; and
an activation unit coupled to said SoC, wherein said activation unit activates said SoC for a limited duration.
US10/224,643 2002-08-20 2002-08-20 Directional finding system implementing a rolling code Abandoned US20040036597A1 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
US10/224,643 US20040036597A1 (en) 2002-08-20 2002-08-20 Directional finding system implementing a rolling code
AU2003272231A AU2003272231B2 (en) 2002-08-20 2003-08-20 A system for monitoring and locating people and objects
EP03754404A EP1540443A4 (en) 2002-08-20 2003-08-20 A system for monitoring and locating people and objects
US10/644,152 US6778902B2 (en) 2002-08-20 2003-08-20 System for monitoring and locating people and objects
NZ535214A NZ535214A (en) 2002-08-20 2003-08-20 A system for monitoring and locating people and objects
CA002496255A CA2496255A1 (en) 2002-08-20 2003-08-20 A system for monitoring and locating people and objects
PCT/US2003/026201 WO2004019168A2 (en) 2002-08-20 2003-08-20 A system for monitoring and locating people and objects
US10/865,528 US7050906B2 (en) 2002-08-20 2004-06-10 System for monitoring and locating people and objects

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/224,643 US20040036597A1 (en) 2002-08-20 2002-08-20 Directional finding system implementing a rolling code

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US10/644,152 Continuation US6778902B2 (en) 2002-08-20 2003-08-20 System for monitoring and locating people and objects
US10/644,152 Continuation-In-Part US6778902B2 (en) 2002-08-20 2003-08-20 System for monitoring and locating people and objects

Publications (1)

Publication Number Publication Date
US20040036597A1 true US20040036597A1 (en) 2004-02-26

Family

ID=31886839

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/224,643 Abandoned US20040036597A1 (en) 2002-08-20 2002-08-20 Directional finding system implementing a rolling code
US10/644,152 Expired - Fee Related US6778902B2 (en) 2002-08-20 2003-08-20 System for monitoring and locating people and objects
US10/865,528 Expired - Fee Related US7050906B2 (en) 2002-08-20 2004-06-10 System for monitoring and locating people and objects

Family Applications After (2)

Application Number Title Priority Date Filing Date
US10/644,152 Expired - Fee Related US6778902B2 (en) 2002-08-20 2003-08-20 System for monitoring and locating people and objects
US10/865,528 Expired - Fee Related US7050906B2 (en) 2002-08-20 2004-06-10 System for monitoring and locating people and objects

Country Status (6)

Country Link
US (3) US20040036597A1 (en)
EP (1) EP1540443A4 (en)
AU (1) AU2003272231B2 (en)
CA (1) CA2496255A1 (en)
NZ (1) NZ535214A (en)
WO (1) WO2004019168A2 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050171696A1 (en) * 2003-09-08 2005-08-04 Axonn L.L.C. Location monitoring and transmitting device, method, and computer program product using a simplex satellite transmitter
US20060044134A1 (en) * 2004-08-25 2006-03-02 Elliott Robert O Wireless item location monitoring system and method
US20060071798A1 (en) * 2004-10-01 2006-04-06 Kiff Liana M Mobile telephonic device and base station
US20070194924A1 (en) * 2006-02-21 2007-08-23 Karr Lawrence J Electronic Fence Mode Alert System and Method
US20080061978A1 (en) * 2006-08-31 2008-03-13 Dennis Huang Moving object locating apparatus
GB2415072B (en) * 2004-06-07 2008-06-11 Dmatek Ltd A monitoring and tracking network
USRE43740E1 (en) 2006-02-21 2012-10-16 RoundTrip, LLC Reverse locator
WO2012033676A3 (en) * 2010-09-07 2013-04-04 3M Innovative Properties Company A monitoring apparatus background
US20160112982A1 (en) * 2014-06-30 2016-04-21 Michael Babineau System and method for the retention of universal serial bus and wireless communiction enabled devices
US20190204403A1 (en) * 2017-12-29 2019-07-04 Sonitor Technologies As Location Determination System Having Rotating Identifiers for Distinguishing Transmitters

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050190053A1 (en) * 2003-01-24 2005-09-01 Diegane Dione Managing an occupant of a structure during an emergency event
US20050045710A1 (en) * 2003-03-24 2005-03-03 Nicholas Burke Amusement park system
GB2405512B (en) * 2003-08-28 2006-04-05 Paul John Smeaton Apparatus and method for monitoring the position of people and objects
US20050207617A1 (en) * 2004-03-03 2005-09-22 Tim Sarnoff Digital representation of a live event
US7548758B2 (en) * 2004-04-02 2009-06-16 Nortel Networks Limited System and method for peer-to-peer communication in cellular systems
US20070099679A1 (en) * 2005-11-01 2007-05-03 Mikko Saarisalo Wireless near field communication control using device state or orientation
JP2007180917A (en) * 2005-12-28 2007-07-12 Toshiba Corp Information processor and control method
US7667646B2 (en) * 2006-02-21 2010-02-23 Nokia Corporation System and methods for direction finding using a handheld device
US20070229282A1 (en) * 2006-03-31 2007-10-04 Lowes Cynthia A Identification and tracking tag
US7548203B2 (en) * 2006-09-15 2009-06-16 Nokia Corporation Performance and power management in direction of arrival determination by utilizing sensor information
US8606605B2 (en) 2006-09-28 2013-12-10 Lo-Q, Plc Reservation management system and method
FI20075426A0 (en) * 2007-06-08 2007-06-08 Polar Electro Oy Performance meter, transmission method and computer program product
US8260324B2 (en) * 2007-06-12 2012-09-04 Nokia Corporation Establishing wireless links via orientation
US7940177B2 (en) * 2007-06-15 2011-05-10 The Johns Hopkins University System and methods for monitoring security zones
US8183982B2 (en) * 2007-08-14 2012-05-22 Infineon Technologies Ag System including reply signal that at least partially overlaps request
WO2009094451A2 (en) * 2008-01-22 2009-07-30 Board Of Regents, The University Of Texas System Systems, devices and methods for imaging and surgery
US7710830B2 (en) * 2008-09-02 2010-05-04 Accuwalk Llc Outing record device
WO2010026566A1 (en) * 2008-09-04 2010-03-11 Hagai Kaner Apparatus to signal a child's location
US8677342B1 (en) 2008-10-17 2014-03-18 Honeywell International Inc. System, method and apparatus for replacing wireless devices in a system
US9210125B1 (en) 2008-10-17 2015-12-08 Honeywell International Inc. System, method and apparatus for binding communication devices through common association
US8891586B1 (en) 2008-10-17 2014-11-18 Honeywell International Inc. System, apparatus and method for identifying transmission frequencies for communicating data
US8385384B1 (en) 2008-10-17 2013-02-26 Honeywell International Inc. System, method and apparatus for selecting frequency hopping sequences
US8553743B1 (en) 2008-10-17 2013-10-08 Honeywell International Inc. System, apparatus and method for communicating messages using multiple frequency hopping sequences
US8259775B1 (en) 2008-10-17 2012-09-04 Honeywell International, Inc. System, apparatus and method for managing message communications in systems employing frequency hopping
US8169328B2 (en) * 2009-06-09 2012-05-01 Lojack Operating Company, Lp Proximity monitoring and locating system
US9735831B1 (en) * 2009-09-22 2017-08-15 Honeywell International Inc. System, apparatus and method for synchronizing communications between devices
WO2011091283A1 (en) 2010-01-22 2011-07-28 Board Of Regents, The University Of Texas System Systems, devices and methods for imaging and surgery
US8692676B2 (en) 2010-02-01 2014-04-08 Perimeter Technologies Inc. Time of flight animal monitoring
US20110221597A1 (en) * 2010-03-11 2011-09-15 Jameson James L Animal Training Device Having a Programmable Stimulus Delivery Switch
CN102128618B (en) * 2010-12-09 2012-11-21 中国测绘科学研究院 Active dynamic positioning method
US20120182172A1 (en) * 2011-01-14 2012-07-19 Shopper Scientist, Llc Detecting Shopper Presence in a Shopping Environment Based on Shopper Emanated Wireless Signals
KR20140104610A (en) * 2013-02-20 2014-08-29 한국전자통신연구원 Apparatus and method for estimating moving path using visible light communication in real time
CN103901458A (en) * 2014-03-14 2014-07-02 中国测绘科学研究院 Dynamic positioning system and method
FR3030052A1 (en) 2014-12-04 2016-06-17 Arnaud Roquel ELECTRONIC DEVICE FOR LOCALIZATION NEAR A LAND OBJECT AND METHOD FOR LOCATING SUCH OBJECT
US10320442B1 (en) 2018-02-09 2019-06-11 Ademco Inc. High bandwidth channel in a frequency hopping system

Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5115223A (en) * 1990-09-20 1992-05-19 Moody Thomas O Personnel location monitoring system and method
US5289163A (en) * 1992-09-16 1994-02-22 Perez Carla D Child position monitoring and locating device
US5337041A (en) * 1992-04-13 1994-08-09 Lorri Friedman Personal safety guard system for stray person or pet
US5471404A (en) * 1993-12-23 1995-11-28 Mazer; Murray S. Occlusion detection system for locator devices
US5594425A (en) * 1994-10-31 1997-01-14 Peoplenet, Inc. Locator device
US5603094A (en) * 1994-07-28 1997-02-11 Greear, Jr.; Willie J. Animal tracking system with transmitter attachable to an animal's collar
US5642303A (en) * 1995-05-05 1997-06-24 Apple Computer, Inc. Time and location based computing
US5652570A (en) * 1994-05-19 1997-07-29 Lepkofker; Robert Individual location system
US5689240A (en) * 1996-06-05 1997-11-18 C.O.P. Corp. Child monitor system
US5748103A (en) * 1995-11-13 1998-05-05 Vitalcom, Inc. Two-way TDMA telemetry system with power conservation features
US5857433A (en) * 1996-07-22 1999-01-12 John C. Files Animal training and tracking device having global positioning satellite unit
US5900818A (en) * 1998-04-01 1999-05-04 Televilt International Ac Animal tracking system
US5914671A (en) * 1997-02-27 1999-06-22 Micron Communications, Inc. System and method for locating individuals and equipment, airline reservation system, communication system
US5952958A (en) * 1996-04-05 1999-09-14 Discovision Associates Positioning system and method
US5987421A (en) * 1998-02-05 1999-11-16 Morfun Systems, Inc. Computerized system and method for locating individual members of discrete groups and for electronically registering and holding the ' groups position in waiting lines
US6078260A (en) * 1998-12-21 2000-06-20 Sony Corporation Method and apparatus for keeping track of children
US6130622A (en) * 1998-08-10 2000-10-10 Trw Inc. System and method for remote convenience function control having a rekey security feature
US6169494B1 (en) * 1998-02-20 2001-01-02 Lucent Technologies, Inc. Biotelemetry locator
US6169484B1 (en) * 1998-04-28 2001-01-02 Itt Manufacturing Enterprises, Inc. Personal location system
US6236365B1 (en) * 1996-09-09 2001-05-22 Tracbeam, Llc Location of a mobile station using a plurality of commercial wireless infrastructures
US6249404B1 (en) * 1999-02-04 2001-06-19 Read-Rite Corporation Head gimbal assembly with a flexible printed circuit having a serpentine substrate
US6249252B1 (en) * 1996-09-09 2001-06-19 Tracbeam Llc Wireless location using multiple location estimators
US6297768B1 (en) * 1999-02-25 2001-10-02 Lunareye, Inc. Triggerable remote controller
US6300903B1 (en) * 1998-03-23 2001-10-09 Time Domain Corporation System and method for person or object position location utilizing impulse radio
US20020063626A1 (en) * 1998-07-31 2002-05-30 Pitzer Beryl E. Personal monitoring system

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4884208A (en) * 1988-05-16 1989-11-28 Equipment Tracking Network, Inc. System for continuously establishing and indicating the location of a movable object
WO1993004425A1 (en) * 1991-08-13 1993-03-04 Universal Photonix, Inc. System for remotely validating the identity of indivuals and determining their locations
US5742644A (en) * 1992-03-12 1998-04-21 Ntp Incorporated Receiving circuitry for receiving serially transmitted encoded information
US5694428A (en) * 1992-03-12 1997-12-02 Ntp Incorporated Transmitting circuitry for serial transmission of encoded information
US5751773A (en) * 1992-03-12 1998-05-12 Ntp Incorporated System for wireless serial transmission of encoded information
SE9304119D0 (en) * 1993-12-10 1993-12-10 Ericsson Ge Mobile Communicat Devices and mobile stations for providing packaged data communication in digital TDMA cellular systems
US5650770A (en) 1994-10-27 1997-07-22 Schlager; Dan Self-locating remote monitoring systems
US5722059A (en) * 1995-02-24 1998-02-24 Ntp Incorporated Radio receiver for use in a radio tracking system and a method of operation thereof
US5650769A (en) * 1995-02-24 1997-07-22 Ntp, Incorporated Radio receiver for use in a radio tracking system and a method of operation thereof
US5973601A (en) * 1995-12-06 1999-10-26 Campana, Jr.; Thomas J. Method of radio transmission between a radio transmitter and radio receiver
US5714937A (en) * 1995-02-24 1998-02-03 Ntp Incorporated Omidirectional and directional antenna assembly
US5640146A (en) * 1995-02-24 1997-06-17 Ntp Incorporated Radio tracking system and method of operation thereof
US5621417A (en) 1995-06-07 1997-04-15 General Electric Company Method and mechanism for reduction of within-train reported data
US5771020A (en) 1995-07-26 1998-06-23 Airborne Research Associates, Inc. Lightning locating system
US5714932A (en) * 1996-02-27 1998-02-03 Radtronics, Inc. Radio frequency security system with direction and distance locator
US6492906B1 (en) * 1998-03-23 2002-12-10 Time Domain Corporation System and method using impulse radio technology to track and monitor people under house arrest
US6660418B1 (en) 1998-06-15 2003-12-09 Aer Energy Resources, Inc. Electrical device with removable enclosure for electrochemical cell
US6084517A (en) * 1998-08-12 2000-07-04 Rabanne; Michael C. System for tracking possessions
US6459888B1 (en) * 1998-09-30 2002-10-01 Skyworks Solutions, Inc. Method of estimating carrier frequency in a digital mobile communications system through multiple hypotheses performed on the received signal
US6246376B1 (en) * 2000-06-28 2001-06-12 Texas Instruments Incorporated Wireless location and direction indicator for multiple devices
US6981157B2 (en) * 2000-08-30 2005-12-27 Lucent Technologies Inc. Method and apparatus for ensuring security of users of short range wireless enable devices
US6600418B2 (en) * 2000-12-12 2003-07-29 3M Innovative Properties Company Object tracking and management system and method using radio-frequency identification tags
US6606418B2 (en) * 2001-01-16 2003-08-12 International Business Machines Corporation Enhanced compression of documents
US6563427B2 (en) 2001-09-28 2003-05-13 Motorola, Inc. Proximity monitoring communication system

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5115223A (en) * 1990-09-20 1992-05-19 Moody Thomas O Personnel location monitoring system and method
US5337041A (en) * 1992-04-13 1994-08-09 Lorri Friedman Personal safety guard system for stray person or pet
US5289163A (en) * 1992-09-16 1994-02-22 Perez Carla D Child position monitoring and locating device
US5471404A (en) * 1993-12-23 1995-11-28 Mazer; Murray S. Occlusion detection system for locator devices
US5652570A (en) * 1994-05-19 1997-07-29 Lepkofker; Robert Individual location system
US5603094A (en) * 1994-07-28 1997-02-11 Greear, Jr.; Willie J. Animal tracking system with transmitter attachable to an animal's collar
US5594425A (en) * 1994-10-31 1997-01-14 Peoplenet, Inc. Locator device
US6075458A (en) * 1994-10-31 2000-06-13 Peoplenet, Inc. Locator device
US5642303A (en) * 1995-05-05 1997-06-24 Apple Computer, Inc. Time and location based computing
US5748103A (en) * 1995-11-13 1998-05-05 Vitalcom, Inc. Two-way TDMA telemetry system with power conservation features
US5952958A (en) * 1996-04-05 1999-09-14 Discovision Associates Positioning system and method
US5689240A (en) * 1996-06-05 1997-11-18 C.O.P. Corp. Child monitor system
US5857433A (en) * 1996-07-22 1999-01-12 John C. Files Animal training and tracking device having global positioning satellite unit
US6249252B1 (en) * 1996-09-09 2001-06-19 Tracbeam Llc Wireless location using multiple location estimators
US6236365B1 (en) * 1996-09-09 2001-05-22 Tracbeam, Llc Location of a mobile station using a plurality of commercial wireless infrastructures
US5914671A (en) * 1997-02-27 1999-06-22 Micron Communications, Inc. System and method for locating individuals and equipment, airline reservation system, communication system
US6127917A (en) * 1997-02-27 2000-10-03 Micron Technology, Inc. System and method for locating individuals and equipment, airline reservation system, communication system
US5987421A (en) * 1998-02-05 1999-11-16 Morfun Systems, Inc. Computerized system and method for locating individual members of discrete groups and for electronically registering and holding the ' groups position in waiting lines
US6169494B1 (en) * 1998-02-20 2001-01-02 Lucent Technologies, Inc. Biotelemetry locator
US6300903B1 (en) * 1998-03-23 2001-10-09 Time Domain Corporation System and method for person or object position location utilizing impulse radio
US5900818A (en) * 1998-04-01 1999-05-04 Televilt International Ac Animal tracking system
US6169484B1 (en) * 1998-04-28 2001-01-02 Itt Manufacturing Enterprises, Inc. Personal location system
US20020063626A1 (en) * 1998-07-31 2002-05-30 Pitzer Beryl E. Personal monitoring system
US6130622A (en) * 1998-08-10 2000-10-10 Trw Inc. System and method for remote convenience function control having a rekey security feature
US6078260A (en) * 1998-12-21 2000-06-20 Sony Corporation Method and apparatus for keeping track of children
US6249404B1 (en) * 1999-02-04 2001-06-19 Read-Rite Corporation Head gimbal assembly with a flexible printed circuit having a serpentine substrate
US6297768B1 (en) * 1999-02-25 2001-10-02 Lunareye, Inc. Triggerable remote controller

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110090041A1 (en) * 2003-09-08 2011-04-21 Gary Naden Asset Management Device and Method Using Simplex Satellite Transmitter Augmented with Local Area Transceiver
US20080018496A1 (en) * 2003-09-08 2008-01-24 Ronnie Tanner Asset management device and method using simplex satellite transmitter augmented with local area transceiver
US7337061B2 (en) 2003-09-08 2008-02-26 Axonn, L.L.C. Location monitoring and transmitting device, method, and computer program product using a simplex satellite transmitter
US20050171696A1 (en) * 2003-09-08 2005-08-04 Axonn L.L.C. Location monitoring and transmitting device, method, and computer program product using a simplex satellite transmitter
US20080097687A1 (en) * 2003-09-08 2008-04-24 Gary Naden Location monitoring and transmitting device, method, and computer program product using a simplex satellite transmitter
GB2415072B (en) * 2004-06-07 2008-06-11 Dmatek Ltd A monitoring and tracking network
US20060044134A1 (en) * 2004-08-25 2006-03-02 Elliott Robert O Wireless item location monitoring system and method
US7394364B2 (en) 2004-08-25 2008-07-01 Robert Odell Elliott Wireless item location monitoring system and method
US20060071798A1 (en) * 2004-10-01 2006-04-06 Kiff Liana M Mobile telephonic device and base station
US7652569B2 (en) 2004-10-01 2010-01-26 Honeywell International Inc. Mobile telephonic device and base station
US20070194924A1 (en) * 2006-02-21 2007-08-23 Karr Lawrence J Electronic Fence Mode Alert System and Method
USRE43740E1 (en) 2006-02-21 2012-10-16 RoundTrip, LLC Reverse locator
USRE44526E1 (en) 2006-02-21 2013-10-08 RoundTrip, LLC Electronic fence mode alert system and method
US7592918B2 (en) * 2006-02-21 2009-09-22 Karr Lawrence J Electronic fence mode alert system and method
US20080061978A1 (en) * 2006-08-31 2008-03-13 Dennis Huang Moving object locating apparatus
WO2012033676A3 (en) * 2010-09-07 2013-04-04 3M Innovative Properties Company A monitoring apparatus background
US20160112982A1 (en) * 2014-06-30 2016-04-21 Michael Babineau System and method for the retention of universal serial bus and wireless communiction enabled devices
US20190204403A1 (en) * 2017-12-29 2019-07-04 Sonitor Technologies As Location Determination System Having Rotating Identifiers for Distinguishing Transmitters

Also Published As

Publication number Publication date
WO2004019168A2 (en) 2004-03-04
AU2003272231A1 (en) 2004-03-11
WO2004019168A3 (en) 2004-04-29
AU2003272231B2 (en) 2005-06-09
CA2496255A1 (en) 2004-03-04
US20040039521A1 (en) 2004-02-26
EP1540443A2 (en) 2005-06-15
EP1540443A4 (en) 2010-06-02
US7050906B2 (en) 2006-05-23
NZ535214A (en) 2006-09-29
US6778902B2 (en) 2004-08-17
US20040260463A1 (en) 2004-12-23

Similar Documents

Publication Publication Date Title
US20040036597A1 (en) Directional finding system implementing a rolling code
US5796338A (en) System for preventing loss of cellular phone or the like
US6169494B1 (en) Biotelemetry locator
US7956746B2 (en) Wireless tracking system and method with tag removal detection
US6624754B1 (en) Personal security and tracking system
US9235972B2 (en) Personal security and tracking system
US9087442B2 (en) Panic device with local alarm and distal signaling capability
US6940407B2 (en) Method and apparatus for detecting loss and location of a portable communications device
US6239700B1 (en) Personal security and tracking system
US7696887B1 (en) Person tracking and communication system
US5742233A (en) Personal security and tracking system
US20060023626A1 (en) System and method for preventing loss of personal items
US7872578B2 (en) Tracking, identification, and security system for a portable device
US20030218539A1 (en) Location tracking apparatus, system, and method
US7791469B2 (en) Short range wireless tracking and event notification system for portable devices
WO2004044606A2 (en) Apparatus and method for tracking the location and position of an individual
EP1915746B1 (en) System as well as method for protecting an item to be secured
US7423536B2 (en) Heat sensor activated detector and method
US8564437B2 (en) Security systems and methods
WO2004049630A1 (en) Communications system and method

Legal Events

Date Code Title Description
AS Assignment

Owner name: BLUESPAN, L.L.C., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MAYS, ROBERT JR.;ATILANO, RAYMOND B.;CASE, ROGER P.;AND OTHERS;REEL/FRAME:013285/0106

Effective date: 20020820

AS Assignment

Owner name: BLUESPAN, INC., TEXAS

Free format text: CHANGE OF NAME;ASSIGNOR:BLUESPAN, L.L.C.;REEL/FRAME:016580/0597

Effective date: 20050101

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION