System and method for utility metering and leak detection
Summary by NHIP
Utility leak detection system
The method monitors utility meters at desired intervals to record minimum usage and identify leaks by searching for time periods where flow exceeds a non-zero threshold. Distinctive elements include sensors such as optical, imaging, acoustic, or flow sensors that interface with electronic meters to detect continuous low-rate consumption.
Claim Score by NHIP
Abstract
The system and method for detecting water and/or gas leaks by monitoring usage patterns is described. In one embodiment, the existence of a leak is detected by looking for usage patterns wherein water or gas is always being used, at least at a low rate. A leak is indicated if usage does not drop to zero, at least for a period of time, during a given time interval (e.g., during a 24-hour period). The severity of the leak is indicated by the minimum amount of usage during the given time period. In one embodiment, the leak detection system is provided in connection with an Automatic Meter Reading (AMR) system.

Term
Term ended
Expired 28 September 2024, 2 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
9 claims: 1 independent, 8 dependent
- 1Broadest claimClaim Score 76, broad(NHIP)A method for detecting leaks, comprising:monitoring a utility meter at desired intervals using a sensor that senses a least one output of said utility meter;recording a minimum utility usage;and identifying an absence of a utility leak by searching for one or more time periods when recorded water flow does not exceed a predetermined non-zero threshold.
83 paragraphs in 5 sections, as filed
REFERENCE TO RELATED APPLICATION
0001The present application is a continuation of U.S. application Ser. No. 11/761,760 titled “SYSTEM AND METHOD FOR UTILITY METERING AND LEAK DETECTION”, which was filed Jun. 12, 2007, now U.S. Pat. No. 7,412,876 which is a continuation of U.S. application Ser. No. 10/948,628 titled “SYSTEM AND METHOD FOR UTILITY METERING AND LEAK DETECTION”, which was filed Sep. 23, 2004, now U.S. Pat. No. 7,228,726 the entire contents of which is hereby incorporated by reference.
BACKGROUND OF THE INVENTION
00021. Field of the Invention
0003The present invention relates to a system and method for electronic utility (e.g., water and gas) metering and leak detection.
00042. Description of the Related Art
0005In a home or building, utilities such as water and gas are used for various reasons throughout the day and night. For example, in homes, water is used randomly and for varying time intervals through the day and night. Although water usage tends to be less at night, water is still used (e.g., for toilets, automatic sprinklers, etc.). The water usage in commercial buildings follows a similar pattern. This makes it difficult to test for leaks, since there is no predictable time during the day or night that water usage drops to zero.
0006As is known, some waterline leaks can be easily detected because of the presence of detected ground water or the presence of water puddles in the vicinity of a water pipe. However, other waterline leaks go undetected until a water bills become unusually high or water damage is discovered.
0007Gas leaks are potentially more dangerous than water leaks, and can be more difficult to detect.
0008Owners of large apartment buildings and commercial buildings face additional problems in monitoring water usage and leak detection. The amount of water and other utilities used by such commercial structures is typically much larger than the usage of a residence or other smaller structure. Moreover, the plumbing and sprinkler systems of such structures tend to be more complex than the systems found in a residence. Thus, any inefficiencies in the usage of utilities is magnified in a large commercial structure, and the costs of such inefficiencies are magnified. For example, in a large commercial structure, water is used for toilets, industrial processes, heating and air-conditioning, fire sprinkler systems, and irrigation sprinkler systems. The management of a large commercial building often does not have an accurate accounting of water usage by the various systems. A maintenance issue as minor as a broken irrigation sprinkler head can cause increased and unnecessary water usage.
0009Conventional water and gas meters used in connection with residential and commercial structures measure the total amount of water or gas used, but do not monitor the usage patterns. Thus, conventional meters do not provide the information needed to detect leaks.
SUMMARY
0010The system and method disclosed herein solves these and other problems by detecting water and/or gas leaks -by monitoring usage patterns. In one embodiment, the existence of a leak is detected by looking for usage patterns wherein water or gas is always being used, at least at a low rate. A leak is indicated if usage does not drop to zero (or below some threshold value), at least for a period of time, during a given time interval (e.g., during a 24-hour period). The severity of the leak is indicated by the minimum amount of usage during the given time period. In one embodiment, the leak detection system is provided in connection with an Automatic Meter Reading (AMR) system.
0011In one embodiment, an imaging sensor is provided to a water or gas meter to read various dials on the meter. In one embodiment, an optical sensor is provided to a water or gas meter to read movement of a lowest-level dials or indicator on the meter. In one embodiment, an acoustic sensor is provided to a water or gas meter to detect flow through the meter.
0012In one embodiment, the monitoring system interrupts utility service if utility usage exceeds a set maximum during a given time period. Excess water usage can occur, for example, if a water line breaks, a building owner exceeds usage limits, etc. Excess gas usage can occur, for example, if a thermostat fails, if a pool heater is left on accidentally, if a stove is left on accidentally, etc. Thus, for example, the monitoring system can be configured to shut off utility service (or notify the utility to shut off service) if water or gas usage exceeds a maximum during a specified time period (e.g., one hour, one day, one week, etc.).
BRIEF DESCRIPTION OF THE DRAWINGS
0013<figref idref="DRAWINGS">FIG. 1A</figref> shows a dial face of a typical water meter register.
0014<figref idref="DRAWINGS">FIG. 1B</figref> shows a dial face of a typical gas meter register.
0015<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of an automatic meter reading system for use in connection with a leak detection system.
0016<figref idref="DRAWINGS">FIG. 3</figref> illustrates the leak-detection AMR system provided to a water meter in a retrofit installation.
0017<figref idref="DRAWINGS">FIG. 4</figref> illustrates the leak-detection AMR system provided to a water meter as original equipment.
0018<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram illustrating various sensors that can be used to detect low-level flow through a water meter or gas meter.
0019<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart showing one embodiment of the operation of the ETR unit wherein relatively continuous monitoring is provided.
0020<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart showing one embodiment of operation of the ETR unit wherein periodic monitoring is provided.
0021<figref idref="DRAWINGS">FIG. 8A</figref> shows one embodiment of a low-flow sensor adapted to measuring leaks in plumbing systems by using a differential pressure sensor.
0022<figref idref="DRAWINGS">FIG. 8B</figref> shows one embodiment of a low-flow sensor adapted to measuring leaks in plumbing systems by using a pressure sensor.
0023<figref idref="DRAWINGS">FIG. 9A</figref> shows one embodiment of a system <b>900</b> to measure leaks in plumbing systems in connection with a water meter <b>901</b>.
0024<figref idref="DRAWINGS">FIG. 9B</figref> shows an integrated low-flow/high-flow meter system that provides AMR metering, leak detection, and water shutoff functions.
0025<figref idref="DRAWINGS">FIG. 10</figref> shows a water metering system adapted to monitoring water use and/or leaks in connection with a sprinkler valve that provides water to one or more sprinkler heads.
0026<figref idref="DRAWINGS">FIG. 11</figref> shows a water metering system adapted to monitoring water use and/or leaks in connection with a manifold having a plurality of sprinkler valves that provides water to one or more sprinkler heads.
0027<figref idref="DRAWINGS">FIG. 12</figref> shows a water metering system adapted to monitoring water use and/or leaks in connection with a commercial structure (or residential structure) having one or more water usage zones and one or more sprinkler zones.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
0028<figref idref="DRAWINGS">FIG. 1A</figref> shows a dial face of a typical water meter register <b>100</b>. The register includes a digital indicator <b>102</b> that reads water used in cubic ft, a radial dial <b>101</b> and radial hand <b>105</b> that indicate water usage between 0 and 1 cu ft, and a low-flow indicator <b>103</b> that makes several rotations for each rotation of the radial hand <b>105</b>.
0029<figref idref="DRAWINGS">FIG. 1B</figref> shows a typical gas meter <b>150</b>. In the meter <b>150</b>, a group of radial dials <b>160</b>-<b>164</b> display digits corresponding to gas usage in cubic ft. In <figref idref="DRAWINGS">FIG. 1B</figref>, the lest-significant digit is displayed by the dial <b>160</b> and the most significant digit is displayed by the dial <b>164</b>. The dial <b>160</b> is similar in effect to the low-flow indicator <b>103</b>.
0030Historically, the utility meters shown in <figref idref="DRAWINGS">FIGS. 1A and 1B</figref> were read manually on periodic basis. Many communities have converted to Automatic Meter Reading (AMR) systems wherein the register is read electronically and remotely. The Automatic Meter Reading system allows the utility company to save on meter reading costs, provide better information about utility use, and provide more accurate billings. Because the AMR systems reduce our meter reading and meter maintenance costs, the systems typically pay for themselves very quickly.
0031In addition to, or in lieu of, the benefit provided to the utility company the AMR system can also be used by the building owner or manager to provide utility information for a building management system to provide cost tracking, maintenance diagnostics, leak detection, etc. Thus, in one embodiment, data from the AMR is provided to monitoring system such as, for example, a building monitoring system, a home computer system, etc.
0032Water and gas AMR systems are similar in nature, and so much of the following discussion refers to water meters with the understanding that the techniques used for water meters can also be used for gas meters. Most AMR systems use miniature radio transmitters attached to the water meter register <b>100</b>. Data from the AMR meter can be collect by readings from handheld radio receivers, from moving vehicles, or from fixed receivers (e.g., mounted in the building, mounted on light poles, etc.). With this process, one driver in a truck is able to read more meters in one day than an entire staff of meter readers. The AMR systems also alleviates access problems, since the utility company does not need access to the meter in order to obtain a reading. The system also allows the building owner or manager to collect utility meter data on a regular (or even continuous) basis.
0033In an AMR system, the utility meter is equipped with an Encoder-Receiver-Transmitter (ERT) device. <figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of an Encoding-Transmitting-Receiving (ETR) ETR unit <b>200</b> for use in connection with a utility meter. In the ETR unit <b>200</b>, one or more sensors <b>201</b> and a transceiver <b>203</b> are provided to a controller <b>202</b>. The controller <b>202</b> typically provides power, data, and control information to the sensor(s) <b>201</b> and the transceiver <b>202</b>. A power source <b>206</b> is provided to the controller <b>202</b>. An optional tamper sensor <b>205</b> (not shown) is also provided to the controller <b>202</b>.
0034In one embodiment, the transceiver <b>203</b> is configured for wireless communication. In on embodiment, the transceiver <b>203</b> is configured for wire or fiber-optic communication on a computer network, telephone network, etc.
0035<figref idref="DRAWINGS">FIG. 3</figref> illustrates the leak-detection AMR system provided to a water meter in a retrofit installation. The sensors <b>201</b> are configured as a sensor module <b>302</b> that is provided to the meter to read the meter register. <figref idref="DRAWINGS">FIG. 5</figref> describes various sensors that can be used to read a conventional (non-electronic) register. In one embodiment, the sensors <b>201</b> read the low-flow indicator, such as, for example, a low-flow indicators shown in <figref idref="DRAWINGS">FIG. 1A</figref> or <b>1</b>B. In one embodiment, the sensors <b>201</b> reads the low-flow indicator using an imaging sensor such as, for example, a CCD or CMOS imaging sensor. In one embodiment, the sensors <b>201</b> reads the low-flow indicator using a illumination source and an optical sensor, such as, for example, a photodiode, phototransistor, or array of such. In one embodiment, the sensors <b>201</b> reads the low-flow indicator without substantially obscuring the other indicators of the meter. In one embodiment, the sensors <b>201</b> is positioned to the side of the low-flow indicator such that the low-flow indicator is still visible.
0036<figref idref="DRAWINGS">FIG. 4</figref> illustrates the leak-detection AMR system provided to a water meter as original equipment. In <figref idref="DRAWINGS">FIG. 4</figref>, the ERT <b>202</b> is provided directly to an electronic register on the water meter.
0037In a conventional AMR system, the ERT does not take continuous readings, but rather “sleeps,” waiting for the meter reader to approach. The meter reader's truck-mounted reading device sends out a continuous “wake up” signal. When an ERT receives a wake up signal, it checks the reading on the meter register, encodes it into a digital signal, and begins transmitting its identification number and the current reading. After a few minutes, the ERT stops transmitting and goes back “to sleep,” waiting for the next “wake up” signal. The truck-mounted computer system matches the ERT identification number with your property and records the reading. At the end of the day, the meter reader unloads the information to the utility company billing system.
0038The ERT is an electronic device designed to read the meter register and transmit the signal. The radio signals used to wake up the ERT and to transmit the signals are relatively weak, typically operating in the 900 MHz frequency band. The devices are usually powered by two long-lasting batteries, designed to last 15 to 20 years. Pit ERTs are usually used for meters located in pits outside the building. Remote ERTs are used when the meter is inside the building or when the ERT needs to be located some distance away from the meter.
0039The Pit ERT mounts directly on the cast iron or concrete lid of an outdoor meter pit. It is typically sturdy enough to stand up to the weather and a certain amount of traffic load. In one embodiment, the ERT looks like a black mushroom with a 7-inch diameter cap and a 2-inch diameter “stem” that passes through a hole in the lid. A wire connects the ERT to the meter register. In sidewalks, a special lid is used that holds the ERT underneath and out of the way of pedestrians.
0040In one embodiment, the monitoring system includes a battery-operated ETR unit <b>200</b> that detects a condition, such as, for example, water or gas flow. The ETR unit is provided to a utility meter for a building, apartment, office, residence, etc. In order to conserve battery power, the ETR unit is normally placed in a low-power mode. In one embodiment, while in the low power mode, the ETR unit takes regular sensor readings and evaluates the readings to determine if an anomalous condition exists. In response to a wake-up signal, the ETR unit also “wakes up” and sends status information to the base unit (or reading device) and then listens for commands for a period of time.
0041In one embodiment, the ETR unit <b>200</b> is bi-directional and configured to receive instructions from the reading device. Thus, for example, the reading device 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 ETR 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 ETR unit reports its general health and status to the reading device (e.g., results of self-diagnostics, battery health, etc.).
0042In one embodiment, the ETR 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 reading device. The two wake-up modes, or combinations thereof, can occur at different intervals.
0043In one embodiment, the ETR units use spread-spectrum techniques to communicate with the base unit and/or the reading device. In one embodiment, the ETR units use frequency-hopping spread-spectrum. In one embodiment, each ETR unit has an Identification code (ID) and the ETR units attaches its ID to outgoing communication packets. In one embodiment, when receiving wireless data, each ETR unit ignores data that is addressed to other ETR units.
0044In one embodiment, the ETR unit <b>200</b> provides bi-directional communication and is configured to receive data and/or instructions from the reading device. Thus, for example, the reading device can instruct the ETR unit <b>200</b> 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 ETR unit <b>200</b> reports its general health and status on a regular basis (e.g., results of self-diagnostics, battery health, etc.)
0045In one embodiment, the ETR unit <b>200</b> 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 reading device. The two wake-up modes, or combinations thereof, can occur at different intervals.
0046In one embodiment, the ETR unit <b>200</b> use spread-spectrum techniques to communicate with the reading device. In one embodiment, the ETR unit <b>200</b> uses frequency-hopping spread-spectrum. In one embodiment, the ETR unit <b>200</b> has an address or identification (ID) code that distinguishes the ETR unit <b>200</b> from the other ETR units. The ETR unit <b>200</b> attaches its ID to outgoing communication packets so that transmissions from the ETR unit <b>200</b> can be identified by the reading device. The reading device attaches the ID of the ETR unit <b>200</b> to data and/or instructions that are transmitted to the ETR unit <b>200</b>. In one embodiment, the ETR unit <b>200</b> ignores data and/or instructions that are addressed to other ETR units.
0047In one embodiment, the sensor <b>201</b> communicates with the reading device 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 reading device on bands above and/or below the 900 MHz band. In one embodiment, the sensor, reading device, 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 device such as another reading device, a cordless telephone, etc.) then the sensor, reading device, and/or base unit changes to a different channel. In one embodiment, the sensor, reading device, 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.
0048Frequency-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.
0049In one embodiment, the ETR unit <b>200</b>, the reading device, and the reading device communicate using FHSS wherein the frequency hopping of the ETR unit <b>200</b>, the reading device, and the reading device are not synchronized such that at any given moment, the ETR unit <b>200</b> and the reading device are on different channels. In such a system, the reading device communicates with the ETR unit <b>200</b> using the hop frequencies synchronized to the reading device rather than the ETR unit <b>200</b>. The reading device then forwards the data to the ETR unit using hop frequencies synchronized to the ETR unit <b>200</b>. Such a system largely avoids collisions between the transmissions by the reading device and the reading device.
0050In one embodiment, the ETR units <b>200</b> uses FHSS and the ETR units <b>102</b>-<b>106</b> are not synchronized. Thus, at any given moment, it is unlikely that any two or more of the ETR units 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 <b>100</b>. If a collision does occur, data lost due to the collision is effectively re-transmitted the next time the ETR units transmit sensor data. When the ETR units and reading device units <b>110</b>-<b>111</b> 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 ETR units, and the reading device use the same hop rate. In one embodiment, the ETR units and the reading device use the same pseudo-random algorithm to control channel hopping, but with different starting speeds. In one embodiment, the starting speed for the hop algorithm is calculated from the ID of the ETR units or the reading device.
0051In an alternative embodiment, the base unit communicates with the ETR unit <b>200</b> by sending a communication packet addressed to the reading device, where the packet sent to the reading device includes the address of the ETR unit <b>200</b>.
0052In one embodiment, the transceiver <b>203</b> is based on a TRF 6901 transceiver chip from Texas Instruments, Inc. In one embodiment, the controller <b>202</b> is a conventional programmable microcontroller. In one embodiment, the controller <b>202</b> is based on a Field Programmable Gate Array (FPGA), such as, for example, provided by Xilinx Corp. In one embodiment, the sensor <b>201</b> includes an optoelectric sensor configured to detect movements of a display on the utility meter. In one embodiment, the sensor <b>201</b> includes an imaging sensor configured to read the utility meter. In one embodiment, the sensor <b>201</b> includes an illumination device for illuminating the utility meter display. In one embodiment, the sensor <b>201</b> includes an acoustic sensor for detecting the acoustic sounds of flow through the utility meter. In one embodiment, the sensor <b>201</b> includes a register sensor for reading an electronic utility meter register.
0053The controller <b>202</b> receives sensor data from the sensor(s) <b>201</b>. Some sensors <b>201</b> produce digital data. However, for many types of sensors <b>201</b>, the sensor data is analog data. Analog sensor data is converted to digital format by the controller <b>202</b>. In one embodiment, the controller evaluates the data received from the sensor(s) <b>201</b> and determines whether the data indicates a leak or other anomalous condition. In one embodiment, the controller <b>202</b> 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 or indicative of a leak. In one embodiment, the data threshold is programmed into the controller <b>202</b>. In one embodiment, the data threshold is programmed by the reading device by sending instructions to the controller <b>202</b>.
0054<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram illustrating various sensors that can be used to detect low-level flow through a water meter or gas meter. In one embodiment, an acoustic sensor is provided to the meter to detect flow through the meter. In one embodiment, an imaging sensor <b>501</b> is provided to the meter to read the digital indicators <b>102</b> and/or the dials <b>160</b>-<b>164</b>. In one embodiment, an illumination source <b>502</b> is provided to illuminate the digital indicators <b>102</b> and/or the dials <b>160</b>-<b>164</b> for the imaging sensor <b>501</b>. In one embodiment, an illumination source <b>504</b> and optical sensor <b>503</b> are provided to detect movement of the radial hand <b>105</b> and/or the fine sensor <b>103</b>. The acoustic sensor <b>509</b>, the imaging sensor <b>501</b>, and/or the optical sensor <b>503</b> are embodiments of the sensor <b>201</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>. Other sensors, such as, for example, magnetic sensors, can be used in combination with the acoustic sensor <b>509</b>, the imaging sensor <b>501</b>, and/or the optical sensor <b>503</b> or used the alternative.
0055The acoustic sensor <b>509</b>, the imaging sensor <b>501</b>, and/or the optical sensor <b>503</b> are provided to the controller <b>202</b>. The controller reads the utility meter by collecting data from the acoustic sensor <b>509</b>, the imaging sensor <b>501</b>, and/or the optical sensor <b>503</b>.
0056In one embodiment, the controller <b>202</b> reads the sensors <b>201</b> at regular periodic intervals. In one embodiment, the controller <b>202</b> reads the sensors <b>201</b> at random intervals. In one embodiment, the controller <b>202</b> reads the sensors <b>201</b> in response to a wake-up signal from the reading device. In one embodiment, the controller <b>202</b> sleeps between sensor readings.
0057In one embodiment, the controller <b>202</b> reads the fine detail indicator <b>103</b> or the lowest-order indicator <b>160</b> on a regular (or random) basis in order to detect leaks. In one embodiment, the controller <b>202</b> wakes up and takes a series of readings from the low-flow indicator <b>103</b> or the lower-order indicator <b>160</b> on a programmed basis to determine usage patterns and for leak detection. If the controller <b>202</b> determines that utility usage appears to be continuous then the controller <b>202</b> assumes a leak exists.
0058In one embodiment, the controller <b>202</b> uses artificial intelligence to determine a sensor reading interval. In one embodiment, the controller <b>202</b> reads the low-flow indicators on a period basis. If the controller <b>202</b> determines that usage is zero during a prescribed number of intervals, then the controller assumes that no leak exists and the controller can program a relatively long interval between readings. If the controller determines that usage is never zero, then the controller <b>202</b> assumes that a leak may exist, and the controller can program a relatively shorter interval between readings in order to search for an interval when no usage occurs. If the relatively shorter interval still does not produce a zero reading, then the controller <b>202</b> can, in one embodiment, take continuous readings for a period of time (e.g., 24 hours, 48 hours, etc.) to search for a period when no usage occurs. If the controller is unable to find a period when usage is zero, then the controller reports a leak condition. In one embodiment, the controller <b>202</b> reports minimum utility usage to the query device to allow the utility company to evaluate possible leak conditions.
0059In one embodiment, the controller <b>202</b> is configured to use a threshold value (rather than zero) in making determinations regarding possible leak conditions.
0060<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart showing one embodiment of the operation of the ETR unit <b>200</b> wherein relatively continuous monitoring is provided. In <figref idref="DRAWINGS">FIG. 6</figref>, a power up block <b>601</b> is followed by an initialization block <b>602</b>. After initialization, the ETR unit <b>200</b> checks for a fault condition (e.g., activation of the tamper sensor, low battery, internal fault, etc.) in a block <b>603</b>. A decision block <b>604</b> checks the fault status. If a fault has occurred, then the process advances to a block <b>605</b> were the fault information is transmitted to the reading device (after which, the process advances to a block <b>612</b>); otherwise, the process advances to a block <b>606</b>. In the block <b>606</b>, the ETR unit <b>200</b> takes a sensor reading from the sensor(s) <b>201</b>. The sensor data is subsequently evaluated in a block <b>607</b>. If the sensor data is abnormal, then the process advances to a transmit block <b>609</b> where the sensor data is transmitted to the reading device (after which, the process advances to a block <b>612</b>); otherwise, the process advances to a timeout decision block <b>610</b>. If the timeout period has not elapsed, then the process returns to the fault-check block <b>603</b>; otherwise, the process advances to a transmit status block <b>611</b> where normal status information is transmitted to the reading device. In one embodiment, the normal status information transmitted is analogous to a simple “ping” which indicates that the ETR unit <b>200</b> is functioning normally. After the block <b>611</b>, the process proceeds to a block <b>612</b> where the ETR unit <b>200</b> momentarily listens for instructions from the monitor reading device. If an instruction is received, then the ETR unit <b>200</b> performs the instructions, otherwise, the process returns to the status check block <b>603</b>. In one embodiment, transceiver <b>203</b> is normally powered down. The controller <b>202</b> powers up the transceiver <b>203</b> during execution of the blocks <b>605</b>, <b>609</b>, <b>611</b>, and <b>612</b>. The monitoring reading device can send instructions to the ETR unit <b>200</b> to change the parameters used to evaluate data used in block <b>607</b>, the listen period used in block <b>612</b>, etc.
0061Relatively continuous monitoring, such as shown in <figref idref="DRAWINGS">FIG. 6</figref>, is appropriate for ETR 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.). <figref idref="DRAWINGS">FIG. 7</figref> is a flowchart showing one embodiment of operation of the ETR unit <b>200</b> wherein periodic monitoring is provided. In <figref idref="DRAWINGS">FIG. 7</figref>, a power up block <b>701</b> is followed by an initialization block <b>702</b>. After initialization, the ETR unit <b>200</b> 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 <b>704</b> followed by a transmit fault block <b>705</b>. If no fault occurs during the sleep period, then when the specified sleep period has expired, the process enters a block <b>706</b> where the ETR unit <b>200</b> takes a sensor reading from the sensor(s) <b>201</b>. The sensor data is subsequently sent to the monitoring reading device in a report block <b>707</b>. After reporting, the ETR unit <b>200</b> enters a listen block <b>708</b> where the ETR unit <b>200</b> listens for a relatively short period of time for instructions from monitoring computer <b>708</b>. If an instruction is received, then the ETR unit <b>200</b> performs the instructions, otherwise, the process returns to the sleep block <b>703</b>. In one embodiment, the sensor <b>201</b> and transceiver <b>203</b> are normally powered down. The controller <b>202</b> powers up the sensor <b>201</b> during execution of the block <b>706</b>. The controller <b>202</b> powers up the transceiver during execution of the blocks <b>705</b>, <b>707</b>, and <b>708</b>. The monitoring reading device can send instructions to the ETR unit <b>200</b> to change the sleep period used in block <b>703</b>, the listen period used in block <b>708</b>, etc.
0062In one embodiment, the ETR unit transmits sensor data until a handshaking-type acknowledgement is received. Thus, rather than sleep if no instructions or acknowledgements are received after transmission (e.g., after the decision block <b>613</b> or <b>709</b>) the ETR unit <b>200</b> retransmits its data and waits for an acknowledgement. The ETR unit <b>200</b> continues to transmit data and wait for an acknowledgement until an acknowledgement is received. In one embodiment, the ETR unit accepts an acknowledgement from a reading device and it then becomes the responsibility of the reading device to make sure that the data is forwarded to the reading device. In one embodiment, the reading device does not generate the acknowledgement, but rather forwards an acknowledgement from the reading device to the ETR unit <b>200</b>. The two-way communication ability of the ETR unit <b>200</b> provides the capability for the reading device to control the operation of the ETR unit <b>200</b> and also provides the capability for robust handshaking-type communication between the ETR unit <b>200</b> and the reading device.
0063Regardless of the normal operating mode of the ETR unit <b>200</b> (e.g., using the Flowcharts of <figref idref="DRAWINGS">FIGS. 6</figref>, <b>7</b>, or other modes) in one embodiment, the monitoring reading device can instruct the ETR unit <b>200</b> to operate in a relatively continuous mode where the sensor repeatedly takes sensor readings and transmits the readings to the monitoring reading device.
0064In one embodiment, a shutoff valve is provided, so that the monitoring system <b>100</b> can shutoff the water supply when a leak and/or energy usage is detected. In one embodiment, the shutoff valve is controlled by the ETR unit <b>200</b>. In one embodiment, the ETR unit <b>200</b> receives instructions from the reading device to shut off the water supply. Similarly, in one embodiment, the ETR unit <b>200</b> controls a gas shutoff valve to shut off the gas supply when a gas leaks is detected.
0065In one embodiment, data from the ETR unit <b>200</b> is provided to a monitoring system The monitoring system gathers water (or other utility) usage data from each of the meters and records utility usage through each meter. In one embodiment, water leaks are detected by examining data from the ETR unit <b>200</b> for the lowest flow rate. An occasional flow rate of zero indicates that there are no leaks. If the flow rate never drops to zero, then either there is a leak or some appliance or system is using water continuously (e.g., a drip irrigation system). If the use never drops to zero, and there is a leak, then the lowest flow rate likely corresponds to the leak flow rate. If the use never drops to zero, then the monitoring system (or utility) can warn the building owner or manager that a leak is suspected. AMR systems where the ETR unit sleeps until awakened by a “wake up” signal and then read the utility meter (e.g., once per month) cannot be used for leak detection because such systems only obtain accumulated data from the mechanical digital indicators <b>102</b> on the meter. Leak detection is based on relatively continuous monitoring (or monitoring at regular or random intervals) such that flow during times when only a leak is flowing is measured. Moreover, detecting leaks by looking for continuous flow does not provide information on the severity of the leak, since merely knowing that water flowed continuously does not indicate what the lowest flow rate is. In one embodiment, the monitoring system calculates water wasted by leaks in the system according to the severity of the leak (e.g., water wasted per day is approximately the leak flow rate per hour times 24). In one embodiment, the monitoring system provides graphs of utility usage by day, by time of day, by month, etc.
0066In some cases, conventional water meters used for providing water to buildings do not read accurately, if at all, at the lowest flow rates produced by a small leak. <figref idref="DRAWINGS">FIG. 8A</figref> shows one embodiment of a low-flow sensor system <b>800</b> for measuring leaks in plumbing systems by using a differential pressure sensor <b>804</b>. An electrically-controlled valve <b>802</b> is provided to a water service line. The first input of the differential pressure sensor <b>804</b> is provided to the water service line on the input side of the valve <b>802</b>, and a second input of the differential pressure sensor <b>804</b> is provided to the water service line on the output side of the valve <b>802</b>. A controller <b>803</b> is provided to the valve <b>802</b> and the pressure sensor <b>804</b>. In one embodiment, the differential pressure sensor provides an output signal that is related to the pressure difference between the first input and the second input. In one embodiment, the pressure sensor is configured as a switch that opens or closes when the pressure differential exceeds a specified value.
0067To test for leaks, the controller <b>803</b> sends an electrical signal to close the valve <b>802</b>. When the valve is closed, the controller <b>803</b> obtains sensor data from the sensor <b>804</b>. If there is a leak in the plumbing attached to the output side of the valve <b>802</b>, then a pressure difference will be measured by the sensor <b>804</b>. The severity of the leak is related to the speed at which the pressure differential increases. If the sensor <b>804</b> is configured as a switch, then the severity of the leak is related to the amount of time that elapses between the closing of the valve <b>802</b> and the operation of the switch in response to the pressure differential. Since water is a relatively non-compressible fluid, a pressure difference across the valve <b>802</b> will arise relatively quickly, and thus the meter controller only needs to close the valve for a relatively short period of time. In one embodiment, the controller <b>803</b> immediately opens the valve <b>802</b> upon reaching a specified pressure differential. A substantial increase in the slope of the differential pressure curve (i.e., the change in differential pressure versus time) is typically indicative of the opening of a valve downstream of the valve <b>802</b>. Thus, in one embodiment, the controller <b>803</b> immediately opens the valve <b>802</b> upon sensing such a change in slope.
0068If water is flowing in the water service line (when the valve <b>802</b> is open), then a relatively small pressure differential will be measured by the sensor <b>804</b>. If no water (or very little water) is flowing in the water service line, then no pressure differential will be measured by the sensor <b>804</b>. In one embodiment, the controller <b>803</b> does not close the valve <b>802</b> when the differential pressure measured by the pressure sensor <b>804</b> suggests that water is flowing in the line. In one embodiment, when the valve <b>802</b> is closed during a leak test, the controller <b>803</b> senses when a water valve downstream of the valve <b>802</b> has been opened because of the relatively sudden increase in the differential pressure sensed by the pressure sensor <b>804</b>. When such an event occurs, the controller <b>803</b> terminates the leak test by immediately opening the valve <b>802</b>.
0069In one embodiment the controller “tests” for water flow by partially closing the valve <b>802</b>. If water is flowing in the water service line, then partial closure of the valve <b>802</b> will cause the differential pressure sensor <b>804</b> to sense a pressure difference. By contrast, if only leakage water is flowing in the water service line, the partial closure of the valve <b>802</b> will not cause a significant pressure differential. If, through partial closure, the controller <b>803</b> determines that water is flowing in the line, then the leak test is terminated. If, through partial closure, the controller <b>803</b> determines that no water (or very little water) is flowing in the line, then the valve <b>802</b> is fully closed for the leak test. Partial closure allows the low-flow system <b>800</b> to test for leaks without substantially impacting normal water usage.
0070<figref idref="DRAWINGS">FIG. 8B</figref> shows one embodiment of a low-flow sensor system <b>801</b> for measuring leaks in plumbing systems by using a pressure sensor <b>808</b>. The system <b>801</b> includes the electrically-controlled valve <b>802</b> and the controller <b>803</b>. The pressure sensor <b>808</b> is provided to the water service line on the output side of the valve <b>802</b>. The output of the pressure sensor <b>808</b> is provided to the controller <b>803</b>. In one embodiment, the pressure sensor <b>808</b> provides an output signal that is related to the pressure in the output line. In one embodiment, the pressure sensor is configured as a switch that opens or closes when the pressure exceeds a specified value.
0071To test for leaks, the controller <b>803</b> sends an electrical signal to close the valve <b>802</b>. When the valve is closed, the controller <b>803</b> obtains sensor data from the sensor <b>808</b>. If there is a leak in the plumbing attached to the output side of the valve <b>802</b>, then a drop will be measured by the sensor <b>804</b>. The severity of the leak is related to the speed at which the pressure drops. If the sensor <b>808</b> is configured as a switch, then the severity of the leak is related to the amount of time that elapses between the closing of the valve <b>802</b> and the operation of the switch in response to the pressure drop. Since water is a relatively non-compressible fluid, the pressure will drop relatively quickly, and thus the meter controller only needs to close the valve for a relatively short period of time. In one embodiment, the controller <b>803</b> measures a relative pressure drop by obtaining a pressure reading from the pressure sensor <b>808</b> before closing the valve. The controller <b>803</b> can then compare the difference in the pressure measured by the sensor <b>808</b> before and after the closing of the valve <b>802</b>.
0072If water is flowing in the water service line (when the valve <b>802</b> is open), then the pressure measured by the sensor <b>808</b> will be relatively less than the static pressure in the line. In one embodiment, the sensor determines a static pressure by obtaining sensor data readings from the pressure sensor <b>808</b> over a period of time and determining a maximum steady-state (non-transient) pressure. In one embodiment, the controller <b>803</b> does not close the valve <b>802</b> when the pressure measured by the pressure sensor <b>808</b> is relatively lower than the static pressure (by a threshold amount). In one embodiment, when the valve <b>802</b> is closed during a leak test, the controller <b>803</b> senses when a water valve downstream of the valve <b>802</b> has been opened because of the relatively sudden pressure drop sensed by the pressure sensor <b>808</b>. When such an event occurs, the controller <b>803</b> terminates the leak test by immediately opening the valve <b>802</b>. In one embodiment, the controller <b>803</b> immediately opens the valve <b>802</b> upon reaching a specified relative pressure drop. A substantial increase in the slope of the pressure curve (i.e., the change in pressure versus time) is typically indicative of the opening of a valve downstream of the valve <b>802</b>. Thus, in one embodiment, the controller <b>803</b> immediately opens the valve <b>802</b> upon sensing such a change in slope.
0073One of ordinary skill in the art will recognize that the systems <b>800</b>, <b>801</b> can also be used for measuring leaks in gas systems (e.g., natural gas, propane, etc.).
0074The low-flow sensor systems <b>800</b>, <b>801</b> can be used alone or in connection with an AMR water meter as described in connection with FIGS. <b>1</b>A and <b>2</b>-<b>7</b>. In one embodiment, the low-flow sensor systems <b>800</b>, <b>801</b> are configured to test for leaks when the AMR water meter determines that little or no water is flowing.
0075<figref idref="DRAWINGS">FIG. 9A</figref> shows one embodiment of a system <b>900</b> to measure leaks in plumbing systems in connection with a water meter <b>901</b>. The water meter <b>901</b> can be a conventional water meter or an AMR water meter (as shown). The differential pressure sensor <b>804</b> is provided to the input and output of the water meter <b>901</b>. The water meter <b>901</b> produces a pressure drop when water is flowing through the meter, and the water meter <b>901</b> produces no pressure drop when no water is flowing through the meter. Thus, if there are not leaks in the system fed by the meter <b>901</b>, during periods of no water flow, the differential pressure sensor <b>804</b> will measure substantially no pressure difference. The pressure difference measured by the pressure sensor <b>804</b> when a leak exists will depend somewhat on the position of the turbine blades (or impeller) blades in the meter <b>901</b> when the meter stops turning. In some cases, for small leaks, there is not enough water flowing through the meter <b>901</b> to cause the impeller to turn. Moreover, for a given flow rate due to a leak, the pressure drop across the meter <b>901</b> varies somewhat depending on the orientation of the impeller. Thus, in one embodiment, the controller <b>903</b> determines the likelihood of a leak based on a statistical analysis. Over a period of time, the impeller blades will stop in various orientations. The controller <b>903</b> takes readings over a number of days to determine the statistically lowest pressure difference. The statistically lowest pressure difference is then related to the magnitude of any leaks in the system.
0076<figref idref="DRAWINGS">FIG. 9B</figref> shows a block diagram of an integrated low-flow/high-flow meter system <b>901</b> that provides AMR metering, leak detection, and water shutoff functions. In the system <b>901</b>, a relatively low-flow sensor <b>909</b>, such as, for example, the low-flow sensor systems <b>800</b> or <b>801</b> is provided in series with a conventional water meter apparatus <b>908</b>. The relatively low-flow sensor <b>909</b> and the meter apparatus <b>908</b> are provided to a controller <b>910</b>. In one embodiment, the controller <b>910</b> provides AMR functions. In one embodiment, the controller <b>910</b> periodically takes low-flow sensor readings using the low-flow sensor <b>909</b> when the meter apparatus <b>908</b> indicates that no water is flowing. In one embodiment, the controller <b>910</b> uses an electrically-controlled valve in the low-flow sensor <b>909</b> to shut off water through the system <b>910</b>. In one embodiment, the controller <b>910</b> shuts off the water in response to a command from an external source. In one embodiment, the controller <b>910</b> shuts off the water in response to an apparent plumbing system malfunction (e.g., a significant and continuous flow of water indicative of a break in a water line or failure of a valve, a significant leak, etc.).
0077<figref idref="DRAWINGS">FIG. 10</figref> shows a water metering system <b>1000</b> adapted to monitoring water use and/or leaks in connection with a sprinkler valve that provides water to one or more sprinkler heads. In the system <b>1000</b> a flow meter <b>1001</b> is provided in series with a sprinkler valve. In one embodiment, the flow meter <b>1001</b> is configured as an AMR meter (e.g., such as the meter shown in <figref idref="DRAWINGS">FIG. 1A</figref>, an ultrasonic flow meter, or other meter technology). In one embodiment, the flow meter <b>1001</b> is configured as a low-flow meter system such as the low-flow meter systems <b>800</b>, <b>801</b>. In one embodiment, the electronically-controlled valve <b>802</b> shown in <figref idref="DRAWINGS">FIGS. 8A and 8B</figref> is used as the sprinkler valve <b>1002</b>. In one embodiment, the low-flow/high-flow meter system <b>901</b> is used to provide water to one or more sprinkler heads (where the system <b>901</b> provides the functions of the flow meter <b>1001</b> and sprinkler valve <b>1002</b>.
0078<figref idref="DRAWINGS">FIG. 11</figref> shows a water metering system adapted to monitoring water use and/or leaks wherein the flow meter <b>1001</b> is provided to a manifold <b>1101</b>. The manifold <b>1101</b> is provided to sprinkler valves <b>1110</b>, <b>1111</b> and <b>1112</b>. A sprinkler controller <b>1102</b> provides control signals <b>1120</b>-<b>1122</b> to the sprinkler valves <b>1110</b>-<b>1112</b>, respectively. The control signals are also provided to a monitoring system <b>1103</b>. An output from the flow meter <b>1001</b> is also provided to the monitoring system <b>1103</b>. One of ordinary skill in the art will recognize that the functions of the controller <b>1102</b> and the monitoring system <b>1103</b> can be combined. The monitoring system <b>1103</b> monitors and records water flow through each of the valves <b>1110</b>-<b>1112</b> by recording water flow data from the flow meter <b>1001</b> when each of the valves <b>1110</b>-<b>1112</b> is opened.
0079The systems <b>1000</b> and <b>1100</b> allow a building owner or other party to monitor and track water use by a sprinkler or irrigation system on a zone by zone basis. The systems <b>1000</b> and <b>1100</b> can report damaged or missing sprinkler heads because water flow is generally excessive through a damaged or missing head. The systems <b>1000</b> and <b>1100</b> can also report clogged heads because water flow through a clogged head is below normal.
0080<figref idref="DRAWINGS">FIG. 12</figref> shows a water metering system combining various elements from <figref idref="DRAWINGS">FIGS. 1-11</figref> for monitoring water use and/or leaks in connection with a commercial structure (or residential structure) <b>1250</b> having one or more water usage zones and one or more sprinkler zones. Water from the water utility company is provided through a main meter <b>1201</b> to the building <b>1250</b> through one or more (optional) meters <b>1202</b> and <b>1203</b>. Water from the main meter <b>1201</b> is also provided to flow meters <b>1204</b> and <b>1205</b>. The flow meter <b>1204</b> provides water to a manifold that services a group of sprinkler valves <b>1220</b>. The flow meter <b>1205</b> provides water to a manifold that services a group of sprinkler valves <b>1221</b>. The sprinkler valves <b>1220</b> are controlled by a sprinkler controller <b>1210</b>, and the sprinkler valves <b>1221</b> are controlled by a sprinkler controller <b>1211</b>. The sprinkler control lines, and meters <b>1202</b>-<b>1205</b> are provided to a monitoring system <b>1230</b>. In one embodiment, the meter <b>1201</b> is also provided to the monitoring system <b>1201</b>. The flow meters <b>1202</b>-<b>1205</b>, and optionally <b>1201</b> are configured to provide water usage data to the monitoring system <b>1230</b>. In one embodiment, the flow meters <b>1202</b>-<b>1205</b>, and optionally <b>1201</b> are configured to provide low-flow sensing for detecting leaks.
0081The monitoring system <b>1230</b> gathers water usage data from each of the meters and records water usage through each meter. In one embodiment, the monitoring system <b>1230</b> calculates water wasted by leaks in the system according to the severity of the leak and the amount of time the leak has existed. In one embodiment, the monitoring system <b>1230</b> provides graphs of water usage by zone, by day, by time of day, by month, etc.
0082Various types of flow meters or flow sensors can be used measure the flow of water or gas or other utilities in connection with the leak detection and monitoring techniques described herein. The traditional water meter and gas meters are based on turbines or impellers that spin in response to flow. Other types of flow meters (flow sensors) can also be used, such as, for example, a differential-pressure flow meter, an orifice plate flow meter, a venturi tube flow sensor, a flow nozzle flow meter, a variable area flow meter or rotameter, a velocity flow meters, a calorimetric flow meter, a turbine flow meter, a vortex flow meter, an electromagnetic flow meter, a positive displacement flow meter, a mass flow meter, a thermal flow meter, etc., and combinations thereof.
0083It 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.
Contents5
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both waysCites: the store holds 99 of 100
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8341106B1 | Cited by | United States of America | Applicant |
| US9841122B2 | Cited by | United States of America | Applicant |
| US9568392B2 | Cited by | United States of America | Applicant |
| US9995486B2 | Cited by | United States of America | Applicant |
| US10697815B2 | Cited by | United States of America | Applicant |
| US11407653B2 | Cited by | United States of America | Applicant |
| US8583386B2 | Cited by | United States of America | Applicant |
| WO2024213737A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11421875B2 | Cited by | United States of America | Applicant |
| US11709108B2 | Cited by | United States of America | Applicant |
| US9557059B2 | Cited by | United States of America | Search report |
| US10503181B2 | Cited by | United States of America | Applicant |
| US2014203949A1 | Cited by | United States of America | Pre-grant |
| US9683674B2 | Cited by | United States of America | Applicant |
| US9657946B2 | Cited by | United States of America | Applicant |
| US10473494B2 | Cited by | United States of America | Applicant |
| US9699525B2 | Cited by | United States of America | Search report |
| US10966379B2 | Cited by | United States of America | Applicant |
| US9835265B2 | Cited by | United States of America | Applicant |
| US10564062B2 | Cited by | United States of America | Applicant |
| US10352814B2 | Cited by | United States of America | Applicant |
| US10203049B2 | Cited by | United States of America | Applicant |
| US10851993B2 | Cited by | United States of America | Applicant |
| US10989427B2 | Cited by | United States of America | Applicant |
| US10962439B2 | Cited by | United States of America | Applicant |
| US9851103B2 | Cited by | United States of America | Applicant |
| US2013153798A1 | Cited by | United States of America | Pre-grant |
| US11866916B2 | Cited by | United States of America | Applicant |
| US10024439B2 | Cited by | United States of America | Applicant |
| US10067026B2 | Cited by | United States of America | Applicant |
| US9645584B2 | Cited by | United States of America | Applicant |
| US11662242B2 | Cited by | United States of America | Applicant |
| US10242414B2 | Cited by | United States of America | Applicant |
| US10094095B2 | Cited by | United States of America | Applicant |
| US11073281B2 | Cited by | United States of America | Applicant |
| US10634538B2 | Cited by | United States of America | Applicant |
| US7920983B1 | Cited by | United States of America | Applicant |
| US10697632B2 | Cited by | United States of America | Applicant |
| US11493371B2 | Cited by | United States of America | Applicant |
| US10039240B2 | Cited by | United States of America | Third party observation |
| US10215291B2 | Cited by | United States of America | Applicant |
| US9939299B2 | Cited by | United States of America | Applicant |
| EP4446708A1 | Cited by | European Patent Office (EPO) | Search report |
| US10627254B2 | Cited by | United States of America | Applicant |
| US9846440B2 | Cited by | United States of America | Applicant |
| US10672252B2 | Cited by | United States of America | Applicant |
| US10267651B2 | Cited by | United States of America | Applicant |
| US12033226B2 | Cited by | United States of America | Applicant |
| US9053519B2 | Cited by | United States of America | Applicant |
| US11708982B2 | Cited by | United States of America | Applicant |
| US11217082B2 | Cited by | United States of America | Applicant |
| US10422531B2 | Cited by | United States of America | Applicant |
| US2011215945A1 | Cited by | United States of America | Pre-grant |
| US10561078B2 | Cited by | United States of America | Applicant |
| US2233297A | Cites | United States of America | Applicant |
| US4061442A | Cites | United States of America | Applicant |
| US4099168A | Cites | United States of America | Applicant |
| US4136823A | Cites | United States of America | Applicant |
| US4226533A | Cites | United States of America | Applicant |
| US4266220A | Cites | United States of America | Applicant |
| US4400694A | Cites | United States of America | Applicant |
| US4420746A | Cites | United States of America | Applicant |
| US4437336A | Cites | United States of America | Applicant |
| US4455553A | Cites | United States of America | Applicant |
| US4514720A | Cites | United States of America | Applicant |
| US4535450A | Cites | United States of America | Applicant |
| US4543570A | Cites | United States of America | Applicant |
| US4556873A | Cites | United States of America | Applicant |
| US4652859A | Cites | United States of America | Applicant |
| US4661804A | Cites | United States of America | Applicant |
| US4670739A | Cites | United States of America | Applicant |
| US4675661A | Cites | United States of America | Applicant |
| US4692742A | Cites | United States of America | Applicant |
| US4692750A | Cites | United States of America | Applicant |
| US4727359A | Cites | United States of America | Applicant |
| US4801865A | Cites | United States of America | Applicant |
| US4811011A | Cites | United States of America | Applicant |
| US4817131A | Cites | United States of America | Applicant |
| US4827244A | Cites | United States of America | Applicant |
| US4862514A | Cites | United States of America | Applicant |
| US4871999A | Cites | United States of America | Applicant |
| US4901316A | Cites | United States of America | Applicant |
| US4916432A | Cites | United States of America | Applicant |
| US4939504A | Cites | United States of America | Applicant |
| US4951029A | Cites | United States of America | Applicant |
| US4977527A | Cites | United States of America | Applicant |
| US4996518A | Cites | United States of America | Applicant |
| US5107446A | Cites | United States of America | Applicant |
| US5134644A | Cites | United States of America | Applicant |
| US5138562A | Cites | United States of America | Applicant |
| US5151683A | Cites | United States of America | Applicant |
| US5159315A | Cites | United States of America | Applicant |
| US5168262A | Cites | United States of America | Applicant |
| US5188143A | Cites | United States of America | Applicant |
| US5229750A | Cites | United States of America | Applicant |
| US5240022A | Cites | United States of America | Applicant |
| US5260687A | Cites | United States of America | Applicant |
| US5267180A | Cites | United States of America | Applicant |
| US5281951A | Cites | United States of America | Applicant |
| US5315291A | Cites | United States of America | Applicant |
13 members in 8 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 94862804 | United States of America | A | |
| 94862804 | United States of America | A | |
| 76176007 | United States of America | A | |
| 76176007 | United States of America | A | |
| 19364108 | United States of America | A | |
| 10948628 | – | – | – |
| 11761760 | – | – | – |
| US20040948628 | – | – | – |
| US20070761760 | – | – | – |
| US20080193641 | – | – | – |
Members13
| Document | Office | Kind | |
|---|---|---|---|
| US2006059977A1 | United States of America | A1 | |
| AU2005290014A1 | Australia | A1 | |
| CA2600976A1 | Canada | A1 | |
| WO2006036513A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US7228726B2 | United States of America | B2 | |
| EP1800103A1 | European Patent Office (EPO) | A1 | |
| CN101036042A | China | A | |
| US2007234784A1 | United States of America | A1 | |
| JP2008514917A | Japan | A | |
| US7412876B2 | United States of America | B2 | |
| RU2007114678A | Russian Federation | A | |
| US2008302172A1 | United States of America | A1 | |
| US7669461B2This record | United States of America | B2 |
68 transactions on the USPTO file
Allowed without a rejection on record.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Correspondence Address ChangeC.ADB | C.ADB | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Printer Rush- No mailingTCPB | TCPB | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Examiner's AmendmentMEX.A | MEX.A | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Application Is Now CompleteCOMP | COMP | |
| Sent to Classification ContractorPGPC | PGPC | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
19 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Surcharge for late paymentSULP | SULP | |
| Fee payment procedurePAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee reminder mailedREMI | REMI | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 07669461
- Publication, DOCDB
- 7669461
- Publication, EPODOC
- US7669461
- Application
- 12193641
- Application, DOCDB
- 19364108
- Application, EPODOC
- US20080193641
Titles
- English
- System and method for utility metering and leak detection
Patent term adjustment
- A delay
- +5 daysthe office missed an examination deadline
- Net adjustment
- 5 days
Classification
- CPC, 3
- G01M3/2807
- G01M3/2815
- G08B21/20
- IPC, 4
- G01M3 02
- G01F1 00
- G01F15 06
- G01F15 061
- USPC, 1
- 073040000