Cooperative operation and maintenance management system and method for heterogeneous low-altitude facilities

Abstract

The invention relates to the technical field of operation and maintenance management, in particular to a collaborative operation and maintenance management system and method for heterogeneous low-altitude facilities, and the system comprises a data unification module which is used for carrying out template mapping on fields in an original operation state sequence, carrying out normalization processing to generate a state vector with a unified structure, and storing the state vector with the unified structure; splicing the state vectors to generate a standard state vector sequence; the abnormal equipment identification module is used for calculating an average value of the collaborative disturbance scores in the sliding window, and screening equipment meeting conditions according to the average value to form a candidate abnormal equipment list; the exception judgment module is used for generating a prediction state of the candidate exception equipment list in a historical normal mode through a pre-trained model, and performing exception credibility scoring to construct a high-credibility exception equipment set; and the task suggestion generation module is used for calculating a comprehensive priority score of the high-credibility abnormal equipment set through a scoring function, and outputting a task suggestion based on the comprehensive priority score and an actual operation and maintenance process.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of operation and maintenance, and in particular to a collaborative operation and maintenance system and method for heterogeneous low-altitude facilities. BACKGROUND

[0002] With the rapid development of low-altitude economy, the deployment scale of unmanned aerial vehicles, low-altitude communication base stations, environmental monitoring sensors and other facilities in urban operation guarantee, traffic monitoring, emergency disposal and logistics services continues to expand. Compared with traditional ground facilities, low-altitude facilities have a wider distribution range, a more complex operating environment, and a high degree of diversity in device types and manufacturer sources, which makes operation and maintenance face higher uncertainty and complexity. On the one hand, different types of low-altitude devices differ significantly in data structure, communication protocol and operating indicators. Existing operation and maintenance systems often rely on customized adaptation or single device models, making it difficult to achieve unified management within the same platform. On the other hand, low-altitude facilities are operated in environments with wind disturbance, electromagnetic interference, high temperature and humidity for a long time, and the device state fluctuates frequently. Abnormal behavior has obvious sporadicity and linkage. Relying solely on single-device threshold or local indicators can easily misjudge short-term disturbances as faults or ignore systematic risks with propagation characteristics. In addition, most existing technologies remain at the level of abnormal alarm or state display, lacking a depiction of the collaborative relationship between devices and a complete linkage mechanism from abnormal identification to operation and maintenance disposal, resulting in operation and maintenance responses that rely heavily on human experience, with low processing timeliness and resource utilization efficiency. Even if some schemes introduce prediction models or centralized analysis methods, they generally lack adaptability to heterogeneous devices, have limited ability to identify real abnormalities, and are difficult to form executable operation and maintenance decisions. Therefore, in the context of high-density deployment of low-altitude facilities and multi-device collaborative operation, how to simultaneously manage heterogeneous devices while accurately identifying systematic abnormalities and forming an executable operation and maintenance loop has become a key technical problem that needs to be solved in the field of low-altitude facility operation and maintenance. SUMMARY

[0003] To solve the above problems, the present application provides a collaborative operation and maintenance system and method for heterogeneous low-altitude facilities.

[0004] To achieve the above purpose, the technical solution adopted by the present application is: The collaborative operation and maintenance system for heterogeneous low-altitude facilities comprises: A data unification module is configured to obtain an original operating state sequence of a device, perform template mapping on fields in the original operating state sequence through a preset state field template, perform normalization processing on the mapped fields, generate a state vector with a unified structure, and splice the state vector to generate a standard state vector sequence. An abnormal device identification module is configured to calculate a collaborative residual between devices by a collaborative residual function, calculate a collaborative disturbance score of the devices based on the collaborative residual, smooth the collaborative disturbance score by a sliding window, calculate an average value of the collaborative disturbance score within the sliding window, and filter devices meeting a condition to form a candidate abnormal device list according to the average value; An abnormality judgment module is configured to predict and reconstruct a state of the candidate abnormal device list at a current time by a pre-trained model, generate a predicted state of the candidate abnormal device list in a historical normal mode, calculate a difference value between the current state and the predicted state of the candidate abnormal device list, generate an abnormality confidence score, and construct a high-confidence abnormal device set according to the abnormality confidence score. A task suggestion generation module is configured to calculate a comprehensive priority score of the high-confidence abnormal device set by a scoring function, and output a task suggestion based on the comprehensive priority score and an actual operation and maintenance process.

[0005] The collaborative operation and maintenance management method for heterogeneous low-altitude facilities includes: An original operation state sequence of a device is obtained, a field in the original operation state sequence is mapped by a preset state field template, the mapped field is normalized to generate a state vector with a uniform structure, and the state vector is spliced to generate a standard state vector sequence. A collaborative residual between devices is calculated by a collaborative residual function, a collaborative disturbance score of the devices is calculated based on the collaborative residual, the collaborative disturbance score is smoothed by a sliding window, and an average value of the collaborative disturbance score within the sliding window is calculated, and devices meeting a condition are filtered to form a candidate abnormal device list according to the average value. A state of the candidate abnormal device list at a current time is predicted and reconstructed by a pre-trained model, a predicted state of the candidate abnormal device list in a historical normal mode is generated, a difference value between the current state and the predicted state of the candidate abnormal device list is calculated, an abnormality confidence score is generated, and a high-confidence abnormal device set is constructed according to the abnormality confidence score. A comprehensive priority score of the high-confidence abnormal device set is calculated by a scoring function, and a task suggestion is output based on the comprehensive priority score and an actual operation and maintenance process.

[0006] Preferably, the state field template includes a power supply state, a temperature state, and a signal strength state.

[0007] Preferably, parameters of the collaborative residual function include a standard Euclidean residual term, an absolute difference term, a weight coefficient, and a structure regularity strength coefficient, the standard Euclidean residual term is used to represent a main difference between devices at a current state, the absolute difference term is used to amplify local high-amplitude deviation, and the structure regularity strength coefficient is used to adjust a degree of influence of a collaborative topology.

[0008] Preferably, the pre-trained model is an autoencoder structure, which includes an input layer, a single hidden layer, and an output layer. The training of the model is completed at the device level or at an edge node.

[0009] Preferably, the predicted state is generated by a prediction function, the parameters of which include the device's state vector at the previous time step, the weights and biases of the coding layer, the nonlinear activation operator, and the parameters of the decoding layer.

[0010] Preferably, the anomaly credibility score is generated by a credibility evaluation function, the parameters of which include the direct deviation of the device's current state from its own historical normal mode, the cooperative disturbance score, the average of the cooperative disturbance scores of all candidate devices at the current time point, and the adjustment coefficient.

[0011] Preferably, the parameters of the scoring function include anomaly confidence score, cooperative perturbation score, and adjustment factor.

[0012] Preferably, the task recommendations include remote command, on-site inspection, and continuous monitoring.

[0013] Preferably, after outputting task suggestions based on comprehensive priority scoring and actual operation and maintenance processes, the method further includes: The comprehensive priority score and task suggestions are structurally encapsulated and output to the task scheduling platform. The beneficial effects of this invention are as follows: This invention first establishes a unified model for the operational status of different types of low-altitude equipment, eliminating differences in data structure and numerical scale between devices and providing a consistent foundation for cross-device analysis. Based on this, by constructing a collaborative state residual structure among devices, it identifies key devices that significantly disrupt collaborative operation from a system-wide perspective, avoiding isolated judgments from a single device's perspective. Furthermore, this invention combines the historical operational characteristics of each device to determine the authenticity of candidate abnormal devices, thus distinguishing between actual device degradation and apparent anomalies caused by environmental disturbances or collaborative propagation. Finally, this invention integrates anomaly credibility with the degree of system collaborative impact to generate maintenance task suggestions that match the device type and control capabilities, achieving closed-loop management from anomaly identification to maintenance execution. Through the above technical solutions, this invention not only improves the accuracy and stability of anomaly identification for heterogeneous low-altitude facilities but also provides clear execution directions for maintenance decisions, effectively enhancing the response efficiency and actual availability of collaborative maintenance of low-altitude facilities. Attached Figure Description

[0014] Figure 1 This is a block diagram of a collaborative operation and maintenance management system for heterogeneous low-altitude facilities in a specific embodiment of the present invention; Figure 2 This is a flowchart of a collaborative operation and maintenance management method for heterogeneous low-altitude facilities in a specific embodiment of the present invention. Detailed Implementation

[0015] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0016] Please refer to Figure 1 As shown, this invention proposes a collaborative operation and maintenance management system for heterogeneous low-altitude facilities, including: The data unification module is used to obtain the original operating state sequence of the device, perform template mapping on the fields in the original operating state sequence through a preset state field template, and normalize the mapped fields to generate a state vector with a unified structure. The state vector is then concatenated to generate a standard state vector sequence. The abnormal device identification module is used to calculate the collaborative residual between devices through the collaborative residual function, calculate the collaborative disturbance score of the devices based on the collaborative residual, smooth the collaborative disturbance score through a sliding window, calculate the average value of the collaborative disturbance score within the sliding window, and filter the devices that meet the conditions to form a candidate abnormal device list based on the average value. The anomaly detection module is used to predict and reconstruct the current state of the candidate abnormal device list using a pre-trained model, generate the predicted state of the candidate abnormal device list under historical normal mode, calculate the difference between the current state and the predicted state of the candidate abnormal device list, generate an anomaly confidence score, and construct a set of highly reliable abnormal devices based on the anomaly confidence score. The task suggestion generation module is used to calculate the comprehensive priority score of a set of highly reliable abnormal devices through a scoring function, and output task suggestions based on the comprehensive priority score and the actual operation and maintenance process.

[0017] Please refer to Figure 2 As shown, in another aspect of the present invention, a collaborative operation and maintenance management method for heterogeneous low-altitude facilities is also proposed, including: Step 1: Obtain the original operating state sequence of the device. Map the fields in the original operating state sequence using a preset state field template, and normalize the mapped fields to generate a state vector with a unified structure. Concatenate the state vectors to generate a standard state vector sequence. Specifically, this includes: This step is used to construct a unified representation of the state of low-altitude equipment, resolving inconsistencies in data structure, indicator meaning, and numerical scale among heterogeneous devices. Different equipment types, such as drones, communication base stations, and environmental sensors, collect data fields that differ, making direct collaborative analysis in the same space impossible. This step uses a two-stage processing method—field template mapping and numerical normalization—to transform the raw collected data into a structurally unified and comparable time-series state vector, providing standard input for subsequent collaborative anomaly identification.

[0018] The input is the sequence of raw operating statuses collected by each device within a certain time period, denoted as: ; in, Indicates the first The original state sequence of each device is obtained from the device body by the edge device or embedded acquisition unit through a communication interface (such as RS485, serial port, Ethernet); This indicates the length of the time window covered by the sequence; Indicates the first The device in the The original state vector at each point in time has a field structure that varies depending on the type of device. For example, a drone may contain battery voltage, current, flight control temperature, and GPS signal strength, while an environmental sensor may contain air temperature, humidity, and power supply status.

[0019] First, template mapping is performed on the field structure. The system predefines a set of status field templates that are shared across devices. Each of them This represents a general device status attribute, such as power supply status, temperature status, signal strength status, etc. The device's original fields are mapped to this template according to their meaning; missing fields are filled with default values, such as... or .

[0020] To eliminate the problem of inconsistent numerical scales, each mapping field is normalized: ; in, Indicates the first The device at the time point Above, the first after field mapping One original indicator value; For the first The average value of each field in historical device data is calculated offline during the deployment period; The corresponding standard deviation; These are normalized state values, which are comparable.

[0021] The normalized results of each dimension are combined into a state vector with a unified structure: ; The final standard state vector sequence is formed by concatenating multiple time points: ; Each of them The normalized device state vector has a fixed dimension. This structure is shared by all devices. This state sequence will be used as input in the next step to construct the inter-device state residual matrix and anomaly filtering.

[0022] This solution achieves structural unification and numerical alignment of heterogeneous low-altitude equipment status data through field templates and standardization mechanisms, avoiding the complexity of modeling each equipment individually, and enabling collaborative status analysis between different equipment in the same space.

[0023] Step 2: Calculate the collaborative residuals between devices using the collaborative residual function. Based on the collaborative residuals, calculate the collaborative disturbance score of the devices. Smooth the collaborative disturbance score using a sliding window and calculate the average value of the collaborative disturbance score within the sliding window. Based on the average value, select devices that meet the criteria to form a candidate list of abnormal devices. Specifically, this includes: This step addresses the high-density deployment scenario of various types of low-altitude facilities by proposing a systematic anomaly identification method based on inter-device state coordination residual calculation. This method is used to screen candidate devices that currently cause the greatest interference to the overall system's coordinated state. Unlike traditional methods that rely on single-point threshold judgments or simple clustering, this step compares the state consistency among multiple devices and incorporates factors such as deployment area characteristics and device role differences. It introduces a structural residual regularization term to construct a more interpretable anomaly indicator system, thereby improving the identification accuracy and deployment adaptability in complex deployment environments.

[0024] The input is the standard state vector sequence output from the previous step. Each of them Indicates the first The device at the time point The standardized state vector on, As for the feature dimension, this vector structure was already based on a cross-device shared template in the previous step. The process is unified. All device data is synchronously cached by the edge gateway at a fixed sampling frequency (e.g., 5 seconds / time), and after time alignment, it is used as the input for this step.

[0025] Considering that low-altitude facilities often have dense local deployments and there are natural business or physical connections between some devices (such as the same power supply source, signal relay), if the state residuals between devices are compared without discrimination, it may underestimate the risk of linkage anomalies caused by some devices in their functional topologies. Therefore, in this step, a weighted collaborative residual modeling method combined with the deployment structure is designed, and a structural regularization term is introduced based on the traditional residual calculation to more effectively capture potential anomaly sources.

[0026] First, define the current time point the upper device and device The collaborative residual between them is , through the collaborative residual function , specifically: ; where is the standard Euclidean residual term, representing the main difference in the current states of two devices; is the absolute difference term used to amplify local high-amplitude deviations, avoiding important dimension anomalies being submerged by the averaging effect; is the weight coefficient of device and in the deployment topology, which is set according to the actual physical deployment or task coupling relationship (for example, sub-devices sharing the same power supply or under the same gateway can be set as , and those without direct association are ); is the structural regularization strength coefficient, which adjusts the influence degree of the collaborative topology, and its value range is usually between , set during the deployment period.

[0027] Through this residual structure design, not only the general state differences between devices are measured, but also structural knowledge and deployment logic are injected into the residual term, so that even when some devices show slight anomalies but their connection relationships are important, they can be significantly identified. This design is especially applicable to core devices with high collaborative dependencies in low-altitude facilities, such as signal relay nodes and key power nodes.

[0028] Next, calculate the total system perturbation degree of device at time as: ; where represents the set of adjacent devices that have deployment associations or task collaboration relationships with device . This total perturbation value represents the overall collaborative perturbation degree caused by device in the current system structure. The larger the value, the more likely it is to be the cause or key node of the current systematic anomaly.

[0029] To improve the stability of the results, the system... Smoothing is achieved using a sliding window, with the window length as the parameter. The average value over (e.g., 3 periods) is used as the final cooperative perturbation score, while a dynamic threshold is set. Select the one that satisfies The candidate set of devices: ; in express The mean within the sliding window, It can be dynamically adjusted based on the number of devices and risk strategies, such as setting it to all devices in the current area. mean plus Double the standard deviation.

[0030] The above mechanism not only considers the degree of deviation of the device state itself, but also integrates the structural position and collaborative value of the device in actual deployment. Through the combined effect of regularization terms and topology coupling weights, it improves the structural sensitivity and engineering adaptability of anomaly identification.

[0031] Step 3: Using a pre-trained model, predict and reconstruct the current state of the candidate abnormal device list to generate the predicted state of the candidate abnormal device list under historical normal mode. Calculate the difference between the current state and the predicted state of the candidate abnormal device list to generate an anomaly confidence score. Based on the anomaly confidence score, construct a set of highly reliable abnormal devices, specifically including: This step, based on collaborative residual screening, determines the "authenticity" of candidate anomalous devices. Its core objective is not to rediscover anomalies, but rather to distinguish between "genuine device anomalies within structural anomalies" and "apparent anomalies caused by collaborative propagation, environmental disturbances, or entanglement with neighboring devices." In the previous step, the system has already used a standard state vector sequence... A collaborative residual structure among devices was constructed, and a set of candidate abnormal devices was output. and the corresponding cooperative perturbation score These results indicate that the equipment is suspected of anomalies at the "group level," but this does not directly equate to the equipment itself having entered an abnormal operating state. This step utilizes the equipment's historical operating trajectory to further determine this issue.

[0032] The input consists of two parts. The first part is the standard state vector sequence output from step one. ,in Indicates device In time The first part is the standardized state vector, which has undergone cross-device field alignment and numerical normalization; the second part is the candidate device set output from step two. and the corresponding cooperative perturbation score This step is only for... The devices in the model perform the modeling and judgment, while the other devices do not participate in the calculation, so as to ensure that the method focuses on the "critical nodes that still need to be confirmed after a systemic anomaly".

[0033] For each candidate device The system does not introduce cross-device samples or use a global model; instead, it constructs an individualized normal state baseline solely using the device's own historical state sequences. Specifically, it selects a sub-sequence of states within a recent time window. A lightweight autoencoder structure is trained to characterize the state change patterns of the device under conditions of "no obvious faults". This autoencoder structure consists of an input layer, a single hidden layer, and an output layer. The hidden layer dimension is smaller than the state vector dimension, used to compress and extract stable operating features of the device. Model training is completed at the device level or edge nodes, using only the device's own historical data to avoid interference from differences in the operation of different devices on the judgment results.

[0034] After training, the model is used to predict and reconstruct the current state of the device. The expected state representation under the constraints of the historical normal mode is obtained through the prediction function, specifically: ; in, This is the standard state vector of the device at the previous moment; and These are the weights and biases of the coding layer, used to map the input state to a low-dimensional implicit representation; It is a nonlinear activation operator used to express the nonlinear change characteristics of the device state; and These are the parameters for the decoding layer, used to restore the implicit representation to the state space; This refers to the model's prediction of the current state under the assumption that the equipment itself is operating normally.

[0035] After obtaining the predicted state, the system compares it with the current actual state. With predicted state The degree of anomaly is measured by the difference in parameters. Considering that in low-altitude facility scenarios, some anomalies are often accompanied by sudden changes in key indicators rather than overall drift, this step introduces a collaborative perception regularization term in addition to the basic residual term. This allows the judgment result to simultaneously reflect "the degree of deviation of the equipment itself" and "its importance in system collaboration," thus constructing an anomaly credibility score. The specific credibility evaluation function is as follows: ; in, This indicates the degree of direct deviation of the device's current state from its historical normal mode; The output of step two is the device cooperative disturbance score; This represents the average of the cooperative perturbation scores of all candidate devices at the current time point, used to eliminate the impact of scale. The adjustment coefficient controls the weight of collaborative information in the judgment of anomaly authenticity. The implication of this design is that when a device not only deviates significantly from its own state but also acts as a high-disturbance node in the system's collaborative structure, its anomaly credibility will be significantly amplified, which is more in line with the actual operation and maintenance logic of "prioritizing the handling of critical node failures" in low-altitude facilities.

[0036] Through the above mechanism, this step avoids false alarms caused by judging solely based on model reconstruction errors, and also avoids the risk of directly equating collaborative residuals with equipment failures. Instead, it organically combines the two to form a joint discrimination method of "individual historical consistency + system collaborative impact." The output includes two results. The first is the anomaly confidence score for each candidate device at the current time. This score will serve as an important input for task prioritization in subsequent operation and maintenance decisions; the second is a set of highly reliable abnormal devices. The set consists of satisfying Devices exceeding a preset threshold constitute the target devices that need to enter the operation and maintenance execution phase.

[0037] Step 4: Calculate the comprehensive priority score of the set of highly reliable abnormal devices using a scoring function. Based on the comprehensive priority score and the actual operation and maintenance process, output task suggestions, specifically including: This step aims to further generate task types and output maintenance recommendations based on the anomaly assessment results generated in the previous stage, thereby achieving a closed-loop transformation from anomaly detection to collaborative maintenance response. Low-altitude infrastructure networks are typically deployed in complex areas such as cities, mountains, and transportation corridors. Different types of equipment (such as drones, communication base stations, and environmental sensors) have significantly different operating characteristics and controllability. Therefore, when generating task recommendations, it is necessary to consider not only the severity of the anomaly but also factors such as equipment type, remote controllability, and communication link quality to ensure that the task recommendations are feasible and engineering-practical. The input data in this step all come from the completed identification and evaluation modules, including the anomaly credibility score of the equipment. (Derived from the combination of modeling residuals and structural regularization), cooperative perturbation score (Generated by residual matrix modeling), both measures whether the device is "truly broken" and whether "its failure will affect others," and must be considered together. In addition, deployment-period registration data such as device type labels and control method support tags are introduced to assist in decision generation.

[0038] The system first targets the set of highly reliable anomalous devices confirmed in step three. Calculate the overall task priority score for each device. This score is used for scheduling and prioritizing multiple devices. It is an indicator that integrates anomaly confidence with cooperative disturbances. Its structural design takes into account both the abnormal behavior of the devices themselves and their structural impact on the system. The specific scoring function is calculated as follows: ; in For equipment The current anomaly confidence score is derived from the modeling residual calculation results of the third stage; The cooperative disturbance score of the equipment in the system structure is derived from the residual propagation graph analysis module; As an adjustment factor, it is recommended to set it to [value missing]. arrive The amplification effect of the cooperative terms is limited. This function structure guarantees that when... Larger (the equipment itself has obvious abnormalities) and When the anomaly is also large (and still spreading), the device will receive a higher priority score. In actual deployments, such devices should be prioritized for processing tasks, such as drone backhaul nodes located on main traffic arteries and low-altitude communication relay equipment.

[0039] After obtaining the task priority score, the system enters the task suggestion generation phase. The goal of task suggestions is to output a decision on "how to handle" each device and specify the task type. Based on actual operation and maintenance processes, task types mainly include three categories: remote command execution, on-site dispatch for repair, and continued monitoring and observation. The judgment logic not only relies on the score but also incorporates the control capability flags and environmental constraint parameters configured in the device attribute table. The task suggestion generation logic is as follows: ; in Indicates device The task suggestion type at the current moment, , The trigger thresholds for "serious anomalies" and "general anomalies" are respectively set (usually the upper 1 / 4 quantile and mean of the anomaly score), and the specific values ​​can be set by the system administrator before deployment or dynamically adjusted. The "remote control support flag" used in task type determination comes from the device registration information database and is configured when the device first connects to the platform. For example, most communication base stations support remote parameter adjustment, but some environmental sensors and devices deployed in mountainous areas cannot be remotely operated. Therefore, even if their anomaly score is high, they can only be suggested to generate a "field maintenance" task. In addition, for devices whose current signal strength is below the set threshold, even if they have remote capabilities, the system can predict the risk of remote failure through the fault simulation module, thereby prioritizing the dispatch of manual tasks and avoiding the operational redundancy of "delivery failure". Here, remote failure refers to not receiving a valid acknowledgment from the device side or detecting that the communication link is unreachable during the most recent command delivery process. This status is provided by the device communication monitoring module.

[0040] Practical task suggestions include not only task type It will also associate recommended execution methods. For example, for "remote command" tasks, it will generate recommended instruction types (such as restart, parameter adjustment); for "on-site maintenance" tasks, it will generate optimal response path suggestions (such as entering the scheduling queue or creating a work order) based on the equipment deployment point coordinates and the distribution of the nearest accessible maintenance personnel. All task suggestion structures will ultimately be encapsulated in the following format: This information is then passed to the task scheduling platform or front-end display system for direct use by subsequent task management modules.

[0041] For example, a drone relay node deployed under a city bridge has an anomaly credibility score of [insert score here]. The cooperative disturbance score is The corresponding calculated priority score is approximately If the device supports remote control, the system will output a "remote command" task, suggesting that parameter adjustments and log restarts be attempted first. If the device with the same score is an environmental sensor deployed in a suburban area with poor communication quality, the system will output a "field maintenance" task and provide a scheduling route. This task suggestion mechanism, which dynamically generates suggestions based on the actual scenario, device attributes, and abnormal behavior, is one of the structural innovations of this invention in operation and maintenance decision-making.

[0042] The above embodiments are merely descriptions of preferred embodiments of the present invention and are not intended to limit the scope of the present invention. Various modifications and improvements made by those skilled in the art to the technical solutions of the present invention without departing from the spirit of the present invention should fall within the protection scope defined by the claims of the present invention.

Claims

1. A collaborative operation and maintenance management system for heterogeneous low-altitude facilities, characterized in that, include: The data unification module is used to obtain the original operating state sequence of the device, perform template mapping on the fields in the original operating state sequence through a preset state field template, and normalize the mapped fields to generate a state vector with a unified structure. The state vector is then concatenated to generate a standard state vector sequence. The abnormal device identification module is used to calculate the collaborative residual between devices through the collaborative residual function, calculate the collaborative disturbance score of the devices based on the collaborative residual, smooth the collaborative disturbance score through a sliding window, calculate the average value of the collaborative disturbance score within the sliding window, and filter the devices that meet the conditions to form a candidate abnormal device list based on the average value. The anomaly detection module is used to predict and reconstruct the current state of the candidate abnormal device list using a pre-trained model, generate the predicted state of the candidate abnormal device list under historical normal mode, calculate the difference between the current state and the predicted state of the candidate abnormal device list, generate an anomaly confidence score, and construct a set of highly reliable abnormal devices based on the anomaly confidence score. The task suggestion generation module is used to calculate the comprehensive priority score of a set of highly reliable abnormal devices through a scoring function, and output task suggestions based on the comprehensive priority score and the actual operation and maintenance process.

2. A collaborative operation and maintenance management method for heterogeneous low-altitude facilities, characterized in that, include: The original operating state sequence of the device is obtained, and the fields in the original operating state sequence are mapped using a preset state field template. The mapped fields are then normalized to generate a state vector with a unified structure. The state vectors are then concatenated to generate a standard state vector sequence. The collaborative residual between devices is calculated using a collaborative residual function. Based on the collaborative residual, the collaborative disturbance score of the devices is calculated. The collaborative disturbance score is smoothed using a sliding window, and the average value of the collaborative disturbance score within the sliding window is calculated. Based on the average value, devices that meet the criteria are selected to form a candidate list of abnormal devices. The candidate abnormal device list is predicted and reconstructed at the current time using a pre-trained model to generate the predicted state of the candidate abnormal device list under the historical normal mode. The difference between the current state and the predicted state of the candidate abnormal device list is calculated to generate an anomaly confidence score. A set of highly reliable abnormal devices is constructed based on the anomaly confidence score. The comprehensive priority score of the set of highly reliable abnormal devices is calculated using a scoring function, and task suggestions are output based on the comprehensive priority score and the actual operation and maintenance process.

3. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, The status field template includes power supply status, temperature status, and signal strength status.

4. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, The parameters of the cooperative residual function include a standard Euclidean residual term, an absolute difference term, a weighting coefficient, and a structural regularization strength coefficient. The standard Euclidean residual term is used to represent the main differences between devices in the current state, the absolute difference term is used to amplify local high-amplitude deviations, and the structural regularization strength coefficient is used to adjust the degree of cooperative topology influence.

5. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, The pre-trained model is an autoencoder structure, which includes an input layer, a single hidden layer, and an output layer. The training of the model is completed at the device level or at an edge node.

6. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 5, characterized in that, The predicted state is generated by a prediction function whose parameters include the device's state vector at the previous time step, the weights and biases of the coding layer, the nonlinear activation operator, and the parameters of the decoding layer.

7. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, The anomaly credibility score is generated through a credibility evaluation function, the parameters of which include the direct deviation of the device's current state from its own historical normal mode, the cooperative disturbance score, the average of the cooperative disturbance scores of all candidate devices at the current time point, and the adjustment coefficient.

8. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, The parameters of the scoring function include anomaly confidence score, cooperative perturbation score, and adjustment factor.

9. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, The task recommendations include remote command, on-site inspection, and continuous monitoring.

10. The collaborative operation and maintenance management method for heterogeneous low-altitude facilities according to claim 2, characterized in that, After outputting task suggestions based on comprehensive priority scoring and actual operation and maintenance processes, the following is also included: The comprehensive priority score and task suggestions are structurally encapsulated and output to the task scheduling platform.

Images