Patent Description:
Homes and commercial buildings have water distributed throughout with various pipes and egress regulated with plumbing fixtures. It is not uncommon for there to be leaks as there are multiple points of failure in any water distribution system. For example, water pipes exposed to freezing temperatures are prone to bursting with the expansion of ice. Leaks cause tremendous property damage, promote toxic mold growth and needlessly waste water.

Detection of leaks in plumbing is notoriously difficult. Often the first sign of a problem is flooding. There are flow sensors that measure movement of liquid, but detection of leaks, especially small ones, is a vexing problem. Although a small leak may never result in noticeable flooding, it can nurture growth of toxic mold and eventually progress to a large leak causing various water damage.

<CIT> B <NUM> discloses a fluid measuring device comprising two pressure ports, a fluid flow restriction and a temperature port. The fluid measuring device can provide users with early leak and spill detection. <CIT> discloses a water leak detector for detecting fluid flow in a pipe system. A difference value between a temperature measured by an ambient temperature sensor and a temperature measured by pipe temperature sensor is compared to a threshold value. If the difference value is above the threshold value for a time period having predetermined duration, it is determined that fluid is flowing in the pipe system.

Described herein is a plumbing analyzer which uses temperature and/or pressure sensors to determine when minute flows are occurring in the plumbing. One or more temperature and pressure sensors are thermally coupled to the liquids within the plumbing. Different configuration plumbing systems may use different algorithms to process the temperature and/or pressure sensor information to accurately detect leaks. Signal processing of the temperature sensor and optionally pressure and/or flow sensors allow recognizing when a minute flow in the pipe is most likely a leak and not normal usage. Some embodiments use pressure sensing to spectrally determine when there is a leak in the plumbing system.

Also described herein is a temperature sensor(s) and/or pressure sensor(s) coupled to the water in the plumbing system which is used to determine if there is a leak. During times of inactivity for fixtures in the plumbing systems, a flow sensor might measure usage of water that would indicate a leak. For very small leaks, the flow is below a minimum measurable flow of the flow sensor. Embodiments of the invention measure temperature of water within a pipe coupled to the plumbing system. Temperature will generally decay in a particular predicable way when there is flow as the temperature of water upon entry to the building is lower than the air temperature within the building. Similarly, pressure will generally decay in certain plumbing system configurations as the leak depletes water from the pipes. Spectral analysis of the pressure data can detect changes in the spectra associated with the leak in some plumbing systems. Signal processing, machine learning and/or statistical approaches are used to analyze the temperature and optionally flow and/or pressure over time to determine when a leak is likely. According to the invention, a method and a system for detecting small leaks of liquid in a plumbing system is disclosed, as set out in the independent claims. Liquid flow is measured within a pipe of the plumbing system with a flow sensor. A temperature of the liquid is measured over time at a point in the plumbing system upstream from a leak while there is no intentional liquid egress and no measured flow with the flow sensor. Measuring temperature over time to determine decay of the measured temperature exceeds threshold decay of liquid in the plumbing system. A leak detected signal is transmitted when the decay exceeds a threshold decay. Some embodiments use signal processing techniques to match the measured temperature to a leak profile. Other embodiments, measure temperature at a second point of the plumbing system and process a second measured temperature at the second point before correcting the processing the measured temperature using the second measured temperature. In some installations, the measuring temperature at the second point is measuring air temperature away from the liquid. One embodiment determines air temperature within a building hosting the plumbing system, where the decay is a function of the air temperature. A thermal mass of the plumbing system can be determined over time to determine the predicted decay. In one embodiment, the flow through the leak in the pipe is below a perceptible limit of the flow sensor.

Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating various embodiments, are intended for purposes of illustration only and are not intended to necessarily limit the scope of the disclosure. The matter for which protection is sought is defined by the appended claims.

In the appended figures, similar components and/or features may have the same reference label.

The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment. It is understood that various changes may be made in the function and arrangement of elements without departing from the scope as set forth in the appended claims.

A plumbing analyzer finds small leaks that are not detected by a conventional flow sensor. For example, turbine flow meters don't sense below <NUM> gpm and ultrasonic flow sensors have resolution down to <NUM>-<NUM> gpm. Statistical approaches and signal processing techniques process temperature readings for the leak detection by relying on variations of the temperature signal to provide first insights into the possibility of a leak with pressure and/or flow sensing optionally assisting in validating the likelihood of a leak in a plumbing system. Embodiments allow detection of leaks below <NUM> gpm and as low as <NUM> gpm.

When water is stagnant in the pipes (i.e., there is no intentional water egress or leaks) the temperature of water varies based on the location the water device is installed and the temperature of the water supply entering the building. Where the water device is installed inside a building, for example, the temperature will stabilize at the ambient temperature typically regulated by a HVAC thermostat. On the other hand, if the plumbing analyzer is placed outdoors it will vary as the weather changes over the course of the day. For small flows that are not detected by conventional flow sensors, there is a change in the temperature noted by the plumbing analyzer. Depending on the rate of water flow the temperature stabilizes at a certain temperature.

The city supplied water temperature varies relatively slowly since they are typically delivered via pipes which are buried underground. Since these pipes are buried underground there is less variation in temperature as compared to the atmospheric temperature. Ground water temperatures vary slightly from around <NUM> to <NUM> °F (<NUM> to <NUM>). Such temperature changes are dependent upon well depth and aboveground storage facilities. Surface water temperatures vary with seasonal change from around <NUM> to <NUM> °F (<NUM> to <NUM>) with even higher temperatures in the deep South and Southwest. It can be said that the city supplied water temperature remains relatively stable during a given season for a given location (Temperature varies from <NUM> °F in Anchorage, AK to <NUM> °F in Phoenix, AZ). The temperature changes noted by the water device are due to water flowing through the pipes and can help detect small unintended water usages or leaks continuously without engaging the shut-off-valve or other techniques that actively engage the plumbing system as described in Application Serial Number <CIT>, which is incorporated by reference for all purposes.

Pressure in the plumbing system can be analyzed with the water device. The municipal water system is pressurized so that the plumbing fixtures dispense water when opened. The water main into the building is typically at <NUM>-<NUM> psi. Most buildings buffer the water main pressure with a pressure reducing valve (PRV) to lower the pressure to <NUM>-<NUM> psi, which also isolates noise seen with sensors when connected directly to the water main. Within the building, temperature and pressure will stabilize at a given rate of flow caused by leak or other egress from the plumbing system even for situations with the flow sensor cannot perceive anything.

Referring first to <FIG>, a block diagram of an embodiment of a water analysis system <NUM> is shown. The municipal water system <NUM> is connected to the building <NUM> with a water main <NUM>, but other embodiments could source their water from a well, a cistern, a tank, or any other source. Different water sources may use different flow and leak detection algorithms.

Remote from the building <NUM> over the Internet <NUM> is a cloud analyzer <NUM> that is in communication with various buildings and user devices <NUM>. User account information, sensor data, local analysis, municipal water usage information for the building <NUM> is passed to the cloud analyzer <NUM>. User devices <NUM> may connect with the water device <NUM> and the cloud analyzer through a local network <NUM> and/or a cellular network. The water device <NUM> can have an Ethernet, a broadband over power line, a WiFi, and/or a cellular connection coupled to the cloud analyzer <NUM>. Some embodiments include a gateway or peer node that the water device can connect to that is coupled to the network <NUM> and/or Internet <NUM> using WiFi, Bluetooth, Zigbee, or other short range wireless signals. Generally, there is a gateway or firewall between the network <NUM> and the Internet <NUM>.

Within the building <NUM>, the plumbing system <NUM> is a collection of pipes connected to appliances and fixtures all coupled to the water main <NUM>. A building may have one or more water device(s) <NUM> in fluid communication with the plumbing system <NUM>. A water device <NUM> may be coupled to the cold and/or hot water pipe at a particular location and wirelessly or wire communicates with the network <NUM>.

One or more point interface(s) <NUM> may or may not be in fluid communication with the plumbing system, but can gather data in some embodiments such as ambient temperature, temperature outside the pipe, and/or acoustic waves inside or outside the pipe. The point interfaces <NUM> are coupled to the network <NUM> to allow input and output to the user with an interface. The point interface may be separate from the plumbing system <NUM> altogether while providing status on the water analysis system <NUM> such as instantaneous water usage, water usage over a time period, water temperature, water pressure, etc. Error conditions such as leaks, running toilets or faucets, missing or defective PRV, water bill estimates, low pressure, water heater malfunction, well pump issues, and/or other issues with the plumbing system <NUM> can be displayed at the point interfaces <NUM>.

The user device <NUM> can be any tablet, cellular telephone, web browser, or other interface to the water analysis system <NUM>. The water device <NUM> is enrolled into a user account with the user device <NUM>. All the information available at a point interface <NUM> can be made available to the user device using an application, app and/or browser interface. The user device <NUM> can wired or wirelessly connect with the water device(s) <NUM>, cloud analyzer <NUM>, and/or point interface(s) <NUM>.

With reference to <FIG>, a block diagram of an embodiment of a water device <NUM> is shown. A power supply <NUM> could be internal or external to the water device <NUM> to provide DC power to the various circuits. In some embodiments, a replaceable battery provides power while other embodiments use the water pressure to drive a turbine that recharges a battery to provide power.

An analysis engine <NUM> gathers various data from the pressure sensor(s) <NUM>, flow sensor(s) <NUM>, temperature sensor(s) <NUM>, and optionally audio sensor(s) <NUM>. Interface pages <NUM> allow interaction with the water device <NUM> through a network interface <NUM> in a wired or wireless fashion. The analysis engine <NUM> also supports a unit interface <NUM> that is physically part of the water device <NUM> to display various status, information and graphics using an OLED, LED, LCD display and/or status lights or LEDs.

Various information is stored by the water device <NUM>, which may be reconciled with the cloud analyzer <NUM> in-whole or in-part using the network interface <NUM>. Sensor data for the various sensors <NUM>, <NUM>, <NUM>, <NUM> are stored in the sensor data store <NUM> over time to allow for longitudinal analysis. For example, several hours through several days of sensor data can be stored. The granularity of readings and length of time stored may be predefined, limited by available storage or change based upon conditions of the plumbing system <NUM>. For example, data samples every second over a two day period could be stored, but when a leak is suspected the sample rate could increase to <NUM> times a second for <NUM> hours of time.

When fixtures or appliances interact with the water in the plumbing system <NUM>, repeating patterns occur at the water device <NUM>. Pattern profiles <NUM> are stored to quickly match current sensor readings to known events. For example, a particular faucet when used may cause the flow, pressure and/or temperature sensor <NUM>, <NUM>, <NUM> readings to fluctuate in a predictable manner such that the pattern profile can be matched to current readings to conclude usage is occurring. Application Serial Number <CIT>, describes this analysis and is incorporated by reference for all purposes. The pattern profiles <NUM> can be in the time domain and/or frequency domain to support various condition matching by the analysis engine <NUM>. Both intentional egress and leaks have pattern profiles <NUM> that are stored.

A configuration database <NUM> stores information gathered for the water device <NUM>. The Table depicts water supply parameters stored in the configuration database <NUM>. Type of plumbing system <NUM> includes those without a PRV, well water, working PRV, and non-functional PRV. The water supply to the water main <NUM> can be from the municipal water system <NUM>, a well, a water tank, or other source. The configuration database <NUM> can be automatically populated using algorithms of the analysis engine <NUM> or manually entered by the user device <NUM>. Different fixtures and appliances connected to the plumbing system <NUM> are noted in the configuration database <NUM>.

Referring next to <FIG>, a block diagram of an embodiment of a cloud analyzer <NUM> is shown. The cloud analyzer <NUM> receives data and configuration information from many buildings <NUM> throughout the water analysis system <NUM>. Each building <NUM> has a system profile <NUM> that is stored including the fixtures, appliances, water device(s) <NUM>, point interface(s) <NUM>, type of water supply, water source type are stored. Account information <NUM> including login credentials, building location, and user demographic information is also stored. Gathered sensor data in raw and processed form is stored as analyzer data <NUM> and could include usage history, specific egress events, leaks detected, etc..

The system analyzer <NUM> can process the data from each building <NUM> to find patterns corresponding to leaks, malfunctions, and other events that are not recognized by the water device <NUM> locally. The system analyzer <NUM> can access any water device <NUM> or point interface <NUM> to test functionality, update software, and gather data. Where a user device <NUM> is coupled to the cloud analyzer <NUM>, the system analyzer <NUM> receives commands to perform requested tasks. For example, the user device <NUM> can query for usage on a per fixture or appliance basis. Overall usage can also be determined. The system analyzer <NUM> can access the water utility usage and billing to provide insights into costs and overall consumption. For those utilities that provide usage information in real time, the usage and cost can be determined for each use of the plumbing system <NUM>.

An account interface <NUM> allows various water devices <NUM> and user devices <NUM> to interact with the cloud analyzer <NUM> through an internet interface <NUM>. The cloud analyzer <NUM> provides historical and real time analysis of buildings <NUM> a user is authorized to access. Various interaction pages allow entry of plumbing system information, configuration parameters, building location and user demographic information. Various reports and status parameters are presented to the user device through the account interface <NUM>.

With reference to <FIG>, a block diagram of an embodiment of a plumbing system <NUM> is shown. The municipal water system <NUM> is connected to a main shutoff valve <NUM>-<NUM> before the water main passes through a water meter <NUM> provided by the municipality for billing purposes. The water meter <NUM> may be electronically or manually read to determine the bill, but some embodiments allow real time reading of the water meter <NUM> electronically.

Building codes often require use of a PRV <NUM>, but not universally. Older homes may also be missing a PRV, have one that no longer functions properly or have less than <NUM> psi supplied by the municipal water system <NUM>. A building shutoff valve <NUM>-<NUM> is often located interior to the building <NUM> and provides another place to close off the water main. A water device <NUM> is located after the building shutoff valve <NUM>-<NUM>, but before a water heater <NUM> in this embodiment. The water device <NUM> can be placed under the sink, near an appliance or any other location where fluid coupling is convenient along with a source of power is nearby. The hot water pipes <NUM> provide heated water to the building <NUM> and the cold water pipes <NUM> provide unheated water varying between the ambient temperature in the building <NUM> and the temperature of the municipal water system <NUM>.

This embodiment has a single bathroom <NUM>, a kitchen <NUM>, a washing machine <NUM>, and a water spigot <NUM>, but other embodiments could have more or less fixtures and appliances. The bathroom <NUM> has a shower <NUM>, sink <NUM>, bathtub <NUM>, and toilet <NUM> that use water. The sink <NUM>, bathtub <NUM>, and shower <NUM> are all hooked to both the hot and cold water pipes <NUM>, <NUM>. The toilet <NUM> only requires cold water so is not hooked to the hot water supply.

The kitchen <NUM> includes a two-basin sink <NUM>, a refrigerator with liquid/ice dispenser, and a dishwasher. The refrigerator only receives cold water <NUM>, but the two-basin sink <NUM> and dishwasher <NUM> receive both cold and hot water <NUM>, <NUM>. Kitchens <NUM> commonly include single-basin sinks and other appliances that might be coupled to the water.

Referring next to <FIG>, a diagram of an embodiment of an installed water device <NUM> is shown. The water device <NUM> passes water through a pipe <NUM> that is integral to the water device <NUM> and attached on both ends to either a hot or a cold water line. The integral portion of the pipe <NUM> could be made of copper, PVC, plastic, or other building pipe material and could be mated to the plumbing system <NUM> with soldered joints, glued joints, and/or detachable and flexible hoses.

There are several modules that make up the water device <NUM>. The power supply <NUM> powers the water device <NUM> and could be internal or external to the enclosure. A network module <NUM> includes the network interface <NUM> to allow wired or wireless communication with the network <NUM> and Internet <NUM> to other components of the water analysis system <NUM>. A display assembly <NUM> includes the unit interface <NUM>.

Another module is the circuit card <NUM> which performs the processing for various sensors. Sensor information can be processed on the circuit card using the analysis engine <NUM> and/or processed in the cloud using the system analyzer <NUM>. Sensor information is gathered and analyzed over hours and days to find weak signals in the data indicating usage, leaks and other issues. The circuit card <NUM> might recognize sensor samples of interest and upload those to the cloud analyzer <NUM> for deeper learning. The circuit card and cloud analyzer can use artificial intelligence, genetic algorithms, fuzzy logic, and machine learning to recognize the condition and state of the plumbing system <NUM>.

This embodiment includes three temperature sensors <NUM> to measure the ambient temperature with a sensor near the outside of the enclosure and away from the internal electronics and water temperature of the water in the pipe <NUM> in two locations. A first temperature sensor <NUM>-<NUM> measures water temperature in contact with the water as it enters the pipe <NUM> of the water device <NUM> away from any heat that the various circuits might generate. A second temperature sensor <NUM>-<NUM> measures water temperature at a second location away from the first temperature sensor <NUM>-<NUM>. Based upon readings of the two water temperature sensors <NUM>-<NUM>, <NUM>-<NUM>, the heat generated by the water device <NUM> can be algorithmically corrected for. Some embodiments may only use a single water temperature sensor and/or forgo the ambient temperature sensing. Ambient temperature may be measured by other equipment in the building and made available over the network <NUM>, for example, the thermostat, smoke detectors, point interface(s) <NUM> can measure ambient temperature and provide it to other equipment in the building <NUM>.

This embodiment includes an electronically actuated shut-off valve <NUM>. The shutoff valve <NUM> can be used to prevent flooding for leaks downstream of the water device <NUM>. Additionally, the shutoff valve <NUM> can aid in detecting leaks. Closing the shutoff valve <NUM> and detecting a falling pressure is indicative of a leak downstream. Some embodiments can partially close the shutoff valve <NUM> to regulate pressure downstream.

A flow sensor <NUM> is used to measure the flow in the pipe <NUM>. In this embodiment, an ultrasonic flow sensor is used, but other embodiments could use a rotameter, variable area flow meter, spring and piston flow meter, mass gas flow meters, turbine flow meters, paddlewheel sensors, positive displacement flow meter, and vortex meter. Generally, these meters and sensors cannot measure very small flows in a pipe in a practical way for building deployments.

The circuit card <NUM> is coupled to a pressure sensor <NUM> coupled to the water in the pipe <NUM>. Readings from the pressure sensor are used to test the PRV, well pump, water supply, and pipe for leaks as well as identify normal egress from the water fixtures and appliances. Pressure and temperature vary with flow such that the pressure sensor <NUM> and temperature sensor <NUM>-<NUM>, <NUM>-<NUM> can be used to detect flow as small as tiny leaks under certain circumstances. The circuit card <NUM> observes trends in the sensor data, performs spectral analysis, pattern matching and other signal processing on the sensor data.

With reference to <FIG>, a chart <NUM>-<NUM> showing an embodiment of a leak condition is shown with temperature data over time. In a situation where the building <NUM> is warmer than the water supply, flow in the plumbing system <NUM> will cause the temperature to fall from the ambient indoor temperature <NUM> to the water supply temperature <NUM>. The slope of the fall increases with the spread in temperature difference and the rate of consumption from the municipal water system <NUM>. Algorithms to detect leak only activate when intentional usage is not present.

Referring next to <FIG>, a chart <NUM>-<NUM> showing an embodiment of a no leak condition is shown with temperature data over time. The measured temperature in the plumbing system <NUM> will generally rise to the ambient indoor temperature <NUM> in the absence of any intentional flow or any leak. Typically, the sensor readings are far noisier than depicted in the charts which show a highly smoothed version.

With reference to <FIG>, a chart <NUM>-<NUM> showing an embodiment of a leak condition is shown with pressure data over time. There is a pressure threshold <NUM> for houses with a PRV or well where the water main or well pump will activate when the pressure in the plumbing system <NUM> falls below the pressure threshold <NUM>. With intentional usage or a leak, the pressure will drop until the plumbing system <NUM> is pressurized by the PRV opening or the pump activating.

Referring next to <FIG>, a chart <NUM>-<NUM> showing an embodiment of a no leak condition is shown with pressure data over time. Generally, the plumbing system <NUM> will remain pressurized so long as there is no intentional or unintentional egress. For buildings without a PRV, the pressure fluctuates as neighbors and other users of the municipal water system <NUM> activate their fixtures and appliances.

With reference to <FIG>, a flow chart of an embodiment of a process <NUM> for detecting leaks is shown. The depicted portion of the process <NUM> begins in block <NUM> where the water device <NUM> is configured. This includes installation that couples the water device <NUM> physically to the plumbing system <NUM>. Power is run to the water device <NUM> along with a connection to the network <NUM>. The water device <NUM> is enrolled into an account with the cloud analyzer <NUM>. Information about the building <NUM>, demographic information about the account owner, etc. are all entered with the user device <NUM>.

Once the physical installation and account configuration is done, the water device <NUM> is configured to detect the topology of the plumbing system <NUM> in block <NUM>. Using signal processing the user activates each fixture and appliance in succession to enroll its signature. Over time, the water device <NUM> in conjunction with the cloud analyzer <NUM> processes sensor data to more accurately detect intentional water egress. In block <NUM>, the flow sensor detects new flow. Where determined to be normal intentional egress in block <NUM> the responsible water fixture(s) and/or appliance(s) responsible are determined in block <NUM>. The usage is recorded in block <NUM>. The sensor data, usage, leaks are logged at the water device <NUM>. In block <NUM>, relevant sensor readings, processed information and any errors and leak conditions are reported to the cloud analyzer <NUM>. Push or pull messages are sent to the user device <NUM> for any leaks, abnormal usage or other errors.

Where the egress is not determined normal in block <NUM>, processing continues to block <NUM>. Abnormal egress <NUM> is where the flow sensor <NUM> detects flow that doesn't correspond to any known fixture or appliance. This could correspond to a change in the plumbing system <NUM> so when the user receives the error, they can correct the system noting the change to the plumbing system <NUM> to avoid false alarms in the future. Processing continues after the suspect leak is detected in block <NUM> to block <NUM>.

Where there is no flow detected by the flow sensor back in block <NUM>, small leak detection is performed. In block <NUM>, the algorithm used for testing varies upon what type of water supply and water source. For example, the algorithm used for well water is different from one used for a building using the municipal water system without a PRV being for the building <NUM>. The various pressure and temperature sensors <NUM>, <NUM> gather data over time in blocks <NUM> and <NUM> as separate processes. The sensor readings are analyzed using various signal processing techniques in block <NUM> as fully detailed in <FIG> below. Where a small leak is detected processing continues to block <NUM> and to block <NUM> where no leak is detected.

Referring next to <FIG>, a flow chart of an embodiment of a process 900A for analyzing temperature sensor <NUM> readings is shown. This process 900A runs continuously where there is no intentional egress detected. The process 900A may run in parallel to leak detection using pressure sensor data as described in <FIG> and <FIG> below. Either the temperature sensing or pressure sensing can independently result in a leak determination in this embodiment. But, other embodiments score each parallel determination and weigh those scores to produce a combined score that results in a leak determination when the composite score is beyond a composite threshold.

The depicted portion of the process begins in block <NUM> where a rolling window of temperature data is loaded into the analysis engine <NUM>. The window can be <NUM> hours, <NUM> hours, <NUM> hours, <NUM> hours, <NUM> hours, <NUM> hours or more in different embodiments. Where there is a change in ambient temperature that would affect measurement of the water in the plumbing system <NUM>, it is corrected for in block <NUM>. The temperature inside the building <NUM> or outdoors can affect the water temperature in the pipes. A model of those changes is built over time for different temperature trends so that it can be removed from the data in block <NUM>. In this embodiment, a transient peak typically appears near the beginning of a downslope in temperature readings as the water falls to the water supply temperature <NUM> and those transient peaks are detected in block <NUM>. The duration of the downsloping trend is tested in block <NUM>. Where the trend is too small, it is discarded in block <NUM> as the window of analysis moves forward through the temperature data before looping back to block <NUM>. A downtrend less than <NUM>, <NUM>, <NUM><NUM>, or <NUM> minutes is discarded in various embodiments.

Where the downtrend is of the correct duration as determined in block <NUM>, the right portion of the window is analyzed for stability in block <NUM>. Generally, leaks are consistent, stable and occasionally increasing in flow. A determination is made in block <NUM> of whether the right portion of the window is stable and consistent in its downslope. Where determined unstable in block <NUM>, processing loops back to block <NUM>. When the right portion of the window is stable processing continues to block <NUM> where a leak is determined before rolling forward in the data in block <NUM> to look for more leak conditions. This process continues such that small leaks are continuously searched for when there is no intentional egress from the plumbing system <NUM>. Some embodiments rely on temperature sensing to detect leaks, while other embodiments use pressure sensing as explained below, still other embodiments use both temperature and pressure sensing algorithms to detect leaks in parallel.

Referring next to <FIG> and <FIG>, a flow charts of an embodiment of a process 900B, 900C for analyzing pressure sensor <NUM> readings is shown. Two different types of pressure sensor analysis are possible depending on whether the building <NUM> has a PRV or well water. With reference initially to <FIG>, the depicted portion of the process begins in block <NUM> where a rolling window of pressure data is loaded for analysis. This embodiment begins the pressure sensor <NUM> analysis after three hours of the pressure readings that do not register any intentional egress from the plumbing system <NUM>. Other embodiments could have a different period such as <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> hours. Where it is determined in block <NUM> that the water supply type is well water, processing goes to block <NUM> of <FIG>.

Where there is a PRV to buffer spectral components of pressure from the municipal water system <NUM> or well water supply as determined in block <NUM>, processing continues to block <NUM> for an initial calibration presumably where there is no leak condition. Should a leak be determined with the temperature sensing algorithm of <FIG>, the calibration is discarded and performed again where there is no leak. In block <NUM>, the pressure sensor data is converted to the frequency domain. Over the sensor window, the energies are averaged at each frequency in block <NUM> before normalization in block <NUM>. The spectrogram of the plumbing system <NUM> without a leak once determined can be removed from future spectral analysis.

At a time after initial calibration to determine the background spectra, the spectra for the possible leak region is determined in block <NUM> for the pressure sensor <NUM> data in the window. The frequency domain values are normalized in block <NUM>. The background spectra are removed from the possible leak spectra in block <NUM>. The remaining spectral components are analyzed in block <NUM>. The remaining spectral components can be added together to see if it exceeds a predetermined threshold. The leak adds unique spectral components that when present and over a threshold are determined a leak in block <NUM>. Where a leak is not determined, processing loops back to block <NUM> to roll the analysis window forward in time.

Referring next to <FIG>, a flow chart 900C for an embodiment of a leak detection algorithm is shown that is used for buildings <NUM> using well water. Typically, a PRV is not present when on a well, but a pump is used to pull the well water from the ground. A pump in the well pumps water through one or more check valves and into the building <NUM>. When there is no water demand, the check valve(s) is closed to maintain a constant pressure in the plumbing system <NUM>. As egress occurs, pressure in the plumbing system <NUM> decreases until a cracking pressure opens the check valve(s) to supply more water. When the lower limit of the pressure threshold is reached, the pump activates to pressurize the plumbing system <NUM> and supply well water. Where there is intended egress or a leak, the pressure varies in a saw tooth pattern over time. The depicted portion of the process 900C begins in block <NUM> where a two hour window of pressure sensor readings are loaded for analysis. Other embodiments could load windows of different sizes.

The pressure readings are smoothed in block <NUM> before splitting the window into smaller frames of thirty seconds. Other embodiments could use <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> second frames. Each of the frames has its slope determined in block <NUM>. Any frames corresponding to the pump being active are filtered out along with frames without significant enough slope that it could be a leak in block <NUM>. What remains are frames that have a slope that corresponds to a leak condition.

In block <NUM>, the frames that are possible leaks are counted, and that count is compared with a threshold. Where the count is below a threshold, the variance in pressure is attributed to noise and processing loops back to block <NUM> where the window is discarded before fetching another window. Where a significant count exists of frames that have slopes like a leak above a threshold, a leak is determined in block <NUM> before looping back to block <NUM>.

A number of variations and modifications of the disclosed embodiments can also be used. For example, the plumbing analyzer can be used to monitor any liquid distributed in pipes. This could include industrial plants, sprinkler systems, gas distribution systems, refineries, hydrocarbon production equipment, municipal water distribution, etc. The plumbing system is a closed system with pressurized liquid (e.g., a gas) that is released in a selective and controlled manner using valves.

In systems where there is no PRV or a poorly functioning one, leaks can be detected by shutting off the water supply to the plumbing system. The pressure will fall off from the plumbing system as the water leaks from the plumbing system. Shutting off the water supply can be done by the water device in some embodiments. As shut off can be inconvenient to occupants, this test can be done at times where normal egress is unlikely to happen. When normal egress does happen, the water supply can be turned on again to quickly provide for normal egress. In some embodiments, when leaks are detected with the algorithms in <FIG> that conclusion might be confirmed with a pressure test after shut off of the water.

Pressure will change with thermal expansion of the plumbing system <NUM>. With the pipes largely being in the walls of the building <NUM>, they are affected by the interior and exterior temperatures. The interior temperature can be measured at the water device <NUM> or through communication with the HVAC system and the exterior temperature can be determined using the location of the building <NUM> with third party weather information. The effect of thermal expansion as a function of these the delta of these two temperatures can be modeled over time. In some embodiments, the effect of thermal expansion is removed from the pressure sensor readings, for example, homes with functioning PRVs.

Implementation of the techniques, blocks, steps and means described above may be done in various ways. For example, these techniques, blocks, steps and means may be implemented in hardware, software, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a swim diagram, a data flow diagram, a structure diagram, or a block diagram. Although a depiction may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. A process is terminated when its operations are completed, but could have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software, scripting languages, firmware, middleware, microcode, hardware description languages, and/or any combination thereof. When implemented in software, firmware, middleware, scripting language, and/or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as a storage medium. A code segment or machine-executable instruction may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a script, a class, or any combination of instructions, data structures, and/or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, and/or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc..

For a firmware and/or software implementation, the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in a memory. Memory may be implemented within the processor or external to the processor. As used herein the term "memory" refers to any type of long term, short term, volatile, nonvolatile, or other storage medium and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term "storage medium" may represent one or more memories for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information. The term "machine-readable medium" includes, but is not limited to portable or fixed storage devices, optical storage devices, and/or various other storage mediums capable of storing that contain or carry instruction(s) and/or data.

Claim 1:
A method for detecting small leaks of liquid in a plumbing system, the method comprising:
measuring liquid flow within a pipe of the plumbing system with a flow sensor; and
if liquid flow is not detected (<NUM>) by the flow sensor:
measuring (<NUM>) temperature of the liquid over time at a point in the plumbing system upstream from a leak;
processing (<NUM>) the measured temperature over time to determine whether a decay of the measured temperature exceeds a threshold decay of liquid in the plumbing system; and
transmitting (<NUM>) a leak detected signal when the decay of the measured temperature exceeds the threshold decay.