Pipe network pressure monitoring method, device, equipment and storage medium

Abstract

The application belongs to the technical field of gas pipe network detection, and discloses a pipe network pressure monitoring method, device, equipment and storage medium. The method comprises the following steps: arranging a pressure monitoring device in a to-be-monitored area, wherein the pressure monitoring device is used for pressure monitoring as a monitoring point; dividing the to-be-monitored area into target areas; dividing the target areas into time periods according to the number of monitoring points in the target areas; monitoring the pipe network pressure based on the divided time periods; and visually displaying the monitored pressure data. Through the above method, each node of the pipe network can be more effectively monitored, the equipment coverage is wider, and the pressure distribution of the pipe network can be better mastered by using the partition and time division methods, and the latest data can be ensured to be continuously obtained for viewing.

Description

Technical Field

[0001] This invention relates to the field of gas pipeline network detection technology, and in particular to a pipeline network pressure monitoring method, device, equipment, and storage medium. Background Technology

[0002] The main purposes of pipeline pressure monitoring are threefold: (1) to monitor and record the overall pressure distribution of medium-pressure pipelines to assist in pipeline planning and scheduling; (2) to monitor and warn of abnormal operating conditions in regional pipelines and at important customers; and (3) to be integrated with other business systems such as equipment management, pipeline simulation, and data analysis. Therefore, it can be seen that pressure monitoring requires both timely data transmission and sufficient coverage. If the coverage area is small, some local pipelines experiencing low pressure may not be effectively monitored.

[0003] Based on the above description, traditional pressure monitoring has the following drawbacks: (1) The transmission frequency of devices that can be installed in large quantities is low, and data cannot be transmitted back in a timely manner. (2) The transmission frequency of devices installed in small quantities is high, but due to installation limitations such as cost and location, the number of installation points is small and the coverage area is small. (3) The functions of the device cannot be effectively iterated and updated.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a method, device, equipment, and storage medium for monitoring pipeline pressure, aiming to solve the technical problems of not being able to transmit data more promptly, having a small number of installation points resulting in a small coverage area, and not being able to effectively update the functions of the equipment.

[0006] To achieve the above objectives, the present invention provides a pipeline pressure monitoring method, which includes the following steps:

[0007] Pressure monitoring equipment is deployed in the area to be monitored, and the pressure monitoring equipment is used as a monitoring point for pressure monitoring.

[0008] The area to be monitored is divided into regions to obtain the target area;

[0009] The target area is divided into time periods based on the number of monitoring points within the target area;

[0010] Pipeline pressure monitoring is conducted based on the defined time periods;

[0011] The monitored pressure data is visualized.

[0012] In some embodiments, dividing the area to be monitored into target areas includes:

[0013] With the main pipe as the center, an expansion space is obtained by extending a preset distance to both sides. The main pipe is determined by expert evaluation or a pipe with a diameter larger than a fixed diameter is used as the main pipe. The expansion space includes all monitoring points.

[0014] The target area is obtained by finding the intersection of the extended space and the area to be monitored. The area to be monitored is divided into independent areas by combining the emergency rescue team area or administrative area with the geographic space.

[0015] In some embodiments, the pipeline pressure monitoring method further includes:

[0016] If the number of monitoring points is lower than the preset number, a corresponding reminder will be output to increase the number of monitoring points.

[0017] In some embodiments, the pipeline pressure monitoring based on the divided time periods includes:

[0018] The time point for uploading pressure data for each monitoring point is determined based on the divided time period and the number of monitoring points.

[0019] Receive and record the pressure data uploaded by each monitoring point according to its corresponding upload time and set transmission frequency.

[0020] In some embodiments, the pipeline pressure monitoring method further includes:

[0021] Upon receiving abnormal pressure data, the abnormal pressure value is extracted from the abnormal pressure data;

[0022] The abnormal pressure value is compared with several preset pressure threshold ranges;

[0023] The set transmission frequency is adjusted based on the comparison results.

[0024] In some embodiments, the pipeline pressure monitoring method further includes:

[0025] The new pressure data uploaded by each monitoring point is verified against the historical pressure data.

[0026] Based on the verification results, abnormal pressure changes in the pipeline network are detected, and the consistency of the pressure change curves at any monitoring point with the pressure change curves at other monitoring points is verified.

[0027] In some embodiments, visualizing the monitored pressure data includes:

[0028] The monitoring points corresponding to the pressure data are displayed on a map according to their geographical coordinates. The pressure data is displayed in a color gradient according to the pressure value. The monitoring points at different times are displayed through a time axis. Abnormal data is displayed in a special style to provide safety risk warnings.

[0029] Furthermore, to achieve the above objectives, the present invention also proposes a pipeline pressure monitoring device, the pipeline pressure monitoring device comprising:

[0030] A deployment module is used to deploy pressure monitoring equipment in the area to be monitored, wherein the pressure monitoring equipment is used as a monitoring point for pressure monitoring;

[0031] The partitioning module is used to divide the area to be monitored into regions to obtain target areas;

[0032] The time-sharing module is used to divide the target area into time periods based on the number of monitoring points within the target area.

[0033] The monitoring module is used to monitor pipeline pressure based on the defined time periods.

[0034] The display module is used to visualize the monitored pressure data.

[0035] In addition, to achieve the above objectives, the present invention also proposes a pipeline pressure monitoring device, which includes: a memory, a processor, and a pipeline pressure monitoring program stored in the memory and executable on the processor, wherein the pipeline pressure monitoring program is configured to implement the steps of the pipeline pressure monitoring method described above.

[0036] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing a pipeline pressure monitoring program, which, when executed by a processor, implements the steps of the pipeline pressure monitoring method described above.

[0037] This invention involves deploying pressure monitoring devices in the monitored area, which serve as monitoring points for pressure monitoring; dividing the monitored area into target zones; dividing the target zones into time periods based on the number of monitoring points within each target zone; monitoring pipeline pressure based on the divided time periods; and visualizing the monitored pressure data. This method enables more effective monitoring of various nodes in the pipeline network, provides wider equipment coverage, and utilizes zoned and time-based approaches to better understand the pressure distribution of the pipeline network and ensure a continuous flow of up-to-date data. Attached Figure Description

[0038] Figure 1This is a flowchart illustrating the first embodiment of the pipeline pressure monitoring method of the present invention;

[0039] Figure 2 This is a schematic diagram of simulated data transmission in the pipeline pressure monitoring method of the present invention;

[0040] Figure 3 This is a structural block diagram of the first embodiment of the pipeline pressure monitoring device of the present invention.

[0041] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0042] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0043] This invention provides a method for monitoring pipeline pressure, referring to... Figure 1 , Figure 1 This is a schematic flowchart of the first embodiment of a pipeline pressure monitoring method according to the present invention.

[0044] In this embodiment, the pipeline pressure monitoring method includes the following steps:

[0045] Step S10: Deploy pressure monitoring equipment in the area to be monitored. The pressure monitoring equipment is used as a monitoring point for pressure monitoring.

[0046] In this embodiment, the executing entity is a pipeline pressure monitoring device, which has functions such as data processing, data communication, and program execution. The pipeline pressure monitoring device can be a computer terminal device or other network device, or other devices with similar functions. This embodiment does not limit the scope of the embodiments.

[0047] It's important to note that traditional pressure monitoring systems suffer from several drawbacks. For example, devices installed in large numbers may have low transmission frequencies, hindering timely data transmission. While devices installed in small numbers may have high transmission frequencies, cost and location limitations restrict the number of installation points and the coverage area. Furthermore, the functionality of the devices cannot be effectively iterated and updated. Typical equipment has a lifespan of 5 to 10 years or more, meaning it won't be replaced every year or two, even if increased functionality is required. Adding more functionality to the device itself presents challenges for software updates during operation. Therefore, stability is paramount for the equipment; the more stable the device, the more efficient it will be. Simplicity in the device also allows for faster development (e.g., if ten functions need to be developed, with potential conflicts between different states or operations, development requires more consideration) and more stable operation (e.g., conflicts between different logics on the device, or multiple interruptions corresponding to different states, ultimately affecting device operation).

[0048] To address the aforementioned technical issues, this embodiment deploys pressure monitoring devices in the area to be monitored, which serve as monitoring points for pressure monitoring. The area to be monitored is divided into target zones. The target zones are then divided into time periods based on the number of monitoring points within each zone. Pipeline pressure monitoring is performed based on these time periods. The monitored pressure data is then visualized. This approach enables more effective monitoring of various nodes in the pipeline network, providing wider device coverage. Furthermore, the use of zone and time-based methods allows for a better understanding of the pipeline's pressure distribution and ensures a continuous flow of up-to-date data. In this embodiment, some functions are placed on the server side, simplifying the device side. A key advantage of the server side is its high efficiency in updating, iterating, and developing, allowing for continuous testing and improvement to adapt to new management needs.

[0049] In this specific implementation, a large number of pressure devices need to be installed at the pipeline nodes. Each pressure device corresponds to a monitoring node for the collection of pressure data and subsequent uploading of pressure data.

[0050] Step S20: Divide the area to be monitored into regions to obtain the target area.

[0051] This embodiment adopts a zoned approach to monitor pipeline pressure. Specifically, the main pipeline is used as the center, and a predetermined distance is extended to both sides to obtain an extended space. The intersection of this extended space and the area to be monitored yields the target area. The area to be monitored is determined by combining the emergency response team area or administrative area with independent geographical areas. The main pipeline is determined by expert evaluation or by using a pipe with a diameter larger than a fixed diameter. The extended space includes all monitoring points. It should be noted that large areas are divided by combining emergency response team areas (or administrative areas such as streets) with independent geographical areas. Using emergency response teams (or administrative areas such as streets) is based on management needs; emergency response teams are the basic unit for pipeline emergency response; administrative areas are the basic unit for government management; both are management approaches. Combining geographical areas takes into account that some independent areas need special attention, such as islands, and smaller areas can also be divided by the main pipeline. If a long ring pipeline is encountered in actual practice, it can be further divided into segments.

[0052] Step S30: Divide the target area into time periods based on the number of monitoring points within the target area.

[0053] Step S40: Monitor pipeline pressure based on the divided time periods.

[0054] The target area is divided into multiple sub-areas. For each sub-area, this embodiment can count the number of monitoring points within that sub-area and then allocate time slots based on that number. For example, the number of pressure points in each area can be counted, and then time periods can be divided within that area. If there are fewer points, the time period will be longer; if there are more points, the time period will be shorter. Priority is given to key times such as 4:00, 8:00, 19:00, 20:00, and 22:00 as data transmission times. 18:00-22:00 is traditionally considered a peak usage time and requires close monitoring; around 4:00 is traditionally considered a low usage time and also requires close monitoring. For example, if there are 12 points in the area, assuming each point uploads data twice a day, the data upload times for monitoring points in the area can be set to 1, 2, 3...11, 12, transmitting one data point per hour. For example, if there are 24 monitoring points in the area, and each point uploads data twice a day, then the data upload times for the monitoring points in the area can be set to 00:30, 01:00, 01:30...11:30, 12:00, etc. By setting it up this way, data is uploaded at each fixed time period, allowing you to view the pressure data for the area.

[0055] After dividing the time period, the number of monitoring points is determined, and the time points for uploading pressure data for each monitoring point are identified. The system receives and records the pressure data uploaded by each monitoring point according to its corresponding time point and the set transmission frequency. For example, the data upload time points for monitoring points are 1, 2, 3...11, 12. Then, one data point is transmitted every hour according to this time point. In this embodiment, each point uploads data twice a day. The number of data uploads and the transmission cycle are only illustrative examples and are not limited in this embodiment. There are 12 measurement points in the same area, and each point uploads data twice a day. It is assumed that each upload contains 12 data points (i.e., one data point is recorded per hour). Normally, measurement recordings are more frequent, with one data point recorded approximately every 5-15 minutes. However, for simplicity, a smaller data value is assumed here, for example... Figure 2 As shown, Figure 2 The shaded area represents the most recent uploaded data for each point.

[0056] In some embodiments, if the number of monitoring points is less than a preset number, a corresponding reminder is output to increase the number of monitoring points. For example, if the number of monitoring points is less than 12, a reminder to add monitoring points is output. Through this method, for a specific management area, the latest uploaded pressure value can be seen every hour. This pressure value can represent the approximate pressure situation in that area, thus providing pseudo-real-time data. Simultaneously, as time progresses, the pressure values ​​of all points in the area at a specific point in the past will gradually be improved and mutually verified. The more pressure monitoring points in an area, the stronger the real-time monitoring capability.

[0057] In some embodiments, during normal transmission, the monitoring point uploads pressure data at a normal transmission frequency, i.e., the set frequency in this embodiment. This set frequency can be set according to actual monitoring needs. For abnormal data, this embodiment extracts abnormal pressure values ​​from the abnormal pressure data; compares the abnormal pressure values ​​with several preset pressure threshold ranges; and adjusts the set transmission frequency based on the comparison results. For example, assuming the pressure threshold ranges are 100–400 and 200–300, when the abnormal pressure value is 150, it is seen that 150 is within the pressure threshold range of 100–400, but exceeds the pressure threshold range of 200–300. In this case, the transmission frequency is set to once every 10 minutes. Similarly, assuming the abnormal pressure value is 80, it is seen that 80 exceeds both the pressure threshold range of 200–300 and 100–400. In this case, the transmission frequency is set to once every 2 minutes. It should also be noted that the transmission frequency is adjusted dynamically in real time. Taking the above example, when the abnormal pressure value rises from 80 to 110, and 110 is within the pressure threshold range of 100 to 400, the transmission frequency will be adjusted from once every 2 minutes to once every 10 minutes.

[0058] It should be noted that the threshold has an upper and lower limit (in some cases, an upper upper limit and a lower lower limit are also set). Exceeding the upper and lower limits are abnormal pressure data (because it is desirable to keep the pressure of the pipeline network stable, and high pressure and low pressure are both abnormal states). Secondly, the purpose of setting the transmission frequency is to increase the data transmission frequency when abnormal data occurs, so as to observe the latest dynamic changes in pressure. The greater the deviation from the pressure threshold, the higher the observation frequency. This embodiment further illustrates the concept using low pressure as an example. Assume the lower pressure limit is 200 and the lower-lower limit is 100. Normally, the sensor transmits data once a day. When the pressure data is below 200, it exceeds the threshold range, so data is transmitted immediately. During this transmission, the data transmission frequency of the pressure sensor is adjusted, for example, to once every 15 minutes (considering the pressure is still relatively high, but it's included in the observation scope, so the frequency can be lower). After a period of time, the pressure returned by the sensor is even lower, below 100. During this transmission, the data transmission frequency of the pressure sensor is further adjusted, for example, to once per minute. At this point, the pressure is indeed very low, and it's necessary to monitor pressure changes closely to take appropriate measures. Generally, setting two threshold ranges is sufficient. If there is a genuine need, more threshold ranges can be considered, and so on.

[0059] Furthermore, this embodiment can also verify the received pressure data. Specifically, it verifies the new pressure data uploaded by each monitoring point against historical pressure data; based on the verification results, it detects abnormal pressure changes in the pipeline network and verifies the consistency of the pressure change curve of any monitoring point with the pressure change curve of other monitoring points. Verification can be divided into two aspects: Verification of the monitoring point's own historical data: Pipeline pressure changes have their own regularity; time series analysis can detect whether there are any abnormal changes. Verification of data comparison between monitoring points within the same area: Whether the pressure change curve of this point is consistent with the pressure change curve of other points within the same time period. Whether the value of this point at a certain past moment is consistent with the value of other points at that same moment. And so on... Figure 2 Examples of data verification: Verification of historical data from monitoring points themselves: Point 1 received 12 data points at 13:00. Analysis of the data from 2:00 to 13:00 was performed to check for any abnormal abrupt changes; none were found, and the trend was an increasing pattern. Verification of data comparison between monitoring points within the same area: Point 1 received 12 data points at 13:00. Analysis was performed to check if the data at 2:00 was consistent with the data at other points at 2:00; analysis was also performed to check if the data at 3:00 was consistent with the data at other points at 3:00. This process continued until 9:00, as the data volume at 10:00 and later was too small for verification. Data after 10:00 could be verified after the data from Point 2 arrived at 14:00, and so on. It should be noted that the above data verification ensured the accuracy of the data and the reliability of the equipment.

[0060] Step S50: Visualize the monitored pressure data.

[0061] Upon detecting pressure data, this embodiment further visualizes the data. Specifically, the monitoring points corresponding to the pressure data are displayed on a map according to their geographical coordinates. A color gradient is used to display the pressure values, and a timeline is provided to show monitoring points at different times. Abnormal data is displayed in a special style to indicate safety risks. For example, the collection points are displayed on a map according to their geographical coordinates, and a color gradient is used to display the pressure values ​​at each point. A timeline is provided to select pressure points at different times for display. Abnormal data is displayed in a special style, such as flashing red, to indicate safety risks.

[0062] This embodiment deploys pressure monitoring equipment in the area to be monitored, which serves as monitoring points for pressure monitoring. The area to be monitored is divided into target zones. The target zones are then divided into time periods based on the number of monitoring points within each target zone. Pipeline pressure monitoring is performed based on these time periods. The monitored pressure data is then visualized. This method enables more effective monitoring of various nodes in the pipeline network, provides wider equipment coverage, and utilizes a zoned and time-based approach to better understand the pressure distribution of the pipeline network and ensure a continuous flow of up-to-date data.

[0063] Furthermore, this embodiment of the invention also proposes a storage medium storing a pipeline pressure monitoring program, which, when executed by a processor, implements the steps of the pipeline pressure monitoring method described above.

[0064] Reference Figure 3 , Figure 3 This is a structural block diagram of the first embodiment of the pipeline pressure monitoring device of the present invention.

[0065] like Figure 3 As shown, the pipeline pressure monitoring device proposed in this embodiment of the invention includes:

[0066] The deployment module 10 is used to deploy pressure monitoring equipment in the area to be monitored, and the pressure monitoring equipment is used as a monitoring point for pressure monitoring.

[0067] The partitioning module 20 is used to divide the area to be monitored into regions to obtain the target area.

[0068] The time-sharing module 30 is used to divide the target area into time periods based on the number of monitoring points in the target area.

[0069] Monitoring module 40 is used to monitor pipeline pressure based on the divided time periods.

[0070] Display module 50 is used to visualize the monitored pressure data.

[0071] This embodiment deploys pressure monitoring equipment in the area to be monitored, which serves as monitoring points for pressure monitoring. The area to be monitored is divided into target zones. The target zones are then divided into time periods based on the number of monitoring points within each target zone. Pipeline pressure monitoring is performed based on these time periods. The monitored pressure data is then visualized. This method enables more effective monitoring of various nodes in the pipeline network, provides wider equipment coverage, and utilizes a zoned and time-based approach to better understand the pressure distribution of the pipeline network and ensure a continuous flow of up-to-date data.

[0072] In some embodiments, the partitioning module 20 is used to extend a preset distance to both sides of the main pipe as the center to obtain an extended space. The main pipe is determined by expert evaluation or a pipe with a diameter larger than a fixed diameter is used as the main pipe. The extended space includes all monitoring points. The intersection of the extended space and the area to be monitored is used to obtain a target area. The area to be monitored is obtained by dividing the area into independent areas based on the emergency rescue team area or administrative area combined with geographical space.

[0073] In some embodiments, the pipeline pressure monitoring method further includes: if the number of monitoring points is lower than a preset number, outputting a corresponding reminder to increase the number of monitoring points.

[0074] In some embodiments, the time-sharing module 30 is used to determine the time point for uploading pressure data corresponding to each monitoring point based on the divided time period and the number of monitoring points; and to receive and record the pressure data uploaded by each monitoring point according to its corresponding time point for uploading pressure data and the set transmission frequency.

[0075] In some embodiments, the monitoring module 40 is configured to extract an abnormal pressure value from the abnormal pressure data when receiving abnormal pressure data; compare the abnormal pressure value with several preset pressure threshold ranges; and adjust the set transmission frequency based on the comparison results.

[0076] In some embodiments, the monitoring module 40 is used to verify the new pressure data uploaded by each monitoring point with the historical pressure data; to detect abnormal changes in pipeline pressure based on the verification results; and to verify the consistency of the pressure change curve of any monitoring point with the pressure change curve of other monitoring points.

[0077] In some embodiments, the display module 50 is used to display the monitoring points corresponding to the pressure data on a map according to geographical coordinates, and to display the pressure data in a color gradient according to the pressure value, and to display the monitoring points at different times through a time axis, and to display abnormal data in a special style to provide a safety risk warning.

[0078] This application embodiment also provides a pipeline pressure monitoring device, including a processor, a communication interface, a memory, and a communication bus. The processor, communication interface, and memory communicate with each other through the communication bus. The memory is used to store computer programs. When the processor executes the program stored in the memory, it implements the above-mentioned pipeline pressure monitoring method.

[0079] The communication bus mentioned in the aforementioned pipeline pressure monitoring equipment can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc.

[0080] The communication interface is used for communication between the aforementioned pipeline pressure monitoring equipment and other equipment.

[0081] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0082] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0083] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0084] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0085] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0086] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

[0087] It should be understood that the above are merely illustrative examples and do not constitute any limitation on the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any restrictions on this.

[0088] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.

[0089] In addition, for technical details not described in detail in this embodiment, please refer to the pipeline pressure monitoring method provided in any embodiment of the present invention, which will not be repeated here.

[0090] Furthermore, it should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0091] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0092] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0093] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

[0094] It is understood that the system provided in the embodiments of the present invention corresponds to the method provided in the embodiments of the present invention, and the explanation, examples and beneficial effects of the relevant content can be referred to the corresponding parts of the above methods.

Claims

1. A method for monitoring pipeline pressure, characterized in that, The pipeline pressure monitoring method includes: Pressure monitoring equipment is deployed in the area to be monitored, and the pressure monitoring equipment is used as a monitoring point for pressure monitoring. The area to be monitored is divided into regions to obtain the target area; The target area is divided into time periods based on the number of monitoring points within the target area; Pipeline pressure monitoring is conducted based on the defined time periods; Visualize the monitored pressure data; The step of dividing the area to be monitored into target areas includes: With the main pipe as the center, an expansion space is obtained by extending a preset distance to both sides. The main pipe is determined by expert evaluation or a pipe with a diameter larger than a fixed diameter is used as the main pipe. The expansion space includes all monitoring points. The target area is obtained by finding the intersection of the extended space and the area to be monitored. The area to be monitored is divided into independent areas by combining the emergency rescue team area or administrative area with the geographic space. The pipeline pressure monitoring based on the defined time periods includes: The time point for uploading pressure data for each monitoring point is determined based on the divided time period and the number of monitoring points. Receive and record the pressure data uploaded by each monitoring point according to its corresponding upload time and the set transmission frequency; The pipeline pressure monitoring method also includes: Upon receiving abnormal pressure data, the abnormal pressure value is extracted from the abnormal pressure data; The abnormal pressure value is compared with several preset pressure threshold ranges; The transmission frequency is adjusted based on the comparison results; The pipeline pressure monitoring method also includes: The new pressure data uploaded by each monitoring point is verified against the historical pressure data. Based on the verification results, abnormal pressure changes in the pipeline network are detected, and the consistency of the pressure change curves at any monitoring point with the pressure change curves at other monitoring points is verified.

2. The pipeline pressure monitoring method as described in claim 1, characterized in that, The pipeline pressure monitoring method also includes: If the number of monitoring points is lower than the preset number, a corresponding reminder will be output to increase the number of monitoring points.

3. The pipeline pressure monitoring method as described in claim 1, characterized in that, The visualization of the monitored pressure data includes: The monitoring points corresponding to the pressure data are displayed on a map according to their geographical coordinates. The pressure data is displayed in a color gradient according to the pressure value. The monitoring points at different times are displayed through a time axis. Abnormal data is displayed in a special style to provide safety risk warnings.

4. A pipeline pressure monitoring device, characterized in that, The pipeline pressure monitoring device is applied to the pipeline pressure monitoring method as described in any one of claims 1 to 3, and the device comprises: A deployment module is used to deploy pressure monitoring equipment in the area to be monitored, wherein the pressure monitoring equipment is used as a monitoring point for pressure monitoring; The partitioning module is used to divide the area to be monitored into regions to obtain target areas; The time-sharing module is used to divide the target area into time periods based on the number of monitoring points within the target area. The monitoring module is used to monitor pipeline pressure based on the defined time periods. The display module is used to visualize the monitored pressure data.

5. A pipeline pressure monitoring device, characterized in that, The pipeline pressure monitoring device includes: a memory, a processor, and a pipeline pressure monitoring program stored in the memory and executable on the processor, the pipeline pressure monitoring program being configured to implement the pipeline pressure monitoring method as described in any one of claims 1 to 3.

6. A storage medium, characterized in that, The storage medium stores a pipeline pressure monitoring program, which, when executed by a processor, implements the pipeline pressure monitoring method as described in any one of claims 1 to 3.

Images