A network adaptive device running state remote monitoring method

Abstract

This invention discloses a remote monitoring method for the operational status of network-adaptive devices, relating to the field of industrial internet technology. The method includes configuring the data collection points of the monitored devices in a remote monitoring terminal, building a corresponding operation and maintenance rule base for the monitored devices on a monitoring server, and generating a monitoring strategy set. The monitoring strategy set is used to scan the data collection points in real time and sample device status signals. Through jitter reduction and anti-interference processing, stable signals are obtained. These stable signals are then entered into a status determination machine to evaluate signal quality and decision accuracy, generating a device status determination result. This invention is based on a retrieval path reachability status linkage and retransmission strategy, forming a continuous and verifiable status event stream. This balances transmission efficiency with real-time monitoring display, thereby ensuring the integrity, temporal consistency, and reliability of monitoring status in complex networks and high-concurrency scenarios.

Description

Technical Field

[0001] This invention relates to the field of industrial internet technology, and in particular to a method for remote monitoring of the operating status of fully network-adaptive devices. Background Technology

[0002] With the maturity of the Industrial Internet and Internet of Things (IoT) systems, remote monitoring technology for equipment operation status has gradually evolved from the early "local instrument / PLC + on-site duty" model to a layered architecture of "multi-source acquisition - network transmission - platform analysis - visualized operation and maintenance". To meet the access needs across regions and scenarios, communication links have also gradually expanded from a single dedicated line to Ethernet, Wi-Fi, cellular networks and their hybrid networking. At the platform level, message queues / publish-subscribe mechanisms, heartbeat keep-alive and work order linkage are commonly used to realize the flow, tracking and real-time display of status events on the monitoring interface, thereby supporting remote inspection, anomaly location and operation and maintenance closed loop.

[0003] In scenarios where multiple networks coexist and link quality fluctuates over time, existing solutions often employ fixed reporting channels or simple retry mechanisms, which are often unable to promptly determine and quantify the reachability status of remote reporting paths. Consequently, they struggle to support adaptive reporting path selection based on link status. Furthermore, in cases of link jitter, packet loss, or congestion, the lack of a tiered retransmission and deduplication receipt mechanism linked to reachability status can easily lead to delayed event reporting, duplicate transmissions, or periodic omissions, affecting the integrity of the status event stream and the real-time nature of monitoring and display. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a remote monitoring method for the operating status of network-adaptive devices to solve the problems of difficulty in real-time determination of remote reporting path reachability and insufficient linkage retransmission deduplication leading to discontinuous status event streams under network conditions.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: This invention provides a remote monitoring method for the operational status of network-adaptive devices. The method includes: configuring the data collection points of the monitored devices in a remote monitoring terminal; constructing a corresponding operation and maintenance rule base for the monitored devices on a monitoring server to generate a monitoring strategy set; using the monitoring strategy set to scan the data collection points in real time and sample device status signals; obtaining stable signals through de-jitter and anti-interference processing; inputting the stable signals into a status determination machine to evaluate signal quality and decision accuracy, and generating device status determination results; monitoring and evaluating the device status determination results to obtain a monitoring event set; processing monitoring events with different priorities according to event work order priorities, selecting appropriate remote reporting paths, and generating deduplicated event receipts; performing real-time determination of the reachability of the remote reporting paths based on the deduplicated event receipts, obtaining path reachability status, and selecting appropriate retransmission strategies to optimize data transmission efficiency based on path reachability status, generating a complete status event stream; and updating the device status based on the complete status event stream on the server and driving the remote monitoring interface to display the device operational status in real time, generating real-time data for the monitoring interface.

[0007] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for generating the monitoring strategy set are as follows: Select the monitored device in the remote monitoring terminal, enter the configuration process, add the collection points one by one in a fixed order and save them, and submit the collection points to the monitoring server through the remote monitoring terminal to obtain the collection point configuration package. Based on the data collection point configuration package, the monitoring server generates and saves operation and maintenance rule entries for each monitored device, accumulating them to form an operation and maintenance rule library. The operation and maintenance rule library is then associated with the data collection points to generate a monitoring strategy set.

[0008] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for obtaining a stable signal are as follows: The device status signals of the collection points are continuously sampled according to the scanning order and scanning cycle specified in the monitoring strategy set to form sampling time sequence data. By eliminating state fluctuations in the sampling timing data through de-jitter processing, de-jittered sample values ​​are obtained. Furthermore, by eliminating abnormal spikes and noise effects in the de-jittered sample values ​​through anti-interference processing, a stable signal is obtained.

[0009] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for generating the device status determination result are as follows: The stable signal is input into the state determination machine and a quality factor constraint determination is performed to obtain the determination credibility. The consistency of the determination credibility is verified to obtain the accuracy of the decision judgment. Threshold comparison and gating are performed on the reliability of the judgment and the accuracy of the decision to generate the equipment status judgment result.

[0010] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for constructing the status determination machine are as follows: The input layer receives the stable signal and initializes the state set and transition conditions. The preprocessing layer aligns and differentiates the stable signal to generate observations. The evaluation layer receives observations, calculates the quality factor, and combines it with the judgment confidence to form a verification quantity. The gating layer is implemented by integrating a threshold configuration structure, a threshold comparison structure, and a gating logic judgment structure. The gating layer compares the signal quality and the verification quantity with their respective corresponding thresholds to generate a transfer permission. When the transfer permission is met, the state transition layer matches the transfer conditions and updates the state set. The output layer generates the device state determination result based on the state set, thus forming the state determination machine.

[0011] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for obtaining the monitoring event set are as follows: Compare the device status determination results with the preset anomaly determination rules in the operation and maintenance rule base item by item, output the anomaly type, and mark the status anomalies that appear in the device status determination results as high-value monitoring events. The running / standby switching events that occur in the equipment status determination results are marked as general monitoring events after recording the switching direction and the time of occurrence. The periodic heartbeat events that appear in the device status judgment results are marked as low-value monitoring events after recording the heartbeat cycle and arrival time. High-value monitoring events, general monitoring events, and low-value monitoring events are aggregated to obtain a monitoring event set.

[0012] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for generating deduplicated event receipts are as follows: Read the event work order priority of the monitoring event, generate event fingerprints according to the high work order priority, perform event deduplication on high-value monitoring events, if deduplication fails, follow the work order reporting path, obtain the acceptance number if the reporting is successful, and generate a high-priority receipt. General monitoring events are merged and deduplicated according to time windows based on medium work order priority. If deduplication fails, the asynchronous queue reporting path is used. If the reporting is successful, the message number is obtained and a medium priority receipt is generated. Value monitoring events are frequency-limited and deduplicated according to low work order priority. If deduplication fails, the batch summary and reporting path is followed. If the reporting is successful, the batch number is obtained and a low-priority receipt is generated. High-priority, medium-priority, and low-priority receipts are aggregated by event identifier and deduplicated to generate deduplicated event receipts.

[0013] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the steps for real-time determination of the reachability of the remotely reported path based on deduplication event receipts to obtain the path reachability status are as follows: Based on the deduplication event receipt, read the corresponding remote reporting path, receipt result and generation time information, obtain path receipt information, and make real-time judgment on the reachability of the remote reporting path; Mark successful receipts in the path receipt information as reachable, mark consecutively failed receipts in the path receipt information as unreachable, and mark the path receipt information where receipts alternate between success and failure as restricted reachable. The reachable, unreachable, and restricted reachable states are marked as corresponding path reachability levels, and the path reachability levels are associated with the corresponding remote reporting paths for storage, thereby obtaining the path reachability status.

[0014] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for selecting an appropriate retransmission strategy based on path reachability to optimize data transmission efficiency and generate a complete status event stream are as follows. Read the corresponding remote reporting path and path reachability level based on the path reachability status, and determine the retransmission strategy for the content to be retransmitted based on the path reachability level. The reachability status in the path reachability level is identified as real-time retransmission, the restricted status in the path reachability level is identified as batch retransmission, and the unreachable status in the path reachability level is identified as temporarily stored content to be retransmitted. The results of real-time retransmission, batch retransmission, and retransmission of temporarily stored content to be retransmitted are merged in chronological order of their generation and written into the event stream record to generate a complete state event stream.

[0015] As a preferred embodiment of the remote monitoring method for the operating status of fully network-adaptive devices described in this invention, the specific steps for generating real-time data for the monitoring interface are as follows: Read status events one by one from the complete status event stream in chronological order, and write the device status corresponding to each status event into the device status record of the server to obtain the current status of the device; The device status is pushed to the remote monitoring interface, which displays the device's operating status in real time and generates real-time data for the monitoring interface.

[0016] The beneficial effects of this invention are as follows: By configuring points and associating them with a rule base, a monitoring strategy set is generated, enabling strategy-based data collection and network-wide adaptation; then, stable signals are obtained through jitter reduction and anti-interference, and quality constraints and consistency verification are performed by a status determination machine to achieve reliable status determination and suppress false judgments; in particular, events are processed hierarchically according to work order priority and deduplicated receipts are generated, enabling priority reporting of key events and redundancy control; and based on the receipt determination path reachability status linkage supplementary transmission strategy, a continuous and verifiable status event stream is formed, balancing transmission efficiency and real-time monitoring display, thereby ensuring the integrity, temporal consistency, and reliability of monitoring status in complex networks and high-concurrency scenarios. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart for a method of remotely monitoring the operational status of network-adaptive devices.

[0019] Figure 2 A flowchart for generating device status determination results.

[0020] Figure 3 A flowchart for obtaining the reachability status of a path.

[0021] Figure 4 This is a flowchart of the supplementary transmission strategy and the complete state event flow. Detailed Implementation

[0022] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0023] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0024] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0025] Reference Figures 1-4As one embodiment of the present invention, this embodiment provides a method for remote monitoring of the operating status of fully network-adaptive devices, comprising the following steps: S1. Configure the data collection points of the monitored devices in the remote monitoring terminal, and build the corresponding operation and maintenance rule base for the monitored devices on the monitoring server to generate a monitoring policy set.

[0026] S1.1 Select the monitored device in the remote monitoring terminal, enter the configuration process, add the collection points one by one in a fixed order and save them, and submit the collection points to the monitoring server through the remote monitoring terminal to obtain the collection point configuration package.

[0027] Furthermore, the configuration process involves adding and saving data collection points one by one in a fixed order. The saving operation writes the data collection points into the configuration record of the remote monitoring terminal and confirms the addition of the data collection points. After the configuration process is completed, the remote monitoring terminal submits the data collection points in the configuration record to the monitoring server. The submission operation sends the data collection points in the form of a submission request and confirms the submission request. After receiving the data collection points, the monitoring server generates a data collection point configuration package. The remote monitoring terminal initiates a request to obtain the data collection point configuration package and receives the data collection point configuration package, thus completing the acquisition of the data collection point configuration package.

[0028] S1.2 Based on the data collection point configuration package, the monitoring server generates and saves operation and maintenance rule entries for each monitored device, accumulates them to form an operation and maintenance rule library, associates the operation and maintenance rule library with the data collection points, and generates a monitoring strategy set.

[0029] Furthermore, the monitoring server reads the collection points from the collection point configuration package and generates maintenance rule entries one by one according to the collection point order (including collection point identifier, corresponding device identifier, collection protocol type, collection parameter configuration, data parsing rules, anomaly judgment rules or status judgment conditions, and rule activation control parameters). After the maintenance rule entries are generated, they are written to the storage location of the monitoring server and the maintenance rule entries are saved. After the monitoring server saves the maintenance rule entries for all collection points, it accumulates and summarizes the maintenance rule entries according to the monitored device dimension to form an maintenance rule library. The monitoring server associates the maintenance rule library with the collection points. In the association process, the maintenance rule entries in the maintenance rule library are established with the collection points in the collection point configuration package, and the association record is saved. The monitoring server generates a monitoring policy set based on the association record.

[0030] It should be noted that the rule activation control parameters include the activation period, hysteresis time, and trigger count threshold, which are used to limit the rule to take effect according to the scan cycle within the specified period, and to constrain the trigger frequency of the event by using hysteresis and the count threshold.

[0031] S2. Use the monitoring strategy set to scan the collection points in real time and sample the equipment status signals. Through jitter reduction and anti-interference processing, obtain stable signals, record the stable signals into the status judgment machine, evaluate the signal quality and the accuracy of decision judgment, and generate equipment status judgment results.

[0032] S2.1. Continuously sample the device status signals at the collection points according to the scanning order and scanning cycle specified in the monitoring strategy set to form sampling time sequence data.

[0033] Furthermore, the device status signal sampling operation is performed on the collection points in the scanning order. It is triggered when each scanning cycle arrives, and the device status signal output by the collection point is read. The reading result is written into the sampling record along with the sampling time. The collection point sampling record is continuously written repeatedly within the scanning cycle specified by the monitoring strategy set to form a continuous sampling process. After the continuous sampling process is completed, the sampling records are arranged and summarized according to the sampling time to obtain the sampling time sequence data covering the scanning order and scanning cycle.

[0034] S2.2. The state fluctuations of the sampling timing data are removed by the jitter removal process to obtain the jitter removal sample value. The abnormal spikes and noise effects of the jitter removal sample value are eliminated by the anti-interference process to obtain a stable signal.

[0035] Furthermore, for the sampled time-series data, the jitter removal process reads the sampled time-series data point by point in the sampling time sequence and identifies state jumps. When a state value is repeatedly switched within a preset time window W or within n consecutive sampling points and the number of switches is not less than m, the corresponding sampling change is determined as a state jump. The jitter removal process performs elimination or merging operations on the sampling points corresponding to the state jumps and outputs jitter-removed sampled values. The anti-interference process reads the jitter-removed sampled values ​​point by point in the time sequence and identifies abnormal spikes and noise effects. The anti-interference process performs smoothing or replacement operations on the jitter-removed sampled values ​​corresponding to abnormal spikes and noise effects and outputs a stable signal.

[0036] It should be noted that state jitter refers to the phenomenon of sampled data repeatedly and rapidly switching between two or more state values ​​in a short period of time (such as switching back and forth between 0 and 1). It is usually caused by interference or critical fluctuations and does not represent a true stable state change.

[0037] Abnormal spikes refer to isolated abrupt changes or a few consecutive points in the sampled sequence after shaking, where the amplitude suddenly deviates significantly from the normal range in a very short time and then quickly falls back. They are usually inconsistent with the actual state changes. Noise effects refer to high-frequency, small-amplitude random fluctuations caused by electromagnetic interference, quantization errors, communication jitter, or sensor background fluctuations, which manifest as continuous jittering of the signal near normal values ​​and reduced stability.

[0038] S2.3 Input the stable signal into the state determination machine and perform quality factor constraint determination to obtain the determination credibility. Perform consistency verification on the determination credibility to obtain the decision judgment accuracy.

[0039] Furthermore, the state determination machine performs quality factor constraint determination one by one. The quality factor constraint determination calculates the quality factor for the stable signal, and the expression is:

[0040] in, The quality factor represents a stable signal and usually takes a value in the range of [0,1]. The closer it is to 1, the better the signal quality, and the closer it is to 0, the worse the quality. This indicates the proportion of outliers (points that exceed the preset range or rules) in the signal; This indicates the proportion of missing data points (i.e., points where no valid signal was collected) in the signal; It indicates the relative degree of fluctuation of the signal (obtained by calculating the standard deviation of the signal within a time window and dividing it by the absolute value of the signal mean). Indicates the degree of relative fluctuation The weights of the impact on the quality factor are derived from the statistical analysis of the CV distribution in historical data and its sensitivity to quality degradation. Indicates the proportion of outliers The weight of the impact on the quality factor is derived from the assessment of the impact of changes in the proportion of outliers on the quality score (such as recognition accuracy and error). Indicates the proportion of missing points The weights for the quality factor are derived from experiments on the impact of the missing proportion on the reliability of the results and the performance of downstream tasks. This represents an exponential function used to non-linearly adjust the quality factor.

[0041] The quality factor is compared with its constraints (which are the criteria for determining whether a stable signal is qualified, usually determined through historical data calibration, rule setting, or online adaptive testing). A higher confidence level is output when the quality factor meets the constraints, and a lower confidence level is output when it does not. After the confidence level is generated, a consistency check is performed. This check compares the confidence levels at adjacent time points and identifies abrupt changes and contradictions. Abrupt changes and contradictions reduce the accuracy of decision-making, while continuous and consistent results improve the accuracy of decision-making.

[0042] It should be noted that the construction process of the state decision machine involves the following specific steps: The input layer receives the stable signal and initializes the state set and transition conditions. The preprocessing layer aligns and differentiates the stable signal to generate observations.

[0043] Furthermore, the input layer receives stable signal sample values ​​and organizes them according to the sampling order, removes duplicate sample values, and fills in missing sample values ​​by linear interpolation of adjacent valid sample values. The input layer initializes the state set and writes the initial state entries, and initializes the transition conditions and writes the change amplitude trigger condition and the continuous satisfaction counting condition. The preprocessing layer receives the stable signal and completes the unified sampling beat alignment. After alignment, the difference between adjacent sample values ​​is obtained to obtain the difference sequence. The stable signal alignment sequence and the difference sequence are spliced ​​together in a fixed order to output the observation.

[0044] The evaluation layer receives observations, calculates the quality factor, and combines it with the judgment confidence to form a verification quantity. The gating layer is implemented by integrating a threshold configuration structure, a threshold comparison structure, and a gating logic judgment structure. The gating layer compares the signal quality and the verification quantity with their respective corresponding thresholds to generate a transfer permission.

[0045] Furthermore, the evaluation layer receives observations and verifies the consistency of observation length and the continuity of observation timestamps. The evaluation layer calculates the mean and variance from the aligned sample values ​​of the observations to characterize amplitude stability. It calculates the root mean square, peak percentage, and sign flip number from the difference sequence of the observations to characterize fluctuation intensity and consistency. Amplitude stability and fluctuation intensity are normalized to synthesize a quality factor. The quality factor, combined with consistency, generates a judgment confidence level. The quality factor and judgment confidence level are combined to form a verification quantity. The gating layer is implemented by integrating a threshold configuration structure, a threshold comparison structure, and a gating logic judgment structure. The threshold comparison structure compares the signal quality with the corresponding threshold and the verification quantity with the corresponding threshold. The gating logic judgment structure synthesizes the comparison results and counts the output transfer permission.

[0046] When the transfer permission is met, the state transition layer matches the transfer conditions and updates the state set. The output layer generates the device state determination result based on the state set, thus forming the state determination machine.

[0047] Furthermore, when the transition permission is met, the state transition layer reads the state set and transition conditions. The state transition layer performs transition condition matching on the current state entry. The transition condition matching includes checking the relationship between the observation and the transition condition threshold and checking the continuous period count. When the transition condition matching is met, the state set is updated and the current state end timestamp, the next state start timestamp, and the corresponding observation summary are written, while the count is reset. The output layer receives the updated state set and generates the device state determination result based on the state identifier of the latest state entry in the state set and outputs it. The state transition layer and the output layer work together to form a state determination machine.

[0048] S2.4. Perform threshold comparison and gating judgment on the reliability of the judgment and the accuracy of the decision-making to generate the equipment status judgment result.

[0049] Furthermore, the threshold comparison compares the judgment confidence level with the judgment confidence level threshold, and the decision judgment accuracy with the decision judgment accuracy threshold. The threshold comparison outputs a pass or fail result. The gating judgment reads the pass or fail result and performs a gating condition combination judgment. The gating condition combination judgment outputs transfer permission when the judgment confidence level meets the judgment confidence level threshold and the decision judgment accuracy meets the decision judgment accuracy threshold. The gating judgment outputs a denial of permission when the judgment confidence level does not meet the judgment confidence level threshold or the decision judgment accuracy does not meet the decision judgment accuracy threshold. The status judgment machine outputs the device status judgment result based on the transfer permission.

[0050] It should be noted that the equipment status determination result refers to the final output given by the status determination machine after threshold comparison and gating judgment, indicating the current state of the equipment and whether state transition is allowed. It usually includes at least the equipment status identifier (such as normal, warning, abnormal, fault, unknown, etc.) and the state transition conclusion (transition to the target state or refuse transition and maintain the current state); it may also include additional information such as alarm flags, reason codes, or suggested actions.

[0051] The reliability threshold is set based on the type of monitored equipment, the characteristics of the acquired signals, and the statistical features of historical stable operating data. It is used to determine whether the current state determination result has sufficient reliability. The decision-making accuracy threshold is set based on the equipment operation experience rules, historical state change patterns, and monitoring business requirements. It is used to set an accuracy threshold for state transition decisions. State transition is only allowed when the decision-making accuracy reaches this threshold, so as to avoid false transitions caused by instantaneous fluctuations or abnormal noise, and to prevent misjudgments caused by instantaneous fluctuations or abnormal noise.

[0052] The confidence threshold and the accuracy threshold for decision-making are independent of each other but work together. The confidence threshold is used to ensure the reliability of the input signal and the decision result, while the accuracy threshold for decision-making is used to constrain the accuracy of the state transition decision. Together, they constitute the decision condition for granting state transition permission.

[0053] S3. Monitor and evaluate the equipment status determination results, obtain the monitoring event set, process the monitoring events according to the event work order priority, select the corresponding remote reporting path, and generate deduplicated event receipts.

[0054] S3.1 Compare the device status determination results with the preset anomaly determination rules in the operation and maintenance rule base item by item, output the anomaly type, and mark the status anomalies that appear in the device status determination results as high-value monitoring events.

[0055] Furthermore, the system reads the status value and occurrence time from the device status determination result, reads the triggering conditions and corresponding exception types item by item according to the preset exception determination rules in the operation and maintenance rule base, performs matching comparison, outputs the exception type and writes the exception identifier into the device status determination result if the match is true, and continues to match the next preset exception determination rule if the match is false. After the preset exception determination rules are compared item by item, the abnormal status of the device status determination result with the exception identifier is marked as a high-value monitoring event.

[0056] It should be noted that the anomaly judgment rules are generally pre-configured by the operation and maintenance rule base. Based on the equipment type and signal characteristics, combined with the protection definition, operation and maintenance experience SOP, and the statistical patterns of historical stable operation and fault work order data, the triggering conditions - anomaly type (which may include level / handling suggestions) are solidified into executable items, sorted by priority, and released in a versioned manner. They can be iteratively updated with new samples and business requirements.

[0057] S3.2. Mark the running / standby switching events that occur in the equipment status determination results as general monitoring events after recording the switching direction and the time of occurrence.

[0058] Furthermore, the status values ​​in the device status determination results are read sequentially according to the time of occurrence, and adjacent status values ​​are compared. The adjacent status value comparison determines the status value to change from running to standby or from standby to running as a running-standby switching situation. After the running-standby switching situation is determined, the switching direction is recorded as running to standby or standby to running. The occurrence time is taken as the occurrence time corresponding to the status value after the switch and recorded. After the switching direction and occurrence time are recorded, the running-standby switching situation is marked as a general monitoring event.

[0059] S3.3. Mark the periodic heartbeat events that appear in the equipment status judgment results as low-value monitoring events after recording the heartbeat cycle and arrival time.

[0060] Furthermore, the system reads the periodic heartbeats appearing in the device status determination results in order of arrival time and writes the arrival time corresponding to each periodic heartbeat into the arrival time record. After the arrival time record is formed, the system selects the arrival times of two adjacent periodic heartbeats and performs a difference calculation. The difference calculation uses the difference between the previous and subsequent arrival times to obtain the heartbeat cycle, and the heartbeat cycle is written into the heartbeat cycle record. After the heartbeat cycle record and the arrival time record are completed, the periodic heartbeats are associated with the heartbeat cycle and the arrival time and marked as low-value monitoring events.

[0061] It should be noted that periodic heartbeat refers to heartbeat-like status events that are repeatedly reported by the equipment at basically fixed time intervals during normal operation, and the difference between adjacent arrival times (heartbeat cycle) is stable or approximately stable.

[0062] S3.4. Summarize high-value monitoring events, general monitoring events, and low-value monitoring events to obtain a monitoring event set.

[0063] Furthermore, high-value monitoring events, general monitoring events, and low-value monitoring events are read in order of occurrence or arrival time, and each event is written to the event summary record. The event summary record retains the event type tag, occurrence or arrival time, and associated information such as device status determination results during the writing process. After the event summary record is written, a duplicate check is performed. Records with the same event identifier and the same occurrence or arrival time are merged, and a monitoring event set is output.

[0064] S3.5 Read the event work order priority of the monitoring event, generate event fingerprints according to the high work order priority, and perform event deduplication on high-value monitoring events. If the deduplication fails, follow the work order reporting path. If the reporting is successful, obtain the acceptance number and generate a high-priority receipt.

[0065] Furthermore, the monitoring event set reads high-value monitoring events and event work order priorities. If the event work order priority meets the high work order priority, an event fingerprint is generated. The event fingerprint generation combines the event identifier, exception type, and occurrence time and outputs the event fingerprint. Event deduplication compares the event fingerprint with historical event fingerprint records. If a match is found, deduplication is considered successful and the process ends. If a match is not found, deduplication is considered unsuccessful and the process enters the work order reporting path. The work order reporting path submits the high-value monitoring event and receives the reporting success result. The reporting success result returns an acceptance number, which is associated with the event fingerprint and written into the receipt record to generate a high-priority receipt.

[0066] It should be noted that after an event is generated, the priority of the event work order is classified according to factors such as the type and severity of the anomaly, the scope of impact and the criticality of the business, the duration and frequency of occurrence, the level of the associated equipment, and historical handling experience. For example, it is divided into high, medium and low. Events that meet the conditions of serious failure or critical business being affected are judged as high priority and are used for subsequent event fingerprint generation and work order reporting path selection.

[0067] S3.6. Merge and deduplicate general monitoring events according to time windows based on medium work order priority. If deduplication fails, the event is reported via an asynchronous queue. If the report is successful, the message number is obtained and a medium priority receipt is generated.

[0068] Furthermore, the monitoring event set reads general monitoring events and event work order priorities. If an event work order meets the medium priority requirement, time window merging and deduplication are performed. The time window length, grouping rules, matching fields (event identifier and switching direction, etc.), and merging strategy are configured by the monitoring server. Time window merging and deduplication reads general monitoring events in the order of their occurrence, groups them into event groups according to time windows, and matches the event identifier and switching direction within each time window. Matching general monitoring events are merged and output; unmatched general monitoring events are retained. If time window merging and deduplication fails, the event is sent to the asynchronous queue reporting path. The asynchronous queue reporting path submits the output result and receives a successful reporting result. A successful reporting result returns a message number, which is written to the receipt record, generating a medium-priority receipt.

[0069] S3.7. Perform frequency limiting and deduplication on value monitoring events according to the low priority of work orders. If deduplication fails, follow the batch summary and reporting path. If the reporting is successful, obtain the batch number and generate a low priority receipt.

[0070] Furthermore, the event work order priority of the value monitoring event is read. When the event work order priority is low, frequency limiting and deduplication are performed. Frequency limiting and deduplication reads the value monitoring events in the order of their occurrence time. The difference between the occurrence times of adjacent value monitoring events is calculated and compared with the frequency limiting condition. If the difference between the occurrence times is less than the frequency limiting condition, it is determined that the deduplication has been successful. If the difference between the occurrence times is not less than the frequency limiting condition, it is determined that the deduplication has not been successful. If the deduplication has not been successful, the batch summary and reporting path is followed. The batch summary and reporting path summarizes the value monitoring events and submits them. If the reporting is successful, a batch number is obtained and a low-priority receipt is generated.

[0071] S3.8. Summarize high-priority, medium-priority, and low-priority receipts by event identifier and remove duplicates to generate deduplicated event receipts.

[0072] Furthermore, after high-priority, medium-priority, and low-priority receipts are generated, they are read in chronological order of generation, and the event identifier, receipt result, and generation time information are extracted and written into the receipt summary record. The receipt summary record is then grouped and summarized by event identifier, with high-priority, medium-priority, and low-priority receipts having the same event identifier entering the same group. Within each group, the receipt result is matched and compared with the generation time information. Records with the same receipt result and duplicate generation time information are merged, and the deduplicated receipt summary result is output, generating a deduplicated event receipt.

[0073] S4. Based on the deduplication event receipt, the reachability of the remote reporting path is determined in real time, the path reachability status is obtained, and an appropriate retransmission strategy is selected based on the path reachability status to optimize data transmission efficiency and generate a complete status event stream.

[0074] S4.1. Based on the deduplication event receipt, read the corresponding remote reporting path, receipt result and generation time information, obtain path receipt information, and make real-time judgment on the reachability of the remote reporting path.

[0075] Furthermore, the system reads deduplicated event receipts in chronological order of their generation and extracts the remote reporting path, receipt result, and generation time information from the receipts, writing them into path receipt information (which refers to the confirmation feedback returned after remote reporting, including whether the result was successfully received or a status code, the reason for failure, and the confirmed message sequence number or timestamp, etc., used to determine path reachability and guide subsequent retransmission). The path receipt information maintains the correspondence between the remote reporting path and the receipt result and records the generation time information. The real-time remote reporting path reachability judgment is based on the path receipt information, reading the receipt results of the same remote reporting path in chronological order, dividing the receipt results into success records and failure records, and statistically analyzing the consecutive occurrence of success records and failure records, outputting the remote reporting path reachability judgment result.

[0076] S4.2 Mark successful receipts in the path receipt information as reachable, mark consecutive failed receipts in the path receipt information as unreachable, and mark the case where the receipts in the path receipt information alternate between success and failure as restricted reachable.

[0077] Furthermore, path receipt information is read and the receipt results are read in chronological order of generation; path receipts with successful results are directly marked as reachable. For consecutive failure receipt identification, receipts for the same remotely reported path are compared chronologically; adjacent failure receipts are considered consecutive failures, and the corresponding path receipts are marked as unreachable. For alternating receipt identification, receipts for the same remotely reported path are compared chronologically; receipts alternating between success and failure are considered alternating receipts, and the corresponding path receipts are marked as limited reachable.

[0078] S4.3 Mark the reachable, unreachable, and restricted reachable states as their corresponding path reachability levels, and associate and store the path reachability levels with their corresponding remote reporting paths to obtain the path reachability status.

[0079] Furthermore, the path reachability level label assigns corresponding path reachability level labels to reachable, unreachable, and limited reachable states, and writes these labels to the path status record. The associated storage reads the remote reported paths and path reachability level labels from the path status record, establishes a one-to-one correspondence between remote reported paths and path reachability levels, and writes it to the associated record. The associated record also writes the generation time information for subsequent updates. The path reachability status retrieval reads the path reachability level corresponding to each remote reported path from the associated record and summarizes and outputs it to obtain the path reachability status containing the correspondence between remote reported paths and path reachability levels.

[0080] S4.4. Read the corresponding remote reporting path and path reachability level according to the path reachability status, and determine the retransmission strategy for the content to be retransmitted based on the path reachability level.

[0081] Furthermore, the remote reporting path and path reachability level in the path reachability status are read and used for matching the content to be retransmitted; the content to be retransmitted is read in the order of its generation time and the remote reporting path identifier is extracted; the retransmission strategy determines the matching of the remote reporting path identifier and the remote reporting path, and if the matching is successful, the path reachability level is obtained; the retransmission strategy determines the comparison of the path reachability level with the retransmission strategy determination rules, and the path reachability level corresponds to real-time retransmission and outputs the real-time retransmission determination result, the path reachability level corresponds to batch retransmission and outputs the batch retransmission determination result, and the path reachability level corresponds to temporarily stored content to be retransmitted and outputs the temporarily stored content to be retransmitted determination result.

[0082] It should be noted that the retransmission strategy determination rules are a set of pre-configured strategy mappings used to convert the path reachability level into specific retransmission methods and control parameters, such as real-time retransmission, batch retransmission, or temporary storage and waiting, and can further limit batch size, retransmission frequency, rate limit and retry interval, etc.; the source is usually formulated and issued by the operation and maintenance platform based on business timeliness and loss tolerance requirements, link bandwidth and cost constraints, device cache capacity and power consumption constraints, as well as historical link quality statistics and stress test conclusions, and supports version maintenance and configuration based on device type or path differentiation.

[0083] S4.5 Identify reachable conditions in the path reachability level as real-time retransmission, identify restricted conditions in the path reachability level as batch retransmission, and identify unreachable conditions in the path reachability level as temporarily stored content to be retransmitted.

[0084] Furthermore, the retransmission strategy mapping reads the path reachability level and performs category identification. Category identification identifies the reachability corresponding to the path reachability level as real-time retransmission, the restricted situation corresponding to the path reachability level as batch retransmission, and the unreachable situation corresponding to the path reachability level as temporarily stored content to be retransmitted. The retransmission strategy mapping writes real-time retransmission, batch retransmission, and temporarily stored content to be retransmitted into the retransmission strategy record. The retransmission strategy record maintains a correspondence with the remote reporting path and is used to select real-time retransmission, batch retransmission, or temporarily stored content to be retransmitted in the future.

[0085] S4.6 Merge the real-time retransmission, batch retransmission, and retransmission results of temporarily stored content to be retransmitted in the order of their generation time and write them into the event stream record to generate a complete state event stream.

[0086] Furthermore, the system reads the real-time retransmission results, the batch retransmission results, and the retransmission results of temporarily stored content to be retransmitted, and extracts the generation time of each of these results. The system then performs a merging process, sorting the real-time retransmission results, batch retransmission results, and temporarily stored content to be retransmitted results in chronological order of generation to form a merged sequence. Finally, the system writes the merged sequence line by line into the event stream record, and outputs the complete state event stream after the event stream record is written.

[0087] S5. The server updates the device status based on the complete status event stream and drives the remote monitoring interface to display the device's operating status in real time, generating real-time data for the monitoring interface.

[0088] S5.1 Read status events one by one from the complete status event stream in chronological order, and write the device status corresponding to each status event into the device status record of the server to obtain the current status of the device.

[0089] Furthermore, the system reads the status events in the complete status event stream sequentially, extracting the device status and the occurrence time information of the status events. Device status writing involves writing the device status and the occurrence time information of the status events into the server's device status record. The server's device status record is located and saved according to the identifier of the monitored device. Device current status acquisition reads the latest written device status and the corresponding occurrence time information of the status events from the server's device status record. The latest write is determined by the maximum value of the occurrence time information of the status events, and the reading result is taken as the device current status.

[0090] S5.2 Push the current status of the equipment to the remote monitoring interface, and display the equipment's operating status in real time through the remote monitoring interface, generating real-time data for the monitoring interface.

[0091] Furthermore, the device status push encapsulates the device status into push content, including the monitored device identifier and generation time information. The device status push sends the push content to the remote monitoring interface and records the push result. After receiving the push content, the remote monitoring interface parses the device status and writes it into the display cache of the remote monitoring interface. The remote monitoring interface displays the device operating status in real time by reading the device status from the display cache of the remote monitoring interface and refreshing the display. The real-time data of the monitoring interface is generated by summarizing the push content and the records in the display cache of the remote monitoring interface.

[0092] In summary, this invention achieves strategic data collection and network-wide adaptation by: generating a monitoring strategy set through point configuration and rule base association; obtaining stable signals through jitter reduction and interference suppression, and performing quality constraints and consistency verification by a status determination machine to achieve reliable status determination and suppress false judgments; especially by processing events hierarchically according to work order priority and generating deduplicated receipts to achieve priority reporting of key events and redundancy control; and forming a continuous and verifiable status event stream based on the receipt determination path reachability linkage supplementary transmission strategy, balancing transmission efficiency and real-time monitoring display, thereby ensuring the integrity, temporal consistency, and reliability of monitoring status in complex networks and high-concurrency scenarios.

[0093] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for remote monitoring of the operating state of a network- adaptive device, characterized in that: include, Configure the data collection points of the monitored devices in the remote monitoring terminal, and build the corresponding operation and maintenance rule base of the monitored devices on the monitoring server to generate a monitoring policy set. The monitoring strategy set is used to scan the collection points in real time and sample the equipment status signals. Through jitter reduction and anti-interference processing, stable signals are obtained. The stable signals are then entered into the status judgment machine to evaluate the signal quality and the accuracy of decision-making, and generate equipment status judgment results. Monitor and evaluate the equipment status determination results, obtain the monitoring event set, process the monitoring events according to the event work order priority, select the corresponding remote reporting path, and generate deduplicated event receipts. Based on the deduplication event receipt, the reachability of the remote reporting path is determined in real time, the path reachability status is obtained, and an appropriate retransmission strategy is selected based on the path reachability status to optimize data transmission efficiency and generate a complete status event stream. The server updates the device status based on the complete status event stream and drives the remote monitoring interface to display the device's operating status in real time, generating real-time data for the monitoring interface.

2. The method for remote monitoring of the operating state of a network- adaptive device according to claim 1, characterized in that: The specific steps for generating the monitoring policy set are as follows: Select the monitored device in the remote monitoring terminal, enter the configuration process, add the collection points one by one in a fixed order and save them, and submit the collection points to the monitoring server through the remote monitoring terminal to obtain the collection point configuration package. Based on the data collection point configuration package, the monitoring server generates and saves operation and maintenance rule entries for each monitored device, accumulating them to form an operation and maintenance rule library. The operation and maintenance rule library is then associated with the data collection points to generate a monitoring strategy set.

3. The method for remote monitoring of the operating state of a network- adaptive device according to claim 1, characterized in that: The specific steps for obtaining a stable signal are as follows: The device status signals of the collection points are continuously sampled according to the scanning order and scanning cycle specified in the monitoring strategy set to form sampling time sequence data. By eliminating state fluctuations in the sampling timing data through de-jitter processing, de-jittered sample values ​​are obtained. Furthermore, by eliminating abnormal spikes and noise effects in the de-jittered sample values ​​through anti-interference processing, a stable signal is obtained.

4. The method of claim 1, wherein the method further comprises: The specific steps for generating the device status determination result are as follows: The stable signal is input into the state determination machine and a quality factor constraint determination is performed to obtain the determination credibility. The consistency of the determination credibility is verified to obtain the accuracy of the decision judgment. Threshold comparison and gating are performed on the reliability of the judgment and the accuracy of the decision to generate the equipment status judgment result.

5. The remote monitoring method for the operating status of fully network-adaptive devices as described in claim 4, characterized in that: The specific steps for constructing the state determination machine are as follows: The input layer receives the stable signal and initializes the state set and transition conditions. The preprocessing layer aligns and differentiates the stable signal to generate observations. The evaluation layer receives observations, calculates the quality factor, and combines it with the judgment confidence to form a verification quantity. The gating layer is implemented by integrating a threshold configuration structure, a threshold comparison structure, and a gating logic judgment structure. The gating layer compares the signal quality and the verification quantity with their respective corresponding thresholds to generate a transfer permission. When the transfer permission is met, the state transition layer matches the transfer conditions and updates the state set. The output layer generates the device state determination result based on the state set, thus forming the state determination machine.

6. The remote monitoring method for the operating status of fully network-adaptive devices as described in claim 1, characterized in that: The specific steps for obtaining the monitoring event set are as follows: Compare the device status determination results with the preset anomaly determination rules in the operation and maintenance rule base item by item, output the anomaly type, and mark the status anomalies that appear in the device status determination results as high-value monitoring events. The running / standby switching events that occur in the equipment status determination results are marked as general monitoring events after recording the switching direction and the time of occurrence. The periodic heartbeat events that appear in the device status judgment results are marked as low-value monitoring events after recording the heartbeat cycle and arrival time. High-value monitoring events, general monitoring events, and low-value monitoring events are aggregated to obtain a monitoring event set.

7. The remote monitoring method for the operating status of fully network-adaptive devices as described in claim 1, characterized in that: The specific steps for generating the deduplication event receipt are as follows: Read the event work order priority of the monitoring event, generate event fingerprints according to the high work order priority, perform event deduplication on high-value monitoring events, if deduplication fails, follow the work order reporting path, obtain the acceptance number if the reporting is successful, and generate a high-priority receipt. General monitoring events are merged and deduplicated according to time windows based on medium work order priority. If deduplication fails, the asynchronous queue reporting path is used. If the reporting is successful, the message number is obtained and a medium priority receipt is generated. Value monitoring events are frequency-limited and deduplicated according to low work order priority. If deduplication fails, the batch summary and reporting path is followed. If the reporting is successful, the batch number is obtained and a low-priority receipt is generated. High-priority, medium-priority, and low-priority receipts are aggregated by event identifier and deduplicated to generate deduplicated event receipts.

8. The remote monitoring method for the operating status of fully network-adaptive devices as described in claim 1, characterized in that: The specific steps for obtaining the reachability status of the path are as follows. Based on the deduplication event receipt, read the corresponding remote reporting path, receipt result and generation time information, obtain path receipt information, and make real-time judgment on the reachability of the remote reporting path; Mark successful receipts in the path receipt information as reachable, mark consecutively failed receipts in the path receipt information as unreachable, and mark the path receipt information where receipts alternate between success and failure as restricted reachable. The reachable, unreachable, and restricted reachable states are marked as corresponding path reachability levels, and the path reachability levels are associated with the corresponding remote reporting paths for storage, thereby obtaining the path reachability status.

9. The remote monitoring method for the operating status of fully network-adaptive devices as described in claim 8, characterized in that: The steps for selecting an appropriate retransmission strategy based on path reachability status to optimize data transmission efficiency and generate a complete state event stream are as follows. Read the corresponding remote reporting path and path reachability level based on the path reachability status, and determine the retransmission strategy for the content to be retransmitted based on the path reachability level. The reachability status in the path reachability level is identified as real-time retransmission, the restricted status in the path reachability level is identified as batch retransmission, and the unreachable status in the path reachability level is identified as temporarily stored content to be retransmitted. The results of real-time retransmission, batch retransmission, and retransmission of temporarily stored content to be retransmitted are merged in chronological order of their generation and written into the event stream record to generate a complete state event stream.

10. The remote monitoring method for the operating status of fully network-adaptive devices as described in claim 1, characterized in that: The specific steps for generating real-time data for the monitoring interface are as follows. Read status events one by one from the complete status event stream in chronological order, and write the device status corresponding to each status event into the device status record of the server to obtain the current status of the device; The device status is pushed to the remote monitoring interface, which displays the device's operating status in real time and generates real-time data for the monitoring interface.

Images