Relaying communications in a wireless sensor system

Information

  • Patent Grant
  • 10573166
  • Patent Number
    10,573,166
  • Date Filed
    Wednesday, December 13, 2017
    7 years ago
  • Date Issued
    Tuesday, February 25, 2020
    4 years ago
Abstract
Various embodiments of wireless ambient sensor unit are presented. The sensor unit may include a wireless transceiver configured to transmit sensor data and to receive instructions. The sensor unit may include a sensor configured to measure an ambient condition. The sensor unit may include a controller in communication with the wireless transceiver and the sensor. The controller may be configured to compare data measured about the ambient condition to a stored threshold while the wireless ambient sensor unit is functioning in a low-power mode. The controller may be configured to exit the low-power mode in response to the comparison of the data with the stored threshold. The controller may be configured to cause the data measured about the ambient condition to be transmitted by the wireless transceiver as one or more messages in response to the comparison to the stored threshold.
Description
BACKGROUND
Field of the Invention

The present invention relates to a wireless sensor unit system providing bi-directional communication between a sensor (e.g., smoke sensor, fire sensor, temperature sensor, water, etc.) and a repeater or base unit in a building protection system.


Description of the Related Art

Maintaining and protecting a building or complex is difficult and costly. Some conditions, such as fires, gas leaks, etc. are a danger to the occupants and the structure. Other malfunctions, such as water leaks in roofs, plumbing, etc. are not necessarily dangerous for the occupants, but can nevertheless cause considerable damage. In many cases, an adverse ambient condition such as water leakage, fire, etc. is not detected in the early stages when the damage and/or danger is relatively small. Sensors can be used to detect such adverse ambient conditions, but sensors present their own set of problems. For example, adding sensors, such as, for example, smoke detectors, water sensors, and the like in an existing structure can be prohibitively expensive due to the cost of installing wiring between the remote sensors and a centralized monitoring device used to monitor the sensors. Adding wiring to provide power to the sensors further increases the cost. Moreover, with regard to fire sensors, most fire departments will not allow automatic notification of the fire department based on the data from a smoke detector alone. Most fire departments require that a specific temperature rate-of-rise be detected before an automatic fire alarm system can notify the fire department. Unfortunately, detecting fire by temperature rate-of-rise generally means that the fire is not detected until it is too late to prevent major damage.


SUMMARY

The present invention solves these and other problems by providing a relatively low cost, robust, wireless sensor system that provides an extended period of operability without maintenance. The system includes one or more intelligent sensor units and a base unit that can communicate with the sensor units. When one or more of the sensor units detects an anomalous condition (e.g., smoke, fire, water, etc.) the sensor unit communicates with the base unit and provides data regarding the anomalous condition. The base unit can contact a supervisor or other responsible person by a plurality of techniques, such as, telephone, pager, cellular telephone, Internet (and/or local area network), etc. In one embodiment, one or more wireless repeaters are used between the sensor units and the base unit to extend the range of the system and to allow the base unit to communicate with a larger number of sensors.


In one embodiment, the sensor system includes a number of sensor units located throughout a building that sense conditions and report anomalous results back to a central reporting station. The sensor units measure conditions that might indicate a fire, water leak, etc. The sensor units report the measured data to the base unit whenever the sensor unit determines that the measured data is sufficiently anomalous to be reported. The base unit can notify a responsible person such as, for example a building manager, building owner, private security service, etc. In one embodiment, the sensor units do not send an alarm signal to the central location. Rather, the sensors send quantitative measured data (e.g., smoke density, temperature rate of rise, etc.) to the central reporting station.


In one embodiment, the sensor system includes a battery-operated sensor unit that detects a condition, such as, for example, smoke, temperature, humidity, moisture, water, water temperature, carbon monoxide, natural gas, propane gas, other flammable gases, radon, poison gasses, etc. The sensor unit is placed in a building, apartment, office, residence, etc. In order to conserve battery power, the sensor is normally placed in a low-power mode. In one embodiment, while in the low power mode, the sensor unit takes regular sensor readings and evaluates the readings to determine if an anomalous condition exists (e.g., block 901 of method 900 of FIG. 9). If an anomalous condition is detected, then the sensor unit “wakes up” (block 902) and begins communicating with the base unit or with a repeater (block 903). At programmed intervals, the sensor also “wakes up” and sends status information to the base unit (or repeater) and then listens for commands for a period of time.


In one embodiment, the sensor unit is bi-directional and configured to receive instructions from the central reporting station (or repeater). Thus, for example, the central reporting station can instruct the sensor to: perform additional measurements; go to a standby mode; wake up; report battery status; change wake-up interval; run self-diagnostics and report results; etc. In one embodiment, the sensor unit also includes a tamper switch. When tampering with the sensor is detected, the sensor reports such tampering to the base unit. In one embodiment, the sensor reports its general health and status to the central reporting station on a regular basis (e.g., results of self-diagnostics, battery health, etc.).


In one embodiment, the sensor unit provides two wake-up modes, a first wake-up mode for taking measurements (and reporting such measurements if deemed necessary), and a second wake-up mode for listening for commands from the central reporting station. The two wake-up modes, or combinations thereof, can occur at different intervals.


In one embodiment, the sensor units use spread-spectrum techniques to communicate with the base unit and/or the repeater units. In one embodiment, the sensor units use frequency-hopping spread-spectrum. In one embodiment, each sensor unit has an Identification code (ID) and the sensor unit attaches its ID to outgoing communication packets. In one embodiment, when receiving wireless data, each sensor unit ignores data that is addressed to other sensor units.


The repeater unit is configured to relay communications traffic between a number of sensor units and the base unit. The repeater units typically operate in an environment with several other repeater units and thus each repeater unit contains a database (e.g., a lookup table) of sensor IDs. During normal operation, the repeater only communicates with designated wireless sensor units whose IDs appears in the repeater's database. In one embodiment, the repeater is battery-operated and conserves power by maintaining an internal schedule of when its designated sensors are expected to transmit and going to a low-power mode when none of its designated sensor units is scheduled to transmit. In one embodiment, the repeater uses spread-spectrum to communicate with the base unit and the sensor units. In one embodiment, the repeater uses frequency-hopping spread-spectrum to communicate with the base unit and the sensor units. In one embodiment, each repeater unit has an ID and the repeater unit attaches its ID to outgoing communication packets that originate in the repeater unit. In one embodiment, each repeater unit ignores data that is addressed to other repeater units or to sensor units not serviced by the repeater.


In one embodiment, the repeater is configured to provide bi-directional communication between one or more sensors and a base unit. In one embodiment, the repeater is configured to receive instructions from the central reporting station (or repeater). Thus, for example, the central reporting station can instruct the repeater to: send commands to one or more sensors; go to standby mode; “wake up”; report battery status; change wake-up interval; run self-diagnostics and report results; etc.


The base unit is configured to receive measured sensor data from a number of sensor units. In one embodiment, the sensor information is relayed through the repeater units. The base unit also sends commands to the repeater units and/or sensor units. In one embodiment, the base unit includes a diskless PC that runs off of a CD-ROM, flash memory, DVD, or other read-only device, etc. When the base unit receives data from a wireless sensor indicating that there may be an emergency condition (e.g., a fire or excess smoke, temperature, water, flammable gas, etc.) the base unit will attempt to notify a responsible party (e.g., a building manager) by several communication channels (e.g., telephone, Internet, pager, cell phone, etc.). In one embodiment, the base unit sends instructions to place the wireless sensor in an alert mode (inhibiting the wireless sensor's low-power mode). In one embodiment, the base unit sends instructions to activate one or more additional sensors near the first sensor.


In one embodiment, the base unit maintains a database of the health, battery status, signal strength, and current operating status of all of the sensor units and repeater units in the wireless sensor system. In one embodiment, the base unit automatically performs routine maintenance by sending commands to each sensor to run a self-diagnostic and report the results. The bases unit collects such diagnostic results. In one embodiment, the base unit sends instructions to each sensor telling the sensor how long to wait between “wakeup” intervals. In one embodiment, the base unit schedules different wakeup intervals to different sensors based on the sensor's health, battery health, location, etc. In one embodiment, the base unit sends instructions to repeaters to route sensor information around a failed repeater.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a sensor system that includes a plurality of sensor units that communicate with a base unit through a number of repeater units.



FIG. 2 is a block diagram of a sensor unit.



FIG. 3 is a block diagram of a repeater unit.



FIG. 4 is a block diagram of the base unit.



FIG. 5 shows one embodiment a network communication packet used by the sensor units, repeater units, and the base unit.



FIG. 6 is a flowchart showing operation of a sensor unit that provides relatively continuous monitoring.



FIG. 7 is a flowchart showing operation of a sensor unit that provides periodic monitoring.



FIG. 8 shows how the sensor system can be used to detected water leaks.



FIG. 9 illustrates a method for using a wireless ambient sensor unit.





DETAILED DESCRIPTION


FIG. 1 shows an sensor system 100 that includes a plurality of sensor units 102-106 that communicate with a base unit 112 through a number of repeater units 110-111. The sensor units 102-106 are located throughout a building 101. Sensor units 102-104 communicate with the repeater 110. Sensor units 105-105 communicate with the repeater 111. The repeaters 110-111 communicate with the base unit 112. The base unit 112 communicates with a monitoring computer system 113 through a computer network connection such as, for example, Ethernet, wireless Ethernet, firewire port, Universal Serial Bus (USB) port, bluetooth, etc. The computer system 113 contacts a building manager, maintenance service, alarm service, or other responsible personnel 120 using one or more of several communication systems such as, for example, telephone 121, pager 122, cellular telephone 123 (e.g., direct contact, voicemail, text, etc.), and/or through the Internet and/or local area network 124 (e.g., through email, instant messaging, network communications, etc.). In one embodiment, multiple base units 112 are provided to the monitoring computer 113. In one embodiment, the monitoring computer 113 is provided to more than one compute monitor, thus allowing more data to be displayed than can conveniently be displayed on a single monitor. In one embodiment, the monitoring computer 113 is provided to multiple monitors located in different locations, thus allowing the data form the monitoring computer 113 to be displayed in multiple locations.


The sensor units 102-106 include sensors to measure conditions, such as, for example, smoke, temperature, moisture, water, water temperature, humidity, carbon monoxide, natural gas, propane gas, security alarms, intrusion alarms (e.g., open doors, broken windows, open windows, and the like), other flammable gases, radon, poison gasses, etc. Different sensor units can be configured with different sensors or with combinations of sensors. Thus, for example, in one installation the sensor units 102 and 104 could be configured with smoke and/or temperature sensors while the sensor unit 103 could be configured with a humidity sensor.


The discussion that follows generally refers to the sensor unit 102 as an example of a sensor unit, with the understanding that the description of the sensor unit 102 can be applied to many sensor units. Similarly, the discussion generally refers to the repeater 110 by way of example, and not limitation. It will also be understood by one of ordinary skill in the art that repeaters are useful for extending the range of the sensor units 102-106 but are not required in all embodiments. Thus, for example in one embodiment, one or more of the sensor units 102-106 can communicate directly with the base unit 112 without going through a repeater. It will also be understood by one of ordinary skill in the art that FIG. 1 shows only five sensor units (102-106) and two repeater units (110-111) for purposes of illustration and not by way of limitation. An installation in a large apartment building or complex would typically involve many sensor units and repeater units. Moreover, one of ordinary skill in the art will recognize that one repeater unit can service relatively many sensor units. In one embodiment, the sensor units 102 can communicate directly with the base unit 112 without going through a repeater 111.


When the sensor unit 102 detects an anomalous condition (e.g., smoke, fire, water, etc.) the sensor unit communicates with the appropriate repeater unit 110 and provides data regarding the anomalous condition. The repeater unit 110 forwards the data to the base unit 112, and the base unit 112 forwards the information to the computer 113. The computer 113 evaluates the data and takes appropriate action. If the computer 113 determines that the condition is an emergency (e.g., fire, smoke, large quantities of water), then the computer 113 contacts the appropriate personnel 120. If the computer 113 determines that the situation warrants reporting, but is not an emergency, then the computer 113 logs the data for later reporting. In this way, the sensor system 100 can monitor the conditions in and around the building 101.


In one embodiment, the sensor unit 102 has an internal power source (e.g., battery, solar cell, fuel cell, etc.). In order to conserve power, the sensor unit 102 is normally placed in a low-power mode. In one embodiment, using sensors that require relatively little power, while in the low power mode the sensor unit 102 takes regular sensor readings and evaluates the readings to determine if an anomalous condition exists. In one embodiment, using sensors that require relatively more power, while in the low power mode the sensor unit 102 takes and evaluates sensor readings at periodic intervals. If an anomalous condition is detected, then the sensor unit 102 “wakes up” and begins communicating with the base unit 112 through the repeater 110. At programmed intervals, the sensor unit 102 also “wakes up” and sends status information (e.g., power levels, self-diagnostic information, etc.) to the base unit (or repeater) and then listens for commands for a period of time. In one embodiment, the sensor unit 102 also includes a tamper detector. When tampering with the sensor unit 102 is detected, the sensor unit 102 reports such tampering to the base unit 112.


In one embodiment, the sensor unit 102 provides bi-directional communication and is configured to receive data and/or instructions from the base unit 112. Thus, for example, the base unit 112 can instruct the sensor unit 102 to perform additional measurements, to go to a standby mode, to wake up, to report battery status, to change wake-up interval, to run self-diagnostics and report results, etc. In one embodiment, the sensor unit 102 reports its general health and status on a regular basis (e.g., results of self-diagnostics, battery health, etc.).


In one embodiment, the sensor unit 102 provides two wake-up modes, a first wake-up mode for taking measurements (and reporting such measurements if deemed necessary), and a second wake-up mode for listening for commands from the central reporting station. The two wake-up modes, or combinations thereof, can occur at different intervals.


In one embodiment, the sensor unit 102 use spread-spectrum techniques to communicate with the repeater unit 110. In one embodiment, the sensor unit 102 uses frequency-hopping spread-spectrum. In one embodiment, the sensor unit 102 has an address or identification (ID) code that distinguishes the sensor unit 102 from the other sensor units. The sensor unit 102 attaches its ID to outgoing communication packets so that transmissions from the sensor unit 102 can be identified by the repeater 110. The repeater 110 attaches the ID of the sensor unit 102 to data and/or instructions that are transmitted to the sensor unit 102. In one embodiment, the sensor unit 102 ignores data and/or instructions that are addressed to other sensor units.


In one embodiment, the sensor unit 102 includes a reset function. In one embodiment, the reset function is activated by the reset switch 208. In one embodiment, the reset function is active for a prescribed interval of time. During the reset interval, the transceiver 203 is in a receiving mode and can receive the identification code from an external programmer. In one embodiment, the external programmer wirelessly transmits a desired identification code. In one embodiment, the identification code is programmed by an external programmer that is connected to the sensor unit 102 through an electrical connector. In one embodiment, the electrical connection to the sensor unit 102 is provided by sending modulated control signals (power line carrier signals) through a connector used to connect the power source 206. In one embodiment, the external programmer provides power and control signals. In one embodiment, the external programmer also programs the type of sensor(s) installed in the sensor unit. In one embodiment, the identification code includes an area code (e.g., apartment number, zone number, floor number, etc.) and a unit number (e.g., unit 1, 2, 3, etc.).


In one embodiment, the sensor communicates with the repeater on the 900 MHz band. This band provides good transmission through walls and other obstacles normally found in and around a building structure. In one embodiment, the sensor communicates with the repeater on bands above and/or below the 900 MHz band. In one embodiment, the sensor, repeater, and/or base unit listen to a radio frequency channel before transmitting on that channel or before beginning transmission. If the channel is in use, (e.g., by another devise such as another repeater, a cordless telephone, etc.) then the sensor, repeater, and/or base unit changes to a different channel. In one embodiment, the sensor, repeater, and/or base unit coordinate frequency hopping by listening to radio frequency channels for interference and using an algorithm to select a next channel for transmission that avoids the interference. Thus, for example, in one embodiment, if a sensor senses a dangerous condition and goes into a continuous transmission mode, the sensor will test (e.g., listen to) the channel before transmission to avoid channels that are blocked, in use, or jammed. In one embodiment, the sensor continues to transmit data until it receives an acknowledgement from the base unit that the message has been received. In one embodiment, the sensor transmits data having a normal priority (e.g., status information) and does not look for an acknowledgement, and the sensor transmits data having elevated priority (e.g., excess smoke, temperature, etc.) until an acknowledgement is received.


The repeater unit 110 is configured to relay communications traffic between the sensor 102 (and, similarly, the sensor units 103-104) and the base unit 112. The repeater unit 110 typically operates in an environment with several other repeater units (such as the repeater unit 111 in FIG. 1) and thus the repeater unit 110 contains a database (e.g., a lookup table) of sensor unit IDs. In FIG. 1, the repeater 110 has database entries for the Ids of the sensors 102-104, and thus the sensor 110 will only communicate with sensor units 102-104. In one embodiment, the repeater 110 has an internal power source (e.g., battery, solar cell, fuel cell, etc.) and conserves power by maintaining an internal schedule of when the sensor units 102-104 are expected to transmit. In one embodiment, the repeater unit 110 goes to a low-power mode when none of its designated sensor units is scheduled to transmit. In one embodiment, the repeater 110 uses spread-spectrum techniques to communicate with the base unit 112 and with the sensor units 102-104. In one embodiment, the repeater 110 uses frequency-hopping spread-spectrum to communicate with the base unit 112 and the sensor units 102-104. In one embodiment, the repeater unit 110 has an address or identification (ID) code and the repeater unit 110 attaches its address to outgoing communication packets that originate in the repeater (that is, packets that are not being forwarded). In one embodiment, the repeater unit 110 ignores data and/or instructions that are addressed to other repeater units or to sensor units not serviced by the repeater 110.


In one embodiment, the base unit 112 communicates with the sensor unit 102 by transmitting a communication packet addressed to the sensor unit 102. The repeaters 110 and 111 both receive the communication packet addressed to the sensor unit 102. The repeater unit 111 ignores the communication packet addressed to the sensor unit 102. The repeater unit 110 transmits the communication packet addressed to the sensor unit 102 to the sensor unit 102. In one embodiment, the sensor unit 102, the repeater unit 110, and the base unit 112 communicate using Frequency-Hopping Spread Spectrum (FHSS), also known as channel-hopping.


Frequency-hopping wireless systems offer the advantage of avoiding other interfering signals and avoiding collisions. Moreover, there are regulatory advantages given to systems that do not transmit continuously at one frequency. Channel-hopping transmitters change frequencies after a period of continuous transmission, or when interference is encountered. These systems may have higher transmit power and relaxed limitations on in-band spurs. FCC regulations limit transmission time on one channel to 400 milliseconds (averaged over 10-20 seconds depending on channel bandwidth) before the transmitter must change frequency. There is a minimum frequency step when changing channels to resume transmission. If there are 25 to 49 frequency channels, regulations allow effective radiated power of 24 dBm, spurs must be −20 dBc, and harmonics must be −41.2 dBc. With 50 or more channels, regulations allow effective radiated power to be up to 30 dBm.


In one embodiment, the sensor unit 102, the repeater unit 110, and the base unit 112 communicate using FHSS wherein the frequency hopping of the sensor unit 102, the repeater unit 110, and the base unit 112 are not synchronized such that at any given moment, the sensor unit 102 and the repeater unit 110 are on different channels. In such a system, the base unit 112 communicates with the sensor unit 102 using the hop frequencies synchronized to the repeater unit 110 rather than the sensor unit 102. The repeater unit 110 then forwards the data to the sensor unit using hop frequencies synchronized to the sensor unit 102. Such a system largely avoids collisions between the transmissions by the base unit 112 and the repeater unit 110.


In one embodiment, the sensor units 102-106 all use FHSS and the sensor units 102-106 are not synchronized. Thus, at any given moment, it is unlikely that any two or more of the sensor units 102-106 will transmit on the same frequency. In this manner, collisions are largely avoided. In one embodiment, collisions are not detected but are tolerated by the system 100. If a collisions does occur, data lost due to the collision is effectively re-transmitted the next time the sensor units transmit sensor data. When the sensor units 102-106 and repeater units 110-111 operate in asynchronous mode, then a second collision is highly unlikely because the units causing the collisions have hopped to different channels. In one embodiment, the sensor units 102-106, repeater units 110-110, and the base unit 112 use the same hop rate. In one embodiment, the sensor units 102-106, repeater units 110-110, and the base unit 112 use the same pseudo-random algorithm to control channel hopping, but with different starting seeds. In one embodiment, the starting seed for the hop algorithm is calculated from the ID of the sensor units 102-106, repeater units 110-110, or the base unit 112.


In an alternative embodiment, the base unit communicates with the sensor unit 102 by sending a communication packet addressed to the repeater unit 110, where the packet sent to the repeater unit 110 includes the address of the sensor unit 102. The repeater unit 102 extracts the address of the sensor unit 102 from the packet and creates and transmits a packet addressed to the sensor unit 102.


In one embodiment, the repeater unit 110 is configured to provide bi-directional communication between its sensors and the base unit 112. In one embodiment, the repeater 110 is configured to receive instructions from the base unit 110. Thus, for example, the base unit 112 can instruct the repeater to: send commands to one or more sensors; go to standby mode; “wake up”; report battery status; change wake-up interval; run self-diagnostics and report results; etc.


The base unit 112 is configured to receive measured sensor data from a number of sensor units either directly, or through the repeaters 110-111. The base unit 112 also sends commands to the repeater units 110-111 and/or to the sensor units 110-111. In one embodiment, the base unit 112 communicates with a diskless computer 113 that runs off of a CD-ROM. When the base unit 112 receives data from a sensor unit 102-111 indicating that there may be an emergency condition (e.g., a fire or excess smoke, temperature, water, etc.) the computer 113 will attempt to notify the responsible party 120.


In one embodiment, the computer 112 maintains a database of the health, power status (e.g., battery charge), and current operating status of all of the sensor units 102-106 and the repeater units 110-111. In one embodiment, the computer 113 automatically performs routine maintenance by sending commands to each sensor unit 102-106 to run a self-diagnostic and report the results. The computer 113 collects and logs such diagnostic results. In one embodiment, the computer 113 sends instructions to each sensor unit 102-106 telling the sensor how long to wait between “wakeup” intervals. In one embodiment, the computer 113 schedules different wakeup intervals to different sensor unit 102-106 based on the sensor unit's health, power status, location, etc. In one embodiment, the computer 113 schedules different wakeup intervals to different sensor unit 102-106 based on the type of data and urgency of the data collected by the sensor unit (e.g., sensor units that have smoke and/or temperature sensors produce data that should be checked relatively more often than sensor units that have humidity or moisture sensors). In one embodiment, the base unit sends instructions to repeaters to route sensor information around a failed repeater.


In one embodiment, the computer 113 produces a display that tells maintenance personnel which sensor units 102-106 need repair or maintenance. In one embodiment, the computer 113 maintains a list showing the status and/or location of each sensor according to the ID of each sensor.


In one embodiment, the sensor units 102-106 and/or the repeater units 110-111 measure the signal strength of the wireless signals received (e.g., the sensor unit 102 measures the signal strength of the signals received from the repeater unit 110, the repeater unit 110 measures the signal strength received from the sensor unit 102 and/or the base unit 112). The sensor units 102-106 and/or the repeater units 110-111 report such signal strength measurement back to the computer 113. The computer 113 evaluates the signal strength measurements to ascertain the health and robustness of the sensor system 100. In one embodiment, the computer 113 uses the signal strength information to re-route wireless communications traffic in the sensor system 100. Thus, for example, if the repeater unit 110 goes offline or is having difficulty communicating with the sensor unit 102, the computer 113 can send instructions to the repeater unit 111 to add the ID of the sensor unit 102 to the database of the repeater unit 111 (and similarly, send instructions to the repeater unit 110 to remove the ID of the sensor unit 102), thereby routing the traffic for the sensor unit 102 through the router unit 111 instead of the router unit 110.



FIG. 2 is a block diagram of the sensor unit 102. In the sensor unit 102, one or more sensors 201 and a transceiver 203 are provided to a controller 202. The controller 202 typically provides power, data, and control information to the sensor(s) 201 and the transceiver 202. A power source 206 is provided to the controller 202. An optional tamper sensor 205 is also provided to the controller 202. A reset device (e.g., a switch) 208 is proved to the controller 202. In one embodiment, an optional audio output device 209 is provided. In one embodiment, the sensor 201 is configured as a plug-in module that can be replaced relatively easily.


In one embodiment, the transceiver 203 is based on a TRF 6901 transceiver chip from Texas Instruments, Inc. In one embodiment, the controller 202 is a conventional programmable microcontroller. In one embodiment, the controller 202 is based on a Field Programmable Gate Array (FPGA), such as, for example, provided by Xilinx Corp. In one embodiment, the sensor 201 includes an optoelectric smoke sensor with a smoke chamber. In one embodiment, the sensor 201 includes a thermistor. In one embodiment, the sensor 201 includes a humidity sensor. In one embodiment, the sensor 201 includes an sensor, such as, for example, a water level sensor, a water temperature sensor, a carbon monoxide sensor, a moisture sensor, a water flow sensor, natural gas sensor, propane sensor, etc.


The controller 202 receives sensor data from the sensor(s) 201. Some sensors 201 produce digital data. However, for many types of sensors 201, the sensor data is analog data. Analog sensor data is converted to digital format by the controller 202. In one embodiment, the controller evaluates the data received from the sensor(s) 201 and determines whether the data is to be transmitted to the base unit 112. The sensor unit 102 generally conserves power by not transmitting data that falls within a normal range. In one embodiment, the controller 202 evaluates the sensor data by comparing the data value to a threshold value (e.g., a high threshold, a low threshold, or a high-low threshold). If the data is outside the threshold (e.g., above a high threshold, below a low threshold, outside an inner range threshold, or inside an outer range threshold), then the data is deemed to be anomalous and is transmitted to the base unit 112. In one embodiment, the data threshold is programmed into the controller 202. In one embodiment, the data threshold is programmed by the base unit 112 by sending instructions to the controller 202. In one embodiment, the controller 202 obtains sensor data and transmits the data when commanded by the computer 113.


In one embodiment, the tamper sensor 205 is configured as a switch that detects removal of or tampering with the sensor unit 102.



FIG. 3 is a block diagram of the repeater unit 110. In the repeater unit 110, a first transceiver 302 and a second transceiver 305 are provided to a controller 303. The controller 303 typically provides power, data, and control information to the transceivers 302, 304. A power source 306 is provided to the controller 303. An optional tamper sensor (not shown) is also provided to the controller 303.


When relaying sensor data to the base unit 112, the controller 303 receives data from the first transceiver 303 and provides the data to the second transceiver 304. When relaying instructions from the base unit 112 to a sensor unit, the controller 303 receives data from the second transceiver 304 and provides the data to the first transceiver 302. In one embodiment, the controller 303 conserves power by powering-down the transceivers 302, 304 during periods when the controller 303 is not expecting data. The controller 303 also monitors the power source 306 and provides status information, such as, for example, self-diagnostic information and/or information about the health of the power source 306, to the base unit 112. In one embodiment, the controller 303 sends status information to the base unit 112 at regular intervals. In one embodiment, the controller 303 sends status information to the base unit 112 when requested by the base unit 112. In one embodiment, the controller 303 sends status information to the base unit 112 when a fault condition (e.g., battery low) is detected.


In one embodiment, the controller 303 includes a table or list of identification codes for wireless sensor units 102. The repeater 303 forwards packets received from, or sent to, sensor units 102 in the list. In one embodiment, the repeater 110 receives entries for the list of sensor units from the computer 113. In one embodiment, the controller 303 determines when a transmission is expected from the sensor units 102 in the table of sensor units and places the repeater 110 (e.g., the transceivers 302, 304) in a low-power mode when no transmissions are expected from the transceivers on the list. In one embodiment, the controller 303 recalculates the times for low-power operation when a command to change reporting interval is forwarded to one of the sensor units 102 in the list (table) of sensor units or when a new sensor unit is added to the list (table) of sensor units.



FIG. 4 is a block diagram of the base unit 112. In the base unit 112, a transceiver 402 and a computer interface 404 are provided to a controller 403. The controller 303 typically provides data and control information to the transceivers 402 and to the interface. The interface 402 is provided to a port on the monitoring computer 113. The interface 402 can be a standard computer data interface, such as, for example, Ethernet, wireless Ethernet, firewire port, Universal Serial Bus (USB) port, bluetooth, etc.



FIG. 5 shows one embodiment a communication packet 500 used by the sensor units, repeater units, and the base unit. The packet 500 includes a preamble portion 501, an address (or ID) portion 502, a data payload portion 503, and an integrity portion 504. In one embodiment, the integrity portion 504 includes a checksum. In one embodiment, the sensor units 102-106, the repeater units 110-111, and the base unit 112 communicate using packets such as the packet 500. In one embodiment, the packets 500 are transmitted using FHSS.


In one embodiment, the data packets that travel between the sensor unit 102, the repeater unit 111, and the base unit 112 are encrypted. In one embodiment, the data packets that travel between the sensor unit 102, the repeater unit 111, and the base unit 112 are encrypted and an authentication code is provided in the data packet so that the sensor unit 102, the repeater unit, and/or the base unit 112 can verify the authenticity of the packet.


In one embodiment the address portion 502 includes a first code and a second code. In one embodiment, the repeater 111 only examines the first code to determine if the packet should be forwarded. Thus, for example, the first code can be interpreted as a building (or building complex) code and the second code interpreted as a subcode (e.g., an apartment code, area code, etc.). A repeater that uses the first code for forwarding thus forwards packets having a specified first code (e.g., corresponding to the repeater's building or building complex). Thus alleviates the need to program a list of sensor units 102 into a repeater, since a group of sensors in a building will typically all have the same first code but different second codes. A repeater so configured, only needs to know the first code to forward packets for any repeater in the building or building complex. This does, however, raise the possibility that two repeaters in the same building could try to forward packets for the same sensor unit 102. In one embodiment, each repeater waits for a programmed delay period before forwarding a packet. Thus reducing the chance of packet collisions at the base unit (in the case of sensor unit to base unit packets) and reducing the chance of packet collisions at the sensor unit (in the case of base unit to sensor unit packets). In one embodiment, a delay period is programmed into each repeater. In one embodiment, delay periods are pre-programmed onto the repeater units at the factory or during installation. In one embodiment, a delay period is programmed into each repeater by the base unit 112. In one embodiment, a repeater randomly chooses a delay period. In one embodiment, a repeater randomly chooses a delay period for each forwarded packet. In one embodiment, the first code is at least 6 digits. In one embodiment, the second code is at least 5 digits.


In one embodiment, the first code and the second code are programmed into each sensor unit at the factory. In one embodiment, the first code and the second code are programmed when the sensor unit is installed. In one embodiment, the base unit 112 can re-program the first code and/or the second code in a sensor unit.


In one embodiment, collisions are further avoided by configuring each repeater unit 111 to begin transmission on a different frequency channel. Thus, if two repeaters attempt to begin transmission at the same time, the repeaters will not interfere with each other because the transmissions will begin on different channels (frequencies).



FIG. 6 is a flowchart showing one embodiment of the operation of the sensor unit 102 wherein relatively continuous monitoring is provided. In FIG. 6, a power up block 601 is followed by an initialization block 602. After initialization, the sensor unit 102 checks for a fault condition (e.g., activation of the tamper sensor, low battery, internal fault, etc.) in a block 603. A decision block 604 checks the fault status. If a fault has occurred, then the process advances to a block 605 were the fault information is transmitted to the repeater 110 (after which, the process advances to a block 612); otherwise, the process advances to a block 606. In the block 606, the sensor unit 102 takes a sensor reading from the sensor(s) 201. The sensor data is subsequently evaluated in a block 607. If the sensor data is abnormal, then the process advances to a transmit block 609 where the sensor data is transmitted to the repeater 110 (after which, the process advances to a block 612); otherwise, the process advances to a timeout decision block 610. If the timeout period has not elapsed, then the process returns to the fault-check block 603; otherwise, the process advances to a transmit status block 611 where normal status information is transmitted to the repeater 110. In one embodiment, the normal status information transmitted is analogous to a simple “ping” which indicates that the sensor unit 102 is functioning normally. After the block 611, the process proceeds to a block 612 where the sensor unit 102 momentarily listens for instructions from the monitor computer 113. If an instruction is received, then the sensor unit 102 performs the instructions, otherwise, the process returns to the status check block 603. In one embodiment, transceiver 203 is normally powered down. The controller 202 powers up the transceiver 203 during execution of the blocks 605, 609, 611, and 612. The monitoring computer 113 can send instructions to the sensor unit 102 to change the parameters used to evaluate data used in block 607, the listen period used in block 612, etc.


Relatively continuous monitoring, such as shown in FIG. 6, is appropriate for sensor units that sense relatively high-priority data (e.g., smoke, fire, carbon monoxide, flammable gas, etc.). By contrast, periodic monitoring can be used for sensors that sense relatively lower priority data (e.g., humidity, moisture, water usage, etc.). FIG. 7 is a flowchart showing one embodiment of operation of the sensor unit 102 wherein periodic monitoring is provided. In FIG. 7, a power up block 701 is followed by an initialization block 702. After initialization, the sensor unit 102 enters a low-power sleep mode. If a fault occurs during the sleep mode (e.g., the tamper sensor is activated), then the process enters a wake-up block 704 followed by a transmit fault block 705. If no fault occurs during the sleep period, then when the specified sleep period has expired, the process enters a block 706 where the sensor unit 102 takes a sensor reading from the sensor(s) 201. The sensor data is subsequently sent to the monitoring computer 113 in a report block 707. After reporting, the sensor unit 102 enters a listen block 708 where the sensor unit 102 listens for a relatively short period of time for instructions from monitoring computer 708. If an instruction is received, then the sensor unit 102 performs the instructions, otherwise, the process returns to the sleep block 703. In one embodiment, the sensor 201 and transceiver 203 are normally powered down. The controller 202 powers up the sensor 201 during execution of the block 706. The controller 202 powers up the transceiver during execution of the blocks 705, 707, and 708. The monitoring computer 113 can send instructions to the sensor unit 102 to change the sleep period used in block 703, the listen period used in block 708, etc.


In one embodiment, the sensor unit transmits sensor data until a handshaking-type acknowledgement is received. Thus, rather than sleep of no instructions or acknowledgements are received after transmission (e.g., after the decision block 613 or 709) the sensor unit 102 retransmits its data and waits for an acknowledgement. The sensor unit 102 continues to transmit data and wait for an acknowledgement until an acknowledgement is received. In one embodiment, the sensor unit accepts an acknowledgement from a repeater unit 111 and it then becomes the responsibility of the repeater unit 111 to make sure that the data is forwarded to the base unit 112. In one embodiment, the repeater unit 111 does not generate the acknowledgement, but rather forwards an acknowledgement from the base unit 112 to the sensor unit 102. The two-way communication ability of the sensor unit 102 provides the capability for the base unit 112 to control the operation of the sensor unit 102 and also provides the capability for robust handshaking-type communication between the sensor unit 102 and the base unit 112.


Regardless of the normal operating mode of the sensor unit 102 (e.g., using the Flowcharts of FIGS. 6, 7, or other modes) in one embodiment, the monitoring computer 113 can instruct the sensor unit 102 to operate in a relatively continuous mode where the sensor repeatedly takes sensor readings and transmits the readings to the monitoring computer 113. Such a mode can be used, for example, when the sensor unit 102 (or a nearby sensor unit) has detected a potentially dangerous condition (e.g., smoke, rapid temperature rise, etc.).



FIG. 8 shows the sensor system used to detect water leaks. In one embodiment, the sensor unit 102 includes a water level sensor and 803 and/or a water temperature sensor 804. The water level sensor 803 and/or water temperature sensor 804 are place, for example, in a tray underneath a water heater 801 in order to detect leaks from the water heater 801 and thereby prevent water damage from a leaking water heater. In one embodiment, a temperature sensor is also provide to measure temperature near the water heater. The water level sensor can also be placed under a sink, in a floor sump, etc. In one embodiment, the severity of a leak is ascertained by the sensor unit 102 (or the monitoring computer 113) by measuring the rate of rise in the water level. When placed near the hot water tank 801, the severity of a leak can also be ascertained at least in part by measuring the temperature of the water. In one embodiment, a first water flow sensor is placed in an input water line for the hot water tank 801 and a second water flow sensor is placed in an output water line for the hot water tank. Leaks in the tank can be detected by observing a difference between the water flowing through the two sensors.


In one embodiment, a remote shutoff valve 810 is provided, so that the monitoring system 100 can shutoff the water supply to the water heater when a leak is detected. In one embodiment, the shutoff valve is controlled by the sensor unit 102. In one embodiment, the sensor unit 102 receives instructions from the base unit 112 to shut off the water supply to the heater 801. In one embodiment, the responsible party 120 sends instructions to the monitoring computer 113 instructing the monitoring computer 113 to send water shut off instructions to the sensor unit 102. Similarly, in one embodiment, the sensor unit 102 controls a gas shutoff valve 811 to shut off the gas supply to the water heater 801 and/or to a furnace (not shown) when dangerous conditions (such as, for example, gas leaks, carbon monoxide, etc.) are detected. In one embodiment, a gas detector 812 is provided to the sensor unit 102. In one embodiment, the gas detector 812 measures carbon monoxide. In one embodiment, the gas detector 812 measures flammable gas, such as, for example, natural gas or propane.


In one embodiment, an optional temperature sensor 818 is provided to measure stack temperature. Using data from the temperature sensor 818, the sensor unit 102 reports conditions, such as, for example, excess stack temperature. Excess stack temperature is often indicative of poor heat transfer (and thus poor efficiency) in the water heater 818.


In one embodiment, an optional temperature sensor 819 is provided to measure temperature of water in the water heater 810. Using data from the temperature sensor 819, the sensor unit 102 reports conditions, such as, for example, over-temperature or under-temperature of the water in the water heater.


In one embodiment, an optional current probe 821 is provided to measure electric current provided to a heating element 820 in an electric water heater. Using data from the current probe 821, the sensor unit 102 reports conditions, such as, for example, no current (indicating a burned-out heating element 820). An over-current condition often indicates that the heating element 820 is encrusted with mineral deposits and needs to be replaced or cleaned. By measuring the current provided to the water heater, the monitoring system can measure the amount of energy provided to the water heater and thus the cost of hot water, and the efficiency of the water heater.


In one embodiment, the sensor 803 includes a moisture sensor. Using data from the moisture sensor, the sensor unit 102 reports moisture conditions, such as, for example, excess moisture that would indicate a water leak, excess condensation, etc.


In one embodiment, the sensor unit 102 is provided to a moisture sensor (such as the sensor 803) located near an air conditioning unit. Using data from the moisture sensor, the sensor unit 102 reports moisture conditions, such as, for example, excess moisture that would indicate a water leak, excess condensation, etc.


In one embodiment, the sensor 201 includes a moisture sensor. The moisture sensor can be place under a sink or a toilet (to detect plumbing leaks) or in an attic space (to detect roof leaks).


Excess humidity in a structure can cause severe problems such as rotting, growth of molds, mildew, and fungus, etc. (hereinafter referred to generically as fungus). In one embodiment, the sensor 201 includes a humidity sensor. The humidity sensor can be place under a sink, in an attic space, etc. to detect excess humidity (due to leaks, condensation, etc.). In one embodiment, the monitoring computer 113 compares humidity measurements taken from different sensor units in order to detect areas that have excess humidity. Thus for example, the monitoring computer 113 can compare the humidity readings from a first sensor unit 102 in a first attic area, to a humidity reading from a second sensor unit 102 in a second area. For example, the monitoring computer can take humidity readings from a number of attic areas to establish a baseline humidity reading and then compare the specific humidity readings from various sensor units to determine if one or more of the units are measuring excess humidity. The monitoring computer 113 would flag areas of excess humidity for further investigation by maintenance personnel. In one embodiment, the monitoring computer 113 maintains a history of humidity readings for various sensor units and flags areas that show an unexpected increase in humidity for investigation by maintenance personnel.


In one embodiment, the monitoring system 100 detects conditions favorable for fungus (e.g., mold, mildew, fungus, etc.) growth by using a first humidity sensor located in a first building area to produce first humidity data and a second humidity sensor located in a second building area to produce second humidity data. The building areas can be, for example, areas near a sink drain, plumbing fixture, plumbing, attic areas, outer walls, a bilge area in a boat, etc.


The monitoring station 113 collects humidity readings from the first humidity sensor and the second humidity sensor and indicates conditions favorable for fungus growth by comparing the first humidity data and the second humidity data. In one embodiment, the monitoring station 113 establishes a baseline humidity by comparing humidity readings from a plurality of humidity sensors and indicates possible fungus growth conditions in the first building area when at least a portion of the first humidity data exceeds the baseline humidity by a specified amount. In one embodiment, the monitoring station 113 establishes a baseline humidity by comparing humidity readings from a plurality of humidity sensors and indicates possible fungus growth conditions in the first building area when at least a portion of the first humidity data exceeds the baseline humidity by a specified percentage.


In one embodiment, the monitoring station 113 establishes a baseline humidity history by comparing humidity readings from a plurality of humidity sensors and indicates possible fungus growth conditions in the first building area when at least a portion of the first humidity data exceeds the baseline humidity history by a specified amount over a specified period of time. In one embodiment, the monitoring station 113 establishes a baseline humidity history by comparing humidity readings from a plurality of humidity sensors over a period of time and indicates possible fungus growth conditions in the first building area when at least a portion of the first humidity data exceeds the baseline humidity by a specified percentage of a specified period of time.


In one embodiment, the sensor unit 102 transmits humidity data when it determines that the humidity data fails a threshold test. In one embodiment, the humidity threshold for the threshold test is provided to the sensor unit 102 by the monitoring station 113. In one embodiment, the humidity threshold for the threshold test is computed by the monitoring station from a baseline humidity established in the monitoring station. In one embodiment, the baseline humidity is computed at least in part as an average of humidity readings from a number of humidity sensors. In one embodiment, the baseline humidity is computed at least in part as a time average of humidity readings from a number of humidity sensors. In one embodiment, the baseline humidity is computed at least in part as a time average of humidity readings from a humidity sensor. In one embodiment, the baseline humidity is computed at least in part as the lesser of a maximum humidity reading an average of a number of humidity readings.


In one embodiment, the sensor unit 102 reports humidity readings in response to a query by the monitoring station 113. In one embodiment, the sensor unit 102 reports humidity readings at regular intervals. In one embodiment, a humidity interval is provided to the sensor unit 102 by the monitoring station 113.


In one embodiment, the calculation of conditions for fungus growth is comparing humidity readings from one or more humidity sensors to the baseline (or reference) humidity. In one embodiment, the comparison is based on comparing the humidity readings to a percentage (e.g., typically a percentage greater than 100%) of the baseline value. In one embodiment, the comparison is based on comparing the humidity readings to a specified delta value above the reference humidity. In one embodiment, the calculation of likelihood of conditions for fungus growth is based on a time history of humidity readings, such that the longer the favorable conditions exist, the greater the likelihood of fungus growth. In one embodiment, relatively high humidity readings over a period of time indicate a higher likelihood of fungus growth than relatively high humidity readings for short periods of time. In one embodiment, a relatively sudden increase in humidity as compared to a baseline or reference humidity is reported by the monitoring station 113 as a possibility of a water leak. If the relatively high humidity reading continues over time then the relatively high humidity is reported by the monitoring station 113 as possibly being a water leak and/or an area likely to have fungus growth or water damage.


Temperatures relatively more favorable to fungus growth increase the likelihood of fungus growth. In one embodiment, temperature measurements from the building areas are also used in the fungus grown-likelihood calculations. In one embodiment, a threshold value for likelihood of fungus growth is computed at least in part as a function of temperature, such that temperatures relatively more favorable to fungus growth result in a relatively lower threshold than temperatures relatively less favorable for fungus growth. In one embodiment, the calculation of a likelihood of fungus growth depends at least in part on temperature such that temperatures relatively more favorable to fungus growth indicate a relatively higher likelihood of fungus growth than temperatures relatively less favorable for fungus growth. Thus, in one embodiment, a maximum humidity and/or minimum threshold above a reference humidity is relatively lower for temperature more favorable to fungus growth than the maximum humidity and/or minimum threshold above a reference humidity for temperatures relatively less favorable to fungus growth.


In one embodiment, a water flow sensor is provided to the sensor unit 102. The sensor unit 102 obtains water flow data from the water flow sensor and provides the water flow data to the monitoring computer 113. The monitoring computer 113 can then calculate water usage. Additionally, the monitoring computer can watch for water leaks, by, for example, looking for water flow when there should be little or no flow. Thus, for example, if the monitoring computer detects water usage throughout the night, the monitoring computer can raise an alert indicating that a possible water leak has occurred.


In one embodiment, the sensor 201 includes a water flow sensor is provided to the sensor unit 102. The sensor unit 102 obtains water flow data from the water flow sensor and provides the water flow data to the monitoring computer 113. The monitoring computer 113 can then calculate water usage. Additionally, the monitoring computer can watch for water leaks, by, for example, looking for water flow when there should be little or no flow. Thus, for example, if the monitoring computer detects water usage throughout the night, the monitoring computer can raise an alert indicating that a possible water leak has occurred.


In one embodiment, the sensor 201 includes a fire-extinguisher tamper sensor is provided to the sensor unit 102. The fire-extinguisher tamper sensor reports tampering with or use of a fire-extinguisher. In one embodiment the fire-extinguisher tamper sensor reports that the fire extinguisher has been removed from its mounting, that a fire extinguisher compartment has been opened, and/or that a safety lock on the fire extinguisher has been removed.


It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrated embodiments and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributed thereof; furthermore, various omissions, substitutions and changes may be made without departing from the spirit of the inventions. For example, although specific embodiments are described in terms of the 900 MHz frequency band, one of ordinary skill in the art will recognize that frequency bands above and below 900 MHz can be used as well. The wireless system can be configured to operate on one or more frequency bands, such as, for example, the HF band, the VHF band, the UHF band, the Microwave band, the Millimeter wave band, etc. One of ordinary skill in the art will further recognize that techniques other than spread spectrum can also be used and/or can be use instead spread spectrum. The modulation uses is not limited to any particular modulation method, such that modulation scheme used can be, for example, frequency modulation, phase modulation, amplitude modulation, combinations thereof, etc. The foregoing description of the embodiments is therefore to be considered in all respects as illustrative and not restrictive, with the scope of the invention being delineated by the appended claims and their equivalents.

Claims
  • 1. A system comprising: multiple wireless devices, each wireless device configured to: measure signal strength of wireless signals received from a wireless base unit and from one or more wireless repeater units; andtransmit the signal strength measurements of the wireless base unit and the one or more wireless repeater units to the wireless base unit;each of the one or more wireless repeater units configured to: measure the signal strength of wireless signals received from the wireless base unit and from the wireless devices; andtransmit the signal strength measurements of the wireless base unit and the wireless devices to the wireless base unit;the wireless base unit configured to: receive the transmitted signal strength measurements; andselect routing paths for communications to each of the multiple wireless devices based on an evaluation of the signal strength measurements.
  • 2. The system of claim 1, wherein the wireless base unit is configured to: based on the selection of the routing paths, send instructions to one of the wireless repeater units to add an identifier (ID) of a wireless device to a database included in the wireless repeater unit to configure the one of the wireless repeater units to route communication traffic for the wireless device through the one of the wireless repeater units.
  • 3. The system of claim 2, the wireless base unit configured to: transmit a communication packet to the wireless device using the selected routing path via the one or the one or more wireless repeaters;the one of the one or more wireless repeaters configured to: receive the communication packet from the wireless base unit; andtransmit the communication packet to the wireless device.
  • 4. The system of claim 3, wherein the one of the one or more repeaters is configured to: enable a receiver to receive an acknowledgment from the wireless device that the wireless device received the transmitted communication packet;determine a random amount of delay; andif the acknowledgement is not received after the determined amount of delay, retransmit the communication packet to the wireless device.
  • 5. The system of claim 3, wherein the one of the one or more wireless repeaters listens to a radio frequency channel before beginning the transmission of the communication packet on the radio frequency channel.
  • 6. The system of claim 1, wherein the wireless base unit is configured to: based on the selection of the routing paths, send instructions to one of the wireless repeater units to remove an identifier (ID) of a wireless device from a database included in the one of the wireless repeater units, so that communication traffic for the wireless device is not routed through the one of the wireless repeater units.
  • 7. The system of claim 1, wherein the system is operable to wirelessly communicate at a frequency in a 900 MHz frequency band.
  • 8. An electronic device configured as a wireless base unit, the electronic device comprising: a wireless transceiver; anda controller, coupled to the wireless transceiver, the controller configured to: receive, from multiple wireless devices, measured signal strength of wireless signals received by the multiple wireless devices from the wireless base unit and from one or more wireless repeater units;receive, from at least one of the wireless repeater units, the measured signal strength of wireless signals received by the at least one of the wireless repeater units from the wireless base unit and from the multiple wireless devices; andselect routing paths to each of the multiple wireless devices for communications based on an evaluation of the received signal strength measurements.
  • 9. The electronic device of claim 8, wherein the wireless base unit is configured to: based on the selection of the routing paths, send instructions to one of the wireless repeater units to add an identifier (ID) of a wireless device to a database included in the wireless repeater unit to configure the one of the wireless repeater units to route communication traffic for the wireless device through the one of the wireless repeater units.
  • 10. The electronic device of claim 9, wherein the wireless base unit is configured to: transmit a communication packet to the wireless device using the selected routing path via the one or the one or more wireless repeaters;enable the wireless transceiver to receive an acknowledgment for the transmitted communication packet;determine a random amount of delay; andif the acknowledgement is not received after the determined amount of delay, retransmit the communication packet.
  • 11. The electronic device of claim 10, wherein the wireless base unit listens to a radio frequency channel before beginning the transmission of the communication packet on the radio frequency channel.
  • 12. The electronic device of claim 8, wherein the wireless base unit is configured to: based on the selection of the routing paths, send instructions to one of the wireless repeater units to remove an identifier (ID) of a wireless device from a database included in the one of the wireless repeater units so that communication traffic for the wireless device is not routed through the one of the wireless repeater units.
  • 13. The electronic device of claim 8, wherein the wireless base unit is operable to wirelessly communicate at a frequency in a 900 MHz frequency band.
  • 14. A wireless device comprising: a wireless transceiver; anda controller, coupled to the wireless transceiver, the controller configured to: measure signal strength of wireless signals received by the wireless device from a wireless base unit and from one or more wireless repeater units; andtransmit the signal strength measurements of the wireless base unit and the one or more wireless repeater units to the wireless base unit, the transmission being effective to cause the wireless base unit to select routing paths for communications to each of multiple wireless devices including the wireless device, based at least in part on an evaluation of the transmitted signal strength measurements.
  • 15. The wireless device of claim 14, wherein the controller is configured to: transmit a communication packet to the wireless base unit;enable the wireless transceiver to receive an acknowledgment that the transmitted communication packet was received;determine a random amount of delay; andif the acknowledgement is not received after the determined amount of delay, retransmit the communication packet to the wireless base unit.
  • 16. The wireless device of claim 15, wherein the acknowledgement is transmitted by the wireless base unit or a wireless repeater unit.
  • 17. The wireless device of claim 15, wherein the wireless device listens to a radio frequency channel before beginning the transmission of the packet on the radio frequency channel.
  • 18. The wireless device of claim 14, wherein the wireless device is operable to wirelessly communicate at a frequency in a 900 MHz frequency band.
  • 19. The wireless device of claim 14, the wireless device comprising one or more sensors, the one or more sensors including: a temperature sensor;a smoke sensor;a humidity sensor;a water sensor;a carbon monoxide sensor; a security sensor;a door motion sensor;a window breakage sensor;a window motion sensor;a moisture sensor;a water flow sensor;a natural gas sensor; ora propane sensor.
  • 20. The wireless device of claim 14, wherein the controller is configured to transmit a communication packet including sensor data and an address comprising a first code and a second code.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/601,705, filed May 22, 2017, and entitled, “RELAYING COMMUNICATIONS IN A WIRELESS SENSOR SYSTEM,” which is a continuation of U.S. patent application Ser. No. 15/090,973, now U.S. Pat. No. 9,723,559, filed Apr. 5, 2016, and entitled, “WIRELESS SENSOR UNIT COMMUNICATION TRIGGERING AND MANAGEMENT,” which is a continuation of U.S. patent application Ser. No. 14/548,137, now U.S. Pat. No. 9,318,015, filed Nov. 19, 2014, and entitled, “WIRELESS SENSOR UNIT COMMUNICATION TRIGGERING AND MANAGEMENT,” which is a continuation of U.S. patent application Ser. No. 14/168,876, now U.S. Pat. No. 9,357,490, filed Jan. 30, 2014, and entitled, “WIRELESS TRANSCEIVER,” which is a continuation of U.S. patent application Ser. No. 12/905,248, filed Oct. 15, 2010, and entitled, “WIRELESS TRANSCEIVER,” which is a continuation of U.S. patent application Ser. No. 12/182,079, now U.S. Pat. No. 7,817,031, filed Jul. 29, 2008, and entitled “WIRELESS TRANSCEIVER,” which is a divisional of U.S. patent application Ser. No. 11/562,313, now U.S. Pat. No. 7,411,494, filed Nov. 21, 2006, and entitled “WIRELESS TRANSCEIVER,” which is a continuation of U.S. patent application Ser. No. 10/856,231, now U.S. Pat. No. 7,142,107, filed May 27, 2004, and entitled “WIRELESS TRANSCEIVER,” the entirety of which are incorporated by reference herein for all purposes.

US Referenced Citations (840)
Number Name Date Kind
2101637 Davis Dec 1937 A
2233297 Polin et al. Feb 1941 A
3805265 Lester Apr 1974 A
4056780 Faulkner Nov 1977 A
4061442 Clark et al. Dec 1977 A
4099168 Kedjierski et al. Jul 1978 A
4136823 Kullberg Jan 1979 A
4165024 Oswalt et al. Aug 1979 A
4226533 Snowman Oct 1980 A
4266220 Malinsowski May 1981 A
4400694 Wong et al. Aug 1983 A
4420746 Malinowski Dec 1983 A
4437336 Abe Mar 1984 A
4455553 Johnson Jun 1984 A
4514720 Oberstein et al. Apr 1985 A
4535450 Tan Aug 1985 A
4543570 Bressett et al. Sep 1985 A
4556873 Yamada et al. Dec 1985 A
4613990 Halpem Sep 1986 A
4652859 Van Wienen Mar 1987 A
4661804 Abel Apr 1987 A
4670739 Kelly Jun 1987 A
4675661 Ishii Jun 1987 A
4679742 Ellis Jul 1987 A
4680583 Grover Jul 1987 A
4688244 Hannon et al. Aug 1987 A
4692742 Raizen et al. Sep 1987 A
4692750 Murakami et al. Sep 1987 A
4727359 Yuchi et al. Feb 1988 A
4750197 Denekamp et al. Jun 1988 A
4772876 Laud Sep 1988 A
4801856 Wajima Jan 1989 A
4801865 Miller et al. Jan 1989 A
4802240 Yamaguchi et al. Jan 1989 A
4811011 Sollinger Mar 1989 A
4817131 Thornborough et al. Mar 1989 A
4817537 Cripe et al. Apr 1989 A
4827244 Bellavia et al. May 1989 A
4857895 Kaprelian Aug 1989 A
4862514 Kedjierski Aug 1989 A
4871999 Ishii et al. Oct 1989 A
4901316 Igarashi et al. Feb 1990 A
4916432 Tice et al. Apr 1990 A
4918690 Markkula, Jr. et al. Apr 1990 A
4939504 Miller Jul 1990 A
4951029 Severson Aug 1990 A
4964121 Moore Oct 1990 A
4977527 Shaw et al. Dec 1990 A
4996518 Takahashi et al. Feb 1991 A
5040238 Comroe et al. Aug 1991 A
5054052 Nonami Oct 1991 A
5107446 Shaw et al. Apr 1992 A
5117501 Childress et al. May 1992 A
5129096 Burns Jul 1992 A
5134644 Garton et al. Jul 1992 A
5138562 Shaw et al. Aug 1992 A
5151683 Takahashi et al. Sep 1992 A
5159315 Takahashi et al. Oct 1992 A
5168262 Okayama Dec 1992 A
5188143 Krebs Feb 1993 A
5201061 Goldberg et al. Apr 1993 A
5210540 Masumoto May 1993 A
5224648 Simon et al. Jul 1993 A
5229750 Welch et al. Jul 1993 A
5240022 Franklin Aug 1993 A
5260687 Yamauchi et al. Nov 1993 A
5265025 Hirata Nov 1993 A
5267180 Okayama Nov 1993 A
5281951 Okayama Jan 1994 A
5295154 Meier et al. Mar 1994 A
5315291 Furr May 1994 A
5319698 Glidewell et al. Jun 1994 A
5331637 Francis et al. Jul 1994 A
5335186 Tarrant Aug 1994 A
5345224 Brown Sep 1994 A
5355518 Kindinger et al. Oct 1994 A
5357241 Welch Oct 1994 A
5369784 Nelson Nov 1994 A
5400246 Wilson et al. Mar 1995 A
5400254 Fujita Mar 1995 A
5408223 Guillemot Apr 1995 A
5424720 Kirkpatrick Jun 1995 A
5425051 Mahany Jun 1995 A
5428964 Lobdell Jul 1995 A
5430433 Shima Jul 1995 A
5432500 Scripps Jul 1995 A
5442758 Slingwine et al. Aug 1995 A
5457680 Kamm Oct 1995 A
5478092 Ishikawa et al. Dec 1995 A
5511232 O'Dea et al. Apr 1996 A
5530433 Morita Jun 1996 A
5540092 Handfield et al. Jul 1996 A
5564626 Kettler et al. Oct 1996 A
5565852 Petlier et al. Oct 1996 A
5565858 Guthrie Oct 1996 A
5568121 Lamensdorf Oct 1996 A
5574435 Mochizuki Nov 1996 A
5579306 Dent Nov 1996 A
5590409 Sawahashi et al. Dec 1996 A
5596652 Piatek et al. Jan 1997 A
5604892 Nuttall et al. Feb 1997 A
5606313 Allen et al. Feb 1997 A
5627515 Anderson May 1997 A
5640151 Reis et al. Jun 1997 A
5652751 Sharony Jul 1997 A
5655561 Wendel et al. Aug 1997 A
5682379 Mahany et al. Oct 1997 A
5686902 Reis et al. Nov 1997 A
5719556 Albin et al. Feb 1998 A
5723848 Bilenko et al. Mar 1998 A
5732007 Grushin et al. Mar 1998 A
5732077 Whitehead Mar 1998 A
5736928 Tice et al. Apr 1998 A
5748092 Arsenault et al. May 1998 A
5761195 Lu et al. Jun 1998 A
5790946 Rotzoll Aug 1998 A
5793882 Piatek et al. Aug 1998 A
5802274 Dorak et al. Sep 1998 A
5833910 Teixido Nov 1998 A
5854994 Canada et al. Dec 1998 A
5859536 Stockton Jan 1999 A
5862803 Besson Jan 1999 A
5881951 Carpenter Mar 1999 A
5889468 Banga Mar 1999 A
5890054 Lodgson et al. Mar 1999 A
5892441 Woolley et al. Apr 1999 A
5892758 Argyroudis Apr 1999 A
5898374 Schepka Apr 1999 A
5907491 Canada et al. May 1999 A
5913180 Ryan Jun 1999 A
5914656 Ojala et al. Jun 1999 A
5917423 Duvall Jun 1999 A
5917433 Keillor et al. Jun 1999 A
5923102 Koenig et al. Jul 1999 A
5939982 Gagnon et al. Aug 1999 A
5943610 Endo Aug 1999 A
5949332 Kim Sep 1999 A
5950124 Trompower et al. Sep 1999 A
5959529 Kail, IV Sep 1999 A
5959568 Woolley Sep 1999 A
5966079 Tanguay Oct 1999 A
5973603 Judy Oct 1999 A
5974236 Sherman Oct 1999 A
5977913 Christ Nov 1999 A
6005669 Pahk et al. Dec 1999 A
6005884 Cook et al. Dec 1999 A
6006100 Koenck et al. Dec 1999 A
6023476 Lo Feb 2000 A
6025788 Diduck Feb 2000 A
6031455 Grube et al. Feb 2000 A
6046675 Hanna Apr 2000 A
6049273 Hess Apr 2000 A
6060994 Chen May 2000 A
6072784 Agrawal et al. Jun 2000 A
6075451 Lebowitz et al. Jun 2000 A
6078050 Castleman Jun 2000 A
6078269 Markwell et al. Jun 2000 A
6078785 Bush Jun 2000 A
6078789 Bodenmann et al. Jun 2000 A
6084522 Addy Jul 2000 A
6091724 Chandra et al. Jul 2000 A
6097288 Koeppe, Jr. Aug 2000 A
6097707 Hodzic et al. Aug 2000 A
6104512 Batey et al. Aug 2000 A
6108544 Dorenbosch et al. Aug 2000 A
6108614 Lincoln et al. Aug 2000 A
6111511 Sivathanu et al. Aug 2000 A
6118988 Choi Sep 2000 A
6124806 Cunningham et al. Sep 2000 A
6125306 Shimada et al. Sep 2000 A
6127928 Issacman Oct 2000 A
6127976 Boyd et al. Oct 2000 A
6134587 Okanoue Oct 2000 A
6134589 Hultgren Oct 2000 A
6154658 Caci Nov 2000 A
6157307 Hardin Dec 2000 A
6175310 Gott Jan 2001 B1
6192400 Hanson et al. Feb 2001 B1
6198913 Sung et al. Mar 2001 B1
6201974 Lietsalmi et al. Mar 2001 B1
6208247 Agre et al. Mar 2001 B1
6215404 Morales Apr 2001 B1
6225894 Kyrtsos May 2001 B1
6239690 Burbidge et al. May 2001 B1
6246882 Lachance Jun 2001 B1
6256303 Drakoulis et al. Jul 2001 B1
6281840 Miyoshi et al. Aug 2001 B1
6313646 Davis et al. Nov 2001 B1
6313745 Suzuki Nov 2001 B1
6320501 Tice et al. Nov 2001 B1
6354493 Mon Mar 2002 B1
6360169 Dudaney Mar 2002 B1
6366217 Cunningham et al. Apr 2002 B1
6369714 Walter Apr 2002 B2
6377181 Kroll et al. Apr 2002 B1
6380860 Goetz Apr 2002 B1
6381467 Hill et al. Apr 2002 B1
6388399 Eckel et al. May 2002 B1
6404082 Rasinski et al. Jun 2002 B1
6405102 Swartz et al. Jun 2002 B1
6409082 Davis et al. Jun 2002 B1
6418299 Ramanathan Jul 2002 B1
6420973 Acevedo Jul 2002 B2
6421539 Jeong Jul 2002 B1
6421731 Ciotti et al. Jul 2002 B1
6424260 Maloney Jul 2002 B2
6424264 Giraldin et al. Jul 2002 B1
6427913 Maloney Aug 2002 B1
6437692 Petite et al. Aug 2002 B1
6441731 Hess Aug 2002 B1
6445292 Jen et al. Sep 2002 B1
6452493 Ma et al. Sep 2002 B1
6453687 Sharood et al. Sep 2002 B2
6473607 Shohara et al. Oct 2002 B1
6476708 Johnson Nov 2002 B1
6480149 Twitchell Nov 2002 B1
6481222 Denniston Nov 2002 B1
6489895 Apelman Dec 2002 B1
6512478 Chien Jan 2003 B1
6515283 Castleman et al. Feb 2003 B1
6519509 Nierlich et al. Feb 2003 B1
6526807 Doumit et al. Mar 2003 B1
6529142 Yeh et al. Mar 2003 B2
6535110 Arora et al. Mar 2003 B1
6542114 Eagleson et al. Apr 2003 B1
6547137 Begelfer et al. Apr 2003 B1
6552647 Thiesen et al. Apr 2003 B1
6553336 Johnson et al. Apr 2003 B1
6559620 Zhou et al. May 2003 B2
6583720 Quigley Jun 2003 B1
6587755 Smith et al. Jul 2003 B1
6600418 Francis et al. Jul 2003 B2
6601016 Brown Jul 2003 B1
6611556 Koener et al. Aug 2003 B1
6611688 Raith Aug 2003 B1
6614349 Proctor et al. Sep 2003 B1
6615658 Snelling Sep 2003 B2
6617962 Horwitz et al. Sep 2003 B1
6619055 Addy Sep 2003 B1
6624750 Marman Sep 2003 B1
6628835 Brill et al. Sep 2003 B1
6639517 Chapman et al. Oct 2003 B1
6665585 Kawase Dec 2003 B2
6666086 Colman et al. Dec 2003 B2
6679400 Goodman Jan 2004 B1
6685104 Float et al. Feb 2004 B1
6690657 Lau et al. Feb 2004 B1
6693907 Wesley et al. Feb 2004 B1
6700533 Werb et al. Mar 2004 B1
6704681 Nassof et al. Mar 2004 B1
6711408 Raith Mar 2004 B1
6714977 Fowler et al. Mar 2004 B1
6800533 Werb Mar 2004 B1
6717507 Bayley et al. Apr 2004 B1
6720888 Eagleson et al. Apr 2004 B2
6731215 Harms et al. May 2004 B2
6735630 Gelvin et al. May 2004 B1
6737974 Dickinson May 2004 B2
6744740 Chen Jun 2004 B2
6745027 Twitchell et al. Jun 2004 B2
6747558 Thorne et al. Jun 2004 B1
6747562 Giraldin et al. Jun 2004 B2
6748804 Lisec et al. Jun 2004 B1
6753775 Auerbach et al. Jun 2004 B2
6759956 Menard et al. Jul 2004 B2
6760578 Rotzoll Jul 2004 B2
6761312 Piatek et al. Jul 2004 B2
6765484 Eagleson et al. Jul 2004 B2
6789220 Lovejoy Sep 2004 B1
6789739 Rosen Sep 2004 B2
6796187 Srinivasan et al. Sep 2004 B2
6798220 Flanigan et al. Sep 2004 B1
6798341 Eckel et al. Sep 2004 B1
6799210 Gentry et al. Sep 2004 B1
6803728 Balasubramaniam et al. Oct 2004 B2
6816063 Kubler et al. Nov 2004 B2
6825758 Laitsaari Nov 2004 B1
6825777 Vock et al. Nov 2004 B2
6826948 Bhatti et al. Dec 2004 B1
6847892 Zhou Jan 2005 B2
6851621 Wacker et al. Feb 2005 B1
6870476 Cockburn et al. Mar 2005 B2
6874037 Abram et al. Mar 2005 B1
6882274 Richardson et al. Apr 2005 B2
6891470 Bohinc May 2005 B2
6891838 Petite et al. May 2005 B1
6892751 Sanders May 2005 B2
6900731 Kreiner May 2005 B2
6909921 Bilger Jun 2005 B1
6919803 Breed Jul 2005 B2
6927688 Tice Aug 2005 B2
6930596 Kulesz et al. Aug 2005 B2
6934540 Twitchell et al. Aug 2005 B2
6935570 Acker Aug 2005 B2
6940392 Chan et al. Sep 2005 B2
6940403 Kail Sep 2005 B2
6965314 Bohinc Nov 2005 B2
6972682 Lareau et al. Dec 2005 B2
6975614 Kennedy Dec 2005 B2
6988079 Or-Bach et al. Jan 2006 B1
6995676 Amacher Feb 2006 B2
7005985 Steeves Feb 2006 B1
7012529 Sajkowsky Mar 2006 B2
7022773 Albano et al. Apr 2006 B2
7026929 Wallace Apr 2006 B1
7027773 McMillin Apr 2006 B1
7034683 Ghazarian Apr 2006 B2
7038585 Hall May 2006 B2
7042352 Kates May 2006 B2
7055759 Wacker et al. Jun 2006 B2
7063667 Ben-Oren et al. Jun 2006 B1
7072668 Chou Jul 2006 B2
7088229 Johnson Aug 2006 B2
7098784 Easley et al. Aug 2006 B2
7102504 Kates Sep 2006 B2
7102505 Kates Sep 2006 B2
7103016 Duffy et al. Sep 2006 B1
7103344 Menard Sep 2006 B2
7109879 Stults et al. Sep 2006 B2
7126470 Clift et al. Oct 2006 B2
7133704 Twitchell Nov 2006 B2
7135965 Chapman et al. Nov 2006 B2
7142107 Kates Nov 2006 B2
7142121 Chan et al. Nov 2006 B2
7142123 Kates Nov 2006 B1
7148800 Cunningham Dec 2006 B2
7148803 Bandy Dec 2006 B2
7155238 Katz Dec 2006 B2
7155264 Twitchell et al. Dec 2006 B2
7191934 Miller et al. Mar 2007 B2
7196622 Lambright Mar 2007 B2
7200132 Twitchell et al. Apr 2007 B2
7209037 Webb Apr 2007 B2
7209468 Twitchell et al. Apr 2007 B2
7209771 Twitchell et al. Apr 2007 B2
7212122 Gloekler May 2007 B2
7218237 Kates May 2007 B2
7221260 Berezowski et al. May 2007 B2
7221668 Twitchell et al. May 2007 B2
7228726 Kates Jun 2007 B2
7230528 Kates Jun 2007 B2
7230933 Bahl et al. Jun 2007 B2
7233958 Weng Jun 2007 B2
7239238 Tester et al. Jul 2007 B2
7248160 Mangan et al. Jul 2007 B2
7253731 Joao Aug 2007 B2
7256505 Arms et al. Aug 2007 B2
7270353 Sironi et al. Sep 2007 B2
7273172 Olsen Sep 2007 B2
7274295 Koch Sep 2007 B2
7277009 Hall Oct 2007 B2
7282944 Gunn et al. Oct 2007 B2
7283052 Bohman Oct 2007 B2
7289497 Pelletier et al. Oct 2007 B2
7289761 Mazar Oct 2007 B2
7299068 Halla Nov 2007 B1
7313421 Dejanovic Dec 2007 B2
7315281 Dejanovic Jan 2008 B2
7317382 Pratt Jan 2008 B2
7319397 Chung Jan 2008 B2
7323981 Peel Jan 2008 B2
7333015 Ekstrom Feb 2008 B2
7336168 Kates Feb 2008 B2
7339469 Braun Mar 2008 B2
7340260 McAlexander Mar 2008 B2
7342496 Muirhead Mar 2008 B2
7342497 Chung Mar 2008 B2
7348875 Hughes et al. Mar 2008 B2
7349803 Belenkii et al. Mar 2008 B2
7349804 Belenkii Mar 2008 B2
7376507 Daily et al. May 2008 B1
7378957 Twitchell et al. May 2008 B2
7378958 Twitchell et al. May 2008 B2
7378959 Twitchell et al. May 2008 B2
7378960 Binding May 2008 B1
7382251 Bohman Jun 2008 B2
7391321 Twitchell et al. Jun 2008 B2
7394358 Cherry Jul 2008 B2
7394361 Twitchell et al. Jul 2008 B1
7394372 Gloekler Jul 2008 B2
7397363 Joao Jul 2008 B2
7411494 Kates Aug 2008 B2
7412876 Kates Aug 2008 B2
7417543 Bergman Aug 2008 B2
7419101 Kawai Sep 2008 B2
7423534 Dhanjal Sep 2008 B2
7423535 Chung Sep 2008 B2
7430437 Twitchell et al. Sep 2008 B2
7434742 Mueller et al. Oct 2008 B2
7438334 Terry et al. Oct 2008 B2
7440781 Beach et al. Oct 2008 B2
7460690 Cohen et al. Dec 2008 B2
7469550 Chapman et al. Dec 2008 B2
7482920 Joao Jan 2009 B2
7489244 August et al. Feb 2009 B2
7515940 Chen et al. Apr 2009 B2
7522568 Twitchell et al. Apr 2009 B2
7526381 Twitchell Apr 2009 B2
7528711 Kates May 2009 B2
7528719 Hopman et al. May 2009 B2
7529547 Twitchell May 2009 B2
7538656 Twitchell et al. May 2009 B2
7538657 Twitchell et al. May 2009 B2
7538658 Twitchell et al. May 2009 B2
7538672 Lockyer et al. May 2009 B2
7539520 Twitchell et al. May 2009 B2
7542849 Twitchell et al. Jun 2009 B2
7561057 Kates Jul 2009 B2
7563991 Clark et al. Jul 2009 B2
7571865 Nicodem et al. Aug 2009 B2
7574168 Twitchell et al. Aug 2009 B2
7574300 Twitchell et al. Aug 2009 B2
7579945 Richter et al. Aug 2009 B1
7583198 Kates Sep 2009 B2
7583769 Smith et al. Sep 2009 B2
7595727 Grijalva et al. Sep 2009 B2
7600137 Trappeniers et al. Oct 2009 B2
7623028 Kates Nov 2009 B2
7626508 Kosuge et al. Dec 2009 B2
7703694 Mueller et al. Apr 2010 B2
D614976 Skafdrup et al. May 2010 S
7735118 Brok et al. Jun 2010 B2
7782200 Fleischmann Aug 2010 B1
7817031 Kates Oct 2010 B2
7837958 Crapser et al. Nov 2010 B2
7893827 Kates Feb 2011 B2
7904209 Podgorny et al. Mar 2011 B2
7907941 Twitchell Mar 2011 B2
7924735 Sun et al. Apr 2011 B2
7940716 Twitchell May 2011 B2
7975292 Corella Jul 2011 B2
7986238 Cho Jul 2011 B2
7994928 Richmond Aug 2011 B2
8000315 Doi et al. Aug 2011 B2
8016205 Drew Sep 2011 B2
8037022 Rahman et al. Oct 2011 B2
8098166 Lang Jan 2012 B2
8111651 Twitchell Feb 2012 B2
8125978 Lim et al. Feb 2012 B2
8165072 Mooney et al. Apr 2012 B2
8175109 Nogueira-Nine et al. May 2012 B2
8188764 Weiss et al. May 2012 B2
8228183 Glenn et al. Jul 2012 B2
8234694 Youn et al. Jul 2012 B2
8255090 Frader-Thompson et al. Aug 2012 B2
8275404 Berger et al. Sep 2012 B2
8391435 Farley et al. Mar 2013 B2
8462662 Robins et al. Jun 2013 B2
8514758 De Kimpe et al. Aug 2013 B2
8531268 Ghabra et al. Sep 2013 B2
8589174 Nelson et al. Nov 2013 B2
8605660 Twitchell Dec 2013 B2
8619652 Singh et al. Dec 2013 B2
8954082 Twitchell Feb 2015 B2
9019110 Kates Apr 2015 B2
9072049 Farley et al. Jun 2015 B2
9183733 Kates Nov 2015 B2
9286787 Kates Mar 2016 B2
9286788 Kates Mar 2016 B2
9295099 Twitchell et al. Mar 2016 B2
9318015 Kates Apr 2016 B2
9357490 Kates May 2016 B2
9386553 Berger et al. Jul 2016 B2
9412260 Kates Aug 2016 B2
9474023 Kates Oct 2016 B1
9532310 Farley et al. Dec 2016 B2
9699736 Farley et al. Jul 2017 B2
9723559 Kates Aug 2017 B2
9860839 Kates Jan 2018 B2
9872249 Kates Jan 2018 B2
9955423 Kates Apr 2018 B2
10015743 Kates Jul 2018 B2
10229586 Kates Mar 2019 B2
10395513 Kates Aug 2019 B2
20010000019 Bowers et al. Mar 2001 A1
20010050550 Yoshida et al. Dec 2001 A1
20020005707 Kerai et al. Jan 2002 A1
20020011570 Castleman Jan 2002 A1
20020011923 Cunningham et al. Jan 2002 A1
20020012323 Petite et al. Jan 2002 A1
20020012337 Schmidl et al. Jan 2002 A1
20020030592 Hakanen et al. Mar 2002 A1
20020030596 Finn et al. Mar 2002 A1
20020033759 Morello Mar 2002 A1
20020039896 Brown Apr 2002 A1
20020050632 Tuttle et al. May 2002 A1
20020050932 Rhoades et al. May 2002 A1
20020070846 Bastian et al. Jun 2002 A1
20020073646 Von Gutfeld et al. Jun 2002 A1
20020075145 Hardman et al. Jun 2002 A1
20020084414 Baker et al. Jul 2002 A1
20020089434 Ghazarian Jul 2002 A1
20020098861 Doney et al. Jul 2002 A1
20020099567 Joao Jul 2002 A1
20020102979 Curley et al. Aug 2002 A1
20020119770 Twitchell Aug 2002 A1
20020124169 Agrawal et al. Sep 2002 A1
20020126005 Hardman et al. Sep 2002 A1
20020130771 Osborne et al. Sep 2002 A1
20020130778 Nicholson Sep 2002 A1
20020140963 Otsuka Oct 2002 A1
20020146985 Naden Oct 2002 A1
20020158775 Wallace Oct 2002 A1
20020186141 Jen et al. Dec 2002 A1
20030005144 Engel et al. Jan 2003 A1
20030008692 Phelan Jan 2003 A1
20030011428 Yamakawa et al. Jan 2003 A1
20030011474 Ng Jan 2003 A1
20030011482 Harms et al. Jan 2003 A1
20030025612 Holmes et al. Feb 2003 A1
20030037125 Luman et al. Feb 2003 A1
20030043763 Grayson Mar 2003 A1
20030051023 Reichel et al. Mar 2003 A1
20030058093 Dohi et al. Mar 2003 A1
20030083064 Cooper May 2003 A1
20030114898 Von Ark et al. Jun 2003 A1
20030117966 Chen Jun 2003 A1
20030122677 Kail Jul 2003 A1
20030140135 Okuyama et al. Jul 2003 A1
20030141973 Yeh et al. Jul 2003 A1
20030144020 Challa et al. Jul 2003 A1
20030146833 Johnston et al. Aug 2003 A1
20030151513 Herrmann et al. Aug 2003 A1
20030162504 Sabongi et al. Aug 2003 A1
20030167391 Al-Ali Sep 2003 A1
20030168443 Dozier Sep 2003 A1
20030174056 Harshaw Sep 2003 A1
20030179073 Ghazarian Sep 2003 A1
20030182077 Emord Sep 2003 A1
20030185289 Colmenarez et al. Oct 2003 A1
20030189491 Ng Oct 2003 A1
20030189948 Sashihara Oct 2003 A1
20030199247 Striemer Oct 2003 A1
20030202477 Zhen et al. Oct 2003 A1
20030209601 Chung Nov 2003 A1
20030214400 Mizutani et al. Nov 2003 A1
20030220075 Baker et al. Nov 2003 A1
20030228846 Berliner et al. Dec 2003 A1
20030231001 Bruning Dec 2003 A1
20030235175 Naghian et al. Dec 2003 A1
20030236077 Sivard Dec 2003 A1
20040007264 Bootka Jan 2004 A1
20040017291 Hardman et al. Jan 2004 A1
20040019783 Hawkes Jan 2004 A1
20040021572 Schoen et al. Feb 2004 A1
20040023629 Klank Feb 2004 A1
20040025018 Haas et al. Feb 2004 A1
20040041706 Stratmoen et al. Mar 2004 A1
20040041731 Hisano Mar 2004 A1
20040050429 Aylward Mar 2004 A1
20040062224 Brownrigg et al. Apr 2004 A1
20040066271 Leck Apr 2004 A1
20040075566 Stepanik et al. Apr 2004 A1
20040082296 Twitchell Apr 2004 A1
20040090329 Hitt May 2004 A1
20040090924 Giaimo et al. May 2004 A1
20040100379 Boman et al. May 2004 A1
20040100394 Hitt May 2004 A1
20040100415 Veitch et al. May 2004 A1
20040102864 Stack et al. May 2004 A1
20040113772 Chou Jun 2004 A1
20040119588 Marks Jun 2004 A1
20040121793 Weigele et al. Jun 2004 A1
20040135691 Duron et al. Jul 2004 A1
20040137959 Salzhauer et al. Jul 2004 A1
20040142716 Orlik et al. Jul 2004 A1
20040143750 Kulack et al. Jul 2004 A1
20040147267 Hill et al. Jul 2004 A1
20040148632 Park et al. Jul 2004 A1
20040150516 Faetanini Aug 2004 A1
20040164238 Xu et al. Aug 2004 A1
20040164855 Okubo Aug 2004 A1
20040174259 Peel Sep 2004 A1
20040176028 Dibernardo Sep 2004 A1
20040181496 Odinotski et al. Sep 2004 A1
20040181693 Milliot et al. Sep 2004 A1
20040183673 Nageli Sep 2004 A1
20040189485 Wang Sep 2004 A1
20040193876 Donley et al. Sep 2004 A1
20040198467 Orlik et al. Oct 2004 A1
20040205781 Hill et al. Oct 2004 A1
20040215532 Boman et al. Oct 2004 A1
20040217858 Ingley et al. Nov 2004 A1
20040219930 Lin Nov 2004 A1
20040222884 Costa et al. Nov 2004 A1
20040224631 Davis et al. Nov 2004 A1
20040224637 Silva et al. Nov 2004 A1
20040232924 Hilleary et al. Nov 2004 A1
20040233041 Bohman et al. Nov 2004 A1
20040233054 Neff et al. Nov 2004 A1
20040233855 Gutierrez Nov 2004 A1
20040233874 Baker Nov 2004 A1
20040236645 Tien Nov 2004 A1
20040239268 Grubba et al. Dec 2004 A1
20040246463 Milinusic Dec 2004 A1
20040246903 Huang et al. Dec 2004 A1
20040246934 Kim Dec 2004 A1
20040263340 Pearson et al. Dec 2004 A1
20040264372 Huang Dec 2004 A1
20050012601 Matsubara et al. Jan 2005 A1
20050030175 Wolfe Feb 2005 A1
20050035877 Kim Feb 2005 A1
20050043068 Shohara et al. Feb 2005 A1
20050043907 Eckel et al. Feb 2005 A1
20050046563 Whitney Mar 2005 A1
20050053063 Madhavan Mar 2005 A1
20050062605 Sutphin Mar 2005 A1
20050071358 Hind et al. Mar 2005 A1
20050073406 Easley et al. Apr 2005 A1
20050078672 Caliskan et al. Apr 2005 A1
20050087235 Skorpik Apr 2005 A1
20050088299 Bandy Apr 2005 A1
20050090211 Lilja et al. Apr 2005 A1
20050093702 Twitchell May 2005 A1
20050093703 Twitchell May 2005 A1
20050099292 Sajkowsky May 2005 A1
20050105841 Luo et al. May 2005 A1
20050111428 Orlik et al. May 2005 A1
20050116667 Mueller et al. Jun 2005 A1
20050125083 Kiko Jun 2005 A1
20050128067 Zakrewski Jun 2005 A1
20050128080 Hall et al. Jun 2005 A1
20050129034 Takeyoshi et al. Jun 2005 A1
20050131652 Corwin et al. Jun 2005 A1
20050145018 Sabata et al. Jul 2005 A1
20050146445 Sieboda et al. Jul 2005 A1
20050152318 Elbatt et al. Jul 2005 A1
20050154527 Ulrich Jul 2005 A1
20050157659 Huitema Jul 2005 A1
20050164633 Linjama et al. Jul 2005 A1
20050174236 Brookner Aug 2005 A1
20050187867 Sokolic et al. Aug 2005 A1
20050190759 Lee et al. Sep 2005 A1
20050194456 Tessier et al. Sep 2005 A1
20050199716 Shafer et al. Sep 2005 A1
20050200475 Chen Sep 2005 A1
20050215280 Twitchell Sep 2005 A1
20050226201 McMillin Oct 2005 A1
20050228991 Schmit Oct 2005 A1
20050245270 Sartori Nov 2005 A1
20050246408 Chung Nov 2005 A1
20050258974 Mahowald Nov 2005 A1
20050261037 Raghunath et al. Nov 2005 A1
20050262923 Kates Dec 2005 A1
20050270151 Winick Dec 2005 A1
20050270160 Chan et al. Dec 2005 A1
20050275527 Kates Dec 2005 A1
20050275528 Kates Dec 2005 A1
20050275529 Kates Dec 2005 A1
20050275530 Kates Dec 2005 A1
20050275547 Kates Dec 2005 A1
20060007008 Kates Jan 2006 A1
20060007863 Naghian Jan 2006 A1
20060032379 Kates Feb 2006 A1
20060041680 Proctor et al. Feb 2006 A1
20060059977 Kates Mar 2006 A1
20060063484 Proctor et al. Mar 2006 A1
20060068832 Islam Mar 2006 A1
20060098592 Proctor et al. May 2006 A1
20060109106 Braun May 2006 A1
20060114102 Chang et al. Jun 2006 A1
20060132485 Milinusic Jun 2006 A1
20060135145 Redi Jun 2006 A1
20060146717 Conner et al. Jul 2006 A1
20060147003 Archacki et al. Jul 2006 A1
20060158326 Easley et al. Jul 2006 A1
20060163422 Krikorian et al. Jul 2006 A1
20060164232 Waterhouse et al. Jul 2006 A1
20060164239 Loda Jul 2006 A1
20060164257 Giubbini Jul 2006 A1
20060187026 Kochis Aug 2006 A1
20060202817 Mackenzie et al. Sep 2006 A1
20060206273 Reichel et al. Sep 2006 A1
20060208099 Chapman et al. Sep 2006 A1
20060239197 Lieuallen et al. Oct 2006 A1
20060255934 Easley et al. Nov 2006 A1
20060256756 Wakabayashi Nov 2006 A1
20060267756 Kates Nov 2006 A1
20060268727 Rangarajan et al. Nov 2006 A1
20060270382 Lappetelainen et al. Nov 2006 A1
20060273896 Kates Dec 2006 A1
20060276161 Twitchell et al. Dec 2006 A1
20060282546 Reynolds et al. Dec 2006 A1
20060286988 Blume et al. Dec 2006 A1
20060287008 Twitchell et al. Dec 2006 A1
20070001854 Chung et al. Jan 2007 A1
20070002792 Twitchell et al. Jan 2007 A1
20070002793 Twitchell et al. Jan 2007 A1
20070004331 Twitchell et al. Jan 2007 A1
20070008408 Zehavi Jan 2007 A1
20070032951 Tanenhaus et al. Feb 2007 A1
20070038787 Harris et al. Feb 2007 A1
20070040673 Bohine Feb 2007 A1
20070041333 Twitchell et al. Feb 2007 A1
20070041345 Yarvis et al. Feb 2007 A1
20070043478 Ehlers et al. Feb 2007 A1
20070043807 Twitchell et al. Feb 2007 A1
20070044524 Coutermarsh et al. Mar 2007 A1
20070063833 Kates Mar 2007 A1
20070069885 Twitchell et al. Mar 2007 A1
20070078999 Corson et al. Apr 2007 A1
20070090946 Kates Apr 2007 A1
20070099628 Twitchell et al. May 2007 A1
20070099629 Twitchell et al. May 2007 A1
20070113882 Meyers May 2007 A1
20070114295 Jenkens May 2007 A1
20070115114 Meyers May 2007 A1
20070115115 Meyers May 2007 A1
20070115827 Boehnke et al. May 2007 A1
20070115859 Meyers May 2007 A1
20070115902 Shamoon et al. May 2007 A1
20070118332 Meyers May 2007 A1
20070121557 Sylvain May 2007 A1
20070133980 Meyers Jun 2007 A1
20070135179 Hardman et al. Jun 2007 A1
20070139183 Kates Jun 2007 A1
20070139197 Hopman Jun 2007 A1
20070147255 Oyman Jun 2007 A1
20070152815 Meyers Jul 2007 A1
20070155327 Twitchell et al. Jul 2007 A1
20070159999 Twitchell et al. Jul 2007 A1
20070195702 Yuen et al. Aug 2007 A1
20070200765 Meyers Aug 2007 A1
20070211076 Kates Sep 2007 A1
20070229237 Kates Oct 2007 A1
20070234784 Kates Oct 2007 A1
20070266575 Nash Nov 2007 A1
20070274232 Axelsson et al. Nov 2007 A1
20070291690 Twitchell et al. Dec 2007 A1
20070291724 Twitchell et al. Dec 2007 A1
20080015742 Kulyk et al. Jan 2008 A1
20080027586 Hern et al. Jan 2008 A1
20080059622 Hite et al. Mar 2008 A1
20080066658 Muirhead Mar 2008 A1
20080094209 Braun Apr 2008 A1
20080099568 Nicodem et al. May 2008 A1
20080111692 Twitchell et al. May 2008 A1
20080112377 Twitchell et al. May 2008 A1
20080112378 Twitchell et al. May 2008 A1
20080117040 Peel May 2008 A1
20080129458 Twitchell Jun 2008 A1
20080141754 Kates Jun 2008 A1
20080142592 Twitchell et al. Jun 2008 A1
20080143484 Twitchell et al. Jun 2008 A1
20080144554 Twitchell et al. Jun 2008 A1
20080151850 Twitchell et al. Jun 2008 A1
20080165749 Twitchell et al. Jul 2008 A1
20080180252 Vogt Jul 2008 A1
20080212544 Twitchell et al. Sep 2008 A1
20080221737 Josephson et al. Sep 2008 A1
20080228904 Crespo-Dubi et al. Sep 2008 A1
20080234878 Joao Sep 2008 A1
20080264888 Zakula et al. Oct 2008 A1
20080278310 Kates Nov 2008 A1
20080278315 Kates Nov 2008 A1
20080278316 Kates Nov 2008 A1
20080278342 Kates Nov 2008 A1
20080284590 Kates Nov 2008 A1
20080291844 Krause Nov 2008 A1
20080302172 Kates Dec 2008 A1
20080303654 Kates Dec 2008 A1
20080303897 Twitchell et al. Dec 2008 A1
20080304443 Twitchell Dec 2008 A1
20080315596 Terry et al. Dec 2008 A1
20090016308 Twitchell Jan 2009 A1
20090057427 Geadelmann et al. Mar 2009 A1
20090092082 Twitchell et al. Apr 2009 A1
20090103462 Twitchell et al. Apr 2009 A1
20090104902 Twitchell et al. Apr 2009 A1
20090122737 Twitchell et al. May 2009 A1
20090129306 Twitchell et al. May 2009 A1
20090135000 Twitchell et al. May 2009 A1
20090143918 Amundson et al. Jun 2009 A1
20090146805 Joao Jun 2009 A1
20090153336 Kates Jun 2009 A1
20090161642 Twitchell et al. Jun 2009 A1
20090181623 Twitchell et al. Jul 2009 A1
20090194601 Flohr Aug 2009 A1
20090290512 Twitchell Nov 2009 A1
20090295564 Twitchell Dec 2009 A1
20090322510 Berger et al. Dec 2009 A1
20100013635 Berger et al. Jan 2010 A1
20100058450 Fein et al. Mar 2010 A1
20100067420 Twitchell Mar 2010 A1
20100097969 De Kimpe et al. Apr 2010 A1
20100109866 Gavrila et al. May 2010 A1
20100141449 Twitchell Jun 2010 A1
20100145865 Berger et al. Jun 2010 A1
20100150122 Berger et al. Jun 2010 A1
20100156608 Bae et al. Jun 2010 A1
20100163633 Barrett et al. Jul 2010 A1
20100166113 Farley et al. Jul 2010 A1
20100168924 Tessier et al. Jul 2010 A1
20100199086 Kuang et al. Aug 2010 A1
20100214060 Twitchell Aug 2010 A1
20100214074 Twitchell Aug 2010 A1
20100214969 Lamm et al. Aug 2010 A1
20100238036 Holcombe Sep 2010 A1
20110001812 Kang et al. Jan 2011 A1
20110025501 Kates Feb 2011 A1
20110078675 Van Camp et al. Mar 2011 A1
20110119747 Lambiase May 2011 A1
20110138044 Bailey et al. Jun 2011 A1
20110151837 Wlnbush Jun 2011 A1
20110176465 Panta et al. Jul 2011 A1
20110282937 Deshpande et al. Nov 2011 A1
20110289320 Twitchell et al. Nov 2011 A1
20120077434 Royston et al. Mar 2012 A1
20120163422 Lee et al. Jun 2012 A1
20120190390 Reunamaki et al. Jul 2012 A1
20120250619 Twitchell Oct 2012 A1
20130016636 Berger et al. Jan 2013 A1
20130070657 Farley et al. Mar 2013 A1
20130223420 Twitchell et al. Aug 2013 A1
20140203943 Kates Jul 2014 A1
20140285336 Kates Aug 2014 A1
20140308963 Twitchell et al. Oct 2014 A1
20140333423 Kates Nov 2014 A1
20140333434 Kates Nov 2014 A1
20150061868 Kates Mar 2015 A1
20150061892 Kates Mar 2015 A1
20150070192 Kates Mar 2015 A1
20150103747 Twitchell Apr 2015 A1
20150172887 Petite Jun 2015 A1
20160029315 Kates Jan 2016 A1
20160044597 Farley et al. Feb 2016 A1
20160219523 Twitchell et al. Jul 2016 A1
20160247382 Kates Aug 2016 A1
20160267761 Kates Sep 2016 A1
20160286490 Kates Sep 2016 A1
20160300183 Berger et al. Oct 2016 A1
20170041876 Farley et al. Feb 2017 A1
20170048798 Twitchell et al. Feb 2017 A9
20170245215 Twitchell Aug 2017 A1
20170257826 Kates Sep 2017 A1
20180098283 Kates Apr 2018 A1
20180115951 Kates Apr 2018 A1
20180262985 Kates Sep 2018 A1
20180262986 Kates Sep 2018 A1
20180262987 Kates Sep 2018 A1
Foreign Referenced Citations (44)
Number Date Country
2388660 Jul 2000 CN
3415786 Nov 1984 DE
0070449 Jan 1983 EP
0093463 Nov 1983 EP
0346152 Dec 1989 EP
0346152 Oct 1990 EP
0467036 Jan 1992 EP
0601820 Jun 1994 EP
0748083 Dec 1996 EP
0748085 Dec 1996 EP
0580298 Jan 1997 EP
0829995 Mar 1998 EP
0930492 Jul 1999 EP
0441999 Aug 1999 EP
0944014 Sep 1999 EP
1692668 Aug 2006 EP
1317733 Apr 2010 EP
1692599 Jul 2013 EP
231458 Jan 1926 GB
2278471 Nov 1994 GB
2308947 Jul 1997 GB
9298780 Nov 1997 JP
10258189 Sep 1998 JP
20040012311 Feb 2004 KR
100509070 Aug 2005 KR
20050102419 Oct 2005 KR
100587735 Jun 2006 KR
20070005515 Jan 2007 KR
20080001235 Jan 2008 KR
9810393 Mar 1998 WO
0021047 Apr 2000 WO
0055825 Sep 2000 WO
0068907 Nov 2000 WO
0069186 Nov 2000 WO
03009631 Jan 2003 WO
2003098175 Nov 2003 WO
2004010398 Jan 2004 WO
2004073326 Aug 2004 WO
2004100763 Nov 2004 WO
2005010837 Feb 2005 WO
2006056174 Jun 2006 WO
2008054938 May 2008 WO
2009140669 Nov 2009 WO
2009151877 Dec 2009 WO
Non-Patent Literature Citations (201)
Entry
US 9,445,367 B2, 09/2016, Farley et al. (withdrawn)
“Advisory Action”, U.S. Appl. No. 13/555,897, dated Nov. 6, 2014, 3 pages.
“Advisory Action”, U.S. Appl. No. 14/168,876, dated Jun. 10, 2015, 3 pages.
“Advisory Action”, U.S. Appl. No. 14/536,108, dated Sep. 3, 2015, 4 pages.
“Advisory Action”, U.S. Appl. No. 12/353,197, dated Jul. 16, 2012, 5 pages.
“Application Note Published by Texas Instruments for CC1100/CC2500 Products”, Accessed on Dec. 19, 2008, 17 pages.
“Best Way to Contra/Indoor Molds, Dust Mites, and other Microorganisms: Measuring and Controlling Indoor Humidity [Brochure]”, Indoor Health Products, Inc. (2001-2002). Layton, Utah: Indoor Health Products, Inc. Retrieved from the Internet: <URL: http://www. relativehumidity-sensor.com> on Jun. 18, 2004, 3 pages.
“Final Office Action”, U.S. Appl. No. 10/856,395, dated Oct. 30, 2006, 10 pages.
“Final Office Action”, U.S. Appl. No. 14/168,876, dated Mar. 18, 2015, 10 pages.
“Final Office Action”, U.S. Appl. No. 14/534,848, dated Jan. 26, 2017, 10 pages.
“Final Office Action”, U.S. Appl. No. 14/339,234, dated Aug. 20, 2015, 12 pages.
“Final Office Action”, U.S. Appl. No. 15/161,880, dated Dec. 20, 2016, 12 pages.
“Final Office Action”, U.S. Appl. No. 14/548,137, dated Sep. 1, 2015, 13 pages.
“Final Office Action”, U.S. Appl. No. 14/534,848, dated Nov. 23, 2015, 13 pages.
“Final Office Action”, U.S. Appl. No. 15/052,172, dated Feb. 9, 2017, 13 pages.
“Final Office Action”, U.S. Appl. No. 15/161,880, dated Mar. 20, 2017, 13 pages.
“Final Office Action”, U.S. Appl. No. 11/562,352, dated Aug. 21, 2008, 14 pages.
“Final Office Action”, U.S. Appl. No. 13/555,897, dated Aug. 29, 2014, 14 pages.
“Final Office Action”, U.S. Appl. No. 15/090,973, dated Nov. 10, 2016, 14 pages.
“Final Office Action”, U.S. Appl. No. 12/353,197, dated Mar. 23, 2012, 15 pages.
“Final Office Action”, U.S. Appl. No. 14/536,108, dated Jun. 13, 2016, 16 pages.
“Final Office Action”, U.S. Appl. No. 13/367,341, dated Feb. 26, 2013, 17 pages.
“Final Office Action”, U.S. Appl. No. 14/298,371, dated Mar. 6, 2015, 17 pages.
“Final Office Action”, U.S. Appl. No. 14/536,108, dated May 26, 2015, 18 pages.
“Final Office Action”, U.S. Appl. No. 14/536,108, dated Nov. 29, 2017, 20 pages.
“Final Office Action”, U.S. Appl. No. 14/338,592, dated May 29, 2015, 22 pages.
“Final Office Action”, U.S. Appl. No. 14/573,625, dated Dec. 14, 2016, 29 pages.
“Final Office Action”, U.S. Appl. No. 11/314,807, dated Jul. 16, 2007, 5 pages.
“Final Office Action”, U.S. Appl. No. 11/314,807, dated Apr. 1, 2008, 5 pages.
“Final Office Action”, U.S. Appl. No. 12/036,915, dated Jul. 8, 2009, 5 pages.
“Final Office Action”, U.S. Appl. No. 10/856,395, dated Apr. 13, 2006, 8 pages.
“First Action Interview Office Action”, U.S. Appl. No. 14/338,592, dated Mar. 24, 2015, 4 pages.
“First Action Interview Office Action”, U.S. Appl. No. 14/339,234, dated Mar. 24, 2015, 8 pages.
“First Action Interview Pre-Interview Communication”, U.S. Appl. No. 15/194,148, dated Jul. 17, 2017, 4 pages.
“First Alert—User's Manual Smoke and Fire Alarm: Battery Powered Photoelectric Smoke Alarm with Silence and Escape Light: Model SA720 [Brochure]”, Mexico: First Alert, Jan. 1, 2007, 6 pages.
“G-Cap 2 Relative Humidity Sensor [Brochure]”, GE General Eastern Instruments—GlobalSpec.com—Retrieved from the Internet: <URL: http://www.globalspec.com/FeaturedProducts/Detail?ExhibitiD=1454> on Jun. 18, 2004, 2 pages.
“Impedance Moisture Sensor Technology [Brochure].”, Michell Instruments L to. Retrieved from the Internet: <URL: http://www.sensorland.com/HowPage029.html> on Jun. 18, 2004, 2 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2006/026158, dated Jan. 17, 2008, 9 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2009/044277, dated Jan. 27, 2010, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2009/044276, dated Jan. 11, 2010, 7 pages.
“Mechanical Data Sheet: PT(S-PQFP-G48) Plastic Quad Flatpack, [Brochure].”, Texas Instruments, Inc. (1996). Dallas, Texas: Texas Instruments, Inc., Jan. 1, 1996, 2 pages.
“Non Final Office Action”, U.S. Appl. No. 15/601,705, dated Jun. 16, 2017, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/647,672, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/216,225, dated Mar. 4, 2008, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/428,536, dated Dec. 24, 2009, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/090,973, dated Jun. 15, 2016, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/161,880, dated Jul. 12, 2016, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/353,197, dated Oct. 6, 2011, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/555,897, dated Dec. 17, 2013, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/534,848, dated Jun. 13, 2017, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/590,880, dated Aug. 11, 2017, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/338,592, dated Mar. 2, 2015, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/534,848, dated Aug. 11, 2016, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/271,850, dated May 11, 2011, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/052,172, dated Jul. 19, 2016, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/948,628, dated Sep. 8, 2006, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/761,760, dated Jan. 16, 2008, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/536,108, dated Dec. 3, 2015, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/536,108, dated May 4, 2017, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/534,848, dated Jun. 1, 2015, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/367,341, dated Jul. 24, 2012, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/905,248, dated Aug. 30, 2013, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/573,625, dated May 5, 2016, 38 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,231, dated Apr. 5, 2006, 4 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/145,880, dated Apr. 27. 2006, 4 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/145,880, dated Mar. 1, 2007, 4 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/573,625, dated Sep. 21, 2017, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/314,807, dated Jan. 18, 2007, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/562,313, dated Sep. 5, 2007, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/562,352, dated Jan. 14, 2008, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/748,388, dated Dec. 17, 2008, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,395, dated Oct. 3, 2005, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/216,225, dated Jul. 10, 2008, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/036,915, dated Oct. 8, 2008, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/875,488, dated Dec. 18, 2015, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,717, dated Dec. 14, 2005, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,717, dated May 31, 2006, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/494,988, dated Mar. 5, 2009, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/182,079, dated Feb. 26, 2010, 7 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,390, dated Dec. 15, 2005, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,231, dated Dec. 21, 2005, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/231,321, dated Jul. 24, 2006, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/468,047, dated Dec. 13, 2011, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 10/856,387, dated Dec. 14, 2005, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/233,931, dated Jul. 10, 2006, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/298,371, dated Sep. 9, 2014, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/168,876, dated Sep. 15, 2014, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 14/100,357, dated Sep. 15, 2014, 10 pages.
“Notice of Allowance”, U.S. Appl. No. 11/748,388, dated May 19, 2009, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 12/647,672, dated Nov. 1, 2012, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 10/948,628, dated May 3, 2007, 2 pages.
“Notice of Allowance”, U.S. Appl. No. 10/856,231, dated Jun. 28, 2006, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 11/231,321, dated Mar. 21, 2007, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 11/145,880, dated Sep. 21, 2007, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 11/314,807, dated Dec. 24, 2008, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 15/161,880, dated Sep. 8, 2017, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/601,705, dated Oct. 5, 2017, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/555,897, dated Jun. 8, 2015, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/298,371, dated Jul. 2, 2015, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/548,137, dated Dec. 10, 2015, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/555,897, dated Dec. 17, 2015, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/168,876, dated Feb. 12, 2016, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/875,488, dated Apr. 8, 2016, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/090,973, dated Mar. 16, 2017, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 10/856,387, dated Jun. 23, 2006, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 10/856,717, dated Mar. 13, 2007, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 10/948,628, dated Apr. 9, 2007, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 11/145,880, dated Jul. 5, 2007, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 11/562,313, dated May 23, 2008, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 11/761,760, dated Jul. 1, 2008, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 11/494,988, dated Jul. 17, 2009, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 12/182,079, dated Jun. 23, 2010, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 11/428,536, dated Feb. 8, 2011, 6 pages.
“Notice of Allowance”, U.S. Appl. No. 10/856,170, dated Dec. 13, 2005, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 10/856,390, dated Jun. 27, 2006, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/620,171, dated Feb. 17, 2014, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/573,625, dated Mar. 28, 2017, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 11/233,931, dated Aug. 10, 2006, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 11/216,225, dated Mar. 10, 2009, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 12/271,850, dated Oct. 6, 2011, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 13/619,681, dated Mar. 3, 2015, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/754,115, dated Dec. 24, 2015, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/754,115, dated May 4, 2016, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 15/179,350, dated Aug. 15, 2016, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/754,115, dated Sep. 20, 2016, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 15/248,576, dated Mar. 15, 2017, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 11/428,536, dated Jul. 23, 2010, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 12/468,047, dated May 31, 2012, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 13/367,341, dated Aug. 5, 2013, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 14/339,234, dated Oct. 27, 2015, 9 pages.
“Preinterview First Office Action”, U.S. Appl. No. 14/338,592, dated Oct. 31, 2014, 4 pages.
“Preinterview First Office Action”, U.S. Appl. No. 14/339,234, dated Nov. 19, 2014, 5 pages.
“Relative Humidity Information [Brochure]”, Indoor Health Products, Inc. (2002) Layton, Utah: Indoor Health Products, Inc. Retrieved from the Internet: <URL: http://www. relativehumidity-sensor.com/relative-humidity.html> on Jun. 18, 2004, 6 pages.
“Response to the Department of Homeland Security and Border Protection Conveyance Security Device Requirements, Version 1.2”, TeraHop Networks, Inc, Dec. 10, 2007, 62 pages.
“Restriction Requirement”, U.S. Appl. No. 11/562,313, dated Feb. 22, 2008, 5 pages.
“Restriction Requirement”, U.S. Appl. No. 12/468,047, dated Oct. 5, 2011, 5 pages.
“Restriction Requirement”, U.S. Appl. No. 10/948,628, dated Dec. 30, 2005, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 11/761,760, dated Dec. 11, 2007, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 10/948,628, dated Apr. 20, 2006, 7 pages.
“Restriction Requirement”, U.S. Appl. No. 12/193,641, dated Apr. 3, 2009, 7 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 11/145,880, dated Dec. 10, 2007, 2 pages.
“TeraHop Networks—Tradeshow Handouts”, MERIT-2030-2040 Gateway Controllers; MERIT-300 Incedent Node; MERIT-TL TeraLink System Software, Jan. 1, 2006, 6 pages.
“TeraHop Networks Atlanta Airport Fire-Recuse Project Description of Project Components”, TeraHop Networks, Feb. 7, 2008, 11 pages.
“TeraHop Networks—Documents A Through I, Including Brief Description”, 121 pages.
“TRF6901 Single-Chip RF Transceiver Product Catalog [Brochure].”, Texas Instruments, Inc. (2001-2003). Dallas, Texas: Texas Instruments, Inc., 27 pages.
“Waterbug: Electronic water detection at its best! [Brochure].”, Winland Electronics, Inc. (2011). Mankato, Minnesota: Winland Electronics Inc. Retrieved from the Internet: <URL:www.winland.com>, Jan. 1, 2011, 1 page.
“Ways to Prevent Mold Problems [Brochure].”, Toxic Black Mold Information Center. (2002). Layton, Utah: Toxic Black Mold Information Center. Retrieved from the Internet: <URL: http://www.toxic-black-mold-info.com/prevent.html> on Jun. 18, 2004, 12 pages.
“Website Page Detailing Features of Texas Instruments' Chipcon Products”, Accessed on Dec. 19, 2008, 1 page.
“Written Opinion”, Application No. PCT/US06/00868, dated Apr. 2, 2007, 3 pages.
“Written Opinion”, Application No. PCT/US2006/026158, dated Nov. 21, 2006, 7 pages.
Bourke, Tony “Server Load Balancing”, Sebastopol, California: O'Reilly Associates, Jan. 1, 2001, 182 pages.
Easley, Linda et al., “Global Container Security System”, U.S. Appl. No. 60/499,338—filed Sep. 3, 2003, 27 pages.
Garcia-Luna-Aceves, J J. “Source-Tree Routing in Wireless Networks”, Proceedings of Seventh International Conference on Network Protocols, 10 pages.
Gira, “Gira Dua/NdS smoke alarm: Double safety by measuring heat and scattered light. [Brochure]”, Radevormwald, Germany: GIRA. Retrieved from the Internet: <URL: http://www.gira.de/gebaeudetechniklprodukte/sicherheit/rauchmelder/rauchwarnmelderdualvds.html> on Apr. 18, 2013,, 7 pages.
Gira, “Gira Dua/VdS smoke alarm: Double safety by measuring heat and scattered light [Brochure]”, Radevormwald, Germany: GIRA. Retrieved from the Internet: <URL: http://www.gira.de/gebaeudetechniklprodukte/sicherheit/rauchmelder/rauchwarnmelderdualvds.html> on Apr. 18, 2013,, 14 pages.
Gira, “Installation and user manual: Smoke alarm device Dua/VdS [Brochure]”, Radevormwald, Germany: GIRA. Retrieved from the Internet: <URL: http://download.gira.de/data2/2330121 O.pdf> on Apr. 18, 2013., 20 pages.
Gu, Daniel L. et al., “C-ICAMA, A Centralized Intelligent Channel Assigned Multiple Access for Multi-Layer Ad-Hoc Wireless Networks with UAVs”, Conference: Wireless Communications and Networking Confernce, 2000, pp. 879-884.
Gu, Daniel L. “Hierarchical Routing for Multi-Layer Ad-Hoc Wireless Networks with UAVs”, 21st Century Military Communications Conference Proceedings, 5 pages.
Haartsen, Jaap “Bluetooth—The Universal Radio Interface for Ad Hoc, Wireless Connectivity”, Ericsson Review No. 3, 8 pages.
Haartsen, Jaap “Bluetooth: Vision, Goals, and Architecture”, Mobile Computing & Communications Review, vol. 1, No. 2, 8 pages.
Hubaux, Jean-Pierre et al., “Toward Self-Organized Mobile Ad Hoc Networks: The Terminodes Project”, IEEE Communications Magazine (vol. 39, Issue: 1, Jan. 2001 ), 7 pages.
Iwata, Atsushi et al., “Scalable Routing Strategies for Ad hoc Wireless Networks”, IEEE Journal on Selected Areas in Communications, 26 pages.
Keshavarzian, “Energy-Efficient Link Assessment in Wireless Sensor Networks”, Conference on the IEEE computer and Communications Societies, vol. 3, 14 pages.
Kidde, “Battery Operated Smoke Alarm with Hush: Model i9060 [Brochure].”, Mebane, North Carolina: Kidde, Jan. 1, 2009, 2 pages.
Lee, Sung-Ju “On-Demand Multicast Routing Protocol (ODMRP) for Ad Hoc Networks”, Retrieved at: https://tools.ietf.org/html/draft-ietf-manet-odmrp-02, 29 pages.
Melodia, Tommaso et al., “On the Interdependence of Distributed Topology Control and Geographical Routing in Ad Hoc and Sensor Networks”, IEEE Journal on Selected Areas in Communications, vol. 23, No. 3, pp. 520-532.
Mingliang, Jiang et al., “Cluster Based Routing Protocol (CBRP)”, Internet-Draft, National University of Singapore, 27 pages.
Morgan, Gary “Miniature Tags Provide Visibility & Cohesion for an LIA Battalion Level ‘Proof of Principle’”, Pacific NW National Laboratory, 11 pages.
Nageli, “Portable Detachable Self-Contained Tracking Unit for Two-Way Satellite Communication with a Central Server”, U.S. Appl. No. 60/444,029—filed Jan. 31, 2003, 38 pages.
Pei, Guangyu et al., “A Wireless Hierarchical Routing Protocol with Group Mobility”, Wireless Communications and Networking Conference, Jan. 21, 1999, 18 pages.
Pei, Guangyu et al., “Mobility Management in Hierarchical Multi-Hop Mobile Wireless Networks”, Eight International Conference on Computer Communications and Networks Proceedings., 6 pages.
Perkins, C E. “Mobile Ad Hoc Networking Terminology”, draft-ietf-manet-term-01.txt—Internet Draft, Nov. 17, 1998, 10 pages.
Perkins, Charles E. “Ad Hoc Networks”, Table of Contents, Chapters 1, 4, and 11, 112 pages.
Ramanathan, Ram et al., “Hierarchically-Organized, Multi-hop Mobile Wireless Networks for Quality-of-Service Support”, Mobile Networks and Applications, 36 pages.
Sharp, Kevin “Physical Reality: A Second Look, Supply Chain Systems”, http://www.idsystems.com/reader/1999_03/phys0399_pt2/index.htm, 5 pages.
Sommer, Ben “Group 4, Passive RF Tags”, 4 pages.
Stojmenovic, Ivan et al., “Design Guidelines for Routing Protocols in Ad Hoc and Sensor Networks with a Realistic Physical Layer”, IEEE Communications Magazine ( vol. 43, Issue: 3, Mar. 2005 ), 6 pages.
Valdevit, Evio “Cascading in Fibre Channel: how to build a multi-switch fabric”, Brocade Communications Systems, available at http://www.brocade.com/SAN/white_papers/pdf/Cascading.pdf, Jan. 1, 1999, 13 pages.
White, et al., “A Conceptual Model for Simulation Load Balancing”,, Proc. 1998 Spring Simulation Interoperability Workshop, Jan. 1, 1998, 7 pages.
Woo, Alec et al., “Taming the Underlying Challenges of Reliable Multihop Routing in Sensor Networks”, Proceedings of the 1st international conference on Embedded networked sensor systems, SenSys2003, Nov. 5, 2003, 14 pages.
“Final Office Action”, U.S. Appl. No. 15/590,880, dated Feb. 8, 2018, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/536,108, dated Feb. 22, 2018, 18 pages.
“Notice of Allowance”, U.S. Appl. No. 14/534,848, dated Jan. 24, 2018, 16 pages.
“Notice of Allowance”, U.S. Appl. No. 15/841,127, dated Feb. 26, 2018, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/821,213, dated May 18, 2018, 8 pages.
“Pre-Interview Communication”, U.S. Appl. No. 15/978,149, dated Jul. 3, 2018, 4 pages.
“Final Office Action”, U.S. Appl. No. 14/536,108, dated Aug. 29, 2018, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/590,880, dated Aug. 28, 2018, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/978,147, dated Sep. 19, 2018, 6 pages.
“Pre-Interview Office Action”, U.S. Appl. No. 15/978,145, dated Jul. 6, 2018, 4 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/590,880, dated Sep. 6, 2019, 10 Pages.
“Non-Final Office Action”, U.S. Appl. No. 15/978,149, dated Sep. 18, 2019, 11 Pages.
“Non-Final Office Action”, U.S. Appl. No. 15/821,213, dated Jun. 19, 2019, 9 pages.
“Final Office Action”, U.S. Appl. No. 15/978,149, dated May 1, 2019, 12 pages.
“Final Office Action”, U.S. Appl. No. 15/590,880, dated Apr. 4, 2019, 10 pages.
“Notice of Allowance”, U.S. Appl. No. 15/978,145, dated May 7, 2019, 5 pages.
“Final Office Action”, U.S. Appl. No. 15/821,213, dated Dec. 27, 2018, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/978,145, dated Oct. 24, 2018, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/978,149, dated Oct. 30, 2018, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 15/978,147, dated Jan. 17, 2019, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 15/821,213, dated Oct. 22, 2019, 7 Pages.
Related Publications (1)
Number Date Country
20180110006 A1 Apr 2018 US
Divisions (1)
Number Date Country
Parent 11562313 Nov 2006 US
Child 12182079 US
Continuations (7)
Number Date Country
Parent 15601705 May 2017 US
Child 15841092 US
Parent 15090973 Apr 2016 US
Child 15601705 US
Parent 14548137 Nov 2014 US
Child 15090973 US
Parent 14168876 Jan 2014 US
Child 14548137 US
Parent 12905248 Oct 2010 US
Child 14168876 US
Parent 12182079 Jul 2008 US
Child 12905248 US
Parent 10856231 May 2004 US
Child 11562313 US