A self-monitoring method for water leakage of a user-side water supply network

By analyzing water consumption changes over a specified time period, combined with user water usage habits and external interference factors, the system automatically monitors water supply pipeline leaks, solving the problem of concealed leaks and reducing water costs and resource waste.

CN115539850BActive Publication Date: 2025-11-18SHENZHEN XINGYUAN INTELLIGENT INSTR TECH
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202211247619.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-10-12
Publication Date
2025-11-18
Estimated Expiration
2042-10-12

AI Technical Summary

Technical Problem

Leaks in residential water supply pipes are often hidden and difficult for users to detect, leading to water waste and increased water costs.

Method used

By defining a specified time period, user water usage data is obtained, and changes in water usage within that time period are used to determine if there is a leak. Combined with external interference factors and user water usage habits, automated leak monitoring is achieved.

Benefits of technology

It enables automated monitoring of water supply pipeline leaks, reducing water waste, lowering water costs, and improving detection efficiency and accuracy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115539850B_ABST
    Figure CN115539850B_ABST
Patent Text Reader

Abstract

The application relates to a water leakage self-monitoring method for a user-side water supply pipe network, which comprises the following steps: demarcating a specified time period; obtaining water consumption data of the user in the specified time period; demarcating a specified range of water consumption fluctuation; analyzing the water consumption data fluctuation in the specified time period; if the water consumption is not zero and the amplitude is in the specified range, the water leakage is determined; otherwise, the water leakage is not determined. The method provided by the application can realize automatic monitoring of the water leakage of the water supply pipeline through monitoring of the water consumption data, does not require the user to actively detect whether water leakage occurs, makes the pipeline leakage problem with concealment more easily exposed, facilitates reminding the user to initiate active inspection and maintenance, helps the user to avoid generating excessive water consumption when water is not needed, thereby reducing water consumption cost, and further saving precious water resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of water supply networks, and in particular to a method for self-monitoring leakage in user-end water supply networks. Background Technology

[0002] Currently, in daily residential water use, leaks in the water supply pipes can cause residents to experience a continuous increase in water consumption even when there is no water usage. This problem not only occurs frequently but is also often insidious, making it difficult for users to detect proactively. This leads to water waste and an unnecessary increase in water consumption.

[0003] If the water supply pipes leak, water consumption will increase at a constant rate per unit time even when users are not actively using water. Meanwhile, for residential water use, there is typically a period during which water consumption is close to zero.

[0004] In response to the above situation, this application proposes a self-monitoring method for water leakage in user-end water supply networks, which is used to detect whether there is a water leakage problem in the user-end water supply pipeline. Summary of the Invention

[0005] In order to detect whether there is a water leakage problem in the water supply pipeline at the user end, this application provides a self-monitoring method for water leakage in the user end water supply network.

[0006] This application provides a method for self-monitoring leakage in a user-end water supply network, which adopts the following technical solution:

[0007] A method for self-monitoring leakage in a user-end water supply network includes the following steps:

[0008] Define a specified time period;

[0009] Retrieve water usage data for a specified time period;

[0010] Determine the leakage situation based on water usage data within a specified time period.

[0011] By adopting the above technical solution, for residential water use, there is usually a period during which each household's water consumption is close to zero. If we can find such a period as the specified timeframe, the probability of users actively using water during this period is very low. Therefore, when using data from this period as the basis for judgment, the impact of users' active water usage on determining whether there is a leak can be ignored.

[0012] Therefore, if water consumption continuously increases during a specified water usage period, it can be determined as a leak. This method can automate the monitoring of water supply pipeline leaks by monitoring water consumption data, eliminating the need for users to actively detect leaks. This makes it easier to expose hidden pipeline leaks and prompts users to initiate proactive inspections and repairs, helping them avoid unnecessary water consumption when not in use, thereby reducing water costs and conserving precious water resources.

[0013] Optionally, the step of determining the leakage situation based on water usage data within a specified time period includes:

[0014] Define a specified range for fluctuations in water consumption;

[0015] Analyze the fluctuations in water usage data within a specified time period. If the water usage is not zero and the amplitude is within a specified range, it is judged as a leak; otherwise, it is judged as no leak.

[0016] By adopting the above technical solution, the specified range should be determined by the range of external interference factors. The above judgment process includes the following situations:

[0017] Due to external interference factors, such as water pressure and external forces, the water consumption within a specified time period may fluctuate slightly around midnight. This is a normal phenomenon and should be judged as no leakage.

[0018] If the water consumption is always zero, it means that there is no water flow near the detection device used to obtain water consumption data under the current circumstances. Assuming that the detection device is not faulty, it is determined that there is no water leakage.

[0019] If the water consumption is not zero, and the specified time period is a time when the user should not use water, and the test shows that the water consumption increases at a constant rate within the specified time period, then it is judged to be a leak.

[0020] If the water consumption is not zero, but the rate of increase in water consumption always fluctuates within a specified range, considering the influence of external factors, the fluctuation can be ignored, and it is judged as a leak.

[0021] If the water consumption is not zero, and its growth rate does not fluctuate within the specified range but fluctuates irregularly, it is judged as normal water consumption by the user. In this case, no judgment should be made, but the water consumption should be retested.

[0022] Optionally, the step of defining the specified time period includes the following steps:

[0023] The data acquisition module acquires users' historical water usage data;

[0024] Define a specified time period based on the user's historical water usage data.

[0025] By adopting the above technical solution, most user households have relatively fixed water usage habits. Therefore, by integrating the user's historical data, it is possible to determine the time periods when the user does not use water or uses very little water. Detecting during these time periods can largely eliminate the interference of the user's active water usage on the leak detection.

[0026] Optionally, the step of defining a specified time period based on the user's historical water usage data includes the following steps:

[0027] Set the duration of a specified time period;

[0028] Define the characteristics for a specified time period;

[0029] Obtain the matching time period, wherein the matching time period conforms to the specified time period characteristics, and the duration of the matching time period is greater than or equal to the duration of the specified time period;

[0030] Select the matching time period as the specified time period.

[0031] By adopting the above technical solution, users may use water infrequently and in small amounts within the specified time period, which is a low-probability event. Therefore, controlling this situation within a certain range will not only not reduce the validity of the conclusions, but will also make it more convenient to obtain the specified time period, avoiding the problem of wasting too much time in the process of obtaining the specified time period and reducing the detection efficiency.

[0032] Optionally, the step of selecting a matching time period as the specified time period includes the following steps:

[0033] Within a marking period, the matching time period is continuously acquired, wherein a marking period includes multiple loop cycles;

[0034] Determine if the matched time period is the same time period in each cycle. If it is, record the matched time period; otherwise, delete the matched time period.

[0035] Within a single testing period, the characteristics of the recorded matching time periods are tested, wherein a single testing period includes multiple labeled periods;

[0036] Determine whether the characteristics of the recorded matching time period meet the characteristics of the specified time period within a test period. If so, the matching time period is defined as the specified time period; otherwise, it cannot be determined as the specified time period.

[0037] By employing the above technical solution, water usage data within a marked period is detected, and matching time periods that meet the above conditions are continuously obtained. That is, if a certain time period meets the above conditions, then the user within that time period is considered to have not actively used water or the frequency and amount of water used will not effectively interfere with the leakage monitoring, and therefore that time period can be marked as a matching time period.

[0038] Subsequently, multiple cycles are formed within a single marking cycle to determine whether the matching time period determined through the above steps appears cyclically or irregularly. If it appears cyclically, it can be determined that the matching time period is formed due to the user's water usage habits and is qualified as a specified time period. Conversely, if the matching time period appears irregularly, it can be considered that the matching time period is not formed due to the user's water usage habits and is not qualified as a specified time period.

[0039] Finally, the matching time periods that qualify as designated time periods, obtained from the above steps, need to be tested over a testing period. If the matching time period meets all the above conditions within a testing period, it can be determined that the matching time period is indeed a time period in which the corresponding user will not actively use water or the number and amount of water used will not effectively interfere with the leakage monitoring. Only in this way can it be designated as a designated time period; otherwise, it cannot be designated as a designated time period.

[0040] Optionally, the step of obtaining water usage data within a specified time period includes the following steps:

[0041] Set the interval time;

[0042] User water usage data is acquired once at the specified interval within a specified time period.

[0043] Optionally, the step of acquiring user water usage data at intervals within a specified time period includes the following steps:

[0044] Record the acquired data;

[0045] Compress the recorded data.

[0046] By employing the above technical solutions, the recorded data consumes system memory, and the larger the total amount of data acquired, the greater the memory usage. However, to improve the accuracy of leak monitoring, more data needs to be acquired, which increases system memory consumption and may cause slowdowns or other negative impacts. Therefore, data compression can save system memory while allowing more data to be recorded, thereby shortening the data acquisition interval and improving the accuracy of data integration results.

[0047] Optionally, in the step of the data acquisition module acquiring the user's historical water usage data, the data acquisition module is used to acquire water meter reading pointer data.

[0048] By adopting the above technical solution, water meters typically use two types of pointers to indicate water consumption: a cloverleaf pointer and a reading pointer. However, using the cloverleaf pointer to obtain water consumption is too sensitive, and the pressure inside the water pipes is often unstable, easily causing the cloverleaf pointer to reverse. Therefore, using the reading pointer provides a more stable and reliable way to obtain accurate data.

[0049] In summary, this application includes at least one of the following beneficial technical effects:

[0050] 1. This method can automatically monitor water supply pipeline leaks by monitoring water consumption data, eliminating the need for users to actively detect leaks. This makes it easier to expose hidden pipeline leaks and prompts users to initiate proactive inspections and repairs. It helps users avoid unnecessary water consumption when water is not needed, thereby reducing water costs and conserving precious water resources.

[0051] 2. By integrating users' historical data, it can identify the time periods during which users do not use water or use very little water. Detecting leaks during these time periods can largely eliminate interference from users' active water usage.

[0052] 3. Users may use water infrequently and in small amounts, which are low-probability events. Therefore, controlling such situations within a certain range will not only not reduce the validity of the conclusions, but will also make it easier to obtain data for the specified time period, avoiding the problem of wasting too much time in the process of obtaining data for the specified time period, which would lead to a decrease in detection efficiency.

[0053] 4. Using data compression methods can save system memory while allowing more data to be recorded, thereby shortening the data acquisition interval and improving the accuracy of data integration results.

[0054] 5. Using a reading pointer to obtain water consumption data can provide more stable and effective data. Attached Figure Description

[0055] Figure 1 This is a flowchart illustrating the overall steps of a self-monitoring method for water leakage in a user-end water supply network, as described in this application embodiment.

[0056] Figure 2 This is a flowchart illustrating the steps of defining a specified time period in a self-monitoring method for water leakage in a user-end water supply network according to an embodiment of this application.

[0057] Figure 3This is a flowchart illustrating the steps of defining a specified time period based on user water usage data in a user-end water supply network self-monitoring method according to an embodiment of this application.

[0058] Figure 4 This is a flowchart illustrating the steps of selecting a matching time period as a specified time period in a user-end water supply network leakage self-monitoring method according to an embodiment of this application.

[0059] Figure 5 This is a flowchart illustrating the steps of obtaining user water usage data within a specified time period in a self-monitoring method for water leakage in a user-end water supply network according to an embodiment of this application.

[0060] Figure 6 This is a flowchart illustrating the steps of a user-end water supply network leakage self-monitoring method according to an embodiment of this application, which involves determining leakage based on water usage data within a specified time period. Detailed Implementation

[0061] The present application will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the application and are not intended to limit the scope of the application.

[0062] In the following description, numerous specific details are set forth for purposes of explanation in order to provide a thorough understanding of the inventive concept. As part of this specification, some of the accompanying drawings of this disclosure are block diagrams illustrating structures and devices to avoid complicating the disclosed principles. For clarity, not all features of the actual embodiment need to be described. Furthermore, the language used in this disclosure has been primarily chosen for readability and instructional purposes and may not have been chosen to define or limit the subject matter of the invention, thus requiring the necessary claims to determine such inventive subject matter. References to “an embodiment” or “an embodiment” in this disclosure mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment, and multiple references to “an embodiment” or “an embodiment” should not be construed as necessarily referring to the same embodiment.

[0063] Unless explicitly defined, the terms “a,” “an,” and “the” are not intended to refer to a singular entity, but rather to include a general category whose specific examples can be used for illustration. Therefore, the use of the terms “a” or “an” can mean any number of at least one, including “a,” “one or more,” “at least one,” and “one or more.” The term “or” means any of the options and any combination of the options, including all options unless explicitly indicated that the options are mutually exclusive. The phrase “at least one of” when combined with a list of items refers to a single item in the list or any combination of items in the list. The phrase does not require all items listed unless explicitly defined as such.

[0064] This application discloses a method for self-monitoring of water leakage in a user-end water supply network. (Refer to...) Figure 1 A method for self-monitoring leakage in a user-end water supply network includes the following steps:

[0065] S1. Define a specified time period.

[0066] For residential water use, there is typically a period during which water consumption is close to zero. If we can identify such a period as the specified timeframe, the probability of users actively using water during this period is very low. Therefore, when using data from this period as the basis for judgment, the impact of users' active water usage on determining whether there is a leak can be ignored.

[0067] Specifically, in different embodiments, the specified time period can be different time periods. Based on the water usage habits of most households, it is known that most households use water significantly less frequently in the early morning hours. Therefore, the user's active water usage during this time period has little impact on the leakage monitoring results and can be used as the specified time period for leakage monitoring.

[0068] Regarding the process of defining the specified time period mentioned above, this application specifically, but not in a limited manner, proposes a method S11-S12 for implementing S1.

[0069] S11. The data acquisition module acquires the user's historical water usage data.

[0070] Most households have relatively fixed water usage habits. Therefore, by integrating users' historical data, we can determine the time periods when users do not use water or use very little water. Detecting leaks during these time periods can largely eliminate the interference of users' active water usage on leak detection.

[0071] Specifically, regarding the data acquisition method, this application provides an example using a pointer water meter in a residential home. The data acquisition module is used to obtain the water meter reading pointer data. Water meters typically use two pointers to indicate water consumption: a cloverleaf pointer and a reading pointer. Using the cloverleaf pointer to obtain water consumption is too sensitive, and the pressure inside the water pipes is often unstable, easily causing the cloverleaf pointer to reverse. Therefore, using the reading pointer provides more stable and reliable data.

[0072] In addition, the data acquisition module can also acquire users' historical water usage data through devices such as ultrasonic sensors.

[0073] S12. Define a specified time period based on the user's historical water usage data.

[0074] Specifically, for the process of defining a specified time period based on users' historical water usage data, this application proposes, but is not limited to, a method S121-S124 for implementing S12.

[0075] S121. Set the duration of a specified time period.

[0076] Specifically, because users' active water usage can affect the determination of a leak, even if the selected time period is a time when users rarely use water, such interference cannot be completely eliminated. Therefore, the duration of this specified time period should be set to a relatively long time that is sufficient to draw a conclusion about a leak. Furthermore, since periods of low water usage are not very long, such as 8 hours of sleep, the duration of the specified time period should not be set too long. For example, the specified time period could be 1 hour or 2 hours.

[0077] S122. Set the characteristics for a specified time period.

[0078] Within the specified time period, users may use water infrequently and in small amounts, which are low-probability events. Therefore, controlling this situation within a certain range will not only not reduce the validity of the conclusions, but will also make obtaining the specified time period more convenient, avoiding the problem of wasting too much time in the process of obtaining the specified time period and reducing detection efficiency.

[0079] Specifically, in different embodiments, the specified time period feature can be set as features with different dimensions and parameters. Among them, different dimensions may include the number of times water is used, the duration of a single water use, the total duration of water use, the amount of water used per use, etc.; different parameters may include the number of times water is used 0-2 times, the duration of a single water use 0-3 minutes, etc.

[0080] As an example, a specified time period can be characterized as follows: water usage frequency within the range of 0-2 times, water usage duration within the range of 0-3 minutes, and total water consumption not exceeding 12 liters. It is important to note that these values ​​should be set according to the specific circumstances of each household; for example, the total water consumption and frequency should differ depending on the number of people.

[0081] S123. Obtain the matching time period, wherein the matching time period conforms to the specified time period characteristics, and the duration of the matching time period is greater than or equal to the duration of the specified time period.

[0082] S124. Select the matching time period as the specified time period.

[0083] Specifically, for the process of selecting the matching time period, this application proposes a method S1241-S1244 for implementing S124.

[0084] S1241. The matching time period is continuously acquired within a marking period, wherein a marking period includes multiple cycle periods.

[0085] Water usage data within a marked period is monitored, and matching time periods that meet the above conditions are continuously obtained. That is, if a certain time period meets the above conditions, then the users within that time period are considered to have not actively used water or the frequency and amount of water used will not effectively interfere with the leakage monitoring, and therefore that time period can be marked as a matching time period.

[0086] Specifically, in different embodiments, the marking period can be determined to be of different lengths, and can be differentiated for different user family situations in order to obtain accurate user profiles. This application specifically, but not in a limited way, proposes a marking period of a length suitable for most users: a marking period of one week, which includes weekdays and rest days, conforming to the lifestyle of most users. In addition, a marking period can also be two weeks.

[0087] Similarly, in different embodiments, a cycle period can also have different lengths. This application proposes a cycle period length as an example, applicable to the case where a marking cycle is one week: a cycle period is one day. In addition, a cycle period can also be two days.

[0088] S1242. Determine whether the matching time period is the same time period in each cycle. If so, record the matching time period; otherwise, delete the matching time period.

[0089] Multiple cycles are formed within a single marking cycle to determine whether the matching time period determined through the above steps appears cyclically or irregularly. If it appears cyclically, it can be determined that the matching time period is formed due to the user's water usage habits and is qualified as a specified time period. Conversely, if the matching time period appears irregularly, it can be considered that the matching time period is not formed due to the user's water usage habits and is not qualified as a specified time period.

[0090] S1243. Within a test period, test the characteristics of the recorded matching time periods, wherein a test period includes multiple marker periods.

[0091] Specifically, in different embodiments, the inspection period can be set to different lengths. For example, an inspection period can be 15 days or 30 days.

[0092] S1244. Determine whether the characteristics of the recorded matching time period meet the characteristics of the specified time period within a test period. If so, then define the matching time period as the specified time period; otherwise, it cannot be determined as the specified time period.

[0093] The matching time period obtained from the above steps that qualifies as a designated time period needs to be tested for a test cycle. If the matching time period meets the above conditions within a test cycle, it can be determined that the matching time period is indeed a time period in which the corresponding user will not actively use water or the number and amount of water used will not effectively interfere with the leakage monitoring. Only in this way can it be designated as a designated time period. Otherwise, it cannot be designated as a designated time period.

[0094] S2. Obtain water usage data for a specified time period.

[0095] Specifically, similar to the method for obtaining historical user data described above, this application provides an example of a residential water meter using pointer sensors. The data acquisition module is used to obtain the water meter reading pointer data. Water meters typically use two pointers to indicate water consumption: a cloverleaf pointer and a reading pointer. If the cloverleaf pointer is used to obtain water consumption, it is too sensitive, and the pressure inside the water pipes is often unstable, which can easily cause the cloverleaf pointer to reverse. Therefore, using the reading pointer can obtain more stable and valid data.

[0096] In addition, the data acquisition module can also acquire users' historical water usage data through devices such as ultrasonic sensors.

[0097] More specifically, for the process of obtaining water usage data within a specified time period, this application specifically, but not limitedly, proposes a method S21-S22 for implementing S2.

[0098] S21. Set the interval time;

[0099] S22. Within a specified time period, acquire user water usage data once at the specified interval.

[0100] Specifically, in order to optimize the data acquisition process and improve the accuracy of subsequent data integration results, this application specifically, but not in a limited way, provides a method S221-S222 to implement S22.

[0101] S221. Record the acquired data;

[0102] S222. Compress the recorded data.

[0103] Recording and acquiring data consumes system memory, and the larger the total amount of data acquired, the greater the memory usage. However, to improve the accuracy of leak monitoring, more data needs to be acquired, which increases system memory consumption and may cause slowdowns or other negative effects. Therefore, data compression can save system memory while allowing more data to be recorded, thereby shortening the data acquisition interval and improving the accuracy of the data integration results.

[0104] S3. Determine the leakage situation based on water usage data within a specified time period.

[0105] This method can automatically monitor water supply pipeline leaks by monitoring water consumption data, eliminating the need for users to actively detect leaks. This makes it easier to expose hidden pipeline leaks and prompts users to initiate proactive inspections and repairs. It helps users avoid unnecessary water consumption when water is not needed, thereby reducing water costs and conserving precious water resources.

[0106] Specifically, this application proposes a data analysis and integration method S31-S32 for the process of judging water leakage based on water usage data within a specified time period.

[0107] S31. Define the specified range for fluctuations in water consumption;

[0108] S32. Determine the fluctuation of water usage data within a specified time period. If the water usage is not zero and the amplitude is within the specified range, it is determined to be a leak; otherwise, it is determined to be no leak.

[0109] Specifically, the aforementioned specified range should be determined by measuring the range of external interference factors. The judgment process includes the following situations:

[0110] Due to external interference factors, such as water pressure and external forces, the water consumption within a specified time period may fluctuate slightly around midnight. This is a normal phenomenon and should be judged as no leakage.

[0111] If the water consumption is always zero, it means that there is no water flow near the detection device used to obtain water consumption data under the current circumstances. Assuming that the detection device is not faulty, it is determined that there is no water leakage.

[0112] If the water consumption is not zero, and the specified time period is a time when the user should not use water, and the test shows that the water consumption increases at a constant rate within the specified time period, then it is judged to be a leak.

[0113] If the water consumption is not zero, but the rate of increase in water consumption always fluctuates within a specified range, considering the influence of external factors, the fluctuation can be ignored, and it is judged as a leak.

[0114] If the water consumption is not zero, and its growth rate does not fluctuate within the specified range but fluctuates irregularly, it is judged as normal water consumption by the user. In this case, no judgment should be made, but the water consumption should be retested.

[0115] In summary, this application provides an example of monitoring pipe leaks at the user end, as follows:

[0116] Set the duration of the specified time period to 1 hour;

[0117] The specified time period is characterized by water usage frequency of 0-2 times, water usage duration of 0-3 minutes, and total water consumption not exceeding 12 liters.

[0118] The detection equipment was used to detect changes in the water meter reading at the pointer.

[0119] Set a marking period of one week, and continuously record the time periods that meet the above-specified time period conditions within one week to determine that the time period is from 2 a.m. to 3 a.m.

[0120] Set a cycle of one day, and within a week, determine whether the matching time period obtained in the previous sequence is the same time period in each day, that is, whether the time period from 2 am to 3 am in each day meets the above-mentioned specified time period conditions.

[0121] Set a testing period of one month, and determine whether the conclusion that 2:00 AM to 3:00 AM is the matching time period is reached every week of the month. If the result is yes, then 2:00 AM to 3:00 AM can be defined as the specified time period.

[0122] The interval is set to 1 minute. Between 2 a.m. and 3 a.m., user water usage data is collected every minute and the data is compressed.

[0123] The specified range for water consumption fluctuation is defined as 6 liters. The fluctuation of water consumption data between 2:00 AM and 3:00 AM is judged. If the judgment result is that the water consumption is not zero and the water consumption amplitude is within 6 liters, then it is judged as a leak.

[0124] The above are all preferred embodiments of this application, and are not intended to limit the scope of protection of this application. Therefore, all equivalent changes made in accordance with the structure, shape and principle of this application should be covered within the scope of protection of this application.

Claims

1. A method for self-monitoring leakage in a user-end water supply network, characterized in that, Includes the following steps: Define a specified time period; The step of defining a specified time period includes the following steps: The data acquisition module acquires users' historical water usage data; Define a specified time period based on the user's historical water usage data; The step of defining a specified time period based on users' historical water usage data includes the following steps: Set the duration of a specified time period; Define the characteristics for a specified time period; Obtain the matching time period, wherein the matching time period conforms to the specified time period characteristics, and the duration of the matching time period is greater than or equal to the duration of the specified time period; Select the matching time period as the specified time period; The step of selecting a matching time period as the specified time period includes the following steps: Within a marking period, the matching time period is continuously acquired, wherein a marking period includes multiple loop cycles; Determine if the matched time period is the same time period in each cycle. If it is, record the matched time period; otherwise, delete the matched time period. Within a single testing period, the characteristics of the recorded matching time periods are tested, wherein a single testing period includes multiple labeled periods; Determine whether the characteristics of the recorded matching time period meet the characteristics of the specified time period within a test period. If so, the matching time period is defined as the specified time period; otherwise, it cannot be determined as the specified time period. Retrieve water usage data for a specified time period; The step of obtaining water usage data within a specified time period includes the following steps: Set the interval time; Within a specified time period, user water usage data is acquired once at the specified interval. Determine the leakage situation based on water usage data within a specified time period; The steps for determining leakage based on water usage data within a specified time period include: Define a specified range for fluctuations in water consumption; Analyze the fluctuations in water usage data within a specified time period. If the water usage is not zero and the amplitude is within a specified range, it is judged as a leak; otherwise, it is judged as no leak. If the water consumption is always zero, it means that there is no water flow near the detection device used to obtain water consumption data under the current circumstances. Assuming that the detection device is not faulty, it is determined that there is no water leakage. If the water consumption is not zero, and the specified time period is a time when the user should not use water, and the test shows that the water consumption increases at a constant rate within the specified time period, then it is judged to be a leak. If the water consumption is not zero, but the rate of increase in water consumption always fluctuates within a specified range, considering the influence of external factors, the fluctuation can be ignored, and it is judged as a leak. If the water consumption is not zero, and its growth rate does not fluctuate within the specified range but fluctuates irregularly, it is judged as normal water consumption by the user. In this case, no judgment should be made, but the water consumption should be retested.

2. The self-monitoring method for leakage in user-end water supply networks according to claim 1, characterized in that, The step of acquiring user water usage data at regular intervals within a specified time period includes the following steps: Record the acquired data; Compress the recorded data.

3. The self-monitoring method for leakage in user-end water supply networks according to claim 1, characterized in that, In the step of the data acquisition module acquiring historical water usage data of the user, the data acquisition module is used to acquire water meter reading pointer data.

Citation Information

Patent Citations

  • Water leakage monitoring method based on composite Internet of Things and Internet of Things system

    CN107835221A

  • Apartment water meter acquisition method and system

    CN115623360A

  • Water leakage detection method for pipe

    CN1808088A

  • Smart metering-based indoor water leakage detection system

    KR102193382B1