Safety monitoring method for flood drainage and control project of reservoir

By monitoring and analyzing the operating status of the GNSS receiver in real time, prioritizing the processing of urgent data and compressing non-urgent data, the equipment overload problem of reservoir drainage and flood control projects under high load conditions is solved, the stability and responsiveness of the system are improved, and the stability and response capabilities of the system are ensured. Safety monitoring and flood control effects of reservoirs.

CN119087467APending Publication Date: 2024-12-06XINJIANG XINLU TRAFFIC ENG CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411163891.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-23
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing safety monitoring technology for reservoir drainage and flood control projects. Under weather conditions with high rainfall, GNSS receivers need to quickly increase the data acquisition frequency and processing capacity, resulting in equipment overload, which may lead to performance degradation, failure and data loss, affecting risk warning and Emergency response.

Method used

By monitoring and analyzing the operating status of the GNSS receiver in real time, evaluating the improvement of data acquisition frequency and processing capacity, prioritizing urgent data, compressing non-urgent data, and dynamically adjusting processing strategies to ensure that the system operates stably under high load conditions.

Benefits of technology

Effectively avoid equipment overload, improve system reliability and durability, ensure real-time processing and transmission of key data, improve risk warning and emergency response capabilities, and comprehensively ensure the safety of the operation of the reservoir.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119087467A_ABST
    Figure CN119087467A_ABST
Patent Text Reader

Abstract

The invention discloses a reservoir drainage and flood control project safety monitoring method, and relates to the technical field of civil engineering monitoring, and the method specifically comprises the following steps: analyzing multiple reservoir data collected by a GNSS receiver in real time, and judging whether the GNSS receiver needs to improve the data collection frequency and processing capacity; under the condition that the data acquisition frequency and the processing capacity of the GNSS receiver need to be improved, the data acquisition frequency and the processing capacity of the GNSS receiver are improved; in the process of improving the data acquisition frequency and the processing capacity of the GNSS receiver, the operation state information of the GNSS receiver is acquired and analyzed, whether the improvement degree of the data acquisition frequency and the processing capacity of the GNSS receiver affects the normal use of the GNSS receiver is evaluated, and corresponding solutions are taken according to the evaluation result. By monitoring and analyzing the operation state of the GNSS receiver in real time, preferentially processing urgent data, compressing and storing non-urgent data, and dynamically evaluating and adjusting the processing strategy, the stable operation of the system and the real-time performance and accuracy of the data are ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to the technical field of civil engineering monitoring, and in particular to a safety monitoring method for reservoir drainage and flood control projects. Background Art

[0002] Reservoir drainage and flood control projects refer to engineering systems that control and regulate water flow through the construction and management of reservoirs and their ancillary facilities to prevent flooding and ensure smooth drainage. The project usually includes structures such as dams, spillways, drainage channels, and diversion tunnels. It aims to store excess water in the rainy season and reduce downstream flood pressure. At the same time, it rationally dispatches water resources in the dry season to ensure agricultural irrigation, urban water supply, and ecological environment needs. Through real-time monitoring and scientific management, the safety and efficiency of the project operation are ensured, and the safety of people's lives and property is protected. Safety monitoring of reservoir drainage and flood control projects refers to the use of advanced technology and equipment to conduct real-time and continuous monitoring and evaluation of the structural status and operation of reservoirs and their ancillary facilities (such as dams, spillways, drainage channels, etc.) to ensure the stability and safety of the project. Safety monitoring aims to timely discover and warn of potential risks, such as dam displacement, foundation settlement, leakage, etc., so as to quickly take preventive and emergency measures to avoid flood disasters caused by project failure. Through accurate monitoring data and analysis, project managers can make scientific decisions to ensure the efficient operation of reservoirs in flood control and drainage, and protect the safety of life and property of people in downstream areas.

[0003] The existing reservoir drainage and flood control project safety monitoring technology specifically includes the following steps: first, conduct a comprehensive geological and structural assessment of the reservoir to determine the areas that need to be monitored; second, install high-precision GNSS receivers at key locations (such as dam bodies, drainage channels and spillways), and configure the receiver's signal parameters and data transmission settings; then formulate a detailed monitoring plan, including setting monitoring parameters such as ground subsidence rate, cumulative settlement, soil displacement change rate and early warning thresholds, and determine the data collection frequency (such as every minute, every hour or every day); start the GNSS receiver to collect real-time data, and transmit the data to the central data processing center in real time through the Internet of Things card or Wi-Fi; pre-process the received data in the data center, including filtering, denoising and outlier removal, and apply the precise single-point positioning algorithm for error correction and displacement data calculation; evaluate the safety status of the structure based on the change trend of the displacement data. If the data exceeds the early warning threshold, the system automatically triggers the early warning mechanism and notifies the project management personnel; finally, regularly generate monitoring reports, including displacement change charts, data analysis results and safety assessments, and perform system maintenance and equipment calibration to ensure the continued accuracy of the monitoring results.

[0004] The prior art has the following deficiencies:

[0005] Under rainy weather conditions, a sharp increase in rainfall will cause rapid changes in reservoir parameters such as water level and flow. Existing GNSS receivers need to significantly increase data collection frequency and processing capacity in a short period of time. However, this rapidly increasing demand for data processing may cause equipment overload, increase receiver power consumption and hardware loss, and ultimately cause equipment heating, performance degradation, and even failure. In addition, when the amount of monitoring data increases dramatically, existing GNSS receivers and their supporting data processing systems may not be able to process such a large amount of data in a timely manner. This will not only lead to data processing delays, reduced accuracy, and lack of real-time performance, and fail to fully capture the dynamic changes of the reservoir, affecting risk warning and emergency response, but may also cause system crashes and data loss, seriously threatening the safe operation of the reservoir and the flood control effect in downstream areas, and increasing potential disaster risks.

[0006] The above information disclosed in this Background section is only for enhancement of understanding of the background of the present disclosure and therefore it may contain information that does not constitute the prior art that is already known to one of ordinary skill in the art. Summary of the invention

[0007] The purpose of the present invention is to provide a reservoir drainage and flood control project safety monitoring method to solve the problems in the above-mentioned background technology.

[0008] In order to achieve the above object, the present invention provides the following technical solution: a method for monitoring the safety of a reservoir drainage and flood control project, which specifically comprises the following steps:

[0009] Analyze multiple reservoir data collected by the GNSS receiver in real time to determine whether the GNSS receiver needs to increase the data collection frequency and processing capacity. If the GNSS receiver does not need to increase the data collection frequency and processing capacity, the GNSS receiver continues to maintain the current working state for monitoring. If the GNSS receiver needs to increase the data collection frequency and processing capacity, continue with the following steps;

[0010] Increasing the data collection frequency and processing capacity of GNSS receivers where such frequency and processing capacity are required;

[0011] In the process of increasing the data collection frequency and processing capacity of the GNSS receiver, obtain and analyze the operating status information of the GNSS receiver, evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and make corresponding solutions based on the evaluation results;

[0012] Acquire and analyze all data collected by the GNSS receiver, evaluate the urgency of each data collected by the GNSS receiver, and classify each data collected by the GNSS receiver into urgent data and non-urgent data based on the evaluation results, when the increase in the data collection frequency and processing capacity of the GNSS receiver affects its normal use;

[0013] Prioritize urgent data, and compress and store non-urgent data;

[0014] Detect changes in the amount of urgent data to be processed and changes in the processing capacity of the GNSS receiver in real time, evaluate whether the GNSS receiver has spare processing capacity to process non-urgent data, and make corresponding adjustments based on the evaluation results.

[0015] Preferably, in the process of increasing the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver is obtained and analyzed, and it is evaluated whether the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and corresponding solutions are taken according to the evaluation results, which specifically includes the following steps:

[0016] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver is obtained and pre-processed;

[0017] Extracting load performance data and throughput data from the operating status information of the GNSS receiver, and analyzing the extracted load performance data and throughput data respectively to generate a device load factor and a data throughput index;

[0018] The generated device load factor and data throughput index are used to construct a data evaluation model to generate an evaluation coefficient;

[0019] The generated evaluation coefficient is compared with the pre-set evaluation coefficient threshold to evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and corresponding solutions are taken according to the evaluation results.

[0020] Preferably, the acquisition logic of the device load factor and data throughput index is as follows:

[0021] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the load performance data in the operating status information of the GNSS receiver is extracted, including the CPU usage rate, memory occupancy rate and corresponding time points at different times within a period of time, and the CPU usage rate and memory occupancy rate at different times within a period of time are represented by functions CPU(t) and MEM(t) according to the time series, t is the time point, and the time period is defined as [t1, t2];

[0022] Calculate the equipment load factor. The specific calculation formula is as follows:

[0023]

[0024] In the formula, LC is the device load factor, and ω1 and ω2 are weight coefficients used to adjust the importance of CPU usage and memory usage when calculating the device load factor;

[0025] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the throughput data in the operating status information of the GNSS receiver is extracted, including the data collection rate, data transmission rate and corresponding time points at different times within a period of time, and the data collection rate and data transmission rate at different times within a period of time are represented by functions ACQ(T) and TRS(T) according to the time series, T is the time point, and the time period is defined as [T1, T2];

[0026] Get the maximum data acquisition rate and maximum data transmission rate of the GNSS receiver. After getting them, calibrate the maximum data acquisition rate and maximum data transmission rate of the GNSS receiver as ACQ respectively. max and TRS max ;

[0027] Calculate the data throughput index. The specific calculation formula is as follows:

[0028]

[0029] Where TI is the data throughput index, ω3 and ω4 are weight coefficients used to adjust the importance of data acquisition rate and data transmission rate in calculating the data throughput index.

[0030] Preferably, the generated equipment load coefficient LC and data throughput index TI are used to construct a data evaluation model, and an evaluation coefficient QG is generated by weighted summation.

[0031] Preferably, the generated evaluation coefficient QG is compared with a preset evaluation coefficient threshold QG yz Compare and evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and make corresponding solutions based on the evaluation results. The specific analysis is as follows:

[0032] If QG≤QG yz , the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will not affect its normal use. The GNSS receiver continues to maintain or increase the current data collection frequency and processing capacity, and the system operates normally;

[0033] If QG>QG yz, the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use. The GNSS receiver stops increasing the data collection frequency and processing capacity and reduces the data collection frequency and processing capacity. At the same time, a system warning is triggered and the staff is notified through the mobile terminal.

[0034] Preferably, in the case where the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, all data collected by the GNSS receiver are acquired and analyzed, the urgency of each data collected by the GNSS receiver is evaluated, and the data collected by the GNSS receiver is divided into urgent data and non-urgent data according to the evaluation result, which specifically includes the following steps:

[0035] Acquire all data collected by the GNSS receiver, and pre-process all data collected by the acquired GNSS receiver;

[0036] Extracting critical information from each data collected by the pre-processed GNSS receiver;

[0037] Analyze the urgent information of each data collected by the GNSS receiver, and generate a data value variation coefficient and a data value deviation coefficient of each data respectively;

[0038] An urgency assessment model is constructed using the data value variation coefficient and the data value deviation coefficient of each generated data to generate an urgency coefficient. The urgency coefficient of each generated data is compared with a preset urgency coefficient threshold to evaluate the urgency of each data collected by the GNSS receiver, and the data collected by the GNSS receiver is divided into urgent data and non-urgent data according to the evaluation results.

[0039] Preferably, the logic for obtaining the data value variation coefficient and the data value deviation coefficient of each data is as follows:

[0040] Extract the urgent information of each data collected by the preprocessed GNSS receiver, including the data value of each data collected by the GNSS receiver at different times within a period of time, and calibrate the data value of each data collected by the GNSS receiver at different times within a period of time as represents the data value of the i-th data collected by the GNSS receiver at time m within a period of time, i = 1, 2, 3, ..., g, m = 1, 2, 3, ..., k, g and k are both positive integers;

[0041] Calculate the coefficient of variation of the data values ​​of each data. The specific calculation formula is as follows:

[0042]

[0043] In the formula, RC iis the coefficient of variation of the data value of the i-th data;

[0044] Obtain the preset data value of each data collected by the GNSS receiver. After obtaining, calibrate the preset data value of each data collected by the GNSS receiver as

[0045] Calculate the data value deviation coefficient of each data. The specific calculation formula is as follows:

[0046]

[0047] In the formula, DD i is the data value deviation coefficient of the i-th data.

[0048] Preferably, the data value variation coefficient RC of each generated data i And the data value deviation coefficient DD i Construct an urgency assessment model and generate the urgency coefficient JP through weighted summation i , and generate the urgency coefficient JP of each data i The preset urgency factor threshold JP yz Compare and evaluate the urgency of each data collected by the GNSS receiver, and divide the data collected by the GNSS receiver into urgent data and non-urgent data according to the evaluation results. The specific division is as follows:

[0049] If JP i ≤JP yz , the urgency of the i-th data collected by the GNSS receiver is low, and the data is classified as non-urgent data;

[0050] If JP i >JP yz , the urgency of the i-th data collected by the GNSS receiver is high, and the data is classified as urgent data.

[0051] Preferably, urgent data is processed first, while non-urgent data is compressed and stored, which specifically includes the following steps:

[0052] Among the data collected by the GNSS receiver, data packets marked as urgent data are preferentially transmitted to the central processing system for real-time analysis and processing, and a predetermined communication protocol is used to ensure the stability and timeliness of data transmission. Data packets marked as non-urgent data are compressed using a data compression algorithm, and the compressed data is stored in a local storage device or cloud storage system, and the stored compressed data is regularly uploaded to the central database for archiving and backup.

[0053] Preferably, real-time detection of changes in the processing volume of urgent data and changes in the processing capacity of the GNSS receiver is performed, and evaluation is performed on whether the GNSS receiver has spare processing capacity to process non-urgent data, and corresponding adjustments are made according to the evaluation results, specifically including the following steps:

[0054] Obtain the amount of urgent data processing and the change in GNSS receiver processing capacity over a period of time;

[0055] Analyze the changes in the processing volume of urgent data and the processing capacity of the GNSS receiver over a period of time, and generate the urgent data processing rate and the idle capacity coefficient respectively;

[0056] Determining a critical data processing rate threshold and an idle capacity factor threshold;

[0057] The urgent data processing rate and the idle capacity factor are compared with the urgent data processing rate threshold and the idle capacity factor threshold respectively to evaluate whether the GNSS receiver has spare processing capacity to process non-urgent data, and make corresponding adjustments based on the evaluation results. The specific analysis is as follows:

[0058] If the urgent data processing rate is greater than the urgent data processing rate threshold and the idle capacity factor is greater than the idle capacity factor threshold, the GNSS receiver has spare processing capacity to process the non-urgent data, and decompresses and processes the compressed and stored non-urgent data;

[0059] If the urgent data processing rate is not greater than the urgent data processing rate threshold and the idle capacity coefficient is not greater than the idle capacity coefficient threshold, the GNSS receiver has no spare processing capacity to process the non-urgent data, and does not decompress and process the compressed and stored non-urgent data.

[0060] In the above technical solution, the technical effects and advantages provided by the present invention are:

[0061] 1. The present invention can effectively solve the problem that under rainy weather conditions, the water level, flow rate and other parameters of the reservoir change rapidly due to the sharp increase in rainfall, and the GNSS receiver needs to increase the data collection frequency and processing capacity in a short period of time, which may cause equipment overload. Specifically, firstly, by real-time monitoring and analysis of the operating status information of the GNSS receiver, it is evaluated whether the data collection frequency and processing capacity of the receiver will affect its normal use, and corresponding solutions are taken to ensure the stable operation of the equipment under high load conditions, avoid equipment heating, performance degradation and even failure due to overload, thereby improving the reliability and durability of the system.

[0062] 2. The present invention can optimize the use of system resources when the amount of monitoring data increases dramatically by giving priority to processing urgent data and compressing and storing non-urgent data, ensuring real-time processing and transmission of key data, reducing data processing delays, and improving data accuracy and real-time performance. By real-time detection of changes in the processing volume of urgent data and changes in the processing capacity of the GNSS receiver, the system can dynamically evaluate and adjust the processing strategy to ensure that the dynamic changes of the reservoir can still be effectively captured when the system load is high, improve risk warning and emergency response capabilities, and prevent monitoring blind spots caused by data processing delays or losses, thereby fully ensuring the safe operation of the reservoir.

[0063] 3. The present invention can accurately evaluate and optimize system performance and ensure stable operation of the system under high load conditions by constructing and using an evaluation model of equipment load factor and data throughput index in the process of increasing the data collection frequency and processing capacity of the GNSS receiver. This method can not only prevent the system from crashing due to overload, but also reduce potential disaster risks and ensure flood control effects in downstream areas through effective resource management and processing strategies, thereby comprehensively improving the safety monitoring capabilities of reservoir drainage and flood control projects and the overall operating efficiency of the system under rainy weather conditions. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0065] Figure 1 It is a schematic flow chart of the reservoir drainage and flood control project safety monitoring method of the present invention. DETAILED DESCRIPTION

[0066] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these example embodiments are provided so that the description of the present disclosure will be more comprehensive and complete, and the concept of the example embodiments will be fully conveyed to those skilled in the art.

[0067] The present invention provides Figure 1 The safety monitoring method for reservoir drainage and flood control projects shown in the figure specifically includes the following steps:

[0068] Analyze multiple reservoir data collected by the GNSS receiver in real time to determine whether the GNSS receiver needs to increase the data collection frequency and processing capacity. If the GNSS receiver does not need to increase the data collection frequency and processing capacity, the GNSS receiver continues to maintain the current working state for monitoring. If the GNSS receiver needs to increase the data collection frequency and processing capacity, continue with the following steps;

[0069] This step is to analyze the multiple reservoir data collected in real time by the GNSS receiver to determine whether the current monitoring status can accurately and timely reflect the actual situation of the reservoir. If the monitoring data shows that the current collection frequency and processing capacity are sufficient to cope with the changes in reservoir parameters, the system will maintain the existing working status; if the monitoring data shows that the current collection frequency and processing capacity are not enough to cope with the rapidly changing reservoir parameters, the collection frequency and processing capacity need to be increased to ensure the real-time and accuracy of monitoring.

[0070] The analysis of data collected by GNSS receivers in real time can be done through software systems that integrate data processing and analysis algorithms that can process and analyze large-scale real-time data. Specific analysis methods include data cleaning, anomaly detection, trend analysis, and statistical modeling. Multiple reservoir data include but are not limited to water level changes, flow changes, rainfall, dam displacement, seepage pressure, and environmental data such as temperature and humidity. Through multi-dimensional comprehensive analysis of these data, the system can identify abnormal situations and rapid changes in trends in order to make judgments.

[0071] Determining whether the GNSS receiver needs to increase data collection frequency and processing capacity can be achieved through set thresholds and rules. When the change in real-time data exceeds the preset threshold, or the data analysis results show significant trend changes and abnormal fluctuations, the system will trigger a mechanism to increase the collection frequency and processing capacity. Using machine learning algorithms and intelligent monitoring systems, thresholds can be automatically adjusted based on historical data and current environmental conditions, and real-time assessments can be made to determine whether data collection and processing capabilities need to be upgraded to ensure the efficiency and reliability of the monitoring system.

[0072] Increasing the data collection frequency and processing capacity of GNSS receivers where such frequency and processing capacity are required;

[0073] The data collection frequency and processing capacity of GNSS receivers can be improved by optimizing software algorithms, adjusting system configurations, and increasing hardware resources. Specifically, first, the data collection and processing algorithms can be optimized to make them more efficient, such as using parallel processing and multi-threading technology to increase data processing speed. Secondly, the system configuration can be adjusted to increase the frequency parameters of data collection so that the receiver can obtain data more frequently. In addition, hardware resources can be expanded, such as increasing the number of processor cores, improving memory capacity, and storage speed to support higher processing capacity. Dynamic load balancing can be achieved at the software level, and data processing tasks can be allocated to multiple processing units to avoid single-point overload. At the same time, cloud computing resources can be used to migrate some data processing tasks to cloud processing to improve the processing power and response speed of the overall system. In these ways, GNSS receivers can quickly increase data collection frequency and processing capacity when demand increases, ensuring real-time and accuracy of monitoring.

[0074] In the process of increasing the data collection frequency and processing capacity of the GNSS receiver, obtain and analyze the operating status information of the GNSS receiver, evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and make corresponding solutions based on the evaluation results;

[0075] In this embodiment, in the process of increasing the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver is obtained and analyzed, and it is evaluated whether the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and corresponding solutions are taken according to the evaluation results, which specifically includes the following steps:

[0076] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver is obtained and pre-processed;

[0077] In the process of increasing the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver can be obtained through the built-in monitoring module and external monitoring tools. The built-in monitoring module collects various performance indicators of the device in real time, such as CPU usage time, memory occupancy, data collection rate, and data transmission rate. This data can be obtained through system calls and the device's performance monitoring interface (API). In addition, external monitoring tools (such as SNMP protocol or dedicated monitoring software) can periodically poll the device to obtain the latest operating status information and transmit it to the central monitoring system for centralized management and analysis. These methods ensure the real-time and accuracy of the operating status information, which helps to fully understand the working status of the device.

[0078] The purpose of preprocessing the operating status information is to ensure the integrity and consistency of the data and improve the accuracy and efficiency of subsequent analysis. The preprocessing process includes steps such as data cleaning, normalization, and outlier detection. First, data cleaning is to remove noise and invalid data to ensure the purity of the data set. Secondly, normalization converts data of different dimensions to a unified scale to make them more comparable. Specifically, min-max normalization or standardization methods can be used to map data values ​​to a specific range (such as between 0 and 1). Finally, outlier detection identifies and processes abnormal data that deviates from the normal range to prevent it from affecting the overall analysis results. These preprocessing steps can be implemented through software automation, using data processing libraries and statistical algorithms to ensure that the operating status information has been optimized and standardized before entering the evaluation model.

[0079] Extracting load performance data and throughput data from the operating status information of the GNSS receiver, and analyzing the extracted load performance data and throughput data respectively to generate a device load factor and a data throughput index;

[0080] When extracting load performance data and throughput data from the operating status information of the GNSS receiver, this can be achieved through system monitoring tools and application programming interfaces (APIs). First, through the monitoring tools that come with the operating system (such as Windows Task Manager), load performance data such as CPU usage time and memory occupancy can be obtained in real time. These tools usually provide interfaces (such as Windows performance counters) for software access. In addition, using specific performance monitoring APIs, such as Performance Monitor or Simple Network Management Protocol (SNMP), software scripts can be written to query and collect this data regularly. For throughput data, the data acquisition rate and data transmission rate can be monitored in real time through the device's built-in logging system or network monitoring tools (such as Wireshark). Combining these monitoring tools with software scripts, the system can automatically extract, record and summarize the required operating status information, ensuring the real-time and accuracy of the extraction process, thereby providing a high-quality data foundation for subsequent analysis.

[0081] The generated device load factor and data throughput index are used to construct a data evaluation model to generate an evaluation coefficient;

[0082] The generated evaluation coefficient is compared with the pre-set evaluation coefficient threshold to evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and corresponding solutions are taken according to the evaluation results.

[0083] The pre-set evaluation coefficient threshold can be determined by historical data analysis, performance benchmarking and simulation. First, historical data analysis is to identify the evaluation coefficient range of the device under normal and abnormal conditions by collecting and analyzing the operating data of the GNSS receiver under different workloads and environmental conditions. Use data analysis tools and algorithms, such as time series analysis and cluster analysis, to find out the distribution and change rules of the evaluation coefficient. Secondly, performance benchmarking is to systematically test the GNSS receiver in a laboratory environment, including the operation under different frequencies and capacities, and record the corresponding equipment load factor and data throughput index, so as to determine the performance limit and safe operation range of the device. Finally, simulation is to use simulation software to simulate the working state of the GNSS receiver under various extreme conditions and predict the evaluation coefficient of the device under high load and high throughput conditions. The data and results generated by these methods can be used to determine a reasonable evaluation coefficient threshold using statistical analysis tools to ensure that it can reflect the actual operating capacity and safety margin of the device. In this way, the software system can evaluate the operating status of the device in real time according to these set thresholds, and take corresponding solutions when necessary to ensure the stability and safe operation of the system.

[0084] In this embodiment, the logic for obtaining the device load factor and the data throughput index is as follows:

[0085] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the load performance data in the operating status information of the GNSS receiver is extracted, including the CPU usage rate, memory occupancy rate and corresponding time points at different times within a period of time, and the CPU usage rate and memory occupancy rate at different times within a period of time are represented by functions CPU(t) and MEM(t) according to the time series, respectively, as the time point, and the time period is defined as [t1, t2];

[0086] In the process of increasing the data collection frequency and processing capacity of the GNSS receiver, the load performance data extracted from the operating status information of the GNSS receiver can be achieved through the monitoring tools, performance monitoring APIs and logging systems of the operating system. Specifically, the performance counters of Windows can be used to monitor the CPU usage and memory occupancy in real time. These tools provide system call interfaces, and the software can query these interfaces regularly to obtain the CPU and memory usage at different time points and record the corresponding timestamps. Performance monitoring APIs (such as Performance Monitor API or SNMP protocol) can also be scripted for regular polling to collect CPU and memory usage data. In order to ensure the integrity and continuity of the data, a logging system can also be used to record all the collected performance data and store it in a local or cloud database for subsequent analysis and processing. In these ways, the software can extract the load performance data of the GNSS receiver at different times in the process of increasing the data collection frequency and processing capacity in real time to ensure the accuracy and timeliness of the data.

[0087] Calculate the equipment load factor. The specific calculation formula is as follows:

[0088]

[0089] In the formula, LC is the device load factor, and ω1 and ω2 are weight coefficients used to adjust the importance of CPU usage and memory usage when calculating the device load factor;

[0090] ω1 and ω2 are weight coefficients used to adjust the importance of CPU usage and memory occupancy in calculating the device load factor. Specifically, these two weight coefficients reflect the different degrees of impact of CPU and memory usage on system performance in different application scenarios. By setting different weight coefficients, you can flexibly balance the impact of CPU and memory according to actual needs. For example, in computing-intensive tasks, CPU usage may have a greater impact on system performance, so a higher ω1 can be set; while in memory-intensive tasks, the impact of memory occupancy is greater, so a higher ω2 can be set. The sum of these two weight coefficients should be 1 (i.e., ω1+ω2=1) to ensure that the calculation results are within a unified range. In addition, these weight coefficients can be adjusted based on historical data and system performance benchmarks to find the best balance point and optimize the evaluation and monitoring of system performance. By reasonably setting and adjusting ω1 and ω2, the actual load of the system can be more accurately reflected, providing strong support for system performance optimization.

[0091] The size of the device load factor is directly related to the evaluation of the stability and normal operation of the GNSS receiver when increasing the data collection frequency and processing capacity. Specifically, the device load factor is an indicator that reflects the combined impact of CPU usage and memory occupancy. When the load performance data of the GNSS receiver is collected and a high device load factor is calculated, it means that the system's resource utilization is close to or has reached its maximum carrying capacity. At this time, further increasing the data collection frequency and processing capacity may cause system overload, performance degradation, extended response time, and even system crashes. On the contrary, a low device load factor indicates that the system resource utilization is low, and the system still has enough room and stability after increasing the data collection frequency and processing capacity, and will not significantly affect its normal operation. Therefore, by monitoring and analyzing the changes in the device load factor, the operating status of the GNSS receiver under different workloads can be effectively evaluated, and it can be determined whether the data collection strategy needs to be adjusted to ensure that the system always operates within a safe and efficient working range, thereby avoiding potential risks and failures caused by excessive load.

[0092] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the throughput data in the operating status information of the GNSS receiver is extracted, including the data collection rate, data transmission rate and corresponding time points at different times within a period of time, and the data collection rate and data transmission rate at different times within a period of time are represented by functions ACQ(T) and TRS(T) according to the time series, T is the time point, and the time period is defined as [T1, T2];

[0093] In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the throughput data from the operating status information of the GNSS receiver, including the data collection rate, data transmission rate and corresponding time points at different times over a period of time, can be extracted by using the device's built-in logging system and network monitoring tools. Specifically, the data collection rate can be monitored and recorded through the built-in logging system of the GNSS receiver, which records the amount of data collected per second with a timestamp. For the data transmission rate, network monitoring tools (such as Wireshark and NetFlow) can be used to monitor the data transmission in real time, record the amount of data transmitted per second, and attach time point information. Combining these two types of tools, through system calls and API interfaces, the software can poll these data sources regularly or in real time, extract the data collection rate and data transmission rate at different times, and record the corresponding time points. All extracted data will be stored in a local or cloud database for subsequent data processing and analysis. This approach not only ensures the real-time and accuracy of data extraction, but also enables continuous monitoring and data recording through software automation, providing reliable basic data for evaluating system performance.

[0094] Get the maximum data acquisition rate and maximum data transmission rate of the GNSS receiver. After getting them, calibrate the maximum data acquisition rate and maximum data transmission rate of the GNSS receiver as ACQ respectively. max and TRS max ;

[0095] The maximum data acquisition rate and maximum data transmission rate of a GNSS receiver can be obtained through a combination of device technical specification documents, benchmarks, and performance monitoring tools. First, device manufacturers usually provide these maximum rate values ​​in technical specification documents, and software can obtain initial values ​​by accessing and parsing these documents. Second, through benchmarking, GNSS receivers can be run in a controlled environment to test their data acquisition and transmission capabilities at extreme loads. Specifically, a test script can be written to make the receiver run at the highest acquisition and transmission frequency, record the data acquisition rate and transmission rate over a period of time, and then take the peak value as the maximum data acquisition rate and maximum data transmission rate. In addition, performance monitoring tools (such as NetFlow, Wireshark) can monitor network traffic in real time and obtain real-time data transmission rate statistics through API interfaces or system calls. These tools usually support high-frequency data acquisition and detailed traffic analysis. The software can query these monitoring data regularly and calculate the maximum value as the maximum data rate. After combining these methods, the software system can calibrate and update the values ​​of the maximum data acquisition rate and transmission rate to ensure that these key performance indicators reflect the true capabilities of the device and provide an accurate benchmark for subsequent performance evaluation and optimization.

[0096] Calculate the data throughput index. The specific calculation formula is as follows:

[0097]

[0098] Where TI is the data throughput index, ω3 and ω4 are weight coefficients used to adjust the importance of data acquisition rate and data transmission rate in calculating the data throughput index.

[0099] ω3 and ω4 are weight coefficients used to adjust the importance of data acquisition rate and data transmission rate in calculating data throughput index. Specifically, these two weight coefficients reflect the different degrees of influence of data acquisition rate and data transmission rate on system performance in different application scenarios. For example, in some scenarios, data acquisition rate may be more critical to system performance. In this case, a higher ω3 weight can be set to better reflect the influence of acquisition rate on data throughput index. On the contrary, in other scenarios, data transmission rate may be more important. In this case, the weight of ω4 can be increased. By adjusting the values ​​of ω3 and ω4, different performance requirements and optimization goals can be flexibly adapted to make the data throughput index more accurately reflect the load of the system in actual operation. The sum of these weight coefficients should be 1 (i.e., ω3+ω4=1) to ensure that the calculation results are within a unified range and maintain the standardization and comparability of the indicators. In addition, through historical data analysis and performance benchmarking, these weight coefficients can be optimized to find the best balance point and maximize the effect of system performance monitoring and optimization.

[0100] The size of the data throughput index is directly related to the evaluation of the stability and normal operation of the GNSS receiver when the data collection frequency and processing capacity are increased. Specifically, the data throughput index is a comprehensive indicator that reflects the data collection and transmission capabilities of the GNSS receiver in a unit time. When the data throughput index is high, it indicates that the data collection rate and transmission rate of the receiver are close to its maximum carrying capacity, which means that the bandwidth and processing resources of the system are close to saturation. Further increasing the data collection frequency and processing capacity may cause system overload, data loss, increased delay, and even system crash. On the contrary, a low data throughput index indicates that the system's collection and transmission capabilities have not yet reached their limits. The system still has room after increasing the data collection frequency and processing capacity, which will not significantly affect its normal use. Therefore, by monitoring and analyzing the changes in the data throughput index, the operating status of the GNSS receiver under different workloads can be effectively evaluated, and it can be determined whether the data collection strategy needs to be adjusted to ensure that the system always operates within a safe and efficient working range, thereby avoiding potential risks and failures caused by excessive load.

[0101] In this embodiment, the generated equipment load coefficient LC and data throughput index TI are used to construct a data evaluation model, and the evaluation coefficient QG is generated by weighted summation.

[0102] In order to construct a data evaluation model with the generated equipment load coefficient and data throughput index, and generate the evaluation coefficient QG through weighted summation, it is first necessary to define the structure and weight parameters of the evaluation model. The specific steps are as follows: First, collect and preprocess the equipment load coefficient LC and data throughput index TI to ensure the accuracy and consistency of the data. Then, set the weight coefficients α and β to reflect the importance of the equipment load coefficient and data throughput index in the evaluation model, respectively. These weight coefficients can be optimized and adjusted through historical data analysis and performance test results to ensure that the model can accurately reflect the actual operating conditions of the system. Next, the equipment load coefficient and data throughput index are combined through the weighted summation method to generate a comprehensive evaluation coefficient QG. The specific calculation formula is as follows:

[0103] QG=α*LC+β*TI

[0104] Among them, α and β are the weights of the device load factor and data throughput index respectively, and α+β=1, ensuring that the evaluation results are within a unified range. The software can process the current device load factor and data throughput index using the above formula through scheduled or real-time calculation to generate a real-time evaluation coefficient QG. By comparing QG with the preset threshold, it can be evaluated whether the current increase in data collection frequency and processing capacity will affect the normal use of the GNSS receiver. If QG exceeds the threshold, the system can automatically trigger an adjustment mechanism to optimize the data collection strategy or warn the user to prevent system overload and ensure stable operation. This process can be implemented through automated scripts or integrated performance monitoring modules to provide continuous and accurate system evaluation.

[0105] In this embodiment, the generated evaluation coefficient QG is compared with the preset evaluation coefficient threshold QG yz Compare and evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and make corresponding solutions based on the evaluation results. The specific analysis is as follows:

[0106] If QG≤QG yz , the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will not affect its normal use. The GNSS receiver continues to maintain or increase the current data collection frequency and processing capacity, and the system operates normally;

[0107] In this case, the software system will continue to maintain or moderately increase the current data collection frequency and processing capacity to ensure the timeliness and accuracy of the monitoring data. The specific implementation steps include: first, continuously obtain and update the operating status information of the GNSS receiver through the automated monitoring module; then, dynamically adjust the parameters of data collection frequency and processing capacity based on real-time monitoring data and historical records; finally, the system will periodically recalculate the equipment load factor and data throughput index, update the evaluation coefficient QG, and compare again to ensure that the system is always within the safe operating range. If QG still meets the conditions during the subsequent monitoring process, the system will continue to optimize the data collection strategy and improve data processing efficiency to maintain an efficient operating state.

[0108] If QG>QG yz , the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, the GNSS receiver stops increasing the data collection frequency and processing capacity and reduces the data collection frequency and processing capacity, and triggers a system warning, notifying the staff through the mobile terminal;

[0109] In this case, the software system needs to take immediate measures to prevent system overload and performance degradation. The specific implementation steps include: first, the system automatically triggers the alarm module, generates a warning message and notifies the relevant staff through the mobile terminal; second, the software system automatically reduces the data collection frequency and processing capacity, adjusts to a lower load level, and ensures stable operation of the system; third, the system recalculates the equipment load factor and data throughput index, and monitors the changes in the evaluation coefficient QG; finally, after receiving the alarm, the staff can view the detailed system status and adjustment records through the monitoring interface, and manually intervene and optimize the system parameters when necessary to ensure that the GNSS receiver resumes normal operation. Through these measures, the system can respond and adjust in a timely manner, avoid risks caused by excessive load, and ensure the continuity and reliability of monitoring work.

[0110] Acquire and analyze all data collected by the GNSS receiver, evaluate the urgency of each data collected by the GNSS receiver, and classify each data collected by the GNSS receiver into urgent data and non-urgent data based on the evaluation results, when the increase in the data collection frequency and processing capacity of the GNSS receiver affects its normal use;

[0111] In this embodiment, when the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, all data collected by the GNSS receiver are acquired and analyzed, the urgency of each data collected by the GNSS receiver is evaluated, and the data collected by the GNSS receiver is divided into urgent data and non-urgent data according to the evaluation result, which specifically includes the following steps:

[0112] Acquire all data collected by the GNSS receiver, and pre-process all data collected by the acquired GNSS receiver;

[0113] All data collected by the GNSS receiver can be obtained through the device's built-in data logging system and real-time data stream interface. Specifically, the GNSS receiver will continuously record various monitoring data during operation, and these data are stored in local log files or output through real-time data stream interfaces. The software can obtain data by reading these log files or subscribing to real-time data streams. For example, using system calls or API interfaces, the records in the log files are read regularly to extract parameters including reservoir water level changes, flow changes, rainfall, dam displacement, seepage pressure, and ambient temperature and humidity. At the same time, through the real-time data stream interface, the software can obtain data instantly when it is generated, ensuring the real-time and integrity of the data.

[0114] The purpose of preprocessing data is to improve the accuracy, consistency and availability of data, thereby ensuring the reliability of subsequent analysis. Preprocessing includes steps such as data cleaning, normalization and outlier detection. Data cleaning is to remove noise and invalid data to ensure the purity of the data set; normalization converts data of different dimensions to a unified scale to make them comparable; outlier detection identifies and processes data that deviates from the normal range to prevent it from affecting the overall analysis results. In specific implementation, the software can use data processing libraries (such as Python's Pandas and NumPy) and statistical analysis methods to automatically process data. Data cleaning is completed by screening and filling missing values, normalization can use minimum-maximum normalization or standardization methods, and outlier detection can use statistical methods or machine learning algorithms to identify and process abnormal data. Through these preprocessing steps, it is ensured that the data input to the evaluation model is of high quality and can accurately reflect the actual operating status of the GNSS receiver.

[0115] Extracting critical information from each data collected by the pre-processed GNSS receiver;

[0116] Extracting the urgency information of each data collected by the preprocessed GNSS receiver can be achieved by calculating the rate of change and degree of deviation of the data. Specifically, the software can use statistical analysis and machine learning algorithms to analyze the preprocessed data. First, calculate the rate of change (Rate of Change, RC) of the data, which is obtained by dividing the amount of change in the data over a period of time by the time interval. For example, using the difference calculation method, calculate the difference between consecutive time points, and then divide it by the time interval to get the rate of change. Secondly, calculate the degree of deviation (Degree of Deviation, DD) of the data, which is obtained by the difference between the current data value and the benchmark value (such as the historical average or the set normal value). For example, using the percentage deviation formula, subtract the absolute value of the benchmark value from the current data value and divide it by the benchmark value. After extracting this urgency information, it can be further used in the urgency assessment model. The software can use data analysis libraries (such as Python's Pandas and NumPy) and machine learning libraries (such as scikit-learn) to automate this process to ensure that the extracted urgency information accurately reflects the real-time changes and abnormalities of the data.

[0117] Analyze the urgent information of each data collected by the GNSS receiver, and generate a data value variation coefficient and a data value deviation coefficient of each data respectively;

[0118] An urgency assessment model is constructed using the data value variation coefficient and the data value deviation coefficient of each generated data to generate an urgency coefficient. The urgency coefficient of each generated data is compared with a preset urgency coefficient threshold to evaluate the urgency of each data collected by the GNSS receiver, and the data collected by the GNSS receiver is divided into urgent data and non-urgent data according to the evaluation results.

[0119] Determining the pre-set threshold of the urgency coefficient can be achieved by combining historical data analysis, statistical methods and machine learning algorithms. Specifically, first collect a large amount of historical data of GNSS receivers under different working conditions, including data of normal operation and abnormal conditions. Use statistical analysis software (such as Python's Pandas, NumPy and SciPy) to perform descriptive statistical analysis on these data and calculate the mean, standard deviation and distribution of various types of data. By analyzing the rate of change and degree of deviation of the data, the characteristic value range of normal operation and abnormal conditions is identified. Then, using machine learning algorithms (such as classification algorithms and cluster analysis), further train the model, optimize the model parameters through methods such as cross-validation, and determine the optimal threshold of the urgency coefficient. For example, using classification algorithms in the scikit-learn library (such as logistic regression, support vector machine, etc.), classify and train and test the data to find a threshold that can effectively distinguish urgent data from non-urgent data. Finally, use these analysis and model results to set the threshold of the urgency coefficient, and regularly update and adjust the threshold through software to ensure that it always adapts to the actual operating conditions of the system, so as to accurately evaluate the urgency of the data collected by the GNSS receiver.

[0120] In this embodiment, the logic for obtaining the data value variation coefficient and the data value deviation coefficient of each data is as follows:

[0121] Extract the urgent information of each data collected by the preprocessed GNSS receiver, including the data value of each data collected by the GNSS receiver at different times within a period of time, and calibrate the data value of each data collected by the GNSS receiver at different times within a period of time as represents the data value of the i-th data collected by the GNSS receiver at time m within a period of time, i = 1, 2, 3, ..., g, m = 1, 2, 3, ..., k, g and k are both positive integers;

[0122] Extracting the urgent information of each data collected by the preprocessed GNSS receiver can be achieved through the data storage system and the real-time data stream interface. Specifically, the GNSS receiver will record the collected data (such as reservoir water level changes, flow changes, rainfall, dam displacement, seepage pressure, and ambient temperature and humidity) in the local database or cloud storage during operation. The software can access these data storage systems regularly or in real time through database queries or API calls to extract data values ​​at different times within a specified time period. For example, use SQL query statements to extract all relevant data within a certain period of time from the database, or obtain real-time data streams from the cloud by calling the RESTful API interface. At the same time, by subscribing to the data stream interface (such as WebSocket), the latest data values ​​can be obtained instantly when the data is generated. In these ways, the software can effectively extract the data values ​​of the GNSS receiver at different times within a period of time, providing a reliable data basis for subsequent data analysis and urgency assessment.

[0123] Calculate the coefficient of variation of the data values ​​of each data. The specific calculation formula is as follows:

[0124]

[0125] In the formula, RC i is the coefficient of variation of the data value of the i-th data;

[0126] The size of the data value variation coefficient of the i-th data is directly related to the urgency of evaluating each data collected by the GNSS receiver. Specifically, the data value variation coefficient reflects the rate of change of the data over a period of time. The larger the variation coefficient, the more drastic the fluctuation of the data over a period of time and the more significant the change. A higher variation coefficient usually means that there are abnormalities or emergencies in the data, such as a sharp rise in reservoir water levels or a sudden increase in rainfall. These changes may indicate potential risks or emergencies and require special attention and timely processing. On the contrary, a lower variation coefficient indicates that the data is relatively stable, with less fluctuations and is within the normal range. By monitoring and calculating the data value variation coefficient, it is possible to effectively identify which data has a higher urgency, so that these urgent data can be processed first when system resources are limited, ensuring the monitoring and emergency response capabilities of the GNSS receiver, and timely warning and response to possible risks and abnormal situations.

[0127] Obtain the preset data value of each data collected by the GNSS receiver. After obtaining, calibrate the preset data value of each data collected by the GNSS receiver as

[0128] Preset data value Refers to the standard or benchmark value of each data collected by the GNSS receiver under normal circumstances. These values ​​usually represent the typical range or average level of each monitoring parameter when the system is running stably. The preset data value can be obtained in the following ways: First, the preset data value can be extracted from historical data. The software performs statistical analysis on a large amount of historical monitoring data to calculate the average value, median or other representative statistics of each data, and these statistics are used as preset data values. Specifically, use data analysis tools (such as Python's Pandas and NumPy) to analyze historical data and extract the typical values ​​of each parameter during normal operation. Secondly, the preset data value can also be set by experts. According to professional knowledge and experience, the benchmark value of each monitoring parameter is set and stored in the configuration file or database for software to call. Finally, the preset data value can also be obtained through the benchmark test during system initialization. At the beginning of system operation, the software can record the initial value of each parameter as the preset data value through a series of benchmark tests. Once these preset data values ​​are determined, the software can query the database or read the configuration file, and call them in real time during operation to compare the current collected data, evaluate its deviation, and ensure the effectiveness and accuracy of the monitoring system.

[0129] Calculate the data value deviation coefficient of each data. The specific calculation formula is as follows:

[0130]

[0131] In the formula, DD i is the data value deviation coefficient of the i-th data.

[0132] The data value deviation coefficient DD of the i-th data i The size of is directly related to the urgency of evaluating each data collected by the GNSS receiver. The data value deviation coefficient reflects the degree of deviation between the current data value and the preset data value. The larger the deviation coefficient, the greater the deviation of the data from the normal range. A higher deviation coefficient usually means that the current data is abnormal and deviates significantly from its preset standard. For example, the water level of the reservoir is significantly higher or lower than the normal value, the flow rate changes far beyond expectations, or the seepage pressure increases abnormally. These anomalies may indicate potential risks or emergencies and require special attention and timely processing. On the contrary, a lower deviation coefficient indicates that the data fluctuates within the normal range, does not deviate significantly from the preset standard, and the system is in a stable state. By monitoring and calculating the data value deviation coefficient, it is possible to effectively identify which data has a higher urgency, so that these urgent data can be processed first when system resources are limited, ensuring the monitoring and emergency response capabilities of the GNSS receiver, and timely warning and response to possible risks and abnormal situations.

[0133] In this embodiment, the data value variation coefficient RC of each data generated is i And the data value deviation coefficient DD i Construct an urgency assessment model and generate the urgency coefficient JP through weighted summation i , and generate the urgency coefficient JP of each data i The preset urgency factor threshold JP yz Compare and evaluate the urgency of each data collected by the GNSS receiver, and divide the data collected by the GNSS receiver into urgent data and non-urgent data according to the evaluation results. The specific division is as follows:

[0134] If JP i ≤JP yz , the urgency of the i-th data collected by the GNSS receiver is low, and the data is classified as non-urgent data;

[0135] This means that the data is relatively stable, does not show significant anomalies or sudden changes, and its current state does not pose a threat to the normal operation of the system. When the software system evaluates this type of data, it will mark it as non-urgent data. This type of data does not need to be processed as a priority and can be recorded and stored according to the normal processing flow, while its status is regularly monitored to ensure that it can be responded to in a timely manner if changes occur in the future.

[0136] If JP i >JP yz , the urgency of the i-th data collected by the GNSS receiver is high, and the data is classified as urgent data;

[0137] This means that the data has significant anomalies or sudden changes, which may indicate potential risks or emergencies, posing a threat to the normal operation of the system. When evaluating such data, the software system will mark it as urgent data. For urgent data, the system will give priority to processing and take immediate response measures, such as increasing the frequency of data collection, encrypting data transmission, or triggering alarms to notify relevant personnel to conduct inspections and interventions to ensure the security and stability of the system. In this way, potential risks can be discovered and responded to in a timely manner to prevent abnormal situations from evolving into more serious problems.

[0138] The process of generating the urgency coefficient is to convert the coefficient of change of each data RC i and the coefficient of deviation DD i The specific steps are as follows: First, calculate the coefficient of variation RC of each data from the preprocessed GNSS receiver collected data i and the coefficient of deviation DD i, these two coefficients respectively reflect the rate of change of data in a certain period of time and the degree of deviation from the normal value. Next, in order to comprehensively consider the influence of these two factors, the weight coefficients γ and δ are set. These two weight coefficients represent the importance of the coefficient of change and the coefficient of deviation in the urgency assessment, and satisfy γ+δ=1. Then, the urgency coefficient JP of each data is calculated by the weighted summation formula i :JP i =γ*RC i +δ*DD i , where γ and δ adjust RC i This weighted summation process can be implemented through software, using data processing libraries (such as Python's Pandas and NumPy) to automate processing and calculation to generate the urgency coefficient of each data, providing a basis for subsequent urgency assessment and data classification.

[0139] Prioritize urgent data, and compress and store non-urgent data;

[0140] In this embodiment, urgent data is processed first, and non-urgent data is compressed and stored, which specifically includes the following steps:

[0141] Among the data collected by the GNSS receiver, data packets marked as urgent data are preferentially transmitted to the central processing system for real-time analysis and processing, and a predetermined communication protocol is used to ensure the stability and timeliness of data transmission. Data packets marked as non-urgent data are compressed using a data compression algorithm, and the compressed data is stored in a local storage device or cloud storage system. The stored compressed data is regularly uploaded to the central database for archiving and backup to reduce storage space occupancy and maintain data integrity.

[0142] In the data processing collected by the GNSS receiver, the system first prioritizes the transmission of data packets marked as urgent data to the central processing system for real-time analysis and processing to ensure timely response to potential risks and abnormal situations; urgent data is transmitted through high-priority communication channels, using TCP / IP protocol or MQTT protocol to ensure the stability and timeliness of data transmission. For data packets marked as non-urgent data, the system uses compression algorithms (such as gzip or LZ4) to compress them to reduce the data volume, and stores the compressed data in local storage devices or cloud storage systems. The stored compressed data is regularly uploaded in batches to the central database for archiving and backup. In this way, the use of storage space can be optimized, the demand for transmission bandwidth can be reduced, and urgent data can be prioritized, timely warnings and responses to potential risks can be given, and the efficiency and security of system operation can be maintained.

[0143] Detect changes in the amount of urgent data to be processed and changes in the processing capacity of the GNSS receiver in real time, evaluate whether the GNSS receiver has spare processing capacity to process non-urgent data, and make corresponding adjustments based on the evaluation results.

[0144] In this embodiment, the processing amount change of urgent data and the processing capacity change of the GNSS receiver are detected in real time, whether the GNSS receiver has spare processing capacity to process non-urgent data is evaluated, and corresponding adjustments are made according to the evaluation results, which specifically includes the following steps:

[0145] Obtain the amount of urgent data processing and the change in GNSS receiver processing capacity over a period of time;

[0146] Obtaining the processing volume of urgent data and the change in the processing capacity of the GNSS receiver within a period of time can be achieved through system log records, performance monitoring tools and real-time data acquisition modules. Specifically, the processing volume of urgent data can be obtained by recording and analyzing the processing records in the system log. The software can query the log file regularly and count the number of urgent data processed within a specified time period. For the change in the processing capacity of the GNSS receiver, key indicators such as the CPU usage, memory occupancy and network bandwidth utilization of the receiver can be monitored in real time through performance monitoring tools (such as Prometheus, Zabbix, etc.), and the changes in these indicators within a specified time period can be recorded. The software can use the API interface of these monitoring tools to obtain real-time data of processing capacity at regular intervals and calculate its change. In these ways, the system can effectively obtain the processing volume of urgent data and the change in processing capacity, providing accurate data support for subsequent evaluation and adjustment.

[0147] Analyze the changes in the processing volume of urgent data and the processing capacity of the GNSS receiver over a period of time, and generate the urgent data processing rate and the idle capacity coefficient respectively;

[0148] To generate the urgent data processing rate and the idle capacity coefficient respectively, first, the software calculates the urgent data processing rate by counting the number of urgent data processed within the specified time period. Specifically, the urgent data processing rate can be calculated by the following formula: Urgent data processing rate = (total amount of urgent data processed) / (total time within the specified time period). Next, the software calculates the average processing capacity of the receiver and further calculates the idle capacity by real-time monitoring of key indicators such as the CPU usage, memory occupancy, and network bandwidth utilization of the GNSS receiver. The idle capacity coefficient can be calculated by the following formula: Idle capacity coefficient = 1-(average processing capacity / maximum processing capacity). Among them, the average processing capacity is the average value of the processing capacity at each moment within the specified time period, and the maximum processing capacity is the design upper limit of the GNSS receiver. Through these calculations, the software can generate the urgent data processing rate and the idle capacity coefficient, providing a basis for subsequent evaluation and adjustment.

[0149] Determining a critical data processing rate threshold and an idle capacity factor threshold;

[0150] Determining the thresholds for the urgent data processing rate and the idle capacity factor can be achieved through a combination of historical data analysis, performance benchmarking, and machine learning algorithms. First, the software can collect and analyze a large amount of historical data to count the range and distribution of the urgent data processing rate and the idle capacity factor under different workloads and conditions. Use data analysis tools (such as Python's Pandas and NumPy) to calculate statistics such as the mean, standard deviation, and percentile of these data to determine a reasonable threshold range. Second, through performance benchmarking, the GNSS receiver is systematically tested in a controlled environment to record the processing performance and capacity under different load conditions, and further verify and adjust the thresholds. Finally, machine learning algorithms (such as cluster analysis and classification algorithms) are used to model and train historical data and test data to optimize threshold settings. The software can use algorithms in the scikit-learn library for model training and verification to find the optimal threshold that can effectively distinguish between normal and abnormal states. In these ways, the software can dynamically adjust and determine the thresholds for the urgent data processing rate and the idle capacity factor to ensure their accuracy and adaptability.

[0151] The urgent data processing rate and the idle capacity factor are compared with the urgent data processing rate threshold and the idle capacity factor threshold respectively to evaluate whether the GNSS receiver has spare processing capacity to process non-urgent data, and make corresponding adjustments based on the evaluation results. The specific analysis is as follows:

[0152] If the urgent data processing rate is greater than the urgent data processing rate threshold and the idle capacity factor is greater than the idle capacity factor threshold, the GNSS receiver has spare processing capacity to process the non-urgent data, and decompresses and processes the compressed and stored non-urgent data;

[0153] When the urgent data processing rate is greater than the urgent data processing rate threshold and the idle capacity factor is greater than the idle capacity factor threshold, it indicates that the current processing capacity of the GNSS receiver can cope with the processing requirements of urgent data, and the system has sufficient remaining processing resources to process non-urgent data. Specifically, the urgent data processing rate is higher than the threshold, indicating that the system can efficiently process all data marked as urgent, and the idle capacity factor is higher than the threshold, indicating that the system still has sufficient CPU, memory and bandwidth resources unused after processing the urgent data. In this case, the software will automatically start the processing flow for non-urgent data. First, the system will decompress the stored non-urgent data and use an efficient decompression algorithm (such as gzip or LZ4) to restore the compressed data to a usable state. Then, the system will perform routine processing and analysis on the decompressed non-urgent data according to the predetermined processing rules, including storage, recording, monitoring and other operations. In this way, the rational use of system resources is ensured, which not only ensures the priority processing of urgent data, but also makes full use of the remaining resources to process non-urgent data, thereby optimizing the overall performance and stability of the system.

[0154] If the urgent data processing rate is greater than the urgent data processing rate threshold and the idle capacity factor is greater than the idle capacity factor threshold, the GNSS receiver has no spare processing capacity to process the non-urgent data, and does not decompress and process the compressed and stored non-urgent data;

[0155] When the urgent data processing rate is not greater than the urgent data processing rate threshold or the idle capacity factor is not greater than the idle capacity factor threshold, it indicates that the current processing capacity of the GNSS receiver is insufficient to cope with the processing requirements of urgent data and non-urgent data at the same time. Specifically, if the urgent data processing rate fails to exceed its threshold, it means that the system has approached or reached its maximum processing capacity when processing urgent data. At this time, the system needs to concentrate resources to prioritize the processing of urgent data to ensure the completion of key tasks; if the idle capacity factor fails to exceed its threshold, it indicates that the system has insufficient CPU, memory and bandwidth resources left after processing urgent data and cannot bear the additional load. Therefore, in this case, the software will determine that the system has no spare processing capacity to process non-urgent data. In order to prevent system overload and performance degradation, the system will suspend the decompression and processing of compressed and stored non-urgent data. In specific implementation, the software will continuously monitor system resources and processing capacity. When it is detected that the urgent data processing rate and the idle capacity factor fail to meet the set threshold conditions at the same time, the task priority will be automatically adjusted to ensure that the processing of urgent data is not affected, while non-urgent data will remain in a compressed storage state and wait for system resources to recover to a sufficient level before processing. This strategy can ensure the stability of the system under high load and the smooth completion of key tasks, avoiding system crashes or performance bottlenecks caused by improper resource allocation.

[0156] The above formulas are all dimensionless and numerical calculations. The formula is a formula for the most recent real situation obtained by collecting a large amount of data and performing software simulation. The preset parameters in the formula are set by technicians in this field according to actual conditions.

[0157] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless (e.g., infrared, wireless, microwave, etc.). 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 containing one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

[0158] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0159] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0160] In the several embodiments provided in the present application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0161] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0162] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0163] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for monitoring the safety of a reservoir drainage and flood control project, characterized in that: The specific steps include: Analyze multiple reservoir data collected by the GNSS receiver in real time to determine whether the GNSS receiver needs to increase the data collection frequency and processing capacity. If the GNSS receiver does not need to increase the data collection frequency and processing capacity, the GNSS receiver continues to maintain the current working state for monitoring. If the GNSS receiver needs to increase the data collection frequency and processing capacity, continue with the following steps; Increasing the data collection frequency and processing capacity of GNSS receivers where such frequency and processing capacity are required; In the process of increasing the data collection frequency and processing capacity of the GNSS receiver, obtain and analyze the operating status information of the GNSS receiver, evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and make corresponding solutions based on the evaluation results; Acquire and analyze all data collected by the GNSS receiver, evaluate the urgency of each data collected by the GNSS receiver, and classify each data collected by the GNSS receiver into urgent data and non-urgent data based on the evaluation results, when the increase in the data collection frequency and processing capacity of the GNSS receiver affects its normal use; Prioritize urgent data, and compress and store non-urgent data; Detect changes in the amount of urgent data to be processed and changes in the processing capacity of the GNSS receiver in real time, evaluate whether the GNSS receiver has spare processing capacity to process non-urgent data, and make corresponding adjustments based on the evaluation results.

2. The reservoir drainage and flood control engineering safety monitoring method according to claim 1 is characterized in that: In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver is obtained and analyzed, and the degree of improvement in the data collection frequency and processing capacity of the GNSS receiver is evaluated to see whether it will affect its normal use, and corresponding solutions are taken according to the evaluation results, which specifically include the following steps: In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the operating status information of the GNSS receiver is obtained and pre-processed; Extracting load performance data and throughput data from the operating status information of the GNSS receiver, and analyzing the extracted load performance data and throughput data respectively to generate a device load factor and a data throughput index; The generated device load factor and data throughput index are used to construct a data evaluation model to generate an evaluation coefficient; The generated evaluation coefficient is compared with the pre-set evaluation coefficient threshold to evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and corresponding solutions are taken according to the evaluation results.

3. The reservoir drainage and flood control engineering safety monitoring method according to claim 2 is characterized in that: The logic for obtaining the device load factor and data throughput index is as follows: In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the load performance data in the operating status information of the GNSS receiver is extracted, including the CPU usage rate, memory occupancy rate and corresponding time points at different times within a period of time, and the CPU usage rate and memory occupancy rate at different times within a period of time are represented by functions CPU(t) and MEM(t) according to the time series, respectively, as the time point, and the time period is defined as [t1, t2]; Calculate the equipment load factor. The specific calculation formula is as follows: In the formula, LC is the device load factor, and ω1 and ω2 are weight coefficients used to adjust the importance of CPU usage and memory usage when calculating the device load factor; In the process of improving the data collection frequency and processing capacity of the GNSS receiver, the throughput data in the operating status information of the GNSS receiver is extracted, including the data collection rate, data transmission rate and corresponding time points at different times within a period of time, and the data collection rate and data transmission rate at different times within a period of time are represented by functions ACQ(T) and TRS(T) according to the time series, T is the time point, and the time period is defined as [T1, T2]; Get the maximum data acquisition rate and maximum data transmission rate of the GNSS receiver. After getting them, calibrate the maximum data acquisition rate and maximum data transmission rate of the GNSS receiver as ACQ respectively. max and TRS max ; Calculate the data throughput index. The specific calculation formula is as follows: Where TI is the data throughput index, ω3 and ω4 are weight coefficients used to adjust the importance of data acquisition rate and data transmission rate in calculating the data throughput index.

4. The reservoir drainage and flood control engineering safety monitoring method according to claim 3 is characterized in that: The generated equipment load coefficient LC and data throughput index TI are used to construct a data evaluation model, and the evaluation coefficient QG is generated through weighted summation.

5. The reservoir drainage and flood control engineering safety monitoring method according to claim 4 is characterized in that: The generated evaluation coefficient QG is compared with the pre-set evaluation coefficient threshold QG yz Compare and evaluate whether the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, and make corresponding solutions based on the evaluation results. The specific analysis is as follows: If QG≤QG yz , the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will not affect its normal use. The GNSS receiver continues to maintain or increase the current data collection frequency and processing capacity, and the system operates normally; If QG>QG yz , the degree of increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use. The GNSS receiver stops increasing the data collection frequency and processing capacity and reduces the data collection frequency and processing capacity. At the same time, a system warning is triggered and the staff is notified through the mobile terminal.

6. The reservoir drainage and flood control engineering safety monitoring method according to claim 5 is characterized in that: In the case where the increase in the data collection frequency and processing capacity of the GNSS receiver will affect its normal use, all data collected by the GNSS receiver are acquired and analyzed, the urgency of each data collected by the GNSS receiver is evaluated, and the data collected by the GNSS receiver is divided into urgent data and non-urgent data according to the evaluation result, which specifically includes the following steps: Acquire all data collected by the GNSS receiver, and pre-process all data collected by the acquired GNSS receiver; Extracting critical information from each data collected by the pre-processed GNSS receiver; Analyze the urgent information of each data collected by the GNSS receiver, and generate a data value variation coefficient and a data value deviation coefficient of each data respectively; An urgency assessment model is constructed using the data value variation coefficient and the data value deviation coefficient of each generated data to generate an urgency coefficient. The urgency coefficient of each generated data is compared with a preset urgency coefficient threshold to evaluate the urgency of each data collected by the GNSS receiver, and the data collected by the GNSS receiver is divided into urgent data and non-urgent data according to the evaluation results.

7. The reservoir drainage and flood control engineering safety monitoring method according to claim 6 is characterized in that: The logic for obtaining the data value variation coefficient and data value deviation coefficient of each data is as follows: Extract the urgent information of each data collected by the preprocessed GNSS receiver, including the data value of each data collected by the GNSS receiver at different times within a period of time, and calibrate the data value of each data collected by the GNSS receiver at different times within a period of time as represents the data value of the i-th data collected by the GNSS receiver at time m within a period of time, i = 1, 2, 3, ..., g, m = 1, 2, 3, ..., k, g and k are both positive integers; Calculate the coefficient of variation of the data values ​​of each data. The specific calculation formula is as follows: In the formula, RC i is the coefficient of variation of the data value of the i-th data; Obtain the preset data value of each data collected by the GNSS receiver. After obtaining, calibrate the preset data value of each data collected by the GNSS receiver as Calculate the data value deviation coefficient of each data. The specific calculation formula is as follows: In the formula, DD i is the data value deviation coefficient of the i-th data.

8. The reservoir drainage and flood control engineering safety monitoring method according to claim 7 is characterized in that: The data value variation coefficient RC of each generated data i And the data value deviation coefficient DD i Construct an urgency assessment model and generate the urgency coefficient JP through weighted summation i , and generate the urgency coefficient JP of each data i The preset urgency factor threshold JP yz Compare and evaluate the urgency of each data collected by the GNSS receiver, and divide the data collected by the GNSS receiver into urgent data and non-urgent data according to the evaluation results. The specific division is as follows: If JP i ≤JP yz , the urgency of the i-th data collected by the GNSS receiver is low, and the data is classified as non-urgent data; If JP i >JP yz , the urgency of the i-th data collected by the GNSS receiver is high, and the data is classified as urgent data.

9. The reservoir drainage and flood control engineering safety monitoring method according to claim 8, characterized in that: Prioritize urgent data, and compress and store non-urgent data. Specifically, the following steps are included: Among the data collected by the GNSS receiver, data packets marked as urgent data are preferentially transmitted to the central processing system for real-time analysis and processing, and a predetermined communication protocol is used to ensure the stability and timeliness of data transmission. Data packets marked as non-urgent data are compressed using a data compression algorithm, and the compressed data is stored in a local storage device or cloud storage system, and the stored compressed data is regularly uploaded to the central database for archiving and backup.

10. The reservoir drainage and flood control engineering safety monitoring method according to claim 9, characterized in that: Real-time detection of changes in the processing volume of urgent data and changes in the processing capacity of the GNSS receiver, evaluation of whether the GNSS receiver has spare processing capacity to process non-urgent data, and corresponding adjustments based on the evaluation results, specifically including the following steps: Obtain the amount of urgent data processing and the change in GNSS receiver processing capacity over a period of time; Analyze the changes in the processing volume of urgent data and the processing capacity of the GNSS receiver over a period of time, and generate the urgent data processing rate and the idle capacity coefficient respectively; Determining a critical data processing rate threshold and an idle capacity factor threshold; The urgent data processing rate and the idle capacity factor are compared with the urgent data processing rate threshold and the idle capacity factor threshold respectively to evaluate whether the GNSS receiver has spare processing capacity to process non-urgent data, and make corresponding adjustments based on the evaluation results. The specific analysis is as follows: If the urgent data processing rate is greater than the urgent data processing rate threshold and the idle capacity factor is greater than the idle capacity factor threshold, the GNSS receiver has spare processing capacity to process the non-urgent data, and decompresses and processes the compressed and stored non-urgent data; If the urgent data processing rate is not greater than the urgent data processing rate threshold and the idle capacity coefficient is not greater than the idle capacity coefficient threshold, the GNSS receiver has no spare processing capacity to process the non-urgent data, and does not decompress and process the compressed and stored non-urgent data.