US 9,874,466 B2Grant
Methods and apparatus for ultrasonic fluid flow measurement and fluid flow data analysis
Issue Date:2018-01-23
•20 Claims
•13 Drawing Sheets
Abstract
A fluid flow meter estimates the velocity of water or another fluid flowing through pipe by comparing measurements of the water velocity to one or more pre-determined templates. The fluid flow meter may collect measurement signals from one or more flow sensors, estimate the fluid velocity or flow rate by comparing the measurement signals to the template, and either store the comparison results in local memory, transmit the results to a remote memory or server, or both. In some embodiments, the fluid flow meter transmits the results to a server via a wireless interface. The transducers and processing system can be powered by a battery, a power line, or, for manifolds installed outdoors, a solar cell. Example transducers and processing systems may also have a passive wake-up feature for power reduction; that is, they may only draw power when water or another fluid flows through the pipe.
Metadata
Assignee
- Reliance Worldwide Corporation
Inventors
- Jeffrey L. Leaders
- Jeffery Dugger
Application Information
Application Number:US 14/715,226
Filing Date:2015-05-18
Priority Date:2011-03-18
Art Unit:2855
Classifications
IPC:
G01F1/66G01F15/06G06F19/00
Field of Search:
G01F 1/1661G01F 1/667G01F 1/663G01F 1/66G01F 1/661G01F 1/662
Patent Drawings (13 sheets)
Description
Related Application
[0001] This application is a U.S. Divisional Application under 35 U.S.C. § 111 of U.S. National Stage Application Ser. No. 14/005,169, entitled “Methods and Apparatus for Fluid Flow Measurement” filed on Nov. 22, 2013, which claims priority under 35 U.S.C. § 371 of International Application No. PCT/US2012/029481, filed on Mar. 16, 2012, which claims the benefit under 35 U.S.C. § 119 of U.S. Provisional Application No. 61/454,344, entitled “Water Manifold with Integrated Flow Sensor” and filed Mar. 18, 2011. The entire contents of the foregoing applications are hereby-incorporated herein by reference.
Background
[0002] A rapidly rising global population is putting increasing pressure on natural resources. Demand for food, water, and energy is expected to rise by 30-50% over the next 20 years. Limited availability of water resources has implications for both the new development of real estate as well for the continued use of already-developed property.
[0003] New real estate development opportunities may be increasingly limited by water availability. Existing or anticipated water shortages may cause regulators to restrict or prohibit housing development. For example, the State of California currently requires water agencies to withhold approval for developments until a determination is made that sufficient water resources exist to serve a proposed development for a period of 20 years.
Summary
[0004] Embodiments of the present technology include a fluid flow meter and a method of measuring fluid velocity. In one example, the fluid flow meter includes a sensor, a memory, and a processor. The sensor is configured to generate a measurement signal by detecting an ultrasonic signal representative of a velocity of a fluid flowing through a lumen. The sensor is also configured to provide a measurement signal representative of the velocity. The memory configured to store a template associated with a possible velocity of the fluid. The processor, which is communicatively coupled to the sensor and to the memory, is configured to compare the measurement signal to the template and to determine an estimated velocity of the fluid based on the comparison. The fluid flow meter may also include a fixation device, such as a lock, clamshell hinge, adhesive, or other suitable device, to secure the sensor to a vessel that defines the lumen. It may also include a communications interface, communicatively coupled to the processor, to transmit a data, such as representations of the estimated velocity or the measurement signal, to a server.
[0005] In one instance, the sensor includes a first transducer to transmit the ultrasonic signal through the fluid flowing through the lumen and a second transducer to receive a reflected, scattered, or transmitted copy of the ultrasonic signal. The sensor also includes a front end, which can be coupled to the first transducer, second transducer, or both, that is configured to produce the measurement signal from the reflected, scattered, or transmitted copy of the ultrasonic signal. The ultrasonic signal can be a first ultrasonic signal, in which case the second transducer may be further configured to transmit a second ultrasonic signal through the fluid flowing through the lumen, and the first transducer may be configured to receive a reflected, scattered, or transmitted copy of the second ultrasonic signal. In such a case, the front end is further configured to produce the measurement signal based on a difference of the reflected, scattered, or transmitted copy of the first ultrasonic signal and the reflected, scattered, or transmitted copy of the second ultrasonic signal.
[0006] The memory in an exemplary fluid flow meter may be configured to store a plurality of templates, where each template in the plurality of templates corresponding to a different possible velocity of the fluid flowing through the lumen. In such a case, the processor can be further configured to compare the measurement signal to each template in the plurality of templates. In some examples, the template is produced at a first sampling frequency and stored in the memory at a second sampling frequency lower than the first sampling frequency. The processor may also be configured to interpolate the measurement signal, the template, or both before or while performing the comparison. In addition, the processor can add a first random waveform to the measurement signal and a second random waveform to the template before performing the comparison.
[0007] In certain examples, the fluid flow meter also includes a manifold that defines the lumen through which the fluid flows. Such a manifold may include an inlet to channel the fluid into the lumen and one or more outlets to channel the fluid out of the lumen. The sensor may be configured to measure the velocity of the fluid flowing into or out of the lumen.
[0008] Another embodiment of the present disclosure includes a method of installing a fluid flow meter, e.g., examples of the fluid flow meter described above. Such an installation method may include securing the fluid flow meter to an exterior of a structure that defines the lumen. It may also include calibrating the sensor by setting the velocity or flow rate of the fluid to a known value (e.g., no flow, 1 gallon per minute, etc.), generating an estimated velocity with fluid flow meter, and calibrating the fluid flow meter based on the known value and the estimated velocity. Calibration may also include generating an estimated diameter of the lumen based on the known value and the estimated velocity and possibly verifying the diameter of the lumen based the estimated diameter and a description of the lumen or the structure.
[0009] Embodiments of the inventive subject matter include water manifolds with integrated flow sensors that address problems associated with insufficient water resources. Example water manifolds include an inlet port to channel water into a lumen and several (e.g., 2-100) outlet ports that channel water out of the lumen. At least one of the outlet ports includes an integrated flow sensor that measures the flow rate of water flowing from the lumen. In some cases, the flow sensor includes a transmit transducer and a second transducer to transmit and detect, respectively, an ultrasonic signal that propagates through the water flowing from the lumen. Alternative flow rate sensors may include magnetic field sources or impellers disposed with output lumens defined by the outlet ports.
[0010] Example water manifolds may also include a wireless interface to transmit data collected by the flow sensors, a processor to monitor data collected by the flow sensors, and a memory to store data collected by the flow sensors. The processor can be configured to interface with a server via the wireless interface, and the server may provide a dashboard (via a smart phone or other networked device) that indicates water usage statistics based on flow rate data collected by the flow sensors. Flow rate data and water usage statistics can be used to reduce water consumption through analysis of usage patterns, elimination of waste, and incentives for lowered water use.
[0011] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the following drawings and the detailed description.
Brief Description of the Drawings
[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosed technology and together with the description serve to explain principles of the disclosed technology.
[0013] FIGS. 1A and 1B show an ultrasonic fluid flow meter before (FIG. 1A ) and after (FIG. 1B ) installation around a pipe.
[0014] FIG. 1C shows the positions of the ultrasonic transducers in the ultrasonic fluid flow meter of FIGS. 1A and 1B when the meter is installed around a pipe.
[0015] FIG. 1D shows an ultrasonic flow meter installed around a pipe.
[0016] FIG. 2 is a block diagram that illustrates electronic components in the ultrasonic fluid flow meter of FIGS. 1A and 1B .
[0017] FIG. 3 is a flow diagram that illustrates operation of the fluid flow meter of FIGS. 1A and 1B .
[0018] FIG. 4A is a plot of a transmitted ultrasonic pulse (top) and a received ultrasonic pulse (bottom) of the ultrasonic fluid flow meter of FIGS. 1A and 1B .
[0019] FIG. 4B is a plot that shows the delay between two received ultrasonic pulses associated with different fluid flow velocities.
[0020] FIG. 5A is a line plot of apodized templates associated with different fluid flow velocities (pulse delays) generated at a first (higher) sampling frequency.
[0021] FIG. 5B is an image plot of the apodized templates of FIG. 5A .
[0022] FIG. 6A is a line plot of an apodized template at a first (higher) sampling frequency (smooth curve) and at a second (lower) sampling frequency (jagged curve).
[0023] FIG. 6B is an image plot of the apodized templates of FIGS. 5A and 5B down-sampled to the second (lower) sampling frequency of FIG. 6A .
[0024] FIG. 6C is an image plot that illustrates a correlation between a received ultrasonic pulse and the down-sampled templates of FIG. 6B .
[0025] FIG. 7 is a flow diagram that illustrates installation of a fluid flow meter.
[0026] FIG. 8A illustrates an architecture of a fluid metering system.
[0027] FIG. 8B illustrates the server and the fluid metering system shown in FIG. 8A .
[0028] FIGS. 8C-8H show screenshots of a dashboard provided by the fluid metering system shown in FIGS. 8A and 8B .
[0029] FIG. 9 is a diagram of a multi-port water manifold with flow sensors that can be integrated into any one of the water manifold's inlet and outlet ports.
Detailed Description
[0030] Following below are more detailed descriptions of various concepts related to, and embodiments of, inventive systems, methods and apparatus for providing fluid flow metering. Features of exemplary fluid flow meters may include, but are not limited to: real-time usage information; accurate metering at low flow rates; accurate calculation of fluid loss; detection of abnormal fluid usage; detection of continuous low velocities; remote meter reading; no moving parts; battery or line power; and no-flow and reverse flow detection. The various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways, as the disclosed concepts are not limited to any particular manner of implementation. Examples of specific implementations and applications are provided primarily for illustrative purposes.
[0031] An exemplary fluid flow meter can engage tenants, reduce cost, and provide automated reporting for property owners and managers. It can engage a tenant by informing the tenant of his or her usage in real-time, and by providing monthly bills. A fluid flow meter may also provide usage information and other data to property owners and managers, which enables the property owners and managers to identify and reduce leaks, waste, and unauthorized usage. This allows management to receive utility payments sooner and reduces management's risk and costs associated with wasteful consumption and leaks. It also helps to ensure that tenants pay only for what they use. In addition, a fluid flow meter may enable automated reporting that compares building performance to similar buildings in a property manager's portfolio or to a competitor's portfolio. Automated reporting may also enable evaluation of a tenant or building owner's environmental performance, including carbon and water use footprinting.
[0032] An exemplary fluid flow meters can be installed on a pipe in multi-tenant rental or institutional housing to monitor water consumption in one or more individual apartments. A server or other computing device may collect information from the fluid flow meter about each tenant's water usage, making it possible to identify tenants whose water usage is abnormally high or low. This information may also make it possible to supply individuals with real-time consumption information as well as coaching and social pressures (e.g., public rankings) that promote water conservation. For example, a server communicatively coupled to a fluid flow meter may proactively notify residents of their own usage rates, their neighbors' usage rates, target usage rates, etc.
[0033] An exemplary fluid flow meter can also be used to monitor occupied and vacant units. This feature may be used during new construction of the community and once property leasing commences. A fluid flow meter can identify events such as undetected leaks and pipe bursts due to freezing, saving owners and residents money by limiting damage and repair costs. The meter can also sense temperatures in the units and can warn management and residents of conditions that may cause damage such as pipe freezing. The fluid flow meter (possibly together with a server) may alert management of these conditions via email, text message, phone, or any other suitable communications method.
[0034] Fluid Flow Meters
[0035] FIGS. 1A-1D show a non-invasive fluid flow meter 100 that clamps around a pipe 10, which defines a lumen containing flowing fluid (e.g., water, gas, oil, or sewage). The fluid flow meter 100 includes a cylindrical housing 104 made of plastic or any other suitable material with a hinge 102 that extends along the long axis of the housing 104. The hinge 102 allows the housing 104 to open (FIG. 1A ) and close (FIG. 1B-1D ) like a clamshell. One or more tabs 106 extending from one edge of the housing 104 may engage one or more locking interfaces 108 (e.g., formed of catches, hooks, ridges, or slots) on another side or edge of the housing 104 to lock the housing 104 in a closed position.
[0036] Together, the hinge 102, tab(s) 106, and locking interfaces 108 enable tool-less, clamp-on installation around existing pipes or installed on newly laid pipes. This simplified clamp-on installation eliminates pipe cutting and pipe breaking, reduces labor costs, and reduces the risk of leaks and contamination associated with pipe cutting and pipe braking. In contrast, installing conventional in-line water meters requires shutting off the water, cutting the pipe, and inserting the meter in-line. For multi-family buildings, this may mean draining the entire building to install the meters, leading to long, inconvenient downtimes. The bigger the building, the greater the time the building may be without water.
[0037] In some cases, the locking interface 108 may include multiple catches or slots to hold the housing 104 closed in one of many positions to accommodate pipes 10 of different outer diameters or shapes. The hinge 102 may also be articulated to accommodate pipes 10 of different diameters (e.g., diameters of about 0.5 inches to about 1.0 inches) or shapes. The meter 100 can work with any suitable type of pipe, including copper pipes, PVC pipe, and even PEX tubing.
[0038] The fluid flow meter 100 also includes a transmit (Tx) ultrasonic transducer 110 and a receive (Rx) ultrasonic transducer 110b (collectively, transducers 110), each of which sits within a respective transducer housing 112a, 112b (collectively, transducer housings 112). Each transducer 110 may include a piezoelectric device (e.g., a thin-film or disk device) as known in the art. In some cases, each transducer 110 may be configured to only transmit or receive ultrasonic signals; in other cases, each transducer 110 may be configured to transmit and receive ultrasonic signals, e.g., in an alternating fashion.
[0039] Once the fluid flow meter 100 is installed properly (e.g., as shown in FIGS. 1B-1D ) and 1C), each transducer 110 is oriented at an angle (e.g., 15°, 30°, 45°, or 60°) with respect to the pipe's longitudinal axis. A compressible or conformal cushion 114 disposed on or along the inside of the housing 104 may cushion and secure the transducers 110 with respect to the pipe 10. The cushion 114 may also apply positive pressure to the transducers 110 and dampen vibrations of the transducers 110. In some cases, the cylindrical housing 104, the transducer housings 112, or both may include adjustment mechanisms, such as set screws or levers, to adjust the angle(s) of the transducers 110 with respect to the pipe. For instance, a plumber, installation technician, or even a consumer may adjust the set screws to maximize the signal-to-noise ratio of the signal detected with the transducers. The meter 100 can be powered by a battery, a power line, or, if installed outdoors, a solar cell. Example meters 100 may also have a passive wake-up feature for power reduction; that is, they may only draw power when water flows through the meter.
[0040] In operation, the transmit transducer 110a transmits a signal, such as a modulated high-frequency burst, or pulse 111, into the pipe 10, as shown in FIG. 4A . Together, the transducers 110 may transmit pulses 111 upstream, downstream, or upstream and downstream in alternating fashion. The pulse 111 propagates through the fluid in the pipe 10, then reflects or scatters off bubbles, particles, or debris within the pipe 10 or the inner wall of the pipe 10 itself. The reflected or scattered pulse 113 (also shown in FIG. 4A ) propagates along a V-shaped (or W-shaped) path back to the receive transducer 110b, which detects a version 113 of the pulse that is delayed, attenuated, and possibly distorted compared to the transmitted pulse 111. Longer paths (e.g., with more reflections) increase the time delay, but may also lead to increased attenuation or distortion.
[0041] The length of the time delay varies with the velocity of the fluid relative to the pulse. When the fluid is not moving (a “no-flow” condition), the time delay equals the product of the pulse's speed and the pulse's propagation distance. When the fluid moves, the time delay increases or decreases by an amount proportional to the fluid's velocity with respect to the pulse. (The received pulse also shifts in frequency with respect to the transmitted pulse by an amount proportional to the relative velocity as understood by those of skill in the art.) Transmitting the pulse 111 upstream results in an increasing delay relative to no-flow for increasing flow rates; transmitting the pulse 111 downstream results in an increasing advance relative to no-flow for increasing flow rates.
[0042] The fluid flow meter 100 may also include a processing system, operably coupled to the transducers 110, that estimates the fluid's velocity and a display 120, that shows the flow rate, meter status, and other parameters. As understood by those of skill in the art, the processing system may include digital components, analog components, or a combination of analog components. It may include purpose-built components (e.g., an application-specific integrated circuit) or programmable/reconfigurable components (e.g., a field-programmable gate array or a field-programmable analog array).
[0043] In some examples, the processing system estimates the fluid's velocity by either measuring the time that reflected pulse crosses a pre-determined threshold or by comparing a representation of the reflected pulse to one or more pre-determined templates, each of which represents a different fluid velocity. (Alternatively, the transmit transducer 110a may emit a continuous-wave (cw) or chirped signal, and the receive transducer 110b may detect a delayed version of the cw or chirped signal. In such an example, the processing system can determine the flow rate by measuring the frequency shift or the difference in phase (phase delay) between the transmitted and received cw or chirped signals.) The relationship between flow rate and time-delay-of-arrival (or frequency shift) is linear at the flow rates of interest (e.g., within a range of about 0 gallons per minute and about 1 gallon per minute, about ¼ gallon per minute, about ½ gallon per minute, about ¾ gallon per minute, etc
[0044] FIG. 2 illustrates a processing system 200 suitable for use in or with the fluid flow meter 100 of FIGS. 1A-1C . The processor 202 collects data, including flow rate data, from the transducers 110 and either stores the data in local memory 220, transmits the data to a remote memory or server, or both. In some embodiments, the processor 202 transmits the data to a server (not shown) via a wireless communications interface 216 (e.g., a Zigbee, Bluetooth, or Wi-Fi interface).
[0045] The processing system 200 includes a processor 202 (e.g., an Atmel Atmega128 microcontroller) that is coupled to a user interface 212 (e.g., a touchpad, one or more buttons, or one or more switches), a universal serial bus (USB) 214, a wireless communications interface 216 (e.g., a Zigbee interface), and a memory 220. The user interface 212 may be coupled to or include the display 120 shown in FIG. 1D . The processor 202 generates ultrasonic transmit pulses 111 and processes digital representations of the received pulses 113. The processor 202 is coupled to the transducers 110a and 110b via a pair of amplifiers 204a and 204b (collectively, amplifiers 204), respectively, that amplify the transmit pulses 111. Each transducer 110a, 110b is coupled to another amplifier 206 via a respective switch 210a, 210b (collectively, switches 210); the switches 210 connect to an analog-to-digital converter (ADC) 208. The processing system 200 may also include one or more filters (not shown) coupled to the amplifier's input or the ADC's input. Together, the amplifier 206, the ADC 208, and the filters form a front end that amplifies, filters, and digitizes the transducer output (measurement signal) and provides the resulting digital signal to the processor 202, which may analyze the digital signal, and display the estimated flow rate or flow velocity on the display 120 (FIG. 1D ).
[0046] In general, the fluid flow meter 100 may have a variety of normal operating modes, including but not limited to sense, wake, idle, sleep, and transmit, and an error mode. It may also have a bootloader mode to install field-updateable firmware via either USB or wireless link and one or more configuration modes to set configuration properties after meter installation. TABLE 1 describes several exemplary operating modes:
[0047]
| TABLE 1 | |
|---|---|
| Fluid Flow Meter Operating Modes | |
| Operating | |
| Mode | Operating Mode Description |
| Sense | The wireless meter is transmitting and receiving |
| ultrasound signals to determine water flow in a pipe and | |
| storing the data locally | |
| Transmit | The wireless meter is transmitting data to the wireless |
| hub | |
| Wake | The wireless meter is fully active and awaiting |
| instructions | |
| Idle | The wireless meter is maintaining a wireless |
| communication link, but all peripherals and main MCU | |
| core are shutdown | |
| Sleep | The wireless meter is fully shut down and waiting for a |
| timer interrupt or external interrupt | |
| Error | The wireless meter is continually transmitting an error |
| code and waiting for corrective response from the system | |
| Bootloader | The wireless meter is waiting for wireless or USB |
| instructions to reprogram program memory space with | |
| updated firmware | |
| Configuration | The wireless meter is waiting to be configured following |
| installation | |
[0048] FIG. 3 is a flow diagram 300 that illustrates operation of the flow meter 100 (and processing system 200). In step 302, an interrupt signal, such as a timer overflow signal, wakes the processing system 200 from a low-power mode, or sleep state. The processing system 200 responds to the interrupt signal by waking the microcontroller unit (MCU; processor 202) in step 304. Once awake, the processor 202 sets a counter to zero in step 306 and enables the ADC 208 and memory 220 (e.g., flash memory) in step 308.
[0049] Once the processing system 200 is fully enabled, the flow meter 100 is ready to measure the velocity of the fluid flowing in the pipe 10. Before transmitting any pulses, the processor 202 either queries the transducer channel, selects a transducer channel (e.g., channel A for transducer 110a) by opening and closing the switches 210 as appropriate, or both in step 310. In step 312, the processor 202 generates the transmit pulse 111, which is amplified by amplifiers 204, and drives the transducers 110, at least one of which emits the ultrasonic pulse 111 into the pipe 10. After a brief delay in step 314, the selected transducer 110a receives the reflected or scattered pulse 113 in step 316. The amplifier 206 amplifies the output signal from the selected transducer 110a, and the ADC 208 digitizes the output of the amplifier 206 and provides the digitized output to the processor 202.
[0050] In step 318, the processor 202 calculates the time delay, or time-of-flight, associated with the pulse's propagation through the pipe, e.g., using a Goertzel infinite impulse response (IIR) algorithm or any other suitable technique. The processor 202 stores a representation of the time-of-flight in a data random access memory (RAM), such as one provided by the memory 220, in step 320. The processor 202 may also transmit information relating to the time-of-flight, including an estimate of the fluid velocity, to a user via the user interface 212 or to a server or other device via the USB 214 or the wireless communications interface 216.
[0051] In step 322, the processor 202 queries the transducer channel setting; depending on the query result, the processor 202 either switches from one transducer channel to the other in step 324, then repeats steps 312 through 322, or queries a counter in step 326. By switching between transducer channels, the fluid flow meter 100 can make upstream and downstream time-of-flight measurements. The counter, which may be internal or external to the processor 202, determines how many transmit/receive cycles that the fluid flow meter 100 performs in response to the interrupt signal (step 302). In the example shown in FIG. 3 , the fluid flow meter 100 is set to perform 100 fluid flow velocity measurements (100 transmit/receive cycles). Other settings may be possible as well (e.g., 1, 5, 10, 25, 50, 250, etc.). Those of skill in the art will readily appreciate that it generally takes more time to make more measurements, but that making more measurements generally improves the accuracy of the resulting velocity estimate.
[0052] If the processor 202 determines that the measurement count equals or exceeds the count in the counter in step 326, it proceeds to compare the upstream and downstream time-of-flight measurements obtained with the transducers 110. For instance, the processor 202 may subtract the upstream measurements from the downstream measurements (or vice versa) to cancel the fixed (no-flow) time delay associated with the pipe 10. In step 330, the processor 202 calculates an average flow velocity (and flow rate) responsive to the comparison of the upstream and downstream time-of-flight measurements. The processor 202 stores representations of the average flow rate, average flow velocity, and/or time-of-flight measurements in memory 220 in step 332. The processor 202 may then return to sleep mode in step 334.
[0053] Fluid Flow Signal Processing Using Templates
[0054] The processor 202 may use any suitable technique to estimate the flow rate or velocity of the fluid in the lumen defined by the pipe 10. In one example, the processor 202 estimates the fluid velocity based on the time it takes an ultrasonic signal, or pulse 111, to propagate from one transducer 110a to the other transducer 110b; changes in the flow rate cause the time delay to change by a corresponding amount. As noted above, the transducers 110 can transmit pulses 111 upstream, downstream, or alternate between both upstream and downstream transmission. Using an upstream/downstream differential approach reduces inaccuracy due to variations in the no-flow time delay (the reference time delay) with temperature, fluid pressure, fluid density, or other conditions. Differences in time-of-arrival relative to zero-flow or between upstream and downstream measurements correspond to flow rate.
[0055] FIG. 4A is a plot of a transmitted pulse 110 and a received pulse 113 (amplitude versus time). The transducers 110 may emit pulses at a carrier frequency of about 100 kHz to about 10 MHz (e.g., about 1 MHz). The pulse duration may be about 5 μs to about 20 μs (e.g., about 10 μs). In some cases, the transducers 110 may emit and receive individual pulses 111, 113 or groups of pulses 111, 113 at a pulse repetition frequency of about 5 Hz to about 50 Hz (e.g., about 10 Hz to about 20 Hz) or at intervals of anywhere from 100 μs to minutes or hours. As understood by those of skill in the art, the duty cycle should be chosen to prevent a received pulse from overlapping or interfering with a subsequently transmitted pulse at the receive transducer 110b.
[0056] FIG. 4B is a plot that illustrates how changing fluid velocity affects a pulse's time-of-flight. It shows two received pulses separated by a delay of about 0.04 μs (inset), which corresponds to a difference in flow rate of about 3.64 gallons per minutes. Increasing the difference in flow rate causes the relative delay to increase, and decreasing the difference in flow rate causes the relative delay to decrease. Changes in the pipe's temperature, diameter, and inner surface may also affect the time delay (and the flow rate), as may changes in fluid density and temperature. For instance, under other conditions, a difference in flow rate of 1 gallon per minute may yield a difference in time delay of about 4 ns to about 5.
[0057] As described above, the processing system 200 amplifies and digitizes the received pulse 111 to produce a measurement signal representative of the pulse's time-of-flight (and, implicitly, the fluid's velocity). In some embodiments, the processor 202 compares this measurement signal to one or more predetermined templates that represent different times-of-flight. For instance, the processor 202 may cross-correlate the measurement signal with each of the one or more templates, e.g., by Fourier transforming the measurement signal, multiplying it with the Fourier transform of each template, and inverse Fourier transforming the resulting product. The resulting cross-correlation may include a peak indicative of a match between the estimated flow velocity (e.g., as represented by the time delay) associated with the measurement signal and the estimated flow velocity associated with the template. The processor 202 may estimate the flow velocity by comparing the measurement signal to only one template (e.g., a template that represents a no-flow condition) and determining the mismatch (e.g., shift in cross-correlation peak) or by comparing the measurement signal to several templates and picking the best match (e.g., the largest cross-correlation peak). In some cases, the processor 202 may interpolate between closely matching templates to improve the measurement precision.
[0058] FIGS. 5A and 5B are a line plot and an image plot, respectively, of templates representing different time delays (and hence different estimated flow velocities). Each template is an apodized pulse that has been shifted with respect to the its neighboring templates by a predetermined amount, e.g., about 0.1 μs. The templates are normalized such that only wave-shape matters; they may also be filtered to match the distortion in the received pulse 113 caused by the pipe and fluid. The processing system 202 may store any suitable number of templates, e.g., 1, 10, 100, or 1000 templates. The templates may be evenly distributed across a predetermined time interval, distributed more densely around certain time delays (e.g., time delays that represent common flow velocities), distributed randomly throughout the predetermined time interval, or distributed in any other suitable fashion. The templates may be regenerated or rearranged as desired.
[0059] In some cases, the templates may be created at a sampling frequency (e.g., about 1 Gsps) that is higher than the processing system's sampling frequency (e.g., about 100 Msps). In these cases, the templates are down-sampled to the processing system's sampling frequency, as shown in FIGS. 6A and 6B , to reduce the amount of space that they take up in the memory (e.g., memory 220) and to increase processing speed as understood by those of skill in the art. Comparing the measurement signal to the down-sampled templates shown in FIG. 6B yields the cross-correlation peaks shown in FIG. 6C , where the darker regions indicate better matches. The processor 202 determines the row number (index) corresponding to the best match (high peak), matches the row number to the corresponding template (e.g., using a look-up table stored in memory 220), and estimates the fluid velocity based on the corresponding template.
[0060] In some examples, the processor 202 finds the template that best matches the measurement signal by taking a single inner product of the measurement signal, represented as a measurement vector, with the templates, represented as a matrix (e.g., as plotted in FIGS. 5B and 6B ). The resulting inner product is a match vector whose length (number of elements) equals the number of templates. If the measurement vector and the templates are normalized, the elements of the match vector take real values between −1 and +1. The element with the value closest to +1 corresponds to the template that best matches the measurement vector; in turn, matching template's velocity best matches the fluid velocity.
[0061] In other examples, the processor 202 computes a “sliding” inner product of the measurement vector with the rows of matrix. Put differently, the processor 202 computes the cross-correlation of the measurement vector with each template in a process similar to matched filtering. To compute the cross correlations, the processor 202 creates multiple, overlapping windows representing the incoming signal, e.g., by dropping one or more the oldest samples of a given window, shifting the remaining samples in the window, and adding new samples at the end of the window. This process yields a sequence of vectors, where the row corresponding to the maximum over the vectors in the sequence corresponds to the best-matching template (and corresponding flow rate). Those skilled in the art will readily appreciate other methods of processing the measurement signal to estimate the fluid velocity, including, but not limited to both analog and digital signal processing techniques.
[0062] Interpolation and Dithering to Increase Precision
[0063] The processor 202 may also interpolate the measurement signal, one or more of the templates, or both the measurement signal and the templates to increase the precision of the fluid velocity estimate. For instance, if the measurement signal matches two templates (nearly) equally well using the techniques described above, the processor 202 may interpolate between the templates to determine a more precise velocity estimate. The processor 202 may also up-sample the measurement signal using, e.g., using sinc or cubic-spline interpolation to increase the processing system's effective sampling frequency. The processor 202 may then correlate or otherwise compare the up-sampled measurement to one or more templates sampled at the same high frequency.
[0064] The processor 202 may also “dither” the amplitudes of the measurement signals, the templates, or both to improve the precision of the velocity estimate. To dither these signals, the processor 202 adds a random waveform from a distribution of a given variance, determined by the separation between adjacent time bins, to the measurement signal. For instance, the processor 202 may draw the random waveform from a white Gaussian noise process at predetermined variance. It also adds an uncorrelated random waveform drawn from distributions of the same variance to each of the templates. (If desired, the random waveforms may be added to the templates before the templates are loaded into the fluid meter's memory 220.)
[0065] To see how dithering improve measurement precision, consider a fluid flow velocity that falls partway between the fluid flow velocities associated with a pair of adjacent templates. By matching the measurement signal to the templates, the processor 202 effectively “quantizes” the measurement signal's time-of-flight, just as an ADC quantizes the amplitude of an analog signal. This quantization process imposes quantization error, which is the difference between the measurement signal's actual time-of-flight and its estimated time-of-flight (the time-of-flight associated with the matching template). Adding a small amount of noise to the measurement signal causes the quantization error to vary. If the noise distribution is symmetrical, then adding noise is just as likely to increase the quantization error as it is to decrease the quantization error. For a measurement signal whose time-of-flight is partway between the times-of-flight of adjacent templates, the noise will, on average, make the measurement signal more likely to match the closer of the two templates, improving the measurement precision.
[0066] Fluid Flow Meter Installation
[0067] FIG. 7 is a flow diagram that illustrates an installation process 700 for the fluid flow meter 100 shown in FIGS. 1A-1C . The process 700 starts in step 702, when a plumber or installation technician identifies or selects the pipe to be monitored with the fluid flow meter 100. The technician removes the meter 100 from its packaging in step 704 and activates the meter 100 in step 706, e.g., by connecting it to a power supply. Once the meter 100 is active, the technician determines the strength of the wireless signal received by the meter's wireless communications interface 216 (step 708), possibly by observing a light-emitting diode (LED) or other indicator on the meter's user interface 212. If the technician determines in step 710 that the signal is too weak to support reliable wireless communications, he or she chooses an installation area with better reception for the wireless communications interface 216 in step 712, then checks the signal strength again in step 710. The technician may repeat steps 710 and 712 as necessary or desired.
[0068] If the signal is strong enough, the plumber or technician installs the fluid flow meter 100 on the pipe 10 in step 714, e.g., by clamping the fluid flow meter 100 around the pipe 10 as shown in FIGS. 1A and 1B . The technician then connects the fluid flow meter 100 to a computing device, such as a computer, tablet, or smartphone, via the fluid flow meter's USB 214 in step 716. In step 718, the technician configures the fluid flow meter 100 using the computing device, possibly by setting a customer identification; a building, apartment, appliance, or other identification; and a network connection (hub) identification for wireless network.
[0069] In step 720, the technician connects the fluid flow meter 100 to the wireless network, e.g., by entering appropriate identification and authentication information via the computing device. The technician tests the wireless connection between the fluid flow meter 100 using the computing device in step 722 and evaluates the test results in step 724. If the test results indicate an unacceptable connection between the fluid flow meter 100 and the network, the technician may uninstall the fluid flow meter 100 and choose another installation area. If the test results are good, the technician tests the transducers 110 using a calibration program on the computing device. This test may yield information, such as received pulse strength and pulse delay, that is evaluated in step 728 to determine the transducers' alignment relative to the pipe 10. If desired, the technician can align the transducers relative to the pipe 10, either by re-installing the fluid flow meter 100 (step 714), adjusting a transducer alignment mechanism (e.g., a set screw), or both. The installation process ends in step 730 in response to the technician's determination that the fluid flow meter 100 is installed properly.
[0070] In some examples, the transducer test in step 726 may include measurements of the time delay associated with a no-flow state. The processing system 200 may use this residual time delay measurement as a reference point when estimating the fluid velocity. It may also use this measurement to estimate the pipe size; for a pulse propagating in a V-shaped path, the pipe diameter is approximately D=vτ/(2 tan θ), where v is the pulse velocity, r is the time delay, and θ is the angle between the pipe's longitudinal axis and the pulse's propagation path. In some cases, the calibration program or the processing system 200 may compare the estimated pipe diameter against a pipe diameter specified in building plans or a job order. If the estimated pipe diameter does not match the expected pipe diameter, the computing device or the fluid flow meter 100 may issue a warning or query, such as “Please check the pipe. The measured pipe diameter is 1.0 inches, but the expected pipe diameter is 0.75 inches. This may not be the correct installation location.” A discrepancy between the estimated and expected pipe diameters could also indicate build-up or debris inside the pipe 10. (In some cases, the fluid flow meter 100 may be configured to monitor the pipe 10 for gradual or sudden changes in the pipe's inner diameter and to report these changes via its wireless communications interface 216.)
[0071] The fluid flow meter 100 may be configured to calibrate itself using readings from the main water meter, branch water meters (including meters within the same building), and/or data from the water usage database. Self-calibration creates a network that is capable of identifying leaks with great accuracy with respect to their location within the network while also being capable of identifying loss due to theft or tampering with the same accuracy.
[0072] Fluid Metering System Architectures and Operation
[0073] Once installed properly, one or more fluid flow meters 100 in a customer's building 82 may be connected to a network a server 800 in an off-site location 80 to form an intelligent fluid flow sensing network 801 as shown in FIG. 8A . As described above, each fluid flow meter 100 can be connected to a wireless hub 806 via a respective wireless link 810 during installation. The wireless hub 806 connects to an internet protocol (IP) network 804, which in turn connects to the application server 800 via the Internet 84. The application server 800 may connect to a database 802; it may also connect to other devices, such as customer computers or smartphones, either directly or via the Internet 84 or any other suitable communications network. Those of skill in the art will readily appreciate that the intelligent fluid flow sensing network may have any other suitable network architectures and that the network components, such as the server 800, database 802, and wireless hub 806 may be located in any suitable location.
[0074] The server 800 may communicate periodically or on-demand with each fluid flow meter 100 in the intelligent fluid sensing network. For instance, the server 800 may transmit a status query (e.g., operating status, leak detection status, etc.) or firmware update to each fluid flow meter 100 on a regular or semi-regular basis. The fluid flow meters 100 may transmit responses or acknowledgements to the server's queries. They may also transmit fluid usage data, including, but not limited to estimated flow velocities, estimated flow rates, the number of flow events (e.g., how often water flowed through the pipe 10 in a given period), the duration of each flow event (e.g., how long the water flowed through the pipe 10), recent user commands, etc.
[0075] Upon receiving the data from the processor, the server 800 stores the data in a water usage database 802. Engines (possibly embodied as computer-readable instructions on a nonvolatile storage medium) compute water usage statistics and present these water usage statistics to homeowners, renters, building owners, property managers, utilities managers, and other users via management dashboards. These dashboards can be displayed via web browsers or special-purpose applications on computer monitors, smart phones (e.g., iPhones, Blackberries, and Droids), laptop computers (including iPads and other tablet computers), or any other suitable display. The meters may be combined with smart manifold sensors (described below) to form a distributed sensor network that can be used to meter individual units in an apartment complex, individual businesses in a shopping mall, or individual homes and businesses in a utility service area. Data collected from such a distributed sensor network provides information on aggregate water usage, individual water usage, and statistics and patterns related to water usage in a given building or water usage zone.
[0076] FIG. 8B is another view of the intelligent fluid (water) flow sensing network 801 shown in FIG. 8A . As described above, the system 801 includes one or more fluid flow meters 100 attached to pipes 10 (not shown). The fluid flow meters 100 communicate with the server 800 via a router or hub 806, which communicates with the server/cloud 800 via a coordinator or gateway 820. The server/cloud 800 and the database 802 feed information, including estimated flow rates and flow velocities, to an analytics engine 822, which is coupled to a display 826. The analytics engine 822 computes water usage, water usage trends, peer rankings, and even a “conservation score” that corresponds to a user's water usage and can be used for water usage rankings. The analytics engine 822 may also be set to detect leaks, freezes, malfunctions, and fraud based on water usage (e.g., a sudden a dramatic increase in water usage may indicate a leak). The analytics engine 822 may provide information relating to water usage via one or more dashboards 830 (discussed below) and via alerts 832 presented on the display 826. These dashboards 830 may be used to enforce a fair water consumption policy based on household information, including the number of occupants, occupants ages, type of house or apartment, time of year, location, weather, etc. The analytics engine 824 may also compute and assign metrics to different properties for insurance purposes based on past histories of leaks or freezes.
[0077] The server/cloud 800 and the database 802 also feed information, including estimated flow rates and flow velocities, to a billing engine 824 that is coupled to the display 826. The billing engine 826 produces both printed bills 828 and electronic bills, which may be displayed via the dashboards 830 and alerts 832. For example, the billing engine 826 may determine how much a user has left in his or her budget and project the number days to exceed budget based on present or historic consumption rates. It may also notify the user, via the dashboard 830 or alerts 832, about the amount remaining in the budget, e.g., using thresholds set the user. In addition, the billing engine 826 may enable flexible payment schedules: the user can choose a date up to which he or she want to pay the utilities, with a minimum mandatory payment. It also enable users and utilities to create a “utility debt” metric and a “resident lease score,” similar to credit score, which relates to the utility debt track record. Leasing agents, property managers, and property owners may check a prospective or current tenant's utility debt or resident lease score when reviewing a lease application.
[0078] FIGS. 8C-8G show a smartphone 850 displaying various screens associated with a water use dashboard provide by the smart water networks illustrated in FIGS. 8A and 8B . (Those of skill in the art will readily appreciate that dashboards may be displayed on other devices, including desktop computers, laptop computers, table computers, and even the fluid flow meter 100.) The dashboard provide real-time and historic data and analysis of a water usage measured by one or more water meters 100 or smart manifolds (discussed below).
[0079] These dashboards enable occupants to track their consumption history and related statistics. They can also view the “health” of their apartment in terms of leak or freeze. Once an occupant has launched a dashboard application and logged in, he or she can view a water consumption history and a peer or local rating; download water usage analytics, profile, and usage summary; search bills by date, amount, and payment status; search consumption by date and amount; and compare usage for any day, week, month, or year.
[0080] Similarly, the dashboards enable property owners and managers to view each consumption details by apartment or unit, community, and common area. They also show a unit's “health,” e.g., in terms of its leak/freeze conditions. Once the owner or manager has launched the dashboard application and logged in, the owner or manager can also download summaries of usage details, notify tenants of leaks or excessive consumption (e.g., via email or text message), create custom reports for individual tenants (or by building or the whole community), and view water usage rankings by region, state, or country.
[0081] In addition, a smart water network administrator may remotely manage one or more of the devices (e.g., meters and manifolds) on the network. They can also access dashboards to monitor cumulative consumption details at community and regional levels as well as one or more of the associated individual dashboards available to occupants, owners, and property managers.
[0082] To access the dashboard, the user launches a dashboard app or program by selecting an appropriate icon 852 displayed on the smartphone 850, as shown in FIG. 8C . The smartphone 850 may display a brief welcome screen (not shown) before displaying menu bars 868 that enable the user to select one of several displays and home dashboard 854, shown in FIG. 8D , that shows the latest water consumption, monthly water usage status, daily water breakdown, bill amount (e.g., in dollars), and alert status. In the event of a leak, the home dashboard 854 may automatically notify building maintenance or provide the user with a list of reputable area plumbers to fix the leaks. In addition, the “Home” dashboard 854, like the other dashboards shown in FIGS. 8C-8G , may be used to refresh the display or to change user information.
[0083] The user may select a consumption statistics/history dashboard 856, shown in FIG. 8E , or a consumption rankings/ratings display 858, shown in FIG. 8F , to check or compare his or her usage history. These dashboards 856 and 858 enable the user to check consumption history, compare usage, and download usage reports. They also illustrate comparisons and rankings within and among social networks, neighborhoods, cities, counties, states, and nationwide using water usage statistics derived from flow rate sensor data. It also allows the user to calculate and compare water footprints, to visualize water usage data, to compute variance in water usage for a given fixture or building, and to view rewards for low consumption and/or for reducing consumption. The consumption rankings/ratings display 854 may also enable the user to: (1) check his or her consumption rating, conservation score, share ratings, or total savings; and (2) simulate usage and savings.
[0084] FIG. 8G shows select a “My Bills” dashboard 860 that shows current and previous water bills, including charges and water usage amounts. The “My Bills” dashboard 856 also enables the user to pay or download his or her bill. The user can also check the billing history and search bills using a “My Bills—Billing History” dashboard 862 as shown in FIG. 8H .
[0085] In some cases, the server 800, fluid flow meter 100, or smart manifold may be preloaded with amounts (dollars) the consumer anticipates will be used each month and notified of amount used for budgeting. For example, the “My Bills” dashboard 856 may display the budgeted amount and the balance remaining Amounts may be carried over to the next month, just as minutes are carried over in prepaid cell phones. The dashboard 856 also enables the user to add or subtract credits (dollars) to his or her balance. Prepaid amounts can also be deposited with the water company or property owner and used for payment of consumer usage.
[0086] Inventive flow-sensing meters and dashboards also enable water credits trading similar to the cap and trade system proposed for carbon emissions. Water pricing is based on a tier usage system. If consumers are aware of their consumption and know what they have yet to consume in a lower tier, they may elect to trade or sell the water they have yet to use in the lower tier to a person or business that is nearing a higher tier rate for that month. Immediate awareness of usage and remaining amounts give consumers the ability to trade/sell their remaining lower tier usage rates to higher consumers at the lower tier rates. It also gives consumers the ability to receive an additional reward from the sale of what they conserve to higher users. Higher users have the ability to purchase unused capacity at lower rates compared to the higher tier rates charged by the utility company. Knowledge of usage should promote conservation and result in greater rewards for those who conserve. Public utilities, property owners, and property managers may benefit as well due to overall lower consumption. A public exchange could be established in the city or private exchanges could be developed for multi-tenant buildings, such as apartment buildings and shopping malls, where tenants of the same building trade water credits.
[0087] Inventive dashboards may also provide advice about how to lower water use and alerts relating to the condition of the plumbing. For instance, inventive dashboards may provide instructions to reduce consumption by changing dishwasher or other appliance settings. An inventive dashboard may also notify the user that a particular appliance or fixture is malfunctioning or due for service and provide a corresponding service alert to the user, owner, or building manager. In addition, it could be used to query and review historical data concerning usage data and to estimate upcoming service and replacement dates for plumbing, appliances, etc.
[0088] Inventive dashboards may also recognize and alert users about changes in flow due to leaks, frozen pipes, flooding, malfunctioning appliances, and other maintenance conditions. Manifolds with flow rate sensors can also be used to detect unauthorized water use, e.g., in vacant apartments. The dashboard may also predict potentially damaging situations, such as freezing temperatures, by combining water usage data with data derived from other sources. The processor may also transmit alerts via the wireless interface to the fire department, emergency services, property owner, utility company, and/or insurance company when flow rate data indicates fire, flooding, or another disruption in service.
[0089] Manifolds with Built-in Flow Sensors
[0090] Other embodiments of the present technology include a smart water manifold that can monitor each plumbing device in a building and control individual lines if it detects a leak or freeze condition. An exemplary smart manifold may also be able to distinguish indoor usage from outdoor usage, eliminating the need for exterior irrigation and usage meters. Like the fluid flow meters described above, the smart manifold may be coupled to or form part of a smart fluid metering system that offers improved customer knowledge of consumption and increased water efficiency. Using a smart manifold (and smart fluid flow meters), utilities and utility customers may: disable wasteful or leaking devices remotely; visualize usage data behavioral economics; (instantly) access current and historical water use information at the device level; compare their usage to usage at similar buildings in their neighborhood, city, and state; compare their indoor and outdoor water use; and set up and receive water use alerts, messages and notifications.
[0091] A smart manifold plumbing system controls the distribution of hot and cold water using at least one manifold to channel water to different rooms and/or fixtures in a house, apartment building, shopping mall, or other structure. (Larger structures, such as apartment buildings, may include multiple manifolds, e.g., one manifold per apartment.) An example smart water manifold may be made of polyethylene, polyvinyl chloride (PVC), or copper pipe that defines a lumen with at least one inlet port and two or more outlet ports. In some cases, a single smart manifold may distribute both hot and cold water through separate hot and cold manifold chambers (lumens); in other cases, the smart manifold plumbing system may include separate hot and cold smart water manifolds. In either case, cold water enters the corresponding cold-water manifold or manifold chamber from the water main or service line, and hot water enters the corresponding hot-water manifold or manifold chamber from the water heater, which is also supplied by the water main or service line. The service line, water main, or water heater maintains water pressure in the manifold. A smart manifold may be installed near the water heater during construction for ease of access.
[0092] Each smart manifold (or manifold chamber) includes multiple output ports (outlets) that connect to flexible piping, such as cross-linked polyethylene (PEX) piping or any other piping that can bend without kinking PEX piping can be connected to the manifold output ports via quick connect fittings as known in the art of plumbing. The piping channels water from the manifold to individual fixtures, such as sinks, dishwashers, showers, bath tubs, toilets, and washing machines. Each outlet may also include a gate valve to stop water from flowing to a particular fixture, e.g., if the line breaks or the fixture is under repair. Gate valves may be controlled manually or automatically, e.g., in response to flow rate data collected by flow rate sensors integrated into the outlet ports. The number and size of the manifold output ports, type of fitting, type of gate valve, and type and size of piping depends on the specific installation, may depend on the particular structure.
[0093] Once the smart water manifold and piping are installed, the flow sensors in the smart water manifold can be activated to monitor water flow to the fixtures throughout the structure. In example smart water manifolds, each outlet port has a dedicated flow sensor, which may be an ultrasonic flow sensor or an impeller-based flow sensor. Another optional flow sensor may measure water entering the manifold from the service line or water heater via the manifold's inlet port.
[0094] FIG. 9 shows an example water manifold 900 with an inlet port 910 that can be coupled to a water main, service line, or water heater. Water enters the manifold 900 via the inlet port 910 and flows out of the manifold 900 to different rooms/fixtures via corresponding outlet ports 920, each of which can be connected to piping (e.g., PEX piping) via an optional quick connect fitting. At least one of the outlet ports 920 includes an integrated flow sensor that measures the flow rate of water flow out of the outlet port in question. (The inlet port 910 may also include a flow sensor.) The inlet port 910 and outlet ports 920 may include gate valves to limit or stop the flow of water into or out of the manifold 900.
[0095] Suitable sensors include an ultrasonic sensor 930 (e.g., as in the fluid flow meter 100 shown in FIGS. 1A-1C ), a Lorentz force sensor 940, and an impeller sensor 950. In the illustrated example, the Lorentz force sensor 940 includes a magnetic field source 942 disposed in-line with the water flow, i.e., within an outlet lumen defined by the outlet port. Charged particles in the water flowing past the magnetic field source 942 create an electric field that varies with the flow rate. Electrodes 944 and 946 on opposite sides of the outlet lumen sense the variations in electric field to provide an indication of the flow rate. Example impeller sensors 950 may include an impeller blade 952 disposed in-line with the water flow, i.e., within an outlet lumen defined by the outlet port. Water flowing past the impeller causes the impeller to spin at rate proportional to the water flow rate. Alternative impeller sensors may include positive displacement, nutating disk, multi jet and turbine options as known in the art.
[0096] Each flow sensor may also be or include an ultrasonic transit-time flow meter that includes two (thin-film or disk) piezoelectric transducers as shown in FIG. 9 : a transmit transducer (TX) 910a that transmits a high-frequency burst, or pulse, into the outlet port and a receive transducer (RX) 910b that detects a reflected version of the pulse after some time delay. (FIG. 4A is a plot of example transmitted and received pulses.) Pulses can be transmitted upstream, downstream, or upstream and downstream in alternating fashion. Transmitting upstream results in an increasing delay relative to no-flow for increasing flow rates; transmitting downstream results in an increasing advance relative to no-flow for increasing flow rates. A processor operably coupled to the flow sensors determines the return-time of the reflected pulse by either measuring the time that reflected pulse crosses a pre-determined threshold or by computing a correlation of the reflected pulse with a pre-determined limit and finding the temporal location of the maximum of the resulting correlation waveform. The relationship between flow rate and time-delay-of-arrival is linear at the flow rates of interest (e.g., within a range of about 0 gallons per minute and about 1 gallon per minute, about ¼ gallon per minute, about ½ gallon per minute, about ¼ gallon per minute, etc.).
[0097] Alternatively, the transmit transducer may emit a continuous-wave (cw) signal, and the receive transducer may detect a delayed version of the cw signal. The processor determines the flow rate by measuring the difference in phase, or phase delay, between the transmitted and received cw signals.
Conclusion
[0098] It should be understood that the systems described above may provide multiple ones of any or each of those components and these components may be provided on either a standalone machine or, in some embodiments, on multiple machines in a distributed system. In addition, the systems, methods, and engines described above may be provided as one or more computer-readable programs or executable instructions embodied on or in one or more articles of manufacture. The article of manufacture may be a floppy disk, a hard disk, a CD-ROM, a flash memory card, a PROM, a RAM, a ROM, or a magnetic tape. In general, the computer-readable programs may be implemented in any programming language, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte code language such as JAVA. The software programs or executable instructions may be stored on or in one or more articles of manufacture as object code.
[0099] A flow diagram is used herein. The use of flow diagrams is not meant to be limiting with respect to the order of operations performed. The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
[0100] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.
[0101] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations.
[0102] However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations).
[0103] Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).
[0104] It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
[0105] The foregoing description of illustrative embodiments has been presented for purposes of illustration and of description. It is not intended to be exhaustive or limiting with respect to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosed embodiments. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents.
[0106] While the invention has been particularly shown and described with reference to specific embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the following claims. For example, the manifolds disclosed herein may be used to monitor flow rates of fluids other than water, such as oil, gasoline, etc.
Claims
What is claimed is:
1. A method of monitoring fluid usage in a dwelling, the method comprising:
generating, by each of a plurality of non-invasive ultrasonic fluid flow sensors installed on a corresponding outlet port among a plurality of outlet ports of a fluid manifold device, a respective measurement signal indicative of a fluid flow parameter of a fluid flowing through corresponding outlet port, the fluid flow parameter including a velocity or a flow rate of the fluid flowing through the corresponding outlet port, the fluid manifold device including a plurality of fluid flow meters installed thereon, the plurality of fluid flow meters including the plurality of non-invasive ultrasonic fluid flow sensors, at least one processor communicatively coupled to the plurality of non-invasive ultrasonic fluid flow sensors, and a wireless communication interface communicatively coupled to the at least one processor;
determining, by the at least one processor, for each outlet port of the plurality of outlet ports, a respective estimate of the fluid flow parameter of the fluid flowing through that outlet port based on the measurement signal generated by the ultrasonic fluid flow sensor installed on that outlet port;
transmitting, by the wireless communication interface via one or more communications networks to a server, for each outlet port of the plurality of outlet ports, data indicative of at least one of the estimate of the fluid flow parameter and the measurement signal associated with that outlet port;
determining, by the server, fluid usage information for each outlet port of the plurality of outlet ports based on the data indicative of at least one of the estimate of the fluid flow parameter and the measurement signal associated with that outlet port;
transmitting, by the server via the one or more communications networks to a client device, data indicative of the fluid usage information for each outlet port of the plurality of outlet ports, the fluid usage information including real-time fluid usage information; and
displaying, by a client software application executing on the client device, the fluid usage information for at least one of the plurality of outlet ports on a display of the client device.
2. The method of claim 1 further comprises:
determining, by a billing engine of the server, billing information or real-time fluid usage charges based on the fluid usage information for each outlet port; and
providing, by the billing engine of the server, the billing information or the real-time fluid usage charges to the client software application for display on the client device.
3. The method of claim 1 further comprises:
detecting, by the server, at least one of a fluid leak, a pipe freeze, and a malfunction based on at least one measurement signal associated with at least one respective outlet port; and
transmitting, by the server, an alert indicative of the fluid leak, the pipe freeze, or the malfunction to the client software application for display on the client device.
4. The method of claim 1, wherein the fluid usage information for each outlet port further includes at least one of estimated fluid flow velocities, estimated fluid flow rates, fluid usage per outlet port, historic fluid usage information, statistics of fluid usage, a number of fluid flow events, and durations of flow fluid events.
5. The method of claim 1, wherein the fluid usage information includes comparisons of fluid usage among a plurality of dwellings.
6. The method of claim 1, wherein transmitting data indicative of at least one of the estimate of the fluid flow parameter and the measurement signal to the server includes transmitting the data indicative of at least one of the estimate of the fluid flow parameter and the measurement signal to a wireless hub via the wireless communication interface, the wireless hub communicatively coupled to the server via the one or more communication networks.
7. The method of claim 1, wherein each outlet port of the manifold is associated with a respective fixture or a respective room in the dwelling.
8. The method of claim 1 further comprising transmitting, by the server, firmware updates to the plurality of the fluid flow meters via the one or more communications network.
9. A system for monitoring fluid usage in a dwelling, the system comprising:
at least one fluid flow metering system including:
a fluid manifold device including at least one inlet port and a plurality of outlet ports, each outlet port for connecting to a respective pipe;
a plurality of fluid flow meters installed on the fluid manifold device for measuring fluid flow at the plurality of outlet ports of the fluid manifold device, the plurality of fluid flow meters including:
a plurality of non-invasive ultrasonic fluid flow sensors, each non-invasive ultrasonic fluid flow sensor installed on a corresponding outlet port among a plurality of outlet ports of the fluid manifold device and including at least a pair of transducers to exchange ultrasonic signals through a fluid flowing through the corresponding outlet port and to generate a measurement signal indicative of a fluid flow parameter of the fluid flowing through the corresponding outlet port, the fluid flow parameter including a velocity or a flow rate of the fluid flowing through the corresponding outlet port;
at least one processor, communicatively coupled to the ultrasonic fluid flow sensors associated with the plurality of outlet ports, to determine for each outlet port of the plurality of outlet ports a respective estimate of the fluid flow parameter of the fluid flowing through that outlet port based on the measurement signal generated by the ultrasonic fluid flow sensor installed on that outlet port; and
a wireless communications interface, communicatively coupled to the at least one processor, to transmit, for each outlet port of the plurality of outlet ports, data indicative of at least one of the fluid flow parameter estimate and the measurement signal associated with that outlet port to one or more remote devices via one or more communications network;
a server to receive, from the fluid flow metering system via the one or more communication networks, for each outlet port of the plurality of outlet ports, the data indicative of the at least one of the estimate of the fluid flow parameter and the measurement signal associated with that outlet port, the server including:
an analytics engine to determine fluid usage information for each outlet port of the plurality of outlet ports based on the data indicative of the at least one of the estimate of the fluid flow parameter and the measurement signal for that outlet port, the fluid usage information including real-time fluid usage information; and
a client software application, executable on a client device, configured to receive data indicative of fluid usage information for each of the plurality of outlet ports from the server via the one or more communication networks, and display the data indicative of fluid usage information for at least one of the plurality of outlet ports on a display of the client device.
10. The system of claim 9, wherein the server further comprises a billing engine to determine billing information or real-time fluid usage charges based on the fluid usage information for each outlet port, and provide the billing information or the real-time fluid usage charges to the client software application for display on the client device.
11. The system of claim 9, wherein the fluid flow metering system or the analytics engine is configured to detect at least one of a fluid leak, a pipe freeze, and a malfunction based on at least one measurement signal associated with at least one respective outlet port, and
wherein the server is configured to send an alert indicative of the fluid leak, the pipe freeze, or the malfunction to the client software application for display on the client device.
12. The system of claim 9 wherein the fluid usage information for each outlet port includes at least one of estimated fluid flow velocities, estimated fluid flow rates, fluid usage per outlet port, a number of fluid flow events, and durations of flow fluid events.
13. The system of claim 9, wherein the client software application is configured to provide a dashboard for displaying the fluid usage information.
14. The system of claim 13, wherein the dashboard enables a fluid user or a fluid provider to access real-time fluid usage data, historic fluid usage data, and statistics of fluid usage data.
15. The system of claim 13 comprising a plurality of fluid flow metering systems associated with a plurality of dwellings, wherein the dashboard enables a fluid user or a fluid provider to access comparisons of fluid usage among the plurality of dwellings.
16. The system of claim 9, wherein each ultrasonic fluid flow sensor includes:
(i) a first transducer to transmit an ultrasonic signal through the fluid flowing through the lumen;
(ii) a second transducer to receive a reflected, scattered, or transmitted copy of the ultrasonic signal; and
(iii) a front end to generate the measurement signal from the reflected, scattered, or transmitted copy of the ultrasonic signal.
17. The system of claim 9, wherein each outlet port is associated with a respective fixture or a respective room in the dwelling.
18. The system of claim 9, wherein at least one port of the inlet port and the plurality of outlet ports of the fluid manifold device includes a gate valve for stopping fluid flow through that port.
19. The system of claim 9, wherein the server transmits firmware updates to the plurality of the fluid flow meters via the one or more communications network.
20. The system of claim 9, wherein the at least one processor is configured to determine, for each outlet port, the respective estimate of the fluid flow parameter by computing cross-correlation values between the generated measurement signal associated with that outlet port and a plurality of templates corresponding to separate possible fluid velocities of the fluid flowing through that port, each template is filtered to match a distortion associated with the generated measurement signal associated with that outlet port.
Patent Citations (177)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3780577(A) | 1973-12-01 | Brown | Applicant |
| US3818757(A) | 1974-06-01 | Brown | Applicant |
| US3935735(A) | 1976-02-01 | Lee | Applicant |
| US4540849(A) | 1985-09-01 | Oliver | Applicant |
| US4545244(A) | 1985-10-01 | Yasuda et al. | Applicant |
| US4838127(A) | 1989-06-01 | Herremans et al. | Applicant |
| US4848164(A) | 1989-07-01 | Quarve et al. | Applicant |
| US4902965(A) | 1990-02-01 | Bodrug et al. | Applicant |
| US4940976(A) | 1990-07-01 | Gastouniotis et al. | Applicant |
| US5010568(A) | 1991-04-01 | Merriam et al. | Applicant |
| US5179862(A) | 1993-01-01 | Lynnworth | Applicant |
| US5251490(A) | 1993-10-01 | Kronberg | Applicant |
| US5381462(A) | 1995-01-01 | Larson et al. | Applicant |
| US5493287(A) | 1996-02-01 | Bane | Applicant |
| US5553505(A) | 1996-09-01 | Bignell et al. | Applicant |
| US5639972(A) | 1997-06-01 | Hastings et al. | Applicant |
| US5661527(A) | 1997-08-01 | Ferguson | Examiner |
| US5721383(A) | 1998-02-01 | Franklin et al. | Applicant |
| US5753824(A) | 1998-05-01 | Fletcher-Haynes | Applicant |
| US5767790(A) | 1998-06-01 | Jovellana | Applicant |
| US5777237(A) | 1998-07-01 | Collier et al. | Applicant |
| US5856622(A) | 1999-01-01 | Yamamoto | Examiner |
| US5895866(A) | 1999-04-01 | Neukermans et al. | Applicant |
| US5970801(A) | 1999-10-01 | Ciobanu et al. | Applicant |
| US5974897(A) | 1999-11-01 | Koyano et al. | Applicant |
| US5986574(A) | 1999-11-01 | Colton | Applicant |
| US6049791(A) | 2000-04-01 | Lerner | Applicant |
| US6065350(A) | 2000-05-01 | Hill et al. | Applicant |
| US6065351(A) | 2000-05-01 | Nagaoka et al. | Applicant |
| US6085586(A) | 2000-07-01 | Arvidson | Examiner |
| US6158288(A) | 2000-12-01 | Smith | Applicant |
| US6305233(B1) | 2001-10-01 | Braathen | Examiner |
| US6330831(B1) | 2001-12-01 | Lynnworth et al. | Applicant |
| US6390999(B1) | 2002-05-01 | Zscheile et al. | Applicant |
| US6397683(B1) | 2002-06-01 | Hagenmeyer et al. | Applicant |
| US6508135(B1) | 2003-01-01 | Martin et al. | Applicant |
| US6556142(B2) | 2003-04-01 | Dunstan | Applicant |
| US6618709(B1) | 2003-09-01 | Sneeringer | Applicant |
| US6657552(B2) | 2003-12-01 | Belski et al. | Applicant |
| US6745632(B1) | 2004-06-01 | Dryer | Examiner |
| US6758100(B2) | 2004-07-01 | Huang | Applicant |
| US6766276(B1) | 2004-07-01 | Dury | Applicant |
| US6772643(B2) | 2004-08-01 | Eguchi et al. | Applicant |
| US6782761(B2) | 2004-08-01 | Imai et al. | Applicant |
| US6868741(B2) | 2005-03-01 | Harman | Applicant |
| US6871534(B1) | 2005-03-01 | Hamada et al. | Applicant |
| US6900737(B1) | 2005-05-01 | Ardalan et al. | Applicant |
| US6900738(B2) | 2005-05-01 | Crichlow | Applicant |
| US6901813(B2) | 2005-06-01 | Riegel | Applicant |
| US6947854(B2) | 2005-09-01 | Swarztrauber et al. | Applicant |
| US6956500(B1) | 2005-10-01 | Ducharme et al. | Applicant |
| US7024944(B2) | 2006-04-01 | Imai et al. | Applicant |
| US7027808(B2) | 2006-04-01 | Wesby | Applicant |
| US7039529(B2) | 2006-05-01 | Keech | Applicant |
| US7058549(B2) | 2006-06-01 | Gysling et al. | Applicant |
| US7059200(B2) | 2006-06-01 | Sallee | Applicant |
| US7098783(B2) | 2006-08-01 | Crichlow | Applicant |
| US7117104(B2) | 2006-10-01 | Urdaneta et al. | Applicant |
| US7126493(B2) | 2006-10-01 | Junker et al. | Applicant |
| US7204157(B2) | 2007-04-01 | Furmidge et al. | Applicant |
| US7310052(B2) | 2007-12-01 | Bowman | Applicant |
| US7315257(B2) | 2008-01-01 | Patterson et al. | Applicant |
| US7330797(B2) | 2008-02-01 | Bailey et al. | Applicant |
| US7342504(B2) | 2008-03-01 | Crane et al. | Applicant |
| US7342506(B2) | 2008-03-01 | Paoli et al. | Applicant |
| US7389187(B2) | 2008-06-01 | Kersey et al. | Applicant |
| US7443313(B2) | 2008-10-01 | Davis et al. | Applicant |
| US7673527(B2) | 2010-03-01 | Ehring et al. | Applicant |
| US7701580(B2) | 2010-04-01 | Bassler et al. | Applicant |
| US7747534(B2) | 2010-06-01 | Villicana et al. | Applicant |
| US8019559(B1) | 2011-09-01 | Stevens et al. | Applicant |
| USD662432(S) | 2012-06-01 | Leaders et al. | Applicant |
| US8489342(B2) | 2013-07-01 | Dugger et al. | Applicant |
| US8618941(B2) | 2013-12-01 | Javey et al. | Applicant |
| US2003/0088527(A1) | 2003-05-01 | Hung | Examiner |
| US2004/0006439(A1) | 2004-01-01 | Hunter | Examiner |
| US2004/0059585(A1) | 2004-03-01 | Villicana et al. | Applicant |
| US2004/0243524(A1) | 2004-12-01 | Crichlow | Applicant |
| US2005/0033534(A1) | 2005-02-01 | Villicana et al. | Applicant |
| US2005/0245827(A1) | 2005-11-01 | Takeda et al. | Applicant |
| US2006/0012491(A1) | 2006-01-01 | Mahowald | Applicant |
| US2006/0020404(A1) | 2006-01-01 | Kishiro et al. | Applicant |
| US2006/0117867(A1) | 2006-06-01 | Froehlich | Examiner |
| US2006/0247869(A1) | 2006-11-01 | Lucero | Applicant |
| US2007/0005273(A1) | 2007-01-01 | Heidl et al. | Applicant |
| US2007/0284293(A1) | 2007-12-01 | Pitchford et al. | Applicant |
| US2008/0001778(A1) | 2008-01-01 | Challener et al. | Applicant |
| US2008/0048883(A1) | 2008-02-01 | Boaz | Applicant |
| US2008/0086394(A1) | 2008-04-01 | O'Neil et al. | Applicant |
| US2008/0129538(A1) | 2008-06-01 | Vaswani et al. | Applicant |
| US2008/0132185(A1) | 2008-06-01 | Elliott et al. | Applicant |
| US2008/0150751(A1) | 2008-06-01 | Sala et al. | Applicant |
| US2008/0156107(A1) | 2008-07-01 | Ao et al. | Applicant |
| US2008/0177678(A1) | 2008-07-01 | Di Martini et al. | Applicant |
| US2008/0180274(A1) | 2008-07-01 | Cumeralto et al. | Applicant |
| US2008/0196511(A1) | 2008-08-01 | Ehring et al. | Applicant |
| US2008/0224892(A1) | 2008-09-01 | Bogolea et al. | Applicant |
| US2008/0250870(A1) | 2008-10-01 | Rhodes | Applicant |
| US2008/0272933(A1) | 2008-11-01 | Cahill-O'Brien et al. | Applicant |
| US2008/0302172(A1) | 2008-12-01 | Kates | Applicant |
| US2009/0006107(A1) | 2009-01-01 | Golden | Applicant |
| US2009/0017771(A1) | 2009-01-01 | Lackey et al. | Applicant |
| US2009/0102681(A1) | 2009-04-01 | Brennan et al. | Applicant |
| US2009/0109056(A1) | 2009-04-01 | Tamarkin et al. | Applicant |
| US2009/0153356(A1) | 2009-06-01 | Holt | Applicant |
| US2009/0160674(A1) | 2009-06-01 | Vangala | Applicant |
| US2009/0189778(A1) | 2009-07-01 | Juan et al. | Applicant |
| US2009/0217771(A1) | 2009-09-01 | Hoecker | Applicant |
| US2009/0309755(A1) | 2009-12-01 | Williamson | Examiner |
| US2010/0313958(A1) | 2010-12-01 | Patel | Examiner |
| US2011/0074601(A1) | 2011-03-01 | Cornwall | Applicant |
| US2011/0219885(A1) | 2011-09-01 | Shumilov et al. | Applicant |
| US2011/0288794(A1) | 2011-11-01 | Chen | Applicant |
| US2012/0017700(A1) | 2012-01-01 | Wiest et al. | Applicant |
| US2012/0144930(A1) | 2012-06-01 | Aughton et al. | Applicant |
| US2012/0173169(A1) | 2012-07-01 | Skelding | Applicant |
| DE19962954 | 2001-06-01 | Applicant | |
| DE10140792 | 2003-03-01 | Applicant | |
| DE10210788 | 2003-09-01 | Applicant | |
| DE202005004510 | 2005-10-01 | Applicant | |
| DE202006001060 | 2006-06-01 | Applicant | |
| DE102006050729 | 2008-05-01 | Applicant | |
| DE102007035478 | 2009-02-01 | Applicant | |
| DE102007059032 | 2009-06-01 | Applicant | |
| EP736751 | 1996-03-01 | Applicant | |
| EP834849 | 1996-04-01 | Applicant | |
| EP629098(A2) | 2001-12-01 | Applicant | |
| EP1306823 | 2003-05-01 | Applicant | |
| EP1887327 | 2008-02-01 | Applicant | |
| EP2012093 | 2008-04-01 | Applicant | |
| EP1983311 | 2008-10-01 | Applicant | |
| EP2131162(A1) | 2009-12-01 | Applicant | |
| GB2229834 | 1990-10-01 | Applicant | |
| GB2440961 | 2008-02-01 | Applicant | |
| GB2452072 | 2009-02-01 | Applicant | |
| JP55-027938 | 1980-02-01 | Applicant | |
| JPS57-128852 | 1982-08-01 | Applicant | |
| JPH109914 | 1998-01-01 | Applicant | |
| JP10-255190 | 1998-09-01 | Applicant | |
| JP2002-048598 | 2002-02-01 | Applicant | |
| JP2002-214012 | 2002-07-01 | Applicant | |
| JP2002-296290 | 2002-10-01 | Applicant | |
| JP2003-152881 | 2003-05-01 | Applicant | |
| JP2004-094766 | 2003-05-01 | Applicant | |
| JP2005-321222 | 2005-11-01 | Applicant | |
| JP2007-071695(A) | 2007-03-01 | Applicant | |
| JP2008-507693 | 2008-03-01 | Applicant | |
| JP2008-232990 | 2008-10-01 | Applicant | |
| JP2008-232991 | 2008-10-01 | Applicant | |
| JP2008-275607 | 2008-11-01 | Applicant | |
| JP2008-298560 | 2008-12-01 | Applicant | |
| JP2008-304281 | 2008-12-01 | Applicant | |
| JP2009-008406 | 2009-01-01 | Applicant | |
| JP2009-085972 | 2009-04-01 | Applicant | |
| JP11-086173 | 2011-04-01 | Applicant | |
| KR100769619 | 2007-10-01 | Applicant | |
| UA72865 | 2005-04-01 | Applicant | |
| WO-2005/015890 | 1900-01-01 | Applicant | |
| WO-90/00724 | 1990-01-01 | Applicant | |
| WO-98/52003 | 1998-11-01 | Applicant | |
| WO-99/31612 | 1999-06-01 | Applicant | |
| WO-99/57697 | 1999-11-01 | Applicant | |
| WO-00/03206(A1) | 2000-01-01 | Applicant | |
| WO-01/35366 | 2001-05-01 | Applicant | |
| WO-02/057721 | 2002-07-01 | Applicant | |
| WO-02/060120 | 2002-08-01 | Applicant | |
| WO-02/084558 | 2002-10-01 | Applicant | |
| WO-03/006924 | 2003-01-01 | Applicant | |
| WO-2004/008414 | 2004-01-01 | Applicant | |
| WO-2004/099732 | 2004-11-01 | Applicant | |
| WO-2007/131169 | 2007-11-01 | Applicant | |
| WO-2008/025939 | 2008-03-01 | Applicant | |
| WO-2008/053193(A1) | 2008-05-01 | Applicant | |
| WO-2009/011817 | 2009-01-01 | Applicant | |
| WO-2009/043065 | 2009-04-01 | Applicant | |
| WO-2009/044126 | 2009-04-01 | Applicant | |
| WO-2010/091648(A1) | 2010-08-01 | Applicant |
Non-Patent Literature (20)
- Wannamaker et al., A Theory of Nonsubtractive Dither, IEEE Transactions on Signal Processing, vol. 48, No. 2, Feb. 2000.Examiner
- Carlson, J. et al., “Ultrasonic particle velocimetry in multiphase flows,” Ultrasonics Symposium, 2002. Proceedings. 2002 IEEE Date of Conference: Oct. 8-11, 2002.Applicant
- Extended European Search Report dated Aug. 7, 2014 in European Patent Application No. 12759881.1.Applicant
- International Report on Patentability on PCT/US2012/029481 dated 710/03/2013.Applicant
- International Search Report on PCT/US2012/029481 dated Jul. 13, 2012.Applicant
- Jimenez, A. et al., “Aqueous-liquids characterization based on encoded ultrasonic signals,” IEEE International Symposium on Intelligent Signal Processing, 2009. WISP 2009. Date of Conference: Aug. 26-28, 2009.Applicant
- Kikura, Hiroshige et al., “Velocity profile measurements in bubbly flow using multi-wave ultrasound technique,” Chemical Engineering Communications, v 197, n 2, p. 114-133, Jan. 2010.Applicant
- Notice of Allowance on U.S. Appl. No. 13/691,296 dated Mar. 20, 2013.Applicant
- Oberg, K; Mueller, D S., “Validation of Streamflow Measurements Made with Acoustic Doppler Current Profilers,” Journal of Hydraulic Engineering 12 (Dec. 2007): 1421-1432.Applicant
- Office Action on U.S. Appl. No. 14/005,169 dated Nov. 13, 2014.Applicant
- Office Action on U.S. Appl. No. 14/005,169 dated Apr. 27, 2015.Applicant
- Swillens, A; Lovstakken, L; Kips, J; Torp, H; Segers, P., “Ultrasound simulation of complex flow velocity fields based on computational fluid dynamics,” IEEE Transactions on Ultrasonics, Ferroelectrics and Frequency Control 56. 3 (2009).Applicant
- Written Opinion on PCT/US2012/029481 dated Jul. 13, 2012.Applicant
- Japanese Notification of Reasons for Refusal on 2013-558215 dated Jan. 26, 2016.Applicant
- Notice of Allowance on U.S. Appl. No. 14/005,169 dated Dec. 15, 2015.Applicant
- Office Action on U.S. Appl. No. 14/005,169 dated Sep. 17, 2015.Applicant
- Japanese Notification of Reasons for Refusal on 2013-558215 dated Aug. 16, 2016.Applicant
- Notice of Allowance on U.S. Appl. No. 15/091,130 dated Jul. 13, 2016.Applicant
- Notice of Allowance on U.S. Appl. No. 15/091,130 dated May 3, 2016.Applicant
- Office Action for Israel Application No. 228440 dated Jul. 19, 2017.Applicant